PS3 Homebrew Status

From GameBrew - a wiki dedicated to homebrew on Video Game Systems.
Jump to: navigation, search
NAND flasher downgrader steps

NOR flasher downgrader steps

Downgrading installation steps

Contents

Dump

Connect your Hardware flashing device and make sure you are getting 100% correct, valid, verified dumps.

Checking console capability of running 3.55

Compare the values found in your dump with those in the table below

metldr+bootldr sizes

You can check metldr and bootldr sizes easily with HxD

  • either after extracting flash with Flowrebuilder and opening seperate files
  • or by looking in the unextracted Flash dump at the correct offset.

This table lists some common known values for your convenience as quick lookup:

IDPS/Target_ID SKU - Datecode / Manufacturing date metldr offset bootldr Notes low
ver
chk
0x2F077 (NOR)
0x80877 (NAND)
0x81E (NOR)
0x4081E (NAND)
0x842 (NOR)
0x40842 (NAND)
size 0xFC0002 (NOR)
0x0 (NAND)
0xFC0012 (NOR)
0x12 (NAND)
01
03
CECHAxx (COK-001) with 1.00 from factory
CECHCxx (COK-002)
ED A0 0E D6 - - - incomplete dump
01
04
CECHAxx (COK-001)
CECHExx (COK-002)
EE 10 0E DD 2A430 2A 3F 2A 3F OK
01
02
DECHAxx (COK-001)
CECHBxx (COK-001)
ED A0 0E D6 2A2E0 2A 2A 2A 2A OK 1.00
03 CECHCxx (COK-002) with 1.00 from factory EB F0 0E BB 30480 30 44 30 44 OK 1.00
01
03
CECHAxx (COK-001)
CECHCxx (COK-002)
ED E0 0E DA 2A3B0 2A 37 2A 37 OK 1.00
05 CECHGxx (SEM-001) E7 B0 0E 77 2E900 2E 8C 2E 8C OK 1.90
05
06
CECHGxx (SEM-001)
CECHHxx (DIA-001)
E7 B0 0E 77 2F200 2F 1C 2F 1C OK 2.30
05
06
CECHGxx (SEM-001)
CECHHxx (DIA-001)
E8 C0 0E 88 2EF80 2E F4 2E F4 OK 2.30
06 CECHHxx (DIA-001) E8 E0 0E 8A 2EF80 2E F4 2E F4 OK 1.97
06 CECHMxx (DIA-001) EA 60 0E A2 2EE70 2E E3 2E E3 OK 1.97
07 CECHJxx (DIA-002)
CECHKxx (DIA-002) datecode 8C
EA 60 0E A2 2EE70 2E E3 2E E3 OK
2.30
08 CECHLxx / CECHPxx (VER-001) E8 D0 0E 89 2EAF0 2E AB 2E AB OK 2.45
08 CECHLxx (VER-001) E8 D0 0E 89 2EB70 2E B3 2E B3 OK 2.45
08
09
CECHLxx (VER-001) with 2.30 from factory - datecode unknown
CECH-20xx (DYN-001) with 2.76 from factory
E8 90 0E 85 2F170 2F 13 2F 13 OK
2.70
09 CECH-20xx (DYN-001) E9 20 0E 8E 2F3F0 2F 3B 2F 3B OK 2.70
0A CECH-21xx (SUR-001) E9 20 0E 8E 2F4F0 2F 4B 2F 4B OK 3.20
03
0B
0B
CECHExx (COK-002W) refurbished
CECH-25xx (JTP-001) with 3.40 from factory - datecode OC
CECH-25xx (JSD-001) with 3.41 from factory - datecode OC
E9 20 0E 8E 2F4F0 2F 4B 2F 4B OK 3.40
0B CECH-25xx (JSD-001) with 3.56 from factory - datecode 0D
CECH-25xx (JTP-001) with 3.56 from factory - datecode 1A
E9 60 0E 92 2F570 2F 53 2F 53 OK 3.50
0B CECH-25xx (JTP-001) with 3.56 from factory - datecode 1B E9 60 0E 92 2F5F0 2F 5B 2F 5B (RLOD+)poweroff @ downgrade 355 3.56
0B
0B
0C
CECH-25xx (JSD-001) with 3.60 from factory - datecode 1B
CECH-25xx (JTP-001) with 3.60 from factory - datecode [N.A.]
CECH-30xx (KTE-001) with 3.65 from factory - datecode [N.A.]
F9 20 0F 8E 2FFF0 2F FB 2F FB "metldr.2"
(RLOD+)poweroff @ downgrade 355
3.60
0D CECH-40xx - - - - - (RLOD+)poweroff @ downgrade 355  ?4.10?

