Finally after lots of testing TeaM-ACiD1C are proud to announce the third official release of Acid Customised Firmware. For this 3.41.010 release we have mainly concentrated on enabling some debug console options and developing the new Haxx category.
This is only the small start of The Acid Custom Firmware WIP project and we have many more plans for the future. We wanted to get this stable version out there for more thorough testing in the wider community.
Especially as things have changed since we started this project, The Holy grail for Custom firmware Developers : Just today a new homebrew app was released for PS3 that enables full write access to the dev_flash on PS3′s internal flash memory.
Some of the changes you will notice in Acid CFW 3.41.010:
★ New Haxx Category next to game
★ Check option for all games, PS3saves and gamedata (greyed out – Not working yet)
★ Quick sign Up in Haxx
★ Titlestore preview in Haxx
★ Titlestore preview (in game) in Haxx
★ Install Packages in Haxx
★ App/home in Game and Haxx
★ Performance Bar
★ No memory limit
★ Quick preview
★ Clear Cache
★ Owner Information for gamedata
★ Various Icon and text mods – POC
★ SaveData Ps1/2 shows up in JB mode
★ Custom firmware version in System info
★ Some other cosmetic differences
We had a few more ideas we are working on and other things like the – No request event error -showing up which we left out for now until we can do more research and testing.
So Now that we have FULL write access to dev_flash with JaiCraB & ps3mrenigma’s new homebrew app – Mount Alejandro this means we can permanently install Acid Customised Firmware (AcidCFW) onto our Ps3s. Of course for those who dont want to permanently mod thier consoles thats fine too, just use JaiCraB’s other tool Firmloader 0.3 to run from USB. So now we have soft-mod solution and a permanently installable way of runnning AcidCFW.
TeaM-ACiD1C (Formerly Team Jesters Jicence): Cfwprophet, DeViL303, Nev, SK Group, B4rtj4h, LuckLuka.
A few important points to note if modifing your dev-flash permanently:
Using this new write-enabler tool could put your console at some risk as the firmware is fully writeable.
Only you are responsible for your console, Do not attemp to modify your flash if you do not fully accept the risks.
It works well if you understand how to use it, if your not sure ask here and myself (DeViL303) or Cfwprophet will help you anyway we can.
I have personally tested erasing over half of my firmware (entire vsh folder) and my PS3 and I had no problem in reinstalling Sony FW3.41 through recovery menu so it seems fairly safe.
WARNING : DO NOT ATTEMPT TO INSTALL ANY FILES THAT YOU HAVE MODDED YOURSELF ON REAL DEV_FLASH WITHOUT RIGOROUS TESTING FIRST USING FIRMLOADER, THIS WRITE-ENABLER COULD BE A HIGHLY DANGEROUS APP IN THE WRONG HANDS AND COULD BRICK YOUR CONSOLE IF YOU MAKE ANY MISTAKES WHILE COPYING FILES. IF YOU BRICK YOUR CONSOLE YOU CAN BLAME NO-ONE ONLY YOURSELF. APPS LIKE THIS NEW ARE ONLY EXPERIMENTAL AT THIS EARLY STAGE AND MAY NOT BE 100% STABLE ! SERVICE MODE MIGHT SAVE YOU BUT NO GUARANTEES.
Stay tuned for more PS3 Hacks and PS3 CFW news, follow us on Twitter and be sure to drop by the PS3 Hacks and PS3 Custom Firmware Forums for the latest PlayStation 3 scene updates and homebrew releases!
yes, your logic is right, and yes there is a lot more than xmls,rcos and modules involved.I have already got debug firmware to install on one of my ps3s but it doesnt achieve much for the average user and you lose BD video support. We are a step or 2 ahead of that, we have them files for weeks
Now we are digging deeper, there are many parts to the PS3 OS and dev_flash is only one of them.
To all those complaining about booting with a dongle, is it really that much hard work to press eject when booting up once a day? If this fact never changes for 5 years would it really make a difference?
To me it is not a problem, I do it without even thinking about it now.its actually safer for all to use payload and usb / hdd as no permanent changes to ps3 OS, just boot normally and all signs of CFW are gone, is it not just a dualboot setup really.
With the eject button being the trigger for booting CFW, Is this not an ideal setup really as far as safety .Ok its slightly more work to boot into CFW but really are we gamers gone that lazy that one button push is a problem.
Right now we are on the way off dumping the WHOLE flash. Including the boot files and everything else. I'm a step ahead but in case of some lib's from unix can not be emulated on win32 i cant compile (again) a tool that i need for. There for i have to find some one that shares the tool or compile it for me.
To go back on topic after all this i will give a nice new feature for our ACiD CFW to the community.
Its a new payload that direct boots acid cfw from boot up off a usb device.Its untested and need to be compiled too.I to time have some troubles to get pl3 running on my win sys.The tools that will be compiled first will not generated and i need to investigate and fix this.
The new payload_usb_vsh adds redirection to /usb000/PS3/AcidCFW/vsh and is writen by TargTrainer and also committed on github here: github.com/TargTrainer/PL3
If some one wants to test and report back if it works then feel free to do so. The payload_dev of pl3 would be used as base to moddify for our cfw payload.So it includes both peek and poke syscalls.The original one and the clean version from kakaroto.
Many thx to TargTrainer for helping and to all testers.
If this work and we get the new payload running, even if it is after a few bug fix's, i will do first a update version with a few more redirection's added followed of a payload that direct boots off the ps3's internal hdd while to same time we keep original os untouched if booted without cfw payload.
Dont forget to use usb000 for cfw to load and also do not forget to place only the vsh folder from acid cfw into usb:/PS3/AcidCFW/.
usb drive -->> port 1 !!
usb root -->> /PS3/AcidCFW/vsh !!