FORUMS

Analysis & Opinion

Top Forum Discussions

[RECOVERY][shooter][CDMA]TWRP touch recovery - SELinux Enabled, KitKat-compatible

14,238 posts
Thanks Meter: 13,549
 
By Captain_Throwback, Retired Moderator / Recognized Contributor on 24th March 2015, 11:56 PM
Post Reply Subscribe to Thread Email Thread
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.

Phone look:


Tablet look:


CHANGELOG for 2.8.7.0:

-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option -- more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)

System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won't prompt to install SuperSU and TWRP won't try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.

resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don't take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.

This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.

CHANGELOG for 2.8.6.0:

-Fix daylight savings time rules for USA and Europe (_that)
-Allow mulitple overlays for popup boxes (Dees_Troy)
-Add pattern style password entry for decrypt (Tassadar)
-Keyboard improvements (_that)
-Update AOSP base to 5.1 (Dees_Troy)
-Reduce theme count to 5 and rely on scaling (Dees_Troy)
-Various scaling improvements (Dees_Troy)
-Improved handling of resources in the GUI (_that)
-Make scroll bar size proportional to list size (_that)
-Allow scoll lists to render without a header (_that)
-Make console scroll per pixel with kinetic scrolling (_that)
-Support styles in XML to reduce XML size and improve consistency (Dees_Troy)
-Various other fixes and improvements (mdmower, bigbiff, codelover, etc)

CHANGELOG for 2.8.5.0:

-Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
-Backups can now be cancelled while the backup is in progress (does not include restore because we don't want to leave your device in a bad state)
-Improve thread handling and move input handling into the main rendering thread to improve stability
-Make MTP work even if unplugged and plugged back in
-Unify scrollable list code and make kinetic scrolling feel more natural
-Fix handling of mapped zip files for OTA updates (CM12 updater)
-USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
-Other small fixes and improvements

CHANGELOG for 2.8.4.0:

-Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
-Fix some MTP related crashes and bugs
-Eliminate TWRP toggling USB IDs during boot if MTP is enabled
-Fix various adb sideload issues
-Improve threading of actions
-Eliminate separate thread for screen timeout
-Update libblkid to 2.25.0
-Use power button as back button on watch themes for easier navigation
-Add mutex locking to data manager
-Improve custom theme handling on encrypted devices
-Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens

CHANGELOG for 2.8.3.0:

-MTP will now tell the host PC that storage is removed instead of disabling MTP completely
-MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
-Update and improve fix permissions and make fixing contexts optional
-Update SuperSU in TWRP to 2.40 and update install process
-Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
-Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
-Fix kernel panic during MTP start on some devices
-Support unicode fonts on devices with True Type Font support
-Fix slider value not showing sometimes (vibration settings page)
-Toggle MTP off during adb sideload to set correct USB IDs
-Reduce library requirements for 5.0 L decrypt
-Other minor fixes and improvements

Note: Starting with TWRP 2.8.2.0 and higher, adb sideload uses a new sideload method originally implemented in AOSP recovery. You will need the latest adb binaries to use sideload in these newer versions of TWRP. The version required is 1.0.32. You can find the version by running "adb version" on your computer. The new sideload feature no longer stores the zip on your device. Instead, a fuse file system is created in RAM and the zip is streamed from your computer. This puts less wear and tear on storage and ensures that large zips will not fill up all of your RAM. The sideload may spit an error on your PC side, but the zip should install just fine on your device.

CHANGELOG for 2.8.2.0:
-Pull in all changes from Android 5.0 lollipop into TWRP
-Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
-Revert some changes to exFAT that were breaking exFAT support on some devices
-Other minor fixes and updates

NOTE: ONLY AOSP/GPE decryption is supported!! TWRP CANNOT (currently) decrypt HTC Sense ROMs!!

DOWNLOAD:
You can find more information and download links on our website!

BUGS:
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log to SD, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed.

If your issue is determined to be 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 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.

XDA:DevDB Information
TeamWin Recovery Project (TWRP), Tool/Utility for the HTC EVO 3D

Contributors
Captain_Throwback, Dees_Troy, bigbiff, _that
Source Code: https://github.com/TeamWin/android_device_htc_shooter


Version Information
Status: Stable
Current Stable Version: 2.8.7.0
Stable Release Date: 2015-06-22

Created 2015-03-24
Last Updated 2015-06-23
The Following User Says Thank You to Captain_Throwback For This Useful Post: [ View ]
 
 
24th March 2015, 11:56 PM |#2  
Captain_Throwback's Avatar
OP Retired Moderator / Recognized Contributor
Flag Bensalem, PA
Thanks Meter: 13,549
 
10
Donate to Me
More
Device-specific Information
Device specific page on our website

Download link to current and past versions
Last edited by Captain_Throwback; 26th March 2015 at 06:57 PM.
25th March 2015, 12:04 AM |#3  
jcfunk's Avatar
Senior Member
Thanks Meter: 409
 
More
Congrats glad to see, shoot was not left behind. I know this took lots work to be current again.
The Following User Says Thank You to jcfunk For This Useful Post: [ View ]
25th March 2015, 03:32 AM |#4  
Jbb3393's Avatar
Senior Member
Flag Seattle
Thanks Meter: 185
 
More
Amazing. Its crazy to see you across so many devices. Do I recall you from themikmik as well? My shooter is at work at the moment (stays there as the work music player) but will try this as soon as I get my hands on it.
It might take a minute but I'm a fan of flashable zip upgrades, mind if I make make one and upload?
25th March 2015, 03:41 AM |#5  
Captain_Throwback's Avatar
OP Retired Moderator / Recognized Contributor
Flag Bensalem, PA
Thanks Meter: 13,549
 
10
Donate to Me
More
Quote:
Originally Posted by Jbb3393

Amazing. Its crazy to see you across so many devices. Do I recall you from themikmik as well? My shooter is at work at the moment (stays there as the work music player) but will try this as soon as I get my hands on it.
It might take a minute but I'm a fan of flashable zip upgrades, mind if I make make one and upload?

Yes, that's me .

Feel free to make whatever you'd like. I won't be making them as part of the official update, though.
The Following User Says Thank You to Captain_Throwback For This Useful Post: [ View ]
25th March 2015, 03:50 AM |#6  
Jbb3393's Avatar
Senior Member
Flag Seattle
Thanks Meter: 185
 
More
Quote:
Originally Posted by Captain_Throwback

Yes, that's me .

Feel free to make whatever you'd like. I won't be making them as part of the official update, though.

Was trying to PM you to keep the off topic conversation outta your thread, but I got a message saying you cannot receive pm's?? While I'm here though... I checked in at the website just the other day and it is quite there, is aamikam still around? I really loved and respected his work
26th March 2015, 02:03 AM |#7  
jcfunk's Avatar
Senior Member
Thanks Meter: 409
 
More
Hey Captain_Throwback, I was looking at BoardConfig.mk

Edit: looks like those list in BoardConfig.mk maybe GSM layout

There is an issue I seen, partition layout changes if your htc unlocked, or not. I haven't htc dev unlocked my phone. Here's what mine looks like.
cat /proc/emmc
dev: size erasesize name
mmcblk0p17: 00040000 00000200 "misc"
mmcblk0p22: 00fffc00 00000200 "recovery"
mmcblk0p21: 01000000 00000200 "boot"
mmcblk0p23: 31fffc00 00000200 "system"
mmcblk0p32: 00140200 00000200 "local"
mmcblk0p25: 06ebde00 00000200 "cache"
mmcblk0p24: 4aabc400 00000200 "userdata"
mmcblk0p28: 01400000 00000200 "devlog"
mmcblk0p30: 00040000 00000200 "pdata"
mmcblk0p18: 02800000 00000200 "radio"
mmcblk0p19: 007ffa00 00000200 "radio_config"
mmcblk0p26: 00400000 00000200 "modem_st1"
mmcblk0p27: 00400000 00000200 "modem_st2"
mmcblk0p8: 00c00200 00000200 "wimax"
mmcblk0p33: 007ffa00 00000200 "udata_wimax"
Last edited by jcfunk; 26th March 2015 at 02:42 AM.
26th March 2015, 03:08 AM |#8  
Captain_Throwback's Avatar
OP Retired Moderator / Recognized Contributor
Flag Bensalem, PA
Thanks Meter: 13,549
 
10
Donate to Me
More
Quote:
Originally Posted by jcfunk

Hey Captain_Throwback, I was looking at BoardConfig.mk

Edit: looks like those list in BoardConfig.mk maybe GSM layout

There is an issue I seen, partition layout changes if your htc unlocked, or not. I haven't htc dev unlocked my phone. Here's what mine looks like.
cat /proc/emmc
dev: size erasesize name
mmcblk0p17: 00040000 00000200 "misc"
mmcblk0p22: 00fffc00 00000200 "recovery"
mmcblk0p21: 01000000 00000200 "boot"
mmcblk0p23: 31fffc00 00000200 "system"
mmcblk0p32: 00140200 00000200 "local"
mmcblk0p25: 06ebde00 00000200 "cache"
mmcblk0p24: 4aabc400 00000200 "userdata"
mmcblk0p28: 01400000 00000200 "devlog"
mmcblk0p30: 00040000 00000200 "pdata"
mmcblk0p18: 02800000 00000200 "radio"
mmcblk0p19: 007ffa00 00000200 "radio_config"
mmcblk0p26: 00400000 00000200 "modem_st1"
mmcblk0p27: 00400000 00000200 "modem_st2"
mmcblk0p8: 00c00200 00000200 "wimax"
mmcblk0p33: 007ffa00 00000200 "udata_wimax"

Those lines are all commented out, i.e. they're just informational. It has no effect on the actual recovery.

If I get a chance I'll update it so it's right, but if you check the recovery.log and fstab you'll see the mounts are correct.

EDIT: Weird that misc would move like that, but fortunately recovery doesn't really use it anyway. I should probably just comment it out.
Last edited by Captain_Throwback; 26th March 2015 at 03:11 AM.
26th March 2015, 11:50 AM |#9  
jcfunk's Avatar
Senior Member
Thanks Meter: 409
 
More
With my version or at less my kernel, I can confirm otg usb is working, mouse and drive. If possible like twrp for other devices can you add usb otg to mount options? Are you still having off mode charging issue? That was why I didn't use philz, had to make my own for f2fs support.
26th March 2015, 12:24 PM |#10  
Captain_Throwback's Avatar
OP Retired Moderator / Recognized Contributor
Flag Bensalem, PA
Thanks Meter: 13,549
 
10
Donate to Me
More
Quote:
Originally Posted by jcfunk

With my version or at less my kernel, I can confirm otg usb is working, mouse and drive. If possible like twrp for other devices can you add usb otg to mount options? Are you still having off mode charging issue? That was why I didn't use philz, had to make my own for f2fs support.

USB-OTG just needs kernel support (unless it's there by default, in which case it just needs to be added to fstab). If you have some kernel patches for it I can try adding them to my prebuilt kernel.

The offmode charging isn't broken - I was just trying to add the progress pngs some of the newer devices have. That didn't work out, but the devices charges fine.

But again, the whole point of open source is so that you can contribute to the project. Maybe you can find someone with a computer you can borrow/use to contribute directly?
26th March 2015, 03:33 PM |#11  
jcfunk's Avatar
Senior Member
Thanks Meter: 409
 
More
Quote:
Originally Posted by Captain_Throwback

USB-OTG just needs kernel support (unless it's there by default, in which case it just needs to be added to fstab). If you have some kernel patches for it I can try adding them to my prebuilt kernel.

The offmode charging isn't broken - I was just trying to add the progress pngs some of the newer devices have. That didn't work out, but the devices charges fine.

But again, the whole point of open source is so that you can contribute to the project. Maybe you can find someone with a computer you can borrow/use to contribute directly?

Where is your source, so I can make some patches.

Read More
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes