AT&T M7 on 4..4.2 does not see Lollipop update. - AT&T HTC One (M7)

Long story short I have an M7 running 4.4.2 on AT&T that I haven't touched in about a year. I just booted it up everything is working properly except when I go to Software Update it tells me the software is up to date and that I can check again in 24 hours.
I've tried rebooting, no luck. Any other ideas? Thanks!

When you say you haven't touched it in a year, do you mean you don't use the phone at all? Or that you just haven't updated or modified it? If you just don't use the phone and don't mind starting from scratch you can run the 7.23.502.1 RUU. You can download it directly from HTC, http://www.htc.com/us/support/rom-downloads.html. I used this a couple of weeks ago and everything went smoothly and the phone runs great.
If you don't want to go that route and want the OTA, some have suggested changing the date on your phone ahead a few days and trying Software Update again. It may trigger the update. I have never tried that so can't say for sure if it'll work. And I haven't seen the OTA zips posted to update it manually.

Related

[Q] Problem with verizon pushing updates

Well here is the issue, I bought the HTC Thunderbolt awhile ago. I then rooted my phone but left the original ROM on it since the custom roms were not stable. I noticed verizon was pushing me some update and I just ignored them. I woke up today to see my phone rebooted with the screen on an exsclamation point. And then my Thunderbolt keeps rebooting itself now. I tried going into ROM Manager to download a Custom ROM but the phone just reboots before I can do it. I just installed Liquid Gingersense v1.6 rom with the MR2 OTA Radio which said it installed just fine after installing the Liquid Gingersense rom. I went through setting up the google account fine and after it booted to the main screen now my phone boots all over again, get stuck at htc screen for a bit then loads the phone fine then boots again. I am really not sure what the heck is going on. I am new to the MR2 OTA Radio since I cam from the Droid 1. So I hope it was not the install order I did it. I Have turned off the phone booted it with still same rebooting over and over issue. If anyone has idea's please let me know. Much appreciated. Thanks
I'm in the same boat. I have wiped the SD card and done a factory reset on the phone. It is no longer rooted, as I can't install and run apps requiring root permission. The update fails every time it tries to install, I also get the exclamation point android screen when the update tries to install. I'll take the update, I don't care. I just want a reliable phone again.
I'm seeing this issue come up a lot. Some of you folks seem pretty upset by it, and reasonably so. Search through the threads and you'll find you solution.
For those who are STILL running that antique and wildly obsolete ROM that the jcase rooting process leaves you with, I'd like to set a few facts before you. First of all, that ROM wasn't provided as a long-term daily driver. It's OLD and it's not very efficient with the battery. Second, simply because it's stock doesn't mean it's inherently stable. It's probably less stable than the custom ROMs out there. Third, the only ROMs really struggling with stability were the 2.01 RUU gingerbread builds. That build is obsolete, but not nearly as obsolete as the ROM that the rooting process leaves you with. The stability issues with the second OTA had nothing to do with the ROM, but rather, the radio that came with the RUU. In short, it's foolhardy to believe that custom ROMs are somehow inherently dangerous or unstable.
I'd like to suggest to whoever might be running the rooted ancient ROM the rooting process leaves you with to abandon it at your earliest convenience. Flash an MR2 radio, and if you like stock, use the stock rooted debloated ROM based on the 1.70 RUU. If you decide not to do this, and your phone auto-accepts the update, you'll probably lose everything on the phone trying to get it working again. Save yourself that hassle. Flashing ROMs isn't hard and people do it everyday.

[Q] Disabling OTA Updates?

