Related
April 1, 2017 .. and it's not an April Fools' Day Joke --> TWRP for Pixel C is official now !
https://twrp.me/google/googlepixelc.html
I would like to continue this thread for publishing test builds and other troubleshooting.
Once the changes are stable and tested I will merge them into TeamWin github for the next official build.
Known issues:
- FBE (file based encryption) is not working correctly, pls use FDE (full disk encryption) instead.
fwtool
The "fix fastboot" advanced menu item has been removed as it's not part of the official TWRP sources.
The fwtool is still existing (/sbin/fwtool) - only the menu item has gone.
If you need the fwtool, to fix fastboot, you can use it like before, but now you have to type the command into terminal inside TWRP.
For more details, pls have a look here .. http://forum.xda-developers.com/showpost.php?p=64777133&postcount=96
Installation:
Please install the new version from your current TWRP.
Pls make a "reboot to recovery" once you have installed the new version.
Of course you can install it via fastboot too.
Sources:
https://github.com/TeamWin/android_device_google_dragon
https://github.com/omnirom/android_bootable_recovery
DOWNLOAD:
https://drive.google.com/drive/fold...oaU1iazg?resourcekey=0-4krcBcSF3tnMFvgcP4kMvw
Have fun!
XDA:DevDB Information
[TWRP][dragon], Tool/Utility for the Google Pixel C
Contributors
followmsi
Version Information
Status: Stable
Current Stable Version: 3.3.1-2
Stable Release Date: 2017-04-01
Created 2016-06-17
Last Updated 2023-01-11
Changes:
Official 3.7.0_9-1 (2023-03-25)
- Exclude MTP
- Restore stock values for init.recovery.dragon.rc
- Enable Screen Timeout
https://dl.twrp.me/dragon/twrp-3.7.0_9-1-dragon.img.html
Official 3.7.0 (2022-10-10)
- New official version -> https://twrp.me/site/update/2022/10/10/3.7.0-released.html
Official 3.6.2 (2022-06-01)
- New official version -> https://twrp.me/site/update/2022/06/01/twrp-3.6.2-released.html
Official 3.6.1 (2022-03-10)
- New official version -> https://twrp.me/site/update/2022/03/10/twrp-3.6.1-released.html
Official 3.6.0 (2021-11-28)
- New official version -> https://twrp.me/site/update/2021/11/28/twrp-3.6.0-released.html
Official 3.5.2 (2021-04-07)
- New official version -> https://twrp.me/site/update/2021/04/07/twrp-3.5.2-released.html
Official 3.5.1 (2021-03-17)
- New official version -> https://twrp.me/site/update/2021/03/17/twrp-3.5.1-released.html
Official 3.5.0 (2020-12-31)
- New official version -> https://twrp.me/site/update/2020/12/31/twrp-3.5.0-released.html
Official 3.4.0-0 (2020-06-22)
- New official version -> https://twrp.me/site/update/2020/06/24/twrp-3.4.0-0-released.html
Official 3.3.1-2 (2020-03-01)
- Script updates to improve encryption -> Thanks to updateing from Team Mokee !
Official 3.3.1-1 (2020-01-27)
- Script updates for Android 10
- Added more languages
- Fixed build issues
- New Kernel
Official 3.3.1-0 (2019-05-19)
- New official version
Official 3.3.0-0 (2019-04-10)
- New official version
Official 3.2.3-0 (2018-07-29)
- New official version
* Fix automatic installing of OTA zips on encrypted devices
* Remove SuperSU from TWRP
* Support both md5 and md5sum file extensions when doing MD5 checking for zip files
Official 3.2.2-0 (2018-06-30)
- New official version
* DRM changes
Official 3.2.1-0 (2017-12-18)
- New official version
Official 3.2.0-0 (2017-11-29)
- New official version
Official 3.1.1-1 (2017-09-15)
- Including all changes for Oreo and for better en/decryption from unofficial V1 and V2
Unofficial 3.1.1-0 twrp-3.1.1-0-dragon-Android-O-v2.img (2017-09-11)
- New "pulldecryptfiles.sh" to copy all "bin" and "lib64" files from system/vendor partitions.
Unofficial 3.1.1-0 twrp-3.1.1-0-dragon-Android-O.img (2017-07-31)
- Official TWRP Nougat ramdisk mixed with new Oreo kernel binary to support Android 8.0 (SDcardFS .. etc.)
Official 3.1.1-0 (2017-05-17)
- Upgrade to 3.1.1-0
Unofficial 3.1.1-0 (2017-05-14)
- Latest TWRP changes (3.1.1)
- Latest kernel sources (2017-05-12)
- Latest LineageOS changes (Android 7.1.2)
Official 3.1.0-0 (2017-04-01)
- Removed "Data (incl. storage)" partition for usb-otg backup of "complete" data partition.
3.1.0-2
- Custom installer script problems should be fixed now.
3.1.0-1
- Removed all the FBE changes - will take longer to get it running on dragon
- Added NTFS-3G support for NTFS R/W -> USB-OTG
- Used new kernel binary with changed F2FS config
3.1.0-0
- @dees-Troy just tagged version 3.1.0 - made a new version based on latest sources.
- Added some more config changes for FBE.
3.0.3-4
- Used latest TWRP and AOSP soruces and enabled some features for FBE encryption.
3.0.3-3
- Added "Data (incl. storage)" partition for usb-otg backup of "complete" data partition
- fstab modification (usb-otg -> auto)
3.0.3-2
- F2FS enabled
- tegra-3.18 kernel -> v170210 (ntfs + f2fs enabled)
3.0.3-1
- Based on Android 7.1.1 AOSP -> android-7.1.1_r14
- Based on TWRP branch for Android 7.1
- tegra-3.18 kernel -> v170208 (ntfs + f2fs enabled)
v23
- Based on Android 7 AOSP -> android-7.0.0_r3
- Based on TWRP branch for Android 7
- tegra-3.18 kernel -> v160907
v22
- Based on Android 7 AOSP -> android-7.0.0_r1
- Based on TWRP branch for Android 7
- chromeos-3.18 kernel -> v160823
- Maybe not fully working as v21 due to new sources.
v21
- Added BRIGHTNESS PATH ... Thx to @ggow
v20
- Added Battery PATH ... Thx to @ggow
v19
- "Failed to unmount `/system `(Device or resource busy)" - Finally fixed now
- New versioning
v18
- MTP is working in recovery now !
- Added dragon keyboard layout files
v17
- "Failed to unmount `/system `(Device or resource busy)" - Not fully fixed - hopefully soon !
- chromeos-3.18 kernel -> v160618
v16
- ADB shell was not working in recovery - fixed now !
- chromeos-3.18 kernel -> v160617
Well done to both you and NYChitman!
I have noticed that when I go to make a backup, it finishes but is unable to unmount partitions after the backup saying that it is busy. If I reboot I am able to mount and unmount properly
Sent from my Nexus 6 using XDA-Developers mobile app
DarthDestroyeis said:
Well done to both you and NYChitman!
I have noticed that when I go to make a backup, it finishes but is unable to unmount partitions after the backup saying that it is busy. If I reboot I am able to mount and unmount properly
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks for the feedback ..
Did you install something before .. maybe still mounted from before ?
Or you just made the backup only ?
Which partitions did you backup ? .. system as well .. or just data ?
Pls post recovery.log on pastebin.com .. helps a lot !
Thanks
http://pastebin.com/SDEw6EWL
Backed up system, data, vendor, etc.
Made a twrp backup before wiping to install new rom
System partition locks up and is unable to be wiped or flashed over until I reboot recovery
Sent from my Pixel C using Tapatalk
DarthDestroyeis said:
http://pastebin.com/SDEw6EWL
Backed up system, data, vendor, etc.
Made a twrp backup before wiping to install new rom
System partition locks up and is unable to be wiped or flashed over until I reboot recovery
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
It´s always system which is complaining .. no other partitions, correct ?
Thanks ... will have a look.
Yup... just the system partition.
Hey. I'm back. Considering taking the risk and installing TWRP again. Will I still be able to take OTAs? No, right?
N4 + Update.ZIP_PixelC_Ryu_NPD56N-system-vendor.zip (flashed via fastboot) +TWRP_dragon_3.0.2-0_v16.img.
loop boot recovery..I tried everything but no chance to boot into system again
ilpolpi65 said:
N4 + Update.ZIP_PixelC_Ryu_NPD56N-system-vendor.zip (flashed via fastboot) +TWRP_dragon_3.0.2-0_v16.img.
loop boot recovery..I tried everything but no chance to boot into system again
Click to expand...
Click to collapse
You did flash system-vendor update.zip via fastboot ?
No good idea.
The kernel and the TWRP are fine to flash via fastboot, but not the system.img and vendor.img.
Like written on first page of the updatr.zip thread.
Pls install the package via TWRP.
Or use unmodified stock image from Google for fastboot.
For recovery bootloop I know only "fastboot reboot".
I had the bootloop once myself, as I still was on M, but the command did help me.
YevOmega said:
Hey. I'm back. Considering taking the risk and installing TWRP again. Will I still be able to take OTAs? No, right?
Click to expand...
Click to collapse
I am not the OTA User
As I know, the tool "flashfire" from Chainfire should handle the whole OTA process smoothly.
The Update.zip packages I do anyway, because I am used to it .. over the years.
Did this for Nexus Flo ... Nexus 10 as well.
For Pixel C I just publish them, because nobody as else is doing it.
Look in Flo and manta xda .. They have these packages too, done by others.
Because of all the problems with OTA .. in the past ..and still today.
Today we have systemless root and regular OTA...times are changing.
Maybe it's time for something like flashfire in the next time ..
sorry I made a typo :
I meant Update.ZIP_PixelC_Ryu_NPD56N-kernel-dragon.zip ( I extracted boot.img)
ilpolpi65 said:
sorry I made a typo :
I meant Update.ZIP_PixelC_Ryu_NPD56N-kernel-dragon.zip ( I extracted boot.img)
Click to expand...
Click to collapse
This should work .. the boot.img is just stock.
Were you rooted and decrypted before?
You did install SuperSu afterwards ?
And 'fastboot reboot' did not help either ?
People have reported they had to go back to M to be able to boot again.
There was one recovery bootloop with stock recovery as well ,
Maybe you try another kernel (boot.img) too ?
A fresh one .. below from the stock kernel
Strange issue .. for me not reproducable at all!
Sorry, can't help you better ..
followmsi said:
This should work .. the boot.img is just stock.
Were you rooted and decrypted before?
You did install SuperSu afterwards ?
And 'fastboot reboot' did not help either ?
People have reported they had to go back to M to be able to boot again.
There was one recovery bootloop with stock recovery as well ,
Maybe you try another kernel (boot.img) too ?
A fresh one .. below from the stock kernel
Strange issue .. for me not reproducable at all!
Sorry, can't help you better ..
Click to expand...
Click to collapse
True... It's really strange..but..pixel c too is a strange device...
anyway thanks for your help !
DarthDestroyeis said:
Yup... just the system partition.
Click to expand...
Click to collapse
v17
- "Failed to unmount `/system `(Device or resource busy)" - fixed now
- chromeos-3.18 kernel -> v160618
Please have a try with v17.
My problems are gone .. no more warning messages while doing backup or restore.
"Failed to unmount `/system `(Device or resource busy)"
Pls test as well !
Thanks
sorry for all this quick releases today .. this is the last one for now !
but when something new is working .. I would like to share it with you ...
v18
- MTP is working in recovery now !
- Added dragon keyboard layout files
Enjoy !
Moah ey..... Yesterday I may had need it urgently ´cause I can´t restore a nandroid lol - this fuxxing mount issue...
Well but a clean flash and set up the device completely new is always a pleasure - isn´t it?
Will test it asap and thx again for your hard work
redukt said:
Moah ey..... Yesterday I may had need it urgently ´cause I can´t restore a nandroid lol - this fuxxing mount issue...
Well but a clean flash and set up the device completely new is always a pleasure - isn´t it?
Will test it asap and thx again for your hard work
Click to expand...
Click to collapse
Today I have made 3 backups and restores
No problems or messages so far ..
But pls test on your device as well .... On Pixel C you never know
Cheers
Ok, will test it now without wipes
redukt said:
Ok, will test it now without wipes
Click to expand...
Click to collapse
Hopefully
About
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.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM" like OmniROM
Click to expand...
Click to collapse
(Source: https://twrp.me/)
Is this the official TWRP thread?
YES until you find any further notice on https://twrp.me .
Features
<MM> (PREVIEW): Build on (Android 6.0) sources
<N> (PREVIEW): Build on (Android 7.1) sources
<O> (PREVIEW + current OFFICIAL): Build on (Android 8.1) sources
<P> (PREVIEW): Build on (Android 9.0) sources
TITAN kernel inside (build with UBER Toolchain)
Time is working (for both STOCK and CM/AOSP based)
Decrypting is supported on: MM, N, O (CM/LOS/AOSP based ROMs) and on STOCK based ROMs (N only)
DT2W (double tap to wake up) - thx for the idea ufocus removed, sorry.
see the Changelog post for all features!
Requirements
You need to have a unlocked bootloader (see FAQ #9) to install and use TWRP!
To avoid issues with some ROMs (e.g. CM) this TWRP version comes without any supersu
Known issues
decrypting STOCK (other then N) is not working - only CM / LOS / AOSP based are fully supported
on some devices (unfortunately not on mine) the screen keeps unresponsive during a backup. Please just be patient it will start working again after the backup has finished.
after flashing Nougat bootloader (e.g. v29a) TWRP may lag. This has been reported by a few but I cannot reproduce that on mine.
Download
official twrp download page (search for your device model)
unofficial / PREVIEW releases:
From time to time I may release unofficial PREVIEW versions before merging them to official builds.
Those are meant as test builds only! Keep in mind that all my changes when they go stable will be merged with the official tree so you can just wait for a stable release.
Keep in mind that unofficial versions may contain unknown bugs!! so don't rely on backups taken from these versions!
Unofficial PREVIEW downloads (most current):
1) When do you need to install a specific flavor (MM, N, O,...) ?
if you want correct time setting in TWRP
if you want to decrypt - so encrypted your device
2) Is there any other reason why I should use a specific flavor (MM, N, O,...) ?
no!
you can use ANY flavor if you don't care about the above 2 reasons
3) So I can use ANY TWRP version to install ANY ROM?
Or do I need to use a specific flavor (MM, N, O,...) when it comes to install ROMs or other ZIPs?
read 2) again!
Download Link: http://leech.binbash.rocks
BETA downloads (extremely outdated): Download section above.
Installation
Optional but highly recommended:
Backup with SALT (click) before doing ANYTHING else!
Method 1) TWRP app (recommended but requires a rooted device)
Google play store: TWRP-App
Without play store: official twrp website
I said you need an unlocked device. So ensure you have it unlocked and for official unlocked G4 models the OEM unlocking option must be enabled!
Install the app and open it. Agree to the Terms.
Select TWRP Flash.
Select your device from the device list (H811, H815) and choose a version.
The file will download to your Downloads folder.
Browse to and select the file.
Tap on Flash to Recovery.
Find out more about the app here.
Method 2) fastboot
This howto works 100% up to and including MM (scroll down for N):
I said you need an unlocked device. So ensure you have it unlocked and for official unlocked G4 models the OEM unlocking option must be enabled (see screenshot)
Connect an USB cable and get ADB running (READ the FAQ!! or the general guide above)
Boot into Android and then type on your PC to reboot into fastboot mode:
adb reboot bootloader
Type on your PC:
fastboot boot twrp.img
(replace twrp.img with the real file name you downloaded)
Then copy the twrp.img to your device while still in twrp (e.g. with a file explorer or by typing adb push twrp.img /sdcard)
Flash the twrp.img with twrp GUI to the recovery partition (choose the button at the bottom named image to show the copied image)
It is highly recommended to verify your TWRP installation by booting into Android now
fastboot reboot
Then execute: adb reboot recovery
or in a Android terminal app execute: reboot recovery
If you see TWRP afterwards then you are safe to use the key combo:
After installing TWRP correctly, you will still have the original LG factory reset screen/menu booting before TWRP, every time. So the correct and only way to get into TWRP with a key combo is to select two times "Yes" in the official LG factory reset menu, and only then you will get into TWRP (It's a restriction by LG. There is no key combo available in some / all / most LG devices to boot directly into recovery and so TWRP).
If that worked go into the reboot menu and choose reboot to recovery again so TWRP should boot up once again
Now all should be in place and TWRP should resist even booting into Android
This howto is for the Nougat bootloader (for LP or MM scroll up):
I said you need an unlocked device. So ensure you have it unlocked and OEM unlocking option is enabled (see screenshot)
Connect an USB cable and get ADB running (READ the FAQ!! or the general guide above)
Boot into Android and then type on your PC to reboot into fastboot mode:
adb reboot bootloader
Type on your PC (fastboot BOOT command has been removed from Nougat!):
fastboot flash recovery twrp.img
(replace twrp.img with the real file name you downloaded)
There is no 100% way to verify your TWRP installation so you have to take the risk but ensure you follow this next step briefly:
After installing TWRP correctly, you will still have the original LG factory reset screen/menu booting before TWRP, every time. So the correct and only way to get into TWRP with a key combo is to select two times "Yes" in the official LG factory reset menu, and only then you will get into TWRP (It's a restriction by LG. There is no key combo available in some / all / most LG devices to boot directly into recovery and so TWRP).
Do this right now!! open the factory reset screen to get into TWRP!
If you skip the step and boot into Android before doing this TWRP will be overwritten by Android so it is crucial important to do this step above directly after flashing TWRP!!!!! if you miss it you will have to flash TWRP again!
If that worked go into the reboot menu and choose reboot to recovery again so TWRP should boot up once again
Now all should be in place and TWRP should resist even booting into Android
Upgrade
Upgrading TWRP is easy. Just push the new image file to your device and flash from TWRP!
boot into TWRP (check the FAQ for a howto)
copy the new twrp.img to your device while still in twrp (e.g. enable MTP in TWRP and use a file explorer or by typing adb push twrp.img /sdcard on your PC (needs ADB installed. Again check FAQ for how to set this up))
In TWRP switch the view to show image files by choosing the button at the bottom named Image and walk to the place where you pushed the new twrp image file.
Choose the new twrp image file and when asked choose the "recovery" partition
done. You can now reboot into recovery again to check that the upgrade has worked.
Support
I have created a Telegram group for all stuff around Android : here
and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here
I'm normally also available in the official twrp IRC channel and besides that it is always the best way for getting direct TWRP support (channel #twrp)!
Before actually going there or if you're new to IRC please read and follow FAQ #5 What is required to get support?
Thread rules
Never ask for ETA's !
Sources
Official builds device tree: github
PREVIEW builds device tree github
Kernel: TITAN kernel
Thanks/Credits
TEAMWIN of course
@DevUt for the continues help on IRC
@jcadduono for some help with qseecomd libs
@kessaras for the TITAN kernel and for being often enough my testing *****
XDA:DevDB Information
Official TWRP, Tool/Utility for the LG G4
Contributors
steadfaster, draymond1987
Source Code: https://github.com/TeamWin/android_device_lge_g4
Version Information
Status: Stable
Current Stable Version: 3.4
Stable Release Date: 2020-06-22
Current Beta Version: any PREVIEW
Created 2016-08-18
Last Updated 2020-08-21
Changelog
Latest Official release
twrp-3.4.0-0
Release date: 2020-06-22
Compatibility: OREO (all other versions should work for flashing but enc, time and any adb commands will work with OREO only)
Download: https://twrp.me
Device Tree changelog: no changes
Summary changelog:
TWRP release notes
Previous Official(!) builds
twrp-3.3.1-2
Release date: 2020-02-28
Compatibility: OREO (all other versions should work for flashing but enc, time and any adb commands will work with OREO only)
Download: https://twrp.me
Device Tree changelog: github
Summary changelog:
you REALLY wanna now what has changed?
check it out
twrp-3.3.1-1
Release date: 2019-07-18
Download: https://twrp.me
Device Tree changelog: while the version seems to be minor this is a MAJOR change: I switched from Android-6.0 to Android-8.1, removing 5.1 support
Summary changelog:
Official TWRP now supports Oreo by default (decrypt, correct time)
This removes support for Lollipop bootloader stack - thats why the image size is almost just the half.
If you are still using an Lollipop / 5.1 bootloader stack (wth..?!) UPGRADE it - or 3.3.1-0 is the last supported for yours. You can always check the PREVIEW flavor for MM which is backwards compatible but do not expect any official builds for LP anymore.
you REALLY wanna now what else has changed?
it is way too much but here check it out and see what you have missed from not using a PREVIEW flavor ....
Latest Official release
twrp-3.3.1-0
Release date: 2019-05-22
Download: https://twrp.me
Device Tree changelog: (no changes)
Summary changelog:
https://twrp.me/site/update/2019/05/22/twrp-3.3.1-0-released.html
Latest Official release
twrp-3.3.0-0
Release date: 2019-04-10
Download: https://twrp.me
Device Tree changelog: (no changes)
Summary changelog:
https://twrp.me/site/update/2019/04/15/twrp-3.3.0-0-released.html
twrp-3.2.3-0
Release date: 2018-08-06
Download: https://twrp.me
Device Tree changelog: (no changes)
TWRP sources changelog: twrp-3.2.2-0 <--> twrp-3.2.3-0 (previous official vs. current official)
Summary changelog:
https://twrp.me/site/update/2018/08/06/twrp-3.2.3-0-released.html
twrp-3.2.2-0
Release date: 2018-07-01
Download: https://twrp.me
Device Tree changelog: (no changes)
TWRP sources changelog: twrp-3.1.1-0 <--> twrp-3.2.2-0 (previous official vs. current official)
Summary changelog:
https://twrp.me/site/update/2018/07/01/twrp-3.2.2-0-released.html
twrp-3.2.1-0
Release date: 2018-05-25
Download: https://twrp.me
Device Tree changelog: twrp-3.1.1-0 <--> twrp-3.2.1-0 (previous official vs. current official)
TWRP sources changelog: twrp-3.1.1-1 <--> twrp-3.2.1-0 (previous official vs. current official)
Summary changelog:
https://twrp.me/site/update/2017/12/09/twrp-3.2.1-0-released.html
twrp-3.1.1-1
Release date: 2017-06-21
Download: https://twrp.me
Device Tree changelog: twrp-3.1.1-0 <--> twrp-3.1.1-1 (previous official vs. current official)
TWRP sources changelog: twrp-3.1.1-0 <--> twrp-3.1.1-1 (previous official vs. current official)
Summary changelog:
decryption fixed (again) for CM/AOSP
twrp-3.0.2-1
Release date: 2017-06-15
Download: https://twrp.me/devices
Device Tree changelog: twrp-3.0.2-1 <--> twrp-3.1.1-0 (previous official vs. current official)
TWRP sources changelog: twrp-3.0.2-1 <--> twrp-3.1.1-0 (previous official vs. current official)
Summary changelog:
LL supported again
Unification of h811 and h815
many bugfixes, speed and other improvements (pls check the above changelog links!)
Latest PREVIEW release
read more about PREVIEWS and the <flavor>'s in the OP (what they are and when to use)!
twrp-<version>-PREVIEW-<buildnumber>_g4_<flavor>
Status: stable
Release date: see leech server
Download: sfX leech server (same download for all G4's)
Kernel: preview builds compile the kernel on build automatically (official not) - so the kernel differ between official and preview
Device Tree changelogs:
MM flavor - NOTE: The support for the MM flavor has reached its END OF LIFE (2020-02-28)
N flavor
O flavor
P flavor
Previous builds
twrp-3.2.1-PREVIEW-116_g4_O (only O!)
Status: testing
Release date: 2018-03-28
Download: Download Page (same download for all G4's)
Device Tree changelog: O flavor
Summary changelog:
newest TITAN
switched kernel toolchain (same then TITAN uses)
decrypting O works (aoscp tested)
complete build on O sources (TWRP)
twrp-3.2.1-PREVIEW-109_g4_N (only N!)
Status: stable
Release date: 2018-03-17
Download: Download Page (same download for all G4's)
Device Tree changelog: N flavor
Summary changelog:
Decrypting STOCK N is working now!
twrp-3.2.1-PREVIEW-106_g4_<flavor>
Status: stable
Release date: 2018-03-15
Download: Download Page (same download for all G4's)
Device Tree changelog: MM flavor and N flavor
PREVIEW vs. OFFICIAL changelog: MM PREVIEW <--> latest official TWRP and N PREVIEW <--> latest official TWRP
twrp-3.2.0-PREVIEW-43_g4_<flavor>
Status: stable
Release date: 2017-12-07
Download: Download Page (same download for h811/h815)
Device Tree changelog:
<custom-m>: https://github.com/steadfasterX/android_device_lge_g4/commits/android-6.0
<custom-n/stock>: https://github.com/steadfasterX/android_device_lge_g4/commits/android-7.1
PREVIEW vs. OFFICIAL changelog:
<custom-mm>: this PREVIEW <--> twrp-3.2.0-0
<custom-n/stock>: this PREVIEW <--> twrp-3.2.0-0
Summary changelog:
<all>: replaced LLAMA kernel with TITAN (thx @kessaras for the kernel )
<all>: updated TWRP codebase to 3.2.0 (https://github.com/omnirom/android_bootable_recovery/compare/android-7.1...android-8.0)
<all>: removed legacy LP decryption support (it MAY still work though bc of the next line)
<all>: using new decryption support by TW_CRYPTO_USE_SYSTEM_VOLD ( https://github.com/omnirom/android_bootable_recovery/commit/71c6c50d0da1f32dd18a749797e88de2358c5ba1 )
This means in theory: decrypting stock and any other ROM should be much easier now.
<custom-n>: enabled debug when decrypting (will be disabled once all decrypting tests are done)
<stock>: builds are now based on 7.1 tree (like custom-n)
<custom-mm>: in some beta versions decrypt was broken which is now fixed again
<all>: fixed time (again)
<all>: from now on I will generate md5 hashes for all unofficial / PREVIEW twrp releases
twrp-3.1.1-BETA-g4-sfXbuild3
Status: stable (it's a BETA though)
Release date: 2017-06-20
Download: Download Page (same download for h811/h815)
Device Tree changelog: previous BETA <--> this BETA
BETA vs. STABLE changelog: this BETA <--> twrp-3.1.1-0
Summary changelog:
decryption fixed (again) for CM/AOSP
BETA-5 Build id #327 (h811 + h815)
Status: stable (it's a BETA though)
Release date: 2016-12-19
Download: Download Page (same download for h811/h815)
Device Tree changelog: build #317 <--> build #327
TWRP sources changelog: build #317 <--> build #327
first working unified TWRP version for both h811 and h815 in one build. That means:
from now on there will be 1 single download file which works for both devices.
factory reset in Android will do it's job now! That means:
using the factory reset hardware key combo will just open TWRP (as it is in all builds)
but when you do a factory reset in Android settings it will boot into TWRP and wipe now
Hint: This requires the ROM uses /grow as /misc partition! Example: CM supports this in CM14.1 since 15th of Dec 2016
Other ROMs may have to change their fstab to make this working for them
BETA-4 Build id #317 (h811 + h815)
Status: stable (it's a BETA though)
Release date: 2016-12-16
Device Tree changelog: build #285 <--> build #317
TWRP sources changelog: build #285 <--> build #317
fixing an issue with cmupdater preventing to upgrade
Using /grow as /misc because the CM devs preferring this (https://review.cyanogenmod.org/#/c/177122/)
BETA-3 Build id #285 (h811 + h815)
Status: stable (but cmupdater is broken here)
Release date: 2016-12-14
Device Tree changelog: build #186 <--> build #285
TWRP sources changelog: build #186 <--> build #285
first fully working version for the h811 device
governor=intelliactive, IO scheduler=sioplus, rhsize=1024. see twrp benchmark
adding /misc to support CM internal updater! Now cmupdater would work if the CM devs will enable it again (will work up to 5th of Dec CM 14 builds nevertheless. The internal cmupdater will prevent booting into recovery after that build date... Tested on h811 and h815.).
Ensuring that factory reset by the hardware key combo will not reset the device (proven on h811 and h815 that it will NOT wipe when open "factory reset" page with hardware key combo)!
Switched back to android-6.0 branch because bigbiff recommended that
BETA-2 Build id #186 (h815)
Status: stable
Release date: 2016-11-21
Device Tree changelog: build #162 <--> build #186
TWRP sources changelog: build #162 <--> build #186
Using FIOPS I/O scheduler
read_ahead_kb=2048
Build id #162 (h815)
Status: stable
Release date: 2016-09-12
Device Tree changelog: build #91 <--> build #162
TWRP sources changelog: build #91 <--> build #162
new: build on the latest 7.0 branch of TWRP
CRITICAL fix: bug when restoring EFS! (Due to an issue in the TWRP sources it was not possible to restore EFS which is fixed now)
fix: time was not correct for CM based ROMs
fix: time was not correct for STOCK based ROMs
new: double tap will awake device
fix: minor issue for bootdevice
fix: launch qseecomd on boot to avoid issues with decryption
fix: logfile messages now all in /tmp/recovery.log instead of cmd specifics
fix: removed /firmware from backup menu --> DO NOT TRY TO RESTORE ANY PREVIOUS /firmware BACKUP! You can restore it with LG Up if you do that by mistake
... for the rest and details checkout the changelog above
Build id #091
Status: abandoned
Release date: 2016-08-18 - Removed due to a bug in twrp sources. Pls see my post here
Device Tree changelog: TeamWin official <--> build #91
TWRP sources changelog: TeamWin official <--> build #91
initial public release
making decryption work
... for the rest and details checkout the changelog above
FAQ
Frequently Asked Questions (FAQ)
What's the meaning of decryption in terms of TWRP?
When you enable full device encryption in your favorite ROM or using stock without modification then your data partition is encrypted. That means no one can access your data when you shutdown your phone.
So in twrp you will see the data partition as a big 32gb unreadable partition even if 3GB are in use when you booted (and therefore decrypted) your ROM.
You CAN still backup that data partition but it will backup the whole 32GB because of encryption.
With this twrp version when started you will be asked for the decryption password and your data partition is readable as in the ROM. When you backup now the data partition it just backups the data in use so 3 GB instead of 32GB.
Regarding any pros of not using full disk encryption in your ROM I can say it does not really matters in performance in all normal cases. You will always read that disabling decryption will give you much more power and so on but the today's spec of phones are so good you will feel a slightly diff only. Ok some users still believe that this is minimal diff is what they need but to be honest: The ONLY way to find an answer for yourself is testing on your own using the SAME ROM and same version! One time with encryption once without. Use the exact same ROM and use the exact same configuration like governors, custom kernels etc.
On the other hand you will get a minimum of security if you enable encryption but give access to everyone finding your lost phone if not!
So it's up to you if you want this risk for a minimum on performance improvement.
And just for sure:
decrypting in twrp is not permanent! Your data gets just decrypted for backing up nothing more nothing less.
[*]You talked about using IRC to get support. What is this and how can I use that?
Note: check the support topic as from now on there is also a Telegram group for that available.
Meaning of IRC => Internet Relay Chat. A very good IRC client is this one here: hexchat <-- download it and read the quick intro to get started: Quick-Start
--> when asked if you want to join a channel type in "#twrp" and after connected you will be in.
If you do not want to install anything you can simply use the webchat instead directly over here: Webchat
Howto communicate? IRC means many people talking the same time and there are some goods and bads to know about using IRC.
So please read this mini and very quick overview (especially the good manners there): Good manners in IRC (matches for all OS not for fedora only)
[*]What is that "adb" thing??
adb stands for: Android Debug Bridge and can help a lot when it comes to work with your device. It is not for developers only but they use it a lot of course.
But a normal user can use this to exchange files without the need of mounting, backing up the device, reboot the device and use it as a very comfortable way of having a terminal emulator.
I highly recommend to use FWUL to connect your device. Not for TWRP only but also for anything else adb/fastboot related.
What Logfiles have to be provided and how?
Two options are available:
Option A is the absolute minimum when reporting an error and it can be done by every user without installing anything or any special skills!! Reports without this minimal requirement will be ignored!
Option B is also very simple but you need to install ADB if not installed already. The steps are very easy and there is an easy installer available.
Keep in mind that if you have a problem and want that to be solved the more you can tell and the more you can provide the better it is. So choose your option wisely....
A) The absolute MINIMUM: recovery.log:
Start in TWRP and connect an USB cable to your device
Menu: Advanced
Menu: Copy Log
Click Home button and go to Menu: Mount
Ensure MTP is enabled (button at the bottom)
Open the file explorer on your PC and go to Sdcard
open the file "recovery.log" in a text editor (windows users: Wordpad)
copy the whole content and paste it on http://bpaste.net (choose a long duration in the drop down). After you pasted your log there a LINK WILL BE GENERATED!!! I NEED THAT URL !!!.
Here are 2 screenshots which should guide you in this:
paste the log file:
copy URL:
Report the link of that paste URL by PM or in this thread
Besides the above tell me:
ROM name or say "STOCK"
ROM version ("LL" or "MM" - if you can tell me the build number as well)
Encrypted device or not
B) But for THE BEST SUPPORT provide not recovery.log only but also dmesg by executing the following cmds on your PC:
Start in TWRP and connect an USB cable to your device. Then on your PC (requires ADB installed! Check FAQ #3 of this post!!):
adb shell
dmesg > /tmp/dmesg.txt
OPTIONAL (only when requested by me): logcat -d -b all > /tmp/logcat.txt
OPTIONAL (only when requested by me): adb pull /tmp/logcat.txt
OPTIONAL (only when requested by me): cat /proc/last_kmsg > /tmp/kmsg.txt
exit
adb pull /tmp/recovery.log
adb pull /tmp/dmesg.txt
OPTIONAL (only when requested by me): adb pull /tmp/kmsg.txt
Open all logs one by one with a text editor like wordpad or similar and paste it here: http://paste.omnirom.org (do NOT paste all in one! Every single log should have a single paste URL)
If the logfile(s) are too big to get them uploaded on paste.omnirom.org use something like gists.github.com if you have a github account or zip it and upload it at www.filedropper.com
Report the link of that paste URLs by PM or in this thread
Besides the above tell me:
ROM name or say "STOCK"
ROM version ("LL" or "MM" - if you can tell me the build number as well)
Encrypted device or not
[*]What is required to get support?
Get IRC running (see FAQ 2)
Get adb running (see FAQ 3)
Collect logs (see FAQ 4)
Go to IRC and paste your problem together with the paste URLs you done before
If you can't see me on twrp or if there are any reasons why you may not get IRC running (serious? even not the webchat??!) answer to this thread and paste your URLs here
[*]Why is the time wrong in TWRP?
most important: use the latest TWRP (atm of writing it has to be the latest BETA 3.1.1 sfx-14). This has been fixed several times on our journey for different ROMs and their versions and should work for STOCK (up to N) and on any custom ROM now very well.
if you still encounter issues: set the time zone correctly in TWRP once. then reboot into TWRP and it should be still the correct time
if you still encounter issues: scroll up to FAQ #4 A) and pull the recovery log and attach it to your post.
For reference here the previous explanations (when using the latest TWRP no actions are required anymore!! even when switching between STOCK and custom ROMS !)
Before CM12.1:
Time setting was handled with the proprietary qcom time_daemon which was responsible to save a time offset of the qcom RTC (Real Time Clock). This time_daemon gets the time from the RTC and save the offset to the current "real" system time in either /data/time or /data/system/time. That means it SHOULD work out of the box for you but as you're reading this it may not.
Since CM12.1 and newer:
The proprietary time_daemon was completely replaced with an open-source alternative provided by sony: "timekeep".
The main principal is the same: the time gets read from the RTC and then gets not written to files in the file system but instead a persistent property is written (timekeep save) each time the time or timezone changes or when Android shuts down. This property is then read at the next boot again by timekeep (timekeep restore).
The handling of timekeep is fixed since build 127 of this twrp version / official 3.0.2-1 version so it should just work for you if you have that build running (or newer).
Stock ROMs:
Stock ROMs or stock based ones like Imperium ROM uses the proprietary qcom time_daemon. That means it SHOULD work out of the box for you but as you're reading this it may not.
When you had read the above and it states it SHOULD work for you but it doesn't:
Boot into twrp:
Menu Mount: select Data to get it mounted
On your PC:
adb shell rm /data/system/time/ats_2
adb shell rm /data/time/ats_2
adb shell rm /data/property/persist.sys.timeadjust
One of the above adb cmds may fail but that doesn't matters.
Now reboot into recovery again and the time should :fingers-crossed: be fine.
If the above give you NOT the correct time:
Please follow all steps of the above FAQ #5 and additionally also give an output of the following cmd while in twrp:
adb shell mount /data
adb shell ls -la /data/time /data/system/time
[*]Does this build supports F2FS?
Yes
[*] Why are some builds about ~50% smaller then other versions of twrp for these devices?
TWRP builds with more than 30 MB contain an uncompressed kernel image and support both bootloader versions : MM and LL
TWRP builds with about 16 MB contain a compressed kernel image and will run with MM bootloader only. As soon as I found out that this was the reason for not booting TWRP on LL devices I reverted the compression to support both again
btw the kernel is build with UBER tool chain
so the short answer is just "compression".
[*]Unlocking? Rooting?
official unlock (h811, h815 EUR) http://forum.xda-developers.com/g4/general/unlock-bootloader-install-twrp-root-t3128241
unofficial unlock (any G4): https://bit.do/unlockg4
[*]Don't trust TWRP for EFS backups? Do you want to have an independent backup of EFS? Do you wanna restore EFS without TWRP?
Consider to use the brand new backup method even for locked devices! DLM Backup
words in blue are commands you have to type on your PC
boot into TWRP
connect usb cable
adb shell
Backup
For the following 2 cmds: replace /external_sd by /sdcard if you have no external SD card. HINT: you have to decrypt /sdcard first if you enabled device encryption!
dd if=/dev/block/bootdevice/by-name/modemst1 of=/external_sd/modemst1
dd if=/dev/block/bootdevice/by-name/modemst2 of=/external_sd/modemst2
dd if=/dev/block/bootdevice/by-name/fsg of=/external_sd/fsg
dd if=/dev/block/bootdevice/by-name/misc of=/external_sd/misc
Restore
For the following 2 cmds: replace /external_sd by /sdcard if you have no external SD card. HINT: you have to decrypt /sdcard first if you enabled device encryption!
dd if=/external_sd/modemst1 of=/dev/block/bootdevice/by-name/modemst1
dd if=/external_sd/modemst2 of=/dev/block/bootdevice/by-name/modemst2
dd if=/external_sd/misc of=/dev/block/bootdevice/by-name/misc
dd if=/external_sd/fsg of=/dev/block/bootdevice/by-name/fsg
[*]You can't unlock your screen after you encrypted your device?
First of all: this has absolutely nothing to do with TWRP but as I encrypt always and everything I encountered a problem after encrypting my device and I just want to share you my solution:
checkout the following tool if you have the same issue described there: http://forum.xda-developers.com/g4/development/tool-lock-screen-fix-encrypted-devices-t3499478
[*]How to open/start/boot into TWRP?
You have 2 options at least:
when Android is booted:
you can do "adb reboot recovery".
Besides that many custom ROMs have a special power option or just download one of the dozens apps letting you do this
via key combo:
The only valid and always working and supported way on getting with a hardware key combo(!) into twrp is using the factory reset screen.
After installing TWRP correctly, you will still have the original LG factory reset screen/menu booting before TWRP, every time. So the correct and only way to get into TWRP is to select two times "Yes" in the official LG factory reset menu, and only then you will get into TWRP (It's a restriction by LG. There is no key combo available in some / all / most LG devices to boot directly into recovery and so TWRP).
Any other key combo like vol up + power depends on the kernel of the ROM! So it may work or not. Factory reset will work always.
If you are interested on the background why the factory reset page cannot be bypassed read on here: https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424/post72628311
For this you have to ensure that you have the latest twrp version really installed(!) because if twrp sits in recovery it will ignore the factory reset command when going through it.
Power down and pull out the battery. Do not forget to remove any USB cable.
Press power down and hold it down. Put battery back while keeping vol down pressed. Press power button and keep now both buttons pressed. When you see the LG logo the first time just release the power button for 1 second ( do not release vol down ) and then press power again and keep both pressed until you see the factory reset screen.
Once you see that screen just go through the steps like you would do a factory reset. If twrp is installed you will just open twrp without wiping any data. Again it is mandatory to have twrp installed otherwise it would really reset your device.
For the paranoid: If you want to be sure use "adb reboot recovery" when in android. When you see twrp all is fine but just do a full backup and then go through the factory reset first.
[*]What is a system IMAGE backup and why does it fail?
Using this new option is an ALTERNATIVE method to backup in opposite to the regular file based method. It is like a bit by bit backup of the COMPLETE partition which is the reason why it is much bigger as a regular backup.
So you likely will NEVER use the Image option or when you're a paranoid one only.
HINT: This method requires an ext4 or exfat partition on your external SD card otherwise image backups will fail due to the file size.
user reports success using the internal storage as target for the backup but if you do this keep in mind that you have to move that backup to your PC manually to ensure you have it by hand for the worst case.
So you may ask now why or when should I select this method? Never. So why is this option here? The main reason is TWRP in FIsH. I want to keep both device trees identical.
.
What's the pros of having a decrypted device? Is going to be smoother, faster or what?
DaarkieDoo said:
What's the pros of having a decrypted device? Is going to be smoother, faster or what?
Click to expand...
Click to collapse
+1 for this question
I'm curious what that technical talk means as well!
It's good to see progress and interest for our device. Is it possible to add dt2w like op3 here and the date and time of nandroids fixed ?
DaarkieDoo said:
What's the pros of having a decrypted device? Is going to be smoother, faster or what?
Click to expand...
Click to collapse
When you enable full device encryption in your favorite ROM or using stock without modification then your data partition is encrypted. That means no one can access your data when you shutdown your phone.
So in twrp you will see the data partition as a big 32gb unreadable partition even if 3GB are in use when you booted (and therefore decrypted) your ROM.
You CAN still backup that data partition but it will backup the whole 32GB because of encryption.
With this twrp version when started you will be asked for the decryption password and your data partition is readable as in the ROM. When you backup now the data partition it just backups the data in use so 3 GB instead of 32GB.
Regarding any pros of not using full disk encryption in your ROM I can say it doesn't matter in performance in normal cases. You will always read that disabling decryption will give you much more power and so on but the today's spec of phones are so good you will feel a slightly diff only. The ONLY way to find an answer is testing on your own using the SAME ROM and same version! Once with encryption once without.
On the other hand you will get a minimum of security if you enable it but give access to everyone finding your lost phone if not! So it's up to you if you want this risk for a minimum on performance improvement.
And just for sure:
decrypting in twrp is *not* permanent it is just decrypted for backing up nothing more nothing less.
Hope that answers your question
.
Sent from my LG-H815 using XDA Labs
ufocus said:
It's good to see progress and interest for our device. Is it possible to add dt2w like op3 here and the date and time of nandroids fixed ?
Click to expand...
Click to collapse
I think that is possible without problems. I check that.
checked:
its not such easy as stated in your commit link. we do not have "touchpanel" there so we need to check what else we could choose maybe those: https://github.com/CyanogenMod/andr...mmit/d3c0189ab7384d42906eea9d521c4d591a160c2f
edit 2:
changing /sys/devices/virtual/input/lge_touch/tap2wake --> 1 (as set in CM) has no effect in twrp.. Need further research..
edit 3:
ok got it. double tap will be added in the next build
.
Sent from my LG-H815 using XDA Labs
steadfaster said:
edit 3:
ok got it. double tap will be added in the next build
Click to expand...
Click to collapse
How about the correct date and time? Is this also an easy one?
Sent from my LG G4 using Tapatalk
albuntu said:
How about the correct date and time? Is this also an easy one?
Sent from my LG G4 using Tapatalk
Click to expand...
Click to collapse
no afaik this is a bug in twrp 3 as it was not a problem as in twrp 2 but I cannot say for sure.
Can you tell me what ROM do you use? and more important: When you reboot is the time correct (directly after reboot!) or is it not correct and gets corrected when connected to the carriers network?
.
steadfaster said:
no afaik this is a bug in twrp 3 as it was not a problem as in twrp 2 but I cannot say for sure.
Can you tell me what ROM do you use? and more important: When you reboot is the time correct (directly after reboot!) or is it not correct and gets corrected when connected to the carriers network?
.
Click to expand...
Click to collapse
I'm on CM13 and yes, the time and date are always correct. I know for sure because i often reboot with flight mode enabled.
Sent from my LG G4 using Tapatalk
steadfaster said:
edit 3:
ok got it. double tap will be added in the next build
Click to expand...
Click to collapse
Now that was fast Thank you! Appreciate the effort. For now we can live with wrong date and time it's not that big of a deal.
I do not understand the whole thing.
The incorrect date is for me a Problem.
Imperium Stock ROM
HorstiG said:
I do not understand the whole thing.
The incorrect date is for me a Problem.
Imperium Stock ROM
View attachment 3852244
Click to expand...
Click to collapse
Please see the the comment of Dees_Troy and bigbiff (both main devs of TWRP):
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/178#issuecomment-35728685
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/238#issuecomment-28525937
--> Means the ROM have to save the time data and TWRP tries to read that. If the ROM do not save that time data TWRP can't know the time.
Well there is a flag for QCOM since some day:
https://github.com/TeamWin/android_...mits/8b9b9c5d869e57cb7857723592044028a8874f61
--> that one is set already in my build but it is still not working
I still looking through the code what the devs actually expecting maybe ... well lets see.
update:
ok so far I can say the following
The Qualcom Time Daemon (proprietary) need to be available in your ROM (e.g. not available in RR)
The time daemon has to run properly (it has to work actually)
The time daemon has to write into either /data/time/ats_* or /data/system/time/ats_*
If those are ok then TWRP will display the time correct. If not blame the ROM not TWRP..
.
I have 4 Files, but all without content.
It´s the same with Stock LG ROM (KTZ)
Have a look please
https://dl.dropboxusercontent.com/u/73964661/Time.zip
On my older Baby LG D290 the Time is OK
HorstiG said:
On my older Baby LG D290 the Time is OK
Click to expand...
Click to collapse
It may be not a device with RTC that would explain it. Or the time daemon in that rom works better/other.
HorstiG said:
I have 4 Files, but all without content.
It�´s the same with Stock LG ROM (KTZ)
Have a look please
https://dl.dropboxusercontent.com/u/73964661/Time.zip
Click to expand...
Click to collapse
The files are not empty so it should work for you afaik...
Which timezone do you live and can you join the twrp channel? That would make it easier for troubleshooting..
.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
It may be not a device with RTC that would explain it. Or the time daemon in that rom works better/other.
The files are not empty so it should work for you afaik...
Which timezone do you live and can you join the twrp channel? That would make it easier for troubleshooting..
.
Click to expand...
Click to collapse
OT. Meine Zeitzone ist die gleiche als Deine. Bei TWRP G+ und xda habe nicht nur ich schon mehrmals das Problem angesprochen. Deshalb hatte ich etwas Hoffnung, dass Du...
Dann werde ich damit leben muessen.
Danke trotzdem und sorry for german
Sent from my LG-H815 using XDA Labs
HorstiG said:
OT. Meine Zeitzone ist die gleiche als Deine. Bei TWRP G+ und xda habe nicht nur ich schon mehrmals das Problem angesprochen. Deshalb hatte ich etwas Hoffnung, dass Du...
Dann werde ich damit leben muessen.
Danke trotzdem und sorry for german
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
ok no I meant IRC channel thats much much better because it is a chat so much more responsive
but I want to investigate that further (I mean my nick says it all) - can you do the following when booted into Android and paste their results:
ls -la /dev/rtc0 /dev/rtc
hwclock -uw (<-- if this gives you an error let me know but continue with the next part)
ls -la /dev/rtc0 /dev/rtc (again)
Boot up in TWRP and paste the results of:
ls -la /dev/rtc0 /dev/rtc
If it is not the correct time in UTC do the above hwclock command again
reboot recovery (so reboot into twrp again)
let me know your results
I'm normally online daily so grab an IRC client like hexchat or pidgin and connect to the channel #twrp. you will see me there. If you do not want to install anything simply use the webchat here: http://webchat.freenode.net/?channels=twrp
.
I WILL BE POSTING THIS ROM TRY AT YOUR OWN RISK NOT MY ROM NOT MY DEVELOPMENT BRICKED PHONE NOT MY ISSUE SRY ( OPPO TOOLS HELP WITH BRICKED DEVICES )
Sang Nguyen
Sang Nguyen ADMINISTRATOR MEMBER BQT
Posts:119 Likes:86 Trophy Points:96
JOIN NOW10/05/16
Information Rom Hexagon Hexagon Rom was developed based on CyanogenMod With the combination of customization features from Slim , Omni , Travel , Aicp, DroidOS ... Brought to you a Custom ROM with many features customized, high stability, convergence of the latest Android essence encapsulated in your smartphone. After all these attempts are today DroidVn-Team will send to you the first Hexagon OnePlus device .. .The other devices will be updated in the coming days, respectively.
Team DroidVN sincere thanks to AOKP , Omni , Travel , AICP , The Muppest
We can not accomplish this rom without you.
- Droid Version: Stable (Stable) - Android Version: 6.0.1 MM - Kernel: 3.4.x - Community Development: Droidvn-Team - Deverloper: Sang Nguyen , Tuan Nguyen, Phuocbull , Nthoa.it - Forum support Forum: Droidvn.com - Source code: Github
: Changelog:
SPOILER: CHANGELOG
Installation Guide (you must ensure the implementation of all the steps below to process successfully installed , we will not be responsible for your phone case damaged SD card, Brick)
Download the ROM and GApps in the phone memory
We recommend using TWRP recovery, and the machine you have to root and custom recovery installed
Boot into recovery
Wipe Cache / System / Dalvik / Data ( No Internal SDcard format )
Install, select the ROM zip file
Next select the GApps zip
Reboot and enjoy. (Note the first boot time can take a while, you should be patient)
Note flash GApps bottom.
: Download:
: GApps:
: Screenshots:
Screenshot_20160623-164246.png Screenshot_20160623-164323.png Screenshot_20160623-170429.png Screenshot_20160623-170648.png Screenshot_20160623-170748.png Screenshot_20160623-171558.png Screenshot_20160623-171609.png Screenshot_20160623-171635.png Screenshot_20160624-120022.png Screenshot_20160625-152441.png
[url]https://mega.nz/#!0VJXHBAD[/url]
KEY- !G96FyEt7Ux8T8t6PPVPNjEsbdML99RN6nPwEPFJ-2I0
This rom comes with supersu already installed and dolby installed also it supports stock partition not sure about the others please test and find out on your own
storage
if you want a unified storage do the chinese storage partition once you have that set up with twrp follow these steps
1: flash rom
2:flash modem if you need to
3:flash cm13 unified storage patch from the cm14 thread ( also available on community.oppo)
4:flash gapps
5:flash any extra mods you might like fyi this rom comes with a built in super user and dolby atmos
give it time to load then check your storage it should say calculating storage then show a full unified partition
support lvm?
how about new lcd? anyone tried?
Code:
clxer said:
support lvm?
Click to expand...
Click to collapse
LVM not support
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
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* 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 LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 9.x (Pie),which is designed to increase performance and reliability over stock Android for your device.All the source code for LineageOS is available in the LineageOS GitHub repo.And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.Official LineageOS website : http://lineageos.org
Downloads Links
LineageOS 16.0 (Unlocked Bootloader) :Test builds :
lineage-16.0-20191019-UNOFFICIAL-odin.zip | by CyberWalkMaN for Xperia ZL
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Google Applications (optional) :OpenGapps : http://opengapps.org/ (Use packages for ARM, Android 9.0, Nano or Pico)Information : Flash the GApps before the first boot. If not, a clean flash is recommended.Flashing and updatingLineageOS clean install :- (Optional) Flash the boot.img kernel from the ROM zip with Fastboot or Flashtool- (Optional) Wipe the data & cache (Backup to make sure not to loose data)- Flash the LineageOS ROM zip from the Recovery- (Optional) Flash the GApps to have the Google Applications- (Optional) Every additional zip you want to flash- RebootLineageOS update / upgrade :- (Information) Don't wipe anything unless you want to- (CM / UNOFFICIAL) Nothing to wipe when switching- (FUTURE RELEASES) Might need clean, informations will be updated- Flash the latest LineageOS ROM zip from the Recovery- (Optional) Flash the GApps on first install / upgrade. Not required later, but do update sometimes- (Optional) Every additional zip you want to flash- RebootLineageOS addonsu for root access :- (Information) Read the Root section of the Q&A thread- (Download) Download the addonsu for arm : LineageOS Downloads / Extras- (Optional) Flash the zip on a working Lineage installation (once)- (Information) Upon ROM updates, the addonsu is preserved- Reboot
Issues and reports- Report issues only if you are using the ROM kernel- If an additional mod is installed, make sure it's unrelated, and mention it- Make sure the issue wasn't discussed earlier in the threads- Share a log of the error with CatLog for example
About LineageOS Legal : http://lineageos.org/legal/The LineageOS team would like to thank everyone involvedin helping with testing, coding, debugging & documenting! Enjoy!
Also thanks to :- The LineageOS Team- The CyanogenMod Team- Everyone involved in working and testing
XDA:DevDB Information
[ROM][FINAL][9.0] LineageOS 16.0 for Xperia ZL, ROM for the Sony Xperia ZL
Contributors
CyberWalkMaN, AdrianDC
Source Code: https://github.com/fusion3-common
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Created 2019-04-22
Last Updated 2019-10-20
FEATURES AND ISSUES
Code:
- Boot : Ok
- GApps : OpenGApps Nano Ok
- FOTA Recovery : Ok (see below)
- WiFi : Ok (real SONY MAC address)
- Bluetooth : Ok (real SONY MAC address)
- WiFi Hotspot : Ok (2.4GHz only)
- RIL - Phone - Data : Ok
- GPS : Ok
- Camera : Ok
- Camcorder : Ok
- MicroSD : Ok
- Accelerometer : Ok
- Compass : Ok
- Gyroscope : Ok
- AOSP sensors : Ok
- FM Radio : Ok
- Vibrator : Ok
- Microphone : Ok
- Audio & external audio : Ok
- Bluetooth audio : Ok
- NFC : Ok
- Kernel : Ok
- Graphics : Ok
- 3D Rendering : Ok
- Clock : Ok
- Offline Charging : Ok
- SEPolicies : Work In Progress
At the moment, FM radio, manual network selection and auto brightness does not work (maybe something else). New builds will be uploaded as source updates / bug fixes are updated.
camera ok?
using as a daily cell phone, this is fast, congratulations.
Switch from nkomarn Lineage 16.O build. Camera works okay, so it was great. Only problem is flashing twrp, cannot successful flash using the app. Always go back to lineage recovery even light indicator goes purple to orange. Any workaround?
Also power off function not work, it rebooted. Anyways, it was great and thank you for continue work on this. Cheers! ?
Sent from my Sony Xperia ZL using XDA Labs
Just started testing this Rom, my feedback for now is:
Autorotate is not working.
Can't change any sound (calls, SMS, etc)- (APP crashes).
I've experienced some random reboots in the first few hours after flashing, it seems stable now.
Advanced reboot is not working properly.
Magisk is working fine.
Nova Launcher is working fine.
I'll continue to test...
Hope my feedback can help make this better.
hi, many thanks to develper! smooth running even such older device! the only issue is battery indicator always start from 12% but I am not sure if it is common issue.
Flash the latest build 0803, Sensors are now working. Auto Rotate is working, since sensor driver is there. FM Working properly also.
Still have issue on Turn Off, it keep restarting.
Cannot able to flash Twrp Recovery, still booting to lineage recovery.
But still, thank you for your time on updating this Rom
Sent from my Sony Xperia ZL using XDA Labs
Fiz uma instalação limpa do zero. Há 2 dias estou usando e sem bugs, ou reinicialização inesperada. Ótimo trabalho e muito obrigado por isso =D
New build uploaded (lineage-16.0-20190824-UNOFFICIAL-odin.zip), major changes since May:
All sensors works now (Thanks to @Chippa_a)
Manual network selection fixed
Telegram calls fixed (Need to confirm)
FM Radio fixed
Small gps improvement
Performance improvement
Updated kernel (fixed bug with rebooting instead of shutting down and some other bugs), also we now use binder and lmk from AOSP 3.18 kernel
SELinux denials resolved at 90%
Magisk issue fixed
Android 9.0.0_r46 (August security patches)
Addonsu is already included, you can enable root access in the developer settings
CyberWalkMaN said:
New build uploaded (lineage-16.0-20190824-UNOFFICIAL-odin.zip), major changes since May:
All sensors works now (Thanks to @Chippa_a)
Manual network selection fixed
Telegram calls fixed (Need to confirm)
FM Radio fixed
Small gps improvement
Performance improvement
Updated kernel (fixed bug with rebooting instead of shutting down and some other bugs), also we now use binder and lmk from AOSP 3.18 kernel
SELinux denials resolved at 90%
Magisk issue fixed
Android 9.0.0_r46 (August security patches)
Addonsu is already included, you can enable root access in the developer settings
Click to expand...
Click to collapse
Thank you for the update! I dirty-flashed it over the 0803 build. You see, I run the stable Magisk v19.3, which, along with some modules, then allowed me to pass both Safetynet tests. Not anymore. As you stated that Selinux was almost ready, I had uninstalled ibuprophen's The SELinux Switch app prior to flashing the new build. I was using it in order to set Selinux to enforcing. As Selinux is still off in the new build, I tried to install the app back, but the new build doesn't allow me to do it. Even the zip, although correctly installed in recovery, after booted up, no SELinux Swich app is in the drawer, because directory /data/app/com.ibuprophen.selinux-1 has been deleted during the boot up process! What's happening?
EDIT: I decided to do a clean install. Everything is back to normal! Thanks, anyway!
Pixel Launcher
Thanks again for your hard work in bringing Android 9 to this very old, but still powerful, device of ours.
Well, I prefer Pixel Launcher over the embedded home app, but it keeps crashing all the time upon being selected as the default home app. For those who also plan to use Pixel Launcher, edit /data/system/packages.xml, and add up the following entries, under <package name="com.google.android.apps.nexuslauncher"> and <perms>:
Code:
<item name="android.permission.STATUS_BAR" granted="true" flags="0" />
<item name="android.permission.MANAGE_ACTIVITY_STACKS" granted="true" flags="0" />
Could you make such changes in your next build?
After flashing the 0824 build, i experienced much better scrolling experience, performance improved a lot.
Also Twrp works now and turn off function work properly, no need to reboot and press volume down go to stock recovery just to turn this off. So thank you for continue working on this
Sent from my Sony Xperia ZL using XDA Labs
I thank you for continuing to develop! I'll install that, i report issues!
Perfect, bug-free, fast and stable ROM, using with magisk, everything runs perfectly.
New build uploaded (lineage-16.0-20191019-UNOFFICIAL-odin.zip), major changes since August:
Fast battery drain fixed (for 15.1 nightlies too)
SELinux denials resolved at 99% (You can make builds in enforced SELinux, but I would recommend continuing to build them in permissive). Current build in permissive SELinux.
Oktober security patches
Minor performance and stability improvements (for 15.1 nightlies too)
Added missing props for gps and Miracast.
Build status - Stable.
Addonsu is already included, you can enable root access in the developer settings
This is where my support for android 8-9 for Z/ZL/ZR/Tablet Z ends, this build will be the last. All the changes made in the sources are already available on github.com/LineageOS, if someone wants to continue supporting and get the official LineageOS 16.0 - write to PM, I will explain in detail what remains to be done in the sources. Also, if someone wants to try to build other roms for our devices based on android 8-9 from the available sources - try to choose CAF-based roms (for example, AOKP, LineageOS, Ressurection Remix, AICP, etc.), then with 95% chance you will build and run the rom. Our sources are based on CAF, and for the build of roms based on AOSP, additional fixes are required, plus there will be problems with sound anyway.
I also want to note that I made a most part of the changes made in 16.0 to the official 15.1 nightlies, which should significantly improve their stability and performance
CyberWalkMaN said:
New build uploaded (lineage-16.0-20191019-UNOFFICIAL-odin.zip), major changes since August:
Fast battery drain fixed (for 15.1 nightlies too)
SELinux denials resolved at 99% (You can make builds in enforced SELinux, but I would recommend continuing to build them in permissive). Current build in permissive SELinux.
Oktober security patches
Minor performance and stability improvements (for 15.1 nightlies too)
Added missing props for gps and Miracast.
Build status - Stable.
Addonsu is already included, you can enable root access in the developer settings
This is where my support for android 8-9 for Z/ZL/ZR/Tablet Z ends, this build will be the last. All the changes made in the sources are already available on github.com/LineageOS, if someone wants to continue supporting and get the official LineageOS 16.0 - write to PM, I will explain in detail what remains to be done in the sources. Also, if someone wants to try to build other roms for our devices based on android 8-9 from the available sources - try to choose CAF-based roms (for example, AOKP, LineageOS, Ressurection Remix, AICP, etc.), then with 95% chance you will build and run the rom. Our sources are based on CAF, and for the build of roms based on AOSP, additional fixes are required, plus there will be problems with sound anyway.
I also want to note that I made a most part of the changes made in 16.0 to the official 15.1 nightlies, which should significantly improve their stability and performance
Click to expand...
Click to collapse
Thanks for your hardwork and making a stable build, but i encounter issue Installing it.
Clean Flash it including system, but result in Rebooting to twrp, tried to flash previous Build then Update, stuck to Boot Animation and Reboot to Twrp. I'm quite sure the file is not corrupted, downloaded it two times. Sadly it was the Final build but hoping you will address and fix it. Thanks
[Updated]
Hello!!
Kran007 said:
Thanks for your hardwork and making a stable build, but i encounter issue Installing it.
Clean Flash it including system, but result in Rebooting to twrp, tried to flash previous Build then Update, stuck to Boot Animation and Reboot to Twrp. I'm quite sure the file is not corrupted, downloaded it two times. Sadly it was the Final build but hoping you will address and fix it. Thanks
[Updated]
Click to expand...
Click to collapse
Could you try the rom? or you can't intall it anyway? I gonna try it in the xperia zl that i will give to my father, but i can't get some error, He gona kill me! Actually , his ZL is running august version.
Can someone make a Build with December Security Patch?