Homebrew is loader9hax worth it?

[deinonychus71]

Emunand is completely useless if you have A9LH.

The day Nintendo release a new update that replaces the firmware, everyone upgrading their sysNAND will get screwed if they didnt double check here first.
We are not sure 100% that it's safe... As long as a9lh can be removed it's not risk-free.

So A9LH worth it? Yes, definitely.
Removing Emunand completely? Yes *IF* you are carefull when upgrading.

 

[Supster131]

The day Nintendo release a new update that replaces the firmware, everyone upgrading their sysNAND will get screwed if they didnt double check here first.
We are not sure a 100% that it's safe... As long as a9lh can be removed it's not risk-free.

Not really. It'll be the same result as updating your emuNAND.

Sure, it won't work for a while, but once the CFW devs support it, it'll work again.

 

[deinonychus71]

From AuReiNand first thread:

when you load sysNAND all FIRMs are automatically patched to prevent overwriting A9LH.

Not really. It'll be the same result as updating your emuNAND.
Sure, it won't work for a while, but once the CFW devs support it, it'll work again.

From my understanding, if a new firmware comes with an official update and is not patched (because reason), it may override a9lh, which means no more entry point on last firmware = screwed.
I don't know enough about it to be entirely sure that it could happen, but Id rather be safe than sorry, at least while this hack is still very new.

 

[sweis12]

From AuReiNand first thread:




From my understanding, if a new firmware comes with an official update and is not patched (because reason), it may override a9lh, which means no more entry point on last firmware = screwed.
I don't know enough about it to be entirely sure that it could happen, but Id rather be safe than sorry, at least while this hack is still very new.

Thats why you just use emunand FFS. :/

 

[tvall]

From AuReiNand first thread:




From my understanding, if a new firmware comes with an official update and is not patched (because reason), it may override a9lh, which means no more entry point on last firmware = screwed.
I don't know enough about it to be entirely sure that it could happen, but Id rather be safe than sorry, at least while this hack is still very new.

it patches the firmware it boots off the sdcard. if nintendo releases an update that changes the firm, it will not be flashed to the firm partitions. which could mean your system isnt able to load the system until you update the copy on the sdcard, depending on how big of a change it is. but chances of completely bricking from an update is almost not there. worst case you just use decrypt9 to flash a backup you made before the update. unless nintendo has a trick hidden to magically update those partitions that we havent yet written a patch for.

if i understand correct

 

[deinonychus71]

it patches the firmware it boots off the sdcard. if nintendo releases an update that changes the firm, it will not be flashed to the firm partitions. which could mean your system isnt able to load the system until you update the copy on the sdcard, depending on how big of a change it is. but chances of completely bricking from an update is almost not there. worst case you just use decrypt9 to flash a backup you made before the update. unless nintendo has a trick hidden to magically update those partitions that we havent yet written a patch for.
if i understand correct

Yes, or unless they modify their update system to flash the firmware before rebooting. Or unless someone tries out another, new CFW that doesnt patch the firm correctly and erase a9hl... Or I don't know...
I am not saying it will happen, just that I feel that a warning should be given to be somewhat cautious when upgrading with system settings.

 

[Supster131]

From AuReiNand first thread:




From my understanding, if a new firmware comes with an official update and is not patched (because reason), it may override a9lh, which means no more entry point on last firmware = screwed.
I don't know enough about it to be entirely sure that it could happen, but Id rather be safe than sorry, at least while this hack is still very new.

Yeah, exactly. FIRM0/FIRM1 is blocked by AuReiNAND, meaning it can't be touched by an update at all. Even if a firmware update were to brick our sysNANDs, A9LH would not be deleted. It would still be there. Which hey, what can we do with that? Restore a NAND backup, the same way you would do with emuNAND. No difference.

We'd just have to wait until CFW devs get it to work on the latest NATIVE_FIRM.

 

[Aahz]

Honestly, the people who are crazy enough to risk bricking their systems in the process of acquiring their OTP and setting-up A9LH are exactly the kind of people which need that extra level of brick protection and future-proofing.

 

[DjoeN]

Honestly, the people who where crazy enough to risk there system to get OTP.bin all have contributed in some way to a safer guide in aquiring it
They all did it, because somebody has to try it anyway (or where fed up with boottimes and yellow screens) so we can learn and provide safer/better ways to get it. All people who wait can only benefit from it

For now i think the guide is as safe as it can gets and people are still working to get it even simpler and safer.

I have 1 system (O3DSXL) thats hardmodded and uses sysnand 10.6 to boot in with AuReiNand in combination with emunand 9.2
I have ctrbootmanager9 on it so i can try different cfw's with A9LH support (Cakes, ReiNand) or boot straight into Decryp9 A9LH in case something goes wrong. My 2DS boots straight in A9LH AuReiNand Emunand 10.6 (sysnand is on 9.2) and my other systems i keep on MenuHax for now, but i got the OTP.bin already.

It really doesn't hurt to get your OTP.bin so you are ready for the future once OTP.bin obtained you can continue with your system setup (MenuHax) or setup the A9LH. all your choice.

 

[Viri]

It unnecessary for most people as there are few "real" advantages.

Lots of people talk about faster boot times and updating sysnand which are ok but the true gems are the recovery mode and the 3D fix for N3DS. With menuhax even after closing the screen the 3D never worked that well, the difference is night and day.

If you're happy with what you have then there is no need to change it.

EDIT: One advantage for the older folks is this makes a completely child friendly system. There is nothing my kids can do to it that can't be fixed in 30 minutes or less. I don't have to worry about menuhax failing and booting into sysnand only to be updated and destroying everything.

