yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] khanam:
I did manage to make it work but it is not easy. Had to modify ROM updater scripts to make them flash on the ext4 partition virtual img using flashfire. I would strongly recommend patch scripts to help people do that. Most ROM devs hard mount the stock partitions. Part of the chaos everyone is experiencing is because of that.

Secondly having a kexec routine will be of great use - being restricted to just 1 kernel kind of defeats the purpose of multi-booting. Just my humble opinion.

Finally, this is not easy to follow for most users - I am quite technical and it took me a while to figure it out. I would suggest some simplification of the UI and combination of various tasks into simpler automated tasks. For example - after installing multi system, i have realized that i always need to reboot to have the directories show up. The reboot should be forced and a warning message should warn users that it will force a reboot of the device and ask them if they want to proceed to install and reboot.... and so on for creating a system.img file (you should be asked to name it for example).
[Android Q&A, Help & Troubleshooting] fire3element:
Anyone else having trouble with the MultiSystem apk v1.3.1?

I will list the issues I had below.

[MENTION=5868929]hsbadr[/MENTION]

This is my first go around with MultiSystem, Took 3 tries to get it to install correctly. The app install did not fail, but was not functioning.

Here are the issues I am having:

MultiSystem apk not installing MultiSystem (took 5 tries and 3 reboots)

MultiSystem apk having a hard time creating a Virtual image

MultiSystem apk not showing status LED when doing actions

MultiSystem apk not properly Mounting Virtual Image (i think, will explain below)

Titanium Backup is making changes to the Virtual Image that are applying to stock ROM also (after mounting the image in MS apk)

Let me explain what I mean about the Virtual sys changes applying to stock. I mount the Virtual image in the MS apk, then make my changes in TiBu. After uninstalling apps in Tibu, those apps are gone on reboot of Virtual. Back in stock, they are still there, but have been moved from the folders they were in and are now in new places in the app drawer.

I also uninstalled the Setup Wizard apk. When I rebooted into stock, it started the setup process over again.

If I freeze an app, it is also frozen in stock.

I understand that Virtual and Stock share the same userspace. Unless I am misunderstanding the purpose of the Mount option in the MS app, I do not see why the changes I have made to the Virtual are showing up in Stock when the Virtual is mounted.

Makes me afraid to change/uninstall anything in a Virtual image.

Would you mind clarifying?

In case you or anyone else is wondering if I have an issues with the install or the base rom, I will list what steps I have made to get here.

Device: Verizon Note 3

Build : MJE

Device Build Date: 10/2013

ROM: Originally on 4.3 running HyperDrive RLS7

Steps taken to Jasmine 5.0.2 and MultiSystem:

- on 4.3 MJE HyperDrive RLS7

- TWRP_ removed all ROM slots

- TWRP,_cleared data, system, cache, dalvik

- Rebooted into Stock then shut down

- ODIN_ MJE tar

- Booted into OS, run setup, let rom settle, rebooted into OS once more

- ODIN_ MC4 tar

- Booted into OS, run setup, let rom settle

- Rooted with TowelRoot

- Installed TWRP 3.75-b04

- TWRP_ wiped data, cache, system, dalvik

- TWRP_ Installed Jasmine 5.0

- DOWNLOAD MODE_ Installed partial firmware img

- Stock Recovery _ Factory Reset

- Rebooted into Jasmine, setup, let rom settle

- Installed FlashFire, then installed Jasmine 5.0.2 update

- Installed MultiSystem apk

- Rebooted, tried to install MultiSystem from within the app, not working, rebooted, tried again, no go, tried again, nope, rebooted, tried again, no, tried once more, successful this time.

During this whole process, I did not stop to install any apps or make any changes when upgrading from once baseband to another. That should eliminate any doubts of outside interference.

Please let me know if I am missing something here. Thanks
[Android Q&A, Help & Troubleshooting] jioleight:
after i partition my unallocated space into ext4 the result is bad disk. when refreshed it goes back to being unallocated.

