[Q&A] MultiSystem for Android

[hsbadr]

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.

It's under testing for VZW/ATT S4, S5, Note 3 & (Note 4 DE); more devices will get supported. It'll take more time to support the devices I don't own (check my signature!) though.

 

[R-1 Rider]

How do I fix the mtab error?



Sent from my SM-N900V using Tapatalk 2

Tada10,
how did you fix your mtab error? I get the mtab error and can not log in to the virtual system. I try to mount the virtual image, but every time I hit update configuration it doesn't seem like it does much except removes the Primary System IMG from displaying. I have run the commands in terminal and they show me running the stock image still.

Any help would be appreciated

 

[Tada10]

Tada10,
how did you fix your mtab error? I get the mtab error and can not log in to the virtual system. I try to mount the virtual image, but every time I hit update configuration it doesn't seem like it does much except removes the Primary System IMG from displaying. I have run the commands in terminal and they show me running the stock image still.

Any help would be appreciated

See screenshot. That's what fixed it.

The IMG mounting issue



Sent from my SM-N900V using Tapatalk 2

 

[R-1 Rider]

See screenshot. That's what fixed it.

The IMG mounting issue



Sent from my SM-N900V using Tapatalk 2

Thanks for the quick reply. I thought I did that, but I guess not. Unfortunately now it won't get past the boot screen. Booted back into stock system and I will keep digging to see what's up.

Thanks again.

 

[Seion]

adb shell partitioning

Is there a way to partition the External SD Card via adb shell for multisystem? I don't think I have a card reader currently.

 

[BobC43]

Booting from Virtual Hangs

I have MultiSystem installed and seem to pass all the tests. When I attempted to make an Image from the Stock it appeared to work. But when I went to boot into the virtual Rom it hung. Had to pull SD card to boot up and turn off MultiSystem. I may have a corrupt img.

How do I delete the coppied image, as I thought it was in /MultiSystem/ under root.

What are the steps to copy the stock rom, and boot into a virtual rom.

Thank you

 

[R-1 Rider]

I have MultiSystem installed and seem to pass all the tests. When I attempted to make an Image from the Stock it appeared to work. But when I went to boot into the virtual Rom it hung. Had to pull SD card to boot up and turn off MultiSystem. I may have a corrupt img.

How do I delete the coppied image, as I thought it was in /MultiSystem/ under root.

What are the steps to copy the stock rom, and boot into a virtual rom.

Thank you

The image is located in:
/MultiSystem/img/system

I had a problem with Multisystem making an image from the stock Rom. The image was corrupted, so I pulled the system image from Jasmine 5.0 and placed it in the Multisystem/img/system folder and now I am running on the virtual side. Time to start tweaking and see what I can mess up....

 

[burbank]

The image is located in:
/MultiSystem/img/system

I had a problem with Multisystem making an image from the stock Rom. The image was corrupted, so I pulled the system image from Jasmine 5.0 and placed it in the Multisystem/img/system folder and now I am running on the virtual side. Time to start tweaking and see what I can mess up....

This is good to know. I have been unable to get MS to build a virtual image from stock. So maybe I'll try that.

---------- Post added at 03:09 PM ---------- Previous post was at 02:39 PM ----------

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 command in Terminal Emulator or ADB shell:

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

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:

busybox 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

I can't get through these steps successfully and I have no idea why. Is the MS app supposed to offer any feedback when the user presses a button? (All I get is are messages that the process has been granted su permissions.)

When I go through the troubleshooting steps above I have more success if I do a sudo first but I still can't get MS to launch from terminal.

Will a future version of MS do all of the partitioning and setup automatically or will that always be a manual process?

Thanks!

---------- Post added at 03:12 PM ---------- Previous post was at 03:09 PM ----------

What are the steps to copy the stock rom, and boot into a virtual rom.
Thank you

There's a button in the multisystem app that is supposed to build an image from the stock ROM. But I don't think it's working for me. If it is I'm not getting any feedback at all and when I look in the image directory within multisystem using the terminal there's nothing there.

 

[hsbadr]

Is there a way to partition the External SD Card via adb shell for multisystem? I don't think I have a card reader currently.

You may try AParted from Play Store, but I think it doesn't work on LP.

I have MultiSystem installed and seem to pass all the tests. When I attempted to make an Image from the Stock it appeared to work. But when I went to boot into the virtual Rom it hung. Had to pull SD card to boot up and turn off MultiSystem. I may have a corrupt img.

