Develop Bugs

[Question] Can't receive OTAs anymore

Hello XDA,
I very recently got an HTC 10 and the 1st thing I did was install TWRP and root the phone using SuperSU. I completely forgot about firmware updates since those were rare on my old phone (HTC one m8).
Now, the problem I face is that I can't receive OTAs anymore since my recovery is modified.
My questions are:
Are OTAs worth to get? Do they significantly improve the phone's behaviour? The 1st OTA (1.21 > 1.30) is said to improve phone and wifi stability as well as camera. Is it that significant?
How should I go about installing OTAs now? Should I flash them?
Thank you!

1. yeah OTA are worth to get, mostly.
2. I'm doing it by : - restoring system image and boot, then flashing proper stock recovery, then manually updating OTA via file on SD, and after that back to TWRP and SuperSU. But this will only work for stock rom.

Thank you, the problem is that I can't find the proper stock recovery anywhere. I'd need the 1.21 european version and I couldn't find it anywhere

To get OTA upgrade, I use the following method:-
Disable security
Full Nandroid
Flash RUU (to get firmware)
Flash TWRP
Restore Nandroid
Enable security (pin/pattern)
Sent from my HTC 10 using XDA-Developers mobile app

Should be able to received OTA, right? just can't install it using TWRP recovery.
I copy the OTA firmware file from /data/data/com.htc.updater/files to external microSD card then move to PC.
extract the firmware.zip, recovery.img is in there, then its just a process of flashing to HTC recovery.
It works for my M7, sort of work for the last 1.95.400.3 to 1.90.400.4 update. What I mean is system is update to 1.90.400.4 but I did see a warning triangle with exclamation mark, this is the first OTA update I experience, don't know if this is normal.
Don't see any issue after update so I guess it work.
BTW, I use ES explorer with root access; WinRAR to extract the recovery cause 7zip can't.
Click to expand...
Click to collapse
Please ignore the above, I was wrong to think the above method will work in HTC 10.

Phone keeps asking me to install an OTA update I already installed

So, I have a Sprint HTC 10. It was rooted, and then an OTA update came out about a week or so ago, version 1.80.651.10.
I unrooted and installed it, since I have TWRP it seems to take over the install process, but more or less does install it correctly.
Once my phone rebooted, it complained that the download was corrupt like it always does (likely due to TWRP) but this has happened before and the update always actually does install successfully. Going to system settings I can confirm that I am on version 1.80.651.10.
However, this time, it seems hell-bent on assuming that the update didn't install. It keeps putting an update notification in the notification bar that refuses to go away. If I go to check for updates, it confirms that I am up to date and the notification disappears.... for a short while, but then appears again asking me to install the update.
How can I get rid of this annoying thing? I haven't even gotten around to re-rooting my phone yet, as been confirmed by root and safetynet checkers, the ROM is basically at stock right now.

Cyber Akuma said:
So, I have a Sprint HTC 10. It was rooted, and then an OTA update came out about a week or so ago, version 1.80.651.10.
I unrooted and installed it, since I have TWRP it seems to take over the install process, but more or less does install it correctly.
Once my phone rebooted, it complained that the download was corrupt like it always does (likely due to TWRP) but this has happened before and the update always actually does install successfully. Going to system settings I can confirm that I am on version 1.80.651.10.
However, this time, it seems hell-bent on assuming that the update didn't install. It keeps putting an update notification in the notification bar that refuses to go away. If I go to check for updates, it confirms that I am up to date and the notification disappears.... for a short while, but then appears again asking me to install the update.
How can I get rid of this annoying thing? I haven't even gotten around to re-rooting my phone yet, as been confirmed by root and safetynet checkers, the ROM is basically at stock right now.
Click to expand...
Click to collapse
If you have twrp installed it wont update the firmware only software. You need to flash firmware seperatly with fastboot.

So I would need to extract the firmware or something out of the OTA file and flash that manually? What partitions would the firmware be updating?
And I am assuming this would overwrite TWRP and I would have to reinstall it?

