NFE Core Editor v2 byDoctorly [updated 28-05-2011]

by **ChaOs_DimeNsiOn** Sun Jun 05, 2011 4:20 pm

Akhirnya di release juga tool yang bisa edit core.Penantian panjang untuk CFW E63 dan sejenisnya akan segera berakhir gan.Walopun tool ini belum perfect untuk mengedit semua partisi rofs1 dan core,tp paling tidak E63 dan sejenisnya akan jd permanent hacked.

[You must be registered and logged in to see this image.]

This NFECore2, NOKIA firmware is used
to modify the core package file. This file
is the key to the firmware file is the file
Size the general characteristics of the
largest (except for a large language
pack, the original is the largest), the most complex structure, the file name
contains "core" "C00" and so forth. This
tool is only allowed to deliver before
the file information, but can not be
modified. Since the number of 600
models were lucky to find and verify changes, the core package can modify
the rofs partition.
We thank the TX. I was not sure who
are those people, but according to the
order of posting, is the Saipan xiaognef
and OPDA model area of 600 leaves.
Thank them for their willingness to
share this strange technology. On the basis of their work, this
NFECore2, to NOKIA for all current
models (Saipan 3, S60v5, S60v3fp2,
S60v3fp1) complete the following
modifications:
(1) unpack the core package ROFS1 partition file;
(Note that only ROFS
partition, there are other file is the core
package can not be changed, so do not
unpack)
(2) modify ROFS partition files and
packaged;
(3) modify the firmware of the
calibration parameters (see 600
models);
(4) Check ROFS partition size, if
possible, can expand ROFS1 partition
space;
(5) If necessary, the core package can
be modified for any file CRC32 values. Second, open the core package file
Start screen in "Open File" button to
start a dialog box, select the core
package file.
Drag and drop files directly to the
window of a core package, but also open the core package file.
Note that the interface in the "Related"
button, you can NFECore2 add Explorer
context menu.
This is more convenient
to open the file.
Open the file later, NFECore2 will read out all relevant information. The upper
part of the file's CRC32 CRC32 value
and location of proposed changes.
Displayed in the lower part including the
file directory, ROFS partition the total
capacity and remaining capacity. Figure Third, pack unpack
No difference between this operation
and NFE, after unpacking, editing ROFS
directory, DIY, and then select the
package you can, pack the files after
the directory in NFECore2 Repack directory. Package can check the
Chinese characters. And NFE of the
most important difference is that if the
capacity gauge package, will terminate
immediately packaged, gives tips. If you want to maintain the CRC32
value, click the "Keep CRC32" can be.
Note, however, where maintaining
CRC32, need to enter the 16 hex
values. This position requires careful
selection. Models are generally non-fp1 place in the 0x11. fp1 the difference
between the position of aircraft is
relatively large. Because E71 event, I
suggest fp1 models do not choose to
keep CRC32. Note that the package before the first
modified calibration, this calibration
changes to be effective. Fourth, change validation Important, this change must verify the
dialog press the "OK to return", do not
fork out, it will mess reform. This is a
newly discovered BUG. This operation is to help the TX
modification check. Please read the
specific principles and leaves Saipan
xiaognef posts.
Figure: Note that the general value of the
original firmware is 2B, non-fp1 models
can be changed to 2A. fp1 models into
2A may not, be changed to 2C. Other
values have not tried. The consequences of mistakes in what I do
not know, please tell us tried TX. Specified, if it is N78, 5320 such
models, as well as many original fp1
models need to be deleted to bypass
some of the language in paragraph 5D
check the package, or need to replace
the head of the language pack to bypass validation, Please note that
these language packs for "bypass"
operation no longer have to check, and
I do not recommend using previously
been "bypassed" treatment of the
language pack, but directly use the original firmware, language pack to DIY. Anyway, keep in mind that, with 600
ways to modify the calibration model
after the original firmware to make use
of the language pack rofs2, 3 files to
DIY. I produced a large language pack is
also OK, but it must be sent to my files, modified might not be. Principle is rofs2,
3's head must remain consistent with
the original. Change the parity change in the source
file directly, please do yourself a
backup. V., ROFS capacity adjustment
(expansion)
There are some models and some
versions of firmware, ROFS1 not used in
some space, which is NOKIA keep
spare, used to upgrade the core package ROFS1 reserved space.
NFECore2 can check whether there is
such a space, and can modify ROFS1
partition size to the maximum. This
modification does not affect the rofs2, 3
files, they can still use. Expansion of operations at any time to give up.
Expansion of operations to change in
the source file directly, make your own
backup. Figure Reaffirmed:
1. Core package changes and there is
great risk of brush than change the
language many times greater risk of the
package, be sure to carefully decide
whether to amend. This tool may not be suitable for beginners.
2. S60v3Fp1 TX models do not use this
tool to temporarily change the core
package. fp1 models may need to
continue using large language pack. 3. In the modified checksum expansion
operation, NFECore firmware will check
for problems. If you do not meet the
characteristics of the original firmware
file, to be safe, NFECore will cancel the
operation.
4. The core package to do your own
backup file, modify the checksum
operation and expansion of operations
directly modify the source files.
Yang mau nyoba silahkan CEKIDOT