Hacking Can't downgrade in hardmod from 11.2.0-35E

[iMarsel]

I'm having a problem downgrading my o3DS XL with firmware 11.2.0-35E, I have hardmod setup alrady backed up my nand and I have tried every guide like this one https://3ds.guide/hardmod-downgrade and this one https://www.reboot.ms/forum/threads/downgrade-3ds-da-11-1-11-2-a-9-2.3252/ I have tried with different version of autofirm with all the files in place like the guide shows but for some reson every time I write the nand back to the 3ds and access homebrew through oothax ang check with 3DSident nothing has changed I'm still on 11.2.0-35 kernel 2.52-0 and FIRM 2.52.0 and if I try to downgrade I get "did not get am:u handle, please reboot." Any idea why is not working beacuse I have tried so many times is making me crazy. Thank You

 

[munchy_cool]

paging @vb_encryption_vb

 

[vb_encryption_vb]

Not writing the patched nand back from the sounds of it.

 

[iMarsel]

Not writing the patched nand back from the sounds of it.

when I write it back to the 3ds with win32 disk imager everythig goes fine I think maybe autofirm is not patching it for some reason

 

[vb_encryption_vb]

Your writing NAND.bin back correct? Also, you have the 10.4 cia, etc files for patching?

 

[iMarsel]

Your writing NAND.bin back correct? Also, you have the 10.4 cia, etc files for patching?

Yes i write it back correctly and i have o3DS 11.2.cia, o3DS 11.1.cia, o3DS 11.0.cia, o3DS 10.4.cia in the autofirm folder with my original nand.bin and I follow the guide correctly wen i chose 1 for old 3ds/xl or 2ds and 3 for my firmware version 11.2 and it generates the new nand. I write it back to the console fine but i'm still on the same version when i check it with 3DSident

 

[Lessthan0tom]

I just had the exact same problem as you. The guide isn't always 100% right since it references so many release tabs for different open source software on Github. If you're using the most recent version of autofirm that the guide currently links to, it says it'll rename the image you put in there from nand.bin to something with backup in the name and the patched version will have the name name as the one you dropped in there originally. If you pay attention you will notice that it actually now leaves the name of the original the same and creates a new one with patched in the name. I reccomend you re-download autofirm and start the process from scratch, paying close attention to what happens at every step.

 

[iMarsel]

I solved it, searching on the forum I found that when you check your nand with HxD it shoud have NCSD" at byte 0x100 mine was some how corrupted so I changed all the wires and used a drifferend sd card reader and it worked.

 

[Deleted-19228]

if any of that was corrupted your 3ds would have bricked

 

[iMarsel]

if any of that was corrupted your 3ds would have bricked

I know and that's strange I was reading and writing with win32diskimager finishing successfully without brick than when i checked my nand with HxD instead of NCSD was like iiiiiiiiiiiiiiiiii. Than i changed all the wires and sd card i read my nand again checked with HxD and was fine. I pached it and wrote it again and it is working.

 

[Deleted-19228]

That's the thing though. You overwrote your NAND on your 3DS so when you re-read it you would read the exact same info you wrote. You literally lost your original 0x100 so what you are saying really makes no sense lol