[Q&A] MultiSystem for Android

[hsbadr]

MultiSystem is a powerful tool for locked- and unlocked-bootloader Android devices with many features that at least includes the following:

• Keeps stock system partition safe/rooted
• Permenant root survival with proper use
• MultiROM support via virtual ROMs
• Unlimited number of virtual ROMs
• Booting options to choose stock, primary, or secondary virtual ROM
• Any of the virtual ROMs can work as a recovery replacement
• Flashing multiple ROMs at the same time without a reboot
• Ability to create/install ROMs on Linux to microSD card
• Great performance & battery life on virtual ROMs
• Recovery solution to install ROMs or Mods
• Easy upgrade to newer versions of Android
• Ability to safely apply OTA updates to virtual system
• Permissive SELinux and other kernel tweaks
• Safe flashing that doesn't trip KNOX flag on Samsung devices
• Wrapper script runs via ADB or a Terminal Emulator on device
• APK to manage all MultiSystem functions with a nice UI and extra options
• Management for the best performance & user experience
• Support for all Android devices with microSD card
• Portability to almost all devices
• Compatibility with all Android versions

Q&A​

What is the concept behind MultiSystem?

It runs virtual Android ROMs on microSD, like booting multiple systems on a PC from different partitions/disks. So, your stock system partition is kept safe/rooted. It won't affect performance or anything (might even be better on the virtual system if you've high quality microSD & the device supports its speed). Also, you can freely modify any of the virtual systems & in the worst case, reboot the safe stock system or another working virtual system to recover. So, no root loss or potential damage to the original device partitions.

Is it a recovery or an APK tool?

It's a shell script that hijacks system at early boot & force Android to boot from the stock system partition or a virtual system IMG & an APK that manages all booting options, virtual ROMs, and works as a recovery replacement + extra features...

Does it work as a recovery replacement?

It IS a POWERFUL recovery replacement. You can do whatever you do in recovery with the APK. HOW? recovery does its magic b/c it doesn't depend on the system & has its own kernel/ramdisk. In MultiSystem, you can boot a virtual ROM from extSD that sure doesn't depend on stock system partition or any of the other virtual ROMs (it does depend on the kernel, which you can't flash on locked devcies anyway). Hence, install, backup, restore, ... & all recovery functions are all possible +++ more features since you're running a full ROM not just a recovery ramdisk like Safestrap.

Bottom Line: I think it's the best & most convenient recovery replacement ever for locked devices & it can also attract unlocked devices for the powerful features, MultiROM, and recovery from within ROM.

Can I use FlashFire along with MultiSystem?

Yes. MultiSystem is compatible with FlashFire & fully supports it on stock & virtual ROMs. So, you can use both/any of them for flashing to either a stock or virtual ROM. However, it's recommended to use MultiSystem when flashing to the stock system partition (shouldn't be needed anyway since you can always be safe & flash to your old/new virtual ROMs).

Does MultiSystem require FlashFire?

No, MultiSystem doesn't require FlashFire. They're fully combatible though.

Would the virtual ROM we install be exactly the one in the stock slot?

In MultiSystem APK, you can create a virtual ROM from stock system, a copy from other virtual ROM, a new IMG, a dev-provided ROM, a flashable .ZIP, ... etc. Literally, your virtual ROMs can be any stock or custom ROM that's compatible with your firmware/kernel.

How can it run virtual ROMs from external microSD card?

External MicroSD will be formated into 2 partitions:

• exFAT or FAT32 for the 1st partition (your new external storage)
• EXT4 for the 2nd partition (your MultiSystem partition)

It'll hijack the system & boot a virtual system from the 2nd partition. The 1st partition will be automatically detected as your extSD.

Can I run unrooted virtual ROM for work apps or any other reason?

Yes. You can add unrooted virtual ROM & reboot to it via MultiSystem APK.

How do you boot back into a different ROM?

MultiSystem APK manages all functions including ROM activation & reboot to current system, another stock/virtual system, download mode, recovery, ... etc.

Will it be OK to still store media like movies/photos/music to extSD?

100% OK; That's my setup a few months ago. 2 virtual ROMs in the SECOND extSD partition in EXT4 format while all personal data are stored on the FIRST extSD partition in exFAT or FAT32 format... TWO COMPLETELY DIFFERET PARTITIONS.

