I just upgrade to 4.4.4 .
I don't know why the home button disable after I upgrade the software from play store.
Swipe to open the google is unable to use too.
Appreciate the help!
that is just not enough information. what software did you upgrade from the play store? 4.4.4 doesn't come from the play store, it comes as an OTA update. did you install a new launcher?
640k said:
that is just not enough information. what software did you upgrade from the play store? 4.4.4 doesn't come from the play store, it comes as an OTA update. did you install a new launcher?
Click to expand...
Click to collapse
Thank you for your reply.
I'm using sprint's latest rom.
I found that every time when I reboot my phone ,while starting the system it will says : starting services.
There is a little wheel is rolling, every time . It takes about 1 minute to Finnish，So I try to skip it then cause this problem, if I wait till it finnished the problem will disappear.
BTW， I have not sim insert my phone.maybe this is the reason?
Very appreciate your help!
myarms said:
Thank you for your reply.
I'm using sprint's latest rom.
I found that every time when I reboot my phone ,while starting the system it will says : starting services.
There is a little wheel is rolling, every time . It takes about 1 minute to Finnish，So I try to skip it then cause this problem, if I wait till it finnished the problem will disappear.
BTW， I have not sim insert my phone.maybe this is the reason?
Very appreciate your help!
Click to expand...
Click to collapse
Are you rooted/ have safestrap/ have bootloader unlocked??? You could fix the problem without too much difficulty if you do.
If not, a factory reset may be your only option. If that doesn't fix the issue, I'd say talk to verizon or moto about getting a new phone.
1ad_m12 said:
Are you rooted/ have safestrap/ have bootloader unlocked??? You could fix the problem without too much difficulty if you do.
If not, a factory reset may be your only option. If that doesn't fix the issue, I'd say talk to verizon or moto about getting a new phone.
Click to expand...
Click to collapse
Thank you 1ad,
I'm using unlock BL phone, I think It's software problem, maybe because I'm using OTA to upgrade to 4.4.4.
myarms said:
Thank you 1ad,
I'm using unlock BL phone, I think It's software problem, maybe because I'm using OTA to upgrade to 4.4.4.
Click to expand...
Click to collapse
Did you use sunshine? I had an issue with my ROM after I used it. I restored from a backup and it fixed my issue/ kept the phone unlocked.
Use this to flash back to stock. Should fix any problems you have. http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
1ad_m12 said:
Did you use sunshine? I had an issue with my ROM after I used it. I restored from a backup and it fixed my issue/ kept the phone unlocked.
Use this to flash back to stock. Should fix any problems you have. http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Click to expand...
Click to collapse
I'm sorry, what's sunshine?
I'm already using stock rom before I'm using Verizon's rom have not kind of problem.
myarms said:
I'm sorry, what's sunshine?
I'm already using stock rom before I'm using Verizon's rom have not kind of problem.
Click to expand...
Click to collapse
Sunshine is a BL unlock exploit for phones with locked BL's.
What I mean by returning to stock rom is reinstalling the firmware. It is very possible that the OTA did not correctly download to your phone/ not install properly.
Thank you for your information, 1ad.
I may try the way you said next time.
Related
I updated to 4.4.2 on my Verizon Developer Edition today and now I'm having issues updating Cloud Print. The Play Store keeps telling me that the package wasn't signed correctly. Do I have any other options besides rooting, uninstalling and then reinstalling it, because it's a system app? Any clues would be really appreciated. I'd post an image, but I'm too new of a user to link to one.
FinalBabality said:
I updated to 4.4.2 on my Verizon Developer Edition today and now I'm having issues updating Cloud Print. The Play Store keeps telling me that the package wasn't signed correctly. Do I have any other options besides rooting, uninstalling and then reinstalling it, because it's a system app? Any clues would be really appreciated. I'd post an image, but I'm too new of a user to link to one.
Click to expand...
Click to collapse
I recommend the basics. Going to the settings and clearing the app cache for the play store, try factory reset (yeah i know it sucks) try downloading the app again on wifi on LTE, etc. etc.
drago10029 said:
I recommend the basics. Going to the settings and clearing the app cache for the play store, try factory reset (yeah i know it sucks) try downloading the app again on wifi on LTE, etc. etc.
Click to expand...
Click to collapse
I've tried all of it and can't seem to sort it out. Think I'll just leave it alone, seeing as I've yet to print from any if my mobile devices. I did apply the update myself and I wonder if that has anything to do with it.
Sent from my XT1060 using Tapatalk
If you applied 4.4.2 from the files available here at XDA unfortunately you don't have the equivalent to a true OTA. The Cloud Print included with it had been modified and you will not be able to update it unless you root, delete it and reinstall it from the play store. The full image file from droid-developers.org has the exact same issue. Very frustrating punishment for those of us who weren't patient enough to wait for the OTA.
jpizz said:
If you applied 4.4.2 from the files available here at XDA unfortunately you don't have the equivalent to a true OTA. The Cloud Print included with it had been modified and you will not be able to update it unless you root, delete it and reinstall it from the play store. The full image file from droid-developers.org has the exact same issue. Very frustrating punishment for those of us who weren't patient enough to wait for the OTA.
Click to expand...
Click to collapse
droid-developers doesn't even have a Verizon 4.4.2 sbf file.
Steve-x said:
droid-developers doesn't even have a Verizon 4.4.2 sbf file.
Click to expand...
Click to collapse
Sorry, I was referring to the GSM Dev Edition. Same exact problem.
jpizz said:
If you applied 4.4.2 from the files available here at XDA unfortunately you don't have the equivalent to a true OTA. The Cloud Print included with it had been modified and you will not be able to update it unless you root, delete it and reinstall it from the play store. The full image file from droid-developers.org has the exact same issue. Very frustrating punishment for those of us who weren't patient enough to wait for the OTA.
Click to expand...
Click to collapse
Alright I figured it had something to do with the fact I installed it from Zip instead of waiting for the OTA. I tried that solution and that didn't work either. When I installed it with root and the tried to install from the Play Store, it just told me "Invalid Package." So I'll wait a little while, until it's solidly rolled out and then go back to 4.4 and then flash the OTA the official way. Thanks for the confirmation on the Zip being the issue. Not having any other issues though, so I might just stick it out.
FinalBabality said:
Alright I figured it had something to do with the fact I installed it from Zip instead of waiting for the OTA. I tried that solution and that didn't work either. When I installed it with root and the tried to install from the Play Store, it just told me "Invalid Package." So I'll wait a little while, until it's solidly rolled out and then go back to 4.4 and then flash the OTA the official way. Thanks for the confirmation on the Zip being the issue. Not having any other issues though, so I might just stick it out.
Click to expand...
Click to collapse
If you have updated to 4.4.2 then you cannot downgrade back to 4.4.
Steve-x said:
If you have updated to 4.4.2 then you cannot downgrade back to 4.4.
Click to expand...
Click to collapse
Have a dev edition with an unlocked bootloader. I've already done it once to try and fix this issue.
FinalBabality said:
Have a dev edition with an unlocked bootloader. I've already done it once to try and fix this issue.
Click to expand...
Click to collapse
Well you must have manually flashed 4.4 without the 4.4 bootloader then, because RSD wont allow you to flash from 4.4.2 down to 4.4.
Be careful because if you take an update while back on 4.4 you will hard brick your phone.
mastarifla said:
Well you must have manually flashed 4.4 without the 4.4 bootloader then, because RSD wont allow you to flash from 4.4.2 down to 4.4.
Be careful because if you take an update while back on 4.4 you will hard brick your phone.
Click to expand...
Click to collapse
Yeah that's exactly what I did, that's a good point. So should I wait for Motorola to post the recovery files, and then flash that when it comes out? Would that be safer?
So i keep being prompted to get the new OTA update and whenever i try to download and install it, it reboots goes to the install screen, gets about 1/4 of the way through, says error and then reboots to an update unsuccessful page
After digging around my phone i also noticed it says my software was modified on the status page
But obviously ive never rooted this phone as its pretty much impossible at the moment
Has anyone experienced something similar and found a way to fix it?
did you disable any of the bloat? that might be your issue.....
xbxjunkie said:
did you disable any of the bloat? that might be your issue.....
Click to expand...
Click to collapse
I did! I'll re enable it all and see if it fixes the issue
jaideng123 said:
So i keep being prompted to get the new OTA update and whenever i try to download and install it, it reboots goes to the install screen, gets about 1/4 of the way through, says error and then reboots to an update unsuccessful page
After digging around my phone i also noticed it says my software was modified on the status page
But obviously ive never rooted this phone as its pretty much impossible at the moment
Has anyone experienced something similar and found a way to fix it?
Click to expand...
Click to collapse
Try a factory data reset but you will wipe your phone and lose all data and apps.
xbxjunkie said:
did you disable any of the bloat? that might be your issue.....
Click to expand...
Click to collapse
That's odd, I even blocked the OTA via adb and mine says official.
OK i tried both, neither worked, also when i boot into recovery i get qe 1/1 at the bottom left side of my screen
Decided to just get a replacement from motorola since I'm still under warranty, but thank you for the suggestions!
jaideng123 said:
Decided to just get a replacement from motorola since I'm still under warranty, but thank you for the suggestions!
Click to expand...
Click to collapse
You could just flash the stock ROM again!
Gundabolu SC said:
You could just flash the stock ROM again!
Click to expand...
Click to collapse
I am unable to obtain the moforoot util to do this. When I put in my ID on the moforoot page, it says my device is not supported. I know for a fact the model and current OS on it. Its 5.1 updated already which is probably why the website is rejecting my request to obtain the util.
I do not think the bootloader will allow me to downgrade. If anybody has a solution, please let me know.
Note: Using XT1254 w/ latest 5.1 update from Aug-Sept.
LatencyXXX said:
I am unable to obtain the moforoot util to do this. When I put in my ID on the moforoot page, it says my device is not supported. I know for a fact the model and current OS on it. Its 5.1 updated already which is probably why the website is rejecting my request to obtain the util.
I do not think the bootloader will allow me to downgrade. If anybody has a solution, please let me know.
Note: Using XT1254 w/ latest 5.1 update from Aug-Sept.
Click to expand...
Click to collapse
If you want to flash an official update that is greater than or equal to the version you're on now, you don't need mofo. You could use fastboot, rsdlite, Motorola device manager or the Verizon upgrade assistant. The upgrade assistant is probably the easiest way to go. That's the annoying pop up software you get whenever you plug your phone into your computer.
TheSt33v said:
If you want to flash an official update that is greater than or equal to the version you're on now, you don't need mofo. You could use fastboot, rsdlite, Motorola device manager or the Verizon upgrade assistant. The upgrade assistant is probably the easiest way to go. That's the annoying pop up software you get whenever you plug your phone into your computer.
Click to expand...
Click to collapse
I tried all 3 different options and none of them work. Then I went into Verizon store and asked them to do it and they told me that they don't do that anymore. Only contacts, photos, etc.
The store told me to send it to Motorola for them to do it. I'm sure there is an ISP somewhere or some trick button internally for them to unlock the bootloader, but nobody is saying.
I am out of options, and I am ready to send it to whomever can fix it for me. PM me if you can guarantee to do it and send it back.
-Thanks
LatencyXXX said:
I tried all 3 different options and none of them work. Then I went into Verizon store and asked them to do it and they told me that they don't do that anymore. Only contacts, photos, etc.
The store told me to send it to Motorola for them to do it. I'm sure there is an ISP somewhere or some trick button internally for them to unlock the bootloader, but nobody is saying.
I am out of options, and I am ready to send it to whomever can fix it for me. PM me if you can guarantee to do it and send it back.
-Thanks
Click to expand...
Click to collapse
Send it to Motorola then. If your phone is less than a year old, they will send you a new one for free.
Hi, my Nexus is on Android 5.0.1 (LRX22C). I haven't rooted or unlocked the bootloader; everything is totally stock. But I'm unable to successfully install the Android 5.1 OTA update. My phone downloads it, verifies it, then reboots to begin the installation process. After working on the update for a while, I see an error message (with an android on its back and a red "X"). The phone stays on that screen for a while, then eventually reboots without having installed the update. I've tried clearing cache, and it doesn't help. Anyone have any ideas?
carrot34 said:
Hi, my Nexus is on Android 5.0.1 (LRX22C). I haven't rooted or unlocked the bootloader; everything is totally stock. But I'm unable to successfully install the Android 5.1 OTA update. My phone downloads it, verifies it, then reboots to begin the installation process. After working on the update for a while, I see an error message (with an android on its back and a red "X"). The phone stays on that screen for a while, then eventually reboots without having installed the update. I've tried clearing cache, and it doesn't help. Anyone have any ideas?
Click to expand...
Click to collapse
Some more info please. What carrier are you using? Was your phone purchased from that carrier or somewhere else?
Evolution_Freak said:
Some more info please. What carrier are you using? Was your phone purchased from that carrier or somewhere else?
Click to expand...
Click to collapse
Thanks! I'm on T-Mobile, and bought the phone from Google Play.
carrot34 said:
Thanks! I'm on T-Mobile, and bought the phone from Google Play.
Click to expand...
Click to collapse
Are you familiar with sideload?
---------- Post added at 09:42 PM ---------- Previous post was at 09:37 PM ----------
Check out my thread on OTA's.
http://forum.xda-developers.com/showthread.php?t=2992919
In post #2, there's a link to the OTA files thread. Take the one that is specifically for T-Mobile. LRX22C to LMY47M.
Evolution_Freak said:
Are you familiar with sideload?
Click to expand...
Click to collapse
Yeah, I've sideloaded before with other devices, but I'd like not to have deal with wiping my phone to unlock the bootloader right now. I'd thought that by not rooting or messing with the bootloader, I'd keep things simple and be able to easily apply OTA updates. So I'm very frustrating that this isn't working. Any idea why this might be happening?
Thanks!
Alan
carrot34 said:
Yeah, I've sideloaded before with other devices, but I'd like not to have deal with wiping my phone to unlock the bootloader right now. I'd thought that by not rooting or messing with the bootloader, I'd keep things simple and be able to easily apply OTA updates. So I'm very frustrating that this isn't working. Any idea why this might be happening?
Thanks!
Alan
Click to expand...
Click to collapse
No, you do not need to wipe or unlock to sideload. Post #3 in the thread I linked, simple instructions on sideloading.
As for why this is happening, anyone's guess but it could, somehow, have something to do with your device having the T-Mobile Sim and being from Google play.
Evolution_Freak said:
No, you do not need to wipe or unlock to sideload. Post #3 in the thread I linked, simple instructions on sideloading.
As for why this is happening, anyone's guess but it could, somehow, have something to do with your device having the T-Mobile Sim and being from Google play.
Click to expand...
Click to collapse
OK, I'll give it a shot. Thanks! Any idea which OTA I want? I'm guessing it's LMY47M, since I'm on a T-Mobile SIM, even though the device was bought from Google? Need I worry that that build isn't up on Google's "Factory Images for Nexus Devices" page? And is there any risk that installing an update this way will make it more complicated to get OTA updates in the future? (I was hoping that by doing things the official way this time, I could avoid having to monkey around with stuff like this.)
Thanks!
Alan
carrot34 said:
OK, I'll give it a shot. Thanks! Any idea which OTA I want? I'm guessing it's LMY47M, since I'm on a T-Mobile SIM, even though the device was bought from Google? Need I worry that that build isn't up on Google's "Factory Images for Nexus Devices" page? And is there any risk that installing an update this way will make it more complicated to get OTA updates in the future? (I was hoping that by doing things the official way this time, I could avoid having to monkey around with stuff like this.)
Thanks!
Alan
Click to expand...
Click to collapse
Yes, you want the LRX22C to LMY47M OTA as I said before. No, you don't need to worry about it not being on the images page. Also a no for it affecting your ability to get OTA's in the future. On a Nexus, this is pretty much as official as getting the OTA natively.
OK, an update: got an error installing the update any way I tried, even after a factory reset. Called Google support, and they're replacing the phone for me.
I have been experiencing a rather annoying bug on my S6. After unlocking the screen, sometimes the status bar will not pull down. This happens about 1/5 unlocks. I have to lock the screen again and then unlock for it to work again. Since the status bar is usually the first thing I use after unlocking, this becomes a real pain. I was hoping that the recent update would fix this, but it's still happening.
Is anyone else experiencing this issue? I couldn't find anything on the forums or Google.
gj13 said:
I have been experiencing a rather annoying bug on my S6. After unlocking the screen, sometimes the status bar will not pull down. This happens about 1/5 unlocks. I have to lock the screen again and then unlock for it to work again. Since the status bar is usually the first thing I use after unlocking, this becomes a real pain. I was hoping that the recent update would fix this, but it's still happening.
Is anyone else experiencing this issue? I couldn't find anything on the forums or Google.
Click to expand...
Click to collapse
Could you please provide additional information about your phone, such as the Base and or ROM?
Maybe try going into Recovery mode and clearing cache, that may resolve it.
Rayman360 said:
Could you please provide additional information about your phone, such as the Base and or ROM?
Click to expand...
Click to collapse
Baseband: G920AUCU1AOCE
ROM: Stock unrooted (G920AUCU1AOE2)
Rayman360 said:
Maybe try going into Recovery mode and clearing cache, that may resolve it.
Click to expand...
Click to collapse
No recovery, but the cache was cleared after I installed the G920AUCU1AOE2 update.
gj13 said:
Baseband: G920AUCU1AOCE
ROM: Stock unrooted (G920AUCU1AOE2)
No recovery, but the cache was cleared after I installed the G920AUCU1AOE2 update.
Click to expand...
Click to collapse
There is the issue right there, your base needs to be G920AUCU1AOE2, your on the older firmware but using the newer ROM. Use Odin to return to stock G920AUCU1AOCE, then do the OTA update from AT&T again. FYI The new PingPong Root still works on the new OTA, if you decide to go that route.
Return to Stock - http://forum.xda-developers.com/att-galaxy-s6/development/5-16-stock-odin-tar-g920aucu1aoce-t3110182
Rayman360 said:
There is the issue right there, your base needs to be G920AUCU1AOE2, your on the older firmware but using the newer ROM. Use Odin to return to stock G920AUCU1AOCE, then do the OTA update from AT&T again. FYI The new PingPong Root still works on the new OTA, if you decide to go that route.
Return to Stock - http://forum.xda-developers.com/att-galaxy-s6/development/5-16-stock-odin-tar-g920aucu1aoce-t3110182
Click to expand...
Click to collapse
That doesn't explain why it was happening when I was on the version that it shipped with. They matched at that point. Good suggestion though.
Rayman360 said:
There is the issue right there, your base needs to be G920AUCU1AOE2, your on the older firmware but using the newer ROM. Use Odin to return to stock G920AUCU1AOCE, then do the OTA update from AT&T again. FYI The new PingPong Root still works on the new OTA, if you decide to go that route.
Return to Stock - http://forum.xda-developers.com/att-galaxy-s6/development/5-16-stock-odin-tar-g920aucu1aoce-t3110182
Click to expand...
Click to collapse
I just updated the baseband to match the software. I'll report back after I use it a bit to see if it happens again. It just happened after I posted that. Ugh x.x
Looks like I'm going to have to factory reset. I was hoping more people would at least vote on the poll -.-
Wireless charging possible cause
It seems like this issue only happens if you use wireless charging. I did a factory reset on the phone and used it for a couple weeks with AC charging and I did not have this issue. As soon as I tried wireless charging again, the issue came right back.
gj13 said:
It seems like this issue only happens if you use wireless charging. I did a factory reset on the phone and used it for a couple weeks with AC charging and I did not have this issue. As soon as I tried wireless charging again, the issue came right back.
Click to expand...
Click to collapse
I strictly use wireless charging, so your blanket statement only applies to you. Never had an issue with three different charging pads.
Sent from my SAMSUNG-SM-G920A using Tapatalk
Anyone?
thegameksk said:
Anyone?
Click to expand...
Click to collapse
According to Slim, root is broken on the new update. They also changed the bootloader so you can't downgrade. They apparently want everyone to update to the new software.
fogame said:
According to Slim, root is broken on the new update. They also changed the bootloader so you can't downgrade. They apparently want everyone to update to the new software.
Click to expand...
Click to collapse
Of course they do... they don't want folks rooting... Sammy knows what's up... if they were decent they'd give us a bootloader unlock to make up for rushing the devices to market to beat Apple on the release date (which is already cracked smh) and catch a few more percent of market share...
Sent from my SM-N930F using Tapatalk
I was able to root. You just can not take the new update, it will prevent root and will not be able to revert back to the old firmware..
galaxyuser88 said:
I was able to root. You just can not take the new update, it will prevent root and will not be able to revert back to the old firmware..
Click to expand...
Click to collapse
For clarification,you were able to root a replacement note 7?
I read,somewhere, that the update starts when you power it on the first time. I am hoping to root mine immediately to avoid the update.
Mean Sixteen said:
For clarification,you were able to root a replacement note 7?
I read,somewhere, that the update starts when you power it on the first time. I am hoping to root mine immediately to avoid the update.
Click to expand...
Click to collapse
Yes you are correct. The update starts to download when you power up the phone, but you can pause the download or postpone it for later install. This is what happened on my phone.
galaxyuser88 said:
Yes you are correct. The update starts to download when you power up the phone, but you can pause the download or postpone it for later install. This is what happened on my phone.
Click to expand...
Click to collapse
Awesome thank you for clarifying.
Once I saw there was complete root with volte I went straight to download mode and did the process. Glad I didn't take the update because it blocks root and the sprint engineer rom.