Hacking Nintendont

  • Thread starter Thread starter sabykos
  • Start date Start date
  • Views Views 10,168,302
  • Replies Replies 42,894
  • Likes Likes 194
what version of nintendont are you using? because the latest nintendont does not corrup any save and please say the number and dont say latest, right now the latest is 327.
Chill, i'm not one to use that 'latest' term, not without using the logical number version. 327.

In a couple of hours i will test again the native save function with each of my original memory cards, i will even use a clone MC i have laying around
 
found pikmin 2 issue and the Fix, pikmin2 is just very very unlucky game, its credit scene happen to have the exact value for a known timer in between but it isnt a timer so we need someone that knows how to do an exception.

Patch:[Timer Clock float 1/ms] applied (0x00DFC604)

I'm surprised this didnt happen much earlier. That is the price of having a very agressive timer patcher needed, I think it would be a good idea to see which games really need it and then create a exception list on where we really need to apply it so we prevent problems like that. Simply what happens is that video material can be any value out there, no limits. Now this exact video segment loaded there just happens to also look like the timer value as pedro already said, we have no way of knowing that beforehand.
 
Chill, i'm not one to use that 'latest' term, not without using the logical number version. 327.

In a couple of hours i will test again the native save function with each of my original memory cards, i will even use a clone MC i have laying around
well tbh i was refering to mcemu not real memory cards since i never used those.
 
so there we go:
-restricted the aggressive timer patching to the hobbit, fixes various side problems such as pikmin 2 crashing and the gc bios slowing down
-changed the exi interrupt times a bit to further prevent lagging in the gc bios and in triforce games
 
well tbh i was refering to mcemu not real memory cards since i never used those.
Well, i said it on my previous post "Only thing i think could improve, or stabilize, is real memory card support in-game, which is not always working properly". Final Fantasy CC is the one i detected, hopefully it happens in scarce titles.
Nintendon't is seriously rocking the house, BTW.
 
Well, i said it on my previous post "Only thing i think could improve, or stabilize, is real memory card support in-game, which is not always working properly". Final Fantasy CC is the one i detected, hopefully it happens in scarce titles.
Nintendon't is seriously rocking the house, BTW.
we dont mess with real memory cards, we let the system do their thing, we have no code for real memcards except the code unlock for them.
 
so there we go:
-restricted the aggressive timer patching to the hobbit, fixes various side problems such as pikmin 2 crashing and the gc bios slowing down
-changed the exi interrupt times a bit to further prevent lagging in the gc bios and in triforce games

I bet that's what was causing the Turok demo loop to freeze, too. Will check it later today.
 
  • Like
Reactions: VinsCool
So I thought, after all these praises I have to test nintendont as well.
Made a FAT32 drive, cleanripped my NGC disks and "got" also the triforce titles. Started the newest build from my HBC, chose a game and the message "Loading patched kernel -3" appeared and my Wii restarted. Not able to get up with the home button.
It was discussed hundred pages ago, but no fix or other information has been posted. Is there anything I could try or is my Wii just not supported?
Google had 4 hits and all of them send me to this thread...
 
So I thought, after all these praises I have to test nintendont as well.
Made a FAT32 drive, cleanripped my NGC disks and "got" also the triforce titles. Started the newest build from my HBC, chose a game and the message "Loading patched kernel -3" appeared and my Wii restarted. Not able to get up with the home button.
It was discussed hundred pages ago, but no fix or other information has been posted. Is there anything I could try or is my Wii just not supported?
Google had 4 hits and all of them send me to this thread...

What games? Did you check the hashes to make sure they're valid? What version of Nintendont? Wii or Wii-U? It sounds like the loader cannot access the NAND. We can't see your console from here. :)
 
As stated before, I am using my Wii, with the newest version of Nintendont (v3.328).
I also checked for a wrong ISO58, but v6176 is installed.

I used cleanrip with my games, so I think they are fine, but since I can't seem to go to redump
LA4NGM0.png

I couldn't check them. But since the "working" triforce games also crash with the same message, I thought, that the games are not the problem.
Is there anything more I could provide for helping you/me with my problem?
 
As stated before, I am using my Wii, with the newest version of Nintendont (v3.328).
I also checked for a wrong ISO58, but v6176 is installed.

I used cleanrip with my games, so I think they are fine, but since I can't seem to go to redump
LA4NGM0.png

I couldn't check them. But since the "working" triforce games also crash with the same message, I thought, that the games are not the problem.
Is there anything more I could provide for helping you/me with my problem?
are you using nintendont directly? you dont have any other usb devices connected to the console besides the hdd with the games?
 
As stated before, I am using my Wii, with the newest version of Nintendont (v3.328).
I also checked for a wrong ISO58, but v6176 is installed.

I used cleanrip with my games, so I think they are fine, but since I can't seem to go to redump
LA4NGM0.png

I couldn't check them. But since the "working" triforce games also crash with the same message, I thought, that the games are not the problem.
Is there anything more I could provide for helping you/me with my problem?

Check the meta.xml in /apps/Nintendont/ and make sure it's not missing the <ahb_access/> tag.

It should look like this one (except the version number.)
 
are you using nintendont directly? you dont have any other usb devices connected to the console besides the hdd with the games?

Nope, only the HDD. Since I just wanted to test it, I thought, I start with it directly before using loaders and creating one additional error source.
Check the meta.xml in /apps/Nintendont/ and make sure it's not missing the <ahb_access/> tag.


It should look like this one (except the version number.)
Yay, looking like it. <ahb_access/> before the last </app>. Checked it with WiiXplorer.
 
Nope, only the HDD. Since I just wanted to test it, I thought, I start with it directly before using loaders and creating one additional error source.

Yay, looking like it. <ahb_access/> before the last </app>. Checked it with WiiXplorer.
is your hdd one of those with encription? people say for instance the latest seageat hdds if im not mistaken use an encription wich nintendont doesnt like.
 
My mistake, I've never seen retail cables, only ever hardmods for direct lines
Edit: I guess I was thinking about older consoles. Again, my mistake. I'm going to take some needed time off of the 'temp :p

The NES is the only Nintendo console to not use S-video (well, also the SNES model 2 and Wii Mini, for some reason).
 
  • Like
Reactions: TotalInsanity4

Site & Scene News

Popular threads in this forum