Hacking Question Switch bricked and cannot go to RCM

[ly0koS]

Long story short, I was updating my OFW to 11.0.0 , heketa and atmosphere to the lastest. After my update, I found out I cannot boot to my emummc...So I decided to make a new emummc,but also refuse to boot.So I'm thinking I better do a restore.And after restoring my OWN BOOT0/BOOT1 and reboot my switch it refuse to boot up anymore.
Now, it refuse to enter RCM mode although I already enabled autoRCM, and also not booting to OFW.
I connect it to my PC but nothing is picked up.Even no new device was detected.
I have measured my switch's battery voltage and get a reading of 3.23V.
My BOOT0/BOOT1 backup is actually pretty old, as it was backup last year...
So what happened?Did I do anything wrong and brick my switch?

 

[HollowGrams]

Long story short, I was updating my OFW to 11.0.0 , heketa and atmosphere to the lastest. After my update, I found out I cannot boot to my emummc...So I decided to make a new emummc,but also refuse to boot.So I'm thinking I better do a restore.And after restoring my OWN BOOT0/BOOT1 and reboot my switch it refuse to boot up anymore.
Now, it refuse to enter RCM mode although I already enabled autoRCM, and also not booting to OFW.
I connect it to my PC but nothing is picked up.Even no new device was detected.
I have measured my switch's battery voltage and get a reading of 3.23V.
My BOOT0/BOOT1 backup is actually pretty old, as it was backup last year...
So what happened?Did I do anything wrong and brick my switch?

Whenever I get issues like this I check and disable autorcm and test OFW. How did yo update to 11.0? Did you flash nand and boot 0 /1?

 

[ly0koS]

Whenever I get issues like this I check and disable autorcm and test OFW. How did yo update to 11.0? Did you flash nand and boot 0 /1?

Yeah I would like to...But right now I cannot even enter RCM mode my switch show nothing and my PC have got nothing when I plug my switch into it.
I update my OFW using the system update in OFW.
I DO flash my boot0/1 using my old backup

 

[HollowGrams]

Yeah I would like to...But right now I cannot even enter RCM mode my switch show nothing and my PC have got nothing when I plug my switch into it.
I update my OFW using the system update in OFW.
I DO flash my boot0/1 using my old backup

Flash nand and flash boot 0/1 then test.

 

[ly0koS]

Flash nand and flash boot 0/1 then test.

Emmm...But how?My switch won't boot into RCM and cannot be detected by my computer
And can I use my old backup?

 

[HollowGrams]

Emmm...But how?My switch won't boot into RCM and cannot be detected by my computer
And can I use my old backup?

Hold power 15 seconds. Charge for a few hours. Unplug charger. Hold power 15 seconds. Try to send payload again.

 

[ly0koS]

Hold power 15 seconds. Charge for a few hours. Unplug charger. Hold power 15 seconds. Try to send payload again.

My switch is charging now, will try afterward.

 

[ly0koS]

Hold power 15 seconds. Charge for a few hours. Unplug charger. Hold power 15 seconds. Try to send payload again.

Tried but PC no response, not pick up any device.

 

[HollowGrams]

Tried but PC no response, not pick up any device.

Hold power 20 seconds then release - hold volume + on switch tablet and plug cable in - Some switches you have to press power to trigger RCM.

 

[Hayato213]

Long story short, I was updating my OFW to 11.0.0 , heketa and atmosphere to the lastest. After my update, I found out I cannot boot to my emummc...So I decided to make a new emummc,but also refuse to boot.So I'm thinking I better do a restore.And after restoring my OWN BOOT0/BOOT1 and reboot my switch it refuse to boot up anymore.
Now, it refuse to enter RCM mode although I already enabled autoRCM, and also not booting to OFW.
I connect it to my PC but nothing is picked up.Even no new device was detected.
I have measured my switch's battery voltage and get a reading of 3.23V.
My BOOT0/BOOT1 backup is actually pretty old, as it was backup last year...
So what happened?Did I do anything wrong and brick my switch?

