To quote: LV2 Loader is a tool for devs to allow the quick testing of modified lv2_kernel.self by launching it from the root of dev_flash without the risk of bricking the PS3 or need for a flasher if the new kernel does not work.
The app will run on any 3.15, 3.41, 3.55 CEX or DEX firmware that has lv1 mmap and lv2 peek and poke patches. It also has udp_printf support which will return the offset of the lv2 boot path in lv1 and a little bit of info about what it is doing.
It works by searching lv1 memory for the lv2_kernel.self boot path then modifying it to point to the root of dev_flash instead. After it finishes searching and patching the path LV2 Loader will reboot lv2 gameos without rebooting lv1.
If the app has already been ran once and the user attempts to run it again before rebooting lv1 or the current lv2 kernel does not have peek and poke it will return you to the XMB.
Using FTP or multiMAN/file manager place your modified lv2_kernel.self into the root of dev_flash on your PS3.
HOW TO USE:
1: Install lv2_loader.pkg
2: Run LV2 Loader from XMB
3: PS3 will beep and reboot. (If you do not hear a beep it has not worked)
NOTE: As long as you do not reboot lv1 you can continue to use the new path and change the lv2_kernel.self each time if you wish.
Q: Can LV2 Loader boot DEX lv2_kernel.self?
A: YES. It will require your PS3 to be QA flagged. Don’t be fooled though. Just because you can boot the DEX lv2 kernel does not mean it will magically function like a DEX. For that to happen it will require more patching but this certainly makes the road easier to figuring it out.
Q: Can LV2 Loader boot lv2_kernel.self from a higher firmware?
A: In testing, booting a 3.56 lv2 kernel resigned for 3.55 worked without any problems. Keep in mind that amongst other things, the ps3 is still using the lower firmware’s appldr so there is no real advantage to doing this at the moment.
Q: Can this brick my PS3?
A: NO, NO, NO. The whole point of LV2 Loader is to prevent this from happening during your development of lv2 patches.
Q: Isn’t the offset for the lv2 boot path the same for all PS3?
A: NO. In testing on five different PS3 we came across seven dramaticly different offsets. Infact one of the PS3 at one stage or another in testing used four of the same offsets as the others and has now returned to the original offset from when we started.
Q: How do I reboot the PS3 without rebooting lv1 hypervisor?
A: Using glevend’s Reboot app will let you reboot the PS3 and maintain the modified lv2 boot path. As a bonus for REBUG users when changing modes with Rebug Selector the PS3 will reboot from the new path as well.
Q: As a user of REBUG firmware, if I boot the DEX lv2 kernel does that mean I am running DEX firmware on a retail PS3?
A: YES. REBUG uses the entire DEX firmware apart from 3 or 4 sprx (to allow QA flag support mainly) and uses the CEX lv2_kernel.self. Booting the DEX lv2_kernel.self will in effect, complete the set.
~ Codename: REBUG
Credit and Thanks:
As always to graf and glevend for the hypervisor work.
Big thanks to Dean for the handy memory mapping tip and adding support for LV2 Loader into multiMAN at the last minute.
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!
To quote: Here is a patched Rebug 0.7 Update Package to enable PSN and v4.25 spoofing on Rebug 3.55.2 Firmware. You must already be using Rebug FW 3.55.2 to use this. If you have already installed Rebug's Official Update 0.7 before, you can still install this. This package relies on you using Rebug's own CEX / DEX Selector to change between 3.55 and 4.25 (PSN access).
I have used all original Rebug files and patched them manually. The 'version.txt' was pulled from the original 4.25 pup. Selfs and 'index.dat' were rebuilt using fail0verflow tools. 'vsh.self.swp' and 'vsh.self.cexsp' are correctly patched to enable PSN access, 4.25 spoofing and switching between Debug and Retail XMB modes without causing RSOD. There are basically 3 modes:
Mode: Normal XMB: Debug = no spoofing (3.55), no PSN access, has 'Debug' options in 'Settings'.
Mode: Rebug XMB: Debug = Spoofed (4.25), PSN enabled, has 'Debug' options in 'Settings'.
Mode: Rebug XMB: Retail = Spoofed (4.25), PSN enabled, no 'Debug' options in 'Settings'.
All above modes are tested working with Reactpsn.
Thanks to Itskamel for his perseverance in sussing out how the fw version should be written in the self. The anonymous source who released the current PSN pass-phrase. Fail0verflow for their tools. Rebug.
Before you install this package, make sure you are in 'normal' mode (3.55) and are not using any other spoofers. If you are, disable and uninstall them. If you have been using FckPSN, put your original 'CA27.cer' back. If you are already spoofed (rebug mode) using Rebug's CEX/DEX selector, use it again to change back to 3.55. Do this by pressing 'L1 + Cross(X)' within the selector. Status should say 'Normal Mode'. Exit selector and check system FW is 3.55.
Now install the 'Rebug_PSN_UPDATE_0.7r3_3.55.2.pkg' from the link below. If you get the message 'same version already installed, continue' select 'YES'.
Now run 'Rebug Unofficial PSN Update Package 0.7r3 (3.55.2)' from XMB (ignore the stuff about v4.11). Select 'YES'. You will get a message 'Update Complete - System Will Reboot'.
After reboot, go back into Rebug's CEX/DEX selector. Press 'L1 + Circle(O)' to activate Rebug mode. Press 'PS' button and exit the selector. System will reboot. Now check in system settings/info that your firmware version says 'version 4.25'.
If it does, you have done the above procedure correctly and you can now log in to PSN. You can also now uninstall 'Rebug Unofficial PSN Update Package 0.7r3 (3.55.2)' from XMB.
Note: If you haven't installed Rebug's CEX/DEX selector, you can find it in 'Install Package Files'/'PS3 Hard Disk'. Both versions 1.5.1 and 1.6.1 work fine. This is for Rebug 3.55.2 Firmware only.
No it is a 3.55.v2 rebug their is higher version like 4.11 dex and 4.21 dex but if you are not technically sound i would not recommend it,you can do a lot more but need some extended knowledge to do the other things, and always a possibility of bricking system so read tutorials and then decide, i chose not to i had it but had glitches so i went back to 3.55 cheers read and decide