[RECOVERY][m7wls] TWRP 3.1.1-0 touch recovery [2017-05-19]

[RECOVERY][m7wls] TWRP 3.1.1-0 touch recovery [2017-05-19] - Sprint HTC One (M7)

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.0.2-0:
-Backups will now include adopted storage keys (Dees_Troy)
-Fixed an adb restore issue (bigbiff)
-Fixed rebooting when no OS is present (Dees_Troy)
-Fixed line wrapping in the GUI terminal (_that)
-Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)
CHANGELOG for 3.1.0-0:
-vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
-adb backup to stream a backup directly to or from your PC, see documentation here: https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9 (bigbiff)
-tweak MTP startup routines (mdmower)
-support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
-support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
-better indicate to users that internal storage is not backed up (Dees_Troy)
-improve automatic determination of TW_THEME (mdmower)
-minimal getcap and setcap support (_that)
-try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
-shut off backlight with power key (mdmower)
-timeout during FDE decrypt (Dees_Troy and nkk71)
-support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
-boot slot support (Dees_Troy)
-TWRP app install prompt during reboot (Dees_Troy)
-support for AB OTA zips (Dees_Troy)
-support new Android 7.x log command (Dees_Troy)
-update recovery sources to AOSP 7.1 (Dees_Troy)
-numerous bugfixes and improvements by too many people to mention
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
DOWNLOAD:
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.

To get root:
Unlock your device via http://htcdev.com
Download the latest TWRP from http://techerrata.com/browse/twrp2/m7wls
Shut off your device.
Press and hold volume down and then press power. Keep holding volume down until a menu shows on your screen.
Use the volume rocker to select fastboot and press power to select fastboot.
Plug the device into your computer.
If you have the right drivers installed your phone screen will now say: FASTBOOT USB
Using a command prompt, type:
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Your device will reboot. Use the volume rocker to select recovery and press power. You will now boot TWRP.
In TWRP, select reboot -> system. You will be prompted to install SuperSU. Swipe to confirm.
When your device boots you will see a prompt to install the full version of SuperSU. Select to do the TWRP install. Your device will download a file, reboot into TWRP which will automatically install the file, then reboot again.
Congratulations, you are now rooted!

Thank you Sir I am glad to see were off to the right start

Thanks for this, Dees_Troy - great work! Thanks for letting me test this as well

Great job dude. You devs are really on top of your game. This is going on my One as of Friday.
Sent from my SPH-L710 using xda app-developers app

youkosnake said:
Great job dude. You devs are really on top of your game. This is going on my One as of Friday.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I know. I think I will run out of thanks to give today.

Thanks for your work Dees_Troy. I know I will also run out of thanks today

budeone said:
Thanks for your work Dees_Troy. I know I will also run out of thanks today
Click to expand...
Click to collapse
Tapatalk gives you unlimited thanks
Sent from my 5th Dimension eVo 3D
*Team 420 band of Misfits*

What happened to the SD card?
Hmmm...new version doesn't give you the ability to choose internal versus external sd? Restoring from an external backup doesn't seem to be an option....
Am I missing something?

sinman02 said:
Hmmm...new version doesn't give you the ability to choose internal versus external sd? Restoring from an external backup doesn't seem to be an option....
Am I missing something?
Click to expand...
Click to collapse
??
There is no external sd on this phone. You have the HTC One?
Sent from my HTCONE using Tapatalk 2

-viperboy- said:
??
There is no external sd on this phone. You have the HTC One?
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
This. But if you're using a different device, you should be able to click up at the top and click internal memory or microsd memory.
Sent straight outta Compton

-viperboy- said:
??
There is no external sd on this phone. You have the HTC One?
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
Took the words right from my finger tips :sly: lol
Sent from my 5th Dimension eVo 3D
*Team 420 band of Misfits*

-viperboy- said:
??
There is no external sd on this phone. You have the HTC One?
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
No...Galaxy s3....didn't realize this was for the One only....I just updated via Goo Manager... How do I flash back to 2.4.4.0?
I guess I was misdirected here from XDA article...
That's what I get for updating without researching...

