Hacking SWITCH NOOB PARADISE - Ask questions here

  • Thread starter Thread starter APartOfMe
  • Start date Start date
  • Views Views 5,999,671
  • Replies Replies 47,915
  • Likes Likes 66
Just tried that and no luck. Any other ideas? I am willing to try whatever you suggest.
Go to your PC and open a command prompt (cmd.exe) and type the following commands

Code:
nslookup
tinfoil.media
server 8.8.8.
tinfoil.media

once done take a screenshot and post it here.

Like so (commands are circled in light blue)

1675746855176.png
 
Hopefully someone here can help me with booting lakka for the first time on my switch. Ive tried searching for answers and had no luck anywhere. If someone could please guide me in the right direction to fix this, id greatly appreciate this. So with that being said, heres the status and problem:

Problem: Lakka says "Failed to load boot device or script."

Current status of switch and storage device:
-storage device properly formatted to FAT32
-switch is jailbroken and blocking nintendo servers etc,
-retroarch is downloaded via hbmenu appstore and currently updated.

Im fairly new to this, and ive exhausted everything i could think of to fix this. My guess would be something in the config files or maybe i didnt install something properly. Thanks!
 
Hopefully someone here can help me with booting lakka for the first time on my switch. Ive tried searching for answers and had no luck anywhere. If someone could please guide me in the right direction to fix this, id greatly appreciate this. So with that being said, heres the status and problem:

Problem: Lakka says "Failed to load boot device or script."

Current status of switch and storage device:
-storage device properly formatted to FAT32
-switch is jailbroken and blocking nintendo servers etc,
-retroarch is downloaded via hbmenu appstore and currently updated.

Im fairly new to this, and ive exhausted everything i could think of to fix this. My guess would be something in the config files or maybe i didnt install something properly. Thanks!

You followed the instructions here to the letter?

https://www.lakka.tv/doc/Nintendo-Switch/
 
Hopefully someone here can help me with booting lakka for the first time on my switch. Ive tried searching for answers and had no luck anywhere. If someone could please guide me in the right direction to fix this, id greatly appreciate this. So with that being said, heres the status and problem:

Problem: Lakka says "Failed to load boot device or script."

Current status of switch and storage device:
-storage device properly formatted to FAT32
-switch is jailbroken and blocking nintendo servers etc,
-retroarch is downloaded via hbmenu appstore and currently updated.

Im fairly new to this, and ive exhausted everything i could think of to fix this. My guess would be something in the config files or maybe i didnt install something properly. Thanks!
Looked into it a bit further, maybe .ini or uenv.txt might be the culprit for unsuccessful boot. here is the following uenv.txt parameters.

overlays=
lakka_boot_options=bt.disable_ertm=1
reboot_action=bootloader
hdmi_fbconsole=1
usblogging=console=ttyGS0,115200,8n1
uartb=no_console_suspend console=ttyS1,115200,8n1
cec_enable=1
performance_mode=0
dock_freq_switch_enabled=0
Post automatically merged:

yes i followed exactly. my next guess is to just restart from step 1 and basically wipe the drive.. im clueless at this point
 
Looked into it a bit further, maybe .ini or uenv.txt might be the culprit for unsuccessful boot. here is the following uenv.txt parameters.

overlays=
lakka_boot_options=bt.disable_ertm=1
reboot_action=bootloader
hdmi_fbconsole=1
usblogging=console=ttyGS0,115200,8n1
uartb=no_console_suspend console=ttyS1,115200,8n1
cec_enable=1
performance_mode=0
dock_freq_switch_enabled=0
Post automatically merged:

yes i followed exactly. my next guess is to just restart from step 1 and basically wipe the drive.. im clueless at this point

Lakka is self-contained. everything sits under /lakka so you don't need to wipe the drive to start over.

What does the contents of your /bootloader/ini/Lakka.ini look like?
 
Open iterm. do the same commands...
That exact command you linked isn't working. When I type is nslookup tinfoil.media I get:

Non-authoritative answer:


Name: tinfoil.media


Address: 104.21.80.252


Name: tinfoil.media


Address: 172.67.136.91

I could try using the nslookup command before the other lines if you would like me to try that.
 
That exact command you linked isn't working. When I type is nslookup tinfoil.media I get:

Non-authoritative answer:


Name: tinfoil.media


Address: 104.21.80.252


Name: tinfoil.media


Address: 172.67.136.91

I could try using the nslookup command before the other lines if you would like me to try that.
You type them one at a time like I did in the picture...
 
Lakka is self-contained. everything sits under /lakka so you don't need to wipe the drive to start over.

What does the contents of your /bootloader/ini/Lakka.ini look like?
lakka.ini looks as such,

[Lakka]
l4t=1
boot_prefixes=lakka/boot/
logopath=lakka/boot/splash.bmp
id=SWR-LAK
icon=lakka/boot/icon_lakka_hue.bmp
 
OK, that looks good.

What does your directory structure look like under sd:l/akka/ and sd:/lakka/boot/
sd:/lakka/ 1st pic and sd:/lakka/boot 2nd pic.
 

