Hacking DO NOT TRY TO CHANGE FROM SCREENINIT TO NOSCREENINIT!!!!!

[MrBananaMan]

problem solver thanks to @zoogie , somehow when i transfered the payload_stage1 and payload_stage2 bins from the noscreeninit folder to the sd card, only the stage1 made it there. as i cant go back in time, i dont know if this was user error or a failure of mac finder (you can make your own assumptions). moral of the story, triple check the files you ahve on the sd card are the right ones.

Now if you excuse me, i'm going to learn to hardmod

 

[zoogie]

The no screen init builds were probably new while the other tools, files, etc were old. That's a recipe for disaster.
Moral of Story: always make sure EVERYTHING is up-to-date with an a9lh update.

 

[MrBananaMan]

The no screen init builds were probably new while the other tools, files, etc were old. That's a recipe for disaster.
Moral of Story: always make sure EVERYTHING is up-to-date with an a9lh update.

the screeninit and the noscreeninit were both uploaded 17 days ago, and this was with the most recent version of everything

 

[CrispyYoshi]

A9LH is safe, but only if you never touch A9LH itself. If you do, make absolutely sure you know what you are doing before you do it: You likely bricked because you had outdated/incompatible payloads that didn't like the other files they were/weren't combined with.

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

the screeninit and the noscreeninit were both uploaded 17 days ago, and this was with the most recent version of everything

Most recent stable, or most recent commit?

 

[MrBananaMan]

A9LH is safe, but only if you never touch A9LH itself. If you do, make absolutely sure you know what you are doing before you do it: You likely bricked because you had outdated/incompatible payloads that didn't like the other files they were/weren't combined with.

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


Most recent stable, or most recent push?

most recent stable, i got everything from the releases tab on github

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

These were the same versions i used to install a9lh 2 days ago

 

[CrispyYoshi]

These were the same versions i used to install a9lh 2 days ago

Were you also using the most recent SafeA9LHInstaller? Was your otp.bin in the folder?

 

[MrBananaMan]

Were you also using the most recent SafeA9LHInstaller? Was your otp.bin in the folder?

Yes and yes

 

[CrispyYoshi]

Yes and yes

If your data_input contents are also in the folder, there are still three possibilities:
- The files corrupted in the download and/or didn't transfer to the 3ds properly
- The 3ds is defective in terms of hardware
- Potential unstable bug in the current "stable" software

Unfortunately I can't help with the last two, but it might be worth md5-hash checking the files in /a9lh/ to ensure they were fine when you attempted the update.

 

[MrBananaMan]

If your data_input contents are also in the folder, there are still three possibilities:
- The files corrupted in the download and/or didn't transfer to the 3ds properly
- The 3ds is defective in terms of hardware
- Potential unstable bug in the current "stable" software

Unfortunately I can't help with the last two, but it might be worth md5-hash checking the files in /a9lh/ to ensure they were fine when you attempted the update.

do you know where to find the hashes so i can compare them

 

[CrispyYoshi]

do you know where to find the hashes so i can compare them

I can't say I know a dedicated place to find them, but you can try re-downloading the files to compare them with, in case they might've corrupted the last time you DL'd them.

 

[DjoeN]

No problem here!

