Talk:E3

How to make a nor backup

1 place a blank micro SD card into the e3 flasher and use the following settings: switch 1 & 2 should be down,

switch 3 should be in the up position, switch 4, 5 & 6 should also be down 2 while in the xmb press the start button on the flasher and backup process will begin (if installed

correctly) you will see each light progess on the indicator from 0% to 100% percent. (once finished the lights will flash alternatively)

E3 Nor dump checker

E3 Nor Dump Checker V1.0.exe (521.7 KB)
Article: http://www.ps3hax.net/2011/11/released-e3-nor-dump-checker-v1-0-released-tested/

Quick bulletproof test

does not test:

• bootldr (corrupted binary not detected)
• metldr (corrupted binary not detected)
• bootldr size (both under- and oversize not detected)
• metldr size (both under- and oversize not detected)
• cISD (didn't catch brick-byte error)
• cCSD (didn't catch brick-byte error)
• trvk_prg0 (didn't catch brick-byte error)
• trvk_prg1 (didn't catch brick-byte error)
• trvk_pkg0 (didn't catch brick-byte error)
• trvk_pkg1 (didn't catch brick-byte error)
• eEID (didn't catch brick-byte error)
• cvtrm (didn't catch brick-byte error)
• CELL_EXTNOR_AREA (didn't catch brick-byte error)

partly test:

• ROS0 (but didn't catch brick-byte error)
• ROS1 (but didn't catch brick-byte error)

does test:

• headerprefix ("00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00")
• header ("00 00 00 00 AC 0F FF E0 00 00 00 00 AD DE EF BE")
• header ("FI.I")
• headersuffix "(FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF")
• filetable ("saceru_eoldare.." etc.)

Conclusion : USELESS, brickdumps will still show as 'valid'.
Recommendation: use Flowrebuilder instead and common sense like mentioned on Hardware flashing page.

Added 22 nov 2011

  New E3 flasher update released, it will backup bios 3 times automatically.
  We suggest user verify those bios with E3 Nor dump checker, to assure the backup bios is no erro. 

Conclusion: Anyone with a flasher (should) know that you can dump it 1 to 1000's times the same bad. Comparing CRC/MD5/SHA1 is not any secure way to validate flash (as mentioned on Hardware flashing). Letting the dumper do it x times, only gives endusers/customers a false sense of reassurance, always a bad idea.

Normal E3 downgrade Process

1. place the e3_downgrade.bin and the bkpps3.bin you made on a micro SD Card.

2. switch 1, 2, 3, 4, 5 should be down and switch 6 (lock/unlock) should be in the up position while in the xmb press start on the flasher and the process will begin. when programming has completed the lights will flash alternately

3. reboot the console and you should see the connect controller using a USB cable screen (if you are just booted back into the xmb you need to manually patch the backup)

4. assuming the process was sucessful and you see the connect controller screen switch off the console from the back of the playstation using the switch provided with the e3 kit and place your USB downgrade jig in the port closest to the flasher.

5. switch the console back on using the switch provided then quickly press the power and eject button if sucessful the console should power off automatically. (if not repeat the process)

6. copy the Lv2diag.self & PS3UPDAT.PUP from step 1 downgrade files onto a usb and place the usb in the same port you had used for the downgrade jig (closest to the flasher) turn on the console and the downgrade process should begin. once finnished the console will turn off automatically

7. next copy the Lv2diag.self onto the usb and place the usb in the same port you used in the last process switch on the console and it should switch off automatically after a few seconds.

8. power the console back on and you should see the connect the controller screen follow the onscreen instructions.

Manual E3 downgrade v2

E3 dumps are byte reversed, and so must our patches (otherwise we have to reverse, paste the v2 in the REV, reverse back again - using byte reversed patches shortcuts that 'reversing confusion' :P)

Dump the flash with the E3, you will end up with a .bin file (e.g. bkpps3.bin)

Patches to insert for v2 downgrade:

target area	patch no.	NOR Offset	Paste length	Remarks
ROS0	patch1.REV (7 MB)	0x0C0010	0x6FFFE0	version string 3.55
ROS1	patch1.REV (7 MB)	0x7C0010	0x6FFFE0	same as patch1.REV
trvk_prg0 (0x40000) trvk_prg1 (0x60000) trvk_pkg0 (0x80000) trvk_pkg1 (0xA0000)	rvk-040000.REV (512 KB)	0x40000	0x80000	one big patch overlapping several area's

save file and use that file to flash the ps3. Afterwards, use RogeroV2, or any prepatched PUP that has the lv1/hypervisor syscon hashchecks patched out - or use the TCL from the talk/discussion page to patch one yourself) and reinstall the firmware in service mode like any V2 downgrade.

Note: If you wish to extract an E3 dump: Flowrebuilder can bytereverse and extract the NOR dump for you.

E3 debricking notes

• Requires soldering wire from SBE (solderpad on NOR flatcable) to TRISTATE (NORpoint on PS3 motherboard)
• Make sure you have correct firmware on SD/TF card
• E3 switches set as 1:Flash fun, 2: OFW, 3: Prog, 4: microSD, 5: PS3 Flash, 6: Lock with the console power disconnected.
• Turn on console to restore (progress LEDs will light up one by one and blink if successfully).
• Unplug powercable and set 1:Flash fun down to PS3 Mode and turn on the PS3, if everything went fine, it will now be debricked (remember: in case syscon has 3.56+ hashes, you need prepatched LV1, see downgrader guides).
  

English-E3 FLASHER repair method if console bricked.pdf (424.95 KB)