Does anybody know a way to disable OTA updates on Thunderbolt? I have a rooted phone, and don't want to deal with updating for now. My problem is the OTA updates cause the phone to reboot, the update fails and then I have to reboot into recovery, clear the caches, reboot again. It's a pain, and it seems to be happening at least once a day now.
Any hacks out there I can apply to disable the OTA updates?
botzen67 said:
Does anybody know a way to disable OTA updates on Thunderbolt? I have a rooted phone, and don't want to deal with updating for now. My problem is the OTA updates cause the phone to reboot, the update fails and then I have to reboot into recovery, clear the caches, reboot again. It's a pain, and it seems to be happening at least once a day now.
Any hacks out there I can apply to disable the OTA updates?
Click to expand...
Click to collapse
If you have Titaniumbackup Pro then just freeze the update/updater apk. If not, I would suggest getting it, it is well worth the cost.
Great suggestion. I have TiBu Pro and have frozen the two Update apps I found in the list along with "VZW Package Installer 1.0" and "Field Test 2.1-update1" and "Field Trial 2.2.1", having done the last three just now. It did try to do yet another update a few hours ago, so we'll have to see if the last three do the trick.
Anybody got any other suggestions for Apps I should freeze to prevent OTA updates?
Update: None of the items I've frozen seems to have made a difference. Still looking for other ideas.
I'm thinking it was DM.apk or something similiar that controlled ota updates. I don't have a stock rom running atm so i can't be sure. When you find the correct one you won't be able to get to the update phone screen from settings any longer. Wish i could be more help but i just can't remember.
Sent from my HTC ThunderBolt using Tapatalk
I was having that same problem and I just broke down and applied the update. I used clockwork rom manager and a rooted/deodexed update file that I found on the forums (linked from androidpolice, i think). Flashed the update, without wiping the current setup, then flashed the radio from the bootloader. Worked like a charm. I've got the update, it's not searching for more, and it reinstalled all the bloatware that I deleted instead of freezing when I got the phone. I went back through and freezed all the bloat junk, and my TB is running better than ever. Oh, and I'm just running a rooted stock rom.
I too suffered the same problem. I just ended up installing a custom rom to get rid of it for good. Best decision I ever made, I really like the Synergy build.

OTA

my phone just started recieving an OTA froom verizon i am rooted on nils rom. i didnt knoiw a OTA was even scheduled. anyone else getting this?
Is this a different OTA from the one that was pushed out a week or 2 ago?
ota????
You gotta read the forums first bud. I all over the place.
The OTA gives you a new radio & a few other minor things, but you need to relock/unroot & reflash it to stock ROM to get it.
ok. got my phone 3 days ago, kept it stock for 2 days figured i would get the OTA then if it wasnt preinstalled, thanks

/old school winmo user android noob question

