[itskamel]

i myself can say i have never even been into fsm. :D

[zaphod]

interesting... you have a NOR and use MM for flashing...and change fw with normal xmb??

or you have a hardware flasher...lol??

[itskamel]

Originally Posted by zaphod interesting... you have a NOR and use MM for flashing...and change fw with normal xmb?? or you have a hardware flasher...lol??

i have never used mm for flashing and dont own a flasher. i have never had a reason to need to go into fsm.

[zaphod]

sounds more and more intresting...

how did you made your conversion?
which software did you use? (i only know preloader and MM.. sure there have to be more ways...)

maybe with ps3loadx?

a PM would be very kind :-)

[itskamel]

Originally Posted by zaphod sounds more and more intresting... how did you made your conversion? which software did you use? (i only know preloader and MM.. sure there have to be more ways...) maybe with ps3loadx? a PM would be very kind :-)

the very first way. with linux, all the way, someone kindly walked me thru it step by step, took like 8 hours.

[PlayStation 3]

Originally Posted by pereb27 Glad you fixed your issue, however, there is no FSM for DEX. Besides, you used the proper FSM tool for your firmware

Yes there is actually, and I accidentally did use the DEX one.

Usage: ------ When you run the app it will beep once and reboot if successful. Three beeps indicates a failure, report the contents of factory.txt in this thread for help. (Factory.txt will save to the USB flash if you put on in the right most USB port of the PS3.) At this point you will come back up in Factory Service Mode (FSM). Place the Lv2Diag.self on the USB the Lv2diag.self will perform its intended purpose automatically. So be aware of that feature should you not be expecting the PS3 to boot back into the non-FSM XMB. This app will not work on any of the "reDRM" firmwares, aka Cobra or TrueBlue CFW. Install the appropriate pkg for your system; FactoryServiceMode.gnpdrm.pkg for CEX and FactoryServiceMode.pkg for DEX. Leave the USB Flash Drive in the PS3. Run the app and listen for the single beep, you should enter FSM automatically. Rename/copy the Lv2diag_exit.self on the root of the FLASH Drive to Lv2diag.self Note: This release simply exits FSM. Do NOT use the RSOD Lv2Diag released earlier unless you have RSOD. Place the USB Flash Drive in the right most USB port of the PS3. Restart the PS3. When it boots up, you will be out of FSM. Enjoy sticking it to the dongle makers in your own little way.

[zaphod]

Originally Posted by itskamel the very first way. with linux, all the way, someone kindly walked me thru it step by step, took like 8 hours.

understand.... using dd for flashing..

did you use red ribbon rc5 for it?

8hours..hm not a high price so you could completly prevent bricks :-)

have paid my investigations and tests with 2 YLOD-Bricks... but fixable with progskeet..

did you also have gone back 2 CEx and did it work without probs?? things like BD-Movie Support, using the save-games and all the other probs being stated out?

[itskamel]

Originally Posted by zaphod understand.... using dd for flashing.. did you use red ribbon rc5 for it? 8hours..hm not a high price so you could completly prevent bricks :-) have paid my investigations and tests with 2 YLOD-Bricks... but fixable with progskeet.. did you also have gone back 2 CEx and did it work without probs?? things like BD-Movie Support, using the save-games and all the other probs being stated out?

yep used red ribbon and i havnt tried to go back to cex, no need, i have another ps3 on 3.55 rebug. as far as the movie support i havnt even tried to see if it will play. i have only 1 blu ray movie, plus if i want to watch blu ray i have another ps3 on ofw.

[pereb27]

Originally Posted by PlayStation 3 Yes there is actually, and I accidentally did use the DEX one.

What you quoted is DEFINITELY wrong, and proof of that is you successfully went into FSM with that version. If it really was for DEX then you would have either bricked or it wouldn't have worked at all. The gnpdrm pkg is for CFWs that don't support unsigned code execution, while the one that doesn't have npdrm is for the ones that do (aka Kmeaw, Rebug...). You just couldn't get out of FSM because you were doing something wrong when trying to get out of it, not when you used the FSM tool.

I guess that tutorial you quoted was worded like this because you could use both packages in most CEX CFWs but only the second one on DEX. But yeah, that will lead to misunderstandings (and as you can see, already did :P).

[CaptainCPS-X]

Originally Posted by pereb27 What you quoted is DEFINITELY wrong, and proof of that is you successfully went into FSM with that version. If it really was for DEX then you would have either bricked or it wouldn't have worked at all. The gnpdrm pkg is for CFWs that don't support unsigned code execution, while the one that doesn't have npdrm is for the ones that do (aka Kmeaw, Rebug...). You just couldn't get out of FSM because you were doing something wrong when trying to get out of it, not when you used the FSM tool. I guess that tutorial you quoted was worded like this because you could use both packages in most CEX CFWs but only the second one on DEX. But yeah, that will lead to misunderstandings (and as you can see, already did :P).

Indeed, at first when I was writing my NAND CEX-To-DEX guide I thought that they were different tools for both FW, but the only difference is the package. One package will only install on CEX FW and the other on DEX.

I compared both lv2diag_exit.self via hex / hash and they are identical.

So @PlayStation 3 , @pereb27 is right, there is no difference in those packages, only the one I just mentioned.

SeeYa!