导读：Dark_AleX产品6月12日下午nandflasher 0.1 beta Originally Posted by Dark_AleX由DA发布 nandflasher 0.1 beta nand刷芯片工具0.1beta This tool enables
Dark_AleX产品6月12日下午nandflasher 0.1 beta
Originally Posted by Dark_AleX由DA发布
nandflasher 0.1 beta
This tool enables to perform some advanced operations to psp nands. It works with both, Undiluted
Platinum and PSP-Devolution modchips (or "generic nand programmers", as you want to call them ).
The device is autodected.
The devolution code has not actually been tested much, because I still don't have devolution.
But hopefully, it will work well.
Users without modchips can use some functions of the program: gipl, sipl, gids, sids, glfs, slfs,
t, ts, and 82, if the specified unit is a file. (to know what the hell i'm talking about, go to
t). Anyways they would need to install the drivers of one of them, or simply get from somewhere a file
没有装mod芯片的也可以用这个软件的一些功能:gipl, sipl, gids, sids, glfs, slfs,t, ts, and 82, 如果指定的单位是个文件.(要知道倒底是什么,看t去)
Refer to file t for usage.
- the gui.图形化界面
- A driver to see the nand logical flash as a storage device in windows.可以在windows中以移动设备显示出来的驱动
- Test the devolution code when i have devolution, fix bugs, etc当我装上devolution后,测试deovlution的代码,修正bug.
Nand flasher command line has the following format.
IMPORTANT: before first use of the program, it is recommended (but not mandatory) that you backup your nands.
nandflasher [-options] function parameters
-d: Enables debug writing. It will write to the screen messages and errors not critical.
-n: Disables verification. By default, nandflasher verifies the writing. For speed reasons
you may want to enable this option. Also, in some bad UP installations, the verify won't work
properly, and it is mandatory to use this option.
Before explaining the functions, i will explain a bit about the "units".
There are three units available for UP (up nand, psp nand and file nand), and two in
psp-devolution (psp nand and file nand). The letters that identify these units are u, p and f.
If you specify the file nand, the LAST parameter of the command line must be a file path for
the nand dump (that may exist or maybe created, depending of the function).
Note the the psp nand cannot be written in the UP chip. It will actually attempt to write, and
it will partially do it, but the data written would be corrupt.
* cr source destination.(Copy raw)
Copies the source nand to destination nand in a binary way: if destination has no bad blocks, at
the end of the operation it will be an EXACT copy of source.
This method will probably cause a brick if destination has bad blocks, unless the source was
once dumped from a nand that had the same bad blocks in the same places as destination currently have them.
This method is more aproppiated for dumping purposes.
Example:nandflasher cr p f "ash" - It dumps the psp nand to the file ash.
Example2: nandflasher cr p u - copies the psp nand to the up nand (may not work in all instalations)
A modification of this function is the crs function, that perform the same operation, except that
it skips idstorage blocks.
* cl iplsource idstoragesource lflashsource destination
It copies logical sections from one or more units, to the destination unit.
The logical copy is more secure than raw copy, because it handles bad blocks in all areas
iplsource: specifies the unit containing the ipl. If this parameter is 0, ipl writing will be skipped.
idstoragesource: same as above, but for idstorage.
lflashsource: same as above, but for lflash.
destination: the destination unit.
Example: nandflasher -n cl f p f u "ash" - Write the ipl and the lflash of the file
ash to the up nand, and it copies the idstorage from the psp nand to the up nand.
Example 2: nandflasher -n cl p 0 0 u - Copies the ipl of the psp nand to the up nand.
* gipl unit iplfile
It extrats the ipl from the specified unit and saves it to file iplfile.
Example: nandflasher gipl p n - extracts the psp nand ipl to the file n
EXample 2: nandflasher gipl f n ash - extracts the ipl from the file ash and
saves it into the file n.
* sipl unit iplfile
It sets the ipl of the specified unit, with the contents of the specified ipl file.
Example: nandimage sipl u n - writes the ipl contained in the file n in the up nand.
* gids unit idsdirectory
It dumps the idstorage of the specified unit to the directory specified by idsdirectory.
After the dump, this directory will have an n file which is the index of the idstorage,
and files with names n that have the contents of each key.
EXample: nandimage gids p myidstorage - dumps the idstorage keys and index of the psp nand into the directory myidstorage.
*sids unit idsdirectory
It writes the idstorage contained in the directory idsdirectory to the specified unit.
The format of the directory input is obviously the same dumped by gids function.
Example: nandimage sids u myidstorage - writes to the up nand, the idstorage of the direcrory myidstorage.
* glfs unit lflashimage
Dumps the lflash (logical flash, that contains the filesystems partitions) from the specified unit to the lflashimage file.
This file can be later manipulated with tools such as WinImage. (except in the case of + not OE nands)
Example: nandflasher glfs p a - dumps the lflash from the psp nand to the file a.
* slfs unit lflashimage
Writes the lflash contained in the file lflashimage to the specified unit.
Example: nandflasher slfs u a - writes the lflash dump file a to UP nand.
* t unit
Tests the specified unit blocks, to know which of them are in good or bad state. Note that this
will erase the nand to be tested, so you will have to program it later.
The test consist in erase test, writes block with all 0 with verify,rites block with all 1 with verify.
This action forces the verification even if -n option is specified, so it shouldn't be used in bad up installations.
This is actually the more slow function of all, but at the end you will know in which state is your nand,
and the number of true bad blocks.
Example: nandflasher t u - will test the up nand.
Example 2: nandflasher t p - will test psp nand (only for devolution, remember that erase and write
doesn't work for psp nand in UP).
Example 3: nandflasher t f "ash" - this is the more stupid action you can do with
the program, because it doesn't have much sense to test a dump file :p
A modification of this function is the ts function, that performs the same action, but skips idstorage.
* 82 unit
Patches the specified ta-082 unit so that it can run a firmware based in a ipl.
The function won't do anything if the unit is not a ta82 one.
Here is a list of more usual operations, and their equivalency with the upflasher.
- Dump the PSP nand to the file "ash" (equivalent to upflasher read psp nand):
nandflasher cr p f "ash"
- Dump the UP nand to the file "ash" (equivalent to upflasher read up nand):
nandflasher cr u f "ash"
- Write a nand dump to UP nand.
For a first time programming (when you use chip for first time), you should use:
nandflasher -n cl f p f u "ash"(it is equivalent to the upflasher up nand write).
For next times, it is better to use the following command (except if you screw the up idstorage, then use the
first one again):
nandflasher -n cl f 0 f u "ash"
- Write a nand dump to the PSP nand (only devolution, DO NOT use on UP).
nandflasher -n cl f 0 f p "ash"
- Patch a ta-082 nand (psp nand, only devolution)
nandflasher 82 p甲亢外伤性癫痫微店推广平台