Hacking Think my 3ds xl automatically updated to 11.9

[loon111]

What's in your boot9strap folder?

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

only just put this there though, wasn't there before

 

[osm70]

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


only just put this there though, wasn't there before

OK, you can try this to check if boot9strap is installed.

If B9S is working correctly, it should be able to dump your console specific files, even if it doesn't boot into any payload.

Hold START+SELECT+X on boot all the way until the Home Menu shows up. Then check your SD card. You should have arm11.bin, arm9.bin, and otp.bin in the boot9strap folder. If those files were dumped, B9S is installed, but not booting payloads for some reason. If those files don't appear, your 3DS is not hacked with boot9strap.

 

[loon111]

OK, you can try this to check if boot9strap is installed.

If B9S is working correctly, it should be able to dump your console specific files, even if it doesn't boot into any payload.

Hold START+SELECT+X on boot all the way until the Home Menu shows up. Then check your SD card. You should have arm11.bin, arm9.bin, and otp.bin in the boot9strap folder. If those files were dumped, B9S is installed, but not booting payloads for some reason. If those files don't appear, your 3DS is not hacked with boot9strap.

thanks mate, done that an nothing there

 

[osm70]

thanks mate, done that an nothing there

Files not showing up?

That probably means the system unhacked itself completely for some weird reason. I have never heard of that happening, so I am lost...

The only thing I can think of is hacking it again from the start.

 

[loon111]

yeah mate, nothing, i never installed the boot 9 though before, i used the old arm 9 an still have all the old dumps?

 

[PrincessLillie]

This is the strangest case of issues with System Updates I've heard thus far.
The only thing I can think of is to follow Plailect's 3DS Hacks Guide from the very beginning.

 

[The Real Jdbye]

yeah mate, nothing, i never installed the boot 9 though before, i used the old arm 9 an still have all the old dumps?

That would explain why Start+Select+X doesn't work.
Follow http://3ds.hacks.guide/

 

[loon111]

This is the strangest case of issues with System Updates I've heard thus far.
The only thing I can think of is to follow Plailect's 3DS Hacks Guide from the very beginning.

So you think i have to do it all again on 11.9.042e

 

[TurdPooCharger]

So you think i have to do it all again on 11.9.042e

