Hacking Switch possibly bricked?

  • Thread starter Thread starter Weyay
  • Start date Start date
  • Views Views 4,880
  • Replies Replies 7

Weyay

Member
Newcomer
Joined
Apr 22, 2019
Messages
5
Reaction score
0
Trophies
0
Age
31
XP
86
Country
United States
So I fucked up recently and updated to 8.0 a few days ago. I booted into RCM and restored my old boot & nand. Unfortunately since doing so, my Switch seems bricked. I cannot load into OFW, I can't run CFW, and the Switch's maintenance mode doesn't boot either, they all get a black screen. I can still boot into rcm, but I've pretty much run out of ideas, been doing research for a solution for 2 days now, and yes, I've tried the newest atmosphere version that works on 8.0, still without success Whenever booting into CFW using hakate, it gives me the error "Found pkg1 (''). UNKNOWN PKG1 VERSION. FAILED TO LAUNCH FIRMWARE" No matter the way I try to load into CFW, it always relates an error towards package1. Also when loading into stock, the Switch just black screens. Also I should mention that the previous Switch version I was using was 7.0.1. Thanks in advance
 
You need to update to the new version of Atmosphere. Unknown PKG1 = your Atmo is out of date. Be sure you’re using latest Fusse-Primary as well
 
You need to update to the new version of Atmosphere. Unknown PKG1 = your Atmo is out of date. Be sure you’re using latest Fusse-Primary as well
Unfortunately I've tried this already, "
Fatal Error: [NXBOOT]: Unable to identify package1" I'm wondering if something happened to the point to where my system's version got corrupt so it basically has no version installed on it. Is this even possible?
 
You need to update to the new version of Atmosphere. Unknown PKG1 = your Atmo is out of date. Be sure you’re using latest Fusse-Primary as well
Or they're somehow running a firmware that Atmosphere doesn't support/recognize at all (I have a few firms that are like this, like 20161011093138) :P

though I doubt this is the case here
 
first of all you updated to 8.0
second of all you downgraded to older firmware,
not thinking of the fuses burned.

1
try running hekate payload first then ofw,

2
Restore your original backup again, making sure to restore the boot0/1 files that come with your backup, using boot0/1 of other system version wont work..

3
use choidujour.exe to build system files and boot0/1 for 5.1.0
flash the boot0/1 files with etcher from choidujour.exe ouput folder,
then run hacdiskmount,enter all your biskeys in the correct places save them,then replace the system files from the output folder of choidujour...

4
Use biskeydump payload and get your system specific keys, or i think lockpick now gets them also.

5
Suggest you follow this guide and rebuild your self a fresh set of system files..
https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/

Skip steps 1,2,3 and start at 4 (only if you have a nand backup)
 
I've been able to follow the guide till step 7, When I activate "ChoiDujour.exe path/to/firmware/file/or/folder: in cmd, I'm getting an error "Only one input firmware file/folder argument is allowed, you gave 2" I'm trying to use firmware version 5.0.1
 
Alright, we didn't get too far before already getting errors. Step 3, I can't dump my keys, lockpickRCM starts up on the Switch, immediately throws the error "Unknown pkg1 version" I had a backup of my prod keys from earlier when my switch wasn't bricked, which then gave me an error in ChoiDujour which I attached a SS of the error...
 

Attachments

  • error.PNG
    error.PNG
    57.4 KB · Views: 305

Site & Scene News

Popular threads in this forum