Database Develop

Is my USB port busted?

Tried connecting my kaiser to 2 different pc's and it won't get detected. The device will charge but activesync won't pick it up. Also its not listed in device manager! I tried disabling/renabling advanced network functionality as well has soft reset the device several times. I'm on the verge of hard reseting BUT when i put my device in bootloader mode it only says serial.. will not say USB as its supposed to
any help would be appreciated.. i'm on death v4 rom btw.
thanks in advance!

fone_fanatic said:
The device will charge but activesync won't pick it up.
Click to expand...
Click to collapse
Can you get an activesync connection via Bluetooth? When you inspect the extUSB connection can you see anything which looks wrong (such as a wire sticking out/in more than the others? What happened preceding this problem?
If you hard reset the device I don't see the relevance of the bootloader. It'll just restore the original image from where it's tucked away in the devices ROM. If it was working fine straight after you installed the ROM thats on it now and doesn't work after a hard restore then that points towards a hardware failure. If you have to go down the path of restoring to a different (original) ROM for returning purposes, there are ways of doing this with a microSD card - although I've not tried. I think the wiki would help there.

bluetooth activesync is working, i did a hard reset and nothing. Flashed to romeos via microsd and now its acting all strange.
After it completed the flash from microsd, i soft reset the device and it rebooted backinto bootloader.. i removed the microsd and soft reset several times and it kept going to bootloader. I attempted to hard reset as well and same thing, would go to bootloader. Removed the battery for a couple minutes and still same thing. Plugged it into USB with it off and it turn on by itself and go straight to bootloader. Unplugged the USB cable, took out the battery and put it back in, then plug the USB cable back in and this time the orange light came on as if charging and it finally booted up. The above has happened to me previously on my hermes but that was when the battery was extremely low, my battery level is currently at 97%!
now its booted into the freshly flashed rom and still same thing... charging but not being recognized by the PC... i've checked the usb port on the device and everything looks fine.
I'm lost at what to do now....

This might be a stupid reply but I had the same problem. My cable was busted so you could try another cable.

I am in the same situation here
Tried it with 3 different PCs with 3 different cables.
It's charging, Active sync pickes it up and trying to connect but fails to connect.
The only think I can come up with, I used new charger in the car. May be it killed the port
Is there any way to find out for sure?

i tried 2 cables with 2 different pcs... its only charging it and the computer won't detect the device at all. Nothing under usb in device manager.. even in bootloader, it only says serial not usb. I've downgraded to a shipped AT&T rom and Radio through the storage card but i still need to downgrade the SPL before i attempt to get a warranty exchange. IS that possible to do with through microsd yet?

I'm having the same issue. The usb port charges the phone fine with the USB cable, but teh computer does not detect the device. I also tried the headphones and they work fine as well. Help!
Update: I just tried a different usb cable, and now the computer recognizes the device, but as an unknown device.!!!!!

fone_fanatic said:
bluetooth activesync is working, i did a hard reset and nothing. Flashed to romeos via microsd and now its acting all strange.
After it completed the flash from microsd, i soft reset the device and it rebooted backinto bootloader.. i removed the microsd and soft reset several times and it kept going to bootloader. I attempted to hard reset as well and same thing, would go to bootloader. Removed the battery for a couple minutes and still same thing. Plugged it into USB with it off and it turn on by itself and go straight to bootloader. Unplugged the USB cable, took out the battery and put it back in, then plug the USB cable back in and this time the orange light came on as if charging and it finally booted up. The above has happened to me previously on my hermes but that was when the battery was extremely low, my battery level is currently at 97%!
now its booted into the freshly flashed rom and still same thing... charging but not being recognized by the PC... i've checked the usb port on the device and everything looks fine.
I'm lost at what to do now....
Click to expand...
Click to collapse
Have you tried these steps?
http://www.microsoft.com/windowsmobile/en-us/help/synchronize/activesync-usb.mspx

ajay6780 said:
Have you tried these steps?
http://www.microsoft.com/windowsmobile/en-us/help/synchronize/activesync-usb.mspx
Click to expand...
Click to collapse
Thanks for that suggestion but still no dice
The computer isn't detecting the device at all! Usually when a usb device is plugged in you can go to device manager and look under USB and see it there, but its not showing up. I've scanned for hardware changes several times and nothing.
I've now tried on 3 different computers (2 pc's and 1 mac) with 2 different USB-MiniUSB cables and nothing!!
i guess i'll just go to the at&t device support center tomorrow and hope they'll replace it on the spot and notice that i've changed the SPL...

can i ask for the people that are having this problem to do the following.
With your device unplugged from the PC open device manager. (Right click My Computer -> Properties -> Hardware (3rd tab) -> Device manager) Then expand the last tab (Universal Serial Bus Controller) and plug in your device.. if it doesn't show up then click actions -> scan for hardware changes..
I just want to make sure if your computer is detecting your device or not..

just an update with my situation. i went into the att device service center today and told them my problem... the guy behind the counter had no clue what he was doing. he just looked at it like a monkey for minutes then swapped it out for a new one. no questions asked even though it was hard spl'd, cid unlocked, and sim unlocked.
but now this device's vibration is really weak and i lost my invsishield protection on the front (kept the battery cover and my ppctechs scren protector)

