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.
Related
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
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?
This is for all variants of the Desire 601
From their site:
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG 2.7.1.0:
Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
Various bugfixes to backup and restore
Improvements to USB storage handling
Added a class to search for files to make finding the correct brightness file automatic in most cases
Various other bugfixes and tweaks
CHANGELOG for 2.7.0.0:
Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
Allow sideloading from /tmp on encrypted devices
Check for a crypto footer before asking for a password to prevent user confusion
Additional checks for validity to auto generated backup names
Text wrap in the console output
Proper caps lock support in the keyboard
Mouse support via USB OTG for devices with a broken digitizer
Improve scanning of storage locations for OpenRecoveryScript
Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
Update SuperSU to 1.93 and improve installation process
Added selinux contexts restoration to fix permissions
Load RTC offset on Qualcomm devices to fix the date/time in recovery
USB Mass Storage fixes Add SELinux support checking
Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
Add 4.4 decrypt support
Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
Various SELinux fixes and bug fixes
Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.
CHANGELOG for 2.6.3.0:
Proper backup and restore of SELinux contexts (thanks to Tassadar)
Pull in some ROM information for backup name generation
Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
Add 1200x1920 theme (thanks to Tassadar)
A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
Initial support for f2fs file system formatting (Moto X)
Update SuperSU install for 4.3 ROMs
Fixed a permissions bug on files created during backup
Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
Ignore lost+found folder during backup and size calculations
Various other minor bug fixes and tweaks
NOTES:
This is the official version of TWRP for our device only modified with the updated partition mount points as changed by the KitKat OTA.
I have also modified it to display the version "v2.7.1.1 (KK)" to visibly distinguish it from the 2.7.1.0 official version.
This is only for Desire 601 users who have updated to KitKat or, at the very least, attempted the update and had their partitions remapped. If you have not updated to KitKat using the OTA you need to use the original version which can be found on their website here.
This is for all variants - zara_cl and zara_ul
DOWNLOAD:
Two links are available for you to download from:
1) My Google Drive
2) Dev-Host
BUGS:
-The only bug I have found so far is when you select Advanced Wipe from the Wipe screen you will see Data listed twice. The second data is actually Internal Storage, so use caution when wiping your device.
This Recovery is only for KitKat right?
So If I'm still on JB I mustn't flash this right? but how if one day the Insertcoin KitKat released and I want to use it, should I flash the Recovery first or the ROM first?
Akishima said:
This Recovery is only for KitKat right?
So If I'm still on JB I mustn't flash this right? but how if one day the Insertcoin KitKat released and I want to use it, should I flash the Recovery first or the ROM first?
Click to expand...
Click to collapse
This is only for people who have updated to KitKat because it remaps the relevant partitions during the update process.
If you haven't done the update, your partitions haven't been remapped and therefore the official version will work just fine for you.
-Duir- said:
This is only for people who have updated to KitKat because it remaps the relevant partitions during the update process.
If you haven't done the update, your partitions haven't been remapped and therefore the official version will work just fine for you.
Click to expand...
Click to collapse
On KitKat from other means(backup restore) this is for me then right?
Kolma said:
On KitKat from other means(backup restore) this is for me then right?
Click to expand...
Click to collapse
I know you tried the OTA, so If your partitions got remapped then yes, if not then no.
i want to install this recovery i have untouched(locked) ZARA_UL(unlocked to all carrier) phone but S-OFF'd when i bought it...so can i simply install this recovery???????? without unlocking bootloader ....and plz guide me how to do it..........
rajat836 said:
i want to install this recovery i have untouched(locked) ZARA_UL(unlocked to all carrier) phone but S-OFF'd when i bought it...so can i simply install this recovery???????? without unlocking bootloader ....and plz guide me how to do it..........
Click to expand...
Click to collapse
U cant install recovery with a locked bootloader
rajat836 said:
i want to install this recovery i have untouched(locked) ZARA_UL(unlocked to all carrier) phone but S-OFF'd when i bought it...so can i simply install this recovery???????? without unlocking bootloader ....and plz guide me how to do it..........
Click to expand...
Click to collapse
Child's Play said:
U cant install recovery with a locked bootloader
Click to expand...
Click to collapse
The recovery image in it's current state requires an unlocked bootloader. However, being S-OFF you can make a special zip file that allows the bootloader to flash it directly with out being unlocked.
-Duir- said:
The recovery image in it's current state requires an unlocked bootloader. However, being S-OFF you can make a special zip file that allows the bootloader to flash it directly with out being unlocked.
Click to expand...
Click to collapse
sir plz help me to s-on my device then i will unlock bootloader by myself through htcdev(((((((i dont want s-off its risky i think and.... i can install custom rom,recovery,kernel with just unlocked bootloader???)))) .......
Hint
Code:
fastboot flash recovery openrecovery-twrp-2.7.1.1-zaracl.img
@-Duir- is there any update for TWRP recovery (kitkat)?
they already release the 2.8 version for Zara but I don't know whether it's for kitkat or JB
Akishima said:
@-Duir- is there any update for TWRP recovery (kitkat)?
they already release the 2.8 version for Zara but I don't know whether it's for kitkat or JB
Click to expand...
Click to collapse
Official is still for JB. I have a modified KK version ready to go, I just need to check two things to see if they're issues with the official version or somehow created by modifying it.
I will also likely make a new thread when I upload it so that it will show up via devdb.
EDIT: New version posted in a new devdb thread. Though accidently in the wrong sub-section.
I'm hoping it can be moved, if so it will be moved to this section, also I will be requesting this thread removed.
Moderator Information
Thread has been closed at OP's request
Many thanks,
Ghost
Code:
*** Disclaimer
I/XDA am/is not responsible for any kind of damage to your device,
or in case it explodes, your surroundings.
Please use it at your own risk!
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
Bugs :
1. Reboot->Recovery doesn't work as required. Reboots to system instead.
Please do report any, if found.
Click to expand...
Click to collapse
Download :
Recovery-TWRP_2.8.3.0u1-NK.zip
Installation :
A. With custom recovery already installed :
1. Download zip
2. Reboot to recovery
2. Install zip in recovery
3. Reboot to recovery
B. With stock recovery (Root required) :
1. Download zip & extract recovery.img
2. Move recovery.img to root of external storage
3. Open Terminal
4. (If using terminal on PC) Execute :
Code:
adb shell
5. Execute the following commands :
Code:
su
dd if=/sdcard/recovery.img of=/dev/recovery
exit
C. Through SP flash tools :
1. Install drivers for your phone using Micromax drivers.
2. Extract the Stock ROM folder and replace recovery.img with recovery.img from zip.
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 of your phone.
5.Check only Recovery, 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.
Sources :
Recovery : https://github.com/omnirom/android_bootable_recovery
Kernel : https://github.com/neomanu/NeoKernel-MT6589-A116
Device : https://github.com/neomanu/android_device_micromax_a116-twrp
Credits :
@suhas.holla (for original device tree)
NO PORT REQUESTS
NO QUOTING THE WHOLE OP
You will be reported!
XDA:DevDB Information
TWRP 2.8.3.0, Tool/Utility for the Micromax A116
Contributors
neomanu
Version Information
Status: Stable
Current Stable Version: 2.8.3.0u1
Stable Release Date: 2014-12-26
Created 2014-12-22
Last Updated 2014-12-29
Reserved
Changelog :
2.8.3.0u1 :
- Added F2FS tools. Can be used to format filesystems to F2FS.
- Removed SuperSU (to fit into partition)
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
2.8.2.0 :
-Pull in all changes from Android 5.0 lollipop into TWRP
-Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
-Revert some changes to exFAT that were breaking exFAT support on some devices
-Other minor fixes and updates
Note: At this time we do not have a GUI representation for pattern unlock. You can still decrypt patterns though by translating the pattern dots to numbers. The pattern dots correspond to numbers in the following pattern:
1 2 3
4 5 6
7 8 9
So an upper-case L would translate to a password of 14789 entered on the keyboard. Eventually we plan to add a proper pattern unlock to TWRP but it is a relatively low priority at this point.
Also note that you will need the latest adb binaries on your computer to sideload with this new version of TWRP.
2.8.1.0 :
- MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
- TrueType Font support - optional as it takes up a decent amount of space so may not be available on all devices - thanks to Tassadar
- Temperature support - thanks to bigbiff
- Various other bugfixes and tweaks
2.8.0.1 :
- Fix a bug that caused weird graphics and touch issues
2.8.0.0 :
- Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
- Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
- Add support for color in the console and give error, warning, and highlight lines different colors
- Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
- Improve handling of /misc thanks to mdmower
- Improve setting of time on Qualcomm devices thanks to [NUT]
- Allow using images on slidervalue GUI objects thanks to Tassadar
- Allow using variables and addition and subtraction in variables for easier theming
- Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
- Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
- Other minor fixes and improvements
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
2.7.1.0 :
- Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
- Various bugfixes to backup and restore
- Improvements to USB storage handling
- Added a class to search for files to make finding the correct brightness file automatic in most cases
- Various other bugfixes and tweaks
Reserved
Awsome work bro.. :thumbup::thumbup:
Thank you so much.. Downloading
good work bro!!:good::good:
thanks for compiling this !!
Can we use this to flash Android 5.0.1 by kashifmin ?? !!
and anyway to solve reboot --> recovery problem ! ?
Awsome work once again MAN!!!!! Really, very greatful to you.... Just one more request to you...... Can you just compile a new kernel for our device from this Source (a tweaked kernel) so that we can have it on cm11.... because the kernel used in cm for now is not tweaked and a bit poor performance... i would have done that work but busy with my exams... so if you can please .. or i would be back within few weeks....
Once AGAIN , NICE WORK!! Keep it UP!!
Regards
Andy
can I flash this recovery... ?? currently I'm using AOSB ROM...
Sent from my Canvas HD
vaas kr said:
can I flash this recovery... ?? currently I'm using AOSB ROM...
Sent from my Canvas HD
Click to expand...
Click to collapse
Sure... you can with mobileuncle tools... (AND RECOVERY(S) ARE MEANT FOR FLASHING )
Regards
Andy
neomanu said:
Code:
*** Disclaimer
I/XDA am/is not responsible for any kind of damage to your device,
or in case it explodes, your surroundings.
Please use it at your own risk!
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
Bugs :
Download :
Recovery-TWRP_2.8.3.0u1-NK.zip
Installation :
A. With custom recovery already installed :
1. Download zip
2. Reboot to recovery
2. Install zip in recovery
3. Reboot to recovery
B. With stock recovery (Root required) :
1. Download zip & extract recovery.img
2. Move recovery.img to root of external storage
3. Open Terminal
4. (If using terminal on PC) Execute :
Code:
adb shell
5. Execute the following commands :
Code:
su
dd if=/sdcard/recovery.img of=/dev/recovery
exit
C. Through SP flash tools :
1. Install drivers for your phone using Micromax drivers.
2. Extract the Stock ROM folder and replace recovery.img with recovery.img from zip.
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 of your phone.
5.Check only Recovery, 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.
Sources :
Recovery : https://github.com/omnirom/android_bootable_recovery
Kernel : https://github.com/neomanu/NeoKernel-MT6589-A116
Device : --to be updated--
Credits :
@suhas.holla (for original device tree)
XDA:DevDB Information
TWRP 2.8.3.0, Tool/Utility for the Micromax A116
Contributors
neomanu
Version Information
Status: Stable
Current Stable Version: 2.8.3.0u1
Stable Release Date: 2014-12-26
Created 2014-12-22
Last Updated 2014-12-26
Click to expand...
Click to collapse
I have flashed twrp recovery 2.7.00 already.. Do i need to flash it ..?
Sent from my Micromax A116
jam884 said:
I have flashed twrp recovery 2.7.00 already.. Do i need to flash it ..?
Sent from my Micromax A116
Click to expand...
Click to collapse
No, you don't.
And everyone, please refrain from quoting the whole OP, and specially no port requests.
Both will be reported immediately.
jam884 said:
I have flashed twrp recovery 2.7.00 already.. Do i need to flash it ..?....
Click to expand...
Click to collapse
neomanu said:
No, you don't. .....
Click to expand...
Click to collapse
you mean there's no tangible benefit of using v2.8.3.0u1 if one's already running v2.7.0.0?
m0han said:
you mean there's no tangible benefit of using v2.8.3.0u1 if one's already running v2.7.0.0?
Click to expand...
Click to collapse
I'm saying that if someone is going to ask such questions after such a lengthy changelog has been posted, they might as well not.
neomanu said:
I'm saying that if someone is going to ask such questions after such a lengthy changelog has been posted, they might as well not.
Click to expand...
Click to collapse
your twrp v2.8.3.0u1 seems to work ok :good:.backup got saved in /emmc/TWRP/BACKUPS/Canvas_HD. how about shortening that to A116?
on another note, i'd like to have the font you've used in your recovery, on twrp v2.8.2.0 for xolo q3000. can you help in any way? thanks.
m0han said:
on another note, i'd like to have the font you've used in your recovery, on twrp v2.8.2.0 for xolo q3000. can you help in any way? thanks.
Click to expand...
Click to collapse
The font used is the new default in TWRP, from v2.8.1.0.
Refer to this commit.
All you need to do is to unpack the ramdisk, add RobotoCondensed-Regular.ttf to /res/fonts/ and change the following in /res/ui.xml according to the required resolution.
Repack and you have the font.
neomanu said:
No, you don't.
And everyone, please refrain from quoting the whole OP, and specially no port requests.
Both will be reported immediately.
Click to expand...
Click to collapse
In my twrp 2.7.0.0 it shows wipe option with dalvik,cache,factory reset..in single swipe.. What should i do to separate them..
Sent from my Micromax A116
jam884 said:
....What should i do to separate them....
Click to expand...
Click to collapse
try clicking advanced wipe and choosing what you need....
m0han said:
try clicking advanced wipe and choosing what you need....
Click to expand...
Click to collapse
Thanx a lot friend...
Sent from my Micromax A116
@neomanu
Thanks for TWRP_2.8.3.0
I have one issue some time stuck when flash zip on TWRP_2.8.3.0u1-NK
When flash same zip in preview recovery (TWRP 2.8.0.0 hyperion70) it work fine
any news on an update to fix the boot to recovery option ??
[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?