Hacking 3ds Bricked after inject secure_infoA to Sysnand

  • Thread starter Thread starter V3N0MBR
  • Start date Start date
  • Views Views 5,705
  • Replies Replies 31

V3N0MBR

Active Member
Newcomer
Joined
Jan 9, 2016
Messages
39
Reaction score
3
Trophies
0
Age
41
XP
649
Country
Brazil
Hello everyone,
Got a bricked 3ds, the guy injected secure_infoA to Sysnand and bricked.

Got to do the hardmod, but the guy didn't got a sysnand backup,

I used emunand tool to backup the emunand from the sd card.

I have hardmod installed but don't know how to recover the secure_infoA from hardmod.

Can someone help me??
 
Hello everyone,
Got a bricked 3ds, the guy injected secure_infoA to Sysnand and bricked.

Got to do the hardmod, but the guy didn't got a sysnand backup,

I used emunand tool to backup the emunand from the sd card.

I have hardmod installed but don't know how to recover the secure_infoA from hardmod.

Can someone help me??
Hmm... I'd say your best bet is to inject the nand backup into an emunand and extract the secure_infoA with decrypt9. I think that's possible anyways.
 
Hello everyone,
Got a bricked 3ds, the guy injected secure_infoA to Sysnand and bricked.

Got to do the hardmod, but the guy didn't got a sysnand backup,

I used emunand tool to backup the emunand from the sd card.

I have hardmod installed but don't know how to recover the secure_infoA from hardmod.

Can someone help me??
Flash your emunand to your nand, or do the above
 
So i have the original secure_info saved, but the emunand backup i think has the secure_info changed to.
 
Last edited by V3N0MBR,
Sorry then the guy fucked up. If you don't have a valid backup with a working Secureinfo_A then the unit is unrecoverable.
You need xorpads to en/decrypt and inject/extract secureinfo_A from a nanddump. Since the unit is bricked you can't dump xorpads except you've got a9lh installed.

These xorpads are console unique and every nanddump is encrypted with it.A 2nd 3DS won't help to restore the unit.
 
Last edited by GothicIII,
restore your original secureinfo a flash to sysnand
Congrats on not reading the thread replies and posting a shit reply... Bravo.

He doesn't have a clean system dump of sysnand or emunand that isn't borked. The system is ka-put.
 
Congrats on not reading the thread replies and posting a shit reply... Bravo.

He doesn't have a clean system dump of sysnand or emunand that isn't borked. The system is ka-put.
I'd post something vengeful but I realized you are not worth a shitierer reply than the one I posted above :)
If you have PMS don't go around telling people they are making a shity reply. - Bravo to you too.

lol
 
Elaborate more on what you have/don't have. Nand, emunand backup, both broken. Original SIA not in either backup. Fat16 nand zor? Any zor?

The more you elaborate the more/less help. We Need to understand how you got there, the files you used/created and saved/didn't save.

Anyone can mess up, spill it all and maybe you will be thrown a life line, if possible....
 
Elaborate more on what you have/don't have. Nand, emunand backup, both broken. Original SIA not in either backup. Fat16 nand zor? Any zor?

The more you elaborate the more/less help. We Need to understand how you got there, the files you used/created and saved/didn't save.

Anyone can mess up, spill it all and maybe you will be thrown a life line, if possible....

I got emuNAND.bin from SD card, but secureInfo_A was changed first.
I got sysNAND.bin from the bricked 3ds with hardmod, but secureInfo_A was changed before.

I got secureInfo_A original backup and changed backup.

Just these files i have.
 
If I'm reading this right, you did the a9lhax region changing steps without having a9lhax and also have no functional backups or xorpads. This means that you are beyond fucked. Congrats.

From the guide (in bold):

"You MUST have already completed Part 5 and installed arm9loaderhax + Luma3DS to use this."
"You SHOULD have confirmed functional NAND backups of your arm9loaderhax 3DS (such as sysNAND-A9LHAX.bin) in case something goes wrong."


Neither of these things were done.
 
Well if you have the original secureinfo_a, there is a moonshot way. Find the sector that secureinfo_a is stored in--it should be small enough to fit into a single sector. Since the file never changed in size, it should be in the same sector as another 3ds, so it would be easy to look up. Then just XOR that sector with the modified secureinfo and XOR it again with the original secureinfo.
 
Well if you have the original secureinfo_a, there is a moonshot way. Find the sector that secureinfo_a is stored in--it should be small enough to fit into a single sector. Since the file never changed in size, it should be in the same sector as another 3ds, so it would be easy to look up. Then just XOR that sector with the modified secureinfo and XOR it again with the original secureinfo.
So, thx for the answer. Where secureInfo is located??
 

Site & Scene News

Popular threads in this forum