[RECOVERY][mt2l03] TWRP 2.8.0.0 touch recovery [2014-10-21] - Huawei Ascend Mate 2

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.8.0.0:
-Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
-Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
-Add support for color in the console and give error, warning, and highlight lines different colors
-Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
-Improve handling of /misc thanks to mdmower
-Improve setting of time on Qualcomm devices thanks to [NUT]
-Allow using images on slidervalue GUI objects thanks to Tassadar
-Allow using variables and addition and subtraction in variables for easier theming
-Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
-Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
-Other minor fixes and improvements
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
CHANGELOG for 2.7.1.0:
-Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
-Various bugfixes to backup and restore
-Improvements to USB storage handling
-Added a class to search for files to make finding the correct brightness file automatic in most cases
-Various other bugfixes and tweaks
CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes
Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.
DOWNLOAD:
Most devices can be updated quickly and easily with the TWRP Manager app:
Play Store Link
1) Install TWRP Manager from the Play Store
2) Open TWRP Manager and provide root permissions
3) Hit Advanced->Install Recovery
4) Verify the correct device name on your screen then press Install Recovery if the correct device is showing
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.

Device specific page with install instructions and download links for all current and past versions.
Note: You must be bootloader unlocked to use TWRP.
I realize that someone else already posted TWRP for this device, but this thread means that the Ascend Mate 2 has official support from Team Win and will be included in future updates.
I am having a few issues with MTP and USB Storage modes. We'll try to get those sorted out. I think it's somewhat kernel related.

Dees_Troy said:
Device specific page with install instructions and download links for all current and past versions.
Note: You must be bootloader unlocked to use TWRP.
I realize that someone else already posted TWRP for this device, but this thread means that the Ascend Mate 2 has official support from Team Win and will be included in future updates.
I am having a few issues with MTP and USB Storage modes. We'll try to get those sorted out. I think it's somewhat kernel related.
Click to expand...
Click to collapse
hey Awesome
thanks a lot .. 
 @modding.MyMind is the one that made the much appreciated alternative but an official channel is very much appreciated indeed

gierso said:
@modding.MyMind is the one that made the much appreciated alternative but an official channel is very much appreciated indeed
Click to expand...
Click to collapse
Yes, thanks to all. (Timestamp on backups appear accurate now. )

Dees_Troy said:
DOWNLOAD:
Most devices can be updated quickly and easily with the TWRP Manager app:
Play Store Link
1) Install TWRP Manager from the Play Store
2) Open TWRP Manager and provide root permissions
3) Hit Advanced->Install Recovery
4) Verify the correct device name on your screen then press Install Recovery if the correct device is showing
OR:
You can find more information and download links on our website!
Click to expand...
Click to collapse
FYI, The TWRP Manager app doesn't have an "advanced" option in settings and MT2L03 isn't in the device name list yet so the program doesn't work to install the image. Installing via ADB works fine though. I'm sure it's just a matter of updating the app on the Play Store until it does list it though Many thanks for the official support! Even off-mode charging works! Very cool
One question: Are the backups that were created with the unofficial version of TWRP still compatible with this version if I want to restore a backup created in the other twrp with this one will it work?

arcadesdude said:
FYI, The TWRP Manager app doesn't have an "advanced" option in settings and MT2L03 isn't in the device name list yet so the program doesn't work to install the image. Installing via ADB works fine though. I'm sure it's just a matter of updating the app on the Play Store until it does list it though Many thanks for the official support! Even off-mode charging works! Very cool
One question: Are the backups that were created with the unofficial version of TWRP still compatible with this version if I want to restore a backup created in the other twrp with this one will it work?
Click to expand...
Click to collapse
Flashify works very well though. You don't need a computer or ADB after the bootloader is unlocked.
Sent from my MT2L03

What's the difference between this and http://forum.xda-developers.com/asc.../2014-09-22-teamwin-recovery-project-t2885144 ???

unofficial made before the official one got thru
15 devs got mt2l03s at the big android BBQ

So they are the same thing? Or do we need to flash this new one? And how do we get rid of the old one if we do? Sorry too many questions I'm a noob.
Sent from my MT2L03

hope there would be one for mt02-l01/2 too.

Dees_Troy said:
Device specific page with install instructions and download links for all current and past versions.
Note: You must be bootloader unlocked to use TWRP.
I realize that someone else already posted TWRP for this device, but this thread means that the Ascend Mate 2 has official support from Team Win and will be included in future updates.
I am having a few issues with MTP and USB Storage modes. We'll try to get those sorted out. I think it's somewhat kernel related.
Click to expand...
Click to collapse
Thanks for support the device into official TWRP build.
I just submitted an issue regarding the adb, hopefully the working adb can make the MTP/Storage troubleshooting easier.
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/305
EDIT: 2015/01/17, please dis-regards above issue, today, I tested again the adb actually works fine.
Thanks again
xordos.

xordos said:
Thanks for support the device into official TWRP build.
I just submitted an issue regarding the adb, hopefully the working adb can make the MTP/Storage troubleshooting easier.
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/305
Thanks again
xordos.
Click to expand...
Click to collapse
You are a life saver!!! I already did thank you so I will thank you again. I also used google drive so that really helps. I cannot save my backup to my external SD drive. Hope that will be solved in the near future.

husky55 said:
You are a life saver!!! I already did thank you so I will thank you again. I also used google drive so that really helps. I cannot save my backup to my external SD drive. Hope that will be solved in the near future.
Click to expand...
Click to collapse
There are 2 different twrp build/thread in this forum, so please be clear which one you are using. And actually both version support save backup to external sd.
The adb/mtp issue i mentioned above is related to PC connection. The twrp main functions are fully working already

xordos said:
There are 2 different twrp build/thread in this forum, so please be clear which one you are using. And actually both version support save backup to external sd.
The adb/mtp issue i mentioned above is related to PC connection. The twrp main functions are fully working already
Click to expand...
Click to collapse
I used the TWRP manager to install. However when it downloaded and installed it crashed. Something about if this is the folder in your HAM2, yes or no, when clicked no it exited, clicked yes and it crashed. So I rebooted the phone into recovery and lo and behold, TWRP is there for the very first time. I had no idea what version that is.
Prior to all this I used the TWRP installer from the Play Store. It installed some version of TWRP but when rebooted into recovery, it was the Android recovery which showed up and allowed no backup at all. I also have the ROM manager installed. That installed some version of TWRP also.
I spent lots of time trying to backup to my 32GB external SD but I do not see it as an option. I used TWRP before on my Samsung S3 so I am somewhat familiar with it and CWM. I was able to make a copy of the backup file into the external SD using ES file manager. Not sure I can restore from it. I really like to save the internal memory for other things.
I am tempted to flash the twrp.img version 2.8 from your google drive again but I am not sure how it's going to workout.
One last note, I read both threads you referred to and lots more. But for some reason I have a hell of a time for something so simple.