Patch the dump & Reflash it to the console

Flowrebuilder : Autopatcher

Flowrebuilder : Autopatcher - completed

For patching you can use:

  • Hexeditor (e.g. HxD)
  • Flowrebuilder (both NOR + unified NAND)
  • in case of Progskeet, latest Winskeet/iSkeet/YASkeet (both NOR + unified NAND)

NAND

Use NAND patches only on NAND consoles, not on NOR!

Target area Patchfile NAND Offset Paste length Remarks
ROS0 patch1 (7 MB) 0x0C0030 0x6FFFE0 CoreOS (prepatched 3.55)
ROS1 patch1 (7 MB) 0x7C0020 0x6FFFE0 CoreOS (SAME as ros0)
trvk_prg0 (0x91800)
trvk_prg1 (0x92810)
trvk_pkg (0x93800)
patch2 (16 KB) 0x91800 0x4000 one big patch overlapping several revoke area's

(above patches in a single package + autopatcher file: NAND downgrade.rar)

NOR

Use NOR patches only on NOR consoles, not on NAND!

Target area Patchfile NOR Offset Paste length Remarks
ROS0 patch1 (7 MB) 0x0C0010 0x6FFFE0 CoreOS (prepatched 3.55)
ROS1 patch1 (7 MB) 0x7C0010 0x6FFFE0 CoreOS (SAME as ros0)
trvk_prg0 (0x40000)
trvk_prg1 (0x60000)
trvk_pkg0 (0x80000)
trvk_pkg1 (0xA0000)
rvk-040000 (512 KB) 0x40000 0x80000 one big patch
overlapping several revoke area's

(above patches in a single package + autopatcher file: NOR downgrade.rar)

E3 Flasher

Use these instead, otherwise you get into a maze of bytereversing: E3 Manual downgrade patches

Reinstall firmware in Factory Service Mode

For this step it is required to have the console assembled (connected PSU, harddrive, wifi/bt board etc)

  1. Use the PSGrade dongle to trigger Factory Service Mode (in the rightmost USB port).
  2. Turn PS3 on, it will trigger Factory Service Mode and turn off the console.
  3. After triggering Factory Service Mode, put the Lv2diag.self (see below) and prepatched firmware to install (named PS3UPDAT.PUP) in root of your USB Mass Storage Device and plug it in the PS3 (again, in the rightmost USB port).
  4. Turn PS3 on, it will install the firmware you had put there (even though you have no screenoutput, you can see it is busy by looking at the activity led of the harddrive and of your USB Mass Storage Device).
  5. PS3 will turn itself off after finishing the firmware installation.

See also Downgrading with PSgrade Dongle, which also contains alot of ready to use PSgrade HEX files for several dongles.

PUP to use

Rogero V3.4 or any firmware with prepatched lv1 (no syscon hash checks)

Different Factory Service Mode SELFs

NAND

For factory Service Mode install:

  • if using the normal lv2diag : Use a NoBD patched PUP (e.g. Rogero NoBD PUP) (to prevent error 0x8002f057)
  • if using the jaicrab NoBD lv2diag : Use the Rogero normal PUP - see note below (and redump flash after FSM to check both ROS)

note: since V3 Rogero is only available as noBD, use that one with normal lv2diag.self

NOR

Use the normal lv2diag and use the Rogero normal PUP

Only when having a console with a broken bluraydrive, you either:

  • use the normal lv2diag : Use a NoBD patched PUP (e.g. Rogero NoBD PUP) (to prevent error 0x8002f057)
  • use the jaicrab NoBD lv2diag : Use the Rogero normal PUP - see note below

note: since V3 Rogero is only available as noBD, us that one with normal lv2diag.self

Filename Size Remarks SHA1 MD5 CRC32 CRC16
Lv2diag.self (365.5 KB) 374272 3.55 get in FSM * 1ED037740D67FEBACA6449CABFF4E95400C9E2EE 099F33A7967F99E91C07E870FD78B3DB 9338ABF2 4FCC
Lv2diag.self (227.38 KB) 232832 jaicrab noBD patched 180823003B086D9D49BC7F83BEA9C769BF73A5EA 3615770407C0C3FA00D8CA49C8ADB362 25E85CFB EDD0

* recommended default choice, see above notes

Check the logfile

After installation of the firmware, take the created logfile in root of USB Mass Storage Device and look if it contains errors (pastie the log if you want to ask for help online on IRC)

Getting out of Factory Service Mode

If everything went fine without errors, you can take the console out of service mode and enjoy your downgraded console :)

  1. Put the Lv2diag.self (see below) in root of your USB Mass Storage Device and plug it in the PS3 (again, in the rightmost USB port).
  2. Turn PS3 on, it will trigger Factory Service Mode off and shutdown.
