Okay, so here's the deal.
I have an AT&T HTC One that was running 4.4 Kit Kat (Click: this ROM) and is S-OFF via RumRunner. I am running the latest TWRP recovery.
Yesterday I got prompted for an OTA and accepted it (in the past, with GPE ROMs, it would just reboot to recovery and do nothing). This is the only way I know of to get rid of the annoying "System update available" notification. I figured it wouldn't do anything and I would simply reboot and be good for a few more days until it prompted again. Low and behold, it actually updated my phone to 4.4.2.
Now, I'm having some issues.
I was a user of DashClock Widget...but now I use Better DashClock. However, this app is now prompting me to download a key. When I try to download the key from the Play Store, I get the message:
Error: Couldn't install on USB storage or SD Card.
SwiftKey Keyboard has the same issue.
Other apps (such as ES File Explorer, ESPN, Fandango, etc. update just fine).
-------------
I have read a bunch of posts that suggest cleaning up temp files (which don't exist on my phone) and to download SELinux Mode Changer and change the mode to Passive...but to no avail.
Can someone help me? Is this the developers issue or did my phone do something wonky?
Thanks!
Exactly the same problem here. I've narrowed it down to paid apps that won't install. Followed the same possible solutions in the 1st post, nothing works. HTC One GE 4.4.2.
IlyaKol said:
Okay, so here's the deal.
I have an AT&T HTC One that was running 4.4 Kit Kat (Click: this ROM) and is S-OFF via RumRunner.
Yesterday I got prompted for an OTA and accepted it (in the past, with GPE ROMs, it would just reboot to recovery and do nothing). This is the only way I know of to get rid of the annoying "System update available" notification. I figured it wouldn't do anything and I would simply reboot and be good for a few more days until it prompted again. Low and behold, it actually updated my phone to 4.4.2.
Now, I'm having some issues.
I was a user of DashClock Widget...but now I use Better DashClock. However, this app is now prompting me to download a key. When I try to download the key from the Play Store, I get the message:
Error: Couldn't install on USB storage or SD Card.
SwiftKey Keyboard has the same issue.
Other apps (such as ES File Explorer, ESPN, Fandango, etc. update just fine).
-------------
I have read a bunch of posts that suggest cleaning up temp files (which don't exist on my phone) and to download SELinux Mode Changer and change the mode to Passive...but to no avail.
Can someone help me? Is this the developers issue or did my phone do something wonky?
Thanks!
Click to expand...
Click to collapse
I had a similar problem. I downloaded the 4.4.2 OTA update and tried flashing it with TWRP three different times. All three times I got that same error message with some apps. It was extremely frustrating. I ended up flashing the stock 4.4 recovery and then flashing the update. It worked perfectly and the problem went away. I then reflashed TWRP.
arfon said:
Exactly the same problem here. I've narrowed it down to paid apps that won't install. Followed the same possible solutions in the 1st post, nothing works. HTC One GE 4.4.2.
Click to expand...
Click to collapse
I had a similar experience. Paid apps would not install from Play Store. Amazon app store or F-Droid apps would install.
But my journey was that I had a 4.4 GPE device suffering through an issue where I can't get my bootloader to unlock. So when 4.4.2 came out I wasn't getting the OTA so I tried flashing just the firmware package from the OTA download. That's when I was getting this error (after a factory reset).
But then next day I got the real OTA and after that the problem went away. So for me it was a firmware issue in that it wasn't the right firmware for my OS.
Weird that you are running 4.4.2 but having this issue. Any chance you didn't come to have 4.4.2 the "natural" way?
msw141 said:
I had a similar experience. Paid apps would not install from Play Store. Amazon app store or F-Droid apps would install.
But my journey was that I had a 4.4 GPE device suffering through an issue where I can't get my bootloader to unlock. So when 4.4.2 came out I wasn't getting the OTA so I tried flashing just the firmware package from the OTA download. That's when I was getting this error (after a factory reset).
But then next day I got the real OTA and after that the problem went away. So for me it was a firmware issue in that it wasn't the right firmware for my OS.
Weird that you are running 4.4.2 but having this issue. Any chance you didn't come to have 4.4.2 the "natural" way?
Click to expand...
Click to collapse
Update was OTA last night, so I guess its as natural as it comes.
arfon said:
Update was OTA last night, so I guess its as natural as it comes.
Click to expand...
Click to collapse
Yeah...my process was as natural as possible.
I was on 4.3 at first...so when I was going to 4.4 KitKat I first flashed back to some basic stock Sense ROM to run RumRunner and attain S-OFF. Then I COMPLETELY NUKED my phone and went to 4.4 KitKat. Had no problems, got the OTA, and now this.
It's aggravating, that's for sure.
I really don't want to completely wipe my phone again and have to re-setup all of my home screens, etc.
I received the OTA which installed despite me having TWRP, not stock recovery (as per http://forum.xda-developers.com/showpost.php?p=48586329). Now I have the same issue installing paid apps (the ones I had already installed before the OTA disappeared off the device).
Short of starting from scratch, I'm at a bit of a loss for a solution...
Nick
Sounds like this is wide-spread...or at least amongst the people who are running newer GPE ROMs on their Ones.
im having the exact same issues here
artmunkie said:
I had a similar problem. I downloaded the 4.4.2 OTA update and tried flashing it with TWRP three different times. All three times I got that same error message with some apps. It was extremely frustrating. I ended up flashing the stock 4.4 recovery and then flashing the update. It worked perfectly and the problem went away. I then reflashed TWRP.
Click to expand...
Click to collapse
Can you point me to where you got the stock recovery from please?
Fixed
It looks like this is all to do with custom recovery and OTA updates. I have TWRP installed. This morning I flashed stock recovery. I then put the OTA update file on the phone storage. Then booted into the stock recovery (which is the first time I've seen it, it would be nice if it was the last as it's tricky to get into), then flashed the 4.2.2. update from there. Once I booted the phone again all my paid apps reappeared. No data lost in the process. I'm not sure if going back to TWRP not will cause the problem again, so for now I'll stick with stock recovery....
arfon said:
It looks like this is all to do with custom recovery and OTA updates. I have TWRP installed. This morning I flashed stock recovery. I then put the OTA update file on the phone storage. Then booted into the stock recovery (which is the first time I've seen it, it would be nice if it was the last as it's tricky to get into), then flashed the 4.2.2. update from there. Once I booted the phone again all my paid apps reappeared. No data lost in the process. I'm not sure if going back to TWRP not will cause the problem again, so for now I'll stick with stock recovery....
Click to expand...
Click to collapse
Can you please detail the procedure ?
If possible including where you got the files (OTA and stock recovery ) and how to put OTA on the sdcard to "provoque" que update.
Thanks in advance!
franciscols said:
Can you please detail the procedure ?
If possible including where you got the files (OTA and stock recovery ) and how to put OTA on the sdcard to "provoque" que update.
Thanks in advance!
Click to expand...
Click to collapse
This.
Also, you left 4.4.2 on the device and just 're-applied' the OTA update? Or did you go back to a NANDROID backup of you on 4.4 or 4.3?
arfon said:
Can you point me to where you got the stock recovery from please?
Click to expand...
Click to collapse
Here you go! I can't remember the thread where I found it, so the file is attached. Just to be clear, this is the stock Android 4.4 recovery for the HTC One GPE.
artmunkie said:
Here you go! I can't remember the thread where I found it, so the file is attached. Just to be clear, this is the stock Android 4.4 recovery for the HTC One GPE.
Click to expand...
Click to collapse
So I flash this recovery and then flash the OTA update (this one?) and I should be good?
IlyaKol said:
So I flash this recovery and then flash the OTA update (this one?) and I should be good?
Click to expand...
Click to collapse
Yeah, that's about it. I used adb to flash the stock recovery to replace TWRP, then used the stock recovery to flash the same update you linked to. After it was done updating I reflashed TWRP. And don't forget to make a nandroid.
Thank you! Will report back when I'm done!
What is the fastboot command to flash the OTA zip file?
I'm back on the stock recovery...phone is still booting/working so I just need to do the OTA part now.
IlyaKol said:
What is the fastboot command to flash the OTA zip file?
I'm back on the stock recovery...phone is still booting/working so I just need to do the OTA part now.
Click to expand...
Click to collapse
Sorry, hectic day at work. I should have said that I applied the update with the stock recovery. Not fastboot.
I basically used the guide linked below to flash the update.
Read Step 2
http://www.androidpolice.com/2012/1...e-nexus-7-now-manual-download-link-available/
artmunkie said:
Sorry, hectic day at work. I should have said that I applied the update with the stock recovery. Not fastboot.
I basically used the guide linked below to flash the update.
Read Step 2
http://www.androidpolice.com/2012/1...e-nexus-7-now-manual-download-link-available/
Click to expand...
Click to collapse
What if you don't have an "apply from adb" option?
I have:
- reboot system now
- apply from sd card
- apply from phone storage
- apply from cache
- wipe data/factory reset
- wipe cache partition
Can't I just open a ADB shell while on the fastboot USB option?
Hi,
I've just upgraded the OS of my HTC One to 4.4 with Sense 5.5 and rooted the handset.
I took the majority of information and downloads from here:
http://htconeroot.com/htc-one-stock-roms/android-4-4-kitkat-sense-5-5-stock-rom-for-htc-one/
while the rooting stuff I grabbed from here:
http://htconeroot.com/htc-one-root/how-to-root-htc-one-windowsmaclinux/
So ok this is my 3rd OS upgrade with root so in a basic sense I did this:
- Updated TWRP to version 2.7.x
- Used TWRP recovery WIPE option to format / (root)
- Installed the 4.4 stock ROM from above link
- TWRP then asked me if I would like to root the device and so I said ok to that
- Booting into the OS everything was fine and I had the SU-Root icon in the Apps menu
I'm not sure what happened if the battery got drained or so but in anycase after a restart the handset was no longer rooted??
As I have the 2.65 SU-ROOT Zip file on my storage partition I went back to TWRP and Install then clicked on the Zip file and re-rooted the device; then wiped the cache and booted back into the OS.
For some reason now the phone isn't able to be rooted at all? I am pretty sure I had similar behavior with Android 4.3, though the initial stock build was absolutely fine.... I think I managed to get from 4.1 to 4.2 successfully.
Will I need to format the handset again then re-install the ROM and re-root or is something else going on which I'm unaware of??
I've also noticed that the device becomes un-rooted each time the battery goes low or dies for some reason... a persistent root would be nice as I have many apps needing full root access; not to mention being able to work with the full Android system too.
Would anyone be able to suggest anything? Thanks!
JohnnySSH said:
Hi,
I've just upgraded the OS of my HTC One to 4.4 with Sense 5.5 and rooted the handset.
I took the majority of information and downloads from here:
http://htconeroot.com/htc-one-stock-roms/android-4-4-kitkat-sense-5-5-stock-rom-for-htc-one/
while the rooting stuff I grabbed from here:
http://htconeroot.com/htc-one-root/how-to-root-htc-one-windowsmaclinux/
So ok this is my 3rd OS upgrade with root so in a basic sense I did this:
- Updated TWRP to version 2.7.x
- Used TWRP recovery WIPE option to format / (root)
- Installed the 4.4 stock ROM from above link
- TWRP then asked me if I would like to root the device and so I said ok to that
- Booting into the OS everything was fine and I had the SU-Root icon in the Apps menu
I'm not sure what happened if the battery got drained or so but in anycase after a restart the handset was no longer rooted??
As I have the 2.65 SU-ROOT Zip file on my storage partition I went back to TWRP and Install then clicked on the Zip file and re-rooted the device; then wiped the cache and booted back into the OS.
For some reason now the phone isn't able to be rooted at all? I am pretty sure I had similar behavior with Android 4.3, though the initial stock build was absolutely fine.... I think I managed to get from 4.1 to 4.2 successfully.
Will I need to format the handset again then re-install the ROM and re-root or is something else going on which I'm unaware of??
I've also noticed that the device becomes un-rooted each time the battery goes low or dies for some reason... a persistent root would be nice as I have many apps needing full root access; not to mention being able to work with the full Android system too.
Would anyone be able to suggest anything? Thanks!
Click to expand...
Click to collapse
I think there is an update for supersu
please google it
if yes than move it to your phone and flash it in the recovery
Thanks I managed to find version 1.94 which worked fine:
http://download.chainfire.eu/396/
I recieved the first OTA update for lollipop and it installed correctly. Now I went to download the large 700+mb 2nd OTA update and after the download completes my phone resets. It goes into installing the update, however about 1/4 of the way through the update, i get the dead droid screen flash on my screen and then my phone reboots back to 4.4.4 and tells me that the updated was unsuccessful. I have a moto x XT1060 dev ed, build KXA21.12-L1.26-4 on system version 212.166.4.
I'm stumped on what to try next. I have already returned everything back to stock and downloaded all updates and I get to the same point and get the same results. I've wiped all data, system, cache, and davlik, installed stock recovery and still get the same results. i've removed super user rights to see if that would work but it did not. I'm at a lose at what to try next. Anyone have any other ideas?
[email protected] said:
I recieved the first OTA update for lollipop and it installed correctly. Now I went to download the large 700+mb 2nd OTA update and after the download completes my phone resets. It goes into installing the update, however about 1/4 of the way through the update, i get the dead droid screen flash on my screen and then my phone reboots back to 4.4.4 and tells me that the updated was unsuccessful. I have a moto x XT1060 dev ed, build KXA21.12-L1.26-4 on system version 212.166.4.
I'm stumped on what to try next. I have already returned everything back to stock and downloaded all updates and I get to the same point and get the same results. I've wiped all data, system, cache, and davlik, installed stock recovery and still get the same results. i've removed super user rights to see if that would work but it did not. I'm at a lose at what to try next. Anyone have any other ideas?
Click to expand...
Click to collapse
I was having this same problem, but here is the process I went through to get through the full update to 5.1:
I saw this post this morning and started with it: http://forum.xda-developers.com/moto-x/general/help-lollipop-update-unlocked-bootloader-t3201426 I had previously downloaded the version of 4.4.4 referenced in it.
I don't have RDSLite installed so I moved on to this post: http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 and used Option #5 since I already the Android SDK tools on my computer. After going through all the steps I have successfully stepped through all three updates, rebooting the phone after each whether it helps or not. My phone is currently optimizing apps after the second 5.1 update.
For reference I was on the most current version of 4.4.4, rooted with TWRP with no modifications to any system/bloatware apps. I originally tried Option #6 in the above thread which allowed me to take the first 5.1 update but the second update failed in the same way you described.
Hope this helps, and good luck!
Thanks for the post. I was reading through that post late last night and I was going through option #2. I didn't read further down to option #5, but that worked perfectly. My phone is optimizing apps as we speak.
hi
all, i have nexus 6 device with 6.0 MRA58R and open bootloader and it was update by the device from google,still before that i try to do root and didn't succeedwith 5.1, so i go back to 5.1 and it was update as i said but the device is stuck by the start or just by regular use...something is wrong and i don't know what, there is also sound when it stuck like A screech sound and it stuck
what to do next?
thanks
If your bootloader is unlocked, as mentioned in your other thread, download a stock image from Google and flash its components (except userdata.img) using ADB. As a result of your tinkering, something got messed up on the device, and flashing the stock image should resolve that.
tried these ...didn't help,it stuckes even after good flash with adb cause with OTA it stucks at the middle
You flashed MMB29Q from the shamu section of the page here? That is the absolute latest factory image available. There should be NO OTA update available.
first of all i tried to download the OTA cause i was with root and did unroot and i want to saw thet it get's the OTA's correct ,then i installed the version as you write, but still when i start the wifi or in regular use the device can be stuck and restart.
any idea to solve it? even in safe mode it stucks
No, not really. Like you mention in your other thread, it appears to be a hardware problem.
For the record, downloading the OTA updates is a waste of time when the latest factory image is available. When you get your replacement device, assuming it's not already on 6.0.1, install the image from the link I gave you, as it already includes in the image all the updates Google has released for Android 6.0.1.
final edit: finally got the officiall RUU to work
installing the microsoft files within this edit below allowed me to install the RUU rather than it auto-crashing after accepting the TOS (its in reference to another HTC phone but it still works for the 510)
and I just did this on the latest pre-Anniversary edition of Windows 10, for whatever reason the in-rom/phone installer would download about 56mb of an "update" and when telling it to install would reboot and get stuck on the bootloader screen (the screen you see when holding VOL down and PWR) and not proceed, not to mention it only was going to install 1.11.506.1, now I have the actual latest cricket version 1.11.506.8 installed
im not 100% certain if the following segmented edit file is needed or if you will be able to install the RUU directly overtop of CM or any other ROM you had, I would try first with the official RUU and if it only says "update" then install the ROM file in the segment below this
http://forum.xda-developers.com/showpost.php?p=53081344
main reason for doing this is horrible battery life and annoying "finding GPS" issues with the CM11 versions for the 32bit GSM phone basically making it useless to utilize gmaps offline mode and my phone being drained entirely after a normal day usage vs the "bloated" stock ROM which is at 80% each day over the last week of each days use.
and zero SIM usability with the CM12.1 version making it virtually pointless, might as well just install a linux OS on it if that was the only choice.
================================================================
first edit:
found a copy of original non-updated cricket ROM here
http://forum.xda-developers.com/showpost.php?p=57807126&postcount=10
===========================================
original post:
I have unlocked bootloader and TWRP installed.
I downloaded the stock zip from htcdev but its missing META-INF according to installing process in TWRP. trying to recover it wont work either because when you extract the zip file and put those in the TWRP backup folder, TWRP doesnt see it as a backup option
The custom "stock" debloated ROM's arent a suitable replacement because they are all built on 4.4.2 and don't have the dot 3 update which HTC pushed out for this phone with latest features/security.
do I have to relock the bootloader or what?
edit
answer posted at the top of the OP
===============
okay so the new issue is that HTC pushed out a system update from the stock but when I go to install it, it reloads and ends up in the bootloader but doesnt install, I relocked the bootloader but its not working
I even tried to go into the TWRP recovery and install the ZIP that was downloaded to the Android folder in the phone but that didnt work either