Develop Bugs

[Q] Soft Brick / USB Brick / General Weirdness

Phone: VZW Galaxy Nexus, Rooted, TWRP Recovery, Lean Kernel
For the first (and last) time in my life I decided to dirty flash a ROM (4/16 build of Project Elite) to my phone (from an earlier build of PE). My phone apparently hated that. It has created an odd world of problems for my phone that I am hoping someone may be able to see a trend with and offer up some suggestions for escaping this odd world.
Here are my phone's symptoms:
(1) Earpiece on phone stopped working: During phone calls, I can only hear audio when using speakerphone. I was able to remedy this by getting the SoundAbout App from the Play store. This tool allows you to manually change how the audio is routed. My phone thinks a headphone is plugged in and tries to route the audio through the headphone jack. This app allows me to fix that problem.
(2) USB File Transfer Mode stopped working: When connecting my phone to the computer it will charge (sometimes, see #3) but my computer will not recognize it as a device. Consequently, adb (and wireless adb), fastboot and ODIN all will not connect to my phone because the phone is not recognized. I have uninstalled, updated and re-installed just about every driver set I can find for the Galaxy Nexus/ I know it is not a driver issue because my wife's Nexus connects to the CPU just fine.
(3) Phone Charging is Intermittent: I have trouble finding a trend with this one. If I toggle Fast Charge (Off or On), my phone will no longer charge. This is fixed by powering off the phone with the cable plugged in. At that point the white battery icon appears and the phone begins charging. If I power the phone back on, the phone will continue to charge but will not be recognized as a USB device.
Here is what I have tried over the past 2 days:
(1) Both GNEX Toolkits: With no USB connectivity, adb and fastboot are not options. This option becomes unavailable with no usb. Have tried both.
(2) ODIN: Phone is not recognized by ODIN tool.
(3) Cleaning USB/Headphone Ports: This produced some interesting black stuff, but no results.
(4) Clean Flash of PE 4/16 Build: Wipe data/cache/dalvik and re-flash. Same problem.
(5) Clean Flash of Stock Rooted Build: Wipe data/cache/dalvik and flash. Same problem.
(6) Mobile ODIN: Cannot locate the tar balls for a stock 4.2.2 factory flash. Have found the necessary files for 4.0.2, but these will not flash in Mobile ODIN. I have read that you have to be on the same android version as the ODIN tar files you are trying to flash. I think this is my best option at this point, but I cannot for the life of me figure out how to get Mobile ODIN to work.
As far as I can tell this is a software problem that is baked somewhere deep in the phone. Since the USB and headphone problem started at the same time, I do not believe it to be hardware. My theory is that somehow fast-charge is locked on (?) and my phone is locked to routing the audio to the headset. If I can find a way to completely wipe everything off and start fresh, I believe my problem will be solved.
Does anybody have any ideas what may be going on here and how I may be able to get this phone back to Stock?
tldr; no usb, no headset audio after dirty flash, how do i get back to stock??

In fastboot, there's no fast charge, since there's no Android running aka no Android kernel running.
Sent from my Nexus

bk201doesntexist said:
In fastboot, there's no fast charge, since there's no Android running aka no Android kernel running.
Sent from my Nexus
Click to expand...
Click to collapse
Thanks for the response.
I am running Win7. Like I said, I have tried connecting my wife's Nexus to the same computer and it is recognized as usual. The only reason I thought it had something to do with FastCharge was that toggling it has an effect on the charging capabilities of my phone. When I boot into FastBoot the phone still does not show up in the Toolkit and running any operation in the Toolkit that uses FastBoot gets hung on "waiting for devices."
My latest experiment is to Flash a Nandroid of a Stock Nexus Image. However, I have not been able to find flashable stock image! Seems like something that would have been a common file so if you are aware of any Stock Nandroid Backups I would love to try that.

7ontheline said:
Thanks for the response.
I am running Win7. Like I said, I have tried connecting my wife's Nexus to the same computer and it is recognized as usual. The only reason I thought it had something to do with FastCharge was that toggling it has an effect on the charging capabilities of my phone. When I boot into FastBoot the phone still does not show up in the Toolkit and running any operation in the Toolkit that uses FastBoot gets hung on "waiting for devices."
My latest experiment is to Flash a Nandroid of a Stock Nexus Image. However, I have not been able to find flashable stock image! Seems like something that would have been a common file so if you are aware of any Stock Nandroid Backups I would love to try that.
Click to expand...
Click to collapse
I don't use toolkits, so I don't know how to help there. Does the device get recognized under Device Manager as a fastboot interface? Have you followed http://forum.xda-developers.com/showthread.php?t=1812959? Tried the Universal Naked Drivers?

bk201doesntexist said:
I don't use toolkits, so I don't know how to help there. Does the device get recognized under Device Manager as a fastboot interface? Have you followed http://forum.xda-developers.com/showthread.php?t=1812959? Tried the Universal Naked Drivers?
Click to expand...
Click to collapse
My device does not get recognized within Device Manager. No yellow exclamation mark, no mention of a connected device, nothing. When my wife's Nexus is connected it shows up as expected and communicates just fine via adb. I have followed the guide you mentioned and have installed ROMs many many times with nor problems previously. I have tried the Universal Naked Drivers. I uninstalled all other drivers and installed these. They work as expected with another Nexus, just nothing with mine. Starting to look like I may just be out of luck here.

7ontheline said:
My device does not get recognized within Device Manager. No yellow exclamation mark, no mention of a connected device, nothing. When my wife's Nexus is connected it shows up as expected and communicates just fine via adb. I have followed the guide you mentioned and have installed ROMs many many times with nor problems previously. I have tried the Universal Naked Drivers. I uninstalled all other drivers and installed these. They work as expected with another Nexus, just nothing with mine. Starting to look like I may just be out of luck here.
Click to expand...
Click to collapse
You seem to be confusing stuff... Fastboot is not ADB, and you have to feed the same driver to windows twice.
You've done this? Sure the USB port doesn't have a bent pin or something?
Sent from my Nexus

My phone is doing the exact same thing. Started about 2 weeks ago. I can't remember but I think it started after flashing the latest liquid smooth rom. I don't think it was a dirty flash but hell I can't remember.
Sent from my Galaxy Nexus using xda app-developers app

tdf666 said:
My phone is doing the exact same thing. Started about 2 weeks ago. I can't remember but I think it started after flashing the latest liquid smooth rom. I don't think it was a dirty flash but hell I can't remember.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Let me know if you figure anything out. I am just dealing with it right now using the SoundAbout App and rebooting my phone whenever it won't charge. It is pretty annoying, but I am at a loss for fixes at this point.
I am not really confusing ADB and Fastboot. I understand that they are two separate ways of communicating with the phone via USB. However, as I stated, there is no USB connectivity other than for charging.

I'm at a loss. Then the other day I got down to 13 percent battery and it started shutting off. I think I'm just going to get another phone. This has been the best and worst phone I've ever had.
Sent from my Galaxy Nexus using xda app-developers app

Stuck on CyanogenMod logo?!

Phone is going full retard now
I have been using CyanogenMod 10.1 nightly 'till now.
I fell down one day and since then it's stuck on the CyanogenMod boot logo. forever.
Recovery is accessible, and I've tried flashing the rom again but I can't get past the point when I should type in adb "fastboot flash boot boot.img"
It's just "<waiting for device>"
and nothing's happening.
even though the device appears on the adb devices list.
I also can't mount storage through recovery.
What the **** is happening to my phone and what can I do to fix it?

Does it appear on the fastboot devices list? Is your phone in fastboot mode, not hboot?

Did you try flashing an RUU?
Sent from my Desire HD using Tapatalk 4 Beta

bananagranola said:
Does it appear on the fastboot devices list? Is your phone in fastboot mode, not hboot?
Click to expand...
Click to collapse
Uhm, it depends. usually it appears on the devices list on adb when I do things right.
It only appeared when I was in clockworkmod recovery though.
The usb completly disconnects whenever I'm in hboot/white background thing.
humzaahmed155 said:
Did you try flashing an RUU?
Sent from my Desire HD using Tapatalk 4 Beta
Click to expand...
Click to collapse
Which RUU though? there are thousands. I didn't try
You helped me that other time to root my phone, if you remember.
well I'm now really scared of flashing RUUs and doing factory resets, as I'm scared the phone will unroot.

YagFrazier said:
Uhm, it depends. usually it appears on the devices list on adb when I do things right.
It only appeared when I was in clockworkmod recovery though.
The usb completly disconnects whenever I'm in hboot/white background thing.
Which RUU though? there are thousands. I didn't try
You helped me that other time to root my phone, if you remember.
well I'm now really scared of flashing RUUs and doing factory resets, as I'm scared the phone will unroot.
Click to expand...
Click to collapse
Hmm, so it looks like your computer isn't detecting your phone in fastboot right, go into device manager and check what the phone has been installed as, Windows sometimes likes to mess around with drivers when it comes to Android phones and debugging
Sent from my Desire HD using Tapatalk 4

Wait, adb and fastboot are not them same...

humzaahmed155 said:
Hmm, so it looks like your computer isn't detecting your phone in fastboot right, go into device manager and check what the phone has been installed as, Windows sometimes likes to mess around with drivers when it comes to Android phones and debugging
Sent from my Desire HD using Tapatalk 4
Click to expand...
Click to collapse
By the way did you select Fastboot when in hboot?
Sent from my Desire HD using Tapatalk 4

YagFrazier said:
Uhm, it depends. usually it appears on the devices list on adb when I do things right.
It only appeared when I was in clockworkmod recovery though.
The usb completly disconnects whenever I'm in hboot/white background thing.
Which RUU though? there are thousands. I didn't try
You helped me that other time to root my phone, if you remember.
well I'm now really scared of flashing RUUs and doing factory resets, as I'm scared the phone will unroot.
Click to expand...
Click to collapse
Have you tried re installing the drivers with the phone unplugged? if you are using windows OS. Try using a different USB port, plugged directly to the motherboard. Do not use a usb hub

humzaahmed155 said:
Hmm, so it looks like your computer isn't detecting your phone in fastboot right, go into device manager and check what the phone has been installed as, Windows sometimes likes to mess around with drivers when it comes to Android phones and debugging
Sent from my Desire HD using Tapatalk 4
Click to expand...
Click to collapse
Yup, my USB also got broken last time I tried to root and this time I used my dad's Kindle USB. looks like it didn't fit that well with the device or something, he got me a normal USB thing and now I can even mount USB storage through ClockworkMod recovery. great since I needed to backup photos.
humzaahmed155 said:
By the way did you select Fastboot when in hboot?
Sent from my Desire HD using Tapatalk 4
Click to expand...
Click to collapse
Nope, looks like that was the problem. stupid me.
It works, it boots. everything seems alright.
The thing is, now there's no wifi. it doesn't want to go on at all.
I've been trying to switch it on for an hour now, it just "turns wifi on" and goes off again. the off button is gray.
Edit: I switched between CyanogenMod 10.1 Nightlies and CodefireXperiment ROM and with nova launcher it's the same, just better now. so happy to have my phone now

YagFrazier said:
Yup, my USB also got broken last time I tried to root and this time I used my dad's Kindle USB. looks like it didn't fit that well with the device or something, he got me a normal USB thing and now I can even mount USB storage through ClockworkMod recovery. great since I needed to backup photos.
Nope, looks like that was the problem. stupid me.
It works, it boots. everything seems alright.
The thing is, now there's no wifi. it doesn't want to go on at all.
I've been trying to switch it on for an hour now, it just "turns wifi on" and goes off again. the off button is gray.
Edit: I switched between CyanogenMod 10.1 Nightlies and CodefireXperiment ROM and with nova launcher it's the same, just better now. so happy to have my phone now
Click to expand...
Click to collapse
Hmm that wifi issue seems interesting, glad i could help

YagFrazier said:
The thing is, now there's no wifi. it doesn't want to go on at all.
I've been trying to switch it on for an hour now, it just "turns wifi on" and goes off again. the off button is gray.
Edit: I switched between CyanogenMod 10.1 Nightlies and CodefireXperiment ROM and with nova launcher it's the same, just better now. so happy to have my phone now
Click to expand...
Click to collapse
Had the same problem with cyanogen10.1, no wifi. I think some DHD's won't work with all cyanogen's. With the XPERIA rom i had wifi, but no GPS In another rom (don't know, which it was) phone said no pictures (but there were 15 to see with ghostcommander...)
Now i installed Android Revolution 7.0 (its a 2.3.5, but its very stable, all works fine...).
It seems, that some DHD's dont't like Android 4 and above... :crying:

