need help after doing the worst mistake i could.

[Cookz]

this happened about 2 years ago now. i was trying to restore my switch from its cfw state back to ofw. i did what i should and did the reverting to backup for the raw gpp, then i made the mistake of accidentally rebooting the console before reverting to the backed up boot files. i immediately turned it off again and redid the entire backup but to no avail. ever since its been stuck on the switch logo whenever i tried to boot it. i was still able to boot into hekate but never further that that. now it wont even turn on at all anymore, tho i dont know if thats an issue with the battery. ive had this issue on the backburner looking for an answer to what i could do. im considering replacing the motherboard but id rather know that would fix it before buying one. thanks in advance

 

[tech3475]

If it's been two years, I would first just leave it on charge for a while.

Second, I would try to get back into Hekate and check your fuse counts VS what OFW version you have on the backup.

 

[randy_w]

Also if you had autorcm or the switch is chipped, leave it on official charger overnight, they will charge very slowly if stuck in rcm mode

 

[Cookz]

If it's been two years, I would first just leave it on charge for a while.

Second, I would try to get back into Hekate and check your fuse counts VS what OFW version you have on the backup.

i dont have the backup anymore at this point... i remember the firmware version being something after 15

 

[tech3475]

i dont have the backup anymore at this point... i remember the firmware version being something after 15

If the fuse count is above what the OFW expects, it wont boot.

It should be possible to update via CFW.

 

[Cookz]

If the fuse count is above what the OFW expects, it wont boot.

It should be possible to update via CFW.

i don't know how to do that

 

[petspeed]

Boot Sys CFW and use Daybreak to install the desired firmware version. You need to download the firmware first. Google to find it, we are not allowed to link to it here.

 

[Cookz]

Boot Sys CFW and use Daybreak to install the desired firmware version. You need to download the firmware first. Google to find it, we are not allowed to link to it here.

but if i cant get any further than hekate? what am i supposed to do?

 

[petspeed]

If the issue is because of fuse count then you should be able to boot yhrough Atmosphere.

 

[tech3475]

but if i cant get any further than hekate? what am i supposed to do?

AFAIK if it's the fuse count (I believe this is viewable via Hekate), you need to boot to CFW, update sysnand and then you should be boot ofw.

Note: I don't know how safe this method will be for online afterwards.

Regardless, make a fresh backup before doing anything.

 

[Cookz]

AFAIK if it's the fuse count (I believe this is viewable via Hekate), you need to boot to CFW, update sysnand and then you should be boot ofw.

Note: I don't know how safe this method will be for online afterwards.

Regardless, make a fresh backup before doing anything.

but the issue is that i couldn't boot no matter if its ofw or cfw

 

[tech3475]

but the issue is that i couldn't boot no matter if its ofw or cfw

Just to confirm, you're running a compatible version of Atmosphere?

 

[Cookz]

AFAIK if it's the fuse count (I believe this is viewable via Hekate), you need to boot to CFW, update sysnand and then you should be boot ofw.

Note: I don't know how safe this method will be for online afterwards.

Regardless, make a fresh backup before doing anything.

this is as much as i can provide as i haven't found the sd card yet

 

[Deleted member 702243]

Also if you had autorcm or the switch is chipped, leave it on official charger overnight, they will charge very slowly if stuck in rcm mode

idk why anyone ever even does this, just hold down power for 30 sec after plugging in and you'll guaranteed be out of rcm and able to charge normally

it doesn't need to be 30 seconds, but 30 seconds guarantees that it will have been long enough

 

[randy_w]

idk why anyone ever even does this, just hold down power for 30 sec after plugging in and you'll guaranteed be out of rcm and able to charge normally

it doesn't need to be 30 seconds, but 30 seconds guarantees that it will have been long enough

no it won't. if autorcm is enabled it will always boot into rcm and charge very slowly. with modchip it might get out of rcm if battery has enough charge for the modchip to finish glitching, but if it's completely dead it won't get out of rcm mode until battery has enough charge

 

