hmm does it showup with anything else? Like the gui rcm injector tool? Or HacDiskMount?It shows also in my system settings that the console is connected.
But it shows a driver error (Treiberfehler=driver error).
View attachment 280050
It doesn't get showed in HacDiskMount.hmm does it showup with anything else? Like the gui rcm injector tool? Or HacDiskMount?
Try going to the settings in Etcher and enable "Unsafe Mode" That might make it show up or try in admin mode.It doesn't get showed in HacDiskMount.
But TegraRCM works still fine, I can load my payloads.
The problem is that BaleaEtcher don't find the System.
View attachment 280052
This information might be helpful (found in another thread)It shows also in my system settings that the console is connected.
But it shows a driver error (Treiberfehler=driver error).
View attachment 280050
Get your Switch into RCM mode, send the memloader.bin payload to it
On the switch's screen, navigate to ums_boot0.ini using the volume buttons, then launch it with the Power Button.
The screen should stay illuminated but black. Open your Device manager, check if you see "LINUX UMS DISK 0" under the "Disks" tree branch
If not, you should uninstall any devices that have a yellow warning icon (when uninstalling devices, make sure to check the "Delete driver software for this device" box too)
Also uninstall the device the same way if it's showing up as a "USB Download Gadget".
After device uninstallation (which you perform by right clicking in Device manager and choosing Uninstall), rescan the device manager list by clicking on the last icon in the toolbar.
The "LINUX UMS DISK 0" Disk should now be there. If it still has a yellow warning, uninstall it again, or shut down the switch (by holding the power button for 12 seconds), and try RCM->memloader again
Open Etcher. Click Select image and browse to the BOOT0.BIN inside the GENERATED NX-X.X.X folder from ChoiDujour (not your original BOOT0.bin backup you might still have somewhere)
If this dialog shows up, simply click Continue (what does Etcher know, anyway?)
Thank you, I can see the device now with the name in the Devicemanager but BalenaEtcher don’t show it.This information might be helpful (found in another thread)
How can I get into this "unsafe mode"?Try going to the settings in Etcher and enable "Unsafe Mode" That might make it show up or try in admin mode.
open Etcher and click the gear on the top right, it's the last option.How can I get into this "unsafe mode"?
Thank you,FOLLOW THIS
IF your prodinfo is borked, used prodinfogen or wait for me to finish updating my pikafix guide in a day or two
Are you using the newest release of Lockpick_RCM? You should still be able to dump them.Thank you,
Few questions about this guide:
“Your own prod.keys file (This needs to be yours specifically (Unless you are trying to just generate the BIS files)! If you don't have them, try to dump them via Lockpick_RCM)”
-can I use the prod.keys which I generated as the Switch worked?
“Your switch firmware (Try to dump them via Tegraexplorer if you don't have them)”
-can I use the firmware folder from the internet because I can’t dunmp them?
If I start TegraExplorer.bin I get following Error:
“
Err: 21
Line: 303
File: source/Main.c
Desc : Keydump failed
”
-Can your guide fix this prod.keys dump error, is this because of the prodInfo issue?
Now I generated a prod.keys file with Lockpick_RCM.bin that solved the error a the begin.Are you using the newest release of Lockpick_RCM? You should still be able to dump them.
You need to put your prod.keys in the right place. Check where the keys are being looked for.Now I generated a prod.keys file with Lockpick_RCM.bin that solved the error a the begin.
I launched the script and selected “Restore Both”, during this I get the error “Failed backing up BIS” and “Failed to mount System”.
I did this, i have no more problems with the prod.keys but I get the error “Failed backing up BIS” and “Failed to mount System”.You need to put your prod.keys in the right place. Check where the keys are being looked for.
Require this guide any kind of Nand or BOOT1/2 because my are completly f******?FOLLOW THIS
IF your prodinfo is borked, used prodinfogen or wait for me to finish updating my pikafix guide in a day or two
Use this to rebuild BOOT files. https://gbatemp.net/threads/how-to-build-clean-boot0-1-files.591409/Require this guide any kind of Nand or BOOT1/2 because my are completly f******?
Need it any sources like a half functioning BOOT1/2 and Nand or install the script the system independent from the Files in the console? Which input resources are needed?
It should generate the boot files as well from memoryRequire this guide any kind of Nand or BOOT1/2 because my are completly f******?
Need it any sources like a half functioning BOOT1/2 and Nand or install the script the system independent from the Files in the console? Which input resources are needed?
Maybe because the NAND is completely wiped it's not able to mount.Thank you, I can see the device now with the name in the Devicemanager but BalenaEtcher don’t show it.
View attachment 280059
My FileExplorer shows it also as drive but brighter than my other drives.
View attachment 280057
Thank you,Maybe because the NAND is completely wiped it's not able to mount.
This is the guide I mentioned before, it's designed to fix cases with no backup/destroyed NAND: https://gbatemp.net/threads/guide-nand-rebuilding-for-no-backup-broken-emmc.593995/
It assumes you have a second Switch to use as a donor to get the needed dumps from, but you can use the PikaFix Pack files instead and you already have a prod.keys backup so you can skip the part that asks you to swap the eMMC chip I think (steps 5 and 6)