sinman02 said:
No...Galaxy s3....didn't realize this was for the One only....I just updated via Goo Manager... How do I flash back to 2.4.4.0?
I guess I was misdirected here from XDA article...
That's what I get for updating without researching...
Click to expand...
Click to collapse
The S3 should have the option at the top of the screen to switch between external and internal memory. That's what I'm using ATM. S3 w/twrp 2.5.0. Give it a whirl before you go back. I like it much better.
Sent straight outta Compton

no recovery found for my Sony Xperia Z with GooManager

did anyone notice, that when u choose reboot, and choose shutdown, it actually reboots back to twrp?
this has been happening since the 2.3.3.2 version that I had.

becks0r said:
no recovery found for my Sony Xperia Z with GooManager
Click to expand...
Click to collapse
valkmanb said:
did anyone notice, that when u choose reboot, and choose shutdown, it actually reboots back to twrp?
this has been happening since the 2.3.3.2 version that I had.
Click to expand...
Click to collapse
I will also bet both of you don't realize you're in the Sprint HTC One thread...

-viperboy- said:
I will also bet both of you don't realize you're in the Sprint HTC One thread...
Click to expand...
Click to collapse
If it isn't obvious by now, the thread was linked on the xda portal as the latest and greatest verison of TWRP:
http://www.xda-developers.com/android/twrp-reaches-version-2-5-0-0-and-sees-debut-on-the-htc-one/
So yes, despite the fact that this forum and thread is for the HTC One for Sprint, people are getting linked over because of the mention there.
That aside, thanks much to the devs for making this work and I am looking forward to loading this on my phone once I get my hands on it.

Does this include Dumlock, like on the international HTC One?
I figure it doesn't otherwise it would probably state it in the OP somewhere, but just want to make sure so that others will definitely know either way.
Sent from either my Nexus 7 or HTC One via XDA Premium

KidCarter93 said:
Does this include Dumlock, like on the international HTC One?
I figure it doesn't otherwise it would probably state it in the OP somewhere, but just want to make sure so that others will definitely know either way.
Sent from either my Nexus 7 or HTC One via XDA Premium
Click to expand...
Click to collapse
Yup, I believe I remember seeing it. However, if they flash the boot.img like I do in the stock ROM, no need for it
Sent from my HTCONE using Tapatalk 2

Related

[RECOVERY][mint] TWRP 3.1.1-0 touch recovery [2017-05-19]

More information:
What is the FOTAKernel partition?
The FOTAKernel partition is used by Sony to do FOTA updates. Unlocked devices can't take Sony FOTA updates so using this partition for storing the recovery ramdisk seems like a good idea. Unlocked users aren't able to use this partition anyway and the FOTAKernel partition is effectively the "recovery" partition on Sony devices.

Very nice and great to see more ot this on our devices.
I will link to the all in one thread when i get home.

Re: [RECOVERY] TWRP 2.3.3.0 touch recovery [2012-01-24]
Awesome news! Official support
Sent from my LT30p using xda premium

Updated!

Re: [RECOVERY] TWRP 2.4.0.0 touch recovery [2013-01-29]
Looks Awesome,I will check it with my Phone
Sent from my Micromax Canvas 3

No recovery found for my Xperia T

question?
Hy works that too on [ROM 4.1.2 - 4.2.1] JELLYBAM - v4.1.0 [17/01] [Mint] [PA.AOKP.CM10] ?

deltomi said:
No recovery found for my Xperia T
Click to expand...
Click to collapse
Same for me

No recovery for my Xperia TX. Please, Dees_Troy, do it for TX community! Thanks!

AW: [RECOVERY] TWRP 2.4.0.0 touch recovery [2013-01-29]
you got to have a rom and kernel with external recovery support. I have pa installed and it works flawlessly
Sent from my Paranoid Nexus T using xda premium

can you give me a link with this kernel.or is this the fota kernel?

AW: [RECOVERY] TWRP 2.4.0.0 touch recovery [2013-01-29]
Dante187 said:
can you give me a link with this kernel.or is this the fota kernel?
Click to expand...
Click to collapse
I'm running the fxp kernel that came with paranoid android. They added external recovery support with fxp204 so when you are running a rom that is based on a older release or on stock it won't work at all
Sent from my Paranoid Nexus T using xda premium

