Hacking Incomplete downgrade procedure from O3DS XL from 10.7 to 9.2, can it be fixed?

Geezerdorf

Well-Known Member
OP
Newcomer
Joined
Apr 11, 2016
Messages
96
Trophies
0
Age
40
Location
ヴェラクルス、メキシコ, AKA Hell.
XP
573
Country
Mexico
As the title suggests, i was trying to make a system downgrade for an O3DS XL i had lying around. Having done at least 3 previous succesful downgrades before, i grew confident. However, 10.7 didn't allow Decrypt9 to proceed and do a NAND backup, resulting in having to do downgrade first, then a NAND backup.

The first time, sysupdater marked an error, with one of the .cia files of the the update (weird, as i used those same files for the Previous 3 O3DS; valid region and all), and ended with a frankenfirmware 9.2, but still allowed me to enter HBL with Cubic Ninja, using 10.7 entrypoints.

I thought that the issue could be a slow SD card, so i changed it with another one, formatted just in case, but to no avail. The second time tried to run sysupdater, it patched several files, but this time, it took longer before prompting an error, and when i tried to press B to quit and reset the system, the screens now go only black. Tried the forced update method to see if i had a little more of chance to achieve something, but it didn't work.
My guess is that since it couldn't patch all the .cias, it may have bricked the nand. Unfortunately, i couldn't get a backup of it, as i was ACTUALLY downgrading to get Decrypt9 working.
I'm really surprised, as i used the same tools and files to downgrade 3 previous O3DSes. Don't know what exactly happened to cause the error.

My question is, is there any way that i could salvage this console and unbrick it? I can Hard mod it without any troubles, but i'm worried since i do not have a nand backup to reflash to this console. Would just a reflashing of the same incomplete nand.img help me? Or could i inject the remaining .cias files to such image and then flash it back to the console? if so, how?

I apologize beforehand if this has been posted before, but i haven't found an explicit answer to that skimming through a lot of threads right now.
 

Seepy

Member
Newcomer
Joined
Mar 24, 2016
Messages
24
Trophies
0
Age
34
XP
85
Country
Probably a stupid question, but have you tried using the recovery menu using L+R+Up+A on boot? If you have and you still cannot access the system, then I would say it's impossible for you to recover the 3DS.
 

Geezerdorf

Well-Known Member
OP
Newcomer
Joined
Apr 11, 2016
Messages
96
Trophies
0
Age
40
Location
ヴェラクルス、メキシコ, AKA Hell.
XP
573
Country
Mexico
Probably a stupid question, but have you tried using the recovery menu using L+R+Up+A on boot? If you have and you still cannot access the system, then I would say it's impossible for you to recover the 3DS.

Yes. No results at all

Tried the forced update method to see if i had a little more of chance to achieve something, but it didn't work.
 

gkoelho

Well-Known Member
Member
Joined
Apr 16, 2015
Messages
558
Trophies
0
Age
31
XP
346
Country
Brazil
Sorry to say, but if u cant boot neither on sysnand or system recovery and doesnt have a valid backup then u are for sure bricked beyond help.

U can send it to nintendo for repair though.
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • No one is chatting at the moment.
    Xdqwerty @ Xdqwerty: yawn