4.0.4 update has kind of broken my phone.
GSM Stock Galaxy Nexus on T-Mobile. No Root. Nothing done to software, firmware, recovery, etc. Bought new from Amazon.
Got the 4.0.4 update notification today. Was on 4.0.2.
Download and Update went fine until upon reboot:
"Android is upgrading...Optimizing application of 2 of 52"
Screen gets really bright, washes out, then goes black. Can't turn screen on after that.
I left it like that for 30 minutes and still couldn't turn the screen on.
Pulled the battery and rebooted. Same thing, stuck on 2 of 52.
Any advice on how to fix this? Please help, thanks!
Related
Using the USB drivers and Firmware from the Samsung Germany website I went from yakjuzs (Hong Kong) to yakju.
After doing this, I powered off my phone, and powered it back on.
After the Google Logo and Animation, I get a message box that says "Android Updating...". after short period of time (under 2s) at the bottom of the screen it says "No Service", then the message box says "starting Applications" under the "Android Updating..." message. The phone then finishes initialization as normal and goes to the home screen.
This made me think that my phone might be trying to upgrade from 4.0.1 to 4.0.2. So I went to the system settings > about phone > system updates and checked for updates. It said my phone was up to date, and the version in the about section is 4.0.1.
Has anyone had this happen to them before? Have any ideas on how to fix this issue?
This happens every time I shutoff my phone and turn it back on. I have also tried a battery pull.
*bump*
Can anyone else out?
Sent from my GSM Galaxy Nexus using the XDA App
1Speed said:
Using the USB drivers and Firmware from the Samsung Germany website I went from yakjuzs (Hong Kong) to yakju.
After doing this, I powered off my phone, and powered it back on.
After the Google Logo and Animation, I get a message box that says "Android Updating...". after short period of time (under 2s) at the bottom of the screen it says "No Service", then the message box says "starting Applications" under the "Android Updating..." message. The phone then finishes initialization as normal and goes to the home screen.
This made me think that my phone might be trying to upgrade from 4.0.1 to 4.0.2. So I went to the system settings > about phone > system updates and checked for updates. It said my phone was up to date, and the version in the about section is 4.0.1.
Has anyone had this happen to them before? Have any ideas on how to fix this issue?
This happens every time I shutoff my phone and turn it back on. I have also tried a battery pull.
Click to expand...
Click to collapse
I ahd this constantly on my Nexus, once I rooted and rommed it went away. I know that is not a valid solution but it was how it stopped for me. Hope you get it sorted.
I was thinking of rooting so that I can get the 4.0.2 or 4.0.3 update so this might work for me too.
Will report back when I give it a shot later tonight
Sent from my GSM Galaxy Nexus using the XDA App
1Speed said:
I was thinking of rooting so that I can get the 4.0.2 or 4.0.3 update so this might work for me too.
Will report back when I give it a shot later tonight
Sent from my GSM Galaxy Nexus using the XDA App
Click to expand...
Click to collapse
I already talked two people on here today into rooting for various problems and both were a success.
Waiting on Google or Samsung to release an update is painful! Root and rom that bad boy up tonight and I bet the issue stops. It only happens me now if I wipe cache or davlik if I need to load a new kernel or something but only happens once then never again! Good luck anyway
This is not an issue.. the system is creating new caches for the apps.. All of them do this, and rooting and rom'ing doesn't "solve" the issue because it still happens from time to time depending on what you load up on your phone.
as josh said, this is totally normal and absolutly nothing to be worried about. there is no way to solve it.
Normally it only happens the first time you turn on the device, or after you flash a new rom, because now it's the first time your loading up the new OS.
once that one time is done, it most likely will never do it again.
Thanks for the help! I may still consider updating manually because I'm impatient when it comes to Google sending the 4.0.2 update
Sent from my GSM Galaxy Nexus using the XDA App
I unlocked and rooted my phone the day I got it on launch day and haven't had any problems until now. My phone randomly turned off and is now stuck in a bootloop. I never installed a custom rom or anything and only rooted to install some root only apps. It just gets to the first screen with Google and the unlocked lock at the bottom and then the google and the lock kind of flicker and move side to side and change colors and then it starts over again.
I'm currently lost, kind of freaking out, and have no idea how to fix this. Any help? Thanks!
Go into fast boot mode and flash stock images.
Sent from my Galaxy Nexus using xda premium
Tried that, but the phone won't turn on at all. Completely dead. Going to Verizon later today, hopefully for it to be replaced. I don't really understand how this happened...if I was messing around with ROMs I would assume it was my fault, but I haven't been.
So Just recently, I tried to install a new kernel on my galaxy nexus (maguro), and everything was going great until I saw that my phone was crashing when I overclocked it from 1.2 to 1.4 and then it wouldn't start, so I pulled the battery and put it back again, and after the boot animation, it just goes blank, almost like it shut off. So I unrooted it and locked it again, and then rooted it again fully, and it's the same problem. The only way I can get it to boot, is by pulling out the battery, connecting it to my computer, and then putting the battery in again, but as soon as I take out the usb cable sometimes it crashes right away, and sometimes it stays there for a couple of minutes and then it crashes. not sure whats going on. If anyone can help me please let me know, as I really want this phone to be fully functional again.
Thanks
Have you tried reflashing the stock images?
Sent from my Nexus 5 using Tapatalk
Do a full wipe and flash a new rom...
This has happened a couple of times. I have the wifi flo Nexus 7 which is unlocked running stock. I got the 5.0 update a while ago and it started getting stuck at the google screen every once in a while. After being stuck at the screen for 10 to 15 minutes, the device would boot up OK. This happened around every 2 weeks or so but it would always boot up eventually. Last week I got the 5.0.2 update and this morning my nexus froze at the google screen. But, it never continued to boot up. I was in a permanent google screen freeze. I couldn't get to recovery. I tried wugfresh and eventually I got to the prone android with the exclamation point. I don't know what I did but all of a sudden it booted up.
Can anyone clue me in as to what is happening. It seems to be lollipop. Any thoughts?
Let me start with some details about the phone:
- It's a Sprint Samsung Galay S3, SPH-L710
- It was rooted and Cyanogenmod was installed successfully, no problems
- Phone was given to my aunt, and she used it for a while
Here's the problem:
A little while ago, she told me the phone turned off and wouldn't turn off again. I told her to charge the phone and see if that helped. She charged the phone and waited for the battery animation to show up full, and then turn on the phone. It booted past the Galaxy S3 logo, past the animated purple Samsung logo, got halfway through the Sprint 4G LTE boot animation with the music and then boom. Shut off. And then back to the battery charging screen but displayed the battery as if it was only 15% remaining. What?? Wasn't it full a minute ago???
Here's what I did to fix it:
Okay so I thought, it's a battery problem. I purchased a second battery from eBay (not OEM) and the same issue occured. Same exact thing happened. I looked up the issue online and it appeared to be a soft brick. I forgot exactly what I did but I downloaded a recovery file and flashed it via ODIN and it turned on. Phew.
I gave the phone back to my aunt and a week later, the same thing happened. Phone dead. Won't start. Won't get past the Sprint boot animation. So I thought to myself, hmm ok. I'll just reflash and do what I did before. But I mean, how often do I have to keep doing this? And she loses data every time I have to flash the phone.
And so I did. I put it into download mode, opened ODIN, browsed for the md5 file (I forgot what file it was, I'm mad at myself for that now) and flashed the phone. It flashed successfully but this time, the phone wouldn't turn on. It kept vibrating as if it's about to turn on but then dies immediately. I left the phone on my desk for a while and all I could hear was *bzzt* [pause] *bzzt* [pause] *bzzt* and I'm thinking, okay. Time to get an OEM battery.
I finally found an original Samsung battery from an authorized Samsung dealer, I was pretty surprised he still had the battery in stock and bought it from him and ran home. Still the same thing. Kept buzzing but won't turn on. And if I do turn it on, it won't get past the Sprint boot animation.
So I looked and looked and looked and looked online and found this: http://forum.xda-developers.com/showthread.php?t=2755793
Long story short, I followed the instructions, flashed successfully with no errors, and now I can boot past the Galaxy logo, boot past the Samsung logo, and finally past the Sprint boot animation until I landed on the Samsung screen. Just a black screen with Samsung that seemed to have a glowing purple around it. I was getting excited. After about 10 seconds, it went to the main welcome screen (the Google setup thing) with the next button and the language selector in the bottom. I was on that screen for about 2 seconds AND THE PHONE TURNED OFF. Back to the battery screen.
What am I doing wrong? Is there something wrong with the phone? Battery? Am I flashing the wrong software? If so, can someone please direct me to the right place?
P.S. If you're thinking, "dude just get her a new phone" she does have a new one now. It's a Galaxy S7 but I really really want to know what's wrong with this phone and it's been annoying me lol
have you tried any other tar.md5 files on it?
youdoofus said:
have you tried any other tar.md5 files on it?
Click to expand...
Click to collapse
I honestly lost track of what I flashed on this phone. Cam you provide me with links to files or just the software version to flash?
heres rwilcos repository. his site is a great place for many things sprint related
http://rwilco12.com/downloads.php?dir=Files/Devices/Samsung Galaxy S3 (SPH-L710)/Stock ROMs/
Might be the power button is faulty...