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
Related
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
.
It's AOSP time ..
Android Pie ..
manta-Classic_Pie_08-2019_AOSP_9.0.0_r46_followmsi.zip --> DISCONTINUED
AospExtended-v6.7-manta-20191018-1203-UNOFFICIAL.zip --> DISCONTINUED
Known issues:
- NavBar works good, but no icons visible. (AospExtended only)
- NFC may not work correctly and drains a lof of battery - Pls disable thru settings menu.
- HWC (hardware composer) is partly broken (icons are not shown correctly and black home screen)
- Encryption seems not work - and has not been tested. -> Pls do not encrypt your data partition yet.
- Camera is not working .. same problem like on Nougat. (broken HAL1 camera and unsupported HAL2 camera)
- If you set pin, pattern or password to unlock the device pls be patient - if you press "confirm" the system is freezing for a few minutes - just wait.
Oreo ..
manta-Classic_01-2019_AOSP_8.1.0_r60_followmsi.zip --> DISCONTINUED
Known issues:
- Headphone jack is not fully working (Pls use the "AudioJack" kernel -> 3.4.67 - current standard kernel for all Oreo ROMs)
- If you install Magisk, pls disable Magisk "Hide" feature. (3.4.113 kernel issue)
- NFC has been taken out - still not working.
- Camera is not working .. same problem like on Nougat. (broken HAL1 camera and unsupported HAL2 camera)
- If you set pin, pattern or password to unlock the device pls be patient - if you press "confirm" the system is freezing for a few minutes - just wait.
Nougat ..
AOSP_7.1.2_r28_N2G48C_manta-ota-eng.followmsi-v1.zip --> DISCONTINUED
Known Issues:
- Camera is not working (broken HAL1 camera and unsupported HAL2 camera)
- Bluetooth is not working - fixed
- Audio jack is not working - fixed (still "old" kernel - 2017-05-09)
System and Cache repartitioning / Opengapps: Error 70
The current system partition is (getting) full !
You need to do repartition your system and cache partitions .. either via TWRP package or manually via shell.
It's an one time task.
But the filesystem of the system.img inside the ROM will keep always the same size .. approx. 800mb.
The filesystem does not know the "real" size of the actual partition.
In general .. If you install an image into a partition the filesystem will have the size of the image (in our case 800mb).
The free space we got thru repartitioning needs to be allocated again.
For this reason we need to enlarge/resize the filesystem after each ROM update and/or clean install.
Only the filesystem .. the partition itself will stay untouched.
The automatic enlarge/resize of the filesystem is part of the ROM installer.
For manual repartitioning have a look here:
https://forum.xda-developers.com/showpost.php?p=77759823&postcount=953
https://forum.xda-developers.com/showpost.php?p=77762148&postcount=954
For automatic repartitioning have a look here:
https://forum.xda-developers.com/showpost.php?p=77764246&postcount=957
https://forum.xda-developers.com/showpost.php?p=77770425&postcount=960
@ipdev - Thanks for your TWRP flashable repartitioning package !
Installation:
1. Boot into TWRP
2. Wipe system, cache and dalvik (Not required if you upgrade from previous build)
3. Install ROM.zip from above
4. install opengapps or beansgapps (arm) (optional)
5. install SuperSU.zip and/or Magisk.zip
6. Reboot into system
- Please install Magisk.zip and/or SuperSu.zip yourself.
- Due to systemless rooting - if you have installed magisk and/or supersu before you need to install it again !
- If you install SuperSu.zip it will boot twice - no panic, it's normal !
- If you had gapps installed before you don't need to install gapps again - the installer will take care.
- If you face any strange issues, pls do a factory reset via TWRP first.
Gapps:
The AOSP installer does not support "/system/addon.d/" scripts !
For this reason Gapps are not persistent like in LineageOS or in other custom ROMs.
I have modified the installer script to add this functionality.
You should be able to keep your gapps installation when you upgrade the ROM.
SuperSU and/or Magisk:
SuperSU.zip and/or Magisk.zip has always to be installed after ROM installation/upgrade - because of systemless rooting.
If you install SuperSu.zip it will boot twice - no panic, it's normal !
SOURCES:
If you want to build your own ROM ..
https://github.com/followmsi/manifests/tree/manta-aex-pie
https://github.com/followmsi/manifests/tree/manta-aosp-pie
https://github.com/followmsi/manifests/tree/manta-aosp-oreo
https://github.com/followmsi/manifests/tree/manta-aosp-nougat
DOWNLOAD:
https://androidfilehost.com/?w=files&flid=289294
https://drive.google.com/open?id=0By6p5AdQfavBNHkxVWhNOW5CdVk
Thanks to @sooti and @Khaon !
Enjoy
Is this "Pixel C" version with new tablet recents?
stunned said:
Is this "Pixel C" version with new tablet recents?
Click to expand...
Click to collapse
Most probably not .. it seems they are not part of AOSP yet - they are included in stock firmware.
Tested the new "stuff" on my Pixel C running AOSP as well .. the "new" mutil windows view did not work as in stock firmware.
Maybe it's related to the new Pixel Launcher .. maybe they are "hidden" and not activated in AOSP.
Also the battery usage alerts were not working on Pixel C ASOP build.
Need to check this ..
Maybe I need to do a complete wipe and start from scratch to get all the new nice stuff working ? .. )
You may have test yourself on manta ...
Cheers
followmsi said:
Most probably not .. it seems they are not part of AOSP yet - they are included in stock firmware.
Tested the new "stuff" on my Pixel C running AOSP as well .. the "new" mutil windows view did not work as in stock firmware.
Maybe it's related to the new Pixel Launcher .. maybe they are "hidden" and not activated in AOSP.
Also the battery usage alerts were not working on Pixel C ASOP build.
Need to check this ..
Maybe I need to do a complete wipe and start from scratch to get all the new nice stuff working ? .. )
You may have test yourself on manta ...
Cheers
Click to expand...
Click to collapse
Pixel c has its own Aosp tree or branch or whatever it is called. We already have the different navkey layout which is not available on phone aosp.
stunned said:
Pixel c has its own Aosp tree or branch or whatever it is called. We already have the different navkey layout which is not available on phone aosp.
Click to expand...
Click to collapse
For the pixel c AOSP version I have used the pixel c branch.
Still not working ..
Just installing new pixel c launcher on the pixel c to see the difference .. if at all.
We will see if and how we can "enable" those features .. on manta hopefully too.
Sent from my AOSP on dragon using Tapatalk
Keep getting error Bluetooth share keeps stopping, flashed with gapps, and without, same error
dnp77 said:
Keep getting error Bluetooth share keeps stopping, flashed with gapps, and without, same error
Click to expand...
Click to collapse
Yep .. will have a look.
Plenty of Bluetooth changes in 7.1.2.
Thanks for the info.
SetupWizard
If you do a clean install and install opengapps there are issues with the gapps "SetupWizard" on 7.1.2 !
Have a look here ...
https://forum.xda-developers.com/showpost.php?p=71740178&postcount=267
You can also mount system (RW) and type:
Code:
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
in TWRP terminal. This will allow you to bypass the SetupWizard altogether on a clean flash.
As it looks like the gapps team is working on an replacement SetupWizard for 7.1.2 ..
Cheers
New version ..
AOSP_7.1.2_r2_N2G47E_manta-ota-eng.followmsi-v2.zip
Installation:
1. Boot into TWRP
2. Wipe system, cache and dalvik (no need to wipe system if you upgrade from previous build)
3. Install AOSP_7.1.2_r2_N2G47E_manta-ota-eng.followmsi-v2.zip
4. Install open_gapps-arm-7.1-xxxx-2017xxxx.zip (optional)
5. Install SuperSU-v2.79-201612051815.zip (optional)
6. Reboot into system
- If you had gapps installed before you don't need to install gapps again - the installer will take care.
- Due to supersu installation it will boot twice - no panic, it's normal !
- If you face any strange issues, pls do a factory reset via TWRP first.
- The SetupWizard from gapps is still buggy on 7.1.2
- Camera is not working
Changes:
- Bluetooth is working now !
Enjoy
Audio jack not working
Nicholas1994 said:
Audio jack not working
Click to expand...
Click to collapse
Thanks for the info .. same/similar problem like in LOS 14.1
Have updated the know issues now ..
Known Issues:
- Camera is not working
- Audio jack is not working
- Bluetooth is not working - fixed in v2
Not sure when the Audio jack issue will be fixed ..
Cheers
followmsi said:
Thanks for the info .. same/similar problem like in LOS 14.1
Have updated the know issues now ..
Known Issues:
- Camera is not working
- Audio jack is not working
- Bluetooth is not working - fixed in v2
Not sure when the Audio jack issue will be fixed ..
Cheers
Click to expand...
Click to collapse
What kernel are you using? this is what you should be using. the issue has something to do with changes in merges beyond 3.4.67, try mine if you want a working kernel with headphone support
sooti said:
What kernel are you using? this is what you should be using. the issue has something to do with changes in merges beyond 3.4.67, try mine if you want a working kernel with headphone support
Click to expand...
Click to collapse
Cool .. This works well
Compiled a new kernel using your sources .. really nice.
Thanks a lot !
New manta kernel .. fixing Audio jack !
manta-kernel_kernel-flasher-5.1-20170409.zip
manta-kernel_kernel-flasher-5.1-20170409.zip.sha1
Installation:
1. Boot into latest TWRP
2. Install manta-kernel_kernel-flasher-5.1-20170409.zip
3. Reboot into system
No need for SuperSU ... or anything else.
The installer will take care.
Thanks to @sooti for the information.
Enjoy
Audio jack Works fine now , thanks for a super rom ?
AOSP - Music.apk
The current Music AOSP app is not working .. google did forget to implement a patch
https://groups.google.com/forum/#!topic/android-rpi/LNUCjXXvn2U
This problem occurs on all 7.1.2 AOSP ROMs.
Here is the patch:
https://android.googlesource.com/pl...+/6036ce6127022880a3d9c99bd15db4c968f3e6a3^!/
Have cherry-picked this patch now and compiled the Music.apk again.
You still need to manually grant access to "storage" for the app.
Made a quick installer to replace the broken apk ..
AOSP_7.1.2_r2_Music.apk_fixed-for-Android-N_manta.zip
Maybe I will remove the app next release completely.
Cheers
Grid view
Google has activated the "grid" view of your recent apps for a few devices in 7.1.2.
It's part of AOSP already.
If you would like to use this feature .. just activate it
Pls type inside terminal app as root ..
mount system RW:
Code:
mount -o rw,remount /system
activate grid:
Code:
echo "ro.recents.grid=true" >> /system/build.prop
Reboot into system ...
I am not sure if we should activate this view per default in the next release.
Some comments please
followmsi said:
Grid view
Click to expand...
Click to collapse
For tablet layout and a 10" screen size I prefer recents grid view, thanks for the hint. :good:
Now all the fresh changes are included ...
AOSP_7.1.2_r2_N2G47E_manta-ota-eng.followmsi-v3.zip
Changes:
- Added new kernel to fix Audio jack
- Enabled "Grid View" per default
- Fixed Music.apk
Installation:
1. Boot into TWRP
2. Wipe system, cache and dalvik (no need to wipe system if you upgrade from previous build)
3. Install AOSP_7.1.2_r2_N2G47E_manta-ota-eng.followmsi-v3.zip
4. Install open_gapps-arm-7.1-xxxx-2017xxxx.zip (optional)
5. Install SuperSU-v2.79-201612051815.zip (optional)
6. Reboot into system
- If you had gapps installed before you don't need to install gapps again - the installer will take care.
- Due to supersu installation it will boot twice - no panic, it's normal !
- If you face any strange issues, pls do a factory reset via TWRP first.
- The SetupWizard from gapps is still buggy on 7.1.2
- Camera is not working
Enjoy
To finalize the manta kernel testing I have made a last version ..
Activated 1 more governor .. and used a cherry-pick to speedup AC charging.
manta-kernel-aosp_kernel-flasher-5.1-20170413.zip
Changes:
- ONDEMAND CPU governor activated
- The kernel has included changes to speed up AC charging
Installation:
1. Boot into latest TWRP
2. Install manta-kernel-aosp_kernel-flasher-5.1-20170413.zip
3. Reboot into system
No need for SuperSU ... or anything else.
The installer will take care.
If you face any strange issues, pls let me know.
Enjoy
*Only tested on TA-1032 but it should work on other models too*
Downloads:
Build 1:
https://mega.nz/#!qIhFkKia!AkUMvQJ0PGVnSePabTvOgO-oUAMZahlCNaZfy2gE4vE
This TWRP now supports removing data encryption on Oreo.
General Changelog for TWRP version:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
Changelog:
Build 1:
- Initial release
What works:
- Touch
- OTG
- Backup (system.img backup doesn't work but don't worry, you can backup System and you'll be fine)
- Restore
- Flashing IMGs and ZIPs
What doesn't work:
- Battery percentage is incorrect (it's possible to fix but need some time)
- MTP (it's possible to fix but need some time)
- you tell me
For full backup you need to remove encryption so you can backup /data too.
If you're wondering why protect_f, protect_s, para and uboot partitions have 0MB it's because these partitions have less then 1MB.
Comment if link need to be updated.
Credits:
@mohancm for Lenovo K4 Note TWRP
Screenshots:
i can't install it with sp flashtools ... now i bricked my phone and i downgrated it to 7.1
Riadh300 said:
i can't install it with sp flashtools ... now i bricked my phone and i downgrated it to 7.1
Click to expand...
Click to collapse
i installed it without problems, tell me your device model and how you installed it.
Worst thing that could happen is that recovery got bricked, to recover simply flash new recovery. it worked for me, with twrp flash img, with flashify and with SP Flash Tool. Maybe you flashed it in wrong way.
Also please can someone flash/test this twrp so i can see does it work for others.
System and Data can be backed up and restored on oreo with this twrp?
Hey! Why Ported One? I did upload the Twrp Recovery Source! https://github.com/ChalapathiRevanth/twrp_device_nokia_heart
You are Free to Compile It
ChalapathiRevanth said:
Hey! Why Ported One? I did upload the Twrp Recovery Source! https://github.com/ChalapathiRevanth/twrp_device_nokia_heart
You are Free to Compile It
Click to expand...
Click to collapse
Top.
Thank you
Reygal21 said:
System and Data can be backed up and restored on oreo with this twrp?
Click to expand...
Click to collapse
data can be backed up only after removing encryption, system can be backed up without problems.
As for restore, it works on Nougat (i restored whole rom when i tried substratum theme)
but i didn't tested for Oreo.
I think that will work on Oreo too because there is no change in partition mount points between Nougat and Oreo.
Update:
I found out that incorrect battery percentage and MTP are not kernel issue so it is possible to fix it.
Is it still ported, or you used twrp kernel source in new version ?
What is the diff between this and mediafire007 ver ? This second one can't find the thread about it.
Thank you Skabo !
Nikola Jovanovic said:
Is it still ported, or you used twrp kernel source in new version ?
What is the diff between this and mediafire007 ver ? This second one can't find the thread about it.
Thank you Skabo !
Click to expand...
Click to collapse
it's ported from Lenovo K4 Note TWRP which have MT6753 CPU
Though i noticed that medifire007 is smother, especially when changing storage. This TWRP have latest TWRP version and touch works smoothly while on mediafire007 TWRP you need to wait in beginning to work.
Can this work on Nokia 1 with Android Oreo 8.1?
abdul_manan said:
Can this work on Nokia 1 with Android Oreo 8.1?
Click to expand...
Click to collapse
no, but i can try to port it, i just need testers.
Edit: Bro you already have twrp for Nokia 1, just search xda Nokia 1 forum.
SkaboXD said:
no, but i can try to port it, i just need testers.
Edit: Bro you already have twrp for Nokia 1, just search xda Nokia 1 forum.
Click to expand...
Click to collapse
Thanks Bro! It worked! But there is a new problem Now. Here it is..
https://forum.xda-developers.com/nokia-1/help/stock-recovery-error-nokia-1-black-t3798928
Tested and working on TA-1028 variant with Android nougat. Installed SuperSU and everything seems okay. Thx dev:victory:
Is there any custom Rom and kernel for Nokia 3 .
Stock Nokia 3 Rom and kernel is really bad
Can i use for Nokia 3 locked bootloader???
How to install ?
please Post Nokia 3 TA1032 Android 8.1 Custom recovery
Umairali321 said:
please Post Nokia 3 TA1032 Android 8.1 Custom recovery
Click to expand...
Click to collapse
Doesn't work on 8.1? Did you tried it?
Havoc 3.0 Q gsi fixed build for Huawei P10 Lite
About
Originally Havoc 3.0 Q gsi based on v204 compiled by ExpressLuke , but for Hi6250 some bugs persist , so I managed to fix them and repacked the IMG then highly compressed.
Fixed
* Camera * media ( sound , video , YouTube ..) * NFC * battery usage * auto brightness * phone Info's ( build number , model , manufacturer , device name .. ) * added Havoc bootanimation .
Bugs
* Offline charging ( requires permissive kernel , Labyrinth kernel 2.0 by Dil3mm4 tested * Blurry can be fixed in phh treble settings > Huawei features > 3rd option ( disabling hwcomposer ).
Installation
* Extract img from xz archive * go to TWRP and do a full wipe (system, data, cache, dalvik/art cache) * flash the image in system image partition * flash root (optional) NOTE1: If you are coming from Android 9 flashing root is a MUST DO ! NOTE2: Flash only the Magisk zip linked in this post ! * reboot to System * reboot to TWRP * flash gapps (optional) * Enjoy !!!
Download
https://mega.nz/#!2S4xxQ6C!f0KJlCA_9_yyJzWZAtlNYVJHktSuyyFY7p82kXK4caM
Twrp recommended ( by @Pretoriano80 ):
https://mega.nz/#!LLhBXSzY!3runNNoW9z1tOHSu-heIUhyy-4u8XHvc8rZMsn547so
Magisk.phh:
https://mega.nz/#!uX4k1KjS!2gnUV3IyLt8XXf4NO3RyZEJnt5YNJQ8tY9i11oGfKYM
Credits: @phhusson ExpressLuke @haky 86 @DarkJoker360 @Dil3mm4
Regards!
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Emui 8.x,bootloader unlocked and TWRP
Based On: AOSP
Version Information
Status: Stable
Created 2019-12-01
6 hrs SoT
Hami_Do said:
6 hrs SoT
Click to expand...
Click to collapse
Wow that's really impressive for a 3000 mAh device! Many people aren't getting that on the Note 10 Plus!
Hi! Thats nice, so basically Is a Kirin gsi? Are gapps included?
TureX said:
Hi! Thats nice, so basically Is a Kirin gsi? Are gapps included?
Click to expand...
Click to collapse
No, it's simply Havoc GSI with several fixes included especially for our device/platform and no, gapps are not included (you would have known if you read the first post more carefully )
TureX said:
Hi! Thats nice, so basically Is a Kirin gsi? Are gapps included?
Click to expand...
Click to collapse
For gapps , pico worked for me as it should , from here :
https://sourceforge.net/projects/opengapps/files/arm64/beta/20191114/
Hami_Do said:
For gapps , pico worked for me as it should , from here :
https://sourceforge.net/projects/opengapps/files/arm64/beta/20191114/
Click to expand...
Click to collapse
Hi! I Guess for Who hasn't a working twrp Is not possible to flash gapps. Thanks for your work and sorry for my english
TureX said:
Hi! I Guess for Who hasn't a working twrp Is not possible to flash gapps. Thanks for your work and sorry for my english
Click to expand...
Click to collapse
the suggested twrp in first post works perfectly on most hi6250 ( emui 8 ) , plus it has an option ( exclude OEM path from data wipe ) from there you don't need to format data & internal storage to boot any gsi/dssi AFAIK.
Only sometimes installing gapps requires resize system from advanced wipe menu.
thanks.. any build for havoc 2.9 ?
How can I remove the bottom pad that appears when I want to use the keyboard?
itsm03 said:
thanks.. any build for havoc 2.9 ?
Click to expand...
Click to collapse
the best 2.9 build here:
https://sourceforge.net/projects/ha...90912-phhgsi_arm64_a-Official.img.xz/download
1- wipe system data cache
2-flash havoc 2.9 and boot up to system
3- reboot to twrp and :
4- flash offline charger fix for pie
5- flash nfc patch for pie
6- flash hwcomposer ( follow instructions )
7- flash gapps and magisk ( optional )
Enjoy.
All flashable patches you find them here:
https://forum.xda-developers.com/p10-lite/how-to/gsis-manual-fixes-hi6250-devices-t3936745
ghassan haddad said:
How can I remove the bottom pad that appears when I want to use the keyboard?
Click to expand...
Click to collapse
Join https://t.me/hi6250group telegram group , there you can share your screenshots to understand the issue.
Hami_Do said:
Join https://t.me/hi6250group telegram group , there you can share your screenshots to understand the issue.
Click to expand...
Click to collapse
I Couldn't post pictures since new members need to wait, add to that I got only one answer telling me that it may not be possible.
I was referring to this pad in the picture
Now Gsi's based on v207 and later are stable , here you find latest Havoc Q gsi :
https://sourceforge.net/projects/expressluke-gsis/files/HavocOS/Ten/ARM64/A/
Probably only NFC patch is needed :
https://forum.xda-developers.com/p10-lite/how-to/gsis-manual-fixes-hi6250-devices-t3936745/page3
=========
No way to boot on my phone (WAS-LX1A)...stuck on boot, after some minutes its reboot, other minutes and then goes in erecovery.
I tried also a totally clean install starting with last firmware stock (WAS-LX1AC432B390) install (dload method) and then flashing Havoc 3.0 (based on v207) system file from fastboot.
Nothing to do and I came back beaten to Android 8.0
.....any help pls?
or maybe it is easier to buy a P30 lite
Tx
Toti
Achieve is currupt :-/
i get Error while flashing image, here is the log
Erro 255
I get error while flashing image here is the log
I have the saame problem on WAS-LX1
anvetoti said:
No way to boot on my phone (WAS-LX1A)...stuck on boot, after some minutes its reboot, other minutes and then goes in erecovery.
I tried also a totally clean install starting with last firmware stock (WAS-LX1AC432B390) install (dload method) and then flashing Havoc 3.0 (based on v207) system file from fastboot.
Nothing to do and I came back beaten to Android 8.0
.....any help pls?
or maybe it is easier to buy a P30 lite
Tx
Toti
Click to expand...
Click to collapse
Any help?
Help this guy and me, please!
From my experience with flashing this device it is most likely that either your device is still encrypted or there are magisk leftovers or data partition wasn't wiped correctly, that's causing rom not to boot. And always use pretoriano's twrp_0.5_test, works best. Sometimes it boots to erecovery, but you can try to reboot and it might work then.
NeoPreacher said:
From my experience with flashing this device it is most likely that either your device is still encrypted or there are magisk leftovers or data partition wasn't wiped correctly, that's causing rom not to boot. And always use pretoriano's twrp_0.5_test, works best. Sometimes it boots to erecovery, but you can try to reboot and it might work then.
Click to expand...
Click to collapse
I think you're right, I also think it's due to encryption or data partition (not magisk because I made a clean installation), because I had the same problem, stuck on boot, with all the Roms (PIE and Q) that require TWRP.
The only rom without problems was OpenKirin-OmniROM Pie Alpha 6.2 which does not require a custom recovery for installation !!
Do you have any operational suggestions to give me or I just have to try with pretoriano's twrp_0.5_test ??
What do you think if :
- In a stock recovery I do a factory reset
- From fastboot I do fastboot erase system, userdata and cache (or better to use format command for userdata?)
- the I flash system.img
- then I flash TWRP
- and then install magisk and gapps from TWRP?
TX
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.5.1 :
Wrappedkey support running only on FBE devices - CaptainThrowback
TWRP App log information reduced - epicX67
Refresh details after system wipe and adb sideload - AdrianDC
Chinese translation updates - betaxb
Support keymaster 2 - PeterCxy
add tzdata to TWRP for timezones - CaptainThrowback
ParitionManager: support delayed adopted storage mount - PeterCxy
Support to start terminal from file manager directory - AndroiableDroid
Nano support - nebrassy
Add nano support to open files from file manager - CaptainThrowback
Include new magisk apk support to be installed by TWRP - ianmacd
Add support to change directory name where TWRP stores backups - epicX67
Add bash support - not the default shell - DarthJabba9
ORS support to format data - AdrianDC
Add support to flash both slots when flashing an image - epicX67
NL translation updates - ianmacd
Cleanup
Installation cleanup - remove dupe PackageExtractFn - klabit87
Remove logd-reinit service - CaptainThrowback
Fixes
Restore system root context - bigbiff
Only include keymaster 2 if tree supports it - CaptainThrowback
Strip lines containing '--' in language_helper.py - ianmacd
Unlocalized string fix - ianmacd
DOWNLOADS: twrp-3.6.2_9-0-ginkgo.img
HOW TO FLASH:
Fastboot Method :
fastboot flash recovery twrp-3.5.2_9-1-ginkgo.img
Boot to OLD TWRP > INSTALL > Select Image > Navigate to twrp-3.5.2_9-1-ginkgo.img > Select it & Swipe to Flash
CREDITS:
TeamWin
CyanogenMod/Lineage Android
XDAevDB Information
[RECOVERY][OFFICIAL]TWRP-3.5.2 for Xiaomi Redmi Note 8/8T, Kernel for the Android General
Contributors
Erwinabs
mauronofrio
Source Code: https://github.com/TeamWin/android_device_xiaomi_ginkgo
Version Information
Status: Stable
Features:
- Decryption works
- Otg works
- Backups works
- Flash Rom works
- F2FS support
- Fastboot boot command support
- Compatibility.zip error fixed
- Willow fully supported
- Android 11 Decryption
- Android 12.1 Decryption
- Android 13 DecryptionDOWNLOAD BUILD :Base A9
twrp-3.6.2_9-0-ginkgo.img64M2022-06-05 20:01:45 UTCtwrp-3.6.1_9-0-ginkgo.img64M2022-03-13 23:24:43 UTCtwrp-3.5.2_9-1-ginkgo.img64M2021-07-04 14:16:19 UTCtwrp-3.5.2_9-0-ginkgo.img64M2021-04-05 05:10:04 UTCtwrp-3.5.1_9-0-ginkgo.img64M2021-03-13 23:04:47 UTCtwrp-3.5.0_9-1-ginkgo.img64M2021-03-06 17:20:59 UTCtwrp-3.5.0_9-0-ginkgo.img64M2020-12-28 17:19:58 UTCtwrp-3.4.0-1-ginkgo.img64M2020-07-22 22:06:01 UTCtwrp-3.4.0-0-ginkgo.img64M2020-06-22 11:27:29 UTCtwrp-3.3.1-1-ginkgo.img64M2020-02-15 00:04:51 UTCtwrp-3.3.1-0-ginkgo.img64M2019-12-05 00:59:27 UTC
Base A10
twrp-3.5.2_10-2-ginkgo.img64M2021-09-26 17:01:39 UTC
Base A11
twrp-3.6.2_11-0-ginkgo.img64M2021-09-26 17:01:39 UTC
Base A12.1
twrp-3.6.2_12-0-ginkgo.img64M2022-07-11 17:01:39 UTC
twrp-3.6.2_12-1-ginkgo.img64M2022-07-2217:01:39 UTC
twrp-3.6.2_12-2-ginkgo.img64M2022-09-21 17:01:39 UTC
Guide Install TWRP - HERE
Does this work with the android 11 decryption? Because my current 3.4x keeps saying "Unable to Decrypt FBE".
22naresn said:
Does this work with the android 11 decryption? Because my current 3.4x keeps saying "Unable to Decrypt FBE".
Click to expand...
Click to collapse
Yes work
Great, I'll try it out!
22naresn said:
Great, I'll try it out!
Click to expand...
Click to collapse
yes, everything is working fine
my suggestion：hiding the persist partion to avoid someone wipe it by mistake。
Suit yourself
wsdyleon said:
my suggestion：hiding the persist partion to avoid someone wipe it by mistake。
Suit yourself
Click to expand...
Click to collapse
Thanks
wsdyleon said:
my suggestion：hiding the persist partion to avoid someone wipe it by mistake。
Suit yourself
Click to expand...
Click to collapse
And hiding it for backup and restore too? I don't think it's a good idea.
x3r0.13urn said:
And hiding it for backup and restore too? I don't think it's a good idea.
Click to expand...
Click to collapse
persist is needed when you lose imei
x3r0.13urn said:
And hiding it for backup and restore too? I don't think it's a good idea.
Click to expand...
Click to collapse
u r →，it's not a good idea for someone。That was the fault that who first “display” the persist partion。
the best solution i thought was that giving one special option to whether display the persist partion
can you guys work on metadata based encryption
to decrypt it.
iamsaalim said:
can you guys work on metadata based encryption
Click to expand...
Click to collapse
Yes bhai
Cool cool
Anyway to force flash this via QFIL?
Every time i connect to internet the phone blocks via mi account.
Do not have the number ou access to the registered mi account anymore.
Anyone knows how to solve this withwout contacting a shaby russian that have the misteryous authorized account?
Erwin Abs said:
DOWNLOAD BUILD :
Official Build :- twrp-3.5.2_9-1-ginkgo.img
Unofficial Build :- recovery_3.5.2_9-Unofficial.img
Click to expand...
Click to collapse
Any clear summary of differences between official and unofficial builds?
pnin said:
Any clear summary of differences between official and unofficial builds?
Click to expand...
Click to collapse
no special difference, just add it
Nixye said:
Anyway to force flash this via QFIL?
Every time i connect to internet the phone blocks via mi account.
Do not have the number ou access to the registered mi account anymore.
Anyone knows how to solve this withwout contacting a shaby russian that have the misteryous authorized account?
Click to expand...
Click to collapse
Dont know , search in youtube
Changelog:
- initial Build A10
twrp-3.5.2_10-0-ginkgo.img