How much space are we going to have for virtual ROMs?
The size of the 2nd partition is optional (> 4GB) for your ROMs, but here is an estimated sizes:

• 1 Virtual ROM Uncompressed = ~2.7 GB ---> ready for running
• 1 Virtual ROM Compressed = ~1.5 GB ---> for full ROM backups

I'd say better allocate 4 GB for each ROM you plan to run. If you just need one virtual ROM to keep stock system safe, 4 GB 2nd extSD partition is enough; The remaining space is allocated for the 1st extSD partition as your external storage.

For me, I run Linux too from extSD via MultiSystem. So, I've 64 GB extSD card with two partitions 32 GB each.

Can I clear up space on an existing SD card and partition it while full or will the entire card need to be wiped and partitioned from scratch?

You need to backup all your files; it'll be wiped & repartitioned.

How can I swap microSD cards & be able to run virtual ROMs?

You can swap microSD cards as you wish provided that the device is powered off; don't remove the microSD card when running a virtual ROM. If the new microSD card doesn't include a 2nd parition of available virtual ROMs, the device will boot directly to the stock system.

Is there a specific sd card you recommended for this?

I personally have two microSD cards:

• SanDisk Extreme Plus 64GB (Up to 80MB/s read speed)
• Samsung 64GB PRO (Up to 90MB/s read speed)

You don't have to change your microSD card for MultiSystem; any card you use on your device should work just fine. The need for more speed is relevant when the device supports that speed & if you're going to buy a new card anyway that you may use with a newer device later.

Can I copy virtual ROMs to a new microSD card?

Yes. I'll add a feature for swapping microSD cards so that you can backup/restore virtual ROMs from/to the current extSD to/from internal storage as follows:

• power off device
• use MultiSystem APK to backup your virtual ROMs
• insert the new properly formatted microSD,
• power on device (it'll boot to stock system)
• use MultiSystem APK to restore your virtual ROMs
• use MultiSystem APK to activate one of your virtual ROMs
• use MultiSystem APK to reboot to any of your ROMs

What about other data/cache partitions and internal storage?

Only system img's are in the extSD. All ROMs share all other partitions. This substantially improves the performance & you won't notice any difference between your stock & virtual ROMs. The reason for performance improvement is that EXT4 loop devices are very fast in reading but not in writing. Your system partition is read-only while data (for example) is read write & cache IMGs cause problems like Safestrap issues on ROM slots. Also, you don't have to worry about switching data/settings between ROMs (they're shared), but you just need to regularly backup your important data (which is healthy anyway).

Can your elaborate where data is stored?

The userdata partition is also shared; so, you'll have access to all your FULL storage partitions & all apps/data similarly on either stock or virtual ROMs. This also solves the Safestrap issue of having less storage on ROM slots...

Will mSDcard incur a significant performance penalty on some devices?

there's no diffrerence between virtual & stock ROMs in terms of performance & battery life. The reason is simple: loop devices associated with the READ-ONLY system IMG mounted from EXT4 partition using a high-quality microSD card IS very fast more than enough.

The read speed is faster than the device can operate anyway + the exact same device should perform on the lowest speed when reading/writing from/to the FAT/FAT32/ExFAT extSD card (where you store your files or even move apps!!!) anyway, which is much slower than the read speed of a loop device mounted from EXT4 partition.

That's why data partition is shared for many reasons, including the poor READ/WRITE performance.

If virtual systems are read only, how do we modify them? Do we have to boot to another multisystem rom to modify a virtual rom?

The stock system partition is mounted by default read only & so are the virtual systems. To modify a stock/virtual system, the MultiSystem APK remounts them read/write. You can modify the currently running virtual system, copy it & modify the copy, modify another stock/virtual system.

How is a corrupted virtual rom handled? Does it see it's bad and default to stock system?

At early boot, MultiSystem checks for the microSD & active virtual ROM to boot it. There's a boot menu that gives you options to select a stock/virtual system, but it crashes on LP. I'm debugging it, but all functions won't be affected if I removed it. To fail safe, you can remove the microSD card to boot to stock system & restore/repair your virtual ROMs.

UPDATE1: MultiSystem v1.0.1 now allows you to also switch to stock system on boot to repair corrupted virtual IMGs or any other reasons. More options will be added during boot to ultimately select another virtual system if the active IMG is not booting normally (e.g., bootloop after applying a mod or flashing a bad .ZIP).

