Develop Bugs

[Q] Big problem with Evo!

Okay so yesterday I accidentally downloaded an old RUU and attempted to run it. I got an error in the middle of it and my phone was then stuck on a silver and black HTC screen. When I unplugged the USB it would take me to the Bootloader where it would then only say "RUU". Phone won't reboot or go into recovery. And one more small problem... The battery just died and wont charge. Would really appreciate some help. Thanks.

proskateronnie said:
Okay so yesterday I accidentally downloaded an old RUU and attempted to run it. I got an error in the middle of it and my phone was then stuck on a silver and black HTC screen. When I unplugged the USB it would take me to the Bootloader where it would then only say "RUU". Phone won't reboot or go into recovery. And one more small problem... The battery just died and wont charge. Would really appreciate some help. Thanks.
Click to expand...
Click to collapse
can I use " Okay so yesterday I accidentally downloaded an old RUU and attempted to run it." in my sig???
btw what hboot did you have before and what version ruu did you try and install?

Yes lmao.
Version 2.10, downloaded new one but having trouble doing it since battery died and not sure the phone will actually connect.

charge the battery some and see if the phone turns on, see if it will boot into recovery/rom etc

Ok, will try to charge battery, but from what i've tried, could not get in to recovery or get the bootloader to come up.

if you can not get anything on the screen and the phone won't mount the sdcard and adb won't connect, be prepared for a drive to the sprint store

NewZJ said:
can I use " Okay so yesterday I accidentally downloaded an old RUU and attempted to run it." in my sig???
btw what hboot did you have before and what version ruu did you try and install?
Click to expand...
Click to collapse
Lmao, about the sig comment
Sent via the Slayer of "ALL" phones the Evo 4g.

Hahahaha ^^^ Anyways new info did get the phone to get a charge. But now cannot get it to connect to computer.

I've actually came across this on the HTC Hero CDMA. i accidentally installed the wrong hero rom, cause at the time i was a noob to the android. an i tried to ruu but it failed. i kept doing all i could and playing with it. but where u ruu got half way through. and debug mode/recovery is reset by half way through.
only thing you can do is try to get into Hboot mode and try to see if u can connect to usb that way. then try to ruu

proskateronnie said:
Hahahaha ^^^ Anyways new info did get the phone to get a charge. But now cannot get it to connect to computer.
Click to expand...
Click to collapse
what does the phone do when you turn it on normal?
will it boot into bootloader?
do you have android sdk on your computer?

NewZJ said:
what does the phone do when you turn it on normal?
will it boot into bootloader?
do you have android sdk on your computer?
Click to expand...
Click to collapse
Just go's back to the "Silver and black HTC screen" and if I pull the USB (when in my computer) It will show me an option in the bootloader thats says RUU thats it. Can't do anything from there.

proskateronnie said:
Just go's back to the "Silver and black HTC screen" and if I pull the USB (when in my computer) It will show me an option in the bootloader thats says RUU thats it. Can't do anything from there.
Click to expand...
Click to collapse
If you can get into the bootloader your going to be just fine. Use the fastboot option in the bootloader to get your phone to connect to your computer, I have done this numerous times to unroot! You might have to reboot your computer just to refresh the connection etc and also reboot the bootloader a few times from that fastboot menu before running the RUU on the computer.

Yellowcard8992 said:
If you can get into the bootloader your going to be just fine. Use the fastboot option in the bootloader to get your phone to connect to your computer, I have done this numerous times to unroot! You might have to reboot your computer just to refresh the connection etc and also reboot the bootloader a few times from that fastboot menu before running the RUU on the computer.
Click to expand...
Click to collapse
Does not give me fastboot option. Like I said can't do anything from there.

So you can get into bootloader but it doesn't give you a fastboot option?

Yellowcard8992 said:
So you can get into bootloader but it doesn't give you a fastboot option?
Click to expand...
Click to collapse
Yeah. It only says RUU that is the only thing in the bootloader. But it does give me info on my Hboot version and stuff.

proskateronnie said:
Yeah. It only says RUU that is the only thing in the bootloader. But it does give me info on my Hboot version and stuff.
Click to expand...
Click to collapse
Okay, you have to get into the fastboot option and then run the RUU. Sorry I am having some trouble understanding because you are being a little vague. But to get into fastboot it has to be done before you run the RUU.

