Hacking [POC] - Fixing OFW Blackscreens with Boot9strap

[MelonGx]

To be noticed that
- Unplugging Camera FFC makes the console work, but you cannot format it (otherwise it will be stuck at 3D Face Raider's confirmation or something more serious) or enter the System Settings with Luma3DS Exception Handler enabled.
- I don't know about Old3DS(XL) much, but I can confirm that a New3DS(XL) cannot be booted with either Upper Screen FFC or 3D FFC unplugged.
Anyway, congratulations to OP's console to be temporary fixed.

 

[Sumea]

just to ask:
What could be a way to fix O3DS that has this problem? My friend has one, and I meant to try to fix it but all things I thought it could be I did not know.

What do you mean with FFC MelonGx?
If possible I will fix my friend's O3DSXL

 

[MelonGx]

just to ask:
What could be a way to fix O3DS that has this problem? My friend has one, and I meant to try to fix it but all things I thought it could be I did not know.

What do you mean with FFC MelonGx?
If possible I will fix my friend's O3DSXL

FFC = Flexible Flat Cable.
O3DS should also have Upper Screen FFC + 3D FFC + Camera FFC.

 

[Sumea]

FFC = Flexible Flat Cable.
O3DS should also have Upper Screen FFC + 3D FFC + Camera FFC.

ah right. I might give that a try.

 

[Spore2]

I'm attempting to unbrick a 3DS from a failed a9lh install. Noob said that he was able to downgrade to 2.1, failed to install a9lh but proceeded to upgrade to 6.2 using a Bravely Default cart. The 3ds restarted to black screen from there.

When I got it, I installed a temp hardmod, dumped the nand, and patched b9s into the nand. B9S was successfully installed, luma works but somehow after 9.2 ctrnand transfer the 3ds still booted into black screen. Somehow, I could only get a 2.1 system to work on it. Any ideas why?

 

[leerz]

did you try to delete or rename the 3ds folder?

 

[Spore2]

did you try to delete or rename the 3ds folder?

Unit boots up to 2.1 but somehow when I go higher it goes black screen. Tried your advice and removed Nintendo folder when I booted 9.2 but still black screen. I hash checked the 2.1 ctrnand transfer the noob used to the one I use that works and they matched. Any other ideas on how to make this work?

 

[leerz]

0. does recovery work when you are getting black screen on 9.2?
-just my theory, 2x fw doesn't check if the camera is busted hence it boots? - that's why if you boot from 2.1, it works and not for 9.2
-if recovery does work, unplug the camera ribbon and your 9.2 should boot.
-------
1. Try a different 9.2 ctrnand (perhaps a eur or us one?)
2. really weird, doesn't hurt to format 2.1 and do the ctrnand to your 9.2 again
3. or go back to 6x, do a systemupdater to 9.2 with the 9.2 files (not ctrnand)
3.a (you might need to use old cfw files such as rx /cakes to get around since luma doesn't work with these old fws)

 

[Spore2]

0. does recovery work when you are getting black screen on 9.2?
-just my theory, 2x fw doesn't check if the camera is busted hence it boots? - that's why if you boot from 2.1, it works and not for 9.2
-if recovery does work, unplug the camera ribbon and your 9.2 should boot.
-------
1. Try a different 9.2 ctrnand (perhaps a eur or us one?)
2. really weird, doesn't hurt to format 2.1 and do the ctrnand to your 9.2 again
3. or go back to 6x, do a systemupdater to 9.2 with the 9.2 files (not ctrnand)
3.a (you might need to use old cfw files such as rx /cakes to get around since luma doesn't work with these old fws)

I was able to successfully unbrick the 3ds. Here's a recap:
1. Received a bricked regular O3ds after it was downgraded from 11.2 down to 2.1 then upgraded to 6.2 using a cart update.
2. Installed a temporary hardmod to dump the nand and patch it with b9s.
3. This gave me access to Luma cfw menu and Godmode9.
4. 2.1 CTR nand transfer successfully boots into home menu but 9.2 CTR nand transfer boots to blackscreen.
5. Asked for recommendations from this thread but none succeeded.
6. What worked was replacing the movable.sed from a working 3ds.

I still can't understand why the movable.sed worked on 2.1 but not on higher firmwares. I traced the hacking process that lead to the brick. The owner used this https://www.youtube.com/watch?v=hr3aGSaXrXg as a guide and also used the linked files.

 

[Spore2]

It's typhoon season over where I am. I'm free from work so I started work on a bricked 2ds that was handed to me over a year ago. The 2ds was on ofw and the original owner said that it booted to blackscreen after failing a few times to boot properly. I suspected that this was caused by the nand test point shorting because of an inherent flaw in the 2ds design. The LCD metal backplate is directly under the the test points without any insulation and can cause the terminals to short. I tested the screen with a working 2ds just to rule out the possibility of a dead lcd, lcd works. These are the steps I've taken to attempt repair.

1. Installed a temporary hardmod to dump nand and patch it with b9s.
2. So far, I've tried using firms from 6.0-10.2 o3ds but the unit is still black screen

Best case scenario so far is that the nand chip is damaged, maybe fried, and a ntrboothax will make it work. I'm just waiting for ntrboothax compatibility with R4 dual core then I can test that theory.

 

[leerz]

It's typhoon season over where I am. I'm free from work so I started work on a bricked 2ds that was handed to me over a year ago. The 2ds was on ofw and the original owner said that it booted to blackscreen after failing a few times to boot properly. I suspected that this was caused by the nand test point shorting because of an inherent flaw in the 2ds design. The LCD metal backplate is directly under the the test points without any insulation and can cause the terminals to short. I tested the screen with a working 2ds just to rule out the possibility of a dead lcd, lcd works. These are the steps I've taken to attempt repair.

1. Installed a temporary hardmod to dump nand and patch it with b9s.
2. So far, I've tried using firms from 6.0-10.2 o3ds but the unit is still black screen

Best case scenario so far is that the nand chip is damaged, maybe fried, and a ntrboothax will make it work. I'm just waiting for ntrboothax compatibility with R4 dual core then I can test that theory.

I was able to successfully unbrick the 3ds. Here's a recap:
1. Received a bricked regular O3ds after it was downgraded from 11.2 down to 2.1 then upgraded to 6.2 using a cart update.
2. Installed a temporary hardmod to dump the nand and patch it with b9s.
3. This gave me access to Luma cfw menu and Godmode9.
4. 2.1 CTR nand transfer successfully boots into home menu but 9.2 CTR nand transfer boots to blackscreen.
5. Asked for recommendations from this thread but none succeeded.
6. What worked was replacing the movable.sed from a working 3ds.

I still can't understand why the movable.sed worked on 2.1 but not on higher firmwares. I traced the hacking process that lead to the brick. The owner used this https://www.youtube.com/watch?v=hr3aGSaXrXg as a guide and also used the linked files.

That's a great update!

the movable sed is tied per format afaik, doing a fresh format on 2.1 then upgraded to 9.2x should have worked.

anyway, glad to sorted it out! I hope your findings prove useful to other people who may encounter the same.