Homebrew Think I Bricked My O3ds, help please!

  • Thread starter Thread starter lordkramGB
  • Start date Start date
  • Views Views 2,376
  • Replies Replies 21

lordkramGB

Member
Newcomer
Joined
Jun 3, 2016
Messages
24
Reaction score
3
Trophies
0
Age
43
XP
115
Country
Ok so i've managed to downgrade consoles before with no problems, managed to get my o3ds downgraded to 9.2, and wanted to setup OTP for the A9LH installer (gateway 3ds) so I decided to try and use plaiSysUpdater to downgrade straight to 2.10
I used GW to backup my sysnand, then using menuhax booted into plaiSysUpdater and went to downgrade to 2.10 option
I made sure I had the correct files in update folder etc on the root of the card.
plaiSysUpdater checked all the files and came back as OK, the downgrade process started and all files went to OK until it got to the end when I got a Nintendo error screen came up (no complete message etc)
I then rebooted and now nothing happens just a black screen
I can boot into recovery mode, but its pointless as I don't want to update to latest 11.0 as i would still have to get a hardmod to downgrade back to 9.2
Question is can I do anything to get my o3ds back running without a hardmod?
Is there a way to restore my sysnand that was backed up on my sd card, or would that possibly be the reason why it bricked in the first place?
Help!
 
have you tried removing the SD card and booting?

a blackscreen after downgrading to 2.1 is common, you usually just remove the SD and it will boot fine
 
Ok so i've managed to downgrade consoles before with no problems, managed to get my o3ds downgraded to 9.2, and wanted to setup OTP for the A9LH installer (gateway 3ds) so I decided to try and use plaiSysUpdater to downgrade straight to 2.10
I used GW to backup my sysnand, then using menuhax booted into plaiSysUpdater and went to downgrade to 2.10 option
I made sure I had the correct files in update folder etc on the root of the card.
plaiSysUpdater checked all the files and came back as OK, the downgrade process started and all files went to OK until it got to the end when I got a Nintendo error screen came up (no complete message etc)
I then rebooted and now nothing happens just a black screen
I can boot into recovery mode, but its pointless as I don't want to update to latest 11.0 as i would still have to get a hardmod to downgrade back to 9.2
Question is can I do anything to get my o3ds back running without a hardmod?
Is there a way to restore my sysnand that was backed up on my sd card, or would that possibly be the reason why it bricked in the first place?
Help!
That's why you follow the guide you were supposed to downgrade RedNAND not Sysnand.
 
tbh for a o3ds i have skipped straight to downgrading sysnand iirc, its not like on a n3ds where the encryption has to be fixed, a o3ds should be compatible with 2.1 by default

that said if your not 100% sure you have a recovery plan you should follow the guide exactly, im wondering if he stayed in GW mode when doing the downgrade, as GW mode causes issues with updating/downgrading nativefirm, so you cannot use GW mode for the downgrade stage
 
Last edited by gamesquest1,
tbh for a o3ds i have skipped straight to downgrading sysnand iirc, its not like on a n3ds where the encryption has to be fixed, a o3ds should be compatible with 2.1 by default

that said if your not 100% sure you have a recovery plan you should follow the guide exactly
lol I just noticed it was you I was about to tag you saying you had a customer :P
 
  • Like
Reactions: gamesquest1
lol I just noticed it was you I was about to tag you saying you had a customer :P
lets see, hopefully he just forgot to remove the SD card after downgrading, but im thinking its the GW issue, i did exactly the same on one console, i completely forgot that GW messes with upgrade/downgrades to sysnand and i ended up bricking by trying to save time :sad: (my laziness ended up taking up more time xD)
 
  • Like
Reactions: Xenon Hacks
lets see, hopefully he just forgot to remove the SD card after downgrading, but im thinking its the GW issue, i did exactly the same on one console, i completely forgot that GW messes with upgrade/downgrades to sysnand and i ended up bricking by trying to save time :sad: (my laziness ended up taking up more time xD)
Yeah OTP helper probably would have said that RedNand was bad because of Gateway.
 
Yeah I have tried removing both sd and gw card but system still won't boot
I can access recovery mode though so is there hope without a hardmod?
Edit I definitely wasn't in GW mode when trying to downgrade as I booted into hbl using menuhax then opened the plaisystemupdater app
 
Last edited by lordkramGB,
As far as I know, 4.0b removes FIRM protection. However, if he used 3.7.1 that still has it, and would def cause a brick. (Fun fact, using the GW's a9lh.bin on 3.7.1 will remove FIRM protect on that, as discovered by Kazuma77)

Yeah I have tried removing both sd and gw card but system still won't boot
I can access recovery mode though so is there hope without a hardmod?
Anyways, you're def bricked. Hardmod only. At least you have a sysNAND backup.
 
What will having a hard mod do for me in the long run? I was confident in doing this downgrade etc as I've done similar things with a psp in the past (different I know)
I originally tired to use the GW guide for the latest beta to try and install the AL9H so my 3ds would boot straight into GW3ds mode but the guide they gave on their site didn't make sense so that's why I tried to downgrade straight to 2.1 from 9.2
 
Last edited by lordkramGB,
Wish I'd known that before but since I've had no problems with stuff before I thought I could do it this time around obviously not!
Is it worth still trying to update using recovery mode so I can at least get back into my 3ds?
 
Wish I'd known that before but since I've had no problems with stuff before I thought I could do it this time around obviously not!
Is it worth still trying to update using recovery mode so I can at least get back into my 3ds?
Updating to any version above 6.x on 2.x will brick your 3DS.

--------------------- MERGED ---------------------------

Use a cart that has a 4.x update pack on it to go back to 4.5 and restore the NAND backup. Or you can update back to 9.2 from there.
 
Wish I'd known that before but since I've had no problems with stuff before I thought I could do it this time around obviously not!
Is it worth still trying to update using recovery mode so I can at least get back into my 3ds?

Mistakes can happen. You will be stuck on 11.0 without any downgrade method, if you use recovery mode.

--------------------- MERGED ---------------------------

Updating to any version above 6.x on 2.x will brick your 3DS.

--------------------- MERGED ---------------------------

Use a cart that has a 4.x update pack on it to go back to 4.5 and restore the NAND backup. Or you can update back to 9.2 from there.

Think you got confused a bit there mate. That is not possible in the OP's situation right now.
 

Site & Scene News

Popular threads in this forum