UPDATE2: Now, on boot, you can choose from two primary/secondary virtual ROM or stock ROM. Flashing multiple ROMs at the same time without a reboot is now possible.

How to check if an IMG is corrupted using MultiSystem status?

Current System IMG: Test_Rom.img
Current System DEV: [B][COLOR="Red"]/dev/block/mmcblk0p23[/COLOR][/B]

When you see "/dev/block/mmcblk0p23"; it's the original system partition; so MultiSystem failed to boot Test_Rom.img, but it should be your current system.

So, the check is simple based on "Current System Device":
/dev/block/mmcblk0p23 = Stock System Partition
/dev/block/loop0 = Virtual System IMG

Note: The block device number (mmcblk0p23) may vary per device & per variant !

Does android do any maintenance whatsoever on stored data within /data or external sd? So if I have an app installed on 1 system and not on another system will android see it and clear the data?

No, all storage partitions are shared between ROMs. If you installed an app, it'll be availabe for all of them. Since on locked devcies we're limited to stock manufacturer-based ROMs, this makes the switch between ROMs very convinient (you don't have to worry about your changes/data/setup & storage space on the another ROM; all ROMs share everything except system). However, you should make regular backups in case a virtual ROM (probably with unsafe mods) results in bootloop due to your user data. In this case, it's safe to wipe data & selectively restore apps/data from backup(s). Another advantage of sharing all storage partitions is that your messages/emails/etc received on a virtual ROM are immediated synced (actually shared) to the other ROMs.

Will anything like Xposed modify the virtual ROM system IMG as opposed to the stock system IMG?

When you run a Virtual System, everything incldung kernel & apps are hijacked to speak to it as the original system.

Can we install AOSP ROMs on locked devices?

You can only install stock/manufacturer-based ROMs on locked devices while unlocked devices can use kexec or flash the required kernel to boot any AOSP/Stock ROMs. I've got a Note 4 Developer Edition & a lot of development is planned to go there (thanks to the unlocked bootloader!) More devices will get supported including unlocked TMO & international variants after adding more features untilizing the unlocked bootloader with kexec'd kernels.

Are there limitations to the combinations of ROMs that can be loaded on the "stock" and "virtual" slots? Can you mix KK and LP?

Yes, if they can run on the same kernel. LP won't run on KK kernels & so, you'd have to upgrade the firmware anyway. As for running mixed compatible Android versions, this is possible but your'd have to backup your data before switching ROMs; if it cause no issues, enjoy smooth switch & if it doesn't, do factory reset in recovery & restore your data backup. Backups via MultiSystem are painless.

Are applications installed once for each ROM slot that has that applicaiton installed, or can I share a game across ROMs (for instance?)

Everything is shared between ROMs, which is very good for storage & for easy switching. Just make regular backups of your sensitive data.

How there are no performance hits while internal storage memory was much faster than any microSD technology?

Read speeds from microSD is very fast compared to write speeds & since virtual ROMs are actually a virtual read-only systems (hence, MultiSystem), they provide a high performance. Moreover, again, read speeds from EXT4 loop devices are higher compared to physical partitions. They're very bad in writing, which we don't need for the read-only "system".

Is there a preferred "daily driver" ROM that should be installed in the stock slot?

Uses a stock ODEXED ROM on stock slot for better stability!

Is it based off of Safestrap?

Short answer NO. I've been working on MultiSystem & Safestrap for ~7 months. Earlier versions of MultiSystem (called, JasmineREC) was based on Safestrap, but it failed to support newer versions of Android mainly due to TWRP changes in the graphics/UI libraries that cause segmentation fault & the stock kernel framebuffer issues. Then, I decided to find another solution. However, the basic idea of system hijack is powered by Safestrap (or 2nd-init recoveries in general) & all the work done by @Hashcode is GREATLY appreciated.

How can it overwrite system files while running?

MultiSystem allows you to install safe mod's or a ROM in full or OTA-like update. It's strongly recommended to install .ZIP files NOT to the current system, b/c some files can not be overwritten while running. So, you can use backup function to copy the current system & install to the new img or any of your other virtual systems. You'll have several options to activate a virtual img & reboot directly to stock system, any virtual img you've activated, quick reboot, Download/bootloader, recovery,... etc.

How would I benefit from it if I'm only running Stock ROM or would there be no point for me to install it?

If you run a ROM on stock system, you're vulnerable to root loss unless/untill a new rooting method for LP comes out. MultiSystem gives you the option to run safe-to-mod virtual ROMs + recovery replacement + extra features.

Is there a way to convert a normal ROM .ZIP into MultiSystem .IMG?

Create or copy any of your IMGs, activate it & reboot to the active IMG! Then, use FlashFire to flash the ZIP file. However, the updater-script should be safe/compatible. Some devs mount the phyical partition, which will redirect everything to it!!

For example:

mount(“ext4″, “EMMC”, “/dev/block/mmcblk0p23″, “/system”);

will mount the original system partition; while

run_program("/sbin/mount", "-t", "auto", "/system");

will mount the current system (stock or virtual). This is recommended/safe.

Would a KitKat ROM work with multisystem even though my stock is Lollipop?

Any ROM requires a compatible kernel & modem. So, running KK ROMs requires flashing KK firmware (namely, kernel & modem). This may work with MultiSystem on other devices, especially if the bootlpoader is unlocked. For example, I plan to add features for Note 4 DevED to allow different Android versions (including AOSP, manufacturer-based, & probably Linux systems) by utilizing kernel swapping or execution.

When MultiSystem comes out will it be open sourced?

Most probably, haven't decided yet!

Anyway, here's the repository on GitHub: https://github.com/hsbadr/MultiSystem

 

[hsbadr]

Video Tutorials

A quick preview of MultiSystem v1.0 tested on Lollipop for VZW Note 3. The video has been captured on a stable virtual ROM of JasmineROM v5.0.1. It's FULLY compatible with FlashFire on virtual/stock systems. More devices will get supported as well, after required testing.

Facebook: https://www.facebook.com/hsbadr/videos/vb.331488823689599/428178174020663

 

[hsbadr]

How to check if you are running a Stock/Virtual System?

There're many ways to check whether you're running a Stock or Virtual system. MultiSystem app should include this simple check at some point. That's important to avoint ruining the Stock system & keep it safe. To make it clear to NOOBZ & anyone who's requesting "another" proof even though I owe hime nothing. Very weird!

Anyway, BusyBox mountpoint applet can print the current block/device mounted to /system mountpoint by running the following command:

busybox mountpoint -n /system

The stock system is mounts the original system partition:

[B][COLOR="Red"]/dev/block/mmcblk0p23[/COLOR][/B]

while the virtual system mounts a loop device associated with a system IMG:

[B][COLOR="Blue"]/dev/block/loop0[/COLOR][/B]

Here're two videos for both stock & virtual systems...

UPDATE:
Now, you could run the following command to print the current system (stock or virtual) and the system device (physical partition or loop device):

MultiSystem status

Note: The block device number (mmcblk0p23) may vary per device & per variant !

 

[hsbadr]

How to repartition microSD card for MultiSystem?

You can use any tool/program for partitioning on Android, Linux, Mac, or Windows. For example, MiniTool Partition Wizard is a good partitioning tool for Windows. So, let's use it for this task. Simply, you need to follow this PDF tutorial (thanks to @carl1961). In sum:

• Step 1: delete old partitions on SD card
• Step 2: create FAT32 PRIMARY partition
• Step 3: create EXT4 PRIMARY partition

Then, apply changes (note that the program UI may get changed in newer versions).

Notes:

• 
  This partitioning tutorial doesn't create PRIMARY partitions (it creates logical partitions). So, you need to change "Create As" from "Logical" to "Primary" when creatig a partition.
• The sizes of the two partitions are arbitrary depending on number of ROMs you plan to install on the 2nd EXT4 partition.
• The 1st partition (check size) is automatically detected as your external storage
• In Terminal Emulator or ADB shell, check the existence of the two partitions by running the following command (in red):
  

  [email protected]:/ # [COLOR="Red"]ls -l /dev/block/platform/msm_sdcc.3/[/COLOR]
  drwxr-xr-x root     root              2015-05-02 21:08 by-num
  lrwxrwxrwx root     root              2015-05-02 21:08 mmcblk1 -> /dev/block/mmcblk1
  lrwxrwxrwx root     root              2015-05-02 21:08 mmcblk1p1 -> [COLOR="Blue"]/dev/block/mmcblk1p1[/COLOR]
  lrwxrwxrwx root     root              2015-05-02 21:08 mmcblk1p2 -> [COLOR="Blue"]/dev/block/mmcblk1p2[/COLOR]

  /dev/block/mmcblk1p1 is mounted by Android as your external storage.
  /dev/block/mmcblk1p2 is NOT mounted & will be your MultiSystem partition.

 

[hsbadr]

How to check microSD card partitions for MultiSystem?

You need to correctly repartition microSD card into two partitions:

• exFAT or FAT32 for the 1st partition (your new external storage)
• EXT4 for the 2nd partition (your MultiSystem partition)

Use the directions in this post!

You should check your 2nd SD partition in EXT4 format mounted to /MultiSystem:

• check that the /MultiSystem directory exists after a reboot
• check that the 2nd SD partition (/dev/block/mmcblk1p2) is mounted to /MultiSystem by running the following command in Terminal Emulator or ADB shell:
  

  mount | grep /MultiSystem

  The output should be:
  

  /dev/block/mmcblk1p2 /MultiSystem ext4 rw,seclabel,relatime,data=ordered 0 0

 

[hsbadr]

How to check MultiSystem Installation?

The 1st thing to do after installing MultiSystem is to check the /MultiSystem directory & its contents (it shouldn't be empty!). Then, check usage by running the following commands in Terminal Emulator or ADB shell:

su
bash
MultiSystem

If it retuns "MultiSystem not found" or permission denied, try to use open MultiSystem app to Update Configurations & try again. If this does't fix it, try the following command:

/MultiSystem/bin/MultiSystem

This should work if you've MultiSystem binaries installed in (extracted to) /MultiSystem directory. If so, you can create a symlink in /system/xbin as follows:

mount -o remount,rw /system
ln -sv /MultiSystem/bin/MultiSystem /system/xbin/MultiSystem

Then, test it by running:

MultiSystem

The last thing before using it is to check the boot options: reboot & monitor the GREEN LED indicator for 3 seconds (change in the app) , which give you the following options:

• Volume UP = Primary virtual ROM
• Volume DOWN = Secondary virtual ROM
• HOME KEY = Stock System

Pressing nothing will boot the active system: stock or primary virtual system. Sure, you should have installed one or more virtual ROMs.

Backup & restore or creating/installing a virtual ROM are easy as copy & paste: all img's will be at

/MultiSystem/img/system

To backup a virtual/stock system, you have many options:

• Use create function to create from stock system
• Use copy function to copy the IMG
• Copy & paste with a new name
• Use FlashFire (fully supported on virtual/stock ROMs)
• ...

If you've IMG mounting issues, run the following commands:

mount -o remount,rw /system
busybox ln -sv /proc/self/mounts /system/etc/mtab

If this doesn't help, try mounting from Terminal Emulator or ADB shell after selecting the IMG in MultiSystem app, by running the following command:

MultiSystem mount virtual

 

[glm0025]

This is the one thing missing from my Note 4. Thank you for the detailed Q&A and i can't wait to try this tool out.

 

[hsbadr]

MultiSystem Video Tutorial

Thanks To: @Tomsgt , aka RootJunky

Don't forget to subscribe & like the video to show appreciation of his great effort & time spent in making the video :highfive::good:

 

[jazzmachine]

Thank you so much for this! My multbooting-manic* appetive is wet (read: RAVENOUS) :laugh: Thank you also for the extremely comprehensive and clear FAQ, which answered nearly every question that I had, as well as some other very helpful ones that hadn't even occurred to me! I just have a few other questions that arose when planning my own personal setup with the incredible tool (just to be clear, I don't plan on updating to TW LP.... propbably for a while). Also this is what I'm thinking for a 3x boot setup: stock odexed ROM (first question). virtual slot 1: Dynamic Kat 4.2 (KK), v-slot 2: AOSP LP... think I'm leaning towards XenonHD.

Questions:
1. Do you have a recommendation for a custom (Kit Kat) ROM compatible with the N910T? AFAIK JasmineROM isn't compatible, looks nice though. Am I correct in my interpretation that any stock-ish odexed ROM would be a good base for a stable installation? I need to look through the DevDB again, but just wondering if you had a recommendation.

2. I just want to make sure about this, because you asked and answered in the OP Would you consider using the stock kernel with the ROM in stock to be "best practice", or does it matter? I just ask because I've been a longtime supporter of the AEL kernel and would prefer to use that (with both the ROM in stock and v-slot 1). Thoughts?

3. RE: the BusyBox installation in the stock slot, is there a particular version/installer that you recommend? I usually use Sterickson's but have also used BB on Rails. both of which install to system/xbin (and remove any former installation from sbin), so just wondering if it made a difference.

Thank you so much again! BTW, just thought I'd mention that I while writing this, I saw that Amazon had PNY 128GB UHS-1 micro sd's for $75 and ordered one . I currently have 2 of that same card, one in my N4 and one in my Note 10.1 2014 and really think that PNY storage products in general are excellent. Just thought I'd put the word out.... curious why this topic made me think of that...

*multibooting-maniac adj. Descriptor of a person and/or geek who has "Hackintosh"-based triple boot installations on two or more personal conputers and needs the computer that they carrry around in their pocket to catch up with the rest of the gang :laugh:

 

[lazer9]

Would a KitKat ROM work with multisystem even though my stock is Lollipop?

Any ROM requires a compatible kernel & modem. So, running KK ROMs requires flashing KK firmware (namely, kernel & modem). This may work with MultiSystem on other devices, especially if the bootlpoader is unlocked. For example, I plan to add features for Note 4 DevED to allow different Android versions (including AOSP, manufacturer-based, & probably Linux systems) by utilizing kernel swapping or execution.

First off, this sounds like a really nifty and useful program/app/modification? Sorry, I don't know what to really call it.

As per the above quoted, I am a little confused. The part about (same kernel)? I may be missing something but in regards to being able to run Lollipop ROM along with KitKat ROM either of which located as primary or virtual (SDcard) , how is this actually possible? As far as I know, while we can use say COD6 - bootloader & modem, I am not aware of an actual "Kernel" that could support both? Hope I am voicing this correctly... :silly:

Other question and I apologize if I missed it as I tried my best to read the well detailed OP's...

- What actual recovery is being used? Can I assume TWRP, and if so, is it a "Special - modified version" OR can we use any of the later TWRPs at our choice?

Thanks! Interested in following this!

 

[lazer9]

Thank you so much for this! My multbooting-manic* appetive is wet (read: RAVENOUS) :laugh: Thank you also for the extremely comprehensive and clear FAQ, which answered nearly every question that I had, as well as some other very helpful ones that hadn't even occurred to me! I just have a few other questions that arose when planning my own personal setup with the incredible tool (just to be clear, I don't plan on updating to TW LP.... propbably for a while). Also this is what I'm thinking for a 3x boot setup: stock odexed ROM (first question). virtual slot 1: Dynamic Kat 4.2 (KK), v-slot 2: AOSP LP... think I'm leaning towards XenonHD.