ammo12 said:
Had the same problem with cyanogen10.1, no wifi. I think some DHD's won't work with all cyanogen's. With the XPERIA rom i had wifi, but no GPS In another rom (don't know, which it was) phone said no pictures (but there were 15 to see with ghostcommander...)
Now i installed Android Revolution 7.0 (its a 2.3.5, but its very stable, all works fine...).
It seems, that some DHD's dont't like Android 4 and above... :crying:
Click to expand...
Click to collapse
Get yourself a CodefireXperiment rom. Together with Nova launcher it's the same as CyanogenMod and even better.
Wifi's good.
I usually stay away from Android Revolution, I developed sincere hate for Sense 3.6 and below.

[Q] Tablet bricked? ADB and Fastboot not detecting device

I'm troubleshooting my friend's nexus 7 2013.
It's stock, not rooted and still locked.
The table won't boot into the OS and recovery isn't working either. They both get stuck at the google logo.
I've gone into bootloader and tried
Code:
ADB devices
and
Code:
fastboot devices
neither ever show the nexus 7.
Now I have my own nexus 7 2013. I've unplugged his and plugged in mine and it recognizes my right away, so I doubt this is a driver issue.
I'm not sure where else to go from here.
Any ideas?

Laxxium said:
I'm troubleshooting my friend's nexus 7 2013.
It's stock, not rooted and still locked.
The table won't boot into the OS and recovery isn't working either. They both get stuck at the google logo.
I've gone into bootloader and tried
Code:
ADB devices
and
Code:
fastboot devices
neither ever show the nexus 7.
Now I have my own nexus 7 2013. I've unplugged his and plugged in mine and it recognizes my right away, so I doubt this is a driver issue.
I'm not sure where else to go from here.
Any ideas?
Click to expand...
Click to collapse
Bootloader only works fastboot. But not if the usb port itself or the boards on the tab have gone south. Did you check that? In my experience if non-booting was caused by Lollipop OTA, the motherboard is messed up beyond a possibility of recovery even for Asus. No unlocking means no flashing of anything. Shows vital signs, but really catatonic.

