The method of installing firmware in fsm uses 2 different lv2diag.self, one to install the firmware and one to exit fsm. Nothing strange about it.
Well speaking as NOOB in terms of dex it is strange when im familiar with ps3 files, I suppose if I ever have done it before it wouldn't be. And when I write tutorials I write them for NOOBS.
PS3 Slim w/ Rebug Rex 4.30.2, 500GB Internal, 1TB/3TB External; PS2 Fat McBoot w/ Hard Drive; Windows 7 x64 Ultimate
Last game finished: Crysis 3 | Currently Playing: Dead Space 3
Well, speaking of lurkandlearn's tutorial, he sure as heck lurked and learned a lot!
Nice tutorial by the way, although with me, I've recently decided to go back and forth with CEX and DEX and with that, I've just renamed the PUPs with mmOS and have ALL the necessary PUPs in one UPDATE folder, WITH a separate text file stating WHAT firmware is ready for installation, like this:
Originally Posted by /dev_usb0/PS3/UPDATE
...
3.55ODEXFW.txt < States current PS3 Update-ready firmware
PS3UPDAT - KMEAW_355.PUP
PS3UPDAT - DEBUG_355DG.PUP
PS3UPDAT - DEBUG_411.PUP
PS3UPDAT.PUP < Current PS3 Update-ready firmware in use
Using lv2diag.self 's is the procedure for factory service mode (unrelated to dex2cex issues). For example, using factory service mode to downgrade also requires 2 lv2diag.self's. One to tell the console to install the pup, then one to leave fsm. Didn't want people to be alarmed by the use of 2; it's normal.
The dex->cex procedure has been refined, but this is an alternative for those worried about (semi-)brick and don't have a dongle.
great way if one doesn't have a flasher, multiman can write to NOR as its proven with this method
and if you are QA flag'd on CEX before the convert and once you go DEX-CEX again, nothing need to be done, verify the QA settings with the combo after convert, all intact, just re-install OFW355/kmeaw whatever and u have clean CEX+working blu-ray drive, that is with hardware flasher, just shutdown console the normal way and reboot, verify QA and re-install OFW355....
also FSM mode for installing PUPS wil format the drive while installing the PUP so with that u loose all settings etc... not that it saved my ass couple times
First go to 3.55, then you can upgrade to 4.20/4.21 safely and go back to 3.55 with downgrader PUP at will.
Here's a tutorial on how to swap firmwares from hdd (much faster, works on DEX): http://psx-scene.com/forums/content/...hout-usb-1888/
So if i place 3 folders 01/02/03 in /dev_hdd0/updater/
and have
01 - cex 355 kmeaw pup
02 - Rogero's DEX 3.55 v2 downgrader pup
03 - dex 4.21
and im on Rogero's DEX 3.55 v2 downgrader firmware
Could i use mM to flash my cex `original flash` then quit to xmb
then update from xmb using above updater method
turn of PS3 with controller
switch PS3 on from console
would this work without gettin a semi-brick
I've recently decided to go back and forth with CEX and DEX and with that, I've just renamed the PUPs with mmOS and have ALL the necessary PUPs in one UPDATE folder, WITH a separate text file stating WHAT firmware is ready for installation, like this:
3.55ODEXFW.txt < States current PS3 Update-ready firmware
PS3UPDAT - KMEAW_355.PUP
PS3UPDAT - DEBUG_355DG.PUP
PS3UPDAT - DEBUG_411.PUP
PS3UPDAT.PUP < Current PS3 Update-ready firmware in use
Hey G
this way you described, do you have to do any renaming or editing of the pup names before the dex>cex/ cex>dex switch, or are they available in the xmb without editing?
if so can you do a short tut please, as i cannot get them to show up in the xmb how you described
this way you described, do you have to do any renaming or editing of the pup names before the dex>cex/ cex>dex switch, or are they available in the xmb without editing?
if so can you do a short tut please, as i cannot get them to show up in the xmb how you described
The only XMB-accessible PUP is the one that is named PS3UPDAT.PUP, so in order for the chosen PUP to be accessible, you'd have to name the PUP file as PS3UPDAT.PUP, and have the PUPs stored in the /dev_usb000/PS3/UPDATE path, and rename the additional PUPs in the same path so that they don't show up in XMB.
Say for example that I want to install the Official DEX 3.55 firmware after I've flashed the console to have the 0x82 TargetID via mM, and I have all my needed PUPs in one folder - I'd then use multiMAN to rename my PUP as such - see below:
Originally Posted by /dev_usb000/PS3/UPDATE
Before the Renaming Process
PS3UPDAT - KMEAW_355.PUP PS3UPDAT - DEBUG_355.PUP < I'm going to rename this PUP so that it shows up in XMB
PS3UPDAT - DEBUG_355DG.PUP
PS3UPDAT - DEBUG_411.PUP
After the renaming process
PS3UPDAT - KMEAW_355.PUP PS3UPDAT.PUP < Now renamed for XMB access - quit mM, and update via XMB
PS3UPDAT - DEBUG_355DG.PUP
PS3UPDAT - DEBUG_411.PUP
After I've converted to DEX, and I've finished mucking around with the DEX-installed PS3, I'd then flash the original CEX flash dump back via mM, and then after that, whilst still on mM, I'd then rename the PUPs again, as follows:
Originally Posted by /dev_usb000/PS3/UPDATE
Before the Renaming Process
PS3UPDAT - KMEAW_355.PUP PS3UPDAT.PUP < This PUP has ALREADY been renamed for XMB usage, so I'll rename it back to its original name
PS3UPDAT - DEBUG_355DG.PUP
PS3UPDAT - DEBUG_411.PUP
After the initial XMB access-barring renaming process
PS3UPDAT - KMEAW_355.PUP PS3UPDAT - DEBUG_355.PUP < Now renamed so that it cannot be accessed via XMB
PS3UPDAT - DEBUG_355DG.PUP
PS3UPDAT - DEBUG_411.PUP
Back to Square One - before renaming the KMEAW MFW
PS3UPDAT - KMEAW_355.PUP < I'm going to rename this firmware for XMB access
PS3UPDAT - DEBUG_355.PUP
PS3UPDAT - DEBUG_355DG.PUP
PS3UPDAT - DEBUG_411.PUP
After the renaming process
PS3UPDAT.PUP < Now renamed for XMB-level access - quit mM and install via XMB
PS3UPDAT - DEBUG_355.PUP
PS3UPDAT - DEBUG_355DG.PUP
PS3UPDAT - DEBUG_411.PUP