Hacking Cant update Wii U because of cios?

[Deleted member 342493]

no worries, you were only trying to help . Nothing wrong with that .

Thanks for understanding me ! and I know it could be the best, but it could work the sysCheck v2.0.1 by Double_A with this? this Syscheck runs IOS58, I know it is a Wii edition, but it shows some vIOS, could it work? and sorry for the changed font, it's happends when I paste things from anothers sites...

 

[TeamScriptKiddies]

Even if that version of Syscheck does run on the vWii it's not going to give us accurate results as there are too many differences between a physical wii and the vWii

 

[Deleted member 342493]

Even if that version of Syscheck does run on the vWii it's not going to give us accurate results as there are too many differences between a physical wii and the vWii

OK, right, the best thing would be a vWii IOS58 running Syscheck I think, but I don't know how to make that, maybe some Syscheck developer could know... for know the only scanning method that I thing it could work is scanning with the latest Pimp My Wii that it have vWii support (It doesn't install nothing) but that's just me...

 

[TeamScriptKiddies]

That could possibly work. What IOS does that run on?

 

[Deleted member 342493]

That could possibly work. What IOS does that run on?

I don't know... that's why I only saying trying, I hope it launch in his vWii and he could do the report.

 

[TeamScriptKiddies]

bluetailsfox11 this might just work. If Pimp My Wii (vWii edition) happens to run on an unaffected IOS, this might the key to getting a report that we can all review. From there we can give you the next steps for getting this back up and running

Grab the app here: http://www.logic-sunrise.com/en/news-659851-pimp-my-wii-302-hack-your-wii-with-ease.html

It looks like it allows you to run it under a wide selection of various IOS. Try launching the test with various IOS's until you find a winner! That's my advice. It won't write anything to NAND as stated previously by @Goku_Junior

 

[Deleted member 342493]

bluetailsfox11 this might just work. If Pimp My Wii (vWii edition) happens to run on an unaffected IOS, this might the key to getting a report that we can all review. From there we can give you the next steps for getting this back up and running

Be sure to tell him to download the latest version, it's 3.02, and he don't download a old version because it's not designed to use with vWii, he need to use only 3.02 , however, It doesn't do a system report (yeah I need to say this before) it says what IOS are corrupted and they need to be changed, I repeat, if he will use this, he need to use the 3.02 (the latest) for security reasons, and don't install nothing.

 

[TeamScriptKiddies]

Linked updated above

 

[Deleted member 342493]

Linked updated above

OK, I hope it helps a little, I'm going to bed now, the latest version shouldn't touch nothing in the NAND it only reads, he only need to use the report option and nothing more, well I hope it helps.

 

[Bug_Checker_]

just some of the "recent" quotes

Learn what you are doing, don't let a tool do your work.

You will understand better how the console is working, and what you can or can't do.

I agree with Cyan. Anyway, an app doesn't get the nickname "Brick My Wii" from boundless success.

1. It's not firmware, you clearly don't understand how the Wii works. That's probably a result of using BrickMyWii instead of learning what you are doing.
2. BrickMyWii installs a very bad setup, and sometimes patches every single IOS, which is a bad idea as it has the potential for problems.
3. Nothing should be done all-in-one. It's very dangerous. By no means is it fool-proof.
4. You shouldn't be on 4.3 (which again, is just a title, not firmware) anyway.
5. If you take a look at the code, it's a disaster. The translations aren't even done properly, so a lot of the menu doesn't make sense in some languages.

Then you have installed an absolutely terrible setup on over 25 Wiis.

People brick because the programming is terrible, not because they don't know what they are doing. However, you don't use Brick My Wii if you know what you're doing.

Yeah, it's called bad programming.

The main problem with Pimp My Wii is the automation itself. Its strength is its weakness. You shouldn't depend on one program to mess with ALL your system titles in the background. You can't stop in the middle and fix something before it's too late. If anything goes wrong, everything goes wrong.

