Related
Hello everyone, first of all I'm not a developer I just compiled the sources of the team ARMv6 with some optimizations.
To install the rom is required TLS recovery.
I and XDA aren't responsible for damage to the device
Features
*JustArchi's optimizations http://forum.xda-developers.com/showthread.php?t=2754997
*UberGCC 6.0 https://plus.google.com/+ChetKener/posts/YzMJEkzPQgp
*graphite optimizations
*kernel build with -Ofast flag for more performance
*rom/kernel build with java 7 for more performance
*kernel 3.0.x
I do not have a galaxy ace so I can not test the same for developed rom for galaxy mini works very well
If anyone is interested and wants to help in the development please let me contact
Download
http://www.mediafire.com/download/wd46m8ad51at2bz/cm-11-20150720-UNOFFICIAL-cooper.zip
reservates
Installed, as soon as the first boot ends and the google setup begins, the phone resets and then boot loop.
Taxogger said:
Installed, as soon as the first boot ends and the google setup begins, the phone resets and then boot loop.
Click to expand...
Click to collapse
soon new version with bug fixed
Mata99 said:
soon new version with bug fixed
Click to expand...
Click to collapse
The problem is still there. Please fix it. Thanks.
tranphu said:
The problem is still there. Please fix it. Thanks.
Click to expand...
Click to collapse
Just checked the zip file. Looks like GAPPS and Setup Wizard wasn't included, why there's Google Setup Wizard on boot?
BTW I'm now making backup of my current ROM, about to flash in a short while.
Edit : Just Flashed, bootloop
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
Hi everyone,
Im presenting to you the universal goodix patch for every android n rom for kate and kenzo . The point of this patch is patching ramdisk for goodix properly and making those changes directly to roms' own boot.img so you dont have to flash any other rom boot.img seperatly and thats why volte will be still there but you still have to flash a custom kernel which support goodix fp. Actually the point is i can give you no bootloop guarantee. By the way im a totally noob so dont give me a hard time
Credits goes to @jhenrique09 and @nicknitewolf
Flashing Instructions:
ROM -> GApps -> Patch -> Kernel which support goodix fp
Goodix Patches:
Goodix_Patch_Citrus
Goodix_Patch_CosmicOS
Goodix_Patch_AOSIP
PS: If you want patch for another rom. Please just simply post the boot.img of the rom which is you are going to flash. I will be adding the others.
scrubjay55 said:
Hi everyone,
Im presenting to you the universal goodix patch for every android n rom for kate and kenzo . The point of this patch is patching ramdisk for goodix properly and making those changes directly to roms' own boot.img so you dont have to flash any other rom boot.img seperatly.
But you still have to flash a custom kernel which support goodix fp. Actually the point is i can give you no bootloop guarantee. By the way im a totally noob so dont give me a hard time
Credits goes to @[email protected]
Flashing Instructions:
ROM -> GApps -> Patch -> Kernel which support goodix fp
Goodix Patches:
Goodix_Patch_Citrus
PS: If you want patch for another rom. Please just simply post the boot.img of the rom which is you are going to flash. I will be trying to add the others.
Click to expand...
Click to collapse
Thank you:good:
Thanks.
why we need 100 variations of one patch? there is universal patch that works on any (or any lineage based) ROM, attached it below. flash this patch, flash custom kernel with Goodix support, that's all.
you wasting your time, tho
thegreatn_ said:
why we need 100 variations of one patch? there is universal patch that works on any (or any lineage based ROM), attached it below. you wasting your time, tho
Click to expand...
Click to collapse
This patch flashes a different rom's boot.img so it may give you bootloop because of ramdisk differences but mine just modify it. Even if it boots, there will be bugs.
I was thinking the same thing and umang96 answered:
Umang96 said:
Every rom has little different ramdisk, if you flash boot.img of one rom on another then most probably you will have bootloop or even if you boot you might face bugs.
Click to expand...
Click to collapse
scrubjay55 said:
This patch flashes a different rom's boot.img so it may give you bootloop because of ramdisk differences but mine jsut modify it.
Click to expand...
Click to collapse
ok, got it, thx
Good work！Thanks！
Pzqqt said:
Good work！Thanks！
Click to expand...
Click to collapse
Glad to hear that
Thanks mate ?
Haven't tried it, but thanks for the effort ill feedback later
@scrubjay55 Can you do LOS please? Here's latest nightly boot.img
https://www.dropbox.com/s/9b8p1fwnyjis0oj/boot.img?dl=0
vkass said:
@scrubjay55 Can you do LOS please? Here's latest nightly boot.img
https://www.dropbox.com/s/9b8p1fwnyjis0oj/boot.img?dl=0
Click to expand...
Click to collapse
It is done and in the op.
This works great. Thanks.
los is lineage os?
ShOgIBaRiBoA said:
los is lineage os?
Click to expand...
Click to collapse
Yes it is.
scrubjay55 said:
Hi everyone,
Im presenting to you the universal goodix patch for every android n rom for kate and kenzo . The point of this patch is patching ramdisk for goodix properly and making those changes directly to roms' own boot.img so you dont have to flash any other rom boot.img seperatly.
But you still have to flash a custom kernel which support goodix fp. Actually the point is i can give you no bootloop guarantee. By the way im a totally noob so dont give me a hard time [emoji14]
Credits goes to @jhenrique09 and @nicknitewolf
Flashing Instructions:
ROM -> GApps -> Patch -> Kernel which support goodix fp
Goodix Patches:
Goodix_Patch_Citrus
Goodix_Patch_CosmicOS
Goodix_Patch_LOS
PS: If you want patch for another rom. Please just simply post the boot.img of the rom which is you are going to flash. I will be adding the others.
Click to expand...
Click to collapse
Please make it RR Nightly goodix too. Thanks for this.
Sent from my Redmi Note 3 using Tapatalk
@scrubjay55
Darekness redefined
Xenon hd
Aosip
Great job ??
Here is boot.img from latest RR nightly
https://drive.google.com/file/d/0B9x7vid3MSMbRGYzTThVVnM5V0k/view?usp=drivesdk
febry_valdy said:
Please make it RR Nightly goodix too. Thanks for this.
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
Tuxedo_20 said:
Here is boot.img from latest RR nightly
https://drive.google.com/file/d/0B9x7vid3MSMbRGYzTThVVnM5V0k/view?usp=drivesdk
Click to expand...
Click to collapse
Done and in the OP. :fingers-crossed:
najafi.ali.68 said:
@scrubjay55
Darekness redefined
Xenon hd
Aosip
Great job
Click to expand...
Click to collapse
Patch for AOSIP is here :fingers-crossed:
Self-made TWRP 3.2.3-0 recovery for MIX 2S
It's official now!
Please go to https://twrp.me/xiaomi/xiaomimimix2s.html to download.
Updates:
v15 (2019-01-09):
Built against latest omni-9.0 tree and lineage-16.0 polaris kernel
This should fix the decryption issue on android 9.0 roms with 2019-01 security patches. If v14 works for you, then no need to flash this.
v14 (2018-12-09):
Built against latest omni-9.0 tree
This should fix the decryption issue on latest android 9.0 roms. If v13 works for you, then no need to flash this.
v13 (2018-11-21):
Fixed wiping issue
v12 (2018-11-16):
Built against latest omni-9.0 tree
This should fix the decryption issue on latest android 9.0 roms. If v11 works for you, then no need to flash this.
v11 (2018-10-12):
Built against latest omni-9.0 tree
This should fix the decryption issue on latest android 9.0 roms
v10 (2018-09-25):
Fixed wiping issue
v9 (2018-09-24):
Built against omni-9.0 tree, updated blobs from MIUI 10 Pie
Fixed android 9.0 decryption
NOTE: If you are on android 8.0/8.1, please use v8, I don't know if v9 would work with oreo
v8 (2018-08-03):
Synced with latest twrp code, version number now 3.2.3-0
v7 (2018-07-20):
Updated kernel and blobs to MIUI 10 8.7.19, fixed the non-booting issue after 8.7.16. Thanks for @simonsmh for fixing!
Synced with latest twrp code, version number now 3.2.2-0
Re-enabled MTP mode. If you have problems like crashing, please detach your device from usb.
v6 (2018-06-09):
Fixed wrong color in screenshots (thanks @wzsx150 for reporting)
Disabled USB MTP mode.
Note: This version has disabled USB MTP mode to take a try to fix the non-responsive problem as @TimesLeader suggested. If you need MTP feature, please stick to v5 and wait for TWRP fixing it.
v5 (2018-06-06):
Synced with latest omni and TWRP code (git-25b850d to git-ff9d097).
touch vibration now works.
removed the TW_BLANK_SCREEN_ON_BOOT option.
note: If you encountered the non-responsive problem, please try to get me some logs (adb logcat, dmesg, etc). Reboot will recover from it.
v4 (2018-06-03):
Synced with latest TWRP code (git-72638b6 to git-bf4f24f, reverted 34ad728).
Thanks @simonsmh for various fixes and cleanups!
v3 (2018-05-26):
No longer laggy UI! Thanks TWRP for their fix!
Also thanks @joemossjr for a stuck-in-blank-screen problem.
v2 (2018-05-21):
Fixed the keystore problem. Now you can safely decrypt the /data partition.
Disclaimer:
Use this at your own risk!
Works:
ADB
Decryption of /data
Screen brightness settings
Smooth UI
Touch vibration
Usage:
Reboot to fastboot mode (unplug, poweroff, vol-dn+power until fastboot appears), then execute:
fastboot boot recovery.img
If your phone got stuck in "Downloading boot.img...", just reboot phone (long press power button) and try again.
Flash to recovery partition (thanks for @sytayeth for testing):
fastboot flash recovery recovery.img
Source code and compile guide:
https://github.com/notsyncing/android_device_xiaomi_polaris
v15 Download: https://drive.google.com/open?id=10jqnlc0sVv0oWH2hYkxUglO5QhJwmnQd
sha256: 508695c7b82933c413cf6521a3deb1b012fe34e155ebf21d2a6f2e69338e9ce4
md5: baf3fa355339e0574b95897ec6a961a7
v14 Download: https://drive.google.com/open?id=1Mhe0BF613HGWwt1gc_95vuXB-ETci6sb
sha256: 16a977900abf77dedf75195239f122e0368d512ba9feb7fe0803823a3585c607
md5: bbb2b7054cd52b72326bf2c39188ebe2
v13 Download: https://drive.google.com/open?id=1nzqC1gKeI-XogjcUX4ZURz0OUT9Rshcg
sha256: dc4c37fdeeaa2a12de9c54c292f0275de02497b0ec0866dca254b625fbc494a7
md5: 404b9d4f22fa22d862c7b60db9d933bc
v8 Download: https://drive.google.com/open?id=1Ge3WuWjjKoHWPIe9jvCtK2kGihHDE8Pm
v8 recovery.img:
sha256: 12b864620650ce55efa9971be89c14eb497cc9ca65cea2e5cee3d5e7b623bb9e
md5: 6c55b55b6408111e9b8bbc50b4364317
Thanks:
@Travismills82 for his TWRP tree used as skeleton: https://github.com/travismills82/twrp_android_device_samsung_star2qltechn
@teamwin for sagit TWRP tree used for partial decryption works: https://github.com/TeamWin/android_device_xiaomi_sagit
@TimesLeader for dipper TWRP tree used for adb works:android_device_xiaomi_dipper
@wuxianlin for enchilada TWRP tree used for init.rc works:android_device_oneplus_enchilada
Do you think this recovery can be flashed from the other one that we have???
Sorry, I just read now that it's not tested.
Cool thx!
why does it so lag?lol
sytayeth said:
Do you think this recovery can be flashed from the other one that we have???
Sorry, I just read now that it's not tested.
Click to expand...
Click to collapse
it should work, but I didn't try it, because on reboot it will be replaced by MIUI recovery
ghost_nup said:
why does it so lag?lol
Click to expand...
Click to collapse
Yes, it lags, but at this moment, I don't know why and have no clue to resolve it
notsyncing said:
Yes, it lags, but at this moment, I don't know why and have no clue to resolve it
Click to expand...
Click to collapse
The one posted in xiaomi.eu thread lags too, there it has not been resolved until now too
Cool!
Sorry but this is exactly the same posted with almost the release of the phone. You stating you made it yourself?
Puksom said:
Sorry but this is exactly the same posted with almost the release of the phone. You stating you made it yourself?
Click to expand...
Click to collapse
The other release doesn't support /data decryption
notsyncing said:
it should work, but I didn't try it, because on reboot it will be replaced by MIUI recovery
Click to expand...
Click to collapse
Yes, It works.
martepato said:
The other release doesn't support /data decryption
Click to expand...
Click to collapse
Thank you, after my test, you can indeed confidential data partition.
im trying to build it from your source but it just stays at a black screen
joemossjr said:
im trying to build it from your source but it just stays at a black screen
Click to expand...
Click to collapse
You could try adb logcat to see if adb started.
Is there any screen flashing? or just black screen?
Also, check the TARGET_RECOVERY_PIXEL_FORMAT workaround on README, or you could experience black screen with flashing.
Can you hit me up on Hangouts? I have made 20 builds today all with the same problem lol my email is [email protected]
---------- Post added at 04:28 AM ---------- Previous post was at 04:27 AM ----------
It's just a black screen adb does start tho
joemossjr said:
Can you hit me up on Hangouts? I have made 20 builds today all with the same problem lol my email is [email protected]
---------- Post added at 04:28 AM ---------- Previous post was at 04:27 AM ----------
It's just a black screen adb does start tho
Click to expand...
Click to collapse
sent you a message on hangout, please check it
New twrp in the op
joemossjr said:
New twrp in the op
Click to expand...
Click to collapse
Thank you so much. Really appreciate your work.
joemossjr said:
New twrp in the op
Click to expand...
Click to collapse
Thanks for your work, this is really helpful.
It's noty work it's the ops work. I just helped with the black screen issue and laggy twrp
Hey guys,
i made a test build from lineageos 17.0 for prague.
if you want to test and give some log to me download https://androidfilehost.com/?fid=4349826312261611324 this build
backup your current rom including /vendor partition.
then wipe /system, /data and /vendor partition.
flash my Rom and then if it's not boot please send me sys/fs/pstore/console-ramoops
my source: https://github.com/feroxx
Bootloop on p10 lite , no possibility for logs even under sys/fs/pstore.
Sorry but it seems many files are missed in vendor of this build.
Hami_Do said:
Bootloop on p10 lite , no possibility for logs even under sys/fs/pstore.
Sorry but it seems many files are missed in vendor of this build.
Click to expand...
Click to collapse
Which files are missing in vendor?
feroxxx said:
Which files are missing in vendor?
Click to expand...
Click to collapse
Compared to stock vendor many folders are missing :
vendor/etc/Bluetooth/
vendor/etc/camera/
vendor/etc/cellular_cloud/
vendor/etc/dhcpcd/
vendor/etc/gnss/
vendor/etc/ikedconfig/
vendor/etc/modemConfig/
vendor/etc/xml/
vendor/usr/
vendor/phone.prop
Maybe others
-------------------+
And about your build :
compatibility_matrix.xml & manifest.xml which are in separate zip don't install correctly in system nor in vendor
--------------------+
That was just an opinion
Best regards
Hami_Do said:
Compared to stock vendor many folders are missing :
vendor/etc/Bluetooth/
vendor/etc/camera/
vendor/etc/cellular_cloud/
vendor/etc/dhcpcd/
vendor/etc/gnss/
vendor/etc/ikedconfig/
vendor/etc/modemConfig/
vendor/etc/xml/
vendor/usr/
vendor/phone.prop
Maybe others
-------------------+
And about your build :
compatibility_matrix.xml & manifest.xml which are in separate zip don't install correctly in system nor in vendor
--------------------+
That was just an opinion
Best regards
Click to expand...
Click to collapse
Actually i want to see lineageos 17.0 boots on prague. After successful boot i can fix issues. i will edit rootdir folder a bit for booting. thanks a lot
https://androidfilehost.com/?fid=4349826312261612961
i made a new build. you can test now
feroxxx said:
https://androidfilehost.com/?fid=4349826312261612961
i made a new build. you can test now
Click to expand...
Click to collapse
Bootloop , no logs
Except this grabbed from splah2 :
https://androidfilehost.com/?fid=4349826312261620338
made a new build
feroxxx said:
https://androidfilehost.com/?fid=4349826312261620338
made a new build
Click to expand...
Click to collapse
Unfortunately another bootloop and same result with stock kernel/ramdisk.
feroxxx said:
made a new build
Click to expand...
Click to collapse
Im sorry to intrude, i cant install OS .zip files on my pralx-1, i seem to only be able to install .img files from adb fastboot (on stock ROM and bootloader) and then install twrp. Otherwise it always gives me bootloop. So i cant be of any help but wanted to thank you for taking your time and to bring lineage back to this model. I've sucessfully installed pphhusson Android 10 gsi trebble available on github (cant post links because of post count) maybe you can take a look and see if he is doing something different in order to avoid bootloop. Theres also a havoc 3.0 release from developerluke (though i havent tested that one). I wish you all the luck and once again thank you for your work, cheers
Do we need updated GPU drivers for fixing graphical glitchs? I read that its common problem with Android 10.
I haven't tried booting Android 10 GSI on P8 lite 2017.
there's an unofficial lineage 17 from Andy Yan in case anyone wants to take a look at it
Code:
https://sourceforge.net/projects/andyyan-gsi/files/lineage-17.0/
I've tried it and it boots just fine but ended up going back to un official havoc 3.0 from developer Luke just because i prefer the added customizations it has
i made a new build
https://androidfilehost.com/?fid=4349826312261647300
can anyone test my rom?
For flashing a treble build, what flavour for our P8 lite 2017 ? Tryed GSI type A arm64 but bootloop (for LOS17 by Andy Yan)