Hacking Nintendont

  • Thread starter Thread starter sabykos
  • Start date Start date
  • Views Views 10,171,976
  • Replies Replies 42,894
  • Likes Likes 194
I'm surprised nobody noticed that much earlier, thats completely normal, its just the firmware number I choose after reloading into the kernel, I use it to see when the kernel says hello to us for the first time, as a security mechanism.


I did notice it, but since I am t00 l33t I didnt say anything :p
 
the wiiu pro controller lasts like 80 hours or 30+ hours if your using it heavily, its the longest controller batery i ever had no even the ps3 controllers last as long, i love the wiiurpo everything fells solid and confy.
I don't have a Wiiu pro controller (yet) but I was talking about the regular Wiiu controller, the PS3 controller actually lasts quite long.

3DS can live much longer than 2-3 hours though. Maybe your battery is dying?

Yeah, the Gamepad battery is poo. It only lasts 5 hours max if all the settings are at their lowest. Those are the disadvantages of having a screen in a controller. I'd recommend picking this baby up: https://store.nintendo.com/ng3/browse/productDetailColorSizePicker.jsp?productId=prod150204
Well I did buy it second hand but I don't think it's dying, it depends on the volume, screen light, 3D effect, and wifi, the more you turn off the longer it lasts, and yes it might last longer than 3 hours but I like to use most of these effects except for the 3D effect, it eats up the battery and hurts your eyes and most games don't look nice too (Kirby looks amazing in 3D though).
However my Wiiu gamepad doesn't even last 10 minutes, I also bought it second hand (I'm poor) but I think the battery in my controller is dying.
 
A little project I'm workin on. It's part of a larger project aimed to be a User Manual for Wiiflow users, explaining everything that can be done from Wiiflow. This includes Nintendont. It will use a flip book style coverflow Currently finishing up the gamecube loaders section. Anyone who would like to offer their assistance is welcome to.


I think you've got a wrong picture of Logitech RumblePad 2 controller. I provided the config file for this a couple of weeks ago.
Also you forgot to mention that Wiimote+Nunchuck also supports rumble.
 
I have try nun feature with 007 . Ir works but is very slow. I have try with wiimote max sensibility but still slow... with mkdd work good as firts controller and real gc pad as second controller.
Nunchack can only works for player 1?
 
I have try nun feature with 007 . Ir works but is very slow. I have try with wiimote max sensibility but still slow... with mkdd work good as firts controller and real gc pad as second controller.
Nunchack can only works for player 1?
You need to give details.
nintendont version?
which 007 game?
wiimote IR sensitivity needs to be set correctly in the wiis setup screens. If you see any number of dots other than 2 it wont work correctly.
What do you mean by slow?
Wiimote + nunchuck can be used for any players that dont already have another controller assigned. You can use it for all 4 player if you have no gamecube controllers pluged in and HID off.
 
I'm surprised nobody noticed that much earlier, thats completely normal, its just the firmware number I choose after reloading into the kernel, I use it to see when the kernel says hello to us for the first time, as a security mechanism.
I took a look at the problem and can assure that the kernel freeze at exactly this line

https://code.google.com/p/nintendon-t/source/browse/trunk/kernel/main.c#224

If you ask yourself how a noob like me figured that out. I changed the lines in kernel's main.c to

Code:
    BootStatus(9, s_size, s_cnt);
 
    DIRegister();
    BootStatus(9, 1, s_cnt);
    u32 *theDIStack = (u32*)malloca(DI_STACK_SIZE * sizeof(u32), 32); //yes, it seems like thats how it works
    BootStatus(9, 2, s_cnt);
    DI_Thread = thread_create(DIReadThread, NULL, theDIStack, DI_STACK_SIZE, 0x78, 1); //simply because its a stack
    BootStatus(9, 3, s_cnt);
    thread_continue(DI_Thread);
    BootStatus(9, 4, s_cnt);
 
    DIinit(true);
 
    BootStatus(10, s_size, s_cnt);
And since I got "Sector size: 4" on my TV I figured that it just stoped in the mentioned line.

