Hacking a Wired Problem with A9LH

  • Thread starter Thread starter Boot_8046
  • Start date Start date
  • Views Views 4,610
  • Replies Replies 52
maybe try reverting back to pre-a9lh backup by not choosing "keep a9lh", if it is something with the a9lh build your on you shoudl atleast be back to a working state and can switch back to a9lh 1
 
Ugh, booting without the "/Nintendo 3DS" folder created a new subfolder and linked the console to it. Do you have any recent NAND backup?
The console doesn't "link" to a Nintendo 3DS folder if it's the same NAND and SD.
The data inside the second ID folder is interchangeable either way, so they can move inside the first random number folder and paste the old (second ID) in there.
I doubt this has anything to do with the games though because they mentioned other things like the date showing 1/1/2011.
 
Going back to CHMM, what version were you using? And what type of application? 3dsx or cia? I think that it must have bricked something in the theme loader, preventing the home menu to load at all, similar to how themehax is loaded. Maybe there should be a way to reset the theme loader via a9lh in order to load the home menu again.
 
The system booting to a black screen is usually the cause of a botched theme. It's boots fine but hangs on the very first frame of loading up the theme, which is why recovery mode or "In Sleep Mode, the system can..." work fine.
You can actually see a VERY faint coloring of the HOME Menu if you look closely.
I'm not sure if you actually deleted the right files. You said it boots fine without the original N3DS folder? That's a cause of removing the suspected theme-data. I will tell you what folder you need to delete, for U(nited States), E(uropean), or J(apan) consoles. What console do you have?
 
  • Like
Reactions: MushGuy
The console doesn't "link" to a Nintendo 3DS folder if it's the same NAND and SD.
The data inside the second ID folder is interchangeable either way, so they can move inside the first random number folder and paste the old (second ID) in there.
I doubt this has anything to do with the games though because they mentioned other things like the date showing 1/1/2011.

By "linked" I meant using it as the primary one, which we can't deny it does.

EDIT: Also, can't remember they said anything about the date. :unsure:
 
Last edited by Kyojin,
just rename the nintendo 3DS folder, verify it works, then you can worry about deleting the themes folder once you know thats your issue
 
By "linked" I meant using it as the primary one, which we can't deny it does.

EDIT: Also, can't remember they said anything about the date. :unsure:
What do you mean by primary? The system doesn't associate with any Nintendo 3DS folder. The first hash is part of the console's CID and the second is the SD Card's. Meaning, the second folder is just an organizational feature for if one uses multiple SDs.
Btw, the middle of the first page
 
The system booting to a black screen is usually the cause of a botched theme. It's boots fine but hangs on the very first frame of loading up the theme, which is why recovery mode or "In Sleep Mode, the system can..." work fine.
You can actually see a VERY faint coloring of the HOME Menu if you look closely.
I'm not sure if you actually deleted the right files. You said it boots fine without the original N3DS folder? That's a cause of removing the suspected theme-data. I will tell you what folder you need to delete, for U(nited States), E(uropean), or J(apan) consoles. What console do you have?
That must be totally it. I remember seeing a Reddit thread about a theme softbrick. Removing the corrupted theme simply should work.
 
What do you mean by primary? The system doesn't associate with any Nintendo 3DS folder. The first hash is part of the console's CID and the second is the SD Card's. Meaning, the second folder is just an organizational feature for if one uses multiple SDs.
Btw, the middle of the first page

Oh yes, post #16 indeed for the date and time reset. Forgot about that. ^_^

What I meant is: in case one has several sdmc/Nintendo 3DS/<ID0> folders (left overs because of formatting), only one is actually active.

What I don't know is in case you just delete that folder (without formatting, which was the case here since he removed sdmc/Nintendo 3DS/ at some point), does the console only re-create a folder using the same ID, or does it regenerate a hash internally (at /nand/data/) and set a new folder? I assumed it did (probably mistakenly) from what he was describing.

As for the theme-data folder, he already tried removing it, Home Menu was available again but all data was gone.
 
Oh yes, post #16 indeed for the date and time reset. Forgot about that. ^_^

What I meant is: in case one has several sdmc/Nintendo 3DS/<ID0> folders (left overs because of formatting), only one is actually active.

What I don't know is in case you just delete that folder (without formatting, which was the case here since he removed sdmc/Nintendo 3DS/ at some point), does the console only re-create a folder using the same ID, or does it regenerate a hash internally (at /nand/data/) and set a new folder? I assumed it did (probably mistakenly) from what he was describing.

As for the theme-data folder, he already tried removing it, Home Menu was available again but all data was gone.
Oh yes, post #16 indeed for the date and time reset. Forgot about that. ^_^

What I meant is: in case one has several sdmc/Nintendo 3DS/<ID0> folders (left overs because of formatting), only one is actually active.

What I don't know is in case you just delete that folder (without formatting, which was the case here since he removed sdmc/Nintendo 3DS/ at some point), does the console only re-create a folder using the same ID, or does it regenerate a hash internally (at /nand/data/) and set a new folder? I assumed it did (probably mistakenly) from what he was describing.

As for the theme-data folder, he already tried removing it, Home Menu was available again but all data was gone.
ID0 folder isn't a copy/paste of the NAND CID, and personally I don't know exactly what it is. I do know that it isn't random; formatting an unlinked emuNAND will relink it, as the system will use the old ID0 folder. It has nothing to do with hax, just how the filesystem was developed.
That's why one "seems" active. A NAND can be "linked" to a ID0, just not as described before.
 
Last edited by Halvorsen,
  • Like
Reactions: Kyojin

Site & Scene News

Popular threads in this forum