dtekkt said:
I'm running the fxp kernel that came with paranoid android. They added external recovery support with fxp204 so when you are running a rom that is based on a older release or on stock it won't work at all
Sent from my Paranoid Nexus T using xda premium
Click to expand...
Click to collapse
First thx.i have now many cm kernels flash who support open recovery then at works fine but the prob is on all other kernels work my wifi not more.i think at exist not open recovery kernel for [ROM 4.1.2 - 4.2.1] JELLYBAM - v4.1.0 [17/01] [Mint] [PA.AOKP.CM10].the original boot.img for this rom support no open recovery.

AW: [RECOVERY] TWRP 2.4.0.0 touch recovery [2013-01-29]
Dante187 said:
First thx.i have now many cm kernels flash who support open recovery then at works fine but the prob is on all other kernels work my wifi not more.i think at exist not open recovery kernel for [ROM 4.1.2 - 4.2.1] JELLYBAM - v4.1.0 [17/01] [Mint] [PA.AOKP.CM10].the original boot.img for this rom support no open recovery.
Click to expand...
Click to collapse
yes I think the rom needs to be updated. I heard of that before, you could try to wipe system and so on (maybe full wipe) after you installed the kernel, maybe that works for your wifi problem. However I prefer paranoid android
Sent from my Paranoid Nexus T using xda premium

Dees_Troy said:
More information:
What is the FOTAKernel partition?
The FOTAKernel partition is used by Sony to do FOTA updates. Unlocked devices can't take Sony FOTA updates so using this partition for storing the recovery ramdisk seems like a good idea. Unlocked users aren't able to use this partition anyway and the FOTAKernel partition is effectively the "recovery" partition on Sony devices.
Click to expand...
Click to collapse
I hava make it to works on TX.BTW,how to use the FOTAkernel partition?

petalex99 said:
No recovery for my Xperia TX. Please, Dees_Troy, do it for TX community! Thanks!
Click to expand...
Click to collapse
I don't have a TX so someone with a TX would have to stop by our IRC channel and offer to test.
dtekkt said:
yes I think the rom needs to be updated. I heard of that before, you could try to wipe system and so on (maybe full wipe) after you installed the kernel, maybe that works for your wifi problem. However I prefer paranoid android
Sent from my Paranoid Nexus T using xda premium
Click to expand...
Click to collapse
Oftentimes the wifi drivers are stored in /system so swapping kernels around without updating the wifi drivers can cause problems with wifi.
sj8023ld said:
I hava make it to works on TX.BTW,how to use the FOTAkernel partition?
Click to expand...
Click to collapse
There's instructions on our website for flashing the FOTAKernel partition or just use GooManager app to install it automatically. There's also a stock kernel that's been repacked with TWRP that will use the FOTAKernel partition available on our website. Kernel devs can use that as a template for packing the ramdisk in a way that will use the FOTAKernel partition so that they can enable the same functionality as seen in CM and PA, etc.

Deleted.

Re: [RECOVERY] TWRP 2.4.0.0 touch recovery [2013-01-29]
And how would one go about updating WiFi drivers to make sure it works after swapping kernels?
Sent from my Xperia T using xda app-developers app

billysimon99 said:
And how would one go about updating WiFi drivers to make sure it works after swapping kernels?
Sent from my Xperia T using xda app-developers app
Click to expand...
Click to collapse
Best solution is to use the zip that installs the kernel again as the zips usually contain the drivers. Other than that, backup and restore system with the kernel.

[RECOVERY][m8whl] TWRP 3.1.1-0 touch recovery [2017-05-19]

Reserved
Based on the work and assistance of @simonsickle so thanks very much to him.
Device specific page on our website.
Download link to current and past versions

Thanks for this!

Thanks @Dees_Troy and @simonsickle!
~Jflteusc on OctOS
KToonsez Kernel
1.998 Max ¦ 189 Min ¦ 702 Screen Off
Ktoonsified v5 Setup

Okay. I'm brain dead. Post says 2.7.0.0.
Link has 2.7.0.2 as latest.
Sorry. Been up since 2am.