Cyber Akuma said:
So I would need to extract the firmware or something out of the OTA file and flash that manually? What partitions would the firmware be updating?
And I am assuming this would overwrite TWRP and I would have to reinstall it?
Click to expand...
Click to collapse
Correct.:good:

Can somebody please explain how to flash the firmware with fastboot?
So I have to flash the OTA with TWRP, afterwards I have to extract the firmware file out of the OTA.zip and flash it with fastboot. But which commands are necessary in fastboot?

To get this out of the way, you can only flash firmware over fastboot if you're S-OFF. Otherwise, you'll need to restore completely to stock via custom recovery or RUU then update by OTA.
The best guide I've found for this is at http://forum.xda-developers.com/htc-10/how-to/2016-05-27-fastboot-flashing-firmware-t3387520.

kjjejones42 said:
To get this out of the way, you can only flash firmware over fastboot if you're S-OFF. Otherwise, you'll need to restore completely to stock via custom recovery or RUU then update by OTA.
The best guide I've found for this is at http://forum.xda-developers.com/htc-10/how-to/2016-05-27-fastboot-flashing-firmware-t3387520.
Click to expand...
Click to collapse
Thats not true. You flash in ruu mode when S - ON. If your are S - Off you can do it from download mode. I think you are a little confused with that thread. Those firmwares are modified and for S -Off phones only.

yldlj said:
Thats not true. You flash in ruu mode. If soff you can do it from download mode.
Click to expand...
Click to collapse
Ah, you're right! Sorry. To flash while S-ON, the CID and MID must match the zip + the bootloader must be locked, right?

kjjejones42 said:
Ah, you're right! Sorry. To flash while S-ON, the CID and MID must match the zip + the bootloader must be locked, right?
Click to expand...
Click to collapse
Im not sure about locked or relocked bootloader, i think it will work with unlocked but i could be wrong.

yldlj said:
Im not sure about locked or relocked bootloader, i think it will work with unlocked but i could be wrong.
Click to expand...
Click to collapse
I just had another thought, correct me if I'm wrong. You can flash the OTA manually through the stock recovery as a ZIP.
The OTA ZIP can either be downloaded in various places online, or you can download it on the phone as usual then find it in /data/data/com.htc.updater/files (if your device is rooted). More info at http://forum.xda-developers.com/showpost.php?p=66548846&postcount=3.
You can then flash the OTA through recovery if you have;
* 100% unmodified system (can be restored from TWRP backup)
* Stock recovery

kjjejones42 said:
I just had another thought, correct me if I'm wrong. You can flash the OTA manually through the stock recovery as a ZIP.
The OTA ZIP can either be downloaded in various places online, or you can download it on the phone as usual then find it in /data/data/com.htc.updater/files (if your device is rooted). More info at http://forum.xda-developers.com/showpost.php?p=66548846&postcount=3.
You can then flash the OTA through recovery if you have;
* 100% unmodified system (can be restored from TWRP backup)
* Stock recovery
Click to expand...
Click to collapse
Correct. Also unmodified boot. But if your flashing unmodified system image, boot and stock recovery you may aswell just boot to android and take the ota.

TMO OXC27.1 Oreo firmware

Anyone has the latest(released Feb 16th) oreo OTA full stock firmware from T-Mobile?

I tried pulling it from a logcat. Was going to fastboot flash it since I can't install it while rooted. Every url I found in the logcat gave me a 405 error though.

I got another Moto Z2 Force today. Fresh out of the box TMO. Came with the OCX27. I have not yet taken the update. If someone can guide me on how to extract the OTA That'd be helpful. Only thing I am willing to do so far with this new device is unlock the bootloader that's it. I will not root or install TWRP until I can extract the OTA and attempt to fix my other device stuck in an unknown baseband no IMEI state. I got there by attempting to install TWRP and root with Magisk.

