Difference between revisions of "Downgrading with Hardware flasher"

From PS3 Developer wiki
Jump to: navigation, search
Line 10: Line 10:
 
: The two most accurate ways are to look at the actual dump and the [[Talk:Playstation_Update_Package_(PUP)#Using_fake_upgrade_to_get_lowest_firmware_version_info|MinVer PUP method]] itself, instead of flying blind on [[SKU_Models#Retail_Models|SKU tables]] and [[SKU_Models#Datecode_.2F_Manufacturing_Date|datecodes]]
 
: The two most accurate ways are to look at the actual dump and the [[Talk:Playstation_Update_Package_(PUP)#Using_fake_upgrade_to_get_lowest_firmware_version_info|MinVer PUP method]] itself, instead of flying blind on [[SKU_Models#Retail_Models|SKU tables]] and [[SKU_Models#Datecode_.2F_Manufacturing_Date|datecodes]]
 
 
 
 
=== metldr+bootldr sizes ===
 
{{metbootldr}}
 
 
 
==Patch the dump & Reflash it to the console ==
 
==Patch the dump & Reflash it to the console ==
 
<div style="float:right">[[File:Flowrebuilder-Autopatcher.png|200px|thumb|left|Flowrebuilder : Autopatcher]]<br />[[File:Flowrebuilder-Autopatcher-completed.png|200px|thumb|left|Flowrebuilder : Autopatcher - completed]]</div>
 
<div style="float:right">[[File:Flowrebuilder-Autopatcher.png|200px|thumb|left|Flowrebuilder : Autopatcher]]<br />[[File:Flowrebuilder-Autopatcher-completed.png|200px|thumb|left|Flowrebuilder : Autopatcher - completed]]</div>

Revision as of 00:00, 2 December 2019

NAND flasher downgrader steps

NOR flasher downgrader steps

Downgrading installation steps

Checking console capability of running 3.55

Compare the values found in your dump with those in the metldr+bootldr sizes table

If not having a dump, use the MinVer PUP method

Note:

The mention of minimal version praxis on several other wikipages is only a rough indication.
The two most accurate ways are to look at the actual dump and the MinVer PUP method itself, instead of flying blind on SKU tables and datecodes

Patch the dump & Reflash it to the console

Flowrebuilder : Autopatcher

Flowrebuilder : Autopatcher - completed

For patching you can use:

NAND + NOR patchfile.txt

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 [1])

Reinstall firmware in Factory Service Mode

PSGrade/JIG - in rightmost USB Port - for triggering factory service mode

USBSTICK - content for factory service mode - downgrading

USBSTICK - in rightmost USB Port - for installing in factory service mode

For this step it is required to have the console fully assembled (connected PSU, coolingblock+fan, harddrive, wifi/bt board, blu-ray drive etc).

  1. Use the PSGrade/JIG dongle to trigger Factory Service Mode
    • Remove power from the console (rear power switch or remove powercord)
    • Put PSGrade/JIG dongle in the rightmost USB port (closest to the Blu-Ray drive)
    • Power the console so it is in standby (rear power switch or attach powercord)
    • Press power button on front of the PS3 then immediately press eject within ~100ms
    • If powered on correctly your dongle will light up (usually green) and trigger Factory Service Mode. The PSGrade will then power off the console. If it boots into the XMB with a red FSM logo in the corner you are using an old PSGrade.
  2. Put the Lv2diag.self (see below) and a pre-patched firmware to install (named PS3UPDAT.PUP) in root of your USB Mass Storage Device and plug it in the PS3 (in the same port as the PSGrade).
  3. Turn PS3 on and it will automatically install the firmware you had put there. You will not have anything on the screen, you can only tell it is installing by the flashing USB and PS3's HDD light
  4. PS3 will turn itself off after finishing the firmware installation (If it flashes red the firmware did not install correctly).
    A logfile should be present in root of the USB Mass Storage Device with no errors

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.7 (mirror / MD5:8f8166b25d6bed891f292c77de5c4b28)

for noFSM, use 9.99 downgrader instead: MD5:b67747f529d047d63151786544a58b50

or any firmware with prepatched lv1 (no syscon hash checks)

Note: if your end-goal is a 3.56+ MFW, then it is safer to downgrade first to 3.55. Upgrading in service mode (mostly errors out 0x8002f14e) is never recommended (only lower or same version).

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.7 Rogero is only available as noBD, use that one with normal lv2diag.self

Filename Size Remarks SHA1 MD5 CRC32 CRC16
Lv2diag.self (365.5 KB) 374272 3.55 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 mirrors: http://mir.cr/1HRZ3M2N / http://mir.cr/060LU86N / http://mir.cr/ATL2LSGI / http://www.mediafire.com/download.php?zmcgdgj6sdh87se /

Check the logfile

XMB red square notification - factory service mode

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)


Tip:

You can boot console to XMB while still in FSM, if you want to be really sure it installed fine.

Remarks:

  • If you are using a component cable the image might be garbled.
  • If you are using HDMI, you don't have any screenoutput at all after the "press PS-button" message. (note: conflicting reports on HDMI working or not in FSM)

Getting out of Factory Service Mode

USBSTICK - content for exit 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 (or 4.2x/4.3x MFW later on) on consoles that where previously on 3.56+ (highly recomended)

You can use either or both QA/reFSM way:


reFSM dehashing

  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

Dump the flash first, in case you brick on dehashing, you can easily flash this one back to debrick

  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

  • FSM gets you a installer LOG (QA does not)
  • FSM does not delete ACT.DAT (QA does)
  • FSM can be done without a BD drive with noBD patched firmware (QA needs the BD drive present)
  • FSM can be done without seeing XMB or Recovery (QA needs Recovery and XMB for the QA-flagging package)

Both ways require installing nonpatched firmware to dehash syscon bank. QA-flag can be removed/reset (but it is better to keep it flagged) 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