Database Develop

QHSUSB_DLOAD mode??

Hi everybody,
a friend of mine got his HTC One (black) yesterday and rooted it. He flashed a proper custom ROM on it which I and another one of my work buddy use as well without any issues (InsertCoin). No further flashes done, no other custom kernels, no S-Off, no SuperCID. Just unlocked Bootloader and custom ROM.
He let the device run dry yesterday evening so it shut off itself automatically. He put it on his charger, the phone turned on, he did some surfing and installing apps from the market and set up his alarm. The phone charged over night and he was also able to switch off the alarm this morning.
He got ready for work, got into his car and wanted to switch on the screen on the one for some good tunes. But the screen stayed black.
When I arrived at work, he was a little upset and panicked a little. I thought I was able to recover the device.
After plugging it in to my work computer, the device manager just shows a unknown device called "QHSUSB_DLOAD" so I went to google and looked it up..
Weird thing is: QHSUSB_DLOAD wasnt seen yet on the HTC One (M7) as far as I can see it and it was pretty bad on the HTC One S. It means "Qualcom High Speed USB Download Mode" and on the One S as well as on the Nexus 4 this devices showed up after the bootloader got damaged or the device got stuck in that mode for good.
When plugging the device in (USB / Wall charger) the charging LED doesnt turn on at all, the capacitive buttons dont start to blink while holding down the power button as well.
This thing seems to be gone for good.
But aint it the way that we dont even have any access to the bootloader if its not an official update from HTC? Signature check and stuff? Since the device was rooted, no OTA updates were able to arrive at all. He told me that he didnt try to flash anything after we flashed the custom ROM.
Any advice on that?

Did you even try booting the device first thru hboot/bootloader or holding the power button to force a restart? If you did try connecting the device while on QHSUSB_DLOAD and execute a compatible RUU on your PC. RUU uses android's download mode to flash the ROM so it should be repaired by an RUU.

Already tried, no luck. Tells me the device has not been found.

I am sorry to hear that, man, but from the looks of it your friend now has a paperweight. I'd take it to an HTC service center and hear what they have to say regarding this; of course it will no longer be covered under warranty, but maybe they can fix it for you for a price or something.

Are you sure RUU can't find the phone? If it can't then I guess only a JTAG box can fix it so either send it to HTC for repair or have someone who knows JTAG fix it.
Try4Ce said:
Already tried, no luck. Tells me the device has not been found.
Click to expand...
Click to collapse

I saw this issue on my friend's GS3 once. It was hard bricked and there was no way to recover from what I read (at least on the GS3). I know I saw a thread somewhere here in this forum about the same issue and someone linked to a Sensation thread where there was a way to fix it but I'm not sure if it would apply to the One

Same problem - but the phone magically fixed itself!
I had the exact same problem with my HTC One as described in OP...
My alarm went off in the morning and I set off for work, my battery was low but I thought that I would just charge it when I got to work. I was playing a game (Dungelot) whilst waiting for my bus and was receiving pop up messages about low battery. When it got to 4% left I decided that I would finish the level then close the game down, but as I was just about to finish, the phone went blank...I assumed that I had naturally used up all the battery life and although peeved that I had probably lost my progress in the game, wasn't too bothered.
I got to work and plugged my phone in to charge on my computer. The computer wanted to search for QHSUSB_DLOAD drivers but I thought this must be what it does when my phone isn't switched on and it finds the device. I cancelled the search prompt and tried to switch my phone on...nothing happened.
I tried for the rest of the day, trying to force shut down the bricked phone by holding power in for 30 secs, trying to power into boot mode etc...everything! But the phone would not switch on and the only response I got from it was a little orange LED every now and again and the QHSUSB_DLOAD prompt.
After googling the prompt - I found myself here and REALLY began to sh*t my pants! I've only had the phone less than a month and felt I was tech-savvy enough to flash my phone with a new ROM (Android Revolution HD) to try and get rid of some of the bloatware. I had flashed a new ROM successfully a coupld of weeks before and everything had been fine up that point.
I went home depressed but throught i'd try to plug my phone into a proper mains charger rather than my work's old USB cable (that came with my previous HTC Desire Z) I was going to try a long night of searching the net to try and find a way where I could at least recover the photo's, Zoe's and vids of my new born son but had such a headache that I gave up and went for an early night.
I was woken unexpectedly the next morning by my phone alarm going off! I stopped the alarm and the home just went to Home screen as normal! I don't know how or why these events happened...whether it was the flashed ROM, the game I was playing, the battery running out before the phone could shut down properly, the old USB cable in my work not charging but detecting the device or a combination of all of those, but so far, the phone jumped back into life with the alarm after being charged in the mains all night!
Thought i'd share as it may just help someone else out there who encounters this!

