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:
Related
Hi guys,
Very strange problem, just got my Nexus 4, it prompted me to update. It was plugged in, charging, I let it restart to update and it simply never came back on. It didn't do any of the Android update process (with the Android on screen), just shut off, and never woke up again.
I've tried holding down volume + power, and the only thing that happens when I do this is the LED notification light flashes red for a few seconds then turns off, then repeats 10 seconds later.
Has anyone got any ideas of what could be the problem, any troubleshooting tips? It seems to be turning on in some way but not properly in that when I plug it into my Windows machine, it starts to install drivers, but still no real sign of life.
Otherwise, looks like I'll be sending it back and waiting weeks for a replacement..
Trying pulling the battery, oh wait...
Qassim said:
Hi guys,
Very strange problem, just got my Nexus 4, it prompted me to update. It was plugged in, charging, I let it restart to update and it simply never came back on. It didn't do any of the Android update process (with the Android on screen), just shut off, and never woke up again.
I've tried holding down volume + power, and the only thing that happens when I do this is the LED notification light flashes red for a few seconds then turns off, then repeats 10 seconds later.
Has anyone got any ideas of what could be the problem, any troubleshooting tips? It seems to be turning on in some way but not properly in that when I plug it into my Windows machine, it starts to install drivers, but still no real sign of life.
Otherwise, looks like I'll be sending it back and waiting weeks for a replacement..
Click to expand...
Click to collapse
Call Google, they set up a call center for these exact types of questions.
Yep looks like I'll have to.
Just thought I would check here in case anyone knew any troubleshooting methods that might bring some life back to it.
Oh dear..
Qassim said:
Hi guys,
Very strange problem, just got my Nexus 4, it prompted me to update. It was plugged in, charging, I let it restart to update and it simply never came back on. It didn't do any of the Android update process (with the Android on screen), just shut off, and never woke up again.
I've tried holding down volume + power, and the only thing that happens when I do this is the LED notification light flashes red for a few seconds then turns off, then repeats 10 seconds later.
Has anyone got any ideas of what could be the problem, any troubleshooting tips? It seems to be turning on in some way but not properly in that when I plug it into my Windows machine, it starts to install drivers, but still no real sign of life.
Otherwise, looks like I'll be sending it back and waiting weeks for a replacement..
Click to expand...
Click to collapse
I've no intention to frighten you. Had similar problem with lg optimus one. Instead of boot, light just flashed for few times and static snow appeared on screen. Service said that it was motherboard failure.
Are you holding it wrong?
As the front and back both have glass..... are you sure its not turned face down?
Sorry I couldn't resist. Hope you get it sorted, and yeah the Google helpdesk is first place to start
Sent from my GT-I9300 using xda premium
if you have a screw driver kit, try opening the back and remove the battery, i heard the battery is removable but needs to be done with caution... again this is only if you dont want to send it back and wait for a month... just a suggestion..
pparavas said:
if you have a screw driver kit, try opening the back and remove the battery, i heard the battery is removable but needs to be done with caution... again this is only if you dont want to send it back and wait for a month... just a suggestion..
Click to expand...
Click to collapse
Would this void warranty?
Sent from my SAMSUNG-SGH-T769 using xda premium
pparavas said:
if you have a screw driver kit, try opening the back and remove the battery, i heard the battery is removable but needs to be done with caution... again this is only if you dont want to send it back and wait for a month... just a suggestion..
Click to expand...
Click to collapse
Usually every phone that have a inreplaceable battery can similete a battery pull pressing powe button and vol up + down for about 10 seconds
pparavas said:
if you have a screw driver kit, try opening the back and remove the battery, i heard the battery is removable but needs to be done with caution... again this is only if you dont want to send it back and wait for a month... just a suggestion..
Click to expand...
Click to collapse
Pretty dumb suggestion for a new device.
Can you get to a recovery menu? Download Mode? Anything?
feedtheducks said:
Would this void warranty?
Sent from my SAMSUNG-SGH-T769 using xda premium
Click to expand...
Click to collapse
No as far as i know and read everywhere.. check this link... i also saw on android central.. that you could keep holding the power button for 10 seconds for it to restart
http://www.technobloom.com/nexus-4-...eplace-xda-warns-of-potential-danger/2218834/
---------- Post added at 11:05 AM ---------- Previous post was at 11:04 AM ----------
feedtheducks said:
Would this void warranty?
Sent from my SAMSUNG-SGH-T769 using xda premium
Click to expand...
Click to collapse
bowenac said:
Pretty dumb suggestion for a new device.
Can you get to a recovery menu? Download Mode? Anything?
Click to expand...
Click to collapse
Thanks for your comments... I never mentioned that its a good suggestion, all i thought was to help a guy in need, sorry if you felt bad..
pparavas said:
if you have a screw driver kit, try opening the back and remove the battery, i heard the battery is removable but needs to be done with caution... again this is only if you dont want to send it back and wait for a month... just a suggestion..
Click to expand...
Click to collapse
No. This is a brand new device with full warranty.
Call support and see what they say.
t0ph0id said:
Trying pulling the battery, oh wait...
Click to expand...
Click to collapse
lmao :laugh:
Ok, I think I've solved it.
I did a bit of searching for similar problems on LG devices, and found a thread on Microsoft.com about an LG Optimus 7. (Do a search for 'LG optimus 7 not turning on' (top result) I can't post links yet).
Yes, a LG Windows Phone device.
I unplugged the device, held down Vol up and Vol down + Power for around 10 seconds, then plugged the device back in and it booted up. The problem is, it is doing this every time and sometimes this method takes a few tries to get it working.
Once the device boots up, it is fine, but this means I can't install the latest OTA update as when it goes to reboot to install, it just falls over, and to get it to start again you need to essentially do a hard reset.
The good news is that I can probably wait a few weeks for the stock levels to replenish before sending it back so I'm not waiting too long without it.
This happened to me at the store yesterday thankfully they were able to call another store before they opened and hold one for exchange seeing how you fixed it I'm glad I wasn't able to resurrect it right then and there
Sent from my Nexus 4 using xda app-developers app
Today while using my one that is rooted with trickdroid 8.0.0 turned off at around 40% randomly, The screen froze at the lockscreen and I when put it to charge the orange light did not appear. I cannot reboot into recovery from the phone nor from adb. When plugged in the computer it is read as QHUSB_DLOAD. Any advice on how to fix this?
dlnas said:
Today while using my one that is rooted with trickdroid 8.0.0 turned off at around 40% randomly, The screen froze at the lockscreen and I when put it to charge the orange light did not appear. I cannot reboot into recovery from the phone nor from adb. When plugged in the computer it is read as QHUSB_DLOAD. Any advice on how to fix this?
Click to expand...
Click to collapse
QHUSB_DLOAD usually means a hard-brick. Does it power on at all? You might try leaving it plugged in overnight, but I suspect your phone just died.
iElvis said:
QHUSB_DLOAD usually means a hard-brick. Does it power on at all? You might try leaving it plugged in overnight, but I suspect your phone just died.
Click to expand...
Click to collapse
It does not power on at all. My battery was at ~40%. Is it possible for the phone to just turn off like that at that percent?
dlnas said:
It does not power on at all. My battery was at ~40%. Is it possible for the phone to just turn off like that at that percent?
Click to expand...
Click to collapse
I haven't seen it on the One, but it was a real problem with the One XL. Phones would just drop to 0% charge and die for no apparent reason. Not pleased to this happening on the One.
iElvis said:
I haven't seen it on the One, but it was a real problem with the One XL. Phones would just drop to 0% charge and die for no apparent reason. Not pleased to this happening on the One.
Click to expand...
Click to collapse
Before it died. I unlocked the phone and the only thing I could do was pull the notification drawer down. It would not let me open any app or even the app drawer.
dude this sounds frightening
Read the HTC Unbricking Project thread, the problem is HTC phone wide so I see no reason why the fix wouldn't also be. At the very least give that thread a read, you've got nothing to lose.
postfatal said:
Read the HTC Unbricking Project thread, the problem is HTC phone wide so I see no reason why the fix wouldn't also be. At the very least give that thread a read, you've got nothing to lose.
Click to expand...
Click to collapse
That fix is only for a couple of specific issues:
Note: This will fix only devices which were bricked by turning S ON. And bricks caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device. Any devices bricked with other ways are currently *not* supported. We are working on it
Click to expand...
Click to collapse
People tried it on the One XL/Evita when this happened, and it didn't work, unfortunately. Note that the method requires the battery to be removed.
tousary shall
iElvis said:
That fix is only for a couple of specific issues:
People tried it on the One XL/Evita when this happened, and it didn't work, unfortunately. Note that the method requires the battery to be removed.
Click to expand...
Click to collapse
I've only had the phone for 2 months and it already bricked. It shouldn't be a problem explaining it to AT&T and getting a replacement right? I mean if I can't turn it on they can't turn it on.
Had the same problem after flashing the wrong recovery..
THis means it is hardbricked and unrecoverable..
You could ask here: http://forum.xda-developers.com/showthread.php?p=43750389#post43750389
Else send it in for repairs
dlnas said:
I've only had the phone for 2 months and it already bricked. It shouldn't be a problem explaining it to AT&T and getting a replacement right? I mean if I can't turn it on they can't turn it on.
Click to expand...
Click to collapse
It's a hardware fault, from everything I've seen, and HTC or AT&T should replace it. AT&T tends to be very easy about this. If the phone won't power on at all, they shouldn't give you a hard time.
Hi there!
This thread is my last hope, so please dont let me down folks...:cyclops:
The story short - one sunny morning i turned on my HTC Nexus One and it got stuck with te X on the screen for about 15 minutes, non of the buttons responded, so i did the first thing that came in my mind - i pulled out the battery. After inserting the battery the phone went full brick, i mean literally, no reaction on anything, even conected to the wall charger, there is no sign of life, no charging LED, nothing. Connected to the PC, it says USB device not recognised.
I dont think this is a hardware proble, the phone workwd fine until this interrupted power on. Phone runned on stock Androud, i have not played aroun with it - no bootloader unlock, no rooting.
I searched the internet for a solution, tried a lot of button combinations like in this thread:
http://forum.xda-developers.com/showthread.php?t=1069032
but still no luck, i cannot restore or flash it while my PC does not recognise the phone.
Found some info about those Usb Jig things, but they work only on Samsung phones, so, is there a way to force the phone to go in recovery mode, or give any sign of life so i can try to recover it or flash a diferent ROM?
The warranty has ended, so no hope there.
Hope there is a way out of this, and, sory for my bad english. :good:
If you can't get your phone to bootloader, recovery or os then your phone is bricked. You could hope its as simple as a bad battery but chances are you would need JTAG to get it running again and at that point you are best of just getting a new phone.
Sorry for the bad news
Sent from my Nexus 4 using XDA Premium 4 mobile app
Hey Guys
Hope, some of you can help me. The problem is:
i bought a new HTC One Mini 2. Cause i had a Cyanogen 10.1 on my previous phone, i thought, that i should install a new CyanogenMod for this phone again. So i unlocked und flashed the Phone. As custom recovery i used TWRP 2.8.5.0... Found that one here in a Thread. After i flashed cm-12-20150411-NIGHTLY-memul.zip on it. After all, i started my phone again and all worked fine. i thought....
So yesterday i powered off my phone, plugged it to the charging-cable and went to sleep. In the morning i got up, picked my phone and wanted to turn it on. What i saw, was the charging screen, blink led is standing on orange and thats it. Cant power it off again, cant boot to recovery... nothing...
And the point is, i dont have the ultilities and the skill to open the phone and remove the battery to see, if that is the problem.
Do you have any ideas for that?? Thanks for leave an answer
lol
peacer95 said:
Hey Guys
Hope, some of you can help me. The problem is:
i bought a new HTC One Mini 2. Cause i had a Cyanogen 10.1 on my previous phone, i thought, that i should install a new CyanogenMod for this phone again. So i unlocked und flashed the Phone. As custom recovery i used TWRP 2.8.5.0... Found that one here in a Thread. After i flashed cm-12-20150411-NIGHTLY-memul.zip on it. After all, i started my phone again and all worked fine. i thought....
So yesterday i powered off my phone, plugged it to the charging-cable and went to sleep. In the morning i got up, picked my phone and wanted to turn it on. What i saw, was the charging screen, blink led is standing on orange and thats it. Cant power it off again, cant boot to recovery... nothing...
And the point is, i dont have the ultilities and the skill to open the phone and remove the battery to see, if that is the problem.
Do you have any ideas for that?? Thanks for leave an answer
Click to expand...
Click to collapse
I works again. was some buggy thing, i guess. A friend took my phone, did same combination that i did to boot in recovery mode and BOOM it reboots and work properly. So, i can't tell u a real solutions, but if you got same problem, keep trying with the POWER-Button and the VOLUME_DOWN-Button. Worked in my case.
Thread can get closed.
peacer95 said:
I works again. was some buggy thing, i guess. A friend took my phone, did same combination that i did to boot in recovery mode and BOOM it reboots and work properly. So, i can't tell u a real solutions, but if you got same problem, keep trying with the POWER-Button and the VOLUME_DOWN-Button. Worked in my case.
Thread can get closed.
Click to expand...
Click to collapse
What he did was a hard reboot, accomplished by holding the power and vol-up buttons for about 10 seconds. Just wanted to add this.
Hey guys,
any solution to this problem??
Got the same issue. unlocked bootloader with htcdev, installed TWRP Recovery and rooted phone, everything worked fine yesterday.
Today I installed xposed framework, then I plugged-in the charging cable and turned off the phone because I wanted to flash xposed in Recovery. But when the phone turned off, it only showed the charging screen with the message ("This build is for development purposes only Do not distribute outside of HTC without HTC's written permission. Failure to comply may lead to legal action.") and didn't react to any button pressings until the battery finally died.
Then I plugged in charging cable again. Now I have again the charging screen, only difference is that the LED doesn't flash permanently but it now blinks. Computer recognizes phone but I can't send fastboot commands since it is turned off.
Any help would be appreciated!
EDIT: After a lot of tries, I finally also managed to fix it with 10 seconds power + volume up....
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