Questions:
1. Do you have a recommendation for a custom (Kit Kat) ROM compatible with the N910T? AFAIK JasmineROM isn't compatible, looks nice though. Am I correct in my interpretation that any stock-ish odexed ROM would be a good base for a stable installation? I need to look through the DevDB again, but just wondering if you had a recommendation.

2. I just want to make sure about this, because you asked and answered in the OP Would you consider using the stock kernel with the ROM in stock to be "best practice", or does it matter? I just ask because I've been a longtime supporter of the AEL kernel and would prefer to use that (with both the ROM in stock and v-slot 1). Thoughts?

3. RE: the BusyBox installation in the stock slot, is there a particular version/installer that you recommend? I usually use Sterickson's but have also used BB on Rails. both of which install to system/xbin (and remove any former installation from sbin), so just wondering if it made a difference.

Thank you so much again! BTW, just thought I'd mention that I while writing this, I saw that Amazon had PNY 128GB UHS-1 micro sd's for $75 and ordered one . I currently have 2 of that same card, one in my N4 and one in my Note 10.1 2014 and really think that PNY storage products in general are excellent. Just thought I'd put the word out.... curious why this topic made me think of that...

*multibooting-maniac adj. Descriptor of a person and/or geek who has "Hackintosh"-based triple boot installations on two or more personal conputers and needs the computer that they carrry around in their pocket to catch up with the rest of the gang :laugh:

