Hacking switch lite retail mode

EnochGreybush

New Member
Newbie
Joined
Jul 30, 2021
Messages
2
Reaction score
0
Trophies
0
Age
40
XP
63
Country
United States
so i bought a switch lite online and when i get it, it boots up just the store demo units, is there anything i can do with this thing or am i completely screwed.. if there is anything that is even helpul to anyone let me know what/how i can do it.
 

Attachments

  • 20210730_124625[1].jpg
    20210730_124625[1].jpg
    1.9 MB · Views: 392
Those devices are identical to retail in every way, same hardware, same firmware, etc. Just they've got some special applications installed and some fuse is blown which tells qlaunch to load program id 0100069000078000 on boot.
If you install a modchip you can my ams builds from the thread mentioned above, which spoofs that fuse. Otherwise it's stuck.
 
Last edited by ZachyCatGames,
  • Like
Reactions: hippy dave
Those devices are identical to retail in every way, same hardware, same firmware, etc. Just they've got some special applications installed and some fuse is blown which tells qlaunch to load program id 0100069000078000 on boot.
If you install a modchip you can my ams builds from the thread mentioned above, which spoofs that fuse. Otherwise it's stuck.

Out of curiosity, why is this build necessary? Atmosphere himself can change the program id searched for qlaunch. is not that enough to launch the normal qlaunch?
 
If the seller didn't mention it being a Demo version he pretty much sold his problems on to you. I say this b/c I don't see any benefit of someone actually wanting to buy one over a normal Switch lite since they both require a modchip for hacks.
 
Out of curiosity, why is this build necessary? Atmosphere himself can change the program id searched for qlaunch. is not that enough to launch the normal qlaunch?
Normal qlaunch is launched (ams doesn't implement the relevant component anyway) and is running normally on these devices, qlaunch itself calls settings::GetQuestFlag (which calls spl::GetConfig, which calls smcGetConfig, which reads a value from fuses) and automatically launches 0100069000078000 if the result given is true.
 
Last edited by ZachyCatGames,
Normal qlaunch is launched (ams doesn't implement the relevant component anyway) and is running normally on these devices, qlaunch itself calls settings::GetQuestFlag (which calls spl::GetConfig, which calls smcGetConfig, which reads a value from fuses) and automatically launches 0100069000078000 if the result given is true.

Yes but adding system_applet_id = str!0x0100000000001000 to the system_settings.ini you can change it to launch the normal qlaunch.
 
Yes but adding system_applet_id = str!0x0100000000001000 to the system_settings.ini you can change it to launch the normal qlaunch.
Again, qlaunch is launched as normal on these devices and is always running in the background. Qlaunch automatically launches RetailInteractiveDisplayMenu, which is a application, if the quest fuse is blown.
ns.applet!system_applet_id is already set to qlaunch.
 
Last edited by ZachyCatGames,
  • Like
Reactions: Raugo
Again, qlaunch is launched as normal on these devices and is always running in the background. Qlaunch automatically launches RetailInteractiveDisplayMenu, which is a application, if the quest fuse is blown.
ns.applet!system_applet_id is already set to qlaunch.

Oh ok thanks, I triend the to do the inverse and with that I launched the kiosk app that's the reason I thought it might work. I guess it's more complicated than I thought becase in my case the app was launched empty.
 

Site & Scene News

Popular threads in this forum