{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction:
MultiROM is one-of-a-kind multi-boot mod for Galaxy J5. It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port, once they are ported to our device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs, daily prebuilt image files to install Ubuntu Touch and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.Features:
Multiboot any number of Android ROMs
Restore nandroid backup as secondary ROM
Use for example Ubuntu Touch or Desktop alongside with Android.
Boot from USB drive attached via OTG cable
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is messing with boot sector and data partition. If something goes wrong you will have to flash factory images again. Make backups. Always.
Installation:
1) Flash the Modified TWRP image with odin or extract the tar file and install the img file with flashify or another recovery that has img install feature.
2) After flashing the recovery image boot into the recovery and Flash the MultiROM zip.
3) That's it you're done. Reboot into system and the multirom menu will show up.
Enjoy!!
MultiROM has 3 parts you need to install:
MultiROM (multirom_vXX_n7-signed.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom_n7_YYYYMMDD.img) - download the IMG file from second post and use fastboot or Flashify app to flash it.
Patched kernel - Not needed for our device.
Your current rom will not be erased by the installation.
Downloads are in 2nd post!!
Important: Since the Kernel hasn't Kexec Hardboot patch, you have to check "use no kexec workaround" box in multirom settings. (it has been set to this option by default)Adding ROMs:
Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using USB drive (not tested yet):
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs:
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one:
To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Explanation of recovery menus:
Main menu:
Add ROM - add ROM to boot
List ROMs - list installed ROMs and manage them
Inject boot.img file - When you download for example kernel, which is distributed as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
Inject boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
Settings - well, settings.
Manage ROM:
Rename, delete - I believe these are obvious
Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.
How does Kexec workaround works:
You need to have a kexec-hardboot supporting kernel or the non-kexec workaround as described perfectly by @nkk71 here: http://forum.xda-developers.com/show...26&postcount=4 (Be sure to leave him a thanks!)
NOTE: Stock Lollipop Firmware required. Will not work on MM bootloaders.
Credits:
A big thanks for:
@nkk71 For his kexec workaround
@Tasssadar For MultiRom Source Code
@Nick Verse
XDA:DevDB Information
MultiRom for Galaxy J5, Tool/Utility for the Samsung Galaxy J5
Contributors
ganesh varma
Source Code: https://github.com/Galaxy-J5
Version Information
Status: Beta
Current Beta Version: 1
Beta Release Date: 2016-12-18
Created 2016-12-18
Last Updated 2016-12-19
Reserved
Downloads:
MultiRom TWRP Recovery:
Recovery Images for LL Bootloader:-
J500F
J500FN
J500G
J500H
J500M
J500Y
MultiRom ZIP Installer: multirom-20161218-v33-UNOFFICIAL.zip
Changelog:
Code:
18.12.2016
=====================
* Initial release
NOTE: Stock Lollipop Firmware required. Will not work on MM bootloaders.
Hit that Thanks button if you like my work!!
Awesome work bro @ganesh varma ..
Congrats & all the best.. :good::good:
That's really cool buddy.
I'm very impressed
Nice one
John
Sent from my Honor 8 using XDA Labs
Uhh, so that means i can dualboot in android?
anyways, cool
Alright! Time to get our hands dirty ?
Great job @ganesh varma and @Nick Verse to port this Mod to our J5. Thankyou so much!
Nice work bro @ganesh varma
????????
Great job. Just noticed that the screen resolution is not okay. It seems somehow it zoomed a bit in....
Will the data partition be the same for both ROMs or different??
I have installed a new ROM in external SD. When I try to boot it, I can't find it, why??
updesh94 said:
Will the data partition be the same for both ROMs or different??
Click to expand...
Click to collapse
No the secondary ROM creates a folder in the internal storage and uses it as data partition. The two roms have their own data partitions.
MiGuPa said:
I have installed a new ROM in external SD. When I try to boot it, I can't find it, why??
Click to expand...
Click to collapse
Did you see by swiping right to the External tab on the multirom menu? The roms installed to SD card will be shown under External tab in multirom menu.
I think that it's so cool that you have made this for the J5
Good work
Thanks for your time
John
ganesh varma said:
Did you see by swiping right to the External tab on the multirom menu? The roms installed to SD card will be shown under External tab in multirom menu.
Click to expand...
Click to collapse
Yes, I also stayed there, and any new
Good Work, man!
works in J500M?
luisfelipee said:
Good Work, man!
works in J500M?
Click to expand...
Click to collapse
Nope, read the #2 post man... For now only F and FN models.
Sent from my SM-J500FN using XDA Labs
Mixed Review!
ganesh varma said:
No the secondary ROM creates a folder in the internal storage and uses it as data partition. The two roms have their own data partitions.
Click to expand...
Click to collapse
So I tried the multirom, It's working absolutely great.. No issues in any rom...
I installed Stock Lollipop primary rom and Resurrection rom as the secondary rom...
Glitches---
1. In the boot menu where OS are displayed if we tap the multirom icon, a ping pong game starts which says "to exit press power button" but then we are stuck in it and only possible way is to remove battery... :laugh:
2. Sometimes the selected rom doesn't boot and nothing happens.. only 1/10 times... :silly:
3. Storage becomes low in /data and /system has a lot of space, can u suggest a way to transfer dalvik-cache of primary rom to /system ??I tried one but it didn't work!!
By the way, It seems awesome to multiboot Roms...
I'm using j500F btw...
Now I tried to install an ROM on internal memory, and when I tried to boot:
JosephDM said:
Nope, read the #2 post man... For now only F and FN models.
Sent from my SM-J500FN using XDA Labs
Click to expand...
Click to collapse
thanks for reply. i asked cuz some F roms works in M model
updesh94 said:
So I tried the multirom, It's working absolutely great.. No issues in any rom...
I installed Stock Lollipop primary rom and Resurrection rom as the secondary rom...
Glitches---
1. In the boot menu where OS are displayed if we tap the multirom icon, a ping pong game starts which says "to exit press power button" but then we are stuck in it and only possible way is to remove battery... :laugh:
Click to expand...
Click to collapse
try press volume down + power button till restart.
to recovery mode when cel stuck, press all buttons (vol+, Vol-, Home and power) when screen off leave 'vol-' only and keep others
Update
Multirom for J500G,J500H,J500M and J500Y variants is now available. Can be downloaded from the second post!!
These recovery images are for LL bootloader's. Multirom for MM bootloader's will be available by the end of next week. :good:
Make sure that you have read all the instructions from the first post when you ran into problems. Everything is mentioned over there.
thanks @ganesh varma...its really awasome i m using on j500f.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for Nexus 5. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
1. Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
2.Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
MultiROM has 3 parts you need to install:
MultiROM (multirom-YYYYMMDD-vXX-d855.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom_d855_YYYYMMDD.img) - download the IMG file from second post and use fastboot or Flashify app to flash it.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 4.2 after first boot (with dalvik cache generated and connected to google account) takes 676mb of space.
2. Ubuntu Touch
Use the MultiROM Manager app to install Ubuntu Touch.
Ubuntu Touch is in development - MultiROM will have to be updated to keep up with future changes in Ubuntu, so there's a good chance this method stops working after a while and I'll have to fix it.
3. Firefox OS
Firefox OS is just another Android ROM from MultiROM's point of view, so grab the ZIP file from Firefox OS' thread and add it as if it were Android
4. SailfishOS
Download CyanogenMod and SailfishOS ZIP as described on Sailfish wiki page. You need alpha2 (20140810) or newer!
Put both CM and SailfishZIP on your device.
Reboot into recovery
Advanced -> MultiROM -> Add ROM
Choose "SailfishOS" as ROM type. Installation to USB drive is not supported, so leave install location as is. Click Next.
Choose first CyanogenMod ZIP and then SailfishOS ZIP. Click install.
Head to SailfishOS thread for more info: http://forum.xda-developers.com/google-nexus-5/development/rom-sailfish-os-alpha-t2841266
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Source code
Kernel https://github.com/Skin1980/D855-kernel/tree/lollipop
Device Tree https://github.com/Skin1980/device-d855-multirom
TWRP https://github.com/Skin1980/Team-Win-Recovery-Project
Credits: @tassadar for the awesome work; @invisiblek and @savoca @patrik.KT for them help
...and all the people that now i forget
PLEASE READ THE MULTIROM WIKI TO UNDERSTAND BETTER WHAT YOU ARE DOING
Frequently
Asked
Questions
IMPORTANT: Need to be with a stock Rom ( tested with mine ChupaChupa 3.0 )
HOW TO INSTALL:
1- reboot in recovery and flash the new TWRP with Multirom support; --> HERE
2- reboot the recovery;
3- flash the kernel with the kexec hardboot patch ( it's my chupakernel 20D based, might works well also with the 20E roms) 2Gb/16 HERE and 3Gb/32 HERE
4- flash the multirom zip; ---> HERE
5- install every Rom you want ( advanced--> multirom --> add rom )
6- reboot and choose the rom you want to boot.
You can also use a Cyanogenmod or similar with the wonderful Rin Kernel by @Tectas --> DOWNLOAD FOLDER
KK Kernel for stock based roms ( based on rin kernel by @Tectas ) 2Gb HERE and 3Gb HERE
Issues:
1- on boot the touch need some seconds to work in multirom menu, you can use the volume keys to move and the power button to select.
Changelogs:
- 07.01.2015 fixed install issue for the secondary roms on TWRP
- 07.01.2015 fixed button layout in TWRP
- 08.01.2015 fixed kernel for the 3Gb version ( now the can multiboot too)
- 08.01.2015 fixed kernel version for both
- 08.01.2015 fixed install to external sd
- 08.01.2015 fixed TWRP version displayed
- 10.01.2015 fixed TWRP layout ( hopefully )
- 10.01.2015 fixed Installation of 2nd ROM from previous backup ( tested with CM12 nightly)
- 20.01.2015 added KK kernel
- 20.01.2015 bigger Multirom Menù
- 26.02.2015 fix for the latest Cyanogenmod
I posted this quickly and i will update ASAP.
Skin1980 said:
reserved
Click to expand...
Click to collapse
another one
Nice
Amazing.
Thanks crack!
Thanks!
Is working fine on D855 16 GB.:good:
So the first ROM need a stock ROM like tour chupa chups?
Great job!
I've got a request. Please, can you compile a KitKat kernel with multirom support? I'm still on 10o, and i won't change it for a long time...
iSnob said:
So the first ROM need a stock ROM like tour chupa chups?
Click to expand...
Click to collapse
Yes
Sent from my SM-N910F using XDA Free mobile app
YaDr said:
Great job!
I've got a request. Please, can you compile a KitKat kernel with multirom support? I'm still on 10o, and i won't change it for a long time...
Click to expand...
Click to collapse
Yes but not for now.... maybe @Tectas can do it quickly
Sent from my SM-N910F using XDA Free mobile app
tnx i will try it
I'm so glad we managed to keep you on these forums.
I'm so looking forward to playing with this. ?
how to restore a rom on second partition??
Thanks a lot for this mod awesome find 1 thing how to restore a rom on second partition???
Nice to see developers getting more interested in G3
Thanks!!! Been waiting since i've seen your video... Will try as soon as possible... =)
Sent from my LG-D855 using Tapatalk
zimmerAndy said:
Thanks a lot for this mod awesome find 1 thing how to restore a rom on second partition???
Click to expand...
Click to collapse
Advanced multirom. Add Rom and the select backup instead of zip
Sent from my SM-N910F using XDA Free mobile app
Nice☺
Skin1980 said:
Advanced multirom. Add Rom and the select backup instead of zip
Sent from my SM-N910F using XDA Free mobile app
Click to expand...
Click to collapse
Hi i get a security error after restoring a rom so i believe that has something to do with kernel right??
Multirom app say my device is unsupported ,where i find the modified recovery?
Ok sorry man with tapatalk dont show link
Yeeeah!! Kitkat supported kernel would be great! Lollypop is worse for now than kk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for LG G PAD 8.3 (V500). It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
1. Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card.
2. Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 2 parts you need to install:
Modified recovery - download the IMG file from second post and use fastboot or TWRP to flash it.
MultiROM - download the ZIP file from second post and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file or TWRP Backup and confirm. As for the space, clean installation of stock 4.2 after first boot (with dalvik cache generated and connected to google account) takes 676mb of space.
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - add ROM to boot
- List ROMs - list installed ROMs and manage them
- Inject boot.img file - When you download for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - well, settings.
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
- Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.
Source code
MultiROM - https://github.com/multirom-v500/multirom
Modified TWRP - https://github.com/multirom-v500/Team-Win-Recovery-Project
MultiROM device tree - https://github.com/multirom-v500/android_device_lge_v500
Thanks a lot to Tasssadar for creating this awesome utility.
And to @nkk71 for the No-KEXEC workaround
XDA:DevDB Information
MultiROM, Tool/Utility for the LG G Pad 8.3
Contributors
beroid, nkk71
Source Code: https://github.com/multirom-v500
Version Information
Status: Stable
Created 2016-11-25
Last Updated 2017-01-30
Downloads
AndroidFileHost
No-kexec workaround
Mini FAQ:
Q: What is the no-kexec workaround?
A: The no-kexec workaround by @nkk71 allows you to use MultiROM without having to flash a kexec enabled kernel.
Please read all things about no-kexec workaround from the author words only, (to avoid duplicity and get latest information), thanks to @nkk71
http://forum.xda-developers.com/showpost.php?p=68738134&postcount=4
@beriod can i install Malladus In this Or Stock 4.4.2?? You only say dont add Stock Lollipop Rom?
Bootloop!
Install Multirom and TWRP Patched By Multirom, then Add Rom And I flash is Validus (5.1.1) Romafter it go on list rom, click the validus in list, flash zip, (GAPPS) and (Patched kernel), and bootloop
Jansxel said:
Install Multirom and TWRP Patched By Multirom, then Add Rom And I flash is Validus (5.1.1) Romafter it go on list rom, click the validus in list, flash zip, (GAPPS) and (Patched kernel), and bootloop
Click to expand...
Click to collapse
You need to have kernel with kexec-hardboot patch only in your primary ROM!
beroid said:
You need to have kernel with kexec-hardboot patch only in your primary ROM!
Click to expand...
Click to collapse
Oh Ahaaha Sorry i try it later. This is the first time i use this.
@beroid can you link me to your kernel v500 sources so i can patch up my cm12.1 kernel, to use kexec hardboot? already doing it on Z2.
thanks.
Can anyone patch stock kernel ? Haven't enough knowledge to that,but I want very much have stock as primary
Написан с LG-V500. Работает на XDA Forums Pro
Maraudeur said:
Can anyone patch stock kernel ? Haven't enough knowledge to that,but I want very much have stock as primary
Написан с LG-V500. Работает на XDA Forums Pro
Click to expand...
Click to collapse
I was thinking about just installing CM12.1 , why do I want to keep stock as primary? if I might ask?
i've integrated that kexec hard-boot patch on my v500 kernel, working fine, but theres an issue...
the screen starts very dimmed, and stays that way until it fully boots CM12. it reminds me of the issue we have with the 4.2.2 base and the 4.4.2 base.
infected_ said:
i've integrated that kexec hard-boot patch on my v500 kernel, working fine, but theres an issue...
the screen starts very dimmed, and stays that way until it fully boots CM12. it reminds me of the issue we have with the 4.2.2 base and the 4.4.2 base.
Click to expand...
Click to collapse
brightness: MiltiRom -> Settings -> Screen Brightness
beroid said:
brightness: MiltiRom -> Settings -> Screen Brightness
Click to expand...
Click to collapse
you must have some sort of issue reading my posts, or my explaining skills suck ..
its not on MR recovery the issue.... its after boot, when the MR menu shows to select ROM, the screen is dimmed, and stays that way until it fully boots to CM12.
nevermind... you we're right... this doesnt happens on sirius, so it was a new prob for me.
thanks and regards!
Update is up (MultiRom + Kernel).
MultiRom Now Supports Stock rom V30A-Korea as secondary
hmmm... @beroid, can you explain the fact, deleted 3 secondary ROMs, after that i flashed 20E as secondary, booted fine..
next thing i am twrp, my internal partition only has 8223MB ? already wiped it 3 times, changed recovery, reflashed CM12.. same thing.
i suppose i will have to flash 4.2.2 and then upgrade to CM12 to fix it, right?
ps: screen in attachment is after the 3 wipes i did...
TWRP shows free space of partition.
in attachment:
Capacity: 11 Gib
Used: 3 Gib
Available: 8 Gib
beroid said:
TWRP shows free space of partition.
in attachment:
Capacity: 11 Gib
Used: 3 Gib
Available: 8 Gib
Click to expand...
Click to collapse
i dont have any secondary ROM installed... those 3GB are the system partitions of the host ROM?
11 GiB are 11.8GB
16GB are 14.90Gib
where did the 3.4GiB (3.6GB) + 3 GiB (3.2GB) went?
sorry for all the noobish questions but is the first time i ever used MR on the v500, and i suppose i never noticed the complete internal memory size.
check /data/media/0/multirom/
beroid said:
check /data/media/0/multirom/
Click to expand...
Click to collapse
ok give me a minute.
---------- Post added at 11:31 ---------- Previous post was at 11:28 ----------
beroid said:
check /data/media/0/multirom/
Click to expand...
Click to collapse
empty. the folder doesnt even exists 'cause ive uninstalled MR and the MR twrp.
infected_ said:
ok give me a minute.
---------- Post added at 11:31 ---------- Previous post was at 11:28 ----------
empty. the folder doesnt even exists 'cause ive uninstalled MR and the MR twrp.
Click to expand...
Click to collapse
Multirom uses only /data/media/0/multirom/
From device with Korean LP (never installed MultiRom).
TLDR:
1: MAKE A BACKUP. Seriously.
2: Downloads in second post. Flash recovery, then kernel, then MultiROM.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
This is a port of Tassadar's MultiROM, a multi-boot mod for OnePlus 2. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
This is still experimental!
Make backups. Seriously. Please.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via USB-C OTG cable
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
2.Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 2 parts you need to install:
Modified recovery (TWRP_multirom_oneplus2_YYYYMMDD.img) - download the IMG file from second post and use fastboot to flash it.
MultiROM (multirom-YYYYMMDD-vXX-oneplus2.zip) - download the ZIP file from second post and flash it in recovery.
Your current ROM will not be erased by the installation.
Adding ROMs
1. Android
Go to recovery, select MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Note that swapping roms between internal and external is not supported (yet). Also, after flashing a factory image to the primary system and boot partition, make sure to immediately inject MultiROM before first boot, otherwise the secondary ROMs will be deleted.
Source code
MultiROM - https://github.com/nkk71/multirom/tree/master (branch master)
Modified TWRP - https://github.com/nkk71/Team-Win-Recovery-Project (branch android-7.1-mrom)
Device tree: https://github.com/MZO9400/device_oneplus_oneplus2-mrom -b twrp-mrom
Thanks
This port is based on the hard work of Tassadar, 500 Internal Server Error, Geoff Levand, webgeek1234, Mike Kasick, Npjohnson, Hashbang173, and many others. Thank you.
Issues
- None that are known. If you find one that this thread does not know about/hasn't answered (solid rule, read the last three pages of the thread befre reporting an issue), report it in the thread
- IF YOU GET LOCKED OUT OF YOUR DEVICE: Don't worry! Your data is fine. Simply boot to TWRP, choose 'Advanced' ==> 'Terminal Command' ==> type "rm -rf /data/system/gatekeeper.*.key" (without the quotes). This is a dirty fix, and should only be used to recover data, not as a permanent solution! After you recover your data, wipe /data (you don't have to wipe Internal Storage), and re-setup the device.
Changelog
Here
Downloads
Downloads in second post
NOTE:
Third party kernels with kexec-hardboot support (can be flashed to primary ROM): THIS IS NO KEXEC MultiROM, you don't necessarily need kexec hardboot supported kernels
Extra Information
Unlike some of the other 64-bit MultiROM ports, this port does have kexec-hardboot enabled, which is less risky and speeds up boot into secondary ROM. Anyone porting MultiROM to a Snapdragon 810 device may find the source to be useful. The patch was written by @500 Internal Server Error
XDA:DevDB Information
MultiROM for OnePlus2, Tool/Utility for the OnePlus 2
Contributors
MZO, nkk71, martinusbe
Source Code: http://github.com/multirom-dev
Version Information
Status: Stable
Current Stable Version: v33b
Stable Release Date: 2017-05-13
Current Beta Version: v33b
Beta Release Date: 2017-04-20
Created 2017-04-20
Last Updated 2017-05-13
MultiROM (folder):
DOWNLOAD
MultiROM v33b
TWRP MultiROM v3.1.1
MultiROM Uninstaller
MultiROM manager modified with OP2 commits has been attached to this post
Method of flashing multirom.
________________
1. Go to TWRP 3.1.0 officially that u already have
2. Flash the multirom image file .. and select recovery when it asks whether u want boot or recovery.
3. When successful go back to maim page and hit reboot recovery
4. Now its multirom
5. Flash the provided multirom zip file. An auto reboot will occur. Hit cancel and go to MISC tab to hit reboot recovery
6. Now the existing rom u had , is primary
7. Go to 3 dot menu of TWRP on upper right corner.
8. Select add rom
9. Flash desired rom
10. Reboot recovery again when successful
11. Go to 3 dot menu again and select list rom
12. Tap on add zip file and add gapps here... That is whatever u file want to flash on a rom just select that rom from rom list and add zip from there
[when flash a secondary, u have to flash zip, then back, and add zip and flash gapps]
13. Hit reboot system.
14. Now a screen will appear even before boot to.ask which rom u want to flash. For the very first time the option is set to, if u don't select any it will boot to primary after 5 seconds, so u hit cancel on that screen (pop up actually)
15. Select the desired rom , double tap on it and it will boot.
First boot of a new rom takes at least 15 to 20 real life minutes.
Notes:
__
To change the option of count down of rom booting selection, go to settings of multirom twrp and turn off option from there. Now every time u reboot.. it will ask which rom u want to boot. And if u don't select any it will stay on same screen till u click something
Tested so far:
Nougat based ROMs
OOS stock
OOS based ROMs
H2OS
MIUI
FlyME
Okay so @Tomsgt has made an amazing guide on how to set up and run MultiROM for our device (or any device), you can find his video right here:
<Mod Edit: Link removed for promoting paid service.>
Awesome work
Yay
btw, link to devicetree doesn't work. found it anyway https://github.com/AOSP-JF-MM/platform_device_oneplus_oneplus2/commits/aosp-7.1.2_mrom
martinusbe said:
Yay
btw, link to devicetree doesn't work. found it anyway https://github.com/AOSP-JF-MM/platform_device_oneplus_oneplus2/commits/aosp-7.1.2_mrom
Click to expand...
Click to collapse
Fixed!
Was getting installation aborted error...removed device check and installed successfully...
Thanks...
[email protected] said:
Was getting installation aborted error...removed device check and installed successfully...
Thanks...
Click to expand...
Click to collapse
Probably because of the ROM. It might need more tags since we can't agree on ONE name
MZO said:
Probably because of the ROM. It might need more tags since we can't agree on ONE name
Click to expand...
Click to collapse
Its working fine now...awesome work... :good:
Great man, thanks a lot.
Sent from my ONE A2003 using XDA-Developers Legacy app
MZO said:
Fixed!
Click to expand...
Click to collapse
cool, thanks for keeping authorship btw
martinusbe said:
cool, thanks for keeping authorship btw
Click to expand...
Click to collapse
My pleasure used your commits and you helped me in the final stage — well deserved!
MZO said:
Probably because of the ROM. It might need more tags since we can't agree on ONE name
Click to expand...
Click to collapse
maybe add some of the known used ones here https://github.com/AOSP-JF-MM/platf...lus2/blob/aosp-7.1.2_mrom/BoardConfig.mk#L231
martinusbe said:
maybe add some of the known used ones here https://github.com/AOSP-JF-MM/platf...lus2/blob/aosp-7.1.2_mrom/BoardConfig.mk#L231
Click to expand...
Click to collapse
Yes! I have done that locally — not sure what other devices names to add. If @[email protected] would let me know his device name I'd be obliged ?
MZO said:
Yes! I have done that locally — not sure what other devices names to add. If @[email protected] would let me know his device name I'd be obliged ?
Click to expand...
Click to collapse
yea, not sure if that takes a comma separated list
been a while since i looked at it all, but i think i didn't have a comma in there on op3
martinusbe said:
yea, not sure if that takes a comma separated list
been a while since i looked at it all, but i think i didn't have a comma in there on op3
Click to expand...
Click to collapse
Yep it worked with commas. Uploading now two more names: Oneplus2 (pretty common), onePlus2 (what was I thinking??)
Will i need to wipe internel storage for first time
ShaDow18 said:
Will i need to wipe internel storage for first time
Click to expand...
Click to collapse
No you won't.
MZO said:
No you won't.
Click to expand...
Click to collapse
What about recovery do i really need fastboot mode or flasify can also do
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for Moto G5 Plus. It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port, once they are ported to our device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs, daily prebuilt image files to install Ubuntu Touch and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Use for example Ubuntu Touch or Desktop alongside with Android, without the need of device formatting, once they are ported to the Moto X Play
* Boot from USB drive attached via OTG cable
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is messing with boot sector and data partition. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
1. Via MultiROM Manager app (We do not have Official Support, so this is not an option for us yet)
This is the easiest way to install everything MultiROM needs. Install the app (Not for Moto X Play) and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel (If you want to use Kexec) - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
2. Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 3 parts you need to install:
Modified recovery (mr-twrp-potter-YYYYMMDD.img) - download the IMG file from second post and use fastboot, TWRP or Flashify app to flash it.
Patched kernel - you can find it in the second post. Download the ZIP file and flash it in recovery. You can use any 3rd-party kernel which include the patch.
MultiROM (multirom-YYYYMMDD-vXX-potter-signed.zip) - download the ZIP file from second post and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using USB drive (not tested yet)
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
In some cases, you might need to flash patched kernel - get coresponding patched kernel version from second post and flash it to the secondary ROM sama way you flashed ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - add ROM to boot
- List ROMs - list installed ROMs and manage them
- Inject boot.img file - When you download for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - well, settings.
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
- Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.
Source code
MultiROM - https://github.com/multirom-dev
Device Tree - https://github.com/Multirom-Lux/android_device_motorola_potter
Donations (Please donate to the Creator @Tasssadar )
I'd be glad if you could spare a few bucks. You can use either paypal or Bitcoins, my address is 172RccLB2ffSnJyYwjYbUD3Nx4QX3R8Ris
Downloads
1. Main downloads
AndroidFileHost
FAQ and other notes
Device encryption
Encryption isn't supported right now. So decrypt your device before using this.
About security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.
Can I flash secondary roms on Micro SD?
Yes but it's is very slow, internal storage is much better to flash secondary roms.
How do I flash Gapps in Secondary ROMs?
After AddRom and is done, go back and Click on the installed Secondary ROM, you will see one of the option to 'Flash Zip', click and install Gapps. Then you can reboot into secondary ROMs, do gapps installation before rebooting otherwise as usual need to deal with SetupWizard FC, at least thats what I observe in my device.
No-kexec workaround (version 4)
As of this version you need to manually enable the no-kexec workaround.
Actually, depending on the developer, (s)he may have already enabled it. Nonetheless, you can still choose to override the settings:
Go to TWRP -> MultiROM -> Settings
and enable the No-KEXEC workaround option
once you do you'll also have the option for ADVanced settings, please see below for a detailed description, though in most cases the default should suffice.
Explanation of the no-kexec workaround advanced options
(the Info page is supposed to provide the same information as here, but I haven't added that yet)
1- Use no-kexec only when needed
This should be the default for most users, the other options are more intended for advanced uses (kernel debugging, and such).
If MultiROM detects a kexec-hardboot enabled kernel in primary slot, it will use the standard kexec method to boot the secondary. If on the other hand it does not detect that the kernel supports kexec-hardboot then it will use the workaround.
2- ... but also ask for confirmation before booting
Same as option 1 above, but in addition you will be presented with a confirmation message, if the workaround is about to be used:
3- Ask whether to kexec or use no-kexec on booting
If the kernel in primary slot does support kexec-hardboot'ing then you will be presented with a choice of which method to use
If the kernel does not support kexec-hardboot then you'll be informed as in option 2 above
4- Always force using no-kexec workaround
Forces the no-kexec workaround to be used, even if the kernel in primary slot has kexec-hardboot support
Options 2 and 3, always present the user with a GUI confirmation, whereas option 1 and 4 will act as instructed without prompting the user.
Visual feedback provided by the Booting... card
Regular kexec-hardboot boot
Booting using no-kexec-workaround
How does all this work, etc
The workaround:
MultiROM TWRP recovery works, and is able to flash ROMs to secondary
MultiROM in essence works (in particular, able to change the mount points during bootup)
what does not work is being able to use the secondary ROM's kernel (due to the lack of kexec-hardboot kernel and tools)
So how do we deal with booting any ROM if we can't use the proper kernel for the ROM?
Easy :
Upon selection of the ROM during MultiROM boot menu, we do the following:
"flash" secondary boot.img to primary partition slot
initiate a full reboot (secondary boot.img is in primary slot)
let the ROM auto-boot up on second boot
The good part:
It works.
.
Every secondary ROM has a boot.img file we can easily access to use the workaround; when you flash a ROM in MultiROM TWRP, not only are the "virtual" system, data, and cache partitions created, but also the boot.img.
The secondary ROMs' boot.img will be found /data/media/0/multirom/<name of rom>/boot.img or if it's on your external ext4 in the appropriate rom folder
We use that file and flash it to primary real boot partition and then upon second boot, the correct boot.img is in place for the correct ROM.
The bad part:
Unlike secondary ROMs, the primary ROM does not have a boot.img file... since it is the primary ROM, the boot.img should always be in the real boot partition, since MultiROM expects the primary kernel to have kexec-hardboot capability, but it does not, so I just go ahead and mess with your primary boot partition.
Since we have no "boot.img" file for the primary, my workaround makes a backup of the boot partition and names it primary_boot.img
In version 4 of the workaround, this backup is created and used only when booting a secondary ROM. When a secondary ROM is selected it's boot.img is flashed to primary slot, upon booting into the secondary ROM, the primary_boot.img is restored.
Long story short: the difference between kexec and no-kexec-workaround
Usual kexec-hardboot MultiROM
Select secondary ROM
MultiROM detects a boot.img
MultiROM reads the secondary boot.img into memory
MultiROM initiates a kexec second boot but into the secondary boot.img from above
MultiROM continues
No-kexec-workaround MultiROM
Select secondary ROM
MultiROM detects a boot.img
MultiROM flashes the secondary boot.img into the primary boot partition
MultiROM initiates a normal second boot but with the secondary boot.img in the real boot partition
MultiROM restores the primary_boot.img and continues as usual
so the difference is in point 3... whereas normal kexec'ing loads the secondary boot.img into memory and goes from there, the workaround, actually flashes it to the real primary boot partition... and continues normally from there
Devices using the no-kexec-workaround successfully
MultiROM threads for:
HTC One M7
HTC One M8
HTC One M9
.
Moto G 2015 by @GtrCraft
Moto X Play by @GtrCraft
OnePlus One (starting here) by @KINGbabasula
OnePlus 3 by @martinusbe
OnePlus X by @martinusbe ... (alpha status)
Sony Xperia Z5 by @Myself5
Sony Xperia L by @STRYDER~007
Sony Xperia SP by @Adrian DC
Xiaomi Redmi 2 by @premaca
.
(possibly Samsung Note 4, unsure if that was continued or not)
Others; unofficial builds? (if you are, kindly let me know, and I'll add you to the list)
Credits to:
@vache (For TWRP trees)
@nkk71 (For kexec workaround)
@fAIyaZ (For testing)
Thanks for this! I really was wanting dualboot for my G5 Plus.
Congrats :good:
Another thread to keep an eye on :cyclops:
Great
Quick Question
Does the twrp image include the latest changes from @vache that fixed sd card support?
kbro_indy said:
Does the twrp image include the latest changes from @vache that fixed sd card support?
Click to expand...
Click to collapse
Wish there was a separate thread
Sent from my Nexus 7 using Tapatalk
kbro_indy said:
Does the twrp image include the latest changes from @vache that fixed sd card support?
Click to expand...
Click to collapse
Yes, it does
Enviado desde mi Moto G (5) Plus mediante Tapatalk
thanks for this
Can anyone make guide video on YouTube ??
[email protected] said:
Can anyone make guide video on YouTube ??
Click to expand...
Click to collapse
No read the posts and you will understand
[email protected] said:
Can anyone make guide video on YouTube ??
Click to expand...
Click to collapse
There already guides on youtube
Yooo WHAT? I need this! Thanks man!
Time for update, mainly for twrp 3.1.1 release that has been added:
https://www.androidfilehost.com/?w=files&flid=182754
Nice Job. :good
Nice work.. Surely will hit the button .
I am here though a little bit off key..
Just want to find out if MULTI LOT can be ported to MTK devices and if yes.. can you do it for us
dmilz said:
Nice work.. Surely will hit the button .
I am here though a little bit off key..
Just want to find out if MULTI LOT can be ported to MTK devices and if yes.. can you do it for us
Click to expand...
Click to collapse
No idea and no
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for Moto G5S Plus. It can boot any Android ROM, besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action in general.
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. But it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
1. Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 2 parts you need to install:
Modified recovery (TWRP_multirom_sanders_YYYYMMDD-xx.img) - download the IMG file from second post and use fastboot or Normal TWRP recovery if you have or any other third party image installers from Google Playstore.
MultiROM (multirom-YYYYMMDD-v33e-UNOFFICIAL-sanders.zip) - download the ZIP file from second post and flash it in recovery.
2. Via MultiROM Manager app
We do not have Official Support, an unofficial APP can be downloaded from second post)
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using USB drive (not tested yet)
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
In some cases, you might need to flash patched kernel - get coresponding patched kernel version from second post and flash it to the secondary ROM sama way you flashed ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - add ROM to boot
- List ROMs - list installed ROMs and manage them
- Inject boot.img file - When you download for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - well, settings.
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
- Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.
Source code
MultiROM - https://github.com/MR-op3/multirom (branch mr-7.1)
Modified TWRP - https://github.com/MR-op3/android_bootable_recovery (branch mr-7.1)
Device Tree - https://github.com/MR-op3/device_motorola_sanders (branch mr)
Credits
nkk71 (For no-kexec workaround)
XDA:DevDB Information
[MOD][OCT 16][Sanders] MultiROM v33 || no-kexec workaround, Tool/Utility for the Moto G5S Plus
Contributors
premaca, syed sajid, GeneticEnginer
Version Information
Status: Beta
Current Beta Version: v33
Beta Release Date: 2017-10-16
Created 2017-10-17
Last Updated 2017-10-31
Changelog and Downloads
If you have come across with WRONG-PIN on Primary after the installation of secondary, flash the following Lock Fix.
Lockfix.zip
20171114
multirom-20171114-v33e- UNOFFICIAL-sanders
TWRP-multirom_sanders_20171114-01.img
20171016
multirom-20171016-v33e-UNOFFICIAL-sanders.zip
TWRP_multirom_sanders_20171016-02.img
- Initial Release
Flash this ZIP file multirom_uninstaller.zipto remove MultiROM from your device. It will erase all secondary ROMs. If you don't want MultiROM menus in recovery, re-flash clean TWRP, but it is not needed - those menus don't do anything if MultiROM is not installed.
Multirom manager APP: Will be uploaded Soon.
FAQ and other notes
Device encryption
Since v32, MultiROM supports encryption on this device (it has to be added for each device separately). It works only with Android-based secondary ROMs and the secondary ROMs don't know the device is encrypted, so they would allow you to encrypt the device again - do not do that. If you're using password, pin or pattern for the encryption, MultiROM will ask you for the password on boot. If you're booting the primary ROM, then Android will ask you for the password _again_ - unfortunately, there is no way for me to pass the "unencrypted" status to Android. If you're booting secondary ROM, MultiROM will ask you for the password again after the reboot - that's because I have to unencrypt the /data partition after the ROM's kernel is loaded.
I could omit the second password prompt when booting secondary ROM by temporarily saving the password somewhere, but that's obviously unsafe. So is using encryption with unlocked device though, so I might add this later.I have not tested it yet, as i never used ENCRYPTION on my device, will try to see if there are issues and more users for this use case
About security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.By default /external_sd is mounted and is used to store the ROMs.
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.
Will Motorola Stock works as Primary or Secondary ROM?
Yes, Motorola Stock version works with Multirom as Primary ROM, It is not advised to install stock as Secondary, use only as Primary ROM. You can then install other Android ROMs as secondaries.
How do I flash Gapps in Secondary ROMs?
After AddRom and is done, go back and Click on the installed Secondary ROM, you will see one of the option to 'Flash Zip', click and install Gapps. Then you can reboot into secondary ROMs, do gapps installation before rebooting otherwise as usual need to deal with SetupWizard FC, at least thats what I observe in my device.
Enabling no-kexec workaround
Please read all things about no-kexec workaround from the author words only, (to avoid duplicity and get latest information), thanks to @nkk71
[url]http://forum.xda-developers.com/showpost.php?p=64248526&postcount=4[/URL]
Reserved
Congrats on the release
But you may have missed a few commits, especially if you're going to be dealing with Oreo and/or sdcardfs
nkk71 said:
Congrats on the release
But you may have missed a few commits, especially if you're going to be dealing with Oreo and/or sdcardfs
Click to expand...
Click to collapse
Sure. Let's get them in. This is initial release, will pick the commits. Needed for our other devices too.
premaca said:
Sure. Let's get them in. This is initial release, will pick the commits. Needed for our other devices too.
Click to expand...
Click to collapse
They're still only on my repo, not merged with multirom-dev yet
https://github.com/nkk71/multirom/commits/master
https://github.com/nkk71/android_bootable_recovery/commits/android-7.1-mrom
There's Android 8.0 file_context fixes, and especially that nasty sdcardfs fix (it's a long commit message, but should be thorough enough)
Also the auto detect legacy props isn't in there (didn't push it, as technically it's supposed to be part of 8.0twrp branch), so if someone get the "assert failed this is for device xxx but your device is '<blank>' " then that's the deprecated legacy property problem.
Really up to you if you want to use these commits (I/we are), but the sdcardfs issue can become really nasty, eg here (he just nuked all his secondaries :/ )
nkk71 said:
They're still only on my repo, not merged with multirom-dev yet
https://github.com/nkk71/multirom/commits/master
https://github.com/nkk71/android_bootable_recovery/commits/android-7.1-mrom
There's Android 8.0 file_context fixes, and especially that nasty sdcardfs fix (it's a long commit message, but should be thorough enough)
Also the auto detect legacy props isn't in there (didn't push it, as technically it's supposed to be part of 8.0twrp branch), so if someone get the "assert failed this is for device xxx but your device is '<blank>' " then that's the deprecated legacy property problem.
Really up to you if you want to use these commits (I/we are), but the sdcardfs issue can become really nasty, eg here (he just nuked all his secondaries :/ )
Click to expand...
Click to collapse
i tried this it asked me for password to decrypt data it says wrong password even when i enter right one
i tried the same password for normal twrp it worked
its notworking out with this
---------- Post added at 12:33 PM ---------- Previous post was at 12:32 PM ----------
i tried this it asked me for password to decrypt data it says wrong password even when i enter right one
i tried the same password for normal twrp it worked
its notworking out with this
Format data button?? I don't know for sure if this is the answer for multi Boot mod but to flash anything in TWRP I had to format data which will also decrypt the phone. As follows... Boot to TWRP, press wipe and then on the right side of the screen above the "slide to wipe" icon is a button that says format data... IT WILL WIPE ALL DATA ON THE INTERNAL STORAGE!! PICTURES, DOWNLOADS, ETC...
winpooh said:
Format data button?? I don't know for sure if this is the answer for multi Boot mod but to flash anything in TWRP I had to format data which will also decrypt the phone. As follows... Boot to TWRP, press wipe and then on the right side of the screen above the "slide to wipe" icon is a button that says format data... IT WILL WIPE ALL DATA ON THE INTERNAL STORAGE!! PICTURES, DOWNLOADS, ETC...
Click to expand...
Click to collapse
Yes ,it can work after reset only, you have to do a backup first.
Thnx for ur work mate.. i really needed it to test out oreo roms without losing the stock one & it's working grt..!!
abhinav2hd said:
Thnx for ur work mate.. i really needed it to test out oreo roms without losing the stock one & it's working grt..!!
Click to expand...
Click to collapse
Be careful and do read the instructions also.
syed sajid said:
Be careful and do read the instructions also.
Click to expand...
Click to collapse
I've used multirom before.. i know how it works ?
abhinav2hd said:
I've used multirom before.. i know how it works ?
Click to expand...
Click to collapse
That's good, I'm not talking about how to use multirom?
Update Multirom Recovery !!!
TWRP-multirom_sanders_20171114-01
https://androidfilehost.com/?fid=962021903579492365
multirom-20171114-v33e- UNOFFICIAL-sanders
[URL="https://androidfilehost.com/?fid=889964283620765983]https://androidfilehost.com/?fid=889964283620765983[/URL]
Do I have to wipe data again after updating?
gaurav.saroya said:
Do I have to wipe data again after updating?
Click to expand...
Click to collapse
Nope, just flash it as normal..
syed sajid said:
Nope, just flash it as normal..
Click to expand...
Click to collapse
Okay thanks
syed sajid said:
Update Multirom Recovery !!!
TWRP-multirom_sanders_20171114-01
https://androidfilehost.com/?fid=962021903579492365
multirom-20171114-v33e- UNOFFICIAL-sanders
https://androidfilehost.com/?fid=889964283620765983
Click to expand...
Click to collapse
Second link not working
gaurav.saroya said:
Second link not working
Click to expand...
Click to collapse
Working ...afh too slow wait till open..
syed sajid said:
Working ...afh too slow wait till open..
Click to expand...
Click to collapse
It's working now