My phone started doing the 4.3 OTA update last night, when the download got to about 43% the phone powered off and now wont turn on again.
The phone is completely stock. S-ON, no root.
When I connect it to the PC it tries to install drivers for QHUSB_DLOAD.
I take it the phone is bricked and has to go back for repair?
mikemod said:
My phone started doing the 4.3 OTA update last night, when the download got to about 43% the phone powered off and now wont turn on again.
The phone is completely stock. S-ON, no root.
When I connect it to the PC it tries to install drivers for QHUSB_DLOAD.
I take it the phone is bricked and has to go back for repair?
Click to expand...
Click to collapse
QHUSB_DLOAD -> yep, i would say hard-brick, needs a motherboard replacement.
OK, thanks, just organising to send it back, hopefully the new one will already have the update.
I take it no-one else has had any problems with the OTA update and this was just a one off?
This was in the UK on Vodafone.
mikemod said:
OK, thanks, just organising to send it back, hopefully the new one will already have the update.
I take it no-one else has had any problems with the OTA update and this was just a one off?
This was in the UK on Vodafone.
Click to expand...
Click to collapse
Not that I can recall, saw a few posts where it sometimes got stuck and had to force a reboot (manually), but not a hard brick. I guess the OTA got stuck updating hboot, and failed which would cause a brick I think.
mikemod said:
My phone started doing the 4.3 OTA update last night, when the download got to about 43% the phone powered off and now wont turn on again.
The phone is completely stock. S-ON, no root.
When I connect it to the PC it tries to install drivers for QHUSB_DLOAD.
I take it the phone is bricked and has to go back for repair?
Click to expand...
Click to collapse
By download, you mean downloading the OTA or installing it?
It was just in the middle of downloading it from HTC, got to about 43% and then powered down.
My htc one m7 phone is stuck too. How do you 'send it off' for a motherboard replacement and how much will it cost? Is it under warranty?
Can I go to the sprint store?
I'm on Vodafone UK and before I got the upgrade to 4.3, I got a small update just first, then the main 4.3 it installed ok and have had no problems as yet. Just wondering if the users that have had problems, got this small update first.
Sent from my HTC One using xda app-developers app
mikemod said:
It was just in the middle of downloading it from HTC, got to about 43% and then powered down.
Click to expand...
Click to collapse
Actually this seems to me more like a hardware issue. The phone can't just power down in the middle of the download, and it can't flash anything from inside the OS, it has to be in recovery. It's just a coincidence that you were doing the update.
Sent from my HTCONE using Tapatalk
Phone was irreparable so has been replaced with a nice shiny new one
Related
hi.
so i think i need help. i updated the phone few days ago to the latest firmware. and the phoen was fine for the next 2 days. i never had to restart or anything. today one of my games wasnt working so i figured my phone might need a restart.
anyway i did. and now my phone is stuck in some service mode i assume ? its a triangle with screw driver inside and a blue moving bar under it.
i dont know what to do. my phone isnt rooted or anything. i didnt even attempt to root after the update. nothing. just restarting the phone :/
am i f**ked ? :/
How did you update, OTA or pushed via FlashTool?
Dinkoz said:
How did you update, OTA or pushed via FlashTool?
Click to expand...
Click to collapse
flashtool
The only thing you can do in situations like this, as told in every such thread, is reflash with the flashtool.
Will FlashTool pick it up when connecting via Vol -Up? If so, try pushing the FTF again,even a different FTF?
i will try when i get home to see if it will pickup the flashtool.
it kinda sucks tho. why it did this ? i didnt even install anything in the stupid thing aside from few games. jesus.
What FTF did you use ? I would suggest using another just in case, you may / may not need to wipe data
the one from the main thread :/. " not the one with the typo "
i think its from singapore one ? because it had some stuff from that country.
i will go home in 1 hour or so and try to flash without wipe.
finger crossed :/
its not accepting the flashtool.
i turn the device off. i click on the back botton. but nothing.
the log says the file is connected in fast boot mode. but there is nothing . i still get the pop screen that shows the instructions how to plug your device.
any help
ll_l_x_l_ll said:
its not accepting the flashtool.
i turn the device off. i click on the back botton. but nothing.
the log says the file is connected in fast boot mode. but there is nothing . i still get the pop screen that shows the instructions how to plug your device.
any help
Click to expand...
Click to collapse
Volume down and plug the usb.
Sent from my C6603 using xda premium
ok. by miracle i got it to work. but i am not sure what happened and why it did this.
all good i guess :/
also, i wonder if there is an official version of this. not bloated with weird stuff. like euro version or something.
also. one more question.
is there a root for this ?
Reinstall the software with sony update service is what you have to do
http://www.sonymobile.com/gb/tools/update-service/
glad to read that is fixed ..
I had this same issue yesterday. I installed the the update from the India c6602. Things were working fine the first day. I did a reset and then had the same issue as the OP had.
A re-flash with the flashtool didn't work the first time and the I tried the Sony companion fix option, and still had problems. Then I realized I had to install the drivers. Are you on windows 8? did you install the drivers that came with the flashtool? I did and then re-flashed, and now its fine again.
ll_l_x_l_ll said:
ok. by miracle i got it to work. but i am not sure what happened and why it did this.
all good i guess :/
also, i wonder if there is an official version of this. not bloated with weird stuff. like euro version or something.
also. one more question.
is there a root for this ?
Click to expand...
Click to collapse
Most people seem to have flashed the Global FTF, you could reflash the old firmware, then when you plug into PC Companion it should flick up the update for you/your region.
I would just flash Global
I was rooting my phone I got to the point where I accepted the 4.4 update it downloaded installed shut off and that was it. I have tried every button combination, It had plenty of charge, and just to make sure I plugged it into a wall charger for 20 minutes. Any suggestions? The screen doesn't come on at all. Thanks, Garrett.
Follow the instructions on how to enter stock recovery. This should help.
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/94946/p/30,6720,8696
Sent from my XT1060 using Tapatalk
Still no luck...
garrettpen said:
Still no luck...
Click to expand...
Click to collapse
Sorry bud. Sounds like you might have bigger issues than I can help you with. However, you should try to connect it to your computer and see if you get anything. Also keep trying to power it on while on a USB or charger.
Hopefully someone with a similar experience can chime in.
Sent from my XT1060 using Tapatalk
http://forum.xda-developers.com/showthread.php?t=2477132
You can try to flash your phones stock ROM using this tool kit if you can get into the Boot loader. I just used it to flash back to stock on my sprint moto x. I know you are in a different situation but I can't hurt to try
Sent from my XT1056 using Tapatalk
garrettpen said:
I was rooting my phone I got to the point where I accepted the 4.4 update it downloaded installed shut off and that was it. I have tried every button combination, It had plenty of charge, and just to make sure I plugged it into a wall charger for 20 minutes. Any suggestions? The screen doesn't come on at all. Thanks, Garrett.
Click to expand...
Click to collapse
hold power button for 1 min if you feel the phone vibrate that is good.
now try holding Volume Up + Power will it boot into the bootloader.
If yes great time to restore to stock
If No then your phone is hard bricked and you will have to get it replaced.
one easy way to find out if your phone is hard bricked is to plug it into the computer and see what drivers it tries to install
if it say qhsusb_dload then i know for a fact that your phone is Hard bricked.
If that is the case call your carrier or go to a local store and tell them that your phone was on 4.2.2 and you downloaded the 4.4 OTA and it rebooted to install it and now it won't turn on at all they should give you a brand new phone because it was the phones problem.
When you get your new phone please post here first with What Carrier Moto X you have and what android version it is on 4.2.2 / 4.2.2 Camera Update / 4.4. and i will help you get your phone rooted and up and running correctly
Good Luck My Friend and please don't be afraid to ask for help
Mist likely hard bricked, you're not the only person this has happen too and won't be the last, if you're getting the driver mussing as previously posted ,I agree and its hard bricked. Which 4.2 stick firmware where you on? Pre camera update? At least you can call you're carrier and say you attempted to install an ota which in fact did brick your phone don't tell them you tried to root it of course, good.luck
Sent on my Moto X
Just received the stock update to Sense 6. I am in Canada, on Telus, fully stock.
When the phone boots into the recovery to flash the update, I am getting a red triangle and the error is unexpected contents in settings.apk
Any suggestions on how to get this update working other than hard resetting before the update?
Thanks.
Can you reboot normally? Just select the Reboot system option? Also, if it insists on going to update, hold power button to forcefully restart and keep pressing the volume down button to get into bootloader mode.
Try restart from there.
As you are FULLY stock (no root, should say LOCKED on that bootloader screen) you can either consider going through the warranty OR trying it yourself to fix by unlocking bootloader OR take it to someone locally.
Unfortunately all options will lead to data loss.
SaHiLzZ said:
Can you reboot normally? Just select the Reboot system option? Also, if it insists on going to update, hold power button to forcefully restart and keep pressing the volume down button to get into bootloader mode.
Try restart from there.
As you are FULLY stock (no root, should say LOCKED on that bootloader screen) you can either consider going through the warranty OR trying it yourself to fix by unlocking bootloader OR take it to someone locally.
Unfortunately all options will lead to data loss.
Click to expand...
Click to collapse
Yes it reboots and yes I have a locked bootloader. I would hard reset before sending it out for servicing.
Any other people having this issue?
mfpreach said:
Yes it reboots and yes I have a locked bootloader. I would hard reset before sending it out for servicing.
Any other people having this issue?
Click to expand...
Click to collapse
Not heard of a problem while updating. You are special.
What are your guys thoughts on flashing a stock ruu and then trying to ota to sense 6?
mfpreach said:
What are your guys thoughts on flashing a stock ruu and then trying to ota to sense 6?
Click to expand...
Click to collapse
Great idea!
mfpreach said:
What are your guys thoughts on flashing a stock ruu and then trying to ota to sense 6?
Click to expand...
Click to collapse
Did your problem solved?
Haha I haven't been able to try, on my 8.1 box I get an error 170 when trying to connect the phone in ruu. On my win7 box the ruu just auto closes....
mfpreach said:
Haha I haven't been able to try, on my 8.1 box I get an error 170 when trying to connect the phone in ruu. On my win7 box the ruu just auto closes....
Click to expand...
Click to collapse
well error 170 is either because your drivers aren't installed correctly or because you have a bad usb cable/port
alray said:
well error 170 is either because your drivers aren't installed correctly or because you have a bad usb cable/port
Click to expand...
Click to collapse
Thanks,I will look into it tomorrow.
Are there even good drivers for 8.1 yet bearing in mind I don't have a USB 3 port?
mfpreach said:
Thanks,I will look into it tomorrow.
Are there even good drivers for 8.1 yet bearing in mind I don't have a USB 3 port?
Click to expand...
Click to collapse
hi, we have similar issues although mine is the soundhound_freemium.apk instead of settings.apk, I hope that you will get your issue settled and also update me and the rest of us who are having the issues here. good luck and thanks! (do check out my thread which I've just posted like 5 minutes back!)
Do not install sense 6 upgrade
I would recommend NOT installing the stock Sense 6 upgrade. I installed it a couple days ago and currently my phone is bricked because of it.
I posted about my issue in another thread. In case people want to read what's been going on i'll repost it here.
Kg810 said:
So I performed the Sense 6 upgrade a couple days ago, update went through fine, yesterday morning my phone started acting all weird (sluggish, random reboots, bunch of apps reporting errors, etc) and battery was draining fast.
I probably rebooted my phone 10 times, 5 times normally by just the power button and the remaining times through the light trick, power button and volume button. Once my phone finally got back to normal, I was typing on whatsapp and then suddenly it froze.
It froze for a couple minutes and then it turned off. I believe the battery was at 39%. I plugged the phone into my work computer and it would make the USB connection sound, then after a few seconds it would display drivers failed to install followed by 3 subtle sounds similar to the connection sound. So right away I checked Device Manager and it displayed QHSUSB_DLOAD.
Currently my phone has been charging all night, currently it is being charged at work and there has been no sign of life.
I've tried putting it in the freezer, the light trick, the laptop connecting/disconnecting trick, and the go ole punching the phone trick. None of them have worked.
The phone is definitely not charging at this point as it is stone cold when I hold it or touch the wall charger.
Any ideas what I can do? I don't want to contact Rogers and have to send it in. I've got so many songs, videos and pictures I have yet to backup.
Any help and/or suggestions welcome.
Click to expand...
Click to collapse
Kg810 said:
I would recommend NOT installing the stock Sense 6 upgrade. I installed it a couple days ago and currently my phone is bricked because of it.
Click to expand...
Click to collapse
Well your issue have nothing to do with the sense 6 update. You even said that you have updated the phone a couple of days before your phone died. QHSUSB_DLOAD mode mean your phone motherboard is dead, either because of an hardware failure or because you have flashed something really wrong (probably not your case). So how an hardware failure could be caused by a sofware update and only occur days later....? unfortunately, you must send your phone for repair.
---------- Post added at 05:23 PM ---------- Previous post was at 05:22 PM ----------
mfpreach said:
Thanks,I will look into it tomorrow.
Are there even good drivers for 8.1 yet bearing in mind I don't have a USB 3 port?
Click to expand...
Click to collapse
if you have a win7 computer, then use that one.
alray said:
Well your issue have nothing to do with the sense 6 update. You even said that you have updated the phone a couple of days before your phone died. QHSUSB_DLOAD mode mean your phone motherboard is dead, either because of an hardware failure or because you have flashed something really wrong (probably not your case). So how an hardware failure could be caused by a sofware update and only occur days later....? unfortunately, you must send your phone for repair.
Click to expand...
Click to collapse
Maybe I wasn't clear.
Tuesday night before I went to bed I performed the upgrade.
Wednesday morning, is when the issues started occuring.
Today is May 29th, Tuesday was May 27th, which is 2 days ago, hence why I said I performed the upgrade a couple days ago.
From the time I performed the install Tuesday night to Wednesday morning when I got into work, there was nothing done to the phone. The only thing that was done was the Sense 6 upgrade.
So you're trying to tell me that the upgrade has nothing to do with it?
Kg810 said:
So you're trying to tell me that the upgrade has nothing to do with it?
Click to expand...
Click to collapse
If your phone was 100% stock, I highly doubt the ota could hard brick it.
like I said QHSUSB_DLOAD = defect motherboard
in most cases because:
1- hardware failure
or
2- Flashing something that screwed your phone (i.e flashing something not meant for your phone with S-OFF)
I'm not saying its impossible, but I think it's more a coincidence
alray said:
If your phone was 100% stock, I highly doubt the ota could hard brick it.
like I said QHSUSB_DLOAD = defect motherboard
in most cases because:
1- hardware failure
or
2- Flashing something that screwed your phone (i.e flashing something not meant for your phone with S-OFF)
I'm not saying its impossible, but I think it's more a coincidence
Click to expand...
Click to collapse
I've had the phone for a little over a year and it has been 100% stock. Never tinkered with it in any way shape or form.
I just can't see how it is a mere coincidence that right after the update, my phone starts acting up, and then becomes bricked.
Kg810 said:
I've had the phone for a little over a year and it has been 100% stock. Never tinkered with it in any way shape or form.
I just can't see how it is a mere coincidence that right after the update, my phone starts acting up, and then becomes bricked.
Click to expand...
Click to collapse
Anyway, your only way out of this qhsusb brick is to send your phone for repair.
Sorry
mfpreach said:
Yes it reboots and yes I have a locked bootloader. I would hard reset before sending it out for servicing.
Any other people having this issue?
Click to expand...
Click to collapse
facing same problem with you. my problem haven't fix. from malaysia
akasi91 said:
facing same problem with you. my problem haven't fix. from malaysia
Click to expand...
Click to collapse
From Malaysia as well, hey mind telling me how big is your sense 6 update download size?
kuzumitaiga said:
From Malaysia as well, hey mind telling me how big is your sense 6 update download size?
Click to expand...
Click to collapse
6xxmb.
Hello everyone,
One week after using my new M7, it is not switching on anymore but luckily my PC recognizes it as QHSUSB_DLOAD. I am trying to find it's RUU but I can't get the CID of the phone to download the suitable RUU.
I Googled the forum but I didn't manage to find anyway I can extract the CID of the phone. How can I get the CID when the phone is bricked and not switching on? Anyone can help me?
Thanks
Gamool said:
Hello everyone,
One week after using my new M7, it is not switching on anymore but luckily my PC recognizes it as QHSUSB_DLOAD.
Click to expand...
Click to collapse
Lucky? Not really. ..
QHSUSB_DLOAD can happen for 2 reasons
1. You have flashed something wrong (an incompatible firmware for example) and the phone went in QHSUSB_DLOAD mode. In this case you might be able to unbrick using the unbricking project.
2. If the phone went in QHSUSB_DLOAD mode itself (not directly after a bad flash) then its an hardware problem and will probably need a motherboard replacement.
alray said:
Lucky? Not really. ..
QHSUSB_DLOAD can happen for 2 reasons
1. You have flashed something wrong (an incompatible firmware for example) and the phone went in QHSUSB_DLOAD mode. In this case you might be able to unbrick using the unbricking project.
2. If the phone went in QHSUSB_DLOAD mode itself (not directly after a bad flash) then its an hardware problem and will probably need a motherboard replacement.
Click to expand...
Click to collapse
What exactly happened:
Bought the phone one week ago, unboxed the phone and received an update. After downloading the update the phone refused to install it and it gave some error message that the current software of the phone is modified and the phone cannot continue installing the downloaded new update.
Two days later, I was transferring some files from another phone to it using Wi-Fi direct via an app, the M7 freezes with no response to anything whatsoever, tried to restart the phone using the power button but it didn't switch on.
I can see that there is hope as long as the PC recognize it. Can you sort up my situation again? Thanks.
Gamool said:
What exactly happened:
Bought the phone one week ago, unboxed the phone and received an update. After downloading the update the phone refused to install it and it gave some error message that the current software of the phone is modified and the phone cannot continue installing the downloaded new update.
Click to expand...
Click to collapse
This happen when the phone CID or MID doesn't match the software version.
Two days later, I was transferring some files from another phone to it using Wi-Fi direct via an app, the M7 freezes with no response to anything whatsoever, tried to restart the phone using the power button but it didn't switch on.
Click to expand...
Click to collapse
If it froze and then rebooted in qhsusub its an hardware problem.
I can see that there is hope as long as the PC recognize it.
Click to expand...
Click to collapse
Not really. If the phone is in QHSUSB_DLOAD mode the only known method to revive it is using the Unbrick project which only work when the phone went in this mode after a bad firmware flash. Its not possible to use a RUU neither, the phone must be booted in bootloader/ RUU mode for that. Still worth trying the unbrick project but I don't think there is any hope.
I have a weird problem since Android 9 update. Every now and then when i restart the phone, it either gets stuck on "restarting" or restarts until "Sony" appears on the screen and keeps restarting. The only way to fix this would be to use the Xperia Companion.
I had bought the Phone on Amazon Germany in July 2018. I sent the phone back to them and they returned it claiming they have "Repaired it" but the problem is back again. Is there anyway it could be fixed or am i stuck with this gorgeous little brick forever?
I have had this issue direct after upgrade: Solution was a factory reset (Hold power and Volume up(or down?) several seconds till the phone vibrates some times...
Gesendet von meinem viennalte mit Tapatalk
yekollu said:
Is there anyway it could be fixed or am i stuck with this gorgeous little brick forever?
Click to expand...
Click to collapse
If it's still within warranty, send it back, again.
You should be familliar with the proccess by now.
Some technicians are lazy and because they can't see what the probelem is when they turn it on they just send it back 'fixed'
You might end up with a new phone :good:
Edit: It's worth plugging it in to Xperia Companion and effecting a repair before you send it back, it might be a dodgy build.
Didgesteve said:
If it's still within warranty, send it back, again.
You should be familliar with the proccess by now.
Some technicians are lazy and because they can't see what the probelem is when they turn it on they just send it back 'fixed'
You might end up with a new phone :good:
Edit: It's worth plugging it in to Xperia Companion and effecting a repair before you send it back, it might be a dodgy build.
Click to expand...
Click to collapse
Thanks for the reply. I have to use the Xperia Companion every time to "Fix" the phone and use it again (while going through the whole process of setting up/Restoring)....
Guess i will have to file a complaint again
Didgesteve said:
If it's still within warranty, send it back, again.
You should be familliar with the proccess by now.
Some technicians are lazy and because they can't see what the probelem is when they turn it on they just send it back 'fixed'
You might end up with a new phone :good:
Edit: It's worth plugging it in to Xperia Companion and effecting a repair before you send it back, it might be a dodgy build.
Click to expand...
Click to collapse
I just noticed that my phone has new IMEI number
Just wondering which update caused bootloop
yekollu said:
I have a weird problem since Android 9 update. Every now and then when i restart the phone, it either gets stuck on "restarting" or restarts until "Sony" appears on the screen and keeps restarting. The only way to fix this would be to use the Xperia Companion.
I had bought the Phone on Amazon Germany in July 2018. I sent the phone back to them and they returned it claiming they have "Repaired it" but the problem is back again. Is there anyway it could be fixed or am i stuck with this gorgeous little brick forever?
Click to expand...
Click to collapse
Hi, was just wondering was it firmware update 47.2.A.4.45 that caused bootloop problem? And did you install via Xperia companion or OTA or ..? tia
strate aero said:
Hi, was just wondering was it firmware update 47.2.A.4.45 that caused bootloop problem? And did you install via Xperia companion or OTA or ..? tia
Click to expand...
Click to collapse
Yes and OTA