Hacking I'm in the TestMenu... why?

[Halvorsen]

I edited my post above.

 

[Aletron9000]

ok, if the cloning didn't work, then there is something messed up with the emunand partition of your sd card.
you might need to erase emunand and set it back up again. it could be the sd card as well

 

[Halvorsen]

I've used multiple SD Cards, I've stated that as well.

 

[Aletron9000]

Maybe it is the SD Card reader, I have not seen an issue where one of the ways I mentioned didn't work.

 

[Halvorsen]

I, uh, mean, if it was an obvious problem, I wouldn't be asking here how to fix it.

SD Card reader seems fine, games run correctly.

 

[Aletron9000]

I, uh, mean, if it was an obvious problem, I wouldn't be asking here how to fix it.

SD Card reader seems fine, games run correctly.

If the sysnand is booting fine, the emunand should be booting fine.

when you tried another sd card, did you move the faulty emunand to that sd card then tried to run it?

 

[invaderyoyo]

I have backups, everything except emuNAND related stuff is working. I cannot get emuNAND to boot, whether it's CTRTransfer, 2.1CTRTransfer (Plailect guide, and yes, it works and boots on my other system's emuNAND), and the original sysNAND copied to emuNAND.

None of them boot.
That's my problem. I don't see the point in making backups; those are completely unrelated to the issue.

EmuNAND's not working at all? When I had it, it worked fine, but I couldn't get the darn thing to downgrade to 2.1. The people on #Cakey tried to help me.

 

[Ryccardo]

To answer your original question, which will hopefully have you shed some light on what happened:

If you install TestMenu, it will launch in only these 3 cases:
-TestMenu selected in Config/Menuselector AND Unitinfo patch enabled in your cfw (or, well, real Panda console...)
-cfw with force testmenu patch
-Home can't start (deleted, corrupted, region change in SecureInfo without installing the correct region OS first)

also, TestMenu defines DevMenu as a ctrnand-installed app with the titleid of 00040000-0ff40002, unfortunately many sources for DevMenu are unfaithful conversions that change this!

 

[Halvorsen]

If the sysnand is booting fine, the emunand should be booting fine.

when you tried another sd card, did you move the faulty emunand to that sd card then tried to run it?

No. But um, I'm getting some weird things. SysNAND cloned to emuNAND does not boot (Obviously I know it "should", fact is that it doesn't boot). And seems like anything derived some the current sysNAND and being cloned to emuNAND doesn't want to boot. I guess this explains the reason 2.1CTRTransfer didn't work, and why my own CTRNAND didn't either. Still confused on how sysNAND boots while cloning the same sysNAND to emuNAND bricks.

I did restore a 9.2E sysNAND backup, and I actually got it to boot. I guess it worked? It seems strange that sysNAND > emuNAND doesn't work, however... I'll keep this emuNAND and preform the CTRTransfer on it, and see if it works. Wish me luck.

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

To answer your original question, which will hopefully have you shed some light on what happened:

If you install TestMenu, it will launch in only these 3 cases:
-TestMenu selected in Config/Menuselector AND Unitinfo patch enabled in your cfw (or, well, real Panda console...)
-cfw with force testmenu patch
-Home can't start (deleted, corrupted, region change in SecureInfo without installing the correct region OS first)

also, TestMenu defines DevMenu as a ctrnand-installed app with the titleid of 00040000-0ff40002, unfortunately many sources for DevMenu are unfaithful conversions that change this!

Seems like it may be the last case?

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

EmuNAND's not working at all? When I had it, it worked fine, but I couldn't get the darn thing to downgrade to 2.1. The people on #Cakey tried to help me.

Gotta say, this is a very weird system. I got emuNAND to boot from a backup, but it doesn't boot if I clone sysNAND to the emuNAND, which I find really weird.

 

[invaderyoyo]

No. But um, I'm getting some weird things. SysNAND cloned to emuNAND does not boot (Obviously I know it "should", fact is that it doesn't boot). And seems like anything derived some the current sysNAND and being cloned to emuNAND doesn't want to boot. I guess this explains the reason 2.1CTRTransfer didn't work, and why my own CTRNAND didn't either. Still confused on how sysNAND boots while cloning the same sysNAND to emuNAND bricks.

I did restore a 9.2E sysNAND backup, and I actually got it to boot. I guess it worked? It seems strange that sysNAND > emuNAND doesn't work, however... I'll keep this emuNAND and preform the CTRTransfer on it, and see if it works. Wish me luck.

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


Seems like it may be the last case?

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


Gotta say, this is a very weird system. I got emuNAND to boot from a backup, but it doesn't boot if I clone sysNAND to the emuNAND, which I find really weird.

Idk if it has something to do with the hardmod, but when I got it, it was already hardmodded and I couldn't get it to work, so I removed the hardmod thinking it might be the hardmod. After that, it still didn't work so I re-hardmodded it to unbrick it. After that I removed the hardmod again.

 

[Halvorsen]

Thanks all who were trying to help.

 

[Dylan the Tactician]