husky55 said:
I used the TWRP manager to install. However when it downloaded and installed it crashed. Something about if this is the folder in your HAM2, yes or no, when clicked no it exited, clicked yes and it crashed. So I rebooted the phone into recovery and lo and behold, TWRP is there for the very first time. I had no idea what version that is.
Prior to all this I used the TWRP installer from the Play Store. It installed some version of TWRP but when rebooted into recovery, it was the Android recovery which showed up and allowed no backup at all. I also have the ROM manager installed. That installed some version of TWRP also.
I spent lots of time trying to backup to my 32GB external SD but I do not see it as an option. I used TWRP before on my Samsung S3 so I am somewhat familiar with it and CWM. I was able to make a copy of the backup file into the external SD using ES file manager. Not sure I can restore from it. I really like to save the internal memory for other things.
I am tempted to flash the twrp.img version 2.8 from your google drive again but I am not sure how it's going to workout.
One last note, I read both threads you referred to and lots more. But for some reason I have a hell of a time for something so simple.
Click to expand...
Click to collapse
OK...Got you. So, I would suggest use the "fastboot flash recovery" command in ModdingMyMind thread, both image file can be used, but I prefer the fastboot way, so we can see what's the output.
Some people has issue re-install TWRP after upgrade to B148, that's why I refer you to
yeah, I forgot that, after update, twrp install may have issues, check this thread around post 169:
http://forum.xda-developers.com/show....php?t=2897452
Click to expand...
Click to collapse
which pretty much says this:
Originally Posted by Kid_Ding View Post
For anyone having issues flashing TWRP after udpate, boot into stock recovery and install update from external SD. The path is above. Then reboot and then reboot to bootloader and flash twrp. Thank @foltz61
Click to expand...
Click to collapse
So, basically you need re-install the B148 update using above particular method, then afterwards, re-flash the TWRP.
We can continue discuss in the other thread.
Cheers.

I installed the TWRP.img latest release from the TWRP web site using ADB fastboot. The file is 14.300 kb in size. TWRP is working properly. I made a recovery backup and restored it. I also had Xposed Installed and some modules installed. When the HAM2 is on and charging everything is normal. i.e working properly.
The problem is when the HAM2 is off and charging, suddenly TWRP started. I got the slide to Unlock from TWRP. There was nothing that I could pinpoint on that would cause this. I installed Boot Manager but it did not show TWRP as being a application which should or will start at boot up.
I know this is a minor annoyance but being trained technically it bothers me. Is there anything I can do to prevent TWRP from starting when plugging in the micro usb connector to a HAM2 in the shut down state.

yes, this is a known issue about off mode charging. we have v2 fixed it (it is in the google drive i shared) but we never release it. because the official twrp team build released in this thread and it works fine.

So now that school is over (for now), I finally downloaded this installer and the correct recovery for the phone, and now it is asking me this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is it just asking me to verify that the path exists?

Sorry I installed twrp so long ago I don't remember. Are you sure you got the 2.8.0 for the right version? The 2.8.1 is for the 05's and not the USA 03's.

oncouch1 said:
Sorry I installed twrp so long ago I don't remember. Are you sure you got the 2.8.0 for the right version? The 2.8.1 is for the 05's and not the USA 03's.
Click to expand...
Click to collapse
There are 2 versions available for the MT2L03: 2.8.0 and 2.8.3. Both give me that same warning message. Can anyone help?

Related