Some phones have miraculously come back from QHSUSB_DLOAD with no explanation of why. Other than that it usually means a hard brick. You can send it to HTC, they will charge you and replace the main board, from what I've heard.
Sent from my HTC One using XDA Premium 4 mobile app
---------- Post added at 08:20 PM ---------- Previous post was at 08:20 PM ----------
Also, its not unheard of. I've seen it happen a few times in these forums.
Sent from my HTC One using XDA Premium 4 mobile app

I wonder if having your alarm set saved you. This phone will actually power itself on so as not to miss an alarm.
Sent from my HTC One using xda app-developers app

lampel said:
I wonder if having your alarm set saved you. This phone will actually power itself on so as not to miss an alarm.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Hi Try4Ce,
I am facing the same issue. If your friend's phone is fixed, can you share with me how the fix happened?
Many thanks in advance.
Krishna Menon.

same here
Any idea how to fix it?

Delingerb said:
Any idea how to fix it?
Click to expand...
Click to collapse
Jtag or send it to HTC is the only way.
Sent from my HTC One using Tapatalk

My Solution
Had the same Problem.
My Solution was to Download "HTC One (M7) Toolkit" and force Fastboot.
Pushed Power and Volume Down until Screen was Flashing.
Took about 2 minutes and the Phone was rebooting.
I have no idea what was happening. I have no idea if this helps or works for others. But its worth trying.
Sorry for my bad english.