i also used Aparted but it i only managed to make the unallocated space into ext2. even when i set it yo ext4
[Android Q&A, Help & Troubleshooting] khanam:
aparted does not work with lollipop due to PIE error.
[Android Q&A, Help & Troubleshooting] midimench:
Had a similar problem with a brand new Samsung micro SD card that wouldn't allow mini partition tool to create an ext4 partition. It kept making ext2 partitions even though I kept checking ext4. I though I was doing something wrong until I tried another SD card, then it worked perfectly.

Sent from my Galaxy Note 3 with MultiSystem 1.3.1
[Android Q&A, Help & Troubleshooting] fire3element:
To update my post before, I am seeing a new problem.

After uninstalling all the apps I did not want (with the Virtual image mounted), I rebooted back into the stock system.

As I previously stated, the uninstalled apps had been move from their folders to another page in the app drawer. Also the initial setup pops up when you restart into stock.

I moved a few of the Verizon apps back into their folder, then rebooted. After the reboot, system process is crashing. Screen is black, but the notification bar is working.

The notification bar functions, but this is as far as you can go. After 4 restarts on the stock system, it finally booted up.

Now, all the apps I had moved back into their folders were moved again. And every restart of stock is now bringing up the initial setup.

After reading a few threads, I am afraid to do a Factory Reset. I do not want to hose my phone.

Someone knowledgeable please step in here. Advice much appreciated.
[Android Q&A, Help & Troubleshooting] hsbadr:
Sorry for not answering everyone's questions!

Factory reset is fine & sometimes recommeded (always make backups with any app you prefer; I use TitaniumBackup.). The ROMs share data ATM & you may need to wipe system data to switch a completely different ROM that may cause data conflicts & FCs.
[Android Q&A, Help & Troubleshooting] jt1998:
Don't take offense but after reading this thread and your dev thread, the consistent theme is no one can get it to work.

I would think if you want followers to be successful and not ask so many questions we need more guidance. Another video tutorial showing how to actually add 2 or more ROM's would be essential.

Again just my opinion. I've had custom ROM's on my phones and tablets and i know/realize devs are busy, have jobs etc like i do. But the difference is the response time to questions and helping in the way needed.

Thanks again and I'm looking forward to trying Multisystem when I can understand it better.

Sent from my Android 4.4.4 LGV500 on Mahdi 2.9 w RedKernel or my Galaxy S5 900T with Android 5.0 and Twi$ted Lollipop V7
[Android Q&A, Help & Troubleshooting] fire3element:
Thank you for the reply. Just want to clarify, are you saying we need to wipe system data on the stock rom after uninstalling stock apps with TItaniumBackup in the virtual rom?

Like this: Create a stock image with the MultiSystem app --> Boot into the Virtual image you just made ---> Use an app like TiBu to uninstall unwanted system apps ----> Boot back into the stock image and wipe data (from the MS app or through the Stock Recovery?).

One more thing I have not been able to get working yet. The MS app is supposed to be able to create a backup of the Virtual image.

Boot to Stock System --> Enter MultiSytem app ---> Copy Image (select the Virtual Rom you have already made in drop down menu) ----> Hit Copy Virtual Image button -----> Wait for Image to be copied.

Now, after the above steps, do we manually go into /MultiSystem/img/system/ and copy the image to a new sd card?

I used this option, and have 2 files in the location mentioned above. The larger of the 2 files is the name of the Virtual Image, but is only 42mb in size. Also, still have no notification light when the MS app is doing actions.

Trying to clear this up for you and anyone else with questions. Please feel free to PM me if you would like for me to write up some bare basic instructions. I seem to be good with being able to explain how something works to those that have a hard time understanding. (not trying to brag, just being helpful)
[Android Q&A, Help & Troubleshooting] wanb1i:
Hsbadr, can I use MultiSystem on a rooted Verizon Samsung Galaxy S3 with NE1 to install CM12 as a virtual rom?

I have MultiSystem on my Note 3 and it worked the first time with no problem, so was hoping I could put it on my wife's S3...?
[Android Q&A, Help & Troubleshooting] mai77:
multisystem is very much like safestrap

http://blog.hash-of-codes.com/how-to-safestrap/

