Related
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?
[Q&A] [ROM][I9295][4.4.2] Super WizCyan - S5 Style [debloated & deodexed + Addon Pac
Q&A for [ROM][I9295][4.4.2] Super WizCyan - S5 Style [debloated & deodexed + Addon Package]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][I9295][4.4.2] Super WizCyan - S5 Style [debloated & deodexed + Addon Package]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Hi everyone,
This ROM is great. every things are working well.
But I don't know how to change the "Right hard key's function. I don't want it show the "recent apps" when we press.
It should be a menu key when we using App.
Please support!
Thanks,
lamhcmute said:
Hi everyone,
This ROM is great. every things are working well.
But I don't know how to change the "Right hard key's function. I don't want it show the "recent apps" when we press.
It should be a menu key when we using App.
Please support!
Thanks,
Click to expand...
Click to collapse
In post# 1 under the downloads section, below version 03 you will find revert longpress to recents & menu. You can download and flash this zip through recovery and menu key will be as before.
no root after flashign WizCyan
After flashing WizCyan 4 with update 1 I don't have root access. I've tried reinstalling several times and I've also tried to install superSU on it's own using CWM, both the latest version and older versions, with no success. I've also tried to install just v4 but the problem persists. Does anybody have any clue on what could be wrong? I've had root on the phone using other ROMs. I use the latest CWM.
And yes, I chose no when promted to fix superuser in CWM. Although I have also tried to pres yes during one installation.
What version of cwm are you having? Also when you click on the supersu app what message do you get?
I used version 6.0.3.5. Today I installed 6.0.5 and redid the flashing of the update and also of superSU 2.16 by it self from CWM. No difference
When i press the superSU app I dont get any message really. Looking at the log it's as if though the app denies all apps access without asking. I tried changing the settings in superSU to allow all requests and then the phone passed the check with root checker and root apps also seem to work. No app is added to the SuperSu applist.
Gudiol said:
I used version 6.0.3.5. Today I installed 6.0.5 and redid the flashing of the update and also of superSU 2.16 by it self from CWM. No difference
When i press the superSU app I dont get any message really. Looking at the log it's as if though the app denies all apps access without asking. I tried changing the settings in superSU to allow all requests and then the phone passed the check with root checker and root apps also seem to work. No app is added to the SuperSu applist.
Click to expand...
Click to collapse
I would suggest that you do a clean install of the ROM, now that your recovery has been updated
Excessive consumption of battery
Sorry, but this was translated by google.
I found a big problem in version 4 and is the battery, prior to this version, the battery works well, the battery lasted the whole day, but now the battery hopefully enduring three hours.
Please, give solution to this problem or any suggestions, as I really like this ROM and do not want to change the other.
Thanks in advance.
srDosaps said:
Sorry, but this was translated by google.
I found a big problem in version 4 and is the battery, prior to this version, the battery works well, the battery lasted the whole day, but now the battery hopefully enduring three hours.
Please, give solution to this problem or any suggestions, as I really like this ROM and do not want to change the other.
Thanks in advance.
Click to expand...
Click to collapse
Will suggest to do a clean install and check and if not then report back. Anyone else facing this issue.. kindly report
srDosaps said:
Sorry, but this was translated by google.
I found a big problem in version 4 and is the battery, prior to this version, the battery works well, the battery lasted the whole day, but now the battery hopefully enduring three hours.
Please, give solution to this problem or any suggestions, as I really like this ROM and do not want to change the other.
Thanks in advance.
Click to expand...
Click to collapse
Ok, did some testing and found that some of the init.d scripts were eating battery therefore have posted an update in the OP removing these and battery consumption should be better after flashing this update.
can i install
i have 4.4.2 NE5 but DBT not PHN,can i install this rom on my firmware and do i need install first version 4 and then flash version 4 update 02?and how much memory i have after flashing this rom is ih still around 12 gb or less?
s4active user said:
i have 4.4.2 NE5 but DBT not PHN,can i install this rom on my firmware and do i need install first version 4 and then flash version 4 update 02?and how much memory i have after flashing this rom is ih still around 12 gb or less?
Click to expand...
Click to collapse
Sure, you can install on any firmware, but if you have wifi issues then you may need to flash modem or some other workaround. Just wipe data/factory reset and install version 04 followed by update 02. I am not sure on what you mean by memory but presume that you are referring to internal sd card. This will depend on what apps/features you install from the addon package and playstore. The ROM will not affect your internal sdcard space as it will be installed on the reserved system space.
Problem with Rom Super Wizcyan - S5 Style
Hello, first sorry by my english, its sucks, but ill try to explain my problem, i install the rom wizcyan - s5 style in my I9295 (of course), and follow all the instruction, like de developer says, starts normaly, but for example, when i push the screen mirroring button, the phone freeze an restart, and occasionally shows a message like "android core process stoped". do all the wipes, and install the 6.0.5 rom manager, all the proces finish ok, install the update, and occurs the same problem, i like this rom its cool , faster and light, without all the samsung crap, someone can help me please, thanks in advance.
Kaitenx said:
Hello, first sorry by my english, its sucks, but ill try to explain my problem, i install the rom wizcyan - s5 style in my I9295 (of course), and follow all the instruction, like de developer says, starts normaly, but for example, when i push the screen mirroring button, the phone freeze an restart, and occasionally shows a message like "android core process stoped". do all the wipes, and install the 6.0.5 rom manager, all the proces finish ok, install the update, and occurs the same problem, i like this rom its cool , faster and light, without all the samsung crap, someone can help me please, thanks in advance.
Click to expand...
Click to collapse
In case you want to use screen mirroring then you would need to install allshare from the addon package
I've been tinkering with trying to get WizCyan totally working on my device for a couple of days, but I can't for the life of me get Wifi working (at first it was root access, but that was fixed by upgrading CWM). Here is the exact process I've followed:
Updated CWM to 6.0.5 (PhilZ's version)
Did a factory reset from recovery (I didn't use the "Clean to install new ROM" function)
Installed WizCyan version 4, followed by update 2
Rebooted, attempted to configure WiFi -- failed.
Flashed the NE5 modem package from the links in the dev thread, using Odin 3.07 -- twice each, as instructed
Still can't get my Wifi to enable. The flash was successful, as I can see the correct baseband on the "about" screen, but it refuses to enable. I'm in Australia, but I believe this phone came from UAE -- would that make a difference to the way the modem interacts with the Wifi hardware? I pulled this info from logcat:
Code:
I/WifiManager( 1084): setWifiEnabled : true
I/WifiService( 882): setWifiEnabled: true pid=1084, uid=10008
E/WifiHW ( 882): ##################### set firmware type 0 #####################
E/WifiHW ( 882): Cannot open "/data/.cid.info": No such file or directory
E/WifiHW ( 882): ==========[WIFI] Station firmware load ===========
E/WifiHW ( 882): return of insmod : ret = -1, Exec format error
E/WifiStateMachine( 882): Failed to load driver
E/WifiStateMachine( 882): sendErrorBroadcast code:10
E/WifiController( 882): Wi-Fi driver is unstable. Received CMD_STATEMACHINE_RESET
In the mean time, I'm going to try to source either a local radio, or one from the original region, to see if that helps.
andycore said:
I've been tinkering with trying to get WizCyan totally working on my device for a couple of days, but I can't for the life of me get Wifi working (at first it was root access, but that was fixed by upgrading CWM). Here is the exact process I've followed:
Updated CWM to 6.0.5 (PhilZ's version)
Did a factory reset from recovery (I didn't use the "Clean to install new ROM" function)
Installed WizCyan version 4, followed by update 2
Rebooted, attempted to configure WiFi -- failed.
Flashed the NE5 modem package from the links in the dev thread, using Odin 3.07 -- twice each, as instructed
Click to expand...
Click to collapse
Can't get anything much from the logcat, it refers to a file that gets created on 1st boot you can try doing a factory reset from settings--> backup & restore--> factory data reset. Only backup your internal sd card before doing this as it will wipe your entire phone including internal sdcard and then reflash the modem.
JASONRR said:
Can't get anything much from the logcat, it refers to a file that gets created on 1st boot you can try doing a factory reset from settings--> backup & restore--> factory data reset. Only backup your internal sd card before doing this as it will wipe your entire phone including internal sdcard and then reflash the modem.
Click to expand...
Click to collapse
Well if I'm going to go that far, I may as well do it properly and completely restore the phone to stock and start again. When I bought it, the first thing I did was root, flash CWM and a CM based ROM -- it's probably worth starting fresh anyway, I'm only going to be using it for a couple more weeks until it's replacement arrives.
I'm currently downloading the latest firmware for my region (XSA), a 4.2.2 based MK3 build from the end of last year -- do you think I'd have better chances if I restored to a 4.4.2 build (like NE5), or should it not matter if I completely reset the phone to factory settings/software?
andycore said:
Well if I'm going to go that far, I may as well do it properly and completely restore the phone to stock and start again. When I bought it, the first thing I did was root, flash CWM and a CM based ROM -- it's probably worth starting fresh anyway, I'm only going to be using it for a couple more weeks until it's replacement arrives.
I'm currently downloading the latest firmware for my region (XSA), a 4.2.2 based MK3 build from the end of last year -- do you think I'd have better chances if I restored to a 4.4.2 build (like NE5), or should it not matter if I completely reset the phone to factory settings/software?
Click to expand...
Click to collapse
Generally doing a factory reset from the phone resets the entire firmware and is helpfull to resolve such issues. if you want to install the entire firmware, I would recommend flashing the 4.4.2 PHN firmware you can get the download link in post# 13. But then there were wifi issues after flashing the PHN firmware for which a factory reset from the phone happened to be the solution.
JASONRR said:
Generally doing a factory reset from the phone resets the entire firmware and is helpfull to resolve such issues. if you want to install the entire firmware, I would recommend flashing the 4.4.2 PHN firmware you can get the download link in post# 13. But then there were wifi issues after flashing the PHN firmware for which a factory reset from the phone happened to be the solution.
Click to expand...
Click to collapse
Thanks for that mention of the firmware, I had the radio from that link but forgot you'd also linked the full package. Google Drive is much faster than the websites I'd been trying to get files from, it took 15 hours to download the XSA firmware I was originally going to use.
You were totally correct, resetting the phone was the solution. I got the PHN firmware, flashed it via ODIN only to find it still hadn't fixed the WiFi problem -- even after a factory reset -- however the process of flash/reset/re-flash fixed it for me -- it seems unnecessary to me, but I guess times have changed since I last tinkered with unlocked devices. I'm happy to say that I now have WiFi working under WizCyan now, just wanted to check back in just in case anybody else was facing similar issues. As painful as it is to have to back up and totally restore, sometimes starting completely fresh is the best solution.
Now I'm off to rebuild my SD Card, lol.
andycore said:
Thanks for that mention of the firmware, I had the radio from that link but forgot you'd also linked the full package. Google Drive is much faster than the websites I'd been trying to get files from, it took 15 hours to download the XSA firmware I was originally going to use.
You were totally correct, resetting the phone was the solution. I got the PHN firmware, flashed it via ODIN only to find it still hadn't fixed the WiFi problem -- even after a factory reset -- however the process of flash/reset/re-flash fixed it for me -- it seems unnecessary to me, but I guess times have changed since I last tinkered with unlocked devices. I'm happy to say that I now have WiFi working under WizCyan now, just wanted to check back in just in case anybody else was facing similar issues. As painful as it is to have to back up and totally restore, sometimes starting completely fresh is the best solution.
Now I'm off to rebuild my SD Card, lol.
Click to expand...
Click to collapse
Glad to know that you managed to get the wifi working.
Personally, I did not face the wifi issue after flashing PHN firmware, but know that quite a few have faced this issue as reported in this thread
Normally my understanding and experience is that when you flash different modems / firmware some corruption occurs and factory reset from within the phone resets the partition & firmware. 1st time I experienced this was when I was using a MTK 6575 based device and had amended the EBR, MBR and scatter files to modify the partition sizes, even though these were flashed through mobiuncle tools (similar to odin), the revised partitions did not get changed until I did a factory reset from within the phone. I know that this is irrelevant here but thought that I would share this.
I am rooted, unlocked, and S-offed and running a custom GPE+ 5.0.1 ROM. I have an unpinnable notification that says "System Update Downloaded: Android L Upgrade for User/Release-Keys". It is an OTA update obviously, but doesn't even say what version it is. I believe I cannot install it because I am running a custom ROM, is that correct? If not, is there any way to install it? Otherwise, how can I get this notification to stop appearing? The update is ~300MB downloaded and I would love to have that space back. Also I think it is keeping my device awake because I use the Xposed mod "Notification Count" and it says the darn thing has sent out a notification a whopping 463 times since my last reboot - within 3-4 hours!. That is insane.
Any help will be appreciated.
EDIT: Woke up the next morning, and now the notification count for this stupid thing is "999+". WTF. Why does it have to be so insistent? Anybody have a solution to this?
A week passed and no response. Bump. Nobody has any idea how to get rid of this thing??
Koolstr said:
I am rooted, unlocked, and S-offed and running a custom GPE+ 5.0.1 ROM. I have an unpinnable notification that says "System Update Downloaded: Android L Upgrade for User/Release-Keys". It is an OTA update obviously, but doesn't even say what version it is. I believe I cannot install it because I am running a custom ROM, is that correct? If not, is there any way to install it? Otherwise, how can I get this notification to stop appearing? The update is ~300MB downloaded and I would love to have that space back. Also I think it is keeping my device awake because I use the Xposed mod "Notification Count" and it says the darn thing has sent out a notification a whopping 463 times since my last reboot - within 3-4 hours!. That is insane.
Any help will be appreciated.
EDIT: Woke up the next morning, and now the notification count for this stupid thing is "999+". WTF. Why does it have to be so insistent? Anybody have a solution to this?
Click to expand...
Click to collapse
Is updating your custom rom to 5.1+ an option? Already many custom roms were updated to 5.1 even 5.1.1.
Interesting. Last time I checked there wasn't a 5.1 version. But it seems the dev recently implemented an initial version: http://forum.xda-developers.com/ver...m-google-play-edition-lollipop-v1-00-t2963841
The current version of 5.1 of this ROM has some known bugs and I would like to hold off until they are fixed - I like having ambient display. Is it worth waiting until they are fixed, or should I just update now?
Is it safe for me to flash the 5.1 ROM over the 5.0.1 without doing even a cache wipe?
Koolstr said:
Interesting. Last time I checked there wasn't a 5.1 version. But it seems the dev recently implemented an initial version: http://forum.xda-developers.com/ver...m-google-play-edition-lollipop-v1-00-t2963841
The current version of 5.1 of this ROM has some known bugs and I would like to hold off until they are fixed - I like having ambient display. Is it worth waiting until they are fixed, or should I just update now?
Click to expand...
Click to collapse
Don't even know what rom it is so its hard to answer. If you prefer a stable rom they yes, you should wait a little more.
Is it safe for me to flash the 5.1 ROM over the 5.0.1 without doing even a cache wipe?
Click to expand...
Click to collapse
You should ask this one in your rom thread, sometime when the update is considered a major update, its recommend to do a full wipe, in some cases you are fine just updating without wiping. You could do a nandroid backup using your custom recovery (save it on your computer, not just on the phone) try to update without wiping. If its working fine, there is no problem, if not you can wipe your phone and restore your backup.
To disable the notification, I would try to go in settings --> apps --> all, search for the updater service, clear cache of that service and then disable it. Then find where the ota file is stored on your phone and delete it. Not sure if it will work, never tried myselef
Is there a way to do a nandroid backup directly to pc? Because I don't have room on my phone, and TWRP Manager only lets internal backups take place.
For some reason I can't search the apps in my ROM. The notification says it is from Google Play Services but I suspect that is simply routed requests from the actual updater service. Do you know what the name of the service is, so I can find it? I have a crazy number of apps and can't find it.
Hi Koolstr,
I know this thread is old, but wanted to let you know I am on an unlocked and rooted HTC One (m7) S-On. I am using TWRP and can backup to external storage using a Micro USB Powered Micro USB Host OTG cable, which I purchased from Amazon.
I am running:
Android version: 5.1
Rom: Google-Plus-Edition-LP_m7_v3.2_072915
Kernel: 3.4.10-NuK3rn3l-Lollipop_v8.00
I am getting a similar Android System Update: Android L upgrade for user/release-keys. I cannot get it to go away. I made a complete nandroid backup and then proceeded applying the update. It will reboot the phone into TWRP recovery and do nothing. The update goes away for a few days and then it comes back. I have tried to look for a way to disable the update, but I am at a stand still. If anyone knows that would be great.
Best,
manderson706
It's something that santod did. I believe there's a post in his topic with the fix. Or just flash the updated GPE from santod
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, my friend called me on a different fone to walk them thru the process of rooting/twrp'ing an h811 using this as a guide ( https://www.youtube.com/watch?v=epcXXkMPRWk ).
and it booted up fine and the touchscreen worked. so i suggested they also try cyanogenmod (11.12.2015 nightly). they booted into twrp and did a backup then factory wipe and installed the cm-12.1...zip.
they booted into cyanogenmod and the touchscreen worked. but the t-mobile lte internet wasnt working so they wanted to go back.
good thing they created a backup first...
so they did a factory wipe then restored their image. when they rebooted the got a message process system not responding and the screen doesnt acknowledge any touch.
we tried going into twrp and doing wipe dalvik/cache ... we tried re-rooting using the steps outlined in the youtube video ... but the same problem persists.
after playing around with twrp and wiping random stuff the fone eventually allowed them to unlock the screen but there was no t-mobile service and after about a minute the screen stopped responding while they were scrolling thru the app-drawer.
i think as of now the only os where the touch-screen works is cyanogenmod; is it possible that cyanogenmod/twrp broke the touchscreen or lte modules in android ?
i thought they were two different os's that used different software/firmware ?
suggestions ?
thanks,
It's possibly a corrupt backup file. I would use TWRP to flash the stock ROM & see what happens.
i assumed re-rooting would clean everything since it uses the send-command program (essentially dd's the whole disk) but i guess not.
we also tried installing the rooted stock rom using twrp but still no joy.
Re-rooting doesn't do anything to the rom or drivers unless you're doing the easy root using a system img file. Then you're pretty much replacing your rom with one that has superuser already on it. That being said, did you upgrade to the 10n firmware/bootstack? The easy root is for 10h firmware/bootstack so that could be the source of your issues.
schneidz said:
hi, my friend called me on a different fone to walk them thru the process of rooting/twrp'ing an h811 using this as a guide ( ).
and it booted up fine and the touchscreen worked. so i suggested they also try cyanogenmod (11.12.2015 nightly). they booted into twrp and did a backup then factory wipe and installed the cm-12.1...zip.
they booted into cyanogenmod and the touchscreen worked. but the t-mobile lte internet wasnt working so they wanted to go back.
good thing they created a backup first...
so they did a factory wipe then restored their image. when they rebooted the got a message process system not responding and the screen doesnt acknowledge any touch.
we tried going into twrp and doing wipe dalvik/cache ... we tried re-rooting using the steps outlined in the youtube video ... but the same problem persists.
after playing around with twrp and wiping random stuff the fone eventually allowed them to unlock the screen but there was no t-mobile service and after about a minute the screen stopped responding while they were scrolling thru the app-drawer.
i think as of now the only os where the touch-screen works is cyanogenmod; is it possible that cyanogenmod/twrp broke the touchscreen or lte modules in android ?
i thought they were two different os's that used different software/firmware ?
suggestions ?
thanks,
Click to expand...
Click to collapse
I relatively had the same problem where I flashed CM and did not like it because it was buggy and so I restored an nandroid and the once working nandroid was plagued with errors of the touchscreen not working, the phone would freeze, system crashes... It ended up being caused by the fact that I did not flash the 10N bootstack update before hand. After I flashed the new firmware and then flashed CM; all of CM's bugs disappeared. I haven't gone back to stock LG software since CM works flawlessly and is now my dailydriver so I cant say for sure if it will fix the stock rom but It probably will since it cleared up all my bugs like the camera not working, videos now playing...
btw to get data working in CM go to settings/mobile networks/Access point Names/ then scroll down and click "T-Mobile US LTE IPv6" and that should fix the internet issues you have since it fixed it for me.
they didnt do anything with the 10n bootstack (i dont know what that is).
maybe cyanogenmod automatically does the 10n thing (how to manually go back to 10h) ?
i assumed re-loading the 5 gb .img file would bring us back to square-1 but i guess not.
also, how to know what bootstack they are running. i told them to check about fone but they told me nothing in there mentions 10n or 10h.
About phone > Software Info > software version will will say h81110n if on 10n.
Same here on Stock...
I have this running stock H81110n software, which I flashed using a KDZ. However, it only freezes up occasionally, and turning the screen on and off once or twice always gets rid of the problem. It's not bad enough for me yet to warrant any factory resets or tweaking so far, but the problem is there...