Database Develop

[RECOVERY][sirius] TWRP 2.7.0.0 Touch Recovery {UNOFFICIAL} [STOPPED]

[RECOVERY][sirius] TWRP 2.7.0.0 Touch Recovery {UNOFFICIAL} [STOPPED]
DooMLoRD said:
since official TWRP is released by @Dees_Troy i am closing this thread!
http://forum.xda-developers.com/showthread.php?t=2772879
thanks to all the devs that make it happen!
regards,
DooMLoRD
Click to expand...
Click to collapse
-------------------------------------------------------------------------------------------------------------
Team Win Recovery Project 2.x, or twrp2 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.
Huge thanks to @Dees_Troy & his team for their excellent work on TWRP! This is a DIRECT port from the Xperia Z1 (honami)!
Phone look:
Tablet look:
CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes
Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
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.
DOWNLOAD:
Kernels will be provided as recovery flashable update.zips! If you dont have existing recovery just open the kernel package using WinZip/WinRAR/7zip extract the boot.img and flash it using fastboot!
FW: 17.1.1.A.0.402
Advanced Stock Kernel with TWRP Recovery v01
MD5HASH: 501a2d64bfb2984aa51817ec8c1a0c55
regards,
DooMLoRD
XDA:DevDB Information
[RECOVERY][sirius] TWRP 2.7.0.0 Touch Recovery {UNOFFICIAL}, Kernel for the Sony Xperia Z2
Contributors
DooMLoRD, Dees_troy, [NUT]
Kernel Special Features: Stock kernel with TWRP Touch Recovery inbuilt!
Version Information
Status: Stable
Created 2014-05-27
Last Updated 2014-06-10

Thanks Bro.... Big tthanks

Great, thx for your work!
Gesendet von meinem D6503 mit Tapatalk

Nice work DooMLord!
Thanks.
Regards peterle

Awesome

Nicccce
Sent from my D6503 using XDA Premium 4 mobile app

Hello everyone
I'm back to this part of forum with 3rd Xperia Z2
But back to the plot. I've flashed this recovery in CWM. And gues what happened... I have 2 recoveries. One is CWM and second is this. Exiting CWM recovery -> enters TWRP
I have DoomKernel V7, Monxdified rom.
Thank in advance!
Cheers!

amon87 said:
Hello everyone
I'm back to this part of forum with 3rd Xperia Z2
But back to the plot. I've flashed this recovery in CWM. And gues what happened... I have 2 recoveries. One is CWM and second is this. Exiting CWM recovery -> enters TWRP
I have DoomKernel V7, Monxdified rom.
Thank in advance!
Cheers!
Click to expand...
Click to collapse
if you are using my kernel, then it has 3 recoveries inbuilt...
if the ROM has its own recovery integrated then that could also interfere...

Wow, this is something new to me, as I came from HTC world It's absolutely no problem for me - I was more curious about what the hell I've done wrong
Huh, better two than none
Thanks for your reply and great job in modding Z2

Nice to see twrp in z2 forum. Time to get into rooting it.
Skickat från min HTC One_M8 via Tapatalk

Works great, used this to flash SuperSU and root.

If I flash this (I currently have your V7 kernel running with CWM, plus TWRP which is built in to Monx ROM), will I be able to upgrade to 2.7.1.0 using the TWRP installer? If I flash this, can I flash your latest v9 kernel over it with no problems?
Thanks,
-Hans

since official TWRP is released by @Dees_Troy i am closing this thread!
http://forum.xda-developers.com/showthread.php?t=2772879
thanks to all the devs that make it happen!
regards,
DooMLoRD

[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.

[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 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?

[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?