Hacking Switch Lakka's payload won't launch from Mac OSX

  • Thread starter Thread starter jebediah
  • Start date Start date
  • Views Views 6,082
  • Replies Replies 9

jebediah

Well-Known Member
Newcomer
Joined
Aug 24, 2015
Messages
63
Reaction score
35
Trophies
0
Age
41
XP
266
Country
United States
Been playing around with homebrews on a Switch running 4.1 by launching the Fusée Gelée payload from an OSX machine. Now I'd like to run Lakka but the script keeps throwing errors. Some of these are just practical errors not covered on Lakka-Switch's installation page (such as "shofel2.py: No such file or directory" because the path specified in the script won't work out of the box), but once all of those are fixed and I actually run the payloads (cbfs.bin and coreboot.rom) through the linux-macos-boot.sh script, I basically get NoBackendError: No backend available

My setup meets all requirements to run Fusée Gelée, and when I get that error from linux-macos-boot.sh then try the Fusée Gelée method instead in order to figure whether the problem comes from the Switch, the exploit does work, so the Switch should have been ready for the Lakka payloads at the time I received their NoBackenError.

Something tells me I haven't figured all the reasons why Lakka isn't working OTB. It looks crystal clear when you read their instructions, but turns out quite messy when you run their linux-macos-boot.sh script on an RCM Switch. They make mention of "if it cannot find the module usb it means that you have insufficient permissions", but that's not the error I'm getting. Or is it?
 
this error (the same from linux) is when you try to use a usb2 port instead of a usb3 port (blue). there is no workaround (or at least no easy ones).
 
Thanks for pinpointing this. I guess the problem comes from the USB-C to multi-USB3 hub I'm using. It works with Fusée Gelée but I guess not with Lakka. I should really get a double-ended USB-C cable...
 
I found a double-ended USB-C cable laying around and used it to launch Lakka and it worked. However, I get no input at all from my Joycons or from a plugged in 8bitdo controller. I can kind of browse the menu by touching the screen and a PC pointer is visible on screen, but this is all erratic and rather useless.

By the way, the way I have the Lakka launcher to actually work is using these 2 commands:

cd boot-scripts-master
python shofel2/shofel2.py payloads/cbfs.bin payloads/coreboot.rom

This thread is solved but I'll appreciate if someone's got a tip to get my Joycons to work. I'm using the latest built of Lakka found here as instructed on their installation page.
 
Unfortunately my only PC is a Mac with usb 2.0 ports. I'm glad I found this thread as I was quite stumped as to why the script wouldn't run. I also have a Windows 10 virtual machine that it detects on and I've installed the driver so it appears as Nvidia APX but it freezes every time this is the output:
"Put your Switch in RCM mode now
TegraRcmSmash (64bit) 1.1.0-1 by rajkosto
Opened USB device path \\?\usb#vid_0955&pid_7321#7&3347e7b8&0&1#{5d27a7f6-9371-4636-8cd9-a156bae10523}
RCM Device with id 800004020000001CC9B24D2401101042 initialized successfully!
Uploading payload (mezzo size: 0, user size: 2364, total size: 29904, total padded size: 32768)...
Switched to high buffer
Smashing the stack!
Smashed the stack with a 0x7000 byte SETUP request!"

Is there any solution to for me?
 
I couldn't find a workaround for my workstation running on Linux.
I grew tired of double booting W10, so I bought a SX dongle which runs any payload. Problem solved.

Sorry to be that guy...
 
Another workaround, is to just launch SXOS freeware, then goto Options select other payload(hekate) then moreconfigs and boot lakka.
 

Site & Scene News

Popular threads in this forum