Hacking So...is my N3DS dead?

[Classicgamer]

I ran into a similar issue with another 3DS and am waiting for the feedback of the latest suggestion.

At the moment it seems Luma3DS is either not finding and patching the NATIVE_FIRM or it's an issue with the 3DS itself. Will update with more info when I hear back about the latest results.

Do you know if reinand was tried?

 

[sarkwalvein]

Do you know if reinand was tried?

Yes, it was found guilty.

 

[Classicgamer]

Yes, it was found guilty.

Not a trial silly, no defendant here. I ask because I don't know if aureinand searches or does things differently than reinand now-a-days.

 

[SomeGamer]

Cakes?

 

[DocKlokMan]

We tried reverting to an older CFW that uses firmware.bin instead, still no go. As far as we can tell it's a mystery. A9LH seems fine because it can load other payloads and the sysNAND backups seem fine because they pass verification when restored (besides the normal corrupted FIRM 0/1 errors that you always get when restoring while keeping A9LH) and when browsing their contents. I'm banking on a physical issue with RAM or something.

 

[3dsn00b]

Do you know if reinand was tried?

Yes. It was tried. Blank screen, no home menu.

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

Just to let everyone know. All arm9 binaries work. A9LH seems fine. It's just that it won't boot beyond that and into home menu. I'm sure this is probably going to happen more as times goes by, because we aren't really sure the consequences of A9LH's long term use. But I'm totally fine with a brick. Because before I started I knew what the potential consequences were. I mean keeping it stock would be safer, but it was way more fun running exploits and messing around. I still have another N3DS with Luma3DS and Updated sysNAND.

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

We tried reverting to an older CFW that uses firmware.bin instead, still no go. As far as we can tell it's a mystery. A9LH seems fine because it can load other payloads and the sysNAND backups seem fine because they pass verification when restored (besides the normal corrupted FIRM 0/1 errors that you always get when restoring while keeping A9LH) and when browsing their contents. I'm banking on a physical issue with RAM or something.

Thanks a lot for your help man, it was greatly appreciated. And to everyone else who tried to help as well: THANKS

 

[dubbz82]

Yes. It was tried. Blank screen, no home menu.

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

Just to let everyone know. All arm9 binaries work. A9LH seems fine. It's just that it won't boot beyond that and into home menu. I'm sure this is probably going to happen more as times goes by, because we aren't really sure the consequences of A9LH's long term use. But I'm totally fine with a brick. Because before I started I knew what the potential consequences were. I mean keeping it stock would be safer, but it was way more fun running exploits and messing around. I still have another N3DS with Luma3DS and Updated sysNAND.

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


Thanks a lot for your help man, it was greatly appreciated. And to everyone else who tried to help as well: THANKS

Could always just run the port of Linux on it until if/when a fix comes around, so it's not a complete loss

 

[GraFfiX420]

I'm not sure if it's a problem with the 3ds's system files, but if you can launch arm9 binaries, why not use this:
https://github.com/Plailect/PlaiSysUpdater/releases/
To downgrade to 9.2, then take a backup of sysnand with d9.
Then restore the backup to sysnand without keeping a9lh.
Then try system recovery to update to 10.7.
The problem with this approach is you will need OoT or Cubic Ninja to complete your hack after this, but it may fix the nand problem, however i'm not 100% sure it will, it's just something you could try.

 

[cavolo]

I'm not sure if it's a problem with the 3ds's system files, but if you can launch arm9 binaries, why not use this:
https://github.com/Plailect/PlaiSysUpdater/releases/
To downgrade to 9.2, then take a backup of sysnand with d9.
Then restore the backup to sysnand without keeping a9lh.
Then try system recovery to update to 10.7.
The problem with this approach is you will need OoT or Cubic Ninja to complete your hack after this, but it may fix the nand problem, however i'm not 100% sure it will, it's just something you could try.

Hint:
.cia != arm9 payload
.3dsx != arm9 payload

 

[kingaz]

Yes. It was tried. Blank screen, no home menu.

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

Just to let everyone know. All arm9 binaries work. A9LH seems fine. It's just that it won't boot beyond that and into home menu. I'm sure this is probably going to happen more as times goes by, because we aren't really sure the consequences of A9LH's long term use. But I'm totally fine with a brick. Because before I started I knew what the potential consequences were. I mean keeping it stock would be safer, but it was way more fun running exploits and messing around. I still have another N3DS with Luma3DS and Updated sysNAND.

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


Thanks a lot for your help man, it was greatly appreciated. And to everyone else who tried to help as well: THANKS

I have a couple of possibly stupid questions:

