Related
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.
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 M
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
What bootloader is supported? Jelly Beans or Kit Kat?
Looks like jbbl
thewraith420 said:
Looks like jbbl
Click to expand...
Click to collapse
Jellybean and KitKat images are now up.
thenameisnigel said:
Jellybean and KitKat images are now up.
Click to expand...
Click to collapse
could you please add md5 or sha1 checksums to the respective downloads so we can verify we have the correct/complete download. thanks a lot!
Just flashed the kk version. The display is the wrong DPI the RAZR m is hdpi, this seems to be xhdpi. The menus show but are extra large and the cot logo isn't showing at all. also touch isn't working.
thewraith420 said:
Just flashed the kk version. The display is the wrong DPI the RAZR m is hdpi, this seems to be xhdpi. The menus show but are extra large and the cot logo isn't showing at all. also touch isn't working.
Click to expand...
Click to collapse
Send me the recovery logs, and I'll take a look at it.
Sent from my XT1080 using Tapatalk
Screenshots!
---------- Post added at 01:52 PM ---------- Previous post was at 01:49 PM ----------
drewwalton19216801 said:
Screenshots!
Click to expand...
Click to collapse
@thewraith420
Is this compatible with the XT905 or just the XT907?
purebasshavoc said:
Is this compatible with the XT905 or just the XT907?
Click to expand...
Click to collapse
All Moto_MSM8960 devices.
can you backup and restore (and flash zips) from USB OTG?
New recovery is here with in-built nvram backup/restore plus rainbow effect support
Just a CWM Based Recovery with awesome feature such as rainbow effect,nvram backup/restore, others find yourself
Installation:: Same as all recoveries
Info:: If recovery automatically reboots press vol + button simultaneously to boot into Boot Menu then Select recovery mode Carliv will boot and it will work normally.
Download Home::
Bugs fixed!! Carliv recovery is now stable
Download here
Credits::
A special thank to the below, and ALL who I do not mention but did contribute a lot with their efforts
@carliv for his recovery and easy guide
@karan1038 for his support
Me for porting this recovery
XDA : DevDB Information
Carliv Touch - ClockworkMod Based Recovery,
Tool/Utility for the Android General
Contributors:
@Swapnil Solanki
Version Information:
Status: V1
Created 2014-12-06
Please Press thanks button if you like my work
Reserved
Hangs and reboots if I try to change any setting, for example enable rainbow mode ,etc.
Sent from my A1 using XDA Free mobile app
akhil1999 said:
Hangs and reboots if I try to change any setting, for example enable rainbow mode ,etc.
Sent from my A1 using XDA Free mobile app
Click to expand...
Click to collapse
Not happening in my phone but I'll check it out for that thnx for reporting
Nice work #Swapnil Solanki ! BTW I'll try it today and report you!:good::good:
Shreeshu10 said:
Nice work #Swapnil Sonlanki ! BTW I'll try it today and report you!:good::good:
Click to expand...
Click to collapse
Thanks shreeshu!! Report me the bugs for sure!!
:good::good::good: its Carvil Touch OR Carliv Touch Recovery
harsh0143 said:
:good::good::good: its Carvil Touch OR Carliv Touch Recovery
Click to expand...
Click to collapse
Carliv Touch Recovery
Bugs fixed!! Carliv recovery is now stable
Download here
Press thanks
Swapnil Solanki said:
Carvil Touch Recovery
Click to expand...
Click to collapse
Actually it's Carliv not Carvil You misspelled my username. Please correct in title and in your posts.
Thanks!
PS: about rebooting issue, after you test the new version, I want to see if that still happens.
carliv said:
Actually it's Carliv not Carvil You misspelled my username. Please correct in title and in your posts.
Thanks!
PS: about rebooting issue, after you test the new version, I want to see if that still happens.
Click to expand...
Click to collapse
Sorry for the misspelling.. is new version available now
Swapnil Solanki said:
Sorry for the misspelling.. is new version available now
Click to expand...
Click to collapse
No problem.
It's available for build from source now, and it will be available for porting in one-two days (I'm finishing now the port builds - I have 45 left x 20 min).
Cheers!
carliv said:
No problem.
It's available for build from source now, and it will be available for porting in one-two days (I'm finishing now the port builds - I have 45 left x 20 min).
Cheers!
Click to expand...
Click to collapse
When it will we available notify me! I'll port it!!
Great work
---------- Post added at 10:58 AM ---------- Previous post was at 10:56 AM ----------
Post some pics
Devam03 said:
Great work
---------- Post added at 10:58 AM ---------- Previous post was at 10:56 AM ----------
Post some pics
Click to expand...
Click to collapse
Thnx! Screenshots will be posted soon when I'll get free time! Carliv 3.0 coming soon!
Keep thanking! My work will continue for Sprout!
:good:
Team Win Recovery Project 3.x, or TWRP3.x 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.
Code:
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Download : TWRP 3.0.2 For Markw
Source Device Tree: Device Tree For Building TWRP
From github I also see you try to build LineageOS 13, thanks
Anyone tried it? Can you post some screenshot?
deviantenator said:
Anyone tried it? Can you post some screenshot?
Click to expand...
Click to collapse
Working like charm. Screenshots? Looks like every other twrp.
alreadyregistered said:
Working like charm. Screenshots? Looks like every other twrp.
Click to expand...
Click to collapse
flashed it! found no bugs
This TWRP version didn't work with my encrypted phone, does any one have this issue?
Thanks
Gesendet von meinem MI MAX mit Tapatalk
How install twrp on my prime? And root would be ideal... Thanks so much for your help (===
Raggamuffin17 said:
How install twrp on my prime? And root would be ideal... Thanks so much for your help (===
Click to expand...
Click to collapse
fastboot flash recovery twrp.img
fastboot boot twrp.img
Thanks.
But is there any different from TWRP 3.0.2 .0 cofface ? and/or Twrp Xiaomi Redmi 4 Pro By Anik1199
Is it original official release from Team Win Recovery Project 3.x, or TWRP3.x ?
coolpixs4 said:
Thanks.
But is there any different from TWRP 3.0.2 .0 cofface ? and/or Twrp Xiaomi Redmi 4 Pro By Anik1199
Is it original official release from Team Win Recovery Project 3.x, or TWRP3.x ?
Click to expand...
Click to collapse
Since Anik TWRP has been made official, you can safely ignore this build
dels07 said:
Since Anik TWRP has been made official, you can safely ignore this build
Click to expand...
Click to collapse
Can you explain pls how to use this Anik TWRP? Hope root/xposed info' would be great appreciated too, thanks
Raggamuffin17 said:
Can you explain pls how to use this Anik TWRP? Hope root/xposed info' would be great appreciated too, thanks
Click to expand...
Click to collapse
Refer to this thread
https://forum.xda-developers.com/android/development/unofficial-twrp-3-0-2-0-recovery-redmi-t3550074
dels07 said:
Since Anik TWRP has been made official, you can safely ignore this build
Click to expand...
Click to collapse
Hi dels07,
I make a mistake by using this unofficial build, i can't boot to miui system now. I read your comment in here mention about this. What should i do? flashing miui rom?
---------- Post added at 12:12 AM ---------- Previous post was at 12:05 AM ----------
adzymaniac said:
Hi dels07,
I make a mistake by using this unofficial build, i can't boot to miui system now. I read your comment in here mention about this. What should i do? flashing miui rom?
Click to expand...
Click to collapse
I got it. Just need enter fastboot, re-flash the twrp and boot. Copy the lazyflasher (i think can't do that before), and flash it, reboot, done. Thanks dels07
alreadyregistered said:
fastboot flash recovery twrp.img
fastboot boot twrp.img
Click to expand...
Click to collapse
is there any other way to boot recovery (with key combination ) other then fastboot boot recovery.img ?
Dadovvv said:
is there any other way to boot recovery (with key combination ) other then fastboot boot recovery.img ?
Click to expand...
Click to collapse
voL+, vol-, power at once
If you have root, there are some apps that will boot into recovery for you.
Is backup working properly? No unable to unmount /system error?
Thank you for making twrp rec, update it asap.
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?