Busted? or just won't work
Hi all,
I have been coming to these forums for a little while and only posted a couple of times. I felt this was important. I was having the same problem. Tried the cables, resets, ROM changes the works. I have had my at&t tilt htc 8925 for 36 days when I reported the problem to them. But it actually started about 10 days before. At&t tech support was very rude and accusatory when it came to them "helping" me. I, like probably all owners of a phone like this treat it like gold. It is very important to me. So when I contacted tech support and was told it was probably abuse or I had "buyers remorse" (I don't want to return the phone I just want it fixed!?)
The best they can do and they do not budge on this is for me to return the phone for an exchange. BUT, and this is a BIG AT&T but, the phone they exchange it with is refurbished. Something someone has returned. I do not want a phone that has been returned. I want mine fixed. "This is my phone, there are many like it but this one is mine" Know what I mean? When I bought the phone the guarantee was "we'll just replace it with a new phone" and I like 1000's of others did not ask if that "new phone" was refurbished. It is. Now advocates will tell you as they did me, refurbished is actually BETTER than new. Huh? Then why aren't all phones sold refurbished ones? And if they are so great, take mine back, give me one of those "crappy" new phones and give mine to someone who wants a sweet refurb. I am outraged by the whole mess.
I have searched forums and complaint sites. The bad usb port problem is NOT an isolated incident. There are a lot of people with the same "it charges but won't sync" problem. This is a known problem they refuse to address. Their stand, send in for refurb.
Personally I would like to see a recall fix class action against at&t. It can be fixed but they just don't want too. I thought I would be relatively safe buying for a huge company. They spend millions on advertising to simply leave their customers twisting in the wind after 30 days. Very bad business.
That's the rant. So I decided that if the warranty was useless anyway I'd take a shot at it myself before sending out for repair myself. There is a place in California PPC Tech http://www.pocketpctechs.com/main.asp?area=home that will fix the usb for $79 and ship it back to you in a few days. They seem to be reputable and a lot of people are opting to fix this problem themselves.
How did I fix mine? by altering the mini usb end of the sync cable. I tried other cables and connectors but I think it has something to do with the contact points. The only way mine would work was if I plugged it in, wiggled it slowly and with a little bit of pressure at times, around until the screen brightens. That means it has made a connection, then don't move. Hold very still. It took both my hands. Wait for what seems like 2 mins and it would start to sync. Based on this. my repair (before I send it to California for repair, which I may end up doing anyway) is make sure the plug on the phone is straight and not damaged. If you can get the phone to sync this way you may be able to crimp the mini end of the usb very very slightly to make the connection you are manually doing by wiggling it around. It took a lot of small tweaking but it now syncs about 29 out of 30 times. That's about as good as it gets.
So good luck to us all. If you can't get it to work yourself send it out west to PPC Tech. In this economy the phone companies like at&t better start getting their customer service back on track before they have no customers to service, It has happened to the biggest before. Wake up AT&T! The days of the business model of massive turnover and new signups is coming to an end as people tighten their belts. Treating current and future users poorly is a sure fire way to put yourself out of business.

here is my gift to you all..
http://forum.xda-developers.com/showthread.php?t=362679
read this post and check EVERY SINGLE LINK in the first post...i had this issue and i ended bending my usb plug every which way until finally i broke the plastic seperator off and in turn smashing the second pin from the left on the top off (the one in charge of activesync) over and over until it broke...i didnt really care i could still flash by sd but then i smashed the + power pin and so i was on the phone with att for many many hours explaining to them that its a known issue to users but not to the company and they finally sent me a replacement..i should have just searched my butt off before trying to deal with a problem/fox it myself (yes i dissasembled it and soldered the pin back on and it broke off multiple times causing me to dissasemble it many many times and smashing it again and i ended up getting alcohol on the water damage void pad which i replaced) learn from me...if you ever have ANY problems that are significant..dont try fixing JUST GET A REPLACEMENT...who cares if its a refurb..if the refurb sucks then send it back until they send you a new kit...after 5 returns you get a new kit soo just keep sendin back them refurbs until your happy

oh and to make it easy on yourself because if you tell att you have a usb problem its NOT covered under warranty and will take you many many hours like me to convince them otherwise (which someone eventually will understand because certain people ARE familiar with this problem at ATT it just depends who you get and how many times youve been elevated in support)..what you need to do is IF YOU CAN return your spl back to stock (if you manage to get a long enough connection with activesync) but if not dont worry too much att doesnt really check spl just that you have the shipped rom on there so load the shipped rom (found on here) on your sd and flash back and just make up some excuse that it isnt working right and youl get a replacement or if you can get the spl revrted jus throw your device in bootloader by a failed flash (pull the usb out during flash) and say its stuck in the funny colored screen lol

jaysjob, i've been dealing with ppctechs for a long time (probably since '03-'04) they're very reputable and highly recommended. They actually got the contract to be the authorized repair center for I-Mate about a year ago.
But why would you pay $79 for something where u can get a complete replacement? Yah it might be a refurb but my device that i turned in was all scratched up from drops.. the images on the start, ie, and messaging buttons by the d-pad had scratched off.. and now the device i got looks brand new (i actually think it is a new one but i never asked if it was a refurb or not)
pazookie, what your saying is true.. always take advantage of the warranty if you have it. If you dont and you want to repair it yourself, know what your doing! I'm very handy and have done many lcd replacements and other various repairs on cellphones (nokias, HTCs, sony ericsson, samsung, motorola, u name it!)
My little brother has the n82 and he bought the black case, I told him to wait for me and i'd help him do it but he got impatient and he thought it was gonna be a simple swap. He ended up breaking his LCD doing it which set him back $80!
anyways i'm happy now with a new device but i'm gonna go back tomorrow and get it replaced again because the vibrate is extremely weak!

fone_fanatic said:
jaysjob, i've been dealing with ppctechs for a long time (probably since '03-'04) they're very reputable and highly recommended. They actually got the contract to be the authorized repair center for I-Mate about a year ago.
But why would you pay $79 for something where u can get a complete replacement? Yah it might be a refurb but my device that i turned in was all scratched up from drops.. the images on the start, ie, and messaging buttons by the d-pad had scratched off.. and now the device i got looks brand new (i actually think it is a new one but i never asked if it was a refurb or not)
pazookie, what your saying is true.. always take advantage of the warranty if you have it. If you dont and you want to repair it yourself, know what your doing! I'm very handy and have done many lcd replacements and other various repairs on cellphones (Niki's, HTCs, sony ericsson, samsung, motorola, u name it!)
My little brother has the n82 and he bought the black case, I told him to wait for me and i'd help him do it but he got impatient and he thought it was gonna be a simple swap. He ended up breaking his LCD doing it which set him back $80!
anyways i'm happy now with a new device but i'm gonna go back tomorrow and get it replaced again because the vibrate is extremely weak!
Click to expand...
Click to collapse
Hi fone
Thanks for the reply.
Yes, I agree with you. If the phone has something else that is messed up like you were saying a scratched screen or buttons. It's just that I am as careful as I can be to keep the phone in nice condition just to send it back for maybe one that someone didn't take the same care of.
Mine works good now. I think it has something to do with when I crimped the cable end. It make a tighter fit. I think that may be the key to mine and others problems. For sure it is becoming more and more clear that there is a design flaw whether att wants to acknowledge it or not.
Thanks for your input about PPC too. If I do end up having to fix it that's probably the way I'll go if that is still the only thing wrong. Otherwise it's in for the warranty as you suggested. I KNOW I'm not that smart.

Im having this same issue and it is definately not a cable problem.

tayloryork said:
Im having this same issue and it is definately not a cable problem.
Click to expand...
Click to collapse
if u think its a hardware problem then take it to a service center. The guys there just follow step by step guides on how to diagnose phone issues. For me he saw a crack in the usb jack on my device and just replaced it. If you send it in to HTC i think theres a higher risk of them figuring outu the device is hard spl'd and wont honor your warranty.

tayloryork said:
Im having this same issue and it is definately not a cable problem.
Click to expand...
Click to collapse
taylor, I'm not saying it is a cable problem. I am saying it is a hardware port problem. I "fixed" mine, probably temporarily, by crimping my usb cord so that it holds more firmly in the port. I did say if you have the same problem and you use the same test I did ie: move it slightly, Gently, not like others I have heard stories of where they ram it from side to side until it snaps off, that you might be able to do what I did. I thought others with the same problem might be able to use this workaround until at&t figures out it is not an isolated incident with thousands of people having the same problem thats all. Hope this helps.
jj

I had a similar problem. Phone would charge fine, but windows didnt even recognise anything was plugged in. Interestingly the bootloader changed to USB when the cable was connected, and Serial when unplugged.
As it turns out (thanks Flying Kiwi for suggesting the obvious I had overlooked) the middle top pin was recessed too much into the plastic guide, so I stabbed it a bit with a scapel and all is well.
So it seems that the Serial/USB section of the bootloader cant even be trusted.

Regarding a possibly bricked phone.

Two nights ago I was watching a video through the YouTube app when suddenly the screen froze up. When it stayed unresponsive for 5 minutes or so, I shut it off by holding the power button down, which seemed to have worked as intended. After that it's become absolutely unresponsive. It will not boot up or turn on whatsoever, nor will the LED light up when plugged into a wall to charge.
The phone was running CM7 and had CWM as recovery, but I'm absolutely stumped as to why it fails to boot up. Has my phone decided to spontaneously brick itself? Is it potentially a hardware fault? Any suggestions would be appreciated. I'll be taking it to a repair center tomorrow, since I've really no choice as of right now.

