[Q&A] MultiSystem for Android

hsbadr · May 3, 2015 at 9:22 PM

K03WL3R said:
Okay, so I have partitioned my SD card and I'm stuck on "You should check your 2nd SD partition in EXT4 format mounted to /MultiSystem" how do I make the Multi system directory on my EXT4?

5.0.2 does it automatically! You should find /MultiSystem directory after a reboot when you're on 5.0.2. I assume you've done the SD partitioning as described here (2 PRIMARY partitions). Then check this!

Grompy · May 3, 2015 at 9:22 PM

K03WL3R said:
Okay, so I have partitioned my SD card and I'm stuck on "You should check your 2nd SD partition in EXT4 format mounted to /MultiSystem" how do I make the Multi system directory on my EXT4?

Read the instructions. Posts 1-6 somewhere through there it tells you everything you need to check and what else you need to do to get multisystem functioning correctly.

Sent from Hsbadr's MultiSystem Ready LP Rom!

hsbadr · May 3, 2015 at 9:30 PM

Grompy said:
Edit: That was it.. I just activated another copy of my stock system I had made prior to creating that file and now the file isn't there.. so looks like it's working fine.. sorry about all the posts.. might want to fix the false positive so someone doesn't accidently mess up their stock system.

Here's how to check if the IMG is corrupted from the log file or MultiSystem status

Code:

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

G.moe · May 3, 2015 at 9:39 PM

On the VZW S4, the SD card is found at msm_sdcc.2, not msm_sdcc.3, so you might need to add a note about that in the card preparation section.

Have you (or has anyone else) tried using this with KitKat as stock? I see documentation about running kitkat when lollipop is stock, but what about running kitkat when kitkat is stock, or running lollipop when kitkat is stock? I haven't tried installing MultiSystem yet from KitKat, however I will if I don't hear from you shortly.

Edit: Also, if you want to message over Telegram or elsewhere for ease of communication, send me a PM.

hsbadr · May 3, 2015 at 9:46 PM

G.moe said:
On the VZW S4, the SD card is found at msm_sdcc.2, not msm_sdcc.3, so you might need to add a note about that in the card preparation section.

Have you (or has anyone else) tried using this with KitKat as stock? I see documentation about running kitkat when lollipop is stock, but what about running kitkat when kitkat is stock, or running lollipop when kitkat is stock? I haven't tried installing MultiSystem yet from KitKat, however I will if I don't hear from you shortly.

Edit: Also, if you want to message over Telegram or elsewhere for ease of communication, send me a PM.

I use the physical SD partition (/dev/block/mmcblk1p2) not the link & it can easily changed in MultiSystem build.prop. So, no worries!

As for KK, it was originally running on KK (not released b/c Safestrap was working already), but I made many changes to fix it on LP.

Long story short, fixing it on KK is much eaier if it won't work by default.

Tada10 · May 3, 2015

hsbadr said:
Here's how to check if the IMG is corrupted from the log file or MultiSystem status

Code:

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

Not sure what I am doing wrong. I can't get it to use /dev/block/loop0

Sent from my SM-N900V using Tapatalk 2

Tada10 · May 3, 2015 at 10:01 PM

Forgot the logs plz look.

Sent from my SM-N900V using Tapatalk 2

hsbadr · May 3, 2015 at 10:02 PM

Tada10 said:
Not sure what I am doing wrong. I can't get it to use /dev/block/loop0

Your Active IMG is corrupted! Create a new one or use the system.img from 5.0 ZIP.

Also Update Configurations & check BusyBox version!

Zrutisan · May 3, 2015

Well, this is weird : I installed an app on my virtual ROM and I find it in my stock ROM... Is it normal?? I checked using busybox mountpoint command and I'm definitely not on the same partition...
EDIT : Actually it's identical, whatever I'm doing on my virtual rom is ported back to the stock partition. I'm very confused.

hoffeva · Mar 25, 2015 58 5 0

Zrutisan said:
Well, this is weird : I installed an app on my virtual ROM and I find it in my stock ROM... Is it normal?? I checked using busybox mountpoint command and I'm definitely not on the same partition...
EDIT : Actually it's identical, whatever I'm doing on my virtual rom is ported back to the stock partition. I'm very confused.

Doing things like installing apps only affects the internal storage on the phone, so it affects all ROMs, virtual or not. Only the system files themselves are stored on the sdcard in the multisystem partition.

Sent from my SM-T700 using XDA Free mobile app

