Toggle sidebar

Strange Blue Blinking Wii U

  • Thread starter Thread starter classiphil
  • Start date Start date
  • Views Views 1,194
  • Replies Replies 20
C

classiphil

Well-Known Member
Newcomer
Level 2
Joined
Dec 3, 2017
Messages
61
Reaction score
9
Trophies
0
Age
45
XP
183
Country
Germany
Something new for me:

The Wii U starts, but does not show anything on the screen. (Solid blue)
When I try to trigger PTB I get the blue blinking light. But not when I start it without PTB.

Could this still be DRAM or SLC-Corruption?

Its a WUP-50 Mainboard. The Daughterboards seem to have gotten quite warm. Interestingly enough all the 4 connectors of the cables of the antennas got black?!? The mainboard it self looks flawless.

Thanks.
 
Thanks, but I used that same SD Card on plenty Wii Us. And just before on another one. I recreated it with the most recent version of fw.img now. Same blue blinking after PTB.
Post automatically merged:

Could it maybe be a broken SD card Reader? Or are there any know incompatible Wii U boards for PTB?
Post automatically merged:

Should ptb run without the Wireless-daughterboards?
 
Last edited by classiphil,
At that early stage, the wireless modules shouldn't matter. I build a minute for you, which runs out of sram instead of dram. Maybe that does something.
 

Attachments

  • Like
Reactions: classiphil
Hey, SDIO, this is so awesome friendly of you. Can I buy you a coffe? Drop me a PM.
Although, I have to tell you: Still blinking blue. I don't get this. Without PTB the Drive is started by boot1 so ... I am confused with this Wii U. The good news is, that it does not seem to be the DRAM now.
All the voltages are there, no shorts. No visible damage, apart from the two daughterboards. Maybe there was some fluid involved as the RF-Shield shows rust.
 
Last edited by classiphil,
I think at this point you would have to try defuse. But not sure if it is worth the effort, since there is a real chance something is wrong with the SoC
 
  • Like
Reactions: classiphil
Holy moly. Defuse works without any problem. I have my otp.bin and seeprom now. I will see how I can go on from here.
I can dump SEEPROM, but de_fuse_otp has only zeroes an an e1 in the end.
(So maybe I got my Drive key at least to use the drive on another Wii U) Espresso otp is out. I dont know, what to do with it though ;) So happy still. A sign of live.
 
Last edited by classiphil,
You need to dump otp with prshhax. Since the OTP reading all zeros is how defuse works
 
SDIO said:
There is a option for that in minute
Click to expand...
I pushed that before. But there was an error. SLC soon done. One sec.
Post automatically merged:

boot1 never jumped to payload! Offset or SEEPROM version might be incorrect.
(try it again just in case, sometimes the resets can get weird)
Press POWER/Q to continue.
 
Never did that. Sorry. I will check the console output.
Post automatically merged:

classiphil said:
Never did that. Sorry. I will check the console output.
Click to expand...
Well, I boot from SD boot1. Can you please tell me how to find my boot1 version? With isfshax "installer"?
 
If you go to sync boot1 version it should tell you the version. Just make sure to abort then, since the one in the SEEPROM can't be read without the otp
 
SEEPROM failed to verify!
(Check your otp.bin?)

Primary boot1 params calc: 80331897 stored: 531aa4a7
Secondary boot1 params calc: df82c4b5 stored: 89dfca4d
Decrypted boot1 versions: v21274 (531a) and v35295 (89df)
Decrypted boot1 sectors: 0xa4a7 and 0xca4d

SEEPROM failed to verify!
boot1 version cannot be written to SEEPROM without a valid otp.bin!
Press POWER/Q or EJECT/P to return...

NAND Type: SLC (WiiU)
checking boot1...
Boot1 hash: "3806d41a5c5f139f5b09bbe5b74a5ec45e0f5507"
Boot1 OK!

boot1 version:.............................0x20B9
boot1 NAND sector:.........................0x1000
CRC32:.....................................0x608CDC79
Boot parameres for boot0 about boot1 copy:
boot1 copy version:........................0x20B9
boot1 copy NAND sector:....................0x1001
CRC32:.....................................0x77F7C83A

So... v8377 i suppose?
Booting without de_fuse still gives solid blue.

When I try to mount the SLC with a foreign otp, it is not mountable? Is this maybe a hint. I can dump it though.
Post automatically merged:

Your DRAM-Test finished withou errors.
Post automatically merged:

I followed your toolchain here: https://gbatemp.net/threads/wii-u-failing-during-boot-sequence.637787/post-10266971
It got me this dump.
Post automatically merged:

Now trying your python script.
No luck. Every dump gives me different values.
 

Attachments

Last edited by classiphil,
This one. I think it is by @SDIO. AFAIK as long as you do not see "BA AD AA AA" in the serial monitor, your DRAM should be fine.

You need defuse.You flash the images like the boot1.img of defuse. You use them one after another. So flash the first image. Boot with the SD, watch the serial monitor. Then the second image.
 

Attachments

Site & Scene News

Go to forum More news

Popular threads in this forum

Strange Blue Blinking Wii U

Hacking Homebrew Project  Modernized YouTube for Wii U

Struggling to get WiiFlow/USBLoaderGX to recognize USB sticks

Feedback  Community Overclock Stats: A5X vs B1X Motherboards

Sonic 3 AIR Wii U teaser screenshot

Wii Games Performance on Wii U (vWii C2W Overclock) – Community Testing & Results Sharing

My dad's Wii U cannot install Aroma. HELP!!

Gaming Homebrew Misc Project  Roséverse - a 1:1 Miiverse revival by Project Rosé!