Ok, so i ran both updates the 3.29.651.6 OTA update
Then the 3.29.651.5 OTA Update
and phone was stock no rooting or anything i was planning on rooting after the
updates where in place. but anyhow after the first OTA my android market app was missing. I figured well after i do the .5 one it might come back and i was wrong it is still missing. Is there a way to put it back on my evo manually ?
or is there something else i should do ?
Thanks for any help ,
John
Well if you plan on rooting anyways, just root and flash a rooted version of the OTA update. If your market doesn't show up when you flash the rooted rom, you can always just download and flash Google apps.
I have a similar problem. I was running what I think was a non rooted 1.47 ota update (friend phone). I say this because I attempted to use simple root a few months ago but it failed. I may have downloaded a PC36IMG.zip file to the sd card though. I say this becasue when I put the phone into recovery and select recovery it fails. It says the PC36IMG.zip image is missing.
Anyway, without recalling my rooting failure from before, today I applied the OTA 3.26 update. Everything went well except that the Market App is missing from the phone. I have not yet run the 3.29 OTA update. I have no idea how to get the market app back. I really don't care about doing a factory reset and loosing my apps and data. I woulld like to keep my pictures and videos though. I am afraid that my half baked simple root attempt from a few months ago has meesed up any prior recovery images. I don't beleive I have the ability to flash anyhing since I can not get passed the PC36img.zip error when choosing recovery from the power down volume recovery screen.
I am not sure what to do now.
I have the same issue! Just updated and the Market app is missing.
Me too~
This is happening a scary bunch!
scoobycarolan said:
This is happening a scary bunch!
Click to expand...
Click to collapse
What does that even mean?
Hi,
I just noticed this was ready to download on my phone today. I downloaded and went to install, but the ClockWordMod Recovery doesn't let me install the update saying, "Image Verification Failed". I assume the problem is that the phone is rooted, and searching through the forums I heard this update isn't really anything big, just removing some German apps or something.
Is there anyway I can stop this update from notifying me? Or anyway to install? My phone is rooted but I'm not bothered about keeping it rooted as at the moment, there is nothing I need the phone to be rooted for. So, either way is fine for me.
Thanks!
If you want to unroot it, just flash generic ruu, more info here http://theunlockr.com/2010/06/07/how-to-unroot-the-htc-desire/
Than simply check for updates and update it
Or wait for few hours for rooted version of this rom
Hi!
I have a branded Desire and installed the update via Recovery. I had to disable the verification to do that (Goldcard inside). But all I got was a boot loop and my phone was derooted. I tried much (e.g. delete my data) and after a couple of hours I found the simple solution: Simply install the update again. Then I rooted my phone and restored the NANDROID Backup I made before I started the update because all of my data was gone.
Then I installed the Update again and this time it worked at the first time. All data was still there. I rooted it again and everything is fine. Don't know why my phone got a boot loop after first try but second try was perfect!
My suggestion: copy the zip from the download folder to the SDcard (made to a Goldcard!!!!) root and to the PC. Just if you need it more than once. Then make a Backup in the Bootloader. Then Install the update via Recovery. If anything goes wrong install the update again!
Got the OTA today. Bog stock not rooted. update failed. After about 30 minutes a retry download button appeared. Pushing it doesn't do anything. Is there a minimum wait between update attempts? Any other ideas?
Same thing happened to me. I have waited 3 days for a repeat but to no avail. I rooted it and installed a custom ROM with the volume fix update in.
http://twitpic.com/7oody4 this?
Mine failed too... mine was just rooted; nothing else
I got the little Android logo with a !
Rebooted again, no update appears; so I decided to just put the update myself.
Twitpik link is broke. Didn't fail during reboot though. Error msg is right in the system update page. The dowload progress bar is grayed out and it says dowload failed instead a percent progress and there is Retry Download button lower right but it doesnt seem to do anything.
texiandave said:
Twitpik link is broke. Didn't fail during reboot though. Error msg is right in the system update page. The dowload progress bar is grayed out and it says dowload failed instead a percent progress and there is Retry Download button lower right but it doesnt seem to do anything.
Click to expand...
Click to collapse
Mine downloaded automatically over night, and asked if I wanted to apply it when I woke up at 6am. Twitpic should work btw, I just looked at it
Mine even said it was downloaded AND verified, but still failed
Rooted on stock rom with CWM.... Without the stock recovery it can't install. Just jumped to a new Rom with the update....I have always hated the auto updates..lol
Is there a way for me to apply this update by itself? Even if I don't have stock recovery? Is it possible to re-set recovery to original without wiping the entire device?
Mine is rooted, stock ROM, CWM recovery.
OTA re-set itself and installed correctly overnight without me doing anything. Not sure why it failed or how it resolved it but it's done.
If you're still having issues try this
http://www.coolsmartphone.com/2011/12/01/galaxy-nexus-ota-patch
Basically its links to the patch (OTA) and how to root/return to stock with a link to the guide on xda
Sent from my Galaxy Nexus using Tapatalk
I eventually received the update. It downloaded and asked for a reboot. I agreed and the phone counted down, then shutdown, but didn't startup. I waited and waited, the power button would not respond, so I removed the battery, and put it back in. It then started up, but still on the old ITL41D software. What did I do wrong? And what do I do now? Is it normal for it to fail to start up aftrr the reboot? Will I get another opportunity?
Sorry for all the questions, but I'm super frustrated
mirilo said:
I eventually received the update. It downloaded and asked for a reboot. I agreed and the phone counted down, then shutdown, but didn't startup. I waited and waited, the power button would not respond, so I removed the battery, and put it back in. It then started up, but still on the old ITL41D software. What did I do wrong? And what do I do now? Is it normal for it to fail to start up aftrr the reboot? Will I get another opportunity?
Sorry for all the questions, but I'm super frustrated
Click to expand...
Click to collapse
Is your phone rooted? If so, I would look at the comment above yours with the link to the patch (and instructions) to flash it manually. If it is not, it will likely allow you to retry in a day or two.
Hope it all works out for you.
EDIT: I just tried flashing the patch manually as per the prior instructions posted and it didn't work. It gave me "Error (Status 7)" and aborted the installation. Although, right when it rebooted back into the home screen, it came up with the official OTA update again. I'm hesitant on trying it again, since it's likely to fail due to whatever reason caused it to fail the first time.
Either way, this is getting aggravating. I really wish there was an easier way to get this patch without needing to lose root and having to re-do things all over again. I have done a TiBu batch run of all of the stuff I need, but still...oh well.
FlareHeart said:
Either way, this is getting aggravating. I really wish there was an easier way to get this patch without needing to lose root and having to re-do things all over again. I have done a TiBu batch run of all of the stuff I need, but still...oh well.
Click to expand...
Click to collapse
Don't think I've ever seen an OTA which left root intact. This occurs when the OTA sets the permissions recursive for the whole directory /system/bin to 755 removing the setuid attribute on the /system/bin/su binary.
The binary will still be there, but will have to have the setuid attribute added back, chdmod 4755, which will then return root.
Does seem odd Google allows the device to be unlocked, but yet unlocked devices get root access wiped. If they claim to want open source and open devices, perhaps they could script an exception for root access and not remove it with every OTA.
Normally, when Error status 7, or any other recovery error, we're in a custom recovery with adb access and can pull the log at /tmp/recovery.log or /cache/recovery.log and examine what caused the issue as more output is stored there than presented on the screen to the user.
Perhaps googling this recovery error code or grabbing the open source from AOSP will show generally what causes it.
Does seem odd the issues other users have had *automatically* cleared themselves after waiting a while.
First idea which comes to mind is perhaps the original OTA had a bug in the scripting and they were slowly replacing and pushing out the updated OTA.
Keep us updated! I'm on the samsung version of ics so I'll probably have to manually push over all the images...but good to keep up with the *official* route.
When trying to install my update, I get signature verification failed in recovery.
Any ideas?
EDIT: Flashed the recovery posted in the Image on Googles site.
Fixed the problem for me.
joeykrim said:
Keep us updated! I'm on the samsung version of ics so I'll probably have to manually push over all the images...but good to keep up with the *official* route.
Click to expand...
Click to collapse
Not technically official, but a MUCH easier way to get the patch and keep all of your settings and root can be done using the slightly modified stock ROM from bigxie (link: http://forum.xda-developers.com/showthread.php?t=1372376)
If you clear just the cache and dalvik, then flash this. You get the patch, SU, and busybox, without losing all of your settings or data.
Worked great for me. Hope that helps!
I have a Yakju Maguro which is currently running JOP40D. I recently installed the ClockWorkMod v6.0.2.3 recovery, and rooted my phone. Now I received the notification for the 4.2.2 OTA update, but as expected CWM gives me an error when attempting to install it. It says "Install Untrusted Package?" and gives me Yes or No as options. Until now, I've always been weary to try the Yes option, so I've always gone for No, and the update obviously didn't install.
So my question is, will it actually work if I select Yes? And if it doesn't, in what condition will my phone be after it fails? Will it boot into the old OS, or will I have to manually re-flash a ROM?
I've tried googling the problem but no one seems to be facing the same exact condition as me. Eveyone reports that the installation simply fails with CWM, and I've never seen any mention of a Yes/No prompt. Also, I haven't found any thread that mentions in what condition the phone will be after the failure, so I'm trying to figure out what's going on.
In addition, I've manually downloaded the "07501b11ad3b.signed-yakju-JDQ39-from-JOP40D.07501b11" zip file from the Google website. Will I be able to flash that instead from CWM, make things simpler?
Thanks for any help.
Hi Guys,
so this morning my SW3 told me there was a system update, cool, so i said yes to the update and let it do its thing.
on coming back, the os version was still the same (LDZ22D) which i thought was odd.
I then did a search and found that there was indeed a new version out (LCA43) and thought something sus was afoot.
I got the twrp from this post http://forum.xda-developers.com/smartwatch-3/development/lwx49k-rooting-easy-t3107501 and booted from twrp
i then pushed the rom i downloaded form here http://www.xperiablog.net/2015/08/2...-update-lca43-intros-interactive-watch-faces/ and promptly tried to flash it like i would any custom rom i would normally flash on any of my other android devices.
I got an error, saying it was expecting "test keys" from a LAZ22D device or a LWX49K device, and that I had LRX22G test keys.
I also tried an ADB sideload which also didn't work.
Am i doing something wrong? Has anyone else ever encountered this?
Full disclosure, I also installed supersu a few months ago, but have had many factory resets since then (new roms on the paired fone) which i wouldn't have thought was an issue?
Cheers for any help you can give
That update only works on stock recovery. Go to my rollback thread and install the complete system of 5.0.1. I put links and directions to all the files. Then roll forward.
Thanks for that @lekofraggle, but I found an easier option, install Sony companion software, reflash "latest" firmware (apparently LAZ22D) then sideload the original update zip. Worked just fine. Just to clarify, I never flashed twrp, just hot booted from it, wondering if root did break ota...
Sent from my Nexus 7 WIFI using Tapatalk
Yes, root breaks most otas, but adb sideload usually works. Glad it was simpler than my doomsday thoughts.