Database Develop

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

Team 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.

Great to have a second choice! I'm still using RomRacer though.

A great clockwork alternative!
Flashed it and it looks great! Haven't tested it out fully but i wish I could use the internal partition because my sdcard is pretty full and the battery percentage would show. Unless i find a reason to switch back to cwm, Ill keep this.

Any plans on adding support for CM7 based roms? Only /sdcard is being recognized, /emmc isn't available at all.
*Edit* Also wanted to include webtop (/osh) in the above question.

I also flashed it, but didn't spend much time in it (got work to do ).
Can the backup restore location be changed to point to backups that were made with other recoveries?

Download link is dead for me

rozzco said:
I also flashed it, but didn't spend much time in it (got work to do ).
Can the backup restore location be changed to point to backups that were made with other recoveries?
Click to expand...
Click to collapse
I don't think other recovery backups will be compatible. The test backup I did yesterday looks like this:
boot.emmc.win
data.ext4.win
system.ext4.win
And none of my CWM backups were showing up when navigating through my sdcard contents.

no more power button + volume down? wow. i need to slow down now
thanks for this.

anyone wana make a zip of this? im sure you will get 3x more users downloading ur recovery than before.

slojko said:
anyone wana make a zip of this? im sure you will get 3x more users downloading ur recovery than before.
Click to expand...
Click to collapse
I did yesterday. See this post from my thread in General.

ive actually been running this for a few days now and found it really awesome!
backup and restores are lightning fast and everyhting ive tried works perfectly
i found that in cm7 based ROMs only the external gets mounted. which is fine because thats what I use
Great work Team Win

Wow, this looks awesome. I just downloaded it and will load it up on my phone in a few minutes. Thanks for the awesome work TeamWin!

Great work, but i'm getting a few issues:
Everytime i try to install something,at the end of process it gives me:
E: cannot load volume /misc.
Also when i mount usb and unmount, later on i try to install something and recovery restarts itself showing homescreen, fixed by going back to usb mount screen and unchecking "unmount cache" although it's weird to see this checked, when actually i didn't check anything( i see only "unmount sd-card" checked when i leave the panel).
Hope this can be addressed soon,cause it's a very nice recovery UI
ATT Atrix 4G
Darkside 4.2
Kernel Faux 0.23 1.45Ghz @stock
Teamwin Recovery 2.0

its possible to use this on locked atrix ?
and..we have any recovery to use with an locked atrix ? i need to wipe my battery and dont know how without a custom recovery....
many tks

There are no recovery for a locked atrix(real ones at least)
Search the market for battery calibration
sent from my Atrix via XDA premium

flaviocc said:
its possible to use this on locked atrix ?
and..we have any recovery to use with an locked atrix ? i need to wipe my battery and dont know how without a custom recovery....
many tks
Click to expand...
Click to collapse
Just unlock it. Its definatley worth it. Then you can get cwm or this and wipe whatever and flash whatever.
And I have to say the recovery is very nice. Kinda weird not using volume buttons but very nice. I am also getting the can't load volume thing error.
Sent from my MB860 with ICS using xda premium

ghost_og said:
I did yesterday. See this post from my thread in General.
Click to expand...
Click to collapse
This works for me One question: can i install .zip file from internal memory,cant find internal sdcard anywhere?

dulexetina said:
This works for me One question: can i install .zip file from internal memory,cant find internal sdcard anywhere?
Click to expand...
Click to collapse
I'm guessing you're on a CM7 based ROM? Currently it only supports motoblur naming (sdcard, sd-ext). They plan on adding support for /emmc at some point. Keep a backup .zip of CWM on your sdcard just in case.

Can you guys take Rom Racer's recovery and just add the tweaks from this CWM to it? Pretty much make a touch version of Rom Racer's...

ghost_og said:
I'm guessing you're on a CM7 based ROM? Currently it only supports motoblur naming (sdcard, sd-ext). They plan on adding support for /emmc at some point. Keep a backup .zip of CWM on your sdcard just in case.
Click to expand...
Click to collapse
I am on blured rom,and even restore did not worked for me-tried many times (to restore full,just data,just system...but no succes) i am back on old recovery until this one gets fixed. This recovery is so simple to use and realy nice,just waiting for full working version now.
Sent from my MB860 using XDA App

[deprecated] [RECOVERY] [new|old bl] TWRP 2.6.0.0 touch recovery [2013-07-23]

