Hacking Just updated to A9Lh. What are some do's and don'ts?

proflayton123 · Sep 16, 2016

Posghetti said:
I'm going to assume it was from when there was something wrong with the newest luma (at that time) (non-dev/dev at that time caused 3DS' to boot with firm errors or something like that, can't really remember what the error was but there was a bunch of threads about it)

Oh? I see.

I was unaware of this~

Halvorsen · Sep 16, 2016

Deonot1 said:
DO NOT USE STAR UPDATER, it Bricked MY system, I had to Use a SdCard Backup Not Just SysNand, SDCARD back up

StarUpdater did NOT brick your system..

astronautlevel · Sep 16, 2016

Deonot1 said:
DO NOT USE STAR UPDATER, it Bricked MY system, I had to Use a SdCard Backup Not Just SysNand, SDCARD back up

StarUpdater does a lot of things, but it doesn't brick your system T_T

DeoNaught · Sep 17, 2016

astronautlevel said:
StarUpdater does a lot of things, but it doesn't brick your system T_T

Well it bricked mine.

astronautlevel · Sep 17, 2016

Deonot1 said:
Well it bricked mine.

No, it didn't. You said you restored an SD card backup, so it was probably just a bad arm 9 loader hax.bin

DeoNaught · Sep 17, 2016

astronautlevel said:
No, it didn't. You said you restored an SD card backup, so it was probably just a bad arm 9 loader hax.bin

it Corrupted My Sdcard or something. I updated through Star Updater, I rebooted and BAM Nothing, Black screen.
Tried Decrypt9 Nothing, Freaked Out, checked Sdcard All my Payloads WERE GONE!! Put a Sdcard Backup with SysNand Backup
Booted Into Decrypt9 Flashed a backup... Saved By the Backup. I did this Twice to Make sure, Same thing Second time.

Rfire · Sep 17, 2016

A do is to perform regular NAND backups.

Not just before system updates either.

There is a phenomena known as a single event upset (SEO) where energy from a star that went supernova hundreds of thousands of years ago sends high energy photons into our atmosphere. When these photons collide with electrical components they can cause erratic behavior, specifically when it comes into contact with flash memory it can potentially alter bits. Though such a thing is rare it is an example of why having recent NAND backups is useful.

