- Joined
- Sep 2, 2020
- Messages
- 1,274
- Trophies
- 0
- Age
- 39
- Location
- TORONTO
- Website
- form.jotform.com
- XP
- 2,205
- Country
case closed with reply mentioned with proper lockpuck_rcm, so I guess initial issue was prod.keys dump wrong or what
Hacking Boot0 or boot1 won't mount to pc through hekate
- Thread starter GreenDuck65777
- Start date
- Views 8,620
- Replies 164
Its not the same because he cant generate the keys with lockpick. Prodinfo is gone. Its not the same issue.
https://github.com/suchmememanyskil...ick-1.19.10-bdk-upgrade/scripts/SystemWipe.te - this is what the systemwipe.te does. I don't see it nuking the full nand.
Mounting the wrong partition and clicking "format" will wipe the nand too. So does a bricker payload. The reason for the nand gone doesnt matter at this point.
We should stop speculating and wait for him to try the guide and the fix. Thats definitely their last straw. If that fails, a donor switch and replacement parts need to be found if it shouldnt end up as an expensive paperweight
Last edited by Slluxx,
I'm now going to sleep. I will try to make it tomorrow, I'm really really tired. Sorry guys that I leave all this now, but I really tired. Also sorry for wasting so much of your time with my unique problem.
Its all good. Just make sure you read the guide i linked at least twice before doing anything. Its important that you understand what everything means before you go ahead and do it. I may be retired from active switch development but ill always help out if someone needs help ^^
- Joined
- Sep 2, 2020
- Messages
- 1,274
- Trophies
- 0
- Age
- 39
- Location
- TORONTO
- Website
- form.jotform.com
- XP
- 2,205
- Country
Little hint from my experimental just did, blank out SN wont trigger cal0 corrupted, and Missing/mismatched prod.key would trigger Tegraexplorer error:NoFAT
So very likely prodinfo partition something goes wrong.
So very likely prodinfo partition something goes wrong.
I dont know what this discussion is still about. The prodinfo is gone, no keys can be extracted and the nand is wiped too. Files on the sdcard were all correct because he reinstalled deepsea. Since he doesnt have a backup of his prodkeys he must now generate a generic one. And with that he may has a chance of rebuilding the nand from a firmware update.
Step1, generate a generic prodinfo with this tool/payload: https://github.com/CaramelDunes/prodinfo_gen .
Step2, follow this guide to rebuild a 6.0.0 (6.0.0 because thats a firmware supported by choidujor) nand from scratch and pray you have all the nessesary things.
If that worked, make a nand backup immediatly and then you can use the atmosphere homebrew to update to 17.x.x
read. the. guide. carefully.
Step1, generate a generic prodinfo with this tool/payload: https://github.com/CaramelDunes/prodinfo_gen .
Step2, follow this guide to rebuild a 6.0.0 (6.0.0 because thats a firmware supported by choidujor) nand from scratch and pray you have all the nessesary things.
If that worked, make a nand backup immediatly and then you can use the atmosphere homebrew to update to 17.x.x
read. the. guide. carefully.
Last edited by Slluxx,
Will make it, but not today. Don't have enough time cuz education.
Post automatically merged:
So, I have a question. How can I obtain hactool keys.txt?
Update: Still don't make it. Really hope that I will get some free time on Friday.
Attachments
Last edited by GreenDuck65777,
From start you are having a problem generating your console Keys, PRODINFO_GEN needs to extract your console keys to create a new file, but your console can not dump keys, so that is the error.What do you mean?
I have not enough knowledge to tell you why you can not extract your console keys.
So, I need @Slluxx ig. And wanted to ask: What is ProdinfoRestore.te? And what is this doing?
Post automatically merged:
Maybe something not right with partition?
Post automatically merged:
So I'm in a loop now. It is impossible to generate prodinfo because the keys cannot be obtained, it is impossible to obtain the keys because there is a problem with prodinfo. That's it, I no longer have options how to restore switch.
Post automatically merged:
So, I have new idea on mind. But it's too experimental and there's really slim chance that it work. What if I use donor prodinfo to overwrite my prodinfo, then launch prodinfogen and use "build prodinfo from donor" and use same prodinfo (or use from scratch), then overwrite donor prodinfo with generated prodinfo. But I think it's not gonna work and kills my switch entirely lol.
Post automatically merged:
What do y'all think guys? It's can work? Or just another stupid idea? (@linuxares, @impeeza, @Slluxx, @jkyoho. Really sorry for pinging, but I can't do this by myself)
Post automatically merged:
Okey, so I got my own device.keys file with my bis keys and tsec keys (also device key) with biskeydump v9. What can I do with it?
Attachments
Last edited by GreenDuck65777,
Not alone but almost in an unrecoverable brick. You NAND is damaged and you don't have your console keys. So only big N can repair the console and let's be sincere they will change the complete soc
You forget one thing. I live in Russia, so no help even from big N. Also new motherboard on Ali costs like switch lite, so no effort.
Similar threads
-
@
Psionic Roshambo:
Some snake lady was showing nipples in one of the games lol I think it was an RPG lol -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
@
NinStar:
unless nintendo is going to start selling consoles at a loss that thing won't be cheap based on everything mentioned so far -
-
-
-
-
-
-