@jazzmachine Curious if you ever found out anymore information on this elsewhere that I may be missing. I see it's reference, youtube videos, and whatnot coming up in various threads but little known as far as it's usability on a (910T) Note 4 - mainly what kernel has to be used that supports kexec on STOCK?

 

[jazzmachine]

@jazzmachine Curious if you ever found out anymore information on this elsewhere that I may be missing. I see it's reference, youtube videos, and whatnot coming up in various threads but little known as far as it's usability on a (910T) Note 4 - mainly what kernel has to be used that supports kexec on STOCK?

Hey there man, wish I could provide you some useful info wrt this project, but unfortunately I've been unable to find anything directly relevant myself. However, this: http://forum.xda-developers.com/note-4/general/dual-boot-n910f-snap-dragon-variant-t3065211 (shout out and thanks to @aukhan!), which you've likely seen as well, has captured my interest. There are direct references to our device in that thread, but I haven't really been able to make any attempts towards making use of it due to "life stuff" conflicting with my phone tinkering / XDA activity . I haven't been able to follow it as much as I'd like (or hit you up with any actual "useful" info ) but at this point (from what I've read) it seems more... practical wrt our N910Ts.

BTW, I've read and been really appreciative of your contributions to the Emotion kernel thread :good: Definitely keep me posted if you make any progress towards the "multi/dual boot dream"... I'll do the same

 