graphdarnell said:
Bootloader only works fastboot.
Click to expand...
Click to collapse
Not sure what you mean here.
graphdarnell said:
But not if the usb port itself or the boards on the tab have gone south. Did you check that?
Click to expand...
Click to collapse
How do I check this?
graphdarnell said:
In my experience if non-booting was caused by Lollipop OTA, the motherboard is messed up beyond a possibility of recovery even for Asus. No unlocking means no flashing of anything. Shows vital signs, but really catatonic.
Click to expand...
Click to collapse
So is the tablet a lost cause? There's no saving it?

We're talking 3 different things here:
1. While on the bootloader page, only fastboot works; ADB won't;
2. Assuming the rest of the equipment functions properly (PC, cable, SDK, drivers), and the USB port is bad, fastboot won't work evidently. The quickest way to test is to use OTG. But since your tab is not going past the Google logo, OTG can't be accessed. If you have an HDMI adapter that hooks your tab to an LCD TV, you might get a mirror image on the TV. If that happens, then the USB port is still good;
3. If the tab turns out the way it is as a result of your "upgrading" it to official Lollipop via OTA, it's more than likely hard-bricked. The only solution is a replacement motherboard.

Stuck in twrp Can not get computer & phone to communicate through adb

I have no files on the phone no Os I do have a backup on my pc but no way to get it on the phone any & all ideas please