Gabbyii · Aug 3, 2011 33 3 0

Multisystem Safe ROMs

So is there a way to tell if another ROM 's updater-script is safe/compatible? (and if its not safe and we flash/convert it - will it brick our phones?) or do we need to wait for ROMs to be released that are Multisystem compatible?

Thanks

Quote:

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!!

Zrutisan · Mar 10, 2014 37 10 0

hoffeva said:
Doing things like installing apps only affects the internal storage on the phone, so it affects all ROMs, virtual or not. Only the system files themselves are stored on the sdcard in the multisystem partition.

Sent from my SM-T700 using XDA Free mobile app

Oh ok, thanks for replying!
So let's say I delete SystemUI or an important system app, I'm screwed? Since SystemUI will be gone in all of my virtual roms.

hoffeva · Mar 25, 2015 58 5 0

Zrutisan said:
Oh ok, thanks for replying!
So let's say I delete SystemUI or an important system app, I'm screwed? Since SystemUI will be gone in all of my virtual roms.

No. Systemui is a system app, so it is installed in the system files. Apps that you yourself install are just regular apps so they aren't in the system directory. System apps are part of the system files.

Sent from my SM-N900V running JasmineROM 5.0.2 Virtual with MultiSystem

Grompy · May 3, 2015 at 11:42 PM

Any user app is by default stored in the /data partition which is shared among your stock system and virtual systems. If you want to only install on a virtual rom you'll have to convert from a user app to a system app via titanium backup or some other app. Or manually push the app to /system/app.

Sent from Hsbadr's MultiSystem Ready LP Rom!

Tada10 · May 3, 2015 at 11:49 PM

How do I fix the mtab error?

Sent from my SM-N900V using Tapatalk 2

murphyjasonc · May 3, 2015 at 11:51 PM

Zrutisan said:
Well, this is weird : I installed an app on my virtual ROM and I find it in my stock ROM... Is it normal?? I checked using busybox mountpoint command and I'm definitely not on the same partition...
EDIT : Actually it's identical, whatever I'm doing on my virtual rom is ported back to the stock partition. I'm very confused.

Yes this is normal. All Roms and the stock system will share apps and data.

bishop0114 · Jan 8, 2008 403 75 0

I have tried creating an img from stock. I let it run for over an hour with the red light on... I have tried multiple times to copy system.img from 5.0 but it shows copying to the MultiSystem folder taking 36+ days to complete. I tried ES Explorer and Root Explorer. If I copy the same file from a folder on my SD card (fat32) to another folder, it copies in about 1 minute. I have followed the instructions so for formatting the card, all folders and files appear to be correct for MultiSystem directory. I have repartitioned the card a few times with the same result. Any ideas?

Tada10 · May 4, 2015 at 1:16 AM

Finally got it!

Running my virtual copy rom!

Sent from my SM-N900V using Tapatalk 2

Tada10 · May 4, 2015 at 1:57 AM

If anyone finds a way for viper4android to work please share!

Sent from my SM-N900V using Tapatalk 2

samccfl99 · May 4, 2015 at 5:49 AM

hsbadr said:
Yes. Thanks to @muniz_ri for being willing to test for S4 & S5. I've not sent it for tesing yet; it's currently beeing tested on my Verizon Note 3.

Theoritically, any device with microSD card will get supported.

The system sounds wonderful and intense. You surely know your stuff to do this. I have read about this in muniz_ri posts a while back. It seems that this may be the only way to get control over Permissive Mode for us due to stupid Samsung/ATT. Viper4Android needs that and it is sad we lost it going to LP. Also we are all waiting for Xposed. We will be last to be sure with Touchwiz. Just wondering when do you think you might turn it over to him for testing? If you don't know, i understand. Gotta make sure it works close to perfect. Lotta high level good work coming out of devs such as FlashFire. Don't know what we would do without you guys. ROTTEN APPLES? PERISH THE THOUGHT...LOL

Thanks for all the hard work. I am an old time programmer. Must be a fun and not fun project, but very satisfying.

[Q&A] MultiSystem for Android

Inactive Recognized Developer

Senior Member

Inactive Recognized Developer

Senior Member

Inactive Recognized Developer

Senior Member

Attachments

Senior Member

Attachments

Inactive Recognized Developer

Member

Senior Member

Member

Member

Senior Member

Senior Member

Senior Member

Attachments

Senior Member

Senior Member

Senior Member

Attachments

Senior Member

Senior Member