http://xdaforums.com/tags.php?tag=multisystem

http://xdaforums.com/tags.php?tag=safestrap

very nice if it works on one's device!

---------- Post added at 12:22 ---------- Previous post was at 12:14 ----------

bs.

this stuff has been done before, on SGY, with SAFESTRAP asf.

it is tested on one single LG and some Galaxy S only.

I presume it will be some effort to port it to other devices and Android versions though.

theoretically it is just about the /etc/fstab plus some "fiddling around"

if it would not work at all the OP would not post so much stuff about his pretty cool project.
[Android Q&A, Help & Troubleshooting] jaymazz13:
So after partitioning my SD card I downloaded multisystem apk on my Verizon note 3. I installed busybox actually updated since I already had it installed and opened multisystem and installed, it looks like it installed correctly and I do see multisystem files on my root directory but it wont launch terminal emulator from the multisystem app so when I launch terminal emulator and check status I get a touch: /multisystem/log//multisystem.log: read-only file system all the way down and in between some of the logs I have a multisystem for android (c) 2014-2015 hsbadr [MENTION=243864]xda[/MENTION] message then some more logs then if you'd like to donate message then some more logs

Not sure what I did wrong, but I can't create a virtual image so something is wrong, any help would be appreciated, thanks
[Android Q&A, Help & Troubleshooting] welchy312:
No settings to get to USB Debugging

I have recently upgraded to LP5.02, and plan on going to Multisystem today as i just purchased a 64GB Micro SD card. I am still somewhat concerned because i have no options in my settings to get to enable or disable usb debugging. I believe it should be under applications, but all i have is application manager and default applications. If there anything i should re-install or do before moving over to multisystem and getting on JasminROM 5.1?

Please advise thank you!!

Adam

Samsung Galaxy note 3 SM-N900V

Android 5.0

Baseband Version: N900VVRUEOB6

Kernel Version: 3.4.0

Build #: JasmineROM_v5.0.2-LRX21V.N900VVRUEOB6
[Android Q&A, Help & Troubleshooting] speedy1979:
Go to settings>about device> scroll down to "Build number" and tap it 7 times. This will turn on developer mode under settings, now go to Developer mode and you will see USB debugging.

PS Welcome to XDA
[Android Q&A, Help & Troubleshooting] welchy312:
Ah Speedy! Thank you so much. I feel dumb now, as i remember doing this when i first got the phone after a good friend explained to me about the easter eggs. One more thing, as i am about to install multisystem. I have a 64 GB Micro SD Card, what would be your recommendations at to each partition size when formatting my card?

Thank you so much for your "Speedy" reply!

Adam
[Android Q&A, Help & Troubleshooting] xXArisXx:
Jasmine 5.1 Configuration?

I've installed the virtual JasmineROM 5.1 , but when I re-install Multisystem on 5.1 , I re-select JasmineRom 5.1 as a Primary Virtual ROM.

BUT!...

