LATEST TWRP
TWRP 2.8.5.1 for T-Mobile LG G3
{
"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"
}
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.
Click to expand...
Click to collapse
Phone look:
Tablet look:
Click to expand...
Click to collapse
CHANGELOG for 2.8.5.0:
-Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
-Improve thread handling and move input handling into the main rendering thread to improve stability
-Make MTP work even if unplugged and plugged back in
-Unify scrollable list code and make kinetic scrolling feel more natural
-Fix handling of mapped zip files for OTA updates (CM12 updater)
-USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
-Other small fixes and improvements
Click to expand...
Click to collapse
Features
* F2FS Filesystem Support
* Double Tap to Wake
* Modem Backup Support
Requirements
- Root
Installation Instructions:
A. With custom recovery already installed:
1. Download
2. Install TWRP in recovery
3. Reboot recovery
B. With stock recovery (Need ADB):
1. Download & extract zip
2. Move recovery.img to internal storage.
3. Open terminal window/command prompt to execute following commands
Code:
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
exit
exit
adb reboot recovery
You should be in your updated recovery now
Download:
AndroidFileHost | BasketBuild
Warning
I am not responsible for anything that happens to your device!
Credits
@Dees_Troy & TeamWin - for TWRP touch recovery
@thecubed & Team CodeFire - for PurpleDrake!
Sources
OmniROM Github
Device Github
g3-common Github
XDA:DevDB Information
[RECOVERY] TWRP touch recovery 2.8.6.1, Tool/Utility for the T-Mobile LG G3
Contributors
777jon, Dees_Troy
Version Information
Status: Stable
Created 2015-02-13
Last Updated 2015-03-26
FAQ:
Can I install via Flashify?
Yes, extract the recovery.img from the zip file and use Flashify to flash it.
How do I enter recovery mode?
http://youtu.be/ifi-ArGeTzQ
Change Log
Code:
03/01/15 (TWRP 2.8.5.1)
- F2FS Filesystem Support
- Double Tap to Wake
02/12/15 (TWRP 2.8.5.0)
- TWRP 2.8.5.0 release
01/13/15 (TWRP 2.8.4.0)
- TWRP 2.8.4.0 release
12/22/14 (TWRP 2.8.3.0)
- TWRP 2.8.3.0 release
12/09/14 (TWRP 2.8.2.0)
- Support Modem Backup
- Display "External SD" instead of "external_sd"
12/08/14 (TWRP 2.8.2.0)
- Initial release
- TWRP 2.8.2.0
Thank you!
Thought this caused issues with flashing lp ROMs?
Sent from my LG-D851 using Xparent BlueTapatalk 2
I had a problem flashing LP with Cloudy's version of TWRP. I had no problem flashing LiquidSmooth with this version.
New TWRP build!
Changes:
- Support Modem Backup
- Display "External SD" instead of "external_sd"
I have a 64GB samsung pro micro sd card, and its formatted ExtFat, I tried mounting it and TWRP reads it just fine (read and write). This is with TWRP v. 2.8.0.1
Should I format the card to fat32 or will it work fine for storing and restoring backups also on ExtFat, scince it is reading it now fine
After flashing this new recovery, the data wouldn't come back up on illusion and when trying to flash newest version of liquid smooth, it would never find tmobile signal. When trying to restore a stockbased rom, it froze restoring data and had to do a battery pull to restore the cloudy rom I'm on now. Wish i wouldnt have flashed now. I had just got illusion set back up the way i like it. Lesson learned.
Sent from my LG-D851 using Xparent BlueTapatalk 2
tymansdaddy said:
After flashing this new recovery, the data wouldn't come back up on illusion and when trying to flash newest version of liquid smooth, it would never find tmobile signal. When trying to restore a stockbased rom, it froze restoring data and had to do a battery pull to restore the cloudy rom I'm on now. Wish i wouldnt have flashed now. I had just got illusion set back up the way i like it. Lesson learned.
Sent from my LG-D851 using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
The signal issue with Liquid is resolved by editing the IPv4 APN or switch to IPv6.
IPv4 - Change fast.t-mobile.com to fast.tmobile.com
I found that if you don't wipe/format the data partition before switching roms, things can get quite problematic.
Cablespider said:
The signal issue with Liquid is resolved by editing the IPv4 APN or switch to IPv6.
IPv4 - Change fast.t-mobile.com to fast.tmobile.com
I found that if you don't wipe/format the data partition before switching roms, things can get quite problematic.
Click to expand...
Click to collapse
One question of topic...u find ipv6 faster than ipv4?
Galaxysm said:
One question of topic...u find ipv6 faster than ipv4?
Click to expand...
Click to collapse
No. IPv4 is much faster in my neck of the woods. I'm not sure why.
I always wipe 3 times and clean flash everything. I also know to change to ipv6. I've been flashing roms for quite a while now since the evo 4g.
Cablespider said:
The signal issue with Liquid is resolved by editing the IPv4 APN or switch to IPv6.
IPv4 - Change fast.t-mobile.com to fast.tmobile.com
I found that if you don't wipe/format the data partition before switching roms, things can get quite problematic.
Click to expand...
Click to collapse
Sent from my LG-D851 using Xparent BlueTapatalk 2
Why isn't 2.8.2.0 on the official twrp website?
Hi guys, any help rooting 10R Tmobile please?
thanks
jongcruz said:
Hi guys, any help rooting 10R Tmobile please?
thanks
Click to expand...
Click to collapse
Try towelroot.com
jongcruz said:
Hi guys, any help rooting 10R Tmobile please?
thanks
Click to expand...
Click to collapse
Use lg flash tool 2014 and download a kdz file of 10c and restore back to it then use purple drake to root.
Where is 2.8.3.0?
stevew84 said:
Where is 2.8.3.0?
Click to expand...
Click to collapse
TWRP 2.8.3.0 is up!
CHANGELOG for 2.8.3.0:
-MTP will now tell the host PC that storage is removed instead of disabling MTP completely
-MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
-Update and improve fix permissions and make fixing contexts optional
-Update SuperSU in TWRP to 2.40 and update install process
-Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
-Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
-Fix kernel panic during MTP start on some devices
-Support unicode fonts on devices with True Type Font support
-Fix slider value not showing sometimes (vibration settings page)
-Toggle MTP off during adb sideload to set correct USB IDs
-Reduce library requirements for 5.0 L decrypt
-Other minor fixes and improvements
Note: Starting with TWRP 2.8.2.0 and higher, adb sideload uses a new sideload method originally implemented in AOSP recovery. You will need the latest adb binaries to use sideload in these newer versions of TWRP. The version required is 1.0.32. You can find the version by running "adb version" on your computer. The new sideload feature no longer stores the zip on your device. Instead, a fuse file system is created in RAM and the zip is streamed from your computer. This puts less wear and tear on storage and ensures that large zips will not fill up all of your RAM. The sideload may spit an error on your PC side, but the zip should install just fine on your device.
Click to expand...
Click to collapse
On twrp 2.8.3.0, MTP does not work for me in recovery. You connect the phone to pc. toggle on mtp and the computer sees it and open the window to edit the files on phone.it allows me to edit external sd but not the internal storage.
777jon said:
New TWRP build!
Changes:
- Support Modem Backup
- Display "External SD" instead of "external_sd"
Click to expand...
Click to collapse
Y'know, I have 2.8.3.0 installed yet neither of those two are the case. Can't find anything to do with modem backups and everything still shows external_sd.
Strange.
Edit: After removing the TWRP theme and installing the MultiROM TWRP (2.8.3) I see the modem backup and the SD label change. Too bad I didn't check the regular TWRP w/out theme but I guess the new stuff was hidden by the skin.
Related
Introduction:
---------------------
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"
}
Notice:
---------------------
The attached recovery images were compiled from TWRP's open source.
They were only tested on a European version of the HTC-HD2 powered by cLK bootloader.
The performance on devices powered by MAGLDR bootloader should be considered untested.
Disclaimer:
---------------------
As usual, use at your own risk. TeamWin, arif-ali or kokotas is not responsible for anything bad that may occur from using twrp2.
Nobody appointed me to compile TWRP for HD2. I'm not TeamWin's member. It just happened...
If anyone else is willing to do it and probably do it better I will be glad to step aside,
Key Features:
---------------------
* Ability to save custom recovery settings
* Touchscreen driven with real buttons and drag-to-scroll
* XML-based GUI that allows full customization of the layout – true theming!
* Settings are saved to the sdcard and persist through reboots
* Ability to choose which partitions to back up and which to restore
* Ability to choose to compress backups – now with pigz (multi-core processor support for faster compression times)
* Basic file manager (copy, move, delete, and chmod any file)
* OpenRecoveryScript scripting engine
* On-screen keyboard in recovery! -- supports long press, backspace repeat, and swipe left deletes everything left of the cursor
* ADB sideload functionality from AOSP
* Pseudo-terminal emulator
* Ability to backup large partitions (size>4GB) by splitting the backup archive.
Mainline TWRP Change-Log:
---------------------
Follow up the changes in mainline project at TeamWin's page : http://www.teamw.in/project/twrp2.
HD2's TWRP Change-Log:
---------------------
Initial TWRP versions
List of changes
TWRP v2.4.0.0.r1 @ 2013.01.17
Compiled version based on mainline code (v2.4.0.0Alpha).
Fix boot partition's filesystem for MAGLDR's backup&restore to work.
Fix getting fs-type from a partition created with a label.
Fix the name of the backup sub-folder(htcleo instead of 0s).
TWRP v2.4.4.0 @ 2013.04.03
Compiled version based on mainline code (v2.4.4.0).
Fix boot partition's filesystem for MAGLDR's backup&restore to work.
Fix the name of the backup sub-folder(htcleo instead of 0s).
TWRP v2.5.0.0 @ 2013.04.10
Compiled version based on mainline code (v2.5.0.0).
NOTE: Compiled unmodified source code refused to boot! So I had to change a little bit more this time, just to get it to boot up.
Fix boot partition's filesystem for MAGLDR's backup&restore to work.
Fix the name of the backup sub-folder(htcleo instead of 0s).
TWRP v2.6.0.0 @ 2013.07.09
Compiled version based on mainline code (v2.6.0.0).
Fix boot partition's filesystem for MAGLDR's backup&restore to work.
Fix the name of the backup sub-folder(htcleo instead of 0s).
TWRP v2.6.1.0 @ 2013.08.31
Compiled version based on mainline code (v2.6.1.0).
Fix boot partition's filesystem for MAGLDR's backup&restore to work.
Fix the name of the backup sub-folder(htcleo instead of 0s).
TWRP v2.6.3.0 @ 2013.09.14
Compiled version based on mainline code (v2.6.3.0).
Fix boot partition's filesystem for MAGLDR's backup&restore to work.
Fix the name of the backup sub-folder(htcleo instead of 0s).
TWRP v2.8.6.0 @ 2015.04.30
Compiled version based on mainline code (v2.8.6.0).
Fix boot partition's filesystem for MAGLDR's backup&restore to work.
Fix the name of the backup sub-folder(htcleo instead of 0s).
Fix some ui bugs in the default theme.
TWRP v2.8.6.1 @ 2015.05.02
It is version 2.8.6 with a quick fix over a bug in the default theme engine that was causing an error during each boot.
Installation:
---------------------
Make sure you have adb and fastboot working. Please don't ask here questions about this - a simple web search will be enough to help you.
Make sure that the size of the 'recovery' partition is enough for the image to fit.
Make sure the name of the recovery *.img file is the one you use in the commands or in flash.cfg
[cLK/MAGLDR]
Flashing the zip file from Recovery
Download zip file to your computer and copy to /sdcard.
Reboot phone into recovery.
Select to install the zip file from your /sdcard.
Reboot Phone into recovery as normal.
[cLK/MAGLDR]
Flashing the *.img file while booted in Android
Download the recovery file to your computer.
If it is a zip file, extract the *.img.
(Win) Open the folder you have the recovery, do a [Shift+RightClick] and select "Open command window here".
(Lnx) Open the folder you have the recovery, RigthClick and select "Open in Terminal".
Execute the commands:
Code:
adb push recovery-leo.img /sdcard/recovery-leo.img
adb shell erase_image recovery
adb shell flash_image recovery /sdcard/recovery-leo.img
Reboot Phone into recovery as normal.
[cLK]
Flashing the *.img file while in fastboot mode(cLK menu)
Download the recovery file to your computer.
If it is a zip file, extract the *.img.
(Win) Open the folder you have the recovery, do a [Shift+RightClick] and select "Open command window here".
(Lnx) Open the folder you have the recovery, RigthClick and select "Open in Terminal".
Reboot phone into cLK menu (fastboot mode).
Execute the commands:
Code:
fastboot erase recovery
fastboot flash recovery recovery-leo.img
fastboot oem boot-recovery
[MAGLDR]
Flashing the *.img file while in USB Flasher mode(using DAF.exe)
WARNING!!! This will erase your current Rom on NAND too!
Download the recovery file to your computer.
If it is a zip file, extract the *.img.
Open the folder you have the recovery and place DAF.exe and flash.cfg in that same folder.
Edit flash.cfg according to required recovery partition size:
Make sure the .img file has the name that flash.cfg specifies!!
i.e. If the *.img file is named recovery-leo.img and min-required-size = 6MB then the flash.cfg could be:
Code:
misc ya 1M
[U]recovery rrecov|ro|nospr 6M recovery-leo.img[/U]
boot yboot|ro 5M
system ya 150M
cache ya 2M
userdata ya|asize|hr allsize
Check out the info about flash.cfg.
Connect the device to the computer via usb, enter MAGLDR and select USB Flasher option.
Right click on DAF.exe and select Run as Administrator.
Click [NEXT] when asked and wait to finish.
Download:
---------------------
HD2_TWRP_2.8.6.1.zip
md5: 93972887cfd3e017d16a09a74900496d
Info: You need to have a recovery partition at least 9 MB to fit the img
HD2_SD_TWRP_2.8.6.1.zip
Info: Extract to the root of your SD Card
Old Releases:
---------------------
HD2_TWRP_2.8.6.0.zip
md5: 882aaa25d9ff17613c64efe53c127d3a
HD2_SD_TWRP_2.8.6.0.zip
HD2_TWRP_2.6.3.0.zip
md5: 53c9522dbaa5ab465874258c01758143
HD2_SD_TWRP_2.6.3.0.zip
HD2_TWRP_2.6.1.0.zip
md5: d66519b22d219865d741389013ea034f
HD2_SD_TWRP_2.6.1.0.zip
HD2_TWRP_2.6.0.0.zip
md5: 185e6b34699e4cdb176780695e9e06aa
HD2_SD_TWRP_2.6.0.0.zip
HD2_TWRP_2.5.0.0.zip
md5: 9604cb28b3e91047abdc3a63d5b827df
HD2_SD_TWRP_2.5.0.0.zip
HD2_TWRP_2.4.4.0.zip
md5: b24bdf020b8ea3222c92df0644c88203
HD2_SD_TWRP_2.4.4.0.zip
HD2_TWRP_2.4.0.0_r1.zip
md5: 8bd2b557442c5af73d38f9e7a054b67a
HD2_SD_TWRP_2.4.0.0.r1.zip
HD2_TWRP_2.3.2.3.img
md5: ad8d1909d54c440f9b79eacad31910b9
recovery-twrp-leo-2.0.0RC0.1.img
md5: 6279a726b19a4ff2fccfe592e23b2e48
recovery-twrp-leo-2.0.0RC0.img
md5: e12fc48a863e4a2984d7fcf3b2cad50a
recovery-twrp-leo-1.1.1-3.img
md5: 6198e06b7ca85379e16acde4d9a19752
recovery-twrp-leo-1.1.1-2.img
md5: 52c51eee07c50a928341b22c3e2a60b6
recovery-twrp-leo-1.1.1-1.img
md5: 4801f88e0d2a62b5a1c3d168a4116d0d
recovery-twrp-leo-1.1.1.img
md5: 7fa63b205facf64bd69d805acf34ae8c
recovery-twrp-leo-1.1.0-2.img
md5: 8bd05c6b1e25bd8cf410e308bed23fe5
recovery-twrp-leo-1.1.0.img
md5: 449b06b28f73e996a33e06c047b51b98
Special Thanks to:
---------------------
* Core twrp 2 development team: agrabren, Dees_Troy, ViViDboarder, and AssassinsLament
* Toastcfh – for his underappreciated dedication to the community
* s0up and kevank for their hard work on the web side of things.
* The rest of Team Win: shift, onicrom, netarchy, kevank, myndwire, bigbiff, dkelle4, shinzul, spiicytuna, and eyeballer
* Amon_RA - for his great Recovery
* Koush - for his dedication to the community and ClockworkMod
* For all the help with devices and testing Akmzero, arif-ali, Evil_DevNull, gus6464, Jesusice, Pyrostic, [R], and Rootzwiki
* As always thank you to the Team's supporters and the Android Community.
[22 Dec 2011][RECOVERY] Team Win Recovery Project (twrp) v2.0.0RC0.1
Original OP
FAQ
FAQ from TWRP team is here
Q: Does Rom Manager work with this
A: No
Q: Will you be providing support for Rom Manager
A: Maybe, when I have time, or if Team View release it before me
Q: Does it work with MAGLDR
A: Yes, use AD recovery
Q: Does this mean we cannot easily install ROMs
A: Yes, but the code for that may be added at later date, this is Work In Porgress
Q: Will reboot to Recovery work as normal
A: Yes
Q: Does Off-mode charging still work
A: Yes, same as CWM on cLK. it will charge when off, but pressing the power button while charging will not turn the phone on
Q: I got "failed with error: -1"
A: make sure the recovery size is 5M, anything below that is not supported, You can check this by running adb cat "/proc/mtd | grep recovery"
Changelog
ChangeLog
---------------------
2011-12-22 - v2.0.0RC0.1
Fix issues with wiping data on MTD devices (thanks Dees_Troy)
2011-12-18 - v2.0.0RC0
Initial release of twrp 2
Full GUI touchscreen with buttons and XML engine
Fixed sdcard free space checking
Fixed bugs with MD5 zip file checking
Now check more places for a serial number
Too many fixes versus twrp 1.1.1 to list
2011-10-11 - v1.1.1-3
Fix sd-ext issues (no longer use auto FS, and use ext3)
2011-10-08 - v1.1.1-2
Fix sd-ext restore issue
Fix issue with SD repartition and the send button again
2011-10-08 - v1.1.1
fixed fix permissions bug
fixed md5 checking for zip install
2011-10-07 - v1.1.0-2
Changed the select key from power to call button
2011-10-07 - v1.1.0-1
Changed buttons so that it works with the HD2
HD2 Initial Release
2011-10-05 - v1.1.0
brand new nandroid process with more error checking and supports ext3/ext4 types of devices
sdcard partitioning is available for devices with a sdcard (courtesy of koush from CWM source)
can choose multiple zips before flashing and they will flash in the order chosen
files & folders are sorted case insensitive
added option to sort zips by file date instead of file name
can apply themes and change time zones without rebooting for instant gratification
saved settings will now persist through version changes
added myn's warm theme with color codes courtesy of myn
added option to wipe system, data, and cache with rm -rf during a nandroid restore to maintain existing file system settings like block size
added options for automatic md5 checking of zips
twrp spam off by default which makes nandroids up to 10x faster
2011-08-05 - v1.0.3
Added timezones that should cover everyone
Added twrp spam feature (twrp settings)
Added fix permissions (advanced menu)
Added wipe cache and dalvik into Flash Zip menu
Added copy recovery.log to /sdcard (advanced menu)
Added output spam/no spam to restores
Added mke2s prebuilt to /sbin
Fixed SD-EXT issues, (no partition SD-EXT features yet)
Fixed EFS partition issues
Changed the way we do backups on mtd devices, which should fix any boot partition issues (we suggest making new backups if you have an mtd device, EVO4G,NS,NS4G,etc)
2011-07-31 - v1.0.2
Fixed SD-EXT issues
Added Format SD-EXT into format menu
Removed GAPPS support, CM7 automatically backsup and restores if you already have GAPPS installed. If you don't, just flash GAPPS zip
Fixed issue where when flashing a rom, rebooting brings you back to recovery. Auto reboot after successful flash should work great now!
Rearranged the format menu
2011-07-30 - v1.0.1
Initial release
Since I had Already started with the ports for the Recovery Themes...
This is the Link to New Thread.
Sory for Any Inconvenience this has caused you Arif...
Please Visit New Thread Here...
If you See any New themes that you would like me to Port please feel free to post on the Thread Linked Above...
tobiascrystal said:
No kidding, you are super fast! In your experience would you say that this has anything over cwm that you have learned getting it to work for us?
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
It is customizable and has touchscreen capabilities.
wow very nice new features compared to clockworkmod...
Just installed few minutes ago, as far as I can tell, it seems all is working fine!
I might have a "small" request, is it possible to map the buttons just like in cwm? I didn't like the idea of using the end button that much...
---------- Post added at 01:51 AM ---------- Previous post was at 01:49 AM ----------
Ultimaex said:
It is customizable and has touchscreen capabilities.
Click to expand...
Click to collapse
Not just yet! This is 1.xx version based, the one you're refering with ts capabilities is 2.x based...
Kool... Now users will have a choice for more than one recovery on leo too... Al thanks to you cheers
And button customization would be good... I hate using the end key.. I fearing... My touch screen might get spoilt again ...
Sent from my HTC HD2 using XDA App
Seems to work great. I did a backup and restore and all went well thumbs up
Sent from my HTC Runnymede using XDA App
So right off the bat I'm impressed with the compression....does it allow us to produce our own zips? I'd like to rename my backups based on the rom they backed up instead of just a date/timestamp.
Nice........
Definitely a thing to look in future
Hope all the bugs are resolved soon
EDIT: - Thanked & RATED 5 STAR (All I can do as of now )
i don't understand how can i install this, becouse this is not zip file. Can you help me please
you install through adb. if you dont know what that is, do a search. there are many FAQ's about it. I would recommend doing plenty of research on it before diving right in.
if someone can do some pictures for me that would be great, as I don't have a camera, or a second phone which has a good quality camera
thanks
How's about battery charging, like clk?
huhjun said:
How's about battery charging, like clk?
Click to expand...
Click to collapse
It's the same as CWM
Edit: Added to FAQ
arif-ali said:
if someone can do some pictures for me that would be great, as I don't have a camera, or a second phone which has a good quality camera
thanks
Click to expand...
Click to collapse
Here you go with some phot... Not so high quality though... If you need better.. Tell me I will upload photos taken from my handy cam ... And what vabout changing end call button to call button
http://db.tt/afg0Szat
Sent from my HTC HD2 using XDA App
i got "failed with error: -1"
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.8.3.0:
-MTP will now tell the host PC that storage is removed instead of disabling MTP completely
-MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
-Update and improve fix permissions and make fixing contexts optional
-Update SuperSU in TWRP to 2.40 and update install process
-Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
-Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
-Fix kernel panic during MTP start on some devices
-Support unicode fonts on devices with True Type Font support
-Fix slider value not showing sometimes (vibration settings page)
-Toggle MTP off during adb sideload to set correct USB IDs
-Reduce library requirements for 5.0 L decrypt
-Other minor fixes and improvements
Note: Starting with TWRP 2.8.2.0 and higher, adb sideload uses a new sideload method originally implemented in AOSP recovery. You will need the latest adb binaries to use sideload in these newer versions of TWRP. The version required is 1.0.32. You can find the version by running "adb version" on your computer. The new sideload feature no longer stores the zip on your device. Instead, a fuse file system is created in RAM and the zip is streamed from your computer. This puts less wear and tear on storage and ensures that large zips will not fill up all of your RAM. The sideload may spit an error on your PC side, but the zip should install just fine on your device.
CHANGELOG for 2.8.2.0:
-Pull in all changes from Android 5.0 lollipop into TWRP
-Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
-Revert some changes to exFAT that were breaking exFAT support on some devices
-Other minor fixes and updates
Note: At this time we do not have a GUI representation for pattern unlock. You can still decrypt patterns though by translating the pattern dots to numbers. The pattern dots correspond to numbers in the following pattern:
1 2 3
4 5 6
7 8 9
So an upper-case L would translate to a password of 14789 entered on the keyboard. Eventually we plan to add a proper pattern unlock to TWRP but it is a relatively low priority at this point.
CHANGELOG for 2.8.1.0:
-MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
-TrueType Font support - optional as it takes up a decent amount of space so may not be available on all devices - thanks to Tassadar
-Temperature support - thanks to bigbiff
-Various other bugfixes and tweaks
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
DOWNLOAD:
Most devices can be updated quickly and easily with the TWRP Manager app:
Play Store Link
1) Install TWRP Manager from the Play Store
2) Open TWRP Manager and provide root permissions
3) Hit Advanced->Install Recovery
4) Verify the correct device name on your screen then press Install Recovery if the correct device is showing
OR:
You can find more information and download links on our 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.
Reserved
Device Page on our website:
http://www.teamw.in/project/twrp2/203
Downloads:
http://techerrata.com/browse/twrp2/R819
In my OPPO R819 Goomanager says "No recoveries were found for your device"
This is great news. Finally a custom recovery for R819!
Download img file here
http://techerrata.com/browse/twrp2/R819
Flash with MobileUncle MTK tools found from Play Store
https://play.google.com/store/apps/details?id=com.mobileuncle.toolbox
Do this with your OWN responsibility! I am not responsible if you screw around and brick your phone!
1. Put downloaded IMG file in root of SDcard
2. Open Mobileuncle Tools
3. Choose 'Recovery Update'
4. On the top of the list should show the IMG file on you SD card that you downloaded.
5. Tap it and confirm with OK to flash.
Can I flash Stock Recovery Back
I have installed TWRP 2.6.3.0, and I have used it to make Backups of the whole ROM.
However, I tried to install the ColorOS Beta 1.0.0 and found out it would not install, reason unknown.
So I used TWRP to clean the partitions /Data, /System, /Cache etc. and then installed successfully the complete ROM for Oppo R819 - R819AS-11.A.07-OTA-INT-007-all-SVN4875-wipe.zip since this is the only available until now. Perfect installation.
The system says that there is a downloadable OTA Update Stock Oppo OS 4.2.1 (Build R819AS_11_A.09_131010). I downloaded it, clicked the greenish-blue button "Install", but the phone is not able to install it, obviously, because the Stock Recovery is different, and the instructions are for it alone. Is there a way to return back to Stock Recovery, despite it looks so bare and ugly, just to update the system?! Or is there another way to do it? Maybe if I knew where is stored the downloaded OTA update, I could flash it via TWRP...
Hmm, strange, I installed Color OS with TWRP. To change to stock recovery all you need is to flash a stock rom, it overwrites the recovery during the install process.
TWRP 2.6.3.0
Sorry, there is no logic in that. I did install Stock ROM, the complete ROM for Oppo R819 - R819AS-11.A.07-OTA-INT-007-all-SVN4875-wipe.zip since this is the only available until now. Perfect installation. Via TWRP, of course. Nothing can change the recovery, it stays the same, it is on its own partition, most notably, so that nothing could mess with it. Simple principle - if you are in Recovery, you cannot destroy Recovery itself.
Thanks to a person, who has a phone Oppo Find 5, but told me the problem is with the root privileges, I managed to get past the problem. I preserved the same TWRP 2.6.3.0 Recovery, since I have no other, and I can't change it. I opened the SuperSU program, and checked inside it to "Disable", temporarily. I did not use the "Permanent Uninstall Root" option, which also exists in it. I rebooted to Recovery, and in TWRP wiped the Cache & Dalvik partitions. After that I chose "Install" and the ColorOS 1.0.0 ROM installed perfectly well. It is beautifull and shiny! :good:
{
"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"
}
Where can I find the stock recovery to flash it back in case I want to revert? Or can anyone give me instructions on how to backup the stock recovery before flashing TWRP?
mundano said:
Where can I find the stock recovery to flash it back in case I want to revert? Or can anyone give me instructions on how to backup the stock recovery before flashing TWRP?
Click to expand...
Click to collapse
Yeah I'd like to know too. Or perhaps anyone has stock recovery.img for R819 ?
Sent from my R819 using Tapatalk
distan7 said:
Yeah I'd like to know too. Or perhaps anyone has stock recovery.img for R819 ?
Sent from my R819 using Tapatalk
Click to expand...
Click to collapse
I have the Stock Recovery from 131010, the file is recovery.img 5,865,472 bytes but it can only be flashed with SP Flash Tool, which is not a thing to recommend to beginners, the Tool needs to have the "MT6589_Android_scatter_emmc.txt". That is why I am afraid to post it plainly, open to anyone, just because they might start experimenting without knowledge and break their Oppo R819. Trust me, if you have installed TWRP Recovery from above, using the MobileUncle Tool, you are safe and well, it is a much better Recovery than the plain Stock one.
I understand your point, but I'm not comfortable in flashing non reversible stuff in my phone...
So I will stick with the stock recovery until there is a safe way to revert back to stock.
Victor perhaps you might share how you extract your recovery.img ? Using dd ?
Sent from my R819 using Tapatalk
Distan7 managed to find a way to revert from TWRP back to Stock Recovery :good:
He has explained it here, has done it twice just to be sure it works every time:
http://www.oppoforums.com/posts/125077/
This is his detailed explanation. Nothing irreversible!
[Oppo R819] Flashing Stock Recovery After Using TWRP
More information on a couple of ways how to recover Oppo R819 are written here:
http://www.oppoforums.com/posts/133578
TWRP was updated today to version 2.7.0.0. I flashed it without problems on my R819.
Sent from my Nexus 7 using Tapatalk
TWRP 2.7.1.0 Updated
TWRP 2.7.1.0 is uploaded to the same place http://techerrata.com/browse/twrp2/R819
vickfred said:
TWRP 2.7.1.0 is uploaded to the same
Looks like development is dead
---------- Post added at 10:45 PM ---------- Previous post was at 10:40 PM ----------
distan7 said:
Victor perhaps you might share how you extract your recovery.img ? Using dd ?
Sent from my R819 using Tapatalk
Click to expand...
Click to collapse
There are many tools available u can get any
---------- Post added at 10:47 PM ---------- Previous post was at 10:45 PM ----------
distan7 said:
Victor perhaps you might share how you extract your recovery.img ? Using dd ?
Sent from my R819 using Tapatalk
Click to expand...
Click to collapse
There are many tools available u can get any
---------- Post added at 11:15 PM ---------- Previous post was at 10:47 PM ----------
ccav2000 said:
TWRP was updated today to version 2.7.0.0. I flashed it without problems on my R819.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thats nice
Click to expand...
Click to collapse
HEY GUYS IT'S M AGAIN THIS TIME I AM HERE WITH SOMETHING SPECIAL FOR YOU ALL !
AFTER HOURS OF CONTINUOUS WORK AND BRICKING MY PHONE WITH SOME HACKING , I'VE FU*K'N TWRP TO WORK FOR OUR PHONE LOL !!
Click to expand...
Click to collapse
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.8.0.1:
-Fix a bug that causes weird graphics glitches and touch issues
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.
DOWNLOAD:
https://drive.google.com/file/d/0ByEZDplbxwxJT01GUXBsTkxnVW8/edit?usp=sharing
How to flash
Download tar file from download link
Download odin (3.07 recommended ) just search for it on xda
Open odin
do whats here
{
"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"
}
[/IMG]
connect device to download mode and hit start
Good work man! :thumbsup:
allram said:
Good work man! :thumbsup:
Click to expand...
Click to collapse
Wouldn't have been possible without you and spegelius
Thanks a lot!
: of course also to the other major developers ☺
I would like to test it. Is it possible to make a zip which can be flashed via CWM?
Best wishes, Christian
baaldfg said:
Thanks a lot!
: of course also to the other major developers ☺
I would like to test it. Is it possible to make a zip which can be flashed via CWM?
Best wishes, Christian
Click to expand...
Click to collapse
Yes i could make a zip but i am not free currently
Otherwise working fine, but doesn't seem to recognise my external memory card. Is there option to enable it or any idea what is causing it?
ElakNovAlamak said:
Otherwise working fine, but doesn't seem to recognise my external memory card. Is there option to enable it or any idea what is causing it?
Click to expand...
Click to collapse
Is it in Exfat format?
allram said:
Is it in Exfat format?
Click to expand...
Click to collapse
Fat32. This is first time having this kind of trouble. So far every rom and recovery has detected it ok.
ElakNovAlamak said:
Otherwise working fine, but doesn't seem to recognise my external memory card. Is there option to enable it or any idea what is causing it?
Click to expand...
Click to collapse
allram said:
Is it in Exfat format?
Click to expand...
Click to collapse
I have searched and tested and have two theories
1- The stock fstab that i used with is in jf-common/rootdir/qcom.fstab has messed up because of the heavy edits i had to make there .
2- It needs some patch that i am not finding .
extra ,
maybe needs a kernel commit or something
i would flash twrp again and test the external sd i have
edit : it doesn't show and the fstab seams fine to me ( i did double check)
Good start. All the red touch screen errors scare me on a recovery that is so critical to what I do. It needs to read / write external SD card. Hope it gets finished and not dropped halfway there.
Pkt_Lnt said:
Good start. All the red touch screen errors scare me on a recovery that is so critical to what I do. It needs to read / write external SD card. Hope it gets finished and not dropped halfway there.
Click to expand...
Click to collapse
I am trying my best with twrp , getting it to run on our phone is a success on its own , but i also encourge people to try the philz touch as i really like the extra features it offers .
mythi said:
I am trying my best with twrp , getting it to run on our phone is a success on its own , but i also encourge people to try the philz touch as i really like the extra features it offers .
Click to expand...
Click to collapse
You realize, via the link to Philz in your first post, that it is an abandoned product, right? Of the three recoveries, TWRP offers the only hope for improvements and bug fixes. CWM is antiquated and brain dead. Philz abandoned, that leaves TWRP half way, (sigh)
Pkt_Lnt said:
You realize, via the link to Philz in your first post, that it is an abandoned product, right? Of the three recoveries, TWRP offers the only hope for improvements and bug fixes. CWM is antiquated and brain dead. Philz abandoned, that leaves TWRP half way, (sigh)
Click to expand...
Click to collapse
TWRP will newer support exFAT, so Phill - the best.
d8389 said:
TWRP will newer support exFAT, so Phill - the best.
Click to expand...
Click to collapse
Did you meant TWRP will never support exFAT?
Pkt_Lnt said:
Did you meant TWRP will never support exFAT?
Click to expand...
Click to collapse
TWRP might support f2fs but i don't know about exfat , any way about the progress of mounting the sdcard i got the option to display on mount settings but nothing happenes upon click that so gonna dig more :crying:
Does "no exFAT support" also means no FAT32 support? Because with this TWRP my ext-sdcard is not selectable, only internal storage
defim said:
Does "no exFAT support" also means no FAT32 support? Because with this TWRP my ext-sdcard is not selectable, only internal storage
Click to expand...
Click to collapse
no actually the recovery has broken sdcard support
Dear Mithy,
could you please release an updated TWRP for our i9295? Latest version is now 2.8.3.0
Thank you very much, and happy new year!
so you are saying that the sgh-i537 has been boot unlocked?
Major-Hardon said:
so you are saying that the sgh-i537 has been boot unlocked?
Click to expand...
Click to collapse
Lol thanks for getting my hopes up but I'm 99% sure this recovery is for the international model (sgh-i9295). I'm not a gambling man but it sounds like the bootloader getting unlocked for our i537 is just never gonna happen. And if it did you'd hear about it, it'd be all over this phone's forum
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.8.3.0:
-MTP will now tell the host PC that storage is removed instead of disabling MTP completely
-MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
-Update and improve fix permissions and make fixing contexts optional
-Update SuperSU in TWRP to 2.40 and update install process
-Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
-Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
-Fix kernel panic during MTP start on some devices
-Support unicode fonts on devices with True Type Font support
-Fix slider value not showing sometimes (vibration settings page)
-Toggle MTP off during adb sideload to set correct USB IDs
-Reduce library requirements for 5.0 L decrypt
-Other minor fixes and improvements
Note: Starting with TWRP 2.8.2.0 and higher, adb sideload uses a new sideload method originally implemented in AOSP recovery. You will need the latest adb binaries to use sideload in these newer versions of TWRP. The version required is 1.0.32. You can find the version by running "adb version" on your computer. The new sideload feature no longer stores the zip on your device. Instead, a fuse file system is created in RAM and the zip is streamed from your computer. This puts less wear and tear on storage and ensures that large zips will not fill up all of your RAM. The sideload may spit an error on your PC side, but the zip should install just fine on your device.
CHANGELOG for 2.8.2.0:
-Pull in all changes from Android 5.0 lollipop into TWRP
-Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
-Revert some changes to exFAT that were breaking exFAT support on some devices
-Other minor fixes and updates
Note: At this time we do not have a GUI representation for pattern unlock. You can still decrypt patterns though by translating the pattern dots to numbers. The pattern dots correspond to numbers in the following pattern:
1 2 3
4 5 6
7 8 9
So an upper-case L would translate to a password of 14789 entered on the keyboard. Eventually we plan to add a proper pattern unlock to TWRP but it is a relatively low priority at this point.
CHANGELOG for 2.8.1.0:
-MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
-TrueType Font support - optional as it takes up a decent amount of space so may not be available on all devices - thanks to Tassadar
-Temperature support - thanks to bigbiff
-Various other bugfixes and tweaks
CHANGELOG for 2.8.0.1:
-Fix a bug that causes weird graphics glitches and touch issues
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
DOWNLOAD:
Look in post #2
Most devices can be updated quickly and easily with the TWRP Manager app:
Play Store Link
1) Install TWRP Manager from the Play Store
2) Open TWRP Manager and provide root permissions
3) Hit Advanced->Install Recovery
4) Verify the correct device name on your screen then press Install Recovery if the correct device is showing
OR:
You can find more information and download links on our 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:
This is an unofficial port, if you have issues dont bother them, you bug me.
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Moto 360 Part
Thread closed so dees_troy can have his official one, go grab that version!!!!!
Download this: 2.8.3.0 with v7 of the 320x290 theme
Put your device into Fastboot mode
Connect to your dongle (here is a guide on that all)
Use the following command "fastboot flash recovery path/to/the/image/you/downloaded.img" without the quotes.
You can either fastboot reboot and then reboot into recovery or fastboot boot the recovery image and have it boot into it.
Flash http://shabbypenguin.com/?developer=Tools&folder=Superuser to gain root
There is no key combo that I've found that would allow directly booting into recovery, so fastboot is still your friend if your rom isnt booting :/.
The gui is offcentered because it is teh smallest one they have and it doesnt match up, the next biggest looked fine except the buttons at teh bottom used to navigate were off screen. I'm pretty terrible with graphics and it would end up worse if i tried, so reach out to twrp themers and the twrp devs to get us a round theme or at the very least a theme that would fit. If you would like to donate in my signature you'll find a magical link that directly supports me being lazy and not finding a real job.
Credits:
My wife for buying me a 360
Hroark for saving the day and helping with TWRP
RootJunky for helping me out with a cable so i could even root and testing
mkaymuzik for working on the 320x290 TWRP theme we will be using
TWRP Team for an amazing recovery.
Ok so in hindsight, this post wasnt needed, so now im going to put my device tree down here because... well i need to have something here right?
Device tree source
there, now its used... happy now?
Nice Work cant wait to get this installed and the Theme updated
great! Now we need a custom rom
BerndHhn said:
great! Now we need a custom rom
Click to expand...
Click to collapse
Agreed!!!! Has anyone tried flashing this yet?
Gotroot said:
Agreed!!!! Has anyone tried flashing this yet?
Click to expand...
Click to collapse
I did ;P
You do it over? Or use app
Gotroot said:
You do it over? Or use app
Click to expand...
Click to collapse
Im not aware of any app that will flash it on a watch.
Would you mind sharing the fastboot or dd cmd ?
---------- Post added at 10:56 PM ---------- Previous post was at 10:51 PM ----------
Or can you use the script posted here and direct it to the img..
shabbypenguin said:
Moto 360 Part
Download this: https://mega.co.nz/#!UQ4RwahC!AnFEeNBrGob9NuAyne62OXXW0MiaWeV7kpwrbjSIzjM
Put your device into Fastboot mode
Connect to your dongle (here is a guide on that all)
Use the following command "fastboot flash recovery path/to/the/image/you/downloaded.img" without the quotes.
You can either fastboot reboot and then reboot into recovery or fastboot boot the recovery image and have it boot into it.
There is no key combo that I've found that would allow directly booting into recovery, so fastboot is still your friend if your rom isnt booting :/.
The gui is offcentered because it is teh smallest one they have and it doesnt match up, the next biggest looked fine except the buttons at teh bottom used to navigate were off screen. I'm pretty terrible with graphics and it would end up worse if i tried, so reach out to twrp themers and the twrp devs to get us a round theme or at the very least a theme that would fit. If you would like to donate in my signature you'll find a magical link that directly supports me being lazy and not finding a real job.
Credits:
My wife for buying me a 360
Hroark for saving the day and helping with TWRP
RootJunky for helping me out with a cable so i could even root
TWRP Team for an amazing recovery.
Click to expand...
Click to collapse
Gotroot said:
Would you mind sharing the fastboot or dd cmd ?
---------- Post added at 10:56 PM ---------- Previous post was at 10:51 PM ----------
Or can you use the script posted here and direct it to the img..
Click to expand...
Click to collapse
I use fastboot from my apk tool folder so, so move your recovery.img into your fastboot path ..... My command looked like this " fastboot flash recovery recovery.img" and there you go.
@shabbypenguin could you post screenshots of how it look at the moment? Will start working on a design concept (as discussed).
I also need a ramdisk-recovery.img version of the moto360's twrp and witch theme resolution did you use ?
im using 240x240 as it proved to be far more effective than 320x320, http://imgur.com/WV4G7kb
So I got the Lollipop update but I had flashed this recovery and when I go to install the update it boots me into TWRP How should I go about this ? Flash with TWRP? or reflash stock recovery?
NUGZZ420 said:
So I got the Lollipop update but I had flashed this recovery and when I go to install the update it boots me into TWRP How should I go about this ? Flash with TWRP? or reflash stock recovery?
Click to expand...
Click to collapse
Usually you need to be on stock recovery to flash update so I would think wear would be the same. Unless someone makes a flashable zip, in which case twrp would be able to flash it
fakieskr8333 said:
Usually you need to be on stock recovery to flash update so I would think wear would be the same. Unless someone makes a flashable zip, in which case twrp would be able to flash it
Click to expand...
Click to collapse
I figured it out kinda feel dumb for asking now I haven't done a OTA and a grip its always flashing it.
NUGZZ420 said:
I figured it out kinda feel dumb for asking now I haven't done a OTA and a grip its always flashing it.
Click to expand...
Click to collapse
Haha no big deal. I had a total brain fart the other day and had to lookup how to adb reboot. Turns out I forgot I was on a Mac and needed to add ./ to the front. Its funny BC I always use a Mac lol.
Will TWRP reinstall root like it will on phones?
I lost root when upgrading to Lollipop and cannot get it back by using the fastboot boot boot.img command.
abuttino said:
Will TWRP reinstall root like it will on phones?
I lost root when upgrading to Lollipop and cannot get it back by using the fastboot boot boot.img command.
Click to expand...
Click to collapse
yup, best bet is to flash supersu though.
as a progress update:
{
"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"
}
UPDATE: I am no longer posting on XDA.
Code:
*** Disclaimer ***
All flashing is done at your own risk!
While nothing from this thread should break your device,
don't come back here blaming anyone if it does!
Introduction
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.
Click to expand...
Click to collapse
Images
Installation instructions
TWRP Image Install method:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed.
Download the latest version of TWRP appropriate for your device/firmware
Reboot to TWRP
Hit Install and tap the "Install Image" button in the lower right
Browse to the location of the TWRP image on your device and select it
Select recovery from the partition list and swipe to flash
Alternate Installation Method:
Fastboot Install Method:
You will need the platform-tools from the Android SDK on your computer. Find the Android command line tools section on the page linked and install the SDK tools package. From the SDK Manager, download only the platform-tools to get adb and fastboot binaries.
Windows users will need proper drivers installed on their computer. You can try the Naked ADB drivers or the Universal ADB drivers if you don't already have a working driver installed
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
Code:
adb reboot bootloader
You should now be in fastboot mode.
Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
Code:
fastboot flash recovery twrp.img
Code:
fastboot reboot
Click to expand...
Click to collapse
Device Changelog
Current version: 3.1.1-0:
Code:
[LIST]Initial official release[/LIST]
Older Device-specific versions:
Code:
[LIST]N/A[/LIST]
Click to expand...
Click to collapse
TWRP Official Changelog
Current version: 3.1.1:
Code:
[LIST]Backups will now include adopted storage keys (Dees_Troy)
[*]Fixed an adb restore issue (bigbiff)
[*]Fixed rebooting when no OS is present (Dees_Troy)
[*]Fixed line wrapping in the GUI terminal (_that)
[*]Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)[/LIST]
Older versions:
Code:
[SIZE="4"][COLOR="Green"]3.1.0:[/COLOR][/SIZE]
[LIST]vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
[*]adb backup to stream a backup directly to or from your PC, see documentation [URL="https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9"]here[/URL] (bigbiff)
[*]tweak MTP startup routines (mdmower)
[*]support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
[*]support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
[*]better indicate to users that internal storage is not backed up (Dees_Troy)
[*]improve automatic determination of TW_THEME (mdmower)
[*]minimal getcap and setcap support (_that)
[*]try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
[*]shut off backlight with power key (mdmower)
[*]timeout during FDE decrypt (Dees_Troy and nkk71)
[*]support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
[*]boot slot support (Dees_Troy)
[*]TWRP app install prompt during reboot (Dees_Troy)
[*]support for AB OTA zips (Dees_Troy)
[*]support new Android 7.x log command (Dees_Troy)
[*]update recovery sources to AOSP 7.1 (Dees_Troy)
[*]numerous bugfixes and improvements by too many people to mention[/LIST]
[SIZE="4"][COLOR="Green"]3.0.3:[/COLOR][/SIZE]
[LIST]Partial release to help support the release of the [URL="https://www.xda-developers.com/team-win-releases-their-first-official-twrp-app-in-the-play-store/"]Official TWRP app[/URL][/LIST]
[SIZE="4"][COLOR="Green"]3.0.2:[/COLOR][/SIZE]
[LIST]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.[/LIST]
[SIZE="4"][COLOR="Green"]3.0.1:[/COLOR][/SIZE]
[LIST]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[/LIST]
[SIZE="4"][COLOR="Green"]3.0.0:[/COLOR][/SIZE]
[LIST]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[/LIST]
[U]Additional Notes[/U]
[LIST]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 updated 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![/LIST]
[SIZE="4"][COLOR="Green"]2.8.7.0:[/COLOR][/SIZE]
[LIST]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)[/LIST]
[U]Additional Notes[/U]
[LIST]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 [url]https://jenkins.twrp.me[/url] and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at [url]https://gerrit.twrp.me[/url] to help us keep devices up to date and working.[/LIST]
Click to expand...
Click to collapse
Downloads
Download
Latest Official versions
Sources
Device tree
Kernel source
Click to expand...
Click to collapse
Known Issues
None
Click to expand...
Click to collapse
Bug Reporting
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed. NOTE: Posts that are reporting bugs or issues without an accompanying recovery log will be ignored! Additionally, providing details about your device setup, including variant, firmware version, and exact steps to reproduce your issue will also be helpful in diagnosing the problem.
{
"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"
}
If your issue is determined to be 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 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!
Click to expand...
Click to collapse
Additional Help/Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Click to expand...
Click to collapse
XDA:DevDB Information
Team Win Recovery Project (TWRP), Tool/Utility for the HTC EVO 4G
Contributors
Captain_Throwback, Dees_Troy, bigbiff, _that
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Stable
Current Stable Version: 3.1.1-0
Stable Release Date: 2017-05-18
Created 2015-03-20
Last Updated 2018-03-07
Device-specific Information
Reserved for FAQ (if needed)
Ty captain,
I like the new additions can't wait to check it out.
+1
Sent from my SM-G900P
2.8.6.0 has been uploaded.
2.8.7.0 has been uploaded.
Anybody tried the new TWRP yet?
Captain_Throwback said:
Anybody tried the new TWRP yet?
Click to expand...
Click to collapse
Working on maKing a Wi-Fi only phone for my cousins birthday out of my old evo I tried to find "supersonic" in the twrp app but it didn't come up. Would you be able to fix that or should I just install it manually?
paridoth said:
Working on maKing a Wi-Fi only phone for my cousins birthday out of my old evo I tried to find "supersonic" in the twrp app but it didn't come up. Would you be able to fix that or should I just install it manually?
Click to expand...
Click to collapse
What TWRP app? There's no official TWRP app. The install method is listed on the Download page for the device and in the OP here.
On the download page it links to the twrp manager app. I am installing over clockwork mod so can't install with recovery and I don't have access to a computer.
paridoth said:
On the download page it links to the twrp manager app. I am installing over clockwork mod so can't install with recovery and I don't have access to a computer.
Click to expand...
Click to collapse
Yeah, that's not an official TWRP app. You can disregard that. You can try Flash Image GUI or Flashify to flash recovery to your device, if you have to use an app, but I never recommend using an app if fastboot is available .
Yea I tried flashify but it locked up. Could I put it in a pc36img.zip and flash it from bootloader?
paridoth said:
Yea I tried flashify but it locked up. Could I put it in a pc36img.zip and flash it from bootloader?
Click to expand...
Click to collapse
What about Flash Image GUI? There's a free version available on XDA (last time I checked).
The bootloader method should also work, it just requires having an appropriate android-info.txt.
I'll try flash image gui and report back thanks!
---------- Post added at 10:28 AM ---------- Previous post was at 10:17 AM ----------
Is this the right one? https://play.google.com/store/apps/details?id=com.joeykrim.flashimagegui
paridoth said:
I'll try flash image gui and report back thanks!
---------- Post added at 10:28 AM ---------- Previous post was at 10:17 AM ----------
Is this the right one? https://play.google.com/store/apps/details?id=com.joeykrim.flashimagegui
Click to expand...
Click to collapse
Did you find more than one?
Just wasn't sure that was the right one. I found it on xda. Flashed twrp 3.0 rebooted to recovery but it took me to the boot loader. Tried again same thing. I'll try flashing an older version
paridoth said:
Just wasn't sure that was the right one. I found it on xda. Flashed twrp 3.0 rebooted to recovery but it took me to the boot loader. Tried again same thing. I'll try flashing an older version
Click to expand...
Click to collapse
You might just have to wait until you get to a PC and do it via fastboot. That way should work without issue.
Unfortunately I'm in hospital so no computer access. I flashed an older version and that worked when I get out I'll try flashing 3.0 with adb thanks!
paridoth said:
Unfortunately I'm in hospital so no computer access. I flashed an older version and that worked when I get out I'll try flashing 3.0 with adb thanks!
Click to expand...
Click to collapse
If you got a previous version installed, you should be able to flash the new version from within TWRP (as indicated in the OP).
Unfortunately it was 2.7 I installed I tried 2.8 but had the same issue
paridoth said:
Unfortunately it was 2.7 I installed I tried 2.8 but had the same issue
Click to expand...
Click to collapse
Is your EVO on the last available software update? I believe it was 5.07.651.6 or something like that?