Thanks guys
Sent from my SM-N900P using XDA Premium HD app

Is it possible to post a recovery flashable zip...for this recovery?
Sent from my 831C using Tapatalk

asafegous said:
Is it possible to post a recovery flashable zip...for this recovery?
Sent from my 831C using Tapatalk
Click to expand...
Click to collapse
I used the terminal emulator install method. You can cut and paste the command line right from the twrp site. Very quick and easy.
Sent from my 831C using Tapatalk

Sweet! Now all I need to see is an RUU for emergency's and ARHD support for Sprint before I pick this phone up on Sprint's network :angel::good:

No answer? Is it a typo?

mcwups1 said:
No answer? Is it a typo?
Click to expand...
Click to collapse
02 would be the latest, 2.700 Is the stable version.
Sent from my gunmetal sexbox

Yay, finally the official post has arrived!

Still don't know which to install.
OP states 2.7.0.0 is stable, but the date is 4/14, which doesn't match any in the link. The only one close to that date is the 2.7.0.2 version, but still isn't the exact date.
The OP and the links don't match.

2.7.0.2 wasn't stable for me. Back on capt.'s 2.7.0.5.
Sent From My HTC One (M8)

mcwups1 said:
Okay. I'm brain dead. Post says 2.7.0.0.
Link has 2.7.0.2 as latest.
Sorry. Been up since 2am.
Click to expand...
Click to collapse
I think this thread just has not been updated with 2.7.0.2 I'm running 2.7.0.2 from the link posted.
---------- Post added at 12:29 AM ---------- Previous post was at 12:28 AM ----------
Rydah805 said:
2.7.0.2 wasn't stable for me. Back on capt.'s 2.7.0.5.
Sent From My HTC One (M8)
Click to expand...
Click to collapse
What wasn't stable? seems ok to me.

Yea Idk y it got labeled 0 when 2 was the latest "official", but nothing wrong with additions cap has added to make it .5. Have been running that through the Mills and have seen reason those additions shouldn't be push to official soure
~m8whl modded stock
2.265 Max ¦ 300 Min
ondemand
row

MassStash said:
Yea Idk y it got labeled 0 when 2 was the latest "official", but nothing wrong with additions cap has added to make it .5. Have been running that through the Mills and have seen reason those additions shouldn't be push to official soure
~m8whl modded stock
2.265 Max ¦ 300 Min
ondemand
row
Click to expand...
Click to collapse
Because those patches, while they may work fine on our device, may not work well (or at all) on others. Even worse, they could break functionality on other devices. Thus the need for complete and proper testing prior to such features being merged.

So, would your recovery (2.7.0.7) be the best to use for now?
I figure you wouldn't run it if it didn't include everything.

mcwups1 said:
So, would your recovery (2.7.0.7) be the best to use for now?
I figure you wouldn't run it if it didn't include everything.
Click to expand...
Click to collapse
If you're having issues with this one, then yes, mine is another option.

Is the Aroma touch issue fixed in this version?
Sent from my 831C using xda app-developers app

[RECOVERY][lenok] TWRP 3.1.1-0 touch recovery [2017-05-19]

Device specific page on our website with manual install instructions.
Download links for all current and past versions.

There's no lg g watch r (lenox) available in twrp app. I have latest version of the app. What's wrong?
Sent from HTC One M8 running Viper One

Vi553r said:
There's no lg g watch r (lenox) available in twrp app. I have latest version of the app. What's wrong?
Sent from HTC One M8 running Viper One
Click to expand...
Click to collapse
You will not be able to use the app to flash this because of the way fast boot works. Unless they make a custom watch app to dd flash it.
Sent from my A0001 using XDA Free mobile app

first things first, kudos to tonu42 for posting the unofficial twrp back in december.
sadly, the 2.8.3.0 build somehow screwed up adb for me - but now with the official 2.8.4.0 and that "powerbutton to go back" functionality...just swell

eeermm....I just flashed the twrp recovery and now when I restart, it always goes into recovery. I can't seem to get to boot.
is this normal?

