Hacking AuReiNAND + Menuhax + Lesshax = 99.99% boot rate

  • Thread starter Thread starter GBAFail
  • Start date Start date
  • Views Views 13,962
  • Replies Replies 90
  • Likes Likes 2
only had time to try 10 boot ups for now. but it got a 9/10 (failed the second time) so that's pretty good. i'l see how it behaves some more later. but for now thanks OP :)
 
Yeah, it's not as dangerous anymore. Especially thanks to OTPHelper and SafeA9LHInstaller.

Only way you can brick now is if you made a mistake.
Not true. Those applications can fail/crash. I've seen reports of OTPHelper not unbricking 2.1.
 
Not true. Those applications can fail/crash. I've seen reports of OTPHelper not unbricking 2.1.
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.
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).
No it's not. I've seen it happen. It didn't unbrick my 2.1.
 
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" (LOL) better boot rate and faster booting.
Don't forget:
Decrypt9 on boot
Sysnand CFW
No it's not. I've seen it happen. It didn't unbrick my 2.1.
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.

Yeah, but 9.2 is necessary for kernel access and CFW. A9LH isn't. It's just a bonus if you don't care about the risks. I already bricked one n3DS and I really can't afford another.
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.
 
  • Like
Reactions: Xenosaiga
Yeah, but 9.2 is necessary for kernel access and CFW. A9LH isn't. It's just a bonus if you don't care about the risks. I already bricked one n3DS and I really can't afford another.
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?
 
will it work with GW?

BTW,enough with VS posts everywhere
we know A9LH is super good, but sometimes we like to stay on the same boat.
 
Last edited by aos10,
  • Like
Reactions: GBAFail
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.
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.
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?
But, like I said. If you want CFW you need 9.2. A9LH? Not so much.
 
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).
 
Last edited by ihaveahax,
  • Like
Reactions: Supster131
Even if you don't screw it up. Especially on n3DS! Even if you do everything right the tools themselves can fail and cause a brick.
I've done it on multiple systems, including two n3ds, and I've never bricked on the post wiki guide.
 
Last edited by astronautlevel,
Last edited by dimmidice,
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)
Hold select once menuhax starts loading, go into the settings, and set the cfw as default.
 

Site & Scene News

Popular threads in this forum