Develop Bugs

Stuck at bouncing dots [SOLVED and ROOTED]

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.

Unlocking the bootloader without access to the OS

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

December OTA - "Couldn't Install System Update"

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.

Question Bricked Pixel 6 Pro Help needed

My pixel 6 pro is stuck in fastboot mode, and for some reason wont boot into android at all. It was running the android 13 beta 2, the device is not rooted, or anything. I have spent the best part of 2 hours navigating through the various bootloader/recovery menus on the phone, but not really getting anywhere. all I was trying to do was unenroll the phone from the beta updates, and return back to stock. it was downloading the latest public build after unenrolling the phone when something happened, and now it doesn't boot.
I am really stuck as I cant use the android flash tool to flash back to the public build of android 12, as I don't have OEM unlocking activated in developer settings on the phone, and obviously not being able to boot into android, means that I cant just restart to enable, like all the guides i have read tell you to do.
Is there a way to flash the phone back to stock android 12 through terminal some how without having OEM unlocking enabled? any help is appreciated, as I am currently looking at a £1000 paperweight at the moment.

There's another software on here called pixel flasher try that if they don't work see of more knowledgeable people message
might have to speak to Google and also were you bought it from
I had the 6 pro put on charge then turned on did restore from back up and it was like 5 to 100 of apps and then it did the march update and it boot looped that was on Saturday
I got into the safeboot mode or whatever it restated as that what I clicked then got into mode again then from there it's froze
I didn't get a replacement till Tuesday lol that was ee had no problems with new one

How about using the android flash tool to reflash the latest beta that you were on?

Also...flashing without a bootloader unlock is like Android No-No ...no.1 ...

TLS993 said:
My pixel 6 pro is stuck in fastboot mode, and for some reason wont boot into android at all. It was running the android 13 beta 2, the device is not rooted, or anything. I have spent the best part of 2 hours navigating through the various bootloader/recovery menus on the phone, but not really getting anywhere. all I was trying to do was unenroll the phone from the beta updates, and return back to stock. it was downloading the latest public build after unenrolling the phone when something happened, and now it doesn't boot.
I am really stuck as I cant use the android flash tool to flash back to the public build of android 12, as I don't have OEM unlocking activated in developer settings on the phone, and obviously not being able to boot into android, means that I cant just restart to enable, like all the guides i have read tell you to do.
Is there a way to flash the phone back to stock android 12 through terminal some how without having OEM unlocking enabled? any help is appreciated, as I am currently looking at a £1000 paperweight at the moment.
Click to expand...
Click to collapse
Since you are able to boot into fastboot, your device isn't bricked and should be recoverable. The first thing you will want to try is booting into Safe Mode to enable OEM unlocking:
1. Press your phone's power button.
2. 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.
3. You'll see "Safe mode" at the bottom of your screen.
If that doesn't work, you can also try to flashing the OTA in recovery mode. Lots of videos on YouTube on how to update via OTA in recovery mode. Here's the Android OTA download page - you won't lose your data with this method. Chose the right image.
Next option would be to try wipe or reset by using the Recovery Mode (this will wipe your phone): While in Fastboot/Bootloader, choose Recovery Mode with the Volume buttons. On your screen, “No command” is displayed. Press and hold the Power button. While you hold Power, press the Volume Up button and let go of both buttons quickly. Choose factory reset option (this will wipe your device so be sure to try safe mode and OTA update methods before this option if you are trying not to wipe the phone).
If you just want to get your phone back without trying to save data, try Google's Official Flash Tool. I know most will say it's a waste of time if your BL is locked - but there have been many reports of users fixing issues just like yours even with a locked Bootloader.
Android Flash Tool
flash.android.com
You'll need a Chrome browser.
Because you're on 13 Beta, you could try just reinstalling the Core OS with the web flash Tool. Uncheck all the boxes (don't wipe or re-lock etc).

TLS993 said:
My pixel 6 pro is stuck in fastboot mode, and for some reason wont boot into android at all. It was running the android 13 beta 2, the device is not rooted, or anything. I have spent the best part of 2 hours navigating through the various bootloader/recovery menus on the phone, but not really getting anywhere. all I was trying to do was unenroll the phone from the beta updates, and return back to stock. it was downloading the latest public build after unenrolling the phone when something happened, and now it doesn't boot.
I am really stuck as I cant use the android flash tool to flash back to the public build of android 12, as I don't have OEM unlocking activated in developer settings on the phone, and obviously not being able to boot into android, means that I cant just restart to enable, like all the guides i have read tell you to do.
Is there a way to flash the phone back to stock android 12 through terminal some how without having OEM unlocking enabled? any help is appreciated, as I am currently looking at a £1000 paperweight at the moment.
Click to expand...
Click to collapse
Go back to 13 beta 2 for now. Download the ota onto cpu. Go into fastboot, boot into recovery. Factory wipe in recovery. Then in recovery, go to sideload via adb. Adb sideload the beta zip. You're welcome . Of course you'll have to know how to use adb and all that but hopefully you do.