droidgreg said:
I got another Moto Z2 Force today. Fresh out of the box TMO. Came with the OCX27. I have not yet taken the update. If someone can guide me on how to extract the OTA That'd be helpful. Only thing I am willing to do so far with this new device is unlock the bootloader that's it. I will not root or install TWRP until I can extract the OTA and attempt to fix my other device stuck in an unknown baseband no IMEI state. I got there by attempting to install TWRP and root with Magisk.
Click to expand...
Click to collapse
Pulling the log through ADB will yield the OTA download link. That's how @joemossjr and I grabbed the Oreo update from nougat for TMO and Sprint.

Uzephi said:
Pulling the log through ADB will yield the OTA download link. That's how @joemossjr and I grabbed the Oreo update from nougat for TMO and Sprint.
Click to expand...
Click to collapse
Step by step instructions would be appreciated.

droidgreg said:
Step by step instructions would be appreciated.
Click to expand...
Click to collapse
It's hard to explain. You have to capture the moment the phone grabs the OTA file from Motorola's update website.
Enable developer options
Enable ADB
Plug phone up to a PC that has updated ADB binaries
Open terminal/command prompt
Adb shell
Logcat
After you do that your terminal of choice will start spitting out the log.
Run the system updater.
Download the OTA. At that moment, one of the logs should give you a VERY long URL. That's the download link you're looking for.
Copy and paste into your browser. You should be auto downloading it.
Done

Very stupid question, but I have to ask, because Moto is a bit wonky on bootloaders and updates, etc.
I'm currently on OCX27 and I've got the notification to download OCX27.1. I do have an unlocked bootloader and I am rooted with Magisk. Since I have not overwritten the recovery partition, can I take this update? On most other phones I have, I've been able to restore the stock recovery partition, flash the update, and flash TWRP back on, but on this Moto, I chose to boot twrp for loading magisk via adb. Make sense? If I'm not able to take this update, can I shut these update notifications off? They are already off in dev options.
Thanks in advance!

joesee said:
Very stupid question, but I have to ask, because Moto is a bit wonky on bootloaders and updates, etc.
I'm currently on OCX27 and I've got the notification to download OCX27.1. I do have an unlocked bootloader and I am rooted with Magisk. Since I have not overwritten the recovery partition, can I take this update? On most other phones I have, I've been able to restore the stock recovery partition, flash the update, and flash TWRP back on, but on this Moto, I chose to boot twrp for loading magisk via adb. Make sense? If I'm not able to take this update, can I shut these update notifications off? They are already off in dev options.
Thanks in advance!
Click to expand...
Click to collapse
I used titanium backup to freeze the update service as it's named in the notification.

charlatan01 said:
I used titanium backup to freeze the update service as it's named in the notification.
Click to expand...
Click to collapse
Thank you. I looked under U for update. I should have searched... It's actually called Motorola Update Services.

joesee said:
Very stupid question, but I have to ask, because Moto is a bit wonky on bootloaders and updates, etc.
I'm currently on OCX27 and I've got the notification to download OCX27.1. I do have an unlocked bootloader and I am rooted with Magisk. Since I have not overwritten the recovery partition, can I take this update? On most other phones I have, I've been able to restore the stock recovery partition, flash the update, and flash TWRP back on, but on this Moto, I chose to boot twrp for loading magisk via adb. Make sense? If I'm not able to take this update, can I shut these update notifications off? They are already off in dev options.
Thanks in advance!
Click to expand...
Click to collapse
You won't be able to update through OTA if you're rooted

https://we.tl/B4j816Z2n8
Here's the link to the TMO OCX27.1 OTA firmware if anyone needs it.

Hi, I am wondering, if I am on ocx 27 do you guys think the 27.1 ota will install in adb sideload as it won't install in ota and I am not rooted. Also, is there a way to extract the bin in the ota?

