If it has been returned by someone to Sony chances are that the person probably upgraded the console while in FSM to 4.25. However the possibility of exiting FSM may not happen due to it been 4.25 and we would need the LV2Diag.self in order to exit FSM which we do not have. Downgrading is not an option, i guess you are fairly stuck in FSM until a way is found to exit it.
K thanks TitanTX. This console was returned from Sony in FSM with 4.25 installed. They wanted to charge for it to get repaired and the owner said to just return it instead. It was a working console but it didn't read discs so he sent it to Sony and this is how they returned it, in FSM mode still on 4.25.
1. If your PS3 is below 355 SKU (ex:Fat), though it was update firmware issue (bluetooth broken or 356v1 issue) before sent to SONY, so there is nothing special for that case, just downgadre back to 355 using flasher then take out FSM with Lv2diag2.
2. If your PS3 is newest one (ex:3K), so its should be BIG NEWS for any devs...
Yep, tried that. Takes about 4 mins and just returns to XMB still in FSM.
I cant upgrade to downgrade as when I go to UPDATE it says it cant read from USB. I tried different USB drives from different slots and none work. It can see the drive just wont read the update file from it. I tried multiple files.
If I connect to LAN and tell it to update via Internet will it still be in FSM if I update or will that kick it out to normal mode? I'm thinking still in FSM thats why I didn't try it yet.
as i said above, you can not use lv2diag.self as long as your firmware up to 355, so the way to fix your problem is DOWNGRADE back to 355 using Flasher (Progskeet/E3) !!
Do not use FSM dongle anymore after downgrade finish cause your console already FSM, so just use Lv2diag-1.self put into root usb with OFW/CFW 355 wait till the update proses finish. then use second lv2diag.self to exit from FSM.. thats the way to fix your problem !!