- - - - - -​
TWRP
- Team Win Recovery Project -​
Attention:
You can find the updated TWRP recoveries by @DJNoXD in his thread here!
Remember that you can donate to TWRP here: http://www.teamw.in/project/twrp2​
This thread is deprecated.
Old content:
I have been asked to create an own thread for the TWRP recovery I compiled for the new bootloader, so here you go.
Personally I prefer TWRP over CWM, but that's for everybody to choose on their own.
We got official TWRP support for the Optimus 2x - but only for the old bootloader. You can use the GooManager app to flash the recovery (see below).
I adapted and compiled TWRP for the new bootloader and tested it for quite a while without a single problem.
Additionally I added a flashable zip recovery installer for the old bootloader if someone prefers that over the use of GooManager.
TWRP is NOT my work, but the work from TeamWin under the lead of Dees_Troy.
If you like TWRP you can donate to TeamWin here: http://www.teamw.in/project/twrp2​
Bugs?:
If you have any issues grab a log, it's really easy: Advanced -> Copy Log to SD. It will copy the log to your external sdcard.
You can post it in here, then I'll review it and forward it to Dees_Troy if it contains an error.
Or contact TWRP directly via their contact form: http://www.teamw.in/contact
I'm not interested in any complaints or bug reports that do not contain a log! Seriously, just don't.
Remember: I'm compiling this for my personal use and am sharing it with you. I don't care if you use it or not, you're free to use CWM or whatever other recovery is out there.​
Download:
http://tonyp.basketbuild.com/index.php?dir=main/P990-stuff/TWRP/
mirror: http://goo.im/devs/tonyp/P990-stuff/TWRP
http://tonyp.hopto.org/?dir=P990/TWRP (I'm only updating this if there's a goo.im outage)​
Installation:
These files are flashable zips, just flash them with your current recovery.
If you want to flash the recovery manually, extract the img files from the zips, push it to the SDCard, open the Terminal Emularot and type:
old bootloader:
Code:
su
dd if=/sdcard/openrecovery-twrp-oldbl-p990.img of=/dev/block/mmcblk0p7
new bootloader:
Code:
su
dd if=/sdcard/recovery-TWRP-newbl.img of=/dev/block/mmcblk0p8
Dees_Troy said:
Team Win Recovery Project 2.3, 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:
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.
CHANGELOG for 2.5.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.5.0.0 as your custom theme will likely not be compatible with the new changes!
-Added scrollable partition lists for mount, backup, restore, wipe, and storage selection
-Add new SliderValue GUI element for selecting brightness and screen timeout (thanks to Tassadar)
-Re-work AOSP and TWRP code to improve license compatibility between GPL and Apache
-Added official theme for 1080x1920 portrait devices (HTC One m7, HTC DNA, HTC Butterfly, Oppo Find 5, Sony Xperia Z, etc)
-Fixed a problem with directory permissions on split archive backups (backups usually restored with no app data)
-Fixed a problem with md5 verification of backups
-Added a search function to libtar (thanks to kokotas)
-Improve handling of XML errors (fix permissions)
-Fixed handling of subpartitions
-Improvements to recovery.fstab flags
-Fixed a problem with decryption not being able to locate the decryption key in some situations
CHANGELOG for 2.4.4.0:
-Added another libtar hardlink workaround to fix restore of some backups (usually related to Ubuntu Touch)
-More fixes for the file selector
-Switched from using busybox md5sum to a direct C function call
-Fixed capturing the exit status of tar based backups/restore - TWRP will display that there was an error if there was one again
-Update exFAT to latest commits
-Added a build flag to disable using the ioctl for screen blanking
CHANGELOG for 2.4.3.0:
-Fixed 2 bugs related to restore, one dealing with mknod failures (by bigbiff) and one dealing with restoring hardlinks (by Dees_Troy)
NOTE: If your backups weren't restoring correctly in earlier 2.4.x versions they should restore correctly now. Hopefully you didn't delete those backups. If you're still having problems, run the restore, go to advanced and copy log, then give us the log. Complaints without logs will be rightfully ignored.
-Added a scroll bar to file selectors and listboxes courtesy of Tassadar
-Added libblkid for more accurate detection of file systems and can now detect exFAT properly thanks to bigbiff
-Added a screen dim effect 2 seconds before screen off on some devices
-Finally fixed file selector crash (one of the joys of working with multi-threaded software)
-Fixed loading of screen timeout setting during startup
-Improvements and bugfixes to screen timeout code
-Fixed persistence of the 24 hour / military time setting
CHANGELOG for 2.4.2.0:
-Add screen timeout - screen will turn off automatically after 60 seconds, saves battery and prevents screen burn-in especially on AMOLED devices
-Add a brightness setting (requires device specific setup and only some devices have been added)
-Add a root checker and offer to install SuperSU if the device isn't already rooted
-Add a write buffer to libtar backups, significant improvements to speeds when backing up to exFAT target, minor improvements for other file systems
-Check and offer to fix root permissions if broken
-Add an option for a 24 hour clock display instead of AM/PM (aka military time)
-Move stock recovery reflash check to occur during the reboot cycle
-Add support for some MTK6xxx devices
-Change libtar to vfork to help prevent memory problems
-Add a "clicked" effect to most buttons, file selector, and listbox
-Improve timezone listbox to be more like file selector (per pixel kinetic scrolling, etc)
-Remove some no longer used settings (Forced MD5 sum on zips, size checking on image backups)
-Other minor bugfixes and improvements
CHANGELOG for 2.4.1.0:
-Fixed a problem with mkdosfs that formatted sdcards to 2GB
-Fixed handoff between vfat and exFAT on devices where blkid didn't detect vfat (fixes some issues with mounting sdcards)
-Fixed problems with changing working directory on MD5 creation/checking that may have prevented unmounting
-Backups will now store a copy of the backup log after the backup is completed (only if backup is successful)
CHANGELOG for 2.4.0.0:
-Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
-Support for exFAT formatted sdcards (also thanks to bigbiff)
-Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
-Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
-Added wipe cache and dalvik after ADB Sideload
-Replaced many system calls with their native C counterparts
-Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
-Fixed AOSP recovery commands to run after decryption on encrypted devices
-Improvements for building TWRP in CM10.1
-Other minor bugfixes and improvements
NOTE: 2.4.0.0 is, as always, still compatible with your older backups!
DOWNLOAD:
The fastest and easiest way to install TWRP [tonyp note: for the old bootloader version!] 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.
Click to expand...
Click to collapse