opz187 said:
Go back to 13 beta 2 for now. Download the ota onto cpu. Go into fastboot, boot into recovery. Factory wipe in recovery. Then in recovery, go to sideload via adb. Adb sideload the beta zip. You're welcome . Of course you'll have to know how to use adb and all that but hopefully you do.
Click to expand...
Click to collapse
Thanks for this, I will give it a go. I have used ADB before, so should be fine with that

Alekos said:
Since you are able to boot into fastboot, your device isn't bricked and should be recoverable. The first thing you will want to try is booting into Safe Mode to enable OEM unlocking:
1. Press your phone's power button.
2. 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.
3. You'll see "Safe mode" at the bottom of your screen.
If that doesn't work, you can also try to flashing the OTA in recovery mode. Lots of videos on YouTube on how to update via OTA in recovery mode. Here's the Android OTA download page - you won't lose your data with this method. Chose the right image.
Next option would be to try wipe or reset by using the Recovery Mode (this will wipe your phone): While in Fastboot/Bootloader, choose Recovery Mode with the Volume buttons. On your screen, “No command” is displayed. Press and hold the Power button. While you hold Power, press the Volume Up button and let go of both buttons quickly. Choose factory reset option (this will wipe your device so be sure to try safe mode and OTA update methods before this option if you are trying not to wipe the phone).
If you just want to get your phone back without trying to save data, try Google's Official Flash Tool. I know most will say it's a waste of time if your BL is locked - but there have been many reports of users fixing issues just like yours even with a locked Bootloader.
Android Flash Tool
flash.android.com
You'll need a Chrome browser.
Because you're on 13 Beta, you could try just reinstalling the Core OS with the web flash Tool. Uncheck all the boxes (don't wipe or re-lock etc).
Click to expand...
Click to collapse
Thankyou for the suggestion, my phone however will not boot into any form of android. It just boots straight to the fast boot screen every time. Pressing the power button, you see the Google logo, but it then boots straight to fastboot. It's as if there is no os on the device at all

TLS993 said:
Thankyou for the suggestion, my phone however will not boot into any form of android. It just boots straight to the fast boot screen every time. Pressing the power button, you see the Google logo, but it then boots straight to fastboot. It's as if there is no os on the device at all
Click to expand...
Click to collapse
You mention power button but you never said you held the volume down button as you were powering on. you must hold the volume down button.

TLS993 said:
Thankyou for the suggestion, my phone however will not boot into any form of android. It just boots straight to the fast boot screen every time. Pressing the power button, you see the Google logo, but it then boots straight to fastboot. It's as if there is no os on the device at all
Click to expand...
Click to collapse
I understand it won't boot into Android. Your phone is fine. If you want help, dm me, I will get you sorted. You just need to re-flash Android using the above Flash tool.

Thanks everyone, After a bit of struggling to get the system image flashed, I finally managed to get it done using ADB sideload.
Took me around 15 attempts to get there, but I'm now up and running again. Thanks to everyone who replied, and assisted with the issue!

TLS993 said:
Thanks everyone, After a bit of struggling to get the system image flashed, I finally managed to get it done using ADB sideload.
Took me around 15 attempts to get there, but I'm now up and running again. Thanks to everyone who replied, and assisted with the issue!
Click to expand...
Click to collapse
That's good to hear - it's hard to brick a Pixel.
Best options to resolve issues is the Flash Tool, OTA Update or cli image. The OTA can be tricky when using platforms tools (adb/fastboot).

Hi
I ordered my phone from US, but did not realize that its Verizon OEM locked.
Any Idea how to unlock the bootloader? any way even paid method i am ready.
Now I am on A13 beta which is fine, can I flash a full rom using ADB update without any issues?

anasmhds said:
Hi
I ordered my phone from US, but did not realize that its Verizon OEM locked.
Any Idea how to unlock the bootloader? any way even paid method i am ready.
Now I am on A13 beta which is fine, can I flash a full rom using ADB update without any issues?
Click to expand...
Click to collapse
No Verizon device can ever have its bootloader unlocked. Sorry, you're just out of luck. With a locked bootloader, you can only ever upgrade to other official ROMs, such as Android 13 Beta 3, 4, and final release.

