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.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 (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
Downloads:
Universal For All T6 Variants
Official - https://dl.twrp.me/t6univ
Installation:
Unlock your phone at www.htcdev.com
Boot phone into fastboot
Perform command fastboot flash recovery twrp-3.2.1-0-t6univ.img
Boot into HBOOT and select recovery
Root:
Download SuperSU http://download.chainfire.eu/supersu
Flash it in recovery
Copy backup to PC suing a PC:
adb shell
su
chmod -R 777 /data/media/TWRP
exit
Now you can copy your backup over
XDA:DevDB Information
TWRP, Tool/Utility for the HTC One Max
Contributors
Flyhalf205
Version Information
Status: Testing
Created 2013-10-26
Last Updated 2018-01-15
Great start @flyhalf
Sent from my HTC One using Tapatalk
Right now it is a 50/50 chance of it being pink and double.
It's not pink and double, however, it doesn't appear to be mounting any of the partitions. "Invalid block device" for all of them.
navalynt said:
It's not pink and double, however, it doesn't appear to be mounting any of the partitions. "Invalid block device" for all of them.
Click to expand...
Click to collapse
I'm shocked it isn't pink. I will fix it later this weekend then. But sounds like an easy fix then. Thanks for update
EDIT: I just uploaded a new copy. @navalynt ... Mounts should be fixed. Also if this does boot. Try turning off phone to see if offmode_charging_animation works Thank you
Damn, fly u everywhere. Lol.
Sent from my HTC Butterfly s using XDA Premium 4 mobile app
---------- Post added at 11:04 AM ---------- Previous post was at 11:03 AM ----------
I cant wait to get my hands on the max!
Sent from my HTC Butterfly s using XDA Premium 4 mobile app
I will try it later today. Since I got one MAX last week.
Sent from my HTC_One_max using xda premium
I put up a new link. Fixed the mounts I do believe so. Someone test it out please.
@zounduser In a crazy way I do end up in a lot of places ha.
Flyhalf205 said:
I put up a new link. Fixed the mounts I do believe so. Someone test it out please.
@zounduser In a crazy way I do end up in a lot of places ha.
Click to expand...
Click to collapse
Backup and restore working in latest version.
So does mounts and adb sideload.
Sent from my C6806 using XDA Premium 4 mobile app
Can anyone confirm root works ? Tried the other thread and I've unlocked boot loader Nd instAlle clockwork which I can confirm works, but installing the root zip dosent give me root
garyfl said:
Can anyone confirm root works ? Tried the other thread and I've unlocked boot loader Nd instAlle clockwork which I can confirm works, but installing the root zip dosent give me root
Click to expand...
Click to collapse
Go flash http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
Flyhalf205 said:
Go flash http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
Click to expand...
Click to collapse
Still dosent work, I still cannot change pixel density or install viper4android
garyfl said:
Still dosent work, I still cannot change pixel density or install viper4android
Click to expand...
Click to collapse
Any changes you make inside the ROM and reboot it will be reverted because of system has write protection on stock kernel.
Flyhalf205 said:
Any changes you make inside the ROM and reboot it will be reverted because of system has write protection on stock kernel.
Click to expand...
Click to collapse
So wait to flash a custom Rom essentially ?
garyfl said:
So wait to flash a custom Rom essentially ?
Click to expand...
Click to collapse
You can boot into recovery and flash things and it will stick. You can edit the build.prop for the density in recovery. You'll have to pull then push and fix permission on it. Reboot and sucess.
Sorry I don't understand, my knowledge is very limited up to this point.
garyfl said:
Sorry I don't understand, my knowledge is very limited up to this point.
Click to expand...
Click to collapse
Do you have a custom recovery?
Sent from my Nexus 4 using XDA Premium 4 mobile app
jschur1 said:
Do you have a custom recovery?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yep one max unlocked boot loader Nd custom recovery
Flyhalf205 said:
I'm shocked it isn't pink. I will fix it later this weekend then. But sounds like an easy fix then. Thanks for update
EDIT: I just uploaded a new copy. @navalynt ... Mounts should be fixed. Also if this does boot. Try turning off phone to see if offmode_charging_animation works Thank you
Click to expand...
Click to collapse
Charging animation shows up when the phone is off.
Any work on getting the recovery working on the sprint model? T6whl
Related
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Dees_Troy said:
[RECOVERY] TeamWin Recovery Project (twrp) 2.0.0RC0 [2011-12-17]
Team Win Recovery Project 2.0, or twrp2 for short, is a custom recovery built with ease of use and customization in mind.
Special thanks to xboarder56 for helping test the port and a couple of other testers that I forget the names of at the moment.
Click to expand...
Click to collapse
NICE, thanks to the both of you! Goin' on tonight fo sho.
Very nice job guys! I just might have to update my signature now.
Is there any future in external sdcard support?
Looks good I guess I'll have to update from the old version, thanks.
Awesome work guys.... this kicks total butt!
Nice! It's come a long way since I used it on my 3D. Alot faster compressed backup, thanks
Sent from my HTC Amaze 4G using xda premium
Has anyone had luck installing this on amaze????
Sent from my HTC Amaze 4G using xda premium
milo356 said:
Has anyone had luck installing this on amaze????
Sent from my HTC Amaze 4G using xda premium
Click to expand...
Click to collapse
I have. I can do it in different ways. flash_image recovery recoveryname.img command from the phone itself if you have the flash_image binary installed or by fastboot flash recovery recoveryname.img with the phone in bootloader mode.
Not complicated at all.
Works great, so much better than using the volume up/down keys and power keys. Two weird things that I want to see if anyone else is having issues with (want to know if it is worth reporting on the github)
1. After accessing recovery I get the "Tell HTC" This phone has just recovered from a abnormal reset message. Didn't get that with clockwork, not sure if it is a bug or not.
2. Cant mount ext SD card. Saw that the EVO 3D had the same issue but they had fixed it. I assume this is a problem with the Amaze since it is the same with clockwork mod?
Sikety said:
Works great, so much better than using the volume up/down keys and power keys. Two weird things that I want to see if anyone else is having issues with (want to know if it is worth reporting on the github)
1. After accessing recovery I get the "Tell HTC" This phone has just recovered from a abnormal reset message. Didn't get that with clockwork, not sure if it is a bug or not.
2. Cant mount ext SD card. Saw that the EVO 3D had the same issue but they had fixed it. I assume this is a problem with the Amaze since it is the same with clockwork mod?
Click to expand...
Click to collapse
Use this one if you want to backup and restore to and from external sdcard.
pardon the question, I've looked all over TeamWin's web site... Is there a way to boot the Amaze into twerp directly?
gregma said:
pardon the question, I've looked all over TeamWin's web site... Is there a way to boot the Amaze into twerp directly?
Click to expand...
Click to collapse
I don't understand your question.
You want to reboot into recovery?
adb reboot recovery
or use the 22 different other ways to reboot into recovery.
Binary100100 said:
I don't understand your question.
You want to reboot into recovery?
adb reboot recovery
or use the 22 different other ways to reboot into recovery.
Click to expand...
Click to collapse
I'm talking about rebooting into recovery when I'm not anywhere near a computer. Such as on my HD2, I would hold the power button down until in MAGLDR, then choose to boot into Recovery. Is there something similar on the Amaze?
Greg
gregma said:
I'm talking about rebooting into recovery when I'm not anywhere near a computer. Such as on my HD2, I would hold the power button down until in MAGLDR, then choose to boot into Recovery. Is there something similar on the Amaze?
Greg
Click to expand...
Click to collapse
Which rom are you using?
There are a couple of roms that have the Advanced Power Menu that has a reboot option. When selected it gives you other options such as recovery and bootloader.
There are also a few apps (do a search for Reboot Recovery) on the Market.
I have always used the option from ROM Manager.
You can also use terminal emulator and use the command "reboot recovery" and that should do it too.
You can also power off the device, hold volume down while pressing power to get to hboot mode then select recovery.
Binary100100 said:
Which rom are you using?
There are a couple of roms that have the Advanced Power Menu that has a reboot option. When selected it gives you other options such as recovery and bootloader.
There are also a few apps (do a search for Reboot Recovery) on the Market.
I have always used the option from ROM Manager.
You can also use terminal emulator and use the command "reboot recovery" and that should do it too.
You can also power off the device, hold volume down while pressing power to get to hboot mode then select recovery.
Click to expand...
Click to collapse
Stock ROM right now, I'm getting things set to start flashing new ROM's. Aha! I did see the "recovery" in hboot. Now once I figure out how I lost the ability to get into hboot by holding the volume down button I'll be good to go!
Greg
---------- Post added at 01:55 PM ---------- Previous post was at 01:22 PM ----------
gregma said:
Stock ROM right now, I'm getting things set to start flashing new ROM's. Aha! I did see the "recovery" in hboot. Now once I figure out how I lost the ability to get into hboot by holding the volume down button I'll be good to go!
Greg
Click to expand...
Click to collapse
I LOVE answering my own darned post.... Didn't realize you had to battery power cycle the device to get it back into hboot. I'm good to go now!
Greg
ok i got it loaded up fine on my phone but i cannot figure out how to flash. i click the install button and it takes me to my directories but i dont see any files in the directories... there is no files listed in the root of either sd card as well. what am i doing wrong?
2sh0rt said:
ok i got it loaded up fine on my phone but i cannot figure out how to flash. i click the install button and it takes me to my directories but i dont see any files in the directories... there is no files listed in the root of either sd card as well. what am i doing wrong?
Click to expand...
Click to collapse
Move the zip file to the other sdcard. Remember that you have two.
Here's a free tip!
Make two empty zip files.
Name one internal.zip
Name the other external.zip
Place the internal.zip in the internal sdcard and the external.zip in the external sdcard.
Reboot into recovery and if you see internal.zip file. Guess what sdcard you're looking at? Same goes for external.
Binary100100 said:
Move the zip file to the other sdcard. Remember that you have two.
Here's a free tip!
Make two empty zip files.
Name one internal.zip
Name the other external.zip
Place the internal.zip in the internal sdcard and the external.zip in the external sdcard.
Reboot into recovery and if you see internal.zip file. Guess what sdcard you're looking at? Same goes for external.
Click to expand...
Click to collapse
Dude, i know this... i came from the vibrant. Im saying that NEITHER card shows ANY files... only directories... no zips on the root of /sdcard or /sdcard/ext-sd... nada, zip, zilch
2sh0rt said:
Dude, i know this... i came from the vibrant. Im saying that NEITHER card shows ANY files... only directories... no zips on the root of /sdcard or /sdcard/ext-sd... nada, zip, zilch
Click to expand...
Click to collapse
I came from the vibrant as well however I wasn't so active there.
I don't understand why you don't see any zip files then. Strange.
Me either... think i'll just try and reload it and see what happens. Thought maybe i was clicking the wrong thing or not clicking something.
---------- Post added at 07:47 PM ---------- Previous post was at 07:43 PM ----------
and its not just that i dont see any zip files. i dont see ANY files at all! every directory i click is empty! even on the system partition! not a single file shows up. only directories and when i click them there is nothing except /.. and /.
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:
What's new in 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.
What's new in 2.6.3.0:
Proper backup and restore of SELinux contexts (thanks to Tassadar)
Pull in some ROM information for backup name generation
Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
Add 1200x1920 theme (thanks to Tassadar)
A few other fixes and tweaks
What's new in 2.6.1.0:
Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
Initial support for f2fs file system formatting (Moto X)
Update SuperSU install for 4.3 ROMs
Fixed a permissions bug on files created during backup
Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
Ignore lost+found folder during backup and size calculations
Various other minor bug fixes and tweaks
Downloadhttp://techerrata.com/browse/twrp2/m8
Huge shoutouts go specifically to
@Flemmard @bigbiff @Dees_Troy
I learned how to properly deal with DTB from these guys....
Known Issues:
No known issues anymore
No exFAT support. Need kernel source to investigate. This is only temporary. FAT32 works perfectly fine.
Random segfaults when starting actions. i.e. flashing restoring, backing up. Just makes you redo what you were trying to do. Dees_troy deems this nearly impossible to trace.
hmm wondering if this will work for the ATT variant since the DTB is variant specific usually, at least thats how it was on the G2.
Just wondering about off mode charging. Is it ok? I know there were issues with 2.7 on the m7. I was just wondering are the same issues present in the m8?
Whenever I finish flashing a ROM the screen goes off immediately, doesn't give me the chance to reboot. Doesn't seem right?
nice one thanks i can backup to ext sd now
djkinetic said:
hmm wondering if this will work for the ATT variant since the DTB is variant specific usually, at least thats how it was on the G2.
Click to expand...
Click to collapse
im using it on ATT version just fine
Ghost said:
Just wondering about off mode charging. Is it ok? I know there were issues with 2.7 on the m7. I was just wondering are the same issues present in the m8?
Click to expand...
Click to collapse
off mode charging works just fine.
guywithdesire1992 said:
Whenever I finish flashing a ROM the screen goes off immediately, doesn't give me the chance to reboot. Doesn't seem right?
Click to expand...
Click to collapse
In the second post, it talks about this.
jmz said:
im using it on ATT version just fine
off mode charging works just fine.
In the second post, it talks about this.
Click to expand...
Click to collapse
Excellent just wanted to make sure as DTB can be kind of a pain, when it comes to different variants.
djkinetic said:
Excellent just wanted to make sure as DTB can be kind of a pain, when it comes to different variants.
Click to expand...
Click to collapse
From the experimenting that has been done all the GSM DTBs are compatible with each other. And all the CDMA DTBs are compatible with each other. But not between GSM and CDMA.
Well i just tried on my m8 att variant and i get stuck at the teamwin curtain screen go figure lol
djkinetic said:
Well i just tried on my m8 att variant and i get stuck at the teamwin curtain screen go figure lol
Click to expand...
Click to collapse
Thats very odd. I have the ATT variant and using this
Try 2 things for me. Reflash but do fastboot erase cache before doing it. Then if it still doesn't work see if you have ADB when at the splash
jmz said:
Thats very odd. I have the ATT variant and using this
Try 2 things for me. Reflash but do fastboot erase cache before doing it. Then if it still doesn't work see if you have ADB when at the splash
Click to expand...
Click to collapse
i did that and it didnt work, i do have working adb which is how i was able to get back in hboot/fastboot.
Ok i was able to fix the hang, deleted my twrp theme folder and twrp settings from the other 2.6.3.3 version of twrp.
djkinetic said:
i did that and it didnt work, i do have working adb which is how i was able to get back in hboot/fastboot.
Ok i was able to fix the hang, deleted my twrp theme folder and twrp settings from the other 2.6.3.3 version of twrp.
Click to expand...
Click to collapse
ah yeah. that will do it.
should this be supporting ext sd card for rom installations? when i browse to External SD, my rom.zip isn't seen, folder looks empty.
nugzo said:
should this be supporting ext sd card for rom installations? when i browse to External SD, my rom.zip isn't seen, folder looks empty.
Click to expand...
Click to collapse
Did you check internal sd it might of saved it there
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Jarheadflip said:
Did you check internal sd it might of saved it there
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yes i know it on my internal, i had to put it there to install it. but i would like to have my rom install files on my external and save my internal space for apps etc.
nugzo said:
yes i know it on my internal, i had to put it there to install it. but i would like to have my rom install files on my external and save my internal space for apps etc.
Click to expand...
Click to collapse
Is your sdcard in exFAT format? If so check second post
Sent from my HTC One_M8 using Tapatalk
Finally some good recovery
jmz said:
Is your sdcard in exFAT format? If so check second post
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I'll check. I formatted it with my phone, shouldn't that format it correctly?
Will this work with the Sprint version?
FIRST EVER Team Win Recovery project TWRP 2.7.0.0 Compiled From Source for Canvas HD with Full Kitkat 4.4.2 Support Courtesy of Kash Kernel [21 May 2014]
About TWRP:
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.
Click to expand...
Click to collapse
Sources :
Team Win Recovery Of Omni Source
Device Tree For Micromax A116
Modified Kernel Source of A116
Download: Check Download Tab
Instructions for flashing in your phone:
1.Download the recovery and Put it in root of your SDCARD
2.Open Mobile uncle tools and select Recovery Update
3.Flash recovery file
4.Done
5.Enjoy
Bugs: No Bugs..You can Report If found
Instructions for flashing using SP Flash Tools:
1. Install drivers for your phone using Micromax drivers.
2. Extract the Stock ROM folder and replace recovery.img with twrp recovery.
3. Extract and open the SP Flash Tools.
4. In SP Flash Tools, click on Scatter-Loading and the program will ask you the location of the scatter loading file for your device select mt6589 scatter file.txt
5.Check only recovery.img, preloader and uncheck all others.
6. Switch off your phone (Remove the battery to make sure it is switched off).
7. In Flash Tool, go to Options and Click USB Mode so that it is enabled. Click options again and then go to DA Download All > Speed and finally select High Speed.
8. Click the Download option (present on the right of Firmware
> Upgrade option) and the flash tool will start looking for your phone.
9. Connect your phone now. The Flash Tool will start the flashing process, the progress of which can be viewed from a yellow progress bar at the bottom of the flash tool.
Warning 1 - Don't interrupt this process as it can potentially brick your device.
Warning 2 - Make sure no power interruption takes place. (Use a laptop to ensure this).
10. After the process completes, a green ring will appear on your device signalling that the process was successful.
11.Disconnect your phone.
Disclaimer: By Downloading and flashing the Recovery may void your Warranty ..Ill not be Responsible for any harm .Do it on your own Risk
Please do give Feedback about My recovery So that others can Judge if its stable or not :fingers-crossed: and also it encourages me to do stuffs like this :good:
Credits:
@michfood For his Repacking Tools
@yuweng For his help
Team Win Recovery Project
@kashifmin for his Kernel
XDA:DevDB Information
TWRP 2.7 Full Touch Recovery , Tool/Utility for the Micromax A116
Contributors
suhas.holla
Version Information
Status: Stable
Current Stable Version: 2.7.0.0
Stable Release Date: 2014-05-21
Created 2014-05-21
Last Updated 2014-05-22
Reserved
What's new in 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
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 AOSP decrypt support
Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
Various SELinux fixes and bug fixes
Thanks bro, #reapect
suhas.holla said:
FIRST EVER Team Win Recovery project TWRP 2.7.0.0 Compiled From Source for Canvas HD[21 May 2014]
Click to expand...
Click to collapse
the op here may also be updated - for info of first-time/casual visitors.
We can use the mobile uncle method too right??
Ok sorry about that just read the op
Sent from my Micromax Canvas HD using XDA Premium 4 mobile app
Uhm, where is the download tab? Am i blind? :what:
GroovyG said:
Uhm, where is the download tab? Am i blind? :what:
Click to expand...
Click to collapse
http://forum.xda-developers.com/devdb/project/?id=4259#downloads
Cheers mate, found it in a normal browser. In the XDA app it's inaccessible, weird...
140+ Downloads Not Even a single reported about the Recovery..Plz do report regarding your experience with this recovery
It's brilliant, backup and flashing happens a lot faster than with previous builds.
No issues encountered so far, great job!
Thanks for the best recovery. Please add screen shots if you can?
Sent from my C2305 using XDA Premium 4 mobile app
Thanks for the Recovery. Updated the Recovery through mobile uncle tool. Was able to make a back up without md5. Generation. But could Not restore the backup inspite of disabling md5 verfication. Does anyone face such issue. Flashing a rom, wiping data, system etc works fine
Sent from my C2305 using XDA Premium 4 mobile app
suhas.holla said:
....TWRP 2.7.0.0.... for Canvas HD with Full Kitkat 4.4.2 Support Courtesy of Kash Kernel
Please do give Feedback .....So that others can Judge if its stable or not ....encourages me to do stuffs like this
Click to expand...
Click to collapse
tried this. things look fine. :good:
review after brief testing:
'auto-generate-name' and 'custom-name' backups both restored fine.
settings get saved & retained over reboots.
rom installs are also fine.
taking screenshots is a breeze, thanks to "adb-enabled in recovery".
check out my screenshots here.
Can we turn off the vibrate on touch??
Sent from my Micromax Canvas HD using XDA Premium 4 mobile app
tandevilz said:
Can we turn off the vibrate on touch?
Click to expand...
Click to collapse
go to settings --> vibration duration and lower values to zero or whatever.
and, while you're in recovery, take the time to explore all menus.
Does anyone face problem in restoring a back up made by disabling the md5 verification option. The system gives error message
Sent from my C2305 using XDA Premium 4 mobile app
baskye said:
...problem in restoring a back up made by disabling the md5 verification option. ....
Click to expand...
Click to collapse
backups with these settings restored fine.
Recovery is great, feels solid and stable while using! All setting etc working properly, nandroid backups are a LOT faster and smaller than any recovery yet, .zip installation time is noticibely faster, adb working flawlessly, USB mount I havent checked yet but sure that it will work too!
All-in-all the best recovery yet. And thanks to you @suhas.holla for it! :good::beer:
deepesh.tickoo said:
....USB mount I havent checked yet but sure that it will work too!
Click to expand...
Click to collapse
didn't work for me. please check & report (with steps/how-to). @suhas.holla too. thanks.
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.
Code:
#include
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Note:
- Decryption with pin will not work if you fastboot boot the image (disable your pin , boot the image, flash the installer, and then reboot recovery)
- If you are on stock and not rooted, then you need to flash Magisk or your device will not boot after "Installation"
- If you are already rooted on stock or Custom ROM with Magisk, you may skip "Installation" and precede below
a.) Download the latest TWRP installer zip and Magisk zip
b.) Flash the TWRP installer as a local Magisk module (Install Magisk via TWRP afterward)
Installation:
1. Download android sdk tools here
2. Enter fastboot mode (You must follow the guide to unlock your bootloader first)
3. Run "fastboot boot recoveryimgfilename.img" (flash the installer for permanent installation and decryption)
a.) If you can't decrypt to access internal storage, you probably still have your pin or pattern enabled.
Tips:
If you already have TWRP flashed, you can only flash the new installer zip from TWRP (If you have Magisk installed don't forget to flash it again afterwards).
If you have some problems with backup, like 255 error or something similar please check this guide: https://forum.xda-developers.com/oneplus-6/how-to/255-error-twrp-backup-restore-999-t3801632
Always use "system_image" and "vendor_image" instead of "system" and "vendor" when you are making a backup.
Download:
TWRP 3.3.1-0 Unofficial img and installer
Source code:
https://github.com/omnirom/android_bootable_recovery
https://github.com/C457/android_device_zte_pine/commits/twrp
https://github.com/C457/android_kernel_zte_sm8150
Donations:
Credits:
bigbiff
Dees-Troy
mauronofrio
Reserved in case something blows up
To answer one of the most anticipated questions, yes this will work on 5g models I'll make a guide in due time.
Hey unjistifieddev when will f2fs formatting be implemented? just wondering since right now its only formatting in ext4, also for some reason system backups will not restore it fails to format, so what i do is flash system image then restore data partition.
do you mean the system partition? the one formatted in ext4 is correct, data can be formatted f2fs and ext4
rafyvitto said:
Hey unjistifieddev when will f2fs formatting be implemented? just wondering since right now its only formatting in ext4, also for some reason system backups will not restore it fails to format, so what i do is flash system image then restore data partition.
Click to expand...
Click to collapse
F2fs formatting should work I'm not sure since I've been wiping my internal to make sure everything works. Also have you tried only backing up and restoring as system image and vendor image? Apparently you can't backup or restore system on these newer devices because system and vendor aren't mounted in fstab but by the kernel early before init runs fstab.
Sent from my ZTE A2020U Pro using Tapatalk
Chris axon 7 said:
do you mean the system partition? the one formatted in ext4 is correct, data can be formatted f2fs and ext4
Click to expand...
Click to collapse
Stock uses f2fs by default and does not mount data as ext4 at all. If it's formatting data in ext4 that's a problem, but I'm not sure that is. Both op7 and Zenfone 6 use f2fs by default and my trees for TWRP were based on them.
Sent from my ZTE A2020U Pro using Tapatalk
Unjustified Dev said:
F2fs formatting should work I'm not sure since I've been wiping my internal to make sure everything works. Also have you tried only backing up and restoring as system image and vendor image? Apparently you can't backup or restore system on these newer devices because system and vendor aren't mounted in fstab but by the kernel early before init runs fstab.
Sent from my ZTE A2020U Pro using Tapatalk
Click to expand...
Click to collapse
Good suggestion i will give that a shot thanks.
rafyvitto said:
Good suggestion i will give that a shot thanks.
Click to expand...
Click to collapse
Which model do you have?
Sent from my ZTE A2020U Pro using Tapatalk
Unjustified Dev said:
Which model do you have?
Sent from my ZTE A2020U Pro using Tapatalk
Click to expand...
Click to collapse
US model
rafyvitto said:
US model
Click to expand...
Click to collapse
I was looking for a G user I'm trying to make TWRP detect different models so it works on all variants. For now it's set to US props so we (I lol) can flash stock.
Sent from my ZTE A2020U Pro using Tapatalk
Unjustified Dev said:
I was looking for a G user I'm trying to make TWRP detect different models so it works on all variants. For now it's set to US props so we (I lol) can flash stock.
Sent from my ZTE A2020U Pro using Tapatalk
Click to expand...
Click to collapse
I see gotcha.
I have a G model ( zte a2020g 4g)
Chris axon 7 said:
Ich hab ein G model ( zte a2020g 4g)
Click to expand...
Click to collapse
cat /proc/vendor_imem/board_id
Sent from my ZTE A2020U Pro using Tapatalk
:/ $ su
:/ # cat /proc/vendor_imem/board_id
6
:/ #
Chris axon 7 said:
:/ $ su
:/ # cat /proc/vendor_imem/board_id
6
:/ #
Click to expand...
Click to collapse
Well that's what I expected same as US board thanks.
Sent from my ZTE A2020U Pro using Tapatalk
Hmm board 14 is much more challenging and POAD kills PINE every time!!
Cheers
Unjustified Dev said:
I was looking for a G user I'm trying to make TWRP detect different models so it works on all variants. For now it's set to US props so we (I lol) can flash stock.
Sent from my ZTE A2020U Pro using Tapatalk
Click to expand...
Click to collapse
Dear, And what is the problem of collecting TWRP for the EU, there it is necessary to change the encryption in boot, I do not see any problems in this
what do you mean ? twrp can decode. I have twrp on it and encrypted data with pin, if I go into twrp and enter my pin decrypts twrp normally without problemme
Sent from my ZTE A2020G Pro using XDA Labs
http://files.nwwn.com/~unjust/Axon 10 Pro/
404 not found
Edit
side goes again
[RECOVERY] TWRP 3.5.0-0 - TeamWin Recovery Project
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. 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.
Key Features:
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)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
flame Device Config: https://github.com/bigbiff/android_device_google_coral
DOWNLOAD:
Please go to https://twrp.me to download the device image.
A11 Testing:
https://build.twrp.me/test/flame/twrp-3.6.0-0-test1-flame.img- updated for lineage-18.1 booting
Old info:
Hello, this is a test build for flame users (will work on coral crosshatch/blueline later). The image is pretty safe for backing up now.
So far I have decryption working, touch, adb and backup and restore seems to work. Super partition volumes can be mounted, and the super partition can be backed up.
Not working: sideload and fastbootd
May FW Date https://build.twrp.me/test/flame/twrp-3.3.1-0-test1-flame.img
June FW Date https://build.twrp.me/test/flame/twrp-3.4.0-0-test1-flame.img
July FW Date https://build.twrp.me/test/flame/twrp-3.4.0-0-test2-flame.img
July FW Date https://build.twrp.me/test/flame/twrp-3.4.0-0-test4-flame.img
- fix super partition restore
- fix persist partition restore
July FW Date https://build.twrp.me/test/flame/twrp-3.4.0-0-test5-flame.img
- allow repacking of TWRP boot.img
- magisk currently doesn't work
August FW Date https://build.twrp.me/test/flame/twrp-3.4.0-0-test6-flame.img
August FW Date https://build.twrp.me/test/flame/twrp-3.4.0-0-test7-flame.img
- fix repacking TWRP with magisk
August FW Date https://build.twrp.me/test/flame/twrp-3.4.0-0-test8-flame.img
- multiuser decryption support
- fastbootd support
3.5.0-0: Android 11 bringup
https://build.twrp.me/test/flame/twrp-3.5.0-0-test1-flame.img
https://build.twrp.me/test/flame/twrp-3.5.0-0-test2-flame.img
- Titan M Wipe working on Format Data
- Apex fixes for flattened directories
- Credit to @Freak07 https://github.com/freak07/FLORAL - using his kernel as a Coral/Flame TWRP base
http://twrp.me
What to backup
* super
* data
* persist
* boot
* any other partition desired
What to restore
* super
* data
* boot - depending on ROM support
Please just restore persist if you have a failed partition. I do not recommend restoring backups from phone to phone unless you know what you are doing.
Repacking TWRP into Boot partition
To repack TWRP into the boot partition to override stock recovery when rebooting to recovery, perform the following steps
1. adb push <latest_boot.img> /sdcard/
2. reboot to bootloader and fastboot latest boot.img of TWRP
3. Go to Install
4. Touch Install Image
5. Select your boot.img from /sdcard
6. Swipe to confirm flash
7. Reboot to recovery and android to verify installation
TWRP won't Boot?
Make sure you have a kernel that supports the R DTBO and LZMA ramdisk starting with test5 such as https://forum.xda-developers.com/pi...nel-kirisakuraq-1-0-0-pixel-4-xl-aka-t3992213
Is this just for flame? Or both coral and flame? Reason I ask is because the 2 devices have significant differences, and if it's just for flame, you'll want to throw it in the regular Pixel 4 subforum
This is for flame as described. I will work on coral next.
They share the same device tree btw.
Weird I thought I chose pixel 4 forum. Asking for this thread to be moved.
bigbiff said:
Weird I thought I chose pixel 4 forum. Asking for this thread to be moved.
Click to expand...
Click to collapse
Ah man lol got me all excited!
Thanks long awaited :good:
Will try later..
ok fastboot boot boots fine to TWRP but decryption wont work for me
https://paste.omnirom.org/view/e9536f05
Can confirm this works for flashing. Booted the image and then ADB pushed magisk and kernel and both flashed successfully!
Will try removing lockscreen security next attempt to gain access to internal storage which should likely work.
Great work to see, we are finally not tied to magisk for flashing things now
Mrcactuseater said:
Will try removing lockscreen security next attempt to gain access to internal storage which should likely work.
Click to expand...
Click to collapse
wont work to @my end
2WildFirE said:
Thanks long awaited :good:
Will try later..
ok fastboot boot boots fine to TWRP but decryption wont work for me
https://paste.omnirom.org/view/e9536f05
Click to expand...
Click to collapse
Can you paste logcat output too?
Please guys don't just say it doesn't work. I need recovery.log and logcat so I can debug issues.
2WildFirE said:
wont work to @my end
Click to expand...
Click to collapse
Can you please post recovery.log and logcat?
bigbiff said:
Can you please post recovery.log and logcat?
Click to expand...
Click to collapse
Yep
Is ADB logcat -l the correct one?
2WildFirE said:
Yep
Is ADB logcat -l the correct one?
Click to expand...
Click to collapse
I usually do in adb shell
logcat > /tmp/logcat.txt
Then adb pull /tmp/logcat.txt
OK here logcat https://paste.omnirom.org/view/9caa8b33
And recovery.log https://paste.omnirom.org/view/3c26a706
hope it helps
2WildFirE said:
OK here logcat https://paste.omnirom.org/view/9caa8b33
And recovery.log https://paste.omnirom.org/view/3c26a706
hope it helps
Click to expand...
Click to collapse
Can you tell me your android build version?
bigbiff said:
can you tell me your android build version?
Click to expand...
Click to collapse
qq3a.200605.001
just to thank you a lot bigbiff for putting so much work and efforts on this, you are great. hope you can sort this out, best luck!! (a p3 user) :fingers-crossed::good: sorry for the ot
2WildFirE said:
qq3a.200605.001
Click to expand...
Click to collapse
There was an update to the platform version, please test https://build.twrp.me/test/flame/twrp-3.4.0-0-test1-flame.img
bigbiff said:
There was an update to the platform version, please test https://build.twrp.me/test/flame/twrp-3.4.0-0-test1-flame.img
Click to expand...
Click to collapse
Thanks will try :good:
@bigbiff
yeah decryption works fine now
@bigbiff
Sorry for dump questions, but if I want to backup, is it enough to backup super and data partition?