Develop Bugs

[BOOT][4.2+][UNOFFICIAL] MultiROM for TF300T [2014-02-13]

MultiROM lets you install multiple ROMs into subfolders, just by flashing them using a modified TWRP.
This is an unofficial port of MultiROM originally developed for the Nexus series to our beloved TF300T.
Big thanks @Tasssadar for the original work!
THIS IS AN EARLY VERSION OF THIS PORT, NOT ALL FEATURES ARE FULLY TESTED.
But please test and give feedback, so I can eventually remove above line.
Features
Run a primary Android ROM from the normal partitions.
Run multiple secondary ROMs from subfolders on an SD card or on an external USB stick/drive.
Easily add/update your primary and secondary ROMs using a modified version of TWRP.
Install Ubuntu and Ubuntu Touch as secondary ROMs Not supported yet.
And more...
Changes vs. official MultiROM
This section is mostly useful for people using MultiROM on another device. New users can safely ignore it.
My first test - installing a plain CM 11, installing MultiROM, and then installing OmniROM with its own kernel - failed gloriously. The reason was that the official MultiROM re-uses the kernel of the currently installed Android system and that kernel does not include the kexec hardboot patch required for MultiROM to work properly.
The beauty of MultiROM is that - once installed with a proper kernel - it allows an average user that has never heard about kexec and never installed a custom kernel to run multi-boot at the touch of a finger. So I decided that my first simple use case must be supported.
The obvious solution was to ship a working kernel with MultiROM, save the currenly installed kernel for the primary ROM and boot that via kexec. The idea is to sacrifice another 10 secs on booting the primary ROM for making MultiROM much easier to install and to use. However, this decision led to several changes in the TWRP user interface:
The "share kernel with primary ROM" option was removed. Each ROM has its own boot image and is always booted via kexec.
The "Inject current boot sector" on the MultiROM screen button was replaced with a "Reinstall" button. Use this, if you have overwritten the boot sector, for example via fastboot. Mind, reinstalling MultiROM will save the current boot partition and use it for booting straight into the primary ROM, so better make sure this works, before running reinstall, or you won't be able to boot into your primary ROM after reinstallation.
The "Add/Remove boot.img" button on the ROM management screen has been replaced with "Replace boot.img" and can be used to easily install a custom kernel for that ROM.
Looking forward to your feedback on this major change!
Downloads
Downloads are available from the "Downloads" tab at the top of the page.
MultiROM installer including the modified TWRP:
multirom-vXX-YYYYMMDD-UNOFFICIAL-tf300t.zip
TWRP for MultiROM (not needed, if you use the installer):
twrp-multirom-vXX-YYYYMMDD-UNOFFICIAL-tf300t.blob
Installing and Upgrading MultiROM
Please read the following instructions carefully, and make sure you understand each step and what it will do to your tablet. The steps are working for me, but you are ultimately responsible, for what you are doing with your own tablet. I will not be responsible, if you brick your tablet, or if your wife gets angry at you for being too preoccupied with your tablet.
Make a backup!
MultiROM will modify your system, and if anything goes wrong, this backup will be more than helpful.
Check the version of your bootloader.
On the bootloader screen, check the version shown on the top left. MultiROM was ported and tested on version 10.6.1.27.5. If your bootloader version is 10.6.1.27.1 or 10.6.1.15.3 you should have no issues. Version 10.6.1.8 might work, but is likely to cause issues; upgrading is highly suggested. For any other version, make sure you first upgrade your bootloader, or you risk ending up with a brick,
Flash the lastest multirom-vXX-YYYYYYYY-UNOFFICIAL-tf300t.zip
Reboot right away!
Make sure you see the blue progressbar on the first boot screen and you see another automatic reboot.
Then the MultiROM boot screen should show up.
Now you should be able to boot your primary ROM via MultiROM. For next steps, check out "Installing ROMs" in the next post.
Uninstall MultiROM
The uninstaller for the official MultiROM has not been ported yet, but you can get rid of MultiROM following these steps:
Flash your favourite (not MultiROM) recovery.
Restore your boot partition from a backup or re-flash your ROM.
Remove the "multirom" folder on the sdcard.
The latter is optional. You may keep it around for trying MultiROM again later.
Changes
2014-03-16:
Fixed MultiROM reinstallation from TWRP.
Some fixes for swapping primary/secondary ROMs.
Some fixes for primary ROM initrd.
Added support for Ubuntu Touch (needs upcoming manager app).
2014-03-02:
Support secondary ROMs on SD card (not fully tested).
Use packaged initrd instead of the primary ROM's.
Some bug fixes.
2014-02-13:
Allows flashing 4.2-based ROMs without removing the assert line in the updater-script.
Several bug fixes for more stability.
Note that changes may be documented, before the downloads are available. Please check back a little later in that case.
Future Work
In no particular order:
Provide uninstaller.
Add the missing features listed above.
Fix TWRP for encrypted filesystems.
Allow replacing the kernel for any ROM, keeping the ramdisk.
Remove unnecessary drivers (net, sound, camera) from the kernel (currently breaks building the kernel).
XDA:DevDB Information
MultiROM for TF300T, a Tool/Utility for the Asus Transformer TF300T
Contributors
f69m
Version Information
Status: Alpha
Created 2014-02-11
Last Updated 2014-03-16