Yellowcard8992 said:
Okay, you have to get into the fastboot option and then run the RUU. Sorry I am having some trouble understanding because you are being a little vague. But to get into fastboot it has to be done before you run the RUU.
Click to expand...
Click to collapse
Don't worry about it. Anyways. I cannot get into bootloader at all unless I unplug the USB.

proskateronnie said:
Don't worry about it. Anyways. I cannot get into bootloader at all unless I unplug the USB.
Click to expand...
Click to collapse
So maybe your SD card is mounted or is the RUU running on your computer as we speak?

Don't think RUU is running but should I try pulling the SD?

proskateronnie said:
Don't think RUU is running but should I try pulling the SD?
Click to expand...
Click to collapse
No you shouldnt need to pull the SD. But I would try rebooting your computer and maybe your phone and get into the bootloader without it connected to your computer. Then connect it and go into fastboot and try what i described earlier.

HTC Desire HD not starting after unsuccessful rooting. please help. i am scared :/

i Couldn't find my problem in the forums im sorry if im repeating it, seriously... im sorry. its about my HTC Desire HD.
i was using Advanced Ace Hack Kit and everything was fine, i downloaded the ROM as the cmd asked me to, installed it, rebooted it twice accroding to the cmd, but then it said something about pressing power button once this step finishes, and thats when my phone got stuck, the volume keys werent working and neither was the power key, just then my power went out and everything crashed!!
now when i turn on my HTC DESIRE HD, it starts but stucks at "HTC" white splash screen; not even "quietly brilliant" comes up, it just stucks on the white screen with HTC... i dont know what to do, please help me someone? did i brick it? can it be repaired if i send it into HTC for repair? please help me!!
once again please guys im extremly sorry if im repeating a thread with this one, im new but i still searched for half an hour over the internet but with no vain. PLEASE REPLY!
its my first expensive phone, and its only been with me for 2 weeks, if this is ruined then my parents wont buy me any other phone.
*fingers-crossed*

Ok man don't panic, just re run the hack kit from the white screen. If it is not working just let me know....
Sent from my Inspire 4G using xda app-developers app

still nothing :/
glevitan said:
Ok man don't panic, just re run the hack kit from the white screen. If it is not working just let me know....
Sent from my Inspire 4G using xda app-developers app
Click to expand...
Click to collapse
tried that just now with the phone off and plugged in (constant orange light) and with the phone on and plugged in(white screen only, no LEDs) and the hack kit just shows the message :
***ERROR ERROR ERROR***
Phone not plugged in
OR
Driver not installed
OR
USB Debugging not enabled.
***ERROR ERROR ERROR***
the pressing vol up button+power button also doesnt do anything, and the screen sticks to the white part for hours :/

I can't help much since my phone is "away" in the insurance company.
But have tried reflash of RUU
Sent from my Desire HD using XDA Premium App

trying that :|
XDA_h3n said:
I can't help much since my phone is "away" in the insurance company.
But have tried reflash of RUU
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
im downloading the custom ROM i found a link to online, which said that i should just connected the switched off phone and run the executable file. fingers scrossed and hoping it works.
believe me buddy; im craving for the one X or even the one S.
but i will get that only if i make through with the DESIRE HD for at-least a year lol, doesn't seem quite possible as of the situation right now.

Ashjerk said:
tried that just now with the phone off and plugged in (constant orange light) and with the phone on and plugged in(white screen only, no LEDs) and the hack kit just shows the message :
***ERROR ERROR ERROR***
Phone not plugged in
OR
Driver not installed
OR
USB Debugging not enabled.
***ERROR ERROR ERROR***
the pressing vol up button+power button also doesnt do anything, and the screen sticks to the white part for hours :/
Click to expand...
Click to collapse
Ok...You Need to reflash the Ruu....do You know how to Get the Cid number

RE:
glevitan said:
Ok...You Need to reflash the Ruu....do You know how to Get the Cid number
Click to expand...
Click to collapse
sorry my network was down. back on now, i dont know what the CiD number is, so yeah i dont know how to get it. sorry :/