[lazer9]

Hey there man, wish I could provide you some useful info wrt this project, but unfortunately I've been unable to find anything directly relevant myself. However, this: http://forum.xda-developers.com/note-4/general/dual-boot-n910f-snap-dragon-variant-t3065211 (shout out and thanks to @aukhan!), which you've likely seen as well, has captured my interest. There are direct references to our device in that thread, but I haven't really been able to make any attempts towards making use of it due to "life stuff" conflicting with my phone tinkering / XDA activity . I haven't been able to follow it as much as I'd like (or hit you up with any actual "useful" info ) but at this point (from what I've read) it seems more... practical wrt our N910Ts.

BTW, I've read and been really appreciative of your contributions to the Emotion kernel thread :good: Definitely keep me posted if you make any progress towards the "multi/dual boot dream"... I'll do the same

Thanks, I will have a look at the thread you mention. It just seems odd that this post popped up in here some time ago with some questions/replies and went completely abandoned, lol :laugh:

Like one of those teaser posts I guess. I've tried to "Google" around and found some YouTube videos along with active threads on different sections of XDA but anything coming down to usability on our N910Ts and for that matter, other devices, seem to indicated the need for a kexec Kernel in "Stock" Rom. I have yet to find/confirm ANY 910T kernel providing kexec support oddly enough but then again, maybe my google skills are lacking. :cyclops:

 

