Related
Hi , greeting everyone !
Before appearing ICS, I made a small update custom, including small changes in the original firmware 3.2.79.
This release is permanently ROOT, busybox is installed proper and is unique , Su and Superuser is up to date ! At the bottom you have Update of this version (activated vibrator and fixed adb command).
Included : 24/01/12
- new boot animation;
- battery percentage, and other new Icon;
- several applications in addition ( office free, flashplayer 11,adobe air.....+++);
- windows animations;
- Sony Ericsson Xperia Arc sound and other stuff.....
Now we have latest update of Su binary v3.0.3.2 , Superuser v3.0.7(41), unique busybox v1.19.3 installed into system/xbin ;
There is no need to install busybox.apk or busybox installer.apk from market, busybox is already installed into /system/xbin/
Also included some tweaks : - increase sdcard speed, - managemant ram memory....and increase reaction speed !
These are the files you need for install this Custom Rom :
- archos.ext4 => http://www.4shared.com/archive/tOxGcPqa/archos.html , http://hotfile.com/dl/143897684/d5edc5d/archos.7z.html
- zImage => http://www.4shared.com/file/KXp8bLDa/zImage.html ; http://hotfile.com/dl/144036333/e7d0e75/zImage.html
- initramfs.cpio.gz => http://www.4shared.com/zip/HnEobpnG/initramfscpiogz.html
How install :
- because the file structure is changed , you need perform a clean installation : Recovery -> Format System -> Reformat Devices...-> I Understand -> ok -> copy firmware_archos_it4.aos into new driver -> ok. After reboot copy archos.ext4 into Internal Storage ( data/media/), reboot into recovery , Recovery System-> Developer Edition Menu -> Remove Kernel ( for boot only to SDE) -> I Understand -> Ok -> Developer Edition Menu -> Flash Kernel and Initramfs -> copy zImage and initramfs into new driver -> Ok ! that's all ....now you have clean install custom rom
Solved - md5sum into superuser when you try to update the su binary , now check md5sum OK!
I did not managed any version of .squashfs because android compiler can't install busybox into system/xbin ( .squashf is NOT RW ), this is why I presented only version of ext4 ...Good Luck !
****************************************************************
Update : 27/01/12
- now >adb shell - fixed and enabel vibrator
- archos.ext4 => http://www.4shared.com/zip/dOscQIvA/archos_up.html ; http://hotfile.com/dl/143982123/b452656/archos_up.zip.html
What did you use to increase ram?
Sent from my HTC Desire HD using xda premium
Quinny899 said:
What did you use to increase ram?
Sent from my HTC Desire HD using xda premium
Click to expand...
Click to collapse
Hi! ...I just increase free ram , lol !
surdu_petru said:
Hi! ...I just increase free ram , lol !
Click to expand...
Click to collapse
Ok
Sent from my ARCHOS 80G9 using xda premium
good job tomorrow i try it (multumesc )
Maryanos25 said:
good job tomorrow i try it (multumesc )
Click to expand...
Click to collapse
..cu placere ....incearca-l nu vei regreta !
with pleasure ...try it...you'll no regret !
Nu ama avut rabdare si l-am instalat. Merge ok. Merci mult.
Y dont have patience and y instaled. Its ok. Thanks.
Sent from my ARCHOS 80G9 using xda premium
Quick question, and I appologize if this is the wrong place for this, I'm currently running your 3.2.78 (ext4). Do I need to update the stock firmware directly from archos first or can I just flash this 3.2.79 rom over what I currently have. Also I "removed android kernel" earlier to always boot rooted if that matters. So what's the best way of going about this?
surdu_petru said:
I did not managed an version of .squashfs because I can't install busybox into system/xbin ( .squashf is R/O ), this is why I presented only version of ext4 ...Good Luck !
Click to expand...
Click to collapse
You can try this:
-get a copy of busybox and symlinks from a working rom (make a .tar or .tar.gz of G9's [email protected])
-copy busybox+symlinks in appropriate directories and chmod them (just to be sure)
-mksquashfs
This *should* work (I've messed around a bit with squashfs on another device)
First custom rom i've seen. Great ! Thank you very much. I will try it later
First thank you surdu_petru Every new rooted/modified rom, I need to start tablet with "original" rom to copy the ext rom into the tablet, and every time, restarting for the first time after the update from sde with the "new" rom, I have SuperUser with empty list (and I have to re-add all the programs in my list). Is there a way to copy the ext rom without booting with original rom? thank you and sorry for my poor english
hitman72 said:
Is there a way to copy the ext rom without booting with original rom? thank you and sorry for my poor english
Click to expand...
Click to collapse
Not yet, accessing /data/media requires a working system (adb is not present in SDE/recovery)
However you should be able to update using "previous" custom firmware- system filename is different
install directly over the version rooted 3.2.79.
Work good. =)
Boot animation - maybe simply text android install? =) Can i change it himself?
gen_scheisskopf said:
You can try this:
-get a copy of busybox and symlinks from a working rom (make a .tar or .tar.gz of G9's [email protected])
-copy busybox+symlinks in appropriate directories and chmod them (just to be sure)
-mksquashfs
This *should* work (I've messed around a bit with squashfs on another device)
Click to expand...
Click to collapse
OK thanks !....but do not want to complicate ... I let the compiler to perform, if he says he can not because I have not rw rights !...I left it ..... I know that there are solutions, but leave it in for users !
ro4sho said:
First custom rom i've seen. Great ! Thank you very much. I will try it later
Click to expand...
Click to collapse
Thanks , lol....
gegabit said:
install directly over the version rooted 3.2.79.
Work good. =)
Boot animation - maybe simply text android install? =) Can i change it himself?
Click to expand...
Click to collapse
Sure, you can change what you want, system is RW, but attention ! do it carefully !
gen_scheisskopf said:
Not yet, accessing /data/media requires a working system (adb is not present in SDE/recovery)
However you should be able to update using "previous" custom firmware- system filename is different
Click to expand...
Click to collapse
In my builds, I added a mechanism to do that, the idea was to add a ".update" to filename to have the initrd replace the old image with the ".update" image before mounting and booting.
Surdu_petru, I don't know if you did the same in your initrd. As gen_scheisskopf mentioned in the sde thread, wiping dalvik-cache is probably a good idea if build changes, it could be done silently there or asked with a menu ? And a common file naming convention between us would help, I saw that you use the archos.img, we could define this as a standard ?
letama said:
In my builds, I added a mechanism to do that, the idea was to add a ".update" to filename to have the initrd replace the old image with the ".update" image before mounting and booting.
Surdu_petru, I don't know if you did the same in your initrd. As gen_scheisskopf mentioned in the sde thread, wiping dalvik-cache is probably a good idea if build changes, it could be done silently there or asked with a menu ? And a common file naming convention between us would help, I saw that you use the archos.img, we could define this as a standard ?
Click to expand...
Click to collapse
Ok I know what you mean...and yes ! for Stock firmware_3.2.79 (files.ext4/squqsh).update exist into initramfs, but because I made some changes in directory structure into Custom Rom , now .update it's not perform .
Ok it's very good idea , for future I'll rename (archos.ext4/squashfs).update
Thanks for your advice !
surdu_petru
will there be a custom rom for the archos 80 g9 250hdd or a root method
it would be nice to have a custom rom on my hard drive tablet
root method only seems to work on sd card versions of this nice tablet
regards phil
philmein said:
surdu_petru
will there be a custom rom for the archos 80 g9 250hdd or a root method
it would be nice to have a custom rom on my hard drive tablet
root method only seems to work on sd card versions of this nice tablet
regards phil
Click to expand...
Click to collapse
Hi!
This custom rom it's work for G9 tablett 80/101 but I don't know if it is supported for HDD.....maybe @letama or or another endorsed person will answer.....for you !
Okay i only started looking at multirom around 4hours before releasing this, so i am aware we already have a multiROM thread, however i do believe it's outdated, and perhaps unsupported now, so i am merging a supported multirom with my TWRP thread where i will be keeping both updated, thanks to @Tasssadar for bringing multiROM to the android community. I failed hard with outdated sources from adam so i have written my own stuff, but i think iodak is using his .diff
Taken and modified from official thread at Flo
Introduction
MultiROM is one-of-a-kind multi-boot mod for Nexus 7. 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
Manual installation
Find all needed files here: MOD Edit: Links removed
I think Iodak has the kexec patch so use his Rom, i'm not too sure on how to add a kexec so i'll look into it, this does support KK roms as i tried it, and so has dan.
MultiROM has 3 parts you need to install:
MultiROM multirom.zip - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_Mrom.zip) - download and flash in recovery.
Patched kernel - Iodaks kernel i believe is kexec patched, worked for me, have a play, i use share kernel for KK roms of the same type. I suggest this.
You current rom will not be erased by the installation.
Download links are somewhere below
Adding ROMs
Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Updating/changing ROMs
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.
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
MultiROM - https://github.com/Tasssadar/multirom/tree/master (branch master)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
Device Tree for building Mrom and TWRPhttps://github.com/Fluoxetine/android_device_lge_p880 (branch TWRP)
Thanks and Links
Official thread with screenshots, donate link, and changelogs
Original Thread for 4xHD by @Adam77Root
FAQ and other notes
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.
Next, MultiROM doesn't work with /data encryption. Not many people who use custom ROMs also use encryption anyway, so that isn't much of a concern.
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.
Can I have different versions of Android working alongside
Yes. As long as you select "Don't shere kernel" when installing the secondary ROM, the systems are separated.
MultiROM recovery says it's 2.6.3.0. Why isn't it updated to 2.6.3.*highernumber*?
It is, it just shows wrong version.
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 you port MultiROM to device X?
No, probably. I won't port MultiROM to any device I don't own, because it is very difficult to provide the level of support I want to provide if I can't test things myself, as proven by the Nexus 4 port. I'll probably keep buying Nexus devices and keep porting MultiROM to those myself, but I can't buy every single device - I'm still a student, all my existing devices were bought using some kind of money grant or donations from users.
But, you can port it yourself, the wiki should give you at least some idea how to do that: https://github.com/Tasssadar/multirom/wiki/Porting-MultiROM
Message from Fluoxetine
I spend a lot of time trying to bring new roms/mods to this and many other devices, this doesn't really cost me anything so i will not ask for money, however i am open to other donations, if you can supply me with a donated spot on a build server that would be great! Otherwise, you can supply me with Drink and Food to snack on whilst i work away, just PM me with an amount and i'll choose a product from amazon and send you my address and info for it to be shipped directly to me Thanks for your time guys.
Click to expand...
Click to collapse
-
-
-
-
-
-
Changelog from my end and not multiROM (Ascending Order)
Code:
- [I] Release within 4 hours of solid working on it [/I]
- Fix Recovery
- Fix touch input
- Build Multirom.zip
- Remove weird vibration
- Fix MultiRom button
- Fix Layout
- Build Modified TWRP
- Create TWRP.fstab
- Build MultiRom.zip
- Fix Sizing
- Build Initial MultiRom.zip
- Create mr_init_devices.c
- Create a modified BoardConfig.mk
- Sync Modified TWRP
- Sync MultiRom
- Sync Omni
Reserved
Great work
Sent from my LG-P880 using Tapatalk
Ha, it's working... Somtimes it's a bit tricky to install secondary ROMs. To get Zaiben RC8 booting I installed it from a backup.
Pure CM11 (20140220 nightly) without gapps is booting, after flashing gapps in MultiROM it dosn't boot. Only using a backup to create it as secondary works for me...
But no way to install AnyKernels like Iodak9.95 om secondary. For CM/ASOP you can try sharing option, for stock-based the only way is using backup with installed custom kernel...
Since AnyKernel there are no boot images for different roms, so there is nothing to inject...
One downer for me is missing ADB in recovery. I've tried mounting USB-Device first, no way. Device manager in Windows shows nothing.
In bootmenue ADB is working, but it's useless without mounted system, data etc. When I use "adb shell mount -o remount,rw system" I got "mount: can't find system in /proc/mounts"
And I noticed after booting any secondary ROM, primary needs wiping cach/dalvikcache to prevent a bootloop...
EDIT: Got system access from ADB...
Code:
adb shell mount /dev/block/platform/sdhci-tegra.3/by-name/APP /system
Nice work man! Does ADB work in MultiROM? Did you check new hardboot patches? It doesn't need target kernel to be patched anymore.
Sent from my OmniROM-powered LG Optimus 4X HD
Adam77Root said:
Nice work man! Does ADB work in MultiROM? Did you check new hardboot patches? It doesn't need target kernel to be patched anymore.
Sent from my OmniROM-powered LG Optimus 4X HD
Click to expand...
Click to collapse
I've got ADB only working from boot menu. With correct mounts from ADB shell I'm able to modfy anthing I need...
But ADB working in TWRP would be nice
Adam77Root said:
Nice work man! Does ADB work in MultiROM? Did you check new hardboot patches? It doesn't need target kernel to be patched anymore.
Sent from my OmniROM-powered LG Optimus 4X HD
Click to expand...
Click to collapse
I don't think ADB works in multiROM, i saw in your patch a few ADB related stuff but in all honesty i think i left them and am still using all the same ones as grouper :') But i will be looking into this.
Also i haven't checked out any of the new hardboot patches, because in all honesty i have no clue what they are :highfive: but i can learn, i'll look into it now I just threw myself at multirom and looked at whatever the other devices had, and then just made it for p880 :3 Touch was an asshole Till i realized all i had to do was change b to an a.
Edit 1: This was the device specific mrom stuff i needed to add https://github.com/Fluoxetine/android_device_lge_p880/blob/TWRP/mr_init_devices.c
Edit 2: Added https://github.com/Tasssadar/androi...mmit/005cf387c1404eac862cc35153d7641d18faef4c this commit manualy, well for the files we had i added, we didn't have lge_devices or reboot.c and reset.c was different :s
Compiling stock CM11 kernel with this patch and see if i can dual boot stock with stock kernel that isnt patched, or cm10.1 with stock cm10.1 selecting "don't share"
Edit 3: Getting Errors with the changes i made, so gonna need some more time to amend them for the p880, i think i might have to call on some other devs to help out with this, i have no idea what i'm doing..
Nice work, could I ask you to prepare multirom uninstaller also?
It is working very well, thanks for this. All I do was I installed a CM-based Kitkat rom (Mokee) in the internal, and for the secondary, I installed stock rom (Zaiben) with kernel sharing enabled. Both roms are working flawlessly.
Thanks man I love your work!!
We can install FirefoxOS and Ubuntu too? MultiRom Manager working?
Sent from my LG-P880 using XDA Premium 4 mobile app
Can't seem to get anything to boot as secondary, I've tried zaiben and nameless. From backup and from zip, with and without kernel sharing.
Most times device just shuts down, once I got to boot animation and then it froze.
All backups normally boot as primary.
Primary uses latest iodak.
Probably I'm doing something wrong since others report it working.
Sent from my LG-P880 using Tapatalk
dcos said:
Can't seem to get anything to boot as secondary, I've tried zaiben and nameless. From backup and from zip, with and without kernel sharing.
Most times device just shuts down, once I got to boot animation and then it froze.
All backups normally boot as primary.
Primary uses latest iodak.
Probably I'm doing something wrong since others report it working.
Sent from my LG-P880 using Tapatalk
Click to expand...
Click to collapse
Try having your device connected to ac power while rebooting to secondary. If that works, then its the same problem as with adams multiboot, but it has two workarounds
Will you keep the non-dualboot twrp ?
I'm really not into this dual boot gimmicks and really like, and am still using your "clean" twrp version that works flawless BTW
Tapatalked from my CM11-LG4XHD-P880
remorema said:
Will you keep the non-dualboot twrp ?
I'm really not into this dual boot gimmicks and really like, and am still using your "clean" twrp version that works flawless BTW
Tapatalked from my CM11-LG4XHD-P880
Click to expand...
Click to collapse
You can use this recovery witout flashing the multiboot binarys... And the N7 multirom uninstaller works after editing the updater-script.
dcos said:
Can't seem to get anything to boot as secondary, I've tried zaiben and nameless. From backup and from zip, with and without kernel sharing.
Most times device just shuts down, once I got to boot animation and then it froze.
All backups normally boot as primary.
Primary uses latest iodak.
Probably I'm doing something wrong since others report it working.
Sent from my LG-P880 using Tapatalk
Click to expand...
Click to collapse
When you see in listeted roms with shared boot "remove boot.img" ,you can do this.
When I klicked "share boot" on ROM installation and after flashing it have its own boot.img. Don't know why, those ROMs will not boot on my device...
I lose signal on Miui 4.2.2 and CM10.1.3 dosen't boot.
I use Omnirom 4.4 and Iodak 9.95 as default.
Dual boot would be intresting if Android/data/ of secondary rom was on the external sdcard. I'm not very confident of using a secondary rom sharing that same folder as the primary rom. IMO that could cause some issues. Example: if I uninstall a game I'm secondary ROM the obb file of that ROM will be deleted on primary ROM and vice versa.
Tapatalked from my CM11-LG4XHD-P880
love you guy! i like the idea of having multiple roms, but I never got this stuff running not on my Lg 4X either on my nexus 7 - hope to get it working now with this release
Kexec for stock Cm11 kernel?
Can someone patch stock Cm11 kernel with kexec-hardboot ?
Okay so, i have uploaded CM11 stock kernel with a kexec patch, although this is not the same patch as used in iodak or stock patched kernel, i have taken the commits from groupers kernel with kexec and have implemented them into our stock cm11 kernel (took ages, had to do it manually).
This should mean that the target kernels do not need to be patched, only the host kernel needs the patch, i tried this with carbon-kk with my kernel flashed and added Carbon-KK WITHOUT SHARING kernel, then when i selected it to boot, as soon as the screen goes black HOLD THE POWER BUTTON, and then it will boot into the secondary Rom with the stock kernel that comes with it!
Well i think so anyway, Danny is testing for me now, maybe some of you could test it too? I'm not sure what will happen, i only tried it with carbon and my kexec as host, and stock carbon as target.
Link is here for the kernel http://d-h.st/j9Z or just check my folder in OP for the MultiROM stuff
For those who are having signal problems or no mobile internet connection from secondary ROM(s) with kernel sharing, you have to copy the kernel modules (baseband_usb_chr.ko, raw_ip_net.ko, scsi_wait_scan.ko) from internal ROM module folder (/system/lib/modules) to your secondary ROM. Make sure to change the permissions as well.
Just my 20 cents .
not able to flash kernel in secondary roms
hi, i have Enox rom as default rom and i installed omni 4.4.2 kk rom as secondary, and no kernel sharing.
now it boots my Enox rom but doesn't boot omni with error to have kernel with patch
so i go in advance > multirom > select omni > flash zip > and flash iodak kernel 9.95, but it fails every time, i tried iodak 9.5 too, but same,
am i doing something wrong or its not possible to flash kernels in secondary roms?
then what am i supposed to do now?
i really don't wanna change kernel of my default rom, it's working perfect with amazing battery life that i want, but i want secondary roms with different kernels ?
-NOTE: The following guide has been specifically written for LG P-880 (Optimus 4X HD), after a lot of reading, flashing and managing ROMs and kernels on MultiROM; I have been asked by some users, and now it's here, I hope it to be clear and useful; it includes some parts extracted from the original Nexus7 thread, and readapted for our device. For the original MultiROM thread by @Tasssadar, go at the link below:
http://forum.xda-developers.com/showthread.php?t=2457063
MultiROM is one-of-a-kind multi-boot mod, originally built for Nexus 7 by @Tasssadar, ported and re-adapted to work with LG P-880 by @Adam77Root, then by @Fluoxetine, and finally by Mourta @IcanhasLG (coming soon, don't ask for ETA's, please). It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to our device. 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, or restore nandroid backups as secondary ROMs, too.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
1) INSTALLATION
MultiROM has 3 parts you need to install:
* MultiROM.zip (A new version built by Mourta @IcanhasLG will come soon; actually, the latest MultiROM.zip by @Fluoxetine can be found here: https://app.box.com/s/fmigiyd8nsprc8jxwahn) - download the ZIP file and flash it in recovery.
* Modified TWRP recovery (the actual modified recovery is the one provided by @Adam77Root - go here for Adam's modified TWRP thread and for download links: http://forum.xda-developers.com/showthread.php?p=46431004). Download the latest IMG file and use terminal emulator to flash it (the easier way to flash it without a PC). Please, follow the steps below for a safe flash:
-Rename the IMG file into "recovery.img"
-Open terminal emulator
-Type "su", then enter
-Type "cat /mnt/sdcard/recovery.img >/dev/block/mmcblk0p1", then enter
-Type "sync", then enter
-Type "exit", then enter
-Reboot your phone
* Kexec-hardboot patched kernel - You can use iodak (patched since from v8), Mourta, or Cyodak. Download the ZIP file and flash it in recovery.
IMPORTANT: You current rom will NOT be erased by the installation.
2) ADDING ROMs:
* Go to recovery, select Advanced -> MultiROM -> Add ROM. At this point, you can choice if you want to share or not to share internal ROM's kernel with your new secondary rom: if you want to, just select the "Share kernel with Internal ROM" option; if you don't, select the "don't share" option. The sharing mode is helpful if you need to use an anykernel kernel with a secondary ROM (see step 2.1) or just to share the Internal ROM's kernel with secondaries, if you need it.
* Select the ROM's zip file you want to flash, or the nandoid backup file you want to restore as a secondary ROM, and confirm.
* Flash Gapps package (optional)
*Flash custom kernel (optional) (WARNING: only no-anykernel patched kernels can directly be flashed on the top of secondary ROMs; if you try flashing an anykernel patched kernel, you will end in a bootloop; if you want to use an anykernel patched kernel on a secondary ROM, go to step 2.1)
2.1) USING ANYKERNEL PATCHED KERNELS WITH SECONDARY ROMs
Actually, MultiROM doesn't support direct flashing of anykernel patched kernels on the top of secondary ROMs. There are some workarounds to let secondary ROMs use this kind of kernels:
a. Share the kernel with internal ROM:
If you flashed an anykernel patched kernel (it must be kexec-hardboot patched, too) on the top of internal ROM, you will be able to share it with secondary ROMs too. If you did it, just follow the steps below, when adding a new secondary ROM:
* Go to recovery, select Advanced -> MultiROM -> Add ROM. At this point, you can choose if you want to share or not to share internal ROM's kernel with your new secondary rom: if you want to, just select the "Share kernel with Internal ROM" option.
b. Remove original boot.img from secondary ROM:
If you flashed a secondary ROM without selecting the "Share kernel with internal ROM" option, but you flashed an anykernel patched kernel (it must be kexec-hardboot patched, too) on the top of internal ROM before, you can share it with secondary ROM following the steps below:
* In recovery, Advanced -> MultiROM -> List ROMs -> "Your rom's name", there is a button: "Remove boot.img". This action switches ROM to "share kernel" mode. Flashing a ZIP which contains kernel (even ROM update!) into that secondary ROM could put it into "don't share" mode again.
* After removing the original boot.img, you will see a new "Inject boot.img" button replacing the old "Remove boot.img" one: this option allows you to inject your secondary ROM with a different boot.img, backed up from other kernels you flashed before on the top of other ROMs, or backed up directly from other ROMs. Do this at your own risk, it may cause bugs or not, depending by your knowledge of what you are going to inject here.
At any rate, I personally tried the a. step above, and after that I tried to flash a ROM's zip update: the "share kernel" mode hasn't been turned off.
3) UPDATING/CHANGING ROMs
a. Primary ROM (Internal)
* Wipe /cache, /dalvik, /system, or do factory reset if needed (it won't erase secondary ROMs)
* Flash ROM's ZIP file as usual
* Flash Gapps package (optional)
*Flash custom kernel (optional) (WARNING: if you want secondary ROMs to properly boot, you should flash only kexec-hardboot patched kernels, on the top of Internal ROM. Flashing a no-patched kernel won't allow MultiROM to manage secondary ROMs' boot).
* After erasing /system partition, or flashing a new kernel, a "bug" could happen: the menu with all the ROMs won't show up during boot.
If so, re-flash the MultiROM zip after having flashed the ROM update and the other related stuff, 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.
b. Secondary Android ROMs
If you want to change a ROM, select it in Advanced -> MultiROM -> List ROMs, delete it using the "Delete" button, then add the new one (following the instructions explained in step 2). To update ROM, follow these steps:
* Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
* Wipe /cache, /dalvik, and so on, by pressing the proper button showed on the screen
* Select "Flash ZIP" and flash ROM's ZIP file.
* Flash Gapps package (optional)
*Flash custom kernel (optional) (WARNING: only no-anykernel patched kernels can directly be flashed on the top of secondary ROMs; if you try flashing an anykernel patched kernel, you will end in a bootloop; if you want to use an anykernel patched kernel on a secondary ROM, go to step 2.1)
4) ERASING SECONDARY ROMs
* Just go to Advanced -> MultiROM -> List ROMs and select the ROM you want to delete.
* Select "Delete"
5) BOOTING SECONDARY ROMs
* Turn on the phone; after the LG logo, the MultiROM boot menu will appear. If you don't do anything, Internal ROM will boot. If you want to boot into secondary ROMs, you have to tap on the countdown pop-up
* After that, you can choose your desired ROM, then press "Boot". For secondary ROMs which don't share kernel with internal ROM: press "Boot" and hold down the power button until phone vibrates (actually, our MultiROM has a bug which doesn't allow secondary ROMs to boot, if you don't hold power button after having tapped "Boot", if you haven't shared kernel with internal ROM.)
6) UNINSTALLING MultiROM
The easiest way is to just reflash your custom kernel or a ROM zip on the top of your internal ROM, after having made the usual wipes: this will erase the MultiROM binaries.
More updates will come when we'll have a new version, such as for swapping ROMs through internal and secondary positions, making the internal ROM secondary, and so on (these features don't work fine, at the moment).
When flashing a zip file (SuperSu etc.) on secondary ROMs with shared Kernel from primary, a boot.img will be created in /data/media/0/multirom/"YourSecondary"/... I use these images to repack them for stock ROMs or MiUi to get them work in MR...
Secondaries with own boot images can be booted too. After you have chose your desired ROM in MR bootmanager, press "Boot" and hold down the power button until phone vibrates. Your device should reboot to the chosen ROM...
Most of the ROMs I've tried as secondary are working flawlessly in MR... Only MoKee have made some Problems...
Fladder72 said:
When flashing a zip file (SuperSu etc.) on secondary ROMs with shared Kernel from primary, a boot.img wil be created in /data/media/0/multirom/"YourSecondary"/... I use these images to repack them for stock ROMs or MiUi...
Secondaries with own boot images can be booted too. After you have chose your desired ROM in MR bootmanager and press "Boot", you have to hold down the power button until phone vibrates. Most of the ROMs I've tried as secondary are working flawlessly in MR...
Click to expand...
Click to collapse
Yep, what you're saying is right, nobody affirmed the contrary
Right, I've forgotten the more banal thing: the necessity of holding down power button, while booting a secondary ROM I'm adding it into the guide right now
For secondary ROMs with shared kernel there is no need for hold down power button. Only for secondaries with own kernel images.
Currently I have in MR:
JellyFishHD 1.3
Vanir 4.4.4 090214
Zaiben RC16
MiUi 4.8.1
All ROMs are booting. Only MiUi have a problem with access to External SD
Fladder72 said:
For secondary ROMs with shared kernel there is no need for hold down power button. Only for secondaries with own kernel images.
Currently I have in MR:
JellyFishHD 1.3
Vanir 4.4.4 090214
Zaiben RC16
MiUi 4.8.1
All ROMs are booting. Only MiUi have a problem with access to External SD
Click to expand...
Click to collapse
Yep, I knew that too, I've already written that in last update Thank you for having helped me remembering those things! You know, sometimes those steps begin automatic, while using this mod, so you don't remember them as a necessary thing to explain, my bad!
Curiously the device boots any ROM while it's connected via USB, without hold down Power button for restart...
Fladder72 said:
Curiously the device boots any ROM while it's connected via USB, without hold down Power button for restart...
Click to expand...
Click to collapse
Yep, it's right, I never understood the reason for that..probably it has something to do with some commits, not rightly ported for our device, or not easily portable
@Fladder72 hows vanir 4.4.4 performnig ? Is it dev based or cm ? Ext4?
@peppethustra great guide will try it when i have the time.BTW we need TWRP or we can flesh it with CWM ?
Vanir 4.4.4 runs like hell... Realy fast with Vanir stock kernel, an a bit faster with Mourta's... For me the fastes KK-Rom at this momemt. :good:
Maybe next I'll give Beanstalk a try...
I use only Ext4, because I don't like f2fs... Too much early stage sh*t...
I'm not shure, but I think, Vanir is CM based...
dimi89 said:
@Fladder72 hows vanir 4.4.4 performnig ? Is it dev based or cm ? Ext4?
@peppethustra great guide will try it when i have the time.BTW we need TWRP or we can flesh it with CWM ?
Click to expand...
Click to collapse
Thank you! You must use modified TWRP built by Adam, as said in OP, it's the only recovery built to work with MultiROM binaries
ok so i returned to multirom thank to u. OFC i was using it before and know how it goes.
I flashed multirom.zip by fluoxetine then flashed latest Adam's recovery via fastboot.
My problem is : Internal : pa 4.5 beta4 with mourta 09.02 kernel ---> then add rom cm11 09.02 unofficial by Demetris with his kernel + gapps ----->reboot ----> in multirom i choose cm11 boot, hold power button blah blah ----> booom again in multirom and trying to boot cm tells me there is no kexec . I think "what the??" booting internal rom and there is pa 4,5 beta4 with demetris 09,02 kernel!! WTF?XDXDXD i can give screenshots
EDIT : keep getting better when i reboot it goes back to mourta's kernel?
seems i found multikernel solution?XD
@gerciolisz Ahahahah, wt*? XD
srsly i'll give you srceenshots in 5 minutes
maybe i should first flash recovery then multirom in new recovery?
dunno
edit : https://drive.google.com/file/d/0Bww8W1t_MtuSd1RBUXV5eVQxb3M/edit?usp=sharing
https://drive.google.com/file/d/0Bww8W1t_MtuSUHJBdldJc1pQaGs/edit?usp=sharing
gerciolisz said:
srsly i'll give you srceenshots in 5 minutes
maybe i should first flash recovery then multirom in new recovery?
dunno
edit : https://drive.google.com/file/d/0Bww8W1t_MtuSd1RBUXV5eVQxb3M/edit?usp=sharing
https://drive.google.com/file/d/0Bww8W1t_MtuSUHJBdldJc1pQaGs/edit?usp=sharing
Click to expand...
Click to collapse
Eheheh, very funny XD
Yep, try flashing on that way, personally I did so, when I flashed TWRP and Multirom coming from CWM..but it remains a strange thing!
peppethustra said:
Eheheh, very funny XD
Yep, try flashing on that way, personally I did so, when I flashed TWRP and Multirom coming from CWM..but it remains a strange thing!
Click to expand...
Click to collapse
I reflashed everything and same issue.. I think @IcanhasLG 's kernel can be a problem here.. I'll gry with old iodak v10 and report here soon
gerciolisz said:
I reflashed everything and same issue.. I think @IcanhasLG 's kernel can be a problem here.. I'll gry with old iodak v10 and report here soon
Click to expand...
Click to collapse
No problem with his kernel here, and I'm using it with MultiROM as principal kernel on the top of internal ROM since from the first release
peppethustra said:
No problem with his kernel here, and I'm using it with MultiROM as principal kernel on the top of internal ROM since from the first release
Click to expand...
Click to collapse
I have the same problem like gerciolisz with mourtas ls and latest kernel.
I wanted to try latest beanstalk today.
I didn't use multirom for a while so i installed recovery and multirom new but this doesn't help.
With flashing orginal iodak v10 in internal rom it works booting secondary rom.
Since you and some users could boot secondary with mourtas kernel it could be that this error is tegra variant relatet.
I have variant 0.
I have tested the different versions from mourta kernel
mourta-2014-07-27 is the last working version on my phone. With all later versions i can't boot secondary roms
Is there a way to log multirom booting?
@Donar81 damn thx man for this whole testing i am sure if there are more than just me mourta will look into this issue.
But i wonder how it work for others... I have variant 1.
Donar81 said:
I have the same problem like gerciolisz with mourtas ls and latest kernel.
I wanted to try latest beanstalk today.
I didn't use multirom for a while so i installed recovery and multirom new but this doesn't help.
With flashing orginal iodak v10 in internal rom it works booting secondary rom.
Since you and some users could boot secondary with mourtas kernel it could be that this error is tegra variant relatet.
I have variant 0.
I have tested the different versions from mourta kernel
mourta-2014-07-27 is the last working version on my phone. With all later versions i can't boot secondary roms
Is there a way to log multirom booting?
Click to expand...
Click to collapse
gerciolisz said:
@Donar81 damn thx man for this whole testing i am sure if there are more than just me mourta will look into this issue.
But i wonder how it work for others... I have variant 1.
Click to expand...
Click to collapse
I have variant3, and I've not the problem.. Yes, maybe it's better to ask him..What do you think, @IcanhasLG?
I have variant 0 and got no problems. I can boot scondaries with Moutras kernel...
---------- Post added at 11:46 AM ---------- Previous post was at 11:30 AM ----------
gerciolisz said:
ok so i returned to multirom thank to u. OFC i was using it before and know how it goes.
I flashed multirom.zip by fluoxetine then flashed latest Adam's recovery via fastboot.
My problem is : Internal : pa 4.5 beta4 with mourta 09.02 kernel ---> then add rom cm11 09.02 unofficial by Demetris with his kernel + gapps ----->reboot ----> in multirom i choose cm11 boot, hold power button blah blah ----> booom again in multirom and trying to boot cm tells me there is no kexec . I think "what the??" booting internal rom and there is pa 4,5 beta4 with demetris 09,02 kernel!! WTF?XDXDXD i can give screenshots
EDIT : keep getting better when i reboot it goes back to mourta's kernel?
seems i found multikernel solution?XD
Click to expand...
Click to collapse
Remove the boot.img in recovery/Multirom/Manage ROMs/YourSecondary. Now your primary will share the Kernel with your scondary. Can you boot now primary and secondary without any issue?
{
"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"
}
MultiROM is a one-of-a-kind multi-boot mod. 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.
IMPORTANT
I'm not responsible for anything, you do all this on your own risk.
Once you have flashed and set up MultiROM, don't flash another boot.img using fastboot.
If you want to uninstall MultiROM, just flash the MultiROM uninstaller.
Your device must not be encrypted.
To all devs maintaing Stock-based ROMs: Feel free to use my patched stock kernels to add MultiROM support to your ROMs.
When booting another ROM, you'll notice that in some cases, you can enter the recovery of the boot.img of the ROM. Please don't use it, flash everything using MultiROM TWRP.
INSTALLATION
Install the MultiRom Manager app from the store and install the recovery and multirom.
Reboot into MultiROM TWRP and flash the MultiROM installer --> Sould be done automatically.
Make sure you are on a Rom compatible with one of these kernels and flash it
In order to boot a secondary rom you MUST enable the "kexec workaround" option in the MultiRom settings found in the recovery.
That's it. You can now go to "MultiROM menu" (Top right corner in the recovery) to start flashing other ROMs.
Alternative installation method (if installation via the above method fails)
Download the files named multirom-<date>.zip and recovery-<date>.img from here.
You should use md5sum to validate the downloaded files using the provided xyz.md5 files in the same download location.
Copy the files to the sdcard of your device.
Use "adb shell" to open a shell on the device and use "su" to obtain root rights (adb must be set up on your computer, instructions are found on xda).
Adjust the following command and enter it in the shell: "dd if=/sdcard/recovery-<date>.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel"
Reboot into recovery (shutdown, then VolDown + Power).
Flash the multirom zip from the sdcard.
Enjoy.
Adding ROMs
Go to recovery, select "MultiROM menu" (Top right corner in the recovery) -> 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 menu" (Top right corner in the recovery) in recovery and do Inject curr. boot sector. if it is not done directly during installation of the Rom.
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 menu" (Top right corner in the recovery) -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Install a stock rom as secondary
This only works if you are using MultiRom version 33c or larger (excluding 33x-z).
1. Existing primary stock rom
Use these instructions if you plan to move an existing stock rom installed as primary. This guide assumes that multirom recovery is properly installed.
Shutdown the device.
Start the device into multirom recovery (VolDown + Power).
MAKE A BACKUP!
Go to "MultiROM menu" (Top right corner in the recovery) in recovery and tap "Swap roms".
Select the option "Copy primary rom to secondary/internal" and start the operation.
Wait until the operation finishes and flash your desired rom. (Alternatively you can also use any secondary rom to be the primary rom using the "Swap option" mentioned above.
Reboot.
2. Fresh stock installation
Use these instructions if you do not have a stock rom installed as primary. This guide assumes that multirom recovery is properly installed.
Shutdown the device.
Start the device into multirom recovery (VolDown + Power).
MAKE A BACKUP!
Install the stock rom via an install zip of via an FTF. NOTE: For the FTF method you need to shutdown the device and boot into download mode (VolDown pressed while connecting the USB cable; cable connected to the PC). Use for instance flashtool to flash ONLY the kernel, system, and cache image. In addition, you MUST select "Wipe apps_log"!
When the device reboots, let it boot up and finish the first time setup procedure.
Shutdown the device.
Start the device into multirom recovery (VolDown + Power).
Go to "MultiROM menu" (Top right corner in the recovery) in recovery and tap "Swap roms".
Select the option "Copy primary rom to secondary/internal" and start the operation.
Wait until the operation finishes and flash your desired rom. (Alternatively you can also use any secondary rom to be the primary rom using the "Swap option" mentioned above.
Reboot.
CHANGELOG
Code:
=== Version 33d (Bugfix release) ===
- Fix the apps_log issue for good (FINALLY).
- Support for LOS in combination with stock.
=== Version 33c ===
- Sync with XperiaMultiRom repository: cleaner implementation of some patches & extends the rom support w.r.t. old builds.
- Improved compatibility of custom N roms (AOSP init system) with stock roms: Allows to use stock roms as secondary rom.
- Bug fix: Set the version number in the Mrom binaries (for automatic updates).
=== Version 33b ===
- Small maintenance update to support "embedded/combined ramdisks" of secondary roms.
=== Version 33a ===
- Fixed booting Stock after starting secondary N rom.
=== Version 33z ===
- Fixed boot image injection of stock roms.
=== Version 33y ===
- New nokexec version 4 (previous: version 2).
- Support for AOSP 1.3.3 kernels (1.2.2 based kernels are also supported).
- Support for Android N (>= 7.0).
- Support for Sony Z2 stock roms as primary rom (I am investigating the installation as a secondary rom: it's installing, but not yet booting).
=== Version 33x ===
- Update Multirom from version 32 to 33.
- Update Multirom TWRP from version 2.8.7.0 to 3.0.2.
Detailed Xperia-Multirom Changelog
MultiRom
MultiRom Recovery
General Multirom Changelog
To be found here.
SOURCEs
MultiROM - https://github.com/XperiaMultiROM/multirom/ (branch master)
Modified TWRP - https://github.com/XperiaMultiROM/android_bootable_recovery (branch master)
Kernel w/ kexec-hardboot patch - https://github.com/Myself5/android_kernel_sony_msm8974/ (M5-Kernel)
FAQs can be found here.
CREDITs
Tasssadar
Myself5
AdrainDC
Olivier
Garcia98
Thunder07
skin1980
Envious_Data
[NUT]
AndroPlus
Panic Brothers
I do not accept donations. But you may consider donation to Myself5 who did the original port, or to Tassadar who envisioned Multirom and did most of the implementation. We just jumped on the rolling train
Myself5:
Tassadar:
Thanks a lot to those who have donated!
XDA:DevDB Information
MultiROM for Sony Xperia Z2, Tool/Utility for the Sony Xperia Z2
Contributors
Myself5, Diewi
Source Code: https://github.com/XperiaMultiROM/multirom/tree/master
Version Information
Status: Testing
Created 2015-01-13
Last Updated 2018-01-23
DOWNLOAD
I still need to fix touch inside the MultiROM menu, for now you need to use the volume buttons to navigate.
https://diewald-net.com/files/public/MultiRom/sirius
The recovery.img is Tassadars modified TWRP to flash secondary Roms. It is needed to flash the secondary Roms.
Reserved
General Informations about Kexec are coming here soon.
Multi-Rom Random Post
Random Reserve Post
This is some real good progress in the Z2 development. When I'm not using the XDA One app I'll properly check out this thread. Thank you so much for this. I'll throw a donation your way at the end of the month.
EDIT:
Personally I think the installation instructions are a little bit ambiguous. Or is that your aim for this early in development?
Like in step one, I am assuming you need to be on an L ROM running your L kernel?
Is the multiROM TWRP embedded into your kernel?
The multiROM installer is the file multirom-20150113-v30x-UNOFFICIAL-sirius.zip, correct?
When do we need to flash the recovery.img you have provided?
Are the files under the KK/ directory needed yet?
Sorry for all the questions, I'm curious and want to try this but I don't wanna make any errors in the installation.
gamer649 said:
This is some real good progress in the Z2 development. When I'm not using the XDA One app I'll properly check out this thread. Thank you so much for this. I'll throw a donation your way at the end of the month.
EDIT:
Personally I think the installation instructions are a little bit ambiguous. Or is that your aim for this early in development?
Like in step one, I am assuming you need to be on an L ROM running your L kernel?
Is the multiROM TWRP embedded into your kernel?
The multiROM installer is the file multirom-20150113-v30x-UNOFFICIAL-sirius.zip, correct?
When do we need to flash the recovery.img you have provided?
Are the files under the KK/ directory needed yet?
Sorry for all the questions, I'm curious and want to try this but I don't wanna make any errors in the installation.
Click to expand...
Click to collapse
CM12 needs to be the host rom
after that you can install all you want
gamer649 said:
This is some real good progress in the Z2 development. When I'm not using the XDA One app I'll properly check out this thread. Thank you so much for this. I'll throw a donation your way at the end of the month.
EDIT:
Personally I think the installation instructions are a little bit ambiguous. Or is that your aim for this early in development?
Like in step one, I am assuming you need to be on an L ROM running your L kernel?
Is the multiROM TWRP embedded into your kernel?
The multiROM installer is the file multirom-20150113-v30x-UNOFFICIAL-sirius.zip, correct?
When do we need to flash the recovery.img you have provided?
Are the files under the KK/ directory needed yet?
Sorry for all the questions, I'm curious and want to try this but I don't wanna make any errors in the installation.
Click to expand...
Click to collapse
you need to flash the recovery.img to the FotaKernel Partition. ATM my M5-Kernel-V2-L is the only host kernel supported (therefore you need to be on CM12 as the Hostrom), more are yet to come (I work on a KK host kernel already and @AndroPlus Kernel is going to get supported soon too). The KK folder is not needed ATM, you just need M5 Kernel, the recovery.img flashed to FOTAKernel (see Recovery Collection Thread on how to do this) and then just flash the multirom*.zip and you are ready to go.
Hi Myself5, thanks for making multiboot rom for Z2, i always wanted to try something like this but my bootloader is "unlock allowed: no" is there any hope to run this on a locked bootloader / stock kernel or should i just complety forget about multiboot forever ??
Thanks for the work.
ptmaniac said:
Hi Myself5, thanks for making multiboot rom for Z2, i always wanted to try something like this but my bootloader is "unlock allowed: no" is there any hope to run this on a locked bootloader / stock kernel or should i just complety forget about multiboot forever ??
Thanks for the work.
Click to expand...
Click to collapse
MR needs a kexec-hardboot patched Kernel to load any other rom's kernel. However, as you can't flash any modified kernel I guess this is not possible for you. Sorry for that.
Hi and thanks for this beautiful feature. But I have a problem: I am on stock ROM 4.4.2 . Can I install a second ROM with a MultiROM remain on stock?
dalla96 said:
Hi and thanks for this beautiful feature. But I have a problem: I am on stock ROM 4.4.2 . Can I install a second ROM with a MultiROM remain on stock?
Click to expand...
Click to collapse
not yet. You need a MR compatible Host Kernel (it needs kexec-hardboot). Till now only my M5 Kernel for CM has it. Wait some weeks, I'm working with @AndroPlus to get kexec-hardboot going withAndroPlus Kernel
Double Post. Credits @tapatalk ...
Myself5 said:
not yet. You need a MR compatible Host Kernel (it needs kexec-hardboot). Till now only my M5 Kernel for CM has it. Wait some weeks, I'm working with @AndroPlus to get kexec-hardboot going withAndroPlus Kernel
Click to expand...
Click to collapse
OK thanks you very much
Are we Need to mod the ROM for that? Are that only work with Z2 ROMs?
I would test it soon as possible with androkernel.
dkionline said:
Are we Need to mod the ROM for that? Are that only work with Z2 ROMs?
I would test it soon as possible with androkernel.
Click to expand...
Click to collapse
no?
just install supported kernel, mod and the custom recovery.img
Just like all recoverys, otg stick doesn't mount... Please use Nut's recovery TWRP as base, that works ever. Is it normal that I can't touch anything really when the MultiRom Menu comes while booting?
Heyyy came across this and its awesome!!! So currently this mod works only for CM-based? Can I use a cm12 as a main and envi rom as my 2nd rom? D:laugh:
EDIT: Actually I tried flashing envi rom but it couldn't boot. My orginal CM12 rom boots fine though. Maybe I'm missing something. Do I need to flash kernels to the rom?
TheFerhatKing said:
Just like all recoverys, otg stick doesn't mount... Please use Nut's recovery TWRP as base, that works ever. Is it normal that I can't touch anything really when the MultiRom Menu comes while booting?
Click to expand...
Click to collapse
... Both your questions would be answered if you would have red the OP. I use @[NUT]s Device trees for TWRP already don't know why OTG is not working for you. A recovery log would be cool (After attaching the USB use adb to get it by using the command)
Code:
adb pull /tmp/recovery.log
The touch, as clearly written above the download link, is not yet working, I still need to fix this.
earthtk said:
Heyyy so currently this mod works only for CM-based? Can I use a cm12 as a main and envi rom as my 2nd rom?:laugh:
Click to expand...
Click to collapse
No as AndroPlus Kernel now has kexec-hardboot too you can use either stock or CM12/based (I'm working on a CM11 compatible Kernel) as the host Rom and any Z2 Rom you want as secondary Rom this is because secondary Roms need no patching (exept whats done when installing my MR itself) so you can use any Rom you want.
dkionline said:
Are we Need to mod the ROM for that? Are that only work with Z2 ROMs?
I would test it soon as possible with androkernel.
Click to expand...
Click to collapse
as you can read above, you only need to mod the host Rom (the Rom which is actually installed to the place it "belongs to") by installing a kexec-hardboot compatible kernel. And yes, OFC it does only work with Z2 Roms, this Mod is just for booting a Rom from a different place, not to magically make every Rom compatible with the Z2
I had read the whole op but not what was written over the download link sorry . But I didn't found where you said that you used Nuts device trees. I'm gonna do a log for you
TheFerhatKing said:
I had read the whole op but nut what was written ovet the download link sorry . But I didn't found where you said that you used Nuts device trees. I'm gonna do a log for you
Click to expand...
Click to collapse
Yeah, well you couldn't knew this, thats true Just checked again and discovered that I just mentioned him at the credits, not why. Sorry for that Looking forward to the log
Dualboot patcher 101
Device : Galaxy Note 4
Difficulty level : Easy
This is a full guide to understand and use Dualboot Patcher App
Download latest app snapshot from : Noobdev
Files » DualBootPatcherAndroid-9.1.0.r80.gd5920b2-snapshot.apk
Latest as of Jan 8 2017
Install it like a normal apk
Dualbooting begins here ---
Main things to do are
Setup Dualboot boot enviroment
Setup Dualboot files
Flashing
Switch between roms
App sharing
Part 1
Setting up for first time use
-Open dualboot patcher app and do the following
-Go to Roms tab then click the 3 dot menu on "Primary"
-Press Set Kernel {if it didnt ask you at the beginning}
-Then press "Update RamDisk"
Part 2
Patching Files for dualboot
-Download the rom you want to dualboot / any mods for it / xposed or whatever flashableZIP you want to install on your secondary rom
-Go to "Patch Zip File" Press the + and click "Add Flashable Zip"
-Select your ROM Zip
-Select your Device (Trelte For exynos or Trlte For Snapdragon)
-Select "Data slot" in Partition Configuration
-The ID is your parition name , basicly SAME ID for zips = Same flash location, Type rom1 for example [No caps]
-Do the same for any other zips (making sure the ID is the excat same)
Part 3
Flashing
Once you are done patching files , you will end up with a duplicate collection of your original files, but they end with _data-slot-[ID].zip suffix
-Grab those files and go flash them in your recovery
-in the recovery screen you will see [Multiboot] prefix behind most scripts, that means you are flashing a patched zip
-Once you are done flashing just hit reboot from the recovery
Part 4
Switching
You will be greated with your new rom , do the first setup and you are now running your secondary rom
Now, to switch roms do the following
-Install your dualboot patcher app on your secondary rom
-Open it and go to "Roms" Section
-Suprise, you will see Primary and below it [ID] (Data Slot)
-Press the primary and reboot , thats it
Part 5
App Sharing
Lets say you want your app data to be available on all your roms , Whatsapp data , telegram data , game data etc
-Open the app on your primary rom , go to "App Sharing" Section and enable " Share Individual applications"
-Press "manage shared applications"
-Click on an app "whatsapp for example"
-Tick "Use shared data"
-Hit ok then Then go back after selecting all your apps
-It must show a toast saying "The changes will take effect next reboot"
-Reboot your device to the secondary rom and do the same thing for the same apps
App data is now shared across both roms,
F.A.Q please read before attempting this
1- Faild to set kernel due to unrecognized device
-Common issue with custom roms, you can fix it by editing your Buid.prop , changing device name , code etc and ro.patcher
2- Flashing files via recovery , will it affect my primary rom ?
- No , all the files are directed to your new rom enviroment , the only things that can affect dualboot is kernel changes
3- How to change primary / secondary kernel ?
-To change primary , just flash the new kernel , then follow " Part 1 " of the guide again
-To Change Secondary , Follow " Part 2 " of the guide to patch the Kernel zip then flash in recovery
4- Where are the files located ?
-your secondary system can be found under /data/multiboot/data-slot[ID]/System (only seen when you are using primary rom or Recovery file manager)
-Your shared app data can be found under /data/multiboot/_Appsharing
5- Enabling app sharing, my data for the app is gone.
-When you enable app sharing it changes the data location, so whatever data you had need to be moved with it, best thing to do is to backup the app you want to share with titaniumbackup (before enabling shared data for it) then restore it when you enable data sharing and rebooting
6- How many roms can i "dualboot"
-As much as you like aslong as you have storage in your data partition i had 4 roms dualbooted at one point
7- How much storage does it consume ?
-CM roms are usually around 1GB for system + few GBs for data (total of 3GB-4GB For normal user with some apps)
-TW roms are heavier around 2-3GB for system (most bloated AF roms) and same for data
8- My secondary rom broke due to a mod or something, how can i switch roms in recovery ?
-Download dualboot utilites
-Files » Utilities : DualBootUtilities-9.1.0.r80.gd5920b2.zip
-Flash in recovery and it will give you an aroma installer enviroment to select your roms
9- Switch roms without aroma
-In TWRP select flash IMG option instead of zip
-Navigate to /internalmem/Multiboot/[ID]/boot.img
-select flash boot
-swipe to flash then reboot
10- Can i install a rom with aroma installer ?
-Yes , just make sure that the aroma does NOT reboot your device after completion as the dualboot script needs to run after the rom script is done to set the new kernel etc
—---------------------------
Hope this helps whoever wants to use this app , its very simple ,it might look complicated but its easy, GL and have fun
This guide can be used for other devices , Dont forget to hit thanks and reply if it helped.
All thanks for the original devoloper and poster @Anik_khan
First here
Will give it a try ASAP and post my feedback soon
I tried to set it up but i keep getting the error message whenever I click on Set kernel: "Could not determine the boot partition because this device's codename 'hltedalvik.dex2oat-filter=speed' is not recognised". I am using the exynos variant, Dooola v12 rom. Can anyone help me, please?
the\downslash\ said:
I tried to set it up but i keep getting the error message whenever I click on Set kernel: "Could not determine the boot partition because this device's codename 'hltedalvik.dex2oat-filter=speed' is not recognised". I am using the exynos variant, Dooola v12 rom. Can anyone help me, please?
Click to expand...
Click to collapse
If you want to dualboot a TouchWiz ROM, I highly recommend installing TW as the primary ROM. Here is screenshot of my dualboot testing list
webmaster750 said:
If you want to dualboot a TouchWiz ROM, I highly recommend installing TW as the primary ROM. Here is screenshot of my dualboot testing list
Click to expand...
Click to collapse
Very nice configuration, thank you
the\downslash\ said:
I tried to set it up but i keep getting the error message whenever I click on Set kernel: "Could not determine the boot partition because this device's codename 'hltedalvik.dex2oat-filter=speed' is not recognised". I am using the exynos variant, Dooola v12 rom. Can anyone help me, please?
Click to expand...
Click to collapse
F.A.Q number 2 : Common issue with Dooola roms , and DN7 roms due to changes in codename
ro.patcher.device=hltedalvik.vm.dex2oat-filter=speed
This line needs to be fixed in doola build.prop
Changing it to
ro.patcher.device=treltexx Used to work for me But some people reported bootloops , so take a back up first just in case
I have the n910v im running red dragon rom and its showing gracelte and its not compatible ive asked for the correct line for the build.prop and havent gotten an answer as wbat line to change and what to change it to ... can anyone help me?
happy2472 said:
I have the n910v im running red dragon rom and its showing gracelte and its not compatible ive asked for the correct line for the build.prop and havent gotten an answer as wbat line to change and what to change it to ... can anyone help me?
Click to expand...
Click to collapse
QUOTE=clewis.it;70300596]Add this line to the end of /system/build.prop
ro.patcher.device=trlte[/QUOTE
Try that it work for my n910w8.
BluePhnx said:
QUOTE=clewis.it;70300596]Add this line to the end of /system/build.prop
ro.patcher.device=trlte[/QUOTE
Try that it work for my n910w8.
Click to expand...
Click to collapse
ro.patcher.device=trlte ?
BluePhnx said:
QUOTE=clewis.it;70300596]Add this line to the end of /system/build.prop
ro.patcher.device=trlte[/QUOTE
Try that it work for my n910w8.
Click to expand...
Click to collapse
This is what i get
happy2472 said:
This is what i get
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=2447534&page=1099
This is the thread I got my info. Go to page 644.
That is what I used.
ro.patcher.device=trlte
Search for that thread for your model but I think it's the same.
BluePhnx said:
Tthttps://forum.xda-developers.com/showthread.php?t=2447534&page=1099
This is the thread I got my info. Go to page 644.
Click to expand...
Click to collapse
Nope still no good ... let me reboot and see
New
happy2472 said:
New
Click to expand...
Click to collapse
Are you on the latest version?
Wow im usually pretty good at doing this stuff ... is there a more simple set of i structions?
happy2472 said:
Wow im usually pretty good at doing this stuff ... is there a more simple set of i structions?
Click to expand...
Click to collapse
look for ro.product.device= instead of ro.patcher.device=
This worked for me -> ro.product.device=trlte
happy2472 said:
This is what i get
Click to expand...
Click to collapse
Sorry for late response. Your issue is due to your custom Rom changing treltexx names in prop to graceltexx. Usually renaming the changed text to treltexx must work. Use a file editor and search for any grace mention and make sure it says treltexx. Specially the device codename
And update the app It seems old
Sent from my SM-G935F using Tapatalk
Unable to access Roms after a Nandroid Restoration
After doing a nandroid back up in twrp... I restored with my 4 roms with the dualboot patcher....
Only one Rom boots and works the others dont work... whats causing this.... is there anyway to fix this because I have many good data on those roms....plus I would like to feel safe I can do a backup of my roms.
ananjaser1211 said:
F.A.Q number 2 : Common issue with Dooola roms , and DN7 roms due to changes in codename
ro.patcher.device=hltedalvik.vm.dex2oat-filter=speed
This line needs to be fixed in doola build.prop
Changing it to
ro.patcher.device=treltexx Used to work for me But some people reported bootloops , so take a back up first just in case
Click to expand...
Click to collapse
You mentioned making a back up... I have not been sucessfull in making a back up of this app roms... I used twrp and None of the Roms work after restoring the back up.
I got error while flashing zip file from recovery on my device... Seems like it does not support for "trltechn".
Help Please
Thanks a lot