Anyway latest arm9loaderhax from @Aurora Wright has screeninit and no screeninit merged, there are no seperate versions anymore!
So you really didn't use the latest and greatest
(Be sure to update your firm0.bin (995.328 bytes), don't use previous firm0.bin (991.232 bytes))

then use latest SafeA9LHInstaller to install and if you leave everything untouched you use and boot the no screen init version
IF you want screeninit, rename arm9loaderhax.bin to arm9loaderhax_si.bin and you boot into the screen init version!

Just learned this the hard way, I tried to change my a9lh from screeninit to noscreeninit by copying the files in the noscreeninit folder to the a9lh folder on SD, copied the arm9loaderhax.bin from safea9lhupdater to the root, and installed it like normal. However, when i turned on my 3ds again, it was bricked!!! Nothing in the troubleshooting guide helped, and irc agreed i bricked. Nobody knew what happened so that i bricked, because i did everything exactly the way I was told to. Word of caution, if you are happy with your 3ds running don't let that light flash at the beginning get you, because it doesn't end well!

You sure didn't read and follow everything regarding latest arm9loaderhax from @Aurora Wright

 

[MrBananaMan]

No problem here!

Anyway latest arm9loaderhax from @Aurora Wright has screeninit and no screeninit merged, there are no seperate versions anymore!
So you really didn't use the latest and greatest
(Be sure to update your firm0 (995.328 bytes), don't use previous firm0 (991.232 bytes))

then use latest SafeA9LHInstaller to install and if you leave everything untouched you use and boot the no screen init version
IF you want screeninit, rename arm9loaderhax.bin to arm9loaderhax_si.bin and you boot into the screen init version!



You sure didn't read and follow everything regarding latest arm9loaderhax from @Aurora Wright

I used the latest release on github, if the changes are really the difference between bricking and not then they should really get made the release version. I used everything latest from github release tabs for all programs, they are what i used to install the hax 3 days ago. Obviously you haven't read what i said because if you did you would understand I can't boot into any payloads, including decrypt9wip, emunand9, hourglass9, and anything i set as arm9loaderhax.bin

 

[CrispyYoshi]

No problem here!

Anyway latest arm9loaderhax from @Aurora Wright has screeninit and no screeninit merged, there are no seperate versions anymore!
So you really didn't use the latest and greatest
(Be sure to update your firm0.bin (995.328 bytes), don't use previous firm0.bin (991.232 bytes))

then use latest SafeA9LHInstaller to install and if you leave everything untouched you use and boot the no screen init version
IF you want screeninit, rename arm9loaderhax.bin to arm9loaderhax_si.bin and you boot into the screen init version!



You sure didn't read and follow everything regarding latest arm9loaderhax from @Aurora Wright

Damn, of all the things I forgot to ask, it was the FIRM itself. Thanks for posting this, I wonder if that was the issue?

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

I used the latest release on github, if the changes are really the difference between bricking and not then they should really get made the release version. I used everything latest from github release tabs for all programs, they are what i used to install the hax 3 days ago. Obviously you haven't read what i said because if you did you would understand I can't boot into any payloads, including decrypt9wip, emunand9, hourglass9, and anything i set as arm9loaderhax.bin

Can you right-click your FIRM0.bin and tell us the exact size of that file, in bytes? It should have come from data_input_v2.zip

 

[MrBananaMan]

My firm is 995 bytes so its the most recent one, not the problem

 

[DjoeN]

Oh, i did read everything you wrote
But like said, you obviuously did something wrong, as i have used latest arm9loaderhax with sagea9lhinstaller on more then 7 systems and no brick!

 

[MrBananaMan]

Oh, i did read everything you wrote
But like said, you obviuously did something wrong, as i have used latest arm9loaderhax with sagea9lhinstaller on more then 7 systems and no brick!

were you using the one from the github releases tab? or were you compiling it yourself/getting it from someone who compiled

 

[DjoeN]

were you using the one from the github releases tab? or were you compiling it yourself/getting it from someone who compiled

Screenshot of what should be:

build myself 16 days ago when screeninit and no screeninit where merged

Top: Root of SD
Bottom: inside a9lh folder

 

[MrBananaMan]

Screenshot of what should be:

build myself 16 days ago when screeninit and no screeninit where merged

Top: Root of SD
Bottom: inside a9lh folder

We are using different versions, i grabbed the one from the release tab taht was updated 17 days ago, before the merge, if you had read you would already know this

 

[CrispyYoshi]

We are using different versions, i grabbed the one from the release tab taht was updated 17 days ago, before the merge, if you had read you would already know this

Wait, what happened to "using the latest version"?

 

[DjoeN]

Doesn't matter, i always update as soon as a new gitupdate is out to test (first my test system, then my 5 other systems (mix of O3DS and N3DS)
Never had a problem (also no problem with the update from 17 days ago), so obviously you did something wrong!