[playerkp420]

Originally Posted by DebugBrain This happened to me too in the past, there was probably some error in writing with E3, I solved by rewriting the dump NOR, after entering in FSM, the PS3 was still on.

Rewriting the dump to the NOR was not necessary. When the PS3 is suppose to boot to a recovery screen, and it is in FSM. It will not boot if it can't find the Lv2diag.self, to tell it which syscall to activate.

If it doesn't find the command, it can't boot to XMB in that state. So it shuts off, and waits for you to tell it what to do.

@TomIPT Glad to see you got it working.

[DebugBrain]

Originally Posted by playerkp420 Rewriting the dump to the NOR was not necessary. When the PS3 is suppose to boot to a recovery screen, and it is in FSM. It will not boot if it can't find the Lv2diag.self, to tell it which syscall to activate. If it doesn't find the command, it can't boot to XMB in that state. So it shuts off, and waits for you to tell it what to do. @TomIPT Glad to see you got it working.

I had put the Lv2diag.self in pendrive, for some reason the ps3 did not recognize him, after writing the NOR again it worked, so I thought there was some mistake of writing, or simply the ps3 was gone haywire, or maybe the pendrive was faulty, even if the use still today

:Hmmmm2:

[TomIPT]

Thanks for all the help, now running Rogero 4.30 without any issues so far