12-14-2010 #21Mbb Guest
or does it means something completely different?
12-14-2010 #22oVERSoLDiER Guest
If you use Alejandro it will overwrite your dev_flash, if you use JailCraB's USB Loader it will be load in the RAM of your PS3. First option is permanently, second option is just till the next boot (RAM will be deleted if you shut down your console).
12-14-2010 #23stinky1978 Guest
I imagine by permanant JB they simply mean that it will allow booting of unsigned code from first boot (no dongle needed). I would expect that it will require you to be just on CFW 3.41.xxxxx
Eventually it would be nice to see them add the hooks from newer firmware added into this one similar to what they do with the wii. Then a simple hex edit to the version number should allow the 3.55 games to run since all the syscals will be where they expect them.
It would be even cooler if we can eventually get to custom boot mode by holding down eject while pressing power (or something) and be like the PSP. Then we can set the back end settings. So people who dont want to have certain menus showing can just disable them, or hide them with a toggle. And you could turn on and off the JB as well.
Hopefully this is going in that direction.
Would be nice if there was eventually a package that will install all this to the PS3 directly without having to run another program first manually overwrite files. It would take away the noob errors
You guys need a custom boot sound added in from the start as well
12-14-2010 #24Mbb Guest
I get it, its called permanent because you can't undo it unless you made a backup and restore the old files?
12-14-2010 #25stinky1978 Guest
Basically it's permanent because it will survive a power cycle. The current method clears as soon as the ram contents are dumped on power down. With a "permanent" JB you could use your boot card to load the CFW on there once, and never need it again.
Think of it as the pandora battery from PSP days.
12-14-2010 #26DeViL303 Guest
Yes, or any other dev_flash backup from any other PS3 on 3.41, there is no difference in dev_flash from EG. slim or phat models on same firmware.
Of course dev_flash2 is unique to your console and contains the registry settings.
12-14-2010 #27B4rtj4h Guest
Please... Keep this topic also as a BUG place!
ANYONE WHO HAS INSTALLED IT PLEASE POST IDEA'S AND BUGS IN HERE!!
do it like this:
Installed via: (what JB stick... PS3Break etc.)
Installation completed 100% without problems?
If no were did it stop?
Found any bugs?
thank you for the contribution! We from Acid1C are gona rock this place!
12-14-2010 #28DeViL303 Guest
Yes, if you have questions about running it please ask in tutorial thread as then others can benefit too from the info.
We have our first feedback from the wider testing being done now that release is out. There is a small issue that is stopping the Backup utility from showing, Im fairly sure this is due to using a certain debug.sprx file.
Can anyone tell me if debug consoles have this backup feature as standard, it will help eliminate problem.
This is where running hybrid firmware will get more complicated for us, as we are trying to add all features from both firmwares but without losing any from each- much testing required. Also as we know the PS+ auto download icon does not show so this may effect PS+ users one day if JB consoles get back online.It would be nice to keep every little feature from both FWs if possible.
12-14-2010 #29Kiriller Guest
Just an idea, how hard would it be to program the xmb so that you can choose either load a totally factory 3.50 or 3.55+ fw to load from one user, and totally cfw or acidfw or just simply jailbroken ps3 from another user. In theory it is possible and attainble, just wondering from dev perspective how hard it may be to code... any input on thisÉ
and thanks to the great release guys, all the hard work is appreciated!
12-14-2010 #30DeViL303 Guest
Just got word that we passed the 3TB of downloads mark on kbx!! Party-time!