• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [AT&T] OTA update won't download M7

K

Kurtis LeCompte

Lurker
So, my rooted One M7 got an OTA update notification, and I downloaded it over WiFi. When I went to install the update, it went into TeamWin recovery instead of updating. I thought it had something to do with the root, so I "unrooted" via the SuperUser app that came, and restarted my phone. Now when I check for AT&T software updates, it says I have the current version, when I don't. What do I do?
 
Never take OTA updates on an HTC unless you're a) not rooted, b) running the stock rom without any changes and it matches your firmware, and c) you have the stock recovery installed.

Iow, with the exception of the bootloader being relocked, your phone has to be in the same condition as it was just being you rooted it, or as it was at the last OTA if you toggle back and forth between the two.

Make sure that you have the latest TWRP installed, get your updates via a TWRP install zip from xda.
 
Yeah.

You never know if an update is just some bits of the operating system, or also radio firmware, or also recovery, or also a new bootloader.

If it can't verify the old bits first, the installer gets lost and can't decide what it's seeing or supposed to do.

If you need detailed help, one of us can move this to the One M7 rooting forum, let us know.
 
Alright. I made a backup, and I am in my console, and followed the long comment here to the fastboot flash zip firmware.zip part, but the "stock firmware" found here, when loaded makes it say "could not allocate 1476361152 bytes" and shows an error. I'm leaving this to one of you because I am honestly tired of rooting in general.
 
If you want to unroot the simplest way is to use a ROM Upgrade Utility (RUU), if one can be found for your branding and software version. You can find some suggestions for ATT RUUs in this thread if you want to try that.

For what you tried, you've not told us which of the many M7 firmware files in that location you tried to flash. If the device is S-On only some of them will work, and no, I've not managed to decode the various folders to work out which might match an ATT device (CID = CWS__001), and don't have time tonight to drag through the XDA thread to try to work out which ones might work for you.

The other alternative is to forget about the official upgrade and just install a custom ROM based on the latest OS release. The advantage of that is that it comes without operator bloat and you can get it weeks or months before the operator releases it.
 
The KitKat RUU, the JB RUU or the Lollipop one from XDA? I linked more than one in that thread.

So what exactly happened: you ran the RUU at it stopped with some message? If so, exactly what message? And what's the current state of the phone?
 
You must log in or register to reply here.
Back
Top Bottom