Is the lv2 peak/poak really working with WutangRZA/Flukes1 CFW?

[nijhawank]

I think enough discussion on the firmware success and it's proven that WutangRZA firmware is stable.

But did anybody test the real feature i.e. is the peak/poak working after you disable the lv2 security (i.e. after running the lv2protectionremove or lv1dumper. I mean disabling the protection is one thing and then testing whether it really got disabled and we are able to successfully do a peak/poke is another thing.

Did somebody created a test program to do a lv2 peak/poak and did it work?

[chesh]

Yeah, they're linked in the OP of the Wutangrza release thread. The lv1dumper and lv2 protection remover packages.

[nijhawank]

Yeah, they're linked in the OP of the Wutangrza release thread. The lv1dumper and lv2 protection remover packages.

They just disable the lv2 security but what I'm asking is after the security is disabled, did somebody tried peaking/poaking the lv2 memory and was succeeded?

Because it was poaking the lv2 memory that resulted in PS3 getting rebooted on Netkas&Flukes1 earlier CFW.
Did somebody really poak the lv2 memory now and it worked fine?

[fldash]

No one has been successful yet, the PS3 locks up each time.

[nijhawank]

No one has been successful yet, the PS3 locks up each time.

So that may mean 2 things:

1. Security is still not properly disabled and poaking lv2 memory is making PS3 lockup/crashes

or

2. Whoever's trying to poak to lv2 memory, is poaking wrong stuff and/or at wrong regions. Because I see deank (multiman guy) comments that he hasn't received any help from any of kakaroto or hermes or other payload devs about what and where to poak in lv2 memory.

Let's hope later's the case.

[Wutangrza]

No one has been successful yet, the PS3 locks up each time.

This isn't true. (unless you meant no one has successfully poked a PL into memory, that would be true)

Essentially on some consoles the console black screens while actually dumping lv1.bin to the HDD. There have been some users who've had no problem dumping a full 16 MB lv1.bin to their HDD, the first guy who tested my CFW in fact had no problem dumping a full 16 MB lv1 to his HDD (the 2nd of TheAnswer's lv1dumpers ran successfully, white screen, pushed x and exited--no black screen).

TheAnswer posted a new compiled pkg that removes the lv1dumper part from lv1dumper and instead JUST disables lv2 protection. This works on everyone's console.

Flukes1, author of the lv1dumper, mentioned that he experienced this same problem during his testing, and he thought it to be a bug in PSL1GHT.

So the TL;DR is that afaik the "freezing" in the as-is lv1dumper code is in the actual dumping of lv1 to HDD, not in the removal of lv2 protection, as the modified lv1dumper (that doesn't actually dump lv1) runs fine on everyone's console (all it does is disable lv2 protection).

edit: Ah, I think I misunderstood what he was saying. Yes, it's true that no one has successfully poked a PL into memory yet, but people definitely have been able to dump lv1.bin to their HDD via lv1dumper.

[fldash]

It's #2. He'll get no help from anyone either. This is the most drama'd scene I've ever seen. Everyone has an agenda of some sort and rarely does anyone want to help anyone else... Who really knows what's going to happen when Sony releases the next firmware? It may go to more shit than it already is.

I give mad props to Waninkoko for having the balls to do something on his own, and be skilled enough to do it. It stinks that it bricked 256MB NAND machines, but he is the only pioneer I see besides geohot at releasing something to be consumed by the general public.

flukes seems knowledgable and smart, but is scared of Sony. Wutang took his knowledge and made a great firmware when combined with geohots patch, but no one has figured out how to use it yet (or if it's actually usable).

I find it amusing that everyone was jumping all over flukes when he released his first firmware which he said had peek/poke, but it didn't work (at least it didn't brick). But now flukes has joined the crusade against Waninkoko saying this on twitter: @marcan42 Testing is probably not a priority for something which is specifically engineered to enable mass scale piracy.

Hipocracy much?

Edit: Wutangrza, you are correct, I was talking about successfully poking... I had no problem running either of the lv1dumpers on my CECHH 40GB non-256MB NAND. I even got the lv1.bin file.

[nijhawank]

That's fine. We have enough talented people out there and it won't take long before a new hero rises and enables the required syscalls on this firmware.

Somebody can try comparing the Waninkoko CFW, extract and decrypt the lv2 from it and compare it with the originals to find the changes and then make those changes at runtime for this firmware.
The payload is already there only thing to find out are the right addresses.