RECOVERY
TWRP & CM-Recovery
Z00A/Z008 ( LP Bootloader)
Just as the title says these are unofficial recovery builds for Asus Zenfone 2 Z00A and Z008 models
These have been tested and confirmed functional. These are built from current CM devices trees, CM kernel source. Source links provided below. If you find any bugs please report with an attached recovery log.
DOWNLOAD
Current Versions provided for both devices
TWRP 2.8.7.3 (LP based)
TWRP 2.8.7.7 (M based)
CM-Recovery 9-28-15 (LP based)
CM-Recovery 12-22-15 (M based)
{ Cm-Recovery doesn't use "version" tags so using build date as a version # }
SOURCES
Recovery built in a CM-12.1/13.0 environment respectively using device trees/kernel
from our CM device trees/kernel CM-zenfone2 github
Z00A LP Tree HERE
Z008 LP Tree HERE
Z00A M Tree HERE
Z008 M Tree HERE
Kernel Source
CM-Recovery source from CM-recovery
TWRP source tyipically from Omnirom
HOWEVER 2.8.7.6 beta uses modified TWRP source from omnirom (and patched from thier gerrit) from
HERE
Code:
Changelog:
1-22-16:
TWRP 2.8.7.7
- fixed OTG & external SDCARD mount
- from TWRP: language support, code cleanup and minor fixes(see twrp github for full list)
- this is pre-release testing main ly for soon to be released TWRP 3.0
12-22-15:
* updated builds
* should fix backups in TWRP
* should fix issues flashing newer ROMS after 12-17-15
12-7-15
* 2.8.7.5 TWRP builds
* fixed opengapps flashing
12-6-15
* split into new thread
* Marshmallow based recoveries now live
* TWRP is WIP prior to next major official tag, new theme included for testing
Z00A/Z008 ( MM Bootloader)
Just as the title says these are unofficial recovery builds for Asus Zenfone 2 Z00A and Z008 models
These have been tested and confirmed functional. These are built from current CM devices trees, CM kernel source. Source links provided below. If you find any bugs please report with an attached recovery log.
DOWNLOAD
Current Versions provided for both devices
TWRP 3.0.2-M1 (MM based)
SOURCES
Recovery built in a Omnirom-6.0 environment respectively using device trees/kernel below
Z00A/Z008 MM Tree HERE
Kernel Source HERE
TWRP source tyipically from Omnirom
Code:
Changelog:
Initial source built MM bootloader friendly based recovery release
Z00D
Just as the title says these are unnoficial recovery builds for the Asus Zenfone 2 Z00D (ze500cl) model
These have been tested and confirmed functional. These are built from experimental devices trees, modified Stock kernel source. Source links provided below. If you find any bugs please report with an attached recovery log.
DOWNLOAD
Current Versions provided for both devices
TWRP 3.0.2-0
SOURCES
Recovery built in a omnirom environment respectively using device trees/kernel
from our my github
Device Tree
Kernel Source
Code:
Changelog:
5-3-16: Initial TWRP build
XDA:DevDB Information
Zenfone2 Recovery, Tool/Utility for the Asus ZenFone 2
Contributors
jrior001, crpalmer
Source Code: https://github.com/CM-zenfone2
Version Information
Status: Beta
Beta Release Date: 2015-12-06
Created 2015-12-07
Last Updated 2016-08-03
Niceeeeeeeeeeeeeeeee
Well this was unexpected, thank you so much for this!
Edit: Well I tried the MM version, and I must say I love the new look! It's kinda laggy, but that's very expected and I got a recovery log.
Aceofzeroz said:
It's kinda laggy, but that's very expected and I got a recovery log.
Click to expand...
Click to collapse
TWRP still uses some really old code for pixelflinger. We have been using a JB era patch from Intel to add x86 optimized acceleration, which Dees_Troy(TWRP dev) and the zenfone5/6 devs ported to KK & LP. I updated it for M, but this is about as good as it gets until TWRP overhauls that section of their code. Without this patch is basically unusable.
And yes the new theme is sexy It's months in the making from TWRP contributer @z31s1g and it's quite lovely.
jrior001 said:
TWRP still uses some really old code for pixelflinger. We have been using a JB era patch from Intel to add x86 optimized acceleration, which Dees_Troy(TWRP dev) and the zenfone5/6 devs ported to KK & LP. I updated it for M, but this is about as good as it gets until TWRP overhauls that section of their code. Without this patch is basically unusable.
And yes the new theme is sexy It's months in the making from TWRP contributer @z31s1g and it's quite lovely.
Click to expand...
Click to collapse
Ah, I understand the situation now and glad that the patch worked out for the time being. Definitely better than not having the latest TWRP to play with, so my highest gratitude for the amazing work bringing up Marshmallow in time for the holidays! :thumbup:
Sent from the Ace's MB865 using Tapatalk
This is a bit wonky with device encryption. It'll boot the recovery without a theme loaded and ask for my pattern (as expected). I'll put that in and it'll decrypt and mount storage, then the "put in your pattern" prompt comes up again (this time, with my twrp theme loaded). I can cancel that prompt just fine and it'll sit on the main screen and I can proceed from there, so it's not a showstopper at least.
This didn't happen on 2.8.7.3.
edit: on flashing opengapps 6.0 micro, I'm warned that the recovery is missing the xz binary and can't flash the zip (and told me to update to the latest recovery for my device, lol). I'll upload the generated log shortly.
edit edit:
Code:
# Begin Open GApps Install Log
-----------------------------------------------------------------------------
ROM Android Version | 6.0
-----------------------------------------------------------------------------
# End Open GApps Install Log
INSTALLATION FAILURE: The installer detected that your recovery does not support
XZ decompression. Please update your recovery or switch to another one like TWRP.
# Begin User's gapps-config
# End User's gapps-config
Fortunately, flashing my L-gapps seems to have worked fine (...seeeeeems to. I'll see if it works. The setup app did at least update itself, so there's that.)
Is there an easy way to update my TWRP? Any apps that can do this for me?
roach9 said:
Is there an easy way to update my TWRP? Any apps that can do this for me?
Click to expand...
Click to collapse
I know Flashify can do that in many devices, I am not sure about ours, I think best way would be to flash it using fastboot.
Marshmallow recovery can be used to flash lollipop Rom...??..and vice versa...??
Any difference for 2.8.7.4 vs .3 other than the look? Googled it and found nothing.
Sayan44 said:
I know Flashify can do that in many devices, I am not sure about ours, I think best way would be to flash it using fastboot.
Click to expand...
Click to collapse
Why not via TWRP itself? TWRP has a feature to flash an .img directly to boot or recovery.
Sent from my ASUS_Z00AD
I am on 2.8.7.3. I am thinking to flash cm13. Is it necessary to update twrp? Or I can flash cm13 using my old one?
Sent from my ASUS_Z00A using Tapatalk
rex_perfect said:
Marshmallow recovery can be used to flash lollipop Rom...??..and vice versa...??
Click to expand...
Click to collapse
Pretty much, LP version is stable and works for flashing M ROMs.
Sent from my ASUS_Z00A using Tapatalk
espeon said:
This is a bit wonky with device encryption. It'll boot the recovery without a theme loaded and ask for my pattern (as expected). I'll put that in and it'll decrypt and mount storage, then the "put in your pattern" prompt comes up again (this time, with my twrp theme loaded). I can cancel that prompt just fine and it'll sit on the main screen and I can proceed from there, so it's not a showstopper at least.
This didn't happen on 2.8.7.3.
edit: on flashing opengapps 6.0 micro, I'm warned that the recovery is missing the xz binary and can't flash the zip (and told me to update to the latest recovery for my device, lol). I'll upload the generated log shortly.
edit edit:
Code:
# Begin Open GApps Install Log
-----------------------------------------------------------------------------
ROM Android Version | 6.0
-----------------------------------------------------------------------------
# End Open GApps Install Log
INSTALLATION FAILURE: The installer detected that your recovery does not support
XZ decompression. Please update your recovery or switch to another one like TWRP.
# Begin User's gapps-config
# End User's gapps-config
Fortunately, flashing my L-gapps seems to have worked fine (...seeeeeems to. I'll see if it works. The setup app did at least update itself, so there's that.)
Click to expand...
Click to collapse
Will look into both issues, I am encrypted currently but without a pin/pattern and don't have that issue.
Sent from my ASUS_Z00A using Tapatalk
So what's the difference of this TWRP and TheSSJ TWRP?
jrior001 said:
Will look into both issues, I am encrypted currently but without a pin/pattern and don't have that issue.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
The 2nd one happened after I decrypted; I forgot to mention that. I don't think it actually happened when I was encrypted using the L-based recovery (I upgraded my recovery, then decrypted, then tried flashing the rom + gapps)
Thread moved to proper forum
jrior001 said:
Will look into both issues, I am encrypted currently but without a pin/pattern and don't have that issue.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Having the same issue actually, not encrypted, worked on .3 no pin or lock on screen either. Happened trying to install the latest Gapps package.
Heavybullets said:
Having the same issue actually, not encrypted, worked on .3 no pin or lock on screen either. Happened trying to install the latest Gapps package.
Click to expand...
Click to collapse
ended up fastboot installing the recovory, didnt work, factory reset, then try it, didn't work, fixing permissions, all that, nothing has worked for me, the latest .4 twrp still comes up with that "The installer detected that your recovery does not support
XZ decompression." Error.
Heavybullets said:
ended up fastboot installing the recovory, didnt work, factory reset, then try it, didn't work, fixing permissions, all that, nothing has worked for me, the latest .4 twrp still comes up with that "The installer detected that your recovery does not support
XZ decompression." Error.
Click to expand...
Click to collapse
well yeah when you have a missing binary reflashing it probably isn't going to do anything, assuming it didn't get corrupted
Related
FEEL FREE TO DONATE US FOR ALL WE'RE DOING FOR YOU!
For general discussions, bug reports and FAQ, write HERE!
Credits:
MoltenMotherBoard team!
Downloads:
CWM Recovery | Code.Google
Full sources:
MoltenMotherBoard sources: MoltenMotherBoard | Github
CyanogenMod sources: CyanogenMod | Github
Kernel: lge-kernel-p880 | Github
Changelog:
20131126
Associated to Power Button the action SELECT_ITEM
From 6.0.4.4 to 6.0.4.5
Code updates from CyanogenMod, Google
20131120
First release
Issues:
Do you want to report an issue? Do it here!
In order to do it, create a new issue, choosing correct labels corrisponding to: Device/OS which you're using, ROM/project you're on, kind of issue.
Also, please, be sure you're running the ROM/project in the exact way we've provided it to you (do not create issues if you're using different
kernel, mod, plugins and dependencies we didn't tell to use).
General Questions: MoltenMotherBoard Projects | General Questions and Info
Official Mantainer(s): Mackief, ItachiSama, p4c0
Installation guide:
[Method 1° ~ fastboot]
Code:
$ adb reboot oem-unlock
$ fastboot flash recovery /PATH-TO-THE-IMG-FOLDER-ON-YOUR-COMPUTER/cwm.img
$ fastboot reboot
[Method 2° ~ adb] (put the recovery.img in your sdcard)
Code:
$ adb shell
$ su
# cat /sdcard/cwm.img > /dev/block/mmcblk0p1
# sync
# exit
$ exit
With CyanDelta work?
negativman said:
With CyanDelta work?
Click to expand...
Click to collapse
Obviously it does. In fact, CyanDelta only make a flashable package, that you have to install manually from recovery. Then, yep.
BTW, now want also to make for you a Touch version of this CWM.
mackief said:
Obviously it does. In fact, CyanDelta only make a flashable package, that you have to install manually from recovery. Then, yep.
BTW, now want also to make for you a Touch version of this CWM.
Click to expand...
Click to collapse
cyandelta installs the zip automatically too, if the recovery supports openrecovery script. TWPR does, and so does the CWM based recovery in CM sources. the original CWM from rom manager does not work properly AFAIK
gandhar said:
cyandelta installs the zip automatically too, if the recovery supports openrecovery script. TWPR does, and so does the CWM based recovery in CM sources. the original CWM from rom manager does not work properly AFAIK
Click to expand...
Click to collapse
It could be that CWM from Rom-Manager is out-to-date.
The only way it could not work, is because thi updated CWM still need some merging and commits by the team. Just try and let us know!
mackief said:
It could be that CWM from Rom-Manager is out-to-date.
The only way it could not work, is because thi updated CWM still need some merging and commits by the team. Just try and let us know!
Click to expand...
Click to collapse
i had last tried a long time back, don't know and don't care about the current condition
i like TWRP much more.
just saw your post on g+ about a ubuntu touch port, any progress on that? i am very interested in that.
mackief said:
Obviously it does. In fact, CyanDelta only make a flashable package, that you have to install manually from recovery. Then, yep.
BTW, now want also to make for you a Touch version of this CWM.
Click to expand...
Click to collapse
Will another Nightly today or tomorrow, check whether a set CyanDelta!
Oh yes, the touch recovery - it would be very great. TWRP I personally do not like it. And the one that I have now for our smartphone is locked Rom Manager!
gandhar said:
i had last tried a long time back, don't know and don't care about the current condition
i like TWRP much more.
just saw your post on g+ about a ubuntu touch port, any progress on that? i am very interested in that.
Click to expand...
Click to collapse
About Ubuntu, it's not that simple.
It seems 4X kernel from CM team does not load into the system.
Unfortunately, I cannot debug which is the problem surely: but I'm sure I'll return on it in a week at least. I've some thoughts about how to make it loading and booting next to the kernel!
negativman said:
Will another Nightly today or tomorrow, check whether a set CyanDelta!
Oh yes, the touch recovery - it would be very great. TWRP I personally do not like it. And the one that I have now for our smartphone is locked Rom Manager!
Click to expand...
Click to collapse
As I understood CWM Touch is buildable only through clockworkmod-builder, and I'll do it. The only problem is that in that site, the sources are out-to-date, linked to 4.3 branches.
So, we have to wait, till CWM will update the sources linked in the site to build a 6.0.4.4 touch recovery.
mackief said:
As I understood CWM Touch is buildable only through clockworkmod-builder, and I'll do it. The only problem is that in that site, the sources are out-to-date, linked to 4.3 branches.
So, we have to wait, till CWM will update the sources linked in the site to build a 6.0.4.4 touch recovery.
Click to expand...
Click to collapse
Do not quite understand! Surely there's a new CWM 6.0.4.4. You can unlock it from Rom Manager? http://forum.xda-developers.com/showthread.php?t=2523732
Hey.
Just built a new build of CWM, now coded 6.0.4.5.
In this new release, CM team has apported an important fix - as also TWRP team has done - that avoid any issue while flashing some of KitKat based roms.
BTW, made a test build of CM11, gonna test it
mackief said:
Hey.
Just built a new build of CWM, now coded 6.0.4.5.
In this new release, CM team has apported an important fix - as also TWRP team has done - that avoid any issue while flashing some of KitKat based roms.
BTW, made a test build of CM11, gonna test it
Click to expand...
Click to collapse
Feel free to take us alpha testers
Sent from my Optimus 4X HD using XDA Premium 4 mobile app
[email protected] said:
Feel free to take us alpha testers
Sent from my Optimus 4X HD using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Just pulled a log, as it does not boot.
Having some issues related to gralloc. Need to debug!
mackief said:
[...]
So, we have to wait, till CWM will update the sources linked in the site to build a 6.0.4.4 touch recovery.
Click to expand...
Click to collapse
Just take a look at my sig we already have 6.0.4.4 touch
laufersteppenwolf said:
Just take a look at my sig we already have 6.0.4.4 touch
Click to expand...
Click to collapse
Oh, marvolous!
But how can I build it? Is it buildable from source?
If you don't want me to build it, just update your port to 6.0.4.5. Ty, dude!
laufersteppenwolf said:
Just take a look at my sig we already have 6.0.4.4 touch
Click to expand...
Click to collapse
When he unlocked from Rom Manager?
mackief said:
Oh, marvolous!
But how can I build it? Is it buildable from source?
If you don't want me to build it, just update your port to 6.0.4.5. Ty, dude!
Click to expand...
Click to collapse
I will update it ASAP
negativman said:
When he unlocked from Rom Manager?
Click to expand...
Click to collapse
Not at all, as only official device maintainers can. And as I am not a maintainer, I can't
Just released new build of CWM.
Changelog:
Associated to Power Button the action SELECT_ITEM
From 6.0.4.4 to 6.0.4.5
Code updates from CyanogenMod, Google
Follow us on Google+, Facebook & Twitter!
Cheers.
We recently changed our Issue Tracker URL.
If you want to report a bug, please, follow the new instructions:
· Issue Tracker URL: Issues | Github
· Important notes: go to the linked URL, create a new issue, choosing correct labels corrisponding to: Device/OS which you're using, ROM/project you're on, kind of issue. Also, please, be sure you're running the ROM/project in the exact way we've provided it to you (do not create issues if you're using different kernel, mod, plugins and dependencies we didn't tell to use).
Development for this project has been totally and officially stopped, as no more needed.
Greetings,
MoltenMotherBoard team.
Hello guys!
After learing a lot from these great devs arround here i decided to start to try out a new project! Multirom!!
You might or might not have heared of it, THE multi-boot mod for the Nexus 7. I found it and have decided to port it for our device.
First of all, it is a very initial release now. Though I have tested multiple cases and didn't find any problem except those in the bug list, bugs can arise. Do have a backup! Also, do read through the whole OP and 2nd post! If you don't understand something, rather read again and/or ask!
For more information on how it works and what it does, I suggest that you read the first few posts in the original thread. Those are very detailed and well-written posts that explain MultiROM in general. Installing roms to USB and Ubuntu/Ubuntu Touch of course doesn't work for our device atm.
Installation
The device must not be encrypted!
You need to flash the modified TWRP recovery that has MultiROM extensions. My version is based on the latest sources with gordon0001's device-specific modifications included. You can keep this recovery if you don't want to use MultiROM anymore and you like TWRP, because the MultiROM extensions don't interfere with other functions, even if the boot sector is not injected.
You have to flash a kernel that is capable of Kexec-hardboot.
Links
You can find everything at https://www.androidfilehost.com/?w=files&flid=32204.
multirom-20150521-v32-UNOFFICIAL-p880.zip : The multirom zip
CM12_Kernel_Patched.zip : CM 12 Kernel with Kexec-Hardboot Patch ; Thanks to @Adam77Root the patch and @laufersteppenwolf for building Kernel
multirom_uninstaller.zip : Selfexplaining
Known Bugs
-Reboot to recovery doesn't work.
-UI has some graphical bugs
-Double Press to boot Secondary Rom doesnt work -> Press twice on the Rom you want to boot and press Powerbutton at the same time till you recoginze a vibration
-You tell me more
Changelog
23 May 2015: Initial release
Credits
@Tasssadar for MultiROM, Kexec-hardboot for Nexus 7 and his help with debugging and porting
@Adam77Root for Thread Content
XDA:DevDB Information
[MOD][23 MAY] MultiROM v32, Tool/Utility for the LG Optimus 4X HD
Contributors
fritzcola
Version Information
Status: Testing
Created 2015-05-23
Last Updated 2015-05-24
Explanation
In the next two examples, I will refer any official, unofficial, or CM-based roms as CM. Keep this in mind.
I use the word 'injected', because MultiROM is actually injected into the boot partition. It works on any kernel that is capable of doing Kexec-hardboot (and if you don't want to use different kernel (i.e. you will use kernel sharing), it will work on unpatched kernels as well).
I may refer to non-shared kernel method as Kexec(-hardboot) method
Example scenario of multi-booting CM with CM and kernel sharing
You are on CM with MultiROM-capable recovery, patched kernel and MultiROM-injected and you want to install e.g. CarbonRom as second.
Boot into TWRP, navigate to Advanced->MultiROM and select 'Add ROM'. Since the base rom is CM, you can share the same kernel. It will be faster as there will be no hardboot needed.
The installation steps are easy and it doesn't take more time than a normal installation.
Example scenario of multi-booting CM with CM and different kernel
You are on CM with MultiROM-capable recovery, patched kernel and MultiROM-injected and you want to install e.g. CarbonRom as second.
Boot into TWRP, navigate to Advanced->MultiROM and select 'Add ROM'. Select 'Don't share'.
Continue with installation.
Now, since the target kernel (that is installed with the rom) is very likely not patched, you will have to flash one of my linked kernels to that rom. Do this by selecting 'List roms', selecting the desired rom, than 'Flash ZIP' and flashing one of the kernels I have patched.
You can only share kernels if you are on the same Android version for example 5.0.x!
Source Codes:
Tree
Any screenshot? I didn't understand the ui bugs. What are they ? Great work fritzcola I will install my device when ui bugs are solved
CrazyWinner said:
Any screenshot? I didn't understand the ui bugs. What are they ? Great work fritzcola I will install my device when ui bugs are solved
Click to expand...
Click to collapse
Look here! https://www.dropbox.com/s/whor0zf6xx7z4jh/VID_20150523_234854.mp4?dl=0
fritzcola said:
Look here! https://www.dropbox.com/s/whor0zf6xx7z4jh/VID_20150523_234854.mp4?dl=0
Click to expand...
Click to collapse
Ow it's no problem for me Installing now , great work !
thanks
its work good
HI @fritzcola i have this bugs
after flash kernel
system ui has stopped on Euphoria rom
sim internet not work on ResurrectionRemix+BlissPop rom
some rom need to disable sim (plane mod )or it got bootloop from home screen PAC-ROM LP rom
work before but now i have this.
many times when add lolipop rom in multiboot i get error
blkdiscrad faild: operation not supported on transport endpoint
e:error executing updater binary in zip '/tmp/mr_update.zip
faild to install zip
thanks
mater2 said:
HI @fritzcola i have this bugs
after flash kernel
system ui has stopped on Euphoria rom
sim internet not work on ResurrectionRemix+BlissPop rom
some rom need to disable sim (plane mod )or it got bootloop from home screen PAC-ROM LP rom
work before but now i have this.
many times when add lolipop rom in multiboot i get error
blkdiscrad faild: operation not supported on transport endpoint
e:error executing updater binary in zip '/tmp/mr_update.zip
faild to install zip
thanks
Click to expand...
Click to collapse
That error with executing bla bla bla is rom related!
I already have TWRP 2.8.6.0 installed. To use your MultiROM Mod do I just need to flash MultiROM zip? Or do I need to flash recovery img (I found in your link)?
Will the uninstall zip send me back directly to the Stock TWRP 2.8.6.0?
__________________________________________
It works. But I'm getting the same problem as @mater2.
"error executing updater binary in zip '/tmp/mr_update.zip";
I tried latest BlissPop 3.4 and Euphoria 1.1.
If it is ROM related how can we solve it?
I saw some users reporting the same problem with the Nexus 5. They said the problem was on the "updater-script" of the ROM.
Thanks for your work and attention.
Enviado de meu Optimus 4X HD usando Tapatalk
gugu6897 said:
I already have TWRP 2.8.6.0 installed. To use your MultiROM Mod do I just need to flash MultiROM zip? Or do I need to flash recovery img (I found in your link)?
Will the uninstall zip send me back directly to the Stock TWRP 2.8.6.0?
__________________________________________
It works. But I'm getting the same problem as @mater2.
"error executing updater binary in zip '/tmp/mr_update.zip";
I tried latest BlissPop 3.4 and Euphoria 1.1.
If it is ROM related how can we solve it?
I saw some users reporting the same problem with the Nexus 5. They said the problem was on the "updater-script" of the ROM.
Thanks for your work and attention.
Enviado de meu Optimus 4X HD usando Tapatalk
Click to expand...
Click to collapse
1. Create backup from primary rom
2. Wipe everything and install rom you want as secondary as primary
3. Make backup from Primary you want to have as secondary
4. Use option to add rom to MR with Backup
5. Restore backup from old Primary
Are iodak and werewolf supporting multirom ?
@fritzcola
@gugu6897
strange thing its work for me all roms i can multiboot after some days and try some roms except euphoria because its not work with patched kernal after that
the error Shows up i try to format every thing internal +cache+davlik
doesn't fix that .
its allow to add 4.4.4 or 4.1.2 rom but 5.0x didn't
thanks for your good work
CrazyWinner said:
Are iodak and werewolf supporting multirom ?
Click to expand...
Click to collapse
I tried Werewolf kernel. The answer is no [emoji17].
Enviado de meu Optimus 4X HD usando Tapatalk
@gugu6897 @CrazyWinner
the kernel in this post (patched kernel) only can used for multiboot.
when use patched kernel
maybe you will have bug with sim internet with all roms except blissbob.
every thing else work good
@CrazyWinner, looks like iodak (and mourta too) has kexec-hardboot, but my secondary ROM (MIUI v5) don't boot. I double tap it, but the device just power off.
Does someone know any ROM that works with MultiROM?
Enviado de meu Optimus 4X HD usando Tapatalk
Look at Known Bugs in post #1
Sent from my A0001 using XDA Free mobile app
fritzcola said:
Look at Known Bugs in post #1
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks, I forgot about that [emoji28].
Enviado de meu Optimus 4X HD usando Tapatalk
progress
is it 'save' and will you update this anytime soon??
an update to MultiROM v33 - MultiROM TWRP 3.0.0-1 would be amazing
Extractor 2.4 from @Alexey71
derders said:
an update to MultiROM v33 - MultiROM TWRP 3.0.0-1 would be amazing
Click to expand...
Click to collapse
+1
I just discover the win tool Extractor 2.4 from @Alexey71 , as I didn't succeed to get finish compiling mmb 5.1.1.37 (or 29), I played with @csk1jw 2xAosp LP &MM system.new.sdat:
http://forum.xda-developers.com/showpost.php?p=57742855&postcount=42
extraction + re-zip(boot.img+file_contexts +/system/) in @laufersteppenwolf Nameless 5.1.zip + twrp’ add 2nd multirom + reboot and IT JUST WORKS!
I can now multiboot, WITH Nameless 5.1 AS PRIMARY: mmb 5.1 as 2nd+
cm11+OEMlg JB (+ BlisspopLP+ crdoidLP).
Many thanks to native kexeced Nameless’ kernel for LP!
Unfortunately’ the re-zipped aosp MM did not boot (boot.img conflict? or primary slot required with kexec.. or I miss more).
I believe there won’t be any future update on mmbLP, so it will be good if, @csk1jw or @MoltenMotherBoard or @streambinder could make an old_fashion-zipped official ultimate edition to be used with gorgeous @fritzcola ’ multirom 2.8.6 .
Also if they explain me how to bake it, patched with microG, i try wakelockblocker's patch for a better battery control in ‘pure’ FLOSS.
I still hope that, in this combination, some could give a try to my infamous nightly-cm11+3; while waiting for a snappy MM snapshot...
http://forum.xda-developers.com/and...kelock-blocker-official-2016-nightly-t3393825
Basics multirom tips;
-If you think something is wrong, like battery drain or excessive reboot: in twrp menu go to advanced menu then fix permissions and re-flash multirom32 on primary rom before rebooting;
-Always use ext sdcard for twrp’s copy-backup and avoid using twrp’s File Manager to restore, otherwise they could be buried and waste your mem until a complete re-format; if needed: boot in primary rom (or install a rom ZIP!) and copy them to sdcard/twrp/backup/IdDevice… with your favorite apk.
-For better efficiency use native kexeced Nameless 5.1 for primary rom.
Actually I don’t know if mmb5.1 is 100% compatible with @laufersteppenwolf ‘s Nameless 5.1_kernel.
Be aware that the smell of night roasted marshmallows is scientifically attracting werewolves.
Samsung Galaxy Tab 2
AOSP - Project
This Rom is based on AOSP to give the user a pure AOSP feeling.
The builds only includes device specific changes to compile and get a booting AOSP!
Code:
#include
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modifications, and
* if you point your finger at me for messing up your device, I will
* laugh at you.
*/
Downloads:
ROM Downloads for all supported devices can be found here
(Those who have a repartitioned system partition use "not-block-based" builds! Other builds won't be flashable on those devices!)
[#DONATETOME]
FAQ
Q: Will there be any updates?
A: Yes, there will, but only if i can fix a bug or AOSP releases an Update - else there's no update needed.
Q: There's a nice feature in XXX-Rom and i like to have this included - ADD IT!
A: Sorry, i'lll keep this Rom Stock-AOSP as possible. Maybe XXX-Rom is a better choice for you, if you really need this feature.
Q: How to enable root?
A: This Rom doesn't have root included. Why? Because root isn't part of AOSP. You can find the way to SuperSU Thread from @Chainfire and download SuperSU as flashable-ZIP if you need root.
Q: Is it possible to overclock the kernel?
A: Yes and no. First of all you need root and a Kernel-App like KernelAdiutor. After that you can slight OC the CPU & GPU - this Rom includes latest SlimLP Kernel.
Q: I found a bug.
A: Nice finding my friend Please provide needed logs - ADB will be your best friend, if you are replying in a development thread
There's a lot of tutorials out on YouTube or XDA on how to setup and use ADB - it's really simple!
At least you should tell step by step how to reproduce the issue.
I started creating a gerneral FAQ on my github - it includes instructions how to flash a Rom, how to get proper logs, etc. etc. etc., you can find it here
Changelog
Code:
2015-11-08 It's stock AOSP as released by Google (Android 5.1.1 R29 LVY48I), only additions
- screenshot: quick delete action
- advanced reboot menu
- Launcher3 instead Launcher2
- BootMessage: Show each app name being optimized during boot
- Show application's package name in the "App info" screen.
- Open app when clicking on icon in App Info screen
(... forgot about the releases between ...)
2015-08-07 based on Android 5.1.1_r9
XDA:DevDB Information
[P31xx][5.1.1] Samsung Galaxy Tab 2 AOSP-Project, ROM for the Samsung Galaxy Tab 2
Contributors
Android-Andi
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Testing
Created 2015-08-07
Last Updated 2017-04-30
Wow! Andi!
Nice to see that AOSP Lollipop came to us again! Great work dev, @Android-Andi ?
Sent from my GT-P3100 using Tapatalk
Amazing, pure LP AOSP for my tab 2.
I really appreciate it...
Is f2fs in Cache and Data supported in this ROM?
Sent from my GT-P3100 using Tapatalk
Bhaskara Rao said:
Is f2fs in Cache and Data supported in this ROM?
Sent from my GT-P3100 using Tapatalk
Click to expand...
Click to collapse
No, sry. Think it needs quite more changes than i would like to add... But i will take a closer look next time
Wow, this is awesome. Now I need to see if I can port Layers on top. Thanks Andi!!!
Sent from my Nexus 6 using Tapatalk
Thank you, Andi for the latest AOSP. No issues on clean installation. ROM is fluid. YouTube is not working. Logs attached.
Bhaskara Rao said:
Thank you, Andi for the latest AOSP. No issues on clean installation. ROM is fluid. YouTube is not working. Logs attached.
Click to expand...
Click to collapse
Thanks buddy I'll look into it next week, have some more time then
Clean install of latest AOSP (aosp_p3110-20150807.zip) with Dhollmen 3.0.101 kernel.
Youtube is working, but 720P videos do not work.
ilyichspb said:
Clean install of latest AOSP (aosp_p3110-20150807.zip) with Dhollmen 3.0.101 kernel.
Youtube is working, but 720P videos do not work.
Click to expand...
Click to collapse
Hey bruh @ilyichspb i also want to flash my kernel
I have tried but i softbricked my tab.
So,it will be great if you tell me the steps to flash a kernel.:laugh:
Aosp is smooth and lagfree.great work Andi.:fingers-crossed::good:
AFAIK Dhollmen Kernel doesn't have a fix for emmc bug. Only Android-Andi's ROMs and Recoveries have it. Take an informed decision before flashing custom kernels.
Sent from my GT-P3100 using Tapatalk
[email protected] said:
So,it will be great if you tell me the steps to flash a kernel.:laugh:
Click to expand...
Click to collapse
full wipe
install (via CWM)
AOSP
kernel
gapps
reboot
---------- Post added at 07:41 AM ---------- Previous post was at 07:39 AM ----------
Bhaskara Rao said:
AFAIK Dhollmen Kernel doesn't have a fix for emmc bug. Only Android-Andi's ROMs and Recoveries have it. Take an informed decision before flashing custom kernels.
Click to expand...
Click to collapse
Looks like you are right. I will keep an eye on that. So far everything is working fine.
Seems like google went to nightly builds, r12 source released
Thanks!, will try soon
What is the recommended recovery to install this rom. I'm still running old ketut's stock rom. Thanks
Android-Andi's latest TWRP.
https://www.androidfilehost.com/?w=files&flid=25704
Sent from my GT-P3100 using Tapatalk
Bhaskara Rao said:
Android-Andi's latest TWRP.
https://www.androidfilehost.com/?w=files&flid=25704
Sent from my GT-P3100 using Tapatalk
Click to expand...
Click to collapse
Whenevr i go to recovery i.e,twrp wipe>advance wipe>change system partition
Twrp says invalid partition select
I have tried this in both android andi's twrp and official twrp
I'm on p3100.
What to do.need help:victory:
I want to flash a rom withf2fs support thats why
[email protected] said:
Whenevr i go to recovery i.e,twrp wipe>advance wipe>change system partition
Twrp says invalid partition select
I have tried this in both android andi's twrp and official twrp
I'm on p3100.
What to do.need help:victory:
I want to flash a rom withf2fs support thats why
Click to expand...
Click to collapse
AOSP doesn't support f2fs.
About f2fs: take my twrp with "f2fs" in it's name. If you have more question about recovery then use the recovery thread pls.
Android-Andi said:
AOSP doesn't support f2fs.
About f2fs: take my twrp with "f2fs" in it's name. If you have more question about recovery then use the recovery thread pls.
Click to expand...
Click to collapse
Sorry! I got the sol of my problem
i didnt select cache and data before tapping on change partition
One question
Does Your latest recovery i,e. 2.8.7.1 supports f2fs.
i want to post this in recovery thread but xda said that u have less than 10 posts
Code:
#include <std_disclaimer.h>
/*
[COLOR="Red"]* Your warranty is now void.[/COLOR]
*
* 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 have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About
Lin·e·age
/ˈlinēij/
noun
lineal descent from an ancestor; ancestry or pedigree.
a sequence of species each of which is considered to have evolved from its predecessor.
some words of wisdom:
WIP
Latest features :
XDA:DevDB Information
LineageOS 14.1 for Falcon (WEEKLY), ROM for the Moto G
Contributors
matmutant, luca020400, LuK1337, Google, LineageOS Team, Motorola
Source Code: https://github.com/lineageos
ROM OS Version: 7.x Nougat
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2017-01-26
Last Updated 2017-02-01
Download & Install
LINKs:
All Downloads
Nightly Changelog
OpenGapps choose ARM>7.1>micro/nano/pico (micro might still be too big... unless you use the custom install options that allows you not to install everything from the package)
Either way, you might want to further customize your installation (both gapps and system apps), refer to this tutorial
REMEMBER:
ONLY use TWRP 3.0.2-1 or up
/!\ Before installing, read post #3. /!\
HOW TO INSTALL
Requirements: Unlocked Bootloader, a Nougat compatible Custom Recovery and the Downloaded Zips.
NB: as with CM14.1, with a Lollipop compatible recovery like TWRP 3.0.2-0, you will get stuck to recovery, It is MANDATORY to update to 3.0.2-1.; the following error is still present : E:unknown command [log] but will not prevent install.
Place the rom and other like Gapps on the internal Storage or on a USB OTG
Reboot to recovery using the hotkey ( PowerOff+Vol- => With Vol- Go to Recovery => Select the recovery option with Vol+ )
Do Wipes (Data, Cache, Dalvik and System partitions) if you are in a different ROM.
Select the Zips
Swipe to install (if using TWRP)
Reboot and wait 2-3 min
HOW TO DIRTY UPDATE
Same as above, without the need of wiping of reflashing gapps.
HOW TO COME FROM CM13/14?
The Best practice way is to follow the clean install way.
BUT it is also possible to update from CM13/14 using an EXPERIMENTAL data migration build.
Here are the Official recommendations :
This build will allow you to ‘upgrade’ from CM to the signed LineageOS weekly
This build may wipe permissions (you’ll have to re-allow app permissions), but should retain all user data
This build will be watermarked with an ugly banner to ensure that you don’t permanently run this EXPERIMENTAL release, and upgrade to a normal weekly after.
The process for this installation will be as follows:
Install EXPERIMENTAL migration build on top of cm-13.0 or cm-14.1 build (don’t try to install LineageOS 13.0 on top of CM 14.1, that will not work).
Reboot
Install LineageOS weekly build
Reboot
Re-setup your application permissions
Given the EXPERIMENTAL nature of this process, we are going to remove this option in two months time.
Click to expand...
Click to collapse
As Always, DO A TWRP BACKUP before trashing your device!
Notes, Bugs, and miscellaneous.
Tips and notes:
When choosing a Gapps package ensure it can fit into /system when flashed.
Nano gapps package is recommended as it fits and provides everything in a base package you will need for gapps support. Then, you can install the other google apps from the store later on if needed.
Remember nightly builds are experimental: they can and will be broken from time to time. Always have a backup at hand.
To transfer files from/to PC when plugged in you will get the charging mode prompt status in the status bar, then click it to change from charging mode to transfer files.
Considering the quite low amount of Falcon users left over here, I'm not sure about making a full-sized FAQ;
For now, the following will take that purpose:
[SIZE=+1]Q1: Question?[/SIZE]answer [SIZE=+1]Q2: How to get Root?[/SIZE]
go to : https://download.lineageos.org/extras
and choose "su (arm)" download.
It's been a long journey since I brought this device... Thank you so much Dev for supporting my 4 years old device... Downloading... LineageOS for falcon... Fingers crossed...
Long live falcon!
Great job!
Question, is there a list of what is working and not working on this rom as far as of hardware?
Thanks
Finally... Officially Supported.
thanks man.
Long live falcon and God bless the developers.
Sent from my Moto G using Tapatalk
theplagueisback said:
Question, is there a list of what is working and not working on this rom as far as of hardware?
Thanks
Click to expand...
Click to collapse
Basically, what worked on CM14.1 works on Lineage on this device, I didn't thoroughly tested it, but I didn't encounter much regressions after the migration (I performed the "Experimental" migration, to be in worse case scenario)
long live my (g)old device
ROM installed, so far so good, device performs as good as a brand new kick ass phone.
Keep up the good work!
Clean installed, seems to be good...
Someone tried if it works Xposed?
seba2907 said:
Someone tried if it works Xposed?
Click to expand...
Click to collapse
:facepalm:
seba2907 said:
Someone tried if it works Xposed?
Click to expand...
Click to collapse
Xposed is not yet available for nougat.
abeloman said:
:facepalm:
Click to expand...
Click to collapse
Sorry for not being at your senior level
BryanByteZ said:
Xposed is not yet available for nougat.
Click to expand...
Click to collapse
Thanks for your answer, I'm in cm13 and i thought it already worked for nougat
seba2907 said:
Sorry for not being at your senior level
Thanks for your answer, I'm in cm13 and i thought it already worked for nougat
Click to expand...
Click to collapse
I'm preying for that its the only thing that hold me on MM.
My 5X is dead. It's time to revive my g1
noice. falcon ftw!
Unofficial TWRP for Oneplus X (Onyx)Additional Features over Official TWRP:
AROMA compatible/supported/working
Compatible with newer EMMC models
Encryption Support
NTFS Support
Fixed Date/Time
Better In-Recovery Power Management
Decreased Boot Time
Synced with latest TWRP Patches
OREO Images/ROMs support.
No SuperSU by default.
No TWRP app.
No HTC Dumlock cruft.
Updated pigz compressor (slightly faster and more tolerant of corruption).
Green Theme by Sultanqasim.
Fixed remote wipe process (Earlier remote wipe issued from play account wasnt processed due to twrp)
Remove android reboot during password check on multiple wrong inputs.
Switched to LZMA compression to decrease size.
Faster I/O performance.
Various twrp upstream patches and fixes.
Downloads: https://www.androidfilehost.com/?w=files&flid=177316
Flashing Instructions:
Using Existing TWRP:
Reboot to recovery > Click on Install > Install Image > recovery > select recovery image and flash > reboot to recovery
Other methods:
https://twrp.me/devices/oneplusx.html
Few Points to remember:
This Recovery should only be used for flashing when you are on New Bootloader
This recovery MUST NOT be used to flash a ROM that is based on old bootloader
Using this recovery, you may break the OTA. So it is advised that you should not flash OTA with this. Rather, Download OTA zip and then flash (Only if you know what you are doing)
Credits:
> TWRP Team
Known Issues:
> Reboot on installing aroma zip for the second time without rebooting recovery or system. [workaround: reboot recovery after flashing aroma zip if you want to flash it again/twice]
Kernel Source:
https://github.com/CheckYourScreen/Arsenic.Kernel-rebased/tree/twrp
XDA:DevDB Information
[RECOVERY][AROMA][UNOFFICIAL] TWRP-3.2.1-r16, Tool/Utility for the OnePlus X
Contributors
CheckYourScreen
Source Code: https://github.com/CheckYourScreen/android_bootable_recovery
Version Information
Status: Testing
Current Stable Version: r16
Stable Release Date: 2018-01-12
Current Beta Version: r1
Beta Release Date: 2017-05-03
Created 2017-05-03
Last Updated 2018-01-12
|| Changelogs ||
r16 -
Updated to TWRP-3.2.1 source
OREO Images/ROMs support.
No SuperSU by default.
No TWRP app.
No HTC Dumlock cruft.
Updated pigz compressor (slightly faster and more tolerant of corruption).
Green Theme by Sultanqasim.
Fixed remote wipe process (Earlier remote wipe issued from play account wasnt processed due to twrp)
Remove android reboot during password check on multiple wrong inputs.
Switched to LZMA compression to decrease size.
Faster I/O performance.
Various twrp upstream patches and fixes.
r1 -
* initial release
Hi Folks!
I generally dont prefer Original Dev. Section for making threads but this one is an Exception, dont want it to get buried under pages
Here's first public beta release of twrp with working AROMA, yep thats right.
You can flash any Aroma installer zip, one minor glitch is there (mentioned in known issues) which I'll fix after my exams are over.
Dont forget to report issues here if you find any!
Reserved
Nimit the God ✌?
We owe you our lives for the recovery finally we have aroma compatibility.
P. S first post ?
Now here is my totally useful comment:
Second
But actually, great work Nimit. Thanks for the time and effort you put into making onyx great again.
Good luck with your exams
Yes to the big dev for onyx
TNX! alot @CheckYourScreen
If we meet in Delhi.. You get a treat for sure.. Thanks
Sent from my ONE E1003 using XDA-Developers Legacy app
Great work .
Great work. thank
Great work again! And thank you. Again!
thank u so much, @CheckYourScreen
Wow wow wow! Thanks dev! All the best for your exams!
Big Thanks @CheckYourScreen ... nice!
I don't want to nitpick here , but the hardware buttons aren't working.
ChzeRub said:
I don't want to nitpick here , but the hardware buttons aren't working.
Click to expand...
Click to collapse
They were disabled intentionally in official twrp and I'd like to keep them as it is, disabled.
CheckYourScreen said:
[*]AROMA compatible
Click to expand...
Click to collapse
Can you explain what this means? I'm aware of what an aroma installer is, but do I gather that they don't work with stock TWRP?
Sorry its a bit of a noob question even though I don't consider myself a noob lol.
kgr said:
Can you explain what this means? I'm aware of what an aroma installer is, but do I gather that they don't work with stock TWRP?
Sorry its a bit of a noob question even though I don't consider myself a noob lol.
Click to expand...
Click to collapse
It means aroma zips will work
Sent from my ONE E1003 using Tapatalk
kgr said:
Can you explain what this means? I'm aware of what an aroma installer is, but do I gather that they don't work with stock TWRP?
Sorry its a bit of a noob question even though I don't consider myself a noob lol.
Click to expand...
Click to collapse
Corrected, it means Aroma installer works with this recovery. All other features listed in the first post are not present in official twrp.
Hi @CheckYourScreen, do u plan on updating this to 3.1.1?