You have to restore boot0/boot1 along with the rawnand files that is associated with it. Did you left the unit on AutoRCM?

 

[ly0koS]

You have to restore boot0/boot1 along with the rawnand files that is associated with it. Did you left the unit on AutoRCM?

Yes,I turned AutoRCM on before it bricked

 

[Hayato213]

Yes,I turned AutoRCM on before it bricked

Can you inject hekate? or are you at the state where the computer not picking up the switch in RCM mode, if it is that you can try Zadig 2.4 to try to troubleshoot the driver, recheck your tegra driver.

what is your fuse count and what firmware were those boot0/boot1 and the Rawnand from?

 

[ly0koS]

Hold power 20 seconds then release - hold volume + on switch tablet and plug cable in - Some switches you have to press power to trigger RCM.

First of all,thanks for help!
I have tried that,and I even put my joy-con triger onto my switch.But still my computer cannot pick up my switch,the device manager didn't refresh at all.
I doubt there is something wrong with the switch hardware itself.

 

[Hayato213]

First of all,thanks for help!
I have tried that,and I even put my joy-con triger onto my switch.But still my computer cannot pick up my switch,the device manager didn't refresh at all.
I doubt there is something wrong with the switch hardware itself.

Probably not the switch I assume you either don't have the neccessary driver, or bad cable maybe, check with Zadig 2.4.

 

[ly0koS]

Can you inject hekate? or are you at the state where the computer not picking up the switch in RCM mode, if it is that you can try Zadig 2.4 to try to troubleshoot the driver, recheck your tegra driver.

what is your fuse count and what firmware were those boot0/boot1 and the Rawnand from?

Thanks!Will try Zadig. But I don't think is the driver fault,because like 10 min ago the TegraRCMGUI can detect my switch and after shutdown...no more.
I just update to OFW 11.0.0 and I think that count of fuse is what I have.
I think my boot0/boot1 is 8.1.0 or something like that.

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

These are all the devices showed it Zadig...
I have changed both cable (CtoC and CtoA) and usb port(both 2.0 and 3.0)

 

[Hayato213]

It is one of the two usb devices, you need the libusbK driver I believe.

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

Did you only restore boot0/boot1?

 

[ly0koS]

It is one of the two usb devices, you need the libusbK driver I believe.

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

Did you only restore boot0/boot1?

YES! And I believe that two usb device are ALL my keyborad. Because when I unplug my switch, these two device still show up in the list.
And I have low hope on driver fault because when I plug my switch into my pc, my pc don't play that "Found new device" sound.
Also I observed my device manager, no refresh when I plug/unplug my switch.
Do restore different version of boot0/boot1 will cause a brick? Which even prevent it boot into RCM?

 

[Hayato213]

YES! And I believe that two usb device are ALL my keyborad. Because when I unplug my switch, these two device still show up in the list.
And I have low hope on driver fault because when I plug my switch into my pc, my pc don't play that "Found new device" sound.
Also I observed my device manager, no refresh when I plug/unplug my switch.
Do restore different version of boot0/boot1 will cause a brick? Which even prevent it boot into RCM?

Yes it cause brick if it is not the matching version, restoring a wrong boot0/boot1 that doesn't match with the NAND is a brick, where the NAND refuse to boot.

 

[ly0koS]

Yes it cause brick if it is not the matching version, restoring a wrong boot0/boot1 that doesn't match with the NAND is a brick, where the NAND refuse to boot.

Ok, that's fair, but in my understanding , the RCM is the mode of recovery, now that also refuse to boot...
I'm totally confused...

 

[Hayato213]

Ok, that's fair, but in my understanding , the RCM is the mode of recovery, now that also refuse to boot...
I'm totally confused...

You can try using a jig, hold Volume Up and press the Power button just in case you are not in AutoRCM, and see if you can load up Hekate. Your situation has nothing to do with RCM mode, if you did restore the wrong boot0/boot1 without restoring NAND.