b0gd4n said:
eeermm....I just flashed the twrp recovery and now when I restart, it always goes into recovery. I can't seem to get to boot.
is this normal?
Click to expand...
Click to collapse
No it isn't normal. I flashed yesterday and haven't experienced this problem, you did flash recovery right? How are you trying to reboot btw?

TimmyUK said:
No it isn't normal. I flashed yesterday and haven't experienced this problem, you did flash recovery right? How are you trying to reboot btw?
Click to expand...
Click to collapse
yeah, so I booted in fastboot and did fastboot flash recovery open....zip
twrp works nice, but when I choose reboot system it starts recovery again.
I am also getting mounting errors (unable to mount data and storage).
EDIT: also, in twrp the Internal Storage is appearing as 0MB

b0gd4n said:
yeah, so I booted in fastboot and did fastboot flash recovery open....zip
twrp works nice, but when I choose reboot system it starts recovery again.
I am also getting mounting errors (unable to mount data and storage).
EDIT: also, in twrp the Internal Storage is appearing as 0MB
Click to expand...
Click to collapse
Symptoms don't sound good. You may have to re-flash the system/software from one of the other threads. Maybe worthwhile re-flashing the previous ver of TWRP?

TimmyUK said:
Symptoms don't sound good. You may have to re-flash the system/software from one of the other threads. Maybe worthwhile re-flashing the previous ver of TWRP?
Click to expand...
Click to collapse
yeah, I'm gonna try following this thread http://forum.xda-developers.com/g-watch-r/development/emergency-guide-how-to-blank-regenerate-t2984678
I'll try another twrp now.

TimmyUK said:
Symptoms don't sound good. You may have to re-flash the system/software from one of the other threads. Maybe worthwhile re-flashing the previous ver of TWRP?
Click to expand...
Click to collapse
ok...so flashing previous version of twrp did not work, same problem with unable to mount.
now, this is weird. I flashed stock recovery, and the watch started straight away...

b0gd4n said:
ok...so flashing previous version of twrp did not work, same problem with unable to mount.
now, this is weird. I flashed stock recovery, and the watch started straight away...
Click to expand...
Click to collapse
That is weird, you running 5.0.1?

TimmyUK said:
That is weird, you running 5.0.1?
Click to expand...
Click to collapse
yeah, 5.0.1.
ok, so after I flashed the stock recovery, and restarted the device normally, I adb sideloaded the 5.0.1 update mentioned in the thread posted earlier.
I then flashed the latest twrp again, and it now seems to be all nice and fine. I can boot to twrp, and the stuff gets mounted and I can reboot the system as well.
dunno what, but smth went wrong the first time I flashed.
all fine now.

Really strange, glad you got it sorted.

@b0gd4n
I've had the same problem at first TWRP Flash.
That's why i've posted this guide

Schmurtz1968 said:
@b0gd4n
I've had the same problem at first TWRP Flash.
That's why i've posted this guide
Click to expand...
Click to collapse
erm, which guide?

b0gd4n said:
erm, which guide?
Click to expand...
Click to collapse
The one you've pointed in this Thread

I did bootloader unlock for my watch using fastboot oem unlock
did fastboot flash recovery twrp.img
fastboot reboot.
I do have TWRP but when i press reboot->System it keeps booting to twrp.
I know to properly flash things on my devices but something here is wrong.

anyone got twrp working after flashing wear 5.02 ?

2.8.5.0 works for me on 5.0.2, Supersu FC's after rebooting and attempting installation. I think this is already a known problem. Just need to do a little more digging.
<edit> Updating to the latest (v2.46) has seemed to have resolved my issue

[RECOVERY][thunder_q45] TWRP 3.1.1-0 touch recovery [2017-05-19]

This thread is only for the Kazam Thunder Q4.5
Other devices look elsewhere.
You should be able to root the Thunder Q4.5 using Framaroot barahir. From there you can install the recovery using the instructions on our website. Download links for current and past versions and instructions for install here.
Kernel source is here.

Wow, never thought official TWRP would make it to this device! Can't wait to try it out.

it's a good news,
specially because it support's external keyboards .

mottlagh said:
it's a good news,
specially because it support's external keyboards .
Click to expand...
Click to collapse
Unfortunately the Q4.5 doesn't support USB host mode so it can't be used with an external keyboard.