Attachments

  • 459288fc65f530c8c8b5bb685f7896f3.png
    459288fc65f530c8c8b5bb685f7896f3.png
    75.9 KB · Views: 74
  • 0e4c1205c1301576ab1f160927b1ce4a.png
    0e4c1205c1301576ab1f160927b1ce4a.png
    20.8 KB · Views: 70
sd:/lakka/ 1st pic and sd:/lakka/boot 2nd pic.
Interesting…yours has files my working version is missing.

Try Gavin’s latest nightly build:

New Lakka build for testing: https://nightly.builds.lakka.tv/mem....aarch64-4.4-devel-20230123090608-0ba0d18.tar
This build fixes a ton of things. Starting with lite gamepad issues on first boot, and some backend stuff..... This also re-implements lakka cpu speed menu, which will automatically scale clocks to OC, and is dvfsb compatible......
For what it is worth I can now play melee all the way through, with minimal issues, and that is with default settings, and vulkan...... clock scaling stuff is now handled automatically by retroarch, so if you dont want, you dont have to touch it.
Post automatically merged:

It says command not found: server
Once you type:
nslookup

hit return
then type:
tinfoil.media

hit return
then type:
server 8.8.8.8

hit return
then type
tinfoil.media

hit return
take a screenshot and post it here.
after that, THEN you can exit the nslookup program,
 
Last edited by binkinator,
Interesting…yours has files my working version is missing.

Try Gavin’s latest nightly build:


Post automatically merged:


Once you type:
nslookup

hit return
then type:
tinfoil.media

hit return
then type:
server 8.8.8.8

hit return
then type
tinfoil.media

hit return
take a screenshot and post it here.
after that, THEN you can exit the nslookup program,
Alright your steps worked.

> tinfoil.media


Server: ipv6 adress blanked out


Address: ipv6adress#53





Non-authoritative answer:


Name: tinfoil.media


Address: 172.67.136.91


Name: tinfoil.media


Address: 104.21.80.252


>


> server 8.8.8.8


Default server: 8.8.8.8


Address: 8.8.8.8#53


>


> tinfoil.media


Server: 8.8.8.8


Address: 8.8.8.8#53





Non-authoritative answer:


Name: tinfoil.media


Address: 172.67.136.91


Name: tinfoil.media


Address: 104.21.80.252


> tinfoil.media

I blanked out my IPV6 Address since I didn't want to post it on a public forum.
 
Alright your steps worked.

> tinfoil.media


Server: ipv6 adress blanked out


Address: ipv6adress#53





Non-authoritative answer:


Name: tinfoil.media


Address: 172.67.136.91


Name: tinfoil.media


Address: 104.21.80.252


>


> server 8.8.8.8


Default server: 8.8.8.8


Address: 8.8.8.8#53


>


> tinfoil.media


Server: 8.8.8.8


Address: 8.8.8.8#53





Non-authoritative answer:


Name: tinfoil.media


Address: 172.67.136.91


Name: tinfoil.media


Address: 104.21.80.252


> tinfoil.media

I blanked out my IPV6 Address since I didn't want to post it on a public forum.
No worries. So is your Switch and your Mac using the exact same name servers for DNS? Your Mac is having no issues resolving the correct IP so there’s nothing wrong with your network. It typically points to an internal IP adress of your router and the router forwards to upstream dns servers.
 
No worries. So is your Switch and your Mac using the exact same name servers for DNS? Your Mac is having no issues resolving the correct IP so there’s nothing wrong with your network. It typically points to an internal IP adress of your router and the router forwards to upstream dns servers.
Switch is using 90dns. Other than that, everything is the same.
 
right, we will need to take 90DNS out of the picture completely and only use dns:mitm for protection. That way (we hope) your switch will get the same results as your Mac.
Already have DNS:mitm, it looks like this:

# Block Nintendo Servers
127.0.0.1 *nintendo.*
127.0.0.1 *nintendo-europe.com
127.0.0.1 *nintendoswitch.*
95.216.149.205 *conntest.nintendowifi.net
95.216.149.205 *ctest.cdn.nintendo.net

I am just worried that the mitm could fail. I also have working exosphere since I can see my serial number is blanked out. In theory, if dns:mitm fails would exosphere keep me safe? I don't want to get banned....
 
Already have DNS:mitm, it looks like this:

# Block Nintendo Servers
127.0.0.1 *nintendo.*
127.0.0.1 *nintendo-europe.com
127.0.0.1 *nintendoswitch.*
95.216.149.205 *conntest.nintendowifi.net
95.216.149.205 *ctest.cdn.nintendo.net

I am just worried that the mitm could fail. I also have working exosphere since I can see my serial number is blanked out. In theory, if dns:mitm fails would exosphere keep me safe? I don't want to get banned....

dns:mitm is built into Atmosphere (as is Exosphere.) If you trust SciresM to code Atmosphere...you could make the jump that he's done equally well on dns:mitm and exosphere. I've been using both for over a year and have not heard of any failures.

Right now you're not able to resolve regular servers and I suspect it's due to the way you have DNS setup. It's not on your network as proven by your Mac. To test, we need to ensure the data you have above is in the /atmosphere/hosts/default.txt file and that you have exosphere.ini set up according to the doc I sent over.
 

Site & Scene News

Popular threads in this forum