Yea not really much else you can do besides taking it in for repairs. Maybe remove battery for an hour, although from the sounds of it, it won't do anything.

Nonverbose said:
Yea not really much else you can do besides taking it in for repairs. Maybe remove battery for an hour, although from the sounds of it, it won't do anything.
Click to expand...
Click to collapse
Doesn't seem to work. However an interesting observation, when plugged into the PC, it's detected as QHSUSB_DLOAD. Is it possible my phone's entered some sort of low-level mode? And if that's the case, is there any way to reverse this? I say I held the power button down and it shut off but I may have hit the volume keys in my panic.
So yes, I remain hopeful there's some miracle that will let me get out of this mess.

vr90 said:
Doesn't seem to work. However an interesting observation, when plugged into the PC, it's detected as QHSUSB_DLOAD. Is it possible my phone's entered some sort of low-level mode? And if that's the case, is there any way to reverse this? I say I held the power button down and it shut off but I may have hit the volume keys in my panic.
So yes, I remain hopeful there's some miracle that will let me get out of this mess.
Click to expand...
Click to collapse
This interests me too, I'll be researching all the info I can find, although the first search on qhsusb_dload has come up with a lot of questions and no answers as yet.
Many threads have blamed partitioning the sdcard in cwm recovery as the cause of this.
Did you manage to get any drivers for this qhsusb_dload mode?
Edit: these might be useful. http://www.x-drivers.com/catalog/flash/mobile_phones/companies/qualcomm/models/qpst/12051.html http://forum.xda-developers.com/showpost.php?p=14909282&postcount=19

Progress.
Nonverbose said:
Did you manage to get any drivers for this qhsusb_dload mode?
Click to expand...
Click to collapse
Yeah, I've tried out the QPST software and drivers and believe it or not, an answer to my fears. My phone has entered Download Mode with seemingly no way to exit it. I can't find any posts about this in regards to the Incredible S. I guess nobody's been careless or unlucky enough to get it to this state. See the attached picture. Also I can't help but note all the question about ENTERING download mode as opposed to EXITING download mode. Is it so simple that my brain simply can't comprehend the answer?

unfortunately, its not a simple answer. Probably the best thread concerning this issue is in the sensation forum http://forum.xda-developers.com/showthread.php?t=1468791

Nonverbose said:
unfortunately, its not a simple answer. Probably the best thread concerning this issue is in the sensation forum http://forum.xda-developers.com/showthread.php?t=1468791
Click to expand...
Click to collapse
A dead-end unfortunately. It seems more like a preventative measure than anything. I can't enter diag mode on account of phone being stuck in download mode. I'd like to believe it's hardware related. Anyway, I believe it's time I called the repair centre. I appreciate the help you've given me.
EDIT: Seems like Fonebiz refuses to repair my phone, warranty or no, as it's an overseas model, (even though it's physically the exact same phone, down to the model S710e) short of sending it overseas. Unbelievable. I think I'll go cry in a corner now.
EDIT2: Gave it to a local shop to send for repair. I'll let them figure it out. If anybody has any information on proper use of the Qualcomm Software Download tool, by all means link to me.

[Q] Hard Brick (QDL) Solution Research - HTC One (M7)

