FORUMS

Galaxy S6 & Edge get €100 Price Cut—New Models Incoming

Samsung has dropped the price of both the Galaxy S6 and S6 Edge by … more

How To Port Fully Featured Sony Xperia Z4 Camera

Xperia Z4’s hardware may not impress, but its software is definitely … more

Experimental TWRP Available For Moto G 2015

XDA Senior Member squid2 has posted experimental builds of TWRP for the Moto G … more

Sunday Debate: How Can We Get a No-Compromise Phone?

Join us in a fun Sunday Debate on Compromises. Come with your opinions and … more

[RECOVERY][p4noterf] TWRP 2.8.7.0 touch recovery [2015-06-23]

1,657 posts
Thanks Meter: 10,767
 
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)

Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.

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 consistentcy (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

DOWNLOAD:
Most devices can be updated quickly and easily with the TWRP Manager app:
Play Store Link
1) Install TWRP Manager from the Play Store
2) Open TWRP Manager and provide root permissions
3) Hit Advanced->Install Recovery
4) Verify the correct device name on your screen then press Install Recovery if the correct device is showing
OR:
You can find more information and download links on our NEW website! NOTE that the 2.8.6.0 version is ONLY available on our new site and is not available on our other, older mirrors!

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.
Last edited by Dees_Troy; 23rd June 2015 at 02:53 PM.
The Following 38 Users Say Thank You to Dees_Troy For This Useful Post: [ View ]
 
 
24th August 2012, 08:32 PM |#2  
BeerChameleon's Avatar
Senior Member
Flag Tucson,Arizona.
Thanks Meter: 1,206
 
Donate to Me
More
Will this work with N0813?

Also should i install it via goo?

Also THANKS!!!


Edit worked awesome!!!

Thanks again, no more buggy cwm!!!!
Last edited by BeerChameleon; 24th August 2012 at 08:36 PM.
24th August 2012, 08:44 PM |#3  
hkeyman's Avatar
Senior Member
Flag Ventura, Ca.
Thanks Meter: 84
 
More
Yes, Working on GT-N8013
Quote:
Originally Posted by davidrules7778

Will this work with N0813?

Also should i install it via goo?

Also THANKS!!!


Edit worked awesome!!!

Thanks again, no more buggy cwm!!!!

Works and Yes install through GOO is fine. Only issue experienced from the install so far is when in recovery trying to type or select sometimes creates double entries or backs out of the function completely. But aside from that it is working as expected.
Attached Thumbnails
Click image for larger version

Name:	TWRP-GT-N8013.jpg
Views:	5124
Size:	255.4 KB
ID:	1280691  
The Following User Says Thank You to hkeyman For This Useful Post: [ View ]
24th August 2012, 08:50 PM |#4  
Senior Member
Thanks Meter: 118
 
More
Quote:
Originally Posted by hkeyman

Works and Yes install through GOO is fine. Only issue experienced from the install so far is when in recovery trying to type or select sometimes creates double entries or backs out of the function completely. But aside from that it is working as expected.

so awesome to have this on the note.

just wondering, does installing this through goo fix the problem we had with CWM root method where if you boot into recovery it would auto write a script to reinstall the standard recovery? right now i am rooted but because of this bug with the new firmware my CWM is gone and i haven't used the adb instructions to fix it.

once you use TWRP you'll never go back to CWM imo
24th August 2012, 08:51 PM |#5  
BeerChameleon's Avatar
Senior Member
Flag Tucson,Arizona.
Thanks Meter: 1,206
 
Donate to Me
More
Quote:
Originally Posted by knives of ice

so awesome to have this on the note.

just wondering, does installing this through goo fix the problem we had with CWM root method where if you boot into recovery it would auto write a script to reinstall the standard recovery?

once you use TWRP you'll never go back to CWM imo

Not sure, but i got out of that issue with the original clockwork.

Pretty sure it will though
24th August 2012, 09:15 PM |#6  
hkeyman's Avatar
Senior Member
Flag Ventura, Ca.
Thanks Meter: 84
 
More
Still rooted...
Quote:
Originally Posted by davidrules7778

Not sure, but i got out of that issue with the original clockwork.

Pretty sure it will though

After installing TWRP and using recovery a few times and then rebooting back into system I am not seeing any root/unroot issues. All is working normally here. Which version of the Tablet are you running? I am on the GT-N8013.
The Following User Says Thank You to hkeyman For This Useful Post: [ View ]
24th August 2012, 09:29 PM |#7  
BeerChameleon's Avatar
Senior Member
Flag Tucson,Arizona.
Thanks Meter: 1,206
 
Donate to Me
More
Quote:
Originally Posted by hkeyman

After installing TWRP and using recovery a few times and then rebooting back into system I am not seeing any root/unroot issues. All is working normally here. Which version of the Tablet are you running? I am on the GT-N8013.

I am not having issues at all

Ask the other guy

Sent from a Baked Black Jelly Belly
24th August 2012, 11:01 PM |#8  
Senior Member
Thanks Meter: 118
 
More
What I am referring to is with the latest rooting method 2 and if you are on the latest firmware when you reboot the firmware automatically rewrites the cwm image. The only way to stop this is via adb check the instructions below that are to be used in the current method


0) Copy the SU/superSU zip file to your tablet.1) Boot into ODIN mode by holding volume down and power. Volume down is the one closest to power.2) Open ODIN on your computer, select the CWM tar.md5 file in the PDA slot, uncheck auto reboot.3) Hit start. It should flash recovery successfully4) Now you want to boot directly into CWM, or you'll lose it. So while holding down volume UP (the one farther from power), hold down the power button. When you see the Samsung Galaxy Note 10.1 logo, let go of power, or else you'll keep rebooting, but keep holding volume UP. Or at least that's what I had to do, which was kind of surprising coming from other Samsung devices.5) Once in CWM, flash the superSU zip file. Congratulations, you have root, but if you reboot now the firmware will nuke CWM. We don't want to have to flash it again, so let's remove the shell script that nukes CWM.6) Under mounts and storage in CWM, mount system.7) Back on your computer, run adb shell. If you forget to mount system it'll complain because it can't find sh, silly adb. For a second I thought Samsung didn't include sh out of the box and then I realized that makes no sense.8) Type su to become root9) rm /system/etc/install-recovery.sh


So anyways I personally don't know jack squat about adb so I am rooted but don't have cwm installed because it overwrite.

Flashing twrp with goo it flashes for me successfully it claims but when I reboot to recovery I still have stock recovery. I suspect because I didn't do the adb.instructions above that this is the problem

I was hoping flashing this would automatically remove that script you need to remove in adb
The Following User Says Thank You to knives of ice For This Useful Post: [ View ]
24th August 2012, 11:05 PM |#9  
Senior Member
Flag San Diego
Thanks Meter: 606
 
More
Quote:
Originally Posted by knives of ice

What I am referring to is with the latest rooting method 2 and if you are on the latest firmware when you reboot the firmware automatically rewrites the cwm image. The only way to stop this is via adb check the instructions below that are to be used in the current method


0) Copy the SU/superSU zip file to your tablet.1) Boot into ODIN mode by holding volume down and power. Volume down is the one closest to power.2) Open ODIN on your computer, select the CWM tar.md5 file in the PDA slot, uncheck auto reboot.3) Hit start. It should flash recovery successfully4) Now you want to boot directly into CWM, or you'll lose it. So while holding down volume UP (the one farther from power), hold down the power button. When you see the Samsung Galaxy Note 10.1 logo, let go of power, or else you'll keep rebooting, but keep holding volume UP. Or at least that's what I had to do, which was kind of surprising coming from other Samsung devices.5) Once in CWM, flash the superSU zip file. Congratulations, you have root, but if you reboot now the firmware will nuke CWM. We don't want to have to flash it again, so let's remove the shell script that nukes CWM.6) Under mounts and storage in CWM, mount system.7) Back on your computer, run adb shell. If you forget to mount system it'll complain because it can't find sh, silly adb. For a second I thought Samsung didn't include sh out of the box and then I realized that makes no sense.8) Type su to become root9) rm /system/etc/install-recovery.sh


So anyways I personally don't know jack squat about adb so I am rooted but don't have cwm installed because it overwrite.

Flashing twrp with goo it flashes for me successfully it claims but when I reboot to recovery I still have stock recovery. I suspect because I didn't do the adb.instructions above that this is the problem

I was hoping flashing this would automatically remove that script you need to remove in adb

Actually, you don't need to use ADB, but that was just the fastest way to do it for me. The script doesn't remove root so you can let it boot up and delete the sript using a root file explorer (these days I'm partial to Solid Explorer Beta). But you'll just have to flash CWM a second time if you let it boot up once.
25th August 2012, 12:15 AM |#10  
Senior Member
Flag Snedsted
Thanks Meter: 14
 
More
Info 2 No recovery found using GooManager
I tried installing TWRP through GooManager, but after several minutes of 'Looking for recoveries...' I guess it gave up

Device: GT-N8000 (EU WiFi+3G).
25th August 2012, 12:26 AM |#11  
Senior Member
Thanks Meter: 118
 
More
Quote:
Originally Posted by iofthestorm

Actually, you don't need to use ADB, but that was just the fastest way to do it for me. The script doesn't remove root so you can let it boot up and delete the sript using a root file explorer (these days I'm partial to Solid Explorer Beta). But you'll just have to flash CWM a second time if you let it boot up once.

Thanks.

Seems like goo is down again so as soon as its up we will see if this works

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

Advanced Search
Display Modes