FORUMS
Remove All Ads from XDA

[ROM][UNOFFICIAL][8.1] switchroot LineageOS 15.1

1,336 posts
Thanks Meter: 4,530
 
By langer hans, Senior Member on 24th July 2019, 06:43 PM
Post Reply Email Thread
23rd August 2019, 04:25 AM |#1461  
Junior Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by Gabri3lZ

Hey guys,

A lot of you were asking if there is an image for xyz GB microSD cards or how to increase the Nintendo Switch partition size to use the same card for the regular Switch OS and Android.
Well, I had the same requirements, therefore I made an interactive bash script that does exactly that. All you need is a Linux environment to run the script on. This can also be an Ubuntu Live-USB Stick for example.

Unfortunately, this is my first post. Therefore, I cannot include any external links. But you can find everything on GitHub under Gabri3lZ/SwitchrootAndroidUtils.


The script lets you decide what size the Android user partition should have, and it will use the rest of the free space for the FAT32 partition for the Nintendo Switch. It also allows to create an additional partition for EMUMMC (for those who want to run homebrew apps on the Switch and want to reduce the risk of getting banned). The script has the following advantages over using Etcher to flash the image:

  • Size for Nintendo Switch partition and Android user partition can be defined by the user
  • Support for an additional partition for EMUMMC
  • No wasted space on the microSD card, no matter what size the card has
  • The whole process is faster, because it does not dump Gigabytes of empty partition data to the microSD card
  • No fragmentation or breaking the (hybrid MBR) partition table because of moving and resizing partitions
  • The partitions are properly aligned (to 1 MiB)

The script is interactive. So you can choose the device you want to flash the image onto and the partition size while the script runs. Here is how to use it:
  1. Download the 16GB image from Switchroot's XDA-Developers post and extract the ZIP file.
  2. Download "flash.sh" to the same directory where the image is.
  3. Open Terminal emulator and navigate to the directory where the image and script are (in Ubuntu, you can use the File explorer to navigate there, right click the folder and select "Open in Terminal").
  4. Execute the script and pass the path to the Android image as a parameter:
    Code:
    sudo ./flash.sh ./android-16gb.img
  5. Follow the instructions in the interactive script.
  6. Follow the remaining instructions in the XDA-Developers post (from step 3).

Hope you enjoy. If there is any feedback about the script, please let me know here or on GitHub.

Hey, really like your script, man! It really seems to make more efficient use of the storage available. Would you recommend running this on a physical machine over a VM? I tried setting up an SD card with your script on a Ubuntu VM but I'm just getting a black screen when trying to boot to Android. I haven't been able to see TWRP yet. Yes, I am pressing + when the Hekate screen shows after tapping Switchroot Android icon. Sometimes I don't see a Hekate after tapping it. Let me know what I should do. I'm using Windows to push Hekate to the Switch.
 
 
23rd August 2019, 04:48 AM |#1462  
Junior Member
Thanks Meter: 3
 
More
Quote:
Originally Posted by DarkFamiliarity

I see, any way to use this card or should I return it and get a slower one? Any recommended 32gb cards? Ty.

You can buy a tf card that is not "u3", and the price should be less than $5. For example, the red-grey TF card of SanDisk
The Following User Says Thank You to 912933438 For This Useful Post: [ View ] Gift 912933438 Ad-Free
23rd August 2019, 04:56 AM |#1463  
Senior Member
Thanks Meter: 15
 
More
Quote:
Originally Posted by DarkFamiliarity

I see, any way to use this card or should I return it and get a slower one? Any recommended 32gb cards? Ty.

I'm using some 1-2€ USB 2.0 card reader for about 6 years. Had 20mb/s write speed.
The Following User Says Thank You to gohan456 For This Useful Post: [ View ] Gift gohan456 Ad-Free
23rd August 2019, 06:22 AM |#1464  
Mario119's Avatar
Senior Member
Thanks Meter: 57
 
More
For some reason Dolphin will not recognize Joystick inputs while using the Joy-Cons. I've tried the 'fix-joycon.zip', along with the modded version created by @SonsofOcelot but they didn't seem to do the trick. Oddly enough Dolphin correctly detects joystick input in the controller binding section, but while in a game they do not function.
23rd August 2019, 07:31 AM |#1465  
Senior Member
Flag casablanca
Thanks Meter: 15
 
