Talk:Hardware flashing: Difference between revisions
m (→A/B Trick) |
m (→A/B Trick) |
||
| Line 2: | Line 2: | ||
(to be inserted in main page later) | (to be inserted in main page later) | ||
The A/B trick is a solution found by DiGiTaLAnGeL to write his Macronix NOR. <br /> | The A/B trick is a solution found by DiGiTaLAnGeL to write his Macronix NOR (but can be tried on other NORs as well). <br /> | ||
Some Sectors of his flash were "slow to write" and using the normal flashing procedure was resulting in a fail or in a freeze of the ProgSkeet Flasher. | Some Sectors of his flash were "slow to write" and using the normal flashing procedure was resulting in a fail or in a freeze of the ProgSkeet Flasher. | ||
Revision as of 14:42, 3 September 2011
A/B Trick
(to be inserted in main page later)
The A/B trick is a solution found by DiGiTaLAnGeL to write his Macronix NOR (but can be tried on other NORs as well).
Some Sectors of his flash were "slow to write" and using the normal flashing procedure was resulting in a fail or in a freeze of the ProgSkeet Flasher.
Needed tools:
- Download Progskeet Flasher v110811-A
- Download Progskeet Flasher v110811-B
Step by step guide:
- Shut Down your PS3 if not and be sure that the Progskeet's USB Cable is not plugged in.
- Put your R7 Switch in OFF Position.
- Power on your PS3.
- Wait 20 seconds.
- Put your R7 Switch in ON Position (now Proskeet is recognized by Windows).
- Open Flasher "A" and flash your file (remember to set up the NOR size/sectors!)
- When it reaches 100% , check C:\Proskeet.log, if you found some sectors failed to write... continue to the next step.
- Without powering off your PS3, unplug Progskeet's USB Cable and Close Flasher "A"
- Open Flasher "B" and replug your USB Cable.
- Flash your file (remember to set up the NOR size/sectors!)
- The Flasher will freeze on those "slow" sectors, just wait!
- If after 1 minute your flasher is still stuck on that sector close the flasher.
- Check again your log for sectors failed to write.
If you still have sectors that have failed to write, start again until they successfully write (Rember to check the Progskeet.log because reaching 100% doesn't mean that the sectors have successfully been written)
NAND
NAND (256MB, old FAT models, needs 32 wires, 15 per NAND + GND + VCC)
2 chips: Samsung K9F1G08U0A-PIB0
NOR
NOR 16MB, newer FAT models + Slims
needs 44 I/O wires: 23 address lines:A0-A22 + 16 Data lines:D0-D15 + 5 control lines:
CE#,OE#,WE#,RESET#,TRISTATE (optional:#RY-BY) + GND + VCC
(NB: RY/BY is optional only for Teensy, Progskeet NEED ALL controllines!)
1 chip: Spansion S29GL128N90TFIR2 or Samsung K8Q2815UQB-P14B
NOR uses 1024 byte sector, just as NAND.
- noralizer.rar (9.95 MB) incl. 2 different FAT models (CECHL04-jestero + CECH?-Phiren) pads labeled
- http://hotfile.com/dl/118618929/f6914e0/ps3flasher.tgz.html (note: older version)
Simple dumping NOR from Linux:
dd if=/dev/ps3nflasha of=NOR.BIN bs=1024
Alternatives for Infectus2 and Teensy 2.0++:
- Progskeet (UF6667) : http://twitpic.com/5pk6dz // http://fronttowardsgamer.com/2011/07/15/exclusive-hacker-talks-progskeet-geohot-and-why-he-doesnt-give-a-sht-about-sony/
- quad NAND with Progskeet: http://subirimg.com/images/img2065.jpg