Hacking Question Bricked Switch

[ethanhawk]

Well I think I’ve found the issue ..
Started from scratch again .
Followed it all again.
Got to stage 13 didn’t load up , so followed stage 14 .

when I tryed deleting system folder I got a error and when I look at 1 folder that wouldn’t delete I found this :—-

so looks like that found is corrupt, but how do I delete it ??
Windows will not delete it at all

update 2:——

found another corrupt folder in savemeta which I also can’t rename or delete .
Clearly this is why I can’t get it to work

is there anyway I can force delete??

 

[magico29]

Question: did you format the sd card before started the process?

 

[ethanhawk]

Yes I did .

The sd card was fine , but seems the System folder on switch was corrupt .
I checked the backup I had and same folder is corrupt in that too .


clearly why the update failed

I’m wondering whether I’m best to try and build a working Nand outta what I have ??

 

[magico29]

why are you saying is a corrupt folder then? how that folder was create?

 

[ethanhawk]

I’m saying that because it’s in the Switch SYSTEM folder and also on the Nand back I made straight after the update failed .

Clearly the card I used to update must have been faulty . And this is why I’m having so much trouble updating the switch .

I’ve been using a brand new sd card , so I know it isn’t that .

now all I have to do is figure out how to fix it

 

[magico29]

that means you backup nand could be corrupt too. did you check the rawnand on hacdiskmount?
do it and post a capture.
run hacdiskmount as administrator, file-open file and select rawnand.bin and open it.
DO NOT TOUCH ANYTHING ELSE AND TAKE A CAPTURE OF HACDISKMOUNT WINDOW.

 

[ethanhawk]

Yes I checked the backup , and when I mount the SYSTEM part , I browse to this folder and it’s all corrupt same as on the switch

which is the picture I

 

[magico29]

i told you do not press anything else. i want to see the main window please.

 

[ethanhawk]

Sorry I uploaded wrong picture ....

should be right now

 

[magico29]

i have no idea why you got that corrupted folder, i followed that guide and got it complete in one shoot.

 

[ethanhawk]

Neither have I ... But this is clearly why it doesn’t work .

so can I make a Nand using what I have ??
Using Hacdisktool ?

 

[magico29]

it wont work, if any of the files are corrupted. looks like you mess them on hacdiskmount.
as i know the guide i sent you is what we supposed to do in case of mess anything, but keeping on mind your rawnand and backups has to be 100% clean.

 

[Lacius]

@ethanhawk I find it interesting that this is the first time you've commented on the corrupted state of these NAND folders using HacDiskMount. That either means you didn't follow my instructions (or else you would have noticed this sooner), or you screwed something up between our troubleshooting sessions and now. I would recommend the following:

1. Restore the earliest NAND backup you have, including BOOT0/1 if it comports with that NAND backup.
2. Use HacDiskMount to see if there's any corruption

You might need to run gptrestore if this is an issue.

@magico29 As for the 6.2.0 files, these were created with a version of ChoiDujour that is compatible with 6.2.0. The reason for this is it eliminates variables, as it was impossible to know what all was done to the Switch, and 6.2.0 is when the system no longer uses keyblobs at all. In other words, a restore of 5.1.0 using HacDiskMount, for example, might fail to boot, while a restore of 6.2.0 on the exact same system might successfully boot.

It is recommended that you follow my troubleshooting steps from our private messages, deleting anything in mounted folders before copying over the new ones from the 6.2.0 package.

As I mentioned before, there's likely a lot of user error going on here with regard to actions and reporting that makes it difficult to troubleshoot.

 

[ethanhawk]

Well I followed it completely , deleted all folders, files in System and USER .

Seems I was using a corrupt Nand .
So double checked everything at every step .

All seemed to be perfect until I got to step 13 ...

Ran the UNBRICK part , screen did it’s thing .
Then I got the error in the picture .
And gives same error in normal mode .

If im honest I’ve no idea what to do next .
I’ve double and triple checked everything

 

[Lacius]

Well I followed it completely , deleted all folders, files in System and USER .

Seems I was using a corrupt Nand .
So double checked everything at every step .

All seemed to be perfect until I got to step 13 ...

Ran the UNBRICK part , screen did it’s thing .
Then I got the error in the picture .
And gives same error in normal mode .

If im honest I’ve no idea what to do next .
I’ve double and triple checked everything

Delete everything off your SD card and then put everything from the "put onto SD" folder onto your SD. Try those steps again.

 

[ethanhawk]

Done all that , used different card , completely clean .
Deleted folders etc

same outcome .
It’s just plain weird.
I wonder if I should let battery drain completely out and try again .
Or maybe the machine is just faulty ?

 

[Lacius]

Done all that , used different card , completely clean .
Deleted folders etc

same outcome .
It’s just plain weird.
I wonder if I should let battery drain completely out and try again .
Or maybe the machine is just faulty ?

1. Remove everything from your SD card
2. Download the latest version of Atmosphere and extract it to your SD card
3. Download the latest fusee-primary (next to Atmosphere)
4. Boot the system with fusee-primary

What happens?

 

[ethanhawk]

1. Remove everything from your SD card
2. Download the latest version of Atmosphere and extract it to your SD card
3. Download the latest fusee-primary (next to Atmosphere)
4. Boot the system with fusee-primary

What happens?

I downloaded latest versions and ..... does the same thing

 

[Lacius]

I downloaded latest versions and ..... does the same thing

At this point, my guess is it is a hardware issue. A quick Google search shows that some people have gotten this error when the hardware was at fault.

 

[ethanhawk]

I think so too .

well thank you very much for being so Patient with me .

ive learnt a lot over last few days .
Back up.
And listen
So thanks to all of you for your help .

I may just keep trying maybe I’ll get lucky .
May just let battery run out completely and see