How do I delete the coppied image, as I thought it was in /MultiSystem/ under root.

What are the steps to copy the stock rom, and boot into a virtual rom.

The image is located in:
/MultiSystem/img/system

I had a problem with Multisystem making an image from the stock Rom. The image was corrupted, so I pulled the system image from Jasmine 5.0 and placed it in the Multisystem/img/system folder and now I am running on the virtual side. Time to start tweaking and see what I can mess up....

You should turn off screen timeout (set to max. 10 minutes) & wait for the RED LED to disappear (should take a few minutes). Also, check the size of the created IMG before reboot. It's located at

/MultiSystem/img/system

I can't get through these steps successfully and I have no idea why. Is the MS app supposed to offer any feedback when the user presses a button? (All I get is are messages that the process has been granted su permissions.)

When I go through the troubleshooting steps above I have more success if I do a sudo first but I still can't get MS to launch from terminal.

Will a future version of MS do all of the partitioning and setup automatically or will that always be a manual process?

I focused on the main functionality of MultiSystem binary (/MultiSystem/bin/MultiSystem) & this is my 1st Android app ever & the initial release of MultiSystem. So, SURE, it'll get improved in the future. I just wanted to release something working very quickly for you to survive root while mod'ing LP ROMs.

 

[gnexdude]

This is where I'm stuck:
"REBOOT to check GREEN LED for boot options & check permissive SELinux..."
I'm following all steps and checking everything, I got the files installed in the MultiSystem folder, I'm just not getting boot options to check permissive SELinux...help anyone? :silly:

 

[captbeard]

Does multisystem mean anything to those on a retail phone that STARTED on 4.4.4 or 5.0? Or only those who got one when 4.4.2 rooting was still possible?

 

[nagi_007pk]

Awesome work!

Hi hsbadr!
While I know the FAQ on the first page highlights a great deal on how this project is supposed to work and it does completely answer most of questions however, I needed to know if kernel modification is possible for secured bootloaders?

I currently own an AT&T Note 3 and have been running Firekat since about two months on KK... Would this also pave the way for AOSP? If at all.

Delighted to have a dev still confidently looking out for the community

Thanks mate

 

[Dodger70]

Having trouble creating a symlink when I run this command: mount -o remount,rw /system i get Permission Denied what am I doing wrong?

 

[G.moe]

Having trouble creating a symlink when I run this command: mount -o remount,rw /system i get Permission Denied what am I doing wrong?

Type "su" and press enter first to ensure you are acting as root.

Does multisystem mean anything to those on a retail phone that STARTED on 4.4.4 or 5.0? Or only those who got one when 4.4.2 rooting was still possible?

Root is required to use MultiSystem; please read the first posts carefully.

 

[Dodger70]

Type "su" and press enter first to ensure you are acting as root.

OK its working now but after I type this command:
ln -sv /MultiSystem/bin/MultiSystem /system/xbin/MultiSystem
I get:
/system/xbin/MultiSystem: File Exists
then I run
MultiSystem (to test the symlink)
and I get:
not found
I cant seem to figure this out.

 

[G.moe]

OK its working now but after I type this command:
ln -sv /MultiSystem/bin/MultiSystem /system/xbin/MultiSystem
I get:
/system/xbin/MultiSystem: File Exists
then I run
MultiSystem (to test the symlink)
and I get:
not found
I cant seem to figure this out.

Try removing the v:

ln -s /MultiSystem/bin/MultiSystem /system/xbin/MultiSystem

 

[captbeard]

Root is required to use MultiSystem; please read the first posts carefully.

I did, but was still unsure because reading some of it was difficult to do, so I wanted clarification. I appreciate your answer, though.

 

[Dodger70]

Try removing the v:

ln -s /MultiSystem/bin/MultiSystem /system/xbin/MultiSystem

Same result.

 

[G.moe]

Same result.

Try:

ln -s /MultiSystem/bin/MultiSystem /system/bin/MultiSystem

A crucial part of MultiSystem's initial development will be setting it up to automatically configure devices appropriately, and I've told @hsbadr about similar issues with the VZW GS4, so I imagine he's already looking into this.

 

[gnexdude]

Try:

ln -s /MultiSystem/bin/MultiSystem /system/bin/MultiSystem

A crucial part of MultiSystem's initial development will be setting it up to automatically configure devices appropriately, and I've told @hsbadr about similar issues with the VZW GS4, so I imagine he's already looking into this.

I thought MultySystem is a read-only file...that's what I'm getting, thanks for the advice guys :good: