You can now. 10 is the limit.Alright sounds great, I just need to make some more forum posts to be able to send messages
@Jeppe
blank screen after choidujor,is auto rcm....
as auto rcm is applied automatically to the outputted boot1/0
biskey and mismatch, wont boot
place ; in front of Encrypted_header_key
in keys.txt /prodkeys to bypass
example
; Encrypted_header_key = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Also check out my posts on bricking ,responses , in my profile CLICK HERE
and read through my thread here CLICK ME for restoring and error fixes check the user comments and my responses on the thread...
What you need to do is rebuild your nand...
to do this you make a copy of any of your known working backups 5.0 /6.1 /7.0 etc so you can build a nand without having to worry about breaking your original backup
So with your copy of your nand backup
use hacdiskmount and choidujour to rebuild your nand to 7.0
when you first boot it will go black cause choidujour makes or applies autorcm to the boot0/1 so you dont burn fuses..
Now...
If you dont have a 7.0 backup dont worry use the 5.0 6.0 or what ever backup you have rebuild it like i said above to 7.0...
and you can use the original 7.0 boot 0/1 as you wont burn fuses as your on 9 burnt already...
To fix your boot0/1 or a blank screen after choidujour use briccmii to bricc your boot0/1 first then un brick and brick it again...
lower system version below your fuse count like 6.0 5.0 4.0 and down anything before 7 will not boot unless you boot it with hekate and if the restore is correct and not corrupt,,
so from what you have told me your biskeys dont match so your backup or your restore is corrupt and wont boot regardless..
So to recap
Search through my guide thread i think i posted process of what to do, or visit this link and rebuild any old good backup nand and update /rebuild it to 7.0..
Check ya biskeys match before transfering to switch....
Hekate only restores in exfat formatted sd card ...
Good luck..
Make a backup of your nand before you experiment...
Stop downgrading, and get as much information as you can...
blank screen after choidujor,is auto rcm....
as auto rcm is applied automatically to the outputted boot1/0
biskey and mismatch, wont boot
place ; in front of Encrypted_header_key
in keys.txt /prodkeys to bypass
example
; Encrypted_header_key = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Also check out my posts on bricking ,responses , in my profile CLICK HERE
and read through my thread here CLICK ME for restoring and error fixes check the user comments and my responses on the thread...
What you need to do is rebuild your nand...
to do this you make a copy of any of your known working backups 5.0 /6.1 /7.0 etc so you can build a nand without having to worry about breaking your original backup
So with your copy of your nand backup
use hacdiskmount and choidujour to rebuild your nand to 7.0
when you first boot it will go black cause choidujour makes or applies autorcm to the boot0/1 so you dont burn fuses..
Now...
If you dont have a 7.0 backup dont worry use the 5.0 6.0 or what ever backup you have rebuild it like i said above to 7.0...
and you can use the original 7.0 boot 0/1 as you wont burn fuses as your on 9 burnt already...
To fix your boot0/1 or a blank screen after choidujour use briccmii to bricc your boot0/1 first then un brick and brick it again...
lower system version below your fuse count like 6.0 5.0 4.0 and down anything before 7 will not boot unless you boot it with hekate and if the restore is correct and not corrupt,,
so from what you have told me your biskeys dont match so your backup or your restore is corrupt and wont boot regardless..
So to recap
Search through my guide thread i think i posted process of what to do, or visit this link and rebuild any old good backup nand and update /rebuild it to 7.0..
Check ya biskeys match before transfering to switch....
Hekate only restores in exfat formatted sd card ...
Good luck..
Make a backup of your nand before you experiment...
Stop downgrading, and get as much information as you can...
Last edited by Canna,
So I finally got it up and running again, thanks to personal help (PM's) from PrEtZaL.
The problem was, that my system and user partitions had somehow become corrupted (possibly a bad nand backup) and my biskeys didn't match.
I wont put down what I did to fix it, because as PrEtZaL says it was very unconventional and a rare situation, and others duplicating it might result in bricking their Switch. So what I did is a last resort when everything else has been tried.
But PrEtZaL truly is a genius and fixed my messed up Switch
The problem was, that my system and user partitions had somehow become corrupted (possibly a bad nand backup) and my biskeys didn't match.
I wont put down what I did to fix it, because as PrEtZaL says it was very unconventional and a rare situation, and others duplicating it might result in bricking their Switch. So what I did is a last resort when everything else has been tried.
But PrEtZaL truly is a genius and fixed my messed up Switch
good news! i like seeing these threads have a good ending!
now delete all wifi connections and never access the net again and you should never get into this strife again.
i suggest you add 90dns before using any wifi again to prevent any more mishaps. i use it and i couldnt update even if i tried too.
congrats on getting your system sorted and its good to see ppl like pretzal helping out us noobs. people like preztal make the scene a positive place!
congrats!
now delete all wifi connections and never access the net again and you should never get into this strife again.
i suggest you add 90dns before using any wifi again to prevent any more mishaps. i use it and i couldnt update even if i tried too.
congrats on getting your system sorted and its good to see ppl like pretzal helping out us noobs. people like preztal make the scene a positive place!
congrats!
Hi all,
I think I have owned (2nd hand) a bricked switch as well
When I try to start the Switch, the screen remains black and RCM is activated. I have then injected the latest hektate payload and could see that already 6 fuses are burnt, so I guess FW 5.0 is installed. When I try to start CFW or OFW (stock) with hektate, I get a PGK1 unkown version error. When I use the biskeydump tool, I only get two keys for HWI and SBK. The TSEC key can't be read, I tried all available biskeydump versions. My last hope is to update the FW to a higher version likle 6.1 or higher. But without TSEC key, this seems to be impossible. Do you have any idea how to proceed?
Thanks for any ideas,
Dary
P.S: I made a full NAND backup as well as BOOT0 and BOOT1 sectors in the current state, but I guess this won't help much here...
I think I have owned (2nd hand) a bricked switch as well
When I try to start the Switch, the screen remains black and RCM is activated. I have then injected the latest hektate payload and could see that already 6 fuses are burnt, so I guess FW 5.0 is installed. When I try to start CFW or OFW (stock) with hektate, I get a PGK1 unkown version error. When I use the biskeydump tool, I only get two keys for HWI and SBK. The TSEC key can't be read, I tried all available biskeydump versions. My last hope is to update the FW to a higher version likle 6.1 or higher. But without TSEC key, this seems to be impossible. Do you have any idea how to proceed?
Thanks for any ideas,
Dary
P.S: I made a full NAND backup as well as BOOT0 and BOOT1 sectors in the current state, but I guess this won't help much here...
Last edited by Dary,
Hello
great that you solved your problem
I think I have the same one could you please help me ?
I get a black screen after the nintendo logo (currently on 8.0.1)
I did an old nand back (4.1) and boot0/1 but still nothing (it is now downgraded I think)
I've tried using choidujour pc but my biskeys are incompatible or something
please help me thank you
Need more info on your downgrade and how you are booting your cfw.
Hekate, Tegra?
Atmosphere, SX, ReiNX?
Fuses burnt?
SD card formatted fat32 or exfat?
I had a 4.1 switch using a fat32 sd card with kosmos/atmosphere
after a bootloop problem I restored my boot0/1 and solved the issue
I then updated to 8.0.1 and was using latest kosmos/atmosphere on an exfat card
played for 2-3 months but not I get a black screen after the nintendo logo on ofw and cfw
tried to restore boot0/1 nothing
tried my old backup nand (4.1.0) still nothing
tried using choidujour I wasn't working until earlier
tried using 4.0.1
followed all the steps but still nothing after the nintendo logo ( when I try to Launch> FS_410-exfat_nocmac_nogc)
I believe I have 9 fuses burnt
thank you
.
Did you try step 14 of this? https://switch.homebrew.guide/usingcfw/manualchoiupgrade
Do you have custom themes on your sd card?
Was it reformated with only the latest bare minimum cfw files on it when you try to boot 4.1?
Last edited by Philliyxx,
yes I did try step 14
no, no themes
what do you mean by bare minimum cfw files ?
I tried booting with only hekate_ipl.ini + fs401exfat on fat32 and exfat sd card
Slow format the card to fat32. Put only atmosphere on it. Push the fusee primary payload from hekate or tegragui/smash. Let us know what happens
Last edited by Philliyxx,
Hmm try 0.8.9 version of atmosphere.
https://github.com/Atmosphere-NX/At....8.9-master-8c3dae84+hbl-2.1+hbmenu-3.0.1.zip
Similar threads
