yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] bd177:
The user partition is the same for both stock and virtual. If you upgraded FF, then you have it for both stock and virtual systems.
[Android Software/Hacking General [Developers Only]] parasthakur37:
Only working on samsung galaxy devices, not on others, for example, yu yureka.
[Android Software/Hacking General [Developers Only]] radavi98:
Permission Help

I can copy images using multisystem into /multisystem/img/system. I can use flashfire to alter those images and change ROMS. I still can not edit, add, remove, rename the files in /multisystem/img/system. The error message I get is EACCES permission denied. What can I do to have access to this directory?
[Android Software/Hacking General [Developers Only]] jimbosi:
MS install error

After some more attempts to get MS installed, here's where I'm stuck:

I follow the below process, which is basically OPs instructions:

Mount RootFS and /system (the commands don't "stick"--see below)

Install Busybox to /system/xbin

Install MS apk

Install MS in app

Wait 3 minutes (per YouTube videos)

Update Busybox via command line--and this is where things deviate.

I get an error saying "read only file system." I can re-run the previous mount commands (mount -o remount,rw rootfs (and) /system. Update Busybox then appears to work.

Checking for the MultiSystem files is successful (the files are there).

Curiously, "MultiSystem status" returns my current IMG is Jasmine 5.0.1, but I did a clean install of 6.1 (OF1). Also "MultiSystem partition is not mounted."

The system log shows mounting the ext4 partition is "busy." My partition tool shows it as unmounted.

So, from there nothing works. Following some rather simple directions is not getting the results/success others are getting. Anyone have any clues to get me going here? TIA for the help!
[Android Software/Hacking General [Developers Only]] siggers:
What explorer are you using? I would suggest FX file explorer in root mode.
[Android Software/Hacking General [Developers Only]] radavi98:
Ive tried es explorer, root explorer, and now fx root and all say denied access. Ive tried changing the permissions via su on terminal emulator also to no avail. I can understand not being able to edit an active img, but I can copy an img into the dir via multisystem app....but thats it. Can not remove or change the name
[Android Software/Hacking General [Developers Only]] jimbosi:
OK, for those having difficulty installing MS (like me)--partition order on the SD card matters. In my first try (and where the install failed), I formatted the SD card with the ext4 partition first, then the FAT partition.

So I reformatted the card (I used aparted) with the FAT (actually exFAT) partition first, with the ext4 partition to the right.

Somehow that partition order also solved another problem, which is that I couldn't write an IMG file to /MultiSystem/img/system, but now I can.

I guess my remaining question is to boot to the virtual system, why do I have to wipe data? The stock system is identical to the virtual one (Jasmine 6.1). I'll do it, but I don't understand exactly why.

Good luck to me, and I hope my experience helps someone.

---------- Post added at 04:00 PM ---------- Previous post was at 03:57 PM ----------

Also, on the first reboot on having installed MS, the SELinux status was set to Permissive, even though I was set to the stock ROM. I didn't have to su/toggles.
[Android Software/Hacking General [Developers Only]] marianofxp:
Hello this tool works with lollipop kernel?

Enviado desde mi LG-E987 mediante Tapatalk
[Android Software/Hacking General [Developers Only]] marianofxp:
Hello good day. my name is Mariano, was watching your videos and I think I can help with my problem. I was trying to follow the letter of your video installation rom jazmine 6.1 with MultiSystem and I failed. and copied the file img rom the right place but boot the terminal screen goes black. and also tried to do a factory reset and all I got is hurt and the stock rom and not the img as describe in the video. nothing but still not as it is and I would like to know is how to turn a regular zip installation for recovery in img To start with multisyatem. I would appreciate if you can help me and who still do not know much and I think the multisystem fabulous as it supposedly can install rom virtuale lollipop ... Greetings and thanks ...

Enviado desde mi SAMSUNG-SM-N900A mediante Tapatalk
[Android Software/Hacking General [Developers Only]] marianofxp:
when you calculate for version 2? you got any proof?

Enviado desde mi SAMSUNG-SM-N900A mediante Tapatalk
[Android Software/Hacking General [Developers Only]] Nappyloxs:
Any chance this will work on vzw note 10.1 (2014)?
[Android Software/Hacking General [Developers Only]] Doubleyou:
Does this application supports Mot G 2014 XT-1068?
[Android Software/Hacking General [Developers Only]] silvoren:
Can't install multysystem

I was running MultySystem with a 5.1 virtual rom. I tried to update to 6.1 Screen said updating jasminerom then it froze. i did a factory data reset and reinstalled MultySystem but when i tried to copy 6.1.img my phone would freeze. I reformatted SD card also tried new SD card. As of now i cant install MultySystem at all. Using FX explorer i see the MultySystem folders but in terminal emulator MultySystem status says MultySystem not found?
[Android Software/Hacking General [Developers Only]] silvoren:
i think i found my problem my SELinux is Enforcing how to change to permissive?
[Android Software/Hacking General [Developers Only]] workdowg:
https://f-droid.org/repository/browse/?fdid=com.mrbimc.selinux Selinuxmodechanger

From my LG-G4, Rooted running Stock 5.1
[Android Software/Hacking General [Developers Only]] silvoren:
Thanks I tried that no luck
[Android Software/Hacking General [Developers Only]] workdowg:
Really, I've used it on both the G3 and G4. I had init scripts that needed to run and some kernel tweaks that needed it.

From my LG-G4, Rooted running Stock 5.1
[Android Software/Hacking General [Developers Only]] kerryh:
What is the benefit, if any, of using this over multiROM?

I did see where the Dev had mentioned expanding support to other devices (M8?) once a stable point had been reached with currently supported devices...Any mention if that has happened yet? I like using multiROM and would also would like a chance to drive this application and give useful feedback if allowed.

Thank you Dev.
[Android Software/Hacking General [Developers Only]] hsbadr:
MultiSystem version 2+ will be going commercial

MultiSystem version 2+ will include many improvements that make it user-freindly, allow loading virtual ROMs without microSD card partitioning, and maintain secure environment to support Mobile Payments such as Android Pay and/or Samsung Pay (if compatible) on rooted Android devices [Tested on Samsung Galaxy Note 4 + Android Pay]. An option to load virtual ROMs from internal storage is under testing, to support Android devices that do not have microSD card slot.

MultiSystem is a powerful and –currently– complicated tool that needs dedicated support. So, the next versions of MultiSystem will be going commercial to assign time to the project. New feature requests and bug reports will be posted in a new thread, most likely in the Paid Software Announcement and Discussion section. No ETA!
[Android Software/Hacking General [Developers Only]] cherryb8844:
Did this work on galaxy s2 i9100 ?
[Android Software/Hacking General [Developers Only]] electrikjesus:
Could you also add support for the G4 if possible?
[Android Software/Hacking General [Developers Only]] exefixxer:
That are great news! I like the project and the idea a lot!

I´m very interested in trying the new version out on my S4.

What first came into my mind was, it would be a great feature to be able to generate totally independent "Virtual Machine Containers" like on a PC with VM-Ware.

I mean also the option to NOT share any files or information of the VM-ROM with the Host-ROM. And run in parallel with the Host-ROM.

My idea behind this is, to not only be limited to Android, but to work with multiple OS like Sailfish and Ubuntu Touch on natively incompatible handsets.

Basically like the first VM-Ware on Android.

Is this technically possible?

Would really like to hear your opinion on this...
[Android Software/Hacking General [Developers Only]] cangcan:
will this work with x86 device such as asus zenfone 2?
[Android Software/Hacking General [Developers Only]] hsbadr:
Some of what you say is already planned in version 2 as announced here. Loading virtual Linux distros via CHROOT is possible, but NATIVELY booting Ubuntu Touch (or any other OS) will require a custom kernel (and porting) for each device.

Not yet, only ARM devices listed here are currently supported. Building it for other devices/architectures would be straightforward though.

It may work, but not tested on these devices.
[Android Software/Hacking General [Developers Only]] radavi98:
Bricked Note 3

Had Multisystem running and now phone when booted does not show the green light and will only boot to the samsung logo with the moving dots and a pulsating blue light. Can boot to download mode and also to bootloader. At the bottom of that screen it says multisystem-csc is loaded. Would llike to save root, how can I get a working OS on? Tried to install jasmine 5.0 and 5.1 but says that the efooter is bad. Sorry I didnt write exact messages but I can not find any working info out there. Any hints?
[Android Software/Hacking General [Developers Only]] surajpai524:
Can I use this for yureka???
[Android Software/Hacking General [Developers Only]] Livi-Tech:
Could you add support for galaxy s3 mini - if it is possible???
[Android Software/Hacking General [Developers Only]] g17123:
Does this work with Canadian varient of Samsung s5?
[Android Software/Hacking General [Developers Only]] mixmoto:
hi! i have got a xiaomi mi4.

i ask you if you can add support for this device! if yes you make me very happy!

thanks!
[Android Software/Hacking General [Developers Only]] mirsaeed.namdar:
Does it support sony Xperia z c6603 or not?

And probably i guess it doesn't support it,then why have you named this for all android devices while it is not true.
[Android Software/Hacking General [Developers Only]] bnwg:
As far as I understand as long as the device is booted into img (/block/loop) not stock it is safe to flash any flashable zip even a zip ROM.

I would like to confirm this before I would flash another ROM.

Thanks.
[Android Software/Hacking General [Developers Only]] jksyankeesrock:
When I tap on "Select .zip file" nothing happens. Does anyone else have this problem or is able to provide a solution?
[Android Software/Hacking General [Developers Only]] mattwheat:
I'm running an ASUS ZenFone 2 on Android 5.1 and 64bit system. Will this run on our device? If not what do you need or what can I do to help get it working and support for the ZenFone 2?
[Android Software/Hacking General [Developers Only]] munirshah77:
Is it possible to have have stock rom and cm13 run using multisystem?? So far I have seen that it allows you to have two instances of the same rom but can a different rom be used as virtual rom?
[Android Software/Hacking General [Developers Only]] gcutter:
Ok I have spent hours and hours reding / trying to install MultiSystem. I have following the directions to the T. I get all install on both Jasamine 5.0.2 and 6.1 as Stock get thru the install and reboot and the /MultiSystem folder is empty after reboot. I never see a green LED on during reboot.

Can I use 6.1 As Stock Rom and then install MS and run 6.1 as Virtual Rom?

I never see SE go to Permissive it is Enforcing.

I am using a 128GB Samsung SD Card if that matters.
[Android Software/Hacking General [Developers Only]] muttleytm:
After install and thinking I have created, saved, mounted virtual image I still get dev/block/mmcblk0p14 when I run MultiSystem status in terminal.

Anyone have any ideas what I need to do? Galaxy SIII sprint
[Android Software/Hacking General [Developers Only]] mauriicio21:
Cant make work in S5 (900t) 5.1.1

Installed multirom, busybox, but in terminal multirom not found
[Android Software/Hacking General [Developers Only]] milladog:
Why has this never been updated so many issues with it? I install it on a cell after setting images up and getting them to boot it just vanishes. This is not right at all!
[Android Software/Hacking General [Developers Only]] martyh1:
Sorry for the cross forum post. I posted this in the note 4 specific thread also here.

This tool doesn't seem to get a lot of replies or maybe support. But here's my experience with my first recent attempt.

I wanted to try to create and boot images from two different custom ROMs. I have a tmobile note 4. I followed the directions and after a few bumps, got it working (verified with the command "MultiSystem status" in terminal emulator). There's no green LED light at boot. It's a red one. I found somewhere instructions that said to boot a different img, you had to use volume-up plus power, etc, at boot time. I can't find those instructions again. Strange that they aren't included in the main threads.

When I say I got it to work, that only means I successfully booted an image off my SD card that I created from the internal "stock" system (really a Custom ROM). Not sure what that alone does for me. I created another image (after restoring another custom ROM I had). I then restored my other ROM from TWRP backup. I then tried booting into that 2nd image, but it seemed to hang on the startup animation (samsung in this case). Maybe it would have booted given enough time? Don't know. I gave it quite a bit of time. In the process, it affected booting into my other image. Somehow, something was changed. When I booted the first img that I could boot successfully before, that image now came up like it was new, in a way (and it took a very long time booting because it had to go through that 'optimizing apps' at startup). When completely booted, all the apps were there, but the the lock screen image changed to default, the system asked me to set up my lock screen, etc. Booting that 2nd img caused something to change, not sure what. I had to TWRP restore to get back. Funny, even after that TWRP restore, the launcher background image changed.

My initial conclusion is that the ROM you've made an image from needs to support MultiSystem in some way. With my current findings, I haven't found a good use for this yet (since I couldn't boot that 2nd image which was created from a 2nd custom ROM).
[Android Software/Hacking General [Developers Only]] bkkzak:
I just wanted to extend an offer to help with v2. I have an arm, arm64, and x86 device that I can test on. If you need any sort of feedback or help, just let me know!
[Android Software/Hacking General [Developers Only]] hsbadr:
Thank you for your interest!

As I mentioned earlier, I received ~ZERO support for this project and decided to go commercial or stop development to save my time. I keep this thread open for everyone who may find the tool (MultiSystem v1.x) or the info useful for current or future devices.
[Android Software/Hacking General [Developers Only]] ultravioletnanokitty:
sure would be great if you put the source code for this tool, which is almost certainly based upon multiple pieces of gpl software, in its completely empty github repository... it's ridiculously selfish (and likely gpl non-compliant) to not release the source code for the current version. i would like to develop this tool further for the galaxy ace style s765c, a currently completely unsupported locked bootloader device. without a more modern place to start, i'll have to resort to a more basic 2nd-init hijack. it would be nice to start getting more elegant rom management solutions on these locked devices!
[Android Software/Hacking General [Developers Only]] hsbadr:
Thanks for the polite request!!!

I've pushed the source code of the current version, as is, to MultiSystem repo. I wanted to clean it up and update the preliminary design (with likely many mistakes) of my first APK, but I didn't have time to finish it.
[Android Software/Hacking General [Developers Only]] ultravioletnanokitty:
i'm sorry, i should have been more polite... i've experienced many developers refusing to publish their source code and i was expecting a similar response.

thank you! whatever the condition of the code, now i can work on it at least! :D
[Android Software/Hacking General [Developers Only]] fyter:
Is it possible to make this awesome program compatible with LG G Flex 2? That phone has locked bootloader too :(

I'd like to help in anyway possible to make this to happen. Thanks.
[Android Software/Hacking General [Developers Only]] tiger2wander:
Thank you for make this possible on Note 4.

I'm just installed this application and trying to create ROM.

I think the UI is a bit confusing and complex with too many text and long page with panels. It should better with tab like step and auto detection to hide some UI to make it more clean and easy to use. I'm using MultiROMMgr on Nexus 4 and I think it has good UI and good approach to adapt this feature, you can take a look on main repository here: https://github.com/Tasssadar/MultiROMMgr

BTW, I'm not read the source code yet, I guess the system image was dump by `dd`, if it going this way, I think I can manual create it by `dd` on Linux and copy to SD card, this way it will speedup the install process and might use for quick ROM development as I can imagine. Isn't it?
[Android Software/Hacking General [Developers Only]] joe7dust:
"requirements: USB SD Card reader." AWWWWWWW damn. Just when I was starting to get excited about setting this up, now I guess I gotta go buy some stuff. Unless there is a way around this? Was wondering why my phone not detected at all in that partition program... Strange it shows both my internal and sd card just fine in windows explorer.

Annnd now I'm stuck in a bootloop! Awesome.

edit: OK I've decided to reflash with Odin to a "better" fw and hopefully that will fix this, anyone know the best one to use when trying to install a 6.0.1 rom like Insanity for the g900t?
[Android Software/Hacking General [Developers Only]] joe7dust:
Can someone please help me get this working? I have stock 5.1.1 installed and I'm trying to get a 2nd boot or virtual boot that is 4.x so I can run an app that is no longer developed and was broken by 5.x

I have followed all the steps but it doesn't seem to be installing MultiSystem at all. When I hit install it shows SU access granted and then some command lines, but then nothing else seems to happen. I expected some sort of feedback like "Successfully Installed!". Also when I then type "MultiSystem" in terminal it says file not found so I don't think it is ever actually installing properly.

It would help if there was some sort of log or error displayed when you click Install MultiSystem but it is not actually installed...
[Android Software/Hacking General [Developers Only]] wanb1i:
Can't run kitkat & Lollipop at the same time, unless your bootloader is unlocked (which you can now do). :) Better to unlock it & flash kitkat rom, back it up with twrp or flashify then flash the lollipop rom, back it up and jump back & forth that way.

Or flash marshmallow... :cool:

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

Now that we can unlock the bootloader, MultiSystem is kind of unnecessary...
[Android Software/Hacking General [Developers Only]] joe7dust:
Well... that whole process would probably take 15 minutes or more each time wouldn't it? Simply wouldn't be worth the effort to get this 1 app running while still being about to run the latest FW. Kind of defeats the whole purpose of MultiROM doesn't it? Also I would think my overall system performance would be better if I ran the newest FW natively then used the virtual ROM for the 4.x install. But maybe there isn't a performance difference between those 2 hypothetical configs.

Anyways, I think my BL is unlocked. I have TWRP flashed from Odin and am rooted. I've gone back and forth from 4.x to 5.x many times the past couple of weeks trying various custom ROMs that all sucked, before deciding on debloating my own version of 5.1.1

So what do I need to do to be able to run the latest FW for my device (5.1.1) and still be able to run an app that only works in Kitkat ?

edit: Also, I have considered flashing 6.0.1 by using files designed for the g900F but I've been warned this is a good way to hard brick the phone, and some have said it's even not possible especially if my goal was to use a custom ROM that required a 6.x BL. For those 2 reasons I'm leery to even consider MM, but if you have info on 6.0.1 for g900t then I'm listening...
[Android Software/Hacking General [Developers Only]] wanb1i:
I'm running the unofficial cm13 (http://xdaforums.com/galaxy-note-3/development/hlte-spr-vzw-temaseks-unofficial-t2953375) working great for me, no problems except no 5ghz Hotspot. Really fast & smooth

, hasn't crashed in the last week. Sooooo...... No risk, no reward! :cool:
[Android Software/Hacking General [Developers Only]] joe7dust:
I don't see the tmobile s5 in your devices list. Are you sure you're running that on a g900t?

---------- Post added at 12:06 PM ---------- Previous post was at 11:40 AM ----------

Checked that thread and don't see g900t listed in supported devices either...

edit: yep... thats for the note 3 only. -.- "---Quote (Originally by joe7dust)---

Does this work on the G900t? I thought you can't run MM on tmobile s5 yet, but someone just pointed me here and claims it will work...

---End Quote---

Whoever pointed you here was wrong. This ROM is for the Note 3."
[Android Software/Hacking General [Developers Only]] wanb1i:
Yup, you're right, my bad, thought this was the note 3 MultiSystem thread. Just unsubscribed. Won't happen again!
[Android Software/Hacking General [Developers Only]] joe7dust:
Np, it happens... now back to my problem.

"Can someone please help me get this working? I have stock 5.1.1 installed and I'm trying to get a 2nd boot or virtual boot that is 4.x so I can run an app that is no longer developed and was broken by 5.x

I have followed all the steps but it doesn't seem to be installing MultiSystem at all. When I hit install it shows SU access granted and then some command lines, but then nothing else seems to happen. I expected some sort of feedback like "Successfully Installed!". Also when I then type "MultiSystem" in terminal it says file not found so I don't think it is ever actually installing properly.

It would help if there was some sort of log or error displayed when you click Install MultiSystem but it is not actually installed..."

I've uploaded logs to help pin down the issue, think it has to do with the format of the SDcard. That part seemed overly complex to me. I wish it could have just been scripted into a flash file or something. http://www.filedropper.com/syslogdumps