droidgreg said:
I got another Moto Z2 Force today. Fresh out of the box TMO. Came with the OCX27. I have not yet taken the update. If someone can guide me on how to extract the OTA That'd be helpful. Only thing I am willing to do so far with this new device is unlock the bootloader that's it. I will not root or install TWRP until I can extract the OTA and attempt to fix my other device stuck in an unknown baseband no IMEI state. I got there by attempting to install TWRP and root with Magisk.
Click to expand...
Click to collapse
Did you get your second Z2 rooted and if so did you use magisk v16? I just got a Z2 today that is on the December 1, 2017 security patch, OCX27.1, Android 8.00 and I'd like to root but hesitant. I have already unlocked the bootloader, placed magisk and twrp-3.2.1-1-nash zip(s) in internal storage, and know how to fastboot boot into recovery, I just don't want to brick my new phone. Any help with step by step instructions once I'm in TWRP to flash magisk is greatly appreciated! Do I need to do any of the following: Keep system read only or allow modifications before flashing magisk? wipe data/factory reset, mount storage, wipe cache and dalvik after flashing? Thanks in advance!

climbhigh77 said:
Did you get your second Z2 rooted and if so did you use magisk v16? I just got a Z2 today that is on the December 1, 2017 security patch, OCX27.1, Android 8.00 and I'd like to root but hesitant. I have already unlocked the bootloader, placed magisk and twrp-3.2.1-1-nash zip(s) in internal storage, and know how to fastboot boot into recovery, I just don't want to brick my new phone. Any help with step by step instructions once I'm in TWRP to flash magisk is greatly appreciated! Do I need to do any of the following: Keep system read only or allow modifications before flashing magisk? wipe data/factory reset, mount storage, wipe cache and dalvik after flashing? Thanks in advance!
Click to expand...
Click to collapse
All you need to do is grab the latest twrp img and zip file from twrp. Should be version 3.2.1-1
Then fastboot boot the img file, then once in twrp you want to flash the zip file, then when that is done reboot back into recovery
Then simply flash Magisk and reboot. Done.

How should I properly Flash Stock Firmware?
New to Moto phones and wondering what the correct method is for reverting to stock? I downloaded the 27.1 Oreo zip from this thread, do I flash it in twrp or should I flash it in adb from the bootloader? I get the following error message in twrp whenever I wipe dalvik/cache, try to install a zip, or do a backup which always says fail. I need a fresh install and re root, etc. Thank you!!

climbhigh77 said:
New to Moto phones and wondering what the correct method is for reverting to stock? I downloaded the 27.1 Oreo zip from this thread, do I flash it in twrp or should I flash it in adb from the bootloader? I get the following error message in twrp whenever I wipe dalvik/cache, try to install a zip, or do a backup which always says fail. I need a fresh install and re root, etc. Thank you!!
Click to expand...
Click to collapse
you can not flash with twrp. open the zip and see if there is a "flash-all.bat" file as well as adb and fastboot files. if not then pull them from one of the other flashall zips and add them to 27.1 zip. boot your phone to the bootloader, connect usb cable to your device and pc, then run the .bat file.

mattlowry said:
you can not flash with twrp. open the zip and see if there is a "flash-all.bat" file as well as adb and fastboot files. if not then pull them from one of the other flashall zips and add them to 27.1 zip. boot your phone to the bootloader, connect usb cable to your device and pc, then run the .bat file.
Click to expand...
Click to collapse
Factory reset gets the same error message shown in the attached photo. Thanks for the info, unfortunately I'm still a bit confused. Is this the only method to return to stock? I've searched but I'm not finding much and this method is completely new to me. In the past I've used Odin and LG up with my other devices, this is my first motorola. If I wipe internal storage in twrp will that erase the OS and need a new install? I am thinking that may clear up my issues but nervous that the phone won't boot up after that. Thanks and my apologies for my noob questions.