WoZzYDoesitbest said:
I have no files on the phone no Os I do have a backup on my pc but no way to get it on the phone any & all ideas please
Click to expand...
Click to collapse
And how did you arrive at this point??
Different USB A to USB C cable's and ports.
Different pc.
Until you get synced with your pc, there's not really much you can do except try a factory reset.

Badger50 said:
And how did you arrive at this point??
Different USB A to USB C cable's and ports.
Different pc.
Until you get synced with your pc, there's not really much you can do except try a factory reset.
Click to expand...
Click to collapse
I tried installing nitrogen but would not get past booting image

WoZzYDoesitbest said:
I tried installing nitrogen but would not get past booting image
Click to expand...
Click to collapse
Then how do you not have any files on your phone? Sorry, I'm just a little confused. Have you tried flashing nitrogen and the twrp installer zip again?
Your device switched slots when you flashed the rom, usually flashing it again will work.

connect the phone on computer if you hear it connected its fine. Just hold the power button + Vol up to go to recovery then factory reset or reboot to bootloader.. i had the same problem 5 hours ago..
its so hard to install a rom, sometimes if you get successful one, once booted up, there's an error ecc..
goodluck.. dont panic.

kismetmookz said:
connect the phone on computer if you hear it connected its fine. Just hold the power button + Vol up to go to recovery then factory reset or reboot to bootloader.. i had the same problem 5 hours ago..
its so hard to install a rom, sometimes if you get successful one, once booted up, there's an error ecc..
goodluck.. dont panic.
Click to expand...
Click to collapse
I got. It Thanks so weird to flash roms. On this phone