[fegar]

Primary system IMG

I can't seem to get MultiSystem to create my primary system IMG. I let it sit while the red LED is on and for quite some time afterwards but it only creates an empty file. Any suggestions would be much appreciated.

 

[DrDank]

Just happened to stumble across this, I used multirom on my older lg optimus g pro.... It worked goud until I had a few custom roms , then it just went all to hell... I think I may give this a try.

 

[PreDavid]

No Virtual IMG Mode works...

There're many ways to check whether you're running a Stock or Virtual system. MultiSystem app should include this simple check at some point. That's important to avoint ruining the Stock system & keep it safe. To make it clear to NOOBZ & anyone who's requesting "another" proof even though I owe hime nothing. Very weird!

Anyway, BusyBox mountpoint applet can print the current block/device mounted to /system mountpoint by running the following command:

busybox mountpoint -n /system

The stock system is mounts the original system partition:

[B][COLOR="Red"]/dev/block/mmcblk0p23[/COLOR][/B]

while the virtual system mounts a loop device associated with a system IMG:

[B][COLOR="Blue"]/dev/block/loop0[/COLOR][/B]

Here're two videos for both stock & virtual systems...

UPDATE:
Now, you could run the following command to print the current system (stock or virtual) and the system device (physical partition or loop device):

MultiSystem status

Note: The block device number (mmcblk0p23) may vary per device & per variant !

So I've chosen the image and tried booting it by VOL UP and over UI reboot into virtual/ active partition... both failed

/block/loop0 doesn't work, remains mmcblk0p23 though it changed to IMG Stock

Thanks for any help!!!

---------- Post added at 21:53 ---------- Previous post was at 21:48 ----------

I can't seem to get MultiSystem to create my primary system IMG. I let it sit while the red LED is on and for quite some time afterwards but it only creates an empty file. Any suggestions would be much appreciated.

How does the log show the empty file? Exit 0 or something like that? Or do you see a 0 MB sized file created?

Have you checked the MultiSystem installation?