Great to hear! Thanx!!
Will test it asap!

It can, it supports bluetooth keyboards.
Sent from my ET Persona 10114-B using XDA Free mobile app

mmonaghan34 said:
It can, it supports bluetooth keyboards.
Sent from my ET Persona 10114-B using XDA Free mobile app
Click to expand...
Click to collapse
Bluetooth isn't available in recovery either.
In other news, I pushed the kernel source to github. Link is in the second post. I trimmed about 1.4GB of logos meant for various other models of MTK phones from the original dropbox link that isn't needed or used in the kernel to reduce the upload size. I believe the logo is actually used in the lk bootloader. If I had the source code for the lk bootloader I could probably patch it to allow fastboot mode with working fastboot boot. I've done that on other MTK devices.
To make TWRP fit, I had to lzma both the kernel and the ramdisk instead of gzip. Fortunately we have kernel source for this device so we were able to make TWRP fit and now we have plenty of room for new features too.

Dees_Troy said:
Bluetooth isn't available in recovery either.
In other news, I pushed the kernel source to github. Link is in the second post. I trimmed about 1.4GB of logos meant for various other models of MTK phones from the original dropbox link that isn't needed or used in the kernel to reduce the upload size. I believe the logo is actually used in the lk bootloader. If I had the source code for the lk bootloader I could probably patch it to allow fastboot mode with working fastboot boot. I've done that on other MTK devices.
To make TWRP fit, I had to lzma both the kernel and the ramdisk instead of gzip. Fortunately we have kernel source for this device so we were able to make TWRP fit and now we have plenty of room for new features too.
Click to expand...
Click to collapse
Well, I have the stock rom if that would help, if yes, pm me and I'll send you a dropbox link.
Also subtle hint for a possible update to TWRP: bluetooth support if at all possible, as this would rectify said issue
Sent from my KAZAM Thunder Q45 using XDA Free mobile app

mmonaghan34 said:
Well, I have the stock rom if that would help, if yes, pm me and I'll send you a dropbox link.
Also subtle hint for a possible update to TWRP: bluetooth support if at all possible, as this would rectify said issue
Sent from my KAZAM Thunder Q45 using XDA Free mobile app
Click to expand...
Click to collapse
Bluetooth probably won't ever happen in recovery. Same for Wi-Fi, phone calls, texting, mobile data, and a whole host of other things that belong in the ROM and not in recovery. These things require proprietary files / binaries to work and a lot of the parts that make them work are in the Java / dalvik / ART side of Android. Java / davlik / ART aren't available in recovery. They would take up way too much space.
Recovery is a mini OS designed to help you get your device back in working order, not a full blown firmware.

Dees_Troy said:
Bluetooth probably won't ever happen in recovery. Same for Wi-Fi, phone calls, texting, mobile data, and a whole host of other things that belong in the ROM and not in recovery. These things require proprietary files / binaries to work and a lot of the parts that make them work are in the Java / dalvik / ART side of Android. Java / davlik / ART aren't available in recovery. They would take up way too much space.
Recovery is a mini OS designed to help you get your device back in working order, not a full blown firmware.
Click to expand...
Click to collapse
Well, that's interesting, as far as I was aware, recovery booted inside dalvik, guess i was wrong :/
Well, you said about fixing fastboot, if that were to happen, would it just be a custom kernel to flash? Or would it be a different method of intallatiion?
Sent from my ET Persona 10114-B using XDA Free mobile app

has anyone had success installing this through the app or the dd command? neither of these worked for me, I had to use MTK droid root & tools which worked

matt4321 said:
has anyone had success installing this through the app or the dd command? neither of these worked for me, I had to use MTK droid root & tools which worked
Click to expand...
Click to collapse
Nope, in the app, the thunder_q45 option wasn't even in the list. Not trued dd yet though
Sent from my KAZAM Thunder Q45 using XDA Free mobile app

What this guy's i need software upgrade i been getting hacked