WoZzYDoesitbest said:
I got. It Thanks so weird to flash roms. On this phone
Click to expand...
Click to collapse
Yes indeed, i never had problems installing roms before, but on this device you have to be 100% precise with the instructions to make it work.
How's it going bro? Did you manage to make it work?

kismetmookz said:
Yes indeed, i never had problems installing roms before, but on this device you have to be 100% precise with the instructions to make it work.
How's it going bro? Did you manage to make it work?
Click to expand...
Click to collapse
Yeah I got Dirty unicorns to boot again this phone is so weird I really wish we had a rom like pure nexus that rom was so dam beast

WoZzYDoesitbest said:
Yeah I got Dirty unicorns to boot again this phone is so weird I really wish we had a rom like pure nexus that rom was so dam beast
Click to expand...
Click to collapse
I loved pure rom on my 6P, unfortunately I think the developer has been consumed with"real life" so we may never see it.
Sent from my Pixel 2 XL using XDA Labs

That's a shame but understandable

Question Can't do anything with a device, looking for a help!

So I've got into a big trouble... I wanted to manually update my Pixel 6 Pro to the latest version using an official OTA (since the update wasn't available yet for my country and I wanted to stay up-to-date). It was all fine until it said 74 % done... and the power in my house has completely turned off... The device hasn't given me any error and rebooted, hower it got stuck on a Google logo. I rebooted to the recovery mode how it was suggested and did a clean factory reset, then rebooted again... and nothing changed, only the logo background has changed (white vs black). The BIGGEST problem is, the device OEM is NOT unlocked I tried entering the fastboot mode and flashing the device with a recovery image but it obviously didn't work as it required OEM to be unlocked... I am in a big depression now, somehow I fear that it's not fixable... But if some awesome soul could suggest a way to try out, that would be great! Thanks in advance.

I would try the android flash tool and flash the whole full ROM onto the phone. Expect to lose your data though.

mkhcb said:
I would try the android flash tool and flash the whole full ROM onto the phone. Expect to lose your data though.
Click to expand...
Click to collapse
Doesn't your phone have to be unlocked to use the flash tool?

The data is all backed up so it's not a problem to lose it. The problem is actually making the phone to boot past the logo... I will try that Android Flash Tool but I fear that the phone should be unlocked first

Try this tool: https://pixelrepair.withgoogle.com/carrier_selection
Not sure if its any different to the android flash tool.

As expected, Android Flash Tool requires you to to have the device unlocked. At this point I am out of ideas and is truly disappointed. The tool mentioned above probably works the same way.

Maybe try sideloading OTA again. Are you able to do that?

mclarence said:
Try this tool: https://pixelrepair.withgoogle.com/carrier_selection
Not sure if its any different to the android flash tool.
Click to expand...
Click to collapse
McNaccken said:
As expected, Android Flash Tool requires you to to have the device unlocked. At this point I am out of ideas and is truly disappointed. The tool mentioned above probably works the same way.
Click to expand...
Click to collapse
Unfortunately, someone else in another thread reported that the Pixel Repair site (not the Android Flash Tool) hasn't been updated for the P6P.

