Database Develop

Friend's "Dead" Phone Problem

Hey everyone,
My friend came across an unfortunate problem with his HTC One. This is what happened according to him:
For the past few months the battery life was getting worse and became terrible, but it's been otherwise fine in terms of performance.
He was at work playing some music via aux
The song stopped playing unexpectedly
Figured that it was a problem with YouTube was like wtf, so he closed YouTube and tried reloading.
It wouldn't show anything and nothing worked, left it that way as to not mess it up more.
Then it completely froze and he shut it off
Not it wont turn back on at all.
He said he left it plugged in charging for a while, still nothing. Tried overnight, still nothing.
Says he really wants to get at least his pictures out of his phone.
So, what are some troubleshooting steps he can take, or what can he do?

suckafoola said:
Hey everyone,
My friend came across an unfortunate problem with his HTC One. This is what happened according to him:
For the past few months the battery life was getting worse and became terrible, but it's been otherwise fine in terms of performance.
He was at work playing some music via aux
The song stopped playing unexpectedly
Figured that it was a problem with YouTube was like wtf, so he closed YouTube and tried reloading.
It wouldn't show anything and nothing worked, left it that way as to not mess it up more.
Then it completely froze and he shut it off
Not it wont turn back on at all.
He said he left it plugged in charging for a while, still nothing. Tried overnight, still nothing.
Says he really wants to get at least his pictures out of his phone.
So, what are some troubleshooting steps he can take, or what can he do?
Click to expand...
Click to collapse
try to boot the phone while shinning a bright light to the light sensor. (this is protection to avoid booting the phone when its in your pocket)
Press and hold Power and Volume down for at least 30 sec
Connect the phone to a Windows computer using the original usb cable (or any other cable already known to work for data transfer) to a USB 2.0 port on your computer, then go to Windows devices manger, is the device detected as QHSUSB ? Or Qualcomm something?

Hi thanks for the reply.
He said that when he plugged into his PC, QHUSB_DLOAD shows up in device manager. So now what?

suckafoola said:
Hi thanks for the reply.
He said that when he plugged into his PC, QHUSB_DLOAD shows up in device manager. So now what?
Click to expand...
Click to collapse
Since the phone went in QHUSB_DLOAD by itself and randomly, this is an hardware failure, the phone will need a new motherboard. It would be fixable only if the phone went in this mode directly after flashing a (incompatible) firmware. Unfortunately there is no way to recover the data from it since the emmc is soldered on that defective board.
Sorry

Wow damn that's real bummer... so there really isn't anything he could do? I remember him telling me that he wanted to salvage pictures from his graduation, but this problem is not letting him

suckafoola said:
so there really isn't anything he could do?
Click to expand...
Click to collapse
Unfortunately no. Another perfect example why you must backup your important files regularly. Smartphones are unreliable for preserving data, they are not made to last very long (well like everything nowadays ).
I already heard of someone desoldering his emmc chip (not from a M7 btw) and soldering it back to other hardware to extract the data so this is not impossible but your friend would have to find someone really qualified to try this kind of thing and it will probably not be cheap if it can be done..... But no there is no conventional method (using your computer and a usb cable) to extract any data from this phone.

@alray I know it sounds silly, but would it be possibly to save the pics by booting into twrp and copying them to a USB otg?
I'm guessing no
And yeah, it's always a bad idea to keep important files and data on one device.. be it a USB flash drive, an external hdd, a laptop, a smartphone.... etc
there's always the chance of it refusing to work or getting stolen.

monrokhoury said:
@alray I know it sounds silly, but would it be possibly to save the pics by booting into twrp and copying them to a USB otg?
I'm guessing no
And yeah, it's always a bad idea to keep important files and data on one device.. be it a USB flash drive, an external hdd, a laptop, a smartphone.... etc
there's always the chance of it refusing to work or getting stolen.
Click to expand...
Click to collapse
how are you supposed to go in twrp if the phone is stuck in qhusb_dload (qhusb_dload = phone not even booting in bootloader = dead).
Sent from my HTC One using XDA Labs

alray said:
how are you supposed to go in twrp if the phone is stuck in qhusb_dload (qhusb_dload = phone not even booting in bootloader = dead).
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
What if it says qualcomm something?
Shining a light method doesnt work, i left it charging for 3 days, nothing, i tried connecting it to computer and turning on, but not working...

boleguc said:
What if it says qualcomm something?
Shining a light method doesnt work, i left it charging for 3 days, nothing, i tried connecting it to computer and turning on, but not working...
Click to expand...
Click to collapse
Doesn't matters what it's saying exactly, it's dead. It's only possible to unbrick a m7 that went in a "Qualcomm something" mode because of a bad firmware flash. If it went in that mode itself, without flashing, your phone is dead.
Sent from my HTC One using XDA Labs

alray said:
how are you supposed to go in twrp if the phone is stuck in qhusb_dload (qhusb_dload = phone not even booting in bootloader = dead).
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
Yeah I expected that lol

**Help needed with no charge and the lacklustre help not given via MAZE(Alpha 4gig)**

