[TOOL] [MultiSystem] MultiROM and Recovery Replacement for Android

[samccfl99]

Yes I Have Patience

DELETED. NEW: FF RESTORE FAILURE ON RESTORE. RAN OUT OF ROOM. ORIGINAL BU 3.39GB, EXT4 PARTITION 8.5GB. Pulled sdcard. Came up with alliance lockscreen and non-nova home screen and that might be because AGAIN all folders in internal storage are in a folder called "0". happened the other day. will move it around and update to see if that fixes it.

THANKS[/COLOR]
[/B]

 

[hsbadr]

DELETED...POST AGAIN IN A WHILE. FF RAN OUT OF ROOM ON RESTORE IN THE MIDDLE OF DATA. EXT4 PARTITION IS 8.5GB, FF BU FILE IS 3.39GB. VIRTUAL ROM CAME UP BUT IT IS STUCK. DUH. NOT ALL DATA THERE. WHAT TO DO...LOL. BATTERY PULL NOW.....

SO it seems to be installed using 1.3.1. i did format 16gb sd card with Mini Tool and made the EXT4 partition 8.5gb and it seems to be right. see screenshots please. Also the log. i guess it is the log. strange all entries have todays date and a time in the future it seems.

But when the device boots up and i get the green led, no option screen comes up. changed it to 30 seconds, still no option. am i misunderstanding something? G900A here on rooted stock 5.0 as requested as stock system.

THANKS[/COLOR]
[/B]

You're fine! The boot menu was removed to make it portable to many devices & independent on the OS version. The current boot options are the LED indicator & selection by key press:

• HOME KEY: boot the stock ROM
• VOLUME UP: boot the primary virtual ROM
• VOLUME DOWN: boot the secondary virtual ROM

 

[samccfl99]

You're fine! The boot menu was removed to make it portable to many devices & independent on the OS version. The current boot options are the LED indicator & selection by key press:

• HOME KEY: boot the stock ROM
• VOLUME UP: boot the primary virtual ROM
• VOLUME DOWN: boot the secondary virtual ROM

No, Not fine...LOL. I am sorry to be a pain. It does not say that in the installation instructions and what about this Permissive Option, does it do that automatically now? OP install instructions still say:

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

But the real problem as i kept changing the post was when i activated loop0 which was a copy of stock (did not know how to make an empty one like OP says), i did an FF restore of Alliance. it was sluggish even loading the program, kinda stuttered and it started to restore System 3 times before it finished that (FF was so slow on restore and it just stopped and said WIPE and started again...in different places and the backup was on internal) and somewhere in DATA, FF got a "no more space" msg. the ext4 partition is 8.5gb. so it never finished. i did a battery pull and Alliance animation came up and stayed there. of course because all of data was not there, i am assuming. pulled sdcard out, it went to a bastardized stock. had root, but nova home screens were not there plus the lockscreen was Alliance. FF is a great app and i know it is in beta, but look at these screenshots. this is the 2nd time this happened to me during Restore, only it was worse. puts all folders in internal into a root folder called "0", but this time it made another sub folder of "0" and then in that one was all the files. OY! I rearranged them and tried to get into SS to restore, but no luck. i dont know. i am not stupid. maybe i will time myself this time going from NCE to LP...LOL. no, not funny. already deleted internal (except Android folder, needs special care) and tried to restore my internal bu, which i know how to do and now it tries to boots and just goes to stock recovery. oh also when i was in that stock, i uninstalled and reinstalled SS (because some com files did not copy for some reason and one of them said safestrap) and then odin the OA1 kernel and rebooted (yes i know about NCE Flasher, not that that would make any difference for this). no SS.

i am tired of putting this phone back together from NCE. not blaming you. i think i am going to give up on this whole thing until someone comes up with a solution to Viper (which they still say does not work even in MS even though it is supposed to have Permissive) and Xposed. if this OC7 base was not so fast and my music faded out and chopped like NG3/XDK, i would have went back to my beautiful GPE theme i had and Viper.