[RECOVERY][i9300] TWRP 2.8.6.0 touch recovery [2015-03-26]

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.8.6.0:
-Fix daylight savings time rules for USA and Europe (_that)
-Allow mulitple overlays for popup boxes (Dees_Troy)
-Add pattern style password entry for decrypt (Tassadar)
-Keyboard improvements (_that)
-Update AOSP base to 5.1 (Dees_Troy)
-Reduce theme count to 5 and rely on scaling (Dees_Troy)
-Various scaling improvements (Dees_Troy)
-Improved handling of resources in the GUI (_that)
-Make scroll bar size proportional to list size (_that)
-Allow scoll lists to render without a header (_that)
-Make console scroll per pixel with kinetic scrolling (_that)
-Support styles in XML to reduce XML size and improve consistentcy (Dees_Troy)
-Various other fixes and improvements (mdmower, bigbiff, codelover, etc)
CHANGELOG for 2.8.5.0:
-Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
-Backups can now be cancelled while the backup is in progress (does not include restore because we don't want to leave your device in a bad state)
-Improve thread handling and move input handling into the main rendering thread to improve stability
-Make MTP work even if unplugged and plugged back in
-Unify scrollable list code and make kinetic scrolling feel more natural
-Fix handling of mapped zip files for OTA updates (CM12 updater)
-USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
-Other small fixes and improvements
CHANGELOG for 2.8.4.0:
-Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
-Fix some MTP related crashes and bugs
-Eliminate TWRP toggling USB IDs during boot if MTP is enabled
-Fix various adb sideload issues
-Improve threading of actions
-Eliminate separate thread for screen timeout
-Update libblkid to 2.25.0
-Use power button as back button on watch themes for easier navigation
-Add mutex locking to data manager
-Improve custom theme handling on encrypted devices
-Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
CHANGELOG for 2.8.3.0:
-MTP will now tell the host PC that storage is removed instead of disabling MTP completely
-MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
-Update and improve fix permissions and make fixing contexts optional
-Update SuperSU in TWRP to 2.40 and update install process
-Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
-Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
-Fix kernel panic during MTP start on some devices
-Support unicode fonts on devices with True Type Font support
-Fix slider value not showing sometimes (vibration settings page)
-Toggle MTP off during adb sideload to set correct USB IDs
-Reduce library requirements for 5.0 L decrypt
-Other minor fixes and improvements
Note: Starting with TWRP 2.8.2.0 and higher, adb sideload uses a new sideload method originally implemented in AOSP recovery. You will need the latest adb binaries to use sideload in these newer versions of TWRP. The version required is 1.0.32. You can find the version by running "adb version" on your computer. The new sideload feature no longer stores the zip on your device. Instead, a fuse file system is created in RAM and the zip is streamed from your computer. This puts less wear and tear on storage and ensures that large zips will not fill up all of your RAM. The sideload may spit an error on your PC side, but the zip should install just fine on your device.
DOWNLOAD:
Most devices can be updated quickly and easily with the TWRP Manager app:
Play Store Link
1) Install TWRP Manager from the Play Store
2) Open TWRP Manager and provide root permissions
3) Hit Advanced->Install Recovery
4) Verify the correct device name on your screen then press Install Recovery if the correct device is showing
OR:
You can find more information and download links on our NEW website! NOTE that the 2.8.6.0 version is ONLY available on our new site and is not available on our other, older mirrors!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Can i install it ontop of the current recovery i have ? ( CWM )
EDIT:
twrp in GooManager is 2.3.0 not 2.3.1.
you can - go on!
Dark_Lord0122 said:
Can i install it ontop of the current recovery i have ? ( CWM )
EDIT:
twrp in GooManager is 2.3.0 not 2.3.1.
Click to expand...
Click to collapse
Yes.
Last version is on their website.
Striatum_bdr said:
Yes.
Last version is on their website.
Click to expand...
Click to collapse
...and .img file is in wrong folder (odin version). Had to chenge it before flash.
Does this also support the external SD?
BackfireNL said:
Does this also support the external SD?
Click to expand...
Click to collapse
Yes
lulonen said:
...and .img file is in wrong folder (odin version). Had to chenge it before flash.
Click to expand...
Click to collapse
what version i can download?
thanks
BackfireNL said:
Does this also support the external SD?
Click to expand...
Click to collapse
It doesn't recognise mine. 64gb Sandisk on international galaxy s3. Formatted in the phone.
zigson said:
It doesn't recognise mine. 64gb Sandisk on international galaxy s3. Formatted in the phone.
Click to expand...
Click to collapse
You'll have to reformat to FAT32. Most 64GB cards get formatted to exFAT which doesn't (and probably never will) have support in the Linux kernel.
Just installed with GooManager.
Checking out the user interface, first impression is very good.
Now backing up my phone (all options incl efs).
Tomorrow i will restore my phone from this backup.
Wil report if any bugs come up.
Regards,
HELP!!!!
@ Dees Troy. just wanted to say thank you to you and your team for the awesome recovery for our i9300's. I installed the new 2.3.1 today and like the v.2.3.0 when i have tried installing some zips i get failed in red letters. I know that i could just restore back to previous backup i did right before i attempted flashing the update on my rom but i'm new to twrp and i would like to see if you could help me. when attempting this i have zip file sig. verification and force md5 check on all zips checked off. when i swipe to confirm flash. when it fails it says to disable the md5 check to avoid this error. i uncheck it and swipe again. then it says sig. verification failed error flashing zip. i know the zip file is good so what is the issue here. i'm flashing from ext. card and i have cleared cache, dalvic, system wipe, and reset. a little help would be awesome so i could figure this out. Thanks in advance.:good:
Subscribed.. thank you.
Sent from my GT-I9300 using xda premium
When trying to install via http://teamw.in/project/twrp2/114 the md5 version it fails saying "<OSM> MD5 hash value is invalid".
So I downloaded the Goomanager but it installs version 2.3.0.0 and not 2.3.1.0.
Why is that?
I just wrote why fev posts ago. 2.3.1.0 is packed with folders inside. I flashesd it via odin after repacking .tar with success.
440hsp said:
@ Dees Troy. just wanted to say thank you to you and your team for the awesome recovery for our i9300's. I installed the new 2.3.1 today and like the v.2.3.0 when i have tried installing some zips i get failed in red letters. I know that i could just restore back to previous backup i did right before i attempted flashing the update on my rom but i'm new to twrp and i would like to see if you could help me. when attempting this i have zip file sig. verification and force md5 check on all zips checked off. when i swipe to confirm flash. when it fails it says to disable the md5 check to avoid this error. i uncheck it and swipe again. then it says sig. verification failed error flashing zip. i know the zip file is good so what is the issue here. i'm flashing from ext. card and i have cleared cache, dalvic, system wipe, and reset. a little help would be awesome so i could figure this out. Thanks in advance.:good:
Click to expand...
Click to collapse
http://teamw.in/VRThemes
http://teamw.in/project/twrp2 (what's new in 2.3.0.0 - update-binary)
i think there's no dual-boot options in this recovery, right?
for using with Siyah kernel i mean
thank
lulonen said:
I just wrote why fev posts ago. 2.3.1.0 is packed with folders inside. I flashesd it via odin after repacking .tar with success.
Click to expand...
Click to collapse
Can you upload a tar file so I can install it via the recovery?
I can not update through goo manager either.
Only has previous version.
This is strange. On my Nexus 7 I was able to upgrage TWRP via Goomanager but not on my Galaxy S3.