Hi guys, been a bit out of the loop (hospital) but bought an Alpha around sep last year...within 2 months i used a official Maze update (OTA) and it then no longer charges...got onto them via facebook (as there were no official threads for this phone back then) and they sent me this to reflash it...
http://www.mazemobile.com/download-center
The ROM used to be there, but they have the ****ing cheek to say "people tried to flash and blamed MAZE" now it was MAZE's update in the first place that buggered my phone.:silly:..i still have the original ROM...
https://drive.google.com/drive/folders/0B8XLZxEJR8albndMcXJhWGtlVDQ
^not sure if that works for you, but basically it was..
:A really crap tutorial
:Maze Alpha flash tool.zip
:Maze_Alpha_V05_20170816
I've followed everything by the letter to no avail???
Now MAZE are bloody useless, can i count on one of you clever chaps to help me out?
P.s it's the 4 gig model.
Many thanks lads...

Any joy?
Is there anybody on here that had the same problem? You guys are usually really helpful, as i'm getting no rsponse from MAZE i thought i'd try where the true tech heads reside (i've received help before on my Xioami phones and smartwatches before) or is it that not many people have bothered with this phone? please help a guy out...much appreciated.

seedaripper said:
Is there anybody on here that had the same problem? You guys are usually really helpful, as i'm getting no rsponse from MAZE i thought i'd try where the true tech heads reside (i've received help before on my Xioami phones and smartwatches before) or is it that not many people have bothered with this phone? please help a guy out...much appreciated.
Click to expand...
Click to collapse
Well the thing is that you need to provide a bit more info. 'I've followed everything by the letter to no avail???' But you are not telling what works or not or what step you are stuck in the manual.
A lot of things come to my mind.
- is it still booting
- did you try another cable - charger
- ...
If it still boots and works a bit can you connect it to a pc and access for example the internal memory etc?
Some more info would be of help to get response... although I find the Maze Alpha part of the forum a lot of read and very little help (a bit of ranting may wake up people)

Cheers...someone lives!
Thanks for responding lukesan (much appreciated)
I'm using the original charger, it was working fine until i got the OTA so i doubt that's the problem.
No it doesn't boot (there is just enough charge to get to recovery mode,fastboot mode,normal boot)
I followed the manual/flash/tool etc (does the google drive doc show up for you as posted above?) everything seemed to go fine...but the problem still persists, it just wont charge?
Maybe i need a new ROM (or it could be the tool MAZE sent me) they are ****ing useless and i've started a bit of a social media campaign against them
(at first they were keeping in touch, but now they just ignore me completely on facebook) it pisses me off no end:crying:
P.s it does connect to my PC (sometimes), where should i dig around?
lukesan said:
Well the thing is that you need to provide a bit more info. 'I've followed everything by the letter to no avail???' But you are not telling what works or not or what step you are stuck in the manual.
A lot of things come to my mind.
- is it still booting
- did you try another cable - charger
- ...
If it still boots and works a bit can you connect it to a pc and access for example the internal memory etc?
Some more info would be of help to get response... although I find the Maze Alpha part of the forum a lot of read and very little help (a bit of ranting may wake up people)
Click to expand...
Click to collapse

seedaripper said:
Thanks for responding lukesan (much appreciated)
I'm using the original charger, it was working fine until i got the OTA so i doubt that's the problem.
No it doesn't boot (there is just enough charge to get to recovery mode,fastboot mode,normal boot)
I followed the manual/flash/tool etc (does the google drive doc show up for you as posted above?) everything seemed to go fine...but the problem still persists, it just wont charge?
Maybe i need a new ROM (or it could be the tool MAZE sent me) they are ****ing useless and i've started a bit of a social media campaign against them
(at first they were keeping in touch, but now they just ignore me completely on facebook) it pisses me off no end:crying:
P.s it does connect to my PC (sometimes), where should i dig around?
Click to expand...
Click to collapse
Just checked, and yes it is the correct manual. But lets say that even me, a veteran (with no patience), had issues with it. It is 100% correct but ... well see later on where you get.
Ok, first couple of things come up in my mind. Could still be the cable, the charger or even the the charging port that is broken. Been in the electronics business since the late 80's and these things can go wrong or broken any minute even thinking that a firmware update caused it.
Charger you can easily check if you just connect it to another charger or a pc usb port. A PC usb port will only deliver (mostly) max 400mA to 500mA .. meaning it will charge, if it still does, extremely slow. So I would keep it connected to a pc all day long or night before trying to switch it on. Trying to switch it on during charging and batt at low level will probably not work. You could try to power on after 2 or 3 hours or so and if it powers on then I would power it off again to get at least some juice in it to play around.
Cable, I would go fetch another one, they will come in handy in the future too. If it doesn't fit properly because the port is to deep in the Alpha then just take a knife and carefully cut a very small piece of the plastic, just 1mm is enough. I've done this on the 2 extra cables I have here and it works perfectly and I don't even see it aesthetically so no harm done on mine.
Now if that still doesn't work we can try the next step. But be very careful to know that that will delete all data, pictures, etc off of the phone. Because of all my toying with this phone I stuck an sd-card in it and doing a backup before I play with it again.
The manual states that you have to press the volume up button.. Well you can already test that without hurting anything as long you don't press anything on the flashtool. So only volume up and then insert the usb cable to a pc. Now the mistake I made in the beginning was to also push the power button.
So on the pc open up your device manager. If you do volume up (not in any of the other modes like fastboot etc, so from a standpoint that the phone is completely off) hold it for 2 or 3 sec and plug it into the PC. Now you should hear the typical usb connection sound and see something happening like an extra device in the manager. Probably you do not have the correct drivers installed for starters. Look for mtk drivers for your OS. Be careful, a lot of crap and virus links out there.
Now another issue that I fell for the first time is that you have to connect it twice like that to the pc to actually flash. First time ... press the 'scan' and let it do it (think the top field will become green) and then disconnect the phone and do the same volume up and connect and then it will allow you to flash.
But first check what is happening before we have to flash it.
Btw I know about their attitude. Well, as a Chinese company they must understand that by this attitude they will not going to sell any products anymore. I only bought mine because it was a special deal and I wanted to test an MTK chipset. They never replied to me why there is no real fast charge on it etc.
I also very very highly recommend you to invest, well for the price of a sandwich, to buy a usb charging doctor which will allow you to see the voltage and current. You don't need to be a doctor to us it and at least you see something instead of having to guess. Also while you are at it buy good quality chargers and a couple of cables. They will always come in handy and take some of the guesswork away if needed.

Top lad.
Again many thanks luksan (hefty bit of typing you did there mate )
I very much doubt it's the charger (i was extremely careful everytime with insertion) or port for that matter...this is the only USB-C i have (everything else is old school micro USB) and i resent forking out more money (the original trader Cafago said to send it back tracked at my own cost...£60!!!)
i'd like to try and fix the bastard and then sell it, never to return
Again, all these probs literally appeared after i did the OTA (i doubt it was coincidence)
i do like your advice on the re-doing the flash twice, so i may give that a go...bloody nora, what a pain in the arse!
Thanks for being a voice in the void pal...
See
lukesan said:
Just checked, and yes it is the correct manual. But lets say that even me, a veteran (with no patience), had issues with it. It is 100% correct but ... well see later on where you get.
Ok, first couple of things come up in my mind. Could still be the cable, the charger or even the the charging port that is broken. Been in the electronics business since the late 80's and these things can go wrong or broken any minute even thinking that a firmware update caused it.
So on the pc open up your device manager. If you do volume up (not in any of the other modes like fastboot etc, so from a standpoint that the phone is completely off) hold it for 2 or 3 sec and plug it into the PC. Now you should hear the typical usb connection sound and see something happening like an extra device in the manager. Probably you do not have the correct drivers installed for starters. Look for mtk drivers for your OS. Be careful, a lot of crap and virus links out there.
Now another issue that I fell for the first time is that you have to connect it twice like that to the pc to actually flash. First time ... press the 'scan' and let it do it (think the top field will become green) and then disconnect the phone and do the same volume up and connect and then it will allow you to flash.
But first check what is happening before we have to flash it.
.
Click to expand...
Click to collapse

seedaripper said:
Again many thanks luksan (hefty bit of typing you did there mate )
I very much doubt it's the charger (i was extremely careful everytime with insertion) or port for that matter...this is the only USB-C i have (everything else is old school micro USB) and i resent forking out more money (the original trader Cafago said to send it back tracked at my own cost...£60!!!)
i'd like to try and fix the bastard and then sell it, never to return
Again, all these probs literally appeared after i did the OTA (i doubt it was coincidence)
i do like your advice on the re-doing the flash twice, so i may give that a go...bloody nora, what a pain in the arse!
Thanks for being a voice in the void pal...
See
Click to expand...
Click to collapse
Well don't flash it twice. You have to put it in that mode twice to start it to complete the procedure. I do not believe in the wipe it 3 times to be sure, turn around and jump to make it better or faster. Loads of voodoo that is not scientifically proven around. It's all about a 0 and a 1, there is nothing in between that.
But .£60 to send that charger, LOL.
A month ago I bought an Aukey charger that included a USB-C cable for like .£12 including shipping to Belgium. (well just followed the rain and snow and landed here)
Let us know what happens next.

Any update on what you did?

GAH!
Yes, i've just tried everything again...nothing seems to work? when i actually start the tool i get a number of errors (including scatter?) then the tool boots, i then go through the broken english bollocks of the 'guide' again, do everything and it still doesn't work?? listen man, could you do me a massive favour...just outline the steps (bullet point wise) on what to do? no chatting about the chinese or voodoo
just nice clear as day steps, because as it stands i'm going to have to pay £70 just to send this piece of **** back (and probably wont get a full refund)
If you could do that (and i mean laymans terms here) i'd be forever grateful...
Cheers bud.:good::good:
lukesan said:
Any update on what you did?
Click to expand...
Click to collapse

seedaripper said:
Yes, i've just tried everything again...nothing seems to work? when i actually start the tool i get a number of errors (including scatter?) then the tool boots, i then go through the broken english bollocks of the 'guide' again, do everything and it still doesn't work?? listen man, could you do me a massive favour...just outline the steps (bullet point wise) on what to do? no chatting about the chinese or voodoo
just nice clear as day steps, because as it stands i'm going to have to pay £70 just to send this piece of **** back (and probably wont get a full refund)
If you could do that (and i mean laymans terms here) i'd be forever grateful...
Cheers bud.:good::good:
Click to expand...
Click to collapse
But what about the drivers etc.... What shows up?

ROM?
lukesan said:
Any update on what you did?
Click to expand...
Click to collapse
Perhaps it's the ROM? any chance you could give me the latest version? (or a link) i keep getting error in the light green field (FAIL) on the Tool?
I'm not sure if it's the tool or the bloody ROM?
As usual not a sodding dicky bird from MAZE (emails,twitter facebook etc) what a sh!tty company...

Nothing shows up...i think the first time i tried to plug it into the PC it ran a scan,(i don't think it found the drivers, as it doesnt show up on my computer :running win 7) from there on in, nothing? it also makes the mandatory PC sound bleep when plugged in, then about a second later i get the discharge bleep? (not sure if this is lack of charge) if i had a frigging phone i'd post screenshots! damned if i do, damned if i don't!
lukesan said:
But what about the drivers etc.... What shows up?
Click to expand...
Click to collapse

seedaripper said:
Nothing shows up...i think the first time i tried to plug it into the PC it ran a scan,(i don't think it found the drivers, as it doesnt show up on my computer :running win 7) from there on in, nothing? it also makes the mandatory PC sound bleep when plugged in, then about a second later i get the discharge bleep? (not sure if this is lack of charge) if i had a frigging phone i'd post screenshots! damned if i do, damned if i don't!
Click to expand...
Click to collapse
Well if it hasn't gotten the correct drivers it will never ever be able to flash. It's like trying to use your house keys to start your car.
I see all kinds of stuff happening if you keep the device manager open. Open up the 'ports' (com & lpt) section. Now press the 'volume up' key for a second or 2 and then connect it to a usb port while holding the key.. release it like a second later when it is connected to the port. Now you should see some stuff happening. Just did it on my win10 machine but should be pretty similar on a win7. One of them says first 'mtk usb' and then 'preloader usb vcom' . If these don't show up then look no further for now.

seedaripper said:
Perhaps it's the ROM? any chance you could give me the latest version? (or a link) i keep getting error in the light green field (FAIL) on the Tool?
I'm not sure if it's the tool or the bloody ROM?
As usual not a sodding dicky bird from MAZE (emails,twitter facebook etc) what a sh!tty company...
Click to expand...
Click to collapse
Have you tried my backup here ?
Flash TWRP using fastboot method and then boot into TWRP and do a restore with the backup I provide for Maze Alpha 4/64

dreambo said:
Have you tried my backup here ?
Flash TWRP using fastboot method and then boot into TWRP and do a restore with the backup I provide for Maze Alpha 4/64
Click to expand...
Click to collapse
His device doesn't charge and his battery is flat so I guess his by the time he can flash the device dies anyway.

er?
lukesan said:
Well if it hasn't gotten the correct drivers it will never ever be able to flash. It's like trying to use your house keys to start your car.
I see all kinds of stuff happening if you keep the device manager open. Open up the 'ports' (com & lpt) section. Now press the 'volume up' key for a second or 2 and then connect it to a usb port while holding the key.. release it like a second later when it is connected to the port. Now you should see some stuff happening. Just did it on my win10 machine but should be pretty similar on a win7. One of them says first 'mtk usb' and then 'preloader usb vcom' . If these don't show up then look no further for now.
Click to expand...
Click to collapse
Ok, did that for a split second 'media TEK preloader USB VCOM (android) (COM4)' flashes up, i managed to click on it quickly and got to mediatek properties...then went to update driver (it searched the net and found it) all this time after the original insertion, literally a second after it just disconnects? (and it doesn't show up in my computer) i get this as device status.....
Currently, this hardware device is not connected to the computer. (Code 45)
To fix this problem, reconnect this hardware device to the computer.
I plug it back in, it says normal, then a second later the above message? any ideas?

lukesan said:
His device doesn't charge and his battery is flat so I guess his by the time he can flash the device dies anyway.
Click to expand...
Click to collapse
Yep, when i try to power on i have a split second of the MAZE logo, then back to death...i Can leave it charging and i get the wobble liquid battery graphic, but it never goes above 0%, as explained this only happened after a firmware update (#dreambo)

Can't get my head round multi quote?
dreambo said:
Have you tried my backup here ?
Flash TWRP using fastboot method and then boot into TWRP and do a restore with the backup I provide for Maze Alpha 4/64
Click to expand...
Click to collapse
Yep, when i try to power on i have a split second of the MAZE logo, then back to death...i Can leave it charging and i get the wobble liquid battery graphic, but it never goes above 0%, as explained this only happened after a firmware update (#dreambo)

seedaripper said:
Ok, did that for a split second 'media TEK preloader USB VCOM (android) (COM4)' flashes up, i managed to click on it quickly and got to mediatek properties...then went to update driver (it searched the net and found it) all this time after the original insertion, literally a second after it just disconnects? (and it doesn't show up in my computer) i get this as device status.....
Currently, this hardware device is not connected to the computer. (Code 45)
To fix this problem, reconnect this hardware device to the computer.
I plug it back in, it says normal, then a second later the above message? any ideas?
Click to expand...
Click to collapse
Mmm, if you see the preloader thing then I guess that is ok. ... it is no longer an 'unknown device' which sounds fine to me. Let me quickly test on my Maze for a sec. (will edit this post).
It is normal that it disconnects. My guess is that it tries to setup comms between device and something on the pc where it can talk to. If there is no communication then it just powers down again. The display etc will all stay off since it directly does the comms to the cpu and the ram. Sort of write only state. So it is a very low level form of programming. Can be scary for people because you see nothing happening on the phone during that process.
Ok just tested again.. Can you do step 1 to 5 in the manual without an error? (to be sure I would right-click on the exe and run it as administrator to start that program)
Till that step 5 no connection to the Alpha is needed. In step 5 if you have pressed 'scan' it should say something like resetting comm ports and only the 'stop all' should be clickable.
If we are that far then I guess we are a step further.
Give that a try and then we'll see for the next step.

lukesan said:
Mmm, if you see the preloader thing then I guess that is ok. ... it is no longer an 'unknown device' which sounds fine to me. Let me quickly test on my Maze for a sec. (will edit this post).
It is normal that it disconnects. My guess is that it tries to setup comms between device and something on the pc where it can talk to. If there is no communication then it just powers down again. The display etc will all stay off since it directly does the comms to the cpu and the ram. Sort of write only state. So it is a very low level form of programming. Can be scary for people because you see nothing happening on the phone during that process.
Ok just tested again.. Can you do step 1 to 5 in the manual without an error? (to be sure I would right-click on the exe and run it as administrator to start that program)
Till that step 5 no connection to the Alpha is needed. In step 5 if you have pressed 'scan' it should say something like resetting comm ports and only the 'stop all' should be clickable.
If we are that far then I guess we are a step further.
Give that a try and then we'll see for the next step.
Click to expand...
Click to collapse
Pics ...hopefully...

Samsung Galaxy A71 died after updating to Android 11

Ok, so here is to explain what happened, so you can have a clue what am I talking about.
I bought Galaxy A71 a month ago (give or take), so out of the box it had Android 10. The phone was working flawlessly. Battery life awesome, pictures from camera great, etc. So, few days ago on March 26, 2021, an update to Android 11 came in. I am a tech nerd, I know about phones, rooting, flashing, etc.
So, I saw that I have around 78-80% of the battery so it was enough to download and install Android 11.
Downloading and installing and optimizing apps after went smooth as silk. I usually soft restarting my device after any software update, so I did that after the installation of Android 11 was entirely finished.
But, this is what happen when I restart my phone the normal way. I press and hold the power button, the dialog of Power off, Reset and Airplane mode came out, tapped twice the reset button and phone went restarting and just.... died. I remember that when I soft restarted my phone, the battery was on 72%. So I tried any trick in the books to turn on my phone again like combinations of pressing buttons, then with USB cable, charger, etc, but nothing was responsive. It's like the phone was clinically dead.
My phone is still under warranty and I will probably end up taking it to the T-mobile store, but the point of this thread is to inform others of the situation like mine and see if someone else had the same problem?
Maybe someone will post a solution what to do in situations like this?
If I find any solution, I will update this post with all the details.

You probably done it.But have you plugged it into A computer to see if the computer can detected it?

Essex_Hal said:
You probably done it.But have you plugged it into A computer to see if the computer can detected it?
Click to expand...
Click to collapse
Yes i did, nothing shows in Device Manager. As I said, I tried every possible trick to wake the phone up, but it was unsuccessful.
I end up taking it to the carrier store cuz it is still under warranty. They told me if they can't fix it, they'll probably give me a new one or to wait for Galaxy A72 To arrive in 2 weeks. We'll see what happens.

BorisMKD said:
Yes i did, nothing shows in Device Manager. As I said, I tried every possible trick to wake the phone up, but it was unsuccessful.
I end up taking it to the carrier store cuz it is still under warranty. They told me if they can't fix it, they'll probably give me a new one or to wait for Galaxy A72 To arrive in 2 weeks. We'll see what happens.
Click to expand...
Click to collapse
Least you still have A warranty to help you.
Good luck with it.Hope you don't lose your data if it's still on the phone.

Essex_Hal said:
Least you still have A warranty to help you.
Good luck with it.Hope you don't lose your data if it's still on the phone.
Click to expand...
Click to collapse
They fix it, it said it was software problem, got stuck on rebooting. I get it today (2 weeks later) and it worked. They managed to turn it on but without a factory reset, every app was there, every picture, video, contacts, call history, etc. I don't know how they did it, but they did. So when I got my phone back I tried to restart it normal way, long press of the power button, then tap Restart and again restart. The phone restart it without a problem. I was happy. Then later that day (2 hours ago when I'm writing this, I notice that always on display when i touch the phone screen will show up but doesn't switch off after 10 seconds (I set it up like that), instead it started to blink in intervals like i was touching the screen continuously. Then I did a deep soft reset. You know, when you press Volume down and Power button at the same time and.... got the same problem again. Phone is non functional, none combination of pressing buttons worked, just like i describe it in the OP. Just for information, I did the same on my previous phone Galaxy A7 2018 and never had this problem. I did it on this phone too, never had a problem. Then I remember it that on both phones when i do that and not having problems were running on Android 10. this phone now update it to Android 11 and that buttons combination is probably bricking the phone. It's just a thing I notice. So I am planning to call the official service that fixed the phone how did they do it, so maybe I can do it myself too. I don't want to wait for another 2 and a half weeks.

I am facing the same issue. And I think my warranty is out. Did you get to ask them how can you turn it on yourself!!
I would really appreciate some help here!

BorisMKD said:
Ok, so here is to explain what happened, so you can have a clue what am I talking about.
I bought Galaxy A71 a month ago (give or take), so out of the box it had Android 10. The phone was working flawlessly. Battery life awesome, pictures from camera great, etc. So, few days ago on March 26, 2021, an update to Android 11 came in. I am a tech nerd, I know about phones, rooting, flashing, etc.
So, I saw that I have around 78-80% of the battery so it was enough to download and install Android 11.
Downloading and installing and optimizing apps after went smooth as silk. I usually soft restarting my device after any software update, so I did that after the installation of Android 11 was entirely finished.
But, this is what happen when I restart my phone the normal way. I press and hold the power button, the dialog of Power off, Reset and Airplane mode came out, tapped twice the reset button and phone went restarting and just.... died. I remember that when I soft restarted my phone, the battery was on 72%. So I tried any trick in the books to turn on my phone again like combinations of pressing buttons, then with USB cable, charger, etc, but nothing was responsive. It's like the phone was clinically dead.
My phone is still under warranty and I will probably end up taking it to the T-mobile store, but the point of this thread is to inform others of the situation like mine and see if someone else had the same problem?
Maybe someone will post a solution what to do in situations like this?
If I find any solution, I will update this post with all the details.
Click to expand...
Click to collapse
have same issue too anyways to fix it?

My Google Pixel 4 XL Dead Overnight!

Hello XDA community yesterday I was using my pixel phone normally and it was working fine today morning I woke up to check time on my phone but my phone was dead, screen was completely pitch black, charging phone doesn't work screen stays dead, even its not going to bootloader it feels like phone is completely dead but when I connect it to pc I hear connection sound and a random pop up show that device is not detected etc. I searched on internet and it feels like when I was sleeping because my phone was on charging and WIFI was connected( normally I don't use WIFI I use mobile data) maybe a software update was installed which made phone software & drivers to get corrupted because nothing is working nor its charging, booting, vibrating its completely dead
I searched on internet and also installed QUALCOMM drivers on my pc that unknown popup while connecting while to pc shifted into
Qualcomm HS-USB QDLoader 9008
and I also get know that a firehose file can maybe fix my phone because maybe bootloader is corrupted or anything if anyone can help me in this matter I will really appreciate it. Thanks!

Noman8 said:
Hello XDA community yesterday I was using my pixel phone normally and it was working fine today morning I woke up to check time on my phone but my phone was dead, screen was completely pitch black, charging phone doesn't work screen stays dead, even its not going to bootloader it feels like phone is completely dead but when I connect it to pc I hear connection sound and a random pop up show that device is not detected etc. I searched on internet and it feels like when I was sleeping because my phone was on charging and WIFI was connected( normally I don't use WIFI I use mobile data) maybe a software update was installed which made phone software & drivers to get corrupted because nothing is working nor its charging, booting, vibrating its completely dead
I searched on internet and also installed QUALCOMM drivers on my pc that unknown popup while connecting while to pc shifted into
Qualcomm HS-USB QDLoader 9008
and I also get know that a firehose file can maybe fix my phone because maybe bootloader is corrupted or anything if anyone can help me in this matter I will really appreciate it. Thanks!
Click to expand...
Click to collapse
Did you try both
Google Pixel - Update and Software Repair
&
Android Flash Tool
flash.android.com
already?
Here is a guide on how to get ADB working:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
Do you have OEM Unlocking enabled? Maybe unlocked bootloader (if your bootloader is dead and you haven't unlocked it previously, there might not be much hope for you)? If you can't even get into recovery/fastboot mode, you are in deep.

Morgrain said:
Did you try both
Google Pixel - Update and Software Repair
&
Android Flash Tool
flash.android.com
already?
Here is a guide on how to get ADB working:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
Do you have OEM Unlocking enabled? Maybe unlocked bootloader (if your bootloader is dead and you haven't unlocked it previously, there might not be much hope for you)? If you can't even get into recovery/fastboot mode, you are in deep.
Click to expand...
Click to collapse
Yes i have tried both nothing is working my phone was fresh it wasn't rooted,its bootloader was locked it was basically working flawlessly as usual but today morning it was dead, bricked nothing is working,phone is not charging pressing power button and volume down does work when connecting to pc because i hear connection and disconnection sound but nothing shows up on the screen. Feels like phone is bricked or anything... Am not sure because i have not done any modifications to my phone i was using normally and its battery was also great idk what happened...

Noman8 said:
Yes i have tried both nothing is working my phone was fresh it wasn't rooted,its bootloader was locked it was basically working flawlessly as usual but today morning it was dead, bricked nothing is working,phone is not charging pressing power button and volume down does work when connecting to pc because i hear connection and disconnection sound but nothing shows up on the screen. Feels like phone is bricked or anything... Am not sure because i have not done any modifications to my phone i was using normally and its battery was also great idk what happened...
Click to expand...
Click to collapse
You might want to wait some time, until the battery runs out/depletes. Then try to charge it/start it. But that route will take a couple of days.

Noman8 said:
No my phone was fresh it wasn't rooted,its bootloader was locked it basically working flawlessly as usual but today morning it was dead, bricked nothing is working,phone is not charging pressing power button and volume down does work when connecting to pc because i head connection and disconnection sound but nothing shows up on the screen. Feels like phone is bricked or anything... Am not sure because i have not done any modifications to my phone i was using normally and its battery was also great idk what happened...
Click to expand...
Click to collapse
Morgrain said:
You might want to wait some time, until the battery runs out/depletes. Then try to charge it/start it. But that route will take a couple of days.
Click to expand...
Click to collapse
Ahan i see btw thanks for replying!

Noman8 said:
Qualcomm HS-USB QDLoader 9008
Click to expand...
Click to collapse
Yes, your pixel is now dead. Similar to what happened with my Pixel 2.

NinjaCoool said:
Yes, your pixel is now dead. Similar to what happened with my Pixel 2.
Click to expand...
Click to collapse
Yes

pixel4-XL_firehose - Google Drive
drive.google.com
This is the pixel 4 and 4 xl firehose

r1pp3d2 said:
pixel4-XL_firehose - Google Drive
drive.google.com
This is the pixel 4 and 4 xl firehose
Click to expand...
Click to collapse
hi brother can it be fixed with firehose? please reply
and what are exact steps to flash Firehose!

r1pp3d2 said:
pixel4-XL_firehose - Google Drive
drive.google.com
This is the pixel 4 and 4 xl firehose
Click to expand...
Click to collapse
i am trying to flash this firehose to my pixel but it is requiring 2 more files "RAW PROGRAM & PATCH" FILE if u can help me here i will appreciate that!

That would be the backup of the phone. These are not backups.

Hi, just lost my pixel 4 after an android security update .
It really looks like planned obsolescence, considering this is happening few months after warranty.
Like you i'm trying to find "raw program" and "patch file".
According this website, thoses files could be generated with a python script from a file named "GPT.bin" i'm actually looking for.
If anyone succeed to respawn, don't be shy and share please.

nicauderan said:
Hi, just lost my pixel 4 after an android security update .
It really looks like planned obsolescence, considering this is happening few months after warranty.
Like you i'm trying to find "raw program" and "patch file".
According this website, thoses files could be generated with a python script from a file named "GPT.bin" i'm actually looking for.
If anyone succeed to respawn, don't be shy and share please.
Click to expand...
Click to collapse
Google doesn't just kill phones like that. My Pixel 4XL is still find, hell my Nexus 6 still works.

nicauderan said:
Hi, just lost my pixel 4 after an android security update .
It really looks like planned obsolescence, considering this is happening few months after warranty.
Like you i'm trying to find "raw program" and "patch file".
According this website, thoses files could be generated with a python script from a file named "GPT.bin" i'm actually looking for.
If anyone succeed to respawn, don't be shy and share please.
Click to expand...
Click to collapse
You are not getting your pixel back now u can replace motherboard now like i did i ordered new motherboard from ali express and Replaced it!

Just received motherboard from Ali and the pixel respawned.

Was charging my pixel 4, it was 100% charged for a good few hours, I woke up around midnight and was playing a game on my phone when suddenly it went black. I unplugged the phone and tried a few fixes. After crying it out and leaving it uncharged I plugged it into my portable charger where the lights came on, still nothing on my phone. I also tried plugging into my computer and no sounds or any sign it had been plugged into my computer from both phone or computer. I was thinking if this is a battery issue it should at least do something on my computer right? I have tried again to plug it into my portable charger and this time no lights on the portable charger. Maybe this isn't the right thread but I figured I'd post here anyway, any suggestions, should I take it to a shop? I'm not tech savvy, could it be a display or battery issue or a motherboard issue like above?
also to note, I had both the front and back glass changed almost a year ago now, and except from one dead pixel on the screen from the original glass break its been fine.
Also to note, I recently moved from Australia to Canada and am using a plug converter that my laptop computer is also plugged into and its fine, so I'm thinking it wasn't a power surge? It has two usb ports and a Au plug on the same converter plug.

Oh, you are not alone. 3 days after Android 13 update, I woke up, my Pixel 4XL alarm went off, used Android Auto to go to work and listen to music, checked email on it at work, plugged it in to my Pixel approved charger/cable as always, picked it up hours later and .... brick. No response to charger plug/unplug even with various other plugs and cables. No response to 30 sec of pressing power or power with up/down volume combos. It was a brick, just like many other Pixel 2,3,4,5 owners reported after various updates over the years, courtesy of Qualcomm chips and Google's lack of quality checking chips. Today's lesson: Stop paying Google for trash. It happened to me 280 days after the warranty expired. Google said that if it was from the Android 13 update, I should take it to UbreakitIfixit near me and they will fix it under an extension of 1 year to the warranty. We'll see. Sadly, it will still have Google's low grade Qualcomm chip design after the repair.

Question [SOLVED] Pixel 7 Dead(?)

Was installing the new build using flash-all.sh (without wipe) as I was rooted with Magisk.
Installer got stuck halfway. Disconnected, tried booting, got an error message saying device may have been corrupted or something like that.
The phone doesn't boot at all now, not even to the bootloader. Literally nothing shows up on the screen.
Any help would be greatly appreciated.

Double-check your download and make sure you have panther for Pixel 7.
Depending on what is corrupted, it may be very difficult to recover. With Qualcomm SoCs you can use a low-level tool like QPST (Qualcomm Product Support Tool). For Exynos you can often use ODIN. For Pixel, ODIN doesn't work and there aren't any QPST files (prob never will be).
I don't know how it works on linux, but on Windows I open Device Manager and plug my phone in. Depending on what you see will determine next steps.

Hung0702 said:
Double-check your download and make sure you have panther for Pixel 7.
Click to expand...
Click to collapse
Yes, the images are for panther.
Hung0702 said:
I don't know how it works on linux, but on Windows I open Device Manager and plug my phone in. Depending on what you see will determine next steps.
Click to expand...
Click to collapse
It now doesn't show up on any system.
Even though the screen was off, the phone was probably on and it was a bit warm. So I let it stay like that and let the battery drain overnight. Today morning I tried various button combinations and it did show a low/empty battery icon for a second. Nothing really happened when I plugged it in to a charger. It did get warm, indicating the battery was probably getting charged, but nothing showed up on screen.

dewri21 said:
Yes, the images are for panther.
It now doesn't show up on any system.
Even though the screen was off, the phone was probably on and it was a bit warm. So I let it stay like that and let the battery drain overnight. Today morning I tried various button combinations and it did show a low/empty battery icon for a second. Nothing really happened when I plugged it in to a charger. It did get warm, indicating the battery was probably getting charged, but nothing showed up on screen.
Click to expand...
Click to collapse
Unfortunately your only option is repair. Find a Google certified repair center such as uBreakiFix. Your device should still be under warranty. The tools necessary to recover a device when the bootloader fails are not publicly available.

V0latyle said:
Unfortunately your only option is repair. Find a Google certified repair center such as uBreakiFix. Your device should still be under warranty. The tools necessary to recover a device when the bootloader fails are not publicly available.
Click to expand...
Click to collapse
I have had pixel phones disassembled and have hooked them up to the android flash tool and they were recognised , even though the screens were blank the tool knew what was connected. Its a shot it might beable to help .

hammered58 said:
I have had pixel phones disassembled and have hooked them up to the android flash tool and they were recognised , even though the screens were blank the tool knew what was connected. Its a shot it might beable to help .
Click to expand...
Click to collapse
The Android Flash Tool works via ADB, so if the bootloader is corrupted or fails for some reason, that isn't an option.
Pixel devices (at least Snapdragon ones) do have the Qualcomm USB mode, but Google's prescribed means of repair in this situation is to simply replace the mainboard; most repair stations do not have QPST or the necessary files to restore the bootloader.

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
I have not come across a pixel device that cannot be restore...Google basically made this phone indestructible from software stand point.
use the above link to restore phone.

In the future I would suggest removing magisk before updating, would save yourself a lot of trouble. Just backup your modules to a folder on your phone and you can get them back quickly

Is it possible for you to take a pic of what your phone says? I think i ran into a very similar situation but i was able to access fastboot, just want to see if it's the same error i got

Make sure that
1. The latest adb is saved to the folder you extracted the factory image file
2. There is enough disc drive space available
Then rerun the flashall.bat from that folder

dewri21 said:
Yes, the images are for panther.
It now doesn't show up on any system.
Even though the screen was off, the phone was probably on and it was a bit warm. So I let it stay like that and let the battery drain overnight. Today morning I tried various button combinations and it did show a low/empty battery icon for a second. Nothing really happened when I plugged it in to a charger. It did get warm, indicating the battery was probably getting charged, but nothing showed up on screen.
Click to expand...
Click to collapse
Yikes. I had that happen to two Pixel 5a phones.
They booted into Qualcomm mode. I checked windows device manager and saw that it was a device, using qcomm, and there is no way to repair this one was rooted, one wasn't rooted.
I ended up buying a pixel 6 and 7.
Also, I noticed this occurred during the monthly patch cycle.
There is no way to get into the bootloader, fastboot, recovery, or safe mode.
I hope that isn't the situation with the 7s as well.
Good luck, please post your findings!

Vio281 said:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
I have not come across a pixel device that cannot be restore...Google basically made this phone indestructible from software stand point.
use the above link to restore phone.
Click to expand...
Click to collapse
Not really. That’s how I broke it while updating. My phone wouldn’t boot at all and wasn’t even detected by my mac and windows pc. Had to send it to the service center.
t3chwizard said:
In the future I would suggest removing magisk before updating, would save yourself a lot of trouble. Just backup your modules to a folder on your phone and you can get them back quickly
Click to expand...
Click to collapse
Thanks, I will do that.
J0nhy said:
Is it possible for you to take a pic of what your phone says? I think i ran into a very similar situation but i was able to access fastboot, just want to see if it's the same error i got
Click to expand...
Click to collapse
It was just a black screen. It wouldn’t boot into any menu whatsoever.
Sui77 said:
Make sure that
1. The latest adb is saved to the folder you extracted the factory image file
2. There is enough disc drive space available
Then rerun the flashall.bat from that folder
Click to expand...
Click to collapse
Yes, that’s how I initially updated which somehow broke it. Anyway, got it repaired for free since it’s in warranty.
grandpajiver said:
Yikes. I had that happen to two Pixel 5a phones.
They booted into Qualcomm mode. I checked windows device manager and saw that it was a device, using qcomm, and there is no way to repair this one was rooted, one wasn't rooted.
I ended up buying a pixel 6 and 7.
Also, I noticed this occurred during the monthly patch cycle.
There is no way to get into the bootloader, fastboot, recovery, or safe mode.
I hope that isn't the situation with the 7s as well.
Good luck, please post your findings!
Click to expand...
Click to collapse
Hi, I had to send in the phone for a repair. It was a free repair since the phone’s in warranty.

That happened to me with Pixel 6 Pro. The screen only showed the charging icin and wouldn't respond and the phone was getting hot. I ended up rebooting it by holding the power key and one of the volume buttons (don't remember which one) for like 30-40 seconds and that rebooted it and from there I got to recovery mode and flashed the image via sideload.