Hello XDA-Forum,
i am new here, so you dont know me. Therefore i have to mention at least one thing about me: I never ask for help. Especially not regarding electronic Devices and Computer Systems. I always found my answers without asking.
Now i do ask for help. Do the math, its a serious problem . As i am used to solve my problems before asking for help, i have much to tell before anyone could add to what i already know about this problem (although i have to admit that i am pretty new to the Smartphone World). And as sure as i know that no one here wants to read another "Phone broken, HELP!" Thread, so sure i know that not everyone has the time or patience to read my ramblings (i actually wrote a rant too, but decided not to include it here ). So i prepared a summary, and you can see at a glance (almost) if you could help me at all.
Short Story:
My HTC One is Hard Bricked, and beyond my ability to repair - stuck in QHSUSB_DLOAD mode, no access to partitions, no booting under dead screen. It seems i have to send it in for repairs, but i dont like that(well who does?). I researched the problem, tried every solution i could find - no result! if you happen to know a solution, please read the long story to learn what i have tried so far, and if your solution is something completely new (something i didnt try) - PLEASE tell me ASAP before i send it in for repairs.
So, i tried everything i know of and came to the conclusion: it is beyond repair, at least for me. But as this is against everything i believe in (well not everything but i hope you get the point ) i want to find some other Solution if not for me ( as i need my Phone to be working again soon) then at least for the next one facing the same problem. Again: read the long story, or at least the last part, to know what i am asking for... Basically i want to collect all information regarding this problem and find a solution if possible.
Oh and i would prefer technical answers (even if i might have to learn more to understand them) over answers that suggest "Dont bother, you are a noob, you wouldnt understand, just send it in". If you are about to give such an answer, rethink and do something else .
Long Story (Part 1 - What happened):
31/12/2013: My HTC One suddenly stopped working. Until then it worked just fine since i bought it in July 2013. It happened without any apparent cause or any hint of what went wrong, during everyday use, no water involved, no falling, nothing that i could identify as cause. I pressed the power button to wake the phone as always - but the screen stayed black. At first i thought the battery could be empty, but i checked it only 5 minutes before, and it said 32%... still i thought the power indicator could be buggy. Since then it never showed any lifesign again though. It wont start, it wont charge.
I researched about this, and it seems that others had the same problem, and on several different devices. I think i found almost every Qualcomm based device, but mostly the problem was caused by flashing, so this can not be the same problem. If i remember correct, i found HTC One, HTC One S, HTC Desire C, HTC Sensation, Nexus 4/7, Samsung Galaxy S3/S4 and maybe some more, with the same issue i have - Device suddenly went black and got stuck in QHSUSB_DLOAD mode without apparent cause. Many people get at least a lifesign from the LED tough ( be it blinking occasionally, or staying on all the time, or blinking after pressing certain buttons) - i dont.
Long Story (Part 2 - What i tried):
I found several tips on how to revive a device in this state, most recommending something like "press power and one(or both) volume button(s) for XX seconds/minutes" sometimes with the addition to do this under a bright light bulb.
I tried holding the power button, power + vol. down, power + vol. up, power + vol. up + vol. down, for {10,20,30 seconds, or 1,1.5,2,3,5,10 minutes} (countless times), and the same under a light bulb (i doubt this makes any difference as i already did some resets previously, outside in pitch black darkness long before the phone died).
Some recommended to plug it in to charge and dont touch it for 3,8,12 hours - i did that. i tried charging with wall plug and via USB at laptop (for short periods and for 1,3,4,6,8,12,18 hours without touching it).
At the moment i try to leave it off the charger for some days (the weekend and probably some days after) hoping that it will eventually loose all charge and does some sort of reset after that. I doubt it will work, or even be enough time for discharging (as i doubt that it actually USES power in this state) but dont know what else to try before sending it in.
The charging-led stays off when plugged in and there is no response at all from the device. Except when i plug it in at the laptop, Windows recognizes it as QHSUSB_DLOAD. And under Linux i get the Qualcomm device too - no partitions though. If i press power for 10 seconds while connected, it reconnects - so the power button is working. QPST recognizes it as "Q/QCP-XXX (Download)". Is this normal or should it recognize the phone model even in download mode? I tried to get some information through QPST but it tells me the phone needs to be in DIAG mode - which i obviously cant activate on the phone itself. Other than that no life sign at all( also no recognition by adb and fastboot - so its not booting under a dead screen as someone suggested somewhere - dont remember where).
Everyone who had gone as far as i did in trying to revive the phone just gets this last answer "JTAG, or send it in for repair".
Long Story (Part 3 - What i learned):
As i understand it, the Qualcomm Processor switches to this state (QHSUSB_DLOAD) in case there is a severe problem. But i want to know exactly WHAT problem can cause this? And if there is ANY way of convincing the processor to switch to some other state without opening the device?
I dont know JTAG, i never heard of it before this research, so please correct me if i am wrong, i did just a brief research on JTAG and found it too complex to grasp in one or two days i will delve into it at a later time. Here is my first few-minutes-glance at JTAG: it is some sort of standardized hardware-debugging protocol built into many chips, and also the Mainboard or Processor or both in modern Smartphones and Tablets. One would need to open the device and solder the connection cables of a "JTAG-Box" to specific contacts on the Phones Mainboard, is that right? or is there a plug? (I think i found some people using a plug and some using solder iron... i dont remember properly.) When a JTAG-Box is connected to a JTAG-enabled chip, it can issue debugging-commands and/or queries to check (and/or modify?) the functionality of the chip. I found some mentions of JTAG via USB without explanation, is this a way to issue JTAG commands without JTAG-Box over USB Cable? (would be very convenient) Or is it just a way to connect the JTAG-Box via USB to the Computer?
You might ask, if i researched it, i should have every answer, so why am i posting this? Right, i got SOME answers. Now, i know...:
1) ... that am not the first one, nor the only one with this particular Problem. And not even my phone model is the only device with this problem. It might be, all Qualcomm powered devices are possible candidates for a sudden-brick-syndrome.
2) ... some ways to revive a Phone in this state (none working for mine).
3) ... if all reviving tricks fail - JTAG or Repair-service.
4) ... that JTAG needs an opened device (or does it? JTAG via USB maybe?)
5) ... that my phone is not entirely dead: at least the processor can still (sort of) communicate with the PC in Qualcomm High Speed USB - DownLOAD mode.
6) ... no one knows (or tells) what the cause is (or could be) for this problem. The only answers i got are: "There are many possible causes." and "It could be a Software problem" (HTC Support) and finaly "No one can tell without analyzing the device" (HTC and Carrier Support) - Sure no one can definitely tell what EXACTLY is wrong with THIS device... but someone could know what COULD be wrong (What the KNOWN causes are), and just tell me.
Long Story (Part 4 - What i want to know):
Well... I could(/should?) just give in and send my phone in for repairs and hope for warranty. But i did unlock the bootloader through HTCDev (had no other option for unlocking due to HBOOT 1.44) and suspect, they might use this fact to refuse warranty and charge me for repairs, which i might not be able to afford right now. Further, i am feeling absolutely helpless in doing so, and i am NOT used to feel helpless facing ANY sort of problem with ANY electronic device! It is NOT a nice feeling! And i want to change that! Even if it will be too late for me, as i have to get my phone back soon and will probably send it in this week for that reason, i want to find a Solution, that anyone could use to solve this Problem without even contacting the Service, if it is possible to find such a Solution. That is the reason i am posting this, and here is what i want to know:
1) EVERY Story about devices stuck in QHSUSB_DLOAD mode.
1a) IF they where revived and HOW.
1b) What was the cause?
1c) If they could not be revived...
- ... and had to be replaced by a new device: what did the repair team tell what exactly was broken? if they told you anything at all.
- ... and needed replacing parts: WHAT parts where replaced?
- ... ANY hint of what caused the defect?​
1d) WHEN did it happen? (while flashing seems to be the most common scenario, but i and some others had it happen during everyday use)​
2) What exactly is possible to do in QHSUSB_DLOAD mode (probably using QPST)? and what isnt? f.e.:
2a) Pulling any data from the phone without switching to DIAG mode?
2b) Getting ANY information about the phone? (IMEI,CID, etc... Hardware components - i guess it would need a switch to DIAG mode?)
2c) Switching to DIAG(or any other) mode ONLY using the PC and USB connection? (if possible, how?)
2d) Pushing any Data to the device
As i understand it, that is the purpose of this mode(is that correct?), but:
2e) What data can be pushed? Bootloader? System Image? .... i think some CPU firmware is delivered with QPST, correct?
2f) Is it possible to convert an existing System Backup so that it can be flashed with QPST? (i understand QPST needs files in IntelHEX format to push them? Or is that just the CPU Firmware?)
2g) QPST recognizes my phone as "Q/QCP-XXX (Download)". Is this normal or should it recognize the phone model even in download mode?​
3a) If i get no Partitions in Linux while the QHSUSB_DLOAD device is recognized, could this be an indicator for an Hardware failure?
3b) Does it mean, at least the flash memory is fried? (my guess)
3c) Could i tell if the Mainboard was fried by NOT even getting a QHSUSB_DLOAD device? Or can it still be the Mainboard?
3d) Can i tell anything from these facts (Getting QHSUSB_DLOAD device recognized but no partitions)? other than "its a hard burned brick" obviously...​
4a) Which kind of HARDWARE failure could create this state?
4b) and how could that happen during normal use in a device that is only 6 months old, and in good condition?​ 5a) What kind of SOFTWARE failure could cause it?
5b) while it is running? (every day use / not flashing)​ 6) IF i send it in:
6a) Will they be able to access my data?
6b) Can they tell (by JTAG maybe) if it was rooted,flashed, had an unlocked bootloader?
6c) And the hardware is dead, will they just replace the fried parts? or replace the Phone with a new one? (not really important but nice to know )​
7a) Is it possible to use ANY type of JTAG commands/queries/(whateveritiscalled) WITHOUT opening the device? (via USB)
7b) Without a JTAG-Box? (already existing software simulating a JTAG-Box)​ 8) What kind of Information can be gathered by JTAG? f.e.:
8a) Working state of hardware components?
8b) Access to files on flash memory?​ 9) What kind of modifications/commands can be made/issued by JTAG? (depends on the device/chip attached i assume?)
I know i could just buy a JTAG-Box and learn everything about JTAG to answer some of these questions myself. But i did not find time for learning about something completely new (new for me) yet, and i dont have the money at the moment to just buy a JTAG-Box without knowing how to, and if i will use it (dont even know how much it is...). I will certainly NOT open my 660€ phone, probably breaking the screen and whatever in the process, because of its DONT-OPEN-ME-Design(nice looking, but in some cases inconvenient), and make it a test-dummy for my first JTAGing steps. So it would be nice if someone with some experience in that matter, could give me a brief overview of the possibilities and uses of a JTAG-Box - AND if there is some way to simulate one.
And finally i would like to get into contact with people who might have a clue of the possible causes for this problem, and the ability and willingness to work on a solution. I did find some WIP Unbricking Projects also working on a solution for QHSUSB_DLOAD related issues, but all of them where Model-specific (and mostly for cases where a specific flashed software was the cause) and none for the HTC One (M7)... Although i would like to have a general solution for every device and cause, i doubt there would be any Model-specific Project if it was POSSIBLE at the moment to provide a general one. It would be nice though, if we could at least TRY to make one(some people probably are already trying). But i assume (from what i read) that the existing unbricking projects still need access to the internal storage. So, no access to storage = hardwarefailure & not unbrickable by software?? Even if thats the case and my phone is realy beyond (sofware)repair, i would still like to get answers to my other questions!
If you did read all of this - Congratulations! Have a coffee and a break
I am sorry for:
- noob questions (if there are any left besides the JTAG related - i cant tell anymore)
- annotations and supplements in braces (it can be annoying, i always squeeze in some thoughts somewhere)
- forcing you to read this wall of text, probably full of spelling and grammar errors (i am tired and somewhat tense)
- bad English (not my native language, and... i am tired)