Ashjerk said:
sorry my network was down. back on now, i dont know what the CiD number is, so yeah i dont know how to get it. sorry :/
Click to expand...
Click to collapse
Man are u online?? I am sending u a PM...
---------- Post added at 03:31 AM ---------- Previous post was at 03:15 AM ----------
Ashjerk said:
tried that just now with the phone off and plugged in (constant orange light) and with the phone on and plugged in(white screen only, no LEDs) and the hack kit just shows the message :
***ERROR ERROR ERROR***
Phone not plugged in
OR
Driver not installed
OR
USB Debugging not enabled.
***ERROR ERROR ERROR***
the pressing vol up button+power button also doesnt do anything, and the screen sticks to the white part for hours :/
Click to expand...
Click to collapse
ok...if you press power + volume up you will never get to hboot...it's volume + power down.
To get the cid number, just boot in hboot, choose fastboot and plug the phone until you see fastboot usb in red. Then open a cmd in the pc and type fastboot getvar all. INFOcidnum is the information u need to get the ruu,

RE:
glevitan said:
Man are u online?? I am sending u a PM...
---------- Post added at 03:31 AM ---------- Previous post was at 03:15 AM ----------
ok...if you press power + volume up you will never get to hboot...it's volume + power down.
To get the cid number, just boot in hboot, choose fastboot and plug the phone until you see fastboot usb in red. Then open a cmd in the pc and type fastboot getvar all. INFOcidnum is the information u need to get the ruu,
Click to expand...
Click to collapse
yo if you're still there; i tried running the RUU executable file and after trying to read from my android phone, it says "error[170]: USB connection error".

Hopefully you get everything figured out dude

Ashjerk said:
yo if you're still there; i tried running the RUU executable file and after trying to read from my android phone, it says "error[170]: USB connection error".
Click to expand...
Click to collapse
Be patient, he'll sort things out.
@glevitan - lol..... second time I see you giving the instructions with the volume + power. You gotta remember it's volume down + power button
Sent from a dream.

I have exactly the same problem.
I cannot run a RUU as my computer won't detect the phone is connected via USB.
Any ideas? I've literally spent the past 4 hours trying to fix it.

klawsterfobik said:
I have exactly the same problem.
I cannot run a RUU as my computer won't detect the phone is connected via USB.
Any ideas? I've literally spent the past 4 hours trying to fix it.
Click to expand...
Click to collapse
Try installing the htc drivers/sync on your computer.
Sent from a dream.

Teichopsia said:
Try installing the htc drivers/sync on your computer.
Sent from a dream.
Click to expand...
Click to collapse
Done, but with no luck. The computer recognizes that the phone has been connected (it beeps and shows "Android Phone - Android Bootloader Interface") but I can't access it like a disk drive.
When I try to run the RUU I get an error saying it can't connect to the USB port...
** I un-installed, then re-installed HTC Sync and it picked the phone up and installed the drivers. So i'm doing the RUU at the moment and all seems to be running sweet. Its just finished and re-starting for the first time in a couple of hours! **
I'll try this rooting thing again eh!

Dont install HTC sync and disconnect ur computer from interner
klawsterfobik said:
Done, but with no luck. The computer recognizes that the phone has been connected (it beeps and shows "Android Phone - Android Bootloader Interface") but I can't access it like a disk drive.
When I try to run the RUU I get an error saying it can't connect to the USB port...
** I un-installed, then re-installed HTC Sync and it picked the phone up and installed the drivers. So i'm doing the RUU at the moment and all seems to be running sweet. Its just finished and re-starting for the first time in a couple of hours! **
I'll try this rooting thing again eh!
Click to expand...
Click to collapse
While using the ace hack dont install HTC sync use the drivers given in "*\tools\windrivers" folder
Most importantly Do not connect your computer to the internet As the driver manager checks for the latest drivers in microsoft website.. I was stuck there for a long time but nothing happened..
when ur not connected to internet it will take the drivers of "Android 1" which is already installed by installing "HTCDriver3.0.0.007.exe" from "*\tools\windrivers" folder.
Comin back the boot screen. Only HTC was visible on the screen after rooting but started the Ace hack again which removed this problem

You'll have a more successful ROOT if you use Ubuntu or a Ubuntu Live CD as I assume your using Windows right ? I used Ubuntu and rooted first time with no problems.

Thanks very

