Yeah I'm a genius xD

[Alkéryn]

Source : http://gbatemp.net/threads/a9lh-question.433725/

 

[Logan Pockrus]

 

[Alkéryn]

I didn't lost it, always was like that
but i'm not crazy, it's just the other in my head doing bullshit ^^

 

[Logan Pockrus]

I didn't lost it, always was like that
but i'm not crazy, it's just the other in my head doing bullshit ^^

Whatever you say, man....

Just kidding. I'm sure you're alright in the head...probably.

 

[Alkéryn]

Whatever you say, man....

Just kidding. I'm sure you're alright in the head...probably.

Just joking ^^ but no one answered so i just answered myself ^^

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

What? I don't even...... WHAT?!

Anyways, OP, please ignore OP. As I still think OP failed to answer OP's question.

Basically Section IV has you flashback emunand_orginal.bin because it should be the initial updated sysnand.bin, as well with having FBI injected into it.

So an overview of how and where this NAND was created is as followed.

sysNAND.bin from Part 2 is the clean 9.2 SysNAND backup of your system, this should be a fresh clean non-A9LH 9.2 Backup, with no FBI injected or anything, just clean.

Part 3 has you created a RedNAND, which is a direct clone of your SysNAND as it is. However, in Part 3, we are also told to use TinyFormat on SysNAND, as a way to unlink them, and have them separate from each other.

Part 4, Section I, has us update RedNAND to the latest version.

Part 4, Section II, has us backup these two NANDs to sysNAND_original.bin (which is completely different than sysnand.bin, but is also should be a clean 9.2 SysNAND backup of your SysNAND after having TinyFormat run on it) - While emuNAND_original.bin is a continuation of your original sysnand.bin from Part 2, but with it being updated and having FBI injected into it.

emuNAND_formatted.bin is made so that if the RedNAND 2.1 downgrade fails, we can restart that process and try and try again.

Would I advise you skip making RedNAND backups? No, not really. Especially not the emuNAND_formatted.bin one, as if your 2.1 downgrade fails, you'll have to pretty much start over from scratch. Cloning to RedNAND and unlinking the NANDs and preparing the RedNAND for the 2.1 downgrade.

All in all, I can only justify skipping the NAND backup on Part 2.

Anyways, here's a bit of how each NAND backup should be and it's line of backups.

sysNAND.bin (part2, clean 9.2 backup) -> emunand_orginal.bin (updated sysnand.bin with FBI injected) -> sysNAND-A9LHAX.bin (final backup with A9LH installed)

SysNAND_original.bin (Part 4, clean 9.2 backup, unlinked from the above and bellow NANDs)

emuNAND_formatted.bin (Part 4, updated RedNAND, unlinked from the above two, and prepared and used for the 2.1 downgrade.)

But she then Killed me with her "Anyways, OP, please ignore OP. As I still think OP failed to answer OP's question." xD

 

[Temptress Cerise]

Just joking ^^ but no one answered so i just answered myself ^^

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


But she then Killed me with her "Anyways, OP, please ignore OP. As I still think OP failed to answer OP's question." xD

Fixed. Not a he. Anyways~ Good luck with whatever it is you are trying to do.

 

[Alkéryn]

Fixed. Not a he. Anyways~ Good luck with whatever it is you are trying to do.

Sorry miss, didn't check ^^ i think i will just follow it normaly until section IV part 5 wher i will go back to a clean 9.2 sys then install fbi through the HBL with FBI.3dsx ^^