Hacking Not able to launch CFW

[switchjos]

I can't launch any CFW..

I'm new to the Switch scene.
Although I did my homework and I read a lot already, I'm unable to launch CFW

1. I used a 3D printer of a friend to make a JIG to enter RCM-Mode (and I put a cupper wire in it)
2. With TegraRcmGUI_v2.4 I'm able to inject any payload (fusee-test.bin, hekate_ctcaer_4.6.bin, biskeydump.bin, ReiNX.bin)
3. With hekate_ctcaer_4.6.bin I'm able to backup all the necessary system-files
4. With biskeydump.bin I now have keys
5. I made atmosphere SDFiles (from SDSetup), unzipped and placed them on a FAT 32-SD-Card (the SD-card works on the switch of my friend after deleting/reinstalling Nintendo folder)

But when I press launch and then CFW, I don't see the Nintendo logo (I see a black screen for a second) and then I see the Switch-logo and then it hangs

7. Injecting ReiNX.bin (with other SDFiles for ReiNX) hangs on the yellow text Reading package1 shows up and then Decrypting package1 (and then it hangs) (so I don't see the picture with the girls showing up)..

So, no CFW for me

My Switch has OFW 1.0.0 and My serial number starts with XAJ40002..), SD Card is 16Gb FAT32 (works on the 1.0.0 Switch of my friend)

We do exactly the same on my friend's Switch, on his Switch it works (even my SD-card works on his device)

What can it be? What can I try?

 

[Kubas_inko]

1.0.0 is kinda unsupported. I think that you have to have developer options on or something like that.

 

[switchjos]

1.0.0 is kinda unsupported. I think that you have to have developer options on or something like that.

Thank you for your fast reply, but my friend has the same Firmware version 1.0.0 on his Switch, and for him it works.
(we never used it because back in the days they wrote that a permanent hack was possible, that's why we kept it eating dust, but now there are a lot of CFW-versions and we don't want to wait for that so called: permanent-CFW)

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

Thank you for your fast reply, but my friend has the same Firmware version 1.0.0 on his Switch, and for him it works.
(we never used it because back in the days they wrote that a permanent hack was possible, that's why we kept it eating dust, but now there are a lot of CFW-versions and we don't want to wait for that so called: permanent-CFW)

a real coldboot I mean with "permanent-hack"

 

[Kubas_inko]

Thank you for your fast reply, but my friend has the same Firmware version 1.0.0 on his Switch, and for him it works.
(we never used it because back in the days they wrote that a permanent hack was possible, that's why we kept it eating dust, but now there are a lot of CFW-versions and we don't want to wait for that so called: permanent-CFW)

Anyways did you do a backup yet?
You might want to try atmo and just udpate via choi to keep fuses to later downgrade (via the NAND backup)

 

[switchjos]

Anyways did you do a backup yet?
You might want to try atmo and just udpate via choi to keep fuses to later downgrade (via the NAND backup)

Yes I did backups and I'm unable to launch atmosphere, that's the problem (so chidujour is not going to run since I can't launch CFW)

 

[Kubas_inko]

Yes I did backups and I'm unable to launch atmosphere, that's the problem (so chidujour is not going to run since I can't launch CFW)

Normal amto. Not via hekate (although that should probably work the same way. DOn't know now.)

 

[switchjos]

Normal amto. Not via hekate (although that should probably work the same way. DOn't know now.)

What do you mean with 'normal atmo?' which payload do I have to use then?(if I can't use hekate?)

 

[Kubas_inko]

What do you mean with 'normal atmo?' which payload do I have to use then?(if I can't use hekate?)

Fuse primary. Here is a "guide": https://nh-server.github.io/switch-guide/

 

[switchjos]

Thank you man. This Totally fixed my problem, the first run crashed, I saw the atmosphere screen, then the screen colored black and then cyaan.
But the second run, worked, I finally have a workin CFW on my Switch Firmware 1.0.0. Thank you Kubas_inko, you saved my day!

 

[Kubas_inko]

Thank you man. This Totally fixed my problem, the first run crashed, I saw the atmosphere screen, then the screen colored black and then cyaan.
But the second run, worked, I finally have a workin CFW on my Switch Firmware 1.0.0. Thank you Kubas_inko, you saved my day!

Hold on. There isn't much you can do on 1.0.0 (except playing some first titles). So I suggest updating to 7.0.0/1 via chodijourNX to preserve fuses and get the full functionality out of your console.
And thanks to atmos features, you don't have to care about autoRCM, as it now properly shuts down.

 

[purzer0]

Thank you man. This Totally fixed my problem, the first run crashed, I saw the atmosphere screen, then the screen colored black and then cyaan.
But the second run, worked, I finally have a workin CFW on my Switch Firmware 1.0.0. Thank you Kubas_inko, you saved my day!

Hi there, I'm having the same problem you did. I'm in AutoRCM in 1.0 and trying to inject fusee-primary.bin to run just Atmosphere like you did (not Hekate), but it still sticks on the Switch logo. I also went back to the version of Atmosphere that was released at the time of your post to make sure it wasn't a problem with the latest version, same problem, after trying 3x each.
I may go back further in the atmosphere versions or clear off other things on the SD card and try, but otherwise, any idea what's going on? Maybe you weren't doing it from AutoRCM and the auto was causing the problem?