roirraW edor ehT said:
No Verizon device can ever have its bootloader unlocked. Sorry, you're just out of luck. With a locked bootloader, you can only ever upgrade to other official ROMs, such and Android 13 Beta 3, 4, and final release.
Click to expand...
Click to collapse
Thanks for your feedback.... just bad luck

TLS993 said:
Thanks everyone, After a bit of struggling to get the system image flashed, I finally managed to get it done using ADB sideload.
Took me around 15 attempts to get there, but I'm now up and running again. Thanks to everyone who replied, and assisted with the issue!
Click to expand...
Click to collapse
Please how did you do for ADB sideload, because I now have the same problem as you and I'm still stuck on fastboot mode
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

radioxmen said:
Please how did you do for ADB sideload, because I now have the same problem as you and I'm still stuck on fastboot modeView attachment 5618033
Click to expand...
Click to collapse
Select recovery mode.
When you see No Command, press power and volume up at the same time (quickly). Then try factory reset. If that doesn't work, choose ota update and follow the links above.

Have same exact issue here.
When I try to sideload, I constantly get "cannot read" error.
I tried Large Address Awareness but even that didn't work.
Any help is appreciated

So this tool cant fix your problems?
Android Flash Tool
flash.android.com

No, I keep getting error that OEM is not unlocked

Question [Solved] root problems