Filename Size Remarks SHA1 MD5 CRC32 CRC16
Lv2diag.self (201.42 KB) 206256 get out FSM 329877CBD47B994EC0AFCEA6AF98114FD9E5128B 7A20BFDAE65EEFB47A4425DB1B52DCDE 72740080 502A

Dehashing

Goal: To be able to install unpatched firmwares on consoles that where previously on 3.56+ (highly recomended)

You can use either or both QA/reFSM way:

QA way

  1. Patch as normal downgrader (ROS 0/1 + RVK prg/pkg)
  2. install prepatched firmware in service mode

Above is already done if you just downgraded

  1. Install and run QA-toggle and make sure it beeps as written in that readme
  • Note: for above to work, you need a BD drive connected and married to the console.
  • Note: to make sure you enabled QA, not accidently disable it, do the button combo (if it shows menu, then console is QA-flagged correct. Remove the QA-toggle package to prevent it from getting QA-flag reset).
Set your cursor on Network Settings and press the key combo (all at the same time): L1+L2+L3(press_left_stick)+R1+R2+dpad_down
  1. Poweroff console
  2. Put unpatched official firmware (e.g. 3.55) on USB Mass Storage device as /PS3/UPDATE/PS3UPDAT.PUP and insert in PS3
  3. Boot into Recovery Menu, select "6. System Update" to reinstall firmware.
  4. If installation finishes without error (there will be no logs you can check!) and boots XMB OK, then dehashing was successful. Congrats, you now finished downgrading and dehashing. Console runs 3.55 and any firmware of choice can be installed, no longer needing to be patched for downgrader.

reFSM way

  1. Patch as normal downgrader (ROS 0/1 + RVK prg/pkg)
  2. install prepatched firmware in service mode

Above is already done if you just downgraded

  1. Put console in service mode with JIG (in case you left service mode and ran the prepatched firmware in normal mode)
  2. Use normal lv2diag.self and unpatched official firmware (e.g. 3.55) on USB Mass Storage device in root and let the system reinstall that in factory service mode (FSM).
  3. After installation is finished console will turn off. Check UPDATER_LOG.TXT in root of USB Mass Storage device (it should have "manufacturing updating SUCCESS(0x8002f000)" in end section).
  4. If everything is OK, then reinsert USB Mass Storage device and let it install again.
  5. After installation is finished console will turn off. Check UPDATER_LOG.TXT in root of USB Mass Storage device (it should have "manufacturing updating SUCCESS(0x8002f000)" in end section).
  6. If everything is OK, then console should now be dehashed and no longer brick with any unpatched firmwares.
  7. Replace lv2diag.self for he one getting out of service mode and put in root.
  8. Power on console, it should turn off and not boot XMB.
  9. Remove USB Mass Storage device and boot console normally. If all went well it should load to XMB now. Congrats, you now finished downgrading and dehashing. Console runs 3.55 and any firmware of choice can be installed, no longer needing to be patched for downgrader.

Remarks

ReFSM way is strongly recomended over QA if you do NOT install a nonpatched firmware

Both ways require installing nonpatched firmware to dehash syscon bank. QA-flag can be removed/reset after succesfull dehash, without bricking.


 <domelec> dehash procedure: fsm install ofw
           after console turns off take out usb stick and look at log file, 
           if log is ok then reinsert usb stick and turn on console,
           ofw will then reinstall, after console turns off again 
           take out usb stick and check log, if ok then exit fsm 
 <eussNL> do double FSM OFW, then get out of service mode.
 <eussNL> check everything is working
 <eussNL> THEN and only THEN, you can install whatever you want, in recovery.
 <eussNL> there is no need for factory mode after dehashing complete
 <eussNL> in fact, if everything works on OFW 3.55 after dehashing, 
 <eussNL> you can install Rogero V3.2 in recovery and QA-extra flag it  
 <eussNL> if OFW 3.55 works then you proven that you dehashed
 <eussNL> so after that you can install whatever MFW 3.55 you want
 <eussNL> If for some reason you cannot dehash because of BD or BT errors
          then you can use PS3MFW Builder and the broken Blueray / broken Bluetooth
          tasks. Do not select downgrader patches, or you will not dehash!
 <eussNL> BD error can be persistant if flasher is still attached, 
          see: http://www.ps3devwiki.com/wiki/Talk:Hardware_flashing#BD_drive_not_found_problem
 <eussNL> 3 options: 1. open R7/R8  /  2. remove flasher control lines / 3. remove all flasher wiring
 <playonlcd> i  think you can update on wiki "dehashing with jaicrab is not recommended
             and will not dehash as needed and thus semibrick by syscon hash panic