yfw it always has been this way. heh
https://gbatemp.net/threads/list-of-known-bricks-setting-up-a9lh.418899/
Huh, two bricks are user error.. what a coincidence.
False information. There's never been reports that didn't unbricked 2.1. Some builds gave false reports of the downgrade (which has already been fixed).
You can not say the applications don't ever fail because that's simply false. Some of us would rather not risk bricking our systems over simple things like a slightly better boot rate and faster booting.
No it's not. I've seen it happen. It didn't unbrick my 2.1.
Don't forget:
Decrypt9 on boot
Sysnand CFW
Did you unbrick the emunand before restoring it to sysnand?
OTPHelper doesn't automatically unbrick as far as I know.
I think OTPHelper has checks against this to prevent a bricked 2.1 emunand from being restored now.
Have you tried taking out the SD card?
If you still have the SysNAND backup you should still be able to get a hardmod to fix it.
If it was due to laziness, not having time, or simply not caring, then I'd understand. You do you.
But if it's risk factor, then I would say your argument would be quite weak. How many people have bricked when downgrading to 9.2?
Wow. I don't want A9LH. Stop being so damn butthurt over it. Geez, you're as bad as PCMR. Yes btw, I did select the unbrick option and it didn't work. I do have the sysNAND backup too. It's really not worth the risk. If you only fuck around in emuNAND you don't need any of that stuff.
But, like I said. If you want CFW you need 9.2. A9LH? Not so much.
You see that @Margen67? He didn't like you stating the facts.
Anyways, your choice if you want to install A9LH or not. Just don't take risk factor into your decision.
I'm off!
I've downgraded my own consoles to 2.1.0-4 7 times (3 Old3DS, 2 New3DS), mostly when the guide was more manual work. one of them was to test the unbricker of OTPHelper and it worked just fine.
I've also helped a few others obtain their OTP, and each time it's worked with no bricked consoles. so the risk of a brick has become virtually nothing at this point unless you don't pay attention, such as using the wrong downgrade packs for your region.
how can someone be so sure it was the "unbrick" option that failed? I tried it once, and also did it manually on a computer, and both produced matching dumps. I have to wonder if something else happened outside of that (faulty SD card? wrong downgrade pack region? failed mid-downgrade?).
and yes, you can still use emunand with arm9loaderhax if you so desire (don't place NAND.bin at the root when you install).
I've also helped a few others obtain their OTP, and each time it's worked with no bricked consoles. so the risk of a brick has become virtually nothing at this point unless you don't pay attention, such as using the wrong downgrade packs for your region.
how can someone be so sure it was the "unbrick" option that failed? I tried it once, and also did it manually on a computer, and both produced matching dumps. I have to wonder if something else happened outside of that (faulty SD card? wrong downgrade pack region? failed mid-downgrade?).
and yes, you can still use emunand with arm9loaderhax if you so desire (don't place NAND.bin at the root when you install).
Last edited by ihaveahax,
I've done it on multiple systems, including two n3ds, and I've never bricked on the post wiki guide.
Last edited by astronautlevel,
OK? And people have too. What's your point? Can we all STFU and get back on point? This thread isn't about A9LH.
when i install ctrbootmanager coldboot cfw (dont matter which cfw) it dont boot cfw it boots hbl.
i need help please (i tried aureinand rxtools and cakes fw) still the same
(minipasta does the same)
i need help please (i tried aureinand rxtools and cakes fw) still the same
(minipasta does the same)
Last edited by Purple_Heart,
too late.
they're not. they're saying why they'd rather not do it. plus all this nonsense is off topic anyway.
Last edited by dimmidice,
Similar threads
