Related
Hi,
I'd like to find out why my ME525 Motorola OTA update now fails...it worked from 2.2 to 2.2.1 before, but I might have rooted and/or installed clockworm recovery and a ton of apks since then...
So here's what I get:
the OTA udate is downloaded, I get a notification that my phone will restart for installation, I press OK and after about 1/3rd into the unzipping/installation I get the picture of the Android robot and an exclamation point inside a triangle.
What do I do wrong?
I use TB to freeze the bloatware on my phone (some 40-some apks the last I've checked) so I was suspecting that it was the problem so I 'unfroze' everything in TB, rebooted and tried OTA again: same result.
Should I (or do I HAVE to?) wipe everything i.e: uninstall CWM recovery and TB before OTA? And if I do so, would re-rooting, and recover from a (TB and/or CWM) recovery backup undo the OTA update?
thanks for any help.
Rooting will stop the updates I believe and I am not sure if the recovery mod does.
It might be worth reflashing the firmware (make a backup of sms, settingst, etc)
Then with the moto bootloader format it to standard, clear cache, log back into Blur once rebooted and try the OTA again if available.
i had a similar problem with my htc wildfire. what you need to do is take off all the custom beta roms and put on the original rom. hope this helps
Thanks guys for the replies.
I've tried doing a factory reset and that didn't do it.
So I bit the bullet and finally did reflash my original sbf and as expected, the OTA update then worked.
Quite a job to bring everything on my phone back to the state it was though..
But on the bright side, I've done my first ever Defy RSD flashing and I've learned a thing or two...
And I finally have the v 2.2.2 Frozen Yogurt installed
Update (5/2/2012):
I think I've isolated the issue as a broken recovery image. It appears that some of us received a broken 4.0.2 OTA and are now suffering for it.
This issue can be completely fixed by manually installing the 4.0.4 update. For reasons stated in my post below (message #9 in this thread), I do not think this issue can be fixed with an OTA update, so don't wait for Google to fix this. Fix it yourself or send it back for a refund.
----
Title says it all.
I have a completely stock GSM Nexus running 4.0.2, YAKJU build. Several times, I have received the notification that the 4.0.4 OTA update is available. Each time when I try to take the update, the phone reboots and gets stuck at the "Google" screen indefinitely.
At this point, the only way to shut the phone off is to remove the battery.
Has anyone else had this problem? I can't believe Google is unable to deliver a working update to a stock phone, especially after the months of delay this has been. (My phone is nearly unusable on 4.0.2 due to the keyboard lag, random reboots and other issues.)
I really don't want to mess with the bootloader due to warranty issues.
Same thing is happening here. Completely stock on 4.02, receive notification for 4.04, downloads, reboots to install, doesn't get past "Google". Not sure what's going on there...
Same here, tried twice now. Left it for about an hour and it went through a stage of the back of the phone getting warm (antenna location, I believe... at the top by the camera) then cooled down later. I thought maybe it was downloading the update? Not sure if it normally downloads before or after the reboot.
Additional info:
Mine's wasn't originally yakju, but I flashed to yakju 4.0.1 from yakjuux (or whatever) when I got it months ago, and was able to get the 4.0.2 update OTA just fine.
Mine was yakju out of the box, so I don't think it's a flashing issue.
Yep, mine too. YAKJU out of the box. I haven't done anything to mod this phone.
I'm going to try to manually update it in the next day or two and share results
No factory reset either
Huh. I thought maybe doing a factory reset from the Settings menu would help. In fact, I can't do that either!
After clicking through all of the confirmation dialogs, the phone reboots and.... get stuck at the Google screen. I have to pull the battery out, just as when applying the 4.0.4 update. Luckily the phone will start up again, but the wipe never happened.
It looks like there's a problem with some Galaxy Nexuses being able to go into recovery, perhaps?
Hi All
I got the exact same problem. Out-of-the-box, no mods, no root, 4.0.2. Got the OTA to 4.0.4 the third time this morning. Still can't pass the "Google" screen.
Solved -- sort of.
Hey all,
I spent some time investigating this issue. Here's what I've determined: for those of us affected with this problem, it appears that we somehow received a botched installation of 4.0.2 (the version we're running currently). What's the botch? Our phones don't have a working recovery image.
You can test this by trying to enter recovery. Turn off your phone. Then, simultaneously press and hold volume-UP, volume-DOWN, and POWER until a screen with an Android on his back appears. This is the fastboot screen. From here, you can choose 'Recovery'. If your phone is like mine, any attempt to go to Recovery will just put you in the dreaded Google logo loop.
So, what's the solution? I'm afraid the only way to resolve this yourself is to unlock the bootloader and do a complete install of the 4.0.4 image yourself. One step of that process is to flash an updated recovery image; this will cure the issue. Fortunately, on the Galaxy Nexus, you can easily re-lock the bootloader with a single command. I have done all of this and can confirm that it works.
If you're not comfortable unlocking the bootloader, the only other way to fix this is to send it back to the vendor. I have a strong suspicion that phones affected by this bug are unable to receive any further OTAs at all. This means Google can't fix your phone by pushing out a different OTA.
Final warning: until this is fixed, you can't do a factory reset, either -- that process will fail because it, too, uses the recovery. So don't plan on selling your phone on eBay until you get this fixed.
Your research is much appreciated modenastradale. It seems this is a fairly big **** up on Google's part. But I guess these things happen. I don't have any particular problems with unlocking the bootloader, I just didn't feel like wiping the phone right now and having to reinstall and set everything back up again which is why I've remained stock this whole time.
Unlike previous phones, this one has felt great out of the box, so I've never had the need to root it to get more performance out of it.
I guess this will be the project for the weekend. Yay!
Looks like a good opportunity for me to switch to the US version (takju).. even though it's 99.9% the same right now. Just in case they give us a better radio for the region.
Idea:
What if I flash the recovery only? (like step D.12 here: http://forum.xda-developers.com/showthread.php?t=1626895)
I already have an unlocked bootloader, so it looks like I wouldn't need to wipe the system to unlock it. I guess I would get the 4.0.2 full image and flash that recovery (not the 4.0.4), though I'm not sure it would made a difference anyway.
I might try it out, but still interested in maybe switching to Takju anyway. I thought about anything that I'd lose by wiping, and since almost everything is on google's cloud (gmail, google music, coctacts, pics on google+, etc) it's not a big deal to wipe.
Fixed
The method I suggested in the last post worked!
You need to be able to flash a recovery image though, which I think would mean you need an unlocked bootloader? The benefit of doing this over just flashing the complete 4.0.4 image is that you don't need to wipe the phone (assuming you already were unlocked)
In more detail, here are the steps I took.
- Preparation (I already had this done) - have Samsung drivers installed on your PC, ADB, fastboot, etc. - check other threads for how to, such as: LINK
- Follow this post's how-to for flashing the recovery image - the poster also has the stock 4.0.2 link, which I can't find on google's site anymore: LINK
- The only command I ended up using is
Code:
fastboot-windows.exe flash recovery F:\recovery.img
Where F:\ was the location I extracted the image file to.
- Restart via:
Code:
fastboot reboot
- When it restarted, it gave me the OTA notification and was able to install fine.
I don't know if the OTA notification would automatically show for everyone, if not you can try to check for updates in the settings or try some of the step on the thread: LINK
related issue
I found and issue on code.google.com that seems related to this.
I'm linking them in the hopes of getting some official response about this.
Just search for number 29954 on code.google.com as I'm not allowed to post links here yet.
This worked perfectly for me. Glad to have that done with. Didn't lose any data at all.
I have this issue also. Stock Galaxy Nexus from the Spain, no mods, not unlocked.
Its necesary unlock bootloader to flash a recovery image
I can reboot my Nexus after going through the install of 4.0.4 (my phone don't get stuck at the Google logo), but the version stays at 4.0.2 however.
Do I also have to unlock bootloader and flash 4.0.4 etc. or is there another way to work around the update problem?
Stock and unlocked Galaxy Nexus bought (and in use) in The Netherlands.
Thanks!
Hi Guys,
I have CID__001 in the UK and received the JB update this morning - great, I've been waiting for it for months, that's why I didn't bother rooting my phone like i did with my desire.
So my phone boots up and EVERYTHING keeps crashing. com.android.phone, android.process.acore, gapps, htc sync etc. Constant error messages, so i can't get rid of them to do anything. The SIM card won't prepare, the home screens never load so I can't access my apps, the battery is draining like crazy, I can't sync my contacts because sync crashes, I called the phone from my landline, the landline phone rang, but the HOX didn't. I also can't access my files on the phone through the computer, the computer recognises it's there, but when i click on it it says 0 files. I don't have a backup, but if i have to lose them to get my phone working, so be it. It's completely messed up.
I have rebooted several times, also in safe mode, but it always happens. I also tried running the RUU because I now have HBOOT 1.36 but it told me it was the wrong RUU and wouldn't update.
I wanted to copy the update file onto the external storage and rename it update.zip so I could flash it from recovery, but i can't access the files through the phone or the computer so that was a bust.
I cleared the cache from the recovery menu, still no joy.
I haven't done a factory reset yet, because I don't want to lose everything and I don't think it would work if I get all the crashes in safe mode.
I need some help, I've got some experience rooting/flashing etc, I did it a lot on my desire, but I am stuck here. I'd like to be able to fix it myself, as all HTC will do is send me a refurbished phone, charge me for the pleasure and I'll lose my data anyway.
My bootloader is unlocked, but I never rooted or flashed anything on it, it was purely stock with an unlocked bootloader.
Any suggestions? I really don't know where to go from here. Typical that I didn't meddle with my phone so I could have the official update and it messes up my phone.
Have you got stock recovery or custom?
Sent from my HTC One X using xda premium
stock
Could be you need a factory reset which is what i would do.
Yep, its gonna have to be a factory reset, if it still don't work contact HTC clearly a fault of theirs, cant see how unlocked bootloader can play a part..
Are you 100% its stock coz you can't clear cache from stock recovery... You need custom recovery.
Sent from my HTC One X using xda premium
Factory reset worked
Yes, my recovery is definitely stock. There aren't many options, but erase cache is one of them.
Factory reset worked. I have lost everything, had to reset from the fastboot screen (not sure what it's called) because it would not work from the phone settings - whatever was necessary to factory reset my phone kept crashing. Resetting from there also formatted my external storage, all my photos and music and everything are gone.
Really annoyed at HTC right now. I waited patiently for months, could have easily rooted and flashed a custom JB ROM but I waited and their update has caused me to lose everything.
Does anyone know why this would have happened or have heard of it happening to other people?
On the up-side...Jelly Bean is now rolling out in the UK!
cec24 said:
Yes, my recovery is definitely stock. There aren't many options, but erase cache is one of them.
Factory reset worked. I have lost everything, had to reset from the fastboot screen (not sure what it's called) because it would not work from the phone settings - whatever was necessary to factory reset my phone kept crashing. Resetting from there also formatted my external storage, all my photos and music and everything are gone.
Really annoyed at HTC right now. I waited patiently for months, could have easily rooted and flashed a custom JB ROM but I waited and their update has caused me to lose everything.
Does anyone know why this would have happened or have heard of it happening to other people?
On the up-side...Jelly Bean is now rolling out in the UK!
Click to expand...
Click to collapse
probably there was a problem with some other apps on the phone, so maybie that wasn't htc fault. But wasn't mass storage working? If yes you could backup everything before doing factory reset.
cuzzo94 said:
probably there was a problem with some other apps on the phone, so maybie that wasn't htc fault. But wasn't mass storage working? If yes you could backup everything before doing factory reset.
Click to expand...
Click to collapse
My phone showed up under my computer, but when I tried to access it, it said 0 files...I tried. Failed, but tried.
This morning I received the Android 8.1 OTA, it took over an hour to process and when it had finished my tablet had been wiped.
Not happy!
Hi same thing happened to me . I called Google up and they gave me a useless answer.
All I can say to others is do not update to 8.1 just yet or back up your data.
Did you by any chance have your bootloader unlocked?
Bhushan8128 said:
Did you by any chance have your bootloader unlocked?
Click to expand...
Click to collapse
I can't remember, it's possible...
Reset for me, and bootloader is NOT unlocked for either device we have (at least I was the first to take the update, so can plan for my girlfriend). Didn't expect this. Especially after the update to 8.0 left things alone. I had JUST started to install apps with data (long time flasher... left these stock, so I tend to avoid non-cloud apps, especially without root backup options).
Wish I'd come on here half an hour ago. Just got the notification about the update and has wiped mine as well.
Sent from my Pixel 2 using Tapatalk
Same here. Just did the OTA. Basically new tablet, never unlocked the bootloader etc..
Interestingly I could not initialize the tablet as new device.
The error I got was that the device was resetted and only the previous owner can go on with the setup (something like this).
I logged into my Google account and now my Pixel C is loading the backup.
But I highly doubled that many of my apps settings were backuped.
In the same boat. Jumped straight into the OTA when prompted, ended up with factory reset and all internal storage wiped. Stock ROM, only thing possible unusual we that when I first went to install it complained I didn't have free space. Fixed that and tried again, ended up reset and wiped.
with my Pixel C it is looping between "Google" and "erasing" and getting no further
Got the OTA update too and it wiped my device, good thing I just brought it so had nothing on it
Amazingly incompetent - who do they think they are - Apple?!
TimSharrock said:
with my Pixel C it is looping between "Google" and "erasing" and getting no further
Click to expand...
Click to collapse
I tried factory reset, and it seemed to make no difference, but I left it looping for several more hours, and it eventually booted into a wiped state. I reconnected it to my account, and is now merrily reinstalling everything from the backup
I just updated with adb sideload and full OTA Image. No wipe for me.
Apparently this is now fixed, time will tell.
https://productforums.google.com/forum/#!topic/nexus/rwWqnT_397c
Hi everybody I am new here so I apologize for my lack of knowledge.
This past Sunday evening I attempted an OTA update on my Verizon S10+. Upon the phone restarting post-update it went into a reboot loop. I have tried everything I am capable of and cannot get it out of the loop. I can access the recovery menu (may not be correct term) and have cleared the cache partition, attempted to "fix apps". Also have attempted to launch in safe mode, also have let the phone go totally dead and restart, but still looping.
Here is the issue, I am fairly certain a factory reset would fix it, I found maybe one or two people with this exact problem after this most recent March update. They said factory reset worked. However, I have some pictures on the phone's internal storage that is not backed up anywhere. I know, very stupid of me to not have been backing up, I should know better.
Last night was my final attempt at a fix that hopefully wouldn't wipe my pictures. I attempted (and I thought I succeeded) to flash the March update to the phone using Odin. Hoping that might result in a successful install of the update and resolve the issue.
No change after flashing the phone. I don't know what to do to try to save those pictures, I was wondering what would happen if I waited for the next update and then tried to flash that to the phone using Odin.
I'm at a loss, you all seem very knowledgeable and helpful and I am already appreciative of the help I have found in past threads here. Any suggestions/thoughts would be great.
Thanks,
Sam
@hainguyenthao Just generously spent a solid hour and a half helping me. It appears I did not flash my phone correctly and/or the data on my phone was already toast after the initial OTA update failure that caused the reboot loop.
Fixed by @hainguyenthao even though I screwed up my own data. Phone is working again!