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

Galaxy Nexus - Several serious problems

Hello everybody.
First I want to say is that I'm sorry for my english. It's not my native language.
And now lets go to my problem:
It started like few days ago when I updated my phone to the newest franco.kernel. After flashing that, my phone began to behave strangely and it didn't want to go tho nexus logo. It just always crashed.
So I decided to plug my phone to PC for flashing stock kernel or older version and what happened.. PC didn't recognize that phone is connected. I tried use Universal Naked Driver, OMAPflash (its just saying "waiting for device") and it still didnt want to work. I tried to plug it in notebook and it didnt work too. Well so I could still go to recovery mode, because I'm using TWRP. I did factory reset and my phone worked again even plug in to PC still hasn't worked.
And today I decided to try flash stock kernel with boot.img via TWRP. Of course it didnt work, so I did a stupid thing and flashed older version of franco.kernel (I don't know why I did that.. Maybe I was thinking it will fix my problem with USB, because it started with flashing the newest version..eh) and then my phone can't go tho Google Logo. Well so I did factory reset again + system reset (really clever) via TWRP well then it didnt work of course (because of no ROM, system), so I remembered that I did nandroid backup before my first factory reset. So I did a restore of backup, but it still stuck at Google Logo and everything I can do now is:
Go to recovery mode (TWRP) or Odin mode (which is just saying "Downloading...")
So I can't flash my phone tho PC, cause it doesn't recognize it is plugged in and I really don't know, what can I do now. I also though that USB cable should be "bad", because I didn't use it too much (like few months ago) so I would buy new one, but I don't think it is that problem, because it worked last time when I rooted my phone with PC etc.(but as I said.. few months ago)
Well.. I hope there will be solution for that.
Thanks in advance for reply.

You can read this. The entire first post. And maybe a couple more.
http://forum.xda-developers.com/showthread.php?t=1626895
Sent from my Nexus

The problem is that my PC doesn't recognize it is connected (when I install drivers, there is "yellow triangle"). It is charging while its connected to PC, but its not working as USB device. If I could see my phone on PC, it could fix my problem and I could return to stock.
Phone is working, it can be charged, it works in recovery-mode (with TWRP) and odin mode, but it cant go tho google logo and PC doesn't recognize it is connected. That's the current status.
+ It's rooted and unlocked....So the warranty is breached and If I will send it back to shop for repair, I will pay a lot of money :-/

Tordiato said:
The problem is that my PC doesn't recognize it is connected (when I install drivers, there is "yellow triangle"). It is charging while its connected to PC, but its not working as USB device. If I could see my phone on PC, it could fix my problem and I could return to stock.
Phone is working, it can be charged, it works in recovery-mode (with TWRP) and odin mode, but it cant go tho google logo and PC doesn't recognize it is connected. That's the current status.
+ It's rooted and unlocked....So the warranty is breached and If I will send it back to shop for repair, I will pay a lot of money :-/
Click to expand...
Click to collapse
Dude, just read the thread. Uninstall all drivers and reboot before doing anything else.
Sent from my Nexus

Tordiato said:
I also though that USB cable should be "bad", because I didn't use it too much (like few months ago) so I would buy new one, but I don't think it is that problem, because it worked last time when I rooted my phone with PC etc.(but as I said.. few months ago)
Click to expand...
Click to collapse
I bought a new USB cable today (Samsung APCBU10) and it works now! So I can flash it back to stock Problem solved.
//Thanks for the help anyway bk201doesntexist

GT-N5100 not charging

Sorry guys, noob here.
Started with the USB not being promptly recognized by my PC, but after some reconnections it worked.
So, one day ago, I installed TWRP via heimdall suite and flashed the last stable Cyanogenmod 12.1 for GT-N5100, following all the instructions. For my surprise, the tablet doesn't charge with any type of source. Tried lots of cables and adapters and nothing.
I returned to stock ROM, 4.4.2, but the same problem remains.
What I found is that somehow it start recharging when plugged for some time, but only some few %, and the tablet is readily recognized via USB when on download mode. So, it's not a hardware issue.
Someone, please help me.

crfiladelfo said:
Sorry guys, noob here.
Started with the USB not being promptly recognized by my PC, but after some reconnections it worked.
So, one day ago, I installed TWRP via heimdall suite and flashed the last stable Cyanogenmod 12.1 for GT-N5100, following all the instructions. For my surprise, the tablet doesn't charge with any type of source. Tried lots of cables and adapters and nothing.
I returned to stock ROM, 4.4.2, but the same problem remains.
What I found is that somehow it start recharging when plugged for some time, but only some few %, and the tablet is readily recognized via USB when on download mode. So, it's not a hardware issue.
Someone, please help me.
Click to expand...
Click to collapse
I think you have system corruption from kernels. I have experienced various issues around power with the note 8.0... all of which were from various kernel loads effecting low level device operation. Unfortunately there is no reset button or easy access to clean out the corruption.
You can remove the battery connection and wait a few minutes. Then connect and go into download mode and flash a stock rom. Then boot to setup and finalize your installation. Check and see if it will charge and properly function with power off and reboot options from the power menu.
If so flash a recovery, and wipe completly and flash your ROM of choice. If you choose a custom kernel outside of the ROM package, that may be done on top of the ROM load, to assist in a clean and trouble free ROM install.

gooberdude said:
I think you have system corruption from kernels. I have experienced various issues around power with the note 8.0... all of which were from various kernel loads effecting low level device operation. Unfortunately there is no reset button or easy access to clean out the corruption.
You can remove the battery connection and wait a few minutes. Then connect and go into download mode and flash a stock rom. Then boot to setup and finalize your installation. Check and see if it will charge and properly function with power off and reboot options from the power menu.
If so flash a recovery, and wipe completly and flash your ROM of choice. If you choose a custom kernel outside of the ROM package, that may be done on top of the ROM load, to assist in a clean and trouble free ROM install.
Click to expand...
Click to collapse
Tried exactly what you said: Opened it, removed the battery for a while, flashed the stock rom via Odin and factory reseted. Nothing changes.
Doesn't charge anyway. It's recognized when in download mode, though.
With 16% battery right now. If it drop to 0%, that means gameover? Or can i charge while on download mode (odin mode)?
Can't I flash TWRP and then install a custom kernel from there?
Thanks, dude.

I use Philz Recovery, as had issues with TWRP long ago and gave up once I tried Philz.
I would have done a full wipe and reset in philz.
You can charge in Philz and in Download mode, once you are able to get the phone to reset the power mode by the kernel flash.
One thing I think may be your issue... the USB connector may be bad. All you need is the voltage pin to go bad. Data will operate without voltage for powering the device.
Removing the USB board and lightly compress the top and bottom of the connectors frame, so that your cable end fits snug. Had to do that a few years ago when a cable end stretched it out after a few uses. Did not go back to using it again once I corrected the fit issue.

gooberdude said:
I use Philz Recovery, as had issues with TWRP long ago and gave up once I tried Philz.
I would have done a full wipe and reset in philz.
You can charge in Philz and in Download mode, once you are able to get the phone to reset the power mode by the kernel flash.
One thing I think may be your issue... the USB connector may be bad. All you need is the voltage pin to go bad. Data will operate without voltage for powering the device.
Removing the USB board and lightly compress the top and bottom of the connectors frame, so that your cable end fits snug. Had to do that a few years ago when a cable end stretched it out after a few uses. Did not go back to using it again once I corrected the fit issue.
Click to expand...
Click to collapse
Tried also, without response.
It really doesn't seem to be a hardware problem.
Right now I plugged into the charger and there you go: Charging!!
I don't know what I did different, but it's working, at least for a while. Probably it will not fully charge, but ok.
I remembered that, prior to flashing TWRP+CM12.1, I got constant pop-ups about Power Sharing. Reading some forums, some guys experienced the same problem with this feature and them their phones stopped charging. Some reported that a factory reset solved, which is not my case.
I will keep posting what I did and if I find something that solves, it may help someone who's stuck with the same error.
Anyway, thanks so much, gooberdude.
(And sorry for my lame grammar.. writing is much harder than reading and listening english)

having same issue tab not charging only showing in odin mode.. i even replace the usb port part still same situation.. going to flash stock rom hope this will work for me .. i am using cm13 on twrp 3.0..

no luck... even after flashing stock 4.4.2 tab is not charging not even in download mode... any suggestion please hlep..!!!

crfiladelfo said:
Sorry guys, noob here.
Started with the USB not being promptly recognized by my PC, but after some reconnections it worked.
So, one day ago, I installed TWRP via heimdall suite and flashed the last stable Cyanogenmod 12.1 for GT-N5100, following all the instructions. For my surprise, the tablet doesn't charge with any type of source. Tried lots of cables and adapters and nothing.
I returned to stock ROM, 4.4.2, but the same problem remains.
What I found is that somehow it start recharging when plugged for some time, but only some few %, and the tablet is readily recognized via USB when on download mode. So, it's not a hardware issue.
Someone, please help me.
Click to expand...
Click to collapse
Hi Noob,
Faced the same issue on N5100. Tries several fix but at last just flashed boefello kernel and the issue is fixed.

Kannanunnikrishnan said:
Hi Noob,
Faced the same issue on N5100. Tries several fix but at last just flashed boefello kernel and the issue is fixed.
Click to expand...
Click to collapse
Hello
My N5100 faces the same problem of charging as this thread.
Could you put in details about your status of N5100
- Your regional model: Ex: EU, America, Asia....?
- Your Tab is working fine until today, doesnt it?
- If it's working fine , what was ROM you are using currently?
- What did Recovery you use to flash ROM?
Thank you so much

Hello my tab has a charging problem too it started with not being recognised when I plug to my computer. When I plug to a power source it charges sometimes other times it just doesn't and I'm certain the charger isn't the problem

Sony Ericsson Play R800AT Boot loop.

So, here's the deal with this phone. It's sat untouched for many many years. The original owner can't remember why she got rid of it (family friend). So I volunteered to take it, and turn it into an emulator device. However, it was made clear as to why she got rid of it. The phone is stuck in a gnarly boot loop. The boot loop is, Sony Ericsson screen lit up, and then goes to an unlit version of the logo. After a while, the phone will restart repeat. The phone will get into flash mode (green light) and will not continue the loop but stays on the unlit version of Sony Ericcson. I've gotten it into fastboot once, maybe twice, but I can't remember exactly how I did it (holding menu doesn't work)
I have installed the drivers for the phone, however, the phone is listed as:
E:\
Device Type: Portal Device
Manufacturer: SEMC
Location: on Volume
The drivers that it is apparently using is wpdfs.inf
Things I have tried to correct this issue.
-The Xperia app (tells me to enter flashmode in its own way and never does anything after)
-Flashing using "FlashTool"
It sees a phone but just says.
"19/025/2018 22:25:46 - INFO - Device connected with USB debugging off
19/025/2018 22:25:46 - INFO - For 2011 devices line, be sure you are not in MTP mode"
I've attempted using a fastboot method but nothing substantial as fastboot rarely happens.
Accessing the device through ADB (ADB shows not devices connected
Accessing the device through FastBoot (FastBoot shows "waiting for devices")
I have crawled through dozens of pages worth of information, similar questions, similar problems and come up short. Any advice would be super helpful.
Will provide images, and further information if requested. Thanks for your time.

I'm not familiar with the at version. Also maybe its already stated in the post and I miss it, did u try flashmode on flashtools and flash stock TFT?this is the first thing you wanna do in case of problems. For fastboot if I remember correctly you have to push search button and not the menu button, but I haven't my xplay with me.

inaroom said:
I'm not familiar with the at version. Also maybe its already stated in the post and I miss it, did u try flashmode on flashtools and flash stock TFT?this is the first thing you wanna do in case of problems. For fastboot if I remember correctly you have to push search button and not the menu button, but I haven't my xplay with me.
Click to expand...
Click to collapse
Hey, I did try flashing the stock firmware, the version is the AT&T version from the US. The problem with attempting to flash is Flashtool doesn't detect the phone. It sees that there's a phone plugged in, but flashing is impossible because it can't find the phone. I figured it must've been a driver issue, so I scoured the web to find drivers but only could find the 800a drivers, so I went ahead and attempted those, but not to no avail.
My next attempt to bring out Windows 7 and attempt to install the drivers on Windows 7, instead of 10. Just been a bit slow, and feeling a bit dejected on the whole project.

Disenfranchised said:
Hey, I did try flashing the stock firmware, the version is the AT&T version from the US. The problem with attempting to flash is Flashtool doesn't detect the phone. It sees that there's a phone plugged in, but flashing is impossible because it can't find the phone. I figured it must've been a driver issue, so I scoured the web to find drivers but only could find the 800a drivers, so I went ahead and attempted those, but not to no avail.
My next attempt to bring out Windows 7 and attempt to install the drivers on Windows 7, instead of 10. Just been a bit slow, and feeling a bit dejected on the whole project.
Click to expand...
Click to collapse
to install flashtools drivers in win 10 you need to disable uac but maybe you already did that. make sure the adb drivers are fully and correctly installe. have you tried flashing a kernel in fastboot mode by pushing the search button? also i would try to install r800i or r800a drivers. then i would suggest to make a little bit of search (i know you already did a lot...) to ensure that you can flash r800i or r800a firmware on your r800at and also try that route. i´m sorry i can´t help you more but i´m in europe and never worked on a r800at..

Hey, dont worry about it. This post is basically a hail mary for a phone that super old. I haven't tried flashing in fast boot because I have only ever gotten in fast boot once or twice. Fast boot is menu key correct? Cause I see conflict information all over the place.

i´m pretty sure it´s the search button for fastboot mode

Do you need a new battery?
Hi Disenfranchised,
I recently got out my old r800i GSM which was regularly being flung across the lounge by my kids, attached a charging cable and I had exactly the same boot loop issues as yours, but only as long as the phone was being charged. I ended up biting the bullet and buying a new battery and the phone started up. I ended up flashing Gin2Kat and it has been working well other than occasionally reverting back to the same behaviour for about an hour if the battery was completely discharged. The funny thing is when i finally manage to boot the phone at the right point during the boot loop cycle, the battery is only at 2%, meaning during the boot loop the battery is charging for maybe only a fraction of the on-off cycle.
It's a bit of an outlay (my battery was about GBP £10 - ebay). I now play SNES games on this every day during my commute. There are a few quibbles - the audio out port doesn't work (bluetooth audio works) and I get a wifi error but I ended up using Gin2Kat's apk installer to install my apps from micro-sd.
Anyway, it's a bit of a risk but see how it goes.
Fuzzy

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.