my advice after quite an adventure in downgrade land: just restore nand. It's simple and easy. Don't do anything fancy like using choidujournx to go back... if something goes wrong you will lose hours of your time with a semi-bricked switch. See this: https://gbatemp.net/threads/used-ch...nt-boot-up-anymore.516594/page-2#post-8251620
still not completely out of the woods!!!
Hi,
i have also updated from 3.0 to 5.1 without burning fuses (still 3 burned).
Now i have to send my switch for a repair.
I will flash my console to the firmware 3.0 with my nand backup and hope that it will be sent back to me with this firmware but I doubt it.
My question now is whether it would be possible to restore to Firmware 3.0 when Nintendo will update to 5.1 during the repair.
I know that the bootloader will panic immediately if too many fuses are burnt, but what about booting into RCM Mode and using CFW only?
Since it is possible to update the firmware from 3.0 to 5.1 without burning fuses (bootloader fuse check disabled with exploit) why is it not possible to disable the fuse burn check if we are downgrading?
i have also updated from 3.0 to 5.1 without burning fuses (still 3 burned).
Now i have to send my switch for a repair.
I will flash my console to the firmware 3.0 with my nand backup and hope that it will be sent back to me with this firmware but I doubt it.
My question now is whether it would be possible to restore to Firmware 3.0 when Nintendo will update to 5.1 during the repair.
I know that the bootloader will panic immediately if too many fuses are burnt, but what about booting into RCM Mode and using CFW only?
Since it is possible to update the firmware from 3.0 to 5.1 without burning fuses (bootloader fuse check disabled with exploit) why is it not possible to disable the fuse burn check if we are downgrading?
Yes you could do that, but it would be useless, since you wouldn't really get the benefits from being on 3.0.0.
In essence, if you go back to 3.0 with fuses burnt, you won't be able to boot unless you go through RCM and send a payload, which defeats the purpose of having a 3.0 switch in case an untethered solution arises.
Last edited by Garrincho,
I understand that but the important factor for the untethered solution is the firmware. Would i not be possible to install atmosphere emunand, the untethered solution or whatever advantage we get with the firmware 3.0 within the CFW?
I'm pretty sure that the current -eventual- solution for untethered (deja vu or jamais vu, i get them mixed up) for FWs under 4.1 is a warmboot solution. So you'd have to boot your <4.1 firmware to then launch the cfw/emunand, and if you had to boot your <4.1 firmware through RCM, that'd defeat the whole purpose.
If another coldboot untethered solution arose for your official firmware, then you wouldn't have to worry about downgrading anyways.
Someone correct me if I'm mistaken.
Similar threads
-
-
-
-
-
-
-
-
-
@
SylverReZ:
You can make a post on the DS forum about your findings, and they'll do their best to respond. They have a GBAtemp account here, you know. -
@
Materia_tofu:
oh ye i made a post i did forget they had an account i prob shouldve tagged them in the post+1
tbh -
-
-
-
-
@
BakerMan:
Update on my brother: He's home now, tired and hungry, obviously, but other than that, seems to be doing fine.+2 -
-
-
@
BakerMan:
Well, from what I've heard from my parents, he had a seizure last night, perhaps an epileptic episode, fucking died, had a near death experience, my dad called the paramedics, they showed up, took him to the hospital, and he woke up covered in tubes, and started complaining.
-
-
-
-
-
-
-
