Hacking Downgrade from 7.0 with NAND backup

[josete2k]

Atmosphere preserves autoRCM when updating.

You can't boot 7.0.0 from RCM.

 

[ZachyCatGames]

You can't boot 7.0.0 from RCM.

Ok? I know that. I was just saying that Atmosphere preserves autoRCM when updating.

 

[Draxzelex]

You can't boot 7.0.0 from RCM.

No but this prevents a fuse from being burnt if your system is on 7.0 as long as you don't disable AutoRCM. This allows you to downgrade to a firmware that matches your fuse count and boot OFW so its still useful.

 

[Ericthegreat]

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...

Hey seems you might be okay, follow the thread for a bit and make sure it's safe first.

https://gbatemp.net/threads/switch-7-0-downgrade-to-6-2-tutorial.530135/

 

[Adran_Marit]

Hey seems you might be okay, follow the thread for a bit and make sure it's safe first.

https://gbatemp.net/threads/switch-7-0-downgrade-to-6-2-tutorial.530135/

OP got it sorted

 

[eldavo2090]

Hey seems you might be okay, follow the thread for a bit and make sure it's safe first.

https://gbatemp.net/threads/switch-7-0-downgrade-to-6-2-tutorial.530135/

I'm good now, had a boot 0/1 backup along with a raw nand one, and that did the trick!

 

[Manurocker95]

Scires just got Atmosphere working on 7.0.0. There's no point to downgrade.

 

[Robert McCoy]

Scires just got Atmosphere working on 7.0.0. There's no point to downgrade.

You'd have to be able to dump 7.0.0 keys for the new atomsphere to work and I doubt most of know how to do without cfw.

 

[eldavo2090]

Scires just got Atmosphere working on 7.0.0. There's no point to downgrade.

Already did, and by the looks from it it's still kinda hard for the average user...

 

[ZachyCatGames]

Already did, and by the looks from it it's still kinda hard for the average user...

It's pretty easy... if you can get the needed needed keys.

 

[eldavo2090]

It's pretty easy... if you can get the keys.

That's the thing... Well it's not that hard as I have them already, but it's more easier to update with the sd files from other CFW like Kosmos or ReiNX... But that's just my opinion....

 

[ZachyCatGames]

That's the thing... Well it's not that hard as I have them already.

You don't. The 7.0.0 keys can only be gotten through private methods as of right now

 

[eldavo2090]

You don't. The 7.0.0 keys can only be gotten through private methods as of right now

Damn right!
I have old keys from 6.2.0!!
Lol well that just shows I was better off restoring my nand... Need to learn a lot more about this stuff...

 

[paulzheng]

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...

wait atmosphere's cfw updating to compatible with 7.0 OFW

 

[Adran_Marit]

wait atmosphere's cfw updating to compatible with 7.0 OFW

It's already comptaible if you have the 7.0 keys already.. if not give it a few days or so

 

[ZachyCatGames]

if you have the 7.0 keys already

Good luck with that part though

 

[Adran_Marit]

Good luck with that part though

Exactly

 

[Noaken]

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...

Just wait for CFW to come on 7.0 it's pretty close.

 

[JuanDurring]

My Switch stealthly updated itself to 7.0 when it was running 6.1 on CFW. I've successfully restored the Boot 0/1 and Nand files and successfully booted back to the state it was at 6.1 so attempted to run CFW again. So I powered it off, put it in RCM mode and loaded ReiNX. I originally used a 32gb microSD to put the nand and boot 0/1 files in for the restore and forgot to remove it and put back the old 64GB that had my games and stuff so when I sent the payload, I saw some orange text on the screen (something about patching) and ReiNX didn't boot.

I then (what it seems like) powered it off, and inserted the original microSD card with my games on it and now I can't get the Switch to detect in RCM mode on TegraRCMGUI and have tried holding the power button down for 10sec, 12 sec, 15 sec, 20 sec, 30 sec and up to 1 minute and can't get the system to boot up. I know the power was in the 90-something percent when it was restoring.

Anyone had this issue and resolved it? I do recall setting up a friend's 6.2 Switch and thought I bricked it (no RCM ready detection, no power, black screen, etc) and was able to get it to boot back up after doing some long power button press and then pressing the home button 1 or 2 times. I've been looking for that link that had that solution and haven't had any luck.

Any help would be greatly appreciated. I'm more than certain that it's not a brick as I was able to boot to stock OFW after restoring it back to 6.0.1.

Thanks in advance!

 

[Adran_Marit]

My Switch stealthly updated itself to 7.0 when it was running 6.1 on CFW. I've successfully restored the Boot 0/1 and Nand files and successfully booted back to the state it was at 6.1 so attempted to run CFW again. So I powered it off, put it in RCM mode and loaded ReiNX. I originally used a 32gb microSD to put the nand and boot 0/1 files in for the restore and forgot to remove it and put back the old 64GB that had my games and stuff so when I sent the payload, I saw some orange text on the screen (something about patching) and ReiNX didn't boot.

I then (what it seems like) powered it off, and inserted the original microSD card with my games on it and now I can't get the Switch to detect in RCM mode on TegraRCMGUI and have tried holding the power button down for 10sec, 12 sec, 15 sec, 20 sec, 30 sec and up to 1 minute and can't get the system to boot up. I know the power was in the 90-something percent when it was restoring.

Anyone had this issue and resolved it? I do recall setting up a friend's 6.2 Switch and thought I bricked it (no RCM ready detection, no power, black screen, etc) and was able to get it to boot back up after doing some long power button press and then pressing the home button 1 or 2 times. I've been looking for that link that had that solution and haven't had any luck.

Any help would be greatly appreciated. I'm more than certain that it's not a brick as I was able to boot to stock OFW after restoring it back to 6.0.1.

Thanks in advance!

got reinx.bin on the sd card?