climbhigh77 said:
Factory reset gets the same error message shown in the attached photo. Thanks for the info, unfortunately I'm still a bit confused. Is this the only method to return to stock? I've searched but I'm not finding much and this method is completely new to me. In the past I've used Odin and LG up with my other devices, this is my first motorola. If I wipe internal storage in twrp will that erase the OS and need a new install? I am thinking that may clear up my issues but nervous that the phone won't boot up after that. Thanks and my apologies for my noob questions.
Click to expand...
Click to collapse
unfortunately other than manually fastbooting each img file to your phone this is the only way. check out this https://forum.xda-developers.com/z2-force/how-to/to-stock-roms-t3672859

BROKEN
droidgreg said:
https://we.tl/B4j816Z2n8
Here's the link to the TMO OCX27.1 OTA firmware if anyone needs it.
Click to expand...
Click to collapse
Please upload again. Thx

sd_N said:
Please upload again. Thx
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=673956719939833411
Here's the official 27.1 firmware. The flashfile.xml has the correct order and commands to flash in fastboot, or search xda for the converter to a flashall.bat.
Sent from my Moto Z (2) using XDA Labs

Stock recovery for OS version 3.41.651.41 needed

I bought the phone (HTC One M9) yesterday and I realized I couldn't install the OTA updates I received because TWRP custom recovery was installed. I've looked through all the threads here but I never found the file I need. Any help would be highly appreciated. By the way,the bootloader is locked and the phone is unrooted, but S-OFF

S-off makes no difference. Unlocked bootloader makes no difference. If you flash a stock recovery over twrp you'll instantly kill the phone.
You need the full proper stock firmware of the exact same version you have on it now in .zip format and flash it from the external sd in download mode. You can use the ruu (.exe) too if it'll flash. Then you can take the ota's.
If the phone has been touched and not flashed back to stock you will need to flash to stock to get ota's. You cannot just "undo" what you've done to it. It must be properly reflashed to get the stock hash and keys.

shivadow said:
If you flash a stock recovery over twrp you'll instantly kill the phone.
Click to expand...
Click to collapse
Why should flashing the stock recovery via twrp kill the phone? If that was the case you wouldn't be able to get back to stock via twrp backups.
Edit @OP: If you have a RUU for the mentioned firmware version then you can use the RUU decryption tool that is linked in the ReadMe thread. The tool will extract the stock recovery from the RUU.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Why should flashing the stock recovery via twrp kill the phone? If that was the case you wouldn't be able to get back to stock via twrp backups.
Edit @OP: If you have a RUU for the mentioned firmware version then you can use the RUU decryption tool that is linked in the ReadMe thread. The tool will extract the stock recovery from the RUU.
Click to expand...
Click to collapse
Unrooted. Twrp will require root. If I remember correctly you flash twrp which roots the phone and then you flash supersu?.
If it is unrooted with twrp on it then it is in an "unknown state" (to me) and not worth risking going any further unless it is a full stock firmware flash. If he flashes a stock recovery over twrp he still wont have system "untouched" which I believe stock recovery requires?.. At least to get the ota's he will need an untouched partition.
Or would he be better off rerooting via twrp and go from there?.

No, twrp doesn't require root nor does flashing twrp root the phone. Twrp is a custom recovery that supports (unlike the stock recovery) flashing files that aren't signed by HTC. SuperSU and magisk are the ones that enable root. For using a metaphora (that might not fit exactly but that should suffice for making things clear): You don't consider your phone to be rooted, either, just because you installed Odin on your PC.
Root can (more or less) be compared with admin permissions on a Windows PC. It has nothing to do with twrp being "installed" or not. There are even methods for rooting phones without the use of twrp (e.g. kingroot - which is adware, btw).
If you flash twrp but don't root your phone then it's simply not-rooted. Keeping the phone in such a state doesn't make much sense since it isn't completely stock, either. However, it's not risky at all.
As long as the system image didn't get modified (e.g. by mounting it via twrp) and you didn't tinker with your phone aside from flashing twrp, re-flashing the stock recovery is absolutely sufficent for getting back to a completely stock state.
The thing is that most people that flash twrp to modify their system partition in one way or another. As you wrote (and due to Android updates being block-based since Android 5), ota's will fail as soon as they notice that the system got modified.
The stock recovery on the other hand doesn't "care" whether your phone is modified or not.
The only problem that might arise is that people tend to re-lock their bootloader since they learned (while using older htc devices) that it would be necessary for flashing certain stock files (e.g. RUUs) or installing OTA's. The m9 won't boot if you re-lock the bootloader and the phone isn't completely stock. There are security checks which don't differentiate between wanted user customizations and critical software failures. Therefore, they will try to save the hardware from damages caused by the "failed" software (by preventing the phone from booting).
In addition, google's frp makes it impossible to re-un-lock the bootloader in such situations if "OEM unlock" isn't activated in the developer settings of the used rom.
That's why the readme thread discourages the average Joe and the average Jane from re-locking this phone.
Sent from my Moto X Style using XDA Labs

