Hacking [Semi-working] NFS2ISO2NFS - convert nfs to iso and back

[VinsCool]

I don't think you could load homebrew with sploits. It seems that there is some sort of lock down... Hang on let me see if I can load anything with smashstack (besides the hbc installer because that doesn't work)

You can load homebrews with exploitable games. Ploggy tested it and it worked (for some, as some homebrews didn't work properly)

 

[ploggy]

What do you mean with this?

I mean I'm having the same issue I had before Truncha was patched back in..
the way I do it is to load Yugioh exploit with Nintendont boot.dol in the root, nintendont boots to the splash screen but it has an error saying it need the Metal.xml but if I put the Meta.xml in teh root with the Boot.dol I just get a black screen?

 

[VinsCool]

I mean I'm having the same issue I had before Truncha was patched back in..
the way I do it is to load Yugioh exploit with Nintendont boot.dol in the root, nintendont boots to the splash screen but it has an error saying it need the Metal.xml but if I put the Meta.xml in teh root with the Boot.dol I just get a black screen?

Have you tried to load a .dol forwarder to any homebrew in their respective apps/homebrew/ folders? Maybe that would do the trick.

 

[ploggy]

What about syscheck?
What does it say now?
And does running the HBC through a save exploit do the same thing?

Running the HBC says this:

I'll try running syscheck again..

--------------------- MERGED ---------------------------

Have you tried to load a .dol forwarder to any homebrew in their respective apps/homebrew/ folders? Maybe that would do the trick.

I'll try what forward do you suggest?

Edit: i'll post in the nintendont thread see if fix94 has some insight?

 

[VinsCool]

I'll try what forward do you suggest?

For example, the one being used in the nintendont forwarder channel. I guess that you only need to grab the .dol from the installable .wad and run it?
I'm only throwing ideas, but who knows

 

[Deleted User]

Running the HBC says this:

I'll try running syscheck again..

--------------------- MERGED ---------------------------


I'll try what forward do you suggest?

I think I know why that happened. I'd Imagine the fw.img sets read limits. So instead of reading everything in slccmpt. (aka vwii) it only reads stuff the game in question needs... but that wouldn't make sense... Because that would mean the games we are injecting WOULD not work... unless the fw.img some how does a check for the ios of the nifs files?! I don't know.. But I can only imagine it cannot work because of how the virtulization is being set.

 

[ploggy]

@ShadowOne333 syscheck says the exact same as before..

 

[Deleted User]

@ShadowOne333 syscheck says the exact same as before..

yep I'm getting the same issue. Using smashstack with a non custom fw.img. I'll test a custom one soon.

 

[ploggy]

Is there a Elf/dol version of the wii Homebrew Channel?

 

[ShadowOne333]

@ShadowOne333 syscheck says the exact same as before..

I wonder, has anyone tried to inject another boot.dol into an ISO and tried loading that?
Now that we have sigpatches perhaps we can try that.
Using the sigpatch fw.img with an injected homebrew app as the boot.dol for the game.
Don't know how feasible this is, if at all, I might just be talking shit honestly but at least giving ideas xD

 

[Deleted User]

I wonder, has anyone tried to inject another boot.dol into an ISO and tried loading that?
Now that we have sigpatches perhaps we can try that.
Using the sigpatch fw.img with an injected homebrew app as the boot.dol for the game.
Don't know how feasible this is, if at all, I might just be talking shit honestly but at least giving ideas xD

in theory.... that could work. stripping down everything within the iso and injecting it could work.... maybe. However I'm the same so i could be wrong.

 

[ploggy]

I wonder, has anyone tried to inject another boot.dol into an ISO and tried loading that?
Now that we have sigpatches perhaps we can try that.
Using the sigpatch fw.img with an injected homebrew app as the boot.dol for the game.
Don't know how feasible this is, if at all, I might just be talking shit honestly but at least giving ideas xD

I'll try it, may as well lol

 

[Deleted User]

I wonder, has anyone tried to inject another boot.dol into an ISO and tried loading that?
Now that we have sigpatches perhaps we can try that.
Using the sigpatch fw.img with an injected homebrew app as the boot.dol for the game.
Don't know how feasible this is, if at all, I might just be talking shit honestly but at least giving ideas xD

found the problem!!!
HackMii v1.2 installer starting up
PVR = 00087200
running under IOS 58 rev 0x1920
63 titles are installed
Found IOS 0: revision: 0x0*
Found IOS 251: revision: 0x5212*
Found IOS 250: revision: 0x5212*
Found IOS 249: revision: 0x5212*
Found IOS 236: revision: 0xffff*
Found IOS 80: revision: 0x1c20.
Found IOS 62: revision: 0x1b1e.
Found IOS 59: revision: 0x2421.
Found IOS 58: revision: 0x1920.
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: 0x508.
Found IOS 12: revision: 0x30e.
Found IOS 9: revision: 0x50a.
Found IOS 2: revision: 0x261.
launching IOS 58 for the installer...

failed to reload IOS for the installer (-1698898192)
starting preparations

preparations done!

This installer can [31;1mNOT[37;1m continue!

There is no usable or vulnerable IOS installed on this Wii.
Please note that we will not use fakesigned IOSes due to
security reasons. Only [31;1munpatched[37;1m versions will be used!

Read the FAQ at: [36;1mhttp://hbc.hackmii.com/faq/[37;1m
Look for an updated version at: [36;1mhttp://bootmii.org[37;1m

If this is already the latest version... well, suck it.

so either the reload is failing. or we have some werid crap going on. Like, why is there a ios2?

(im going to load brawl again but instead of injected for real and see what shows up)

 

[VinsCool]

@ploggy I created a nintendont forwader. Can you test it from the exploit game?

https://www.dropbox.com/s/ajj9qvy4cc0wwhw/boot.dol?dl=0

 

[Feffe]

Is there a Elf/dol version of the wii Homebrew Channel?

You might try Loadmii
http://wiibrew.org/wiki/Loadmii

 

[ploggy]

@ploggy I created a nintendont forwader. Can you test it from the exploit game?

https://www.dropbox.com/s/ajj9qvy4cc0wwhw/boot.dol?dl=0

Same error @VinsCool

You might try Loadmii
http://wiibrew.org/wiki/Loadmii

@Feffe just locks up after launching the dol

Ok I'll try them now.

 

[Feffe]

found the problem!!!
HackMii v1.2 installer starting up
PVR = 00087200
running under IOS 58 rev 0x1920
63 titles are installed
Found IOS 0: revision: 0x0*
Found IOS 251: revision: 0x5212*
Found IOS 250: revision: 0x5212*
Found IOS 249: revision: 0x5212*
Found IOS 236: revision: 0xffff*
Found IOS 80: revision: 0x1c20.
Found IOS 62: revision: 0x1b1e.
Found IOS 59: revision: 0x2421.
Found IOS 58: revision: 0x1920.
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: 0x508.
Found IOS 12: revision: 0x30e.
Found IOS 9: revision: 0x50a.
Found IOS 2: revision: 0x261.
launching IOS 58 for the installer...

failed to reload IOS for the installer (-1698898192)
starting preparations

preparations done!

This installer can [31;1mNOT[37;1m continue!

There is no usable or vulnerable IOS installed on this Wii.
Please note that we will not use fakesigned IOSes due to
security reasons. Only [31;1munpatched[37;1m versions will be used!

Read the FAQ at: [36;1mhttp://hbc.hackmii.com/faq/[37;1m
Look for an updated version at: [36;1mhttp://bootmii.org[37;1m

If this is already the latest version... well, suck it.

so either the reload is failing. or we have some werid crap going on. Like, why is there a ios2?

(im going to load brawl again but instead of injected for real and see what shows up)

Can you run Syscheck? There's no IOS 255 in your log, but we know from @ploggy Syscheck scan everything is working under IOS 255.
So either you and Poggy are using two different fw.img with two different main IOSes or somehow the HBC installer doesn't recognize IOS 255. Which might also be the problem with Nintendont, and in this case we should recompile Nintendont to use IOS 255.
Just some thoughts...

 

[Deleted User]

Can you run Syscheck? There's no IOS 255 in your log, but we know from @ploggy Syscheck scan everything is working under IOS 255.
So either you and Poggy are using two different fw.img with two different main IOSes or somehow the HBC installer doesn't recognize IOS 255. Which might also be the problem with Nintendont, and in this case we should recompile Nintendont to use IOS 255.
Just some thoughts...

no I was using bootmii's log Which told what is there. And I just did it again with normal vwii log. And its clear whats going on. the fw.img does not allow ios reloads. As everything was identical during the second test (except it sucessed. but the ioses where identical) (which Iused a physical disc of brawl instead of the inject) So this means that the fw.img is proably preventing ios reloads.

--------------------- MERGED ---------------------------

You might try Loadmii
http://wiibrew.org/wiki/Loadmii

plus loadmii doesn't have a compiled download which makes my life a little harder.

 

[Feffe]

no I was using bootmii's log Which told what is there. And I just did it again with normal vwii log. And its clear whats going on. the fw.img does not allow ios reloads. As everything was identical during the second test (except it sucessed. but the ioses where identical) (which Iused a physical disc of brawl instead of the inject) So this means that the fw.img is proably preventing ios reloads.

My point is, why there's no IOS 255 in your log? It was the main IOS in Ploggy's Syscheck log.

 

[Deleted User]

My point is, why there's no IOS 255 in your log? It was the main IOS in Ploggy's Syscheck log.

BECAUSE ITS NOT SYSCHECK. bootmii's log doesn't take into account of ios 255! jeeeze

--------------------- MERGED ---------------------------

My point is, why there's no IOS 255 in your log? It was the main IOS in Ploggy's Syscheck log.

plus how the heck I'm I supposed to load system check if its in a .dol. which smash stack only excepts .elfs