OMG this post is incredibly long. I'll give you a short answer.
Yout phone is hard bricked and MAYBE a JTAG may fix it, BUT the phone needs to be opened, which with this phone is pratically impossible to be done, furthermore you need smb with experience on those things.
If you weren't soing anything to your phone(s-off, hboot flash, ruu, etc) than probably the motherboard is dead. I have seen this happen a lot of times with this phone, probably because of not genuine charger/faulty. You SHOULD sebd your device for repair definitely, I'm 99.9% sure no one will notice it's HTC dev unlocked, cause it doesn't turn on. A lot of users have sent their and had no problems. Good luck!
Sent from my HTCONE using Tapatalk

Very interested in the actual answer, and the reason, subscribed.
Sent from my iPod touch using Tapatalk

elvisypi said:
... MAYBE a JTAG may fix it, BUT the phone needs to be opened, which with this phone is pratically impossible to be done, furthermore you need smb with experience on those things...
Click to expand...
Click to collapse
Thats why i wont just try it... not on this phone, and not before i know more about JTAG.
elvisypi said:
...If you weren't soing anything to your phone(s-off, hboot flash, ruu, etc) than probably the motherboard is dead...
Click to expand...
Click to collapse
Well, the phone is (was) s-off, rooted, and running ARHD 40.3 + TWRP 2.6.3.3 - but i did this long before it died and never had problems during the process, or while using the device.
elvisypi said:
...probably the motherboard is dead. I have seen this happen a lot of times with this phone, probably because of not genuine charger/faulty...
Click to expand...
Click to collapse
I mostly used the HTC plug which came with the phone for charging. Although i didnt use the original cable, because it broke shortly after i got it. Sometimes i used a USB-Battery-Pack to charge the phone on-the-go. Could any of this be the Cause?
elvisypi said:
...I'm 99.9% sure no one will notice it's HTC dev unlocked, cause it doesn't turn on. A lot of users have sent their and had no problems. Good luck!
Click to expand...
Click to collapse
So, they cant just JTAG it (or do something similar) and it will turn on again? Obviously not if the motherboard is fried... but is it possible that it isnt, and they can? I will send it in nontheless, but i would like to understand what is possible, and find the cause aswell as a solution.
oh and thank you!

MarvThor said:
Thats why i wont just try it... not on this phone, and not before i know more about JTAG.
Well, the phone is (was) s-off, rooted, and running ARHD 40.3 + TWRP 2.6.3.3 - but i did this long before it died and never had problems during the process, or while using the device.
I mostly used the HTC plug which came with the phone for charging. Although i didnt use the original cable, because it broke shortly after i got it. Sometimes i used a USB-Battery-Pack to charge the phone on-the-go. Could any of this be the Cause?
So, they cant just JTAG it (or do something similar) and it will turn on again? Obviously not if the motherboard is fried... but is it possible that it isnt, and they can? I will send it in nontheless, but i would like to understand what is possible, and find the cause aswell as a solution.
oh and thank you!
Click to expand...
Click to collapse
Hi, just wondering if you had any updates to your story?
I have a HTC One in basically the same situation - it totally died on my wife in the middle of her using it. The battery was at over 50% and we have never even dev unlocked it or flashed ROMs or recovery etc. No lights come on when charging, tried all manner of the power, power+vol key combos etc, tried the bright light as well, nothing gets it to come alive. Plugging into the computer does recognise the HSUSB_DLOAD low level qualcomm device but as yet I havent been able to get drivers to allow it to be recognised. I am taking it to a place on the weekend that says they have JTAG box and may be able to help. I would send it away for warranty replacement but it's my wife's phone and she hadnt backed up the photos on it for a few months and we have a 20 month old son, so we are trying everything possible to retrieve the data off it. Lesson learned, will be putting in place backup regime on our phones from now on!
Will let you know if any joy comes from the JTAG process
Reading your recent comments it is interesting to note that we do have an external power brick (IO Gear 11,000 mAH unit) that we sometimes have charged the phone on. Potentially we even used the 2.1A output from this power brick rather than the 1.0A output on occasion.

Sorry, i totally forgot about this Thread over all the other things in the last weeks (Starting a Business, moving to a new Place.. etc).
scarecrow420 said:
Hi, just wondering if you had any updates to your story?
Click to expand...
Click to collapse
Yes, i sent it in for repairs, and got it back two weeks later. They had to replace the Mainboard and some other Parts(plus some they broke during Repairs), i could not get any information about the possible causes other than "there are many"... It was covered by the warranty though.
I dont think they could get any data from the Phone.
scarecrow420 said:
Will let you know if any joy comes from the JTAG process
Click to expand...
Click to collapse
I would appreciate that
scarecrow420 said:
Reading your recent comments it is interesting to note that we do have an external power brick (IO Gear 11,000 mAH unit) that we sometimes have charged the phone on. Potentially we even used the 2.1A output from this power brick rather than the 1.0A output on occasion.
Click to expand...
Click to collapse
If the cause is indeed the power brick, i will have to check mine again (measure its output). It is supposed to have 5.0V 1.0A output only, which is the same that the HTC Charger is labeled with.
Well, good luck with your Phone! But if your Phone is as dead as mine, i am afraid you probably wont get those Photos back...
-
Ok, i got my phone back without trouble - but i am still researching (when i have got the time ) the causes and a possible solution for this problem. So, if anyone has any information that could be helpful: please post it here!

