Steam recently changed the default privacy settings for all users. This may impact tracking. Ensure your profile has the correct settings by following the guide on our forums.
changed the path where the Pandora RFLASH.ELF looks for the original
EBOOT.
It now looks for the EBOOT as RFLASH.DAT (simply rename it) and when
not found it looks for /PSP/GAME/RECOVERY/EBOOT.PBP
.
added detection of TimeMachine and disabled backup/restore functions
on there, since they don't work propperly on TM.
Complete firmware restore (see below) DOES work fine and is still
enabled on TM.
.
added "slots" for the backup functions.
With those you can have multiple independant sets of backups on your
stick and use them directely without needing to rename folders.
If you DO rename the seperate backup slot folders, their new names
will correctly show up in the Flasher - so you can give them
descriptive names that tell you whats in there.
.
extended the functionality of the backup/restore options.
You can now restore a complete firmware (flash0) regardless of what's
currently installed.
The flash0 files' signcheck is removed during backup and recreated on
restore, so you can even move and flash the backed up firmware on
another PSP (as long as it is the same model, i.e. no Fat FW on a Slim
and vice versa, model is checked to match before flashing to avoid
bricks)!
This might also come in handy for people wanting to flash firmwares
not nativly supported by Recovery Flasher, like 3.60-M33, which never
can be supported since there's no updater for it to extract it from,
but with the right backup you can install it anyway.
Also note that for restoring a complete FW you also need the target
FWs official updater to be on the memstick (RECOVERY folder or
memstick root) as some updater modules are required for initializing
the flash!
(for 3.60 use the 3.52 updater.)
*** UPDATE *** UPDATE *** UPDATE ***
Enjoy!
(first post has been updated with new download )
It's some modules from the DATA.PSP that are needed (that goes for every FW that's going to be restored).
All the other stuff (.RCO, .PRX, IPL) comes from the backup itself.
And since 3.60 is more or less a 3.52, only with Slim hardware drivers instead of Fat ones, the 3.52 updater will do just fine.
<p>Thank you for your work Hellcat. I'll be updating my stick right now.
These new features will be fun to play with.
Thanks so much for your work!!!!!</p>
ok, i get it.
plus, the 3.52 updater modules were also used in FreePlay's 3.60 flasher.
and Hellcat, fabulous app you made!
I'm waiting for the day that anyone makes a 3.60-M33 Universal Flasher.
It could be possible.
An installer that flashes (CFW) 3.60 for most PSP Slims (no TA-088 V3)
but it would be an EBOOT.
all you would need to do is get 360.PSAR (the CFW files)+ 352.PBP( for update modules) and the app would do the rest of the work.
(btw,this is just speculation.)
Or just restore a 3.60 backup to any Slim you wanna have 3.60-M33 on
It does almost what you describe above, only that it doesn't use the 360.PSAR, but it's own backup instead.
<p>@ Illegal Mach</p>
<p>A couple of dots of paint, from a model brush, works good for id'ing all my pandora stuff.
just a thought....
@ Hellcat
thought .1 was the bees knees. And now with all the fixes, adding, and with the updutes. I have say " WELL DONE "
I would still like to know where the brain power
comes from? Is it genetic or does it just pop up
every so often? WHAATEVER it is...lol...Great job on the software...And in case we (your humble followers) haven't said it enough. Thank You for your hard work. Thank You Thank You Thank You Thank You. There that should hold ya, well.., for a couple days.</p>
<p>And that from someone who can't draw straight line with a ruler......</p>
Or just restore a 3.60 backup to any Slim you wanna have 3.60-M33 on
It does almost what you describe above, only that it doesn't use the 360.PSAR, but it's own backup instead.
i know it works, and its great!
but can some dev make a seperate/alternate 3.60-M33 installer that utilizes a 360.PSAR and 3.52 updater modules.
btw, nice app Hellcat!
since this is an app for 3.xx, it doesn't work on 1.50 kernel PSPs.
this app works on 3.60 M33 and higher only.
there is a bug in this app for 3.52 M33-4 and all lower CFW.
1.
your app does a firmware dump on 3.52 and it messes up the folders: 3.52 kernel is kn folder, but app changes it to kd in backup.
2.
plus your app forgets to dump 1.50 kernel which is the real kd folder in all se, oe, and up to 3.52 m33.
3.
module and nodule folders have same exact files.
all of that will lead to a BRICK!
sorry Hellcat, if i sounded harsh, because i wasn't trying to be.
i just wanted to point out the bugs that I found.
those bugs are for 1.50 hybrid CFW ( 2.71 SE through 3.52 M33)
this app's firmware backup/restore only works on CFW independent of 1.50 ( example: 3.71 m33)
*bugs 1 and bug 2 cause a brick. bug 3 wastes flash0 space.
btw, all other functions work fine, only full flash0 restore/backup is bugged. (in 3.52 or lower only)
the bugs do NOT exist in 3.60 or higher.