Homebrew [Release] NTM - NAND Title Manager for DSi

[TheSegaKid]

Actually got it working, but after a few installs it bricked, should have taken notes on the blocks -_-

 

[Pk11]

Actually got it working, but after a few installs it bricked, should have taken notes on the blocks -_-

oh oof... NTM has a lot of checks on the size so unless you were installing system apps it shouldn't be possible to brick by going over, the most likely way it could brick is the same as installing Unlaunch or doing a system update, simply the NAND dying of overuse causing a write to fail somehow.

What exactly happened and do you have Unlaunch? (ex. "An error has occurred", a number error, black screens, etc)

 

[Max6356]

OK. so i was installing flipnote on the SysNAND. so i went to the the tmd perservation so i checked and found the right id for flipnote so i renamed the id with the same name of the rom but with .tmd, dragged it to the same location as the rom. and guess what? IT STILL SAYS TMD NOT FOUND EVEN THO I LITERALLY HAVE IT AND IT SHOWED THE TMD IN THE TOP SCREEN. is there a fix. NTM is lying about the tmds.

 

[Pk11]

OK. so i was installing flipnote on the SysNAND. so i went to the the tmd perservation so i checked and found the right id for flipnote so i renamed the id with the same name of the rom but with .tmd, dragged it to the same location as the rom. and guess what? IT STILL SAYS TMD NOT FOUND EVEN THO I LITERALLY HAVE IT AND IT SHOWED THE TMD IN THE TOP SCREEN. is there a fix. NTM is lying about the tmds.

Whoops, I think I forgot to actually test that it worked when it had a TMD, only when it didn't...

Just released a fix: (Note Universal-DB takes a little bit to update, download from GitHub in the next half hour or so)

---

Version 0.1.4 - Derp fix​

Please see the wiki for information on how to use NTM.​

Bug fixes​

• Fixes the TMD warning always triggering, instead of only when the TMD is missing

As usual, the download is on GitHub or Universal-DB

 

[TheSegaKid]

Hi it's me again, got a new dsi but since the shop is in maintenance I cant access data management. How would I know how many blocks I'm taking up when installing apps

 

[Pk11]

Hi it's me again, got a new dsi but since the shop is in maintenance I cant access data management. How would I know how many blocks I'm taking up when installing apps

Either simply open the "Test" menu in NTM and it'll show (make sure you're in SysNAND mode or it'll show for your SDNAND) or get the latest commit build and run the Data Management enabler if you want real data management.

Also, can you give any more details on what exactly happened? Like, on the bricked console, does holding A + B while booting still let you go to the Unlaunch menu? Or what error did you get? That's really concerning if NTM actually bricked a console, especially if it wasn't just random NAND failure.

 

[TheSegaKid]

Either simply open the "Test" menu in NTM and it'll show (make sure you're in SysNAND mode or it'll show for your SDNAND) or get the latest commit build and run the Data Management enabler if you want real data management.

Also, can you give any more details on what exactly happened? Like, on the bricked console, does holding A + B while booting still let you go to the Unlaunch menu? Or what error did you get? That's really concerning if NTM actually bricked a console, especially if it wasn't just random NAND failure.

I simply got the "An error has occurred Hold down power button" and I dont have unlaunch installed on it, it got this error after always trying to boot into the dsi menu. This started happening after installing too many apps without my brain thinking about the blocks I could be taking up

 

[Pk11]

I simply got the "An error has occurred Hold down power button" and I dont have unlaunch installed on it, it got this error after always trying to boot into the dsi menu. This started happening after installing too many apps without my brain thinking about the blocks I could be taking up

Huh... That sucks, I tested very carefully to make sure that it couldn't over install but I guess I must've messed something up.

 

[TheSegaKid]

It did said when installing on the apps that "I think bricked it cant confirm if it bricked" that there was enough memory on storage. But I'm not gonna put blame on anything or anyone else but me on that. Not sure why it said "Enough room?: Yes"

 

[Pk11]

Version 0.1.5 - Data Management enabler and improved safety​

Please see the wiki for information on how to use NTM.​

What's new?​

• Adds an option to the main menu to enable Data Management in System Settings
  • This is done by simply creating an empty file for /sys/dev.kp, which causes Data Management to show up
  • This could potentially interfere with usage of the DSi Shop, though I think the shop would just replace it with with a proper one, but as the shop is dead there's not really any worry

Bug fixes​

• Changes the free space check to always leave at least 1 MiB free, hopefully this is enough margin for error as to prevent any more bricks, like the one reported by @TheSegaKid
  • I wish I knew exactly why that happened as I tested, using no$gba, down to the exact byte that my space calculations matched up iirc, but it's likely I missed something and since I was allowing such tight margins that allowed it to mess up
  • This shouldn't be a major concern for users with Unlaunch, but especially if you don't have Unlaunch I strongly recommend updating

As usual the download is on GitHub and Universal-DB

---

It did said when installing on the apps that "I think bricked it cant confirm if it bricked" that there was enough memory on storage. But I'm not gonna put blame on anything or anyone else but me on that. Not sure why it said "Enough room?: Yes"