This right here is what is making me consider it. I just downgraded 2 o3DS XLs to 9.2 for my niece and nephew. I installed Themehax. I just know when I install emunand, rxtools and all that stuff. They will end up changing the theme, and the emunand won't boot anymore. I wish there was a way to parental control the damn themes.

 

[Just Passing By]

Honestly, the people who where crazy enough to risk there system to get OTP.bin all have contributed in some way to a safer guide in aquiring it
They all did it, because somebody has to try it anyway (or where fed up with boottimes and yellow screens) so we can learn and provide safer/better ways to get it. All people who wait can only benefit from it

For now i think the guide is as safe as it can gets and people are still working to get it even simpler and safer.

I have 1 system (O3DSXL) thats hardmodded and uses sysnand 10.6 to boot in with AuReiNand in combination with emunand 9.2
I have ctrbootmanager9 on it so i can try different cfw's with A9LH support (Cakes, ReiNand) or boot straight into Decryp9 A9LH in case something goes wrong. My 2DS boots straight in A9LH AuReiNand Emunand 10.6 (sysnand is on 9.2) and my other systems i keep on MenuHax for now, but i got the OTP.bin already.

It really doesn't hurt to get your OTP.bin so you are ready for the future once OTP.bin obtained you can continue with your system setup (MenuHax) or setup the A9LH. all your choice.

I completely agree. I remember back to that one day when revision 2 came out for the OTP Guide and it was complete chaos. There were bricks left and right and it was bad. I think the main reason was because of a missing step or file for N3DS and it caused like all of them to brick. Without those people reporting back, who knows how many more people would've bricked. They may have saved 100+ N3DS owners from bricks.

 

[cooroxd]

I'd personally do it only if someone makes a youtube tutorial

 

[Urbanshadow]

System CTRNAND restoration is a big pro for A9LH. You can brick the system CTRNAND and recover it with a backup without a hard mod. And that's really neat. With the FIRM partition protection provided by the "CFW" (Because its not a modified firmware loader, but an original firmware patching and loader system) there's almost nothing you can fear to do without hardmod, even directly on sysnand.

 

[sj33]

As long as we still have to keep some kind of EmuNAND on our cards as a failsafe and to use Decrypt9, then I'm not sure I understand the purpose of swapping the NANDs bar making VC installs easier.

I'll swap my NAND when things have matured and the blocks to writing to FIRM have stood the test of time.

 

[democracy]

Every year thousands of menuhax power buttons are abused daily...
Put an end to world power button abuse by supporting ARM9.

 

[cherryduck]

It takes a long time and it's complicated to set up but I love A9LH.

With menuhax the system would occasionally not boot, and sometimes loading homebrew would also refuse to boot. I found myself holding down the power button to force the system off, then trying again, too many times, it was annoying and time consuming, even using lesshax. Further to this, I had to go a complex route to load MiniPasta, hold down L to make sure it booted into patched sysnand, inject FBI, install my GBA cias, reboot to emuNAND, install my GBA cias there, and then finally be able to play them...

With A9LH and sysNAND I boot up, it works every time, quickly, and I can straight away install my GBA cias and play them. Homebrew seems a lot more stable too, I haven't had anything freeze or refuse to boot yet. I can boot straight to Decrypt9 if I choose rather than loading sysNAND by holding L on boot, launching Cubic Ninja, then selecting Decrypt9.

Although the initial set up is complex and time consuming, once it's up and running, there's a lot less messing around, a lot more stability, and a lot more convenience.

I also like the idea of having a truly hacked system as opposed to chaining exploits to boot emuNAND. It just gives me a little geeky thrill to know my 3DS itself is hacked and not just some aspect of it.

 

[TimX24968B]

I don't have to worry about menuhax failing and booting into sysnand only to be updated and destroying everything.

thats why I didn't put a theme on emunand

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

Er... Actually, A9LH worth it

• It makes emuNAND useless (though you can have it in A9LH);
• Theoretically you can have CFW in any system version till now (just there's almost no one working on that) with 100% boot rate and super fast;
• If using emuNAND you can run it faster;
• It can improve some homebrews there insn't 100% (like GBA emulator and other stuff);
• It creates a opportunity to create new kinds of homebrews (though no one made something totally new yet)
• Probably there more stuff that I forget or I don't know

So... it worth whatever you're a dev or a end-user.

It seems like there isn't a full definition on getting it up and running and working (at least from that thread and what I've seen elsewhere), however, and how to do specific things with it. I'm going to wait until its fully developed and there are more tutorials to do specific things with it.

 

[Deleted User]

It unnecessary for most people as there are few "real" advantages.

Lots of people talk about faster boot times and updating sysnand which are ok but the true gems are the recovery mode and the 3D fix for N3DS. With menuhax even after closing the screen the 3D never worked that well, the difference is night and day.

If you're happy with what you have then there is no need to change it.

EDIT: One advantage for the older folks is this makes a completely child friendly system. There is nothing my kids can do to it that can't be fixed in 30 minutes or less. I don't have to worry about menuhax failing and booting into sysnand only to be updated and destroying everything.

I like that last edit point.... But... It's not actually the A9LH that fixes the 3D but actually AuReiNand. I am using AuReiNand MenuHax and I don't have to close the system at all to get 3D

 

[rockbmi]

For the 100% boot rate and the very fast boot, i thought it was worth it. No issues downgrading and getting the OTP file on a New 3DS XL. Everything works great and i now know that any future stuff coming out i can easily use without any issue.

 

[Bu2d85]

I like that last edit point.... But... It's not actually the A9LH that fixes the 3D but actually AuReiNand. I am using AuReiNand MenuHax and I don't have to close the system at all to get 3D

It was A9LH first before the screen init. After screen init became a thing AuReiNand was updated to turn the screen off before loading. If you still have an older version of A9LH you do not need the latest build of AuReiNand for the 3D fix.