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.
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
20160214: Upstream merge till 34741d9cefd5981d23330eb6f6130d7d30ddf206
20160328: Upstream merge till a915ec4215386949ab0a92d2c401c004864cba6a
DOWNLOAD:
at least u already use TWRP 2.8.7.0 by @dh.harald
1) Download Folder
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
Device: https://github.com/fire855/android_device_xiaomi_ferrari
Kernel: https://github.com/fire855/android_kernel_xiaomi_ferrari
Vendor: https://github.com/fire855/android_vendor_xiaomi_ferrari
Credits:
@dh.harald
@omerjerk
@fire855
@k2wl
Altaf-Mahdi
rohanpurohit
Thanks for sharing. Is it working just update recovery while i use custom rom??
Sent from my MI 4i using Tapatalk
dkasmara said:
Thanks for sharing. Is it working just update recovery while i use custom rom??
Sent from my MI 4i using Tapatalk
Click to expand...
Click to collapse
yes, just flash it via some apps like flashify or rashr
dkasmara said:
Thanks for sharing. Is it working just update recovery while i use custom rom??
Sent from my MI 4i using Tapatalk
Click to expand...
Click to collapse
D4rkCyb3r said:
yes, just flash it via some apps like flashify or rashr
Click to expand...
Click to collapse
Already mentioned above
And the step
I've fleshed it over the old version, it's really cool, and the bug with duplicating storage was fixed.
Thanks a lot.
Thanks for the latest version!
why in this version wipe process too long?
just me?
old twrp by magdag
fumakila said:
why in this version wipe process too long?
just me?
old twrp by magdag
Click to expand...
Click to collapse
It's same like dh.harald
Use rm rf instead of format
Rm rf it's linux command to remove entire directory
faizauthar12 said:
It's same like dh.harald
Use rm rf instead of format
Rm rf it's linux command to remove entire directory
Click to expand...
Click to collapse
How to change it?
blackagent said:
How to change it?
Click to expand...
Click to collapse
Please check setting section(TWRP Setting ..... ,u can see the setting button)
Hi, I got this while use format data.
Sorry for my bad English.
rhotha said:
Hi, I got this while use format data.
Sorry for my bad English.
Click to expand...
Click to collapse
Hmm ,i never use format data feature..
I used wipe
I will find out why
And wait for next commit from TWRP repo
Anyway ,can u tell me which firmware and which rom u used ?
How can I do merge the partitions?
In the 1st version of this new TWRP 3, he doubled the partitions.
So I updated to the 2nd version but also have duplicate partitions.
How can I fix this?
It's just a display bug nothing to worry about just use it as normal
nice job brother.. :good:
but it takes a long time when the wipe cache and Dalvik
sorry for bad english
-Rhoby|™-Bugs said:
nice job brother.. :good:
but it takes a long time when the wipe cache and Dalvik
sorry for bad english
Click to expand...
Click to collapse
Firmware?
Rom ?
-Rhoby|™-Bugs said:
nice job brother.. :good:
but it takes a long time when the wipe cache and Dalvik
sorry for bad english
Click to expand...
Click to collapse
Go to TWRP settings -> use rm rf instead of format
Gesendet von meinem Mi 4i mit Tapatalk
faizauthar12 said:
Hmm ,i never use format data feature..
I used wipe
I will find out why
And wait for next commit from TWRP repo
Anyway ,can u tell me which firmware and which rom u used ?
Click to expand...
Click to collapse
I use global v6 6.6.6.0
Edit: the case is same with twrp 2.8.7.0 by dh.harald
Could you please advise why do I can't see USB OTG at this TWRP?
ROMs used are CM13 by fire 865 and RR since 3/23.
RiD91 said:
Could you please advise why do I can't see USB OTG at this TWRP?
ROMs used are CM13 by fire 865 and RR since 3/23.
Click to expand...
Click to collapse
Try change file format type of this usb.
Related
[RECOVERY][skyrocket] TWRP 3.1.1-0 touch recovery [2017-05-19]
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.
CHANGELOG for 3.0.2-0:
-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)
CHANGELOG for 3.1.0-0:
-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 here: https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9 (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
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!
DOWNLOAD:
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
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:
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.
will try, thanks!
I missed twrp from my evo days
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I had a chance to work with Dees_Troy on this. It's easily the best recovery ever made. The touch interface is second to none.
Sent from my Skyrocket
It won't flash on top of CWM 5.0.2.7 because the assert will fail. If the board checked for MSM8660_SURF, I think it would work on both hercules and skyrocket.
Edit: this will flash on top of CWM 5.0.2.7. I'm not sure about 5.8.1.3 touch or 5.5.0.4 touch. Removed for now.
cant find it in goomanager
romracer said:
It won't flash on top of CWM 5.0.2.7 because the assert will fail. If the board checked for MSM8660_SURF, I think it would work on both hercules and skyrocket.
Edit: this will flash on top of CWM 5.0.2.7. I'm not sure about 5.8.1.3 touch or 5.5.0.4 touch.
Click to expand...
Click to collapse
Zip updated to MSM8660_SURF.
tjsooley said:
cant find it in goomanager
Click to expand...
Click to collapse
Same here
just search for twrp and download the skyrocket zip
You've got to be kidding me... we have THREE different recoveries now! O.O
This would have been simply absurd from the old Aria days...
Sent from my SAMSUNG-SGH-I727 using XDA
iandr0idos said:
You've got to be kidding me... we have THREE different recoveries now! O.O
This would have been simply absurd from the old Aria days...
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
Four... 5.5.0.4 touch, 5.8.1.3 touch, 5.0.2.7 original and now this one. I've not used TWRP before but it seems pretty nice from the poking I've done so far.
iandr0idos said:
You've got to be kidding me... we have THREE different recoveries now! O.O
This would have been simply absurd from the old Aria days...
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
Yeah, but the other 3 recoveries lack WIN! >_>
I've never considered the two touch recoveries to be different recoveries... but okay.
I did a successful backup and restore. So at least that is working.
Sent from my SAMSUNG-SGH-I727 using XDA
romracer said:
Four... 5.5.0.4 touch, 5.8.1.3 touch, 5.0.2.7 original and now this one. I've not used TWRP before but it seems pretty nice from the poking I've done so far.
Click to expand...
Click to collapse
Five if you count 5.0.2.6 separate from 5.0.2.7. So, will TWRP eliminate the need to do multiple wipes/clears/partition formats now? (since our current recoveries were T989 based).
DoctorQMM said:
Five if you count 5.0.2.6 separate from 5.0.2.7. So, will TWRP eliminate the need to do multiple wipes/clears/partition formats now? (since our current recoveries were T989 based).
Click to expand...
Click to collapse
That would be great!
Everything works great except i can't browse the sdcard. When i click emmc it goes to the internal and when i click sdcard it goes to internal. Anyone else having this issue?
Use the mount menu to change from internal to external.
Thanks,trying now
Dees_Troy said:
Zip updated to MSM8660_SURF.
Click to expand...
Click to collapse
you updated the file and placed it in the "stingray" folder, not skyrocket. im sure all the people with xooms are confused by that as well....
Thanks that fixed it. Im so used to cwm, but this is way better!
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.
CHANGELOG for 3.0.2-0:
-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)
CHANGELOG for 3.1.0-0:
-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 here: https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9 (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
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!
DOWNLOAD:
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
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:
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.
Awesome Work!
Team Win is a pretty fitting name. :good:
Beats the hell out of ClockworkMod.
Well done! Installs and backs up fine.
What's with the clock though in Recovery? Is the system time not available? Seems to think that it's back at the start of the unix epoch
If you go Advanced -> Terminal Command - > Select -> Type "date" -> press enter
Date returns : Wed Jan 7 15:21:55 EST 1970
Installed like a boss. Backed up and ready to go.
Sent from my SCH-I535 using xda app-developers app
** instructions **
For dummies like me ...
Download the GooManager App ... direct download or Play Store produce the same results -- GooManager 2.1.1. If you direct download, scroll to the bottom of the page for the most recent version.
Once you have GooManager installed, open it and go to Menu>Install OpenRecoveryScript>Yes. GooManager will automatically find and install the most recent recovery for your phone. In our case, this is TWRP 2.2.
To confirm installation, push Reboot Recovery from GooManager's main screen.
Things to know:
1. Backup files are accessible through >data>media>TWRP, even though they are on your internal SD card.
2. Zip files you want to flash are also accessible through >data>media, if you first move them to the root of your internal SD card before booting into recovery.
Pj
Phoenix, AZ
For anyone that is having problems backing up to EXTERNAL SD Card please take a look at this: Link
Took me a while to figure out why my 64GB MicroSD wasn't being detected by any recovery and several apps couldn't detect it.
ChuckFarley said:
Installed like a boss. Backed up and ready to go.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
So this working perfect for you then? I might have to switch over to this recovery cause it looks badass!
pdinphx said:
For dummies like me ...
Download the GooManager App ... direct download or Play Store produce the same results -- GooManager 2.1.1. If you direct download, scroll to the bottom of the page for the most recent version.
Once you have GooManager installed, open it and go to Menu>Install OpenRecoveryScript>Yes. GooManager will automatically find and install the most recent recovery for your phone. In our case, this is TWRP 2.2.
To confirm installation, push Reboot Recovery from GooManager's main screen.
Pj
Phoenix, AZ
Click to expand...
Click to collapse
Sorry, but do you need to already be rooted to do this?
d1ez3 said:
Sorry, but do you need to already be rooted to do this?
Click to expand...
Click to collapse
Of course.
mds96 said:
So this working perfect for you then? I might have to switch over to this recovery cause it looks badass!
Click to expand...
Click to collapse
Yup, working great! Nice easy install, too.
Sent from my SCH-I535 using xda app-developers app
jmacko said:
Well done! Installs and backs up fine.
What's with the clock though in Recovery? Is the system time not available? Seems to think that it's back at the start of the unix epoch
If you go Advanced -> Terminal Command - > Select -> Type "date" -> press enter
Date returns : Wed Jan 7 15:21:55 EST 1970
Click to expand...
Click to collapse
I have the same situation with the time and date, but otherwise appears to be working perfectly. I posted the question on their github site to see if something needs to be done.
d1ez3 said:
Sorry, but do you need to already be rooted to do this?
Click to expand...
Click to collapse
Is the bug where the backup dates showing 1970 still exist? Something still seems weird regarding the date/time according to the poster above.
I've been able to backup with this recovery, but I have not tried to restore a backup.
Also, I have not been able to flash any zips, as the recovery doesn't allow me to explore either my internal or external sd cards.
What am I doing wrong?
Pj
Phoenix, AZ
will this work for all the other carriers as well? the original TWRP file that birdman posted on rootz he said that it should. i know this is changed but wonder if that still holds true.
would it work with sprint?
Just wanted to say I've created a backup and successfully restored. I was also able to flash a different boot animation from this thread: http://forum.xda-developers.com/showthread.php?t=1756885.
The only issue is with the date/time with the backup, but not a big deal.
zeddicus225 said:
Just wanted to say I've created a backup and successfully restored. I was also able to flash a different boot animation from this thread: http://forum.xda-developers.com/showthread.php?t=1756885.
The only issue is with the date/time with the backup, but not a big deal.
Click to expand...
Click to collapse
Thanks for confirming restore functionality.
Sent from my SCH-I535 using xda premium
zeddicus225 said:
Just wanted to say I've created a backup and successfully restored. I was also able to flash a different boot animation from this thread: http://forum.xda-developers.com/showthread.php?t=1756885.
The only issue is with the date/time with the backup, but not a big deal.
Click to expand...
Click to collapse
Where did you put the zip so that this recovery could find it?
Pj
Phoenix, AZ
so you just root, then load goo manager and let goo manager load the recovery right?
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.
CHANGELOGS :
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.
TWRP 3.0.0.0_2 (All Variants support)
twrp-3.0.0.0_2-falcon.img #CHANGELOG
Old downloads :
OLD TWRP 3.0.0.0
twrp-3.0.0-falcon_gpe.imgtwrp-3.0.0-falcon.img
Latest TWRP 2.8.7.0
twrp-2.8.7.0.-falcon_M_GPE.img
twrp-2.8.7.0.-falcon_M_GPE_NOTHEME.img
twrp-2.8.7.0.-falcon_M_STOCK.img
twrp-2.8.7.0.-falcon_M_STOCK_NOTHEME.img
TWRP 2.8.7.0
twrp-2.8.7.0.-falcon_GPE.img - 9.8 Mo (AFH Mirror)
twrp-2.8.7.0.-falcon_GPE_NOTHEME.img - 9.2 Mo (AFH Mirror)
twrp-2.8.7.0.-falcon_STOCK.img - 9.8 Mo (AFH Mirror)
twrp-2.8.7.0.-falcon_STOCK_NOTHEME.img - 9.2 Mo (AFH Mirror)
TWRP 2.8.6.0 - OLD
twrp-2.8.6.0-falcon.img - 9.0 Mo
twrp-2.8.6.0-falcon_GPE.img - 9.0 Mo
*Later
twrp-2.8.6.0-falcon_GPE.img - 10.0 Mo
twrp-2.8.6.0-falcon.img - 9.9 Mo
* Later later 2.8.6.0.1
twrp-2.8.6.0.1-falcon_GPE.img - 8.9 Mo
twrp-2.8.6.0.1-falcon_STOCK.img - 8.9 Mo
* Later later later
twrp-2.8.6.0.-falcon_GPE_NOTHEME.img - 9.2 Mo
twrp-2.8.6.0.-falcon_GPE.img - 9.8 Mo
twrp-2.8.6.0.-falcon_MULTI_NOTHEME.img - 9.2 Mo (Might be able to run GPE and STOCK. This need to be tested !)
twrp-2.8.6.0.-falcon_STOCK_NOTHEME.img - 9.2 Mo
twrp-2.8.6.0.-falcon_STOCK.img - 9.8 Mo
twrp-2.8.6.0.-falcon_MULTI.img - 9.8 Mo (Might be able to run GPE and STOCK. This need to be tested !)
TWRP 2.8.5.0
twrp-2.8.5.0-falcon.img - 10.0 Mo
twrp-2.8.5.0-falcon_GPE.img - 10.0 Mo
TWRP 2.8.4.0
openrecovery-twrp-2.8.4.0-falcon_GPE.img is for GPE ONLY (ext4 userdata)
openrecovery-twrp-2.8.4.0-falcon_STOCK.img is for STOCK ONLY (f2fs userdata)
openrecovery-twrp-2.8.4.0-falcon_GPE_LP.img is for GPE ONLY (ext4 userdata & lollipop bootloader)
openrecovery-twrp-2.8.4.0-falcon_STOCK_LP.img is for STOCK ONLY (f2fs userdata & lollipop bootloader)
TWRP 2.8.3.0
twrp-2.8.3.0_falcon-GPE_sub77.img
twrp-2.8.3.0_falcon-STOCK_sub77.img
TWRP 2.8.2.0 :
twrp-2.8.2.0_falcon-GPE.img is for GPE ONLY (ext4 userdata)
twrp-2.8.2.0_falcon-STOCK.img is for STOCK ONLY (f2fs userdata)
How to install ? :
Do
Code:
sudo fastboot flash recovery twrp-3.0.0-falcon_gpe.img
or
Code:
sudo fastboot flash recovery twrp-3.0.0-falcon_gpe.img
Sources
- android_device_motorola_falcon
Bugs ?
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
Support
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
[RECOVERY][falcon] TWRP 3.0.0-0 touch recovery [2016-03-06], Tool/Utility for the Moto G
Contributors
h2o64
Version Information
Status: Stable
Created 2014-12-22
Last Updated 2016-03-06
is it normal if I can see some line running from top to bottom of my screen?
and I can do backup but can not restore it.
and can not boot after this.
it's really alpha
gpe 5.0.1
S0bes said:
is it normal if I can see some line running from top to bottom of my screen?
and I can do backup but can not restore it.
and can not boot after this.
it's really alpha
gpe 5.0.1
Click to expand...
Click to collapse
I know fixes.
New release in a minute.
h2o64 said:
I know fixes.
New release in a minute.
Click to expand...
Click to collapse
it is gpe related. i have just checked with xt1032.
Is dis multirom recovery and btw how much you approached in multirom ..
sub77 said:
it is gpe related. i have just checked with xt1032.
Click to expand...
Click to collapse
Yes yes.
I'm uploading the two new files :
twrp.fstab is the fstab for backup.
BUT the actual one backup userdata f2fs only.
SO we needed to make 2 different ones
Bhavy123 said:
Is dis multirom recovery and btw how much you approached in multirom ..
Click to expand...
Click to collapse
@sub77 and me are doing this in order to get a proper Multirom v30 (TWRP 2.8.2.0 based)
h2o64 said:
Yes yes.
I'm uploading the two new files :
twrp.fstab is the fstab for backup.
BUT the actual one backup userdata f2fs only.
SO we needed to make 2 different ones
@sub77 and me are doing this in order to get a proper Multirom v30 (TWRP 2.8.2.0 based)
Click to expand...
Click to collapse
Wish you all d best and really wish that you sussessfully port one to our device.Thanks for d hardwork btw how much time will it take more to port multirom ?
Bhavy123 said:
Wish you all d best and really wish that you sussessfully port one to our device.Thanks for d hardwork btw how much time will it take more to port multirom ?
Click to expand...
Click to collapse
I don't know
NEW BUILD :
- graphic issue fixed
- add differents recoveries for GPE or STOCK
@sub77 , MTP issue is due to the lollipop encrytion.
Maybe "twrp set tw_mtp_enabled 0" will solved it ?
Backup/ Restore works without any issues on XT1032 Retail EU, first version of TWRP2.8.2.0. :good:
Cant download new version from Mega (shows me only blank screen), Mirror would be nice :fingers-crossed:
Kai Obey said:
Backup/ Restore works without any issues on XT1032 Retail EU, first version of TWRP2.8.2.0. :good:
Cant download new version from Mega (shows me only blank screen), Mirror would be nice :fingers-crossed:
Click to expand...
Click to collapse
I'm mirroring.
Thanks a lot for this, specially for fixing the graphical glitch. I'll be trying it on GPE 5.0.1 ASAP. By the way, can you hangouts me? Thanks
Edit: After flashing, the screen flickering is still there
mount usb storage doesn't work - stock version.
xpirt said:
mount usb storage doesn't work - stock version.
Click to expand...
Click to collapse
Sure ?
EDIT :
MTP doesn't work
@h2o64 I flashed gpe version!!
Graphical glitch is there and i cant even factory reset!!
The recovery restarts when i do factory reset!!
Sent from my Moto G using XDA Free mobile app
your mirror is broken
also i cannot get into recovery at all
i see teamwin logo for a moment and then my phone reboots into lollipop
calusari said:
your mirror is broken
also i cannot get into recovery at all
i see teamwin logo for a moment and then my phone reboots into lollipop
Click to expand...
Click to collapse
Just reboot again and it should work.
Else, provide logs please
Flashhhh said:
@h2o64 I flashed gpe version!!
Graphical glitch is there and i cant even factory reset!!
The recovery restarts when i do factory reset!!
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
The factory reset make the device reboot because there is a wierd thing with the userdata partiotion (encryption issues ... again ...) BUT the partition is wiped.
Could you describe the graphical glitch ?
Flashed the stock image on a german xt1032
Usb-otg, wiping cache/dalvik, flashing supersu zip (on 4.4.4 stock) all working :good:
Edit: Flashed update to 2.8.3 and now recovery is unusable because of massive screen issues..
With techerrata's build screen is fine..
Added TWRP 2.8.3.0 Version
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.
@h2o64 what is the difference between this build and official build
Edit : OK I got the answer
reversegear said:
@h2o64 what is the difference between this build and official build
Edit : OK I got the answer
Click to expand...
Click to collapse
And here, we know who built it, we know the trees,...
And we can upgrade faster.
I made this recovery because I'm working on multirom and I wanted to share this piece of work
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.
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.
DOWNLOAD:
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:
You can find more information and download links on our NEW website! NOTE that the 2.8.6.0 version is ONLY available on our new site and is not available on our other, older mirrors!
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
TWRP 3.0.0-x OFFICIAL Builds, Tool/Utility for the HTC Pico (Explorer)
Contributors
MSF Jarvis, abhi_qwerty, thewisenerd,Dees_Troy
Source Code: https://github.com/TeamWin/android_device_htc_pico
Version Information
Status: Stable
Current Stable Version: 3.0.0-2
Stable Release Date: 2016-03-22
Created 2015-12-31
Last Updated 2016-03-23
Reserved
Features:
- Material UI thanks to @z31s1g
- F2FS compatible
- Supports OpenRecoveryScript commands placed in /cache/recovery -- Was borked in 2.8.0.0 and 2.8.5.0
- Data backups are now functional; backup sd-ext if you're on one of my ROMs
- Issues with bootloops due to dirty flashes solved. For those on aw3som3 or CM 12.1, use respective images from my TWRP Experiments Thread.
Reserved
Bugs(Currently very minor ones, thank god)
- MTP borked on Arch Linux (reported by @abhi_qwerty)
- USB Storage borked on Windows (tested by me)
Useful Links
- Flashing Guide
- NAND Recovery
MSF Jarvis said:
Since this is an alpha build, I'll need all the feedback I can get. I currently require feedback for whether USB Storage and MTP are working or not. @chankya, wanna help?
Click to expand...
Click to collapse
hey MSF yes both MTP and usb storage worked for me i booted up your cyanogen os build with this recovery that worked too. Let you know if i found any bug :good:
chankya said:
hey MSF yes both MTP and usb storage worked for me i booted up your cyanogen os build with this recovery that worked too. Let you know if i found any bug :good:
Click to expand...
Click to collapse
Thanks. @abhi_qwerty has also confirmed his download. He'll also confirm if they work on Linux.
MSF i tried this on ubuntu 15.10 so it is working on linux don't know about windows
chankya said:
MSF i tried this on ubuntu 15.10 so it is working on linux don't know about windows [emoji14]
Click to expand...
Click to collapse
Means it'll probably work on my Wily Werewolf system too. Will check Windows compatibility at night when Dad comes back from office. Sometimes helps to have a non-techie family[emoji6]
MSF Jarvis said:
Means it'll probably work on my Wily Werewolf system too. Will check Windows compatibility at night when Dad comes back from office. Sometimes helps to have a non-techie family[emoji6]
Click to expand...
Click to collapse
True story :good::good:
Mission accomplished.
USB Storage is dead on Windows 8.1, but MTP works almost as fast as USB Storage. Shouldn't be an issue for anyone.:fingers-crossed:
@abhi_qwerty, have a read of this and then tell if the issue persists.
Does this work with older JB and KitKat ROMs that are not aw3some based?
hrkh83 said:
Does this work with older JB and KitKat ROMs that are not aw3some based?
Click to expand...
Click to collapse
Unfortunately not. But I can cook something up if there's people wanting that.
Edit: Though that'll qualify as unofficial, as it'll be a personal build. That'll show up on the Experiments thread, if ever.
MSF Jarvis said:
Unfortunately not. But I can cook something up if there's people wanting that.
Edit: Though that'll qualify as unofficial, as it'll be a personal build. That'll show up on the Experiments thread, if ever.
Click to expand...
Click to collapse
@MSF Jarvis
Yes.
I would be deeply grateful if you could make a non-aw3som3 based updated TWRP available for me and other users who want to install older ROMs.
hrkh83 said:
@MSF Jarvis
Yes.
I would be deeply grateful if you could make a non-aw3som3 based updated TWRP available for me and other users who want to install older ROMs.
Click to expand...
Click to collapse
Available here
MSF Jarvis said:
Available here
Click to expand...
Click to collapse
@MSF Jarvis
Thank you very much. I am deeply grateful. I will try it and report back.
hrkh83 said:
@MSF Jarvis
Thank you very much. I am deeply grateful. I will try it and report back.
Click to expand...
Click to collapse
Good. I haven't got around to trying this out so testers are appreciated.
hrkh83 said:
@MSF Jarvis
Thank you very much. I am deeply grateful. I will try it and report back.
Click to expand...
Click to collapse
But I don't see any download on it. Are you sure you downloaded the right recovery image??
Sent from my HTC Explorer A310e using Tapatalk
!!!!!!!!!! Serious help needed !!!!!!!!!
I flashed 2.8.7.0 using Rashr(Cause my phone usb somehow got fu*ked up and couldnt do fastboot using pc).
Now I am trying to flash new ROM . It's not allowing boot any ROM, i dint get any error while flashing , success msg is coming but it's not booting up(even I aint seeing any ROM bootanimation) and again TWRP recovery menu is coming. Already tried flashing 4 ROMS no luck :'(
And I also tried flashing new recovery(old version) using 'image' toggle but it's giving 255 error.
Please help me I anit using my mobile and I dnt have any other mobile.
ReX-Hell2heAven said:
!!!!!!!!!! Serious help needed !!!!!!!!!
I flashed 2.8.7.0 using Rashr(Cause my phone usb somehow got fu*ked up and couldnt do fastboot using pc).
Now I am trying to flash new ROM . It's not allowing boot any ROM, i dint get any error while flashing , success msg is coming but it's not booting up(even I aint seeing any ROM bootanimation) and again TWRP recovery menu is coming. Already tried flashing 4 ROMS no luck :'(
And I also tried flashing new recovery(old version) using 'image' toggle but it's giving 255 error.
Please help me I anit using my mobile and I dnt have any other mobile.
Click to expand...
Click to collapse
Which ROM were you using before this?
Sent from my pico using XDA Labs
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.
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
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 arm65 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)
DOWNLOAD FOLDER :
TWRP-3.0.2-0
INSTALL METHOD [ODIN] :
1. Open Odin.
2. Reboot phone in to Download Mode (press and hold Volume Down + Home + Power buttons).
3. Connect phone and wait until you get a blue sign in Odin.
4. Insert .tar.md5 file to PDA/AP.
5. Make sure re-partition is NOT ticked.
6. Click the start button, sit back and wait a few minutes.
7. Wait until the flashing process is complete.
8. And have fun with TWRP 3.0.2-0 .
FEATURE :
1. f2fs [not tested] if u want use this fs make sure u're running kernel with f2fs support.
2. SElinux [full selinux support]
3. MTP, sideload, shell, and etc are working fine.
BUGS :
same as 3.0.0-0, i mean can't set brightness.
report to me if u find another bug
CREDITS :
CyanogenMod Team
Omni Team
@NV-Dev
@lesleyxxx15
DO WITH YOUR OWN RISK !!!
IF YOU WANNA RESHARE THIS RECOVERY, PLEASE FOLLOW THIS RULES :
DON'T USE SHORTENER LINK (i.e. adfly, adfoc, etc)
Source Code : soon
Press thanks button if u like me or like my twrp
Reserved
The MD5 is invalid. at least on my computer
Avikush said:
The MD5 is invalid. at least on my computer
Click to expand...
Click to collapse
change name TWRP-3.0.2-0-UNOFFICIAL-royss.tar.md5 to recovery.tar.md5 sorry for that, will re-up the correct name
Here is the S6310T version:
http://www.mediafire.com/file/x293x7c1zp3wvp0/TWRP-3.0.2-0-20161013-UNOFFICIAL-royss-S6310T.zip
Thanks @zainifame
latest build.
Avikush said:
Here is the S6310T version:
http://www.mediafire.com/file/15c23j6ksqti2z8/recovery-TWRP-3.0.2-S6310T.img
Thanks @zainifame
---------- Post added at 09:38 PM ---------- Previous post was at 09:33 PM ----------
I can't connect through ADB, "unauthorized"
Click to expand...
Click to collapse
have u add 51-android.rules to your ubuntu or else linux os?
on my twrp build adb are working fine, test on my s6310, I'll check it out your attachment later
zainifame said:
have u add 51-android.rules to your ubuntu or else linux os?
on my twrp build adb are working fine, test on my s6310, I'll check it out your attachment later
Click to expand...
Click to collapse
sideload is working fine. only problem is the shell, push, pull and the rest of the commands.
on NV-dev build it works without hitting anything on the phone, just boot recovery.
Here it's says "unauthorized" (windows) or "device offline" (linux), in your build and in mine too (which is not a build actually, just another kernel)
Avikush said:
sideload is working fine. only problem is the shell, push, pull and the rest of the commands.
on NV-dev build it works without hitting anything on the phone, just boot recovery.
Here it's says "unauthorized" (windows) or "device offline" (linux), in your build and in mine too (which is not a build actually, just another kernel)
Click to expand...
Click to collapse
will check again later bro, i want prepare for school so i can't help now
new build is up, goto OP for download link
changelog :
fix adb access [unauthorized]
fix reboot mode
still can't set brightness, will try fix this at next build
zainifame said:
new build is up, goto OP for download link
changelog :
fix adb access [unauthorized]
fix reboot mode
still can't set brightness, will try fix this at next build
Click to expand...
Click to collapse
Your updater script missing some characters, so it's not working
Avikush said:
Your updater script missing some characters, so it's not working
Click to expand...
Click to collapse
already re-up new file, download again
I just flashed it and it doesn't detect my external sdcard (0mb, should be 2gb; filesystem is fat32), while OS detects it normally.
Then I flashed 2.8.5.0 and it works flawlessly.
Mckol said:
I just flashed it and it doesn't detect my external sdcard (0mb, should be 2gb; filesystem is fat32), while OS detects it normally.
Then I flashed 2.8.5.0 and it works flawlessly.
Click to expand...
Click to collapse
it's fine on me using my last build 3.0.2-0, can u send me recovery.log and last_log while u'r using my build? i will check it
Ok I'm gonna try it now. edit: Still the same problem, cannot mount sdcard. Here is the last log http://pastebin.com/wGyVELLc
Mckol said:
Ok I'm gonna try it now. edit: Still the same problem, cannot mount sdcard. Here is the last log http://pastebin.com/wGyVELLc
Click to expand...
Click to collapse
It's weird, on my gt-s6310 it can mount eksternalsd, what exactly your device variant?
Sent from my land using XDA Labs
zainifame said:
It's weird, on my gt-s6310 it can mount eksternalsd, what exactly your device variant?
Click to expand...
Click to collapse
It's exactly GT-S6310 not 12 nor t. It's from Polish carrier plus BTW, but I think there's nothing left from stock.
will it work on 6312 or 6313t ?
fbs said:
will it work on 6312 or 6313t ?
Click to expand...
Click to collapse
Don't know, just try
Sent from my land using XDA Labs
It 's work on s6312
Thank youuuuuuu :good::good:
Please update !