1. Copy everything off your SD card onto a computer.
2. Reformat the SD card with MiniTool Partition Wizard (free edition) with these settings:
   • Format: FAT32
   • Cluster Size: 32 KB
     
   • Partition: Primary
   • Disk: MBR
   MiniTool Partition Wizard Software Tutorial Guide
   1. Delete Partition
   2. Initialize to MBR Disk -or- Convert GPT to MBR Disk (if it's in GPT Disk)
   3. Rebuild MBR
   4. Create a New Partition [ Create as: Primary | File System: FAT32 | Cluster Size: 32 KB ]
3. Full Write + Verify the empty card in H2testw. Do not skip this step.
4. If the card passes the test, delete the *.h2w test files. Do not add back your main setup at this moment.
   
   • If the card failed hardware inspection, replace it and go back to steps 1 or 2.
5. Download SafeB9SInstaller v0.0.7. Extract the SafeB9SInstaller.firm from the ZIP and rename as boot.firm.
   • Put this on the root of the SD card.
6. Download Luma3DS v7.0.5. Extract arm9loaderhax.bin from the ZIP and put it on the root of the SD card.
7. Insert the SD card into your 3DS, turn on the system, and hold the (SELECT) button.

If the 3DS boots, tell us whether you see Luma3DS v7.0.5 configuration or SafeB9SInstaller v0.0.7 on the bottom screen.

 

[osm70]

1. Copy everything off your SD card onto a computer.
2. Reformat the SD card with MiniTool Partition Wizard (free edition) with these settings:
   • Format: FAT32
   • Cluster Size: 32 KB
     
   • Partition: Primary
   • Disk: MBR
   MiniTool Partition Wizard Software Tutorial Guide
   1. Delete Partition
   2. Initialize to MBR Disk -or- Convert GPT to MBR Disk (if it's in GPT Disk)
   3. Rebuild MBR
   4. Create a New Partition [ Create as: Primary | File System: FAT32 | Cluster Size: 32 KB ]
3. Full Write + Verify the empty card in H2testw. Do not skip this step.
4. If the card passes the test, delete the *.h2w test files. Do not add back your main setup at this moment.
   • If the card failed hardware inspection, replace it and go back to steps 1 or 2.
5. Download SafeB9SInstaller v0.0.7. Extract the SafeB9SInstaller.firm from the ZIP and rename as boot.firm.
   • Put this on the root of the SD card.
6. Download Luma3DS v7.0.5. Extract arm9loaderhax.bin from the ZIP and put it on the root of the SD card.
7. Insert the SD card into your 3DS, turn on the system, and hold the (SELECT) button.

If the 3DS boots, tell us whether you see Luma3DS v7.0.5 configuration or SafeB9SInstaller v0.0.7 on the bottom screen.

That won't work, though. They can't boot firm files:

yeah mate, nothing, i never installed the boot 9 though before, i used the old arm 9 an still have all the old dumps?

 

[GothicIII]

Files not showing up?

That probably means the system unhacked itself completely for some weird reason. I have never heard of that happening, so I am lost...

The only thing I can think of is hacking it again from the start.

Exactly the same thing happened for me too in 2016 I believe (a9lh). I think I posted here about that and everyone bitchered I updated the console by myself (no one except me had access to the 3ds). Had to downgrade and install a9lh again. Very weird and it didn't happen again.
I swear it just updated itself over night.

EDIT: I just can't find the post. Maybe it was deleted or I posted it in a different forum. Sorry for not providing any evidence.

 

[osm70]

Exactly the same thing happened for me too in 2016 I believe (a9lh). I think I posted here about that and everyone bitchered I updated the console by myself (no one except me had access to the 3ds). Had to downgrade and install a9lh again. Very weird and it didn't happen again.
I swear it just updated itself over night.

But that's still weird. Even if you update the 3DS firmware, it will still be hacked. In fact, updating the firmware doesn't matter. It won't break anything. (Assuming you are on the latest version of Luma, but even if you aren't, you need to just replace one file on your SD card and everything gets fixed again.)

 

[TurdPooCharger]

That won't work, though. They can't boot firm files:

Or his SD card is formatted wrong and can't be read, which is why I directed him to use MiniTool Partition Wizard..

Or his SD card is fake or bad, so the files end up being read as corrupt. Why the reason for H2testw..

Then there's adding both SafeB9SInstaller AND Luma3DS v7.0.5. If he has boot9strap custom firmware, it will boot SafeB9SInstaller regardless whether it is v1.0 through v1.3..

If however he has A9LH, he'll boot Luma3DS v7.0.5.

Or simply, his card reader no longer reads SD cards.

Or he softbricked so bad that he's required to used NTRboot to recover from.

 

[GothicIII]

But that's still weird. Even if you update the 3DS firmware, it will still be hacked. In fact, updating the firmware doesn't matter. It won't break anything. (Assuming you are on the latest version of Luma, but even if you aren't, you need to just replace one file on your SD card and everything gets fixed again.)

I know. I'm pretty skilled about that stuff. (You can search my profile and see for yourself). It should never happen and there is no evidence that the console can do it by itself. Devs would have found that long ago.

 

[osm70]

Or his SD card is formatted wrong and can't be read, which is why I directed him to use MiniTool Partition Wizard..

Or his SD card is fake or bad, so the files end up being read as corrupt. Why the reason for H2testw..

Then there's adding both SafeB9SInstaller AND Luma3DS v7.0.5. If he has boot9strap custom firmware, it will boot SafeB9SInstaller regardless whether it is v1.0 through v1.3..

If however he has A9LH, he'll boot Luma3DS v7.0.5.

Or simply, his card reader no longer reads SD cards.

Or he softbricked so bad that he's required to used NTRboot to recover from.

Oh, right. You did say to add the Luma payload. My mistake.

 

[Skirlez]

Wait. couldn't it be that he still has A9LH?
OP, backup your arm9loaderhax.bin file on your SD card, and remove it. (not the backup)
If your system doesn't boot, you still have A9LH.
If your system does boot, you don't appear to have CFW.
Follow this:https://3ds.hacks.guide/seedminer
and inform us when you're done.