[RECOVERY] TWRP 2.6.3.0 touch recovery [2013-09-16]
- Thread starter Dees_Troy
- Start date
Is there any reason that your recovery would not restore a backup successfully? I mean it said it did but the ROM would never boot and there are no logs for me to reference. I would do a backup/restore and both would say successful but the restore would fail 100% of the time with bootlooping. I really liked the UI but need to be able to restore in a pinch. It just so happened that I did a full wipe and could not install a ROM without boot looping or do a restore. I had to manually push a recovery image from ext4 to get my phone running again. I used 2.2.2.0 btw
There's a copy log button under advanced to copy the log to your sdcard.
Or, do it like the pros, so to speak and: adb pull /tmp/recovery.log
Also isn't a bad idea to wipe cache after a restore if your backup didn't include cache as part of the backup.
You can flash this over the stock recovery, but afaik most stock recoveries are locked down and will only install a zip that's specially signed by the manufacturer. You can use GooManager for an easy, automated install if you have root. If you don't have root then you can fastboot flash (instructions are on our website). Of course, you have to be S-off or unlocked to install a recovery no matter what method of installation you choose.
Same here - flashed with goo manager on DHD - took a backup without error.
After installing new rom - no go - sitting on boot screen - Cache cleaned before boot.
Ok - tried to factory reset - and did a clean fresh install ... no go ...
OK - tried to restore backup - holy **** - no go - same error - boot loop.
Reflashed 4EXT Recovery - installed same image - and here i am again - without my config - because Restore did not work .
Something is wrong with this recovery on DHD ! Terrible wrong ...
After installing new rom - no go - sitting on boot screen - Cache cleaned before boot.
Ok - tried to factory reset - and did a clean fresh install ... no go ...
OK - tried to restore backup - holy **** - no go - same error - boot loop.
Reflashed 4EXT Recovery - installed same image - and here i am again - without my config - because Restore did not work .
Something is wrong with this recovery on DHD ! Terrible wrong ...
When I go into adb sideload mode, 'adb devices' shows nothing. It just shows 'List of devices attached'. When I go out of adb sideload mode, it shows '<device ID> recovery'. I can't use 'adb sideload <filename>.zip' because it doesn't recognize my phone. I know there's something I'm not doing right but I've searched and haven't been able to find much info regarding this. What am I doing wrong here? I have adb v1.0.29 installed on my computer.
installing, will report
edit: installed, worked smoothly, though after the reboot i got prompted for a mysl(11601) to approve for superuser access, what is this? never seen it before.
edit: installed, worked smoothly, though after the reboot i got prompted for a mysl(11601) to approve for superuser access, what is this? never seen it before.
Last edited:
Similar threads
- Locked
- Poll
- Locked
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
28Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s 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.32
You can use Droid explorer to reboot into recovery without any volume keys. this is a computer application that is able to read your device in any stage, booting, recovery and even during bootanimation.
Just boot up ur device and connect it to your computer
Launch droid explorer
wait for device to be detected and connected
goto tools and reboot into recovery
Done.2very good!
the option to wipe cache after flashing something is very useful
only one thing i miss from 4EXT: wipe all partitions expect SD. it was so useful! i hope it will be added in the next release.
For the record:
Factory reset wipes both data and cache. Dalvik cache is part of data and cache so there's no need to wipe dalvik if you already did a factory reset. 99% of the time the ROM zip that you install wipes system for you, so you usually don't need to wipe system and doing so is just more wear and tear on your emmc chip along with wasted time.
So, for 99% of cases, a factory reset is all you need.
