Uhmm....?? just get the IDPS activation tool and change the Q&A flag of your ps3 retail to get a debug one. Or better say get the Q&A tool.
What do you mean? Setting token with target ID changed you will get Q&A debug? You need to change ID to match debug too? So if i change to 0x82 instead what i have wirting that IDPS to eid than Q&A flagging with tokenator using new IDPS i would receive DEBUG console and able to install debugFW? Seems too easy.
DexL0ve PS3 Patched DEX LV2_Kernel.Self for CEX Consoles Arrives
Following up on the previous update, this weekend PlayStation 3 homebrew development group DexL0ve have made available a PS3 patched DEX LV2_Kernel.Self for CEX consoles followed by a revision below that fixes PS3 crashing issues.
Essentially this PKG release is a patched LV2 DEX (Debug / Test) kernel for CEX (Retail) PS3 consoles based on the recent LV2 Loader release.
To quote: From my limited understanding of PS3 coding and reading the NFO file, that by using the LV2_Loader released by Team Rebug earlier, and by QA flag'ing your CEX machine, this file is basically a patched LV2 DEX kernel that will load fully on your CEX machine and thereby give you some DEX (aka) TEST machine L0VE on your Jailbroken PS3 Console.
From Cyberskunk: Syscall 8, 9, 10 are broken in this lv2_kernel.self. The patch for 3.55 CEX lv2 has been used which ends up point to the wrong offset. The kernel will still work but if an app calls those syscalls the PS3 will crash. Hopefully it was just a mistake and they will fix it..
just read another news before this and seems like this is the answer (?) :
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.
Last edited by CFWfanboy; 02-06-2012 at 12:02 AMReason: Automerged Doublepost