OS 8.1.0
SXOS 2.9.2

Just freezing on Deletу system

After hard reset with power button console goes to initialization, but updates for all games are existing on the HOME screen

UPD. I tried to repeat an error, but second time all was fine

Hello
do we really need haku33 or just an hard reset is good ? lot of people are just use hard reset et don't get ban
Thanks

How do I fix script error 1? just wondering as i dont know

I try to carry out the procedure and I get the attached error.

I'm new to nintendo switch. Here is a dump issue.

• I put haku33.nro in the sd card
• Booted the atmosphere
• Already did the 90DNS
• Opened haku33
• Press - + ZR ZL altogether
• Nothing happen

I dunno what I did wrong
Please help

I wiped my switch using haku33 and got a black screen with my home button glowing but it doesn't seem to power on anymore. please help me

It has only black Screen and the Home Button is shining
Pls Help Mr

The problem found so far is that after the whitewashing is completed, re-enter the system. After the real cracking and the genuine system enter, the Nintendo icon is lit up, and the black screen will not respond after a while.
Use lockpink-rcm to extract the system firmware, which cannot be extracted. The machine seems to have turned into bricks.

Tried using Haku33 on HOS 16.0.0 through title override with no success, not sure if it has to do with Haku33 or something else though.
Had to boot into stock HOS and initialize the console from there.

On Atmosphere 1.5.0, hekate 6.0.2.

Only 2.9 can worked in SX Core, it looks like reset OK, but restart not found red Nintendo.

i am trying to use haku33, pressing zr+zl is okay (turns blue on screen) but when i press volume up or down, instead of haku recognizing it.. it just function as normal volume buttons. how can i resolve this?

Hi !

Err : 21
Line : 303
File : source/main.c
Desc : Keydump failed

Once I star the cleaning I get this error, please can I have help ? ^^' And thanks for the work btw, I really want to use this.

After starting the program (v4.5 on mariko) from hekate, the black screen on switch oled (FW 13.1.0)

Hi, can you give me an example about how to use Hekate in Hekate More configs?

I found the config ini in romfs/ini, but I can not find the Hekate.bin. I see the release only hava nro.

I tryied rename haku33.nro to haku33.bin, but where I launch it through More configs, device return black screen
I think there must be some reasons I don't know.

Could you please give me a more detailed explanation about how mariko device use through More configs?

Hello!
First of all, thank you for the awesome tool.

I used it to factory reset the system, however, the OFW stays in 9.2 (which I manually updated in the past, using Choidujour).

Would you think this is as clean as I can get the system to - can I go back online even though the OFW wasn't updated through Nintendo's servers?

(For some reason, I thought I had done a proper NAND backup, turns out I just created a small backup of something else so I cannot restore to my original NAND anymore).

Thank you kindly for your time

With https://github.com/StarDustCFW/Haku33/blob/master/romfs/Haku33.te

TegraRcmSmash run Haku33_payload.bin:

t shows:
An error occured:

Function: dump_biskey
Errcode:57
Dese: BISKEY DUMP FAILED

Press any button to return.

It looks like the line:color("GREEN") should change to color(0x00FF00)
Maybe println need to replace p too?

atmosphere SYS 16.0 AMS 15.0

If not, will it?

Hago todo como indica pero una vez termina y se apaga la pantalla procedo a encender normalmente (como si estuviera virgen) pero de nuevo vuelve a arrancar ReiNX y me vuelve a hackear la sysNAND.

Imagino que no sea problema del homebrew pero estoy estancado en este punto y no se a donde mas acudir.

Ayuda por favor. Gracias.

PD: Para futuras releases... ¿podrias hacer que sea opcional el borrado del .nro? En caso de que el homebrew pueda leer el nombre de su propio .nro se me ocurre que segun el nombre que tenga pueda permanecer una vez hecho su trabajo. Si no,,, 2 .nro distintos... uno que se borre y otro que no. ¿El motivo? cada prueba que hago tengo que sacar y cambiar de sitio la tarjeta para volver a meter el homebrew.

Explained thoroughly by SciresM, so I'll just link to their writeup.

Workaround: Booting to Atmosphere >=1.6.1 will unbrick the console.

Using Atmosphere 1.6.2, Firmware 16.1.0:

• After wiping, version 5.7 causes HOS to not start whatsoever, the screen remains black
• After wiping, version 6.0 starts but you permanently receive the 2002-4373 error code and the console keeps asking you to reboot

This seems to be consistent.

I reset my switch with haku33, to start over. The system worked fine and was able to connect to and use Nintendo services for a few weeks, but is now now banned.
I have been using an emunand with incognito and exosphere product blanking for years to prevent a ban from happening.
I have used cfw on the nand before, and didn't have a clean backup.
That is why I used haku33.

console: SwitchLite-mariko(chip cracked), 13.0.0s
haku33 version: 4.4

Tegra explorer 4.0.1

"
Err : 21
Line : 303
File : source/main.c
Desc: Keydump failed

Press A to continue
"

Pressed power btn to continue, it says "[WARN] Keys required. Make sure you're on the latest version of TegraExplorer!"
then power btn again, slided to systemWipe.te, press power, it says "[WARN] Keys required. Make sure you're on the latest version of TegraExplorer!"

Please help, thanks for your time!
Truely appreaciate it!

Thank you for your contributions, and recent 3.3 release supporting up to 12.0.0. Sorry if my issue is silly but I am a newbie and have already googled with no avail. I accidentally updated my firmware from 12.0.0 before changing my mind on having my CFW on sysNAND. Will the latest 3.3 release work on 12.0.1 firmware?

I applied the clean, but now my Switch does not turn on