Database Develop

[OFFICIAL][RECOVERY] Cannibal Open Touch v3.0 Alpha Builds (latest: Alpha 10)

Cannibal Open Touch 3.0 Alpha 10
Disclaimer:
While we try to test our work as much as possible, it is always a possibility that something could go wrong and screw up your phone. We are not responsible for any damage that is done to your device, either directly or indirectly, as a result of using Cannibal Open Touch or any other Project Open Cannibal projects. Any damage done to your device is your responsibility and your responsibility only. We do this for fun, and we simply like to share our work.
What is Cannibal Open Touch?
Cannibal Open Touch is a custom recovery (like ClockworkMod or TWRP), created purely out of love for the platform and the desire to contribute something cool to the community. The name embodies everything that Cannibal Open Touch is. We take what we believe are the best features of popular recoveries like TWRP and ClockworkMod and, well, cannibalize them along with rolling out our own features.
Features:
Full Touch UI
Complete theme support, including app for management of themes (we'll get to that in a sec)
On-device backup and restore
Backup and restore via ADB
Much much more planned!
Bugs:
During installation, the standard Android installing icon gets displayed instead of the custom dialog box.
If you find a bug, please do not report it here! Instead, report it in the GitHub repository!
Screenshots
See the Screenshots tab above. (Or click me if you're using Tapatalk!)
Nandroid has been replaced!
Nandroid is in fact gone, and has been replaced with a much more robust backup solution. Backups can now be made either with ADB (the recommended way) or via the new Backup and Restore item in the main menu. Backups made via the built-in menu can be copied to a PC and restored via ADB, and backups made via ADB can likewise be copied to your device and restored using the Backup and Restore menu.
Code:
adb backup -f mybackupfilename.ab boot system data cache
You can also restore said backup by using adb, like so:
Code:
adb restore mybackupfilename.ab
Downloads:
Cannibal Open Touch Moto_MSM8960 Jellybean builds (latest: CannibalOpenTouch-2.99.10_msm8960_jbbl.img)
Cannibal Open Touch Moto_MSM8960 KitKat+ builds (latest: CannibalOpenTouch-2.99.10_msm8960.img)
How to install:
Download the latest Alpha image
Reboot to bootloader:
Code:
adb reboot bootloader
Flash the image with fastboot
Code:
fastboot flash recovery /path/to/downloaded/recovery.img
Boot into recovery mode
Alternatively, you may boot the image instead of flashing it:
Code:
fastboot boot /path/to/downloaded/recovery.img
Changelog:
3.0 Alpha 10 (2.99.10)
Themes are now stored in /cache/cot/themes to fix an issue introduced with FDE.
3.0 Alpha 9 (2.99.9)
Real menu scrolling! (but volume keys still work)
All backup/restore operations now verify that you want to take action
Resized UI to be more usable on all device resolutions
Themes can now display a battery charge indicator (depends on individual theme settings)
3.0 Alpha 8 (2.99.8) (not released)
Not released
3.0 Alpha 7 (2.99.7)
On-device backup and restore
3.0 Alpha 6 (2.99.6)
Complete theme support
Recovery settings (Theme settings and Unsigned ZIP flashing)
The preceding list is not 100% complete. See the project source code page for the full commit list.
Cannibal Open Touch themes app:
We are currently seeking Alpha testers for an app that will let users download and choose themes without rebooting to recovery mode. Currently there are 20 slots open. If you wish to join please PM me. The only requirement is you must have a Google+ account and are willing to submit proper bug reports, should any arise.
Cannibal Open Touch Themes:
You can now make your own themes for Cannibal Open Touch! See the example themes (it's pretty self-explanatory). Themes must be installed in /sdcard/cot/themes/theme_name (or /data/media/cot/themes/theme_name) in order to work. Please feel free to submit pull requests to have your custom themes added to the theme repository. They will also be packaged and made available to download via the Cannibal Themes app (mentioned above)!
Contribute to Project Open Cannibal
If you like our work and want to see more, consider a donation to the project!
Project Open Cannibal gerrit: http://review.projectopencannibal.org
Credits:
tdm, for the superb touch code (and lots more)
sblood86, for joining the project and leading the charge to greatness
thenameisnigel, for picking up our webhosting while I was gone
anyone else who has ever contributed to any Android-related project
XDA:DevDB Information
Cannibal Open Touch, Tool/Utility for the Motorola Droid RAZR HD
Contributors
thenameisnigel, Sblood86, drewwalton19216801, tdm, CyanogenMod, Koush and many others
Source Code: https://github.com/ProjectOpenCannibal/android_bootable_recovery-cm
Version Information
Status: Alpha
Created 2014-11-23
Last Updated 2014-12-03

Reserved

Reserved

Giving this a try, thanks!

Good deal will this work for jbbl?

TecknoFreak said:
Good deal will this work for jbbl?
Click to expand...
Click to collapse
Yep, I built it for jbbl bootloaders.
Sent from my XT1080 using Tapatalk

thenameisnigel said:
Yep, I built it for jbbl bootloaders.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
One thing I couldn't find while playing with it was the option to format partitions as f2fs. Am I blind or is this option N/A?

CWGSM3VO said:
One thing I couldn't find while playing with it was the option to format partitions as f2fs. Am I blind or is this option N/A?
Click to expand...
Click to collapse
Not available at the present moment, but if you really want it, submit it in the feature requests tab if you're on XDA using a browser.
Sent from my XT1080 using Tapatalk

CWGSM3VO said:
One thing I couldn't find while playing with it was the option to format partitions as f2fs. Am I blind or is this option N/A?
Click to expand...
Click to collapse
thenameisnigel said:
Not available at the present moment, but if you really want it, submit it in the feature requests tab if you're on XDA using a browser.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
I take back what I said, F2FS partitions are supported in COT. Like Drew said, there's no way to change the partition type yet. But if you have a pre-existing F2FS partition, you're all set.

CWGSM3VO said:
One thing I couldn't find while playing with it was the option to format partitions as f2fs. Am I blind or is this option N/A?
Click to expand...
Click to collapse
There is currently no way to switch partition types in COT recovery mode, though this is something we will consider adding in the future.
thenameisnigel said:
I take back what I said, F2FS partitions are supported in COT.
Click to expand...
Click to collapse
F2FS is supported code-wise but is not enabled by default, though this is something we'll be enabling shortly.

CWGSM3VO said:
One thing I couldn't find while playing with it was the option to format partitions as f2fs. Am I blind or is this option N/A?
Click to expand...
Click to collapse
drewwalton19216801 said:
There is currently no way to switch partition types in COT recovery mode, though this is something we will consider adding in the future.
F2FS is supported code-wise but is not enabled by default, though this is something we'll be enabling shortly.
Click to expand...
Click to collapse
Enabled. Alpha 10 that has F2FS enabled by default is up! Woot, woot!

Alpha 10 Jellybean & KitKat images are now up.

A little curious why you just have the option to backup to pc and not backup to internal or external sd card? Or is that just an older picture I'm seing? Looks good though.

cj360 said:
A little curious why you just have the option to backup to pc and not backup to internal or external sd card? Or is that just an older picture I'm seing? Looks good though.
Click to expand...
Click to collapse
Older picture. That was before we added on device backups.
Sent from my XT1080 using Tapatalk

Sweet! I'm in the middle of switching over to the KKBL versions of everything so I'll give this a shot!
---------- Post added at 04:08 PM ---------- Previous post was at 03:21 PM ----------
One bug I found is that this recovery does not boot after doing a "fastboot -w" to wipe the userdata (and cache) clean. I'm guessing it's trying to mount it?
Also, did not find a "back" button when I went into themes.

[RECOVERY][lt02ltetmo] TWRP 3.1.1-0 touch recovery [2017-05-19]

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.0.2-0:
-Backups will now include adopted storage keys (Dees_Troy)
-Fixed an adb restore issue (bigbiff)
-Fixed rebooting when no OS is present (Dees_Troy)
-Fixed line wrapping in the GUI terminal (_that)
-Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)
CHANGELOG for 3.1.0-0:
-vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
-adb backup to stream a backup directly to or from your PC, see documentation here: https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9 (bigbiff)
-tweak MTP startup routines (mdmower)
-support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
-support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
-better indicate to users that internal storage is not backed up (Dees_Troy)
-improve automatic determination of TW_THEME (mdmower)
-minimal getcap and setcap support (_that)
-try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
-shut off backlight with power key (mdmower)
-timeout during FDE decrypt (Dees_Troy and nkk71)
-support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
-boot slot support (Dees_Troy)
-TWRP app install prompt during reboot (Dees_Troy)
-support for AB OTA zips (Dees_Troy)
-support new Android 7.x log command (Dees_Troy)
-update recovery sources to AOSP 7.1 (Dees_Troy)
-numerous bugfixes and improvements by too many people to mention
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
DOWNLOAD:
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.

Note, this is for the LTE T-Mobile model only. It may work on other LTE models. I seriously doubt that it will work on the Wi-Fi only model as it uses a completely different chipset.
Device specific page with instructions for a manual install.
Direct download link for all current and past versions.

Support Sm-t210 ?

gr9nole said:
Support Sm-t210 ?
Click to expand...
Click to collapse
T210 is the Wi-Fi only model which uses a Marvell chipset instead of the Qualcomm chip found in the LTE models. This makes the 2 devices completely different internally and thus a completely different recovery would be needed for the T210.

Dees_Troy said:
T210 is the Wi-Fi only model which uses a Marvell chipset instead of the Qualcomm chip found in the LTE models. This makes the 2 devices completely different internally and thus a completely different recovery would be needed for the T210.
Click to expand...
Click to collapse
Stupid question
Is it for the sm t210r?

gr9nole said:
Support Sm-t210 ?
Click to expand...
Click to collapse
rookie12 said:
Stupid question
Is it for the sm t210r?
Click to expand...
Click to collapse
It's for SM-T217T.

jstath1972 said:
It's for SM-T217T.
Click to expand...
Click to collapse
Understand

T110 users are in the game now !
paziusss has now provided a TWRP 2.6.3.0,
which has got NO BOOT LOOP on T110.
great progress, since before last week T110 users had to reflash recov on a single use basis :crying:
maybe TWRP ver. 2.8.6.0 can be adapted for tab3 lite T110 too, at some point ...

Guys, can you please try to read the OP and the second post before flooding this thread with "haz support for t210 plz?".
This was made for the LTE models only, specifically the T217T and will NOT work on the WiFi only models.. None of them.

mtp is not working

Aroma installer touch not working.
Sent from my ASUS_T00J using XDA Free mobile app

Is there a way to get this working on lt02ltespr?
Sent from my SM-T217S using Tapatalk

miggsr said:
Is there a way to get this working on lt02ltespr?
Sent from my SM-T217S using Tapatalk
Click to expand...
Click to collapse
its working on lt02ltespr

DarkFrenzy said:
its working on lt02ltespr
Click to expand...
Click to collapse
Yes I just got it flashed... Also I flashed the ported cm 12 u have posted. But I have an issue where screen flickers. I recorded a small video of it if you want to see what I mean.
Sent from my unknown using Tapatalk

miggsr said:
Yes I just got it flashed... Also I flashed the ported cm 12 u have posted. But I have an issue where screen flickers. I recorded a small video of it if you want to see what I mean.
Sent from my unknown using Tapatalk
Click to expand...
Click to collapse
you should flash the new kernel. did u flashed it

No not yet because wasn't sure where the link was I might have downloaded it.
Sent from my unknown using Tapatalk
---------- Post added at 03:19 AM ---------- Previous post was at 03:15 AM ----------
DarkFrenzy said:
you should flash the new kernel. did u flashed it
Click to expand...
Click to collapse
Bingo that was it! Thanks for the help. I flashed 12.1 kernel
Sent from my unknown using Tapatalk

DarkFrenzy said:
you should flash the new kernel. did u flashed it
Click to expand...
Click to collapse
Bingo that was it! Thanks for the help. I flashed 12.1 kernel
Sent from my unknown using Tapatalk

miggsr said:
Bingo that was it! Thanks for the help. I flashed 12.1 kernel
Sent from my unknown using Tapatalk
Click to expand...
Click to collapse
If u want data u should flash Lkernel
Sent from my ASUS_T00J using XDA Free mobile app

DarkFrenzy said:
If u want data u should flash Lkernel
Sent from my ASUS_T00J using XDA Free mobile app
Click to expand...
Click to collapse
It's okay as long as I have Wi-Fi I don't use the data on that line anymore. I've disabled it from my account with sprint. But lol if there was a way to get free data then sure haha
Sent from my unknown using Tapatalk

miggsr said:
It's okay as long as I have Wi-Fi I don't use the data on that line anymore. I've disabled it from my account with sprint. But lol if there was a way to get free data then sure haha
Sent from my unknown using Tapatalk
Click to expand...
Click to collapse
Hmm. If u dont need data u can use cm13.
In cm12 and 13 Camera will not work
There is a fix for camera u should flash if u want it
Sent from my ASUS_T00J using XDA Free mobile app

[RECOVERY][AROMA][UNOFFICIAL] TWRP-3.2.1-r16

Unofficial TWRP for Oneplus X (Onyx)​Additional Features over Official TWRP:
AROMA compatible/supported/working
Compatible with newer EMMC models
Encryption Support
NTFS Support
Fixed Date/Time
Better In-Recovery Power Management
Decreased Boot Time
Synced with latest TWRP Patches
OREO Images/ROMs support.
No SuperSU by default.
No TWRP app.
No HTC Dumlock cruft.
Updated pigz compressor (slightly faster and more tolerant of corruption).
Green Theme by Sultanqasim.
Fixed remote wipe process (Earlier remote wipe issued from play account wasnt processed due to twrp)
Remove android reboot during password check on multiple wrong inputs.
Switched to LZMA compression to decrease size.
Faster I/O performance.
Various twrp upstream patches and fixes.
Downloads: https://www.androidfilehost.com/?w=files&flid=177316
Flashing Instructions:
Using Existing TWRP:
Reboot to recovery > Click on Install > Install Image > recovery > select recovery image and flash > reboot to recovery
Other methods:
https://twrp.me/devices/oneplusx.html
Few Points to remember:
This Recovery should only be used for flashing when you are on New Bootloader
This recovery MUST NOT be used to flash a ROM that is based on old bootloader
Using this recovery, you may break the OTA. So it is advised that you should not flash OTA with this. Rather, Download OTA zip and then flash (Only if you know what you are doing)
Credits:
> TWRP Team
Known Issues:
> Reboot on installing aroma zip for the second time without rebooting recovery or system. [workaround: reboot recovery after flashing aroma zip if you want to flash it again/twice]
Kernel Source:
https://github.com/CheckYourScreen/Arsenic.Kernel-rebased/tree/twrp
XDA:DevDB Information
[RECOVERY][AROMA][UNOFFICIAL] TWRP-3.2.1-r16, Tool/Utility for the OnePlus X
Contributors
CheckYourScreen
Source Code: https://github.com/CheckYourScreen/android_bootable_recovery
Version Information
Status: Testing
Current Stable Version: r16
Stable Release Date: 2018-01-12
Current Beta Version: r1
Beta Release Date: 2017-05-03
Created 2017-05-03
Last Updated 2018-01-12

|| Changelogs ||
r16 -
Updated to TWRP-3.2.1 source
OREO Images/ROMs support.
No SuperSU by default.
No TWRP app.
No HTC Dumlock cruft.
Updated pigz compressor (slightly faster and more tolerant of corruption).
Green Theme by Sultanqasim.
Fixed remote wipe process (Earlier remote wipe issued from play account wasnt processed due to twrp)
Remove android reboot during password check on multiple wrong inputs.
Switched to LZMA compression to decrease size.
Faster I/O performance.
Various twrp upstream patches and fixes.
r1 -
* initial release

Hi Folks!
I generally dont prefer Original Dev. Section for making threads but this one is an Exception, dont want it to get buried under pages
Here's first public beta release of twrp with working AROMA, yep thats right.
You can flash any Aroma installer zip, one minor glitch is there (mentioned in known issues) which I'll fix after my exams are over.
Dont forget to report issues here if you find any!

Reserved

Nimit the God ✌?
We owe you our lives for the recovery finally we have aroma compatibility.
P. S first post ?

Now here is my totally useful comment:
Second
But actually, great work Nimit. Thanks for the time and effort you put into making onyx great again.
Good luck with your exams

Yes to the big dev for onyx
TNX! alot @CheckYourScreen

If we meet in Delhi.. You get a treat for sure.. Thanks
Sent from my ONE E1003 using XDA-Developers Legacy app

Great work .

Great work. thank

Great work again! And thank you. Again!

thank u so much, @CheckYourScreen

Wow wow wow! Thanks dev! All the best for your exams!

Big Thanks @CheckYourScreen ... nice!

I don't want to nitpick here , but the hardware buttons aren't working.

ChzeRub said:
I don't want to nitpick here , but the hardware buttons aren't working.
Click to expand...
Click to collapse
They were disabled intentionally in official twrp and I'd like to keep them as it is, disabled.

CheckYourScreen said:
[*]AROMA compatible
Click to expand...
Click to collapse
Can you explain what this means? I'm aware of what an aroma installer is, but do I gather that they don't work with stock TWRP?
Sorry its a bit of a noob question even though I don't consider myself a noob lol.

kgr said:
Can you explain what this means? I'm aware of what an aroma installer is, but do I gather that they don't work with stock TWRP?
Sorry its a bit of a noob question even though I don't consider myself a noob lol.
Click to expand...
Click to collapse
It means aroma zips will work
Sent from my ONE E1003 using Tapatalk

kgr said:
Can you explain what this means? I'm aware of what an aroma installer is, but do I gather that they don't work with stock TWRP?
Sorry its a bit of a noob question even though I don't consider myself a noob lol.
Click to expand...
Click to collapse
Corrected, it means Aroma installer works with this recovery. All other features listed in the first post are not present in official twrp.

Hi @CheckYourScreen, do u plan on updating this to 3.1.1?

[RECOVERY][enchilada] TWRP 3.2.3-0 Touch Recovery [UNOFFICIAL]

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.
DOWNLOAD: Fixed....
Things that are different from official build:
fixed wrong theme color in screenshots on OP6.
Add support for QCOM haptics vibrator. (fixed vibration)
BUGS:
mtp (causes kernel panics) (can add a test build if needed)
flashing aroma packages
If you have found a bug, please consider posting it to our github issues log and then I'll report to Dess_Troy. If you have a significant problem that cannot be answered in this thread, your best bet is to PM Dees_Troy directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDAevDB Information
[RECOVERY][enchilada] TWRP 3.2.3-0 Touch Recovery [UNOFFICIAL]
Contributors
Joemossjr
Dees_Troy
wuxianlin
@notsyncing on github for the fixes
Source Code: Github
ROM OS Version: 8.x Oreo
Version Information
Status: Testing
Created 2018-07-07
Last Updated 2018-08-01
Donation Link: Buy this man a beer

Thanks for this. Add the version that supports MTP. Will test and let you know!

It's definitely bugged lol but I'll add it tomorrow

Thank you very much!

joemossjr said:
It's definitely bugged lol but I'll add it tomorrow
Click to expand...
Click to collapse
I'm working with your 3.2.1 version since the beginning and except aroma absolut everything is working. Never had any issue with MTP. Always worked stable so far. I did countless restores and all worked flawless even with swipe code in place.
So thanks very much to provide us with the very first working TWRP for the OP6.
Regarding aroma support, would you agree to my feeling that this is not an issue to be solved in the twrp framework but probably being a bootloader or firmware issue?

Simple temporary fix to avoid kernel panic on mtp:
Do not connect usb cable
Toogle unmount mtp, wait few second and enable mtp again in mount menu in recovery. Connect usb.

xXx said:
I'm working with your 3.2.1 version since the beginning and except aroma absolut everything is working. Never had any issue with MTP. Always worked stable so far. I did countless restores and all worked flawless even with swipe code in place.
So thanks very much to provide us with the very first working TWRP for the OP6.
Regarding aroma support, would you agree to my feeling that this is not an issue to be solved in the twrp framework but probably being a bootloader or firmware issue?
Click to expand...
Click to collapse
I'll be getting logs tonight while flashing an aroma package to see what's needed lol I feel like it's something simple but we will see. Thanks for the support everyone I do this on my free time lol I'll post the mtp enabled here shortly

mtp has been added to the downloads folder and is specified in the name!

https://github.com/opengapps/opengapps/issues/493
seems like its a dead issue at the moment on twrp. aroma hasnt been updated in a while. I am in contact with a dev who may know how to fix it. Stay tuned

joemossjr said:
https://github.com/opengapps/opengapps/issues/493
seems like its a dead issue at the moment on twrp. aroma hasnt been updated in a while. I am in contact with a dev who may know how to fix it. Stay tuned
Click to expand...
Click to collapse
thanks, very much appreciated :highfive:

joemossjr said:
mtp has been added to the downloads folder and is specified in the name!
Click to expand...
Click to collapse
Yes I have tested it and can confirm it's working. Just make sure you unmount mtp and remount it before attaching the USB cable (thanks to @DocRambone for the tip)

DocRambone said:
Simple temporary fix to avoid kernel panic on mtp:
Do not connect usb cable
Toogle unmount mtp, wait few second and enable mtp again in mount menu in recovery. Connect usb.
Click to expand...
Click to collapse
This works, thanks!

It's not working for me both new versions. Boot looped.
Sent from my ONEPLUS A6003 using XDA-Developers Legacy app

mbr007 said:
It's not working for me both new versions. Boot looped.
Click to expand...
Click to collapse
Did you remember to flash magisk after reboot into twrp?

lollyjay said:
Did you remember to flash magisk after reboot into twrp?
Click to expand...
Click to collapse
Yeah you have to flash magisk if you already had it flashed before hand

joemossjr said:
mtp has been added to the downloads folder and is specified in the name!
Click to expand...
Click to collapse
I just flashed your new mtp enabled zip version and screen brightness went down considerably even it's on 100% already. Does anybody know a workaround to get it brighter again?

Can you add another mirror like androidfilehost please? Unable to access google drive...

xXx said:
I just flashed your new mtp enabled zip version and screen brightness went down considerably even it's on 100% already. Does anybody know a workaround to get it brighter again?
Click to expand...
Click to collapse
Seems to be a general problem. I've the same, but not only with this version of TWRP, also with the original version.
It starts by me sometimes flashing 3.2.1.0 if i remember right and I never found a solution to get the screen brightness full back again ?

adiher said:
Seems to be a general problem. I've the same, but not only with this version of TWRP, also with the original version.
It starts by me sometimes flashing 3.2.1.0 if i remember right and I never found a solution to get the screen brightness full back again ?
Click to expand...
Click to collapse
I can make a new build that's higher

joemossjr said:
https://github.com/opengapps/opengapps/issues/493
seems like its a dead issue at the moment on twrp. aroma hasnt been updated in a while. I am in contact with a dev who may know how to fix it. Stay tuned
Click to expand...
Click to collapse
Could this have anything to do with why aroma isn't working?
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/page5
From the magisk 16.6 change log.
Note to ROM Developers
If you are embedding Magisk Zip into your ROM, and your ROM uses Aroma Installer, please be aware that on some devices (most likely Samsung devices), it is possible that the installation process of Magisk could break Aroma. Please test flashing your ROM zip before releasing to your users. If you found out you are the few unfortunate devices, unzip the Magisk zip, and do the following changes and re-zip the installer:
Code:
# Remove or comment out these 2 lines in META-INF/com/google/android/updater-script eval $BOOTSIGNER -verify < $BOOTIMAGE && BOOTSIGNED=true $BOOTSIGNED && ui_print "- Boot image is signed with AVB 1.0"
The reason why Aroma Installer breaks is unknown. Maybe consider letting the project that's abandoned for nearly 5 years go?

[Kernel][11.15.2020][4.14.205][F2FS] Dragonfly for LG G8 Korean / US

Dragonfly Kernel v1.5 for the LG G8 Korean / US
Introduce
First of all, I'd like to thank Metaphysics team for giving the first custom kernel of G8 USA. Unfortunately I'm using G8 - Korean and they haven't released version for the Korean variant yet. I had to learn how to build a kernel for myself based on their kernel source. However, I want to learn more so I decided to compile the kernel from LGE open source. Now, my kernel is quite stable to be released and shared to the G8 community. You can call it the Dragonfly kernel.
Main Features:
- Based on LGE open source LMG820N_Android_Q_v20r: http://opensource.lge.com/osSch/list?types=NAME&search=g820n
- Linux-Stable-Upstream included to latest 4.14.205
- Next-Gen CAF-Tag LA.UM.8.11.r1-02600-NICOBAR.0 merged
- Regular CAF-Tag for SD855 merged LA.UM.8.1.r1-16200-sm8150.0
- Compiled by ProtonClang 12.0.0 with -O3 speed optimizations
- No VLAs
- Magisk included
- F2FS support
EAS related features:
- EAS implementation patched up to latest CAF state
- Disable autogroups and use cgroups for more efficient task placement
- CPU input boost
File System related features:
- Include rapid GC by @arter97
Network related features:
- Wireguard Support (Details)
- Add new TCP congestion algorithm: BBR2, agilesd
Memory related features:
- Include zstd
Wakelock Blocker:
- Add Boeffla Wakelock Blocker v1.1.0
- The most common and safe wakelocks are blocked by default: qcom_rx_wakelock;wlan;wlan_wow_wl;wlan_extscan_wl;netmgr_wl;NETLINK
How to flash the Kernel:
- You can flash the kernel zip file via TWRP or Magisk
- You can also extract the new_boot.img to flash it via fastboot mode
Known bugs:
- You tell me
DOWNLOAD:
Download is located always in
https://github.com/anht3889/LGE_G820_Kernel_Caf/releases
Important: Read after Download
Be sure to turn off Secure start-up before flash this kernel
Credits:
- Metaphysics kernel team: https://github.com/KamioRinn/Metaphysics_LGE_G820_Kernel
- SGCMarkus for his guide of building kernel and TWRP
- Erick G for bringing new TWRP to G8 which supports F2FS
- Jean Carlos Bencosme for adding / picking kernel features
- Kirisakura for his great kernels
- Sultanxda for his simple_lmk
- LGE for the kernel open source
- All other great kernel devs
Contributors
quantan
Source Code: https://github.com/anht3889/LGE_G820_Kernel_Caf
XDA:DevDB Information
Dragonfly, Kernel for the LG G8
Contributors
quantan
Kernel Special Features:
Version Information
Status: Stable
Created 2020-09-16
Last Updated 2020-11-14

Previous versions, e.g. v1.4, don't work with the new TWRP 3.4. Therefore, I use Anykernel from v1.5. I recommend you follow the steps below:
1. Install magisk patched stock boot.img
2. Install new TWRP 3.4 from Magisk Manager
3. Reboot to TWRP
4. Install Magisk and reboot to TWRP
5. Install Disable Verity zip file and reboot to TWRP
6. Install my kernel Dragonfly v1.5
For newer version, i.e. v1.6, you don't need to repeat all steps above. You just want to flash thew newest Dragonfly.
And good news to you guys, TWRP 3.4 supports F2FS so I decided to enable F2FS support in my kernel as well. To make F2FS, please follow these steps:
1. Install my kernel v1.5
2 .Reboot to TWRP 3.4
3. Change file system of /data to F2FS
4. Replace the attached modified fstab to support F2FS of /data
5. Reboot
Note: You will lose your data.
In case you don't know:
- TWRP-3.4.0.0-G820N.zip and fstab.alphaplus for G8 Korean
- TWRP-3.4.0.0-G820UM.zip and fstab.alphalm for G8 US
Give credits to Erick G and @SGCMarkus for bringing TWRP to our phones.

Changelog:
v1.5:
- Fix touch issues for TWRP
- Add Kcal
- Add KLapse v5.0
- Update to 4.14.205
- Update lze and add lzo-lre for Zram
- Use Anykernel
v1.4:
- Import LGE v20r open source changes
- Upstream to linux-stable v4.14.203
- Upstream CAF LA.UM.8.1.r1-16200-sm8150.0
- Fix audio and OK Google hot word issues
- Improve schedutil
- Power saving workingqueues enabled by default
- Change various drivers ( MM, audio) to user power efficient workingqueues. Thanks to @Freak07 's commits
- Update sdcardfs
v1.3:
- Merge tag 'LA.UM.8.11.r1-04300-NICOBAR.0'
- Add ntfs and exfat support
v1.1 - v1.2 - Intial kernel

Good work ...mostly. Huge showstopper is the missing support for exfat/ntfs with sdcard. With USB exfat is working. Only fat32 formatted sdcards are working. But this is a nogo with files > 4GB

tron1 said:
Good work ...mostly. Huge showstopper is the missing support for exfat/ntfs with sdcard. With USB exfat is working. Only fat32 formatted sdcards are working. But this is a nogo with files > 4GB
Click to expand...
Click to collapse
Thank your for pointing it out. I just add exfat and ntfs support to v1.3. Enjoy it

tron1 said:
Good work ...mostly. Huge showstopper is the missing support for exfat/ntfs with sdcard. With USB exfat is working. Only fat32 formatted sdcards are working. But this is a nogo with files > 4GB
Click to expand...
Click to collapse
Which exact Model do you use? Is there a specific german Model nesessary?

Deutschmann said:
Which exact Model do you use? Is there a specific german Model nesessary?
Click to expand...
Click to collapse
It doesn't work on any LG g8s models...

@quantan Could you make it compatible with LG G8s models? LM-G810 is the model code

Hi Guys. The new v1.4 is just released. I have been quite busy due to family and work stuff. Here is the changelog:
- Import LGE v20r open source changes
- Upstream to linux-stable v4.14.203
- Upstream CAF LA.UM.8.1.r1-16200-sm8150.0
- Fix audio and OK Google hot word issues
- Improve schedutil
- Power saving workingqueues enabled by default
- Change various drivers ( MM, audio) to user power efficient workingqueues. Thanks to @Freak07 's commits
- Update sdcardfs

Eduxki said:
@quantan Could you make it compatible with LG G8s models? LM-G810 is the model code
Click to expand...
Click to collapse
I'll check if I can make a version for LG G8s tomorrow. However, I can't guarantee that it will work for G8s or not since I don't have that phone. @Eduxki Give me your model, e.g. LMG810EA, and your operator / country as well. Is Android 10 available for your phone now since this kernel is for Android 10

quantan said:
Hi Guys. The new v1.4 is just released. I have been quite busy due to family and work stuff. Here is the changelog:
- Import LGE v20r open source changes
-...
Click to expand...
Click to collapse
thanks for your hard work! i just installed it on my G820N with latest 20s-fw... seems to be working fine so far.
PS: installed it via TWRP, and had twrp re-inject itself into the boot-img afterwards again.... => would be nice if your prepared installer zip-file would not just include magisk, but also twrp (just as a safety-measure to not loose twrp when installing your kernel.
PPS: after your src rebase/update to that 20r kernel source drop, "dragonfly" is working with my 20s-fw image again!! your previous version with only 20a kernel src only worked until 20m (march sec-patch) firmware, neither 20o nor 20s could run stable on that 20a-kernel. gui hung, apps didn't respond etc... thankful that 20s-fw finally runs stable so far on those 20r-kernel updated version.

kimba99 said:
thanks for your hard work! i just installed it on my G820N with latest 20s-fw... seems to be working fine so far.
PS: installed it via TWRP, and had twrp re-inject itself into the boot-img afterwards again.... => would be nice if your prepared installer zip-file would not just include magisk, but also twrp (just as a safety-measure to not loose twrp when installing your kernel.
PPS: after your src rebase/update to that 20r kernel source drop, "dragonfly" is working with my 20s-fw image again!! your previous version with only 20a kernel src only worked until 20m (march sec-patch) firmware, neither 20o nor 20s could run stable on that 20a-kernel. gui hung, apps didn't respond etc... thankful that 20s-fw finally runs stable so far on those 20r-kernel updated version.
Click to expand...
Click to collapse
Thank you for your feedback. Actually in Dragonfly v1.3 I did lots of changes to schedultil based on Pixel 4 XL kernel. However it didn't work well. Sorry about that. In the v1.4, I revert the changes and make other improvement to schedutil gov.
I'll look into the TWRP injection and hopefully it will be available in v1.5 or 1.6. Any other features you guys want, please let me know.

quantan said:
Thank you for your feedback. Actually in Dragonfly v1.3 I did lots of changes to schedultil based on Pixel 4 XL kernel. However it didn't work well. Sorry about that. In the v1.4, I revert the changes and make other improvement to schedutil gov.
I'll look into the TWRP injection and hopefully it will be available in v1.5 or 1.6. Any other features you guys want, please let me know.
Click to expand...
Click to collapse
as for TWRP integration: keep in mind that there are also separate versions for INTL vs KOR edition of TWRP, just like with the kernel itself!
further ideas? :cyclops: ... fix touchscreen in recovery => code fixes already exist, check here:
https://github.com/ErickG233/LMV500-sm8150_kernel/commit/1b5b93d72ec87054ef2d80c8d955dcdaa40d4332
if i come up with additional ideas i'll let u know.
PS: it's been a while since i last modded/hacked/upgraded android kernels :good:
PPS: maybe sth like the ooooold "crossbreeder" mod =>
https://github.com/f1vefour/CrossBreeder ... but i'm unsure if this is still relevant and or working on "10"... as the original code is rather... dated

Thank you for your efforts. Is there a GSI suitable for g820?

kimba99 said:
as for TWRP integration: keep in mind that there are also separate versions for INTL vs KOR edition of TWRP, just like with the kernel itself!
further ideas? :cyclops: ... fix touchscreen in recovery => code fixes already exist, check here:
https://github.com/ErickG233/LMV500-sm8150_kernel/commit/1b5b93d72ec87054ef2d80c8d955dcdaa40d4332
if i come up with additional ideas i'll let u know.
PS: it's been a while since i last modded/hacked/upgraded android kernels :good:
PPS: maybe sth like the ooooold "crossbreeder" mod =>
https://github.com/f1vefour/CrossBreeder ... but i'm unsure if this is still relevant and or working on "10"... as the original code is rather... dated
Click to expand...
Click to collapse
- The fix for touchscreen in recovery is added to my kernel.
- I currently have no idea about TWRP. I have ramdisk with TWRP but no magisk. Can you install TWRP and Magisk then export boot.img and give it me? I will extract ramdisk from it then integrate the ramdisk to my kernel.
lufan said:
Thank you for your efforts. Is there a GSI suitable for g820?
Click to expand...
Click to collapse
Havoc, Bliss, Lineageos GSI should be good.

quantan said:
- The fix for touchscreen in recovery is added to my kernel.
- I currently have no idea about TWRP. I have ramdisk with TWRP but no magisk. Can you install TWRP and Magisk then export boot.img and give it me? I will extract ramdisk from it then integrate the ramdisk to my kernel.
Havoc, Bliss, Lineageos GSI should be good.
Click to expand...
Click to collapse
It can be used, but it can't double-click the wake-up screen, the display after the screen is not turned off, and the vibration intensity is not adjustable. I backup the g820 boot through twrp, which contains magisk. I hope you can use it
https://drive.google.com/file/d/17I-m9QdmOzn7CXH3hOl-c04Jnvd7GC3P/view?usp=sharing

wrote you a PM quantan, with my backup stuff in it likewise.
cheers and best regards =)

lufan said:
It can be used, but it can't double-click the wake-up screen, the display after the screen is not turned off, and the vibration intensity is not adjustable. I backup the g820 boot through twrp, which contains magisk. I hope you can use it
https://drive.google.com/file/d/17I-m9QdmOzn7CXH3hOl-c04Jnvd7GC3P/view?usp=sharing
Click to expand...
Click to collapse
kimba99 said:
wrote you a PM quantan, with my backup stuff in it likewise.
cheers and best regards =)
Click to expand...
Click to collapse
Could you guys test the kernel v1.5 with TWRP to make sure it work. Thank you.
https://github.com/anht3889/LGE_G820_Kernel_Caf/releases/tag/v1.5-test

quantan said:
Could you guys test the kernel v1.5 with TWRP to make sure it work. Thank you.
https://github.com/anht3889/LGE_G820_Kernel_Caf/releases/tag/v1.5-test
Click to expand...
Click to collapse
I saw this link in TG channel. It has been tested. Twrp can't access it

@lufan Have you tried it. If not please try it to double check. The ramdisk from KR boot is working.