anyway to recover DSI XL brick?

  • Thread starter Thread starter duduqaz
  • Start date Start date
  • Views Views 4,612
  • Replies Replies 31
you can get the console id even if the console has no emmc.
If I change dsi CPU or a blank eMMC chip, how to get console id(Uniqe ID) without emmc.
But i can't find any info/tools on how to get the CID.
I don't know if twlnandtool (still in development) can do this, or create a new NAND.
 
Last edited by k66,
There's an amazing tool named AES-TEST that displays a register. You can get the console id with that.
All tools get the CID from the emmc register. There's an old fork of fwtool that gets it from ram. I managed to find it. The problem is that fwtool turns off the console if there's no emmc present. I guess it checks for the emmc at startup. The solution is to edit the code and compile it. But i know nothing about programming.

I know abot nand tool, but it's for pc, has nothing to do with the console's ram.
 
  • Love
Reactions: k66
There's an amazing tool named AES-TEST that displays a register. You can get the console id with that.
Where can I find AES-TEST and how to use it. If I replace a new CPU, can I still get a console id?
Can the original NAND still be used after replacing a new CPU? (like a emulator)
I know abot nand tool, but it's for pc
I am talking about twlnandtool
 
Last edited by k66,
Oh... That tool looks really intersting. Sadly, there's no release. I don't know how to compile It. In the screenshots I can see the CID and the samsung brand. I hope it reads it from ram 2FFD7BCh. Do you know if there 's a compiled version floating around?

about the console id, you can get the file from here (scoll down a little):
https://www.ngemu.com/threads/dsi-cid-discovered.169257/
The buttons don't do anything, except switch between the 2 pages. I'll add a picture from this faulty console without emmc. A few post above, I said i already got the console id, And you can see in the picture that it is the same. I've also tested this on a working dsi xl console and the console id matched with the one reported by safenandmanager.

I don't know if a different cpu will work. you can get the console id from it like i've said. I don't know if you encrypt the nand with the cpu cid will work,

PS: if you look at the bottom of my picture you will see that the console id is repeating itself. I run the rom directly from ntrboot,.
PS2: I think we'll have to deal with 2 more files: dev.kp and HWINFO_S.dat. But first we must get the cid.
PS3: I see that twlnandtool has an oprion to repair mbr. the emmc is in the trash now...
 

Attachments

  • console iD.jpg
    console iD.jpg
    354.3 KB · Views: 41
Last edited by gorgyrip,
  • Like
Reactions: k66
Oh... That tool looks really intersting. Sadly, there's no release. I don't know how to compile It. In the screenshots I can see the CID and the samsung brand. I hope it reads it from ram 2FFD7BCh. Do you know if there 's a compiled version floating around?
I don't have a compiled version.
I asked author, there are still bugs at the moment, and author does not recommend that I use it.
Maybe you can develop with author @rvtr :lol:
 
Last edited by k66,
yes, that was me. have you managed to get the console id?
I got the console id(UID) :lol:, console id matched with NAND backup's no$gba footer.
(on a normal regular DSi, I have not changed CPU yet)
 

Attachments

  • 20250512.png
    20250512.png
    726.5 KB · Views: 40
  • 20250512a.png
    20250512a.png
    702.5 KB · Views: 30
  • 20250512a5.png
    20250512a5.png
    9.3 KB · Views: 29
Last edited by k66,
  • Like
Reactions: gorgyrip
There's an amazing tool named AES-TEST that displays a register. You can get the console id with that.
All tools get the CID from the emmc register. There's an old fork of fwtool that gets it from ram. I managed to find it. The problem is that fwtool turns off the console if there's no emmc present. I guess it checks for the emmc at startup. The solution is to edit the code and compile it. But i know nothing about programming.

I know abot nand tool, but it's for pc, has nothing to do with the console's ram.
hi, did u managed to solve the problem someway?

this error makes me upset... its hard to believe the console died in a r4 hack attempt, the error is right after the old owner tried it.
 
I replaced the emmc with a sd card. RVT-R helped me with the software. The console is now stuck in factory firmware. It can play game carts, including R4. But there's no home menu. Homebrew doesn't work.
 
  • Like
Reactions: rvtr
Homebrew doesn't work.
For a little more context, a lot of homebrew wants to check NANDs when run on a DSi. They compare a hard-coded MBR, so NAND init will fail unless you have the exact same chips as real hardware.

iirc unlaunch also does this but with a hard coded NAND IDs as well. May be wrong on unlaunch though since I haven't touched it in a bit.
 

Site & Scene News

Popular threads in this forum