Try4Ce said:
Any advice on that?
Click to expand...
Click to collapse
CoryTallman said:
Some phones have miraculously come back from QHSUSB_DLOAD with no explanation of why. Other than that it usually means a hard brick. You can send it to HTC, they will charge you and replace the main board, from what I've heard.
Click to expand...
Click to collapse
bkmenon said:
Hi Try4Ce,
I am facing the same issue. If your friend's phone is fixed, can you share with me how the fix happened?
Many thanks in advance.
Krishna Menon.
Click to expand...
Click to collapse
Delingerb said:
Any idea how to fix it?
Click to expand...
Click to collapse
This is some kind of mode that is enabled when you hold power on button when the device battery is completely drained. i.e. when you try to turn device on it will not boot up (Special I was connected to usb cable via PC to charge my phone NEXUS 4 when I get into this mode). I saw a similar mode where nvflash commands are executed something like APX(can't recall correctly) with Tegra 4 device (that time also I was connected with a usb cable and charging the tablet when it was completely drained!). A simple solution to quit this issue is DO not Panic and let the device get a little charge. After that boot normally with the power button. In case if it didn't try other modes to enter such as recovery or fastboot reboot commands if your device is getting recognised..

QHSUSB DLOAD means its a hard bricked phone, No amount of messing about with it will fix it, Send it to a service centre, it will probable have to have the motherboard replaced..Sorry

My device entered in QHSUSB_DLOAD mode after the 4.4 ota was installed and 30 minutes later, I was able to turn up the phone. It restarted itself like 5 times and then it was normal. Miracle..

danielr18 said:
My device entered in QHSUSB_DLOAD mode after the 4.4 ota was installed and 30 minutes later, I was able to turn up the phone. It restarted itself like 5 times and then it was normal. Miracle..
Click to expand...
Click to collapse
What do you mean by "force"? What did you do exactly?

My device wouldn't do anything, and it was in QHSUSB_DLOAD . But when I later pushed the power button for a minute, it worked.

danielr18 said:
My device wouldn't do anything, and it was in QHSUSB_DLOAD . But when I later pushed the power button for a minute, it worked.
Click to expand...
Click to collapse
mine spent the night carrying on waking took the charger and the green light for continued access, tried to turn it on but could not. After reading your response, I tried to hold the power button for longer. After 15 seconds the phone rang and the light came on, everything works perfect so far

Today while I was updating firmware phone gone to QHSUSB_DLOAD mode.
I am guessing it's end of road. :crying:

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

Am I Screwed? Please Help!

So I barely used my phone yesterday, just hotspot for my dad's iphone to upload some pics from his phone to my gdrive while we were out, check notifications from my lockscreen, and whatsapp my wife a couple times. That was done no problem. Hours later without using my phone it was lagging badly, and wouldn't start up certain apps like LastPass, Free Adblocker Browser, and I installed Malwarebytes and did a scan and found nothing, but it would crash instantly upon opening after that as with the other 2 apps. I didn't try many apps, some I would tap on and no response, but that was 1 or 2 apps. The odd thing is my Play Store was uninstalled somehow, which would make me think it was a virus which is why I tried Malwarebytes.
Since that didn't work I did some searching and saw some advice online to boot into recover and wipe the cache partition. I did this and it booted up fine, and I went to sleep. I wake up today, and the phone appears dead. No signs of life. Although, I did put it on the wireless charger and the light changed as if it was charging. I plugged it into my computer and saw in Device Manager under Ports it loaded "Qualcomm HS-USB QDLoader 9008" successfully. I've read if that shows (is this EDL mode?) it can be recovered. It's not showing now after I tried a hard reset, but the wireless charging light still changes. CORRECTION: QDLoader just reappeared as I type this message!
Is this a hard brick? Is my phone finished? Please help with anything you can think of! Like I said there's no signs of life on the actual phone. I tried the hard reset too.
My Note8 is USA Unlocked SM-N950U1 being used in Canada, I don't know the bootloader version, but I THINK it's 5, I haven't installed any malicious/modded apps, I'm not rooted.
Please please help!
Thanks!

delan007 said:
So I barely used my phone yesterday, just hotspot for my dad's iphone to upload some pics from his phone to my gdrive while we were out, check notifications from my lockscreen, and whatsapp my wife a couple times. That was done no problem. Hours later without using my phone it was lagging badly, and wouldn't start up certain apps like LastPass, Free Adblocker Browser, and I installed Malwarebytes and did a scan and found nothing, but it would crash instantly upon opening after that as with the other 2 apps. I didn't try many apps, some I would tap on and no response, but that was 1 or 2 apps. The odd thing is my Play Store was uninstalled somehow, which would make me think it was a virus which is why I tried Malwarebytes.
Since that didn't work I did some searching and saw some advice online to boot into recover and wipe the cache partition. I did this and it booted up fine, and I went to sleep. I wake up today, and the phone appears dead. No signs of life. Although, I did put it on the wireless charger and the light changed as if it was charging. I plugged it into my computer and saw in Device Manager under Ports it loaded "Qualcomm HS-USB QDLoader 9008" successfully. I've read if that shows (is this EDL mode?) it can be recovered. It's not showing now after I tried a hard reset, but the wireless charging light still changes. CORRECTION: QDLoader just reappeared as I type this message!
Is this a hard brick? Is my phone finished? Please help with anything you can think of! Like I said there's no signs of life on the actual phone. I tried the hard reset too.
My Note8 is USA Unlocked SM-N950U1 being used in Canada, I don't know the bootloader version, but I THINK it's 5, I haven't installed any malicious/modded apps, I'm not rooted.
Please please help!
Thanks!
Click to expand...
Click to collapse
Sorry but your phone is finished..

Can you enter to downoad mode ?
on power off condition, press & hold vol down & bixby button, then press power button until download mode appear

ariey said:
Can you enter to downoad mode ?
on power off condition, press & hold vol down & bixby button, then press power button until download mode appear
Click to expand...
Click to collapse
Nothing shows on the screen whatsoever, but it does show life on the wireless charger, and in Windows 7 Device Manager under Ports it shows Qualcomm HS-USB QDLoader 9008.
I'm taking the phone to the official Samsung Service Centre where I live for a free diagnostic to see if they can do anything.

I think I'm stuck in what's known as EDL Mode which I see no solution for, but I could be wrong.

MrMike2182 said:
Sorry but your phone is finished..
Click to expand...
Click to collapse
Samsung Service Centre's can't even repair it?

delan007 said:
Samsung Service Centre's can't even repair it?
Click to expand...
Click to collapse
The service center could fix it yes.. If it's stuck in EDL mode maybe take a look at the root thread for version 5 of the bootloader because they might have a way out of that.. Do you have a picture of the screen it's stuck on?

MrMike2182 said:
The service center could fix it yes.. If it's stuck in EDL mode maybe take a look at the root thread for version 5 of the bootloader because they might have a way out of that.. Do you have a picture of the screen it's stuck on?
Click to expand...
Click to collapse
The phone screen is black as in off. It hasn't turned on since it bricked. Only signs of life are the wireless charger light coming on showing the phone as charging, and the qdloader 2008 on my computer. I didn't see version 5 of the bootloader anywhere, but I may be looking in the wrong spot?
Thanks for the help!

delan007 said:
The phone screen is black as in off. It hasn't turned on since it bricked. Only signs of life are the wireless charger light coming on showing the phone as charging, and the qdloader 2008 on my computer. I didn't see version 5 of the bootloader anywhere, but I may be looking in the wrong spot?
Thanks for the help!
Click to expand...
Click to collapse
I suggest you just take it to the service center because I think your internal memory card is done.. A phone doesn't just normally brick itself. It's not able to find an operating system which is why it's not doing anything.

MrMike2182 said:
I suggest you just take it to the service center because I think your internal memory card is done.. A phone doesn't just normally brick itself. It's not able to find an operating system which is why it's not doing anything.
Click to expand...
Click to collapse
Looks like you're right bro, I took it in and they said no signs of life, and wasn't a battery fault as they tried a new one. He said the motherboard is fried. This was at an official Samsung Service Centre too.
Thanks everyone for the help!

This is interesting, I have the SM-N950U1 and mine just basically did this 3 days ago now. I woke up and the phone was dead (was working the night before, left on charge and went to bed). Since then I was able to turn it on a few times and do the wipe/data delete, but now I'm stuck only being able to kinda get into download mode.
I wonder if there is an issue wit the SM-N950U1 models...

I would take your device to a Samsung Service Center and let them take a look at it.

iceepyon said:
I would take your device to a Samsung Service Center and let them take a look at it.
Click to expand...
Click to collapse
I was able to do this in to a Samsung repair center the other day, they took one look at it and handed it back to me and said it wasn't something they could deal with. They recommended sending it to Samsung directly. I took it to a uBreakiFixit store, which is what Samsung recommended. I heard the guy in the back talking about it saying it needed to be re-flashed and the OS put back on and he handed it back to the front desk guy who relayed the message to me, hah!
Oh well, now its a paperweight...

Question Why is my phone not turning on after restarting?

Hello, guys! I had my Xiaomi Redmi 9t for 6 months now and so far I only encountered minor problems, not until now. Before that, I never did turned my phone off for a very long time or I have never restarted it, but since I noticed that my GPS was crappy---because it didn't show any accurate data while I'm using the Strava app to track my bicycle rides. So, I restarted it and after that the screen just went total black, it never responded despite of how long I pressed the power button, and also I just unplugged it from the charger because it was almost full. I was also able to use it few minutes after the restart without any problems, I heard from other users who owned this phone that this also the same problem they are encountering.
Also, it's not bricked or anything because it was still functioning normally. For not being bricked, I cannot access the fastboot mode since I cannot even turn it on.

If you try to charge it again, does the screen turns on then shows a charging animation?

dinsel said:
If you try to charge it again, does the screen turns on then shows a charging animation?
Click to expand...
Click to collapse
It doesn't do anything. There's no display neither a vibration.

Your device is dead booted. The cause might be related to hardware. So, what I recommend for you is to bring that to a service center to get fixed or replaced. F.

dinsel said:
Your device is dead booted. The cause might be related to hardware. So, what I recommend for you is to bring that to a service center to get fixed or replaced. F.
Click to expand...
Click to collapse
yeah, there are a lot of fellow Filipino users who complained about the same problem. But I think it's also about the latest firmware update, because my younger sisters had the phone but they did not have any of my problem and their firmware versions aren't updated yet.

And just to think of it, the latest update also made my phone cranky. The wifi suddenly turns off and on and the GPS thing (which i mentioned in the post).

You have not been able to press the power + volume button for 10 seconds to achieve something?

ceesarsu said:
You have not been able to press the power + volume button for 10 seconds to achieve something?
Click to expand...
Click to collapse
No. He can't.

derunheimlich said:
Hello, guys! I had my Xiaomi Redmi 9t for 6 months now and so far I only encountered minor problems, not until now. Before that, I never did turned my phone off for a very long time or I have never restarted it, but since I noticed that my GPS was crappy---because it didn't show any accurate data while I'm using the Strava app to track my bicycle rides. So, I restarted it and after that the screen just went total black, it never responded despite of how long I pressed the power button, and also I just unplugged it from the charger because it was almost full. I was also able to use it few minutes after the restart without any problems, I heard from other users who owned this phone that this also the same problem they are encountering.
Also, it's not bricked or anything because it was still functioning normally. For not being bricked, I cannot access the fastboot mode since I cannot even turn it on.
Click to expand...
Click to collapse
Plug it into a computer. Search for device manager in the windows search box. If it shows 'Qualcomm 9008' or something like that, it can be fixed but only in a service center. If it shows 'unknown usb port' then you lack the usb drivers, but still can be fixed. If it does not show in computer, not even 'unknown usb device', your device is not bricked, it is gone for good (or maybe the usb port is fried and also the battery drained, you can replace them as a last resort)

Did it get wet?

LR7875 said:
Plug it into a computer. Search for device manager in the windows search box. If it shows 'Qualcomm 9008' or something like that, it can be fixed but only in a service center. If it shows 'unknown usb port' then you lack the usb drivers, but still can be fixed. If it does not show in computer, not even 'unknown usb device', your device is not bricked, it is gone for good (or maybe the usb port is fried and also the battery drained, you can replace them as a last resort)
Click to expand...
Click to collapse
LR7875 said:
Plug it into a computer. Search for device manager in the windows search box. If it shows 'Qualcomm 9008' or something like that, it can be fixed but only in a service center. If it shows 'unknown usb port' then you lack the usb drivers, but still can be fixed. If it does not show in computer, not even 'unknown usb device', your device is not bricked, it is gone for good (or maybe the usb port is fried and also the battery drained, you can replace them as a last resort)
Click to expand...
Click to collapse
I turned it over to the service center yyesterday. They told me that it'll be fixed tomorrow or friday. Which I'm really hoping.

blackhawk said:
Did it get wet?
Click to expand...
Click to collapse
No. I haven't even dropped it

Had the same problem today, phone is updated to the lastest firmware. Just woke up and the phone isn't even turning on, tried fastbooting while charging but nothing at all on the screen. Didn't get it wet nor dropped it. Guess we gotta replace the phone huh.

I don't update. The first thing disable is OTA updates. Many apks still running factory load versions as well.
In over 1.5 years on Pie, no factory resets due to malware. My current load is over a year old, still fast and stable.
Rule#1 if your OS is running fast, stable and fulfilling its mission... let it be.

blackhawk said:
I don't update. The first thing disable is OTA updates. Many apks still running factory load versions as well.
In over 1.5 years on Pie, no factory resets due to malware. My current load is over a year old, still fast and stable.
Rule#1 if your OS is running fast, stable and fulfilling its mission... let it be.
Click to expand...
Click to collapse
Completely agreed if you have a Xiaomi. I regretted updating to MIUI 12 because it is s l o w.

LR7875 said:
Completely agreed if you have a Xiaomi. I regretted updating to MIUI 12 because it is s l o w.
Click to expand...
Click to collapse
Doesn't matter what OS; leave a strong running OS alone... as long as you understand it's vulnerabilities. Even a malware forced reload be easier than putting up with a doggy OS every second of every day

blackhawk said:
Doesn't matter what OS; leave a strong running OS alone... as long as you understand it's vulnerabilities. Even a malware forced reload be easier than putting up with a doggy OS every second of every day
Click to expand...
Click to collapse
MIUI android 11:
Unfortunately, system UI has stopped.
Me:
Grabs a drill

LR7875 said:
MIUI android 11:
Unfortunately, system UI has stopped.
Me:
Grabs a drill
Click to expand...
Click to collapse
Yeah the whole Hulk SMASH thing... maybe a lobotomy is more civilized.

LR7875 said:
MIUI android 11:
Unfortunately, system UI has stopped.
Me:
Grabs a drill
Click to expand...
Click to collapse
At the moment my mobile is all great, it is a little more fluid with android 11

No idea, man. Sounds serious problem.

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.