[CaptainCPS-X]

Originally Posted by svenmullet But when writing the NOR back using dd, it completely overwrites the flash, so all I did was restore my flash back to exactly how it was when I dumped it, before converting. This was the dump I used to generate the DEX bin, which worked perfectly fine. There's only two reasons I can think of as to why this would brick me, the first is that syscon got updated when I installed 4.11 DEX (or while using the downgrade 3.55 pup), the second is the flash was corrupted somehow, either while writing it, or during transfer from my computer via USB pendrive. (although I double checked the file on the drive by comparing it with the original CEX file, and they were identical in HxD) So it's gotta be some syscon thing. When I receive my E3 flasher I plan to flash back the DEX nor image and I should be okay.

Let me know how it goes when you get the E3 flasher, I am waiting for an E3 flasher as well, but to downgrade a 4.11 NOR PS3. I will definitely make some experiments to clear some things up regarding the conversion back to CEX from DEX.

SeeYa!

[haz367]

ok..just saying that after u cex2dex it, so after installing the dex, did anyone made a new dump after this??! u should if u can and then extract the flashdump, u will see one ROS is empy wich need to be filled, so without knowing u go one with ur stuff, update/downgrade, always leaving that ros folder empty and then u flash back the cex and perhaps something goes wrong...and from 4.xx we use the special downgrade one for that so no problem with syscon hashes(or if was QA flagged before)...could be totally wrong here, just putting it out there cuse not many seem to know this about the empty folder, it can't be anything good anyhow, the e3 flasher wil come to the rescue..good luck

[stussy1]

How about a vote for see how things go before converting

[laundrymoney]

Captain, do you know how to get linux running on DEX?

[sbmotoracer]

I used a flasher to convert back and forth. CEX to DEX and back

I never updated my console beyond 3.55 though.

[gingerbread]

Originally Posted by sbmotoracer I used a flasher to convert back and forth. CEX to DEX and back I never updated my console beyond 3.55 though.

Hardware flasher?

Thanks.

[zaphod]

AVOIDING BRICKS

after a long research and another brick after sucessfully cex2dex on the way back dex2cex i know why it happens...

we forgot a very special point: DEHASHING!!!!

Here my way to the 2nd brick YLOD (also got it fixed by my friend with the progskeet):

the YLOD:
- have sucessfully converted to DEX / installed Rogero DEX 3.55 v2 / No other DEX installed
- playing a little bit with the leaked targetmanager and the debug outputs... nice tool btw
- want to go back to cex...interesting in the way and if i get it running... also want to have blueray-movie back...
- used this way:
- in DEX 3.55 XMB Shutdown the PS3 / Entering FSM with JIG-Dongle / flashed back my ori-cex-flash-file with jaicrab preloader 3.1
- the PS3 shuts down after flashing is cpmplete / Turn it on / FSM comes up checked if there are the "Debug Settings" no they are away.. seems good...
- tried installing CEX-Fw 3.55 with FSM-XMB -> error
- used the Lv2diag.self from ps3devwiki to install the cex-fw / PS3 shuts down / checked Log on usb-stick all ok
- put the FSM-Exit-File on USB-Stick (the one for 3.55) / put it in / PS3 starts and shuts down..
- Turn on PS3 -> YLOD

i used a CEX-CFW 3.55 build with mfw0.2.1 but i have not the latest lv1 patch tcl in it...

so the cfw i used was not "dehashed".... so the syscon say "NO" to it and YLOD...

other important things i found out:

- its not possible to use Multiman for NANDS.. the flashing back WILL NOT WORK!!! tried all Versions also the special debug versions... Preloader 3.1 is NANDs friend.. iam sure that this is not the problem.. always worked..

- you NEED a hardware JIG / Dongle for the FSM Mode.. .the software version is buggy... dont use it in this case!!!!

- use the right Lv2diag files... double check if they are the right ones... best found on ps3devwiki in download... if 3.55 than use the fixed ones for 3.55

- NEVER TURN OFF the PS3 by yourself in the whole process... it will always be shutdown by the used programs in the FSM-Mode

- for fw-flashing use the FSM / Lv2diag.self method and check the log on the usb-stick...

- exiting the FSM is always the last point after finishing all jobs and checking all logs.. NEVER EXIT BEFORE -> YLOD

the tutorial could be made extremly shorter no need for linux to get the root_key... just use the method from naehrwert (atm you have to downgrade to 3.41 to run the server on the PS3 but it seems that a 3.55 version is coming)...

- only use dehashed fw, before converting cex2dex make sure your cfw is dehashed.. (can be done with toggle_qa and the "pressthebuttonstocheck" thing...)

- only way back from DEX2CEX is with 3.55DEX with lv1/lv2 patched / always downgrade any higher version first!

- downgrading form 4.20DEX u have to use a special PUP-File.. (cant proof if it worked, never go higher than 3.55DEX)

thats it... much information i know.. but important to avoid bricking around...
had cost me 2 bricks and much time...

the patch_lv1checks.tcl V2 could be found on ps3devwiki... you have to copy/paste and save the file manually.. all download links are dead that i tried...

hope this helps...

[CaptainCPS-X]

Thanks for sharing this information @zaphod ! This will help many for sure! I appreciate it!

If I can't sell my bricked PS3 to someone with a Progskeet in 1 or 2 months, maybe Ill just buy the whole Progskeet equips and unbrick it. LOL, by that time I will have a collection of four PS3s, 1 Slim, 3 CECHE01 (1 YLOD, 1 Bricked, 1 Working) xD

SeeYa!

[zaphod]

just buy the progskeet-equipment... fix your bricked and YLOD PS3 (mine runs fine.. the YLOD can be fixed if you have the ori-backup.... or just try to read out the nands and patch them with the needed files.. ) then sell the PS3 you dont need...

and with your experience then.. you could offer a NAND-unbrick service :-)

[gingerbread]

@zaphod

1. I have a NAND FAT, from your post I can understand that, if I want to go back to CEX, I can use Preloader Advance 3.1 (Without the special USB dongle)?

2. Once I have entered FSM, I could flash back using the original "backuprflash.bin"? Once flashing is done, do not exit FSM?

3. Does this also mean that, I must perform a system update using a 3.55 CEX CFW while in FSM?

4. Once the update is done, I can exist FSM?

Please clarify.
Thank you.