Hacking Another vWII semi brick thread :(

[brandonwh64]

First of all, can you still launch YAWWM on your bricked vwii?

yes I can.

 

[ScarletDreamz]

try to install any of the wads you got using YAWWM.

 

[brandonwh64]

try to install any of the wads you got using YAWWM.

it fails with -1017

 

[brandonwh64]

try to install any of the wads you got using YAWWM.

Here is a picture

 

[ScarletDreamz]

why is the wad called IOS36, is that from a CLEAN DUMP of an Unmodded vWii? meaning that those are indeed vWii Wads?

 

[brandonwh64]

why is the wad called IOS36, is that from a CLEAN DUMP of an Unmodded vWii? meaning that those are indeed vWii Wads?

it is the vIOS from the clean dump of the other wiiu I softmodded from him. When it starts what IOS should I choose to load the other IOSes with?

 

[endoverend]

it is the vIOS from the clean dump of the other wiiu I softmodded from him. When it starts what IOS should I choose to load the other IOSes with?

I don't think you have a single IOS which has permissions to install others. You'll need to use the ios236 installer v7 with a clean vIOS 36 wad.

 

[kirbysepic]

I have Got a scimilar Problem. But I have only the yu-gi-oh game to use for the exploit. Do I need Lego Batman to Run the hbc? My Problem is in the other thread
https://gbatemp.net/threads/wii-u-may-be-fullbrick-please-help.421496/#post-6225191

 

[brandonwh64]

I have Got a scimilar Problem. But I have only the yu-gi-oh game to use for the exploit. Do I need Lego Batman to Run the hbc? My Problem is in the other thread
https://gbatemp.net/threads/wii-u-may-be-fullbrick-please-help.421496/#post-6225191

I just read your thread and from what I seen on your Syscheck, you have a viable IOS that you can use to flash IOS's. in my case it is not and I believe my system is just hosed until someone can hack it through wiiu menus or has a was to emulate a nand access IOS to reflash.

 

[ScarletDreamz]

I just read your thread and from what I seen on your Syscheck, you have a viable IOS that you can use to flash IOS's. in my case it is not and I believe my system is just hosed until someone can hack it through wiiu menus or has a was to emulate a nand access IOS to reflash.

Mind posting again another Syscheck, please?

 

[Bug_Checker_]

Spoiler

BTW here is the syscheck

SysCheck HDE v2.4.0 HacksDen Edition by JoostinOnline, Double_A, R2-D2199, and Nano
...runs on IOS36 (rev 3864).

Region: NTSC-U
System Menu 4.3U (v609)

Could not detect the drive date!
Homebrew Channel is not installed

Hollywood v0x0
Console ID: 605512406
Console Type: Wii
Shop Channel Country: United States (49)
Boot2 v0
Found 43 titles.
Found 30 IOS on this console. 0 of them are stubs.

IOS9 (rev 1290): No Patches
IOS12 (rev 526): No Patches
IOS13 (rev 1032): No Patches
IOS14 (rev 1288): No Patches
IOS15 (rev 1288): No Patches
IOS17 (rev 1288): No Patches
IOS21 (rev 1295): No Patches
IOS22 (rev 1550): No Patches
IOS28 (rev 2063): No Patches
IOS31 (rev 3864): No Patches
IOS33 (rev 3864): No Patches
IOS34 (rev 3864): No Patches
IOS35 (rev 3864): No Patches
IOS36 (rev 3864): No Patches
IOS37 (rev 5919): No Patches
IOS38 (rev 4380): No Patches
IOS41 (rev 3863): No Patches
IOS43 (rev 3863): No Patches
IOS45 (rev 3863): No Patches
IOS46 (rev 3863): No Patches
IOS48 (rev 4380): No Patches
IOS53 (rev 5919): No Patches
IOS55 (rev 5919): No Patches
IOS56 (rev 5918): No Patches
IOS57 (rev 6175): No Patches
IOS59 (rev 9249): No Patches
IOS62 (rev 6942): No Patches
IOS80 (rev 7200): No Patches
BC v6
MIOS v10
vIOS512 (rev 7): No Patches
vIOS513 (rev 1): No Patches
Report generated on 03/29/2016.

Spoiler

Ok just wanted to update you guys on this issue I have. I took some time off working on it to keep reading and start doing more research. I went back and ran syscheck on every single IOS (besides IOS250) one by one (yea it took a while LOL) and I found out that the only other IOS besides 250 that was modified was IOS58. I started doing research on IOS58 and after careful planning I decided to delete it. Once I deleted it, I rebooted and tried the hackmii installer again which froze on scam screen again . I was about to give up until I took a look at my SD card to see that it actually made progress in the installer and made a LOG file. So this is what it does.

HackMii v1.2 installer starting up
PVR = 00087200
running under IOS 59 rev 0x2421
44 titles are installed
Found IOS 250: revision: 0x5212*
Found IOS 9: revision: 0x50a.
Found IOS 62: revision: 0x1b1e.
Found IOS 59: revision: 0x2421.
Found IOS 57: revision: 0x181f.
Found IOS 56: revision: 0x171e.
Found IOS 55: revision: 0x171f.
Found IOS 53: revision: 0x171f.
Found IOS 48: revision: 0x111c.
Found IOS 46: revision: 0xf17.
Found IOS 45: revision: 0xf17.
Found IOS 43: revision: 0xf17.
Found IOS 41: revision: 0xf17.
Found IOS 38: revision: 0x111c.
Found IOS 37: revision: 0x171f.
Found IOS 36: revision: 0xf18.
Found IOS 35: revision: 0xf18.
Found IOS 34: revision: 0xf18.
Found IOS 33: revision: 0xf18.
Found IOS 31: revision: 0xf18.
Found IOS 28: revision: 0x80f.
Found IOS 22: revision: 0x60e.
Found IOS 21: revision: 0x50f.
Found IOS 17: revision: 0x508.
Found IOS 15: revision: 0x508.
Found IOS 14: revision: 0x508.
Found IOS 13: revision: 0x408.
Found IOS 12: revision: 0x20e.
Found IOS 2: revision: 0x261.
Found IOS 80: revision: 0x1c20.
launching IOS 38 for the installer...

IOS launched...

IOS versions: Installer: 38, HBC: 0
starting preparations

You could have just tried to skip certain IOS versions with SysCheck without deleting an official vIOS(59).
@Cyan head must have exploded when he read that.
But congratulations on the huge balls you have(and not fully bricking your vWii).
But deleting an official vIOS is a HUGE NO-NO.
(Please, anyone else reading this, understand just how risky this is!)

I am assuming you have a Wii U that is at version 5.2.0 or greater(5.5.1 as of April 19th 2016) based on the versions of your vIOS.

There are some bugs/errors in SysCheck HDE v2.4.0 HacksDen Edition by JoostinOnline, Double_A, R2-D2199, and Nano

@JoostinOnline might be able to comment on that.

Errors seem to include:
Could not detect the drive date!
Hollywood v0x0
Console Type: Wii
and listing vIOS as IOS

But it is not just isolated to just your log. It has been seen with @shaneod this log
https://gbatemp.net/threads/wii-u-may-be-fullbrick-please-help.421496/page-2#post-6226674

Spoiler

SysCheck HDE v2.4.0HacksDenEdition of JoostinOnline,Double_A, R2-D2199,andNano...Runs on IOS36 (rev 3864).Region: PAL
SystemMenu4.3E(V514)

The drive date could not be recognizedHomebrewChannel1.1.2 uses IOS58Hollywood v0x0Console ID:607933355ConsoleType:WiiShopChannelCountry:Germany(78)
boot2 v0

There46 titles have been found.There33 IOS were found, of which 0nofunction(stub).
IOS9 (rev 1290):No patch
IOS12 (rev 782):No patch
IOS13 (rev 1288):No patch
IOS14 (rev 1288):No patch
IOS15 (rev 1288):No patch
IOS17 (rev 1288):No patch
IOS21 (rev 1295):No patch
IOS22 (rev 1550):No patch
IOS28 (rev 2063):No patch
IOS31 (rev 3864):No patch
IOS33 (rev 3864):No patch
IOS34 (rev 3864):No patch
IOS35 (rev 3864):No patch
IOS36 (rev 3864):No patch
IOS37 (rev 5919):No patch
IOS38 (rev 4380):No patch
IOS41 (rev 3863):No patch
IOS43 (rev 3863):No patch
IOS45 (rev 3863):No patch
IOS46 (rev 3863):No patch
IOS48 (rev 4380):No patch
IOS53 (rev 5919):No patch
IOS55 (rev 5919):No patch
IOS56 (rev 5918):No patch
IOS57 (rev 6175):No patch
IOS58 (rev 6432): USB 2.0
IOS59 (rev 7201):No patch
IOS62 (rev 6430):No patch
IOS80 (rev 7200):No patch
IOS236 (rev 65535):TruchaBug, ES Identify, NAND access
IOS249 [56](rev 21010, info: d2x-v10beta52-vWii): NAND access, USB 2.0
IOS250 [57](rev 21010, info: d2x-v10beta52-vWii): NAND access, USB 2.0
IOS251 [58](rev 21010, info: d2x-v10beta52-vWii): NAND access, USB 2.0

Report was generated on 02/01/2015.

So I am less concern about those issues.

Although it appears to be, the issue that causes problems is common when running SysCheck with IOS36 (rev 3864) but seems not to be in effect when running vIOS58 (rev 6432). (So I guess it would be nice to test theory by being able to choose which vIOS SysCheck will run with.)
It has been around since at least SysCheck v2.2.1
https://gbatemp.net/threads/semi-bricked-vwii.368993/page-3#post-5056857
make that at least SysCheck v2.2.0
https://gbatemp.net/threads/semi-bricked-vwii.368993/page-6#post-5069899
In fact, I can not find ever there was a valid use of:
"Runs on the vIOS36 (rev 3864)" or
"Runs on vIOS36 (rev 3864)"

(Btw, shaneod That log is either running a Wii U with firmware 2.0.x to 3.1.x or downgraded his vWii IOS versions(perhaps for IOSU exploit))
(It turns out it was an accidentally downgraded vWii IOS by kirbysepic which was fixed.)

Now back to your issues:
if you can still write to your sd card:
you need to backup both your Wii U NAND and your vWii NAND(and obviously your keys).
put them away in multiple safe locations (ie dvd rom and cloud).
Then extract everyone of your vWii IOS versions into a folder like c:\brandonwh64_vIOS.
Then compare those vIOS with your buddy's vWii in a folder like c:\mybuddies_vIOS.
Then compare those files. If you are on windows open a command prompt and type

fc /b c:\brandonwh64_vIOS\*.* c:\mybuddies_vIOS\*.* > c:\brandonwh64_vIOS\results_of_compare.txt

BUT before you do that you NEED to move/remove IOS12 and IOS13 from YOUR directory(brandonwh64_vIOS).See below.

I am going to assume most will check out fine.

But, here are the things that stand out from your SysCheck log:

IOS12 (rev 526): This is a Wii Version IOS
IOS13 (rev 1032): This is a Wii Version IOS
vIOS58 This is of course missing (because you deleted it)
BC v6 This Should not be here
MIOS v10 This Should not be here

No cIOS listed This is most likely because you deleted all other cIOS and then skipped checking cIOS 250 with SysCheck

 

[shaneod]

@Bug_Checker_ that wasn't my syslog. I was fixing the formatting of the op's syslog.

 

[Bug_Checker_]

okay thanks for info. Made edits to post above to reflect new info.

@brandonwh64
If HASHLOG exists on your sd card(after running SysCheck) in the root directory(I believe),Please post.
It should be "sd:/IOSsyscheck.log"

 

[brandonwh64]

@Bug_Checker_
I re ran the syscheck and it does create a IOSsyscheck.log file but it is blank.

Here is a most recent syscheck

SysCheck HDE v2.4.0 HacksDen Edition by JoostinOnline, Double_A, R2-D2199, and Nano
...runs on IOS36 (rev 3864).

Region: NTSC-U
System Menu 4.3U (v609)

Could not detect the drive date!
Homebrew Channel is not installed

Hollywood v0x0
Console ID: 605512406
Console Type: Wii
Shop Channel Country: United States (49)
Boot2 v0
Found 43 titles.
Found 30 IOS on this console. 0 of them are stubs.

IOS9 (rev 1290): No Patches
IOS12 (rev 526): No Patches
IOS13 (rev 1032): No Patches
IOS14 (rev 1288): No Patches
IOS15 (rev 1288): No Patches
IOS17 (rev 1288): No Patches
IOS21 (rev 1295): No Patches
IOS22 (rev 1550): No Patches
IOS28 (rev 2063): No Patches
IOS31 (rev 3864): No Patches
IOS33 (rev 3864): No Patches
IOS34 (rev 3864): No Patches
IOS35 (rev 3864): No Patches
IOS36 (rev 3864): No Patches
IOS37 (rev 5919): No Patches
IOS38 (rev 4380): No Patches
IOS41 (rev 3863): No Patches
IOS43 (rev 3863): No Patches
IOS45 (rev 3863): No Patches
IOS46 (rev 3863): No Patches
IOS48 (rev 4380): No Patches
IOS53 (rev 5919): No Patches
IOS55 (rev 5919): No Patches
IOS56 (rev 5918): No Patches
IOS57 (rev 6175): No Patches
IOS59 (rev 9249): No Patches
IOS62 (rev 6942): No Patches
IOS80 (rev 7200): No Patches
BC v6
MIOS v10
vIOS512 (rev 7): No Patches
vIOS513 (rev 1): No Patches
Report generated on 04/21/2016.

 

[JoostinOnline]

There are some bugs/errors in SysCheck HDE v2.4.0 HacksDen Edition by JoostinOnline, Double_A, R2-D2199, and Nano

@JoostinOnline might be able to comment on that.

Errors seem to include:
Could not detect the drive date!
Hollywood v0x0
Console Type: Wii
and listing vIOS as IOS

The method for detecting vIOS and console type requires AHB access. It's something I'm working on in my free time (what little there is). The only reason vIOS512 and vIOS513 are correctly detected is because I use another method that won't work on a regular vIOS. Don't hold your breath for an update though.