Another problem is that the author seems to be under the assumption that newer = better. That's not always the case, especially with the Wii. Pimp My Wii installs the latest cIOS and System Menu. The benefit of having multiple slots is that you can have different versions of a cIOS, because some versions work for specific games, some don't. Many people have reported problems with the latest d2x cIOS. 222 and 223 (hermes cIOS) should be v4 to increase compatibility. The System Menu shouldn't be above 4.1 because 4.2+ has less brick protection/recovery options (many people will tell you it doesn't matter, but redundancy for brick protection is VERY GOOD THING), prevents region free for modchips (unless you use the unstable Priiloader region free hacks), and attempts to brick region changed Korean Wii's at every startup.

Now onto IOS's. Pimp My Wii patches every single IOS (although you can say "no"), which isn't a good thing. Now a patched IOS here and there isn't a big deal, and I recommend having your System Menu IOS patched, but don't go messing with every IOS you've got. With AHB access, you can patch a vanilla IOS on the fly if you need to, so there aren't any permanent changes.

As far as people bricking, a google search of '"Pimp My Wii" brick' returns about 19,400 results. Now obviously those aren't all cases of people bricking. I'm sure at least half of them are topics where people call it "Brick My Wii" and such, but you'll still find plenty of legitimate bricks caused by the software.


I think that answers all your questions. If I missed something, or if I wasn't clear, just post your question below.

That's why I recommend people to learn instead of using automation.
That's why I would prefer people to teach and explain instead of telling other users to "just use modmii" or "just use PimpMyWii" or "just use xxxxx"
Explain things, redirect users to guide where they first learn how their console is working internally, and they will understand why they are doing things, they will better report problems and get better helps.

For example, take the time to write a little paragraph if no guide exists yet, or redirect to an existing post from someone else. I quickly explained what IOS are here, no need to put a lot of details, it helped the user, and probably many other visitors.


If you don't have time to help, don't try to be the first one to answer "just use ... common tools name" as if it was common knowledge, or like you are bored of answering the same question over and over. Someone else can help better.

Sources:
http://gbatemp.net/threads/pimp-my-wii-yay-or-nay.352978/
http://gbatemp.net/threads/pimp-my-wii-yay-or-nay.352978/#post-4745298
http://gbatemp.net/threads/pimp-my-wii-yay-or-nay.352978/#post-4745307
http://gbatemp.net/threads/pimp-my-wii-yay-or-nay.352978/#post-4745653
http://gbatemp.net/threads/pimp-my-wii-yay-or-nay.352978/#post-4745744
http://gbatemp.net/threads/pimp-my-wii-yay-or-nay.352978/#post-4748107
http://gbatemp.net/threads/pimp-my-wii-yay-or-nay.352978/page-2#post-4749308
http://gbatemp.net/threads/pimp-my-wii-yay-or-nay.352978/page-3#post-4751053

This entire thread I referenced happen AFTER all but the last of the 3.0x versions of PMW came out.

 

[TeamScriptKiddies]

just some of the "recent" quotes










Sources:
http://gbatemp.net/threads/pimp-my-wii-yay-or-nay.352978/
http://gbatemp.net/threads/pimp-my-wii-yay-or-nay.352978/#post-4745298
http://gbatemp.net/threads/pimp-my-wii-yay-or-nay.352978/#post-4745307
http://gbatemp.net/threads/pimp-my-wii-yay-or-nay.352978/#post-4745653
http://gbatemp.net/threads/pimp-my-wii-yay-or-nay.352978/#post-4745744
http://gbatemp.net/threads/pimp-my-wii-yay-or-nay.352978/#post-4748107
http://gbatemp.net/threads/pimp-my-wii-yay-or-nay.352978/page-2#post-4749308
http://gbatemp.net/threads/pimp-my-wii-yay-or-nay.352978/page-3#post-4751053

This entire thread I referenced happen AFTER the latest and LAST version of PMW came out.

All we're suggesting he does is use the testing function of PimpMyWii which is equivalent to running a Syscheck. The only difference here, is he can choose a different (hopefully unaffected) IOS to run the tool with. NOTHING is being written to NAND during the process. Everything is running in RAM. No programming/flashed involved whatsoever.

