Hacking Question Can I downgrade without a NAND backup?

[blahblah]

I will give that a try, thanks. Just wondering, in order to boot into atmosphere, should I remove the boot.dat file from SX OS and replace it with Atmosphere's? I am using a Mac, so no payload injector for me, I am relaying only on the SX Pro dongle.

You can leave the boot.dat there. Use this website in Chrome to inject the Atmosphere payload: https://fusee-gelee.firebaseapp.com/

Works on a Mac. You must use Chrome for it.

 

[Jellykrop]

You can leave the boot.dat there. Use this website in Chrome to inject the Atmosphere payload: https://fusee-gelee.firebaseapp.com/

Works on a Mac. You must use Chrome for it.

Thank you very much, I will try in a couple of minutes, since I freaked out and decided to launch a NAND backup of my downgraded firmware with Hekate. I will keep you posted

 

[Adran_Marit]

I used ChoiDuJourNX, browsed the 4.0.1 firmware folder containing NCA's, installed it and turned off the console. Then when booting I held vol+ and inserted my dongle, the SX OS boot screen showed up, and I clicked on "boot CFW", then this error message appeared.

did you do the backup?

 

[Jellykrop]

did you do the backup?

I previously had a NAND backup of 4.0.1 which I lost because my hard drive died. So I decided I would downgrade from 6.1 (previously updated with ChoiDuJour) to 4.0.1 in order to re-do a NAND backup, and that I would update right after it's done. But right now, after the "successful" downgrade to 4.0.1 (using ChoiDuJour), I can't boot into CFW (I haven't tried OFW yet), I am getting an error (2002-4315) when trying to do so.

 

[Adran_Marit]

I previously had a NAND backup of 4.0.1 which I lost because my hard drive died. So I decided I would downgrade from 6.1 (previously updated with ChoiDuJour) to 4.0.1 in order to re-do a NAND backup, and that I would update right after it's done. But right now, after the "successful" downgrade to 4.0.1 (using ChoiDuJour), I can't boot into CFW (I haven't tried OFW yet), I am getting an error (2002-4315) when trying to do so.

Alrighty did you do a 6.1 backup? and do you do another backup as soon as you got to 4.

 

[Jellykrop]

Alrighty did you do a 6.1 backup? and do you do another backup as soon as you got to 4.

Yes I do have a NAND backup of 6.1 (but done while autoRCM was still ON, so I worry that the boot sectors might be broken...). I am also currently doing a NAND backup of 4.0.1 using Hekate, for what it's worth... I don't know, it might be useful in the future.

 

[Adran_Marit]

Yes I do have a NAND backup of 6.1 (but done while autoRCM was still ON, so I worry that the boot sectors might be broken...). I am also currently doing a NAND backup of 4.0.1 using Hekate, for what it's worth... I don't know, it might be useful in the future.

okay when you did the 6.1 backup did you backup the boot files as well?

Can I suggest trying kosmos or reinx to see if you can boot 4.0.1 cfw, if not then restore the 6.1 backup only if you have the boot files, else you will to generate them manually

 

[Jellykrop]

okay when you did the 6.1 backup did you backup the boot files as well?

Can I suggest trying kosmos or reinx to see if you can boot 4.0.1 cfw, if not then restore the 6.1 backup only if you have the boot files, else you will to generate them manually

I backed up the boot files for 6.1 but autoRCM was enabled when I did it, so I don't know if they can be restored without going into trouble

 

[Adran_Marit]

I backed up the boot files for 6.1 but autoRCM was enabled when I did it, so I don't know if they can be restored without going into trouble

Yeah they can be restored, hekate will restore the boot files regardless of they state they were in

i.e either autorcm'd or normals

 

[Jellykrop]

Yeah they can be restored, hekate will restore the boot files regardless of they state they were in

i.e either autorcm'd or normals

Alright, but would my console boot after the restore process is complete?

 

[Adran_Marit]

Alright, but would my console boot after the restore process is complete?

By restoring boot and the nand provided they arent corrupt, yes

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

but with autorcm you would need to push the payload as per norm

 

[Jellykrop]

By restoring boot and the nand provided they arent corrupt, yes

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

but with autorcm you would need to push the payload as per norm

Sounds good to me I will try the following : after my backup completes, I will try to boot into another CFW (other than SX OS, maybe Atmosphère), if that works, I will try to update with ChoiDuJour back to 6.1. If that doesn't work, I will try restoring my 6.1 NAND backup (boot sectors + rawnand.bin), I will keep you posted, thank you very much for your help

 

[Jellykrop]

Weird...

 

[blahblah]

Nothing weird about that. Looks fairly normal to me.

 

[Jellykrop]

Atmosphère refuses to boot too.

 

[Jellykrop]

Atmosphère doesn't boot

 

[blahblah]

Atmosphère refuses to boot too.

I can fix this, but it's a lot of work involving running ChoiDuJour on a PC and probably removing the users data from the Switch, including saves. Not sure there is a good tutorial on the site on how to do this -_-.

 

[Kubas_inko]

Atmosphère doesn't boot

Spoiler

 

[Jellykrop]

I can fix this, but it's a lot of work involving running ChoiDuJour on a PC and probably removing the users data from the Switch, including saves. Not sure there is a good tutorial on the site on how to do this -_-.

I think I'm simply going to restore my NAND backup, that will be much easier. Thank you

 

[blahblah]

I think I'm simply going to restore my NAND backup, that will be much easier. Thank you

Np!