am I screwed? I wanted to clone my emunand to my sysnand but picked godmode9 and wiped out sysnand and copied emunand to it. I still have godmode9 open but too scared to reboot. Did I overwrite FIRM0 and FIRM1?
Hacking Nuked CTRNAND, is A9LH still there or...
- Thread starter lisreal2401
- Start date
- Views 3,325
- Replies 34
I'd say it depends on when you created your emuNAND. If you created it after installing a9lh, then you most likely removed a9lh when wiping sysNAND then you put it back when copying your emuNAND to sysNAND. Otherwise nope, you wiped it.
But why are you using GodMode9 for that though? That's a job for emuNAND9, Decrypt9, or Hourglass9, but not GodMode9.
But why are you using GodMode9 for that though? That's a job for emuNAND9, Decrypt9, or Hourglass9, but not GodMode9.
The problem is I can't find any access to the FIRM partitions in the app. In godmode9 I wiped all of SYSNAND CTRNAND but touched nothing else. So I don't know if it's protected or if it's apart of the stuff I deleted. I realize this was really stupid in hindsight but I won't reboot until I know whether it's safe, I'm fucked, or I can fix it within godmode9 itself.
Be careful of what you are saying. If you wiped ONLY CTRNAND, A9LH is still there. If you wiped ALL of sysnand, it may not be. Honestly, unless you have backups, there isn't anything you can do in GodMode9 to restore, so you might as well reboot and see.
That's what he says in the title, but maybe he confuses stuff. I'm not saying he's a complete idiot (otherwise he would have rebooted without thinking about it) but if he was a pro, he would not have used GodMode9 for that, or he would if he was a real pro but in that case he would not have had any problem.
I have a backup of the clean 9.2.0-22J somewhere, but it's in a standard .bin format, and I don't have the xorpads. The emunand, by the way, is region changed. There's no distinction between CTRNAND and where the FIRM partitions would be. Is there a key sequence to access the FIRM partitions because I can't find them otherwise.
Okay, so you are confirming you have absolutely no idea what you are doing. Therefore you should have never used GodMode9 in the first place. SafeMode9 is for users like yourself.
In any case, CTRNAND is a partition of SYSNAND. the FIRMS are NOT on that partition, so they were not wiped. Non-A9LH backups are pointless at this point. Xorpads wouldn't help you here unless you wanted to extract the CTRNAND from the 9.2 backup and then inject it into your current setup.
Or do what Sketchy1 recommends.
*FACEPALM*
He is recommending to:
-Restore your 9.2 system image, AS LONG AS IT"S FROM THAT EXACT CONSOLE
-Use Plailect's Guide to redo A9LH (since 9.2 is required for A9LH and you can be on that)
-???
-Profit
I am recommending to restart, as wiping CTRNAND doesn't wipe firms.
It's up to you, and none of us are responsible for if you end up with a system you cannot use.
Yeah, the xorpads were to put the extracted content back into the CTRNAND partition. But it seems like that doesn't matter either way.
But you should be fine anyway, because you restored ctrnand data. My way is just "safest" b/c its the stock image that came with the system.
And godmode9 doesn't have nand restore to my knowledge, as its just a file manager
I can't restore images within godmode9. I can't run any other app without rebooting. But if you say so... I will.
Then he couldn't restore his 9.2 image, so that's pointless.
--------------------- MERGED ---------------------------
Restart while holding down the button for the GodMode9 payload. This way we'll know if A9Lh is still there.
Congrats then bro, but please, get rid of godmode9, safemode9 is more appropriate for you.Holy shit yeah luma is still here
-
K3Nv2
-
AncientBoi
-
The Real Jdbye
*is birb*
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
@
AncientBoi:
What Network is it on? I wanna see what you guys are talking about. N What time frame is it on?
-
-
-
-
-
