Database Develop

[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.7.0.1] [altev | VK810] [4-21-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.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
This is for the Verizon Gpad Only
DOWNLOAD:
Please note this is for 4.2.2 only!
Also if you want to take an OTA from Verizon you will need to put the stock recovery back and probably unroot
VK810_twrp_2.7.0.1.zip just unzip it and follow the directions in the README
update **
VK810_twrp_2.7.0.2.zip just flash it in recovery (must have 2.7.0.1 installed first)
Instructions:
Code:
open your terminal and cd to where loki_flash and twrp.lok is
now run these commands:
adb push loki_flash /data/local/tmp/loki_flash
adb push twrp.lok /data/local/tmp/twrp.lok
adb shell
su
cd /data/local/tmp
chmod 777 loki_flash
./loki_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
@id10terror for patching the aboot.img for this device. Be sure and thank him
@traccdma for testing
if I forgot someone please let me know

reserved

Has the Verizon tablet had a 4.4.2 ota yet?

Drgravy said:
Has the Verizon tablet had a 4.4.2 ota yet?
Click to expand...
Click to collapse
Not that I've received. I got a small patch but it is still 4.2.2
Worked great! Thanks for all your work.

Thanks! Finally the VK810 gets some dev love.
BTW, I really think you should put a big sign that says NOT FOR V500, VERIZON WIRELESS VERSION ONLY as some people don't bother to check thoroughly and the term VK810 doesn't mean much to them, they might end up bricking their device...
Sent from my iPhone using Tapatalk

Thanks for the mention @Drgravy! I've initiated a pull request for the loki_patch changes to djrbliss' git
https://github.com/djrbliss/loki/pull/60
Sent from my VS980 4G using Tapatalk

The readme has no carriage returns in it and is confusing for someone like me who hasn't used adb at all. Can you list the instructions here?
EDIT: Nevermind. It opens find in WordPad.
EDIT 2: Worked like a charm! I had to re-select the type of USB connection I had, but once I did that, 'adb devices' showed the tablet and I was able to push and install TWRP!

id10terror said:
Thanks for the mention @Drgravy! I've initiated a pull request for the loki_patch changes to djrbliss' git
https://github.com/djrbliss/loki/pull/60
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Awesome your commit was merged

Drgravy said:
Awesome your commit was merged
Click to expand...
Click to collapse
Yep, just saw that! Glad I could contribute something to the Verizon G Pad people!
Sent from my VS980 4G using Tapatalk

I know this isn't said enough, but thank you guy so much for getting this working!

Thanks guys!
Sent from my G2

Great work, thanks guys for the successful effort! Now if we could get some ROM love for this thing

@Drgravy
How do i install this recovery?..
Do i have to connect to a computer or can i just install from tablet?
I have nevet used adb terminal...
Thank u for ur hard work...and any help u can give
I read the readme but have never usef adb..
Any help would be greatly appreciated

cobra7361 said:
@Drgravy
How do i install this recovery?..
Do i have to connect to a computer or can i just install from tablet?
I have nevet used adb terminal...
Thank u for ur hard work...and any help u can give
I read the readme but have never usef adb..
Any help would be greatly appreciated
Click to expand...
Click to collapse
if you dont have adb installed you need to install it
this may or may not help with that:
http://forum.xda-developers.com/sho...cct=/sitesearch.php&__utmv=-&__utmk=235630466
then just run the commands in the README

Thanks, DrGravy! This is awesome.
There were no hard returns in the instrux, so I want to confirm:
adb push loki_flash /data/local/tmp/loki_flash
adb push twrp.lok /data/local/tmp/twrp.lok
adb shellsucd /data/local/tmpchmod 777 loki_flash./loki_flash recovery /data/local/tmp/twrp.lok
The last line seems wonky with that period after "loki_flash." Not sure if there's a line break there somewhere.

ibawanzingee said:
Thanks, DrGravy! This is awesome.
There were no hard returns in the instrux, so I want to confirm:
adb push loki_flash /data/local/tmp/loki_flash
adb push twrp.lok /data/local/tmp/twrp.lok
adb shellsucd /data/local/tmpchmod 777 loki_flash./loki_flash recovery /data/local/tmp/twrp.lok
The last line seems wonky with that period after "loki_flash." Not sure if there's a line break there somewhere.
Click to expand...
Click to collapse
open it with wordpad instead of note pad
I'll put the instructions in the OP just give me a couple of minutes
*Edit, Instructions in OP now

Great, thanks very much! I was a bit nervous when it looked like it corrupted the bootloader, but it's great to finally have a custom recovery!
Drgravy said:
open it with wordpad instead of note pad
I'll put the instructions in the OP just give me a couple of minutes
*Edit, Instructions in OP now
Click to expand...
Click to collapse

Getting error
Hey guys,
Thank you for all your work. I am getting the following error:
[email protected]:/data/local/tmp $ ./loki_flash recovery /data/local/tmp/twrp.lok
data/local/tmp/twrp.lok
[+] loki_flash v2.1
[-] Failed to open aboot for reading.
1|[email protected]:/data/local/tmp $

prana22 said:
Hey guys,
Thank you for all your work. I am getting the following error:
[email protected]:/data/local/tmp $ ./loki_flash recovery /data/local/tmp/twrp.lok
data/local/tmp/twrp.lok
[+] loki_flash v2.1
[-] Failed to open aboot for reading.
1|[email protected]:/data/local/tmp $
Click to expand...
Click to collapse
Did you SU in ADB then grant root on the tablet?

edgemaster191 said:
Did you SU in ADB then grant root on the tablet?
Click to expand...
Click to collapse
Doh! That was it. Thanks!

[RECOVERY][OBSOLETE]TWRP 2.8.1.0 touch recovery[2014-10-22]

This recovery is obsolete now as there is no need anymore for stock Samsung kernel and hacked dependencies. Proper release with CM kernel is here.
TWRP 2.8.1.0
for Samsung Galaxy S4 LTE+ (GT-I9506)
Thanks to TeamWin
TWRP official site: http://teamw.in/project/twrp2
XDA Dev Thread: http://forum.xda-developers.com/showthread.php?t=1943625
IRC: #twrp on Freenode IRC servers (or webchat)
Github: https://github.com/omnirom/android_bootable_recovery
​
Screenshots:
{
"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"
}
How to install:
- Flash tar with ODIN (use AP slot) or zip with custom recovery
- Tested with CM11/solk2 (backup & restore) on GT-I9506
- Needs Bootloader 4.4 (?)
Bugs:
- brightness slider in 'Settings' doesn't work
- Restoring modem might freeze. I guess its locked by bootloader. (issue)
Changelog (2014-10-22):
2.8.1.0
Fix crash when rapid firing command line commands
Add support for temperatures in tenths of a degree Celsius
gui: Disable unnecessary checks if TW_CUSTOM_THEME is defined
Do not set contexts during a factory reset
Fix placement of Android Secure and SD-EXT on wipe page
Fix wiping crash when block device is not present
Update reference to 24-hour clock
display cpu temperature in twrp
Add support for TrueType fonts
Fix exfat-fuse handling
and more...
Official Changelog (2.8.0.0):
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.

TWRP work great and thanks so much

At last, one recovery that seems to work right.
Now a few ROMs and let the show begin LOL

Did anyone test a exFAT micro SD?
Gesendet von meinem GT-I9506 mit Tapatalk

I tried to flash it via CWM or Odin, but unfortunately it doesn't boot.

neumann said:
I tried to flash it via CWM or Odin, but unfortunately it doesn't boot.
Click to expand...
Click to collapse
Which device?
Where does it hang exactly? On 'Recovery booting...' (in blue) screen?
Which rom do you have installed?
Is adb working?

DualJoe said:
Which device?
Where does it hang exactly? On 'Recovery booting...' (in blue) screen?
Which rom do you have installed?
Is adb working?
Click to expand...
Click to collapse
I have an i9506 (ks01lte) with solks CM11 installed, the first official nightly from 2 days ago. It hangs where it says 'Recovery booting.....', where I still can see the S4 logo.
I did not check adb yet, because I thought, that recovery is not loading at all. Is there anything I should try, if adb is running?

neumann said:
I have an i9506 (ks01lte) with solks CM11 installed
Click to expand...
Click to collapse
Do you have 4.4 bootloader installed (from official stock rom 4.4)?

DualJoe said:
Do you have 4.4 bootloader installed (from official stock rom 4.4)?
Click to expand...
Click to collapse
Yes.

neumann said:
Yes.
Click to expand...
Click to collapse
See if logcat is running, create logs and post the files.
Any fancy stuff installed like exfat sdcard or something?
Code:
adb shell "dmesg > /tmp/dmesg.log"
adb pull /tmp/dmesg.log
adb pull /tmp/recovery.log
Edit: Quotes added to adb shell, sry.

DualJoe said:
See if logcat is running, create logs and post the files.
Any fancy stuff installed like exfat sdcard or something?
Code:
adb shell "dmesg > /tmp/dmesg.log"
adb pull /tmp/dmesg.log
adb pull /tmp/recovery.log
Edit: Quotes added to adb shell, sry.
Click to expand...
Click to collapse
sorry, but adb is not running.
I just doule chcked it, I have bootloader I9506XXUBNA2 installed, which is 4.3, but I'm pretty sure I came from Stock KK 4.4. Could this be the problem?

neumann said:
sorry, but adb is not running.
I just doule chcked it, I have bootloader I9506XXUBNA2 installed, which is 4.3, but I'm pretty sure I came from Stock KK 4.4. Could this be the problem?
Click to expand...
Click to collapse
Yes, probably. The 4.4 kernels come with a new device tree format.

DualJoe said:
Yes, probably. The 4.4 kernels come with a new device tree format.
Click to expand...
Click to collapse
Can I then just flash a 4.4 kernel over my 4.3 kernel? If yes, which one would you recommend?

The kernel comes shipped with every recovery. Its the 4.4 bootloader you need. Just flash a full stock rom once. You'll get a new baseband/modem and such as well.

DualJoe said:
The kernel comes shipped with every recovery. Its the 4.4 bootloader you need. Just flash a full stock rom once. You'll get a new baseband/modem and such as well.
Click to expand...
Click to collapse
Do I really need to flash full stock to get the 4.4 bootloader? It's a long procedure to have CM11 back then. Isn't it possible to flash just the bootloader? When I do a full backup I have always a file called boot.img, isn't that the bootloader?

neumann said:
Do I really need to flash full stock to get the 4.4 bootloader? It's a long procedure to have CM11 back then. Isn't it possible to flash just the bootloader? When I do a full backup I have always a file called boot.img, isn't that the bootloader?
Click to expand...
Click to collapse
Boot.img is the kernel, not the bootloader.

neumann said:
Do I really need to flash full stock to get the 4.4 bootloader? It's a long procedure to have CM11 back then. Isn't it possible to flash just the bootloader?
Click to expand...
Click to collapse
The bootloader comes with complementary data like baseband and other partitions. If something's not correct it might brick your phone. I don't recommend that unless you know exactly what you're doing.
You can try to backup your rom (/data) manually during runtime via ADB (split by 2GB):
Code:
tar -czvpf - /data | split -b 2000m - /storage/sdcard1/databackup.tar.gz
/data holds the internal /sdcard as well (/data/media/0). You can check the size by this:
Code:
busybox du -sh /data/media/0
If you think its too large and you want to exclude it from the backup use this:
Code:
tar --exclude='/data/media/0' -czvpf - /data | split -b 2000m - /storage/sdcard1/databackup.tar.gz
And once you have TWRP running you can install CM11, format /data (just factory reset) and restore with this/adb:
Code:
cat /external_sd/databackup.tar.gz* | tar xzpvf - -C /
You might lose internal /sdcard on stock rom install (not sure though..) so i've chosen /storage/sdcard1 (external_sd) as output folder for the backup (better safe than sorry...).

Thanks a lot, I'll try this and let you know.

Added some options to exclude backing up internal sdcard.

Hmm.. wait. I don't think it will work as it will exceed the 4GB max file size barrier of FAT32. Will look up some split options in a second...

[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

[OFFICIAL][TWRP][d5110] TWRP for Infinix Hot 2

Team Win Recovery Project 3.x, or twrp3 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.
{
"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"
}
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOADS
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
TWRP for Infinix Hot 2
Credits
@MSF Jarvis
@Nonta72
@Dees_troy
@jcadduono
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
[OFFICIAL][TWRP][d5110] TeamWin Touch Recovery, Tool/Utility for the Infinix HOT 2
Contributors
HostZero, MSF Jarvis, Dees_troy
Source Code: https://github.com/TeamWin/android_device_infinix_d5110
Version Information
Status: Stable
Created 2016-06-08
Last Updated 2016-06-08

Reserved

How to back to stock recovery ?

0utc0ntr0l said:
How to back to stock recovery ?
Click to expand...
Click to collapse
Download STOCK recovery and flash it using TWRP.

Thank You So Much For Your Effort And I Have A Problem When I Used The Method That You've Written To Install The Recovery When I Entered To My Recovery And Tap INSTALL And Then Selected INSTALL IMAGE And I Selected The Recovery Image It Appears To Me The Only Partition That I Can Flash It To It Is The BOOT Partition

youssef0789 said:
Thank You So Much For Your Effort And I Have A Problem When I Used The Method That You've Written To Install The Recovery When I Entered To My Recovery And Tap INSTALL And Then Selected INSTALL IMAGE And I Selected The Recovery Image It Appears To Me The Only Partition That I Can Flash It To It Is The BOOT Partition
Click to expand...
Click to collapse
Thankyou I will work on patch soon.

youssef0789 said:
Thank You So Much For Your Effort And I Have A Problem When I Used The Method That You've Written To Install The Recovery When I Entered To My Recovery And Tap INSTALL And Then Selected INSTALL IMAGE And I Selected The Recovery Image It Appears To Me The Only Partition That I Can Flash It To It Is The BOOT Partition
Click to expand...
Click to collapse
It seems like you are using twrp by jemmini.
You can flash it with flashify/rashr or any flashing app.
Or via terminal
Code:
dd if=PATH_TO_DOWNLOADED_FILE of=/dev/block/platform/mtk-msdc.0/by-name/recovery
This might different on android one rom.
Since jemmini's TWRP is only can flash boot images

RendyAK said:
It seems like you are using twrp by jemmini.
You can flash it with flashify/rashr or any flashing app.
Or via terminal
Code:
dd if=PATH_TO_DOWNLOADED_FILE of=/dev/block/platform/mtk-msdc.0/by-name/recovery
This might different on android one rom.
Since jemmini's TWRP is only can flash boot images
Click to expand...
Click to collapse
Thank You So Much I'll Give It A Try But I Tried To Flash It With This Method
1 . Download the latest image file (.img) from the download link above and rename it to twrp.img, then copy it into the same folder as the factory ROM.
2 . Open up the MTK Flash Tool and use the scatter loading button to select the scatter file for this device.
3 . Uncheck all partition boxes except for the RECOVERY partition.
4 . Click on the folder/filename path for RECOVERY, then browse to and select the twrp.img file.
5 . Click on the [Download] button in the MTK Flash Tool.
6 . Power off your device completely.
7 . Plug the device into the computer and wait for it to flash. If it fails to flash the first time, you may have to unplug the phone and click [Download] again. Try this a few times. If it still doesn't work, try a different USB port and USB cable.
And When I Flashed It It Was Successfully Installed But There Was A Problem It Doesn't Show My SD Card

youssef0789 said:
It seems like you are using twrp by jemmini.
You can flash it with flashify/rashr or any flashing app.
Or via terminal
Thank You So Much I'll Give It A Try But I Tried To Flash It With This Method
1 . Download the latest image file (.img) from the download link above and rename it to twrp.img, then copy it into the same folder as the factory ROM.
2 . Open up the MTK Flash Tool and use the scatter loading button to select the scatter file for this device.
3 . Uncheck all partition boxes except for the RECOVERY partition.
4 . Click on the folder/filename path for RECOVERY, then browse to and select the twrp.img file.
5 . Click on the [Download] button in the MTK Flash Tool.
6 . Power off your device completely.
7 . Plug the device into the computer and wait for it to flash. If it fails to flash the first time, you may have to unplug the phone and click [Download] again. Try this a few times. If it still doesn't work, try a different USB port and USB cable.
And When I Flashed It It Was Successfully Installed But There Was A Problem It Doesn't Show My SD Card
Click to expand...
Click to collapse
Yeah, that is the bug of this twrp :3 @HostZero

RendyAK said:
Yeah, that is the bug of this twrp :3 @HostZero
Click to expand...
Click to collapse
Sir,
If your not aware I had been doing testing series for TWRP for d5110 successfully i have compiled and people were like no issues, so i went up publishing and Recovery Partition Flashing! I am trying to work on patch. if possible can you provide me the mmc* partition list. (ex: mmcb500...) I need those for boot and recovery, so i will make stable.
- HostZero

HostZero said:
Sir,
If your not aware I had been doing testing series for TWRP for d5110 successfully i have compiled and people were like no issues, so i went up publishing and Recovery Partition Flashing! I am trying to work on patch. if possible can you provide me the mmc* partition list. (ex: mmcb500...) I need those for boot and recovery, so i will make stable.
- HostZero
Click to expand...
Click to collapse
Here it is.
From /proc/emmc on Infinix 5.1 Rom.
The sdcard partition should be the same with android one rom.

RendyAK said:
Here it is.
From /proc/emmc on Infinix 5.1 Rom.
The sdcard partition should be the same with android one rom.
Click to expand...
Click to collapse
Please do this
adb devices
su (root using TWRP or any other way)
ls -al /dev/block/platform/mtk-msdc.0/by-name
Now copy the partition table and try to give me.
This will provide the mmc/infinix partition table.
- HostZero

HostZero said:
Please do this
adb devices
su (root using TWRP or any other way)
ls -al /dev/block/platform/mtk-msdc.0/by-name
Now copy the partition table and try to give me.
This will provide the mmc/infinix partition table.
- HostZero
Click to expand...
Click to collapse
This can be do with Terminal tho :3

RendyAK said:
This can be do with Terminal tho :3
Click to expand...
Click to collapse
Thankyou I will enter new table and most probably 3.0.2-1 or wait for 3.0.3-0.
- HostZero

I would like to report several issues:
1. NVRAM should've mounted as emmc, not ext4 (there's error in the log), also you should make secro as a sub partition of nvram. In my previous encounter with mediatek, if your secro partition corrupted or missing, your IMEI will still not detected (or detected partially).
2. There's no micro SD card mount point, despite the card is detected. Why?
I decompiled the official image, make necessary edit, and recompiled again. Tested fine on my brother's hot 2.
Download here if you want.

awaaas said:
I would like to report several issues:
1. NVRAM should've mounted as emmc, not ext4 (there's error in the log), also you should make secro as a sub partition of nvram. In my previous encounter with mediatek, if your secro partition corrupted or missing, your IMEI will still not detected (or detected partially).
2. There's no micro SD card mount point, despite the card is detected. Why?
I decompiled the official image, make necessary edit, and recompiled again. Tested fine on my brother's hot 2.
Download here if you want.
Click to expand...
Click to collapse
Fixed All of Them:
https://gerrit.twrp.me/1640
- HostZero