If someone were to use PimpMyWii for some of the other purposes it was designed for, sure its more dangerous then the traditional methods. But just using it for testing purpose and not tampering with any firmware or anything on NAND, nothing can be permanently damaged. If anything goes horribly wrong during the testing phase, all he has to do is force the console off and turn it back on again, voila, RAM is cleared out, issue resolved.

He is UNABLE to run a normal Syscheck so we're giving him an alternative. Hopefully this will allow him to get a report on what the issue is with his console so we can help him get it fixed. All we're suggesting he use PimpMyWii for is diagnostic purposes, nothing more. For someone who's pretty anal about others reading the thread thoroughly, you don't seem to be very good at it either....

 

[Bug_Checker_]

All we're suggesting he does is use the testing function of PimpMyWii which is equivalent to running a Syscheck. The only difference here, is he can choose a different (hopefully unaffected) IOS to run the tool with. NOTHING is being written to NAND during the process. Everything is running in RAM. No programming/flashed involved whatsoever.

If someone were to use PimpMyWii for some of the other purposes it was designed for, sure its more dangerous then the traditional methods. But just using it for testing purpose and not tampering with any firmware or anything on NAND, nothing can be permanently damaged. If anything goes horribly wrong during the testing phase, all he has to do is force the console off and turn it back on again, voila, RAM is cleared out, issue resolved.

He is UNABLE to run a normal Syscheck so we're giving him an alternative. Hopefully this will allow him to get a report on what the issue is with his console so we can help him get it fixed. All we're suggesting he use PimpMyWii for is diagnostic purposes, nothing more. For someone who's pretty anal about others reading the thread thoroughly, you don't seem to be very good at it either....

He has an alternative that doesn't requirement any risk to his WiiU/vWii. After reading NAND, it's all done on the pc. He will know that he has good IOS's or bad IOS's. But I guess I could have said "just try installing IOS 3 and STOP when you get to IOS200" and hope that that worked for him. But again, If I myself wouldn't do it why would I ask others to do it.
And the topic of being of being "rude": You must have misread something I wrote because I asked for a read/reread and IIRC pretty sure I said "please" but I'm never gonna say "pretty please". <author's note "no rudeness intended">

 

[Tomobobo]

So wait, what if you don't have a backup of your nand and you run into this problem? Are you screwed?

 

[Deleted member 342493]

So wait, what if you don't have a backup of your nand and you run into this problem? Are you screwed?

That's what we are trying to fix, but in the case you have NAND backupd you can't restore it yet, but it's strange the Wii U won't update anymore because you intall the cIOS, I have intalled since more than 1 year and I can still updating.

 

[TeamScriptKiddies]

That's what we are trying to fix, but in the case you have NAND backupd you can't restore it yet, but it's strange the Wii U won't update anymore because you intall the cIOS, I have intalled since more than 1 year and I can still updating.

The reason he can't update has nothing to do with having CIOS's on there. If you have the proper CIOS's installed for the vWii your Wii U will update no problem. We aren't 100% sure what his issue is just yet, that's what we're trying to figure out.

 

[JoostinOnline]