Installing ROMs
Custom 4.2- and 4.4-based ROMs
To install/update your primary ROM, just flash it as usual with the modified MultiROM TWRP, using "Install" from the main screen.
Installing a secondary ROM is just as easy, but use:
Advanced > MultiROM > Add ROM
You can update a secondary ROM by flashing it from the ROM management screen, using;
Advanced > MultiROM > List ROMs > [select your ROM] > Flash ZIP
OTA updates using the update manager coming with your ROM should work fine for both primary and secondary ROMs.
Note: It is no longer necessary to remove the assertion from a 4.2 updater-script.
Gaps, SuperSU, etc.
You can flash additional ZIP files for a secondary ROM from the ROM management screen, using:
Advanced > MultiROM > List ROMs > [select your ROM] > Flash ZIP
Asus Stock ROM
Asus stock ROM has a different installer and won't work the same way as custom ROMs.
Here are the steps to install stock ROM as your primary ROM:
Sorry, I have not tested this myself yet, please let me know, how it works out.
Unzip the Asus ROM twice to get the blob.
Flash the blob using fastboot.
Boot into stock ROM.
Re-install the modified TWRP using fastboot (use the separate download).
In TWRP: Advanced > MultiROM > Reinstall.
This should give you a working MultiROM setup with stock ROM as your primary ROM.
If you need more detailed instructions on the first two steps, please refer to the guides in the General section.
Ubuntu Touch
Coming soon...
Ubuntu
Not working yet.
Notes on Specific ROMs
CROMi-X 5.3
Don't try to install CROMi-X as a secondary ROM. It has an amazing installer, but that will nuke your primary ROM's /system partition.
Trouble-shooting
If your primary or one of your secondary ROMs is not booting properly, it can help to restore the boot partition of the primary ROM and then do a clean reinstall of MultiROM.
No worries, you can move your installed secondary ROMs to the side and move them back later.
First try restoring the boot partition from your latest backup, before installing MultiROM and reboot.
If your device boots cleanly into your primary ROM, without showing the MultiROM boot screen, you can skip ahad to step 3.
Next try flashing an unmodified recovery, re-flash your primary ROM and reboot.
If your device boots cleanly into your primary ROM without showing the MultiROM boot screen, you are ready to go to step 3.
Otherwise you should post your issue.
Use a root terminal or a root exlorer to remove the folder /data/media/0/multirom.
Alternatively you can rename that folder, keeping your installed ROMs.
Note: though this folder is on the sdcard, you have to use the path given; trying to use /sdcard or /storage you will get "permission denied", when trying to remove or rename the folder.
Reflash the latest multirom-v*.zip and reboot.
Make sure you see the blue progressbar on the first boot screen and you see another automatic reboot.
Then the MultiROM boot screen should show up.
Try booting your primary ROM. It should now start cleanly.
Try installing a secondary ROM, or move it back to /data/media/0/multirom/roms/ from the folder you renamed above.
Just moving back the folder will make it show up on the MultiROM boot screen.
Please read and follow each step carefully.
If these steps do not make all your ROMs boot properly, please post about your issue in this thread.

Source Code Repositories
The easiest way to build MultiROM is using my manifest following the build instructions below.
Here is a list of the MultiROM-specific repositories that can be built by adding them to the OmniROM tree:
Latest manifest:
https://github.com/f69m/android
MultiROM (check out to "bootable/multirom"):
https://github.com/f69m/multirom
TWRP for MultiROM (check out to "bootable/recovery"):
https://github.com/f69m/multirom-twrp
libbootimg (check out to "external/libbootimg"):
https://github.com/Tasssadar/libbootimg
TF300T device config (check out to "device/asus/tf300t"):
https://github.com/f69m/android_device_asus_tf300t
TF300T kernel (check out to "kernel/asus/tf300t"):
https://github.com/f69m/android_kernel_asus_tf300t
Look out for branches named "multirom-*" in above repositories.
Please check the manifest for the latest stable branch.
Build Instructions
Using my manifest makes it easy to check out the MultiROM repositories and a small part of the OmniROM tree needed for building.
Code:
repo init -u git://github.com/f69m/android -b multirom
repo sync
manifest/pick-cherries.sh
source build/envsetup.sh
lunch mrom_tf300t-userdebug
make -j4 multirom_zip

Sweet! Thanks man, this looks pretty cool!
Sent from my SGH-T999 using xda app-developers app

Finally, first download is up!
Let me know, how it works for you.

Thanks for your work.
Now I use CROMi-X 5.3 ROM. If I install MultiROM and TWRP for MultiROM, the exist CROMi-X 5.3 ROM can keep on primary ROM??

