Related
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 7.x (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 14.1 on your device, or coming from another ROM?
Unlock Bootloader!
Download the zip(s).
Install Appropriate FW base (STOCK MM 4.21.40.xx base is required) simple FW update package is available at my download link
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package. Open Gapps x86 7.1
Broken Features / Known Issues
VIDEO ENCODER/DECODER ISSUES: This results in green lines on videos/pictures taken using the Intel HW encoder/decoder and other playback issues dependent on video formats. See the list below:
Snapchat: thin greeen line tends to appear on recorded videos for snapchat
Asus Pixelmaster Camera App: Super resolution mode does not work. Turning off "Optimizations" from settings clears up any green line issues.
Some video formats do not play as expected
FM Radio is unsupported.
audio is a little weird in Real Racing 3.
sim 2 cannot be disabled (this is true for all CM builds on non qualcomm hardware)
Other than Fugu (Nexus Player TV box) there are no Vendor released M x86/x86_64 builds in existance. You may experience some issues with GAPPS and some known apps not loading or working correctly. Below is a list of KNOWN apps that do not currently run on CM13 based x86 Zenfone 2 builds :
Polaris Office, Chase Mobile, Showbox...
DRM content is currently broken
Live Display (color calibration) not working yet
Screen recording not working
Chromecast screen mirroring not working, native casting works though.
factory reset from setting menu has been reported to cause recovery boot loops.
Battery life is horrible, numerous display wakelock issues
CM14 (not device specific issues)
No CMTE yet
Status bar icon changing broken
CM file manager has trouble accessing external sdcard
Battery profile is non functional/string errors
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking or ask the same question over and over again.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
As the Zenfone2 has multiple models from multiple countries please include the following information in your report:
model #
CPU Speed / RAM Size
device state when errors occur (BT/wifi/nfc on ? On a call ? sitting idle on shelf ? )
method to reproduce if you've found something consistent
Download Links
CyanogenMod for Z00A/ ze551ml: ROM
CyanogenMod for Z008/ ze550ml: ROM
Recovery Links
Z00A
MM BL compatible TWRP: TWRP
Z008
MM BL compatible TWRP: TWRP
Google apps addon:
Recommend GAPPS for now as the updated x86 gapps.
Flashable Modem updates:
FOR INFO ON MM BOOTLOADER BASED BUILDS SEE THIS POST
XDA:DevDB Information
CyanogenMod 14.1 Nightly Bulids (Z00A/Z008), ROM for the Asus ZenFone 2
Contributors
jrior001, crpalmer, say99
Source Code: https://github.com/CyanogenMod/android_kernel_asus_moorefield
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: 4.21.40.xxx stock base
Version Information
Status: Beta
Beta Release Date: 2016-11-09
Created 2016-11-09
Last Updated 2016-11-22
Reserved
Official CM-13.0 -> CM14.1 Upgrade Guide
As seen with my previous unofficial CM-13.0 builds based on the MM Stock roms, An upgrade to the MM Firmware and bootloader is required going forward.
This guide is here to assist.
1) Download ROM and 7.1 GAPPS
2) Download my Firmware Update package for Z00A or Z008 . FASTBOOT AND ADB ARE REQUIRED!
3) Follow the included instructions to update Firmware and flash the new compatible TWRP. If for some reason the new TWRP is not flashed automatically flash it manually via fastboot. "fastboot flash recovery recoverimagename.img
4) Reboot to recovery and flash CM 14 and Gapps, reboot and enjoy. Data Wipe on upgrade is not required
CM 14.1 from Stock MM
1) Unlock Bootloader
2) Flash compatible TWRP
3) Perform desired backups
4) From recovery, factory reset & install ROM & 7.1 GAPPS
5) Enjoy!
CM 14.1 from CM13 Mm based beta builds
1) Reboot to TWRP( should already have good version)
2) Flash CM14.1 and 7.1 GAPPS
3) Reboot and enjoy!!
Yes!!!
yes u made it sir.. most awaited build of the year.. we really appreciate your time and efforts given to the project.. May God bless you.. behalf of all the zf2 a big thanks to @jrior001 and @say99
Sent from my ASUS_Z008 using XDA-Developers mobile app
just a question. Do i need to be on MM Bloobs or can I upgrade straight from LP bloobs? Also has the Brazilian sensors bug been fixed on CM14.1?
leoarten said:
just a question. Do i need to be on MM Bloobs or can I upgrade straight from LP bloobs? Also has the Brazilian sensors bug been fixed on CM14.1?
Click to expand...
Click to collapse
Has this been resolved in stock? I've heard mixed reports. I've included the updated sensor firmware from the .144 stock update so if it's in there we got it.
See post 2 as I update it, gonna try trying o cover all possible situations in guide there.
Sent from my ASUS_Z00A using Tapatalk
Awesome!
Downloading...
Downloading now.
Is the camera bug still present on N? Shouldn't the MM BLOBS fix that?
Thanks for your effort, @jrior001 !!!!
Thanks.. but just to clarify.. I need to update bootloader to MM Blobbs before I install CM14 right? or just flash new TWRP and flash rom as per usual (from LP Bloobs)? Im a bit confused.. Yes I saw theres a MM Bloobs session.. but couldnt find the answer to this.
Awesome work btw
jrior001 said:
Has this been resolved in stock? I've heard mixed reports. I've included the updated sensor firmware from the .144 stock update so if it's in there we got it.
See post 2 as I update it, gonna try trying o cover all possible situations in guide there.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
leoarten said:
Thanks.. but just to clarify.. I need to update bootloader to MM Blobbs before I install CM14 right? or just flash new TWRP and flash rom as per usual (from LP Bloobs)? Im a bit confused.. Yes I saw theres a MM Bloobs session.. but couldnt find the answer to this.
Awesome work btw
Click to expand...
Click to collapse
Direct from post #2:
Official CM-13.0 -> CM14.1 Upgrade Guide
As seen with my previous unofficial CM-13.0 builds based on the MM Stock roms, An upgrade to the MM Firmware and bootloader is required going forward.
This guide is here to assist.
1) Download ROM and 7.1 GAPPS
2) Download my Firmware Update package for Z00A or Z008 . FASTBOOT AND ADB ARE REQUIRED!
3) Follow the included instructions to update Firmware and flash the new compatible TWRP. If for some reason the new TWRP is not flashed automatically flash it manually via fastboot. "fastboot flash recovery recoverimagename.img
4) Reboot to recovery and flash CM 14 and Gapps, reboot and enjoy. Data Wipe on upgrade is not required
Sent from my ASUS_Z00A using Tapatalk
Thank you very much..
jrior001 said:
Direct from post #2:
Official CM-13.0 -> CM14.1 Upgrade Guide
As seen with my previous unofficial CM-13.0 builds based on the MM Stock roms, An upgrade to the MM Firmware and bootloader is required going forward.
This guide is here to assist.
1) Download ROM and 7.1 GAPPS
2) Download my Firmware Update package for Z00A or Z008 . FASTBOOT AND ADB ARE REQUIRED!
3) Follow the included instructions to update Firmware and flash the new compatible TWRP. If for some reason the new TWRP is not flashed automatically flash it manually via fastboot. "fastboot flash recovery recoverimagename.img
4) Reboot to recovery and flash CM 14 and Gapps, reboot and enjoy. Data Wipe on upgrade is not required
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Thanks for your job, but no sensors found in brazilians devices...
ysllan said:
Thanks for your job, but no sensors found in brazilians devices...
Click to expand...
Click to collapse
Not that I can do anything about Asus's fail here but I'd like to see a logcat & dmesg captured from boot on this issue.
Sent from my ASUS_Z00A using Tapatalk
Is there Xposed for CM 14?
yumms said:
Is there Xposed for CM 14?
Click to expand...
Click to collapse
Nope right now. Just stay tuned for updates from rovo's thread.
Sent from my ASUS_Z00A using XDA Labs
jrior001 said:
Not that I can do anything about Asus's fail here but I'd like to see a logcat & dmesg captured from boot on this issue.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Did you use the 144 blobs? Asus solved problems with this version.
Enviado de meu ASUS_Z00A usando Tapatalk
I'm sorry to be a pain in the ars*. But you've mentioned you're basing on .144 stock update right? Having said that the link you posted with the zip to update bootloader Ive found files mentioning 4_21_40_134.bin (.134) wouldnt this be the reason sensors arent still working for brazilians devices? I had a look at Asus website and this is fix has been implemented on .144 update. So is this update on script and files updating bootloader or are they on the ROM itself..
Now I know the rules on XDA and I wouldnt dare to ask for ETA, however if this is the case, I would ask very politely if you could update the scripts files to .144 whenever's convenient for you and whenever you have time. That would be much appreciate. I will be coming back to this post and will be waiting anxiously for this.. Take you time and Thank you again.
jrior001 said:
Has this been resolved in stock? I've heard mixed reports. I've included the updated sensor firmware from the .144 stock update so if it's in there we got it.
See post 2 as I update it, gonna try trying o cover all possible situations in guide there.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
jrior001, crpalmer, say99 are best!)) Makes backup and installed
see, told you guys that it will be soon please take use of logcat whenever you guys are reporting some issue, we won't be able to do anything without logcat if we can't produce it on our device. Enjoy people
jrior001 said:
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 7.x (Nougat), which is designed to increase performance and reliability over stock Android for your device.
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 14.1 on your device, or coming from another ROM?
Unlock Bootloader!
Download the zip(s).
Install Appropriate FW base (STOCK MM 4.21.40.xx base is required) simple FW update package is available at my download link
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package. Open Gapps x86 7.1
Broken Features / Known Issues
VIDEO ENCODER/DECODER ISSUES: This results in green lines on videos/pictures taken using the Intel HW encoder/decoder and other playback issues dependent on video formats. See the list below:
Snapchat: thin greeen line tends to appear on recorded videos for snapchat
Asus Pixelmaster Camera App: Super resolution mode does not work. Turning off "Optimizations" from settings clears up any green line issues.
Some video formats do not play as expected
FM Radio is unsupported.
audio is a little weird in Real Racing 3.
sim 2 cannot be disabled (this is true for all CM builds on non qualcomm hardware)
Other than Fugu (Nexus Player TV box) there are no Vendor released M x86/x86_64 builds in existance. You may experience some issues with GAPPS and some known apps not loading or working correctly. Below is a list of KNOWN apps that do not currently run on CM13 based x86 Zenfone 2 builds :
Ingress, Polaris Office, Chase Mobile, Showbox...
DRM content is currently broken
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking or ask the same question over and over again.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
As the Zenfone2 has multiple models from multiple countries please include the following information in your report:
model #
CPU Speed / RAM Size
device state when errors occur (BT/wifi/nfc on ? On a call ? sitting idle on shelf ? )
method to reproduce if you've found something consistent
Download Links
CyanogenMod for Z00A/ ze551ml:ROM
CyanogenMod for Z008/ ze550ml:ROM
Recovery Links
Z00A
MM BL compatible TWRP: TWRP
Z008
MM BL compatible TWRP: TWRP
Google apps addon:
Recommend GAPPS for now as the updated x86 gapps.
Flashable Modem updates:
FOR INFO ON MM BOOTLOADER BASED BUILDS SEE THIS POST
XDA:DevDB Information
CyanogenMod 14.1 Nightly Bulids (Z00A/Z008), ROM for the Asus ZenFone 2
Contributors
jrior001, crpalmer, say99
Source Code:https://github.com/CyanogenMod/android_kernel_asus_moorefield
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: 4.21.40.xxx stock base
Version Information
Status: Beta
Beta Release Date: 2016-11-09
Created 2016-11-09
Last Updated 2016-11-09
Click to expand...
Click to collapse
haha thx so much bt wechat isnt working too haha
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
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
What's new in 3.2.2-0:
</> CHANGELOG : ? </>
Code:
Code:
* adb backup fixes
* OTA style update zips will now install automatically without prompting for decrypt
* minor tweaks to handling date/time on Qualcomm devices
* updates to some language translations
</> DOWNLOAD ? </>
https://twrp.me
$ TIP $
You can update it from previous TWRP recovery if you already have it installed, else install it as fresh by using adb or Official TWRP Installer app from google play store or similar
To flash with Fastboot/Adb:
Code:
Code:
make sure OEM-Unlocking is ON
$ adb reboot bootloader
$ fastboot flash recovery twrp-3.2.2-0-woods.img
To contribute:
TWRP Code Review
TeamWin
XDAevDB Information
Moto E4 ROMs, Kernels, Recoveries, & Other Development
Contributors
iykeDROID™ {dumbDevpr*}
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Created: 2018-07-12
Last Updated: 2018-07-13
Great news. Now I'm waiting for stable and fully working Oreo ROM and start flashing.
ka4o_pi4a said:
Great news. Now I'm waiting for stable and fully working Oreo ROM and start flashing.
Click to expand...
Click to collapse
from the looks of things on my side, i don't think that will happen in anytime too soon.
let's just hope for a God sent dev to take over the Moto E4(woods) development .
if any bug with the TWRP, create/open an issue regarding such bug on GitHub :
https://github.com/omnirom/android_bootable_recovery
( make sure to see how other issues were created and follow such trend )
thanks
I am getting a wrong architecture error (error 64 in twrp) when trying to flash ARM gapps.
EstebanxZ said:
I am getting a wrong architecture error (error 64 in twrp) when trying to flash ARM gapps.
Click to expand...
Click to collapse
wait for next update or use this at your own risk
https://t.me/motoe4woods/12179
Same here. Wrong architecture. Even the backup was corrupted and I wasn't able to flash back my stock ROM. This is my last Motorola device.
ka4o_pi4a said:
Same here. Wrong architecture. Even the backup was corrupted and I wasn't able to flash back my stock ROM. This is my last Motorola device.
Click to expand...
Click to collapse
i used it to install Both XOSP & Gapps Pico today.
Few days ago I was spent my day on trying to flash some ROM, but didn't manage to flash any (Pico,nano, micro, etc) gapps... All finished with the same error 64. Then I install last beta of twrp and successfuly install gapps, but can't boot into system (boot into recovery every time).
ka4o_pi4a said:
Few days ago I was spent my day on trying to flash some ROM, but didn't manage to flash any (Pico,nano, micro, etc) gapps... All finished with the same error 64. Then I install last beta of twrp and successfuly install gapps, but can't boot into system (boot into recovery every time).
Click to expand...
Click to collapse
please your issues on that specific ROM's thread.
As far as i know, the TWRP recovery works fine even before the unofficial beta... woods has come to it's best so far.
thanks.
Already do that. Also try with two or three different ROMs and get the same error. Doesn't matter, I'LL wait for some more stable version of twrp and some ROM.
Tks
Thanks man!
Laruzzo said:
Hi, this TWRP version to Moto E4 woods is not good.
It does not install GAPPS, and do not install SUPER SU.
With GAPPS the error is about 64 bits version. And with supersu it says that "Bad recovery no Unzip."
I tried with a unnoficial version and worked everything.
Please update in TWRP site to a new version with bug fix.
Look a this thread with the version that worked with Moto E4 woods.
https://forum.xda-developers.com/mo...rp-3-1-1-r1-port-xt1760-t3772249/post76177524
Click to expand...
Click to collapse
Dude,
learn how to read a full post with instructions & proper way of reporting an issue anywhere you find yourself.
Know you device SoC, Architecture, etc ... don't just talk any how.
also, commits has not been merged
see on gerrit.twrp.me :=> https://gerrit.twrp.me/#/c/android_device_motorola_woods/+/63/
Finally, always check to see if no one has report similar issue and been solved before you start writing sh*t into the air
https://postimages.org/
https://forum.xda-developers.com/showpost.php?p=77250466&postcount=6
NOTE : MOTO E4 SERIES IS ARM(32bit) Architecture Device, stop trying to flash/install ARM64 Gapps as you stop being dumb.
OK
Ok, I´m sorry you are the developer and I should thanks for your great work. May you please share here the alternative file that works with gapps? Because I cannot access telegram at the momment. Thank you very much and sorry again if my words was not good. I respect and admire your work.
Laruzzo said:
Ok, I´m sorry you are the developer and I should thanks for your great work. May you please share here the alternative file that works with gapps? Because I cannot access telegram at the momment. Thank you very much and sorry again if my words was not good. I respect and admire your work.
Click to expand...
Click to collapse
Download ⍖ ?
TWRP-323.0-Unofficial-woods.img
iykeDROID™ said:
TWRP is an open source, community project.
..
..iykeDROID™[/URL] {dumbDevpr*}
Source Code: https://github.com/TeamWin
[/SIZE][...his other way cause I doubt about official ¿‽
Click to expand...
Click to collapse
Abish4 said:
Format Data Partition with F2FS format is not available which is usually available with every Moto Device Kernel
Click to expand...
Click to collapse
please deal with the kernel source here : https://github.com/MotorolaMobilityLLC/kernel-mtk/tree/nougat-7.1.1-release-woods
Abish4 said:
Can you help with this other way cause I doubt about official ¿‽
Click to expand...
Click to collapse
due to negligence, you couldn't check the source code here : https://github.com/TeamWin/android_device_motorola_woods
also check the twrp site : https://twrp.me/motorola/motorolamotoe4.html
I cannot flash gapps arm 7.1.x
Hi. I have one MotoE4 XT1763 Mediatek MT6735 with unlocked bootload.
would you recommend flashing the
twrp-3.2.3-0-woods.img 15.1M
Or the
TWRP-323.0-Unofficial-woods.img 15.5M
for the Lenovo Moto E4(XT1762)
?
Thank you peoples. TWRP unofficial working fine
Hey peoples. Accidentally i wiped my system. I have a backup in pc. I dont have sd card right now. How can i put the backup wich is in pc back to TWRP backup folder in order to restore ?
LePro 3 : How to install GSI Roms, and where to find them
The point of this discussion is to alleviate the confusion of installing and configuring GSI Roms.
Although many of us would prefer to use fully native Android Pie Roms that are specifically designed for our phones, we do not yet have Official Pie Rom options, and there isn't alot of Beta options to choose from. Consequently, we get bored easily and are always searching something new.
Thankfully, GSI provides a wide range of alternative options and there's nothing wrong with experimentation and quelling our curiosities. In the end, lets just make sure that we continue to support our XDA Le Pro 3 developers, and if you can afford to do something nice for them...Please do so!
This thread is a work in progress and and intended to be a group effort, your participation is very welcome and highly appreciated
The OP will change often to add further information, or to correct inaccuracies, dead links, etc. So remember to check the OP occasionally, for updated information and links for useful add-ons or fixes.
The goal is that participants/you; share experiences, reviews, and suggestions.
In example, which GSI Roms you've tried, what was the experience like, was it worth it the time, did you use add-ons, etc.
If your installation required plugins, add-ons, fixes and what specifically did you use, PLEASE provide the link...etc.
Please don't say that you used a zip file to fix something and then not mention the name of that item.
Again, this a teamwork thread, be descriptive, it helps us understand what works and what doesn't. Be kind, share, discuss, and answer questions with patience and humility. If this is all new to you, feel feel to ask for help. [/I]
For now, I am providing the steps that I personally took to install and try several GSI Roms, See the steps below to get started and try this new GSI option for yourself.
Step 1 - Gather all needed Files
Latest Twrp : https://twrp.me/leeco/leecolepro3.html
Base Rom Currently base rom options are : Lineage 15.1 Treble, AICP 13.1 and Bootleggers ( Trebled Version)
Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Gapps 9.0 : https://opengapps.org/ (I personally use Nano, or Pico > Best to choose something small )
Lineage 15.1 Treble Build : https://forum.xda-developers.com/le-pro3/development/rom-lineageos-15-0-leeco-le-pro3-t3683720
Lineage Boot: https://mega.nz/#!uuoBiaDK!_6JlNChLg...7ZKRzCcwNI3_p0 (Can also be extracted from 15.1 or any trebled rom)
AICP 13.1 Treble version: https://forum.xda-developers.com/le-pro3/development/rom-aicp-13-0-pro3-aka-zl1-x727-x720-t3698058
Bootleggers https://forum.xda-developers.com/le-pro3/development/bootleggers-rom-x727-x720-t3838454
Preferred GSI Rom: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
BlackScreen Kernel for Oreo Base : https://androidfilehost.com/?fid=11410932744536996059
BlackScreen Kernels for Pie Base Rom : https://androidfilehost.com/?w=files&flid=285063
___________________________________________________________________________________________
Step 2 - Installation Part 1 - Automated Vendor Option - See Bottom of OP for more Manual vendor flash method
Longterm and recommended - Quick Recovery Method
******Boot to Recovery> Flash Preferred Base Rom > Flash Gapps, Flash Magisk******
1. Choose advanced wipe : Select system, Data, Cache and Dalvik Cache
2. Reboot Recovery
3. Flash Trebled Lineage or Trebled AICP ( from Links above)
4. Reboot Recovery - Flash Rom a second time.
5. Flash Gapps 8.1
6. Flash Magisk 17.1
7. Reboot to recovery, reboot to OS > Must do Basic Setup.
8. After setup - Reboot to Recovery Create full backup> Check Everything.
9. Optional save copy of Backup to PC, this will help you quickly restore the phone should you encounter any issues.
Once you have a full Backup of a your trebelized installation, you are now ready to install GSI Rom.
Some GSI Roms have Gapps included while others do not.
If you chosen GSI rom ( seems ideal) that does not have Gapps, you will need to flash Gapps 9.0
Step 3 - Installation Part 2
GSI Installation Steps
1. Reboot Recovery
2. Do a factory reset
3. Install GSI to system
4. Flash Gapps 9.0 ( if needed)
5. Flash Magisk
6. Reboot to recovery, reboot to OS > Setup GSI > Enjoy!
___________________________________________________________________________________________________________________
ADDONS and ISSUE FIXES ( Only if needed- some GSI's will not have these issues)
Safety Net Fix: https://forum.xda-developers.com/oneplus-5t/how-to/guid-bypassing-safetynet-august-t3837809
Adaptive Brightness Fix : [url]https://forum.xda-developers.com/attachment.php?attachmentid=4581000&d=1535255905
NFC Fix https://mega.nz/#F!kgdGiI6L Key: !_Gr9otePqXOX7yVLtjUxfQ ( Thanks to @ enigmatic92 and @ ademir.dias for providing a working accessible link)
Option 2 NFC Fix : Pie-NFCFix-Universal_v1.zip
Substratum Dark Mode : The Fix is simple join Substratum Beta then use a compatible Pie them
See more information here: https://forum.xda-developers.com/showpost.php?p=77651573&postcount=36
Disable Rounded Corners: https://goo.gl/CcEMzi ( Substratum add-on)
Substratum Beta through Google https://play.google.com/apps/testing/projekt.substratum
Android P dark themes : Pi Dark [substratum]
Here is a free dark overlay to get you started Pie compatible, Open Source, Signed-off-by: Harsh Shandilya
OverLay : https://mega.nz/#F!kAw1WK6I Key: !wtX2GAY2676wjGFiwNwpVg
___________________________________________________________________________________________________________________
Installation Option 2 -
Quicker install Method - You can choose to have no backup at all or save a partial recovery ( System,Root) which is very helpful to have available, if you break your installation
Step 1 - Installation Part 1
Gather your Preferred Base Rom , Gapps, Magisk
Boot to Recovery
Choose advanced wipe : Select system, Data, Cache and Dalvik Cache
Reboot Recovery
Flash Trebled Lineage or Trebled AICP ( see Links above)
Reboot Recovery - Flash Rom a second time.
No Gapps needed ( save alot of time by skipping setup)
Flash Magisk 17.1
Reboot to Recovery Create full backup> Check Everything.
( Note that you are not booting to system, this method install base and provides a recovery, to will help save time when starting over or returning to a standard Rom.)
Optional save copy of Backup to PC, this will help you quickly restore the phone should you encounter any issues.
Once you have your gappless backup of a your trebelized installation, you are now ready to install GSI Rom.
Some roms have Gapps included while others do not.
If you chosen GSI rom that does not have Gapps, you will need to flash Gapps 9.0
Step 2 - Installation Part 2
1. Reboot Recovery
2. Do a factory reset
3. Install GSI to system
4. Flash Gapps 9.0 ( if needed)
5. Flash Magisk
6. Reboot to recovery, reboot to OS > Setup GSI > Enjoy!
The steps listed above assumes that you know the fundamentals of fastboot, using TWRP recovery, etc.
Using GSI’s roms is essentially testing GSI roms, there is no guarantee, although quite a few run extremely well on many devices.
The instructions above are just guidelines, of course as per XDA policy, anything that you choose to flash is done at your own risk
Generic System Image (GSI) list
LePro 3 use type A
Here's a collection of available GSI ROMs, in order to keep it easy to choose what you want.
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Treble-Enabled Device Development
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
Project Treble
https://forum.xda-developers.com/project-treble
With any GSI Rom, if it doesn't list our phone specifically ( Zl1 or Zl0) then you use the versions Label type A or : arm64 A only
I am personally using Havoc: https://sourceforge.net/projects/hav...0.zip/download
Installing updates - Steps Needed
The Base Rom method is easier a superior to using Trembled TWRP ( for me the using regular Twrp and Base cause the system to have better stability.
To update GSI Rom
You do not need to wipe any vendor partitions.
Place the update in your downloads folder, and unpack it.
Boot to recovery,
Clear simple cache,
Flash GSI rom to system,
Clear caches
Reboot to system > finished.
If you have a bootloop [email protected] reflash lineage boot.
Troubleshooting Tips
Trouble booting/stuck in bootloop ? : Resolution here: https://forum.xda-developers.com/showpost.php?p=77668925&postcount=71
UPDATE - September 20- 2018 - Manual Vendor Method - Using Codeworks New Treble TWRP
Download : twrp-3.2.3-0-20180919-codeworkx-zl1
Install Trebled TWRP
Choose Longterm or Quick method from Above, (regarding creating a backup)
After you have your Recovery, placed unpacked GSI Rom and vendor files on your Storage Drive,
Flash GSI to System
Flash 3 Vendor files
Flash Gapps if needed
Flash Magisk 17.1
Reboot to Recovery, clear cache
Reboot to system
If you have a good suggestion, I will add it to the OP and in will give your full deserved credit
Thanks to following members for their feedback and offer to help keep this thread accurate by providing reviews and their support @rob_z11, @Ramg77, @enigmatic92, @willngg @ademir.dias @4K2K
@*.*.*.* Please do not copy this OP into another thread without providing credit a link to this OP.
So far we we know that the following Roms work on the Leeco pro 3
Benzo, version 9/1
Havoc, most recent version. : Gapps is installed separately - I have experienced no issues at all with this rom. Currently using BlackScreen 5.3. r3
AOSP Extended 9.0 v6' Per @willngg : https://forum.xda-developers.com/showpost.php?p=77652380&postcount=37
If I left anyone out of this post let me know.
If anyone tries a GSI Rom not listed above, and it boot and runs, with success, please let me know so I can update this comment.
Today I installed the latest build of [9.0] [GSI] Pixel Experience P - UNOFFICIAL.
Very good and stable rom, with the same issues of the other GSI (Nfc, mobile network setup, stock camera)
It brings less personalization than Benzo but does not have as many problems with the Gapps that it comes pre-installed.
It's PR2 and it brings September security patch.
I'm noticing that all the GSIs that I've tried so far have a sharpness and screen definition that I did not see in Oreo, it's what I think.
Link: https://forum.xda-developers.com/pr...ce-development/9-0-pixelexperience-p-t3833294
Ramg77 said:
Today I installed the latest build of [9.0] [GSI] Pixel Experience P - UNOFFICIAL.
Very good and stable rom, with the same issues of the other GSI (Nfc, mobile network setup, stock camera)
It brings less personalization than Benzo but does not have as many problems with the Gapps that it comes pre-installed.
It's PR2 and it brings September security patch.
I'm noticing that all the GSIs that I've tried so far have a sharpness and screen definition that I did not see in Oreo, it's what I think.
Link: https://forum.xda-developers.com/pr...ce-development/9-0-pixelexperience-p-t3833294
Click to expand...
Click to collapse
I fully agree!
tsongming said:
So far we we know that the following Roms work on the Leeco pro 3
Benzo, version 9/1
Havoc, most recent version. : Gapps is installed separately - I have experienced no issues at all with this rom. Currently using BlackScreen 5.3. r3
If I left anyone out of this post let me know.
Click to expand...
Click to collapse
First things first, excellent work with the guide step by step, very complete.
I add to the information that there is a new version of Benzo (0912) but it was very difficult to install because the Gapps that are preinstalled have a conflict with the Google Play Store, once all the steps are finished and before starting the first boot of the system , the protection of Google (factory reset protection or FRP) must be removed by means of a PC program, otherwise the initial setting will not go beyond "Searching for Updates". How I said the installation of this Rom is complicated.
Finally in XDA as in the Russian forum 4PDA I read that is about to come out a patch to run the NFC in the GSI Android Pie Roms, hopefully so.
Informative post! Aosip has been treblized too, have not tried it as a base however.
Ace42 said:
Informative post! Aosip has been treblized too, have not tried it as a base however.
Click to expand...
Click to collapse
Thanks,
I am using AICP as a base for Havoc with the boot.img from lineage and Blackscreen 5.3.r3 .
Its a flawless installation, Gapps is installation separately the gapps issue that some GSI Roms bring is avoided completely.
Sound quality, Call Quality, Battery life all excellent. Plus, I have installed all of my usual Magisk mods (alot!) without breaking the install.
Ramg77 said:
First things first, excellent work with the guide step by step, very complete.
I add to the information that there is a new version of Benzo (0912) but it was very difficult to install because the Gapps that are preinstalled have a conflict with the Google Play Store, once all the steps are finished and before starting the first boot of the system , the protection of Google (factory reset protection or FRP) must be removed by means of a PC program, otherwise the initial setting will not go beyond "Searching for Updates". How I said the installation of this Rom is complicated.
Finally in XDA as in the Russian forum 4PDA I read that is about to come out a patch to run the NFC in the GSI Android Pie Roms, hopefully so.
Click to expand...
Click to collapse
Yes, its the 0901 version that has no issues, right?
I only tried the 09/12 version, after seeing your post. and prior to that I was on two separate versions of miui GSI. and 2 versions of P beta
The Miui 10 Oreo version will be excellent once its display bugs are worked out.
tsongming said:
Yes, its the 0901 version that has no issues, right?
I only tried the 09/12 version, after seeing your post. and prior to that I was on two separate versions of miui GSI. and 2 versions of P beta
The Miui 10 Oreo version will be excellent once its display bugs are worked out.
Click to expand...
Click to collapse
That's right, the 0109 is the stable version of Benzo.
Against my principles I passed Antutu to the Pixel Experience 9 that I am testing and it gave me a very good score although I still seem that Android 9 offers the best user experience on this phone and Antutu does not reflect that.
Edit: The phone did not raise temperature while running the Antutu tests.
Incredible work @tsongming!! You are a fine machine....
tsongming said:
Thanks,
I am using AICP as a base for Havoc with the boot.img from lineage and Blackscreen 5.3.r3 .
Click to expand...
Click to collapse
Do you still need the lineageOS boot.img if you're using blackscreen?
Plan on flashing GSI soon. Really appreciate your instructions as they will help me and many others.
tsongming said:
LePro 3 : How to install GSI Roms, and where to find them
The point of this discussion is to alleviate the confusion of installing and configuring GSI Roms.
Although many of us would prefer to use a fully native Android P Rom that is specifically designed for our phones, we do not currently have alot of native options.. In consequence, we get bored easily and are often ready to try something new.
Thankfully, we have options, and there's nothing wrong with experimentation and quelling our curiosities. Lets just make sure that we continue to support our own Le Pro 3 developers, and if you can afford it, do something nice for them
This thread is a work in progress and a group effort, your participation is very welcome and highly appreciated
The OP will change to add or change to add further information or correct inaccuracies. So check the OP occasionally.
The goal here is that all participants/ you to share experiences, reviews, and suggestions. I.E : which GSI Roms have you tried , what was your experience, was it worth it, did you use addons, if so what, can you provide the link...etc. or add ons that they have tried. This should be fun!
For now, I am providing the steps that I personally took to install and try several GSI Roms, See the steps below to try it for yourself..
Step 1 - Gather all needed Files
Latest Twrp : https://twrp.me/leeco/leecolepro3.html
Base Rom Currently two options Lineage 15.1 Treble and AICP Treble version
Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Gapps 9.0 : https://opengapps.org/ (I personally use Nano, choose something small )
Lineage 15.1 Treble Build : https://sourceforge.net/projects/lin...1.zip/download
Lineage Boot: https://forum.xda-developers.com/att...9&d=1536591029 Can be used with AICP as well.
AICP Treble version: https://forum.xda-developers.com/showpost.php?p=77596157&postcount=4898
Preferred GSI Rom: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
BlackScreen 5.3.r3 : https://forum.xda-developers.com/showpost.php?p=77596092&postcount=540
ISSUE Resolutions Files
Safety Net Fix: https://forum.xda-developers.com/oneplus-5t/how-to/guid-bypassing-safetynet-august-t3837809
Step 2 - Installation Part 1
Longterm ( recommended - Quick Recovery Method)
******Boot to Recovery> Flash Preferred Base Rom > Flash Gapps, Flash Magisk******
1. Choose advanced wipe : Select system, Data, Cache and Dalvik Cache
2. Reboot Recovery
3. Flash Trebled Lineage or Trebled AICP ( from Links above)
4. Reboot Recovery - Flash Rom a second time.
5. Flash Gapps 8.0
6. Flash Magisk 17.1
7. Reboot to recovery, reboot to OS > Must do Basic Setup.
8. After setup - Reboot to Recovery Create full backup> Check Everything.
9. Optional save copy of Backup to PC, this will help you quickly restore the phone should you encounter any issues.
Once you have a full Backup of a your trebelized installation, you are now ready to install GSI Rom.
Some GSI Roms have Gapps included while others do not.
If you chosen GSI rom ( seems ideal) that does not have Gapps, you will need to flash Gapps 9.0
Step 3
GSI Installation Steps
1. Reboot Recovery
2. Do a factory reset
3. Install GSI to system
4. Flash Gapps 9.0 ( if needed)
5. Flash Magisk
6. Reboot to recovery, reboot to OS > Setup GSI > Enjoy!
___________________________________________________________________________________________________________________
Option 2 - Step 1
Quicker install Method - You can choose to have no backup at all or save a partial recovery ( System,Root) which is very helpful to have available, if you break your installation
Step 1
Gather your Preferred Base Rom , Gapps, Magisk
Boot to Recovery
Choose advanced wipe : Select system, Data, Cache and Dalvik Cache
Reboot Recovery
Flash Trebled Lineage or Trebled AICP ( see Links above)
Reboot Recovery - Flash Rom a second time.
No Gapps needed ( save alot of time by skipping setup)
Flash Magisk 17.1
Reboot to Recovery Create full backup> Check Everything. ( Note that you are not booting to system, this method install base and provides a recovery, to will help save time when starting over or returning to a standard Rom.)
Optional save copy of Backup to PC, this will help you quickly restore the phone should you encounter any issues.
Once you have your gappless backup of a your trebelized installation, you are now ready to install GSI Rom.
Some roms have Gapps included while others do not.
If you chosen GSI rom that does not have Gapps, you will need to flash Gapps 9.0
Step 2
1. Reboot Recovery
2. Do a factory reset
3. Install GSI to system
4. Flash Gapps 9.0 ( if needed)
5. Flash Magisk
6. Reboot to recovery, reboot to OS > Setup GSI > Enjoy!
The steps listed above assumes that you know the fundamentals of fastboot, using TWRP recovery, etc.
Using GSI’s roms is essentially testing GSI roms, there is no guarantee, although quite a few run extremely well on many devices.
The instructions above are just guidelines, of course as per XDA policy, anything that you choose to flash is done at your own risk
Generic System Image (GSI) list
LePro 3 use type A GSI
Here's a collection of available GSI ROMs, in order to keep it easy to choose what you want.
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Treble-Enabled Device Development
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
Project Treble
https://forum.xda-developers.com/project-treble
Thanks to following members for their feedback and offer to help keep this thread accurate by providing reviews and their support
@rob_z11, @ Ramg77, @DrMyrkurs
Click to expand...
Click to collapse
Excellent job.
Thanks for your contribution and dedication for the our device.
Enviado de meu LEX720 usando o Tapatalk
Hi
Ramg77 said:
First things first, excellent work with the guide step by step, very complete.
I add to the information that there is a new version of Benzo (0912) but it was very difficult to install because the Gapps that are preinstalled have a conflict with the Google Play Store, once all the steps are finished and before starting the first boot of the system , the protection of Google (factory reset protection or FRP) must be removed by means of a PC program, otherwise the initial setting will not go beyond "Searching for Updates". How I said the installation of this Rom is complicated.
Finally in XDA as in the Russian forum 4PDA I read that is about to come out a patch to run the NFC in the GSI Android Pie Roms, hopefully so.
Click to expand...
Click to collapse
I've been running benzo without major problems for days.i updated to 9/12 with no problems.only new prob I found in the update is the mobile network is inaccessible from settings but 3rd party app can access it.no prob with gapps running.no play store issues either.great rom so far.cant wait to try havoc and a few others. Cool thread,thanks.
https://forum.xda-developers.com/le...ject-treble-lepro3-x72x-t3820844/post77636757
This is to fix adaptive brightness
Ascertion said:
Do you still need the lineageOS boot.img if you're using blackscreen?
Plan on flashing GSI soon. Really appreciate your instructions as they will help me and many others.
Click to expand...
Click to collapse
Probably not since Blackscreen overwrites the boot. When I first tried installing GSI's, I was only successful after using the Lineage boot, and the treble Black Screen had not been released yet.
rob_z11 said:
https://forum.xda-developers.com/le...ject-treble-lepro3-x72x-t3820844/post77636757
This is to fix adaptive brightness
Click to expand...
Click to collapse
Thanks, I added it to the OP
Good work with the guide mate
Thank you for this in-depth summary.
Here is my Antutu for the Havoc GSI
Sent from my LEX727 using XDA Labs
I flashed latest aex pie yesterday.just ran it for few hours.everything worked good and fast minus the usual nfc,and few settings arent complete but runs smooth and stable.moved back to latest benzo just cause it's more complete.but aex is still a great option.love options.lol
Havoc 3.0 Q gsi fixed build for Huawei P10 Lite
About
Originally Havoc 3.0 Q gsi based on v204 compiled by ExpressLuke , but for Hi6250 some bugs persist , so I managed to fix them and repacked the IMG then highly compressed.
Fixed
* Camera * media ( sound , video , YouTube ..) * NFC * battery usage * auto brightness * phone Info's ( build number , model , manufacturer , device name .. ) * added Havoc bootanimation .
Bugs
* Offline charging ( requires permissive kernel , Labyrinth kernel 2.0 by Dil3mm4 tested * Blurry can be fixed in phh treble settings > Huawei features > 3rd option ( disabling hwcomposer ).
Installation
* Extract img from xz archive * go to TWRP and do a full wipe (system, data, cache, dalvik/art cache) * flash the image in system image partition * flash root (optional) NOTE1: If you are coming from Android 9 flashing root is a MUST DO ! NOTE2: Flash only the Magisk zip linked in this post ! * reboot to System * reboot to TWRP * flash gapps (optional) * Enjoy !!!
Download
https://mega.nz/#!2S4xxQ6C!f0KJlCA_9_yyJzWZAtlNYVJHktSuyyFY7p82kXK4caM
Twrp recommended ( by @Pretoriano80 ):
https://mega.nz/#!LLhBXSzY!3runNNoW9z1tOHSu-heIUhyy-4u8XHvc8rZMsn547so
Magisk.phh:
https://mega.nz/#!uX4k1KjS!2gnUV3IyLt8XXf4NO3RyZEJnt5YNJQ8tY9i11oGfKYM
Credits: @phhusson ExpressLuke @haky 86 @DarkJoker360 @Dil3mm4
Regards!
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Emui 8.x,bootloader unlocked and TWRP
Based On: AOSP
Version Information
Status: Stable
Created 2019-12-01
6 hrs SoT
Hami_Do said:
6 hrs SoT
Click to expand...
Click to collapse
Wow that's really impressive for a 3000 mAh device! Many people aren't getting that on the Note 10 Plus!
Hi! Thats nice, so basically Is a Kirin gsi? Are gapps included?
TureX said:
Hi! Thats nice, so basically Is a Kirin gsi? Are gapps included?
Click to expand...
Click to collapse
No, it's simply Havoc GSI with several fixes included especially for our device/platform and no, gapps are not included (you would have known if you read the first post more carefully )
TureX said:
Hi! Thats nice, so basically Is a Kirin gsi? Are gapps included?
Click to expand...
Click to collapse
For gapps , pico worked for me as it should , from here :
https://sourceforge.net/projects/opengapps/files/arm64/beta/20191114/
Hami_Do said:
For gapps , pico worked for me as it should , from here :
https://sourceforge.net/projects/opengapps/files/arm64/beta/20191114/
Click to expand...
Click to collapse
Hi! I Guess for Who hasn't a working twrp Is not possible to flash gapps. Thanks for your work and sorry for my english
TureX said:
Hi! I Guess for Who hasn't a working twrp Is not possible to flash gapps. Thanks for your work and sorry for my english
Click to expand...
Click to collapse
the suggested twrp in first post works perfectly on most hi6250 ( emui 8 ) , plus it has an option ( exclude OEM path from data wipe ) from there you don't need to format data & internal storage to boot any gsi/dssi AFAIK.
Only sometimes installing gapps requires resize system from advanced wipe menu.
thanks.. any build for havoc 2.9 ?
How can I remove the bottom pad that appears when I want to use the keyboard?
itsm03 said:
thanks.. any build for havoc 2.9 ?
Click to expand...
Click to collapse
the best 2.9 build here:
https://sourceforge.net/projects/ha...90912-phhgsi_arm64_a-Official.img.xz/download
1- wipe system data cache
2-flash havoc 2.9 and boot up to system
3- reboot to twrp and :
4- flash offline charger fix for pie
5- flash nfc patch for pie
6- flash hwcomposer ( follow instructions )
7- flash gapps and magisk ( optional )
Enjoy.
All flashable patches you find them here:
https://forum.xda-developers.com/p10-lite/how-to/gsis-manual-fixes-hi6250-devices-t3936745
ghassan haddad said:
How can I remove the bottom pad that appears when I want to use the keyboard?
Click to expand...
Click to collapse
Join https://t.me/hi6250group telegram group , there you can share your screenshots to understand the issue.
Hami_Do said:
Join https://t.me/hi6250group telegram group , there you can share your screenshots to understand the issue.
Click to expand...
Click to collapse
I Couldn't post pictures since new members need to wait, add to that I got only one answer telling me that it may not be possible.
I was referring to this pad in the picture
Now Gsi's based on v207 and later are stable , here you find latest Havoc Q gsi :
https://sourceforge.net/projects/expressluke-gsis/files/HavocOS/Ten/ARM64/A/
Probably only NFC patch is needed :
https://forum.xda-developers.com/p10-lite/how-to/gsis-manual-fixes-hi6250-devices-t3936745/page3
=========
No way to boot on my phone (WAS-LX1A)...stuck on boot, after some minutes its reboot, other minutes and then goes in erecovery.
I tried also a totally clean install starting with last firmware stock (WAS-LX1AC432B390) install (dload method) and then flashing Havoc 3.0 (based on v207) system file from fastboot.
Nothing to do and I came back beaten to Android 8.0
.....any help pls?
or maybe it is easier to buy a P30 lite
Tx
Toti
Achieve is currupt :-/
i get Error while flashing image, here is the log
Erro 255
I get error while flashing image here is the log
I have the saame problem on WAS-LX1
anvetoti said:
No way to boot on my phone (WAS-LX1A)...stuck on boot, after some minutes its reboot, other minutes and then goes in erecovery.
I tried also a totally clean install starting with last firmware stock (WAS-LX1AC432B390) install (dload method) and then flashing Havoc 3.0 (based on v207) system file from fastboot.
Nothing to do and I came back beaten to Android 8.0
.....any help pls?
or maybe it is easier to buy a P30 lite
Tx
Toti
Click to expand...
Click to collapse
Any help?
Help this guy and me, please!
From my experience with flashing this device it is most likely that either your device is still encrypted or there are magisk leftovers or data partition wasn't wiped correctly, that's causing rom not to boot. And always use pretoriano's twrp_0.5_test, works best. Sometimes it boots to erecovery, but you can try to reboot and it might work then.
NeoPreacher said:
From my experience with flashing this device it is most likely that either your device is still encrypted or there are magisk leftovers or data partition wasn't wiped correctly, that's causing rom not to boot. And always use pretoriano's twrp_0.5_test, works best. Sometimes it boots to erecovery, but you can try to reboot and it might work then.
Click to expand...
Click to collapse
I think you're right, I also think it's due to encryption or data partition (not magisk because I made a clean installation), because I had the same problem, stuck on boot, with all the Roms (PIE and Q) that require TWRP.
The only rom without problems was OpenKirin-OmniROM Pie Alpha 6.2 which does not require a custom recovery for installation !!
Do you have any operational suggestions to give me or I just have to try with pretoriano's twrp_0.5_test ??
What do you think if :
- In a stock recovery I do a factory reset
- From fastboot I do fastboot erase system, userdata and cache (or better to use format command for userdata?)
- the I flash system.img
- then I flash TWRP
- and then install magisk and gapps from TWRP?
TX