Homebrew Is there something wrong with A9LH?
- Thread starter tubbyman2000
- Start date
- Views 4,560
- Replies 70
Because they think they can't. They're afraid their 3DS will auto-brick as soon as they think about installing a9lh on it.
People are understandably weary about downgrading down to 2.1 then upgrading again, especially on the N3DS where you have to 'unbrick' the firmware. It was put off for quite a while.
Also, we've only recently gotten user-friendly guides. The process remains unavoidably long and complicated, however,
Also, we've only recently gotten user-friendly guides. The process remains unavoidably long and complicated, however,
Seeing as you have to dedicate 4 hours of your time and make 10 gigabytes of NAND backups for a 256b file, and downgrade your sysNAND to 2.1 just to get it, I see why people would be deterred. Doing any step wrong can make you lost data or hardbrick,
It's great though, but most undedicated people would rather do Menuhax and call it a day.
It's great though, but most undedicated people would rather do Menuhax and call it a day.
Last edited by Halvorsen,
4 hours at least. plus even these "user friendly" guides are quite confusing.
For me, laziness. Autobooting into EmuNAND with HomeMenuHax works just fine for me so I don't really have much desire to bother with setting up a9lh.
I was going to post something about the guides being numerous and confusing but I thought people would get annoyed at me for it.
Similar to how there are 101 different versions of sysUpdater.
Last edited by Halvorsen,
Yep, 4 hours. And also, just earlier, I experienced black screen upon booting a9lh region changed emunand twice, weird. The only thing I did is try to update a copy of Triforce heroes since It prompts of an update. It failed, then I reboot, next thing that happens it doesnt boot. Works fine now though. I just find it weird.
The time it takes for the whole process could be another factor, I tried it with my 2ds to test A9LH and the process takes a very long time with all the nand backups and everything, which took about 2 nights to do. So I'm putting off doing it to my main 3ds for a while until I have more time to just do it all at once.
Last edited by CitizenSnips,
I don't know if I rushed or something, but pretty sure I only took 2 hours for 2 3ds. Including the backup and restoring. Maybe because I did them simultaneously, and I read it like 10 times over and over again before actually doing it.
I gotta say, it is kinda scary playing around with NAND, as I don't have a hardmod. I guess the chances of getting bricks scares other people on doing it. But the the current methods are safer than before, maybe they just didn't know that's the case.
I gotta say, it is kinda scary playing around with NAND, as I don't have a hardmod. I guess the chances of getting bricks scares other people on doing it. But the the current methods are safer than before, maybe they just didn't know that's the case.
It took me 4 hours since I need to validate all the TMD mismatchs before proceeding and I start from the very first part. But then again, If you already have CFW installed, then 2 hours is possible.
Did you know: Turning on your 3DS has a 0.0000000000000000000000000000000000000000000000000000000000000000000000000001% chance of making it brick?
It's best to just never touch it again
Seriously though, nothing is wrong with A9LH as long as you do everything correctly.
It's almost ALWAYS user error if they brick.
Last edited by Margen67,
I tried the process with the Plailect guide. I tried the thing about downgrading EmuNAND to 2.1, and it always fails to verify, and always tells me it was bricked! Even the troubleshooting guide didn't help me.
I re-downloaded the 2.1 update files around 10 times, and followed the process exactly as Plailect described. The verification fails every single time. I downgraded EmuNAND to 2.1 around 25 times, and it was always the same.
Also, tried with 7 different micro SD with different sizes and different models (and companies). 4 of them were new.
So, it just doesn't work for me. Oh, and it´s a O3DS, not an N3DS, I know 2.1 downgrade is always bricked on N3DS.
I re-downloaded the 2.1 update files around 10 times, and followed the process exactly as Plailect described. The verification fails every single time. I downgraded EmuNAND to 2.1 around 25 times, and it was always the same.
Also, tried with 7 different micro SD with different sizes and different models (and companies). 4 of them were new.
So, it just doesn't work for me. Oh, and it´s a O3DS, not an N3DS, I know 2.1 downgrade is always bricked on N3DS.
Did you know: Turning on your 3DS has a 0.0000000000000000000000000000000000000000000000000000000000000000000000000001% chance of making it brick?
It's best to just never touch it again
Oh no! That's the same chance that a masterball will fail against a wild pokemon!
*turns off ds*
Never touching it again.
nope, didn't know that because it's absolute horseshit.Did you know: Turning on your 3DS has a 0.0000000000000000000000000000000000000000000000000000000000000000000000000001% chance of making it brick?
It's best to just never touch it again
Similar threads
-
-
-
-
@
Vetusomaru:
actually anime have also toned down fanservice a lot at the last 2 decades. when was the last time you saw nipples in anime that isnt hentai? -
-
-
@
Vetusomaru:
even at "uncensored" home releases they still show no nipples with few, rare exceptions
-
-
-
-
-
-
-
@
Vetusomaru:
even at seinen i am reading, the only one that shows nipples sometimes is Oversized Sextet
-
-
-
@
Vetusomaru:
i still havent read the manga. also surprisinly i like both the new and the old anime adaption.
-
-
-
@
Skelletonike:
That's one of the issues I have with ecchi stuff recently, it focuses too much on the sexual aspect, not the comedy effect. -
-
-
-
@
Skelletonike:
Rumiko Takahashi got so much fan email about the character that she brought her back in the manga, it was going to be completely different originally (with the alien of the week type).
-