Hacking Question Permanent Violet Screen on Switch.

[rajkosto]

I had this violet screen while using NXLoader. I didn't do anything special to solve it. I think I just held the power button a few seconds... Am I lucky ??

no. that's normal when running older payloads at the end they show a colored screen, different from getting one DURING NORMAL BOOT.

 

[Insidious611]

Well, if it's just a bootloader error it could be a number of different things causing that, some of which are quite fixable. But given "Failed to initialize SDMMC" from biskey, this guy's machine is indeed probably fried.

EDIT: Also, what rajkosto said.

 

[cricket]

Try using bricmii v2 from https://switchtools.sshnuke.net/ to undo the autoRCM, and then re-do the autoRCM (without rebooting to horizon, to protect your fuses), and see if that works.

 

[Zonark]

Unit is dead you need to hard mod the nand and flash your backup but you didn’t make a backup so unit is dead non repairable... what did you do to cause this

 

[rajkosto]

Unit is dead you need to hard mod the nand and flash your backup but you didn’t make a backup so unit is dead non repairable... what did you do to cause this

everything except the PRODINFO can be regenerated, still that means you need to have backed up the PRODINFO or re-envigorate the eMMC until you can get it off safely
+ the problem might not be the eMMC itself but some power rail not delivering enough juice, since you say you can get it to boot sometimes.

 

[Zonark]

everything except the PRODINFO can be regenerated, still that means you need to have backed up the PRODINFO or re-envigorate the eMMC until you can get it off safely
+ the problem might not be the eMMC itself but some power rail not delivering enough juice, since you say you can get it to boot sometimes.

He could also try to reseat the nand

 

[TallahaseeTosh]

Unit is dead you need to hard mod the nand and flash your backup but you didn’t make a backup so unit is dead non repairable... what did you do to cause this

Happend when I changed out a joy con rail and ribbon that I broke. The console boots straight into rcm mode unless I let the battery die. The new cable most have fried or shorted something. I did get lakka to boot from the sd. So atleast I can play emulators.

 

[Zonark]

Happend when I changed out a joy con rail and ribbon that I broke. The console boots straight into rcm mode unless I let the battery die. The new cable most have fried or shorted something. I did get lakka to boot from the sd. So atleast I can play emulators.

Have you reseated the nand yet though?

 

[TallahaseeTosh]

Have you reseated the nand yet though?

Yeah I took it out and reseated it. Same result.. What i dont understand is why I can boot linux (lakka) from sd. But when i run a payload it fails to initialize sdmmc?

 

[rajkosto]

sdmmc probably refers to the emmc not microsd, they are on different IO and power rails, you might have messed up the 1.8V io rail when you messed with your joycons, sorry.

 

[TallahaseeTosh]

sdmmc probably refers to the emmc not microsd, they are on different IO and power rails, you might have messed up the 1.8V io rail when you messed with your joycons, sorry.

Hey well atleast it helps me understand whats going on. Thanks for all the help guys. I will purchase another console and just use this for emulators.

 

[ehnoah]

Had the Same when I booted brickmiiv2 -> SX OS, but after a full Reboot it worked. It seems a payload can cause this, if you chain them.

 

[Benoit934]

You should be carefull with your eMMC, always open it read only, if you use memloader you should remove all files not related to SD so you are safe.
The process should always be like :
Dump eMMC files to SD
Do your edits on the SD (keep originals, check the digest, save it on hard drives, cloud whatever is safe)
Load with your payload modified system files from SD

Do not write any bit on eMMC and avoid reading it too often

For PRODIFO you can still try to dump your eMMC to extract those data and fix the corrupted part but you will need some hardware

the "recovery strategy" is literally right below his image of the working switch ?
he sent me his RawNand.bin via PM, i verified its exactly the thing i thought it would be (see my post near the end of page 1), i wrote a payload that restores the GPT of the switch to the one it comes out of the factory with (the GPT is the same on all currently released switches, because there's no reason for it to change until they start releasing 64GB/16GB,etc models) and he ran it, which fixed his "brick"

PSA : Windows contain brick codes

 

[MROcellote]

Try Gptrestore it helped me.
I provided a file.
You also need some way to inject the payload.

 

[mitcha]

purple screen also for me too ;( after installing succesfully the exfat driver for my 4.1.0 ofw (using kirby SA from BBB release), i can rcm any payload , so i run gptrestore.bin it say OK ,then press power button ,but remain purple screen, any idea

edit :
Solved by restauring the nand partitions and boot1/0 with hekate

 

[magico29]

Try to boot into Hekate, your NAND is prob corrupted, let me know the results.

hekate do not show any options to nand recovery,i have same problem.i can run payloads,i can get into rcm mode and etc,memoloader is causing this.

 

[magico29]

Try to boot into Hekate, your NAND is prob corrupted, let me know the results.

hekate do not show any options to nand recovery,i have same problem.i can run payloads,i can get into rcm mode and etc,memoloader is causing this.

--------------------- MERGED ---------------------------

purple screen also for me too ;( after installing succesfully the exfat driver for my 4.1.0 ofw (using kirby SA from BBB release), i can rcm any payload , so i run gptrestore.bin it say OK ,then press power button ,but remain purple screen, any idea

edit :
Solved by restauring the nand partitions and boot1/0 with hekate

could please help us, and post how you restore using hekate,cause i tried and i cant restore,i dont see any other options on hekate.
can u please post the steps and what files has to be used,on pc and on sd card please baby.

 

[hippy dave]

hekate do not show any options to nand recovery,i have same problem.i can run payloads,i can get into rcm mode and etc,memoloader is causing this.

Use ctcaer's latest from the pinned thread, it has backup & restore options.

 

[magico29]

Use ctcaer's latest from the pinned thread, it has backup & restore options.

awesome baby thanks!!

--------------------- MERGED ---------------------------

Use ctcaer's latest from the pinned thread, it has backup & restore options.

i cant find it,am sorry.

 

[hippy dave]

awesome baby thanks!!

--------------------- MERGED ---------------------------


i cant find it,am sorry.

Sorry, i should have said the Sticky threads, at the top of this forum. Anyway, here:

https://gbatemp.net/threads/rcm-payload-hekate-ctcaer-mod.502604/

 

[magico29]

Sorry, i should have said the Sticky threads, at the top of this forum. Anyway, here:

https://gbatemp.net/threads/rcm-payload-hekate-ctcaer-mod.502604/

version 3.2 i just got it baby. thanks!!
do i need to place any backup files inside my sd card? in order to use the restore process?

 

[RAGER]

magico29,
yeah, place backed up files in root of SD.