bpair9 said:
What this guy's i need software upgrade i been getting hacked
Click to expand...
Click to collapse
In what way have you been getting 'hacked', because I think you will find that hacking is the art of writing code/optimizing the performance of anything, while cracking is breaking into/hijacking a digital system usually for malicious purposes (what the stupid media calls hacking).
Also, if someone really did have remote access to your device, then a software update wouldn't help.
Sent from my ET Persona 10114-B using XDA Free mobile app

Anyone had any luck installing 2.8.6.0?
I've tried through MTK droid root & tools, as well as through 2.8.5.0 flashing the img to the recovery partition.
It just hangs at the spalsh screen
@Dees_Troy I think 2.8.6.0 is borked on this phone
Reverting to 2.8.5.0 and it boots

So i heard about how @matt4321 was having issues installing the recovery from the app or root shell, do either of these work yet? Or do i just use mtk flash tools to install? or is there a way to temp boot into twrp then use it to install itself? Thanks
Sent from my KAZAM Thunder Q45 using XDA Free mobile app

mmonaghan34 said:
So i heard about how @matt4321 was having issues installing the recovery from the app or root shell, do either of these work yet? Or do i just use mtk flash tools to install? or is there a way to temp boot into twrp then use it to install itself? Thanks
Sent from my KAZAM Thunder Q45 using XDA Free mobile app
Click to expand...
Click to collapse
I've been using mtk droid root and tools.
2.8.6.0 still doesn't work though

matt4321 said:
I've been using mtk droid root and tools.
2.8.6.0 still doesn't work though
Click to expand...
Click to collapse
So, as I'm new to all this custom recovery installation without fastboot, would anyone be able to give me a guide on how to use mtk droid root and tools to install twrp?
Many thanks
Sent from my KAZAM Thunder Q45 using XDA Free mobile app

Dees_Troy said:
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.
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Click to expand...
Click to collapse
Any chance of v3.0.0 for Q45 ? @Dees_Troy

[A2017U][RECOVERY][UNOFFICIAL] TWRP 3.0.2-2 touch recovery for ZTE Axon 7

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.0.2-2:
-Fix subpartition restore bug (ex: EFS)
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
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:
TWRP 3.0.2-2
Can be updated quickly and easily within TWRP if TWRP is already installed
1) Download the latest version from the above link
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
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.
SOURCE/THANKS:
Device tree: https://github.com/TeamRegular/android_device_zte_ailsa_ii
@DrakenFX for testing and requesting my help
@Unjustified Dev for being....ME of course

Prerequisites:
* Unlocked bootloader Guide Here
Installation:
Code:
adb reboot bootloader
fastboot flash recovery twrp-3.0.2-2-a2017u.img
fastboot reboot
To enter recovery:
* Power + volume up
Code:
adb reboot recovery
Installing Mods:
If you plan on modifying the system, please follow this post here or you'll result in a bootloop.

Reserved

Holy **** that is quick. You are a hero.
I picked up the chinese model though, still waiting for bootloader... They confirmed it but they are taking their time.
Hoping the devices are similar enough that this twrp will also work on mine.

aPexalpha said:
Holy **** that is quick. You are a hero.
I picked up the chinese model though, still waiting for bootloader... They confirmed it but they are taking their time.
Hoping the devices are similar enough that this twrp will also work on mine.
Click to expand...
Click to collapse
The base HW should be the same across the world. The only real difference is the Force Touch feature in the Chinese 6GB model, which might necessitate a different touch screen driver.
The Chinese ROM also calls the device the ailsa_ii, just with a different model number.

that's awsome, very nice work. Now the custom ROMs have open doors

In BoardConfig.mk, wouldn't we want "BOARD_HAS_NO_REAL_SDCARD := false" (just leave it out) and "TW_NO_USB_STORAGE := false" (or leave it out)? I'm pretty sure it has OTG support and it definitely has a real SD card.
Thanks for getting the repo up and running as well.

Very good news! Suprised how fast it all went down, cheers! On a side note, is there any chance this or any other method will ever work for EU models? I really like the phone, but waiting for the manufacturer to do something about the software is kind of hopeless.