Hi guys! Sorry for my bad english but i'm italian. My HTC One gone in QHSUSB_DLOAD mode 3 times (it's not a joke) and i've still it in my hands
This is my configuration now: (today my phone entered in QHSUSB_DLOAD mode)
Firmware = 4.19.401.8 (Darkbootoader)
ROM = SkyDragon v12.0
Kernel = ElementalX 13.0
PVS = 5
Today when tried to turn on the screen with doble tap it do nothing, screen was completly black and same thing when i hold the power button with vol down. After i plug in USB (it was a normal nokia cable) cable and hold power + vol. down for about 20 seconds (there wasn't LED or blinking button, anything) it's boot into bootloader:highfive:
I suppose (because every time my phone bricks when i do too Undervolting) it has "hangry" of energy and it boots up anymore if i don't give him an "help". The same thing when i had the MIUI with the same undervolting
Maybe is too much Undervolting the reason of hard brick, did you undervolt your CPU like me?

Did you find out any answer?
Where you able to bring it back to life?
Did you send it back to HTC for repairs? How did it go?

Would this work?
http://unlimited.io/qhsusbdload.htm

Dredead said:
Would this work?
http://unlimited.io/qhsusbdload.htm
Click to expand...
Click to collapse
third time.

To make a long story short (like you did in the OP), I have to same problem
The cause: flashing newer firmware version. All the symptoms are exactly the same. When I get home from work today I will try these 2 things, they are a little variation of what I already tried:
http://htc-one.wonderhowto.com/how-to/fix-soft-bricked-htc-one-by-flashing-new-rom-via-adb-0154361/
http://www.androidlegend.com/how-to-use-adb-fastboot-commands-with-your-android-device/
I don't have much hope that I can fix it myself and am already in contact with HTC though. The main problem is that I'm in Argentina and I bought the phone in Germany..
You didn't find any other possible fixes, right?

Hi, I Have Same Problem Since A Month With My HTC One M7 32GB
I Got this phone as a Gift From USA HTC one M7. My Phone Just got hanged on lockscreen when i try to restart it, it turns off but did not turn on,no single light is turning on, no screen light or notification, no recovery or download mode. its like a brick piece. i tried all charging tricks such as USB PC ,Wall Charger for Hours, Orignal Charger and rest things, i cannot send phone to USA , i am in qatar, what should i do, any guys who experienced such problem and how did they solved it and, what will be the cost if no warranty. any help ? thanks in advance. :crying:

till22 said:
To make a long story short (like you did in the OP), I have to same problem
The cause: flashing newer firmware version. All the symptoms are exactly the same. When I get home from work today I will try these 2 things, they are a little variation of what I already tried:
http://htc-one.wonderhowto.com/how-to/fix-soft-bricked-htc-one-by-flashing-new-rom-via-adb-0154361/
http://www.androidlegend.com/how-to-use-adb-fastboot-commands-with-your-android-device/
I don't have much hope that I can fix it myself and am already in contact with HTC though. The main problem is that I'm in Argentina and I bought the phone in Germany..
You didn't find any other possible fixes, right?
Click to expand...
Click to collapse
Hi, how did this go? I just bricked mine doing the same thing... upgrading firmware. I can't get it to respond to any of the suggested methods. What sucks is that the firmware update dialog in fastboot looked good to me. Sucks...

mkclarke said:
Hi, how did this go? I just bricked mine doing the same thing... upgrading firmware. I can't get it to respond to any of the suggested methods. What sucks is that the firmware update dialog in fastboot looked good to me. Sucks...
Click to expand...
Click to collapse
The link to the fix is on page one
http://forum.xda-developers.com/showthread.php?t=2770684

clsA said:
The link to the fix is on page one
http://forum.xda-developers.com/showthread.php?t=2770684
Click to expand...
Click to collapse
Cool, thanks! I wonder if a vm running linux would work. All my machines are windows. Not sure how the vm would handle the usb connection. I'll have to see what I can figure out.

I just used an ubuntu boot CD when I did it
Sent from my HTC One using Tapatalk 4

clsA said:
I just used an ubuntu boot CD when I did it
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Yes! I just thought of that after I posted. I think I still have an ubuntu live CD around here somewhere...
Thanks!

I'll be damned! This worked! I just popped in the latest Ubuntu liveCD and went to town. My phone is now up and charging. Once it's at 100%, I'll try pushing TWRP recovery to it and restoring my last backup.
Thanks again for sending me to that link!
---------- Post added at 10:42 AM ---------- Previous post was at 09:59 AM ----------
Done and done... pushed TWRP and restored my last backup. It's as if it were never bricked! And it also updated my kernel, which is what I was trying to do in the first place.

Just for future reference for anyone coming across this thread, there are two distinct types of bricks being discussed here.
The first results from a borked firmware update. In this case, everything works on the hardware side, it's just that the phone can't boot because the firmware is messed up. This is usually fixable using Dexter's method.
The second, and the problem experienced by the OP, is more serious and is hardware related. I have seen this occur with multiple HTC models. Something related to power management on the motherboard dies so that the phone no longer can no longer get power to start up. When this happens, the phone will typically have shut down without warning despite having a good battery charge. I have never seen or heard of a fix for it beyond returning it for warranty repair.

htc m7 pn07110 bricked
htc m7 pn07110 bricked
hi i have a problem when usin my phone it suddenly freezers and was not able to get acces to anything (Was rooted/Bootloader Unlocked/having Custom Rom/TRWP/S-ON).. tried to restore my rom by usin twrp 2.8. but there was no file and it cannot mount my storage...
Then, found on a thread to restore stock ROM via RUU, so i relocked my bootloader and then find myself stuck at everything
When I plug in AC adapter for charging, phone load in bootloader, and whenever i press "Fastboot/Factory Reset" my phone freezes
Even fastboot and ADB command freezes my phone,
I need help please.
Code:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.28.3218.04
OpenDSP-v32.120.274.0909
OS-6.09.401.111
eMMC-boot 2048MB
Nov 12 2014,21:44:28.0

Got the LCA43 update now watch dead

I was pleased to get the update, it asked that I get the charge up to 40% plus which I did and left it plugged in and proceeded. Took quite a while and then went to battery charge instead of reboot as has happened in the past.,, I did hit the power switch and it turned off, now nothing no charge indicator and no matter how long I hold the power switch nothing.. And other tips to wake this puppy up? I originally got it at Google IO.. Wonder if Google will help?

dartdog said:
I was pleased to get the update, it asked that I get the charge up to 40% plus which I did and left it plugged in and proceeded. Took quite a while and then went to battery charge instead of reboot as has happened in the past.,, I did hit the power switch and it turned off, now nothing no charge indicator and no matter how long I hold the power switch nothing.. And other tips to wake this puppy up? I originally got it at Google IO.. Wonder if Google will help?
Click to expand...
Click to collapse
I doubt that Google will be able to help you. Also, since its being about a year now, your watch probably doesn't have a warranty from Samsung anymore. Might still worth a try though.
See if your watch is detected by pc. I remember my watch had a glitch once. It wasn't booting up and was showing up as a device in device manager. I forgot the exact name, but it was not something you usually see when you connect in fastboot or adb mode. If it does then there might still be hope.
Try to boot your watch into fastboot mode. You need to press the power button and slide with your finger on the screen from left top corner to right bottom corner. Just slide it multiple times while holding the button. If it boots then you can either do factory reset or full reflash.

Thanks for the tips, Samsung seemed quite accommodating and gave me a return ship label,, we shall see, hoping for the best and not outrageous... Xing fingers...
aligatro2010 said:
I doubt that Google will be able to help you. Also, since its being about a year now, your watch probably doesn't have a warranty from Samsung anymore. Might still worth a try though.
See if your watch is detected by pc. I remember my watch had a glitch once. It wasn't booting up and was showing up as a device in device manager. I forgot the exact name, but it was not something you usually see when you connect in fastboot or adb mode. If it does then there might still be hope.
Try to boot your watch into fastboot mode. You need to press the power button and slide with your finger on the screen from left top corner to right bottom corner. Just slide it multiple times while holding the button. If it boots then you can either do factory reset or full reflash.
Click to expand...
Click to collapse

dartdog said:
Thanks for the tips, Samsung seemed quite accommodating and gave me a return ship label,, we shall see, hoping for the best and not outrageous... Xing fingers...
Click to expand...
Click to collapse
If they do end up "repairing" it, you will get a brand new watch. Samsung doesn't bother re-flashing or repairing old watches, they just send you a new one. Don't include your wristband though. You'll get your old one back... unless they lose it.

watch return
They were quite insistent that I send everything, band, charger and watch,, so we'll see..
aligatro2010 said:
If they do end up "repairing" it, you will get a brand new watch. Samsung doesn't bother re-flashing or repairing old watches, they just send you a new one. Don't include your wristband though. You'll get your old one back... unless they lose it.
Click to expand...
Click to collapse

dartdog said:
They were quite insistent that I send everything, band, charger and watch,, so we'll see..
Click to expand...
Click to collapse
Must be different in your country. Here is the instructions they sent me when I was sending my watch for repairs.
Shipping Guide Line
(1) Verify above information is correct
i.e: Name, Shipping Address, Model number and Serial number etc
(2) DO NOT INCLUDE ANY ACCESSORIES. (Cables, Remote control, manuals, Battery, Drivers, toner cartridge, imaging unit, transfer belt, waste toner bin etc), unless otherwise instructed.
(3)
a) Package Properly, this is the responsibility of sender
b) Include copy of this authorization in the package.
(4) Arrange shipping with UPS courier (United Parcel Service)
a) Attach UPS waybill on outside of the package.
b) write down UPS tracking number for your records
Click to expand...
Click to collapse