Ashjerk said:
i Couldn't find my problem in the forums im sorry if im repeating it, seriously... im sorry. its about my HTC Desire HD.
i was using Advanced Ace Hack Kit and everything was fine, i downloaded the ROM as the cmd asked me to, installed it, rebooted it twice accroding to the cmd, but then it said something about pressing power button once this step finishes, and thats when my phone got stuck, the volume keys werent working and neither was the power key, just then my power went out and everything crashed!!
now when i turn on my HTC DESIRE HD, it starts but stucks at "HTC" white splash screen; not even "quietly brilliant" comes up, it just stucks on the white screen with HTC... i dont know what to do, please help me someone? did i brick it? can it be repaired if i send it into HTC for repair? please help me!!
once again please guys im extremly sorry if im repeating a thread with this one, im new but i still searched for half an hour over the internet but with no vain. PLEASE REPLY!
its my first expensive phone, and its only been with me for 2 weeks, if this is ruined then my parents wont buy me any other phone.
*fingers-crossed*
Click to expand...
Click to collapse
i was in the exact same situation. All you have to do is connect your phone to your pc while its stuck on ''HTC'' boot screen. Wait for like a minute then use cmd and write 'adb reboot bootloader'. You should be able to fix it yourself from there
EDIT: doesnt work once bootloader is unlocked T_T im stuck on the white screen again...

IBeKay said:
i was in the exact same situation. All you have to do is connect your phone to your pc while its stuck on ''HTC'' boot screen. Wait for like a minute then use cmd and write 'adb reboot bootloader'. You should be able to fix it yourself from there
EDIT: doesnt work once bootloader is unlocked T_T im stuck on the white screen again...
Click to expand...
Click to collapse
Reflash a stock rooted rom and it's boot.img (found in the zip) and it will work.Or any custom.

Steam. said:
Reflash a stock rooted rom and it's boot.img (found in the zip) and it will work.Or any custom.
Click to expand...
Click to collapse
I would but there is no way of me getting to bootloader or recovery unless I force it into them, which I cant because I unlocked bootloader...

[Q] One x won't recognise computer.

Hi,
I want to root my One X (international) but I get stopped straight away because my phone won't connect to my computer. When I plug the USBs to both my computer and my phone nothing happens, except charging. There are no options given and the phone doesn't show up as a drive on the computer.
I've installed HTC Synch Manager, tried 4 USB cords, tried 3 computers, I've switched on USB Debugging.
The HOX is on Android 4.1.1
Any ideas? I've scoured many forums to no avail. I'd really like to try some custom roms.
Cheers,

Hello
I have the same problem with my HOX and no solution
Gr

Are you saying there is no solution or that you don't know of one? Can someone confirm that this is a known and unresolvable problem or should I keep looking for a solution?

I will have a try then.....the bootloader is untouched (locked) and the phone has never been detected by the pc before ?
Also interesteded in what OS you are running !

Do you have the latest HTC usb drivers installed? Have you checked in device manager to see if phone is visible? Latest version of HTC sync installed?
Sent from my HTC One X using xda app-developers app

Thanks. I bought the phone second hand from a young lass who had broken the screen (which I have replaced) so I presume the phone is standard and been updated to 4.1.1.
Some software information:
Software number 3.14.862.27
HTC SDK API level 4.63
Kernel version:3.1.10-g5ebf4bc [email protected]#1 SMP PREEMPT
I don't know if the phone has ever been detected by a computer before. I have installed the latest HTC Sych Manager on my Vista computer and no, the phone isn't detected in the device manager.
Although I have rooted my previous phone (Defy) and had kept up to date with the latest roms I am still fairly new at this.
Thanks for any help.

And the OS on your pc ?

Mr Hofs said:
And the OS on your pc ?
Click to expand...
Click to collapse
Vista

Drivers or not, when you plug it in it should be recognized as something. Or a HTC phone or a unknown device anyway....

Mr Hofs said:
Drivers or not, when you plug it in it should be recognized as something. Or a HTC phone or a unknown device anyway....
Click to expand...
Click to collapse
That's what I thought but I get nothing except charge. That is why I've tried a number of cables. I'm suspecting my micro USB socket is faulty. I've cleaned it and even checked how it's mounted. Solidly soldered so I'm checking every other avenue before replacing it as I have a dead Hox for spares.
Any idea if there is a way of rooting without a computer?

Nope ...not possible without a pc

Mr Hofs said:
Nope ...not possible without a pc
Click to expand...
Click to collapse
Ok. So is it your opinion that I'm stymied? Are there any other avenues I can try?
The phone is pretty good the way it is, I just like playing around with Roms etc. I'd also like to get rid of the Vodafone crap.

My guess something is broken somewhere in the usb connection....ofcourse, otherwise it would be recognized. But you figured that out already. Maybe a phone repair shop can take a quick peek at it ?
Otherwise your stuck on what you have now.

