Hacking BOOTROM Error! cant boot NAND backup

[feloncio]

Hi!
i was to do a hardmod to my old 3ds XL,i have a backup of my NAND and a modified nand for downgrade.
when i write the modified nand restart my 3ds but a blue screen with a bootrom error appear (error code: 00F800FF
F8F8FFFF FFFFFFFF
00000000 00000000)

i tried re write my original NAND, weld the SD card, turn on without hardmod, turn on with hardmod and SD connected to PC but doesn't work... blue screen appear any time.
any idea about it? i dont know what to do

i hope that any guy can help me and sorry for my bad english!

PD: when disk manager is making my nand backup, i pressed two times the pad (moving in menu), i think that this action affect my nand backup (or maybe not... idk)

 

[8BitWonder]

I'm no expert with hardmods, but from looking at this; https://www.3dbrew.org/wiki/Bootloader
It looks like you maybe have a bad NAND dump, that or the changes you've made are failing sig checks. Maybe try another clean dump? (Hopefully you made multiple)

 

[feloncio]

thanks for response, well... i checked the NAND.bin in hex editor and the "NCSD" it's ok.
i tried writing original nand on patched nand a lot of times but nothing change
i dont know if i can format the disk from windows and write the original nand from zero, its possible do this? or my brick will be turn in a piece of shit?

please somebody help meeeee!! haha

 

[Majickhat55]

thanks for response, well... i checked the NAND.bin in hex editor and the "NCSD" it's ok.
i tried writing original nand on patched nand a lot of times but nothing change
i dont know if i can format the disk from windows and write the original nand from zero, its possible do this? or my brick will be turn in a piece of shit?

please somebody help meeeee!! haha

Check your soldering too, perhaps you bridged a connection somewhere?

 

[feloncio]

Check your soldering too, perhaps you bridged a connection somewhere?

ill check it now but any idea about format using SD adapter from PC?

 

[feloncio]

FAILED!
i checked all connections, all pines and all its ok... i tried to read the NAND in another notebook with the same result
i put my backup NAND and my new patched NAND but nothing change!!
any idea?

 

[lyk93]

Show us a picture of your soldering work.

Sent from my Redmi Note 2 using Tapatalk

 

[Skyshadow101]

@vb_encryption_vb @gamesquest1


Any ideas?

 

[Ev1lbl0w]

According to https://www.3dbrew.org/wiki/Bootloader#Error_Codes , "Both the firm0 and firm1 partitions are corrupt". So, this probably indicates a bad NAND dump.

Can you run SHA-256 or MD5 hashes of all the dumps you have done and confirm they're all the same?

 

[PegLegs]

i dont know if i can format the disk from windows and write the original nand from zero, its possible do this? or my brick will be turn in a piece of shit?

^made me giggle^

U dun goofed me finks

 

[feloncio]

Show us a picture of your soldering work.

Sent from my Redmi Note 2 using Tapatalk

yes, here is!! you can see that all its ok!!
i think that the problem is not here... what do u think?

According to https://www.3dbrew.org/wiki/Bootloader#Error_Codes , "Both the firm0 and firm1 partitions are corrupt". So, this probably indicates a bad NAND dump.

Can you run SHA-256 or MD5 hashes of all the dumps you have done and confirm they're all the same?

sorry, i dont have MD5 from my original dump and i have only one backup from original (yes, i'm so stupid!! )
but, in hex. the offset 100 show me the NCSD correctly! so, i dont know what to do
i'll buy another SD card reader for test but... i think that the problem is not in the SD reader...

any other idea?
i dont have raspberry pi for try with this!

 

[gamesquest1]

if your original dump was bad then you are screwed, write the original nand backup, then dump it again and check that the hash matches that of the original dump, if it different then there is hope that it's just not writing back correctly, if it matches then your original dump was probably corrupt

can you check at 0xb130000 and see if there is anything there or if it's just all zeros

 

[TheToaster]

And this, my friends, is why we make multiple dumps and check the sizes and hashes of them.

 

[feloncio]

if your original dump was bad then you are screwed, write the original nand backup, then dump it again and check that the hash matches that of the original dump, if it different then there is hope that it's just not writing back correctly, if it matches then your original dump was probably corrupt

can you check at 0xb130000 and see if there is anything there or if it's just all zeros

sure

here is b130000... its ok? or have any problem?
and, now ill try to write the original NAND and check it with hex.

thanks guys!! i hope more comments i really apreciate it!!