I guess it falls under "unless otherwise instructed" He was quite specific.. !!I did get the same printed instructions though...

As predicted Samsung sent an invoice for $188 to "repair" obviously not worth it with the new stuff coming out and particularly insulting since the OTC SW update caused it... Does not make me happy with Samsung to say the least...

I purchased mine from Amazon and in 6 months it was dead. Samsung would not warranty it in the USA because they told me that they didnt know where amazon bought it from and therefore wanted me to find out what country it came from and then they woudl give me that country customer service #. COMPLETE BULLcrap. amazon ended up giving me a refund.

Pixel 4xl stuck on 50% . Switches off randomly and has a battery symbol with a (?).

Hi All.
Battery stuck on 50% won't change even when charge or discharge. Today it randomly shutdown in my pocket. and then had a battery symbol with a ?. The phone eventually turned on, I've tried turning off location, rebooting still having issues. Sometimes the battery saving mode stops working, i.e. it cannot be turned on. As I can see the problem concerns a large group of users and nobody knows what this problem is related to. Google is silent as usual. Is this a problem with the software or components ?! I am in a bad situation because I have no warranty for the device and I do not know where to send the phone in Poland because no one knows what is the cause of the problem. Help me please.
https://support.google.com/pixelphon...25796722?hl=en
https://support.google.com/pixelphon...22385581?hl=en