I do thank you for answering. it seemed everything finally wound up ok after MS install until i tried to restore a custom rom. that is one of the points of MS, right? FF not really ready. i was afraid to flash something because of what you said about the way they need to change the updater script for MS. maybe i should not think so much....LOL. well i am going to watch some tv and chill for now. am home and the phone is a toy mostly and for outside use. maybe you might answer with something to try. if i could get SS back, then i could restore. who knows if that would even work. probably going to have to start with NCE again. actually could do it in my sleep now.

EDIT: Nice stressless break. Back to work. So i odin the OC4 kernel back and boot into that bastardized stock. FF was still there (i knew that anyway) and i restored my stock. was ok. of course who knows what is going on in internal storage. some of the files did not copy. very strange. i done that so many times. now i just restored my Alliance rom. it came up. looks ok. powering down to put prod 32gb sdcard back in. its up and all good. lets see how it works.

So what do you think about the screenshots? do you think i should post it on the FF thread? i am sure Chainfire looks at it all, but he does not say much until a new release is ready. not complaining. people like him and you and muniz_ri keeps our phones going. I do not understand what i did wrong if the system was installed correctly. I can tell you that i did not do the wipes in MS because it was on that virtual copy of the stock rom already and did not know what would happen. i did not do a wipe in FF before restoring because it does not seem to be necessary and when i asked that question in the thread, no answer. i started to use wipe before restore and then that crazy thing happened once with folder "0". maybe it needed a wipe in the virtual rom. FF seems to be the only way to restore a rom in MS. you can flash a zip in MS. it has backup and restore, but i do not think it can restore an FF backup, could it. I think too much. i am very logical and reactionary and think about the instructions given and what i know. maybe i should be a dummy. just an old time assembler, cobol, etc programmer and many other things [/OLD....LOL. Dangerous? Again, sorry to be so wordy. Please give me your thoughts when you get a chance, here or in PM. i would appreciate it. if not maybe in another few releases of MS and FF i will be giving it a try again. Even though i like FF alot, going back to SS for backup and restore, even though it takes up more room. the flashing i guess is ok in FF. Yes, i have SS back because Carl was nice enough to give me his zips to swap the files. THANK YOU CARL. My one cent..LOL.


THANKS (sorry i am so wordy and brain to keyboard sometimes is too fast...LOL)

 

[jt1998]

Video stops too soon and doesn't show you how to add more ROMs. This is imperative to be a MultiSystem.

Sent from my Android 4.4.4 LGV500 on Mahdi 2.9 w RedKernel

 

[hsbadr]

No, Not fine...LOL. I am sorry to be a pain. It does not say that in the installation instructions and what about this Permissive Option, does it do that automatically now? OP install instructions still say:

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

But the real problem as i kept changing the post was when i activated loop0 which was a copy of stock (did not know how to make an empty one like OP says), i did an FF restore of Alliance. it was sluggish even loading the program, kinda stuttered and it started to restore System 3 times before it finished that (FF was so slow on restore and it just stopped and said WIPE and started again...in different places and the backup was on internal) and somewhere in DATA, FF got a "no more space" msg. the ext4 partition is 8.5gb. so it never finished. i did a battery pull and Alliance animation came up and stayed there. of course because all of data was not there, i am assuming. pulled sdcard out, it went to a bastardized stock. had root, but nova home screens were not there plus the lockscreen was Alliance. FF is a great app and i know it is in beta, but look at these screenshots. this is the 2nd time this happened to me during Restore, only it was worse. puts all folders in internal into a root folder called "0", but this time it made another sub folder of "0" and then in that one was all the files. OY! I rearranged them and tried to get into SS to restore, but no luck. i dont know. i am not stupid. maybe i will time myself this time going from NCE to LP...LOL. no, not funny. already deleted internal (except Android folder, needs special care) and tried to restore my internal bu, which i know how to do and now it tries to boots and just goes to stock recovery. oh also when i was in that stock, i uninstalled and reinstalled SS (because some com files did not copy for some reason and one of them said safestrap) and then odin the OA1 kernel and rebooted (yes i know about NCE Flasher, not that that would make any difference for this). no SS.

i am tired of putting this phone back together from NCE. not blaming you. i think i am going to give up on this whole thing until someone comes up with a solution to Viper (which they still say does not work even in MS even though it is supposed to have Permissive) and Xposed. if this OC7 base was not so fast and my music faded out and chopped like NG3/XDK, i would have went back to my beautiful GPE theme i had and Viper.

I do thank you for answering. it seemed everything finally wound up ok after MS install until i tried to restore a custom rom. that is one of the points of MS, right? FF not really ready. i was afraid to flash something because of what you said about the way they need to change the updater script for MS. maybe i should not think so much....LOL. well i am going to watch some tv and chill for now. am home and the phone is a toy mostly and for outside use. maybe you might answer with something to try. if i could get SS back, then i could restore. who knows if that would even work. probably going to have to start with NCE again. actually could do it in my sleep now.

EDIT: Nice stressless break. Back to work. So i odin the OC4 kernel back and boot into that bastardized stock. FF was still there (i knew that anyway) and i restored my stock. was ok. of course who knows what is going on in internal storage. some of the files did not copy. very strange. i done that so many times. now i just restored my Alliance rom. it came up. looks ok. powering down to put prod 32gb sdcard back in. its up and all good. lets see how it works.

So what do you think about the screenshots? do you think i should post it on the FF thread? i am sure Chainfire looks at it all, but he does not say much until a new release is ready. not complaining. people like him and you and muniz_ri keeps our phones going. I do not understand what i did wrong if the system was installed correctly. I can tell you that i did not do the wipes in MS because it was on that virtual copy of the stock rom already and did not know what would happen. i did not do a wipe in FF before restoring because it does not seem to be necessary and when i asked that question in the thread, no answer. i started to use wipe before restore and then that crazy thing happened once with folder "0". maybe it needed a wipe in the virtual rom. FF seems to be the only way to restore a rom in MS. you can flash a zip in MS. it has backup and restore, but i do not think it can restore an FF backup, could it. I think too much. i am very logical and reactionary and think about the instructions given and what i know. maybe i should be a dummy. just an old time assembler, cobol, etc programmer and many other things [/OLD....LOL. Dangerous? Again, sorry to be so wordy. Please give me your thoughts when you get a chance, here or in PM. i would appreciate it. if not maybe in another few releases of MS and FF i will be giving it a try again. Even though i like FF alot, going back to SS for backup and restore, even though it takes up more room. the flashing i guess is ok in FF. Yes, i have SS back because Carl was nice enough to give me his zips to swap the files. THANK YOU CARL. My one cent..LOL.

THANKS (sorry i am so wordy and brain to keyboard sometimes is too fast...LOL)

I'd suggest for you to wait for a more stable version. It's in a very early stage now. OR, check the users who have successfuly used it (e.g., VZW Note 3 users here)

EDIT: Also check this report if you're using F2FS:

Hey there! I noticed a small bug while using Multisystem, if you install the necessary scripts it bootloops the device if the system partition is F2FS instead of EXT4. I tried MultiSystem on 2 roms that by default only reformat the /System partition to F2FS. The glitchy only happens there. On the good side, I tried a ROM that uses EXT4 for the /System partition and it worked! I think you should mention something about that in your FAQ. It may help others. I will try to provide a logcat as soon as possible on this.

THE CURRENT VERSION DOES NOT SUPPORT F2FS FILE SYSTEM.

Video stops too soon and doesn't show you how to add more ROMs. This is imperative to be a MultiSystem.

What? I've just answered that exact same question in the Q&A thread!

 

[jt1998]

Lol. Sorry its that important! I didn't know which thread you'd respond to.

Sent from my Android 4.4.4 LGV500 on Mahdi 2.9 w RedKernel

 

[xtam]

So...my previous phone was motorola razr maxx xt910 with locked bootloader.
And there was nice app - bootmenumanager or safestrap, which allowed following:
have multiple virtual roms, and stock rom.
So when i had installed stock rom, with stock kernel i could also boot cm based rom which required own, cm kernel.
It was done by kexec.

Is it possible here to have stock rom, with stock kernel, and as second system cm based rom like fusion or blisspop with own kernel witout needing to flash kernel on every boot?

 

[vanemburghj]

I rode the short bus to school so.......

Watched both videos, read the Q&A, and the posts and none of them explains how to install more than 1 virtual ROM. So how do you do that? Have FireFlash installed, however, just not jumping out at me on installing more ROMs. I want to have FireKat and Cyanogenmod as my virtuals with stock 4.4.4 on system partition.

I know you say in post #25 you answered jt1998's exact same concern in Q&A, read Q&A 5 times and just did not see it.

 

[jt1998]

Watched both videos, read the Q&A, and the posts and none of them explains how to install more than 1 virtual ROM. So how do you do that? Have FireFlash installed, however, just not jumping out at me on installing more ROMs. I want to have FireKat and Cyanogenmod as my virtuals with stock 4.4.4 on system partition.

I asked same question and am still waiting....

Sent from my Android 4.4.4 LGV500 on Mahdi 2.9 w RedKernel

 

[crusrod]

Hsbadr great work thus far, you have done amazing things. Here is comfirmation of my recent payment for more development from you. Good:Great: Transaction ID: 7BU85271CL994083N

 

[Magnum_Enforcer]

I'll just leave this here:

2. Member conduct.

"2.1 Language: XDA is a worldwide community. As a result, what may be OK to say in your part of the world, may not be OK elsewhere. Please consider who is reading what you write and don't use profanity, sexually explicit language, rudeness or swearing including the use of characters to replace letters in swear words. Conversely, while reading posts from other members, remember that the word you find offensive may not be offensive to the writer. Tolerance is a two-way street.

2.2 Nudity: XDA is used by people of all ages, including minors. It is unacceptable to post nude or pornographic imagery, which includes the exposure of male or female genitalia and / or female breasts.

2.3 Flaming / Lack of respect: XDA is about sharing and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.

2.4 Personal attacks, racial, political and / or religious discussions: XDA is a discussion forum about certain mobile phones. Mobile phones are not racial, political, religious or personally offensive and therefore, none of these types of discussions are permitted on XDA.

2.5 All members are expected to read and adhere to the XDA rules."

Magnum_Enforcer
FSM

 

[Gerxp]

So how do I install like 5 roms? And how do I choose from them?
I dont see how to do that in the tutorial.

 

[sacnotsack]

So how do I install like 5 roms? And how do I choose from them?
I dont see how to do that in the tutorial.

You would add each rom to a data slot.

When you want to switch roms, you just select the rom you want to switch to (within dual boot patcher) and reboot.

 

[jt1998]

You would add each rom to a data slot.

When you want to switch roms, you just select the rom you want to switch to (within dual boot patcher) and reboot.

from my understanding no one has successfully accomplished this and no sign of the dev in a bit

 

[LordArcadius]

Can I use this in MTK devices?

 

[Borfas]

Multisystem: Not found .............

 

[Minto107]

This seems to be a very cool thing. Can I ask if you are going to support more devices in the future? I would really see this on my GS3 I9305 that would be awesome!
Cheers and keep up good work

 

[xGMERZ]

I'm always getting MultiSystem partition is not mounted? Also about 50 lines saying it couldn't write the log as its read only. Followed the video tutorial

 

[jt1998]

Anybody know where the developer went??

from my Samsung Galaxy S5 SM-G900T on AT&T, Android 5.0. DOB1 with twi5ted lollipop ROM v7

 

[hsbadr]

So how do I install like 5 roms? And how do I choose from them?
I dont see how to do that in the tutorial.

You need to make virtual IMGs for the 5 (or more) ROMs in

/MultiSystem/img/system/

assuming there's enough space in the 2nd SD card partition (EXT4 MultiSystem partition). All ROMs share all partitions (including data) except system ATM. If the ROMs are very different, you'll need to wipe system data before switching.

Can I use this in MTK devices?

Not tested! Test it yourself & report me back!

Multisystem: Not found .............

I'm always getting MultiSystem partition is not mounted? Also about 50 lines saying it couldn't write the log as its read only. Followed the video tutorial

Read Q&A thread & follow OP instructions! You'll find installation log in

/data/log/MultiSystem.log

You may need to manually mount system & rootfs rw, if it didn't work by default.

This seems to be a very cool thing. Can I ask if you are going to support more devices in the future? I would really see this on my GS3 I9305 that would be awesome!
Cheers and keep up good work

The current version may work on S3 as well; it's not tested though.

Anybody know where the developer went??

The dev has real life, family, & work. This is a hobby & I'm supporting it in my free time.