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.
Related
Hello,
My Galaxy Nexus seems to be caught in a boot loop. I woke up this morning took my phone off the charger and it almost immediately said shutting device down and the battery indicator was red with an "X". Now every time I reboot the phone it goes to the Google and then through the Nexus logo gets to the desktop (I don't don't have a lock screen enabled) and then it buzzes and then goes into shutdown. I know the battery has juice because I booted into recovery mode and left the screen on and it doesn't show any signs of shutting it down from there. Also,when I rebooted several times I can get it to the desktop for about five minutes and the battery does show that it's three quarters full. When I decided to go into recovery mode I was able to select recovery when I hit the power button it boots up and then it comes with the android lying down with the red! I got it restored to the factory settings. Then rebooted and started to set up and it crashed and shutdown. when entering my Google account the Gallery Stopped and some other service had to force quit then it locked up. This all started after updating to 4.2.2. Now when I restore it and reboot, it just says "Welcome" and then says it is shutting down. I tried a few times and also deleted the cache as well to see if that would help (it didn't). Is there any way to get a clean update or do I need to send it in to Samsung.
Any help would be appreciated, thanks.
Also, it is a Samsung Galaxy Nexus from the Google Play Store and has NOT been rooted.
Did you flash the proper update for your device, i.e. yakju or takju? You could always reflash a full image to fix: http://forum.xda-developers.com/showthread.php?t=1626895
bodh said:
Did you flash the proper update for your device, i.e. yakju or takju? You could always reflash a full image to fix: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
It was OTA update. Here is where I am at now: I shutdown the phone plugged it in and let it charge. Then I was able to restore to factory settings, but the camera app still doesn't work, it says the gallery app has crashed. I can go into the gallery app, but when I try to access the camera it crashes. So far that is the only error I am getting, is there a way to reinstall the camera app?
You need to flash the stock nexus favtory images trough fastboot. It is the best for a clean start as it restores all the partitions to stock. Its the best fresh start when problems like this happen.
Get it here: https://developers.google.com/android/nexus/images
Download the 4.2.2 (takju/yakju) images, ectract it and flash it via fastboot.
I am 99% sure everything will be fine after this.
Let me know how it goes
Sent from my Nexus Prime
thegtfusion said:
Download the 4.2.2 (takju/yakju) images, ectract it and flash it via fastboot.
Click to expand...
Click to collapse
I downloaded the image, but what are the steps to install it? Also, the phone is not rooted.
Pronoun said:
I downloaded the image, but what are the steps to install it? Also, the phone is not rooted.
Click to expand...
Click to collapse
Ok, does your phone have an unlocked bootloader?
If not, you need to unlock the bootloader in order to use fastboot.
so the steps are:
-unlock the bootloader
-follow this guide: http://forum.xda-developers.com/showthread.php?t=1626895
thegtfusion said:
Ok, does your phone have an unlocked bootloader?
If not, you need to unlock the bootloader in order to use fastboot.
so the steps are:
-unlock the bootloader
-follow this guide: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
I did it but the camera and any app that uses the camera is still not working.
If you reflashed a factory image and it's still not working, then it's probably going to be a hardware issue. Especially if the led was red, it sounds like it needs to go to samsung. Possibility of water damage?
Flash the binary update then followed with 4.2.2 kernel
Can you be more specific as to what binary update you are suggesting? It may help.
Pronoun said:
I did it but the camera and any app that uses the camera is still not working.
Click to expand...
Click to collapse
Did you flash userdata? I've got the feeling that you didn't.
Fastboot boot a recovery and wipe data/factory reset.
I'm on yakju, and my OTA installed fine, and I had/I'm on TWRP 2.4.1.0.
Sent from my Nexus
followed a tutorial (Cnncted's youtube clip - How to root the ASUS ZenFone 2 ) to root
Accidentally (very stupid) pressed the update option when an OTA update showed up yesterday (Jul 8 2015), and after that the phone won't start properly - stopped at in search of incredible...
No luck with trying to boot into recovery mode (power + volume up). It just vibrates once and the screen is black. Trying to flash recovery image with ADB and flashtool etc, but the MTP usb connection failed. If I connect it to the PC using the USB cable and then press the power button to turn it on (stuck in that ..."incredible" screen), device manager shows the Z200AD name with a yellow exclamation mark beside, and Asus ZenUI software will automatically start. But it's not really recognized by the PC.
So...if you have any suggestions for me to try, please let me know and that would be greatly appreciated!
Harry
p.s. This is a US version, so the it's the WW sku?
Same problem here. I have a rooted 551ML and on July 6th I received an OTA update. I installed it and I'm stuck in boot loop. I have hundreds of family pictures in the internal memory.
The good news is that I have access to boot loader and recovery.
I could not find any custom recovery for Zenfone 2. They are not out yet, right? Is there any way to copy the internal memory of the phone (that doesnt load the OS) to the SD card? Or to paste a file img.boot taken from a downloaded official rom and copy it over the corrupted one on the phone's memory?
If you can access the bootloader, you can do this:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
Btw, there is a custom recovery out there (TWRP, check the Development section), but you will need an unlocked bootloader to use it in your state (I think).
US version is the WW SKU btw. Hope this helps.
joel.maxuel said:
If you can access the bootloader, you can do this:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
Btw, there is a custom recovery out there (TWRP, check the Development section), but you will need an unlocked bootloader to use it in your state (I think).
US version is the WW SKU btw. Hope this helps.
Click to expand...
Click to collapse
Joel, thanks a lot! I will give it a try.
fingers and toes crossed...
I faced this problem too. All I did was to flash the boot.img of my version using fastboot,
Then I flashed the firmware, without factory reset I started the phone.
I was continiously getting an error "com.android.process has stopped". Ignoring that, I just backed up my whole data. Did a factory reset. Updated
Boom!! Everything was normal... I hope this helps
Just a quick update - followed the method in the link that Joel referred to, and everything worked beautifully. I did get two error messages like “the contact stopped working..." “The process android.process.acore has stopped working.” I fixed this problem by clearing the data/cache from the "contact" app, and that did the trick without a factory reset etc.
I unrooted the device using SuperSU. The fastboot screen, however, still shows a random serial number 0123456789ABCDEF. Is there a way to revert it back to the real one? I do see the real one from settings - about - status.
xxmmx said:
Joel, thanks a lot! I will give it a try.
fingers and toes crossed...
Click to expand...
Click to collapse
xxmmx said:
Just a quick update - followed the method in the link that Joel referred to, and everything worked beautifully. I did get two error messages like “the contact stopped working..." “The process android.process.acore has stopped working.” I fixed this problem by clearing the data/cache from the "contact" app, and that did the trick without a factory reset etc.
I unrooted the device using SuperSU. The fastboot screen, however, still shows a random serial number 0123456789ABCDEF. Is there a way to revert it back to the real one? I do see the real one from settings - about - status.
Click to expand...
Click to collapse
Isn't everyone serial number the same? mine is.
This is something that I am not sure of. Yours has been rooted as well?
I would like to know what the fastboot screen looks like before rooting.
GGL-Daz said:
Isn't everyone serial number the same? mine is.
Click to expand...
Click to collapse
xxmmx said:
This is something that I am not sure of. Yours has been rooted as well?
I would like to know what the fastboot screen looks like before rooting.
Click to expand...
Click to collapse
Pretty sure rooting didn't affect my fastboot screen at all.
actually i rooted my zenfone 2 and there was an OTA and i tried to install it without un-rooting my phone. the phone would not turn on and it gets stuck in the boot animation.
the phone wasn't detected by the ADB in my pc so i thought of installing some custom recovery, thought that could help.
i tried installing TWRP but i did not unlock the bootloader and now i am not able to enter in recovery mode either, everytime i try to get in the recovery modethe phone restarts and goes to fastboot mode.
please help.
dip_anker said:
actually i rooted my zenfone 2 and there was an OTA and i tried to install it without un-rooting my phone. the phone would not turn on and it gets stuck in the boot animation.
the phone wasn't detected by the ADB in my pc so i thought of installing some custom recovery, thought that could help.
i tried installing TWRP but i did not unlock the bootloader and now i am not able to enter in recovery mode either, everytime i try to get in the recovery modethe phone restarts and goes to fastboot mode.
please help.
Click to expand...
Click to collapse
I was having a similar issue where adb wouldn't recognize my phone but fastboot was detecting it. What I ended up doing was grabbing the latest stock firmware zip from asus, transferring it to my external sd card via adapter and renamed it to MOFD_SDUPDATE.zip. Then go into fastboot (restart with volume up key) and proceed to recovery. It should automatically update your system from there. The only bummer is having to re-configure everything.
5ifty1 said:
I was having a similar issue where adb wouldn't recognize my phone but fastboot was detecting it. What I ended up doing was grabbing the latest stock firmware zip from asus, transferring it to my external sd card via adapter and renamed it to MOFD_SDUPDATE.zip. Then go into fastboot (restart with volume up key) and proceed to recovery. It should automatically update your system from there. The only bummer is having to re-configure everything.
Click to expand...
Click to collapse
i tried it with prerooted as well as the stock rom, it did not work for me. isn't there any way to flash CM12.1 using the fastboot ?
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.
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
So I may have caused this by filling up the storage taking some family videos, but here is what happened:
P6P working great for months now, unlocked boot-loader, rooted with latest Magisk, flashed May OTA images last moth and updated to Jun the other day. NO issues after the flash and phone ran fine even after several reboots.
The other day after I filled up the storage, I connected to PC and moved off some videos to make space. Pretty sure this worked and when done, I decided to do a reboot. After that, it never booted fully and after animation rebooted continuously.
I have since flashed on both slots (a/b), May and June OTA images, and it still will not boot. I am pretty sure IF I WIPE DATA, this will work, but my goal here is to try everything possible to not have to do that this time. I know it would have been best to have a backup, but that's another discussion.
Goals would be:
1) Full boot into OS w/o wipe
2) ADB access so I could at least pull some files off before resorting to wiping data.
Fastboot of course works fine, and adb connects for 10 seconds or so while animation is going, but not sure what I can do during this quick time?
Could that camera filling up storage have caused these issues?
I think if we had something like TWRP like back in the days, I could use adb, but dont think thats around these days.
Any advise?
banshee28 said:
So I may have caused this by filling up the storage taking some family videos, but here is what happened:
P6P working great for months now, unlocked boot-loader, rooted with latest Magisk, flashed May OTA images last moth and updated to Jun the other day. NO issues after the flash and phone ran fine even after several reboots.
The other day after I filled up the storage, I connected to PC and moved off some videos to make space. Pretty sure this worked and when done, I decided to do a reboot. After that, it never booted fully and after animation rebooted continuously.
I have since flashed on both slots (a/b), May and June OTA images, and it still will not boot. I am pretty sure IF I WIPE DATA, this will work, but my goal here is to try everything possible to not have to do that this time. I know it would have been best to have a backup, but that's another discussion.
Goals would be:
1) Full boot into OS w/o wipe
2) ADB access so I could at least pull some files off before resorting to wiping data.
Fastboot of course works fine, and adb connects for 10 seconds or so while animation is going, but not sure what I can do during this quick time?
Could that camera filling up storage have caused these issues?
I think if we had something like TWRP like back in the days, I could use adb, but dont think thats around these days.
Any advise?
Click to expand...
Click to collapse
Try Android Flash Tool and leave all the boxes unchecked.
Alternatively, since you can get into fastboot you could flash the factory image, but beforehand modify the flash-all.bat file by removing the -w (this will allow you to keep data).
Lughnasadh said:
Try Android Flash Tool and leave all the boxes unchecked.
Alternatively, since you can get into fastboot you could flash the factory image, but beforehand modify the flash-all.bat file by removing the -w (this will allow you to keep data).
Click to expand...
Click to collapse
So I should have mentioned this... I used both Pixel Flasher and Android Flash Tool with same results on each. I have also used both tools successfully to update previous months updates with NO issues.
banshee28 said:
So I should have mentioned this... I used both Pixel Flasher and Android Flash Tool with same results on each. I have also used both tools successfully to update previous months updates with NO issues.
Click to expand...
Click to collapse
I'm not sure about OTA as I've always used the full image but the full image version (if I'm not mistaken) needs a certain amount of storage to unpack everything it needs to install. There might not be enough room.
banshee28 said:
So I may have caused this by filling up the storage taking some family videos, but here is what happened:
P6P working great for months now, unlocked boot-loader, rooted with latest Magisk, flashed May OTA images last moth and updated to Jun the other day. NO issues after the flash and phone ran fine even after several reboots.
The other day after I filled up the storage, I connected to PC and moved off some videos to make space. Pretty sure this worked and when done, I decided to do a reboot. After that, it never booted fully and after animation rebooted continuously.
I have since flashed on both slots (a/b), May and June OTA images, and it still will not boot. I am pretty sure IF I WIPE DATA, this will work, but my goal here is to try everything possible to not have to do that this time. I know it would have been best to have a backup, but that's another discussion.
Goals would be:
1) Full boot into OS w/o wipe
2) ADB access so I could at least pull some files off before resorting to wiping data.
Fastboot of course works fine, and adb connects for 10 seconds or so while animation is going, but not sure what I can do during this quick time?
Could that camera filling up storage have caused these issues?
I think if we had something like TWRP like back in the days, I could use adb, but dont think thats around these days.
Any advise?
Click to expand...
Click to collapse
Have you tried booting into safe mode? This is what I would do:
Flash the latest OTA in recovery mode. Then during restart, as soon as you see Google Boot animation, hold volume down.
Is your Bootloader unlocked? (When you boot into fastboot mode, does it say unlocked?).
Alekos said:
Have you tried booting into safe mode? This is what I would do:
Flash the latest OTA in recovery mode. Then during restart, as soon as you see Google Boot animation, hold volume down.
Is your Bootloader unlocked? (When you boot into fastboot mode, does it say unlocked?).
Click to expand...
Click to collapse
Yes bootloader is unlocked. Tried volume down right after animation and it took me into fastboot?
Tulsadiver said:
I'm not sure about OTA as I've always used the full image but the full image version (if I'm not mistaken) needs a certain amount of storage to unpack everything it needs to install. There might not be enough room.
Click to expand...
Click to collapse
Actually I am flashing the factory images I think they are called from here: Images
So maybe these are not OTA. I have only used these images.
banshee28 said:
Yes bootloader is unlocked. Tried volume down right after animation and it took me into fastboot?
Click to expand...
Click to collapse
Google's Help Page for Find problem apps by rebooting to safe mode - this can be a lifesaver and keep you from having to do a restore to 100% complete stock or even from having to do a factory reset. This will deactivate all Magisk modules, and they'll remain deactivated even after you boot normally after briefly booting to safe mode. You can reenable the Magisk modules as you wish to try to narrow down the problem if it was caused by a Magisk module. This can even get things working again after a Magisk Module wasn't finished installing and potentially causing a bootloop.
banshee28 said:
Actually I am flashing the factory images I think they are called from here: Images
So maybe these are not OTA. I have only used these images.
Click to expand...
Click to collapse
Correct, those are not the OTA files, those are the full factory images. For reference, the OTAs are here Full OTA Images for Nexus and Pixel Devices, although I, too, prefer the full factory image, but the OTA as suggested by @Alekos above would be worth a try.
roirraW edor ehT said:
Google's Help Page for Find problem apps by rebooting to safe mode - this can be a lifesaver and keep you from having to do a restore to 100% complete stock or even from having to do a factory reset. This will deactivate all Magisk modules, and they'll remain deactivated even after you boot normally after briefly booting to safe mode. You can reenable the Magisk modules as you wish to try to narrow down the problem if it was caused by a Magisk module. This can even get things working again after a Magisk Module wasn't finished installing and potentially causing a bootloop.
Correct, those are not the OTA files, those are the full factory images. For reference, the OTAs are here Full OTA Images for Nexus and Pixel Devices, although I, too, prefer the full factory image, but the OTA as suggested by @Alekos above would be worth a try.
Click to expand...
Click to collapse
Yea I tried to enter safemode many times, unfortunately it never works. Each time I try now, hit the vol down when animation starts, it takes me to fastboot!
I will try the OTA next, maybe these will work!! Thanks.
banshee28 said:
Yea I tried to enter safemode many times, unfortunately it never works. Each time I try now, hit the vol down when animation starts, it takes me to fastboot!
I will try the OTA next, maybe these will work!! Thanks.
Click to expand...
Click to collapse
Safe Mode is definitely a challenge to get into until you get used to it. So you followed these directions for it exactly?
Press your phone's power button.
When the animation starts, press and hold your phone's volume down button. Keep holding it until the animation ends and your phone starts in safe mode.
You'll see "Safe mode" at the bottom of your screen.
As far as I know, the animation is after it's possible to get into fastboot mode, but maybe something else is going on here.
Good luck!
roirraW edor ehT said:
Safe Mode is definitely a challenge to get into until you get used to it. So you followed these directions for it exactly?
Press your phone's power button.
When the animation starts, press and hold your phone's volume down button. Keep holding it until the animation ends and your phone starts in safe mode.
You'll see "Safe mode" at the bottom of your screen.
As far as I know, the animation is after it's possible to get into fastboot mode, but maybe something else is going on here.
Good luck!
Click to expand...
Click to collapse
Yep, tried it many times, same way, it originally just rebooted and most recently reboots into fastboot each time.
I just successfully flashed the OTA image via sideload. Everything seemed to work and flash properly. Someone mentioned full factory image could require more space, so was hoping OTA was the answer....
Unfortunately it gets to animation, then eventually reboots.
Never had this many issues with a phone before, what could cause this while each image flashes "successfully"?
banshee28 said:
Yep, tried it many times, same way, it originally just rebooted and most recently reboots into fastboot each time.
I just successfully flashed the OTA image via sideload. Everything seemed to work and flash properly. Someone mentioned full factory image could require more space, so was hoping OTA was the answer....
Unfortunately it gets to animation, then eventually reboots.
Never had this many issues with a phone before, what could cause this while each image flashes "successfully"?
Click to expand...
Click to collapse
I wish I knew what else to suggest. About the only option left seems to be to use the Android Flash Tool including a full wipe. I would allow it to force flash all partitions and just untick the option to re-lock the bootloader so it stays unlocked.
banshee28 said:
Yea I tried to enter safemode many times, unfortunately it never works. Each time I try now, hit the vol down when animation starts, it takes me to fastboot!
I will try the OTA next, maybe these will work!! Thanks.
Click to expand...
Click to collapse
When your phone is rebooting/bootlooping, start holding the Volume down button when the screen is blank, before any logos start to appear. That should put you in safe mode.
Lughnasadh said:
When your phone is rebooting/bootlooping, start holding the Volume down button when the screen is blank, before any logos start to appear. That should put you in safe mode.
Click to expand...
Click to collapse
Appreciate all the help guys, but nothing is working. This did get me into fastboot quicker, skipping the animation but that's about it.
I tried flashing A side only, B side only, both sides, and both factory and OTA images, same. I can get to Animation each time, but eventually reboots. Amazing how filling up space from camera could have caused this!?
Will of coruse have a backup next time, but will also look for a phone with SD card for data so this would most likely never be an issue.
I think as edor has stated not sure there is much left to try.
banshee28 said:
Appreciate all the help guys, but nothing is working. This did get me into fastboot quicker, skipping the animation but that's about it.
I tried flashing A side only, B side only, both sides, and both factory and OTA images, same. I can get to Animation each time, but eventually reboots. Amazing how filling up space from camera could have caused this!?
Will of coruse have a backup next time, but will also look for a phone with SD card for data so this would most likely never be an issue.
I think as edor has stated not sure there is much left to try.
Click to expand...
Click to collapse
If you're bootloader is unlocked, just downloaded the full factory image (non ota), remove the " -w " command (which wipes data) in the flash-all.bat file and flash away. This will keep your data intact.
The flash tool should do the same thing but doing it manually, you can keep an eye on the progress in the command terminal window to make sure there are no errors.
The data and system partitions are different. Filling up your data partition won't cause corruption like this. They are completely separated partition tables.
Also you tried the flash tool and unchecked wipe and re-lock options?
I used the PixelFlahser app as well as the online official Android Flash Tool, with all those options unchecked, yes.
Both flashed with no errors although the phone never booted. I will try using ADB directly now and see if that helps!
So i used adb cli, and it did exactly the same. I am getting some errors though saying
Code:
"archive does not contain" and lists several items such as boot.sig, vendor_boot.sig, boot_other.img, odm_dlkm.img, product.sig, system.sig, etc....
Are these important??
I have flashed just using the zip files before with no special unzipping and they have always worked fine.
banshee28 said:
So i used adb cli, and it did exactly the same. I am getting some errors though saying
Code:
"archive does not contain" and lists several items such as boot.sig, vendor_boot.sig, boot_other.img, odm_dlkm.img, product.sig, system.sig, etc....
Are these important??
Click to expand...
Click to collapse
That is normal. That happens with every month's update.
Would installing a CUSTOM ROM or 13 Beta make any difference???
banshee28 said:
Would installing a CUSTOM ROM or 13 Beta make any difference???
Click to expand...
Click to collapse
No. Don't go down that road. If you can't get Stable working, then there's something deeper wrong. So you've tried the Android Flash Tool with all default options checked (to wipe, flash all partitions) except not to lock the bootloader? i.e. letting it wipe all your data?