Had this.
This is going to sound dumb:
Shut your phone off.
Now squeeze the phone around the G logo on the back (like you're trying to compress it).
Now turn it back on and charge normally.
This is potentially only a temporary fix as I have no idea how this would be software related.

If you can enter bootloader mode, you still have chance to save your phone by yourself :
(1)Make sure there is fastboot&ADB tool in your computer
If you don't have it, please download from here(https://developer.android.com/studio/releases/platform-tools). To click the one depends on which one of OS you have and then install in your computer
(2)Download google factory image file from here(https://developers.google.com/android/images). To choose the model of your phone and download it then extract file.
(3)Reboot your phone to bootloader mode. Then use USB cable and make phone connected to your computer USB port. Then execute the window commend mode. key in
fastboot devices ===> make sure your phone being catched by your computer
flash-all ===> To build up a whole new pixel OS in your phone.
Good luck !
Kris

Shayded said:
Had this.
This is going to sound dumb:
Shut your phone off.
Now squeeze the phone around the G logo on the back (like you're trying to compress it).
Now turn it back on and charge normally.
This is potentially only a temporary fix as I have no idea how this would be software related.
Click to expand...
Click to collapse
Unfortunately, this is only temporary. After one day the problem happened again!

SignumOne said:
Unfortunately, this is only temporary. After one day the problem happened again![/QUOTE
Ive had my pixel 4 xl since november and it just started automatically shutting off when in my pocket all by it self a few weeks ago , took cell phone to my sevice provider and they sent it in for repair ...received a new phone ...well refurbished p4 xl only to have if start happening again days later and have the 50% battery start happening also ....contacted google and they are in the process of sending me a new refurbished p4 xl , so this will be my 3 rd p4 xl ..lol
very frustrating to say the least ....ive had to hard reboot my phone at least 20 times a day or basically keep it out of any pockets , the is common issue apparently with pixels phones from what i've read in the link https://support.google.com/pixelphone/thread/22397169?hl=en
I've talked with loyalty department at my service provider and if it happens again with the pixel that google sends me , then they will allow me to void my contract and supply me with a new device from a different brand ...ie Samsung or apple or whatever else is available on the market right now on there website.
i'll be really bummed if i have to switch to a samsung or apple buuuuuut need a stable device ...lol
So to anyone having this issue that still has a basic warranty, there are at least 2 options ...rma device over and over till you get one that doesn't have this problem or contact service provider and explain your situation and most likely they will be understanding to the fact that you have purchased a 1200.00 phone that requires constant rma's and hopefully allow you to exchange for a different brand of phone that doesn't have this these problems
Click to expand...
Click to collapse

Mr. Blanco said:
SignumOne said:
Unfortunately, this is only temporary. After one day the problem happened again![/QUOTE
Ive had my pixel 4 xl since november and it just started automatically shutting off when in my pocket all by it self a few weeks ago , took cell phone to my sevice provider and they sent it in for repair ...received a new phone ...well refurbished p4 xl only to have if start happening again days later and have the 50% battery start happening also ....contacted google and they are in the process of sending me a new refurbished p4 xl , so this will be my 3 rd p4 xl ..lol
very frustrating to say the least ....ive had to hard reboot my phone at least 20 times a day or basically keep it out of any pockets , the is common issue apparently with pixels phones from what i've read in the link https://support.google.com/pixelphone/thread/22397169?hl=en
I've talked with loyalty department at my service provider and if it happens again with the pixel that google sends me , then they will allow me to void my contract and supply me with a new device from a different brand ...ie Samsung or apple or whatever else is available on the market right now on there website.
i'll be really bummed if i have to switch to a samsung or apple buuuuuut need a stable device ...lol
So to anyone having this issue that still has a basic warranty, there are at least 2 options ...rma device over and over till you get one that doesn't have this problem or contact service provider and explain your situation and most likely they will be understanding to the fact that you have purchased a 1200.00 phone that requires constant rma's and hopefully allow you to exchange for a different brand of phone that doesn't have this these problems
Click to expand...
Click to collapse
I fully understand you. I am in a worse position. As a loyal Google fan, I bought my pixel from someone who didn't have a proof of purchase. In Poland it was difficult to get it, and as it was 1.5 times more expensive than everywhere else. It seems that I can throw out the pixel and buy another phone for a lot of money. I am most annoyed by the company's attitude. It looks like they are xxxxx on us.
Click to expand...
Click to collapse

Kris Chen said:
If you can enter bootloader mode, you still have chance to save your phone by yourself :
(1)Make sure there is fastboot&ADB tool in your computer
If you don't have it, please download from here(https://developer.android.com/studio/releases/platform-tools). To click the one depends on which one of OS you have and then install in your computer
(2)Download google factory image file from here(https://developers.google.com/android/images). To choose the model of your phone and download it then extract file.
(3)Reboot your phone to bootloader mode. Then use USB cable and make phone connected to your computer USB port. Then execute the window commend mode. key in
fastboot devices ===> make sure your phone being catched by your computer
flash-all ===> To build up a whole new pixel OS in your phone.
Good luck !
Kris
Click to expand...
Click to collapse
Have you checked if it works for you?

SignumOne said:
Have you checked if it works for you?
Click to expand...
Click to collapse
i've flashed full stock images , custom roms and still have the same issue on both stock and custom rom

Had the same problem three weeks ago. Contacted Google Support und they send me a new phone as a replacement on warranty.

SignumOne said:
Hi All.
Battery stuck on 50% won't change even when charge or discharge. Today it randomly shutdown in my pocket. and then had a battery symbol with a ?. The phone eventually turned on, I've tried turning off location, rebooting still having issues. Sometimes the battery saving mode stops working, i.e. it cannot be turned on. As I can see the problem concerns a large group of users and nobody knows what this problem is related to. Google is silent as usual. Is this a problem with the software or components ?! I am in a bad situation because I have no warranty for the device and I do not know where to send the phone in Poland because no one knows what is the cause of the problem. Help me please.
Click to expand...
Click to collapse
This is the "No Warranty Solution" : Flash a full factory image and allow it to completely wipe your phone. This is the second step Google support would give you (the first is doing a factory data reset from Recovery). If after flashing your phone, restoring it to the original "out of the box" state, you still have a battery issue, then the next step is to replace your battery. If you forgot to state in your OP that your bootloader is still locked (so you can't flash the image) then you need to do that first. Bottom line is you need to factory reset the phone to rule out a software issue. If the restored phone still has the same problem, then you need to focus on the hardware. Best of luck. :good:

Yes, it does !
SignumOne said:
Have you checked if it works for you?
Click to expand...
Click to collapse

Same happened to me with 4 XL 64.
I've been able to "fix" with the turn off and squeeze but the problem has turned into the battery discharge displayed gets stuck at a percentage and it won't charge. I have to turn off & squeeze to get it back.
Finally called Google and they are making me send my phone in for repair. Now I assume for turnaround sake, they'll just send me a new refurb back. That also means I'm not confident the problem will be resolved as there are over 150 replies on the Google Support page identifying this problem.
https://support.google.com/pixelphone/thread/25796722
Looks like some folks are getting a replacement before sending the problem phone back but others are required to send it in or drop off at repair facility.
Good for me? I have Preferred Care and I'll keep sending them back until I get one that works.
Bad for me? I'll have to keep sending them back + I splurged on the orange color so I doubt I'll ever see that again.

I've actually dealt with this. This is a hardware issue. I had the same problem. Covered by warranty, I took it to ubreakitifix after contacting Google and they took care of me. Trust me this isn't a issue where you can flash this or squeeze that. This is a hardware issue on Google's part. There's nothing you can do as a phone user about a defective battery in a 6+ month old $1000 phone

angus242 said:
Same happened to me with 4 XL 64.
I've been able to "fix" with the turn off and squeeze but the problem has turned into the battery discharge displayed gets stuck at a percentage and it won't charge. I have to turn off & squeeze to get it back.
Finally called Google and they are making me send my phone in for repair. Now I assume for turnaround sake, they'll just send me a new refurb back. That also means I'm not confident the problem will be resolved as there are over 150 replies on the Google Support page identifying this problem.
https://support.google.com/pixelphone/thread/25796722
Looks like some folks are getting a replacement before sending the problem phone back but others are required to send it in or drop off at repair facility.
Good for me? I have Preferred Care and I'll keep sending them back until I get one that works.
Bad for me? I'll have to keep sending them back + I splurged on the orange color so I doubt I'll ever see that again.
Click to expand...
Click to collapse
You might be able to convince them to send you a device before you ship it off, citing the current global situation and a need for a cell phone

OP lives in Poland and has no receipts or warranty. Poland is not a supported country so he is looking for "non-warranty" solutions.

Shayded said:
You might be able to convince them to send you a device before you ship it off, citing the current global situation and a need for a cell phone
Click to expand...
Click to collapse
The return process was pretty great. I shipped my existing phone off on a Monday (Illinois to Texas) and by the following Monday, I received my exact phone back (has a screen protector on it). I was very satisfied with that. HOWEVER, the "repair" still has an issue where if I charge to 100%, the icon stays at 100% until I reboot and then it'll display the correct battery %.
The repair documentation was a bit vague and said they replaced the "charging port". I still believe there's a unannounced hardware issue. Can anyone say, class action????
---------- Post added at 04:16 AM ---------- Previous post was at 03:49 AM ----------
I wonder what the next step would be if I started another repair claim?

Holding the power button down for more than 3 consecutive seemed to solve a similar issue for me. My P4 was holding certain percentages for too long (even though the phone actually lost more).

Suavie103 said:
I've actually dealt with this. This is a hardware issue. I had the same problem. Covered by warranty, I took it to ubreakitifix after contacting Google and they took care of me. Trust me this isn't a issue where you can flash this or squeeze that. This is a hardware issue on Google's part. There's nothing you can do as a phone user about a defective battery in a 6+ month old $1000 phone
Click to expand...
Click to collapse
This post seems to have been ignored. If it happens to me, I'll try that. But my carrier purchase didn't qualify for Google extended care add-on. Standard warranty only. Does that make a difference in what Google would do in this case?
I use Accubattery and monitor charge cycles for "battery wear". Even following "Battery College" recommendations, battery health has dropped from 99 to 95%; I've had the P4XL since November. I'm now slowing the charge, getting away from power delivery to see if that helps slow the wear. SOT varies greatly per charge.
I use a belt pouch for carrying phone while away from home. Rarely, I put it in my pocket but do so at home- front pocket only- never back pocket. May just be bad phone batteries from what I've read.
Sent from my Pixel 4 XL using Tapatalk

v12xke said:
OP lives in Poland and has no receipts or warranty. Poland is not a supported country so he is looking for "non-warranty" solutions.
Click to expand...
Click to collapse
For 5 weeks my Pixel has been in the authorized repair center in Germany. They don't have parts to fix it. They told me that. It is not known how long this may take. I haven't had such a circus with a good smartphone. I love Google products, but I feel very disappointed because Pixel cost me a lot of money and this is definitely a factory defect.

SignumOne said:
For 5 weeks my Pixel has been in the authorized repair center in Germany. They don't have parts to fix it. They told me that. It is not known how long this may take. I haven't had such a circus with a good smartphone. I love Google products, but I feel very disappointed because Pixel cost me a lot of money and this is definitely a factory defect.
Click to expand...
Click to collapse
Sorry to hear this, and surprising, as Germany is a supported country with many authorized repair centers. Did you send it to PSC? They claim to be Google-certified and have all factory parts? COVID-19 may also be delaying things. Hope things turn out well for you. :good: