Hacking Did I destroyed my switch?

[XaneTenshi]

you know, this has been bothering me for a while now, if a nand restore requires a boot0/1 backup so much, why is it not automatically backed up when you do a rawnand?
I'd bet so much money half the people with a nand backup never backed boot0/1...

I've actually had a similiar thought. Why is it that so many people ONLY backup rawnand.bin, when the boot files backup option is clearly stated under "Full backup" in Hekate, same as rawnand. Actually, what even makes people think that rawnand.bin is the only file they need in the first place?

EDIT. With that being said, I do see your point...

 

[Cencil]

You should backup your 6.2 man. Never do nothing drunk its a bad idea ;(

Well, he did something.

 

[radicalwookie]

I find lack of grammatical knowledge in this thread disturbing

 

[barbarpappa1]

I find lack of grammatical knowledge in this thread disturbing

I’m sorry but my native spoken language isn’t English.

 

[Zaybokk]

as long as you have prodinfo, it is repairable.

wait ...what?.. i have mine as well.. so exactly what can this do??

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

Isn't this why people are updating their firmware that special way that don't burn fuses so that they then can downgrade without killing their machines?
I think I heard that a machine that has too many fuses burnt for it's firmware version will get a bluescreen of death.
If you have a nand backup from 6.2 maybe there is a way to upgrade to that and bring your switch back to life?

yes he can do a firmware recovery to OFW 6.2.0 by lan connection with adapter and or by simple holding recovery firmware boot then a special boot screen will appear to recover his firmware to latest OFW, then he can properly downgrade as needed but just remember to take sd card in case it can possibly erase or format it while in firmware recovery ......

 

[barbarpappa1]

yes he can do a firmware recovery to OFW 6.2.0 by lan connection with adapter and or by simple holding recovery firmware boot then a special boot screen will appear to recover his firmware to latest OFW, then he can properly downgrade as needed but just remember to take sd card in case it can possibly erase or format it while in firmware recovery ......

That sounds interesting! I would really like to restore my switch to OFW 6.2 as I don't care about being able to run CFW on it now.
have you seen a guide for this? or can you point me the right way? I do have a usb to lan adapter.

 

[PrEtZaL]

I also tried that guide yesterday. got error with keys.txt and later gave up.
There is no way to retrieve the keys with 8 burnt fuses it seems. I always get error with biskeydump and it cant retrieve the tsek key.
I am out of ideas atm.

Its your boot0/boot1 files you need to use memloader and etcher to write to them using choidujour then run custom kip

 

[barbarpappa1]

Its your boot0/boot1 files you need to use memloader and etcher to write to them using choidujour then run custom kip

Thank you for your suggestion but I am really tired of spending hours and hours trying to fix this
I'd rather just restore it to OFW and sell it. I have another switch on firmware 3.02 that works perfect for CFW

 

[Zaybokk]

That sounds interesting! I would really like to restore my switch to OFW 6.2 as I don't care about being able to run CFW on it now.
have you seen a guide for this? or can you point me the right way? I do have a usb to lan adapter.

dont need a lan adapter unless you never had wifi on it before?. it really depends.. do this button combination:

1. Turn off the console by pressing the power button on top of the console for five seconds.
2. Press POWER button + Volume Up + Volume down at the same time.
3. Release all buttons when the Switch logo appears on the screen.
4. The console should now be in recovery mode with the option to update.
5. You're now Back to Stock OFW 6.2.0 firmware.

 

[barbarpappa1]

dont need a lan adapter unless you never had wifi on it before?. it really depends.. do this button combination:

1. Turn off the console by pressing the power button on top of the console for five seconds.
2. Press POWER button + Volume Up + Volume down at the same time.
3. Release all buttons when the Switch logo appears on the screen.
4. The console should now be in recovery mode with the option to update.

ok. That I've tried many times. It just don't work for me. The switch logo never appears.

 

[PrEtZaL]

Thank you for your suggestion but I am really tired of spending hours and hours trying to fix this
I'd rather just restore it to OFW and sell it. I have another switch on firmware 3.02 that works perfect for CFW

Get discord and Ill run you through it. it'll take a few minutes
https://discord.gg/F7zjDK

 

[Kubas_inko]

wait ...what?.. i have mine as well.. so exactly what can this do??

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



yes he can do a firmware recovery to OFW 6.2.0 by lan connection with adapter and or by simple holding recovery firmware boot then a special boot screen will appear to recover his firmware to latest OFW, then he can properly downgrade as needed but just remember to take sd card in case it can possibly erase or format it while in firmware recovery ......

Sorry. I never looked into it, I just know it is possible. I think downgrade guide is actually it. So this might be it???

 

[Canna]

you know, this has been bothering me for a while now, if a nand restore requires a boot0/1 backup so much, why is it not automatically backed up when you do a rawnand?
I'd bet so much money half the people with a nand backup never backed boot0/1...

Cause its stored in a different partition or part of nand then the system files/ rawnand. this is another reason why i made a full backup guide to make sure users back up everything on there switch. and save there ass when it comes to moments like this....

as for original post ... you should restore ya dump your 5.1 to the switch use the hekate to boot the console every time,into stock or cfw which ever you prefer.
you then have a couple of options ...
Run hekate everytime and boot with 5.1

Or

boot with the 5.1 dump then update officially or by using choirdujour nx to 6.2
the choice is yours to be honest tho if you already was on 6.1/6.2 then you already have burnt fuses so doesn't matter if you use hekate now or not as hekate is a fusecheck bypass.and your most probally on 6.1/6.2 fuse count..

Remember kiddies and folks always make a backup and it does not matter the version as any version will save your ass some day... always nice to have a current backup for convenience...

BACKUP GUIDE AND RESTORE GUIDE HERE PASS IT ROUND FOLKS THANKS

Click Me​

 

[Clydefrosch]

yeah but you know not everyone ready your guide on here.
many don't read any guides at all or just the shortended 'get a backup'.
and with boot01 taking like 2 seconds to do, it could just be automatic every time

 

[Zaybokk]

Cause its stored in a different partition or part of nand then the system files/ rawnand. this is another reason why i made a full backup guide to make sure users back up everything on there switch. and save there ass when it comes to moments like this....

as for original post ... you should restore ya dump your 5.1 to the switch use the hekate to boot the console every time,into stock or cfw which ever you prefer.
you then have a couple of options ...
Run hekate everytime and boot with 5.1

Or

boot with the 5.1 dump then update officially or by using choirdujour nx to 6.2
the choice is yours to be honest tho if you already was on 6.1/6.2 then you already have burnt fuses so doesn't matter if you use hekate now or not as hekate is a fusecheck bypass.and your most probally on 6.1/6.2 fuse count..

Remember kiddies and folks always make a backup and it does not matter the version as any version will save your ass some day... always nice to have a current backup for convenience...

BACKUP GUIDE AND RESTORE GUIDE HERE PASS IT ROUND FOLKS THANKS

Click Me​

does this apply to 6.2.0?..
or only firmware lower than this one?.. or possible if you have keys.txt? or hactool key file?

 

[Canna]

does this apply to 6.2.0?..
or only firmware lower than this one?.. or possible if you have keys.txt? or hactool key file?

Not sure what your asking me here but what i said should work with
All

the main things to backup on your switch are the
biskeys
prodinfo
prodinfo f
rawnand/or sys partitions.
boot1/0

With those you can pretty much do anything to your switch and still be able to recover it

 

[Zaybokk]

Not sure what your asking me here but what i said should work with
All

the main things to backup on your switch are the
biskeys
prodinfo
prodinfo f
rawnand/or sys partitions.
boot1/0

With those you can pretty much do anything to your switch and still be able to recover it

okay, i have all them, and probably then some..
but my issues is trying to downgrade from 6.2.0 to 6.1.0
alot of people saying you can with ChoiDujour.exe ,
but i tried this countless times with and without hacktool keys file still same errors, no success??..
so. im lost at this point...... any help be grateful guys thanks.. please stop referring me that same guide like a 100 times because i tried that guide followed it to the t but still a no go... getting the errors on command line when i do this one:

1. In the command prompt, type "ChoiDujour.exe --keyset=keys.txt fw" without quotes
   • If ChoiDujour says it cannot find firmware files or keys.txt, you likely put keys.txt or the firmware files in the wrong location. Try steps 1.9-1.13 again.
   • If the script fails otherwise, your keys.txt may be incompatible with ChoiDujour.
2. Once finished, you should see a message similar to "All files verified! Prepared firmware update is in folder NX-6.1.0" in the command prompt. Make sure you can find this folder, it will be used later.
3. following this guide : https://guide.sdsetup.com/#/manual620downgrade
4. as i said stuck at that point.. and read on some other threads , other ones same as me too..

you**-With those you can pretty much do anything to your switch and still be able to recover it:
apparently not..

 

[Canna]

okay, i have all them, and probably then some..
but my issues is trying to downgrade from 6.2.0 to 6.1.0
alot of people saying you can with ChoiDujour.exe ,
but i tried this countless times with and without hacktool keys file still same errors, no success??..
so. im lost at this point...... any help be grateful guys thanks.. please stop referring me that same guide like a 100 times because i tried that guide followed it to the t but still a no go... getting the errors on command line when i do this one:

1. In the command prompt, type "ChoiDujour.exe --keyset=keys.txt fw" without quotes
   • If ChoiDujour says it cannot find firmware files or keys.txt, you likely put keys.txt or the firmware files in the wrong location. Try steps 1.9-1.13 again.
   • If the script fails otherwise, your keys.txt may be incompatible with ChoiDujour.
2. Once finished, you should see a message similar to "All files verified! Prepared firmware update is in folder NX-6.1.0" in the command prompt. Make sure you can find this folder, it will be used later.
3. following this guide : https://guide.sdsetup.com/#/manual620downgrade
4. as i said stuck at that point.. and read on some other threads , other ones same as me too..

you**-With those you can pretty much do anything to your switch and still be able to recover it:
apparently not..

Send me your commands you are typing into the cmd prompt please and il point out or correct

 

[Zaybokk]

Send me your commands you are typing into the cmd prompt please and il point out or correct

okay, just sec..
here are the pics of them:
oh, and i have more too.. this is just the first ones.. or maybe main ones shall i say....

 

[Canna]

okay, just sec..
here are the pics of them:
oh, and i have more too.. this is just the first ones.. or maybe main ones shall i say....

Your first folder is correct and apperas to be running correctly can you post a pic of your folder structure,, ? you do have hactools files in the same folder of choidujour dont you ? if so then your keys.txt files is not good enough and you should find another