The other user with this problem said that it first occured in r230. However this line was there before, but the lines around changed. I took a look at DIinit in Di.c, in my opinion there isn't much that could cause a freeze there. The file operations of FatFs (like f_open) should work well, otherwise the kernel probably would have stopped at "Checking FS...". If I had to guess I would say IOS_Open and IOS_close might be the culprits. No idea if sync_before_read can cause freezes. Unfortunately I have no idea how I figure out which line in DIinit is the problem...

EDIT: Just saw that DIinit quite changed since r230. It might be a good idea to check other old versions too. As expected i have little time the next days. MAybe I take a lok at this before new years eve.
 
I know that just stating it isnt a bad ISO. And matches the sha-1


I've had ISO images match all the hashes and still not work myself but I've tried other dumps of the same game and it worked fine. One game I've had it happen with was Tony Hawk's Pro Skater 3. Tried three different dumps, all had the same hashes, one of the dumps was completely clean and works fine. So, try other dumps.
 
I've had ISO images match all the hashes and still not work myself but I've tried other dumps of the same game and it worked fine. One game I've had it happen with was Tony Hawk's Pro Skater 3. Tried three different dumps, all had the same hashes, one of the dumps was completely clean and works fine. So, try other dumps.

Okay gonna try that
 
I've had ISO images match all the hashes and still not work myself but I've tried other dumps of the same game and it worked fine. One game I've had it happen with was Tony Hawk's Pro Skater 3. Tried three different dumps, all had the same hashes, one of the dumps was completely clean and works fine. So, try other dumps.
It is extremely unlikely that two different images will have the same sha-1 and be different internally. Especially if you also check MD-5 and CRC-32. If it worked in one case and not another with the exact same setup (same HDD or SD), the more likely difference was fragmentation. Recopying the file can change how the file was fragmented. The other possibility is if the game is just flaky (works sometimes, doesn't work other times, regardless of the image).
 
  • Like
Reactions: flamepanther
It is extremely unlikely that two different images will have the same sha-1 and be different internally. Especially if you also check MD-5 and CRC-32. If it worked in one case and not another with the exact same setup (same HDD or SD), the more likely difference was fragmentation. Recopying the file can change how the file was fragmented. The other possibility is if the game is just flaky (works sometimes, doesn't work other times, regardless of the image).


Then again, I don't know what I'm talking about, but, I've had issues with one verified ISO and tried another ISO dump of the same game and it worked. Anyways.
 
I've had ISO images match all the hashes and still not work myself but I've tried other dumps of the same game and it worked fine. One game I've had it happen with was Tony Hawk's Pro Skater 3. Tried three different dumps, all had the same hashes, one of the dumps was completely clean and works fine. So, try other dumps.
No luck same result
 
Has anyone had problems with TimeSplitters 2 (NTSC) randomly freezing? I want to play with forced 480p and widescreen but every 5-10 minutes it will freeze with that high pitched sound. Using the same settings on Dios Mios Lite and it will play fine without freezing but it has this graphical issue.

(Nintendont v2.259, USB Loader GX r1233 and used DMToolbox RAW Format)


Found the problem in case anyone else runs into it, Force Widescreen seems to cause the issue. Turned it off and so far haven't had anymore freezes
 
I've been wrong before, but here's an article that talks about sha-1 collisions:
http://thehackernews.com/2014/02/98-of-ssl-enabled-websites-still-using.html
Note that it is currently possible to get two different files with colliding sha-1. If you ripped your own disc that chances of it happening by accident are astronomical. Even if someone intentionally generated a file just to have the wrong sha-1 they would have needed a $700000 system to create it (according to the article, maybe a little less expensive now).

The much more likely situation is a fragmented file, bad sectors, or location on the drive (drive speed). This assumes you ran the checksums on the file where it was being run from (HDD or SD) to avoid copying errors.

If anyone runs into this situation, I'd like to know.
Requirements:
Two copies of a file that generate the same sha-1.
Binary compare the files (Use the same device that generated the sha-1s). HxD, for example, can generate the checksums and do the binary compares.

If they're really different, the binary diff will tell you.
 
Nintendont last rev/
Luigi's Mansion + Classic Controller = black screen
Luigi's Mansion + setting native controller + GC controller = work Fine
 

Site & Scene News

Popular threads in this forum