ORIGINAL PROBLEM:
Pixel XL 128gb VS, received this morning with 63L.
1) Enabled debugging and OEM unlock.
2) Took the update as everyone said 63V is ok. But it turned out to be 63X(?) (I am on VZW network but phone purchased directly from google).
3) Used adb to get into bootloader mode and unlocked bootloader, which reset my phone and started fresh.
4) Enabled debugging again, OEM unlock was greyed out this time.
5) Rebooted, a message popped up something like 'needs to be locked to verify update' then google screen with unlocked lock symbol in the bottom.
6) Robooted again just to test. Still showed same thing, everything else seems to be working fine.
7) went back into adb mode and did fastboot boot boot-to-root.img
8) adb said successful
9) Phone restarted and showed the screen with bouncing dots. That was 55-ish minutes ago. Nothing else happening, but the screen with jumping dots.
Anyway to fix it or am I screwed?
Edit: Just tried and see if adb recognizes it now, nope.
@n3far1us,
A lot of discussion on SuperSU thread about this, but few answers yet.
Here > http://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156/page57
cam30era said:
@n3far1us,
A lot of discussion on SuperSU thread about this, but few answers yet.
Thank you @cam30era for sending me to the right direction. Did not realize I needed to look into SuperSU thread for this. I was searching in the wrong areas.
Click to expand...
Click to collapse
Same issue here
Same issues here after taking V update which completed then immediately flashed elemental kernel then rerooted which said ok now stuck on jumping dots for atleast an hour? Any ideas how to fix this I followed the directions of a dveloper on here and it screwed me!
QUOTE=n3far1us;69558628]Pixel XL 128gb VS, received this morning with 63L.
1) Enabled debugging and OEM unlock.
2) Took the update as everyone said 63V is ok. But it turned out to be 63X(?) (I am on VZW network but phone purchased directly from google).
3) Used adb to get into bootloader mode and unlocked bootloader, which reset my phone and started fresh.
4) Enabled debugging again, OEM unlock was greyed out this time.
5) Rebooted, a message popped up something like 'needs to be locked to verify update' then google screen with unlocked lock symbol in the bottom.
6) Robooted again just to test. Still showed same thing, everything else seems to be working fine.
7) went back into adb mode and did fastboot boot boot-to-root.img
8) adb said successful
9) Phone restarted and showed the screen with jumping dots. That was 40-ish minutes ago. Nothing else happening, but the screen with jumping dots.
Anyway to fix it or am I screwed?
Edit: Just tried and see if adb recognizes it now, nope.[/QUOTE]
@kirschdog1,
Follow the SuperSU thread that I referenced above.
On it now but it doesnt look like anyone has an answer for us!
cam30era said:
@kirschdog1,
Follow the SuperSU thread that I referenced above.
Click to expand...
Click to collapse
THE FIX
After about 6 hours of bouncing dots and trying out various things, @dowlf finally saved my life.
To recover the phone, I followed-
1) Boot to bootloader
2) Select 'Recovery' then once in recovery hold power and vol-up buttons for 5 sec then let go of the vol-up (but keep pressing power)
3) From there, choose Apply Update from ADB
4) Run 'adb sideload blahblah.zip' (mine was 63X OTA)
5) Choose 'Reboot system now' once copying done.
THE ROOT
After figuring out how to fix it, I immediately went back trying to root it again.
However, this time I decided to do more research and it appeared that I may have used an outdated boot-to-root.img which kicked off the bootloop. The first file was dated 10/31 and the second one I found was dated 11/03. I decided to try the 2nd one this time with "fastboot boot" command and voila!
My Pixel is successfully rooted on 63x!
Thanks to @Chainfire for all the hard work!
Oh and this is the link where I found the second file from-
https://plus.google.com/+Chainfire/posts/24xhJN724HG
Please help!
Guys I have a 32gb Pixel XL from Verizon, I unlocked the bootloader, and today I tried the boot-to-root and now i'm stuck on the bouncing dots, I've downloaded the OTA update, tried the flash-all script, didn't work, failed out at one part,
i tried sideloading the ota.zip and it said failed to sideload ota.zip and i'm FREAKING out i just bricked this phone...
PLEASE ASSIST. My phone is my livelyhood for my job and without it i'm screwed.
YankelMyWankel said:
Guys I have a 32gb Pixel XL from Verizon, I unlocked the bootloader, and today I tried the boot-to-root and now i'm stuck on the bouncing dots, I've downloaded the OTA update, tried the flash-all script, didn't work, failed out at one part,
i tried sideloading the ota.zip and it said failed to sideload ota.zip and i'm FREAKING out i just bricked this phone...
PLEASE ASSIST. My phone is my livelyhood for my job and without it i'm screwed.
Click to expand...
Click to collapse
Try flashing everything manually.
Sent from my Pixel XL using XDA-Developers mobile app
YankelMyWankel said:
Guys I have a 32gb Pixel XL from Verizon, I unlocked the bootloader, and today I tried the boot-to-root and now i'm stuck on the bouncing dots, I've downloaded the OTA update, tried the flash-all script, didn't work, failed out at one part,
i tried sideloading the ota.zip and it said failed to sideload ota.zip and i'm FREAKING out i just bricked this phone...
PLEASE ASSIST. My phone is my livelyhood for my job and without it i'm screwed.
Click to expand...
Click to collapse
Make sure you have the latest android SDK for adb and fastboot or it won't play very well
Sent from my Google Pixel XL using XDA Labs
alright, so i got stuck in ALMOST same situation, rooted my device got stuck on dots.
googled my problem and found this thread and found it more helpful, the only thing creating confusion is the OTA required.
got my device on 11th of this month and i guess started using it on 12th or 13th, and when i turned it on it asked me for updates and straight away i downloaded all the updates, but unfortunately i forgot to check what build number i was on.
so could you guys please help me out with the OTA version?
shall i go with the latest one?
and the rest is the same right?
like after sideloading the OTA file my device will be back to stock and unrooted ?
OKAY SO I'VE SOLVED MY PROBLEM BY JUST INSTALLING OTA WITH SIDELOAD COMMAND.
Thank you for the solution guys.
Related
Hello all, I have searched for more than a couple hours and just seem to be getting nowhere. Here's the deal: I have an HTC One M8 with TWRP, root, an unlocked bootloader and S-ON. I want to install Lollipop, but can't take the OTA.
I know a little bit about what I'm doing, I tried to flash a rooted stock ROM but it didn't take. I wiped all directories but the internal storage. Also wiped the Dalvik, `but I could not get the update to take. I tried a few other things but out of fear of bricking my phone I wasn't very adventurous. I flashed the backup I made beforehand and it worked fine.
I think I have the wrong file...? Could my S-ON be the problem?
Sprint HTC One M8 (HK edition)
Android: v4.4.4
Sense: v6.0
Kernel: 3.4.0
Baseband: v1.08.20.0916
Build:3.31.654.2
All I want to do is flash lollipop. Will I have to lock the bootloader and go back to stock recovery to do it? Can I use adb sideload to install it via adb?
Thank you for your time.
http://forum.xda-developers.com/showpost.php?p=59071793&postcount=10
ckpv5 said:
http://forum.xda-developers.com/showpost.php?p=59071793&postcount=10
Click to expand...
Click to collapse
I'm pretty sure my phone is toast.
PLEASE HELP, it worked just fine before I took your advice...
I relocked the bootloader and verified it multiple times before doing this. I made sure everything was exactly the way it was explained in the instructions, all files were correct.
I put the phone into fastboot, which I verified with adb.
I ran the Sprint_HTC_One_M8_HK_4.20.654.10_RUU .exe file and followed the instructions.
Both the program and pphone are currently frozen. They have been this way for almost 2 hours now.
The phone is stuck at the black HTC splash screen and the installer says
Updating...(0/7)... #(<--- these dots are still in motion like its installing)
Updating the ROM image on your Android phone...
[color=redPlease do not remove the USB connection from the Android phone or launch any programs during the update process.[/red]
Remember, this operation will take about 10 minutes.
Click to expand...
Click to collapse
I haven't done anything, its still plugged in.
I don't know what to do, can I just unplug it and flash my bavkup with TWRP?
PLEASE HELP I'M FREAKING OUT.
ckpv5 said:
http://forum.xda-developers.com/showpost.php?p=59071793&postcount=10
Click to expand...
Click to collapse
not_important said:
I'm pretty sure my phone is toast.
PLEASE HELP, it worked just fine before I took your advice...
I relocked the bootloader and verified it multiple times before doing this. I made sure everything was exactly the way it was explained in the instructions, all files were correct.
I put the phone into fastboot, which I verified with adb.
I ran the Sprint_HTC_One_M8_HK_4.20.654.10_RUU .exe file and followed the instructions.
Both the program and pphone are currently frozen. They have been this way for almost 2 hours now.
The phone is stuck at the black HTC splash screen and the installer says
I haven't done anything, its still plugged in.
I don't know what to do, can I just unplug it and flash my bavkup with TWRP?
PLEASE HELP I'M FREAKING OUT.
Click to expand...
Click to collapse
Ok, the phone is not recognized by adb but is still recognized by fastboot, can I reboot it into TWRP by using
Code:
fastboot reboot recovery
then just flash the backup I made before all this crap started?
*EDIT* RESOLVED
Never mind, I resolved it myself. I just typed
Code:
fastboot reboot
and hit enter. It booted right up.
not_important said:
Ok, the phone is not recognized by adb but is still recognized by fastboot, can I reboot it into TWRP by using
Code:
fastboot reboot recovery
then just flash the backup I made before all this crap started?
*EDIT* RESOLVED
Never mind, I resolved it myself. I just typed
Code:
fastboot reboot
and hit enter. It booted right up.
Click to expand...
Click to collapse
I looked through it and all user made folders are gone, but all user downloaded apps are still there. I also noticed that superSU root access was off, but the 'apply on boot' option was turned on, could this be what crashed the updater?
Couple of days ago I got this OTA notification that Android 7.1 preview is available for update. As my phone is rooted I started the manual update procedure. After the flashing was finished, I restarted the phone and then I saw it was stuck at the Google screen. Just stuck, no response. Seemed unusual to me.
Let me tell you that I have been modding my Nexus 5 for about two years. I am familiar with most of the tweaks that can be done to a Nexus device. Nexus 5 served me amazingly. I bought Nexus 5x 3 months ago.
So, after it was stuck I restarted. Still stuck. I will tell you step by step what I did then:
1. Flashed the OS 7.1 again (I dunno why, the flash.all script doesn't work for me, so I always do that manually) - result is the same.
2. Last October update (NBD90W) was available in the folder so I flashed that - same result.
3. I downloaded the previous one (NRD90S) and flashed that - same result.
4. I locked the phone and unlocked again to erase everything (not sure if that's a good idea), then flashed the OS again - same result.
5. Then I tried LGUP and the tot files to give it the factory version. LGUP detects the phone, started installing. When the installation is finished and the phone restarted - same result.
6. Now that I gave it the factory version the phone got locked!
7. I searched google for hours but couldn't find a way to unlock it as the OS is not booting and I cannot turn USB debugging on!
8. Then I tried the default recovery mode (Android recovery, from the recovery screen Power + volume up) as it doesn't require unlocking the device. Wiped the cache and restarted - same result.
9. My phone is detected by the pc and ADB. So, I wiped everything and tried ADB sideload and get this error E: footer is wrong
10. I tried Nexus root toolkit. It detects the phone in fastboot mode, then restarts it and then it again is stuck on the Google screen.
I am extremely depressed!
I am from Bangladesh and there is no authorized LG servicing center here. So, I can't ask for there help.
All that I did over the past two years was the awesome threads of xdadevelopers. So, a big thumbs up for you guys :good:.
I learnt from the web that phone can be hard bricked if a wrong bootloader is flashed. That's impossible for me as I always remove the factory image extracted files after flashing is done from the ADB>platform-tools folder.
Now, is the phone hard-bricked? If it is, what to do with it? Any kind of suggestion will be very much appreciated.
I've been watching several threads for the last few days, and have not seen this exact issue. I would greatly appreciate some help.
Device:
- Nexus 5X LGH790 32GB
- Stock bootloader / fastboot
- Never unlocked / rooted / etc.
The only advanced thing I've done is join the beta program a few months ago to get 7.0 early. Got that without any issue.
Issue:
I received the 7.1.1 OTA on the day it came out. Installed with no problems. The next day, the phone just froze in the middle of regular use. After about 15 seconds, it started boot looping to the Google splash screen. I can hold volume-down to enter fastboot, but when I select recovery mode, it just starts looping again. Pretty much all I could do was power it off. I did find out by accident that if I left it looping for long enough, sometimes it actually loaded normally (I even saw beta program warning/notice). But when I tried using it for more than a minute, it would freeze, reboot, and loop again.
What I've already tried:
- I tried using the WugFresh NRT fix softbrick method. I was able to quickly turn on debugging one of the times that I left it to loop. But when NRT sent a reboot the phone, it threw it back into the loop and NRT stopped recognizing the device.
- I tried to follow the unbrick procedure using a TOT file in this thread: http://forum.xda-developers.com/nexus-5x/help/tutorial-how-unbricked-nexus-5x-16gb-t3481766 But even after using LGUP, I still cannot even get into recovery mode.
- I filed a bug in the AOSP here: https://code.google.com/p/android/issues/detail?id=225802.
I'm at a loss here. On another thread, a member suggested this type of loop was a hardware/solder joint issue. I suppose that's possible... but man, what a coincidence that would be! Just now after the OTA the hardware fails? Any other thoughts? I'm pretty new to a lot of the terms/methods here, so maybe I missed something.
Thanks, DCK.
Update: I tried using LGUP again. The phone still gets stuck on the Google screen then boot loops.
Now, however, I am able to get into recovery mode consistently. Other threads have suggested doing an OTA sideload at this point. But I cannot seem to get my device recognized. The NRT shows no ADB devices connected. So I'm still stuck. Is there another way to try sideload?
DC_Knight said:
Update: I tried using LGUP again. The phone still gets stuck on the Google screen then boot loops.
Now, however, I am able to get into recovery mode consistently. Other threads have suggested doing an OTA sideload at this point. But I cannot seem to get my device recognized. The NRT shows no ADB devices connected. So I'm still stuck. Is there another way to try sideload?
Click to expand...
Click to collapse
Try fastboot/bootloader mode and fastboot flash the OTA manually.
Update 2: Seems like all the other things I tried over the last few days have caused various unofficial USB drivers to be installed. I've tried uninstalling most of them. I downloaded the google USB driver from latest SDK. But my 5X is still recognized as a Kedacom device when it is sitting at FastBoot.
However, I must have made some progress because I was able to start the sideload process. Unfortunately, I am now stuck on yet another error. The phone hangs at "verifying update package" and then after about 2 minutes... it reboots itself and starts looping again!
I thought I had it. So close. Now I want to throw the phone. Going to sleep, but would be grateful for any other suggestions in the morning.
- DCK
use nrt to erase all partitions, then download 7.1 factory image, unzip and flash one by one the partitions.
DC_Knight said:
...
I'm at a loss here. On another thread, a member suggested this type of loop was a hardware/solder joint issue. I suppose that's possible... but man, what a coincidence that would be! Just now after the OTA the hardware fails? Any other thoughts? I'm pretty new to a lot of the terms/methods here, so maybe I missed something.
Thanks, DCK.
Click to expand...
Click to collapse
Sounds like the boot loop issue many people have been having (the hardware/solder issue). It happened to me a few weeks ago after upgrading to Android 7.0. I got a replacement device from google.
If you're bootloader is locked, NRT or any other method to flash the factory image is not going to work. The only suggestion I have is to un-enroll in the beta program and hope your device will boot long enough to flash the ota Google will send the device to get back to 7.0. Note, this will wipe your device.
Sent from my Nexus 9 using XDA-Developers mobile app
Same problem here. It can't be recognized after I reboot to fastboot. So I can't flash anything.
If the device isn't recognized try this http://forum.xda-developers.com/showpost.php?p=69273414&postcount=33. It's worked for a few of us with the same problem
Sent from my Nexus 9 using XDA-Developers mobile app
Enter stock recovery then flash the full ota via adb sideload
My Nexus 5X just corrupted itself a couple days ago and unfortunately I did not enable OEM unlocking before that happened. I was running stock, un-rooted and from looking online the past couple days I see no way to unlock the bootloader so I can wipe everything and re-flash. I can get into fastboot, but not recovery mode. Recovery mode just says "No Command" with the little android on its side. I have tried all the fastboot commands that one would normally try and they all return some version of "device is locked" error messages. Is there any way at all to unlock the bootloader or flash stock, or otherwise get into recovery without checking that OEM unlocking option in the Developer Options of the OS? I don't care about my data, I just want to get my phone working again. It's out of warranty so I am willing to try anything to get it working again.
I'm in the same situation
This is why I always enable Oem unlocking on all devices I own regardless of security for things like this .
_Ghost said:
This is why I always enable Oem unlocking on all devices I own regardless of security for things like this .
Click to expand...
Click to collapse
Yeah, im going to be doing that from now on. I am pretty sure it was an OTA update that did it. It had just updated a day or two before. I was able to get into Recovery and sideload a different OTA update. The update failed and the phone rebooted, but it rebooted into Android. I was able to get my data off and all seems stable for now.
How did you fix it?!
coryrwest said:
Yeah, im going to be doing that from now on. I am pretty sure it was an OTA update that did it. It had just updated a day or two before. I was able to get into Recovery and sideload a different OTA update. The update failed and the phone rebooted, but it rebooted into Android. I was able to get my data off and all seems stable for now.
Click to expand...
Click to collapse
I am in this exact situation. Phone out of warranty, just want to get it back on, don't care about the data on it.. but the "device state" is locked. I can get it into recovery but the sideload fails, I think because the device is locked. How did you get your phone to work again??
I've tried following these instructions (I'm new and can't post a URL: [ttps://drive.google.com/file/d/0Bz6x7k-VkpUJam5Mc1hKa09PVGc/view) and it fails during step 19.
I've also tried these instructions (I can't post the URL but if you google this exact phrase, it's the first link: Nexus 5X Bootloop Fix - The Step-by-step DIY Guide - TechBii) but the phone is locked so I can't do it.
Help!
See this post please: https://forum.xda-developers.com/nexus-5x/general/petition-google-release-official-t3672987
Thanks
So did you ever get it to work or just thre the phone in the garbage, @coryrwest
See my latest post in the thread: https://forum.xda-developers.com/showpost.php?p=71241965&postcount=4
How?
coryrwest said:
Yeah, im going to be doing that from now on. I am pretty sure it was an OTA update that did it. It had just updated a day or two before. I was able to get into Recovery and sideload a different OTA update. The update failed and the phone rebooted, but it rebooted into Android. I was able to get my data off and all seems stable for now.
Click to expand...
Click to collapse
I'm having a similar issue, how did you exactly get it into recovery? Cause mine will simply keep rebooting if I select recovery mode from bootloader
I have an unrooted Pixel 3 XL and am unable to install the December update. Each time I try, my phone reboots and sits on the updating screen with the progress bar for several minutes, then reboots and tries again two more times, then finally boots back to the home screen with a notification saying "Couldn't install system update." If I click on this notification I can "Try Again" but it always does the same thing.
Does anyone know what could be causing my phone not to update, or how to look at logs that would tell me what's going on?
Jinded said:
I have an unrooted Pixel 3 XL and am unable to install the December update. Each time I try, my phone reboots and sits on the updating screen with the progress bar for several minutes, then reboots and tries again two more times, then finally boots back to the home screen with a notification saying "Couldn't install system update." If I click on this notification I can "Try Again" but it always does the same thing.
Does anyone know what could be causing my phone not to update, or how to look at logs that would tell me what's going on?
Click to expand...
Click to collapse
unrooted and bootloader locked?
Jinded said:
I have an unrooted Pixel 3 XL and am unable to install the December update. Each time I try, my phone reboots and sits on the updating screen with the progress bar for several minutes, then reboots and tries again two more times, then finally boots back to the home screen with a notification saying "Couldn't install system update." If I click on this notification I can "Try Again" but it always does the same thing.
Does anyone know what could be causing my phone not to update, or how to look at logs that would tell me what's going on?
Click to expand...
Click to collapse
Could you be using the wrong image?
Sent from my iPad using Tapatalk
ptn107 said:
unrooted and bootloader locked?
Click to expand...
Click to collapse
Yes I have the Verizon variant so unrooted and bootloader locked.
zebradude said:
Could you be using the wrong image?
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
I'm just running the regular system update process through Settings > System > Update, so unless my phone got confused about what phone it is I'm not sure how this would happen haha.
The only "non-regular" modification I've made to my phone is that I use Tasker and have granted it several system-level permissions through ADB, but this has never impacted a system update in the past...
Jinded said:
I'm just running the regular system update process through Settings > System > Update, so unless my phone got confused about what phone it is I'm not sure how this would happen haha.
Click to expand...
Click to collapse
I see. Sorry I thought you were side loading the image. OTA wow weird.
I've thought about trying to sideload the OTA, but on the OTA download site the first prerequisite listed is that there are currently no pending system updates, which is clearly not the case for me. Anyone know if there's actually a risk in attempting this?
https://developers.google.com/android/ota
Jinded said:
I've thought about trying to sideload the OTA, but on the OTA download site the first prerequisite listed is that there are currently no pending system updates, which is clearly not the case for me. Anyone know if there's actually a risk in attempting this?
https://developers.google.com/android/ota
Click to expand...
Click to collapse
There is no risk sideloading an OTA via recovery. What do you have to lose?
v12xke said:
There is no risk sideloading an OTA via recovery. What do you have to lose?
Click to expand...
Click to collapse
Well worst case I'd have to wipe and flash factory image, but I really don't want to go through that right now, especially this being the first time I don't have Titanium to restore everything haha
Jinded said:
Well worst case I'd have to wipe and flash factory image, but I really don't want to go through that right now, especially this being the first time I don't have Titanium to restore everything haha
Click to expand...
Click to collapse
I think you misunderstand. You cannot flash the factory image because you are BL locked. Sideloading an OTA image via recovery is also called a "rescue OTA". Don't worry...your bootloader is locked so you're not going to hose anything. You are stuck now... cannot use system update. Flashing the OTA is not going to wipe your data, or render your phone unbootable. It MAY however get you "unstuck". Just follow Google's detailed instructions on the page you linked. Good luck! :good:
v12xke said:
I think you misunderstand. You cannot flash the factory image because you are BL locked. Sideloading an OTA image via recovery is also called a "rescue OTA". Don't worry...your bootloader is locked so you're not going to hose anything. You are stuck now... cannot use system update. Flashing the OTA is not going to wipe your data, or render your phone unbootable. It MAY however get you "unstuck". Just follow Google's detailed instructions on the page you linked. Good luck! :good:
Click to expand...
Click to collapse
Hmm so it seems I can't even sideload the OTA, I'm guessing cause of the locked bootloader. When I reboot to recovery the screen just says "No command" and no buttons on the phone do anything, I see no option on the phone to sideload via ADB. Running "adb devices" on my connected laptop shows the active device in host mode, but I think it has to be in sideload mode for it to work. I've also tried clearing cache and data from the Google app before trying the regular update method again, but that didn't help either.
Jinded said:
Hmm so it seems I can't even sideload the OTA, I'm guessing cause of the locked bootloader. When I reboot to recovery I see no option on the phone to update via ADB, and "adb devices" shows no active devices. I've also tried clearing cache and data from the Google app but that didn't help either...
Click to expand...
Click to collapse
1) You do not need an unlocked bootloader to sideload an OTA.
2) Everyone with P2/P3/P4 stock recovery can sideload an OTA via adb. You don't even have to have USB debugging enabled in Developer settings. It is hard coded into recovery.
3) You probably aren't in recovery mode. Youtube a video on how to get into recovery mode, or Google "rescue OTA" or "sideload OTA via adb".
4) Upload a photo of your recovery screen
5) Double check you are using the latest adb/fastboot binaries
6) Report back
v12xke said:
1) You do not need an unlocked bootloader to sideload an OTA.
2) Everyone with P2/P3/P4 stock recovery can sideload an OTA via adb. You don't even have to have USB debugging enabled in Developer settings. It is hard coded into recovery.
3) You probably aren't in recovery mode. Youtube a video on how to get into recovery mode, or Google "rescue OTA" or "sideload OTA via adb".
4) Upload a photo of your recovery screen
5) Double check you are using the latest adb/fastboot binaries
6) Report back
Click to expand...
Click to collapse
You're right on #3, I didn't properly enter recovery mode - after getting to the "No Command" screen I was pressing and holding power and vol+ together (which didn't do anything) instead of holding power and then pressing vol+ to enter the menu. Anyway, once I got in I pressed "Apply update from ADB," confirmed via "adb sideload" that the phone was in the right mode, and started the OTA sideload (see picture for the PowerShell output). Once this completed successfully, I rebooted the phone but it did the same thing as before - 3 bootloops then boot into the home screen with an "update failed" notification.
Jinded said:
You're right on #3, I didn't properly enter recovery mode - after getting to the "No Command" screen I was pressing and holding power and vol+ together (which didn't do anything) instead of holding power and then pressing vol+ to enter the menu. Anyway, once I got in I pressed "Apply update from ADB," confirmed via "adb sideload" that the phone was in the right mode, and started the OTA sideload (see picture for the PowerShell output). Once this completed successfully, I rebooted the phone but it did the same thing as before - 3 bootloops then boot into the home screen with an "update failed" notification.
Click to expand...
Click to collapse
I would have expected a more verbose output but have not personally had to do a rescue OTA (my phones are all BL unlocked), so I don't know what the correct output looks like... but note there are no errors. Are you positive you are using the latest binaries I linked to? My version is 29.0.5 (October 2019). "adb version"
You stated you were unrooted, but are you BL unlocked? If not, you only have one option left that I am aware of. That is to to a factory data reset from recovery (or settings). If you were to contact Google Support and let them know where you are now and what you have done so far, they are going to have you FDR. The full OTA you flashed via adb is more complete than an incremental OTA and should have corrected your issue. If you are not BL locked yet, but have an unlockable phone you would still have to wipe data during the unlocking process, so go ahead and start backing your stuff up anyway. Good luck! :good:
v12xke said:
I would have expected a more verbose output but have not personally had to do a rescue OTA (my phones are all BL unlocked), so I don't know what the correct output looks like... but note there are no errors. Are you positive you are using the latest binaries I linked to? My version is 29.0.5 (October 2019). "adb version"
You stated you were unrooted, but are you BL unlocked? If not, you only have one option left that I am aware of. That is to to a factory data reset from recovery (or settings). If you were to contact Google Support and let them know where you are now and what you have done so far, they are going to have you FDR. The full OTA you flashed via adb is more complete than an incremental OTA and should have corrected your issue. If you are not BL locked yet, but have an unlockable phone you would still have to wipe data during the unlocking process, so go ahead and start backing your stuff up anyway. Good luck! :good:
Click to expand...
Click to collapse
I have the Verizon variant, so bootloader cannot be unlocked (OEM unlocking is disabled in Developer Options).
adb version shows me:
Android Debug Bridge version 1.0.41
Version 29.0.5-5949299
I think at this point I'm gonna wait for the January update and see if that one takes. Thanks for all the help!
Jinded said:
I have the Verizon variant, so bootloader cannot be unlocked (OEM unlocking is disabled in Developer Options).
adb version shows me:
Android Debug Bridge version 1.0.41
Version 29.0.5-5949299
I think at this point I'm gonna wait for the January update and see if that one takes. Thanks for all the help!
Click to expand...
Click to collapse
Well, you learned something here anyway. I believe incremental OTA's need to be applied sequentially, but since I always flash the full image I'm admittedly not very versed on OTA's. You may want to research that point further so you don't end up waiting two weeks for naught. Also would not hurt to make sure to manually sync backups, verify photos is backing to the cloud, and in TiBu do a "force redo of your backups" then zip that entire folder, transferring it safely off the phone. Best of luck and Merry Christmas!
v12xke said:
Well, you learned something here anyway. I believe incremental OTA's need to be applied sequentially, but since I always flash the full image I'm admittedly not very versed on OTA's. You may want to research that point further so you don't end up waiting two weeks for naught. Also would not hurt to make sure to manually sync backups, verify photos is backing to the cloud, and in TiBu do a "force redo of your backups" then zip that entire folder, transferring it safely off the phone. Best of luck and Merry Christmas!
Click to expand...
Click to collapse
Well that's the issue - I don't have the option to use an app like TiBu because I can't have root, so as far as I know I basically have to rely on Google's automatic backups/restores during initial phone setup, if I end up doing a factory reset. Before this phone I've always had a rooted phone with TiBu doing nightly backups to the cloud, so not having that has already been giving me anxiety the entire time I've had this phone haha.
I think the biggest thing I learned is to never buy a Verizon model phone again.
Jinded said:
Well that's the issue - I don't have the option to use an app like TiBu because I can't have root, so as far as I know I basically have to rely on Google's automatic backups/restores during initial phone setup, if I end up doing a factory reset. Before this phone I've always had a rooted phone with TiBu doing nightly backups to the cloud, so not having that has already been giving me anxiety the entire time I've had this phone haha.
Click to expand...
Click to collapse
Ah, ok. Well the Google backup has improved dramatically with 9 & 10 and works quite well. Hope you get it sorted soon. :good:
@Jinded, what happens if you try to sideload the OTA for the same version you currently have?
I have been wondering in a different thread, if the Goggle OTAs will work well on Verizon devices. It used to be there were device specific releases on the Google site as well as the general releases. Things like vendor and modem would likely be different.
Edit:
Reading through the forum, this post suggests that settings that are enabled in November are not available in December, preventing the update. Booting to safe mode will probably reset the ROM settings without factory resetting. Less to set back up.