Related
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.
I am having difficulties updating to the newest system update on the stock rom. I am rooted and have unlocked my bootloader, so that may have something to do with it. I am also running on straight talk, but I doubt that would be an issue, as it says it's already downloaded it and it just needs to install it. When I click install now, it turns the phone off, does the little thingy, then reboots. Upon rebooting, everything loads up, and a popup appears saying that the update failed, and then every hour it pops up asking to update. Do you know why this is happening and how to fix it, or a way to permanently suppress this popup?
ace_case said:
I am having difficulties updating to the newest system update on the stock rom. I am rooted and have unlocked my bootloader, so that may have something to do with it. I am also running on straight talk, but I doubt that would be an issue, as it says it's already downloaded it and it just needs to install it. When I click install now, it turns the phone off, does the little thingy, then reboots. Upon rebooting, everything loads up, and a popup appears saying that the update failed, and then every hour it pops up asking to update. Do you know why this is happening and how to fix it, or a way to permanently suppress this popup?
Click to expand...
Click to collapse
You need to be completely stock to take the OTA. If you haven't flashed Mex or Bell, I have a zip, maybe flashable (can't test, broke phone) that contains a completely stock /system. Or you can just backup your apps and flash the stock AT&T fastboot.
Post with link to zip.
skeevydude said:
You need to be completely stock to take the OTA. If you haven't flashed Mex or Bell, I have a zip, maybe flashable (can't test, broke phone) that contains a completely stock /system. Or you can just backup your apps and flash the stock AT&T fastboot.
Post with link to zip.
Click to expand...
Click to collapse
Is there a way to just suppress the update? I am a little wary of flashing etc. after the close call my first time...
ace_case said:
Is there a way to just suppress the update? I am a little wary of flashing etc. after the close call my first time...
Click to expand...
Click to collapse
Yes, you clear the cache. But if you want to leave yourself open to be vulnerable to the Heartbleed bug, a pretty serious security issue, then by all means, leave your front door unlocked so hackers can tap into your device and take anything they want.
palmbeach05 said:
Yes, you clear the cache. But if you want to leave yourself open to be vulnerable to the Heartbleed bug, a pretty serious security issue, then by all means, leave your front door unlocked so hackers can tap into your device and take anything they want.
Click to expand...
Click to collapse
I'd say it's more like posting on Craigslist that you're going on vacation and then leaving all the doors open with your debit/credit card on the coffee table. It's a pretty serious bug, and according to wikipedia, 1.5% of the most popular 800,000 websites are still vulnerable to the bug, not to mention running a sideloaded app or connecting to a malicious website.
got the same issue on one of my atrix hd's but not the other. On mine that I unlocked the bootloader and rooted myself took the ota update but the other which was bought in the same condition will not and just keeps giving an error. trying to figure this out now so will update.
lilred91 said:
got the same issue on one of my atrix hd's but not the other. On mine that I unlocked the bootloader and rooted myself took the ota update but the other which was bought in the same condition will not and just keeps giving an error. trying to figure this out now so will update.
Click to expand...
Click to collapse
Flashing back to completely stock may be the easiest way to get the update.
lilred91 said:
got the same issue on one of my atrix hd's but not the other. On mine that I unlocked the bootloader and rooted myself took the ota update but the other which was bought in the same condition will not and just keeps giving an error. trying to figure this out now so will update.
Click to expand...
Click to collapse
If you flash the OTA update manually using something like Philz recovery, you can see the progress on the screen and where it stops updating. For me, it kept hanging on updating the smartactions.apk, which was because I had previously (long time ago) merged updates of the app to my System partition (along with a few other apps that were updated). This will mess up any attempt to do an OTA update, because your "stock" ROM is no longer stock.
I ended up having to flash back to the real stock with Mythtools, then install the OTA zip manually.
If you can't find the zip in your cache, you can download it directly from this post (thanks @skeevydude): http://forum.xda-developers.com/showpost.php?p=52657363&postcount=13
I'm currently stuck at the s5 active logo screen and then it boots into recovery. I've tried flashing the full odin.rar (yes I extracted it) and it fails everytime. I get the message "Sw REV CHeck Fail: [aboot]Fused 2> Binary 1. I've already tried wiping the data from the recovery menu. Nothing is working.
We need more info. What were you attempting to do and from what ROM. Are you sure you are using the proper ROM 900 or 870?
I was attempting to downgrade back to stock from 5.0 and hit the stock kernel instead of the firmware accidently when in odin. And yes I am absolutely sure i'm using the 870 rom.
Edit: What if I use a stock img and a PIT file for the phone? OR is it because I need a 5.0 lollipop firmware to flash through odin?
Edit number 2: okay I'm stupid, im on G870AUCU2BOF3. I'm going to have to reflash the of3 zip aren't I?
Okay so I found the OF3 cfg on another thread and was able to load it and flash it and get my phone working! Now, the next question is can I root in my situation or downgrade or am I just stuck?
Edit: Going to wait for a possible root! Mod can close this thread.
if you loaded the 2400258.cfg you probably loaded the OF3 bootloader as well and now you can't go back. No root at this time and it doesn't look good for the future.
Cloudsdabomb said:
Okay so I found the OF3 cfg on another thread and was able to load it and flash it and get my phone working! Now, the next question is can I root in my situation or downgrade or am I just stuck?
Edit: Going to wait for a possible root! Mod can close this thread.
Click to expand...
Click to collapse
At command prompt type without the qoutes.
"getprop ro.bootloader"
Then paste output.
Sent from my SAMSUNG-SM-G870A using Tapatalk
If you took the of3 ota or are otherwise on the of3 bootloader your stuck there....no downgrade or root as of this time.
Me too
I am in a similar situation. Saturday I was on a rooted 4.4.2, flashed a stock unrooted 4.4.2 with Odin (G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5), let AT&T update me to 4.4.4, installed the old kernel with Odin (G870A_NE4_Stock_Kernel.tar.md5), rooted with towelroot, installed the new kernel with Odin (G870A_OA1_Stock_Kernel.tar.md5), updated to 5.0 with Odin and it retained root. However, certain things such as XPosed didn't work and I really really hated the white notification drawer so I just want to go back. I tried flashing the stock 4.4.2 in Odin again and it said success. It restarts and seems to be working but gets stuck on the AT&T logo. Now if I restart it always sticks on the AT&T logo even when I flash again. I don't know what else to try. A different file? Is there a way to go back to KitKat?
Update: I got into recovery mode (I kept trying vol up, vol down, power but it's actually vol up, home, power). I wiped the cache and did a data reset and restarted the phone. It worked! I'm excited to have a black notification screen again
pgross41 said:
I am in a similar situation. Saturday I was on a rooted 4.4.2, flashed a stock unrooted 4.4.2 with Odin (G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5), let AT&T update me to 4.4.4, installed the old kernel with Odin (G870A_NE4_Stock_Kernel.tar.md5), rooted with towelroot, installed the new kernel with Odin (G870A_OA1_Stock_Kernel.tar.md5), updated to 5.0 with Odin and it retained root. However, certain things such as XPosed didn't work and I really really hated the white notification drawer so I just want to go back. I tried flashing the stock 4.4.2 in Odin again and it said success. It restarts and seems to be working but gets stuck on the AT&T logo. Now if I restart it always sticks on the AT&T logo even when I flash again. I don't know what else to try. A different file? Is there a way to go back to KitKat?
Update: I got into recovery mode (I kept trying vol up, vol down, power but it's actually vol up, home, power). I wiped the cache and did a data reset and restarted the phone. It worked! I'm excited to have a black notification screen again
Click to expand...
Click to collapse
How long did you have to wait for your phone to boot all the way up from the ATT logo? Mine is doing exactly the same thing and I've flashed all kinds of kernels via odin and heimdall with no affect. None of the various fixes I've found have helped, including trying to re-apply the OTA file (system just won't do it). All I wanted was to unroot. Awesome.
The first boot can take a while but if it lasts more than 10 minutes it's probably not going to happen. I've gotten it stuck there twice since my last post and I'm always able to salvage it by going into recovery mode (vol up, home, power while powered off). Wipe the cache and data reset and it should be a fresh start like out of the box new.
Hm. So the only real two options are take it in to AT&T and hope they have the full stock G870AUCU2BOF3 image to flash over (since Samsung locked down their bootloader so hard, so downgrading is impossible :good: ) or hope they release G870AUCU2BOF3 on SamMobile/Kies/Smart Switch. This is like the new hard brick... potentially it's salvageable but the company (I'm guessing AT&T here since this is an AT&T exclusive phone) is just screwing us. Guess I'll try the walk of shame to AT&T. Or maybe putting in a claim like that one person did, get a whole new phone because of a mysterious cut on the rear panel seal...
Alright, took it in to AT&T and sure enough they had the full 5.0 image available so after signing a no-return data waiver (didn't even confirm my AT&T account or ask for any ID) the tech took my phone in the back and flashed it back to stock. First boot still showed the "custom" with unlocked padlock on the boot screen but after I rebooted it, I guess it updated the bootloader because it was back to normal.
No more root and he confirmed there's no way to go back to 4.4 once you go up to 5.0, so if you want root, I'd suggest staying away from 5.0. At least now I can use my phone again. Just thought I'd post this up in case anyone wasn't sure if AT&T would actually be able to reflash stock 5.0 and at the very least get your phone working again... enough to put on ebay and get a Moto or some other brand that doesn't lock down the bootloader so hard.
Edit: note the first boot will take a few minutes but I knew it worked when there was a quick vibe and the notification light went from pulsing blue to off. Maybe 4-5 minutes.
retro486 said:
Alright, took it in to AT&T and sure enough they had the full 5.0 image available so after signing a no-return data waiver (didn't even confirm my AT&T account or ask for any ID) the tech took my phone in the back and flashed it back to stock. First boot still showed the "custom" with unlocked padlock on the boot screen but after I rebooted it, I guess it updated the bootloader because it was back to normal.
No more root and he confirmed there's no way to go back to 4.4 once you go up to 5.0, so if you want root, I'd suggest staying away from 5.0. At least now I can use my phone again. Just thought I'd post this up in case anyone wasn't sure if AT&T would actually be able to reflash stock 5.0 and at the very least get your phone working again... enough to put on ebay and get a Moto or some other brand that doesn't lock down the bootloader so hard.
Edit: note the first boot will take a few minutes but I knew it worked when there was a quick vibe and the notification light went from pulsing blue to off. Maybe 4-5 minutes.
Click to expand...
Click to collapse
It's not Samsung that locks down the bootloader, it's AT&T. the T-Mobile Version doesn't have a locked bootloader and is easily rooted . Just have to SIM unlock it and you can use T-Mobile phone on AT&T network.
Delete
I've just taken my phone out of box, this is October 2015, and the moment I opened the phone first it started overheating and second I checked for updates and it says "software upto date".
The software is stuck at 5.0 and I don't know why I'm not receiving a single update when it's the time people are getting Android M. I've a Nexus 5 too and it's up to date to Marshmallow while this one is still stuck at 5.0 Lollipop.
I guess this has got to do something with the OTA feature and I want to fix this instead of flashing OS manually. So please tell me what to do now.
Till now after many Google searches I did twice reset of my phone and cleared data cache everything of Google Services Framework, but still nothing is helping.
Just 1 day old nonrooted nothing ever did, everything's from my side fine, just not understanding what to do.
Please please help me soon, I'm regretting buying nexus 6 now!
Aniket Sarkar said:
I've just taken my phone out of box, this is October 2015, and the moment I opened the phone first it started overheating and second I checked for updates and it says "software upto date".
The software is stuck at 5.0 and I don't know why I'm not receiving a single update when it's the time people are getting Android M. I've a Nexus 5 too and it's up to date to Marshmallow while this one is still stuck at 5.0 Lollipop.
I guess this has got to do something with the OTA feature and I want to fix this instead of flashing OS manually. So please tell me what to do now.
Till now after many Google searches I did twice reset of my phone and cleared data cache everything of Google Services Framework, but still nothing is helping.
Just 1 day old nonrooted nothing ever did, everything's from my side fine, just not understanding what to do.
Please please help me soon, I'm regretting buying nexus 6 now!
Click to expand...
Click to collapse
seriously?? your regretting it ??
you need patience...
patience....
patience....
I think I've mentioned that I'm not even getting 5.1, okay not even 5.0.1
Can someone please understand the level of problem I'm facing?
I've already mentioned while others are at 6.0, I'm not going anywhere ahead of 5.0
Please help!
Where did you buy your phone from? Are you sure it is not running a custom ROM? Is the bootloader locked?
Keep the phone connected to the internet (WiFi or cellular data), and sign into your Google Account, and wait another day. It may take a day or two to get update notification.
Edit - depending on your build#, you can download the OTA files and sideload them using ADB (don't need to unlock bootloader if that is a concern), or the faster option would be to just unlock the bootloader, and flash the latest factory image.
im on my 3rd day on my nexus.. but im not losing hope.. im still waiting for the ota.. its on 5.1 lmy47d...
So here is something funny. I was waiting and waiting for 6.0 on my nexus 6 for days. Never came. I have friends that have the same phone on the same carrier and they had already received their updates. So frustration and being impatient had gotten the best of me and I decided i was going to side load the update. In order to do so you need to unlock the boot loader which will wipe all of your data, EVERYTHING. When the phone rebooted completely wiped i went through the initial set up and it wasn't 5 min later the 6.0 update came rolling in like no big deal. WTF. I don't know why it wouldn't find it on its own but i wouldn't. Needless to day that is what I did and ended up getting it in a round about way. Maybe give that a try if you get to impatient and at that point if it doesn't show up just side load it. Hope this helps
Same, stuck on 5.1 LMY47D
google gives us factory images for a reason. if you arent patient enough to wait for an ota, just flash a factory image yourself, instead of starting threads about how you arent getting an ota. whats the point of a thread about you not getting an ota?
snoprosledneck88 said:
....I decided i was going to side load the update. In order to do so you need to unlock the boot loader which will wipe all of your data, EVERYTHING.
Click to expand...
Click to collapse
Sideloading the OTA using "ADB sideload" doesn't require you to unlock the bootloader.
Unlocking the bootloader is needed if you choose to flash the factory image file instead of the OTA file
jj14 said:
Sideloading the OTA using "ADB sideload" doesn't require you to unlock the bootloader.
Unlocking the bootloader is needed if you choose to flash the factory image file instead of the OTA file
Click to expand...
Click to collapse
Your right, I'm sorry. That's what I meant to say.
Sent from my Nexus 6 using Tapatalk
I got mine today and its on android 5 Doesn't want to update either, keeps saying its up to date. Haven't done anything yet with the phone. Looking now how ADB Sideload works.
jj14 said:
Where did you buy your phone from? Are you sure it is not running a custom ROM? Is the bootloader locked?
Keep the phone connected to the internet (WiFi or cellular data), and sign into your Google Account, and wait another day. It may take a day or two to get update notification.
Edit - depending on your build#, you can download the OTA files and sideload them using ADB (don't need to unlock bootloader if that is a concern), or the faster option would be to just unlock the bootloader, and flash the latest factory image.
Click to expand...
Click to collapse
I've bought it from an online retailer Flipkart in India.
I'm sure there's no changes made in phone and it's original and is as a new nexus 6 should be. Just this software update is causing me problems
snoprosledneck88 said:
So here is something funny. I was waiting and waiting for 6.0 on my nexus 6 for days. Never came. I have friends that have the same phone on the same carrier and they had already received their updates. So frustration and being impatient had gotten the best of me and I decided i was going to side load the update. In order to do so you need to unlock the boot loader which will wipe all of your data, EVERYTHING. When the phone rebooted completely wiped i went through the initial set up and it wasn't 5 min later the 6.0 update came rolling in like no big deal. WTF. I don't know why it wouldn't find it on its own but i wouldn't. Needless to day that is what I did and ended up getting it in a round about way. Maybe give that a try if you get to impatient and at that point if it doesn't show up just side load it. Hope this helps
Click to expand...
Click to collapse
Well I'm damn impatient, if I'd 5.1.1 and waited for 6.0 I'd have definitely had some patience, but waiting from 5.0 doesn't make sense.
Anyways to the point, after listening to your story, I tried same thing, clearing cache and reset from recovery mode, but still it didn't help
Hope there's some other resolution to this now.
I suspect it was your post that I responded to, at another forum - but you have two options really
1. Unlock bootloader (wipes data), and flash latest image
2. ADB Sideload OTAs one after the other in the right sequence (see http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 for OTA URLs) - check your current build and choose a path to get to the build you want
I am having the same problem.
I am having the same problem. Have you tried resetting the phone and starting it without the sim?
I just got a n6 today, and its running on 5.1.1. The marshmallow update came a long time ago so i thought it would update, but it showed that phone is up to date. Why is this so and how do i update?
entermetallica said:
I just got a n6 today, and its running on 5.1.1. The marshmallow update came a long time ago so i thought it would update, but it showed that phone is up to date. Why is this so and how do i update?
Click to expand...
Click to collapse
First of all congrats on the new phone. I'm on AT&T and updates came too slow for me. I chose to flash a system image to get upgraded to marshmallow and now we can download ota's directly from Google to keep up to date. Cutting out the need to wait for our updates to be made available from the carriers. Edit: to be clear you have to flash the ota's as well.
I believe others have removed sim card to try to get ota via wifi. I think. Anyway good luck.
Sent from my SM-T700 using Tapatalk
If you just got it today, good! Don't waste your time setting it up. Remove your SIM card and download the newest factory image "MOB30I" from here for the Nexus 6 (Shamu)
Just follow the instructions and you will be on the latest software. Then you should get OTA's normally from here on out. If you do it the Google recommended way it will wipe the phone so that's why I said don't set it up. If you already set it up it's going to be harder but you can manually flash the radio, bootloader, boot (kernel), and system with retaining your data but it's more hassle than it's worth.
Dopamin3 said:
If you just got it today, good! Don't waste your time setting it up. Remove your SIM card and download the newest factory image "MOB30I" from here for the Nexus 6 (Shamu)
Just follow the instructions and you will be on the latest software. Then you should get OTA's normally from here on out. If you do it the Google recommended way it will wipe the phone so that's why I said don't set it up. If you already set it up it's going to be harder but you can manually flash the radio, bootloader, boot (kernel), and system with retaining your data but it's more hassle than it's worth.
Click to expand...
Click to collapse
Thank you for your help, Im trying to flash it as it says on the website, but my device is not recognized after I type adb reboot bootloader. The phone shows up in adb devices but not in fastboot.
entermetallica said:
Thank you for your help, Im trying to flash it as it says on the website, but my device is not recognized after I type adb reboot bootloader. The phone shows up in adb devices but not in fastboot.
Click to expand...
Click to collapse
Assuming you're using Windows, if you look in device manager do you see anything either with a red x or yellow exclamation mark? If so you are missing the driver. This thread has the driver zip and briefly explains how to install it via device manager. Once you get the driver installed it should work fine.
And I can't remember if you need to or not to flash the stock images, but you might need to unlock your bootloader. Tap the build number a bunch of times and you will have access to developer options, and there you might need to check "Allow OEM unlocking" or something like that. Again I'm not 100% sure if that's necessary or not. I've ran my bootloader unlocked since day 1 and haven't looked back.
The bootloader does need to be unlocked to flash anything at all, except for a Google-signed OTA image.
Thanks for the help, ive done it. I had to boot into fastboot, and then install drivers from device manager
Sent from my Nexus 6 using XDA-Developers mobile app