Is there a way to stop the auto updates on Rezound?
I have a bionic, and might sell it since I'm a HTC fan and love HTCs. But the biggest problem I have ran into is the auto updates not updating since I ran the root/custom ROM thing on the phone. I had it plugged in last night and woke up to my boss banging on my door to wake up for work since it tried to auto update. If I can just disable the automatic OTA updates I would be happy.
I'm sure there's a simple setting to change somewhere...and I apologize since I haven't had acomputer for like a year and I have only spent the year before programming so the only thing I really know mobile wise is Windows Mobile... Sadly, I miss WinMo lol.
/Help an old man.
Edit: by not updating I mean it will try to update automatically without my permission, and will load the bootloader screen and will just error out on the bootloader screen and will not reboot the phone so my alarms will not go off in the morning... I cannot have this. if this is the case, the rezound is for sale tomorrow...but I don't want it to be. I know there has to be a simple setting somewhere...
Edit2: I really need to change my signature lol. I haven't changed it in 2+ years.
codybear said:
Is there a way to stop the auto updates on Rezound?
I have a bionic, and might sell it since I'm a HTC fan and love HTCs. But the biggest problem I have ran into is the auto updates not updating since I ran the root/custom ROM thing on the phone. I had it plugged in last night and woke up to my boss banging on my door to wake up for work since it tried to auto update. If I can just disable the automatic OTA updates I would be happy.
I'm sure there's a simple setting to change somewhere...and I apologize since I haven't had acomputer for like a year and I have only spent the year before programming so the only thing I really know mobile wise is Windows Mobile... Sadly, I miss WinMo lol.
/Help an old man.
Edit: by not updating I mean it will try to update automatically without my permission, and will load the bootloader screen and will just error out on the bootloader screen and will not reboot the phone so my alarms will not go off in the morning... I cannot have this. if this is the case, the rezound is for sale tomorrow...but I don't want it to be. I know there has to be a simple setting somewhere...
Edit2: I really need to change my signature lol. I haven't changed it in 2+ years.
Click to expand...
Click to collapse
whats auto updating ???? your apps or your phone firmware ????
charismakid said:
whats auto updating ???? your apps or your phone firmware ????
Click to expand...
Click to collapse
phone firmware. It tries to update the phone firmware and has been with some
BS update I already have in my rom but it boots into the bootloader and fails there and stays in the bootloader and just chills in the bootloader all night. Which causes my boss banging on my door ten minutes before my shift. lol.
codybear said:
phone firmware. It tries to update the phone firmware and has been with some
BS update I already have in my rom but it boots into the bootloader and fails there and stays in the bootloader and just chills in the bootloader all night. Which causes my boss banging on my door ten minutes before my shift. lol.
Click to expand...
Click to collapse
Should only try to update if it detects your firmware version as 1.02.605.6, the first Gingerbread build that shipped with the phone. It is trying to apply the 2.01.605.11 Over-The-Air update from February, the latest official build released.
Usually fails from being on a Custom ROM, low battery, or bad download. Aside from stock ROM, only had this update issue on one old custom GB ROM from the Development section.
So, what ROM setup do you have? There is probably a solution on the forum to edit build.prop firmware version or something to get the update refused. Will take a look. Long term solution is to back up data and update to a newer GB ROM based on the OTA firmware, or do all the stuff to get ICS, Unlock the phone, and S-off once you read up more.
i was once on winmo too i had an omnia but if you have a custom rom on the rezound it will not update
First off, thanks for the replies. Been busy with work lately and haven't had a chance to hop back on to reply.
PhantasmRezound said:
Should only try to update if it detects your firmware version as 1.02.605.6, the first Gingerbread build that shipped with the phone. It is trying to apply the 2.01.605.11 Over-The-Air update from February, the latest official build released.
Usually fails from being on a Custom ROM, low battery, or bad download. Aside from stock ROM, only had this update issue on one old custom GB ROM from the Development section.
So, what ROM setup do you have? There is probably a solution on the forum to edit build.prop firmware version or something to get the update refused. Will take a look. Long term solution is to back up data and update to a newer GB ROM based on the OTA firmware, or do all the stuff to get ICS, Unlock the phone, and S-off once you read up more.
Click to expand...
Click to collapse
You know, I spaced that out. I know I was running the latest before I flashed it, and I just assumed it was an up to date ROM. I'll have to check and see what version of GB it is, otherwise I'll just get a ICS ROM on it this weekend since I have time. I guess that's what you get for rushing through and doing it drunk.
I am running the Business Gingersense ROM btw.
yojoe600 said:
i was once on winmo too i had an omnia but if you have a custom rom on the rezound it will not update
Click to expand...
Click to collapse
It attempts to update, but boots into the recovery (I think I might have said bootloader in my OP), and then fails to install the update due to the custom ROM, but sits in the recovery menu and does not reboot automatically.
But I think the post above yours explained why it was happening...I was assuming it was an up to date GB ROM since I read the update was from February and it's been a few months, but now that I have time this weekend I'll be able to get things fixed.
Thanks again to both of you for replies. (And sorry for the bump in the threads guys)

Random restarts on custom roms?

