Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Thread Closed

[RECOVERY/M8_UL_CA] TWRP 2.7.0.4 Touch Recovery [2014-04-09]

OP jmz

28th March 2014, 11:06 PM   |  #1  
jmz's Avatar
OP Recognized Developer / Retired Forum Moderator
Flag Virginia Beach
Thanks Meter: 4,296
 
3,499 posts
Join Date:Joined: Sep 2008
Donate to Me
More
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:


What's new in 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.

What's new in 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

What's new in 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

Download
Last edited by jmz; 13th April 2014 at 06:10 PM.
The Following 50 Users Say Thank You to jmz For This Useful Post: [ View ]
28th March 2014, 11:07 PM   |  #2  
jmz's Avatar
OP Recognized Developer / Retired Forum Moderator
Flag Virginia Beach
Thanks Meter: 4,296
 
3,499 posts
Join Date:Joined: Sep 2008
Donate to Me
More
Huge shoutouts go specifically to
@Flemmard @bigbiff @Dees_Troy

I learned how to properly deal with DTB from these guys....

Known Issues:
No known issues anymore


No exFAT support. Need kernel source to investigate. This is only temporary. FAT32 works perfectly fine.
Random segfaults when starting actions. i.e. flashing restoring, backing up. Just makes you redo what you were trying to do. Dees_troy deems this nearly impossible to trace.
Last edited by jmz; 10th April 2014 at 02:47 AM.
The Following 6 Users Say Thank You to jmz For This Useful Post: [ View ]
28th March 2014, 11:45 PM   |  #3  
hmm wondering if this will work for the ATT variant since the DTB is variant specific usually, at least thats how it was on the G2.
28th March 2014, 11:49 PM   |  #4  
Stephen's Avatar
Forum Moderator / Retired Recognized Developer
Thanks Meter: 4,402
 
6,303 posts
Join Date:Joined: Jul 2010
Just wondering about off mode charging. Is it ok? I know there were issues with 2.7 on the m7. I was just wondering are the same issues present in the m8?
29th March 2014, 12:21 AM   |  #5  
Member
Thanks Meter: 22
 
87 posts
Join Date:Joined: Oct 2010
More
Whenever I finish flashing a ROM the screen goes off immediately, doesn't give me the chance to reboot. Doesn't seem right?
29th March 2014, 12:53 AM   |  #6  
jaythenut's Avatar
Senior Member
Thanks Meter: 1,645
 
5,467 posts
Join Date:Joined: Sep 2012
More
nice one thanks i can backup to ext sd now
29th March 2014, 02:06 AM   |  #7  
jmz's Avatar
OP Recognized Developer / Retired Forum Moderator
Flag Virginia Beach
Thanks Meter: 4,296
 
3,499 posts
Join Date:Joined: Sep 2008
Donate to Me
More
Quote:
Originally Posted by djkinetic

hmm wondering if this will work for the ATT variant since the DTB is variant specific usually, at least thats how it was on the G2.

im using it on ATT version just fine

Quote:
Originally Posted by Ghost

Just wondering about off mode charging. Is it ok? I know there were issues with 2.7 on the m7. I was just wondering are the same issues present in the m8?

off mode charging works just fine.

Quote:
Originally Posted by guywithdesire1992

Whenever I finish flashing a ROM the screen goes off immediately, doesn't give me the chance to reboot. Doesn't seem right?

In the second post, it talks about this.
29th March 2014, 02:12 AM   |  #8  
Quote:
Originally Posted by jmz

im using it on ATT version just fine



off mode charging works just fine.



In the second post, it talks about this.

Excellent just wanted to make sure as DTB can be kind of a pain, when it comes to different variants.
The Following User Says Thank You to djkinetic For This Useful Post: [ View ]
29th March 2014, 02:14 AM   |  #9  
jmz's Avatar
OP Recognized Developer / Retired Forum Moderator
Flag Virginia Beach
Thanks Meter: 4,296
 
3,499 posts
Join Date:Joined: Sep 2008
Donate to Me
More
Quote:
Originally Posted by djkinetic

Excellent just wanted to make sure as DTB can be kind of a pain, when it comes to different variants.

From the experimenting that has been done all the GSM DTBs are compatible with each other. And all the CDMA DTBs are compatible with each other. But not between GSM and CDMA.
29th March 2014, 02:26 AM   |  #10  
Well i just tried on my m8 att variant and i get stuck at the teamwin curtain screen go figure lol

Thread Closed Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes