Post Reply

[RECOVERY] TWRP 2.6.3.0 touch recovery [2013-09-16]

OP Dees_Troy

24th August 2012, 08:19 PM   |  #1  
Dees_Troy's Avatar
OP Senior Recognized Developer
Flag KC MO
Thanks Meter: 9,468
 
1,602 posts
Join Date:Joined: Mar 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:


Tablet look:


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

CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks

Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.

Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.

DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!

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.

XDA:DevDB Information
[RECOVERY] TWRP 2.6.3.0 touch recovery [2013-09-16], a Tool/Utility for the Samsung Galaxy Note 10.1

Contributors
Dees_Troy, bigbiff

Version Information
Status: Stable
Current Stable Version: 2.6.3.0
Stable Release Date: 2013-09-16

Created 2013-09-16
Last Updated 2013-09-16
Last edited by Dees_Troy; 30th August 2013 at 09:44 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
 
16,146 posts
Join Date:Joined: Aug 2008
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
 
278 posts
Join Date:Joined: Nov 2006
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:	4682
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: 116
 
917 posts
Join Date:Joined: Jul 2007
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
 
16,146 posts
Join Date:Joined: Aug 2008
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
 
278 posts
Join Date:Joined: Nov 2006
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
 
16,146 posts
Join Date:Joined: Aug 2008
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: 116
 
917 posts
Join Date:Joined: Jul 2007
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: 603
 
1,017 posts
Join Date:Joined: Nov 2010
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 Aalborg
Thanks Meter: 13
 
208 posts
Join Date:Joined: Jan 2010
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).

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

Advanced Search
Display Modes