z1022 said:
Now I use CROMi-X 5.3 ROM. If I install MultiROM and TWRP for MultiROM, the exist CROMi-X 5.3 ROM can keep on primary ROM??
Click to expand...
Click to collapse
Absolutely, just flash the multirom-*.zip file (includes TWRP), and you should be able to boot into CROMi-X via MultiROM.
But I have not tested with CROMi-X yet, so make sure you have a backup!
Sent from my TF300T using Tapatalk

Thanks
I will try later and report back.
CROMi kernel should be not included the kexec. Can I use the Multirom to install second ROM ??

z1022 said:
I will try later and report back.
Click to expand...
Click to collapse
Great, looking forward to hearing about your experiences.
CROMi kernel should be not included the kexec.
Click to expand...
Click to collapse
The CROMi-X kernel does not need kexec for my MultiROM port to work. This is different from the official MultiROM for Nexus. See post #1 on more details.
Can I use the Multirom to install second ROM ??
Click to expand...
Click to collapse
Of course, that's the whole idea!
Check post #2 for instructions.
Sent from my TF300T using Tapatalk

Hi f69m!
1000 THANKS!
I successfully installed this MultiROM on TF201 with bootloader from TF300T v. 10.6.1.27.1 ! :laugh:
As Primary ROM i have NIGHTLY CM11 for TF300T. As "virtual" ROM i installed the same ROM (i want to examine the new GRIMKERN_KitKat).
All works properly with 1 exception:
Don't works the touchscreen during "blue" window for ROM-selection.
So I had to specify the "default" firmware in TWRP.

Dasdranamin said:
Hi f69m!
1000 THANKS!
I successfully installed this MultiROM on TF201 with bootloader from TF300T v. 10.6.1.27.1 ! :laugh:
Click to expand...
Click to collapse
Wow, amazing!
All works properly with 1 exception:
Don't works the touchscreen during "blue" window for ROM-selection.
So I had to specify the "default" firmware in TWRP.
Click to expand...
Click to collapse
Hmm, not quite sure, what you mean with "blue" window. You mean the MultiROM menu that comes up after boot? If yes, could you send me a copy of /proc/last_kmsg after booting your ROM? It has the kernel log of MultiROM; maybe I can spot the issue there.
Sent from my TF300T using Tapatalk

f69m said:
Wow, amazing!
Hmm, not quite sure, what you mean with "blue" window. You mean the MultiROM menu that comes up after boot? If yes, could you send me a copy of /proc/last_kmsg after booting your ROM? It has the kernel log of MultiROM; maybe I can spot the issue there.
Click to expand...
Click to collapse
Yes. That's what I meant.

Dasdranamin said:
Yes. That's what I meant.
Click to expand...
Click to collapse
Thanks for the log. It is a different touchscreen, but don't see anything that should cause issues.
In TWRP touch is working fine?
I'll have a look at the differences in the input handers and will probably send you a special version with more logging.
Sent from my TF300T using Tapatalk

f69m said:
Thanks for the log. It is a different touchscreen, but don't see anything that should cause issues.
In TWRP touch is working fine?
Click to expand...
Click to collapse
Yes, in TWRP touch works without any problem!
I'll have a look at the differences in the input handers and will probably send you a special version with more logging.
Click to expand...
Click to collapse
That would be great! Thanks in advance!

f69m said:
Great, looking forward to hearing about your experiences.
The CROMi-X kernel does not need kexec for my MultiROM port to work. This is different from the official MultiROM for Nexus. See post #1 on more details.
Of course, that's the whole idea!
Check post #2 for instructions.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
Install MultiROM and try to install Omni 4.4.2. ROM in second. However, stick in OMNI booting Screen.

z1022 said:
Install MultiROM and try to install Omni 4.4.2. ROM in second. However, stick in OMNI booting Screen.
Click to expand...
Click to collapse
I successfully installed just now on TF201 Omni 4.4.2. ROM TF300T Homebuild versions [20140126] (it's last ROM with MultiWindow feature) + Gapps Mini Modular Package.
All works properly. :good: MultiWindow too.

how long omni finished the booting.
---------- Post added at 11:59 PM ---------- Previous post was at 11:50 PM ----------
z1022 said:
Install MultiROM and try to install Omni 4.4.2. ROM in second. However, stick in OMNI booting Screen.
Click to expand...
Click to collapse
Try CM11 in second ROM. still stick in CM11 booting screen.

z1022 said:
how long omni finished the booting.
Click to expand...
Click to collapse
First time about 5 min (with Gapps).
Next times about 2 min.

Nice! cant wait to try this, thanks for your hard work!

Hi f69m,
I found: in "MultiROM menu that comes up after boot" I can select a ROM by VOLUME UP/DOWN and confirm by POWER (like in "old" CWM). :laugh:

[Q] Switch parition

Hello, i have managed to root my Find 7 x9076 on Cos 2.0.4i b and will be following Recovery Flasher for flashing recovery. My question here is:
1. on 2.0.4ib it gives option for Switch Partition (to merge some partition to get more space) but is it called LVM or Unified?
2. Once i have flashed TWRP or any other recovery and after having used Switch Partition, will i be able to flash any custom rom for find 7 or does it have to be only Unified rom?
will appreciate the help i can get.

treacherous_hawk said:
Hello, i have managed to root my Find 7 x9076 on Cos 2.0.4i b and will be following Recovery Flasher for flashing recovery. My question here is:
1. on 2.0.4ib it gives option for Switch Partition (to merge some partition to get more space) but is it called LVM or Unified?
2. Once i have flashed TWRP or any other recovery and after having used Switch Partition, will i be able to flash any custom rom for find 7 or does it have to be only Unified rom?
will appreciate the help i can get.
Click to expand...
Click to collapse
LVM.
More info at http://www.oppoforums.com/threads/reference-lvm-storage-user-guide.23440/

Entropy512 said:
LVM.
More info at http://www.oppoforums.com/threads/reference-lvm-storage-user-guide.23440/
Click to expand...
Click to collapse
Read that already and thank you for such a great post. Now, once i have done LVM using switch parition will i be able to flash any custom rom or just those which say unified?

treacherous_hawk said:
Read that already and thank you for such a great post. Now, once i have done LVM using switch parition will i be able to flash any custom rom or just those which say unified?
Click to expand...
Click to collapse
You can only flash ROMs which support LVM repartitioning.
---------- Post added at 11:56 PM ---------- Previous post was at 11:52 PM ----------
I've compiled a list of ROMs here: http://www.oppoforums.com/index.php?threads/23362/

Irwenzhao said:
You can only flash ROMs which support LVM repartitioning.
Click to expand...
Click to collapse
how to distinguish between the 2, if i take omnirom example it only says Find7 https://dl.omnirom.org/find7/
doesn't mention if it is supports LVM or not.
Also which all roms are available for Find7 with LVM Support?
Edit: Got it from your post on oppoforum. Thanks mate.
Edit: @Irwenzhao can i flash DU on Find7 x9076 as it says 7a.

treacherous_hawk said:
how to distinguish between the 2, if i take omnirom example it only says Find7 https://dl.omnirom.org/find7/
doesn't mention if it is supports LVM or not.
Also which all roms are available for Find7 with LVM Support?
Edit: Got it from your post on oppoforum. Thanks mate.
Edit: @Irwenzhao can i flash DU on Find7 x9076 as it says 7a.
Click to expand...
Click to collapse
Yes I believe DU is universal.

Irwenzhao said:
Yes I believe DU is universal.
Click to expand...
Click to collapse
Ok. so are these rom with LVM repartition are LVM aware and automatically detect if the phone is LVM or not? and it is not it will install like normal rom and if it is then it will install with LVM?
can you also tell me all the model number for Find 7 and 7a? as i also see Find7s as model

treacherous_hawk said:
Ok. so are these rom with LVM repartition are LVM aware and automatically detect if the phone is LVM or not? and it is not it will install like normal rom and if it is then it will install with LVM?
can you also tell me all the model number for Find 7 and 7a? as i also see Find7s as model
Click to expand...
Click to collapse
Find 7s is the Find 7QHD model.

Irwenzhao said:
Find 7s is the Find 7QHD model.
Click to expand...
Click to collapse
this is the one with model number x9076?
Edit: more i read more i get confused. I was going through @Entropy512 thread on 4.4.x omnirom and he has provided lvm script for setup and remove. So if i already setup lvm using the inbuilt feature on cos 2.0.4ib and then install twrp (i believe it has to be lvm aware twrp? does such twrp exist?) and then flash either omni 4.4 or 5.0 or nameless rom kk or LP then it will still be lvm remaped?
2nd scenario: i do not have to do lvm remapping, install omni rom 4.4 or 5.0 and after installing omni i can run setuplvm and removelvm as required?

treacherous_hawk said:
this is the one with model number x9076?
Edit: more i read more i get confused. I was going through @Entropy512 thread on 4.4.x omnirom and he has provided lvm script for setup and remove. So if i already setup lvm using the inbuilt feature on cos 2.0.4ib and then install twrp (i believe it has to be lvm aware twrp? does such twrp exist?) and then flash either omni 4.4 or 5.0 or nameless rom kk or LP then it will still be lvm remaped?
2nd scenario: i do not have to do lvm remapping, install omni rom 4.4 or 5.0 and after installing omni i can run setuplvm and removelvm as required?
Click to expand...
Click to collapse
I don't use LVM repartitioning, nor do I support using that method. Coldbird's method is much simpler in my opinion. You'll need to do more research/reading up on your own.

Irwenzhao said:
I don't use LVM repartitioning, nor do I support using that method. Coldbird's method is much simpler in my opinion. You'll need to do more research/reading up on your own.
Click to expand...
Click to collapse
Well after reading entropy's posts i have decided not to use unified method, also why risk it when there is already an option for lvm. If someone else could answer me on this as to if LVM repartition would remain while switching from COS to Omni or nameless.

Um, pretty much every question you've asked was answered in the post that I linked to... (With the exception of nameless adding autodetect last week, I need to update the list)
Other than the question of switching from one firmware to another (like COS 2.0.4 to Omni) - If you've got LVM set up, and you switch from one thing that supports LVM to another, all you need to do is Wipe Data/Factory reset in recovery (which you need to do whenever switching anyway...)
setuplvm/removelvm are only for enabling/disabling LVM - once it's enabled it stays enabled

maybe someone can help. LVM doesnt seem to make my device 32GB. still shows 3GB in nameless
1. flashed twrp 3.0.2-0
2. wipe/format all (no more OS, clean device)
3. flash setuplvm
4. reboot twrp
5. flash nameless 6, gapps (no root needed right? nameless already rooted?)
am i doing something wrong here?

Cyanogenmod 14.1 official nightly

Hi all,
Seems there is a CM14.1 nightly now available for find7s on the official CM site, link here: hxxps://download.cyanogenmod.org/?type=nightly&device=find7s
Was just wondering if anyones given it a go yet, and if so knows whether or not it supports LVM and how stable the rom is?
Haven't found any info that states one way or the other, hoping someone knows.
Thanks in advance.

About the storage support:
Stock -> YES
LVM - NO
Coldbird - Not tested
Chinese - YES
New display:
Cant test it because i havent the new display
At the moment no theme engine
Is stable for daily driver FROM MY POINT OF VIEW

Its a little bit weird that there is not available yet on the page https://www.cmxlog.com/14.1/
Hope it will appear here soon as well as it is already here:
(Find 7a) https://download.cyanogenmod.org/?device=find7
and
(Find 7) https://download.cyanogenmod.org/?device=find7s

Dirty flashed cm-14.1-20161205-NIGHTLY over cm-14.1-20161201-UNOFFICIAL via menu CyanogenMod updates. Everything seems to be OK. One remark: boot time when update is completed is quite long, so be patient. Of course in order to not see "SD corrupted" it is necessary to flash cm-13.0-find7-unified-storage-patch.zip
EDIT: Just for your information: boot animation CM face is gone. Now there is word "android" in plain white.

great news

Finally there we are changes logs:
https://www.cmxlog.com/14.1/find7/
https://www.cmxlog.com/14.1/find7s/

Android 7.1.1 in the next nightly

CyanogenMod will never support LVM.
This is 7.1 right? Or is it 7.0? I downloaded the 7.1 GAPPS, which should be correct for this build...
I updated it, and it runs smooth without any force crashes and nonsense. (Besides the time I tried to open an app not built for nougat, =P. If you're hesistant about updating, don't think, just do it.

Injected said:
About the storage support:
Stock -> YES
LVM - NO
Coldbird - Not tested
Chinese - YES
New display:
Cant test it because i havent the new display
At the moment no theme engine
Is stable for daily driver FROM MY POINT OF VIEW
Click to expand...
Click to collapse
i want to upgrade from an existing cm 13 installation, it is alredy unified with the chinese method, did you made a clean installation? what about the need of flashing Wuxianlin's patch after every upgrade? thanks in advice

-lorenzo- said:
i want to upgrade from an existing cm 13 installation, it is alredy unified with the chinese method, did you made a clean installation? what about the need of flashing Wuxianlin's patch after every upgrade? thanks in advice
Click to expand...
Click to collapse
Yup u can do that. After flashing cm14.1 official, u might wanted to flash cm13 patch by wuxianlin, then flash the gapps and lastly wipe the cache and dalvik

-lorenzo- said:
i want to upgrade from an existing cm 13 installation, it is alredy unified with the chinese method, did you made a clean installation? what about the need of flashing Wuxianlin's patch after every upgrade? thanks in advice
Click to expand...
Click to collapse
And yes you need to flash Wuxianlin's patch after every upgrade just for aesthetic purpose, that is to fix the SDcard damage info bug, unless CM find7 maintainer will fix that, and when it happen you will no longer need to flash the Wuxianlin's CM13 patch.

I am on crdroid right now (LVM) and i really want to try this. Please tell me in short how to revert back to stock partition and then flash this.

Yashraj Chawla said:
I am on crdroid right now (LVM) and i really want to try this. Please tell me in short how to revert back to stock partition and then flash this.
Click to expand...
Click to collapse
1. If you are on LVM you need to back to stock partition layout. Just google for "Find 7 unbrick tool" for procedure. "Sahara" tool is available for download here: http://d3bzg7dsosz4ht.cloudfront.net/OTA/Find7/FIND7WX_12_A.09_140810.tgz
2. Setup Chinese partition layout: http://forum.xda-developers.com/showpost.php?p=64149659&postcount=3
3. Flash wuxianlin's version of TWRP: link available under point 10. on http://community.oppo.com/en/thread-47844-1-1.html
4. Flash cm-14.1 last official nightly build: https://www.cmxlog.com/14.1/find7/
5. Flash nano open gaaps
6. Flash SU
7. Flash cm-13.0-find7-unified-storage-patch
8. Enjoy newest, very stable and fast Android 7.1.1.

Yashraj Chawla said:
I am on crdroid right now (LVM) and i really want to try this. Please tell me in short how to revert back to stock partition and then flash this.
Click to expand...
Click to collapse
rafal.polska.b said:
1. If you are on LVM you need to back to stock partition layout. Just google for "Find 7 unbrick tool" for procedure. "Sahara" tool is available for download here: http://d3bzg7dsosz4ht.cloudfront.net/OTA/Find7/FIND7WX_12_A.09_140810.tgz
2. Setup Chinese partition layout: http://forum.xda-developers.com/showpost.php?p=64149659&postcount=3
3. Flash wuxianlin's version of TWRP: link available under point 10. on http://community.oppo.com/en/thread-47844-1-1.html
4. Flash cm-14.1 last official nightly build: https://www.cmxlog.com/14.1/find7/
5. Flash nano open gaaps
6. Flash SU
7. Flash cm-13.0-find7-unified-storage-patch
8. Enjoy newest, very stable and fast Android 7.1.1.
Click to expand...
Click to collapse
OMG! No! Just need to flash "unlvm" script to revert to stock layout, that is supported by this ROM. Then flash ROM, gapps and SuperSU.
Anyway, to configure chinese storage, if desired, step 1 is unnecesary: just step 2 is enough.
And, of course, don't forget to make a backup in external SD because any choosen method (unbrick tool, setup chinese storage or revert LVM) erases both data and internal card.
Edit:
Here you can find the removelvm_find7_FULL_WIPE script needed to revert to stock layout; flashing it from TWRP is the only you need. When in stock again, you can proceed as usual flashing ROM, gapps and everything you want.

DELETE

Thanks everyone for the info, might hold off as I have LVM, here's hoping that namelessrom put out an official nougat rom in the not too distant future.

New Display is not supported
Injected said:
About the storage support:
Stock -> YES
LVM - NO
Coldbird - Not tested
Chinese - YES
New display:
Cant test it because i havent the new display
At the moment no theme engine
Is stable for daily driver FROM MY POINT OF VIEW
Click to expand...
Click to collapse
New Display is not supported. Colors, ghosting, and bleeding will still be running wild just like all older CM.
The only Custom ROM on the planet that fully supports new display is OmniROM and it seems that they could use some help. Please support their effort: omnirom.org

javier.pc said:
OMG! No! Just need to flash "unlvm" script to revert to stock layout, that is supported by this ROM. Then flash ROM, gapps and SuperSU.
Anyway, to configure chinese storage, if desired, step 1 is unnecesary: just step 2 is enough.
And, of course, don't forget to make a backup in external SD because any choosen method (unbrick tool, setup chinese storage or revert LVM) erases both data and internal card.
Edit:
Here you can find the removelvm_find7_FULL_WIPE script needed to revert to stock layout; flashing it from TWRP is the only you need. When in stock again, you can proceed as usual flashing ROM, gapps and everything you want.
Click to expand...
Click to collapse
Thank you guys i just did that and i must say CM - 14.1 is Lovely :good:

Yashraj Chawla said:
Thank you guys i just did that and i must say CM - 14.1 is Lovely :good:
Click to expand...
Click to collapse
It is. But omnirom support substratum theme.

StormTrooper89 said:
It is. But omnirom support substratum theme.
Click to expand...
Click to collapse
I think you can install substratum theme in CM14.1 (but only substratum themes that support Android 7.1.1), since there no theme engine inside CM14.1

[PATCHER][APP] Dual Boot Patcher [OFFICIAL SNAPSHOT]

This tool/app will allow any number of ROMs to be installed at the same time. It works by patching the secondary ROM's installation scripts and boot image to load the ROM files from an alternate location (/system/multiboot, /cache/multiboot, and /data/multiboot). Because of the way this is implemented, no changes to the primary ROM are necessary
Donators
A huge thanks goes out to all of the donators for supporting this project! I if forgot to add you (and you want to be added), please send me a quick PM.
See all of our supporters here: https://gist.github.com/chenxiaolong/3f3fb485cbd0cb77c4281941433ec54d
It patches...
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
NOTE: If you want to dualboot an EUI ROM, I highly recommend installing EUI as the primary ROM.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
Windows (GUI)
Double click DualBootPatcher.exe and choose the file you want to patch.
--------
After patching the zip file, a new file, like some_rom_dual.zip file will be created. For example, patching ktoonsez's
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013.zip
would create a new
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013_dual.zip
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/showthread.php?t=2491299
How do I...?
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.​
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a ROM.
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!​
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.​
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.​
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.​
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it ​
Downloads:
[LINK] Dual Boot Patcher (Snapshots) and DualBootUtilities recovery zip
Donations:
Donations are not required, but are greatly appreciated Donators will have their names listed in a nice big font on this post and will also be listed in the README file of the patcher.
Source code:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Please note, any bugs regarding app itself can be created over at https://github.com/chenxiaolong/DualBootPatcher/issues
Any other device-specific stuff can be asked over here itself.
XDA:DevDB Information
Dual Boot Patcher, Tool/Utility for the LeEco Le 1S
Contributors
chenxiaolong, DroidThug, https://github.com/chenxiaolong/DualBootPatcher/graphs/contributors
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Snapshot
Current Beta Version: 9.2.0.r25.g0638efb
Beta Release Date: 2017-04-11
Created 2017-04-11
Last Updated 2017-04-11

FAQ
What does this do:
It allows you to multiboot between ROMs
What does it require:
It requires an unlocked bootloader, and root access
I have problems regarding this app:
1. Post the MultiBoot.log from your internal storage
2. Describe the problems with details such as which ROM, Kernel etc, and which variant of device you own (e.g x501, x507 etc.)
Does it support VoLTE:
This is not related to the tool. Do not ask for it
Help! I hardbricked/softbricked my device:
Sure, just describe what you did exactly
___ MORE TO COME
Any builds from and after 9.2.0.r25.g0638efb dated Mon, 10 Apr 2017 timed 19:57:27 should be okay to use for Le 1S

Can you make video how to install and run this app

sumitgp said:
Can you make video how to install and run this app
Click to expand...
Click to collapse
There are some out in youtube. But they are kinda outdated. Maybe someone will make it in the near future

DroidThug said:
There are some out in youtube. But they are kinda outdated. Maybe someone will make it in the near future
Click to expand...
Click to collapse
Your welcome bro
And ur contribution marvelous
Just keep going we are with u
Love u bhai thanks

is it work on LETV Le 1s x507
thanks for app
Iam asking because I dont understand LeEco 1S Products
Because LeEco 1s is X509
LETV 1S is x507
Is it also works on LETV Le 1s x507? please

fire3k said:
thanks for app
Iam asking because I dont understand LeEco 1S Products
Because LeEco 1s is X509
LETV 1S is x507
Is it also works on LETV Le 1s x507? please
Click to expand...
Click to collapse
Yes it work on le 1s x507

sumitgp said:
Yes it work on le 1s x507
Click to expand...
Click to collapse
Thnaku very much
then I'll try

fire3k said:
Thnaku very much
then I'll try
Click to expand...
Click to collapse
Thanku Very Much
I installed DualBootPatcher in My Le1S x507
and installed anlogside EUI, LineageOS 14.1 and Resurrection Remix 5.8.2 .
and they both working fine and installed gapps in both ROMS.
But 1 problem: that I installed SuperSu in LineageOS 14.1 and its working fine but when I try to install Supersu in Resurrection Remix 5.8.2, it installed perfectly there is no errors but when I open SuperSu app in Resurrection Remix 5.8.2 , It said that su binaries not installed
then I try to install Magisk12 in Resurrection Remix 5.8.2 and it gives some error.Please Giveme some Suggetion how to install magisk
Note: before install magisk, I already Patched it for RR 5.8.2

fire3k said:
Thanku Very Much
I installed DualBootPatcher in My Le1S x507
and installed anlogside EUI, LineageOS 14.1 and Resurrection Remix 5.8.2 .
and they both working fine and installed gapps in both ROMS.
But 1 problem: that I installed SuperSu in LineageOS 14.1 and its working fine but when I try to install Supersu in Resurrection Remix 5.8.2, it installed perfectly there is no errors but when I open SuperSu app in Resurrection Remix 5.8.2 , It said that su binaries not installed
then I try to install Magisk12 in Resurrection Remix 5.8.2 and it gives some error.Please Giveme some Suggetion how to install magisk
Note: before install magisk, I already Patched it for RR 5.8.2
Click to expand...
Click to collapse
Bhai check devloper option if there is any setting for root
If this will not work then try to share apps (super su app)
If above mentioned methods not work then try isu (higher version) of super su u can found it on los site
Thanks and warm regards

sumitgp said:
Bhai check devloper option if there is any setting for root
If this will not work then try to share apps (super su app)
If above mentioned methods not work then try isu (higher version) of super su u can found it on los site
Thanks and warm regards
Click to expand...
Click to collapse
Thanks for sugestion
but there is no option in Setting or devoloper option in Resurrection Remix 5.8.2 . only setting available in Magisk manager but it displays message that there is no root in system. Also tried chainfire Supersu. installs SuperSu App and when I tried to open it displays that There is no root binaries. Please help.
root is functioning in Resurrection Remix 5.8.2, when I install ROM without Dual Boot Patcher. but Only installs One ROM at a time no multiboot. Please any suggestion?

Thanks For Dual Boot Patcher
Atlast Solved
First I Flashed Chainfire SuperSu, then reboot then check root , it failed, and then I reboot and flash Magisk 12 and reboot. This Time All Ok Root Succeded

thanks for the updates!

If any one have le 1s related problem and solution or any one want to try new rom or kernal asap then all of u are welcome in our group on telegram so plz join with us
Requriemt
1. Download telegram from play store
2. Just click below link
https://telegram.me/LeSuperGroup
Thanks all of u

error
it shows error while booting 2nd rom

pravesh46 said:
it shows error while booting 2nd rom
Click to expand...
Click to collapse
What error? Be specific or give logs-,-

'have to try this! Thanks.
But, could this by any way interfer or get problem with F2FS formatted partitions (data,cache) ?

I'm also having some errors while installing the secondary rom...like extracting system errors

Hi! my Le1S gone in bootloop. Is there any solution to boot into the Primary ROM (i.e. eUI) via twrp? I have installed dual boot patcher & made eui as primary rom, lineage as secondary rom in "rrnougat" data slot & resurrection remix as secondary rom in " rrnougat2 " data slot.
From the past 2 weeks, I am using resurrection remix rom & sometimes eui. Today, I was on rr & my phone was hanging. So, I simply just restarted it & then, it gone in bootloop.
So, canI boot into my primary eui rom via twrp?, as dual boot patcher app cannot be accessed. Please help.

iamkamlesh said:
Hi! my Le1S gone in bootloop. Is there any solution to boot into the Primary ROM (i.e. eUI) via twrp? I have installed dual boot patcher & made eui as primary rom, lineage as secondary rom in "rrnougat" data slot & resurrection remix as secondary rom in " rrnougat2 " data slot.
From the past 2 weeks, I am using resurrection remix rom & sometimes eui. Today, I was on rr & my phone was hanging. So, I simply just restarted it & then, it gone in bootloop.
So, canI boot into my primary eui rom via twrp?, as dual boot patcher app cannot be accessed. Please help.
Click to expand...
Click to collapse
You can switch to other rom using dualbootutilities.zip. Just flash the zip . Then select ROM u want to switch & then select switch to..

Best ROM for Hardcore Gaming? (ex: PUBG mobile)

Best rom with custom kernel support for better gaming. Since stock miui is too heavy. PLease suggest

Unofficial LineageOS by nijel8, my script & pico Gapps.

Zola III said:
Unofficial LineageOS by nijel8, my script & pico Gapps.
Click to expand...
Click to collapse
which script exactly sir? there are number of them

This one, maybe
https://forum.xda-developers.com/mi...ce-kernel-tuning-tweaks-t3584897/post71739624

Scripts are in fifth post, you use one for a variant of the phone you have.
https://forum.xda-developers.com/showpost.php?p=71739624&postcount=5
You flash it like anything else from TWRP & if you don't like it you flash back stock one from same post.

Zola III said:
Scripts are in fifth post, you use one for a variant of the phone you have.
https://forum.xda-developers.com/showpost.php?p=71739624&postcount=5
You flash it like anything else from TWRP & if you don't like it you flash back stock one from same post.
Click to expand...
Click to collapse
Kernel? should i flash it over a stock miui kernel or can you suggest a kernel for miui9.2 global stable. Cheers

pg8286 said:
Kernel? should i flash it over a stock miui kernel or can you suggest a kernel for miui9.2 global stable. Cheers
Click to expand...
Click to collapse
I explicitly told you which ROM, Gapps & script you need to flash. Script won't work with MIUI! Their is no costume kernel for MIUI!
ROM:
https://forum.xda-developers.com/mi-max/development/rom-lineageos-14-1-t3529851
Why this one? Because it's rock stable & far less buggy than MIUI. It comes with semi costume kernel (only really needed things ware add & set as defaults) which is also much more secure than others available. Same kernel is adopted by all newer costume ROM's. It's also semi costume ROM & contains only fixes like full support for dual SIM, VOLTE status bar indicator that you won't find in official LineageOS builds, it also uses firmware property libs for hardware directory from Xiaomi MIUI builds. It doesn't contain any added apps or anything else different from official LineageOS. Reed the first post carefully before flashing!
Pico Gapps are the smallest one's & only ones that don't come with Google Asistent which alone saves 100MB of RAM.
So from TWRP as I assume you already have it if you don't find also nijel8 TWRP & install it first. You first flash the ROM, firmware, Pico Gapps (all linked in the first post for ROM), power/performance script. Let it boot in settings find & enable hotplug install your apps & games & enjoy.

Zola
Your script Does it work with..... RR-O v6.0.0 , micro gapp?

el.magic said:
Your script Does it work with..... RR-O v6.0.0 , micro gapp?
Click to expand...
Click to collapse
Gapps are Gapps. I told pico Gapps because they are smaller and lack Google assistant for sole gaming purpose that means 100MB free RAM. I don't know about RR (I doubt it) ask the author.