When I restart the phone it boots on Jasmine 5.0.2 :( . Can someone tell me how do i fix it or How do i have to reconfigurate Jasmine 5.1 after boot it as Primary Virtual ROM???

I m Stressed!
[Android Q&A, Help & Troubleshooting] welchy312:
Install a stable stock ROM

I am in the process of installing MultiSystem, and have a question on one of the steps here (highlighted in red): I currently have JasmineROM 5.02 installed. Is this considered a stock ROM or would i install JasmineROM 5.1 as the stock ROM? I believe the JasmineROM 5.1 would be the stock ROM i install as stock but i just wanted to make sure. Thank you for all your help. it is greatly appreciated.

Quote:

READ everything about MultiSystem here & Q&A thread

BACKUP all your data to an external storage or computer

INSTALL a stable stock ROM for your stock system

PARTITION your microSD card as described (here)

DOWNLOAD the latest version of MultiSystem APK

MOUNT rootfs & system read/write in Terminal Emulator

Code:

su

mount -o remount,rw rootfs

mount -o remount,rw /system

INSTALL BusyBox to /system/xbin

INSTALL MultiSystem APK & open it

INSTALL MultiSystem binaries by pressing Install button

UPDATE BusyBox by runnig the folowing commands in Terminal Emulator

Code:

su

MultiSystem advanced update_busybox

REBOOT to check LED indicator for boot options

CHECK permissive SELinux after reboot

Now, you should be able to create a virtual ROM & boot into it...

---------- Post added at 05:21 PM ---------- Previous post was at 04:46 PM ----------

Also, one more thing, i am reading through the directions on the main thread and also watching the video from RootJunkie, and the video does NOT show anything about the steps i highlighted in RED. Do i need to worry about doing these, or can i just click the install in the multisystem app? And if i do need to run these commands, and i have already clicked the install button in MultiSystem app, can i go back and do them after? Please advise. Thanks again!

Quote:

READ everything about MultiSystem here & Q&A thread

BACKUP all your data to an external storage or computer

INSTALL a stable stock ROM for your stock system

PARTITION your microSD card as described (here)

DOWNLOAD the latest version of MultiSystem APK

MOUNT rootfs & system read/write in Terminal Emulator

Code:

su

mount -o remount,rw rootfs

mount -o remount,rw /system

INSTALL BusyBox to /system/xbin

INSTALL MultiSystem APK & open it

INSTALL MultiSystem binaries by pressing Install button

UPDATE BusyBox by runnig the folowing commands in Terminal Emulator

Code:

su

MultiSystem advanced update_busybox

REBOOT to check LED indicator for boot options

CHECK permissive SELinux after reboot

Now, you should be able to create a virtual ROM & boot into it...
[Android Q&A, Help & Troubleshooting] welchy312:
Bootloop

So per my last post (which i still don't see as posted on here yet?) ,I did see this on the QA: It looks like the IMG is corrupt, as my DEV system showed the following:

Current System DEV: /dev/block/mmcblk0p23

My question is, how do i get back? As i explained in my previous post, i was able to boot to DL mode, and wipe system/data, and get back to JasmineROM v5.02 and still rooted, however it had installed a lot of default bloatware default stuff. Any ideas?

Quote:

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

Code:

Current System IMG: Test_Rom.img

Current System DEV: /dev/block/mmcblk0p23

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 !
[Android Q&A, Help & Troubleshooting] lazer9:
So does this actually work on a Note 4 (910T)? I am unsure of a "kexec" Kernel for this device. Can anyone elaborate?

Thanks
[Android Q&A, Help & Troubleshooting] milladog:
Need some help fast. I installed 5.0, then 5.02 then flashed firmware via odin. Rebooted cell and installed busy box, multisystem and terminal. Followed the directions on multisystem page and video. I select the 5.1 image as primary and reboot cell. I see the green blinking light and start tapping volume up button as the video shows. The cell boots with samsung splash screen and I reinstall multisystem and update configs. It sees my 2 stock roms but won't stick to 5.1 im on 5.0 it shows in general tab. I use terminal it says multisystem not found.....wtf am I doing wrong here help....need my cell cant' use it like this....

Edit: ok I installed busy box again and multisystem status shows stock. What am I doing wrong to make it run the virtual image 5.1?
[Android Q&A, Help & Troubleshooting] milladog:
I got it working yay. Did several reboots, reinstalled busybox, then opened multisystem. Then I selected the stock image I made and made it primary as I had other times. I then rebooted when the green light came on I only hit the volume up key once it worked perfectly. Booted up then opened multisystem again selected jasmine 5.1 img and made it as the primary image then I rebooted again but this time I tried something. I hit the volume up key 4-5 times nothing...rebooted to where I just was. So I selected the 5.1 again as primary and this time on reboot and green light I only hit the volume up key once and it started the 5.1 change and booting!!! I then waited and it never booted all the way to setup. I pulled the battery and booted into recovery mode and did a factory reset/cache and then rebooted the cell. After 7 mins it arrived at the setup screen and away I went. On my cell only one time you can hit the volume up key I hope this helps others maybe I donno, on my cell tapping the volume up will not load virtual image . I jumped for joy seems to be running ok letting it settle. Thanks for all your hard work Hsbadr!!! As always it rocks....and to all others who made all this possible.
[Android Q&A, Help & Troubleshooting] wanb1i:
Hsbadr,

Can you tell me if MultiSystem will work on the N915V Verizon (non-dev) with KingRoot/Super SU Me as a temporary root and would this establish a permanent root?

Also, do you know if the Lollipop OTA on the N915V can be reverted back to Kitkat like the Note 4?
[Android Q&A, Help & Troubleshooting] lunerceli:
[MENTION=3308172]hasba[/MENTION]dr, I have multisystem installed, but when I go into terminal and type MultiSystem status it comes back as read-only file system. Won't let me even create an img file and led does not come on when rebooting. I am running lollipop 5.0 on tmobile Galaxy s5. Any help would be appreciated.
[Android Q&A, Help & Troubleshooting] SammyNote23310.1:
So i have been trying to get MultiSystem to boot to a virtual img but it doesnt. I have a Verizon Galaxy S5 and i have followed the steps laid out in the installation and checked that i have everything installed correctly, i have even tried the terminal commands to get something to work. Everytime i check to see if it is running my running MultiSystem status and it always says that i am on the stock with the stock location. Please help....
[Android Q&A, Help & Troubleshooting] HelixtheII:
How does one delete a system image once it is created?

I get zero indicators that MultiSystem is ever doing anything, aside from the brief scripting toast. It took three installs and two reboots to get MultiSystem to even create its own directory and that's with following both the original instructions and the video to a T. Caveat, since MultiSystem never gave me indication that it was busy doing something in the background, I did manage to create two stock system images. I'd dearly love to remove both and start over but I don't even know if I should at this point.

EDIT: Let me clarify, can I go in and rm the img files without incident or do I need to do a little more?
[Android Q&A, Help & Troubleshooting] maxsm:
Note2

Thank you sir I got my note 2 running multisystem
[Android Q&A, Help & Troubleshooting] dave7802:
Does this work with Stock and CM Build?

Or while its shared Data, will we have to wait for Version 2.0

I was trying for CM12.1 As STOCK (Note 3 SN9005 Fully unlocked)

Then Jas as the Virtual ROM.

Or do i have to use this the other way around? CM is my Daily, but touchwiz would be nice form time to time.

This is why i was after it as the Virtual.
[Android Q&A, Help & Troubleshooting] TwiggieSmalls:
Is multi system a strict requirement for running 5.1.x?

From what I've read it seems that multi system can be thought of as a powerful but optional tool since flashfire is able to flash these rom versions already. I've flashed 5.0.2 on my fiancés note 3 and I'm wondering if I can just use Flashfire to flash up to 5.1 or 5.1.x in the future? I don't plan on having multi Roms ready to swap to on her phone, just a stable rom with new features for me to tinker with before giving it back to her.

So I guess my main question is must I have multi system to continue to on flashing 5.x jasmine roms?

Thanks in advance!
[Android Q&A, Help & Troubleshooting] gigilie:
S6?

[MENTION=3308172]hasba[/MENTION]dr hey bro any chance of a S6 port of MS? I skimmed through threads didnt see anyone trying or having luck and the vzw s6 is in need of something like this. we have ff but thats it!
[Android Q&A, Help & Troubleshooting] morthnuravrgjosf:
Smooth Sailing

Installed and running smoothly so far. Tested a couple virtual ROMS on stock OF2..love it. ESPECIALLY since I no longer am restricted by P.I.E.! My IDE loves you..as do I..keep up the good work.
[Android Q&A, Help & Troubleshooting] Debugging:
Question? I pressed Create Virtual IMG and in video it says a led light will come on and stay on while its creating but a led did not come on, can that be expected some times? I know everything else is installed and done correctly up to this point and don't want to mess anything up by pressing it again or exiting. :confused:

---------- Post added at 07:45 AM ---------- Previous post was at 07:37 AM ----------

Well i looked in the IMG then system folder to see if it did create and it has i guess because it was empty before pressing Create Virtual IMG but now has a StockSystem folder/img in the system folder.