Hacking Question Accidentally clicked on the update pop-up, now stuck without CFW.

[BlackBlue]

Btw Lakka still works on 12.0.0.

 

[BaamAlex]

Btw Lakka still works on 12.0.0.

Lakka runs outside from horizon os. So, it doesnt matter

 

[Chocola]

Damn, I'm trying to downgrade using ChoiDuJour.exe but the app just won't accept my keys

Just wait for atmosphere support, don't try to downgrade with outdated software if you didn't like brick your Switch

 

[Goku1992A]

I just don't know why people connect to the internet on a CFW switch best leave it on airplane mode and not worry. Seems like OP doesn't have dualboot set up where you can upgrade or downgrade your emuMMC at no risk

 

[BlackBlue]

Lakka runs outside from horizon os. So, it doesnt matter

Of course it matters. I can use Retroarch.

 

[BaamAlex]

Of course it matters. I can use Retroarch.

Yeah with lakka. And it does not matter. Lakka runs independently from hos.

 

[Chocola]

Of course it matters. I can use Retroarch.

Lakka its a independent distribution based on Linux, like Ubuntu for Switch or Android (Switchroot), you can run always these things if you have a method to inject payloads because didn't use the original operating system of the Switch.

Atmosphere or any other CFW, run over Horizon OS (the original operating system of Switch), this is the reason why you can run Lakka and can't atmosphere for example.

 

[BlackBlue]

Yeah with lakka. And it does not matter. Lakka runs independently from hos.

I didn't write I can use Retroarch with Atmosphere. It matters to me.

 

[bad361]

I'm sitting here right now wondering if people have ever heard of 90DNS....

Why use 90dns when there has been a safe method of blanking prodinfo in atmos since like half a year or more... But yeah, the picture with CJ on the first page perfectly describes this thread.

 

[BaamAlex]

Why use 90dns when there has been a safe method of blanking prodinfo in atmos since like half a year or more... But yeah, the picture with CJ on the first page perfectly describes this thread.

The reason is simple. It avoids system updates. An update can temporarily break your cfw setup. That's why you should use it. But either way, blanking the prodinfo has nothing to do with dns blocker.

 

[Tac 21]

jesus how many people running atmosphere DON'T have a emmuand?

 

[Burorī]

jesus how many people running atmosphere DON'T have a emmuand?

*slowly raises hand*

 

[Tac 21]

build one next time-

they are nice to have for things like these

 

[BaamAlex]

build one next time-

they are nice to have for things like these

But in case of the switch it doesn't matter whether they use an emummc or not. I don't know why, but the people think, they miss something when they don't update their consoles. Read a lot of threads or watch a lot of videos. And in such threads, where know-nothing adorn themselves with lack of knowledge. And in such threads trash is babbled that CFW-xy works with the latest firmware. Although this is not so. People install all kinds of stuff, but have no idea what they are actually doing. That's the problem I think. And through all the reading and watching videos, of course, it unsettles them i would say.

 

[Burorī]

build one next time-

they are nice to have for things like these

Well... I don't really use CFW for alot other than Homebrew and uhh... "Not very legally obtained games"

 

[AsukaL1to]

Yeah I'm kinda having the same issue except it got worse.

I kept getting an error when injecting the payload, it kept saying "unknown pkg1" and "HOS version not supported"
then it would put me in the hekate menu where all the settings could be changed.

I asked on this forum what I could do to just boot into the stock switch system. I knew that you could do that by turning off auto RCM mode, but I asked if this would be fine with the errors I got. Someone told me it would be fine so I disabled auto RCM mode and powered off the switch through hekate. Then I tried to power it back on and the switch would not turn on.

This is where I have been having a problem. After turning off auto RCM and powering off the switch through hekate, I can't seem to turn my switch back on. I tried holding the power button for 20 to 30 seconds and nothing happened, then tried going into rcm mode as I thought I could just reinject the payload through TegraRCM but my switch was never detected. Maybe its bc I am using the tinfoil and joycon method of the rcm mode which is kinda scuffed, but I've been trying to get rcm mode to work. Any help with this is greatly appreciated.

Any Help with this is greatly appreciated.

I tried searching around to see what others have done and apparently I should try removing the sd card then try booting it, but I'm not sure if this is safe considering the only way to boot the switch now is through a payload but idk.
I'm just trying to get it back to the stock switch system while we wait for the new updates on Atmosphere.

 

[Burorī]

Yeah I'm kinda having the same issue except it got worse.

I kept getting an error when injecting the payload, it kept saying "unknown pkg1" and "HOS version not supported"
then it would put me in the hekate menu where all the settings could be changed.

I asked on this forum what I could do to just boot into the stock switch system. I knew that you could do that by turning off auto RCM mode, but I asked if this would be fine with the errors I got. Someone told me it would be fine so I disabled auto RCM mode and powered off the switch through hekate. Then I tried to power it back on and the switch would not turn on.

This is where I have been having a problem. After turning off auto RCM and powering off the switch through hekate, I can't seem to turn my switch back on. I tried holding the power button for 20 to 30 seconds and nothing happened, then tried going into rcm mode as I thought I could just reinject the payload through TegraRCM but my switch was never detected. Maybe its bc I am using the tinfoil and joycon method of the rcm mode which is kinda scuffed, but I've been trying to get rcm mode to work. Any help with this is greatly appreciated.

Any Help with this is greatly appreciated.

I tried searching around to see what others have done and apparently I should try removing the sd card then try booting it, but I'm not sure if this is safe considering the only way to boot the switch now is through a payload but idk.
I'm just trying to get it back to the stock switch system while we wait for the new updates on Atmosphere.

Probably the Joy-Con method

 

[AsukaL1to]

Probably the Joy-Con method

Yeah that's probs the problem.

Do you think if I disconnect the battery it'll kind reset everything and allow me to boot into the stock system, or just leave me in the same situation?

 

[bad361]

The reason is simple. It avoids system updates. An update can temporarily break your cfw setup. That's why you should use it. But either way, blanking the prodinfo has nothing to do with dns blocker.

well, you can also use dns.mitm in atmos to block updates.. i see no reason to use 90dns anymore

 

[BaamAlex]

well, you can also use dns.mitm in atmos to block updates.. i see no reason to use 90dns anymore

Both are technically the same. Doesn't matter if i write 90dns or the feature from atmosphere.