Hacking Arm9loaderhax vs Menuhax Coldboot Comparison

  • Thread starter Thread starter NekoMichi
  • Start date Start date
  • Views Views 12,069
  • Replies Replies 76
  • Likes Likes 5
Random bricks? There is no possibility for a random brick, and not a single random brick has been reported by any user. The risk of doing this is exactly the same risk as downgrading.
Looks like most bricks have come from user-error. So far I've installed A9LH on 3 consoles with no problem (other than sleep deprivation from the long and tedious process:blink:). When sysUpdater was first used, weren't there reports of it crashing mid-installation? I can't verify those claims but random crashing mid-installation or mid-NAND restoring is my biggest fear when doing these things.
 
@funnystory I see what you mean, but some people could on the contrary even see that as an upside. Just figure that you can remove your SD card from your 3DS when you're not using it and voilà, no one can update your sysNAND behind your back since no one can boot your 3DS. And even if they could, AuReiNand would still be able to boot on the updated sysNAND.
 
  • Like
Reactions: Supster131
Looks like most bricks have come from user-error. So far I've installed A9LH on 3 consoles with no problem (other than sleep deprivation from the long and tedious process:blink:). When sysUpdater was first used, weren't there reports of it crashing mid-installation? I can't verify those claims but random crashing mid-installation or mid-NAND restoring is my biggest fear when doing these things.
I remember one report, back when the 10.3-9.2 downgrade sysUpdater first came out. He said that it crashed mid-downgrade, but I haven't seen a report like that since then and he was using a VERY early version of sysUpdater. Chances are, the downgrade did indeed finish but he had the wrong CIA pack.
 
  • Like
Reactions: NekoMichi
I remember one report, back when the 10.3-9.2 downgrade sysUpdater first came out. He said that it crashed mid-downgrade, but I haven't seen a report like that since then and he was using a VERY early version of sysUpdater. Chances are, the downgrade did indeed finish but he had the wrong CIA pack.
Ah, I see. I was initially very worried about stuff like that but with each successful downgrade/installation I do, I get a little less paranoid.
 
  • Like
Reactions: endoverend
What's "it"? The programs don't mess up. No one has ever reported them messing up.

Looks like most bricks have come from user-error. So far I've installed A9LH on 3 consoles with no problem (other than sleep deprivation from the long and tedious process:blink:). When sysUpdater was first used, weren't there reports of it crashing mid-installation? I can't verify those claims but random crashing mid-installation or mid-NAND restoring is my biggest fear when doing these things.
So this can only go bad if i dont do this incorrectly? I have confidants in myself, but not downgrading to 2.1

Edit- did not mean to put correctly ;-;
 
Last edited by Lumince,
So this can only go bad if i dont do this correctly? I have confidants in myself, but not downgrading to 2.1
Bro. This can go south even if it's not your fault. Just make sure YOU are focused on downgrading. That'll minimize the risk by a lot and make 2 or 3 dumps of everything and check their checksums to see if they match up.
 
  • Like
Reactions: pbanj
So this can only go bad if i dont do this correctly? I have confidants in myself, but not downgrading to 2.1
Downgrading to 2.1 is very similar to downgrading to 9.2 in terms of risks. The only difference is that on N3DS(XL), downgrading emuNAND to 2.1 will brick it (this is intentional, and required for the entire process to work), and it's important to dump the 2.1 emuNAND and run the unbricking script on your PC before attempting to flash it to sysNAND.
 
Using Menuhax + ctrbootloader and MSET or Cubic Ninja as a backup.

Idort master race! Get on my level!
 
You know what I mean. Not like me doing something wrong. but it messing up in the process.
The only real way to fuck it up is to not use your OTP. If you are using your own OTP, you should be good to go.
Hell, if you really aren't sure of yourself, there's plenty of Tempers willing to compile your loader using your OTP
It is not master race because by using arm9hax you lose your ability to boot into sysnand without an SDcard. You give up crucial functionality for 10 seconds of boot time.
Implying you would use your 3DS without your SD card.
 
Last edited by The Catboy,
Looks like most bricks have come from user-error. So far I've installed A9LH on 3 consoles with no problem (other than sleep deprivation from the long and tedious process:blink:). When sysUpdater was first used, weren't there reports of it crashing mid-installation? I can't verify those claims but random crashing mid-installation or mid-NAND restoring is my biggest fear when doing these things.
Yeah the original sysupdater used for downgrading did that.
 
  • Like
Reactions: NekoMichi
auReinand + arm9loaderhax on an O3ds Xl it takes about 8-9 secs to boot
cakesCFW - arm9loaderhax on an O3ds Xl it takes about 7-8 secs to boot

salu2
 
i know but do dgrade to a fw on n3ds that doesnt exist for it...... i dont know

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

it is possible with emunand ??
 
Actually if you think about it, time-saving isn't much of an advantage given how long the preparation takes. Say for example it takes 2 hours for someone to set up A9LH purely to get faster boot times and they save 10 seconds per boot. It took 7200 seconds to set up, so the time spent is only offset after 720 boots. Assuming the person only boots once per day, then it would take 2 years to "save" the time spent on setting up. But these are just random calculations I did out of boredom.

The main advantages of A9LH come with the better stability, 100% boot success rate (eliminating the need for re-boots), safer recovery options in case of a brick, and blocking FIRM0/1 updates for future-proofing.
 

Site & Scene News

Popular threads in this forum