More
Quote:
Originally Posted by Mario119

For some reason Dolphin will not recognize Joystick inputs while using the Joy-Cons. I've tried the 'fix-joycon.zip', along with the modded version created by @SonsofOcelot but they didn't seem to do the trick. Oddly enough Dolphin correctly detects joystick input in the controller binding section, but while in a game they do not function.

Be sure to bind gamecube and wii controllers (include nunchuk) and choose the right controller after starting the game, pull down when in game to see the menu.
23rd August 2019, 09:02 AM |#1466  
Junior Member
Flag Lucerne
Thanks Meter: 11
 
More
Quote:
Originally Posted by osxdude

Hey, really like your script, man! It really seems to make more efficient use of the storage available. Would you recommend running this on a physical machine over a VM? I tried setting up an SD card with your script on a Ubuntu VM but I'm just getting a black screen when trying to boot to Android. I haven't been able to see TWRP yet. Yes, I am pressing + when the Hekate screen shows after tapping Switchroot Android icon. Sometimes I don't see a Hekate after tapping it. Let me know what I should do. I'm using Windows to push Hekate to the Switch.

I tested running the script on a Ubuntu 19.04 Live-USB and a VirtualBox VM. Both worked for me and I could boot into TWRP and Android every time. I use my Pixel 2 phone to push the Hekate payload. But I don't think this should make any difference. Which Hekate payload Version did you use? I used v5.0.1.

Otherwise I don't know what the problem could be. Maybe you could try creating a new GPT partition table yourself (using GParted) and adding 1 large ext4 partition over the whole free space, before you run the script again.
23rd August 2019, 10:41 AM |#1467  
Junior Member
Thanks Meter: 0
 
More
Hey all

So yesterday I used a 32GB micro SD to install Lineage OS with gapps etc. After going through the whole process and waiting 3 hours for it's first startup, I decided to start over with another memory card that was faster. So I went through the whole setup again, booting through hekate and choosing Switchroot Android, but boots directly into the OS. I have no option of installing gapps. How do I fix this?

Edit: NVM, I was an idiot. Was in a hurry and didn't hold down + when I selected Switchroot Android
23rd August 2019, 11:13 AM |#1468  
Member
Thanks Meter: 21
 
More
Quote:
Originally Posted by [email protected]

So I went through the whole setup again, booting through hekate and choosing Switchroot Android, but boots directly into the OS. I have no option of installing gapps. How do I fix this?

Gapps installation occurs in TWRP. Access TWRP by holding volume + the moment you tap Switchroot in hekate.

Once in TWRP, tap Install and select the gapps you downloaded to your FAT32 (PC readable) partition. Slide to flash gapps.
23rd August 2019, 11:21 AM |#1469  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by Count_NOOBula

Gapps installation occurs in TWRP. Access TWRP by holding volume + the moment you tap Switchroot in hekate.

Once in TWRP, tap Install and select the gapps you downloaded to your FAT32 (PC readable) partition. Slide to flash gapps.

Yeah, thanks! I was in a hurry and forgot that part. Read my guide again and saw I missed a step, but thanks for the input
23rd August 2019, 06:33 PM |#1470  
Senior Member
Thanks Meter: 13
 
More
Has there been any word from the devs about future updates? I know they are still active on discord but it seems pretty strange with how active they were on here before release and then after release not a word.
24th August 2019, 01:24 AM |#1471  
Senior Member
Thanks Meter: 16
 
More
Quote:
Originally Posted by Phillyrider807

Has there been any word from the devs about future updates? I know they are still active on discord but it seems pretty strange with how active they were on here before release and then after release not a word.

They were active on here before the release because the build was basically already done days before release & they were only focused on fixing deep sleep which they failed to do. Before that they were silent. They are silent now because they are working on Pie and once it's close to being ready for release they'll probably become active here again.
The Following User Says Thank You to techjunky90 For This Useful Post: [ View ] Gift techjunky90 Ad-Free
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes