Related
So I just got a notification from ATT saying that there is a software update available. Has anyone else gotten this and installed it? Is it jelly bean or a minor update? I haven't tried it myself because I am rooted.
Sent from my HTC PH39100 using xda app-developers app
Bigluc said:
So I just got a notification from ATT saying that there is a software update available. Has anyone else gotten this and installed it? Is it jelly bean or a minor update? I haven't tried it myself because I am rooted.
Sent from my HTC PH39100 using xda app-developers app
Click to expand...
Click to collapse
Yes just got it I'm Rooted & S-OFF
it won't be jelly bean since the ONE X series doesn't have it yet haha just a minor I bet
Can someone detail this update?
*Edit* Called AT&T the Update was released October 9th it an 13mb update so yea Minor the girl
on the phone was talking to fast for me to listen what it offers
Got it last night. Android version did not change. Couldn't tell for sure if any other numbers updated. It wouldn't kill AT&T to send out an e-mail or text message telling us what the update was for.
got the same thing i have no idea what is the update
Update has my phone stuck in a darn boot loop..any idea what it is?
Sorry bludiamond.
Since my phone is rooted, I did not want to install this update. It's quite upsetting that AT&T forces the update unconditionally.
Anyway, I had let the download to complete, but did not let it to install. The update did prompt me, whether I want it to install now, or later. I had opted for later.
Then, after some Googling, I had deleted the download (from /sdcard/Download), and had un-installed the following services: com.htc.demoflopackageinstaller and com.smithmicro.dm.
Then, I've rebooted the phone. Afterwards, the phone still had a notification, that there's an update ready to be installed. When, selecting the notification, updater did realize that the downloaded file is gone, and had prompted me whether or not I'd like to download the update again, on which, I had responded no. The notification is gone, and AT&T did not prompt me to download and install the update again, at least not yet.
My phone seems to be OK.
I was hoping for a new Radio/RIL. That's not what this is...
New Kernel & Recovery. If you are rooted and on a custom rom Do Not run the update. I'm sure the developer of the rom you are on will work to add anything useful to future updates.
The dates on these files is 7/27/12 so it took At$t over to months to test & release.
To delete it look in /cache/fota/OTAPkg.zip
Once gone you shouldn't be bothered by it anymore.
Have anyone successfuly downloaded and installed it?
What's new? Bluetooth bugs fixes? Usable Voice Dialer? Better battery life?
Sense 4.0?
Please comment.
Sent from my HTC PH39100 using xda app-developers app
gattech said:
Have anyone successfuly downloaded and installed it?
What's new? Bluetooth bugs fixes? Usable Voice Dialer? Better battery life?
Sense 4.0?
Please comment.
Sent from my HTC PH39100 using xda app-developers app
Click to expand...
Click to collapse
Think the majority of users on here are rooted and running custom roms so they wouldnt' be installing this.
I forgot I was unlocked and rooted. Now I am really stuck. How do I get out of the dead Android loop?
I googled the update, and found this on the ATT Support website.
Beginning on October 9, 2012, AT&T and HTC have released an additional software update for the HTC Vivid that will be available via firmware over-the-air (FOTA). This 13MB software package updates the firmware version to 3.26.502.56_R23 and improves sensor performance.
NOTE: Customers must have a data SOC in order to obtain any FOTA updates. Customers who have a data opt-out SOC are not able to receive FOTA updates.
strose09 said:
Think the majority of users on here are rooted and running custom roms so they wouldnt' be installing this.
Click to expand...
Click to collapse
Hmmm....
Sent from my HTC PH39100 using Tapatalk 2
For the users in boot loop I just recovered from it. Boot into cwm and clear the cache a couple of times and reboot.
Sent from my HTC PH39100 using xda app-developers app
kos26 said:
For the users in boot loop I just recovered from it. Boot into cwm and clear the cache a couple of times and reboot.
Sent from my HTC PH39100 using xda app-developers app
Click to expand...
Click to collapse
This Fix works. My phone no longer boot loops
3f62011 said:
Sorry bludiamond.
Since my phone is rooted, I did not want to install this update. It's quite upsetting that AT&T forces the update unconditionally.
Anyway, I had let the download to complete, but did not let it to install. The update did prompt me, whether I want it to install now, or later. I had opted for later.
Then, after some Googling, I had deleted the download (from /sdcard/Download), and had un-installed the following services: com.htc.demoflopackageinstaller and com.smithmicro.dm.
Then, I've rebooted the phone. Afterwards, the phone still had a notification, that there's an update ready to be installed. When, selecting the notification, updater did realize that the downloaded file is gone, and had prompted me whether or not I'd like to download the update again, on which, I had responded no. The notification is gone, and AT&T did not prompt me to download and install the update again, at least not yet.
My phone seems to be OK.
Click to expand...
Click to collapse
After getting my phone out of the boot loop I tried this and am no longer prompted to update. Thank you for the help
Apatche69 said:
This Fix works. My phone no longer boot loops
After getting my phone out of the boot loop I tried this and am no longer prompted to update. Thank you for the help
Click to expand...
Click to collapse
I had the looping issue too. I cleared the cache once and rebooted. Received a message that there was a problem with the update and to wait for the next update. Phone seems to be okay since.
I'm unlocked s/on..no custom rom..it was so early, I must have hit the wrong button, so I'm stuck in the loop and can't seem to get into recovery either..ugh
I'm stock - not rooted. I did do the download without any problems, although you do have to manually reboot after the update.
It supposedly improves the sensor. Not sure what that means, but that's what the ATT website says. Other than it changing my default ringtone, I don't see any difference.
Could not get it out of the loop. Took it to the service center and neither could they..they ended up replacing it under warranty..thank goodness. Said that another lady came in with the same issue as well.
AT&T Upgrade to Nowhere
I'm running stock on the HTC Vivid and got this upgrade pushed out by AT&T. This is the second AT&T upgrade I've done on this phone (the first was to ICS not long after I got the phone).
I ran the update yesterday, which force rebooted my phone and I watched as the upgrade downloaded and installed, then came back up.
NOTHING has changed. I don't know what AT&T supposedly upgraded, but it's certainly nothing noticeable.
I didn't even get the "3.26.502.56_R23" software designation that the AT&T help article says I was supposed to see.
It was literally an upgrade to nowhere. Not sure why I wasted time off the grid and battery power on it.
As usual-- AT&T fail.
At least no harm was done.
I was rooted, stock ROM, and got the notification yesterday. I postponed as much as I could but it finally wouldn't let me anymore and I let it try to update.
Of course, went into a boot loop. I did eventually get the boot looping to stop by reflashing the wxc recovery image and CWM-root, but then my wifi wouldn't work. I suspected some difference in the kernel version or some other borking of the update.
Long story short, I had to re-lock, go back to stock, and re-unlock and root again. Then spend the time (ongoing) to get my environment back. Thank goodness for Titanium backup pro and Dropbox. LOL.
Wish I could bill AT&T for the 18 hours I've spent. And if they push it to me again, I'll be irritated.
I had the notification for 4.2 update yesterday morning and after pondering for the day I decided to initiate the upgrade which for some reason or another the update failed.
Is there anyway of finding out why the update failed and since the failure I've had no further notifications of the update so how can I try the update again?
Thanks
Jon
Update just failed for me too, which having read up, looked like it might have been because of having an alternate recovery installed.
So I removed the recovery .................UPDATE FAILED
Removed root.....................................UPDATE FAILED
Locked Bootloader..............................UPDATE FAILED
Full system wipe.................................UPDATE FAILED
You can force a retry by going to App,------All-------Google Services Framework and stopping the process and wiping the data
Then checking for update manually.
Some folks say you can have problems with Play and push notification after the framework wipe, but as I had gone the route of restoring to default, I wasn't bothered as I will just do the same again.
I wonder if there is a deeper issue however, than just my tablet.
Phil
jonchill said:
I had the notification for 4.2 update yesterday morning and after pondering for the day I decided to initiate the upgrade which for some reason or another the update failed.
Is there anyway of finding out why the update failed and since the failure I've had no further notifications of the update so how can I try the update again?
Thanks
Jon
Click to expand...
Click to collapse
did you guys did anything or change anything from system, like change the proxyprovider.apk for flash support? Mine failed through OTA and even via manual update but then I changed back the those apks and things went well and now I am on 4.2. Just sharing my experience and hope it can help you guys. somewhat.
If you guys replaced the stock recovery, deleted or froze any stock apps,or modified any system configuration files, OTA is going to fail.
My tablet updated just fine and it is both rooted and unlocked. My galaxy nexus which is the same (both rooted and unlocked) for some reason fails on the 4.2 update.
I had the exact same problem over the past two days, I don't have a custom recovery, just unlocked bootloaded and root.
just lou said:
If you guys replaced the stock recovery, deleted or froze any stock apps,or modified any system configuration files, OTA is going to fail.
Click to expand...
Click to collapse
OOOOOH! I froze then deleted the KOREAN IME app, because why the heck do I need a Korean app on my tablet? Hmm, so what are my options? Can I just redownload the Korean IME off the play store and OTA will work then?
Was there any other forced IME like Chinese that's 'baked in' to the Google ROM? I forgot if I may have deleted any others, but I think it was only Korean.
just lou said:
If you guys replaced the stock recovery, deleted or froze any stock apps,or modified any system configuration files, OTA is going to fail.
Click to expand...
Click to collapse
That explains it then I've deleted and frozen stock apps.
Thanks
I'm the same, i deleted system apps.
Is the only way to fix this to use a pc and adb the 4.1.2 zip and gapps?
Is there any way to fix it from the device itself?
(I've tried flashing the 4.1, 4.1.2 and 4.2 via CWM)
Would reflashing the 4.1 gapps help?
Sent from my Nexus 7 using xda premium
I had the same problem. Used titanium backup and the "integrate system apps updates into ROM" option and then couldn't update to 4.2.
Tried several things I read in this forum but nothing worked.
Had to erase everything and flash the stock ROM I downloaded from Google. They have a 4.2 stock ROM too so didn't need to update afterwards.
Then restore all your apps from backup and you are set.
Sent from my Nexus 7 using Tapatalk 2
Wow, all because a damn Korean IME app? Geez, what a pain, Google. :|
Chocoburger said:
Wow, all because a damn Korean IME app? Geez, what a pain, Google. :|
Click to expand...
Click to collapse
The alternative is that you restore your system folder to its original state (i.e. get hold of that Korean IME app, stick it back in /system/app and set the correct permissions). I had to do this with Google Wallet but it can be done if you know exactly what you've changed and avoids flashing a factory image and setting your device up again (albeit that Titanium makes this relatively painless now).
Have a brand new 32 GB N7, and having the same update fail, right out of the box, like wtf
CFRTim said:
Have a brand new 32 GB N7, and having the same update fail, right out of the box, like wtf
Click to expand...
Click to collapse
Me too. Also a 32gb N7. I owned it less than a week. Multiple factory resets didn't correct the issue either. I returned it to the store for a refund. Didn't want to keep a device that would never install updates.
I have 32 gigabyte Nexus 7 and it came with Android 4.2 out of the box so I guess no problems with the updates
Sent from my Nexus 7 using XDA Premium HD app
CFRTim said:
Have a brand new 32 GB N7, and having the same update fail, right out of the box, like wtf
Click to expand...
Click to collapse
So your saying you opened it, turned it on, signed in.....then your status bar should show system update available, click it, accept, let it do its thing and it just failed?
Sent from my Nexus 7 using Tapatalk HD
If you search the forums this has been addressed and solved. You need to reflash the os - you don't need root. Use wugs toolkit. Its a problem on googles end where the nexus was formatted incorrectly, and a reflash fixes it.
Sent from my Nexus 7 using Tapatalk HD
Yep. Got the Android robot on his back, with the triangle/exclamation point on top of him, after downloading, restarting and almost complete install. I've tried multiple times and miserably failed each time, at the same point. Eventually, I was able to manually update it using Wug's Nexus Toolkit, since all other methods failed. Thank you Wug
Sent from my Nexus 7 using Tapatalk 2
Hey guys,
I'm using a stock S3 LTE (i9305) from my carrier and my device status is "Modified" even though I've never attempted to root it and can't run rooted apps. Can you guys please go Settings -> scroll down to About device at the bottom -> Status -> scroll to the bottom and check whether your "Device status" is Normal or Modified?
I've not flashed any roms nor rooted but it says modified for me. When I tried checking for updates it says my device has been modified. Strangely it occasionally reverts to "Normal" after a reboot. Just wish to see if anyone else has this problem.
There is also no triangle that appears during the boot up sequence. Is my warranty void?
Thanks!
From memory I think this is normal!
Mine (Australian Telstra i9305T) says "Normal" I'm afraid. Maybe the warehouse boyz got to yours
even though you are not rooted , Did you install CWM ?
I'm from Portugal, and I have the same... And when I try search for software updates I have this error
Sent from my GT-P7500 using xda app-developers app
Hi,
Mine also appears as "Modified"
Country: Portugal
Carrier: TMN
I Would assume that this is due to Carrier modifications to add their bloatware. But then again maybe not.
risinhux: I guess you are talking about the error: Your device has been modified. Software update are not available.
dhkx said:
Hey guys,
I'm using a stock S3 LTE (i9305) from my carrier and my device status is "Modified" even though I've never attempted to root it and can't run rooted apps. Can you guys please go Settings -> scroll down to About device at the bottom -> Status -> scroll to the bottom and check whether your "Device status" is Normal or Modified?
I've not flashed any roms nor rooted but it says modified for me. When I tried checking for updates it says my device has been modified. Strangely it occasionally reverts to "Normal" after a reboot. Just wish to see if anyone else has this problem.
There is also no triangle that appears during the boot up sequence. Is my warranty void?
Thanks!
Click to expand...
Click to collapse
Hold the home button,down volume button and power button at the same time and put it into odin mode and there should be info there,whats official and whats not..
seeyouinmdreams said:
Hi,
Mine also appears as "Modified"
Country: Portugal
Carrier: TMN
I Would assume that this is due to Carrier modifications to add their bloatware. But then again maybe not.
risinhux: I guess you are talking about the error: Your device has been modified. Software update are not available.
Click to expand...
Click to collapse
Yes... I'm talking about this error...
My device are TMN too!
Sent from my GT-P7500 using xda app-developers app
My phone is not rooted as well and it's currently running on jelly bean 4.1.1. I have never rooted my phone ever but when I clicked software update in the setting, it doesn't allow me to and it says device is modified. What should I do to update my phone?
Thanks in advance. =)
Kellyeung13 said:
My phone is not rooted as well and it's currently running on jelly bean 4.1.1. I have never rooted my phone ever but when I clicked software update in the setting, it doesn't allow me to and it says device is modified. What should I do to update my phone?
Thanks in advance. =)
Click to expand...
Click to collapse
try factory reset might have to do it twice though... good luck
dhkx said:
Hey guys,
I've not flashed any roms nor rooted but it says modified for me. When I tried checking for updates it says my device has been modified. Strangely it occasionally reverts to "Normal" after a reboot. Just wish to see if anyone else has this problem.
There is also no triangle that appears during the boot up sequence. Is my warranty void?
Thanks!
Click to expand...
Click to collapse
Same issue here with Samsung GT-I9305 Swisscom Branded. After a reboot the "modified" is back to "Normal" and you can update.
Swedish Tele2 operated Phone here.
Mine is normal - I guess it has been said before, your operator might have modified it
Call them and ask.
Skickat från min GT-I9305N via Tapatalk 2
stock rooted
have recently rooted my device but from what i can recall it said modified before i gained root access, when i checked software update last night it was able to check for update but it now has reverted back to modified...any thoughts?
telstra GTI-9305T stock, rooted
jimyeah said:
have recently rooted my device but from what i can recall it said modified before i gained root access, when i checked software update last night it was able to check for update but it now has reverted back to modified...any thoughts?
telstra GTI-9305T stock, rooted
Click to expand...
Click to collapse
factory reset the phone ... should work
rizky77 said:
factory reset the phone ... should work
Click to expand...
Click to collapse
I can confirm that a factory reset restores the status from modified back to normal.
Sent from my GT-I9305 using Tapatalk 2
I have just tried a new method on my rooted gti9305t to check for an ota update without having to factory reset the device.
*go into settings, then apps.
*tap on the tab that says 'all' and scroll down to google services framework.
*tap 'clear data', and then 'force stop'
After this process when you go back to software update it should check for the update, it worked for me.
:thumbup:
Sent from my GT-I9305T using xda app-developers app
jimyeah said:
I have just tried a new method on my rooted gti9305t to check for an ota update without having to factory reset the device.
*go into settings, then apps.
*tap on the tab that says 'all' and scroll down to google services framework.
*tap 'clear data', and then 'force stop'
After this process when you go back to software update it should check for the update, it worked for me.
:thumbup:
Sent from my GT-I9305T using xda app-developers app
Click to expand...
Click to collapse
For me, this method don't work
Sent from my GT-P7500 using xda app-developers app
No dice
T-Mobile Note 2 (SGH-T889, v4.1.1, Build number JRO03C.T889UVALL4, Baseband T889UVALL4, rooted),
Clearing data / force stop had no affect:
Your device has been modified. Software updates ate not available
(Being rooted, well yes, it is "modified“, but it's worth a try).
People, I solved my problem: D
I used the Triangle Away
Don't look for a fix, you should be able to get a new phone from your Telco, I wouldn't accept a pre-used device
Sent from my GT-I9305 using xda premium
Hi, I used PwnMyMoto-1.4.3-TMobile.apk to get root on my T-mobile Moto X.
http://forum.xda-developers.com/showthread.php?t=2444957
Today, there was an OTA update that downloaded and said it would install. Now the phone is stuck in a boot loop. It boots OK but about 45 seconds after loading it shuts down and reboots. I'm guessing its because the PwnMyMoto removed the stock recovery or altered it to be unable to install the OTA update. However I guess the phone still sees the downloaded OTA update and wants to install it, so it reboots the phone to try to install.
I can't post in the PwnMyMoto thread because I'm too new to XDA
I have froze the ota apk to try to prevent this
small update. I used the T-mobile bundle here to get stock recovery.img and put that on my phone (because PwnMyMoto removes it) and then the OTA update installed. I guess instead I could have removed the downloaded update if I knew where it was!! After the OTA I lost root
http://sbf.droid-developers.org/ghost_rcica/list.php
emerica243 said:
I have froze the ota apk to try to prevent this
Click to expand...
Click to collapse
what do you mean by this? Can you tell me how to do that?
jackashe said:
what do you mean by this? Can you tell me how to do that?
Click to expand...
Click to collapse
Freezing a particular app can be done using Titanium Backup. Its available for download on play store. Titanium Backup requires root permissions. Freezing an app will leave the app on your phone but it wont work cuz its frozen lol... the app wont be uninstalled. this way if you decide later that you need the app then you can just unfreeze it and use it.
OK, I have TB and I know it supports freeze. I didn't realize you could freeze the OTA capability as a separate program. However given that I already downloaded the update, its too late to freeze.
jackashe said:
small update. I used the T-mobile bundle here to get stock recovery.img and put that on my phone (because PwnMyMoto removes it) and then the OTA update installed. I guess instead I could have removed the downloaded update if I knew where it was!! After the OTA I lost root
http://sbf.droid-developers.org/ghost_rcica/list.php
Click to expand...
Click to collapse
sorry if i or many people would have seeen this earlier we could have stopped you. Always be patient next time because you may have lost root forever now. Not that we know a patch will come through to allow us to maintain root in 4.3, but jcase said he proabbly wouldn't make a rot for 4.3 because it could be a pain and he doens't want to waste any of the exploits he knows of. You could always figure out a way your phone is bad and go exchange it and root again and don't take OTA until someone has figured out something to do to maintain root. It would be worth it for me.
You always have the option to unlock your bootloader with the T-Mobile version. I plan on unlocking the Dev edition I will be buying and then buying a SquareTrade warranty and that will cover any issues I might ever have including breaking/water damage.
jackashe said:
small update. I used the T-mobile bundle here to get stock recovery.img and put that on my phone (because PwnMyMoto removes it) and then the OTA update installed. I guess instead I could have removed the downloaded update if I knew where it was!! After the OTA I lost root
http://sbf.droid-developers.org/ghost_rcica/list.php
Click to expand...
Click to collapse
FSRBIKER said:
You always have the option to unlock your bootloader with the T-Mobile version. I plan on unlocking the Dev edition I will be buying and then buying a SquareTrade warranty and that will cover any issues I might ever have including breaking/water damage.
Click to expand...
Click to collapse
Yup I almost unlocked the boot loader but instead I was able to flash stock recovery. I wish android itself was smart enough to not try to install OTA when recovery was gone. I finally read through the jcase thread and I think I might have been able to delete the downloaded OTA by running:
Code:
fastboot erase cache
fastboot erase userdata
But I didn't try that. I also don't know what exactly that would have erased.
I will certainly look into a SquareTrade warranty!
Argh, I'm having the same problem. I have a Sprint version with unlocked bootloader and PwnMyMoto 1.1. Began after OTA update today. I have about 20 seconds after booting up that I'm able to do things on the phone before it goes into a loop; I've tried uninstalling the camera and disabling the gallery, which I thought were the two things that were updated. Safe mode doesn't work, nor does trying to enter recovery through fastboot. I've even tried factory resetting the phone from settings, but it can't do this before the power-down process begins. I haven't had any success with working through adb and the command prompt on this phone (device not found). At this point, I'm SOL and out of ideas with a bricked phone. Any other ideas?
UPDATE... Tried the fastboot erase cache & userdata; essentially performed a hard reset of device. Not the most convenient thing, but at least I have a working phone now.
so if we freeze updater and ota, we should be covered?
not sure about the other suspect apk with is fota.apk. I rename otacerts.apk as well. I may be a little paranoid about this but bricking is definitely not an option
jayboyyyy said:
sorry if i or many people would have seeen this earlier we could have stopped you. Always be patient next time because you may have lost root forever now. Not that we know a patch will come through to allow us to maintain root in 4.3, but jcase said he proabbly wouldn't make a rot for 4.3 because it could be a pain and he doens't want to waste any of the exploits he knows of. You could always figure out a way your phone is bad and go exchange it and root again and don't take OTA until someone has figured out something to do to maintain root. It would be worth it for me.
Click to expand...
Click to collapse
Yeah, root is great... I guess I'll just have to keep fingers crossed that jcase works on 4.2.2 post OTA but since it hasn't even been pushed to all carriers maybe it won't happen. Yes, I should have NOT gotten the OTA, but once it had downloaded my phone was totally unusable until I restored recovery and it installed itself.
jackashe said:
Yeah, root is great... I guess I'll just have to keep fingers crossed that jcase works on 4.2.2 post OTA but since it hasn't even been pushed to all carriers maybe it won't happen. Yes, I should have NOT gotten the OTA, but once it had downloaded my phone was totally unusable until I restored recovery and it installed itself.
Click to expand...
Click to collapse
Curious have you tried to reroot, and for future reference I believe ota are usually in cache under the previous build # for Verizon at least.
shane1 said:
Curious have you tried to reroot, and for future reference I believe ota are usually in cache under the previous build # for Verizon at least.
Click to expand...
Click to collapse
I did try rooting again using PwnMyMoto-1.4.3-TMobile.apk but it failed to install (since one of the exploits it used is patched)
I have t-Mobile but how would I get to the cache? My phone would boot for about 45 seconds and in that time-frame I could adb shell into the phone but could not find the path for the OTA update. Do you mean it would be in /cache/some-build/ or so?
Yes in cache and you would have to attempt from a PC , which might not have been possible because the phone kept rebooting. Also I am sry for your loss
Would ota root keeper do anything for us?
Sent from my XT1058 using XDA Premium 4 mobile app
IncredibleHulk6 said:
Argh, I'm having the same problem. I have a Sprint version with unlocked bootloader and PwnMyMoto 1.1. Began after OTA update today. I have about 20 seconds after booting up that I'm able to do things on the phone before it goes into a loop; I've tried uninstalling the camera and disabling the gallery, which I thought were the two things that were updated. Safe mode doesn't work, nor does trying to enter recovery through fastboot. I've even tried factory resetting the phone from settings, but it can't do this before the power-down process begins. I haven't had any success with working through adb and the command prompt on this phone (device not found). At this point, I'm SOL and out of ideas with a bricked phone. Any other ideas?
UPDATE... Tried the fastboot erase cache & userdata; essentially performed a hard reset of device. Not the most convenient thing, but at least I have a working phone now.
Click to expand...
Click to collapse
Can you please tell me how you did this? Thanks in advance
Perhaps this thread helps http://forum.xda-developers.com/showthread.php?p=46179190#post46179190
Erk, after getting into the same post-Root update loop, I flashed back to stock using the recipe here: http://forum.xda-developers.com/showthread.php?p=46175635&postcount=8
I now have 13.9.0Q2.X-116-X-17-51 installed.
When I go to System updates to update to the OTA update 13.0Q2.X-116-X-17-54, I get told that I am already updated to the latest version.
Any help would be much appreciated!
jayboyyyy said:
sorry if i or many people would have seeen this earlier we could have stopped you. Always be patient next time because you may have lost root forever now. Not that we know a patch will come through to allow us to maintain root in 4.3, but jcase said he proabbly wouldn't make a rot for 4.3 because it could be a pain and he doens't want to waste any of the exploits he knows of. You could always figure out a way your phone is bad and go exchange it and root again and don't take OTA until someone has figured out something to do to maintain root. It would be worth it for me.
Click to expand...
Click to collapse
manfly9884 said:
Can you please tell me how you did this? Thanks in advance
Click to expand...
Click to collapse
You have to make sure you have downloaded & installed the Android SDK and the latest Motorola Android drivers to your computer. On your phone, shut it down before it has the chance to re-enter the boot loop cycle. Then press the down button simultaneously with the power button for a few seconds and release the down button a split second before releasing the power button. This enters the bootloader (you may have to try it a few times to get it). Plug your phone into the computer and open a command prompt on the computer; type "fastboot erase cache", hit enter, type " fastboot erase userdata" and hit enter. You'll see confirmation in the command prompt and your phone will reboot as factory reset.
Well I am surprised I received the 5.0.1 update notification but after agreeing and letting device restart, it didn't happen and device claims that is up to date and still on 5.0
Did Google retired the OTA?
Your not alone im having the same issue. My 6 is on verizon and the same issue has happened that you described. Cleared data in the frame service. Phone claims up to date...still 5.0
Darn it....
At least AT&T and Verizon respect the "direct updates form Google" advantage of the Nexus brand.
Anyone able to help?
If you've flashed a custom recovery and/or are rooted, the OTA will fail. It will just reboot without doing anything, then the OTA disappears when back in Android and autoupdate says you're up to date.
You can download the image from the Nexus factory images site, extract the system and radio images, and flash them yourself with either fastboot or Nexus Root Toolkit.
This post gave me the idea:
http://forum.xda-developers.com/showpost.php?p=57411133&postcount=75
And here's the link to the latest N6 image from Google:
https://dl.google.com/dl/android/aosp/shamu-lrx22c-factory-ff173fc6.tgz
You'll need WinRAR or similar to extract the download from Google.
It failed for me too, bone stock. Connect your phone to a charger . it reappear and I was able to update
Dxtra i have tried this and it has yet to reappear how long has it taken for you to see it repop
Same here.... Verizon/Stock Nexus 6. Mine didn't even reboot. After I chose to accept the update, screen just flashed to up-to-date. Now claiming up-to-date each time.
Strange I'm in the UK and have the exact same problem. Got a notification thru last night for the 5.0.1 update, decided to leave it until this morning and it's gone. Must be something to do with Google.....
I am bone stock and have the same issue . Last night it said there was a new update and I said ok lets do it.. It said it was going to restart and then it never restarted or nothing and says its up to date even though its on 5.0 . I am on verizon !!!
StrangeTimes said:
Dxtra i have tried this and it has yet to reappear how long has it taken for you to see it repop
Click to expand...
Click to collapse
Immediately. I guess I was lucky
I did not root/installed custom ROM neither, which boost the upset. But again, I am glad that I should not worry for update delays due the device being from a carrier's branded, and evidently I am not the only one, I will give Google the opportunity before opting for manually flash the update which that means dealing with an 20+ GB backup first.
Sent from my Nexus 6 using XDA Free mobile app
Question
Hey i was wondering, I got my OTA update last night and of course my phone is unlocked and rooted but i still attempted to download and install it. I was successful in downloading the update and my device rebooted. I shortly got the error message so i rebooted the device and when i logged back on i was still on 5.0 and the OTA notification is now gone.
My question is, since i downloaded 5.0.1 and the device rebooted in the attempt to complete the install will this now cause my phone to no longer get the 5.0.1 update notification? I plan on unrooting once i get the notification so i can go ahead and OTA and when that is completed root the phone again. Or am I now forced to flash a factory reset in order to get that OTA update again?
ideally i would prefer to wait for the OTA so i dont have to factory reset.
ATT Stock
I had this disappearing 5.01 update issue as well. I figured I'd grab the OTA and adb sideload load as I had in the past. However, I've found that I can't get the device to go into Recovery mode at all. Power and Volume+ at the robot with the red exclamation triangle yields nothing. Perhaps the reason the update didn't happen is because the update itself couldn't activate Recovery either.
gleonard3 said:
I had this disappearing 5.01 update issue as well. I figured I'd grab the OTA and adb sideload load as I had in the past. However, I've found that I can't get the device to go into Recovery mode at all. Power and Volume+ at the robot with the red exclamation triangle yields nothing. Perhaps the reason the update didn't happen is because the update itself couldn't activate Recovery either.
Click to expand...
Click to collapse
Once you're in the recovery screen, make sure you are holding the power button first, then clicking volume up. If you hit them at the same time it doesn't work.
capcanuck said:
Once you're in the recovery screen, make sure you are holding the power button first, then clicking volume up. If you hit them at the same time it doesn't work.
Click to expand...
Click to collapse
You are correct! Thanks. Reading elsewhere had it backwards. This worked. Off to update now. Thanks again.
No worries bud
capcanuck said:
Once you're in the recovery screen, make sure you are holding the power button first, then clicking volume up. If you hit them at the same time it doesn't work.
Click to expand...
Click to collapse
Do I hold down power first for a while before volume up? Its driving me crazy
Sent from my Nexus 6 using XDA Free mobile app
Do I need to be rooted to flash update? On my one plus I could download update and the go to recovery and flash it.
Tia,
Ian B
Slorks said:
Do I hold down power first for a while before volume up? Its driving me crazy
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Just for literally a second or so..