Waninkoko CFW - Nice try, but not ready for prime time yet...

OK, by now, we've all heard about the bricked Phats with 256 NANDs. No way to unbrick them without soldering in a NAND flasher; but those who have installed it successfully are reporting all sorts of issues - XMB halting, errors with backups, etc...

I applaud Waninkoko for his efforts, and am eternally grateful for his work on the Wii, but perhaps he might take a step back, look at flukes1's approach, and create a new CFW that isn't as problematic (I hate to say "buggy" here, as the problems seem to relate to the heavy lv2 modifications)

If flukes1's CFW solution is woprking for backup managers, I say we should test it and hammer on it and see what comes out of that, instead of rushing into Waninkoko's first release. I'm sure his next release will be far more solid, but until then, proceed with caution.

Just my 2 cents worth. Feel free to agree or disagree below!

I have a phat 80 gb, with p3go - 3.41 firmware. UNTIL the custom fw doesnt bring something revolutionary like NTFS and suport for ALL games (all to work), i dont spend time with them. I have games to play, lots of people who brick their ps3, has nothing else to do. Not all but a part must be, they cant stand that you need a dongle and everything work, or almost everything.

Thanks, and excuse my bad english (is not my first language).

I'm on his firmware and I've yet to have a single threatening issue. The only problems I've been having are with my two backups of GT5 and Heavy Rain, they don't want to play nice and panic the kernel. Other than that, everything is running smoothly. [I assume syscall 36 is causing a conflict with those two]

Edit - Heavy Rain and GT5 are both working now, thanks to Rogero!

has flukes1's released a full CFW with working peek/poke and jailbreak then??

Waninkoko is well known in the Wii forums for releasing buggy as hell software and not fixing it for ages. Not surprised, though don't take that as a lack of gratitude.

A patch was released by Wutangrza that has fluke's lv1 patch + lv2 peek/poke (fluke wouldn't release them himself, but it is based off his direct instructions for how to accomplish it), but no BM's will work with it until they poke the syscall into memory themselves for use.

Quote:

---

Originally Posted by chesh

A patch was released by Wutangrza that has fluke's lv1 patch + lv2 peek/poke (fluke wouldn't release them himself, but it is based off his direct instructions for how to accomplish it), but no BM's will work with it until they poke the syscall into memory themselves for use.

---

so waninkoko's release does not require the BM to poke the syscall into memory then??

Have you looked at what he did to lvl2 ?


I am suprised this didnt brick more machines to be honest.

Quote:

---

Originally Posted by sheridan2000

so waninkoko's release does not require the BM to poke the syscall into memory then??

---

He put the payload for JB'ing (syscall 36, etc) right into lv2 instead of poking it into memory with a BM. Not the right way to do it at all and very risky. Comes right back to, "omg omg omg don't patch lv2!"

@Saner: my thoughts exactly!

Quote:

---

Originally Posted by chesh

He put the payload for JB'ing (syscall 36, etc) right into lv2 instead of poking it into memory with a BM. Not the right way to do it at all and very risky. Comes right back to, "omg omg omg don't patch lv2!"

@Saner: my thoughts exactly!

---

So at this stage its probably best to install wutangrza that covers LV1 and wait for a BM mamanger that will work on 3.55 that will poke into memory lv2...think ive got it correct...still working on the lingo ETC