Hacking PSA: Stop downgrading unless you know what you're doing!

[Draxzelex]

Mhm i noticed that too, but can someone pls enlighten me WHY people are downgrading at all? I mean i totally see why you want to use RCM, preserve your fuses so you can downgrade to an exploitable FW once there gets an cooldboot exploit or smth else interessting released, but there´s nothing out yet.
What´s the reason, the urge, to downgrade? Is there any reason at all to use a lower FW with RCM and hekate when your fuses are already burnt?

Impatience at waiting for CFW to update because people have to play their totally legal backups, homebrew applications, and emulators.

 

[Idontknowwhattoputhere]

This should be stickied

 

[der:Tom]

Impatience at waiting for CFW to update because people have to play their totally legal backups, homebrew applications, and emulators.

I get that, but atm every cfw works on 8.0.1 (is there any homebrew that has compatibility issues?), that´s what i don´t get...

 

[Draxzelex]

I get that, but atm every cfw works on 8.0.1 (is there any homebrew that has compatibility issues?), that´s what i don´t get...

When people are downgrading, they are usually downgrading from a firmware which CFW does not currently support which is firmware 8.1 at the moment.

 

[der:Tom]

Ah ok, didn´t notice that 8.1 came out (the last days?) that explains a lot, thx for clearing that up

 

[Kafluke]

Yeah and they're restoring their clean nand backups in prep for atmos emu nand. Most just dont realize that you dont just load up your raw nand and go. You also need boot0 and boot1 and fuses must match

 

[Kafluke]

I counted at least 3 threads on the main page this morning of people restoring nands and they dont know what they're doing.

 

[Pokfan1]

I upgraded to 9.1 with OFW(wifi update) on my clean sysnand.
Is there any drawback apart from the fact that I may have problem restoring my old sysnand?

 

[Draxzelex]

I upgraded to 9.1 with OFW(wifi update) on my clean sysnand.
Is there any drawback apart from the fact that I may have problem restoring my old sysnand?

You can only boot the console through RCM so enabling AutoRCM is highly recommended.

 

[Pokfan1]

You can only boot the console through RCM so enabling AutoRCM is highly recommended.

Why? Sorry I am a bit confused
I mean I have a clean sysNAND with v9.1 OFW.
If I setup again emuNAND with v9.1, why i won't be able to boot without RCM?
Thank you for your reply

 

[Draxzelex]

Why? Sorry I am a bit confused
I mean I have a clean sysNAND with v9.1 OFW.
If I setup again emuNAND with v9.1, why i won't be able to boot without RCM?
Thank you for your reply

You asked if there were any issues in restoring your old sysMMC which I would assume is on a lower firmware since you called it "old".

 

[Pokfan1]

You asked if there were any issues in restoring your old sysMMC which I would assume is on a lower firmware since you called it "old".

No, I don't care about any backup I have. I just asked if there is any other problem.

 

[pLaYeR^^]

No, I don't care about any backup I have. I just asked if there is any other problem.

If you have burnt fuses, you can still restore your old NAND backup but only boot with RCM to it (disable fuse check). So it's pretty useless. Another thing is that you have lost access to exploits on older firmware versions like Deja Vu.

 

[Pokfan1]

If you have burnt fuses, you can still restore your old NAND backup but only boot with RCM to it (disable fuse check). So it's pretty useless. Another thing is that you have lost access to exploits on older firmware versions like Deja Vu.

Nice thanks!

 

[Kafluke]

There's more to it than that.

If you've EVER been online with your "dirty" sysnand since making the original backup, forget about going online. Inevitable ban.

 

[Ottoclav]

So wait. I have been trying to get ofw 510 working on my newly acquired switch. I'm running Hekate 5.3 that came with the recommended package from the SDSetup homebrew page. I've followed the tutorial all the way to the end. I've had a GBATemp member walking me through the process, since I am unfamiliar with how to use the .exe files and ChoiDujoir and all that. As far as I can follow, I've done everything correctly. According to this post though, should I be loading up 9.1 or 9.2 HOS since I have 12 fuses burnt up? I thought that Hekate was supposed to bypass the fuse count, but when I try booting the FS_XXX-exfat_nocmac_nogc file, it just freezes at the Hekate-IPL screen. I've been through steps 14 and 13 three times, and no change in the screen freeze at Hekate-IPL. If I take out the hekate_ipl.bin and rename the hekate_bak.bin to the original hekate_ipl.bin name, then when I select CFW(SysNand), i get the red "Pkg2 decryption failed! Failed to launch HOS! press any key..." error.

I am currently using a Samsung 128Gb SD card, formatted exFAT. I've seen a response that this could be the problem. Is it truly?

 

[Adran_Marit]

So wait. I have been trying to get ofw 510 working on my newly acquired switch. I'm running Hekate 5.3 that came with the recommended package from the SDSetup homebrew page. I've followed the tutorial all the way to the end. I've had a GBATemp member walking me through the process, since I am unfamiliar with how to use the .exe files and ChoiDujoir and all that. As far as I can follow, I've done everything correctly. According to this post though, should I be loading up 9.1 or 9.2 HOS since I have 12 fuses burnt up? I thought that Hekate was supposed to bypass the fuse count, but when I try booting the FS_XXX-exfat_nocmac_nogc file, it just freezes at the Hekate-IPL screen. I've been through steps 14 and 13 three times, and no change in the screen freeze at Hekate-IPL. If I take out the hekate_ipl.bin and rename the hekate_bak.bin to the original hekate_ipl.bin name, then when I select CFW(SysNand), i get the red "Pkg2 decryption failed! Failed to launch HOS! press any key..." error.

I am currently using a Samsung 128Gb SD card, formatted exFAT. I've seen a response that this could be the problem. Is it truly?

Try regular cfw boot also you shouldn't be using the old method incase of things like this

 

[Ottoclav]

Try regular cfw boot also you shouldn't be using the old method incase of things like this

without a proper label that i can read in the actual GUI, i don't know what 'regular' CFW boot means. The "old" method is the only method available, since ChoiDujoirNX cannot be accessed without actually booting into the CFW, amiright?

 

[Adran_Marit]

without a proper label that i can read in the actual GUI, i don't know what 'regular' CFW boot means. The "old" method is the only method available, since ChoiDujoirNX cannot be accessed without actually booting into the CFW, amiright?

Boot using cfw of your choice and using choidujourNX to downgrade, there is also a different method which is slightly easier than the whole PC Choi downgrade

find it here - You would want the emmc rebuild section

 

[Ottoclav]

Boot using cfw of your choice and using choidujourNX to downgrade, there is also a different method which is slightly easier than the whole PC Choi downgrade

find it here - You would want the emmc rebuild section

I don't mean to be plucky, but my post was very clear that I cannot access CFW, so ChoiDujourNX is out of the question. I am stuck in Hekate 5.3 GUI for now. I will read up on your link though, just in case the Pkg2 decryption problem can be fixed with an emmc rebuild.