McNaccken said:
So I've got into a big trouble... I wanted to manually update my Pixel 6 Pro to the latest version using an official OTA (since the update wasn't available yet for my country and I wanted to stay up-to-date). It was all fine until it said 74 % done... and the power in my house has completely turned off... The device hasn't given me any error and rebooted, hower it got stuck on a Google logo. I rebooted to the recovery mode how it was suggested and did a clean factory reset, then rebooted again... and nothing changed, only the logo background has changed (white vs black). The BIGGEST problem is, the device OEM is NOT unlocked I tried entering the fastboot mode and flashing the device with a recovery image but it obviously didn't work as it required OEM to be unlocked... I am in a big depression now, somehow I fear that it's not fixable... But if some awesome soul could suggest a way to try out, that would be great! Thanks in advance.
Click to expand...
Click to collapse
If you can still get into recovery mode, maybe try sideloading the OTA again?
EDIT: Ninja'd by @znel52

Lughnasadh said:
If you can still get into recovery mode, maybe try sideloading the OTA again?
EDIT: Ninja'd by @znel52
Click to expand...
Click to collapse
Yeah I'm afraid since he did a factory reset debugging got disabled. Worth a shot though.

znel52 said:
Yeah I'm afraid since he did a factory reset debugging got disabled. Worth a shot though.
Click to expand...
Click to collapse
Oh crap, didn't think about that.

I know not everyone has access to a laptop but if you do always use that over a desktop. In the event of something like this you will have the battery power to carry you through.
I'm sorry this happened to you. The only option may be to send it to Google for repairs.

Sorry for your phone. I experienced this on a nexus 6 that didn't have USB debugging or OEM unlock enabled. I tried sideload, put the update package on the phone storage, try to update with Android recovery. Nothing worked. Stuff happens with phones. I hope you can get a new phone.
God bless.

Sorry to hear this. It seems that I need to open USB debugging option just in case for my Pixel 6, which finally arrived across the ocean after a month.

McNaccken said:
So I've got into a big trouble... I wanted to manually update my Pixel 6 Pro to the latest version using an official OTA (since the update wasn't available yet for my country and I wanted to stay up-to-date). It was all fine until it said 74 % done... and the power in my house has completely turned off... The device hasn't given me any error and rebooted, hower it got stuck on a Google logo. I rebooted to the recovery mode how it was suggested and did a clean factory reset, then rebooted again... and nothing changed, only the logo background has changed (white vs black). The BIGGEST problem is, the device OEM is NOT unlocked I tried entering the fastboot mode and flashing the device with a recovery image but it obviously didn't work as it required OEM to be unlocked... I am in a big depression now, somehow I fear that it's not fixable... But if some awesome soul could suggest a way to try out, that would be great! Thanks in advance.
Click to expand...
Click to collapse
Since the Repairtool has not been updated for your needs and considering that your device is not unlocked, your only option is to contact Google (/your seller). Maybe they can offer you an updated version of the tool (unlikely) or replace your device.
You just described, btw, my horror scenario when updating the BIOS of my PC. The lights going out, when doing a firmware update o.o
Oh my. I'm so sorry for you to have experienced that.

Ok, so I did a CMOS reset on my main PC, since it also failed to load after the lost power accident. Loaded my PC then just fine and tried connecting the phone again. Got to recovery mode and tried "adb devices" command... and it listed my Pixel device !! I tried the "adb sideload" command but it's stuck at 5% for at least 20-30 mins. The phone's last message is "Verifying update package". Not sure if it's a good sign, but afaik if USB debugging is off etc, you can not use adb commands. What would you guys suggest, try waiting for another 30 mins or unplug the phone, restart PC and try again? I am using USB-A to USB-C cable btw, maybe I could use USB-C to USB-C.

