Database Develop

[SOLVED] HTC HD7 won't start after failed update (Step 9 of 10) , Phone is Dead

I tried updating my phone and it got stuck on step 9 which was the reboot process. and the screen was just white with the HTC logo.
It was stuck on this step for a good 3 hours so i assumed something was wrong. I cancelled the update and unplugged the phone from the computer and it was stuck on the HTC screen still so i took out the battery.
And when i put the battery back in and tried turning it on it wouldn't turn on. And so now it my phone won't even turn on! I'm very frustrated. I thought at first it was dead but when i plugged it in the charger the charging light won't even come on. Tried Wall Charger and Computer
Please someone help! I need a solution
(Problem Solved by Flashing the Set with RIFF Box)

Try to put into bootloader and flash a rom from an ruu. You'll start from scratch but if it works it works.
Sent from my HD7 using XDA Windows Phone 7 App

@ Reeg420
Thanks for the Reply Man, But i try to put the Phone in Boot loader by Pressing the Volume Down Key and Power Key But no respond from the Phone...
Please advise if i am doing it Correct.

Its not showing any sign on Power at all even when i plug it to the PC or wall socket charger.

Pretty sure that's how to put in bootloader. Try to take battery out out for like 2-3 minutes, put back in then try bootloader. Doesn't make sense since the Zune updates basically overwrites files to update, not like previous windows mobile updates that wipes the the phone then replaces everything. Keep trying. Is there a possibility the battery is dead?
Sent from my HD7 using XDA Windows Phone 7 App

tariqsdk said:
Its not showing any sign on Power at all even when i plug it to the PC or wall socket charger.
Click to expand...
Click to collapse
Whenever you update a phone and something goes wrong, it is always advised to make sure you DON'T remove the battery, especially while updating, if you hadn't removed the battery you could've ran the Windows Phone support tool. You have Bricked your mobile.
If there is no life not even charging you have bricked it.. Sorry to tell you this
You ain't the first person to brick your mobile and sadly you won't be the last
Quick Question: How were you updating your phone? via Zune client where it specifically says Do not remove the cable or battery.. Or via rom update manager for manually updating roms where it says the same thing? Hate to sound horrible but people should really pay attention to what it clearly states during updating..
Additional Info: Just thought id add and ask what you were updating, basically if you were updating either the bootloader or the radio (if these were in the update as well) you've bricked it, and with there being no life at all it tells me its dead and the cpu refuses to boot, the only way to bring it back from the dead is to JTAG it which I don't believe has been done for the HD7 yet and is a massive pain to do, Best thing you can do is send it in for repair and hope that they repair it, normally they don't