TWRP does support a great theme engine, see here: http://www.teamw.in/project/twrp2themers
If you know of nice themes for our HDPI (480x800) device or created your own please post them here
Personally I'd love to get the Holo Theme by thecoby xdhpi theme to get ported to our hdpi device:
http://forum.xda-developers.com/showthread.php?t=1942309
I don't have time to do that at the moment, so I'm posting it here if someone is interested in doing it.
If not I'll do it once I find the time.
Thanks to aldyu we do have the Holo Dark Theme now fully functional for our device!
Check out his post here and don't forget to press thanks!
Installation:
Download the theme, rename it to ui.zip, create the folder /TWRP/theme at the internal SDCard and put the zip into it.
Preview:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

reserved

Great! i tried twrp when you posted in thread cm10 pa, has more options than cwm, but has bugs in other roms???

[480x800] TWRP Holo Theme - Light / Dark

Thanks for the awesome recovery port!
The button between home and back broke the recovery (or was it the theme?). After I pressed the button and pulled the battery the TWRP screen kept on flashing and never entered the recovery (or let me boot the phone). I had to NVFlash to get my device back. Flashed it again same problem. Deleted TWRP folder, now it works flawlessly.
TWRP Theme - Holo Light

kukharski said:
[480x800] TWRP Holo Theme - Light / Dark
Click to expand...
Click to collapse
Thanks, didn't see it. Although it's not finished yet according to the posts in the thread it does look nice
C0D3N1N3R said:
Thanks for the awesome recovery port!
The button between home and back broke the recovery (or was it the theme?). After I pressed the button and pulled the battery the TWRP screen kept on flashing and never entered the recovery (or let me boot the phone). I had to NVFlash to get my device back. Flashed it again same problem. Deleted TWRP folder, now it works flawlessly.
TWRP Theme - Holo Light
Click to expand...
Click to collapse
Eh, certainly not TWRP's fault. Maybe the themes. Or no idea what you did
The button is for displaying the recovery log, pressing it again will remove the log again.
I've been using this quite often when I was testing every aspect of the recovery to ensure it's safe.

I tried pressing it again but the log didn't disappear. Flashed it again and not it works!
Oh and the time is not correct

you have to set the time manually in settings?!
btw tony thanks a lot - really appreciate your work! i waited so long for TWRP on new bootloader! everything works great so far! you are such a huge WIN for all p990 owners!
THANKS

oh wow, this is very nice, better as CWM Touch recovery 6x.x.x i think.

AW: [RECOVERY] [new|old bl] TWRP 2.3.3.0 touch recovery [2013-01-19]
Why can' t I see the batterystatus?
Gesendet von meinem LGP990 mit CM10.

Thanks tonyp

Re: [RECOVERY] [new|old bl] TWRP 2.3.3.0 touch recovery [2013-01-19]
Unbeliveable! Thx Tonyp!!!

I updated my TWRP to 2.4, please update it!
http://goo.im/devs/tonyp/P990-stuff/TWRP
More details later, gtg now.

Re: [RECOVERY] [new|old bl] TWRP 2.4.0.0 touch recovery [2013-02-01]
I'm sorry for the noob questions but i have lots of backups from CWM, does those backups work on TWRP?
Really interested in using this recovery (no more button mashing) and the possibility to rename the backups is awesome.
Thank you very much Tony!!
Sent from my LG-P990 using xda app-developers app

I.m.Tuga said:
I'm sorry for the noob questions but i have lots of backups from CWM, does those backups work on TWRP?
Really interested in using this recovery (no more button mashing) and the possibility to rename the backups is awesome.
Thank you very much Tony!!
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
No, you can not use it.
The best option was i missed in CWM is flash in Batch-Mode. But the clock and the battery status are a funny gimmick. Nice but not important.

Re: [RECOVERY] [new|old bl] TWRP 2.4.0.0 touch recovery [2013-02-01]
Okay, as promised another post about the new twrp version.
The v3.3.0.0 version for the new bootloader has unfortunately been compiled exactly at the time pengus kernel source had the rare ext4 race bug.
So I'd recommend everyone on the new bootloader to update to the new version asap.
If you think you got errors then just do a backup, format /system, /data and /cache, then restore. Most people, including me, shouldn't be affected though.
The new kernel should be absolutely stable, it's based on Kowalski kernel 011p4 (which is like p3 but with the shutdown bug fuxed). This one is completely stable again. (remember, even cwm is using the cm kenel which I'd consider less stable than pengus one).
I had planned to update TWRP during this weekend anyways as twrp 2.4.0.0 got released.
Now cm10.1 users can safely use twrp as well!
Lol, while heading to the twrp website I noticed it got a new update today.
So expect a twrp 2.4.1.0 release tomorrow
What's new in 2.4.0.0:
Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
Support for exFAT formatted sdcards (also thanks to bigbiff)
Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
Added wipe cache and dalvik after ADB Sideload
Replaced many system calls with their native C counterparts
Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
Fixed AOSP recovery commands to run after decryption on encrypted devices
Improvements for building TWRP in CM10.1
Other minor bugfixes and improvements
Sent from my LG-P990 using xda app-developers app