So I updated my phone to Android 13, after I updated my phone I needed to regain root perms, so I flashed a patched magisk boot.img file, it went wrong here.
so now(after) I am unable to start my pixel 6 pro, all I get is "Your device is corrupted it cannot be trusted and may not work properly", + the bootloader is unlocked message.
and whenever I start the phone it either shows a battery icon(as in it has no battery? idk it was on 20%) or the colorful "Google" logo, no it doesn't show the colored "G"/doesn't get to that point(as in it's stuck).
I cannot get the phone to show up in "adb devices" it has worked before.
I very much need help, I went throughout all of YouTube and Google(search) and found nothing.
Any idea?

can you get into bootloader and does it detect?

passion8059 said:
can you get into bootloader and does it detect?
Click to expand...
Click to collapse
Okay, so how do I even get it into bootloader?

TheShinyEnd said:
Okay, so how do I even get it into bootloader?
Click to expand...
Click to collapse
Power + Vol - (down)

passion8059 said:
Power + Vol - (down)
Click to expand...
Click to collapse
So I am right now am seeing the battery icon/logo(powered off) and when i press the power button with the vol down it doens't seem to move.. unless it's like a 20sec press?

TheShinyEnd said:
So I updated my phone to Android 13, after I updated my phone I needed to regain root perms, so I flashed a patched magisk boot.img file, it went wrong here.
so now(after) I am unable to start my pixel 6 pro, all I get is "Your device is corrupted it cannot be trusted and may not work properly", + the bootloader is unlocked message.
and whenever I start the phone it either shows a battery icon(as in it has no battery? idk it was on 20%) or the colorful "Google" logo, no it doesn't show the colored "G"/doesn't get to that point(as in it's stuck).
I cannot get the phone to show up in "adb devices" it has worked before.
I very much need help, I went throughout all of YouTube and Google(search) and found nothing.
Any idea?
Click to expand...
Click to collapse
You must have flashed the boot.img that someone else uploaded from their phone? I did the same yesterday with the same result.
Fix....Use Android flash tool to flash the Aug update;
*****MAKE SURE TO UNCHECK lock bootloader, wipe device, force flash partitions. after it is finished.... copy boot.img to your phone and patch it with magisk. Then copy the magisk patched boot.img back to your PC and then flash your patched boot.img to both slots using Platform Tools CMD Good Luck

Okay I manage to get it into Fastboot, thank you very much both! much appreciate the help and your time!

TheShinyEnd said:
So I am right now am seeing the battery icon/logo(powered off) and when i press the power button with the vol down it doens't seem to move.. unless it's like a 20sec press?
Click to expand...
Click to collapse
TheShinyEnd said:
So I am right now am seeing the battery icon/logo(powered off) and when i press the power button with the vol down it doens't seem to move.. unless it's like a 20sec press?
Click to expand...
Click to collapse
remove any cables wait till nothing on screen & try again

jcp2 said:
You must have flashed the boot.img that someone else uploaded from their phone? I did the same yesterday with the same result.
Fix....Use Android flash tool to flash the Aug update;
*****MAKE SURE TO UNCHECK lock bootloader, wipe device, force flash partitions. after it is finished.... copy boot.img to your phone and patch it with magisk. Then copy the magisk patched boot.img back to your PC and then flash your patched boot.img to both slots using Platform Tools CMD Good Luck
Click to expand...
Click to collapse
Diff question:
I tried to(tmp) boot with the patched magisk boot.img but it doesn't seem to be willing to boot with it. how did you manage to get it to boot with the patched boot.img? is it any different than the normal android 12?
-- edit: I use my own patched files, that are not "made" by others. using the android 13 image file

I always download the full zip in order to get the boot.img for the zip, then I use Android Flash Tool to download and flash the full zip update. Let the phone reboot unrooted. If you have the magisk patched boot.img from your phone, copy it to your PC and use Platform tools to flash it to both slots using the CMD prompt.
Open a Command Prompt in the folder you copied the patched boot.img to.
Flash the boot.img (Magisk Patched) to both slots: fastboot flash boot <drag and drop boot.img> --slot all

TheShinyEnd said:
Diff question:
I tried to(tmp) boot with the patched magisk boot.img but it doesn't seem to be willing to boot with it. how did you manage to get it to boot with the patched boot.img? is it any different than the normal android 12?
-- edit: I use my own patched files, that are not "made" by others. using the android 13 image file
Click to expand...
Click to collapse
Before you do any more modding, have you flashed the A13 bootloader to both slots so you don't get in trouble with the new ARB? If not, I suggest you do so before you do anything.
If you have, never mind, lol...

I've used the android flash tool, now shows that the phone is corrupt, Android Recovery -- cannot load Android system Your data may be corrupt. If you continue to get this message...
Try again or Factory data reset.
13.0.0 (TP1A.220624.021, Aug 2022)
Yes I got in trouble with the ARB
I don't really understand on how this works, I just follow a YouTube tutorial. not that i'm new(to rooting, been doing this from March~) but that just I don't understand on how android works, especially if a13 is different than a12
The tutorial I've used :
Spoiler
I'll try to recover the phone will see how it'll go, and if i won't manage i'll reset the device, I backed up via Google one.. i'm less worried -- data reset. was unable to recover

TheShinyEnd said:
I've used the android flash tool, now shows that the phone is corrupt, Android Recovery -- cannot load Android system Your data may be corrupt. If you continue to get this message...
Try again or Factory data reset.
13.0.0 (TP1A.220624.021, Aug 2022)
Yes I got in trouble with the ARB
I don't really understand on how this works, I just follow a YouTube tutorial. not that i'm new(to rooting, been doing this from March~) but that just I don't understand on how android works, especially if a13 is different than a12
The tutorial I've used :
Spoiler
I'll try to recover the phone will see how it'll go, and if i won't manage i'll reset the device, I backed up via Google one.. i'm less worried -- data reset. was unable to recover
Click to expand...
Click to collapse
Fixed it.
so a little back story, at a random point in my day the phone(p6p) said restart to apply update, and I was rooted at the time and thought it would failed, and I went for it. it did manage to install(2nd "July" august update). then I saw a vid about A13 and thought I might aswell try to install A13 on my phone, I opted in the beta and downloaded A13, took a little bit but I manage to install it aswell.
I think this was the problem. I don't know as to how, but maybe magisk or some module manage to make the device itself think it's not rooted.. albeit it shows that the bootloader is indeed unlocked.
Needless to say, I managed to fix the problem, gained root perms again. thanks for the help and your time! much appreciated

TheShinyEnd said:
I opted in the beta and downloaded A13, took a little bit but I manage to install it aswell.
Click to expand...
Click to collapse
Opting into the Beta wasn't necessary before manually downloading Android 13 - if that's what you meant.
Now that you've opted into the Beta program, you should unopt out of it, otherwise you will continue to get beta versions of Android as opposed to stable.

roirraW edor ehT said:
Opting into the Beta wasn't necessary before manually downloading Android 13 - if that's what you meant.
Now that you've opted into the Beta program, you should unopt out of it, otherwise you will continue to get beta versions of Android as opposed to stable.
Click to expand...
Click to collapse
I meant the System update downloading phase

TheShinyEnd said:
So I updated my phone to Android 13, after I updated my phone I needed to regain root perms, so I flashed a patched magisk boot.img file, it went wrong here.
so now(after) I am unable to start my pixel 6 pro, all I get is "Your device is corrupted it cannot be trusted and may not work properly", + the bootloader is unlocked message.
and whenever I start the phone it either shows a battery icon(as in it has no battery? idk it was on 20%) or the colorful "Google" logo, no it doesn't show the colored "G"/doesn't get to that point(as in it's stuck).
I cannot get the phone to show up in "adb devices" it has worked before.
I very much need help, I went throughout all of YouTube and Google(search) and found nothing.
Any idea?
Click to expand...
Click to collapse
same issue here, did you find any solution buddy??
snaptube
vidmate​

paulanswer240 said:
same issue here, did you find any solution buddy??
Click to expand...
Click to collapse
explain? can you not boot or you don't have root? or both