Related
TWRP
6 June 2014 [v2.7.1.0] md5sum: ce3dace05b3994a18d5ef327509edd97
Recovery for flashing in Odin [DOWNLOAD] md5sum: cb3dda4cb604a523c09fe8da7d13e2d8
Source
Credits:
TeamWin
Dees-Troy
CWM
CWM 6.0.5.0 md5sum: 4bfb28bcf29dc04243df246860f24940
Recovery for flashing in Odin CWM 6.0.5.0 md5sum: b5856bd395248af1c74dac8b92cd258e
For Odin: select the ops file, enable one package in options, then load the md5 file with the One Package button[1]
Install Directions:
Download to sdcard
Reboot into existing recovery
Install zip
Reboot recovery
Upgrades
Same as install directions above
Older TWRP Recoveries
17 Mar. 2014 [v2.7.0.0] md5sum: 43d156bfc38476239eeb9728b6130b00
Recovery for flashing in Odin [DOWNLOAD] md5sum: 6d7a708ddf70a8c73f41d66fe79cf883
* Flash pre-kitkat roms
* Use model number, rather than serial number. Rename back-up directory to SGH-T679
Note: v2.6.3.0 will only work with KitKat.
18 Feb. 2014 [DOWNLOAD] md5sum: 4e1625e2021c1ed13d396a3d263252a1
Recovery for flashing in Odin [DOWNLOAD] md5sum: 7fb9d25fe4f1c97136566f2847851cde
* Changes
25 Jan. 2014 md5sum: 2bd3bf72741279b5b3ea7747a977573a
Recovery for flashing in Odin md5sum: 52094a40ecd01512018d613de7ba15ab
* Add usb mount
5 Jan. 2014 [DOWNLOAD]
TWRP 2.6.3.0 md5sum: 2bd0281efe5edb83fa0a42f43f621b2b
* Fixed backwards compatibility, thanks to @meekrawb
* For those that renamed backup folder from serial no. to model no. with 12/27 build will need to rename it back to serial no.
27 Dec. 2013
TWRP 2.6.3.0 md5sum: 931c00589311cd0ffdd8c6a085c82a15
Removed for backwards compatibility
Older CWM Recoveries
CWM 6.0.4.8 md5sum: 6a149c09f7711eb2b3c6c038fa65e012
Recovery for flashing in Odin CWM 6.0.4.8 md5sum: 7dfa121c83a7e5b5d9e198e65829dc04
CWM 6.0.4.7 md5sum: 0d41e83332600f5e9b3ee7eda9f28014
Recovery for flashing in Odin CWM 6.0.4.7 md5sum: be428304f6b11982068edb24b1820d86
CWM 6.0.4.6 md5sum: ad7478be7a07aa86a2d472496a701c9b
CWM 6.0.4.5 md5sum: 576630dac0959cb2d2620a0ab9f2e799
Recovery for flashing in Odin CWM 6.0.4.5 md5sum: 34a2fec6089968e382cf9cfd19737ce4
* For Odin: select the ops file, enable one package in options, then load the md5 file with the One Package button[1]
Does adb work for you? Was working for me with the old TWRP 2.5.1 built by smartguy44 if I remember correctly... but doesn't work with this one. (Didn't try today's update though.)
aaopt said:
Does adb work for you? Was working for me with the old TWRP 2.5.1 built by smartguy44 if I remember correctly... but doesn't work with this one. (Didn't try today's update though.)
Click to expand...
Click to collapse
Just tried it with linux and adb doesn't recognize it. I currently don't have anything for android on windows, so not sure if it's a driver issue or with twrp. I'll try on windows later and get back with you.
edit: Do you think this would work? Reversing the secondary_storage points in ramdisk does not mount sdcard1 in twrp. I have to compile twrp with them bound in the original order for it to mount sdcard1.
jfbs said:
Just tried it with linux and adb doesn't recognize it. I currently don't have anything for android on windows, so not sure if it's a driver issue or with twrp. I'll try on windows later and get back with you.
edit: Do you think this would work? Reversing the secondary_storage points in ramdisk does not mount sdcard1 in twrp. I have to compile twrp with them bound in the original order for it to mount sdcard1.
Click to expand...
Click to collapse
I don't think the mount points are related to my TWRP adb problem. Phone just doesn't show up at all for me in "adb devices" when booted to TWRP. Does it show up there for you?
And don't go to any trouble with Windows on my account -- this laptop runs Ubuntu Saucy 99% of the time, and only boots to Windows on rare occasions.
aaopt said:
I don't think the mount points are related to my TWRP adb problem. Phone just doesn't show up at all for me in "adb devices" when booted to TWRP. Does it show up there for you?
And don't go to any trouble with Windows on my account -- this laptop runs Ubuntu Saucy 99% of the time, and only boots to Windows on rare occasions.
Click to expand...
Click to collapse
No, it doesn't connect for me either. Looking for a solution.
edit: does anything from here stand out to you?
Will this work for the SGH-T759?
How do I get this on my device if so? I've rooted, custom recovery and flashed countless roms on many devices but this one has me stuck. Keep finding what I think is for the t759 but then all this t679 stuff pops up.
Any help would be great! Thank you!
noriyori said:
Will this work for the SGH-T759?
How do I get this on my device if so? I've rooted, custom recovery and flashed countless roms on many devices but this one has me stuck. Keep finding what I think is for the t759 but then all this t679 stuff pops up.
Any help would be great! Thank you!
Click to expand...
Click to collapse
no
jfbs said:
5 Jan. 2014 [DOWNLOAD]
TWRP 2.6.3.0 md5sum: 2bd0281efe5edb83fa0a42f43f621b2b
Fixed backwards compatibility, thanks to @meekrawb
For those that renamed backup folder from serial no. to model no. with 12/27 build will need to rename it back to serial no. Otherwise, there isn't any difference with this build.
27 Dec. 2013
TWRP 2.6.3.0 md5sum: 931c00589311cd0ffdd8c6a085c82a15
Removed for backwards compatibility
Issues:
Restore paths use model no. instead of serail no. for those on 12/27 version. See post #2.
USB Storage Mounting deprecated - looking for a fix
ADB sideload isn't connecting
Click to expand...
Click to collapse
The new TWRP went on, no problem!!! Thanks so much for tweaking it.
Edit: And it works great. Thank you for this update!
how to install?
Can someone please provide exact installation instructions for this?
download file, put on sd card, boot into recovery and then flash like you would a rom
smartguy044 said:
download file, put on sd card, boot into recovery and then flash like you would a rom
Click to expand...
Click to collapse
Thanks for the quick response! The link kept giving me a spam redirect like 20 times...then it finally worked.
Tried the newest build from OP. Mounting usb storage didn't quite work. Plus while trying to install a ROM I got the same mount error mentioned by someone in the CM11 thread. Went back to the 27-Dec build of TWRP (I think-- downloaded it when it was still in the CM11 thread) and the same ROM installed without issues.
aaopt said:
Tried the newest build from OP. Mounting usb storage didn't quite work. Plus while trying to install a ROM I got the same mount error mentioned by someone in the CM11 thread. Went back to the 27-Dec build of TWRP (I think-- downloaded it when it was still in the CM11 thread) and the same ROM installed without issues.
Click to expand...
Click to collapse
Internal and external storage mount on this device in recovery with win 8.1 quickly. Latest twrp installs rom's fine as well on mine.
Edit: Just to be sure, again, I wiped everything in twrp and installed 1/31 without any issues in less than 3 minutes.
jfbs said:
Internal and external storage mount on this device in recovery with win 8.1 quickly. Latest twrp installs rom's fine as well on mine.
Edit: Just to be sure, again, I wiped everything in twrp and installed 1/31 without any issues in less than 3 minutes.
Click to expand...
Click to collapse
I hope you'll forgive me if I don't find "it works for me" to be a convincing argument, based on the /data-and-kernel-related issues in your CM11 thread that affected some people's devices and not others.
But the good news is, now that your CM11 includes a kernel more friendly to the other set of devices, rebuilding TWRP seems to have included that kernel too. In other words, your 2630e build installed the 0220 CM11 build for me without complaining about the /data partition... and the 0220 ROM also booted without complaints. Thanks for keeping at it.
USB mount and adb are still not working for me with Ubuntu 13.10. But I can live without them, though they are nice to have.
Flashable from Stock Recovery
Are the recoveries flashable from Stock Recovery?
does it work
Does it work on SGH-T599N
g7755725 said:
Does it work on SGH-T599N
Click to expand...
Click to collapse
No, this is for the SGH-T679 only
Does anyone have a copy of the TWRP for flashing through odin? The links in this thread don't work.
Hi !
I have a 32 Gb Touchpad on CM10.1 and i'd like to upgrade on CM11 with Milaq ROM.
So, i downloaded The_apes Flashable zip (this one : sys_512mb_data_plus_24576mb-signed.zip) and i flash it with ClockworkMod 5.x. I've got 2 errors like this.
After that, i flashed with the new ClockworkMod 6.x, but, now, when i want to flash ROM, i've got only 0/ and obb/ folders. I can't acces to sdcard/cminstall.
Boot on Android works fine, but, what i have to do to finish my upgrade on CM11 ?
Thanks a lot for your help !
Edit : on ES Explorer you have to activate root access to see /data/media/0
Bristow69 said:
Hi !
I have a 32 Gb Touchpad on CM10.1 and i'd like to upgrade on CM11 with Milaq ROM.
So, i downloaded The_apes Flashable zip (this one : sys_512mb_data_plus_24576mb-signed.zip) and i flash it with ClockworkMod 5.x. I've got 2 errors like this.
After that, i flashed with the new ClockworkMod 6.x, but, now, when i want to flash ROM, i've got only 0/ and obb/ folders. I can't acces to sdcard/cminstall.
Boot on Android works fine, but, what i have to do to finish my upgrade on CM11 ?
Thanks a lot for your help !
Click to expand...
Click to collapse
Welcome to the world of DataMedia.
In CM10.1 use a Root Browser app (e.g. ROM Toolbox lite) or a file manager app with root permissions (e.g. ES File Explorer or X-Plore) to move your CM11 ROM zip to a directory accessible to your new CWM recovery.
Myself I store all my ROM and recovery zips in the Download directory, where Chrome and Firefox also download files to.
e.g.
/storage/sdcard0/Download
/data/media/0/Download
Thanks woodytrain for your quick reply.
I tried to put my ROM /storage/sdcard0/Download but it's the same, i don't see this folder.
In /data, i've no folder
I tried to find obb/ with ES Explorer and it found it on /mnt/, is it normal ?
Last thing, i gone in WebOS in order to use Tailor and found this partition layout, i think it's not ok to flash KitKat :
USB (media) = 25.43 Gib
Android (system) = 408 Mib
Android (cache) = 200 Mib
Android (data) = 1.5 Gib
Unused Space = 8 Mib
I don't knom how to install KK on my touchpad. I don't understand because i don't thing to be a newbie, i flashed i9000 on CM 10.2, Touchpad on CM10.1, but KK made me crazy !
Thanks for your help !
You need to change your partition sizes. At the very least need to increase /system
And if you want to install a DataMedia (DM) ROM, you need to make additional adjustments.
Right now there are three (or four) KitKat (4.4.2) ROM's for the TouchPad (tenderloin) to choose from:
CM11 - 3.0 kernel (Milaq) - DM
CM11 - 3.4 kernel (invisiblek) - DM
Evervolv - AOSP - 3.4 kernel (flintman) - (two version:- one DM and one not)
If you want to install KitKat on your TouchPad will need to do some reading. Keep in mind all these KK 3.x kernel based ROMs are in development (experimental and/or for testing). Each has its own pros and cons, and various TouchPad features are not yet working, features you might have observed working in previous JB 2.6 kernel ROMs.
If you want to stay with JB, until KK is better baked for the TouchPad you may want to try out the new JB 3.x kernel ROM just released from jcscullins (01-25-14). It is NOT a DM ROM, whereas Milaq's CM10.2 (JB) is a DM ROM.
http://forum.xda-developers.com/showthread.php?t=1811480
Suggestions:
1. For each ROM you are interested in thoroughly read the OP. And suggest reading, at the minimum the last five pages of each thread.
2. Then visit [ROM GUIDE] How to Update/Install Android 4.2, 4.3 and 4.4 Builds on the HP TouchPad
http://forum.xda-developers.com/showthread.php?t=2321397
3. Be sure to read the info on how to update your partition for DM support. If you decide to go with a DM ROM, I would suggest using Tailor to change your partitions since you have Tailor installed on your device already.
4. Backup your device before proceeding. Generate a nandroid backup in your recovery as well as back up your app/data with Titanium Backup
5. A "full wipe" in your recovery (factory reset, including clearing caches, formatting /system) is generally recommended when doing major upgrades (not just a nightly flash of the same ROM).
Once you have chosen a ROM to install, and have downloaded the zips for both the matching ROM and Recovery zips (note each ROM has it's own specific recovery version matched to the ROM), then you should be ready to upgrade.
If you have questions before upgrading post your SPECIFIC questions/issues, identifying the ROM version you are coming from and going to.
Thanks woodytrain for your help.
I understood what i missed : root explorer button on Es Explorer
So, now, i can see my files with clockwork Recovery, yes ! I put them in /data/media/0/Download.
After that, i'm gone on Tailor to resize my partitions.
Now, i have :
600 Mb for system
200 Mb for cache
15 Go for media
and ~ 6 Go for data, it's not enough but don't care now...
So, i flashed my rom (Milaq CM11) and gapps (after factory reset, format /system, clear /cache) but now, when i boot on cyanogen, i've cyanogen logo and that's all... only a blank screen, i think i'will made an other post except if you have an idea
Bristow69 said:
So, i flashed my rom (Milaq CM11) and gapps (after factory reset, format /system, clear /cache) but now, when i boot on cyanogen, i've cyanogen logo and that's all... only a blank screen, i think i'will made an other post except if you have an idea
Click to expand...
Click to collapse
Not sure what is meant by "15 Go for media". Recommend you follow the partition instructions as listed in the OP of Milaq's CM11 ROM thread. At any rate...
Before you started the process did you do a nandroid, and backup your apps and data with TiBu or helium?
Then when you did the wipe, did you clear Dalvick cache as well?
And then did you flash the CWM recovery version listed in the OP of Milaq's CM11 ROM thread (CWM 6.0.4.6)? You MUST use that version.
http://milaq.exnet.me/downloads/tenderloin/misc/recovery-clockwork-6.0.4.6-tenderloin.zip
You might want to redo the process and hold off installing gapps until you have booted into CM11. Then go back to recovery and install the gapps listed in the OP. Or install one of the PA-gapps packages.
With a few more posts you receive the right to post to the ROM dev thread. Joy!
I reply only to increase my posts and because i made a big big mistake after this post, i formated all partitions on clockworkmod (6.0.4.6 ). So i will create an other thread on forum...
Mad and Confused
I was duped into updating to 4.4 evervolv when i was on their 4.3.1 rom and im not understanding the layout of my sd-card now. i know all my info is still there but unsure how to reformat so i can use all my space. 32gb touchpad. i will use root explore app to get all my data but can i use onboard storage app to format? Really pissed im in this situation at all. Stupid to be on a 4.3.1 rom and update only to find out it's now a 4.4 rom and my sd-card is different. Thanks much
Nevermind, got it sorted. Good excuse to repartition and reformat everything. Still want nothing from evervolv but there 16mb Gapps package, mwahaha
Welcome to Lollipop
Clean install with custom recovery (TWRP) (recommended)
Download the following files:
aosp_mako-ota-eng.5.0.zip or aosp_mako-ota-eng-preroot.5.0.zip (if you want to have root*) (mirrors, thanks to dorqus)
* In case you have already downloaded aosp_mako-ota-eng.5.0.zip you can also flash aosp_mako-boot-root.5.0.zip to prepare for root
optional: BETA-SuperSU-v2.19.zip
defcon-L-gapps-v2.zip
Recommended: Backup your apps:
Code:
adb backup -apk -obb -all -system
Recommend: Backup your internal storage (see FAQ below for the reason). Either copy all files in Explorer or use adb:
Code:
adb pull /sdcard/
Boot to recovery
Recommend: Factory reset. Warning: All your apps and app data will be deleted! Make sure you have a backup!
Recommend: Format/wipe internal storage (see FAQ below for the reason). Warning: All your files will be deleted! Make sure you have a backup!
Format/wipe system
Unmount system
Install aosp_mako-ota-eng.5.0.zip (or aosp_mako-ota-eng-preroot.5.0.zip)
Install gapps-lp-20141105-signed.zip
Optional: Install BETA-SuperSU-v2.19.zip
Reboot
Have a break and don't panic! The first boot can take 5 to 10 minutes
Optional: Recover from backup:
Code:
adb restore backup.ab
Optional: Copy your files back to internal storage
Clean install with fastboot
You won't have GApps this way ...
WARNING: If you flash userdata.img, all your data will be gone! Even the files on internal storage!
Download the images
boot.img or boot-root.img (prepared for root, you still have to install SuperSU somehow...)
system.img
Optionalrecovery.img
Optional, should be empty: cache.img
Optional, should be empty: userdata.img
Boot to bootloader
Flash
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash system system.img
FAQ
Oh no, all my files are lost!!!
or
Why should I wipe internal storage?
5.0 uses a much stricter SELinux policy than most 4.4 ROMs do. Normally the first boot should migrate all the things (and it did for me, but only the first time). If not, you are no longer able to see your internal storage (aka SD card). E.g. Camera says: Please enter an SD card. To fix that problem you have to either wipe the internal storage and let Android recreate the file structure. (You can before still access the /sdcard in TWRP for a backup with adb). Or you can fix the SELinux context with the following command (in recovery):
Code:
adb shell
IFS="
"
for i in `find /data/media`; do chcon u:object_r:media_rw_data_file:s0 "$i"; done
Is this the official update from Google?
No, this is an AOSP build from the latest Lollipop sources.
Do I need to be on stock 4.4.4 before flashing?
No, but you should consider doing a factory reset otherwise.
Can I do a dirty upgrade?
Yes, you can. But you might spend a lot of time in fixing F/Cs...
Can this ROM be rooted?
Yes, just flash aosp_mako-ota-eng-preroot.5.0.zip (or aosp_mako-boot-root.5.0.zip) and BETA-SuperSU-v2.19.zip
Known issues
General:
No access to internal storage, even not with adb or as root. Seems like SELinux is misconfigured. See FAQ for solution
Due to incomplete GApps:
WLAN/mobile based location isn't working
No face unlock (libs missing) works with new gapps
calendar sync provider missing works with new gapps
How to build
This ROM is build with the original Google sources:
Code:
repo init -u https://android.googlesource.com/platform/manifest -b android-5.0.0_r2
See https://source.android.com/source/building.html for build instructions.
Binary blobs are taken from https://developers.google.com/android/nexus/blobs-preview.
The kernel is the default precompiled kernel provided by Google (can be found in device/lge/mako-kernel/kernel).
To prepare for root, you have to remove the seclabel line from system/core/rootdir/init.rc:
Code:
service flash_recovery /system/bin/install-recovery.sh
class main
seclabel u:r:install_recovery:s0
oneshot
C-o-M said:
Welcome to Lollipop
Download: https://drive.google.com/file/d/0B10l7w-7w3boRzlmT1pxSFF5YlU/view?usp=sharing
We don't have 5.0 gapps yet, so I flashed pa-gapps-modular-mini-4.4.4-20140930 (after removing the version check in updater-script). Works great so far.
I'm running a dirty upgrade from 4.4.4, no issues so far. Just format /system, flash ota.zip and gapps, wipe cache and enjoy.
Click to expand...
Click to collapse
I guess this requires me to be running stock 4.4.4 before flashing.
Could you post the system.img , userdata.img , cache.img , boot.img and recovery.img so I could flash it via fastboot.
Thanks
Amazing work!!
can you upload modified pa gapps??
or any instruction to modify it?
Good job!
trasteando...
is this from google ?
richardyusan said:
is this from google ?
Click to expand...
Click to collapse
all ROM's are from Google's base dude
maybe what you really mean is from stock L image?
is this rooted guys?
Is this official aosp build and can I clean flash?
Please explain how to root tris ROM?!
C-o-M said:
Welcome to Lollipop
Download: https://drive.google.com/file/d/0B10l7w-7w3boRzlmT1pxSFF5YlU/view?usp=sharing
We don't have 5.0 gapps yet, so I flashed pa-gapps-modular-mini-4.4.4-20140930 (after removing the version check in updater-script). Works great so far.
I'm running a dirty upgrade from 4.4.4, no issues so far. Just format /system, flash ota.zip and gapps, wipe cache and enjoy.
Click to expand...
Click to collapse
dirty flash from stock 4.4.4 ?
also can you provide a link to working gapps
great job , waiting issues from other
groovepeppy said:
all ROM's are from Google's base dude
maybe what you really mean is from stock L image?
Click to expand...
Click to collapse
lol you don't say
we know every android build is from google
is this official from google or not?
richardyusan said:
lol you don't say
we know every android build is from google
is this official from google or not?
Click to expand...
Click to collapse
It's in the topic dude.
AOSP not OTA
Bladyle said:
It's in the topic dude.
AOSP not OTA
Click to expand...
Click to collapse
What he means is this proper aosp fully working 100% and has latest kernel and everything?
SRun said:
What he means is this proper aosp fully working 100% and has latest kernel and everything?
Click to expand...
Click to collapse
it will be 100% working when we have OTA or after some time with AOSP when developers fix all the missing binaries, libraries, bugs and etc.
SRun said:
What he means is this proper aosp fully working 100% and has latest kernel and everything?
Click to expand...
Click to collapse
i think we should install the rom and experience
Bugs? Root? Smooth? Please post bugs and stuff
I'm returning to stock 4.4.4 as I type this, and then I will do a clean flash of this 5.0 AOSP build and see how I go. Shall report back here upon completion.
richardyusan said:
lol you don't say
we know every android build is from google
is this official from google or not?
Click to expand...
Click to collapse
understood "sam"
that's why i wrote "maybe what you really mean is from stock L image?"
how to i disable the version check to install gapps?
anyway to get the official launcher? the one in this rom looks like 4.4 stock
i didn't find any p880' examples, for Anykernel2.
?Does zip' anykernel.sh -included, will work with:
block=/dev/block/platform/sdhci-tegra.3/by-name/LNX;
thanks for help?
btw: Since multirom kexec64 came out, do you believe lg G5 (removable battery & sdcard) is the "unknown heir" of 4X HD?
bloomed in the moonlight
EXPERIMENTAL!
Attached is an ak2 unofficial version of Nameless2' kexeced kernel from @laufersteppenwolf (~cm12' tree):
(prim-origin https://github.com/NamelessRom/android_kernel_lge_p880/tree/n-2.1 )
Included is Pingpong' cve2015-3636 patch and original bootanimation.
It can be flash, on primary rom, over @csk1jw aosp5.1.1 with Fritzcola' twrp 2.8.6.
Once done you can try multiboot with other compatible roms.
PROCEED WITH CAUTION and follow:
1) install aosp5.1.1 and boot it once;
2) without rebooting under multiromV32' recovery :
-full backup aosp5.1.1
-+ install ak2.zip
-+ perform advanced/fix permissions
-+ install multirom-20150521-v32-UNOFFICIAL-p880.zip
3) reboot
If you loose multirom (can happen if you flash a new 2nd rom or other ...), re-fix permissions and re-flash multirom v32.
Since Nameless' ko are flashed to system; if you want backward to aosp5.1.1, you need to restore full backup.
Don't complain, but light a post if you believe it's can be harmfull.
Thanks for any suggestion (and vote to poll).
How can i anykernel a kernel from CM13 stock blobs?
I compiled it and now i want to anykernel it...
InterrtuptoR said:
How can i anykernel a kernel from CM13 stock blobs?
I compiled it and now i want to anykernel it...
Click to expand...
Click to collapse
Anykernel reproduces this holy thread : http://forum.xda-developers.com/showthread.php?t=2319018
Be sure, in your zip, to follow p880' specifics mounts updater-script (/META-INF/com/google/android/) and check mkbootimg.sh (/kernel/) for exact line_action=boot_info. Don't forget the modules (/system/lib/modules/) ...
Anykernel2.zip will give you full (very complicated & very advanced fake update-binary) tricks for "live" repack with a big /anykernel.sh, in case of incompatibility with alfsamsung' cm13 (fastboot boosted kernel<->ROM (?)).
Introduction
Hello everyone! In the past few days, I was approached by a few people wanting to know the steps I take to successfully flash a ROM as a secondary ROM in MultiROM. Since there seems to be many people interested in trying out new ROMs while still keeping their daily-driver primary ROM untouched, I decided to make this thread for those interested. The following is a tutorial to modify a TWRP flashable ROM zip to make it compatible with MultiROM and then flashing it as a secondary ROM. Let's get straight to it then!
Compatibility
Device(s)
OnePlus 5
ROM(s)
Mostly All ROMs (in theory, at least, hence mostly)
Android Version(s)
Android Nougat 7.x.x
Android Oreo 8.x.x
Prerequisites
Basic knowledge about TWRP flashing, fastboot flashing, zip editing, MultiROM usage, etc.
A working fastboot interface on your computer
Zip-editor installed on your computer (I prefer Bandizip)
Unlocked bootloader (how-to guide here)
Unencrypted/decrypted system (how-to guide here)
Steps To Follow
Step 1: Create a new folder on desktop (or wherever you prefer) and download the following stuff in it:
The flashable ROM zip that you wish to modify to use a secondary ROM in MultiROM
update-binary.zip (attached at the end of this post)
The latest MultiROM recovery and MultiROM zip (available here)
An updated copy of the latest SuperSU (available here)
Step 2: Extract the update-binary.zip file after which you will get the modified update-binary file that we have to use
Step 3: Open the downloaded ROM zip in the zip program that you use and inside it, navigate to META-INF\com\google\android
Step 4: Delete the existing update-binary that you see there and replace it with the update-binary that you extracted in step 2
Step 5: Save the modified zip (this is now the modified ROM zip that can be flashed as a secondary ROM via MultiROM)
Step 6: Copy the modified ROM zip, the SuperSU zip and the MultiROM zip that you downloaded in step 1 to your phone's internal storage
Step 7: Reboot your phone to the bootloader mode and connect it to your computer
Step 8: Open command prompt and navigate to the folder where you've downloaded the MultiROM TWRP image file
Step 8: Run the following command to flash MultiROM TWRP to your phone's recovery partition:
Code:
fastboot flash recovery TWRP_multirom_cheeseburger_20170919-03.img
Step 10: Once the flashing is successful, reboot to the bootloader mode again using the command:
Code:
fastboot reboot-bootloader
Step 11: Press the volume down button until you see "Recovery mode" on your phone's screen and then press the power button to boot to recovery
Step 12: Once you're in the recovery mode (running MultiROM TWRP), flash the MultiROM zip first and then reboot your phone to recovery
Step 13: Once the phone has rebooted to the recovery mode, open the MultiROM menu (three parallel horizontal lines on the top right of your phone's screen) and click on the "Add ROM" option
Step 14: Select the modified ROM zip and flash it (choose the "internal memory" option if it prompts for a partition to flash the secondary ROM in)
Step 15: Once done, hit back to open the MultiROM menu, then click on the "List ROMs" option and select the ROM that you just installed
Step 16: Once you select the ROM that you just installed, select the "Install Zip" option and flash the SuperSU zip
Step 17: Once the SuperSU zip is flashed, reboot your phone to system and you will notice a new selection menu is now displayed before the phone boots into the system
Step 18: Select the new ROM that you just flashed as the secondary ROM to boot to it
Step 19: The phone will bootloop a couple of times - DON'T WORRY, THIS IS NORMAL AFTER FLASHING SUPERSU - and in between the reboots if you see the ROM selection menu appear again, just select the newly flashed ROM and let it continue
Step 20: It should boot into your secondary ROM after a couple of bootloops/reboots!
Disclaimers
You are doing this at your own risk. I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you are unsure of how to go about something. Also, please don't forget to make a full nandroid backup via TWRP in case anything goes wrong.
The above method works for me 99% of the time, but there are a few ROMs that I wasn't able to boot as secondary no matter what I tried. If a ROM doesn't boot as secondary for you using the tutorial above, I'll try my best to help you, but I may or may not succeed.
I haven't tried the above method with Magisk instead of SuperSU. If you wish to try, feel free to do so at your own risk.
Flashing of the secondary ROM will most probably corrupt your primary ROM's password/pin (if you have one setup). If you can't get into your primary ROM after flashing the secondary ROM using your password/pin, flash this zip in TWRP which will remove your lockscreen security settings (but won't touch your fingerprints, if you have any setup).
Thanks To
@martinusbe for adapting MultiROM (recovery, installer zip, manager application, uninstallation zip) to OnePlus 5
@Chainfire for SUperSU and all the work he's ever done for the community
All of you guys for viewing this thread
Changelog
December 26, 2017 - Initial post
OP Update Information
Created: December 26, 2017
Last Updated: December 26, 2017
@shadowstep This will be very useful to many people. Merry Christmas to you
SlyUK said:
@shadowstep This will be very useful to many people. Merry Christmas to you
Click to expand...
Click to collapse
Thanks! I hope so too. Merry Christmas to you too!
P.S. - I tried the above method with Liquid Remix 8.0 and Dirty Unicorns 12.0, worked fine for me.
shadowstep said:
Thanks! I hope so too. Merry Christmas to you too!
P.S. - I tried the above method with Liquid Remix 8.0 and Dirty Unicorns 12.0, worked fine for me.
Click to expand...
Click to collapse
Nice... speaking of Dirty Unicorns. Here is an update today.
SlyUK said:
Nice... speaking of Dirty Unicorns. Here is an update today.
Click to expand...
Click to collapse
Yes, I follow them on Google+. Read the announcement sometime back. I compile my personal, unofficials builds of DU 12, so have already gotten a sneak peek.
shadowstep said:
Yes, I follow them on Google+. Read the announcement sometime back. I compile my personal, unofficials builds of DU 12, so have already gotten a sneak peek.
Click to expand...
Click to collapse
Oh well thats fantastic. DU Oreo should be amazing once unleashed, i'm sure.
Thanks, but can I have official Oreo in primary rom and an other rom in secondary?
Garfanki said:
Thanks, but can I have official Oreo in primary rom and an other rom in secondary?
Click to expand...
Click to collapse
Should work, yes. I tested the steps with a Nougat primary ROM and an Oreo secondary ROM; worked fine. So the setup you're looking for should also work. Give it a shot!
Ok thanks, I will try!
shadowstep said:
Should work, yes. I tested the steps with a Nougat primary ROM and an Oreo secondary ROM; worked fine. So the setup you're looking for should also work. Give it a shot!
Click to expand...
Click to collapse
can i use magisk instead of supersu ?
kimikim0 said:
can i use magisk instead of supersu ?
Click to expand...
Click to collapse
Already mentioned this in the OP (Point 3 under Disclaimers). I haven't tested the method with Magisk in place of SuperSU.
This is because when I was initially trying to figure all this out, most of the stuff that I was going through pointed out that Magisk wasn't doing too well with the secondary ROM and hence I just chose SuperSU; didn't even bother testing Magisk when SuperSU worked fine.
If you wish to test, go for it. Should do no harm.
kimikim0 said:
can i use magisk instead of supersu ?
Click to expand...
Click to collapse
iirc magisk scripts won't run on secondary rom installation ( twrp multirom or dual boot patcher ) will give you errors and nothing will happen
Sent from my OnePlus 5 using XDA Labs
primary system can't boot when i flash multirom zip file into oos oreo as primary,and for other 8.0 roms as primary,secondary 8.0 roms boot with primary system,same like dual boot patcher,only work with gzosp based 8.0 roms as secondary
billsz said:
primary system can't boot when i flash multirom zip file into oos oreo as primary,and for other 8.0 roms as primary,secondary 8.0 roms boot with primary system,same like dual boot patcher,only work with gzosp based 8.0 roms as secondary
Click to expand...
Click to collapse
I haven't tested the method with OOS 5.0 Oreo as my primary ROM. When I last tested, I was running a custom Nougat based ROM (AOSiP) and with that I tested multiple Oreo based custom ROMs (after modifying them, of course, as mentioned in the tutorial) as secondary ROMs and they all worked fine. Not to mention, of course, that if you don't modify the ROM zip files with the updater-binary file I attached in the OP, then it just won't work.
I would like to have os stable Oreo as primary ROM and other Oreo build as secondary ROM, but the installation of secondary rom fails... Why? Is not possibile have 2 ROMS with Oreo?
Any help?
Garfanki said:
Any help?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=74636311&postcount=702
Actually, after Oos Oreo 8.0 upgrade, primary via MultiROM.zip won't boot anymore; there were 2 evolutions since OP5 'old' multirom:
1-Magisk support for 2nd roms
2-Encryption support for 2nd roms WITH rebranded data/media/0/multirom directories
I tried rebuilding both : 1) doesn't boot (like 'old'), and 2) boots primary via latest Multirom, BUT 2nd always reboot to recovery, despite working installation files (Magisk/sparse img or not) and decrypted device.
Also, OP5 adbd never worked for MultiROM neither log. So waiting for a skilled (new un-/encryption Oreo status) dev to follow AdrianDC sd820 latest MultiROM : https://github.com/XperiaMultiROM/android_device_sony_dora/tree/master/multirom , considering that there is no working MultiROM for any sd835 yet...
(Kexec-ed kernel would even be better...)
Most powerful is EFIdroid due to our new bootloader edk2, but here: dev/bricks are unrecoverable...
The 'funky' thing is that I got intermediate 1) working 100%, for antic p880 device with Magisk/sparseImg support ok for 2nd roms.
Thank you, so I must wait... Happy New Year!
oF2pks said:
https://forum.xda-developers.com/showpost.php?p=74636311&postcount=702
Actually, after Oos Oreo 8.0 upgrade, primary via MultiROM.zip won't boot anymore; there were 2 evolutions since OP5 'old' multirom:
1-Magisk support for 2nd roms
2-Encryption support for 2nd roms WITH rebranded data/media/0/multirom directories
I tried rebuilding both : 1) doesn't boot (like 'old'), and 2) boots primary via latest Multirom, BUT 2nd always reboot to recovery, despite working installation files (Magisk/sparse img or not) and decrypted device.
Also, OP5 adbd never worked for MultiROM neither log. So waiting for a skilled (new un-/encryption Oreo status) dev to follow AdrianDC sd820 latest MultiROM : https://github.com/XperiaMultiROM/android_device_sony_dora/tree/master/multirom , considering that there is no working MultiROM for any sd835 yet...
(Kexec-ed kernel would even be better...)
Most powerful is EFIdroid due to our new bootloader edk2, but here: dev/bricks are unrecoverable...
The 'funky' thing is that I got intermediate 1) working 100%, for antic p880 device with Magisk/sparseImg support ok for 2nd roms.
Click to expand...
Click to collapse
Good evening, I try to flash flyme rom (downloaded by chinese forum) as secondary rom but the installation fail... Any idea?
Error 7
Can I flash xXx rom as secondary? or does it only work with lineage os based roms?