Just got s-off on my DNA but installing a custom Rom makes the phone randomly freeze and reboot. Tried CM11, carbon, and a few others. The time before restarting varies wildly from 10 seconds after boot to 20-30 minutes. It seems more frequent when the screen is on or when plugged into my PC but I could just be imagining things or could be coincidence.
I have flashed and rommed many phones over the years and this one really has me stumped.
I cleared the cache and dalvik and formatted the system partition before installing the Rom and gapps. I have tried multiple roms and multiple versions of gapps as well with no luck. I have superCID of 11111111 from the original unlock process if that makes any difference. I have currently RUUd back to 3.06 for now and it seems perfectly stable on the stock Rom. Any help would be appreciated!
renegadeone8 said:
Just got s-off on my DNA but installing a custom Rom makes the phone randomly freeze and reboot. Tried CM11, carbon, and a few others. The time before restarting varies wildly from 10 seconds after boot to 20-30 minutes. It seems more frequent when the screen is on or when plugged into my PC but I could just be imagining things or could be coincidence.
I have flashed and rommed many phones over the years and this one really has me stumped.
I cleared the cache and dalvik and formatted the system partition before installing the Rom and gapps. I have tried multiple roms and multiple versions of gapps as well with no luck. I have superCID of 11111111 from the original unlock process if that makes any difference. I have currently RUUd back to 3.06 for now and it seems perfectly stable on the stock Rom. Any help would be appreciated!
Click to expand...
Click to collapse
check my thread in the same section, mine started doing this two nights ago. I don't know why it started, my phone was fine prior to this. I did nothing to it, had been running Venom for a while, and two nights ago it started rebooting randomly and wildly. I have switched ROMs twice since then and it has not stopped. Like you said, it tends to be when the screen is on or gets plugged up. But unfortunately mine is doing it a lot on answering phone calls. I don't know if we are having same issure or what.
Possibly
lemonoid said:
check my thread in the same section, mine started doing this two nights ago. I don't know why it started, my phone was fine prior to this. I did nothing to it, had been running Venom for a while, and two nights ago it started rebooting randomly and wildly. I have switched ROMs twice since then and it has not stopped. Like you said, it tends to be when the screen is on or gets plugged up. But unfortunately mine is doing it a lot on answering phone calls. I don't know if we are having same issure or what.
Click to expand...
Click to collapse
I don't know if we are having the same issue it may be that we are though. I am on stock 3.06 not one reboot since I went to work this morning. Get home, install the newest twrp (it is removed in the RUU process), install cm11 snapshot m5, and the appropriate gapps. I got through setup to the point of adding my gmail and it froze and rebooted. I tried cwm recovery too but it made zero difference
TBH my screen is shattered really bad and I was going to replace it but I don't want to if I have to run stock roms forever. I was running one of the original Venom roms before s-off was possible, but then I broke the screen and switched back to my droid bionic but now I can afford the new LCD so I want to get this one running
renegadeone8 said:
I don't know if we are having the same issue it may be that we are though. I am on stock 3.06 not one reboot since I went to work this morning. Get home, install the newest twrp (it is removed in the RUU process), install cm11 snapshot m5, and the appropriate gapps. I got through setup to the point of adding my gmail and it froze and rebooted. I tried cwm recovery too but it made zero difference
TBH my screen is shattered really bad and I was going to replace it but I don't want to if I have to run stock roms forever. I was running one of the original Venom roms before s-off was possible, but then I broke the screen and switched back to my droid bionic but now I can afford the new LCD so I want to get this one running
Click to expand...
Click to collapse
Did you use the proper recovery stated in the thread to flash the rom, have you installed any new apps recently? Does it happen when you run the phone in safemode? Have you tried Performing an RUU and the unlocking and installing a custom rom again?
Did all that
Jaggar345 said:
Did you use the proper recovery stated in the thread to flash the rom, have you installed any new apps recently? Does it happen when you run the phone in safemode? Have you tried Performing an RUU and the unlocking and installing a custom rom again?
Click to expand...
Click to collapse
I have done all of that stuff multiple times
I haven't installed any apps at all on it. This phone is basically brand new, I got it right when they launched. I shattered the screen like 3 days after I got it, and tucked it in a drawer. It has been sitting there ever since.
I have another piece to add to the puzzle. While it has the stock ROM installed it seems to get service and work just fine, but when I install the custom ROMS it has absolutely zero cell connectivity (though WiFi works fine.)
Going into the settings reveals that on the custom roms it shows the IMEI and MEID as Unknown, and the ICCID is listed as Unknown as well. If I try to change the network mode (to LTE/CDMA or any one of the many available options) it says com.phone has crashed.
After the RUU process I have my proper MEID and ICCID showing in the settings panel, and service returns.
Can't flash radio?
After discovering the issues with the service while on custom ROMS I wondered if the radio had something wrong with it.
I tried to manually reflash the radio via fastboot (fastboot flash radio radio.img).
I tried this both in standard fastboot as well as in the rebootRUU mode, but both times I get an error that says remote not allowed. Could my bootloader somehow still be locked? The flag in bootloader mode says "Unlocked" but I unlocked manually after obtaining s-off rather than doing it officially via HTCdev. just trying to explore all options
My phone did that at one point. I had to re-lock and RUU back to 100% stock. I then unlocked my phone with Rumrunner S-Off tool. Flashed a Sense 6 ROM and has been working fine since.
Fixed!
So this problem is fixed!! I am not 100% sure what did the trick, so I will post my solution here in case anybody else experiences a similar issue. I won't go into too much detail with these instructions as all the tools are here: http://forum.xda-developers.com/showthread.php?t=2612740
I first downgraded to the 1.15 hboot and radio. I had to rebootRUU and flash them there as it can't be done directly in fastboot as far as I know.
Do them one at a time (flash the hboot, then reboot-bootloader, then rebootRUU then flash the radio, then reboot bootloader again.)
After doing this I tried to run the RUU exe but it came up with an error that it could not update my phone, so I did the manual Alt 3.06 RUU.
This seemed to work great, restarted the phone and saw the stock rom. I then changed from superCID 11111111 back to the stock CID, relocked my bootloader went back to s-on status. At this point I ran the RUU.exe again just to make sure everything was as stock as could be.
Got that all finished, ran RumRunner again, installed CM11 and no reboot for nearly 24 hours. Pretty sure all is well!
renegadeone8 said:
I don't know if we are having the same issue it may be that we are though. I am on stock 3.06 not one reboot since I went to work this morning. Get home, install the newest twrp (it is removed in the RUU process), install cm11 snapshot m5, and the appropriate gapps. I got through setup to the point of adding my gmail and it froze and rebooted. I tried cwm recovery too but it made zero difference
TBH my screen is shattered really bad and I was going to replace it but I don't want to if I have to run stock roms forever. I was running one of the original Venom roms before s-off was possible, but then I broke the screen and switched back to my droid bionic but now I can afford the new LCD so I want to get this one running
Click to expand...
Click to collapse
thats kinda crazy... i was on bionic before my dna. my screen on DNA is shattered like crazy. thought about going back to bionic temporarily, instead i'm gonna replace my screen and RUU and see if it fixes my problem
lemonoid said:
thats kinda crazy... i was on bionic before my dna. my screen on DNA is shattered like crazy. thought about going back to bionic temporarily, instead i'm gonna replace my screen and RUU and see if it fixes my problem
Click to expand...
Click to collapse
Good news and bad news. The good news is for you!!! I think I figured out what the problem was. It seems to be an issue either with using an older radio, or an older hboot on a newer ROM. I don't know why exactly, but the RUU process was not properly updating my radios. This may be because I ran an RUU while unlocked at one point (every guide I see is very adamant about relocking before the RUU process.)
The bad news is that I ordered a new LCD for my DNA, and I ruined my phone trying to do the repairs. It is by FAR the worst phone I have ever had to work on. I have replaced LCD's in Galaxy devices, Iphones/ipod touches, laptops, TV's, and one in a smartwatch and have never hurt a thing. Got my DNA back together and it flat out wont turn on I don't know what the problem is, but something is fried. Hope you have better luck than me!

Categories

Resources