Re: [RECOVERY] [new|old bl] TWRP 2.4.0.0 touch recovery [2013-02-01]
Did try twrp, made a backup with it and tried to restore from that backup but the backup folder was empty, am i missing something...
Sent from my LG-P990 using xda app-developers app

Re: [RECOVERY] [new|old bl] TWRP 2.4.0.0 touch recovery [2013-02-01]
I.m.Tuga said:
Did try twrp, made a backup with it and tried to restore from that backup but the backup folder was empty, am i missing something...
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
I did plenty of backups with twrp, always worked like a charm.
In twrp you can choose the backups location (internal or external sdcard).
So check if it's on the other partition.
Speaking about TWRP.
Please read my update in the twrp thread.
You can wait till tomorrow with updating twrp though, I will push version 2.4.1.0 tomorrow.
Sent from my LG-P990 using xda app-developers app

Okay, about version 2.4.1.0:
My self-built newbl build had already been at version 2.4.1.0
I was in a little hurry and confused myself with the 2.4.0.0 version for the oldbl lol :cyclops:
Now the official build reached 2.4.1.0 as well: http://teamw.in/project/twrp2/65
I downloaded it and zipped it into a flashable zip again, download at the OP.
To avoid confusion I uploaded "recovery-TWRP-2.4.1.0-newbl-20130201.zip" file as well - but it's exactly the same recovery as the previous one.
If you downloaded the "recovery-TWRP-2.4-newbl-20130201.zip" file you already got the newest version and don't have to reflash it it.
2.4.0.0 and 2.4.1.0 changelog:
What's new in 2.4.1.0:
Fixed a problem with mkdosfs that formatted sdcards to 2GB
Fixed handoff between vfat and exFAT on devices where blkid didn't detect vfat (fixes some issues with mounting sdcards)
Fixed problems with changing working directory on MD5 creation/checking that may have prevented unmounting
Backups will now store a copy of the backup log after the backup is completed (only if backup is successful)
What's new in 2.4.0.0:
Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
Support for exFAT formatted sdcards (also thanks to bigbiff)
Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
Added wipe cache and dalvik after ADB Sideload
Replaced many system calls with their native C counterparts
Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
Fixed AOSP recovery commands to run after decryption on encrypted devices
Improvements for building TWRP in CM10.1
Click to expand...
Click to collapse
2.4.0.0 is a big update. If you want to read more details about the meaning of the above lines in the changelog I'd suggest to read the following post which explains them in more details:
http://rootzwiki.com/news/_/article...dated-to-240-big-changes-under-the-hood-r1360

[RECOVERY] TWRP 2.6.0.0 [2013-07-08]

Team 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.5.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.5.0.0 as your custom theme will likely not be compatible with the new changes!
-Added scrollable partition lists for mount, backup, restore, wipe, and storage selection
-Add new SliderValue GUI element for selecting brightness and screen timeout (thanks to Tassadar)
-Re-work AOSP and TWRP code to improve license compatibility between GPL and Apache
-Added official theme for 1080x1920 portrait devices (HTC One m7, HTC DNA, HTC Butterfly, Oppo Find 5, Sony Xperia Z, etc)
-Fixed a problem with directory permissions on split archive backups (backups usually restored with no app data)
-Fixed a problem with md5 verification of backups
-Added a search function to libtar (thanks to kokotas)
-Improve handling of XML errors (fix permissions)
-Fixed handling of subpartitions
-Improvements to recovery.fstab flags
-Fixed a problem with decryption not being able to locate the decryption key in some situations
CHANGELOG for 2.4.4.0:
-Added another libtar hardlink workaround to fix restore of some backups (usually related to Ubuntu Touch)
-More fixes for the file selector
-Switched from using busybox md5sum to a direct C function call
-Fixed capturing the exit status of tar based backups/restore - TWRP will display that there was an error if there was one again
-Update exFAT to latest commits
-Added a build flag to disable using the ioctl for screen blanking
CHANGELOG for 2.4.3.0:
-Fixed 2 bugs related to restore, one dealing with mknod failures (by bigbiff) and one dealing with restoring hardlinks (by Dees_Troy)
NOTE: If your backups weren't restoring correctly in earlier 2.4.x versions they should restore correctly now. Hopefully you didn't delete those backups. If you're still having problems, run the restore, go to advanced and copy log, then give us the log. Complaints without logs will be rightfully ignored.
-Added a scroll bar to file selectors and listboxes courtesy of Tassadar
-Added libblkid for more accurate detection of file systems and can now detect exFAT properly thanks to bigbiff
-Added a screen dim effect 2 seconds before screen off on some devices
-Finally fixed file selector crash (one of the joys of working with multi-threaded software)
-Fixed loading of screen timeout setting during startup
-Improvements and bugfixes to screen timeout code
-Fixed persistence of the 24 hour / military time setting
CHANGELOG for 2.4.2.0:
-Add screen timeout - screen will turn off automatically after 60 seconds, saves battery and prevents screen burn-in especially on AMOLED devices
-Add a brightness setting (requires device specific setup and only some devices have been added)
-Add a root checker and offer to install SuperSU if the device isn't already rooted
-Add a write buffer to libtar backups, significant improvements to speeds when backing up to exFAT target, minor improvements for other file systems
-Check and offer to fix root permissions if broken
-Add an option for a 24 hour clock display instead of AM/PM (aka military time)
-Move stock recovery reflash check to occur during the reboot cycle
-Add support for some MTK6xxx devices
-Change libtar to vfork to help prevent memory problems
-Add a "clicked" effect to most buttons, file selector, and listbox
-Improve timezone listbox to be more like file selector (per pixel kinetic scrolling, etc)
-Remove some no longer used settings (Forced MD5 sum on zips, size checking on image backups)
-Other minor bugfixes and improvements
CHANGELOG for 2.4.1.0:
-Fixed a problem with mkdosfs that formatted sdcards to 2GB
-Fixed handoff between vfat and exFAT on devices where blkid didn't detect vfat (fixes some issues with mounting sdcards)
-Fixed problems with changing working directory on MD5 creation/checking that may have prevented unmounting
-Backups will now store a copy of the backup log after the backup is completed (only if backup is successful)
CHANGELOG for 2.4.0.0:
-Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
-Support for exFAT formatted sdcards (also thanks to bigbiff)
-Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
-Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
-Added wipe cache and dalvik after ADB Sideload
-Replaced many system calls with their native C counterparts
-Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
-Fixed AOSP recovery commands to run after decryption on encrypted devices
-Improvements for building TWRP in CM10.1
-Other minor bugfixes and improvements
NOTE: 2.4.0.0 is, as always, still compatible with your older backups!
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.0.0 [2013-07-08], a Tool/Utility for the Sony Xperia Tablet Z
Contributors
Dees_Troy, bigbiff
Version Information
Status: Stable
Current Stable Version: 2.6.0.0
Stable Release Date: 2013-07-08
Created 2013-08-20
Last Updated 2013-08-20