[RECOVERY][dlx] TWRP 3.0.0-0 touch recovery [2016-02-06]

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our NEW website! NOTE that the 2.8.6.0 version is ONLY available on our new site and is not available on our other, older mirrors!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Dees_Troy said:
Thanks to Dr_Drache for testing for me!
Team Win Recovery Project 2.3, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.3.2.0:
-Fixes / enhancements to handle the multiple user setup introduced by Android 4.2 (see notes)
-Fixed a bug with deleting a backup with a space in the name
-Added highlights on keyboard key presses
CHANGELOG for 2.3.1.0:
-Unmount system after boot to prevent some status 7 symlink failed errors on zip install
-USB Mass Storage code improvements
-Better handling of mounting storage during boot for some devices
-Fixed a problem with sizes of images (boot & recovery) after resetting defaults
-Fixed size errors during backup for some devices on recovery, etc.
-Fixed a problem with restoring backups when multiple archives were present
CHANGELOG for 2.3.0.0:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
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 30 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Click to expand...
Click to collapse
Sweet thanks.
Sent from my CM9 HTC Thunderbolt from Tapatalk 2.4
Note, I forgot to have Dr_Drache test off-mode charging. Can someone install this, turn the device completely off, then plug it into a charger. The charge light should come on, maybe blink once or twice, but after about 2 minutes, the charge light should stay on without blinking anymore. Please let me know!
jonah1234 said:
Sweet thanks.
Sent from my CM9 HTC Thunderbolt from Tapatalk 2.4
Click to expand...
Click to collapse
THANK YOU
Dees_Troy said:
Note, I forgot to have Dr_Drache test off-mode charging. Can someone install this, turn the device completely off, then plug it into a charger. The charge light should come on, maybe blink once or twice, but after about 2 minutes, the charge light should stay on without blinking anymore. Please let me know!
Click to expand...
Click to collapse
Off mode charging is fine
Sent from my ADR6425LVW using Tapatalk 2
vinylfreak89 said:
Off mode charging is fine
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Good deal, thanks for checking it and confirming.
I've ran into some trouble with mine. I have created three backups, each with slight differences to system, trying some things out on the ROM. The lase edit was the build.prop. It wouldn't boot so I went to Recovery to restore one of my backups. When it is a good 10 seconds into restoring system, the progress bar stops turning and it reboots. Each time I try this it seems to stop at a slightly different point into the system restore. Most of the time it wont go far enough to allow boot, just the splash screen and then it automatically boots into TWRP.
All of that is ok, and I could get around it, but now my phone is dead! Any suggestions?
*Edit* Got it guys. I was able to use the USB charger from my TPrime and it charged in TWRP. After it charged a bit I was able to fastboot flash TWRP again and restore one of the backups. I'm not sure how it became corrupted, but its all good now!
When will the size be fixed?
Sent from my HTC Droid DNA
jonah1234 said:
When will the size be fixed?
Sent from my HTC Droid DNA
Click to expand...
Click to collapse
I don't have a DNA or any other 1080 * 1920 device that uses a portrait layout (no rotation in recovery). I am unable to do the upscale myself. There's a theme guide on our website if someone wants to to do it.
Dees_Troy said:
I don't have a DNA or any other 1080 * 1920 device that uses a portrait layout (no rotation in recovery). I am unable to do the upscale myself. There's a theme guide on our website if someone wants to to do it.
Click to expand...
Click to collapse
Alright I will give that a try later today.
Sent from my HTC Droid DNA
For some reason I can't make backups anymore. It gets about a quarter way, then reboots. I tried cwm..and same issue. Anyone have any ideas?
it has rebooted on me during a backup as well. i tried again and was successful, but there definitely seems to be a bug somewhere
Hello,
Definitely a bug, seems that after the first successful backup unit will no longer get past the system file.
UPDATE, your backups will complete if you do not change the name. Leave it as the date or default name If this does not work for you the only other thing I have done since it was rebooting was to install/update busybox. This may also work for those who are restoring backups and getting the reboot...did you change the file name? Whatever I am sure it is just a temp bug that will be fixed soon as well as the layout.
Cheers
Has anyone got a fix for the screen size yet?
starscream86 said:
Has anyone got a fix for the screen size yet?
Click to expand...
Click to collapse
I was looking into it ealier today. I haven't gotten it just yet tho.
Sent from my HTC Droid DNA
jschill31 said:
Hello,
Definitely a bug, seems that after the first successful backup unit will no longer get past the system file.
UPDATE, your backups will complete if you do not change the name. Leave it as the date or default name If this does not work for you the only other thing I have done since it was rebooting was to install/update busybox. This may also work for those who are restoring backups and getting the reboot...did you change the file name? Whatever I am sure it is just a temp bug that will be fixed soon as well as the layout.
Cheers
Click to expand...
Click to collapse
I have backups failing when not changing the name as well. Bug happens either way.
After several attempts I am eventually able to get a good backup, but it fails more often than it completes.
Deuces said:
I have backups failing when not changing the name as well. Bug happens either way.
After several attempts I am eventually able to get a good backup, but it fails more often than it completes.
Click to expand...
Click to collapse
Interesting, obviously this needs a bit of work. I have not tried to make another one, I have been spending time modding the factory shipped rom. There are so many features hidden by Verizon. Also there is something running in the background that eats our batteries. Hard to start cranking on a rom without a reliable recovery. I sent a note over on the TWRP website, hopefully someone will have some ideas. On the size issue has anyone tried using a TWRP skin from one of the 1080p tablets?
Cheers
Have you looked into using one of the 1080p tablet themes? I plan on doing that tonight.
Sent from my HTC6435LVW using Tapatalk 2
jschill31 said:
Have you looked into using one of the 1080p tablet themes? I plan on doing that tonight.
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
Any luck with that?
starscream86 said:
Any luck with that?
Click to expand...
Click to collapse
Hello,
Actually a big NO on that...this recovery isn't even recognizing the THEME folder? It seems this has a few bugs to iron out. I looked at pulling the resource the other day and building a new one but I can't seem to find a reliable git for the DNA? If anyone knows of one please let me know and I will pull the files late tonight. I am not a DEV by all means but have been building for multiple devices for over two years and have a smoking build machine. I am not comfortable working on any roms until we have a solid recovery. Don't get me wrong, this does backup after a few tries but what I am worried about is a fail when trying to restore. I have read where Clockwork it the same way, seems to have something to do with the partitions?
Cheers

[RECOVERY][2014-06-04] TWRP 2.7.1.0 Touch Recovery for KitKat Devices

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

