Hacking Downgrade from 7.0 with NAND backup

  • Thread starter Thread starter eldavo2090
  • Start date Start date
  • Views Views 18,308
  • Replies Replies 112
  • Likes Likes 1
Hmm. Seems that nobody mentioned this.
You can downgrade to/restore older versions but you would need to boot through bootloader which bypasses fuze check. If you have proper files for restoration, go ahead and restore, but first do a new backup.
 
It is a damn shame to post this thread, with this subject but it happened.
My console was updated, to blame anyone in my family would be stupid as I had time to prevent this from happening, anyway, I just want to ask... I have a backup that I made in 12/30/18, 6.2 and I use Kosmos CFW, and I wanted to restore my backup with hekate.
Don't really know much about fuses and that stuff so I wanted to know what risks I have in restoring it from the latest firmware...

Again I am terribly sorry to ask for help with this stupid issue but I really appreciate your help in responding my questions...
yes as long as you can still boot RCM you can restore a backup. You will just need to restore boot0/1 as well
 
this may sound like the dumbest thing ever but i (made a nand backup first) updated to 7.0 then followed that long ass guide i previously linked, and downgraded to 6.1.0 (i used an old backup of my tsec keys that i had previously dumped while still on 6.2 for this downgrade process) and everything is fine. My switch didn't get bricked at all. I feel this is due to me using my old tsec keys and not dumping the ones from updating to 7.0 since apparently 7.0 rewrites your tsec keys to attempt to block cfw. ALSO i was using atmosphere for this whole process.
 
  • Like
Reactions: eldavo2090
It is a damn shame to post this thread, with this subject but it happened.
My console was updated, to blame anyone in my family would be stupid as I had time to prevent this from happening, anyway, I just want to ask... I have a backup that I made in 12/30/18, 6.2 and I use Kosmos CFW, and I wanted to restore my backup with hekate.
Don't really know much about fuses and that stuff so I wanted to know what risks I have in restoring it from the latest firmware...

Again I am terribly sorry to ask for help with this stupid issue but I really appreciate your help in responding my questions...
You never know, maybe it won't be too long.
 
Hmm. Seems that nobody mentioned this.
You can downgrade to/restore older versions but you would need to boot through bootloader which bypasses fuze check. If you have proper files for restoration, go ahead and restore, but first do a new backup.

Exactly this!
In the worse case scenario you'll have your ver 7 backup.
 
I can confirm, only downgrading to 6.2.0 is broken.

6.1.0 and lower are "safe" because they don't use the TSEC.

I'm on 7.0.0 with burned efuses and 6.1.0 emunand...
 
  • Like
Reactions: JJTapia19
I can confirm, only downgrading to 6.2.0 is broken.

6.1.0 and lower are "safe" because they don't use the TSEC.

I'm on 7.0.0 with burned efuses and 6.1.0 emunand...

Yet I downgraded to 6.2? *thonk* lemme try again

EDIT: I upgraded to 7.0 now have 9 burnt fuses, downgraded back to 6.2 using hekate. Booted CFW fine using both Hekate and ReiNX.bin

When I restored my backup I restored boot 0/1 as well.

Thanks
 
Last edited by Adran_Marit,
  • Like
Reactions: josete2k
Yet I downgraded to 6.2? *thonk* lemme try again

EDIT: I upgraded to 7.0 now have 9 burnt fuses, downgraded back to 6.2 using hekate. Booted CFW fine using both Hekate and ReiNX.bin

When I restored my backup I restored boot 0/1 as well.

Thanks
Can you boot in OFW with hekate now?
 
I don't get why people think that a NAND backup would brick your Switch if you restore it? It doesn't!
If your fuse count is wrong it only means you'll have to boot via hekate (custom bootloader everytime).
If you used Choixdujour, this does not even apply!
 
I don't get why people think that a NAND backup would brick your Switch if you restore it? It doesn't!
If your fuse count is wrong it only means you'll have to boot via hekate (custom bootloader everytime).
If you used Choixdujour, this does not even apply!

sometimes you need to restore boot0/1 as well, and if you don't have those that's when issues arise
 
sometimes you need to restore boot0/1 as well, and if you don't have those that's when issues arise

Yep! That's what would make a complete NAND backup no?
Why backup 29 GB and only leave out a few bytes?
PSA: Boot0/1 are part of the backup process (has always been!)
 
Yep! That's what would make a complete NAND backup no?
Why bakcup 29 GB and only leave out a few bytes?
PSA: Boot0/1 are part of the backup process (has always been!)

lol I'm aware but some people when they get told to do a nand backup will do just the nand and nothing else.
 
Yet I downgraded to 6.2? *thonk* lemme try again

EDIT: I upgraded to 7.0 now have 9 burnt fuses, downgraded back to 6.2 using hekate. Booted CFW fine using both Hekate and ReiNX.bin

When I restored my backup I restored boot 0/1 as well.

Thanks

Nice news..

I'm with SXOS and emunand 6.2.0 don't work so I assumed that 6.2.0 OFW won't boot.

So, SXOS seems to have the key embebbed and hekate/Atmosphere extract it from TSEC...
 

Site & Scene News

Popular threads in this forum