Have you tried closing the lid and reopening it?

How long have you waited for the screen to come online?

Also, does pressing buttons make sounds?

I ask these because I'm wondering if it has anything to do with the screen init...

Edit: Okay, reading through the thread, it looks like we're doing a less than thorough job of "customer" support.

3dsn00b, if you haven't given up, please provide the following screenshots:

1) The root folder of your micro sd card.

2) Your luma folder.

3) Your settings in Luma3DS.

Also, this might be worth checking out:

https://github.com/Plailect/Guide/wiki/Troubleshooting#ts_sys_a9lh

 

[Deleted User]

Yes, it was found guilty.

You lovable Largen! *Shrek reference

 

[Ricken]

I'm not sure if it's a problem with the 3ds's system files, but if you can launch arm9 binaries, why not use this:
https://github.com/Plailect/PlaiSysUpdater/releases/
To downgrade to 9.2, then take a backup of sysnand with d9.
Then restore the backup to sysnand without keeping a9lh.
Then try system recovery to update to 10.7.
The problem with this approach is you will need OoT or Cubic Ninja to complete your hack after this, but it may fix the nand problem, however i'm not 100% sure it will, it's just something you could try.

I second this. Last Resort i guess

 

[gamesquest1]

I just found something weird. Inside Decrypt9 > Maintenance Options > System Info the Serial Number doesn't match the one on the back of my 3DS. Actually it's only missing a '1' at the end.

yeah the last digit isn't actually part of the serial its a barcode check digit

as for the actual issue i have no idea sorry XD....im just wondering if maybe part of the firm protection stuff is interfering with nand restores or something, maybe try writing a nand backup then dumping your nand afterwards and checking it was actually wrote correctly

 

[Kourin]

Edit: Okay, reading through the thread, it looks like we're doing a less than thorough job of "customer" support.

Are you joking? The people here have been extremely helpful and thorough from what I've read.

 

[kingaz]

Are you joking? The people here have been extremely helpful and thorough from what I've read.

Helpful? Most definitely, and I apologize if I implied otherwise. Thorough? No.

Here's how stuff has gone:

Friendly GBATemper: You should try this!

OP: I did, it didn't work.

Friendly GBATemper: You sure you did this?

OP: I did, it didn't work.

In this, we're making the dangerous assumption that a user going by the handle of 3dsn00b A) set everything up correctly and B) knows how to use these tools correctly.

I didn't mean to cast aspersions here, but I think we should try to eliminate more basic problems before troubleshooting for a more exotic problem.

 

[3dsn00b]

1) The root folder of your micro sd card.

2) Your luma folder.

3) Your settings in Luma3DS.

Also, this might be worth checking out:

https://github.com/Plailect/Guide/wiki/Troubleshooting#ts_sys_a9lh

The test payload doesn't work. No boot when I use the test payload.

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

Edit: Okay, reading through the thread, it looks like we're doing a less than thorough job of "customer" support.

And I'm not really a customer hahahah, as I don't pay you anything. But I am extremely appreciative of the help I have received here. <3

 

[CrispyYoshi]

OP, have you already tried my suggestion? https://gbatemp.net/threads/so-is-my-n3ds-dead.424291/page-4#post-6292110

 

[3dsn00b]

OP, have you already tried my suggestion? https://gbatemp.net/threads/so-is-my-n3ds-dead.424291/page-4#post-6292110

Yes, I have it set up like this on the R trigger:

[KEY_R]
path = /boot.3dsx
delay = 1000
offset = 0x12000
payload = -1
screenEnabled = 1
splash = 1
​

It boots, but is stuck on "is loading..."

 

[CrispyYoshi]

Yes, I have it set up like this on the R trigger:

[KEY_R]
path = /boot.3dsx
delay = 1000
offset = 0x12000
payload = -1
screenEnabled = 1
splash = 1
​

It boots, but is stuck on "is loading..."

Hmm, actually I think it wasn't BootCTR9... I swear I saw someone make an A9LH bootloader that supported .3dsx files. I'll have to get back to you on that tomorrow.

 

[3dsn00b]

Hmm, actually I think it wasn't BootCTR9... I swear I saw someone make an A9LH bootloader that supported .3dsx files. I'll have to get back to you on that tomorrow.

I'm not sure you can run a .3dsx file from A9LH. It would be great if you could, but I think payloads can only be binaries. If there was a binary version of HBL that would be great, but I think HBL needs to use the full 3DS hardware to run, not just ARM9 portion of it?? That's just an "ignorant" guess though, as all binaries I've seen run in a text mode with limited GUI, HBL has a decent GUI - taking advantage of other 3DS hardware.