I was updating it through Zune, And it was stuck at step 9 and it was stuck like 4 hours.
Well it is is Bricked then i guess this is my Last windows Phone
I was happy with my iphone 4 but i don't know what strikes at my head that i decide to sell it and buy this stupid HD7 ( May be i am Stupid not the Phone)...
I will hit the Repair Market to get it fix through JTAG ( I search on Google and find that it's Possible for HD7) and update the thread later.
Wish me Good Luck

tariqsdk said:
I was updating it through Zune, And it was stuck at step 9 and it was stuck like 4 hours.
Well it is is Bricked then i guess this is my Last windows Phone
I was happy with my iphone 4 but i don't know what strikes at my head that i decide to sell it and buy this stupid HD7 ( May be i am Stupid not the Phone)...
I will hit the Repair Market to get it fix through JTAG ( I search on Google and find that it's Possible for HD7) and update the thread later.
Wish me Good Luck
Click to expand...
Click to collapse
I know iPhone 4's are perfect, I think Apple has 0% percent returns. Oh don't forget the bumper, they are so in season... and they help to prevent drop calls.
My guess is there is a reason for the 4 hour update, possibly the phone got disconnected breifly during the update... that happens and the phone will just sit there and never finish. I have a few micro USB cords and they seem to be a bit prone to faluire after months of use. My nephew, who is 19... and well as careless as a 19 year old was holding the phone in his hand did just that, almost bricked his. Fortunately for my nephew the 7720 update program had already copied everything to the phone and it was during the reboot so it updated anyway.

Well the Update is...
Here in Kish Island, No Repair Shop has that RIFF Box to do the Repair and One Guy has promise to do the Job in one week, So i Guess i have to wait till then and Manage on my all time Rough and Tough Nokia E5....

Yes, its Alive Again...
With the help of RifF box and 50 Bucks, its up and running again with all of my Data and apps,
i am thinking again about updating it on Mango update....What do u guys think should i give it a try?

Can you please help me? i have same problem, i am in Tbilisi, and here repair markets could not fix my problem...
Can you please give me any info about that market?
did they had problem about imei repair? here is this problem and we can not fix it yet...

qarsaoti said:
Can you please help me? i have same problem, i am in Tbilisi, and here repair markets could not fix my problem...
Can you please give me any info about that market?
did they had problem about imei repair? here is this problem and we can not fix it yet...
Click to expand...
Click to collapse
Dear, I am afraid that i can't help you a lot on this as i just ask the repair shop and they said that they can fix it with the help of some hardware called RIFF Box and they did in few hours. Just to be noted that they have to disassemble your phone to so that.
regarding IMEI problem i have no idea too. Best of Luck and i can understand your feelings.

tariqsdk said:
Dear, I am afraid that i can't help you a lot on this as i just ask the repair shop and they said that they can fix it with the help of some hardware called RIFF Box and they did in few hours. Just to be noted that they have to disassemble your phone to so that.
regarding IMEI problem i have no idea too. Best of Luck and i can understand your feelings.
Click to expand...
Click to collapse
i heve the same problem and i have riff box
can u tell me how to repair my phone
thx

i did not fixed my phone problem yet, and he does not know how to fix it, he repaired it in market..

no solution to repair such phone ??

HTC HD7 is dead due to update failure step 9.
hi tariqsdk,
Even my HTC HD7 is dead by the same reason as yours.
Can you plz help me out to get my phone alive?. I m currently in Singapore.
Please send me your valuable info.
Thanks
Uday
---------- Post added at 04:45 PM ---------- Previous post was at 04:41 PM ----------
hi tariqsdk,
Even my HTC HD7 is dead by the same reason as yours.
Can you plz help me out to get my phone alive?. I m currently in Singapore.
Please send me your valuable info.
Thanks
Uday

Dear all,
to be honest my phone is dead again when i try to do some ****ty update .....
i am trying to find someone to do this again. i will update accordingly soon.

I have the same problem
Hi, I have the same problem and my phone's been dead for 3 months now
I went to a repair shop in Cairo, and they did the JTag thing, but he was unable to download or install the right ROM... Everytime he tries installing a different ROM it fails and he has to start all over again.
Do you know where I can find/download the ROM that works with my T-Mobile HD7 after we do the JTag?

Still no Update....

Hey where you find a RIff box in Pakistan , I've half bricked my phone

HTC One M7 Touchscreen Dead

Hi all,
Anyone else having any issues like this? I see this was a common problem on that HTC One X as well (thread for reference: http://forum.xda-developers.com/showthread.php?t=2010897 ). I haven't seen any reports of this and I searched the forums and the internet...maybe I've had bad luck because of the similar name, but I haven't heard anything official from XDA or otherwise
Occasionally, it seems that the middle area can work if there is enough static on the screen. Here is my screen map to show what I'm talking about:
UPDATE:
How strange. This issue started happening on Saturday, but on Monday when I was about to go down to T-Mobile to return the phone for a warranty repair, it suddenly fixed itself. I have full screen functionality. I didn't change any settings, didn't flash anything new, etc. The phone was never turned off (other than when I was testing if a restart or power cycle would fix it). I'll keep monitoring it in any case...

armadeous said:
Hi all,
Anyone else having any issues like this? I see this was a common problem on that HTC One X as well (thread for reference: http://forum.xda-developers.com/showthread.php?t=2010897 ). I haven't seen any reports of this and I searched the forums and the internet...maybe I've had bad luck because of the similar name, but I haven't heard anything official from XDA or otherwise
Occasionally, it seems that the middle area can work if there is enough static on the screen. Here is my screen map to show what I'm talking about:
Click to expand...
Click to collapse
Exactly, I haven't heard before this similar problem... I think you are the first.
Have you installed a special app ?
Have you tried to reboot before to use it a another time ?
But I think that it's a problem with your touchscreen. So the best you can do, it's to send it back to HTC

This is definitely a digitizer defect. Only fix is to replace the glass/digitizer. Send it back to HTC as soon as possible because it will only get worse over time. I had the same problem with my one X
Sent from my HTC One using xda app-developers app

I have the same problem; RMA time it seems. I am a bit worried if they will accept it under warranty or not, because I unlocked the bootloader .

strumf666 said:
I have the same problem; RMA time it seems. I am a bit worried if they will accept it under warranty or not, because I unlocked the bootloader .
Click to expand...
Click to collapse
Did you find out if it can be replaced under warranty if you unlock your boot loader? I also have the exact same problem on mine the top part of my screen which has a completely bunked touch sensor it goes nuts if used touch anywhere near the top of the phone..
But like you I unlocked my boot loader and installed quite a few different roms thinking it would solve the problem… I am wondering if there is a way to relock the boot loader and make it look like it never happened? Although I doubt it because they probably have the information about the phone at HTC since they sent me the token to unlock it..

Well, apparently there isn't much you can do if you are on hboot 1.54 (like me), since you need to be s-off to erase the *tampered* flag if you just relock it will stay.
I didn't send it for repairs yet, but I will report when I do.

Hello guys,
i've got the same problem, my phone just started to act very wired, my top part of the display is not responsible, seems part of touchscreen is broken. Have you solved it somehow or you applied for warranty.
the same situation -bootloader unlocked and flashed different roms, I'm S ON, so can't flash RUU to see if it's software problem or HW

Did you brought it back to HTC? Since today im having the same problem.. Same for me, unlocked. Guess I'll have to pay

AndyLeJizm said:
Did you brought it back to HTC? Since today im having the same problem.. Same for me, unlocked. Guess I'll have to pay
Click to expand...
Click to collapse
not yet, i still believe someone will come with s off and then i can apply for warranty

Spartn said:
not yet, i still believe someone will come with s off and then i can apply for warranty
Click to expand...
Click to collapse
Okay so I am a total idiot I think haha. I am on s-off. Could I revert everything to stock? (including the bootloader not saying the relocked warning)
Sent from my HTC One using xda app-developers app

AndyLeJizm said:
Okay so I am a total idiot I think haha. I am on s-off. Could I revert everything to stock? (including the bootloader not saying the relocked warning)
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
yes, you can simply revert everything back to stock, btw please do so asap, i'm really interested in if the stock will solve the problem with touchscreen, best would be if you flash RUU, please let me know the result

Spartn said:
yes, you can simply revert everything back to stock, btw please do so asap, i'm really interested in if the stock will solve the problem with touchscreen, best would be if you flash RUU, please let me know the result
Click to expand...
Click to collapse
Yes I will report back when I flashed RUU. I'm pretty 100% this will not solve the problem but it's worth the try.
I'm also really struggling if I should it send back to HTC or not, I have this feeling they will flash my Hboot to 1.54 so newer customers can't get their hands on S-Off. A local telephone repair-dudey could fix my screen for 170 euro which is a pretty good deal.
I Sent HTC an e-mail with the current situation and still waiting for a reply, will report the whole story back

Spartn said:
yes, you can simply revert everything back to stock, btw please do so asap, i'm really interested in if the stock will solve the problem with touchscreen, best would be if you flash RUU, please let me know the result
Click to expand...
Click to collapse
Okay I flashed RUU but with no avail. Im still having a line in my screen that doesnt work! I'm thinking of just letting it repair by the local telephone guy. HTC here in the netherlands work with an external company called Dynafix which will take about 3-4 weeks of time to repair it, and I'm also afraid that they will upgrade my hboot to 1.54 so I will lose the ability to s-off. (Not 100% sure, but just feeling it)
I hope you have enough information, we're both screwed without replacing a digitizer.. oh well, karma will strike back someday

They won't put you back to s-on, read in another thread that some phones ship with s-off and htc do not have any way of knowing who set the flag to off
Sent from my HTC One using xda app-developers app

HTC should replace your ones under warranty regardless of bootloader/soff. It is a physical hardware issue and has nothing to do with the software on the phone.
Sent from the one and only HTC One

AndyLeJizm said:
Okay I flashed RUU but with no avail. Im still having a line in my screen that doesnt work! I'm thinking of just letting it repair by the local telephone guy. HTC here in the netherlands work with an external company called Dynafix which will take about 3-4 weeks of time to repair it, and I'm also afraid that they will upgrade my hboot to 1.54 so I will lose the ability to s-off. (Not 100% sure, but just feeling it)
I hope you have enough information, we're both screwed without replacing a digitizer.. oh well, karma will strike back someday
Click to expand...
Click to collapse
not good news, i was hoping that the problem might be fixed once RUU is flashed at least we know that repair center is the only option here
i would suggest to send the phone to HTC, better than to give it to someone to fix it, this phone is quite complicated when speaking about opening, but up to u and i think u will get a new phone if u send it to htc repair center... so no signs that the phone was opened etc.. up to u, the same with my phone, if i apply for warranty i will have to wait about 30 days, but for now no go without LOCKED and TEMPERED removed..
if i had to apply for warranty with tempered...no s off in upcoming few months, i will arrgue with HTC that screen HW itself doesn';t have anything with software, even if there would be status "hahaha htc" and not unlocked i will not pay for their crap more money

Well I have really no idea what happened but the phone decided to fix itself and I no longer have digitizer problems anymore.. So far its working (for over more then 8 hours already).
But yeah, you are right, it's probably better to bring it to HTC then a local repair shop when it get's broken again.
Well that's that, I really hope your phone kicks back to it's normal state aswell!! (I received an email regarding my issue and they said a factory reset would help, I doubt it though.. flashed a RUU and the problem was still there)

Same Problem ( is it HW or SW )
hello guys , i have the same problem as shown in the pic attached
i made HTC secret code and the Line Drawing test shows the problem well
, i made hard reset but still the same ,
i bought the phone from Amazon.com USA and now am in egypt
dont know if i can send it to HTC support
btw the problem time is unstable , sometimes working fine and other becoming weird any help ?
UPDATE : after contacting HTC support they replied to me with the below :
'' Thank you for your email regarding your HTC device. I apologize for the issues you have experienced with the device functionality, Mohamed.
There are a number of reasons that your device could be having this issue. It can be caused by an application, task killers, or software issues. To determine which one, we will need to put the phone in safe mode. Safe mode is a method that allows the device to run without non-essential applications.
Press and hold the power button until the power menu comes up then press and hold on the Power off option and pop up will come up with the option to reboot into safe mode.
After you put it in Safe Mode, try using it without third party applications for a at least 24 hours to see how the device works. If it does not have this issue, then it is one of your applications. Try adding them back one at a time to see which one is responsible.
If the issues still persist please contact HTC repairs: HTC RMA Center, 1-866-449-8358 8AM - 1AM ET 7 days a week. That way you can go through the repair process as it is a little complex and we would need to speak to you on the phone to setup the repair ticket.
If you have any other questions about your device please feel free to contact us via email at any time.''
i tried it but still the same , i think it is hardware issue :'(

Can anyone confirm whether this S-OFF software can re-lock the bootloader and make it look like the warranty is still intact ? I need to send my phone back to HTC for a new digitizer stat

Yeah it's possible. Here's a guide for you: http://www.htc1guru.com/guides/return-stock-guide/

[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

[Q] ATT HTC One, Non-Rooted, No Issues Suddenly Non-Responsive in HSUSB-QLoader

Hey all,
I've had an HTC One M7 from ATT for a year and two days. I know it it is that time, because I according to ATT and HTC, it's my problem now because my warranty and insurance expired.
It has been a wonderful phone. I have not rooted it or ran any non-Play Store apps. I have not dropped it or exposed it to water. It was working normally, and sitting at 70%, when it powered down.
Power button and holding it down didn't do anything. No response from being plugged in. I ran through power+up vol, then power+down vol, then power+up vol+down vol (for five minutes). I will let it charge all tonight, but I don't know if that will do anything.
When plugged into my computer, it registers as "Qualcomm HS-USB QDLoader 9008 (COM5)," which from what I read, is the sign of a hardbrick.
I am currently abroad and don't know if I will be able to find a JTAB (from what I gather, that can help). Are there ANY other ideas of how to get this phone running again? It happened so randomly, I can't imagine that the HW would suddenly die; it must be SW.
My only thought is that it doesn't like the HTC European charger, and it Borked the charge data. But HTC Tech Support said as it was OEM, there shouldn't be any problem.
A few important work SMS and the phone number of a date I was in the process of confirming with are on this phone. Please help.
Heartfelt thanks,
vorwarnung

vorwarnung said:
Hey all,
I've had an HTC One M7 from ATT for a year and two days. I know it it is that time, because I according to ATT and HTC, it's my problem now because my warranty and insurance expired.
It has been a wonderful phone. I have not rooted it or ran any non-Play Store apps. I have not dropped it or exposed it to water. It was working normally, and sitting at 70%, when it powered down.
Power button and holding it down didn't do anything. No response from being plugged in. I ran through power+up vol, then power+down vol, then power+up vol+down vol (for five minutes). I will let it charge all tonight, but I don't know if that will do anything.
When plugged into my computer, it registers as "Qualcomm HS-USB QDLoader 9008 (COM5)," which from what I read, is the sign of a hardbrick.
I am currently abroad and don't know if I will be able to find a JTAB (from what I gather, that can help). Are there ANY other ideas of how to get this phone running again? It happened so randomly, I can't imagine that the HW would suddenly die; it must be SW.
My only thought is that it doesn't like the HTC European charger, and it Borked the charge data. But HTC Tech Support said as it was OEM, there shouldn't be any problem.
A few important work SMS and the phone number of a date I was in the process of confirming with are on this phone. Please help.
Heartfelt thanks,
vorwarnung
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2770684

alray said:
http://forum.xda-developers.com/showthread.php?t=2770684
Click to expand...
Click to collapse
Thank you for the suggestion!
I'm not experienced with tools like this. My device is not-rooted, and I cannot tell if it is powered on or off. Will this tool still work?

vorwarnung said:
Thank you for the suggestion!
I'm not experienced with tools like this. My device is not-rooted, and I cannot tell if it is powered on or off. Will this tool still work?
Click to expand...
Click to collapse
your phone is bricked, this tool is the only known way to recover from qhusb_dload mode, read the guide carefully and follow instructions.
the only other way out of this is to send your phone to htc so the can replace the motherboard.

alray said:
your phone is bricked, this tool is the only known way to recover from qhusb_dload mode, read the guide carefully and follow instructions.
the only other way out of this is to send your phone to htc so the can replace the motherboard.
Click to expand...
Click to collapse
This just happens without any signs or warning? I feel like a critical software problem like this would be taken care of in debug. The only change to my phone was an OTA to Sense 6 two weeks ago, but it hasn't had any problems software or otherwise. Sure looks like HTC screwed me over with this one.

vorwarnung said:
This just happens without any signs or warning? I feel like a critical software problem like this would be taken care of in debug. The only change to my phone was an OTA to Sense 6 two weeks ago, but it hasn't had any problems software or otherwise. Sure looks like HTC screwed me over with this one.
Click to expand...
Click to collapse
It happened to me also after a firmware update ...the link he posted saved my One !!!

vorwarnung said:
This just happens without any signs or warning? I feel like a critical software problem like this would be taken care of in debug. The only change to my phone was an OTA to Sense 6 two weeks ago, but it hasn't had any problems software or otherwise. Sure looks like HTC screwed me over with this one.
Click to expand...
Click to collapse
QHSUSB_DLOAD = Dead phone, either because of hardware defect or because a firmware incompatibility
option 1: follow the guide to revive your phone, if it doesn't work
option 2: send the phone to htc for repair.
option 3: there is no other options!
---------- Post added at 07:36 PM ---------- Previous post was at 07:34 PM ----------
clsA said:
It happened to me also after a firmware update ...the link he posted saved my One !!!
Click to expand...
Click to collapse
this guy (dexter) did an awesome work

clsA said:
It happened to me also after a firmware update ...the link he posted saved my One !!!
Click to expand...
Click to collapse
I suppose it's wishful thinking to assume that I'll keep any data on the phone, eh? I had to turn off my backup while I'm studying abroad, so I have about two months worth of contacts and photos to lose. Aw, well. Thanks for telling me about your experience!

vorwarnung said:
I suppose it's wishful thinking to assume that I'll keep any data on the phone, eh? I had to turn off my backup while I'm studying abroad, so I have about two months worth of contacts and photos to lose. Aw, well. Thanks for telling me about your experience!
Click to expand...
Click to collapse
unfortunately, there is no way to transfer data from your phone in qhsusb_dload mode
sorry

vorwarnung said:
I suppose it's wishful thinking to assume that I'll keep any data on the phone, eh? I had to turn off my backup while I'm studying abroad, so I have about two months worth of contacts and photos to lose. Aw, well. Thanks for telling me about your experience!
Click to expand...
Click to collapse
The fix was all in firmware I don't remember loosing anything in the process ...it was like a Miracle happened

clsA said:
The fix was all in firmware I don't remember loosing anything in the process ...it was like a Miracle happened
Click to expand...
Click to collapse
In your experience with this, can you run it in a virtualbox? I can see my device, and it's recognized as it should within Ubuntu and Fedora (both virtual), but the .sh can't seem to locate my phone. Since it is pulling the correct code, I can assume it is not a hardware issue.
I'm sorry if you're not qualified to answer this question, but being new, it won't let me post in Dexter's thread.
Thanks!

vorwarnung said:
In your experience with this, can you run it in a virtualbox? I can see my device, and it's recognized as it should within Ubuntu and Fedora (both virtual), but the .sh can't seem to locate my phone. Since it is pulling the correct code, I can assume it is not a hardware issue.
I'm sorry if you're not qualified to answer this question, but being new, it won't let me post in Dexter's thread.
Thanks!
Click to expand...
Click to collapse
I just used an Ubuntu live CD
Sent from my LG-E970 using Tapatalk

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: