Hi, minor issue but annoying. I sideloaded and uodated to the latest U firmware for Europe this morning. All went smoothly. Now I keep getting the android system update notification. Any way of fixing this?
Thanks in advance
nbhadusia said:
Hi, minor issue but annoying. I sideloaded and uodated to the latest U firmware for Europe this morning. All went smoothly. Now I keep getting the android system update notification. Any way of fixing this?
Thanks in advance
Click to expand...
Click to collapse
Theres is L and X ota too, perhaps it wants one of those?
That would be odd? I'm in the UK running the H build originally. From what I understood, the U build was for Europe.
Good point though. Is there anyone in the UK on the EE network that has let the phone update via the network push. If so, what build got pushed? Cheers
A quick update. I let it install (expecting it to fail). And it worked? Even though I was rooted and running elemental x kernel. I've more ended up on the V build. It gets stranger. I checked the kernel and it was now stock. I panicked thinking they may have locked the bootloader, so I rebooted to check and thankfully still locked. What was strange through is that after the last reboot, I was back on elemental kernel and rooted again?? The build was still V. Everything working fine... I'm just confused
Another update. I've rebooted a few times now to see if anything changes between different boots. Looks like I'm running stock V build evertime. Root and elemanntalx kernel lost which I'll flash later. I'm still surprised the OTA for the network push worked even though I was rooted running a custom kernal.
nbhadusia said:
Another update. I've rebooted a few times now to see if anything changes between different boots. Looks like I'm running stock V build evertime. Root and elemanntalx kernel lost which I'll flash later. I'm still surprised the OTA for the network push worked even though I was rooted running a custom kernal.
Click to expand...
Click to collapse
“Curiouser and curiouser!” Cried Google (they were so much surprised, that for the moment they quite forgot how to speak good Android).”
Related
So I have an unlocked GSM Galaxy. I'm still running 4.01
Every time I restart my phone, I get a message saying "Android is Upgrading" but it never upgrades to 4.02 (or .03 or whatever it should be upgrading to). Is anyone else having this issue?
I have NOT rooted yet.
When I go to check for updates it says my phone is up to date.
Any ideas?
Thanks.
pretty sure this is normal. everytime i flash something it does it to me, but every reboot after that it's fine.
PittsburghG1 said:
So I have an unlocked GSM Galaxy. I'm still running 4.01
Every time I restart my phone, I get a message saying "Android is Upgrading" but it never upgrades to 4.02 (or .03 or whatever it should be upgrading to). Is anyone else having this issue?
I have NOT rooted yet.
When I go to check for updates it says my phone is up to date.
Any ideas?
Thanks.
Click to expand...
Click to collapse
have you done any mods?
usually you get the android is upgrading when you install a new app or wipe the dalvik cache. the android is upgrading is the apps rebuilding in cache.
its quite annoying and you shouldn't have it on every boot (just the first or after a mod)
I get the same thing on 4.0.1..I'm pretty sure its normal. At least for this build
Sent from my Galaxy Nexus using XDA App
I think what it might be doing is wiping cache.
Sent from my Galaxy Nexus using XDA App
I get it too. Figured it was normal
Meaple said:
I get it too. Figured it was normal
Click to expand...
Click to collapse
hmm. all you guys on 4.0.1? thats annoying. worth the trouble to get to 4.0.2 asap
I think i was on .1 for about a day so I didn't notice it...boot time without it is superfast
ogdobber said:
hmm. all you guys on 4.0.1? thats annoying. worth the trouble to get to 4.0.2 asap
I think i was on .1 for about a day so I didn't notice it...boot time without it is superfast
Click to expand...
Click to collapse
It really only takes a sec anyway.
Sent from my Galaxy Nexus using XDA App
Mine does this to and it's kind of annoying
Mine does it every time I turn the phone on and off. Still on 4.0.1 ITL41F build too on AT&T in the US. Lasts for 2 or 3 seconds and then the phone boots up. I thought this was normal behaviour of Android trying to search for updates. Is this not happening to everyone?
Sent from my Galaxy Nexus using XDA App
OK, my friend's Verizon Nexus doesn't do it for some reason. Also, I get the notification to upgrade to 4.0.2, but it never upgrades...even if I accept the update. I thought the "UPgrading Android" and this issue were connected.
Is anyone else getting the 4.0.2 notification then the update isn't applying?
Also, I have not rooted or applied and mods to the phone. I may try a factory reset and see what happens, obviously I don't want to do that, but I'll try.
Oh and it happens every single time I boot the phone.
thanks for all the responses!
I get this, 4.0.1 UK model here.
I am sure though after a few restarts of nothing major changing then it stopped?
I used to get this on 4.0.1, but since I force upgraded to 4.0.2 I havent seen it. I downloaded to official 4.0.2 from here and applied it through CWM.
has anyone who is having this problem received the 4.0.2 upgrade notification then been unable to upgrade?
That's the boat I'm in now. It won't upgrade. I'm thinking about doing a factory reset.
PittsburghG1 said:
has anyone who is having this problem received the 4.0.2 upgrade notification then been unable to upgrade?
That's the boat I'm in now. It won't upgrade. I'm thinking about doing a factory reset.
Click to expand...
Click to collapse
Most people are sure that the 4.0.2 update got pulled as there were too many bugs with it. I wouldn't worry about it.
Just to clarify...this has happened to me about 4 times...
1) I'm notified of the update.
2) I click update now
3) I get the android guy with the lightening in his belly showing that I'm updating
4) phone restarts
5) I get the Upgrading Android and Upgrading Applications messages
6) Phone completes booting
7) When I go to about Phone Android version is still 4.0.1
Then steps 4,5,6 and 7 always repeat any time I restart my phone ever since I got my update notification about 2 weeks ago.
So, it seems as its trying to upgrade to 4.0.2 everytime I restart but it can't.
Whether they pulled the update or not, my phone was being pushed the update but was unable to update. So basically, I'm thinking will I ever be able to update or should I just wipe now as there is clearly some problem?
I get this too, on the 4.0.1 build. Only takes a few seconds tho, nothing too annoying, I thought it is normal. But thinking about it, my Desire S with a ICS custom rom only did this after an upgrade or a modification...
But I haven't got any 4.0.2 update notification yet. Received my Nex on the 28th of December.
I just ended up rooting, upgrading to 4.0.3 and its never happened again. Thanks everyone though for the feedback.
I'm on 4.0.2. Had the phone a week, it updated to 4.0.2 the first time I turned it on, then again after I unlocked the bootloader and nothing else.
It's a UK vodafone.
Sent from my Galaxy Nexus using XDA App
I have an International GNex running on T-Mobile US: I've had the same message "Android is upgrading" on all reboots when I was on 4.0.1. Since the 4.0.2 update (received OTA on January 11), the message never appeared again.
Hope this helps
I updated to Android 4.2.2 some days ago, I tested somethings on it before realising the Wi-Fi didn't work. I didn't do much about it there and then, since I had to get up early the day after and it was getting late.
So I went to school and checked if the Wi-Fi worked there, it did.
I already tried a hard reset, and it looks like the phone finds the Wi-Fi in the setup phase, but then it goes back to "Not in range".
I didn't find anyone with a similar problem so I just thought I'd post it here.
Thanks in advance to anyone answering!
Norberedv1 said:
I updated to Android 4.2.2 some days ago, I tested somethings on it before realising the Wi-Fi didn't work. I didn't do much about it there and then, since I had to get up early the day after and it was getting late.
So I went to school and checked if the Wi-Fi worked there, it did.
I already tried a hard reset, and it looks like the phone finds the Wi-Fi in the setup phase, but then it goes back to "Not in range".
I didn't find anyone with a similar problem so I just thought I'd post it here.
Thanks in advance to anyone answering!
Click to expand...
Click to collapse
Is this update official or did you flash some custom ROM? If it's official, you should try some RUU to go back before the update and maybe update again, see if the issue persists. It it's custom, you should try re-flashing and if that doesn't help, try another ROM or maybe official.
Since you experienced this problem after updating, it's most likely software related.
unikulkiss said:
Is this update official or did you flash some custom ROM? If it's official, you should try some RUU to go back before the update and maybe update again, see if the issue persists. It it's custom, you should try re-flashing and if that doesn't help, try another ROM or maybe official.
Since you experienced this problem after updating, it's most likely software related.
Click to expand...
Click to collapse
It's the official update.
I'm not extremely good with these things.. So how would I use an RUU to revert to an old version?
Norberedv1 said:
It's the official update.
I'm not extremely good with these things.. So how would I use an RUU to revert to an old version?
Click to expand...
Click to collapse
You can learn HERE how to use RUU and how to find what version is right for your phone.
Like the title says, on every 5.1 ROM I keep getting random reboots. They happen indiscriminately, with no clear reason at all. Other people report no issues at all. On 5.0.2 I have no issues at all. I have no idea what causes it could be or no knowledge on how to diagnose it...I want to use 5.1, but if this keeps happening I don't think I can ?.
I've not had any issues with random reboots, been running euphoria rom (updating with each new build) and glitch kernel for weeks with no issues.
Assuming you're doing clean flashes, with no extra mods, and not restoring system data, yes? Its even possible that restoring app data from backups can cause weird things to occur at times. If you haven't yet, wipe everything and clean flash, restore apps only from play store, and see if it still happens.
Otherwise, maybe a specific app is causing problems? You could try and grab some logs to narrow down the cause, but I know that's very tough to do if the issue is intermittent and seemingly random. Still it is the only way to tell for sure what's happening.
Here's a guide on how to grab the different logs if that helps at all: http://forum.xda-developers.com/showthread.php?t=1520508 .
LucentBirch said:
Like the title says, on every 5.1 ROM I keep getting random reboots. They happen indiscriminately, with no clear reason at all. Other people report no issues at all. On 5.0.2 I have no issues at all. I have no idea what causes it could be or no knowledge on how to diagnose it...I want to use 5.1, but if this keeps happening I don't think I can ?.
Click to expand...
Click to collapse
The random reboots are caused by outdated 5.0.2 binaries, if you update to 5.1 it should mend it random reboots. Also if your ROM developer might or will update the ROM to 5.1 with the updated binaries!
Killah1994 said:
The random reboots are caused by outdated 5.0.2 binaries, if you update to 5.1 it should mend it random reboots. Also if your ROM developer might or will update the ROM to 5.1 with the updated binaries!
Click to expand...
Click to collapse
Well I know for a while that some 5.1 roms were using the 5. 0. 2 binaries because the 5.1 weren't released yet... And they never really said whether or not they updated the binaries or if they were even released...I updated my tablet to a 5.1 R_5 this morning and it hasn't rebooted all day...so maybe they have?
LucentBirch said:
Well I know for a while that some 5.1 roms were using the 5. 0. 2 binaries because the 5.1 weren't released yet... And they never really said whether or not they updated the binaries or if they were even released...I updated my tablet to a 5.1 R_5 this morning and it hasn't rebooted all day...so maybe they have?
Click to expand...
Click to collapse
5.1 binaries and factory image for this device were just rolled out today. This may indeed resolve your issues, but give the custom rom devs some time to catch up, they'll need to grab the latest source and post new builds for the latest binaries to be included.
Same thing here
I excitedly loaded up the 5.1 build on my 2013 wireless today. SAME ISSUE. I can't do anything .
I didn't wipe the device when I upgraded. I was rooted - unrooted / flashed / rooted using the Nexus Root Tooklit as I have since Jelly Bean. I used the option to use NO WIPE MODE to try and keep my apps intact.
Any help appreciated.
mrdrumsc said:
I excitedly loaded up the 5.1 build on my 2013 wireless today. SAME ISSUE. I can't do anything .
I didn't wipe the device when I upgraded. I was rooted - unrooted / flashed / rooted using the Nexus Root Tooklit as I have since Jelly Bean. I used the option to use NO WIPE MODE to try and keep my apps intact.
Any help appreciated.
Click to expand...
Click to collapse
in that case you should try wiping then flash the 5.1 factory image and see if it works.
PrizmaticSmoke said:
5.1 binaries and factory image for this device were just rolled out today. This may indeed resolve your issues, but give the custom rom devs some time to catch up, they'll need to grab the latest source and post new builds for the latest binaries to be included.
Click to expand...
Click to collapse
cm12.1. rebooted once today while using chrome.
Reboots better!
I concur with the messages I've been seeing. After several app updates over the weekend, culminating in some Chrome updates, the tablet seems stable. I haven't re-rooted it yet.
I wonder if something has to do with the "notification crash" error listed in the changelog for 5.1.1.
Either way, looking forward to 5.1.1!
Hi, Ive not long had my m9. When i got it it updated straight away and got the charging bug.
Since then I have s-off'd and tried various roms with not too much luck.
I now have a bug that occurs when i flash a new rom. This has happened when i flashed 3 different roms. Leedroid, Viper and android revolution. the rom flashes ok, then starts to boot, and builds art. It then finishes building art and starts to complete the boot process, and then it reboots and tries to build art again.
I flash back to my stock backup and everything is fine again. (apart from the damned charging bug)
Has anyone else experienced something similar?? am i missing something??
Go in twrp and make factory reset
just tried that, didnt work
Did you update your firmware? if you're still on 1.x firmware, those 2.x roms will reboot.
yeah. have tried matching roms to firmware and still get the same result. trying viper one currently. in a massive bootloop again. It boots enough to say "nfc service has stopped working" and thats what made me think it might be firmware, but it seems to make no difference.
cant even adb whilst its booting.. getting waiting for device.
What version of twrp are you using?
2.8.6.1
philicibine said:
2.8.6.1
Click to expand...
Click to collapse
Update to 2.8.7.0 and see if it continues.
I've solved this, and my charging issue. Finally!!
I decided to flash the earliest ruu I could find and then let it do all of the ota updates itself.
I then rerooted, flashed updated firmware and am now running leedroid.
Thanks for the help guys.
Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
drakemiller40 said:
Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
Click to expand...
Click to collapse
Hi, the link you provided points to build 4. You can find build 9 which is the latest slimkat here http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1183-d2lte
This is the one I have for my Koodo I747M. *note camera seemed a little buggy in some instances, so I installed open camera. Seemed to work a lot better.
I'll give it a try, thanks for the help. Quick question, will this work on my phone model without bricking? I only tried the at&t not the d2lte.
Also can you send me the link for this open camera you were talking about for my device as well?
drakemiller40 said:
I'll give it a try, thanks for the help. Quick question, will this work on my phone model without bricking? I only tried the at&t not the d2lte.
Also can you send me the link for this open camera you were talking about for my device as well?
Click to expand...
Click to collapse
I'd imagine it should be ok, since we have the same phone pretty much I'm on koodo which is pretty much telus without the customer service hehe. for kitkat at the end of development they basically lumped a d2att, d2tmo etc together. (this has reverted for the lollipop builds out there).
The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course.
It's a google play app open source, the slimkat one I had seemed to lockup when switching from front to back camera and from camera to video. https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en
What are you using to flash them?
serathe said:
I'd imagine it should be ok, since we have the same phone pretty much I'm on koodo which is pretty much telus without the customer service hehe. for kitkat at the end of development they basically lumped a d2att, d2tmo etc together. (this has reverted for the lollipop builds out there).
The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course.
It's a google play app open source, the slimkat one I had seemed to lockup when switching from front to back camera and from camera to video. https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en
What are you using to flash them?
Click to expand...
Click to collapse
Im not very experienced lol and got lost on:
"The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course. "
I'm using TWRP
Ah, ok I just keep a backup in case anything goes bad flashing roms. If you use TWRP to flash them it only affects the boot image, data and system. So if you have problems you can restore from backup nice and easy.
I'm swapping between a few right now. So far my only uh oh experience was when I tried to upgrade TWRP, no problems with roms. But I use TWRP as well, works great.
Basically the baseband version on our phone, it's the radio and bootloader. Before I had rooted it I had gotten the latest updates by checking for updates. It downloaded and upgraded to FOB1 (Baseband I747MVLUFOB1), then I rooted and played with flashing. Not sure if you made a backup of your original install before trying another rom. But it's not a necessity for slimkat, I don't believe.
serathe said:
Ah, ok I just keep a backup in case anything goes bad flashing roms. If you use TWRP to flash them it only affects the boot image, data and system. So if you have problems you can restore from backup nice and easy.
I'm swapping between a few right now. So far my only uh oh experience was when I tried to upgrade TWRP, no problems with roms. But I use TWRP as well, works great.
Basically the baseband version on our phone, it's the radio and bootloader. Before I had rooted it I had gotten the latest updates by checking for updates. It downloaded and upgraded to FOB1 (Baseband I747MVLUFOB1), then I rooted and played with flashing. Not sure if you made a backup of your original install before trying another rom. But it's not a necessity for slimkat, I don't believe.
Click to expand...
Click to collapse
Yeah I always create a nandroid and backup my IME.
drakemiller40 said:
Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
Click to expand...
Click to collapse
First thing to try for GPS problems is taking off the back cover and snugging up all the little screws around the phone. Sometimes they work their way loose and the GPS antenna seems to be the first thing to suffer from it.
If that doesn't cure it you might need to flash a stock or at least stock based ROM and rebuild the nvram. Here's a link that describes how to do that if you need to.