But at the very least, make a backup before altering the NAND through things like home menu mods, updating firmware, etc. Also verify the NAND backup after Decrypt9 backs it up to ensure the SHA hash matches. Then copy it to your computer (optionally keep it on the SD card for convenience but as long as you have a copy somewhere it's not necessary).

DeoNaught · Sep 17, 2016

Rfire said:
There is a phenomena known as a single event upset (SEO) where energy from a star that went supernova hundreds of thousands of years ago sends high energy photons into our atmosphere. When these photons collide with electrical components they can cause erratic behavior, specifically when it comes into contact with flash memory it can potentially alter bits. Though such a thing is rare it is an example of why having recent NAND backups is useful.

I tried it twice.

astronautlevel · Sep 17, 2016

Then your SD card might be bad.

xJoelituh · Sep 17, 2016

osm70 said:
Few things to keep in mind.

A9LH replaced your "bootloader". Your 3DS no longer boots from NAND, but from the SD card. It starts the arm9loaderhax.bin file, which is Luma in this case. Luma then patches the firmware and runs it from the Nand.

That means, your 3DS won't boot if you don't have that file. Just try removing the SD card and powering on. It will just shutdown right away.

That's actually a good thing, though. If you manage to brick, you can replace that file with something like Hourglass9, boot into it and restore your Nand backup.

You can make your 3DS load without SD card(and I recommend it because this may help you)

https://gbatemp.net/threads/a9lh-can-now-boot-without-sd-card.432593/

osm70 · Sep 17, 2016

xJoelituh said:
You can make your 3DS load without SD card(and I recommend it because this may help you)

https://gbatemp.net/threads/a9lh-can-now-boot-without-sd-card.432593/

Well, I was talking about what the OP has.

cravas · Sep 17, 2016

Deonot1 said:
it Corrupted My Sdcard or something. I updated through Star Updater, I rebooted and BAM Nothing, Black screen.
Tried Decrypt9 Nothing, Freaked Out, checked Sdcard All my Payloads WERE GONE!! Put a Sdcard Backup with SysNand Backup
Booted Into Decrypt9 Flashed a backup... Saved By the Backup. I did this Twice to Make sure, Same thing Second time.

It seem you really have no idea of what a BRICK is:

A BRICK is when the only way to restore it is by altering anything diferent from what it was created for in the first place.
What happened to you was only a damaged system at software level that is perfectly recoverable by putting files back in.
It's the same you can do with a PC (for eg.) and an Administrator account: delete your registry and your OS will die.

For you to simulate a "brick" (as you have put it) on A9LH (NOT SD less forks), all you have to do is delete the arm9loaderhax.bin. (or boot it without SD)
But the recovery is as easy as to put it back and the console will be as it was.

But for a brick to be a BRICK, the only way to recover it would be to either Hardmod it or replace some of the Hardware.

Picture this: you downgrade a N3DS to 2.1 (which was never meant to work with that FW) and you close the lid to enter "sleep mode". It will do something to the MCU controller that will make it permanently damaged. (BRICKED)
No SysNAND restore (even with a hardmod flash) will save your console.
Now the only way to recover this is by swapping the damaged board with a new one.

Another Picture: You make a permanent hardmod with microUSB or miniUSB port and you connect it directly to a USB source (either a charger or USB port on PC).
Your NAND chip will fry because of the 5V injection. Guess what; BRICK.
Once again, only solution to recover will be changing hardware (either the NAND chip or the Mainboard itself).

Yet another Picture: You launch Decrypt9 (Hourglass9, Emunand9, whatever) and you restore a NAND from another console. You'll brick because the only way to restoring will be through hardmod.
If you were able to launch Decrypt9 again (that you can't), then it wouldn't be a brick since you're able to do it via software without the need of altering anything.

There are lots of situations but just wanted to give you a few pointers.
Hope it helps.

GilgameshArcher · Sep 17, 2016

Do lots of backups, NANDs, SD and game SAVs

Do not mess with the Home Menu.

dragonjud · Sep 17, 2016

Let me hijack the thread a bit, while still on topic: Since I just converted two of my n3ds, is it safe to update via game cartridge as well. Or are updates only safe via the System settings option?
Not much of an online player, so if I can update to something somewhat recent (instead of the very latest) that will be fine with me.

zeldaism · Sep 17, 2016

Whenever there is a 3ds update make sure to update your 3ds in recovery mode. Hold dpad up, L, R, A, and press the power button. You should be greeted with the system updater from the settings. This prevents a9lh from getting erased which could happen.

ADS3500 · Sep 17, 2016

zeldaism said:
Whenever there is a 3ds update make sure to update your 3ds in recovery mode. Hold dpad up, L, R, A, and press the power button. You should be greeted with the system updater from the settings. This prevents a9lh from getting erased which could happen.

A9lh can't get erased because most custom firmwares have firm protection, and updating with recovery mode isn't going to do anything differently from a normal update. Updating with Gateway will remove a9lh though because it doesn't have firm protection.

zeldaism · Sep 17, 2016

*snip*

DeoNaught · Sep 17, 2016

cravas said:
It seem you really have no idea of what a BRICK is:

A BRICK is when the only way to restore it is by altering anything diferent from what it was created for in the first place.
What happened to you was only a damaged system at software level that is perfectly recoverable by putting files back in.
It's the same you can do with a PC (for eg.) and an Administrator account: delete your registry and your OS will die.

For you to simulate a "brick" (as you have put it) on A9LH (NOT SD less forks), all you have to do is delete the arm9loaderhax.bin. (or boot it without SD)
But the recovery is as easy as to put it back and the console will be as it was.

But for a brick to be a BRICK, the only way to recover it would be to either Hardmod it or replace some of the Hardware.

Picture this: you downgrade a N3DS to 2.1 (which was never meant to work with that FW) and you close the lid to enter "sleep mode". It will do something to the MCU controller that will make it permanently damaged. (BRICKED)
No SysNAND restore (even with a hardmod flash) will save your console.
Now the only way to recover this is by swapping the damaged board with a new one.

Another Picture: You make a permanent hardmod with microUSB or miniUSB port and you connect it directly to a USB source (either a charger or USB port on PC).
Your NAND chip will fry because of the 5V injection. Guess what; BRICK.
Once again, only solution to recover will be changing hardware (either the NAND chip or the Mainboard itself).

Yet another Picture: You launch Decrypt9 (Hourglass9, Emunand9, whatever) and you restore a NAND from another console. You'll brick because the only way to restoring will be through hardmod.
If you were able to launch Decrypt9 again (that you can't), then it wouldn't be a brick since you're able to do it via software without the need of altering anything.

There are lots of situations but just wanted to give you a few pointers.
Hope it helps.

Well I knew it wasn't a Hard Brick, it was a Brick if you know what I mean, was Pretty sure it wasn't HardBrick
But it was corrupted.

ADS3500 · Sep 17, 2016

zeldaism said:
Aurora stated that Nintendo could release a update that can take away a9lh if they figure out how it works. Thats why she made the recovery mode just in case.

Recovery mode updates your system the exact same way a normal update does, so if Nintendo did release an update that removes a9lh, updating with recovery mode would still remove it from your system. It's also extremely unlikely that Nintendo will ever release an update that removes a9lh. It would require updating a part of the system that they've never updated before, and they tried that with the Wii before and it ended up bricking a bunch of systems that weren't modded, so the same thing would probably happen with the 3ds.

zeldaism · Sep 17, 2016

*snip*

Hacking Just updated to A9Lh. What are some do's and don'ts?

The Temp Loaf'

Well-Known Member

Well-Known Member

I'm here to steal memes and break dreams

Well-Known Member

I'm here to steal memes and break dreams

Well-Known Member

I'm here to steal memes and break dreams

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

I'm here to steal memes and break dreams

Well-Known Member

Well-Known Member

Similar threads

Popular threads in this forum