Homebrew [Help] dsi ware downgrade

[buckshot6]

Not an expert on otp less downgrades.
I have not tried to do otp less downgrade.
I saw more that 2 post that said they have bricks.
Not a lot of good guides out there that tell every step.

I had a black screen of death and recovered also did the dsi down grade.
just saying what I had to fix my problem.

 

[stefanoteco]

What version of SafeA9LHInstaller did you use?

2.5.1, the most recent from github (used the homebrew version with ninjhax)

 

[PrometheusG.]

https://github.com/AuroraWright/SafeA9LHInstaller/releases/tag/v2.6.1

this is the latest release of safeA9LHInstaller

 

[stefanoteco]

... shit

but i'm pretty sure Plailect's guide redirects to the 2.5.1 version. Maybe this fucked up the process?

 

[PrometheusG.]

No,I don't think so..

 

[el_gonz87]

Yeah strange I used 2.5.1 myself without any issues like I said after black screen then reset console after 20 secs then success.

I always redownload the files twice and use a file compare program (beyond compare) to make sure I got the right installer/a9lh/input v3/etc...

When you tried to load from homebrew did it go staring to black screen? Did you press select?

Iys very strange for safeA9lhinstaller to fail like this.

Maybe like @buckshot6 said something got corrupted with your home folder. Try a fresh SD card formatted to fat32 with 32kb clusters and see if it boots (may take 30-40 secs).

Did you make a backup of the Nintendo 3DS folder from part 1?

 

[stefanoteco]

It doesn't boot even withou the card, but i'll try it.

I got the installer screen and pressed select. I had others devices with glitched screen but even then I was able to ARM9Hax them but in this case I really have no idea

 

[el_gonz87]

Sorry to hear this, unfortunately yes this means you got a brick if you pressed select and it tried to install A9LH and now it boots without SD. Both my black screens where just trying to launch the program.

This bug was found on 2.5.1 but no issues were reported for it:

• The previous A9LH key2 was wrong and skipped the first 16 bytes of stage1. While this hasn't caused issues to date, the key has been replaced with a new one found again by @gemarcano. The key will also be updated on the fly as soon as you update the A9LH payloads.

At least you have a NAND backup, you can get it hardmodded and recover the device. Best of luck!

 

[stefanoteco]

well, at least I tried heheh.