[The Real Jdbye]

but the issue is that i couldn't boot no matter if its ofw or cfw

Most likely it's just out. Like others have said, it takes a while to get the console to turn on if it runs out of battery with AutoRCM turned on.

As for being stuck on the boot logo, if the boot partitions are mismatched with the firmware version, luckily it's not difficult to make replacement boot0/boot1 files without a backup. If you downgraded the firmware and the fuse count doesn't match, you'll have to upgrade again. Rest assured, both of those things are fixable using RCM. But first of all, you need to leave it on charge and get into Hekate again.

 

[jkyoho]

FUSE count 18 you should be on 16~16.1.0 HOS

 

[Cookz]

Most likely it's just out. Like others have said, it takes a while to get the console to turn on if it runs out of battery with AutoRCM turned on.

As for being stuck on the boot logo, if the boot partitions are mismatched with the firmware version, luckily it's not difficult to make replacement boot0/boot1 files without a backup. If you downgraded the firmware and the fuse count doesn't match, you'll have to upgrade again. Rest assured, both of those things are fixable using RCM. But first of all, you need to leave it on charge and get into Hekate again.

im able to get into hekate i just need to find my sd card with the files

Post automatically merged: Nov 18, 2024

managed to get into hekate but i cant get any further than that

 

[Deleted member 702243]

no it won't. if autorcm is enabled it will always boot into rcm and charge very slowly. with modchip it might get out of rcm if battery has enough charge for the modchip to finish glitching, but if it's completely dead it won't get out of rcm mode until battery has enough charge

yes, boot into rcm. if you force power off then it powers back off... and guess what, the cable is connected, making it charge

why do people still repeat this bullshit even in 2024, you can try this so easily for yourself. power off, plug into your computer with tegrarcm or something, and hold power off for a while. it will disconnect while still connected to usb, and charge normally because it's not in rcm anymore

think for like 5 seconds before you speak, hardware isn't magic and doesnt just magically power on for no reason after powering it off

you plug it in, plugging it in makes it power on into rcm. hence why you hold power button to power it back off

 

[randy_w]

yes, boot into rcm. if you force power off then it powers back off... and guess what, the cable is connected, making it charge

why do people still repeat this bullshit even in 2024, you can try this so easily for yourself. power off, plug into your computer with tegrarcm or something, and hold power off for a while. it will disconnect while still connected to usb, and charge normally because it's not in rcm anymore

think for like 5 seconds before you speak, hardware isn't magic and doesnt just magically power on for no reason after powering it off

you plug it in, plugging it in makes it power on into rcm. hence why you hold power button to power it back off

I don't know if you can't read or just don't know what autorcm is or how it works, but before you calling something you don't know bullshit, do some basic research or you are just embarrassing yourself.

Again, if battery's completely dead on a switch with autorcm, there's no way to get out of it other than leaving it charging in rcm. It will charge, but very slowly. It will only get recognized by tegrarcm and accept a payload when battery has enough charge. Same for chipped switch, it will only boot when battery has enough charge for the glitching process to finish. On a completely dead battery, protection circuit will cut off its output to protect the cell, and it takes time for the cell to charge up till cell voltage reaches the threshold (2.5v iirc) to reactive output. How long this process takes depends on how dead the battery is, if it's completely dead it could take several hours to reactivate the battery, that's why people always say leave it charging overnight.

As for your method, holding the power button to force it off doesn't magically charge the battery and reactivate its output, so it will never work on a completely dead battery

Post automatically merged: Nov 19, 2024

managed to get into hekate but i cant get any further than that

If you don't have a matching dump of the firmware matching fuse count, you need to dump your own prod.keys and use emmchaccgen to generate system titles, then use nxnandmanager to restore them. sthetix has several unbrick guides, i think you need to use level 2 guide since you have your old dump and your own prod.keys