Well, it connects to the PC, but it only charges so I think this might be a software bug. Maybe you could try to root it and see if it fails at adb commands. My guess is that it will work. Just follow a rooting guide CAREFULLY and don't skip any steps.
Sent from my HTC One X using xda app-developers app

ViktorN said:
Well, it connects to the PC, but it only charges so I think this might be a software bug. Maybe you could try to root it and see if it fails at adb commands. My guess is that it will work. Just follow a rooting guide CAREFULLY and don't skip any steps.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
But he can't flash anything because there is no data connection, only power connection

First make sure usb debugging is on in settings. Maybe unlocking the bootloader and rooting will work. It's done from the fastboot usb screen where adb and fastboot commands should work. Give it a try before sending for repair.
Sent from my HTC One X using xda app-developers app

AW: [Q] One x won't recognise computer.
Einwod said:
First make sure usb debugging is on in settings. Maybe unlocking the bootloader and rooting will work. It's done from the fastboot usb screen where adb and fastboot commands should work. Give it a try before sending for repair.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I definitely agree with his idea, but the first thing you should do is completely restore you're one x.
Then check in hboot, that's power volume down wether the device is locked or relocked.
After that get the latest drivers, connect your hox in fastboot and try to unlock your device via HTC devs.com
Good Luck.
P.S. tell us what happens, we might find a solution all together
Sent from my HTC One X using xda app-developers app

psyko93 said:
I definitely agree with his idea, but the first thing you should do is completely restore you're one x.
Then check in hboot, that's power volume down wether the device is locked or relocked.
After that get the latest drivers, connect your hox in fastboot and try to unlock your device via HTC devs.com
Good Luck.
P.S. tell us what happens, we might find a solution all together
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Thanks for this. You have given me some hope.
I've done a factory reset, checked that Debugging is on and checked in Hboot, it says *** LOCKED ***
I've connected the HOX to my Vista computer in which I've installed HTC Synch Manager. I presume this installs the latest drivers?
My Hox is still not recognised by the computer. When I request the identifier token it gets stuck on < Waiting for device >
Have I followed your instructions correctly?
Edit 1: Just to be sure I repeated the procedure on my desktop computer which is also running Vista. Same results.
Is there any way of extracting the identifier token within the phone?
Edit 2: I pulled the motherboard out and checked the micro USB port with a microscope. Pretty grotty inside so I cleaned, tightened and checked it. All clean but still no computer connection.
M

Any news/luck? Would like to know the outcome for this. :banghead:
Sent from my HTC One X using xda app-developers app

AW: [Q] One x won't recognise computer.
Okay, so far so good. What you can do next is: go to settings/apps/all apps
and search for the pc-sync app and check if its enabled.
Next thing, try this special debugging driver http://blog.gambliser.com/dl/?p=144.
Good luck
Sent from my HTC One X using xda app-developers app

Installed TWRP and battery died!!

So i was planning on rooting my htc one x, it wouldn't have been the first phone i root. But for some reason after fastboot unlocking and everything. The phone said:
***TAMPERED***
Fastboot unlocked
Which is a good sign because it meant i was doing things right (i suppose) but for some reason every time i would try to put it in recovery so i could get the TWRP menu it would just reboot. I said to myself "oh its 3am ill go to sleep and do it tomorrow" bad idea. Battery died overnight and now it wont turn on even if i put it to charge. I tried connecting it to the computer and the pc tries to install some drivers, it says
QHSUSB_DLOAD "X"No Driver Found
Unidentified Device "X" Device Unpluged
Any idea on what i can do to get my phone to work again?

Download the latest HTC drivers:
http://forum.xda-developers.com/showthread.php?t=2217396
Find a USB2.0 port and connect your phone and try to get it into fastboot and run the charging script for a long time:
http://forum.xda-developers.com/showthread.php?t=1658084
Good luck!
Edit: Sure you have a One X? Next time try one of the other available recoveries.

I'm thinking you have the one XL, i havent seen tegra 3 htc's with tampered on bootloader
Sent from my HTC One X using xda app-developers app

Stefan0vic said:
I'm thinking you have the one XL, i havent seen tegra 3 htc's with tampered on bootloader
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I have!
Hope you managed to charge your phone using the script.
To make sure you have a One X, could you post the result of the command "fastboot getvar all" but make sure you mask your serial and IMEI.

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.