McNaccken said:
Ok, so I did a CMOS reset on my main PC, since it also failed to load after the lost power accident. Loaded my PC then just fine and tried connecting the phone again. Got to recovery mode and tried "adb devices" command... and it listed my Pixel device !! I tried the "adb sideload" command but it's stuck at 5% for at least 20-30 mins. The phone's last message is "Verifying update package". Not sure if it's a good sign, but afaik if USB debugging is off etc, you can not use adb commands. What would you guys suggest, try waiting for another 30 mins or unplug the phone, restart PC and try again? I am using USB-A to USB-C cable btw, maybe I could use USB-C to USB-C.
Click to expand...
Click to collapse
My apologies for asking the obvious - did you select "adb sideload" in the recovery menu ? At least I was blind enough to oversee that I need to select this option first
Can you boot into fastboot from the recovery ? If yes you could also try installing a factory image instead of the update package.... I read you cannot because your device is locked, but you can unlock in fastboot (you can always relock later).... only downside is that this will clear all data on the phone for sure....

McNaccken said:
So I've got into a big trouble... I wanted to manually update my Pixel 6 Pro to the latest version using an official OTA (since the update wasn't available yet for my country and I wanted to stay up-to-date). It was all fine until it said 74 % done... and the power in my house has completely turned off... The device hasn't given me any error and rebooted, hower it got stuck on a Google logo. I rebooted to the recovery mode how it was suggested and did a clean factory reset, then rebooted again... and nothing changed, only the logo background has changed (white vs black). The BIGGEST problem is, the device OEM is NOT unlocked I tried entering the fastboot mode and flashing the device with a recovery image but it obviously didn't work as it required OEM to be unlocked... I am in a big depression now, somehow I fear that it's not fixable... But if some awesome soul could suggest a way to try out, that would be great! Thanks in advance.
Click to expand...
Click to collapse
I had a similar issue with applying ota updates and have seen quite a few reports of users having trouble. Not sure what the deal is, but for some reason this phone seems super finicky with updates. Are you still in the return window? You may want to reach out to Google support or one of their "authorized repair shops".
For me, I ran the flash all bat, rebooted, got a message saying my device can't be trusted. So I rebooted, wiped data, rebooted again and got the same thing. So I rebooted, ran the flash all bat file again, rebooted phone, and screen went black and it never powered on again. Suspect circuit board may have fried some how. Anyways, long story short, contacted Google and had a replacement sent out with minimal hassle.

McNaccken said:
Ok, so I did a CMOS reset on my main PC, since it also failed to load after the lost power accident. Loaded my PC then just fine and tried connecting the phone again. Got to recovery mode and tried "adb devices" command... and it listed my Pixel device !! I tried the "adb sideload" command but it's stuck at 5% for at least 20-30 mins. The phone's last message is "Verifying update package". Not sure if it's a good sign, but afaik if USB debugging is off etc, you can not use adb commands. What would you guys suggest, try waiting for another 30 mins or unplug the phone, restart PC and try again? I am using USB-A to USB-C cable btw, maybe I could use USB-C to USB-C.
Click to expand...
Click to collapse
so you can get through this... you'll be fine. pick adb sideload and it will say waiting, then run the command.
you can also change slots at the bootloader menu or try running the unlock oem command to see if it will allow you to unlock..... not sure if you can change slots without unlocking bootloader. try different USB ports on your computer (and restart your computer just in case) along with using the latest platform tools (adb/fastboot) and USB driver directly from Google (not third party apps or websites.
download the OTA zip again (and just open and close it quickly to verify it isn't corrupt).. and also make sure you have 5-10GB of space free on your computer.
usually the boot slot is changed whenever an OTA is flashed. it will tell you what slot you're in at the bootloader menu (where it says fastboot and device state locked).
can you try holding power button (when it's not plugged in) and as soon as you see then Google logo, hold volume down. that will get you to safe mode. and as quickly as you can, enable "OEM Unlocking" - which will allow you to flash a full factory image.
sorry for this comment being all over the place. if you need help, just reply, and I'll be more methodical next time

s3axel said:
I read you cannot because your device is locked, but you can unlock in fastboot (you can always relock later).... only downside is that this will clear all data on the phone for sure....
Click to expand...
Click to collapse
I don't think the problem is that his bootloader is locked - it's unlocked, however, they factory reset the device which likely caused USB Debugging to be turned off, as it defaults to after a factory reset.
I'm so glad years ago I swore to use Uninterruptible Power Supplies (UPS) for all the PCs I build for myself or my wife.