Homebrew Question Would it be "legal" for me to post "blank" boot0 / 1 for repair purposes?

[flduch]

Ok mattyrog, hope that SciresM can give me good advices.

May I use now the switch as "standard" switch and connect it on the internet for doing some firmware updates ? May I risk to be banned ?

Thanks

 

[mattytrog]

Ok mattyrog, hope that SciresM can give me good advices.

May I use now the switch as "standard" switch and connect it on the internet for doing some firmware updates ? May I risk to be banned ?

Thanks

No you will be fine. As long as you are completely stock, will be fine.

None of our test units have been banned

 

[ZachyCatGames]

@flduch linkle works fine for regenerating keyblobs. Run “linkle keygen -k <text file with needed keys>” and it’ll output working encrypted keyblobs that you can just throw into your boot0, the keyfile needs to contain your secure_boot_key (console unique), tsec_key (console unique), decrypted keyblobs (not console unique), all keyblob_key_source_xx keys (not console unqiue), and keyblob_mac_key_source (not console unique).

 

[flduch]

Thanks a lot ZachyCatGames, now I can reuse LockPick_RCM and BisKeyDump attesting that the encrypted keyblobs in Boot0 are now valid !

Now I have to follow the way to recover my switch as before.

 

[flduch]

My switch is living again as before !

Thanks to all that help me to recover my briked switch. Without your help it couldn't repair my switch.

Thanks again and wish all the best :-)

 

[Freezerbomb]

I'm happy to host just pm me the pack.

If people can't figure out how to use a one click auto-xbins client to get the files then they shouldn't be modding a switch.

lol. The one clicker auto xbins thing never works for me. I have to connect the old fashion way.

 

[DBOA]

Reading the few last pages, I'm thinking my switch's PRODINFO might be busted, I'm going to check it later today.
Hopefully I can try to rebuild it from scratch if it's broken.

Crossing Fingers...

 

[Heavens7thCloud]

Only 6.2 & 7.0.1 in the xbins file at the moment.

The drill is launch my modded Hekate in the file (switchboot.bin)

Go to tools, choose a backup folder (BACKUP_1 for example)and backup your boot0/1 (and maybe prodinfo too).

Once done, go to this folder on your PC and you will see the BACKUP_1 folder with a subfolder called BOOTS in it. These are the ones you have just backed up. DO NOT DELETE THESE! Either keep them in BACKUP_1 or drag them to your PC. In fact, use the "quick backup" option to backup prodinfo too.

Make a new folder next to the BACKUP_1 called BACKUP_2 and make a subfolder with BOOTS folder.

Copy the repair files to this empty BOOTS folder.

Boot up the switchboot.bin, go to tools, select backup folder 2 (BACKUP_2) and restore the new BOOT0/1 using the

option under dangerous (Restore BOOT0/1 without size check) and restore the new BOOT0/1.

Enable autoRCM if you are saving fuses, boot, done.

You will need to launch with Hekate / Switchboot.bin if you are going to 6.2.0 and you have 9 fuses burnt.

Similarly, if you have 8 fuses burnt and you are building / using a 7.0.1 emmc, fuses will be burnt to match. If 6.2.0, you will have 8 burnt fuses... 7.0.1 = 9 fuses.

Remember - DO NOT USE THE FULL-SIZE ones. I merely included them for posterity. I have labelled them in the archive. Use the smaller ones or you will be saying goodbye to your keyblobs. However, the Switch will still start with missing keyblobs.

Just MAKE SURE THE FILES YOU ARE RESTORING ARE 1536kb (boot0) and 512KB (boot1).

@Canna

@mattytrog

Here is where the current switch i'm working on is at:

• The switch is on 7.0.1
• I have a rawnand.bin file that was created on 6.2.0 using rei.nx
• I only have the boot0/boot1 files that mattytrog created for 6.2.0
• The switch was on autoRcm when it was updated from 6.2.0 to 7.0.1

I have a similar question on another thread. However, this one seems more active and you stated the above steps earlier in this thread. My question is this:
Do i need to follow the above steps? Or do I need boot hekate and restore rawnand.bin and then the boot0/boot1 files? I know those files are generic...do i need to do anything to them before i restore them?

 

[Heavens7thCloud]

I was able to figure this out. There was a special payload included with the generic boot0/boot1. I had to remove my memory card and boot using this special payload. Then, i was able to reinsert my memory card and restore the generic boot0/boot1 files.

I have now successfully updated to 9.0.1 and am setting up emuMMC. Thanks much for all the help!!!!!

 

[brickedswitchelron]

Hi, Im trying to revive my switch with the Unbrick_your_switch_iha2. i had a few questions, wondering if anyone could help me out.

At step 4 it says "Dump rawnand.bin or mount emmc using memloader"
How do I dump rawnand.bin? does it mean placing it on the sd and restoring it using hetake?
and also at step 4) Restore console using "Use On PC" - "6.2.0 restore Files". Follow manual Choidujour downgrade tutorial"
From what step do I start?

 

[Mikeltii]

I haven`t worked out the sums myself yet. But I`m working on it. You can get the keys if your system is booting. First one I have come across. And I`ve done A LOT of them.

you said you come across the first, is the one for the prodinfo/prodinfof.. i cant fix my console getting always fail entropy but my biskey are of my console

 

[shchmue]

well someone else came to me with bad keyblobs and i found the pattern but no idea what's causing it. every 0D0A in the source file (what looks like random data since it's all code/encrypted) is getting replaced with 0A. something is trying to convert windows newlines to unix ones, which is honestly hilarious but why is this happening? lmao

edit: after asking around the most likely culprit sounds like the ftp client. i tried both winscp and filezilla on windows 10 and mine didn't corrupt despite the presence of this byte pattern. it is possible to FTP in ASCII mode and have this happen so somehow this must be what's happening

 

[fennectech]

I would like to go about performing the process with linkle. (or at least figure out how it works. Ive got plenty of time. Just need information. i figured out how the application works. Do i just put the keys linkle gives me at the appropiate offsets in boot0?

 

[mattytrog]

well someone else came to me with bad keyblobs and i found the pattern but no idea what's causing it. every 0D0A in the source file (what looks like random data since it's all code/encrypted) is getting replaced with 0A. something is trying to convert windows newlines to unix ones, which is honestly hilarious but why is this happening? lmao

edit: after asking around the most likely culprit sounds like the ftp client. i tried both winscp and filezilla on windows 10 and mine didn't corrupt despite the presence of this byte pattern. it is possible to FTP in ASCII mode and have this happen so somehow this must be what's happening

Filezilla line endings are indeed the culprit. Sorry I forgot to update. Change to Windows line endfings rather than Unix ones

 

[linuxares]

It's 100% Filezillas fault. It's set to automatic it will copy it in ASCII and not Binary. You force set Filezilla to Binary and will work without issue.

 

[xbmcuser]

It's 100% Filezillas fault. It's set to automatic it will copy it in ASCII and not Binary. You force set Filezilla to Binary and will work without issue.

This is really the fault of Unix ftp from back in the day, default for FTP was always ascii. They just wanted to stay consistant

 

[linuxares]

This is really the fault of Unix ftp from back in the day, default for FTP was always ascii. They just wanted to stay consistant

Yepp! The protocol needs an update for sure but here we are unfortunately.

 

[fennectech]

Can confirm. my filezilla is on auto. The console still boots and thats why i didnt discover it before!

 

[fennectech]

And here we have it "treat files without an extension as ascii files"

 

[lantern5540]

mattytrog Did you ever write detailed instructions for your brick_your_switch pack ?