Homebrew Boot.firm soft Rick help

  • Thread starter Thread starter Al970h2435
  • Start date Start date
  • Views Views 1,746
  • Replies Replies 9

Al970h2435

Member
Newcomer
Joined
Sep 28, 2020
Messages
11
Reaction score
4
Trophies
0
Age
38
XP
89
Country
United States
Hey everybody just got to use Nintendo 3DS off eBay, that was missing the boot.firm since no SD card was provided.

It will not boot just the blue light for a second. After extensive troubleshooting a discovered version Luma3d 7.1boot.firm causes a screen to flicker for a quick second.

I took a picture to see what it was. Its the 7.1 configuration screen.

What file am I missing now since the 3ds still turns off.
 

Attachments

  • IMG_20200928_123938_016.jpg
    IMG_20200928_123938_016.jpg
    977.9 KB · Views: 275
Hey everybody just got to use Nintendo 3DS off eBay, that was missing the boot.firm since no SD card was provided.

It will not boot just the blue light for a second. After extensive troubleshooting a discovered version Luma3d 7.1boot.firm causes a screen to flicker for a quick second.

I took a picture to see what it was. Its the 7.1 configuration screen.

What file am I missing now since the 3ds still turns off.
First update your boot9strap

https://3ds.hacks.guide/updating-b9s

Then update Luma3DS to 10.2
 
No, I don't have a ntrboothax card, thinking I might need this.

Tried to update boot9strap and Luma but all the boot.firm I have tried (7.1 to 10.) have tried no effect. Just a blue light for a quick second, then it powers off.

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

I also tried renaming the safeb9installer.firm to boot.firm and got the blue light to be permanent, yet no screen lights up. Seems almost as if I'm missing something.

This is very difficult to diagnose since I'm not sure what method was us to obtain cfw.
 
Luma3DS v7.1 means that the 3DS has outdated boot9strap v1.0, which is not compatible with newer FIRM payloads.

Try reinserting the (micro)SD card at different angles to get a better connection between the card and reader. If the SafeB9SInstaller v0.0.7 screen shows up with SafeB9SInstaller.firm as the renamed boot.firm, do the Updating B9S & Finalizing Setup {boot9strap v1.3 , Luma3DS v10.2 , GodMode9 v1.9.1 or newer , Sys 11.13.0-45U , FBI v2.6.0 , Homebrew Launcher v2.2.0 , CTRNAND Luma3DS, etc.}.

EDIT - Try cleaning the (micro)SD card slot reader with a drinking straw. Do not blow air; spit can corrode pins. Use suction to pull dust out of the slot.
 
Last edited by TurdPooCharger,
Luma3DS v7.1 means that the 3DS has outdated boot9strap v1.0, which is not compatible with newer FIRM payloads.

Try reinserting the (micro)SD card at different angles to get a better connection between the card and reader. If the SafeB9SInstaller v0.0.7 screen shows up with SafeB9SInstaller.firm as the renamed boot.firm, do the Updating B9S & Finalizing Setup {boot9strap v1.3 , Luma3DS v10.2 , GodMode9 v1.9.1 or newer , Sys 11.13.0-45U , FBI v2.6.0 , Homebrew Launcher v2.2.0 , CTRNAND Luma3DS, etc.}.

EDIT - Try cleaning the (micro)SD card slot reader with a drinking straw. Do not blow air; spit can corrode pins. Use suction to pull dust out of the slot.


Tried renaming safeB9Installer.firm as boot.firm and no dice. I also reformatted the SD and used h2testw to verify the SD card is working.

Still just getting a blue light for a quick second then it powers off.
 
Tried renaming safeB9Installer.firm as boot.firm and no dice. I also reformatted the SD and used h2testw to verify the SD card is working.

Still just getting a blue light for a quick second then it powers off.
Make sure your (micro)SD card is formatted in [ FAT32 format | 32 KB cluster size | MBR disk | Primary partition ] settings. See the quadruple reformat technique. If the card is not formatted in those settings, the 3DS will refuse to read/write to it. If your main card still does not work despite the quad reformatting, try a diffferent/another card.
 
Okay, got it to boot. The issue was ribbon cable was lose which was causing the device to turn off.

However now I notice the volume/3d slider doesn't work. I did a quick motherboard swap a confirmed the sliders(hardware & ribbon cables) are working perfectly.

So I would assume on the CFW motherboard is missing something just like it needed the boot.firm files to boot, to make the sliders work. Any thoughts?
 
Okay, got it to boot. The issue was ribbon cable was lose which was causing the device to turn off.

However now I notice the volume/3d slider doesn't work. I did a quick motherboard swap a confirmed the sliders(hardware & ribbon cables) are working perfectly.

So I would assume on the CFW motherboard is missing something just like it needed the boot.firm files to boot, to make the sliders work. Any thoughts?
In GodMode9, the volume slider is used to adjust screen brightness. If the slider does not work there, that means the motherboard has hardware damage.

Check around the connector area (female side) for the speaker/3D&volume slider assembly (ie, missing resistor, hairline crack in a trace on the board, missing flip lock).

n3DSXL_side_B_(connectors).png
 

Site & Scene News

Popular threads in this forum