HostZero said:
Fixed All of Them:
https://gerrit.twrp.me/1640
- HostZero
Click to expand...
Click to collapse
Why would you create a fix when it's already fixed? I submitted that like half a month ago dude...
https://gerrit.twrp.me/#/c/1598/
https://gerrit.twrp.me/#/c/1597/
You approved my changes then on gerrit. Why did you do this?

awaaas said:
Why would you create a fix when it's already fixed? I submitted that like half a month ago dude...
https://gerrit.twrp.me/#/c/1598/
https://gerrit.twrp.me/#/c/1597/
You approved my changes then on gerrit. Why did you do this?
Click to expand...
Click to collapse
Bro! I don't remember if I approved. Anyways your changes were not pushed to git. My changes are pushed & I have even got
CPU Temperature for this.
Logo Backup and OEM backup and few other changes which would make twrp more stable.

HostZero said:
Bro! I don't remember if I approved. Anyways your changes were not pushed to git. My changes are pushed & I have even got
CPU Temperature for this.
Logo Backup and OEM backup and few other changes which would make twrp more stable.
Click to expand...
Click to collapse
You +1'd my changes on gerrit. And it IS pushed to github, you can check the commits of mine in TWRP device tree, it is pushed on June 19th.
https://github.com/TeamWin/android_device_infinix_d5110/commits/android-5.1
While it is good you added more partition to backup (note: IIRC, oem partition is not used by infinix) and cpu temp, I only complained about my changes duplicated by you, and that you claimed it.
Anyways, please don't make a duplicate fix in the future

CPU TEMPRATURE, Theres a Fix That i discovered.
and OEM partition is there for d5110 as per me.
I have duplicated on NVRAM etc all are new.