Reserved
The images are built using pollux_windy compatible kernels, but if you're using the FOTAKernel setup, it will work with either model. If someone wants to come by #twrp and test builds for regular pollux I'll be happy to try to add support for that model as well.

pls add the information that its for pollux_windy only!

Followed the instruction but " no recoveries were found "
And if you put "for pollux ONLY" on the title that would be great
Sent from my SGP311 using xda app-developers app

I'm at a loss right now. I get up to the point where it's time to connect my tablet to the computer and when I press the volume up button it just flashes this blank screen until I give up. Also my computer doesn't recognize the device being plugged in when I reach this step. Both my mac and Windows computers. I'm at the point where I wanna either return it or pay someone to get twrp on it. I can't stand this Sony skin... I NEED CM 10!

XDA Moderation is contacting OP to clarify the TWRP is for a specific device version.
Thank You.
MD

Moscow Desire said:
XDA Moderation is contacting OP to clarify the TWRP is for a specific device version.
Thank You.
MD
Click to expand...
Click to collapse
AFAIK recovery is bundled within the boot image for Pollux* so we need to know also which kernel is bundled or if they support a multi loader (little kernel or whatever)
Inviato dal mio SGP311 usando Tapatalk 4

I'm just as lost. I'm trying to find a custom recovery for the "POLLUX" and not the "WINDY"

If it's of any use, I'll repeat here what I've already posted in a duplicate TWRP thread in this forum:
If you go to the Team Win website (use the link in the OP), then click on "get TWRP for my device" only the Pollux_windy (wifi only) version is shown.
Again, on the Team Win website, looking at the install instructions for TWRP on the Tablet Z Pollux_Windy, it's not straight forward which makes me think it can't be done using goo. Have a look here : http://www.teamw.in/project/twrp2/185
Very confusing.

is anyone using this recovery? feedback please. thanks
----------------
This was mentioned in the TWRP page
Code:
If you happen to be using lk, then boot your device into lk's fastboot mode and flash using this command:
fastboot flash recovery fotakernel.img
how do I know I'm using "lk"? thanks again

mrjayviper said:
how do I know I'm using "lk"? thanks again
Click to expand...
Click to collapse
If you don't know then you probably aren't using it. LK is a 3rd party bootloader ported to the TabZ

.........

can we fastboot flash this image file ?

golfinggino said:
can we fastboot flash this image file ?
Click to expand...
Click to collapse
No - Sony use a combined kernel/recovery so just flashing the TWRP imgage will not work.
You first have to go through the process of installing the "LK kernel". This effectively splits-out the kernel and recovery.
You can then "fastboot flash boot" the boot.img for whichever custom ROM you have, and then also "fastboot flash recovery" the TWRP recovery image.
See this thread : http://forum.xda-developers.com/showthread.php?t=2333826 , specifically posts #1,2,3,20,39,60,61.
I've done it and I've now got TWRP with my PAC ROM. The process was quite easy - but just watch the timings of when you press the volume buttons. Also, when the tablet goes into LK fastboot mode the LED is red. Bit of a bad choice of colour as it has caused some people to think their tablet has died.

to install TWRP on my stock and unlocked bootloader, I just used the adb commands mentioned in the TWRP site.

mrjayviper said:
to install TWRP on my stock and unlocked bootloader, I just used the adb commands mentioned in the TWRP site.
Click to expand...
Click to collapse
Maybe you have a link to the commands. I cant find it

egosapienz said:
Maybe you have a link to the commands. I cant find it
Click to expand...
Click to collapse
Half way down this page : http://www.teamw.in/project/twrp2/185
Try it out. Maybe I did something wrong but it didn't work for me - maybe it only works on stock ROM.
I had to install LK kernel to get TWRP with PAC ROM - see my post above