That's really weird... As per ^ I've just made a new release that just adds a bit of margin for error that it will always leave free, hopefully that prevents anything like this ever happening again.

It's actually especially odd since the DSi doesn't usually do "An error has occurred" for a DSiWare space overflow, it should instead force you into Data Management and make you delete something. Just to be 100% sure, you weren't somehow installing as "system titles" right? That shouldn't have even been offered but if it was bugged and somehow did that would maybe get that error...

 

[TheSegaKid]

Are you able to download the dsi browser app with this?

 

[TheSegaKid]

I'm 100% sure I installed it as normal

 

[TheSegaKid]

Version 0.1.5 - Data Management enabler and improved safety​

Please see the wiki for information on how to use NTM.​

What's new?​

• Adds an option to the main menu to enable Data Management in System Settings
  
  • This is done by simply creating an empty file for /sys/dev.kp, which causes Data Management to show up
    
  • This could potentially interfere with usage of the DSi Shop, though I think the shop would just replace it with with a proper one, but as the shop is dead there's not really any worry
    

Bug fixes​

• Changes the free space check to always leave at least 1 MiB free, hopefully this is enough margin for error as to prevent any more bricks, like the one reported by @TheSegaKid
  
  • I wish I knew exactly why that happened as I tested, using no$gba, down to the exact byte that my space calculations matched up iirc, but it's likely I missed something and since I was allowing such tight margins that allowed it to mess up
    
  • This shouldn't be a major concern for users with Unlaunch, but especially if you don't have Unlaunch I strongly recommend updating
    

As usual the download is on GitHub and Universal-DB

---

That's really weird... As per ^ I've just made a new release that just adds a bit of margin for error that it will always leave free, hopefully that prevents anything like this ever happening again.

It's actually especially odd since the DSi doesn't usually do "An error has occurred" for a DSiWare space overflow, it should instead force you into Data Management and make you delete something. Just to be 100% sure, you weren't somehow installing as "system titles" right? That shouldn't have even been offered but if it was bugged and somehow did that would maybe get that error...

Yes, I installed it as a normal dsiware

 

[Pk11]

Are you able to download the dsi browser app with this?

Yeah, it should work the same as any other DSiWare.

Yes, I installed it as a normal dsiware

Welp, sucks that it bricked... I think you must've just been exceptionally unlucky with the sizes and gotten it to write a couple bytes too much in a way I overlooked or so...
If you can ever do a hardmod it should be a simple fix of just deleting a DSiWare and/or installing Unlaunch manually, but unfortunately without Unlaunch I don't think there's any easy fix.

 

[TheSegaKid]

I have a theory that if I had unlaunch installed on my dsi, I could have went on unlaunch and then into NTM and simply remove the dsiware that caused the error and everything would go back to normal. Which is why I will have unlaunch installed before installing dsiware, and if the dsiware works without a problem then I can delete unlaunch after

 

[godreborn]

another success.

 

[Pk11]

I have a theory that if I had unlaunch installed on my dsi, I could have went on unlaunch and then into NTM and simply remove the dsiware that caused the error and everything would go back to normal. Which is why I will have unlaunch installed before installing dsiware, and if the dsiware works without a problem then I can delete unlaunch after

Yeah, that's why I strongly recommend having Unlaunch installed if it's not detected on running NTM and in the wiki.

Though there's a notable brick risk on uninstalling Unlaunch, so what I would personally recommend is to leave it installed and simply set NO BUTTON to Launcher (the DSi Menu), then it's just like stock but much safer. If you don't have the splash/sounds in the DSi Menu simply reinstall Unlaunch from TWiLight Menu++ with "Launcher Patches" enabled.

 

[TheSegaKid]

I've discovered a problem, I'm unable to customize where I want my dsiware to be placed in the menu, if I restart my dsi or go into a game and go back to dsi menu, the dsiware moves back to where is originally was when unboxed

 

[Pk11]

I've discovered a problem, I'm unable to customize where I want my dsiware to be placed in the menu, if I restart my dsi or go into a game and go back to dsi menu, the dsiware moves back to where is originally was when unboxed

mhh, likely some file on NAND got corrupted... I'm not sure what it would be, you may be able to fix it by restoring an old NAND backup or making a new one, checking for any seemingly broken files, testing in no$gba, and if fixed restoring that.

Whatever you do, assuming you have it, do not uninstall Unlaunch. I had that happen on one DSi and it bricked on uninstalling Unlaunch. I happened to have a NAND backup from shortly before uninstalling and the brick was 100% consistent in no$gba so it's very likely your console would brick without Unlaunch atm.

If you don't have a good NAND backup I can try testing on my backup to see if I can find the cause of the positions not saving, I haven't really messed with it much. It's possible it's caused by the first few hundred bytes of the DSi Menu's title.tmd getting 0'd out, that's what caused mine to brick. Not sure how it happened, but by uninstalling Unlaunch it exposed an issue already present but previously kept safe by having Unlaunch.

 

[TheSegaKid]

I'm sadly not creating a NAND backup. I have none from this dsi and I can't restart on a new one. I have no idea why I can't move any of the apps or games. Should I just backup now to see if you can find the problem?