[RECOVERY][ariel] TWRP 2.8.6.0 touch recovery [2015-06-07]

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.8.6.0:
Fix daylight savings time rules for USA and Europe (_that)
Allow mulitple overlays for popup boxes (Dees_Troy)
Add pattern style password entry for decrypt (Tassadar)
Keyboard improvements (_that)
Update AOSP base to 5.1 (Dees_Troy)
Reduce theme count to 5 and rely on scaling (Dees_Troy)
Various scaling improvements (Dees_Troy)
Improved handling of resources in the GUI (_that)
Make scroll bar size proportional to list size (_that)
Allow scoll lists to render without a header (_that)
Make console scroll per pixel with kinetic scrolling (_that)
Support styles in XML to reduce XML size and improve consistentcy (Dees_Troy)
Various other fixes and improvements (mdmower, bigbiff, codelover, etc)
CHANGELOG for 2.8.5.0:
Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
Backups can now be cancelled while the backup is in progress (does not include restore because we don't want to leave your device in a bad state)
Improve thread handling and move input handling into the main rendering thread to improve stability
Make MTP work even if unplugged and plugged back in
Unify scrollable list code and make kinetic scrolling feel more natural
Fix handling of mapped zip files for OTA updates (CM12 updater)
USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
Other small fixes and improvements
CHANGELOG for 2.8.4.0:
Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
Fix some MTP related crashes and bugs
Eliminate TWRP toggling USB IDs during boot if MTP is enabled
Fix various adb sideload issues
Improve threading of actions
Eliminate separate thread for screen timeout
Update libblkid to 2.25.0
Use power button as back button on watch themes for easier navigation
Add mutex locking to data manager
Improve custom theme handling on encrypted devices
Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
CHANGELOG for 2.8.3.0:
MTP will now tell the host PC that storage is removed instead of disabling MTP completely
MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
Update and improve fix permissions and make fixing contexts optional
Update SuperSU in TWRP to 2.40 and update install process
Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
Fix kernel panic during MTP start on some devices
Support unicode fonts on devices with True Type Font support
Fix slider value not showing sometimes (vibration settings page)
Toggle MTP off during adb sideload to set correct USB IDs
Reduce library requirements for 5.0 L decrypt
Other minor fixes and improvements
Note: Starting with TWRP 2.8.2.0 and higher, adb sideload uses a new sideload method originally implemented in AOSP recovery. You will need the latest adb binaries to use sideload in these newer versions of TWRP. The version required is 1.0.32. You can find the version by running "adb version" on your computer. The new sideload feature no longer stores the zip on your device. Instead, a fuse file system is created in RAM and the zip is streamed from your computer. This puts less wear and tear on storage and ensures that large zips will not fill up all of your RAM. The sideload may spit an error on your PC side, but the zip should install just fine on your device.
Everything seems to be working. No known issues. USB-OTG works also
Downloadhttps://www.androidfilehost.com/?fid=24052804347756852
or use our TWRP Manager software to install it automatically for you
Install either by DD or maybe flashify will work for you.
Code:
dd if=recovery.img of=/dev/block/mmcblk0p7
Thanks goes to @Dees_Troy as this was my first MediaTek based device to build recovery for
This will also be taken official this week.
Pulled download temporarily
Thanks for your work dude but we do not have recovery image for our Fire 6 HD sadly ...
alucard_xs said:
Thanks for your work dude but we do not have recovery image for ou Fire 6 HD sadly ...
Click to expand...
Click to collapse
The HD 7 and HD 6 are EXACTLY the same device. The OTAs for both are EXACTLY the same. The only difference is the screen size. There essentially is no difference betweent the 2 devices
Sure but what about factory / recovery image, is there anyone floating around ?
alucard_xs said:
Sure but what about factory / recovery image, is there anyone floating around ?
Click to expand...
Click to collapse
just dump your current recovery.img.
dd if=/dev/block/mmcblk0p7 of=/sdcard/stockrecovery.img
Then as soon as you boot into recovery make a backup.
Root
Will flashing the SuperSU package in recovery root, or cause a bootloop?
ryanyz10 said:
Will flashing the SuperSU package in recovery root, or cause a bootloop?
Click to expand...
Click to collapse
Dont need to flash anything with TWRP. If you boot twrp then choose reboot to system option it will ask if you want to install SuperSU.
Reuploaded fixed version. Found a couple bugs that i didn't notice before. All good now
So for us the slow ones, can you explain this in detail?
You've replaced the stock recovery with TWRP, so we can flash images from USB drives ? But you need root to do the first flash to recovery, correct?
Will Amazon update re-write the recovery partition so you are back to stock ?
bibikalka said:
So for us the slow ones, can you explain this in detail?
You've replaced the stock recovery with TWRP, so we can flash images from USB drives ? But you need root to do the first flash to recovery, correct?
Will Amazon update re-write the recovery partition so you are back to stock ?
Click to expand...
Click to collapse
yes. and future custom roms if they come. You should be disabling OTAs anyways. OTAs im pretty sure will fail anyways with a custom recovery
jmz said:
yes. and future custom roms if they come. You should be disabling OTAs anyways. OTAs im pretty sure will fail anyways with a custom recovery
Click to expand...
Click to collapse
Man, that's pretty awesome! It sounds like one just needs one good TWRP flash, and then it's not that hard to recover after a screw up via OTG.
And it seems like with this TWRP we should be able to flash Amazon updates onto the device (such as 4.5.4), and install root on top after that ? Root 4ever ? How hard is it to make TWRP flash stock Amazon updates ? I want 4.5.4 , with root !!!
You could also change the size of /cache, and add it to /data, or move dalvik cache from /data to /cache, see these allocations (there is 1 Gb of space in /cache !!!):
http://forum.xda-developers.com/fire-hd/help/internal-memory-structure-hidden-t3122246
So even without a custom ROM there are tons of easy tweaks that one could do.
I actually got to like the Fire OS, it is super stable for me. With custom recoveries things are often quite rocky for a while. I'd like to get some sort of Android Setup app, in order to change things above and beyond what Amazon allows (such as that Cyrillic AOSP keyboard!).
Once you figure out how to put stock Amazon update files onto the device plus root, you can pretty much play with Xposed and get into risky stuff (not being afraid of bootloop.) Just make sure to keep the trusty TWRP handy!!!
bibikalka said:
Man, that's pretty awesome! It sounds like one just needs one good TWRP flash, and then it's not that hard to recover after a screw up via OTG.
And it seems like with this TWRP we should be able to flash Amazon updates onto the device (such as 4.5.4), and install root on top after that ? Root 4ever ? How hard is it to make TWRP flash stock Amazon updates ? I want 4.5.4 , with root !!!
You could also change the size of /cache, and add it to /data, or move dalvik cache from /data to /cache, see these allocations (there is 1 Gb of space in /cache !!!):
http://forum.xda-developers.com/fire-hd/help/internal-memory-structure-hidden-t3122246
So even without a custom ROM there are tons of easy tweaks that one could do.
I actually got to like the Fire OS, it is super stable for me. With custom recoveries things are often quite rocky for a while. I'd like to get some sort of Android Setup app, in order to change things above and beyond what Amazon allows (such as that Cyrillic AOSP keyboard!).
Once you figure out how to put stock Amazon update files onto the device plus root, you can pretty much play with Xposed and get into risky stuff (not being afraid of bootloop.) Just make sure to keep the trusty TWRP handy!!!
Click to expand...
Click to collapse
Yeah, I am going to be working on the update this week. Starting a new job tomorrow.
Also, I added a link to our software TWRP Manager so it is even easier to install TWRP.
jmz said:
Yeah, I am going to be working on the update this week. Starting a new job tomorrow.
Also, I added a link to our software TWRP Manager so it is even easier to install TWRP.
Click to expand...
Click to collapse
I just saw your boot unlocker thread, you should better manage your cross-references Congrats for getting us this far!
But I wonder if one could just flash 4.5.4 first, and then unlock the bootloader, and install TWRP, then root. Which bootloader versions can be unlocked? All so far? So people who were force updated to 4.5.4 are not SOL ?
Of course, it's easier to just have TWRP flash Amazon updates, then root is always available. That would be an enabling step, with the ability to flash Amazon stock ROMs, one can mess things up totally, and still recover back.
Exciting times, man !!!!
bibikalka said:
I just saw your boot unlocker thread, you should better manage your cross-references Congrats for getting us this far!
But I wonder if one could just flash 4.5.4 first, and then unlock the bootloader, and install TWRP, then root. Which bootloader versions can be unlocked? All so far? So people who were force updated to 4.5.4 are not SOL ?
Of course, it's easier to just have TWRP flash Amazon updates, then root is always available. That would be an enabling step, with the ability to flash Amazon stock ROMs, one can mess things up totally, and still recover back.
Exciting times, man !!!!
Click to expand...
Click to collapse
Messing with things more and more I don't think that is a fully working bootloader unlock. For example, I can't boot an unsigned boot.img after flashing. But I can boot it if I flash to recovery partition then issue adb reboot recovery.
Or that may just be a MTK/Amazon/LK thing. Not too sure at this point. But it seems right now, custom kernels are out of the question.
jmz said:
Messing with things more and more I don't think that is a fully working bootloader unlock. For example, I can't boot an unsigned boot.img after flashing. But I can boot it if I flash to recovery partition then issue adb reboot recovery.
Or that may just be a MTK/Amazon/LK thing. Not too sure at this point. But it seems right now, custom kernels are out of the question.
Click to expand...
Click to collapse
I see what you mean ... Even a partial unlock is huge step forward in terms of customization options, and the biggest deal is that now it's not too scary to screw up! Btw, in Amazon update files there is recovery-from-boot.p, is that the image we need for recovery? Or should we make a proper one via dd?
In Amazon update they seem to update recovery, but I wonder who checks for signed boot.img ? Is this part of the chipset ?
(from /recovery/etc ):
#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery:5888256:6d9d1bbc4172c107db3228ed8d9f97111219c617; then
log -t recovery "Installing new recovery image"
applypatch -b /system/etc/recovery-resource.dat EMMC:/dev/block/platform/mtk-msdc.0/by-name/boot:5370112:c2c686ada1b194050a3c8f05e2102345df48e9ce EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery 6d9d1bbc4172c107db3228ed8d9f97111219c617 5888256 c2c686ada1b194050a3c8f05e2102345df48e9ce:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
bibikalka said:
I see what you mean ... Even a partial unlock is huge step forward in terms of customization options, and the biggest deal is that now it's not too scary to screw up! Btw, in Amazon update files there is recovery-from-boot.p, is that the image we need for recovery? Or should we make a proper one via dd?
In Amazon update they seem to update recovery, but I wonder who checks for signed boot.img ? Is this part of the chipset ?
(from /recovery/etc ):
#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery:5888256:6d9d1bbc4172c107db3228ed8d9f97111219c617; then
log -t recovery "Installing new recovery image"
applypatch -b /system/etc/recovery-resource.dat EMMC:/dev/block/platform/mtk-msdc.0/by-name/boot:5370112:c2c686ada1b194050a3c8f05e2102345df48e9ce EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery 6d9d1bbc4172c107db3228ed8d9f97111219c617 5888256 c2c686ada1b194050a3c8f05e2102345df48e9ce:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
Click to expand...
Click to collapse
all devices have that in some form or another.
I would make a dd backup of the stock one before flashing.
jmz said:
just dump your current recovery.img.
dd if=/dev/block/mmcblk0p7 of=/sdcard/stockrecovery.img
Then as soon as you boot into recovery make a backup.
Click to expand...
Click to collapse
Is there an option in TWRP Manager to save stock recovery without any reboots? This sounds like an easy feature to add. Or is this part of "live backup" ?
bibikalka said:
Is there an option in TWRP Manager to save stock recovery without any reboots? This sounds like an easy feature to add. Or is this part of "live backup" ?
Click to expand...
Click to collapse
No there isn't.
Well, I guess I am out of the game for awhile. Just bricked my Fire.

[ROM][Stock] Moto-Lite Stock Android 7.0 ROM for xt1575

Moto-Lite Stock Nougat ROM
Android 7.0 / NPHS25.200-23-1
Moto X Pure Edition XT1575
TWRP Flashable Installer
Rooted, Debloated, Optimized
•••••••••••••••••••••••••••••••••••••••••••••••••••••​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What's Moto-Lite?
Moto-Lite is an entirely stock-based Motorola ROM, with performance optimizations, systemless root, and some moderate debloating. This ROM is intended to give users a clean, slimmed down stock experience -- via a TWRP flashable installer.
_______________________________________
DISCLAIMER:
By proceeding further, you are assuming full responsibility for your device. Although this ROM has been thoroughly tested, I assume no liability in the event you damage your device or otherwise render it inoperable. Follow the simple instructions and things should go smoothly.
_______________________________________
BUILD INFO:
•Android Version: 7.0 Nougat
•Build No. NPHS25.200-23-1
•System Version: 25.211.1
•API Level: 24
•Build Date: October 30, 2017
•Security Patch Level: October 1, 2017
•Kernel Version: 3.10.84-perf
•Bootloader Version: AO.52
_______________________________________
FEATURES:
•Rooted with Magisk 20.4-Stable
•Static BusyBox Binaries: v1.31.1
•Moderately Debloated
•Safety Net Pass (ctsProfile/basicintegrity)
•Force Encrypt Disabled (Opt Encrypt)
•dm-verity/AVB 2.0 Disabled
•Custom Moto Boot Logo
•Optimized for RAM Efficiency
•su.d Support
•Fully Odexed per Stock Config
_______________________________________
Official Motorola Firmware for XT1575:
This firmware repo encompasses official firmware packages that originated from Motorola's servers. This link includes Android 5.1.1, Android 6.0 and Android 7.0-based firmware builds, including the NPHS25.200-23-1 build upon which this Moto-Lite ROM is based.
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
Kernel Source Code:
https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-NPH25.200-15
_______________________________________
PREREQUISITES:
Per the general rule of thumb, you will need an unlocked bootloader and a custom recovery such as TWRP. I recommend using the most current official TWRP build from here: https://dl.twrp.me/clark/
In order to circumvent force encryption during installation, you will need external storage such as a microSD card or an OTG USB storage device. (The /userdata partition must be formatted prior to installation; hence, all files and data stored on your device will be erased.) If you do not have, or do not wish to use, an external storage medium, alternative install instructions have been provided, for which you will need a PC or laptop computer and a good quality micro USB to USB syncing/charging cabke
NOTE: The below instructions assume that your device's firmware has been updated to the NPHS25.200-23 firmware build. It is also assumed that your device's modem/baseband version is M8992_1255331.29.01.88.09R SUPER_NA (the most current version).
_______________________________________
Instructions for installation are outlined under two separate headings: A. INSTRUCTIONS - STANDARD INSTALL, which apply to users who have an external micro SD card or an OTG supported external storage medium; and B. INSTRUCTIONS - NO EXTERNAL STORAGE, which should be used by those who do not have, or do not wish to use, a micro SD card or an OTG supported external storage device. For the latter you will need a laptop or computer and a good quality micro USB to USB syncing cable, for transferring the ROM zip file to your phone during the process
A. INSTRUCTIONS - STANDARD INSTALL:
1. Download the ROM zip from the below link and save it to external storage;
2. Boot your device into TWRP recovery mode;
3. On the TWRP home screen, select WIPE and choose the option to format data. Select WIPE again, then ADVANCED WIPE, and wipe System and Cache;
4. Select INSTALL, select the ROM zip, and commence installation;
5. Once the ROM is installed, the installation script will patch the stock boot image via Magisk v20.4-Stable to enable systemless root. BusyBox v1.31.1 static binaries will also be installed;
6. Reboot your system once the installer indicates finished. During the first boot, it is completely normal for a single boot loop to occur. This will not occur on subsequent boot-ups;
7. Once you complete initial device setup, open the Magisk Manager app and install any updates or any additional runtime steps that may be required. The app will display prompts for any necessary actions on your part;
8. Enjoy & profit...
B. INSTRUCTIONS - NO EXTERNAL STORAGE DEVICE
1. Download the ROM zip from the below link and save it to your computer;
2. Boot your device into TWRP recovery mode;
3. On the TWRP home screen, select WIPE and choose the option to format data. Select WIPE again, then ADVANCED WIPE, and wipe System and Cache;
4. Transfer the ROM.zip the file from its saved location on your computer to the now-formatted internal storage directory on your phone (via a micro USB to USB syncing/charging cable);
5. Reboot Recovery;
6. Select INSTALL, select the ROM zip, and commence installation ;
7. Reboot your system once the installer indicates finished. During the first boot, it is completely normal for a single boot loop to occur. This will not occur on subsequent boot-ups;
8. Once you complete initial device setup, open the Magisk Manager app and install any updates or any additional runtime steps that may be required. The app will display prompts for any necessary actions;
8. Enjoy & profit...
At the time I cooked up this ROM, the latest stable Magisk version was v20.4, so my systemless root installer encompassed within the ROM installer employs Magisk v20.4 stable. After installing the ROM, booting up and completing initial setup, open the Magisk Manager app to update Magisk to the most current version.
_______________________________________
THANK YOU:
Thanks to the amazing @osm0sis for his static BusyBox binary installer. And many thanks to @topjohnwu, the genius developer and creator of Magisk. Huge thanks to @pitflyer, who gave feedback and input on methods of install, and who revisited and outlined the steps for an alternative installation without using a micro SD or OTG supported storage device.
Thanks to @sd_shadow for his input and guidance on installation.
_______________________________________
BUGS:
Since this ROM is based entirely on an official Motorola stock firmware build, no significant bugs or instabilities should be expected. I have tested this ROM thoroughly after performing some optimizations (RAM, I/O Schedule tweaks. Entropy tweaks, etc.), moderate debloating and Magisk installation. I have noted no remarkable bugs, instabilities or performance flaws. However, please leave a comment in the event you discover flaws or bugs. I will look into the issue and try to resolve it. If possible, submit a bug report. Otherwise, list as much detail and specifics as possible regarding the issue.
_______________________________________
DOWNLOAD LINKS:
Moto-Lite XT1575 Android 7.0 ROM
**V2 updated ROM: Magisk v24.3, Busybox v1.34.1 static binaries, some additional debloating and some more RAM optimizations made on the kernel level.
V2 Moto-Lite xt1575 Android 7.0 ROM​
Been running this for a week or so. It's fine - love what you took out. An issue exists with moto voice. I cannot get past the setup as I cannot record my phrase. The continual response is that the environment in which I am recording is too loud. I live in the forest - I can hear dew evaporate(/s), it's not too loud .
I run Xposed with Gravity, removed google account after I set some apps up, freeze with SDMaid, block most net action with Afwall - only hiccup on the phone is moto voice, which, I can live without. Thanks for doing your thing.
bronkish said:
Been running this for a week or so. It's fine - love what you took out. An issue exists with moto voice. I cannot get past the setup as I cannot record my phrase. The continual response is that the environment in which I am recording is too loud. I live in the forest - I can hear dew evaporate(/s), it's not too loud .
I run Xposed with Gravity, removed google account after I set some apps up, freeze with SDMaid, block most net action with Afwall - only hiccup on the phone is moto voice, which, I can live without. Thanks for doing your thing.
Click to expand...
Click to collapse
Thanks for your input on this. I'll take a look at the Moto Voice service and see if I have debloated a system app or process that is Moto Voice dependent. Did you notice the Moto Voice issue before installing Xposed & GravityBox? Yeah I absolutely love SD Maid Pro. A great system-level tweaking tool with many uses.
Gravitybox, yessir. I typically get my dumps in order, reboot to twrp, wipe it all, flash a ROM, reboot, initial setup, dev mode and those settings, airplane mode, reboot, flash xposed, reboot, set up my phone. You know, if I do it that way.
Lol, I got no time to see if your kung-fu works right before I fuk it up with xposed. I can't answer the only and perfect question that you asked me. What's even more perfect than that failure is that I bought a g power the other day and haven't used my Xpure since last week. This g power has a burn't pixel though. WTF. I had it 8 days to replace the phone I used 5 years.....sigh.
THanks for responding, sorry I can't help you help me. Probably going to return the g power and use the x pure again and wait for a sweet-ass black-friday deal to replace it. There's a 7T on craigslist winking at me, though... I probably won't reset anything on the Xpure though, runs sweet. Hard phone to replace.
Edit - yeah - been using SD maid for years - love it, use the hsit out of it. ONly realized yesterday that I can dump apks of all installed apps at one go. It just keeps on giving.
Thank you for making this! I've been running for a week with no issues. Phone feels snappy. This is a great option to flash stock without going the ADB route. Cheers!!
mddunner said:
Thank you for making this! I've been running for a week with no issues. Phone feels snappy. This is a great option to flash stock without going the ADB route. Cheers!!
Click to expand...
Click to collapse
Thank you for your feedback and kind words. Glad to hear the ROM worked well on your device.
thank you works great and its rooted.
Another report this works great. For those like me who don't like to read the directions, if you copy the file to the internal storage as you would expect it gets wiped. If you don't have external storage, you can recopy the file in TWRP afterwards -- you just have to reboot recovery to see the files. After that all is well and this ROM is working great.
EDIT: I'm an idiot. I was trying to flash the kernel source zipfile, and not the actual system image...
pitflyer said:
Another report this works great. For those like me who don't like to read the directions, if you copy the file to the internal storage as you would expect it gets wiped. If you don't have external storage, you can recopy the file in TWRP afterwards -- you just have to reboot recovery to see the files. After that all is well and this ROM is working great.
Click to expand...
Click to collapse
Thanks for your feedback. In fact, you make a very valid point regarding external storage devices -- although the /userdata partition needs to be formated in order to disable force-encrypt, some device owners simply may not have external storage mediums or, like many users, may want to expedite the installation process. I will edit the instructions to include installation of the ROM from internal storage, for users who do not own, or have access to, an OTG based external.storage device.
Since you installed from intternal storage, and thus could not format the data partition prior to install, I am assuming your /userdata partition was force encrypted during the initial boot up. Please clarify on this. Thank you.
Hodgdon said:
EDIT: I'm an idiot. I was trying to flash the kernel source zipfile, and not the actual system image...
Click to expand...
Click to collapse
Happens to the best of us. Is the ROM working ok for you?
Viva La Android said:
Thanks for your feedback. In fact, you make a very valid point regarding external storage devices -- although the /userdata partition needs to be formated in order to disable force-encrypt, some device owners simply may not own an OTG based external storage device. I will edit the instructions to include installation of the ROM from internal storage, for users who do not own, or have access to, an OTG based external.storage device.
Since you installed from intternal storage, and thus could not format the data partition prior to install, I am assuming your /userdata partition was force encrypted during the initial boot up. Please clarify on this. Thank you.
Click to expand...
Click to collapse
I'm not sure what happened, I just know that after I realized formatting user data would delete the zip file, I copied the file through TWRP back to the now empty internal storage. TWRP still did not see it, so I rebooted recovery and then it saw it (which as you expect was the only file on internal storage). And it just worked...
I'm not using this phone heavily but it seemed to work fine afterwards and I definitely like having the 'stock' experience w/ root built in and the moderate debloat. Here are my edited steps that worked w/o external storage for me:
NEW: 1. Download the ROM zip from the below link and save it to <<computer>>
SAME: 2. Boot your device into TWRP recovery mode;
SAME: 3. On TWRP, select WIPE and choose the option to format data. Select WIPE again, then ADVANCED WIPE, and wipe System and Cache;
NEW: 4. Copy the file from <<computer>> to the now empty internal storage (via USB cable in TWRP recovery)
NEW: 5. Reboot Recovery
6. Select INSTALL, select the ROM zip, and commence installation -- the rest is the same
pitflyer said:
I'm not sure what happened, I just know that after I realized formatting user data would delete the zip file, I copied the file through TWRP back to the now empty internal storage. TWRP still did not see it, so I rebooted recovery and then it saw it (which as you expect was the only file on internal storage). And it just worked...
I'm not using this phone heavily but it seemed to work fine afterwards and I definitely like having the 'stock' experience w/ root built in and the moderate debloat. Here are my edited steps that worked w/o external storage for me:
NEW: 1. Download the ROM zip from the below link and save it to <<computer>>
SAME: 2. Boot your device into TWRP recovery mode;
SAME: 3. On TWRP, select WIPE and choose the option to format data. Select WIPE again, then ADVANCED WIPE, and wipe System and Cache;
NEW: 4. Copy the file from <<computer>> to the now empty internal storage (via USB cable in TWRP recovery)
NEW: 5. Reboot Recovery
6. Select INSTALL, select the ROM zip, and commence installation -- the rest is the same
Click to expand...
Click to collapse
Thank you for clarifying and taking the time to detail your steps. I will edit my existing instructions and add the installation method you outlined, as an alternative for members who do not have an OTG based external storage device. I will credit you with outlining the steps. Thanks again.
Viva La Android said:
Thank you for clarifying and taking the time to detail your steps. I will edit my existing instructions and add the installation method you outlined, as an alternative for members who do not have an OTG based external storage device. I will credit you with outlining the steps. Thanks again.
Click to expand...
Click to collapse
No problem and thank you for sharing the updated ROM!
This looks like the solution I need ...
Could y'all PLEASE define exactly which TWRP yer using to get this from the SDcard into the phone?
Essentially, I UL my BL via moto, fastbooted TWRP (3.1? I'd heard going past 3.2 invited a.b partition foibles) however this still gives me the "Unlocked Bootloader" BSOD, ergo cannot USE twrp - it simply reboots into a functional fone (but obviously NOT secure)
The XT1575 came (used) with stock Nougat ... can supply logcat etc if that's of any use to removing this stupid VIBRATOR screen that won't let me get into TWRP at all
TYVM
VW
You may use any version of TWRP you wish for installing this ROM. I would personally recommend the latest official TWRP v3.5.2-9.0, released just last month. TWRP for the xt1575 Clark was built using device-specific kernel source code. Thus, no matter which version of TWRP you encounter, A/B partitioning will not be a factor because the Clark does not now, nor has it ever, used the A/B partitioning scheme.
So try these steps exactly: download TWRP v3.5.2-9.0 from here https://dl.twrp.me/clark/ , rename it to twrp.img and store the image in your ADB/Fastboot directory on your PC. Also, save a copy of this renamed TWRP image on your xt1575. Boot your Moto into fastboot mode and connect the device to your PC using an adequate data sync cable. Open a command window on your PC in the path of your ADB/Fastboot directory. After confirming.a proper sync, flash TWRP by executing this command:
fastboot flash recovery twrp.img
Now boot to TWRP using:
fastboot boot twrp.img
Once booted into TWRP, select Install, tap the Install Image option in the lower-right of the display, navigate to the saved location of twrp.img you saved earlier and select it. Now, select Recovery from the partition options presented. Commence installation. When finished, TWRP should be installed properly on your /recovery partition. To ensure its persistence as properly installed, choose Reboot and Recovery.
Now you may install the ROM by the instructions outlined in this thread.
NOTE: There have been reports for years of xt1575 owners encountering difficulty with "making TWRP stick" while using the stock Android OS; i.e., TWRP being overwritten or replaced by stock recovery upon the first reboot to the Android OS following TWRP installation via fastboot. This is a common occurrence on many Motorola devices when TWRP is installed alongside the stock OS. (The best I can recall, this glitch is related to a "boot.p" script present in the stock Android ROM.) The instructions I outlined above can be used as a workaround to this issue to prevent custom recovery from being replaced or overwritten by stock recovery.
For what it is worth, I appear to be using 3.0.2-0. I see that's pretty old, but I don't seem to have any issues.
mddunner said:
For what it is worth, I appear to be using 3.0.2-0. I see that's pretty old, but I don't seem to have any issues.
Click to expand...
Click to collapse
Yeah it's an older version, but other than the upstream codebase, the newer versions for the Clark (built on the Android 9 Pie tree) are not remarkably different in terms of the GUI. For purposes of what we are doing here --installing a stock ROM archived package --pretty well any TWRP or OrangeFox custom recovery build will suffice.
For any members interested, I have updated this build to include Magisk v24.3, BusyBox v1.34.1, and I've done a bit more debloating and added some RAM tweaks on the kernel level. I'll need testers as I no longer own this device. Let me know by leaving a reply if you would like to test. I am posting a link in the downloads section for the updated ROM, but again I emphasize, this is of yet untested.

Categories

Resources