GretaLewd said:
Half way down this page : http://www.teamw.in/project/twrp2/185
Try it out. Maybe I did something wrong but it didn't work for me - maybe it only works on stock ROM.
I had to install LK kernel to get TWRP with PAC ROM - see my post above
Click to expand...
Click to collapse
Not shure if I should do it. Its for the WIFI-only Tab. My bootloader is locked too. But anyway thanx for the link

egosapienz said:
Not shure if I should do it. Its for the WIFI-only Tab. My bootloader is locked too. But anyway thanx for the link
Click to expand...
Click to collapse
Download the above file. Copy the file to /sdcard/fotakernel.img and run the following commands using terminal emulator or in adb shell:
su
dd if=/sdcard/fotakernel.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
------
I wouldn't do it if yours is the polux. it clearly says wifi only and there seems to be no TWRP for the LTE version.

mrjayviper said:
Download the above file. Copy the file to /sdcard/fotakernel.img and run the following commands using terminal emulator or in adb shell:
su
dd if=/sdcard/fotakernel.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
------
I wouldn't do it if yours is the polux. it clearly says wifi only and there seems to be no TWRP for the LTE version.
Click to expand...
Click to collapse
You´re right. I´ll wait. Thanx

[RECOVERY] [TWRP 2.8.0.0] [v500] [9-11-2014]

Team 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:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tablet look:
CHANGELOG for 2.8.0.0:
-Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
-Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
-Add support for color in the console and give error, warning, and highlight lines different colors
-Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
-Improve handling of /misc thanks to mdmower
-Improve setting of time on Qualcomm devices thanks to [NUT]
-Allow using images on slidervalue GUI objects thanks to Tassadar
-Allow using variables and addition and subtraction in variables for easier theming
-Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
-Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
-Other minor fixes and improvements
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
CHANGELOG for 2.7.1.0:
-Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
-Various bugfixes to backup and restore
-Improvements to USB storage handling
-Added a class to search for files to make finding the correct brightness file automatic in most cases
-Various other bugfixes and tweaks
CHANGELOG for 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.
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.
DISCLAIMER:
I nor anyone else is responsible for what you do to your device.
but if something goes wrong I will do my best to help
DOWNLOAD:
GooManager won't work for this device so please see Below for download links.
You can find more information and download links on our website!
Updated TWRP 2.6.3.1 for cm/aosp 3 versions
please check the software version in your: settings/ about tablet / software information / software version
and grab the one that matches yours
Click to expand...
Click to collapse
V50010a (<--V50010b use this one)
V50010c
V50010e
Archived builds
Flashable zip (works on any version if you already have a custom recovery installed just flash in recovery)
Flashable zip v2.6.3.2 ( ** updated with 1200x1920 theme works on any version if you already have a custom recovery installed just flash in recovery)
Flashable zip v2.6.3.3 ( ** updated with brightness slider works on any version if you already have a custom recovery installed just flash in recovery) credit goes to aicjofs
Flashable zip 2.7.0.0
Flashable zip 2.7.0.0B (added back option to backup recovery)
Flashable zip 2.7.0.0 with USB OTG
v500-TWRP_2.7.1.0-recovery.zip (just flash in recovery)
Current build
v500-TWRP_2.8.0.0-recovery.zip (just flash in recovery)
These builds are for the 4.4.2 bootloader
If you are on the 4.4.2 OTA this is the build you want:
just flash it in recovery
4.4.2-v500-TWRP_2.7.0.1-recovery.zip
New version 2.7.1.0
4.4.2-v500-TWRP_2.7.1.0-recovery.zip
New Version 2.8.0.0
4.4.2-v500-TWRP_2.8.0.0-recovery.zip (just flash in recovery)
If you don't have twrp on your device already
use the script from this thread scroll down to step 3 http://forum.xda-developers.com/showthread.php?t=2698267
then flash the above build in twrp
Credits:
@aicjofs for mentioning the kernel from the ota and all around help
@id10terror - for all the work he has done on the ota
@autoprime- for his 4.4.2 root
@annoyingduck- for testing
Click to expand...
Click to collapse
Don't forget to checkout the themes in post 2
loki : https://github.com/djrbliss/loki (click download zip on the right side)
These instructions are for 4.2.2 Only!!
Instructions:
Code:
you must be rooted
you must have fastboot and adb installed on your pc
download twrp
download loki
unzip loki
place twrp in bin folder of loki
connect your tablet to pc
open a terminal and cd to that bin folder
then run these commands:
adb push twrp.lok /data/local/tmp
adb push loki_tool /data/local/tmp
adb shell
su
chmod 755 /data/local/tmp/loki_tool
/data/local/tmp/loki_tool flash recovery /data/local/tmp/twrp.lok
exit
exit
adb reboot recovery
That is it you will now be in recovery
cheers
CREDITS:
@djrbliss for his bootloader patch LOKI this wouldn't be possible without it
@Dees_Troy and team win for this wonderful recovery
@mustbepbs for getting started with building recovery
@nycbjr and cmb roms
if I forgot someone please let me know

also found some nice themes you guys might like
http://forum.xda-developers.com/showthread.php?t=2675649 credit goes to @z31s1g
just grab the ones from the 1200 themes dropbox folder that is labled 2700
they have a configurable navbar and status bar and such
als here is a nice theme by @aicjofs http://forum.xda-developers.com/showpost.php?p=49969043&postcount=203

