ROM Hack Clone A9LH sysNAND results in bricked emuNAND?

[WiiUBricker]

I couldn't find any information about it. If you have a sysNAND with A9LH installed and try to clone that sysNAND to emuNAND with emuNAND9, you get a bricked emuNAND? Because I have created emuNANDs this way multiple times and all won't boot. If that's the case, this would mean that people who don't have pre-A9LH NAND backups are locked out from using emuNAND ever again unless there is a method to remove A9LH from sysNAND.

Edit: I'm speaking hypothetically. I have made sysNAND and emuNAND backups, so please refrain from attempting to lecturing me about the importance to make NAND backups! Thx

 

[SomeGamer]

unless there is a method to remove A9LH from sysNAND.

There is! Just restore a pre-A9LH NAND backup.

 

[WiiUBricker]

There is! Just restore a pre-A9LH NAND backup.

Yeah, but what if you don't have a pre-A9LH backup, as said in my post above?

 

[k3rizz3k]

Not trying to troll you.. But this is why all guides stress the importance of multiple nand backups. You don't have even a pre a9lh sysnand backup?

 

[WiiUBricker]

Not trying to troll you.. But this is why all guides stress the importance of multiple nand backups. You don't have even a pre a9lh sysnand backup?

Yes I have. I'm just speaking hypothetically.

 

[Margen67]

What do you need an emunand for?

 

[k3rizz3k]

What do you need an emunand for?

I use mine as a sandbox, to test things without worrying about restoring my sysnand. Can do things quick and dirty

 

[WiiUBricker]

What do you need an emunand for?

For this.

 

[The Real Jdbye]

Yeah, but what if you don't have a pre-A9LH backup, as said in my post above?

And that's why the guide specifically mentions to make both emuNAND and sysNAND backups, and why everyone says to follow the guide exactly. There is no room for error when it comes to getting OTP and installing a9lh, but the guide is written so that not much can go wrong if it's followed exactly. If someone doesn't follow the guide properly and they run into issues they only have themselves to blame.
That is strange though, a9lh replaces the FIRM partitions, but CFW doesn't use them anyway, every CFW uses a firmware.bin on the SD card instead (or in the case of rxTools, a firm folder), so I would think an emuNAND with a9lh installed would still work fine.

 

[WiiUBricker]

And that's why the guide specifically mentions to make both emuNAND and sysNAND backups, and why everyone says to follow the guide exactly. There is no room for error when it comes to getting OTP and installing a9lh, but the guide is written so that not much can go wrong if it's followed exactly. If someone doesn't follow the guide properly and they run into issues they only have themselves to blame.
That is strange though, a9lh replaces the FIRM partitions, but CFW doesn't use them anyway, every CFW uses a firmware.bin on the SD card instead (or in the case of rxTools, a firm folder), so I would think an emuNAND with a9lh installed would still work fine.

Edit: I'm speaking hypothetically. I have made sysNAND and emuNAND backups, so please refrain from attempting to lecturing me about the importance to make NAND backups! Thx

 

[Margen67]

Sysupdater might let you restore FIRM, but it might cause a brick, so I wouldn't recommend it.

 

[The Real Jdbye]

.

I know, I read that already, and I'm saying that hypothetically everyone already has sysNAND and emuNAND backups and hypothetically this isn't even a valid question since everyone has followed the guide and this scenario would never occur.

 

[WiiUBricker]

If I attempt to downgrade a 10.7 A9LH sysNAND to 9.2 with sysUpdater, would this delete A9LH from NAND?

 

[chbinnc]

Yesterday I just booted an a9lh emunand, I restored a9lh 9.1 sysnand to emunand with Decrypt9, I didn't try to directly boot it (You may try it and prove your problem was just caused by bug from emunand9), but then injected a former 10.5 emu ctrnand and booted with auroreinand.

 

[WiiUBricker]

Yesterday I just booted an a9lh emunand, I restored a9lh 9.1 sysnand to emunand with Decrypt9, I didn't try to directly boot it (You may try it and prove your problem was just caused by bug from emunand9), but then injected a former 10.5 emu ctrnand and booted with auroreinand.

Yeah, it seems like I was pressing the wrong button when launching emuNAND. I pressed L instead of R which resulted in the system trying to load emuNAND with the firmware90.bin, which of course won't work since my emuNAND is on 10.7. I am attempting to downgrade my linked 10.7 emuNAND with sysupdater to 9.2 as we speak. Fingers crossed.

Edit: And it worked.

 

[The Real Jdbye]

If I attempt to downgrade a 10.7 A9LH sysNAND to 9.2 with sysUpdater, would this delete A9LH from NAND?

Should work as long as your CFW isn't blocking firm install.

 

[WiiUBricker]

This thread is done for. Thanks everyone for the help.