Hacking Can I brick trying to update my al9h?
- Thread starter miss_nakano
- Start date
- Views 4,071
- Replies 45
Currently updating, please help me on this step:
8.Copy the contents of the arm9loaderhax zip to a9lh folder on your SD card
so which zip is that?I've downloaded all content of this page https://3ds.guide/updating-a9lh but there's no "arm9loaderhax zip".
Thanks!
8.Copy the contents of the arm9loaderhax zip to a9lh folder on your SD card
so which zip is that?I've downloaded all content of this page https://3ds.guide/updating-a9lh but there's no "arm9loaderhax zip".
Thanks!
After finishing all of the procedures, the 3ds can get to luma without Microsd inserted, but all my theme and games are gone..but this is normal right?does this mean I'm on v4 now?
Because your themes and games are stored on your SD card, but sdless is a v4(official), v3(unofficial) feature if I remembered correctly. So you should be good.
The only 100% brick protection available is a hardmod. Anything which writes to NAND has the potential to brick. Just make sure you make a valid NAND dump before doing anything NAND related. Then if you do get a brick which isn't software recoverable you can hardmod and restore.
I installed the newest version from https://3ds.guide/updating-a9lh, the data input also say v4..I think I installed the v4 one. So there used to be a v3 too with this sdless feature?It seems I already succeed updating it then. Thanks.
This is why I asked before updating it..It just seems possible to brick because it does something to the NAND, but thank god I already updated successfully. I supposed everyone else that want to update need to be careful and attentive with ALL the steps and procedure to prevent screwing the 3ds.
D
Deleted User
Guest
I just noticed this.The guide says to install version 3 during the process of installing a9lh for the first time but in the update section it has version 4.Why keep version 3 on the first time users install guide if its the unofficial release of sdless? I have version 3 basically because of that.Ill probably have to update too.
Last edited by ,
I gave up from updating my AL9H after seeing the warning message: "Couldn't verify stage1 and/or stage2 integrity! Continuing might be dangerous!" during the process.
I followed the 5 steps tutorial in the past and this new updating tutorial looks like to be targeted to people which used the new guide to hack their 3ds.
I followed the 5 steps tutorial in the past and this new updating tutorial looks like to be targeted to people which used the new guide to hack their 3ds.
If you check between both, you'll see that the files inside are the same (same hash) except on v4 there's no firm_100.bin(otpless file). That way, latest safe9installer won't try to use it.
Since the guide reverted to OTP version, there's no danger of it with safe9installer v2.0.3
D
Deleted User
Guest
So your saying because the guide requires the otp it has to use the version with the otpless file correct? incase someone decides to use it even though the guide doesn't recommend it anymore.So updating to 4 is just removing the otpless file then to prevent unknown bricks.
- Joined
- Feb 10, 2009
- Messages
- 5,484
- Trophies
- 2
- Location
- Sacramento, California
- Website
- lazerlight.x10.mx
- XP
- 5,482
- Country
Someone made a thread that gave some details about versions, but anyways, it's recommended to update to the latest one of A9LH anyways.
What does this do for me? Because so far my A9LH functions properly and has no issues. I really don't want to do anything if I don't need to. Telling me it's recommended isn't an applicable answer here. And my console has a capture card form katsukity, so I'd like to minimize un-required chances of brick.
What it does for everyone else: booting without SD, unified screeninit/noscreeninit (call the boot file arm9loaderhax_si.bin/arm9loaderhax.bin), some internal changes especially compared to v1
Fine, you're not required to upgrade; but I hope you didn't install any official updates to sysnand before you got cfw, because those bring a comparable brick risk (by rewriting the kernel partitions) with little, negative, or zero gain
What it does for everyone else: booting without SD, unified screeninit/noscreeninit (call the boot file arm9loaderhax_si.bin/arm9loaderhax.bin), some internal changes especially compared to v1
Fine, you're not required to upgrade; but I hope you didn't install any official updates to sysnand before you got cfw, because those bring a comparable brick risk (by rewriting the kernel partitions) with little, negative, or zero gain
Your explanation on "official updates" is vague, or rather non existent. All firmwares prior to A9LH were just "official updates". So please be more specific before you pop off. My N3DS had 9.6, downgraded to 9.2, installed A9LH, and updated to whatever happened to be the newest at the time. Then system transfer was done to that console from my old one. However all that transferred was NNID. I lost everything else and had to manually download everything again. Everything downloaded to this 3DS was done after A9LH. I don't care about booting without SD, I'm pretty sure my A9LH already calls on the arm9loaderhax.bin file, and "some internal changes" is as vague as Nintendo saying "system stability". My A9LH is about a week maybe from before OTPless came out.
Last edited by YourHero,
As clear as it can be.
To boot arm9loaderhax.bin, your console MUST have a valid NCSD header, secret sector, and firmware partitions.
The first one is never modified in normal operation; the firmware partitions are rewritten (with an obvious potential risk, if the power fails at the wrong time or stuff) whenever the unmodified* operating system is updated, or a9lh is updated
* CFW used with a9lh blocks the rewriting of the firmware partitions, as installing a clean kernel to them would remove a9lh on o3ds, and brick a n3ds (because the secret sector used with a9lh is incompatible with the original one)
Similar threads
-
-
-
@
SylverReZ:
I haven't been gaming for such a long time. Been mostly busy with sleep, hardware tinkering and checking GBAtemp frequently. -
-
@
Maximumbeans:
It's going alright thanks+1 I know what you mean with gaming time. It's precious where I can get it these days. -
@
Maximumbeans:
I think that's why I focus on just enjoying single player experiences that aren't too competitive
-
-
-
-
-
@
SylverReZ:
@Maximumbeans, Indeed. I've been working on getting this Infecutus chip to work on my PS2. But after soldering, I realised that a plastic piece was missing from the power ribbon cable to the power and eject buttons.
-
@
SylverReZ:
Now I could go with soldering the contacts from the cable to the connector on the mobo, but doesn't sound like a good permanent solution.
-
@
Maximumbeans:
Man, that's beyond my brain I'm no good with hardware for now. I'd like to get into hardmods in future though
-
@
SylverReZ:
@Maximumbeans, Maybe start practice soldering. Get a cheap-ass soldering iron and follow some good YouTube tutorials.+1
-
@
SylverReZ:
Least my experience has gotten better than over a decade ago. My iron would constantly bump into components and break them.
-
@
Maximumbeans:
Sounds good. I actually did soldering but like 16 years ago for school so uuuuh probably rusty haha
-
@
SylverReZ:
@Maximumbeans, Same here. I did soldering at school from a teacher who I honestly liked since he had plenty of good electronics experience.+1
-
-
-
-
-
@
SylverReZ:
It was like all clear and fancy. Tbf I'm not too experienced with chess, but would like to learn someday.
-
-
-