Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installer freezes and bricks after checksum. #158

Closed
GoogleCodeExporter opened this issue Jun 1, 2015 · 9 comments

Comments

Projects
None yet
1 participant
@GoogleCodeExporter
Copy link

commented Jun 1, 2015

What steps will reproduce the problem?
1. Installed HBC via Smash Stack
2. Ran Priiloader
3. Install freezes after "Checksum complete" message. 

What is the expected output? What do you see instead?

Instead of Priiloader installing the wii becomes bricked to a black screen.

What version of priiloader are you using? On what ios/system menu?

Version 0.6 on System Menu 4.3

Do you have any IOS patches installed? (if so which ios and what patch?)

None, I tried to install Priiloader right after installing the HBC.

What are your wii system menu settings

Not changed, it was same as out of the box.

I was installing homebrew for a friend on their Christmas present wii. Luckily, 
I was able to exchange it for another wii at Wal-Mart, saying it was a gift and 
mentioning nothing of homebrew. The other one I didn't install Priiloader on, 
as I was scared to death to brick two wiis. Any idea why this happened?

Original issue reported on code.google.com by nintendo...@gmail.com on 7 Jan 2011 at 11:23

@GoogleCodeExporter

This comment has been minimized.

Copy link
Author

commented Jun 1, 2015

what were the system menu settings and how the hell can you get it crash like 
that :/

if i could get it to crash like that then i can fix it.

and are you REALLY sure it said checksum success ? cause that means the write 
was correct and was verified as correct. im also not sure why the hell it would 
freeze after a verification

Original comment by dac...@gmail.com on 7 Jan 2011 at 11:52

@GoogleCodeExporter

This comment has been minimized.

Copy link
Author

commented Jun 1, 2015

also pointing out that 0.6 does the check TWICE (when its written to /tmp which 
is harmless and after it is moved to the system menu title...)

Original comment by dac...@gmail.com on 7 Jan 2011 at 11:53

@GoogleCodeExporter

This comment has been minimized.

Copy link
Author

commented Jun 1, 2015

I didn't really check the System Menu settings, but the wii was set up just 
days before, so they didn't have much time to fiddle with them. English, 
widescreen, no internet connection. Not much else.

I'm positive it said checksum success, then just hung there. I had to hold down 
the power button to turn it off, then I'd get a black screen when I tried to 
turn it on.

That's why I posted this, because it's confusing to me too. If everything was 
verified and pretty much all the program had to do was exit back to HBC, why 
would it brick?

The only thing I did different with this installation was ran Priiloader 
immediately after installing the HBC via Smash Stack. I doubt it, but could 
going straight from the HackMii installer to the HBC to installing be the 
problem?

Original comment by nintendo...@gmail.com on 9 Jan 2011 at 4:38

@GoogleCodeExporter

This comment has been minimized.

Copy link
Author

commented Jun 1, 2015

no thats not the problem.

thanks for reporting and ill see what i can do :/

Original comment by dac...@gmail.com on 9 Jan 2011 at 9:35

@GoogleCodeExporter

This comment has been minimized.

Copy link
Author

commented Jun 1, 2015

Issue 166 has been merged into this issue.

Original comment by dac...@gmail.com on 24 Jan 2011 at 7:15

@GoogleCodeExporter

This comment has been minimized.

Copy link
Author

commented Jun 1, 2015

Could be the same, but mine hang in "Patching Tmd..." message, so my question 
is the next is this one of that full bricked wii? And if i cant get in to 
recovery menu is it priiloader changes in the system or any other reason??

Original comment by wam...@gmail.com on 24 Jan 2011 at 7:31

@GoogleCodeExporter

This comment has been minimized.

Copy link
Author

commented Jun 1, 2015

May also be related, I just bricked using the 0.4 installer; it got as far as 
failing the ES_DIverify step, then asked if I wished to continue or quit. I 
chose to exit by hitting the Home button, and the "Aborting mission" message 
appeared as expected, but then the app froze. I let it sit for about ten 
minutes, then held power to shut down. Now powers on to black screen. No 
drivechip or Injectus here, so I believe it's quite thoroughly busted. Anyone 
for spare parts?

Original comment by vaguerant on 25 Jan 2011 at 2:11

@GoogleCodeExporter

This comment has been minimized.

Copy link
Author

commented Jun 1, 2015

yes im in for spare parts.
even if you dont have the keys ill gladly take the parts if you want to send 
them :P

also, i dont think the installer did that as all it does then is a ISFS_Deinit 
which just does a IOS_Close(fs_fd). so its all ios stuff
but ok

Original comment by dac...@gmail.com on 25 Jan 2011 at 6:23

@GoogleCodeExporter

This comment has been minimized.

Copy link
Author

commented Jun 1, 2015

Original comment by dac...@gmail.com on 4 Apr 2011 at 7:14

  • Changed state: Fixed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.