Drgravy said:
for science
Click to expand...
Click to collapse
Thanks Man. Did you use the Kingo root method ? What are your opinions on it in terms of safety ? How did you go about it ?

naruto.ninjakid said:
Thanks Man. Did you use the Kingo root method ? What are your opinions on it in terms of safety ? How did you go about it ?
Click to expand...
Click to collapse
yes I used kingo
personally I think its safe but I tend not to worry about that stuff
I just connected my tab and followed the directions

Warranty lose when installing?

Alexey71 said:
Warranty lose when installing?
Click to expand...
Click to collapse
It's great to see this kind of action around here.
Thanks a lot

Drgravy said:
I just connected my tab and followed the directions
Click to expand...
Click to collapse
@Drgravy
hi, just to be safe, this procedure for ADB and FastBoot is correct, right?
http://techbeasts.com/2013/08/26/how-to-install-adb-fastboot-drivers-on-your-windows-pc-guide/
because with windows 8.1 I have not done modding on my N7000 and I do not remember a beep
anyway thanks for the work done

Palux said:
@Drgravy
hi, just to be safe, this procedure for ADB and FastBoot is correct, right?
http://techbeasts.com/2013/08/26/how-to-install-adb-fastboot-drivers-on-your-windows-pc-guide/
because with windows 8.1 I have not done modding on my N7000 and I do not remember a beep
anyway thanks for the work done
Click to expand...
Click to collapse
Yes is perfect!

any help? i cant install it
loki aboot version does not match device

Alexey71 said:
Warranty lose when installing?
Click to expand...
Click to collapse
truthfully i am not sure
Palux said:
@Drgravy
hi, just to be safe, this procedure for ADB and FastBoot is correct, right?
http://techbeasts.com/2013/08/26/how-to-install-adb-fastboot-drivers-on-your-windows-pc-guide/
because with windows 8.1 I have not done modding on my N7000 and I do not remember a beep
anyway thanks for the work done
Click to expand...
Click to collapse
I am not up on windows
I have one old windows machine that I keep around just in case it is running vista
sugaritos said:
any help? i cant install it
loki aboot version does not match device
Click to expand...
Click to collapse
well I'll need some values from your: build.prop
so use your favorite root browser and navigate to system/build.prop and tell me these values:
Code:
ro.product.model=
ro.product.brand=
ro.product.name=
ro.product.device=
ro.product.board=
ro.build.version.incremental=
ro.build.version.sdk=
ro.build.version.codename=
ro.build.version.release=
ro.build.description=
ro.build.fingerprint=

Drgravy here is the info from my build.pop. i managed to pull the aboot.img from my device but i cannot use loki patch..
Code:
ro.product.model=LG-V500
ro.product.brand=lge
ro.product.name=awifi_open_kr
ro.product.device=awifi
ro.product.board=MSM8960
ro.build.version.incremental=V50010c.1379452672
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.description=awifi_open_kr-user 4.2.2 JDQ39B V50010c.1379452672 release-keys
ro.build.fingerprint=lge/awifi_open_kr/awifi:4.2.2/JDQ39B/V50010c.1379452672:user/release-keys

sugaritos said:
Drgravy here is the info from my build.pop. i managed to pull the aboot.img from my device but i cannot use loki patch..
Code:
ro.product.model=LG-V500
ro.product.brand=lge
ro.product.name=awifi_open_kr
ro.product.device=awifi
ro.product.board=MSM8960
ro.build.version.incremental=V50010c.1379452672
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.description=awifi_open_kr-user 4.2.2 JDQ39B V50010c.1379452672 release-keys
ro.build.fingerprint=lge/awifi_open_kr/awifi:4.2.2/JDQ39B/V50010c.1379452672:user/release-keys
Click to expand...
Click to collapse
ok i see the difference
to make this work you will need to open a new issue here : https://github.com/djrbliss/loki/issues?page=1&state=open
and provide this info and also provide your aboot.img
he should be able to update loki for your device

yesterday a new firmware update has come. when i update i must open again a new issue? (this update will come to all devices lg said. it may fixes the blue line issue)

sugaritos said:
yesterday a new firmware update has come. when i update i must open again a new issue? (this update will come to all devices lg said. it may fixes the blue line issue)
Click to expand...
Click to collapse
possibly
any time we take a update from lg we risk loki not working anymore

sugaritos said:
yesterday a new firmware update has come. when i update i must open again a new issue? (this update will come to all devices lg said. it may fixes the blue line issue)
Click to expand...
Click to collapse
Can you post what the new firmware identifier is? Does anybody know what changed?

But on my Tablet installed TWRP?
ro.product.model=LG-V500
ro.product.brand=lge
ro.product.name=awifi_open_cis
ro.product.device=awifi
ro.product.board=MSM8960
ro.build.version.incremental=V50010a.1380630039
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.description=awifi_open_cis-user 4.2.2 JDQ39B V50010a.1380630039 release-keys
ro.build.fingerprint=lge/awifi_open_cis/awifi:4.2.2/JDQ39B/V50010a.1380630039:user/release-keys
Click to expand...
Click to collapse

Alexey71 said:
But on my Tablet installed TWRP?
Click to expand...
Click to collapse
as long as it is V50010a.xxxxxxxxx
you should be fine

I've been working with Dees_troy to make this official

can i flash twp.img with any toolkit?

