[Setup-Guide]Setting up Android with EmuMMC + bigger FAT32 partition.

That is a nice tool! The added step of generating a boot.scr based on where the end user wants their L4T Ubuntu doesn't seem like it should be that difficult, since we have the information on how to do it available. I don't know how the tool handles hybrid-gpt/mbr partitioning, though, which is kind of the mess that this approach revolves around. It is possible. I hope I can contribute in some way!

 

@tabzer hello, i am trying with your multi-boot trick, but i dont get the point of the modification of boot file.
the name mmcblk0p9 is specially arranged or it is just a casual pick ?
i don't use emummc and have only 8partitions , do i must set the name to mmcblk0p8 ?
i picked mmcblk0p9 like you did ,but did not success with l4t.
is it the only change to make within the boot file?

 

The 9th is for the setup you get if you follow Tariq's video and do the same thing. If you aren't doing emummc, then your partition setup will be different.

What partition did you flash your L4T Ubuntu to?

 

@tabzer the 8th，after 7 partition of Android exactly set from the video，then 8th partition named mmcblk0p8，unformatted, dd’d with 1.img

 

I am assuming that you got the 1.img from the 2.00 release. I went ahead and made this for the 8th partition.

Try it to see if it makes a difference. First time booting can take a little longer than normal time btw.

 

thanks，after redo everything all from scratch , including renaming the partition to mmcblk0p8 it is now working with the boot file you provided .it must have been some mistake when i decrypt and encrypt the boot file.

 

The names of the partitions don't really matter. That's just how linux, internally, determines which partition address to boot. You can rename your partition L4T Ubuntu, or whatever you want. Anyway, glad it's working.

 

FYI 2.0.0 and 3.0.0 uses the same boot.scr

 

I've had previous guidance on getting my multiboot situation to work but still have a ways to go on finishing up on it. I've gotten both android and linux running on separate SD cards at the moment, I haven't created my partition for emummc yet as I haven't gotten my other Linux machine running yet to do the partitioning.

The plan is to set up Linux on a separate SD card and mirror it over to my main SD where I'm running android and then copy my emummc to finish it up.

So far I haven't had any issues getting emummc, Linux, or Android to run, but I'd like to plan ahead and get familiar with this boot.src file as well as thoughts on Linux 2.00 vs 3.00? Because once I have this figured out I would like to write a guide for everybody else who might want to take on this interesting project

 

whats wrong with a texted based tutorial? to slow to focus

 

I plan on writing one soon because there is a few things that is not covered honestly for me it's a bit of a pain to pause and rewind when it comes to what he types in the terminal but it's the best tut out there if you try to follow it

 

well even tho this was posted over a few months ago i found a someone who already made a simple script

 

I sense a little self-entitlement.

 

i honestly dont give a shit what you sense, i found a tool with a super simple write up that works perfectly i just wish i could delete my posts

 

Well not to give you more to care less about but do you mind explaining how the tool works?

As much as I'm all for a automatic setup tool and the fact that I've finally set up both my switches and would rather not do it over, I would like to learn more about how this tool sets up android emummc and Linux on a single SD card, let alone if this tool can also reflash android for pie without it affecting your emummc or Linux..

Speaking of pie, I'm also going to take this opportunity to ask if it is built like Oreo with 6 partitions to flash each sector to(i.e. vendor, system, boot, etc) any feedback on both subjects are much appreciated​

 

Nothing honest about that. Try deleting your account.

I'm sure the guy with a strict non-contribution policy is talking about this: https://github.com/lulle2007200/SwitchSDSetup

 

Yes it sets you up the partitions then you give the file path for either both or one or the other of android and or ubuntu then automaticly dd it and create partitions then after that, creats a empty emmummc partition for you, then i used my emummc.img backup i found then dd it to the last partition it was assing to, im not stupid your just a sloth

— Posts automatically merged - Please don't double post! —

Yes it sets you up the partitions then you give the file path for either both or one or the other of android and or ubuntu then automaticly dd it and create partitions then after that, creats a empty emmummc partition for you, then i used my emummc.img backup i found then dd it to the last partition it was assing to, im not stupid your just a sloth

 

Ah neato... I didn't dd my emummc partitions, the video demonstrated that you could just let hekate nyx do the work for you as long as you use gdisk to set the partition table correctly. Aside from manually creating bigger android partitions to ensure you have room for when pie comes around, emummc is the only other part of the multiboot that's trickier than the rest, because it's the only partition that sets up invisibly and it's hard to make sure of what you're doing if it's rather hard to confirm it, I mean you can delete the partition and it'll still be there and honestly when it comes to updating your multiboot setup in general I'm sure nobody wants to start from scratch every time.

Don't get me wrong I totally like the idea of the tool but when trying to put together a definitive guide I want to provide all the options for now and the future. Definitely want to encourage the more noobish (no offense) to try this stuff out.

 

I just want to say thank you for your awesome guide! If I decide to create a guide before then is there any way to create it a way that you or anyone who has contributed can add on and fix it? I just never done a guide and I want you and possibly some of those who were actively in your thread in the beginning to contribute to it as a work on progress.