Hi,
Verizon released the March security update for the Pixel: https://www.verizonwireless.com/support/google-pixel-update/
I hope that will fix all bluetooth issues!
Edit: Google images are available now: https://developers.google.com/android/images
that is to say the google store update is also upcoming. cheers
OTA coming down on my phone...
March factory images posted.
https://ota.googlezip.net/packages/.../7bad6688385deb9cfa8c47bff12294b3a545ee36.zip
Incremental OTA to NOF27B from NOF26V. 60MB.
For once, normal system update picked up first day - normally has been another 3-4 days on my device
xdatastic said:
https://ota.googlezip.net/packages/.../7bad6688385deb9cfa8c47bff12294b3a545ee36.zip
Incremental OTA to NOF27B from NOF26V. 60MB.
Click to expand...
Click to collapse
Does anyone know if taking this will take root of off a stock rooted Pixel with NOF26V? I have read something about Flashfire but I don't know if that works well with the Pixel or not to install the update. I've been out of the rooting game for awhile.
Joppykid said:
Does anyone know if taking this will take root of off a stock rooted Pixel with NOF26V? I have read something about Flashfire but I don't know if that works well with the Pixel or not to install the update. I've been out of the rooting game for awhile.
Click to expand...
Click to collapse
Nevermind, looks like i'll have to sideload and reinstall twrp and root.
Joppykid said:
Does anyone know if taking this will take root of off a stock rooted Pixel with NOF26V? I have read something about Flashfire but I don't know if that works well with the Pixel or not to install the update. I've been out of the rooting game for awhile.
Click to expand...
Click to collapse
It will take away root. It has updated bootloader so I would take the OTA or use fastboot and then re root
Edit it may not work taking OTA with root
Just FYI, I have upgraded the whole February image via flash fire, It worked
Joppykid said:
Nevermind, looks like i'll have to sideload and reinstall twrp and root.
Click to expand...
Click to collapse
mac796 said:
It will take away root. It has updated bootloader so I would take the OTA or use fastboot and then re root
Edit it may not work taking OTA with root
Click to expand...
Click to collapse
Yeah, It wouldn't install. I'll have to sideload or try flashfire
Joppykid said:
Yeah, It wouldn't install. I'll have to sideload or try flashfire
Click to expand...
Click to collapse
I haven't tried flash fire but I was reading the directions for it and it sounded like it wasn't a good idea to update bootliader with it. But I may be wrong. I would like to give it a try one of these days
mac796 said:
I haven't tried flash fire but I was reading the directions for it and it sounded like it wasn't a good idea to update bootliader with it. But I may be wrong. I would like to give it a try one of these days
Click to expand...
Click to collapse
Well. I'll let you know, I already started the process lol. Looks like it may have failed installing the OTA.
---------- Post added at 04:48 PM ---------- Previous post was at 04:46 PM ----------
Yeah, It didn't work. Unrooted my phone though. Lol.
Joppykid said:
Well. I'll let you know, I already started the process lol. Looks like it may have failed installing the OTA.
---------- Post added at 04:48 PM ---------- Previous post was at 04:46 PM ----------
Yeah, It didn't work. Unrooted my phone though. Lol.
Click to expand...
Click to collapse
Lol. Directions say that is dangerous
mac796 said:
Lol. Directions say that is dangerous
Click to expand...
Click to collapse
Consider myself lucky then lol. Everything I tried, the update failed to install lol. I am just going to re-root and stay on this version for now. I don't feel like doing a full on flash tonight. Thanks for everyone's responses.
OK I updated my buddies phone with fastboot I removed the-w and it still wiped everything. Did something change?
Anyone else experience this on stock rooted, updating with fastboot, the new factory image?
mac796 said:
it still wiped everything ... updating with fastboot, the new factory image?
Click to expand...
Click to collapse
Err, you did use the OTA Image, that's around 820megabytes, and not the Factory Image that is around 1.8gigabytes, yeah?? Coz if you've used the 'new factory image', well, that might wipe everything :crying:
https://developers.google.com/android/images |
Terms and conditions
Warning: Installing this factory image will erase all data from the device. While it may be possible to restore certain data backed up to your Google Account, apps and their associated data will be uninstalled. Before proceeding, please ensure that data you would like to retain is backed up to your Google Account.
Click to expand...
Click to collapse
Updated and my Bluetooth is back to normal. Immediately connects to all my devices whether its my car or headphones or speakers. No issues at all
h0mer_ said:
Err, you did use the OTA Image, that's around 820megabytes, and not the Factory Image that is around 1.8gigabytes, yeah?? Coz if you've used the 'new factory image', well, that might wipe everything :crying:
https://developers.google.com/android/images |
Click to expand...
Click to collapse
I used the factory but I removed the-w in the bat file which I have been doing since November, this time it wiped it. I guess I should have side loaded it. Maybe Google changed something.
mac796 said:
I used the factory but I removed the-w in the bat file which I have been doing since November, this time it wiped it. I guess I should have side loaded it. Maybe Google changed something.
Click to expand...
Click to collapse
Any backups before the update? Mucking about, but not much else you can now do.
I guess I should have side loaded it.
Click to expand...
Click to collapse
A cautionary tale for others.
Related
Shesh...the device been out for over a week now, im shock to see theres still not a official firmware image
immunityx said:
Shesh...the device been out for over a week now, im shock to see theres still not a official firmware image
Click to expand...
Click to collapse
I agree. I wanted the stock images to test if my device got a bad flash from the factory causing all of the multi touch and freezing issues. I ended up just exchanging at BB and have yet to upgrade to JSS15 in case that is the culprit.
Rod3 said:
I agree. I wanted the stock images to test if my device got a bad flash from the factory causing all of the multi touch and freezing issues. I ended up just exchanging at BB and have yet to upgrade to JSS15 in case that is the culprit.
Click to expand...
Click to collapse
There is no official one but there is an unofficial one, when the TWRP bug got me, it saved my system. It would still be soft-bricked waiting on Google otherwise.
I know right we need that incase something goes wrong and we can restore right to that i know we have ones on here but i want official
Sent from my Nexus 7 using Tapatalk 4
Hmmm nexus4 all over again
>^.^< Sent from meow HTC One which is like catnip to me atm
here's a flashable OTA image, is that not the same thing?
http://droidbasement.com/db-blog/?p=3120
Midnight_Rider said:
here's a flashable OTA image, is that not the same thing?
http://droidbasement.com/db-blog/?p=3120
Click to expand...
Click to collapse
they want a factory google released image
Midnight_Rider said:
here's a flashable OTA image, is that not the same thing?
http://droidbasement.com/db-blog/?p=3120
Click to expand...
Click to collapse
Nope. A factory image contains all the partitions, not just an update zip. Its used mainly to help devices that are completely broken (won't turn on), or people who want to unroot and go back to complete stock.
If it was there, it would be here: https://developers.google.com/android/nexus/images
That's what's keeping me from unlocking and rooting mine.
A
I want/need that as a backup..... just in case....
gotcha, i understand the diff
danvee said:
That's what's keeping me from unlocking and rooting mine.
A
I want/need that as a backup..... just in case....
Click to expand...
Click to collapse
It is extremely rare to have anything go wrong just unlocking the phone. You might as well go ahead and do it because eventually you will and it'll force a wipe data. Might as well do it now before you install too much stuff.
You can leave root and custom recovery until the images show up if you are concerned about borking your system.
sfhub said:
It is extremely rare to have anything go wrong just unlocking the phone. You might as well go ahead and do it because eventually you will and it'll force a wipe data. Might as well do it now before you install too much stuff.
You can leave root and custom recovery until the images show up if you are concerned about borking your system.
Click to expand...
Click to collapse
Not the unlocking. The rooting...
danvee said:
That's what's keeping me from unlocking and rooting mine.
A
I want/need that as a backup..... just in case....
Click to expand...
Click to collapse
danvee said:
Not the unlocking. The rooting...
Click to expand...
Click to collapse
this is what i did, after unlocking and rooting and installing TWRP go into recovery and make a nandroid backup and keep it safe off the device, keep it on the device, so if you need it you can restore it
That's what I'd be do once rooted, but it's the risk of the process failing without the factory image as a backup....
For example, rooting fails, no custom recovery flashed, OS hosed.....
I like having that safety net....
danvee said:
That's what I'd be do once rooted, but it's the risk of the process failing without the factory image as a backup....
For example, rooting fails, no custom recovery flashed, OS hosed.....
I like having that safety net....
Click to expand...
Click to collapse
oh i gotcha, but you have your steps out of order. first you unlock the bootloader which doesn't flash anything to your device. then you push the recovery image to your device from your PC using adb. yes this step could go horribly wrong, but if you have everything in place you should be ok. this step is very easy as well, not much to screw up and doesnt take any time at all, none of this does.
then once the recovery is installed, reboot your phone so you know everything comes up fine. then reboot into the recovery and flash SuperSU and voila! you have a rooted phone. boot back into the OS and run an app that requires root (Root Checker is a good one to use as a test) to make sure all is well
i understand your concern, but of all the android devices i have owned, the new nexus has been by far the easiest one of all to root and it is meant to be that way so developers can play with it and customize it and learn from it
plus there's this too
http://forum.xda-developers.com/showthread.php?t=2381582
Midnight_Rider said:
oh i gotcha, but you have your steps out of order. first you unlock the bootloader which doesn't flash anything to your device. then you push the recovery image to your device from your PC using adb. yes this step could go horribly wrong, but if you have everything in place you should be ok. this step is very easy as well, not much to screw up and doesnt take any time at all, none of this does.
then once the recovery is installed, reboot your phone so you know everything comes up fine. then reboot into the recovery and flash SuperSU and voila! you have a rooted phone. boot back into the OS and run an app that requires root (Root Checker is a good one to use as a test) to make sure all is well
i understand your concern, but of all the android devices i have owned, the new nexus has been by far the easiest one of all to root and it is meant to be that way so developers can play with it and customize it and learn from it
plus there's this too
http://forum.xda-developers.com/showthread.php?t=2381582
Click to expand...
Click to collapse
these are all wonderful points, but it doesn't change the fact that google should have released the image already
indianajonze said:
these are all wonderful points, but it doesn't change the fact that google should have released the image already
Click to expand...
Click to collapse
agreed, but im sure they are waiting to make sure there are no major bugs reported so they can fix it first, then release it. it will be out
That would mean yet another update, then.
Midnight_Rider said:
agreed, but im sure they are waiting to make sure there are no major bugs reported so they can fix it first, then release it. it will be out
Click to expand...
Click to collapse
Google has never waited before. The only thing that generally holds up posting factory images are licensing issues. They posted the 4.3 images for the Nexus 4, Nexus 7 (2012), and various Galaxy Nexus devices. There is no reason they didn't post the Nexus 7 images unless it is licensing related.
bozzykid said:
Google has never waited before. The only thing that generally holds up posting factory images are licensing issues. They posted the 4.3 images for the Nexus 4, Nexus 7 (2012), and various Galaxy Nexus devices. There is no reason they didn't post the Nexus 7 images unless it is licensing related.
Click to expand...
Click to collapse
good point
Per Droid-Life:
http://www.droid-life.com/2014/12/02/android-5-0-1-headed-to-aosp-as-build-lrx22c/
I'm ready!
I've got five candles lit and Kenny G on in the background, plus I'm wearing my fancy silk robe.
So yeah, I'm ready ☺
SilkyJohnson said:
I've got five candles lit and Kenny G on in the background, plus I'm wearing my fancy silk robe.
So yeah, I'm ready ☺
Click to expand...
Click to collapse
I laughed way to hard for that.
SilkyJohnson said:
I've got five candles lit and Kenny G on in the background, plus I'm wearing my fancy silk robe.
So yeah, I'm ready ☺
Click to expand...
Click to collapse
Lmao!
This is why we get "Nexus". We are the bleeding edge
I just get my device today and then rooted it immediately to find out there is an update coming out. I wonder how the OTA is going to do when I'm rooted????
tee00max said:
I just get my device today and then rooted it immediately to find out there is an update coming out. I wonder how the OTA is going to do when I'm rooted????
Click to expand...
Click to collapse
Lollipop checks to see if ANY system files are modified. If yes, it fails. Before, you could just put stock recovery back on and pretty much call it a day. I will just flash the factory image, boot up and take the OTA - then immediately go back into fastboot and put recovery, root and an unencrypted kernel right back on. Lollipop's app restore functionality I kind of like, so I can be back up and running pretty quick.
Or you could try to restore only data through recovery, but that's risky when jumping versions. I won't do it.
P.S. I think any proper Nexus owner should always have the latest stock image downloaded to their computer. If you ever need to save your ass it's just a click away. Plus, come downgrade time you're ready to go when you get off work ?
P.P.S. use Google Remote Desktop and leave your home computer on the developer page. That's what I did on the N5 when our images got released. That puppy was downloaded and ready to go the second I walked in the door.
tee00max said:
I just get my device today and then rooted it immediately to find out there is an update coming out. I wonder how the OTA is going to do when I'm rooted????
Click to expand...
Click to collapse
If you have a custom recovery you'll have to do a system wipe before you can flash the OTA.
Sent from my Nexus 6
Looks like factory images are starting to go up:
"Update: *And just like that, Android 5.0.1 factory images have gone live for a handful of devices, including the Nexus 9, Nexus 7 (2013) WiFi, and Nexus 10. Basically, we are looking at the WiFi devices. *You can grab individual image fileshere."
-per Droid-Life
SilkyJohnson said:
Lollipop checks to see if ANY system files are modified. If yes, it fails. Before, you could just put stock recovery back on and pretty much call it a day. I will just flash the factory image, boot up and take the OTA - then immediately go back into fastboot and put recovery, root and an unencrypted kernel right back on. Lollipop's app restore functionality I kind of like, so I can be back up and running pretty quick.
Or you could try to restore only data through recovery, but that's risky when jumping versions. I won't do it.
Click to expand...
Click to collapse
Can we only flash boot.img and System.img? would this fix root and replace any modded system files?
iboj007 said:
Can we only flash boot.img and System.img? would this fix root and replace any modded system files?
Click to expand...
Click to collapse
Hey, I'd give it a try! In theory I'd say it could.
SilkyJohnson said:
P.S. I think any proper Nexus owner should always have the latest stock image downloaded to their computer. If you ever need to save your ass it's just a click away. Plus, come downgrade time you're ready to go when you get off work ?
P.P.S. use Google Remote Desktop and leave your home computer on the developer page. That's what I did on the N5 when our images got released. That puppy was downloaded and ready to go the second I walked in the door.
Click to expand...
Click to collapse
For Sureeee. It seems i have had a few more issues with this phone in which having the factory images and fastboot have been a godsend.
crashercarlton said:
For Sureeee. It seems i have had a few more issues with this phone in which having the factory images and fastboot have been a godsend.
Click to expand...
Click to collapse
Agreed.
I can't get ADB to work after unlocking, but fastboot works like a champ and that's all I really use. I use ADB to reboot into BL ? I haven't cared or missed it enough to troubleshoot and fix.
Just refreshed the Dev page and it seems everything recent has been updated, minus the N5/6.
I have faith ?
jbdan said:
Lmao!
This is why we get "Nexus". We are the bleeding edge
Click to expand...
Click to collapse
Yup. I feel like I did when I first got my Galaxy Nexus and updates were fat and furious.
Sent from my Nexus 6
SilkyJohnson said:
Lollipop checks to see if ANY system files are modified. If yes, it fails. Before, you could just put stock recovery back on and pretty much call it a day. I will just flash the factory image, boot up and take the OTA - then immediately go back into fastboot and put recovery, root and an unencrypted kernel right back on. Lollipop's app restore functionality I kind of like, so I can be back up and running pretty quick.
Or you could try to restore only data through recovery, but that's risky when jumping versions. I won't do it.
Click to expand...
Click to collapse
rlh445 said:
If you have a custom recovery you'll have to do a system wipe before you can flash the OTA.
Sent from my Nexus 6
Click to expand...
Click to collapse
Right now I am running stock recovery. All I have is the bootloader unlocked and have root access.
I'll wait for a TWRP flashable zip :fingerscrossed:
tee00max said:
Right now I am running stock recovery. All I have is the bootloader unlocked and have root access.
Click to expand...
Click to collapse
It'll fail with root now.
looks like they're posting wifi only for now
indianajonze said:
looks like they're posting wifi only for now
Click to expand...
Click to collapse
Typical Googs.
I wonder... Has anyone already got an OTA update to 5.0.2? Google released the factory image on its website recently so we can do it manually, but I personally don't want to, and waiting for the OTA)... If anyone got it, you can share here p.s. already got mine and updated
Nexus 7 2nd WiFi Android 5.0.2
You could be waiting weeks. Just fastboot flash that **** it takes two minutes and you don't have to wipe your data.
yosmokinman said:
You could be waiting weeks. Just fastboot flash that **** it takes two minutes and you don't have to wipe your data.
Click to expand...
Click to collapse
Thanks, but I'm lazy)))
Nexus 7 2nd WiFi version Android 5.0.1
yosmokinman said:
You could be waiting weeks. Just fastboot flash that **** it takes two minutes and you don't have to wipe your data.
Click to expand...
Click to collapse
Unless I'm missing some step.. I thought flashing factory image wipes all data .
vkk178 said:
Unless I'm missing some step.. I thought flashing factory image wipes all data .
Click to expand...
Click to collapse
If you remove the “-w” flag from the flash-all.bat file in the factory images zip it will prevent wiping data.
kilroystyx said:
If you remove the “-w” flag from the flash-all.bat file in the factory images zip it will prevent wiping data.
Click to expand...
Click to collapse
What about a locked device?
mutantlx said:
What about a locked device?
Click to expand...
Click to collapse
you need to unlock it, that makes it full wipe by default , so you can flash a factory image.
idCyber said:
you need to unlock it, that makes it full wipe by default , so you can flash a factory image.
Click to expand...
Click to collapse
That's what I thought, thanks [emoji4]
Cool..just received the ota update. i guess the updates are being rolled out as we speak
Got the 5.0.2 OTA this morning pst.
now we need someone to capture it
mutantlx said:
now we need someone to capture it
Click to expand...
Click to collapse
A member has already captured it in another thread. Here's a link to his post. Credit naturally to him:
http://forum.xda-developers.com/showpost.php?p=58285301&postcount=448
[emoji98]
My N7 Flo received her OTA notification just now too. I wish the OTAs would flash with TWRP
mutantlx said:
What about a locked device?
Click to expand...
Click to collapse
Read this guide and maybe you find a way to don't lose your data or let say recover your data after wiping in the first time that you unlock the bootloader.
http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351
Failed
Just got mine and it failed to go on to stock rooted 5.0.1. Recovery reported an error; not sure why?
I just got the OTA update but am not clear on what this release contains. I haven't been able to get my hands on any release notes? Is there anything big in this update?
Thanks,
Rick
C5Longhorn said:
I just got the OTA update but am not clear on what this release contains. I haven't been able to get my hands on any release notes? Is there anything big in this update?
Thanks,
Rick
Click to expand...
Click to collapse
Noting big, no major fixes it should just be more responsive and feel a bit faster. Fact that I can confirm.
Sent from my Nexus 7
I just got the OTA update. Installing now.
I've had a LOT of wifi issues on L, wifi is always disconnected with "Authentication Problem" shown, if i reconnect it's fine. I haven't seen it again since moving to 5.0.2, but then again, it's only been 24h.
Hello, I have rooted and installed TWRP in my nexus 6p and now I have received the OTA update but I can't install it. How can I install it without losing my data?
Thanks
Sent from my Nexus 6P using XDA Free mobile app
airmark said:
Hello, I have rooted and installed TWRP in my nexus 6p and now I have received the OTA update but I can't install it. How can I install it without losing my data?
Thanks
Sent from my Nexus 6P using XDA Free mobile app
Click to expand...
Click to collapse
Unfortunately you cant :/
Download TiBu that is the closest you can get...
If you download a custom rom that keeps it up to date, they will probably include the update and you can just flash over it. but stock rom there isnt much u can do.
airmark said:
Hello, I have rooted and installed TWRP in my nexus 6p and now I have received the OTA update but I can't install it. How can I install it without losing my data?
Thanks
Sent from my Nexus 6P using XDA Free mobile app
Click to expand...
Click to collapse
Download the Google factory image for the 6p. Use fastboot to manually flash the system.img, boot.IMG, and recovery.IMG. take the ota then reroot.
Sent from my Nexus 6P using Tapatalk
airmark said:
Hello, I have rooted and installed TWRP in my nexus 6p and now I have received the OTA update but I can't install it. How can I install it without losing my data?
Thanks
Sent from my Nexus 6P using XDA Free mobile app
Click to expand...
Click to collapse
Go to guide, instructions there:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
raul4916 said:
Unfortunately you cant :/
Download TiBu that is the closest you can get...
If you download a custom rom that keeps it up to date, they will probably include the update and you can just flash over it. but stock rom there isnt much u can do.
Click to expand...
Click to collapse
Yes you can.
I did that and after rebooting I got a message saying:
Encryption unsuccessful
and prompting me to do a factory reset!
please don't tell me i have to wipe data!? quick googling doesn't seem promising...
airmark said:
I did that and after rebooting I got a message saying:
Encryption unsuccessful
and prompting me to do a factory reset!
Click to expand...
Click to collapse
airmark said:
please don't tell me i have to wipe data!? quick googling doesn't seem promising...
Click to expand...
Click to collapse
What did you do?
airmark said:
please don't tell me i have to wipe data!? quick googling doesn't seem promising...
Click to expand...
Click to collapse
Trying to undo the last steps by flashing back the modified boot.img and TWRP.
Booting into TWRP and it asks for a password to decrypt storage!!!
Is wiping the only option??
I followed the guide religiously. What went wrong?
Heisenberg said:
What did you do?
Click to expand...
Click to collapse
I followed the guide (part 10. How To Take An OTA Update If You Have Root).
Then after rebooting (before installing the OTA that is) I got a message saying encryption unsuccessful and I needed to wipe my phone. I turned it off instead and tried to restore it as it was before. Screw the OTA, I just need my phone back. I flashed back boot and recovery, is system.img or vendor.img the culprit?
Any ideas? Do I need to wipe data?
airmark said:
Trying to undo the last steps by flashing back the modified boot.img and TWRP.
Booting into TWRP and it asks for a password to decrypt storage!!!
Is wiping the only option??
I followed the guide religiously. What went wrong?
Click to expand...
Click to collapse
airmark said:
I followed the guide (part 10. How To Take An OTA Update If You Have Root).
Then after rebooting (before installing the OTA that is) I got a message saying encryption unsuccessful and I needed to wipe my phone. I turned it off instead and tried to restore it as it was before. Screw the OTA, I just need my phone back. I flashed back boot and recovery, is system.img or vendor.img the culprit?
Click to expand...
Click to collapse
I really don't know what went wrong here, other people have done this with no issues. In TWRP it should be able to decrypt as long as you enter the password/pin.
Heisenberg said:
I really don't know what went wrong here, other people have done this with no issues. In TWRP it should be able to decrypt as long as you enter the password/pin.
Click to expand...
Click to collapse
I had a screen lock pattern, I entered the numbers that correspond to it (from what I read somewhere else, like a num keypad), no joy.
But then again, shouldn't actual booting into the system work as well? Why give this error msg?
I'm going to format then...
unless your super comfortable with ADB and fastboot, flashing things through them is never a good idea, you will screw up allot of the time. its always easier for the average user to wait for a ota zip and flash that. Or never root and accept otas.
Im not saying never use adb, just dont use it when its super important to keep your data
TheAtheistOtaku said:
unless your super comfortable with ADB and fastboot, flashing things through them is never a good idea, you will screw up allot of the time. its always easier for the average user to wait for a ota zip and flash that. Or never root and accept otas.
Im not saying never use adb, just dont use it when its super important to keep your data
Click to expand...
Click to collapse
The only problem with that is even when an OTA zip is available you'd need to use fastboot to flash system etc to remove root anyway.
So I formatted, then set it up, then tried restoring my latest nandroid backup and now it doesn't recognise the pattern lock!
Heisenberg said:
The only problem with that is even when an OTA zip is available you'd need to use fastboot to flash system etc to remove root anyway.
Click to expand...
Click to collapse
i meant a TWRP zip. unless im misunderstanding something, you can just flash those over your current rooted stock and be on your way
---------- Post added at 07:50 PM ---------- Previous post was at 07:47 PM ----------
airmark said:
So I formatted, then set it up, then tried restoring my latest nandroid backup and now it doesn't recognise the pattern lock!
Click to expand...
Click to collapse
known problem, read this
Thanks for that, although at first after reading the first few posts I thought there was no solution, luckily I kept reading until here: http://forum.xda-developers.com/showpost.php?p=63797741&postcount=34
I did that and it worked! so at least I got back my working phone. Back to square one (almost, I lost all my local copies of photos, with only cloud backup for the last 2 weeks or so) with no OTA installed. I may try it again at some other point or wait for a more safe method.
airmark said:
Thanks for that, although at first after reading the first few posts I thought there was no solution, luckily I kept reading until here: http://forum.xda-developers.com/showpost.php?p=63797741&postcount=34
I did that and it worked! so at least I got back my working phone. Back to square one (almost, I lost all my local copies of photos, with only cloud backup for the last 2 weeks or so) with no OTA installed. I may try it again at some other point or wait for a more safe method.
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6p/development/rom-nexus6p-stock-roms-t3234067
TheAtheistOtaku said:
http://forum.xda-developers.com/nexus-6p/development/rom-nexus6p-stock-roms-t3234067
Click to expand...
Click to collapse
Thanks, I've just overcome the trauma and gathered the courage needed to give it another go today
So, do I have this right? If I download and flash build MDA89D ROM will it upgrade in place over my currently installed build MDB08K without losing my data? (I asked in that thread as well)
Sent from my Nexus 6P using XDA Free mobile app
i was on android m latest build and then i decided to try the new android n dp3 beta so i enrolled my 6p and updated through the ota update but after the update my 6p never started it stucks at the boot animation forever i tried wiping cache and also did a full wipe but its still the same. the oem unlock option is also disabled so i cannot flash factory images. i came to know that when we want to roll back to android m from the current beta we just have to unenroll our device from the beta and google sends an ota update of the current marshmallow build to roll back to it. now want i want to try is sideload that update package through adb an see if i can go back to android marshmallow. Please any of you who are trying out the latest android n beta provide me the zip file for the ota which google sends when we unenroll our device?
actually there is a simple step. anybody using the nexus 6p and running the latest android n beta just unenroll your device and when you get a notification for the ota update just enable usb debugging adn connect to computer and type command adb logcat and in the logcat file there will be a url for the ota just give me that url i will download it and try
Try to adb side load dp3. I think it can be installed on stock recovery and a fresh install might help. Wipe cache and factory reset afterwards and hope for the best. This won't make your problem any worse but has a chance at helping.
I had something similar like this happen, for my fix, all I did was boot to bootloader, cleared cache and then did a complete shutdown, do not just reboot, just rebooting, would go thru the boot loop, but a full power down allowed it to boot up normally. Not sure if it will help in your situation, but it's an easy try
murphyjasonc said:
Try to adb side load dp3. I think it can be installed on stock recovery and a fresh install might help. Wipe cache and factory reset afterwards and hope for the best. This won't make your problem any worse but has a chance at helping.
Click to expand...
Click to collapse
spookytay said:
I had something similar like this happen, for my fix, all I did was boot to bootloader, cleared cache and then did a complete shutdown, do not just reboot, just rebooting, would go thru the boot loop, but a full power down allowed it to boot up normally. Not sure if it will help in your situation, but it's an easy try
Click to expand...
Click to collapse
no its not happening. if anyone of you are using nexus 6p and are on the android n beta then please can you follow what i have posted in the first comment?
Ame123 said:
no its not happening. if anyone of you are using nexus 6p and are on the android n beta then please can you follow what i have posted in the first comment?
Click to expand...
Click to collapse
I second this. Would be very helpful if someone could post the official roll-back marshmallow .zip for the 6p.
https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Good luck! Hope this helps people
Dev preview 3 downgrade to MM
matt1515 said:
https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Good luck! Hope this helps people
Dev preview 3 downgrade to MM
Click to expand...
Click to collapse
My phone is in the same position as OP. Do I just sideload this ZIP using adb?
Update: Sideload completed, first boot froze and phone restarted then second boot has booted to welcome screen!! Dude I cannot thank you enough I tried literally everything and nothing worked and I lost hope until I saw this!
AlfexOmega said:
My phone is in the same position as OP. Do I just sideload this ZIP using adb?
Click to expand...
Click to collapse
Correct.
AlfexOmega said:
My phone is in the same position as OP. Do I just sideload this ZIP using adb?
Update: Sideload completed, first boot froze and phone restarted then second boot has booted to welcome screen!! Dude I cannot thank you enough I tried literally everything and nothing worked and I lost hope until I saw this!
Click to expand...
Click to collapse
Good stuff! Glad to help I thought this would work!
matt1515 said:
Good stuff! Glad to help I thought this would work!
Click to expand...
Click to collapse
So this was the OTA that you get when you unenroll your Nexus from the Beta Programme?
matt1515 said:
Good stuff! Glad to help I thought this would work!
Click to expand...
Click to collapse
Yep--can confirm this worked for me as well. Thank you so much for posting the .zip, matt1515.
AlfexOmega said:
So this was the OTA that you get when you unenroll your Nexus from the Beta Programme?
Click to expand...
Click to collapse
Yes sir I unenrolled from the beta I got the link from adb logcat
---------- Post added at 01:22 PM ---------- Previous post was at 12:48 PM ----------
Ame123 said:
actually there is a simple step. anybody using the nexus 6p and running the latest android n beta just unenroll your device and when you get a notification for the ota update just enable usb debugging adn connect to computer and type command adb logcat and in the logcat file there will be a url for the ota just give me that url i will download it and try
Click to expand...
Click to collapse
https://android.googleapis.com/packa...cd4f52b800.zip
matt1515 said:
Yes sir I unenrolled from the beta I got the link from adb logcat
---------- Post added at 01:22 PM ---------- Previous post was at 12:48 PM ----------
https://android.googleapis.com/packa...cd4f52b800.zip
Click to expand...
Click to collapse
Nice! Thanks so much again
matt1515 said:
https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Good luck! Hope this helps people
Dev preview 3 downgrade to MM
Click to expand...
Click to collapse
it worked. thank you very much for helping:good::good::good::good:
Same thing happened to me, luckily it decided itself to boot fully after an hour. However I did notice that USB debugging was not enabled after all this mess. Does that mean if it didn't resolve then I would have had a nice brick without the option of side loading from a PC? Also does the unlock bootloader in dev options need to be checked off for any reason other than flashing custom roms? Can I still install official images and still have the bootloader locked?
Now I'm just looking for ways to be prepared in the future in case it happens again, thanks
kick069 said:
Same thing happened to me, luckily it decided itself to boot fully after an hour. However I did notice that USB debugging was not enabled after all this mess. Does that mean if it didn't resolve then I would have had a nice brick without the option of side loading from a PC? Also does the unlock bootloader in dev options need to be checked off for any reason other than flashing custom roms? Can I still install official images and still have the bootloader locked?
Now I'm just looking for ways to be prepared in the future in case it happens again, thanks
Click to expand...
Click to collapse
Leave USB debugging and OEM Unlock enabled. This will help you so much more in the event of any issues during updates.
If OEM Unlock is turned off then you cannot flash factory images. You CAN leave this off and still ADB Sideload OTAs. However, if the ADB Sideload update is corrupt or flashes and you are stuck in a bootloop, there is very little that can be done to resolve it.
Sent from my Nexus 5X using Tapatalk
Has anyone here who flashed back to MM tried to do the OTA N update again? How did it go?
freezerbite said:
Has anyone here who flashed back to MM tried to do the OTA N update again? How did it go?
Click to expand...
Click to collapse
Yes. I tried but again got stucked in bootloop. So i am not touching any beta
It's so weird that some people get stuck with this boot loop issue and some just don't. I know things can happen, but I feel there's a enough users in the same boat that there's has to be a common denominator.
Sent from my Nexus 6P using Tapatalk