- Joined
- Mar 29, 2018
- Messages
- 41
- Trophies
- 0
- Age
- 26
- Location
- Australia
- Website
- www.youtube.com
- XP
- 190
- Country
this happened to me couple days back, except im on 3.0.1
- backed up 3.0.1 nand incase choixdujoir messes my system
- i used choixdujour to upgrade to 5.1.0 with autorcm
- downgraded back to 3.0.1
- when i booted up i had the same error, (semi-bricked?)
- i restored my 3.0.1 nand i backed up before using choixdujour
- system is back to normal
- checked my fuses with briccmii and i had 4 before and 4 after
- backed up 3.0.1 nand incase choixdujoir messes my system
- i used choixdujour to upgrade to 5.1.0 with autorcm
- downgraded back to 3.0.1
- when i booted up i had the same error, (semi-bricked?)
- i restored my 3.0.1 nand i backed up before using choixdujour
- system is back to normal
- checked my fuses with briccmii and i had 4 before and 4 after
I am not sure what you mean. How do you initialize the switch after (or before... not clear on this one) you downgrade with choidujour?
--------------------- MERGED ---------------------------
ok, so time for an update. After getting in touch with Canna (thanks mate for staying up so darn late. You gave me 3 hours of help dude. You really are awesome!!!) and spending a few hours investigating what happened. We still aren't sure about the cause of my semi-brick. We tried going back to firmware 5.0.2 (exfat) by using hackdiskmount and etcher. We did everything right but for some odd reason I would only get a black screen (I later found out that Canna's hunches were right, everything was done perfect but my sd cart formated to exfat was the issue). We then decided to use Hekate to restore my backup nand. However, rather than restore the full nand which was time consuming we opted to use "restore GPP partitions" and "restore Boot0/1." This worked and I could now boot into Horizon. I thought everything was great... however, some more problems arose...
Firstly, I repeated the same steps I initially did when I decided to install cfw. I upgraded using the same firmware files to 5.0.2 with exfat. I used Choidujournx. I booted Rajnx cfw as well. I proceeded to try and install DKC:TF in nsp format. Unfortunately, when it came time to load it after the installation, it stalled. This same file worked before my semi-brick. I tried oceonhorn and it also crashed trying to load the game. I should mention that the versions of 4nxci and tinfoil I used are the exact same ones as before so it is not them.
I think that after this fun adventure I am simply going to do a full NAND restore and cross my fingers. I will be following Canna's guide to do this. I will retrace all my steps from earlier when I first installed CFW and see if my Switch gets back to speed...
Last edited by udo4ever,
enter maintenance mode and select the "initialize console" option, is what i mean.
huh? how does that make any sense? you'd have to do it again after downgrading anyway.
Update 2:
so I did a full Nand restore and retraced my steps to get a full cfw. Everything works the way it did before my brick.
Moral of the story. If you want to downgrade, save yourself a heck of a lot of time and frustration and just do a complete Nand restore. Either be ready to part with your saves or back them up. Either way, you will still have to reinstall all your NSPs again which is a bummer especially if you only have XCI files....
so I did a full Nand restore and retraced my steps to get a full cfw. Everything works the way it did before my brick.
Moral of the story. If you want to downgrade, save yourself a heck of a lot of time and frustration and just do a complete Nand restore. Either be ready to part with your saves or back them up. Either way, you will still have to reinstall all your NSPs again which is a bummer especially if you only have XCI files....
didn't wanna transfer that content folder then lol,, still have not found no info on the black screen,, i honestly think it may be due to the autorcm as i think i removed that from @Mat37 console after i restored it cause it didn't wanna boot, but booted normally after we removed autorcm But i cant remember.... Your welcome and im so freaking tired but your worth it budd, we got your switch working i guess
And before you say guys yes i know you get black screen with rcm im not stupid, we couldnt load the os..
Last edited by Canna,
I think that's just because we forgot autoRCM was well .. automatically installed when updating with rajkosto's guide
hahaha Canna,
no, no, you fixed my switch actually!!! when it was booting to the black screen it had nothing to do with what you did in in terms of partitions and such. If I had simply listened to your hunch and formated my sd card to fat32 I am 100% sure we would have gotten it going without resorting to Nand restore. Here's why. When restoring my full nand and using cfw for the first time it gave me the very same black screen. I ejected my sd card and it booted. properly. I then formated the sd card to fat32 and everything worked a ok. don't know if I am making sense but you got it going. Whatever it was, the black screen thing had something to do with the type of partition on my SD card.
On a side note, I have no doubt you are tired. I feel real bad about that. I can't thank you enough for showing me some really neat things too. Mad props to you!
Did you run briicmi and toggle the bricc state, I had a similar problem and that's what I had to do, something to do with bis key 0? Idk.
But we used the exfat support and the outputted kip file from choirdujour...
Mr wizard mentioned the bricmii which is what i used on @Mat37 nand restore.. i think were missing a snippet of information some were, im sure rajkosto mentioned some were that we need to do something if we get black screen.. but nothing like that is mentioned in the non burn fuse guide...
But hey we got your nand restored we can start a fresh from there.
And also lets call it solved i dont want countless replies or problem solving unless some one has the 100% correct answer...
Remember girls and boys playing with your nand is a dangerous business, backup your system before you even think of getting dirty with it you animals.
Last edited by Canna,
Also this:
2. TRY TO KEEP YOUR SETTINGS (Experimental, might NOT result in a properly working firmware when downgrading):
Source: https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/
2. TRY TO KEEP YOUR SETTINGS (Experimental, might NOT result in a properly working firmware when downgrading):
Source: https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/
I have tried both methods keep or remove and still same. i solved it before with maty i was just too tired to remember this time. This is solved now..Just not the black screen, after we did everything right. weird. end of please
Sorry, I stand corrected. I always thought since you'll end up soft bricked after downgrading without initializing first, you cannot do the initialization after.
Sent from my SM-G950F using Tapatalk
You boys are playing with fire. You'll end up with a brand new paperweight.
There is 0 incentive to downgrade right now for the average user. If a exploit in a older firmware is found, by that time the tools like hekate and ChoiDujourNX will much more refined and bugfixed.
There is 0 incentive to downgrade right now for the average user. If a exploit in a older firmware is found, by that time the tools like hekate and ChoiDujourNX will much more refined and bugfixed.
This is the right answer. You do NOT need to restore your NAND. Just hold down power for 12 seconds to turn off your device. Hold +/- volume and hit power. Keep holding +/- until you get to the initialization menu.
I've downgraded numerous times with ChoiDujourNX without initializing. I used the reboot function in the homebrew and I've been able to load firmwares from 6.0 to 3.0.2 without initialization.
Similar threads
- Solved
![[Truth]](/data/avatars/s/37/37733.jpg?1351072321){kind=avatar}
-
Xdqwerty
what are you looking at? -
K3Nv2
-
The Real Jdbye
*is birb*
-
-
-
-
-
-
-
-
-
@
K3Nv2:
I can think of the design teams process another joystick and no audio or a joystick and mono audio
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