Until I fix the issue about TMD size (it's not so much a bug as more laziness from the original version of SysCheck), I'll make a version that skips vIOS36 and post it here. I'll try to make a proper fix in the next version.

 

[TeamScriptKiddies]

He has an alternative that doesn't requirement any risk to his WiiU/vWii. After reading NAND, it's all done on the pc. He will know that he has good IOS's or bad IOS's. But I guess I could have said "just try installing IOS 3 and STOP when you get to IOS200" and hope that that worked for him. But again, If I myself wouldn't do it why would I ask others to do it.
And the topic of being of being "rude": You must have misread something I wrote because I asked for a read/reread and IIRC pretty sure I said "please" but I'm never gonna say "pretty please". <author's note "no rudeness intended">

We never suggested that he install any IOS's. We simply told him to try the one's he already has until he finds a winner (assuming he finds one that works). At no point did we ever imply he should write to NAND at all.

 

[JoostinOnline]

We never suggested that he install any IOS's. We simply told him to try the one's he already has until he finds a winner (assuming he finds one that works). At no point did we ever imply he should write to NAND at all.

The points about Brick My Wii still stand.

Anyway, the original SysCheck just gives up if something unexpected happens, instead of working around it. There is a lot of stuff to address and that's actually been rather low on the list since it happens so rarely.

I recently modified/cleaned up Title Lister to log the titles and exit properly. I'll post that if a custom version of SysCheck doesn't work. That way we'll at least know what is installed on his vWii.

 

[JoostinOnline]

This should skip vIOS36.
http://expirebox.com/download/9b5bf437e255430d82aedf51dfae7b23.html

 

[Bug_Checker_]

Ok I have something that should work on a windows pc(tested on x64) and does not need a command prompt.
It will NOT make/package a WAD but it should show what was changed in NAND.
It's giantpune's NAND Extract(NAND READ ONLY pc program) r105 (windows exe binary compiled by wiisixtyfour)
There is a Mac OS X version(untested) see below

Make a working copy of your original NAND
Make a working copy of your current NAND
Download nandExtract.zip and giantpune-tools-dlls.zip
Extract both zip archives and copy ALL 6 files from giantpune-tools-dlls.zip into same directory as nandExtract.exe

Open nandExtract.exe(double click is fine)

Open Nand (no drag and drop available)
under "File" -> "Open Nand" (shortcut keys "Ctrl + O")
Click on "+" sign next to "ticket"
Hover over "00000001" (Essential system titles)
Right mouse click and select "Extract" and Choose folder destination(in the box scroll down to select "Computer" (or click to the left of username to close and "Computer" will move up screen) then "Local Drive c:"(example "c:" could be any drive) then select "Make New Folder" in root drive
name it "original_nand_extract".
Also "Extract":
"00010002" (System channels)
"00010008" ("Hidden" channels)

You should not need(but there's no harm/hell you could do the entire NAND if you wanted by hovering over "/"(at top of window) and right mouse clicking) to "Extract" some or all of the following(this list may not be complete)
00010000 (Disc-based games)
00010001 (Downloaded channels)
00010004 (Disc-based gamesGame channels and games that use them)
00010005 (Downloaded Game Content)

Repeat steps for "title" by Clicking on "+" sign next to "title" etc.
Repeat steps for "meta" by Clicking on "+" sign next to "meta" etc.
Finally, Hover over "shared1" and "Extract"

Then follow same steps for current NAND but change name of "Make New Folder" from "original_nand_extract" to "current_nand_extract".

Now get ExactFile (1.0.0.15 BETA)
Select "Create Digest"
make sure boxes are checked next to "Include subfolders" and "Output to File:"
Then next to "Method and Format:"select either "MD5" or "sha1"(or "sha1sum")(sha1 is recommended)
IF you use sha1, the content files will match their tmd sha1's nicely (so it is recommended)
drag and drop ,first, the "original_nand_extract" folder onto the first/top text box (just to the left of a box with"...") press "Go" then close popup window(don't worry file will be saved in "original_nand_extract" folder)
Then do the same for "current_nand_extract" folder

Please post results of both files or upload files somewhere.

This should work for both BootMii NAND/wii backups as well as DumpMiiNand/vWii backups. (but I've only tested it with BootMii nand/wii backup)

Sources:
http://forum.wiibrew.org/read.php?17,66182,66183 (Windows version)
http://forum.wiibrew.org/read.php?17,67713 (Mac OS Xversion)-(untested by me)

http://www.mediafire.com/?ow9bg9wsto5ak1w (giantpune-tools-dlls.zip)
http://wiisixtyfour.webs.com/files/nandExtract.zip (r105 nandExtract.zip windows)

http://www.exactfile.com/downloads/
http://www.exactfile.com/files/ExactFile-Setup.exe