MeggaMortY said:
Very good news! Suprised how fast it all went down, cheers! On a side note, is there any chance this or any other method will ever work for EU models? I really like the phone, but waiting for the manufacturer to do something about the software is kind of hopeless.
Click to expand...
Click to collapse
It all depends on ZTE Europe releasing a bootloader unlock for the European (Global) version of the phone.

Thank you! Sharing the device tree helps a ton with additional development. Let's see what we can build with this.

TeutonJon78 said:
In BoardConfig.mk, wouldn't we want "BOARD_HAS_NO_REAL_SDCARD := false" (just leave it out) and "TW_NO_USB_STORAGE := false" (or leave it out)? I'm pretty sure it has OTG support and it definitely has a real SD card.
Thanks for getting the repo up and running as well.
Click to expand...
Click to collapse
1st config as I remember is for internal storage. Something about not allowing you to partition it.
2nd config is to remove mass storage support. TWRP supports mtp.
Sent from my 6045I using Tapatalk

Thank you! One question, which I suppose isn't just limited to TWRP: Though we have TWRP (again, awesome!), we don't have a stock image or a way to get back to "locked, unrooted" status yet or the default ROM, right?

ScaryBugThing said:
Thank you! One question, which I suppose isn't just limited to TWRP: Though we have TWRP (again, awesome!), we don't have a stock image or a way to get back to "locked, unrooted" status yet or the default ROM, right?
Click to expand...
Click to collapse
Unfortunately I do not know. ZTE blocked the command fastboot boot so we couldn't backup the stock recovery.img we had no choice but to flash it. You can however backup system image in recovery and restore it later. This is the first thing that should be done before flashing root as well as a normal backup. If you restore your system image you can always OTA update through TWRP since it will be an untouched image. I do doubt that you can return to official OEM locked status unless they say it won't void warranty if you unlock it.
Sent from my 6045I using Tapatalk

ScaryBugThing said:
Thank you! One question, which I suppose isn't just limited to TWRP: Though we have TWRP (again, awesome!), we don't have a stock image or a way to get back to "locked, unrooted" status yet or the default ROM, right?
Click to expand...
Click to collapse
Nope, as far as I know. ZTE has to release the stock factory images. It's extremely difficult to create from a mere backup because it requires ZTE's signature verification.
Sent from my XT1095 using Tapatalk
---------- Post added at 12:16 PM ---------- Previous post was at 12:13 PM ----------
I'm really happy for the TWRP. Thank you man.
Sent from my XT1095 using Tapatalk

When I flash SuperSU 2.76 the phone just turns off, which is kind of strange. Has anyone else had any luck?

Got the same thing when I flash SuperSU

goalkeepr said:
When I flash SuperSU 2.76 the phone just turns off, which is kind of strange. Has anyone else had any luck?
Click to expand...
Click to collapse
allan1229 said:
Got the same thing when I flash SuperSU
Click to expand...
Click to collapse
After you try to install super su and the phone turns off boot back into recovery and
adb pull /cache/recovery/last_log

first time doing this. let me know if its right
http://www.mediafire.com/download/s988ykn9wws5a63/last_log

Unjustified Dev said:
1st config as I remember is for internal storage. Something about not allowing you to partition it.
2nd config is to remove mass storage support. TWRP supports mtp.
Sent from my 6045I using Tapatalk
Click to expand...
Click to collapse
Ah, that would make sense. I couldn't tell from the TWRP documentation if either one was general. The SD one is about partition, I just didn't know if applied to an external card (not that most people partition one since Windows doesn't allow it anyway). You definitely wouldn't want people partitioning their internal one.
It makes sense to get rid of UMS, as then TWRP couldn't read it while you're connected to the computer. It's unfortunate they names it USB rather than UMS then. Thanks.

Unjustified Dev said:
Prerequisites:
* Unlocked bootloader Guide Here
Installation:
Code:
fastboot flash recovery twrp-3.0.2-0-a2017u.img
fastboot reboot
To enter recovery:
* Power + volume up
Code:
adb reboot recovery
Click to expand...
Click to collapse
I'm confused I connect my phone and go into command prompt and do the first command fastboot flash recovery twrp-3.0.2-0-a2017u.img enter and all I get is waiting on device am I doing something wrong?

Database Develop

welcome