When trying the first method always get this message:
/data/local/tmp/loki_flash recovery /data/local/tmp/openrecovery-twrp-2.6.3.0-awifi.img
sh: recovery: not found..
so googled a little and found this APP, at XDA forum... worked like a charm http://forum.xda-developers.com/showthread.php?t=2349847.

[RECOVERY][HOLIDAY] TWRP 2.8.0.0 Touch Recovery [2014-09-19]

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:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tablet look:
CHANGELOG for 2.8.0.0:
-Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
-Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
-Add support for color in the console and give error, warning, and highlight lines different colors
-Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
-Improve handling of /misc thanks to mdmower
-Improve setting of time on Qualcomm devices thanks to [NUT]
-Allow using images on slidervalue GUI objects thanks to Tassadar
-Allow using variables and addition and subtraction in variables for easier theming
-Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
-Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
-Other minor fixes and improvements
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
CHANGELOG for 2.7.1.0:
-Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
-Various bugfixes to backup and restore
-Improvements to USB storage handling
-Added a class to search for files to make finding the correct brightness file automatic in most cases
-Various other bugfixes and tweaks
CHANGELOG for 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
DOWNLOAD:
You can download the image here
XDA:DevDB Information
Team Win Recovery Project, a Recovery for the HTC Vivid
Contributors
WildfireDEV, josegalre
Version Information
Status: Testing
Created 2014-09-27
Last Updated 2014-09-27

Why is status testing? It is stable, right?

Does it work with the Rogers one too or just the At&t Vivid only? I'm confused.

Zeekayy said:
Does it work with the Rogers one too or just the At&t Vivid only? I'm confused.
Click to expand...
Click to collapse
The name of thread says HOLIDAY...it supports every variant!

projektileSAM said:
The name of thread says HOLIDAY...it supports every variant!
Click to expand...
Click to collapse
Thankyou.

3 cheers for WildfireDEV
NEW STUFF
NEW STUFF
NEW STUFF
Thank you

rignfool said:
3 cheers for WildfireDEV
NEW STUFF
NEW STUFF
NEW STUFF
Thank you
Click to expand...
Click to collapse
Thanks guys couldn't have done it without Jose so make sure to give him some thanks as well. The recovery should be working fine. The only problem I see right now is the inability to charge inside of recovery and the battery percentage being continually stuck on 66% or something like that. Could someone please report back and tell me if the recovery is working as I might have uploaded a non working version.

WildfireDEV said:
Thanks guys couldn't have done it without Jose so make sure to give him some thanks as well. The recovery should be working fine. The only problem I see right now is the inability to charge inside of recovery and the battery percentage being continually stuck on 66% or something like that. Could someone please report back and tell me if the recovery is working as I might have uploaded a non working version.
Click to expand...
Click to collapse
I am downloading it now and will install it and get back to you in a couple minutes.
I have installed it successfully and it works so far, just installed the latest nightly with it. And yes the battery percentage is stuck at 66% and does not change but other than that so far i don't see any issues.

slick97477 said:
I am downloading it now and will install it and get back to you in a couple minutes.
I have installed it successfully and it works so far, just installed the latest nightly with it. And yes the battery percentage is stuck at 66% and does not change but other than that so far i don't see any issues.
Click to expand...
Click to collapse
Thanks for that. For all the PAC users I will be making a few edits to the PAC branch of the device tree to correspond with the new recovery. The next nightly that is released I would like you guys to check if it flashes without a hitch.

WildfireDEV said:
Thanks for that. For all the PAC users I will be making a few edits to the PAC branch of the device tree to correspond with the new recovery. The next nightly that is released I would like you guys to check if it flashes without a hitch.
Click to expand...
Click to collapse
We talking the flash zip button in PAC console?
Or the update recovery option in developer options?

rignfool said:
We talking the flash zip button in PAC console?
Or the update recovery option in developer options?
Click to expand...
Click to collapse
No I meant the way you guys normally flash like download from web and flash. Also try the flash zip button see if it works but I really meant the other one. Good suggestion @rignfool

WildfireDEV said:
No I meant the way you guys normally flash like download from web and flash. Also try the flash zip button see if it works but I really meant the other one. Good suggestion @rignfool
Click to expand...
Click to collapse
Another question...
Does this support the 'flash after update' directory?

Thank you WildFire and Jose for keeping the Vivid alive!
I just read about the charging bug, is this going to be updated with a fix or is this the last version for now?

calikevin said:
Thank you WildFire and Jose for keeping the Vivid alive!
I just read about the charging bug, is this going to be updated with a fix or is this the last version for now?
Click to expand...
Click to collapse
Should release a new version with it working when I have time

WildfireDEV said:
Should release a new version with it working when I have time
Click to expand...
Click to collapse
just flashed the latest nightly, flashed good but google now launcher is dead, tried to change in settings and it force closes.

Ok...
I tried to flash the 9/30 nightly... But its borked... However...
When I tried to flash the 9/30 gapps from tkruzze... It failed... Bad updater it said...
Switched to 2.6.3.0... Flashed no problem... Checked md5sum... It passed...
Also... Could not successfully move a file from external_SD to sdcard with the file manager... And it was not a zip... It was no extension...

I had problems flashing gapps with this v2.8 as well, reverted back to 2.6 and the same file worked without a hitch

Please take down the non working recovery...

rignfool said:
Please take down the non working recovery...
Click to expand...
Click to collapse
I will upload a new version for you to check if it works soon