Thanks, but I went ahead and flashed a zip RUU for that firmware version, then flashed the nougat one afterwards

tmobile oos 11.0.1.2 need to root

Most of the directions involve rooting android 10.
there isnt really any info on rooting latest tmobile 11.0.1.2 firmware
i have bootloader unlocked and was rooted before accidental forced update to new firmware.
can someone clarify can i just flash global rom with patched boot image or because i am on tmobile i cant?
I cant find a download of the tmobile firmware to do the magisk patch boot image..
any help to get root back would be awsome
thanks

Fastboot flash recovery twrp.img
Fastboot reboot recovery
Adb sideload magisk.zip
Reboot

HueyT said:
Fastboot flash recovery twrp.img
Fastboot reboot recovery
Adb sideload magisk.zip
Reboot
Click to expand...
Click to collapse
Where are you getting the twrp?

I've been struggling with my phone as well. I own Tmobile OP7T in the US. I am able to convert it to international/global version and update to the latest 11.0.1.1 package. I am able to unlock SIM and unlock bootloader just fine.
However every time I try to use a patched magisk img to root my phone, my phone bricks. Every single time. I've used multiple patched img files on XDA for 11.0.1.1 and none works. And to get the phone working again, I have to use the MSMdownloadTool, revert back to Tmobile 10.0.0.13, unlock bootloader, install via flash-all.bat to international/global version, and download the OTA package to upgrade to 11.0.1.1, then I am unable to root the phone at all.
Any suggestions?

tintn00+xda said:
I've been struggling with my phone as well. I own Tmobile OP7T in the US. I am able to convert it to international/global version and update to the latest 11.0.1.1 package. I am able to unlock SIM and unlock bootloader just fine.
However every time I try to use a patched magisk img to root my phone, my phone bricks. Every single time. I've used multiple patched img files on XDA for 11.0.1.1 and none works. And to get the phone working again, I have to use the MSMdownloadTool, revert back to Tmobile 10.0.0.13, unlock bootloader, install via flash-all.bat to international/global version, and download the OTA package to upgrade to 11.0.1.1, then I am unable to root the phone at all.
Any suggestions?
Click to expand...
Click to collapse
recovery.img
drive.google.com
rename to twrp.img and move file to adb folder in windows10

HueyT said:
recovery.img
drive.google.com
rename to twrp.img and move file to adb folder in windows10
Click to expand...
Click to collapse
Yes I found the file after some digging earlier today.

tintn00+xda said:
I've been struggling with my phone as well. I own Tmobile OP7T in the US. I am able to convert it to international/global version and update to the latest 11.0.1.1 package. I am able to unlock SIM and unlock bootloader just fine.
However every time I try to use a patched magisk img to root my phone, my phone bricks. Every single time. I've used multiple patched img files on XDA for 11.0.1.1 and none works. And to get the phone working again, I have to use the MSMdownloadTool, revert back to Tmobile 10.0.0.13, unlock bootloader, install via flash-all.bat to international/global version, and download the OTA package to upgrade to 11.0.1.1, then I am unable to root the phone at all.
Any suggestions?
Click to expand...
Click to collapse
Did u slove it ? I have same problem