Hi,
I got a new Motox two days ago, I started it normally, updated the OS as asked and used it without GSM (I am waiting for my nano sim) until last night, when it froze and never came back on.
I tried to press the power button for a looong time, I tried power+volume down, I charged it all night (the led does not come on).
When I connect it to my Linux box it is detected as the Qualcomm QDL device.
I am probably sending it back, but I wonder if I no one knows a magic solution to this problem?
I saw a thread that talks of using the Qualcomm QDL interface to re-flash the bootloader, but that's Windows only and I do not have access to a Windows box.
Any suggestions?
Thanks,
There must be more to this. What exactly have you done with the phone? Need the details.
Never heard of of an X bricking by itself.
KJ said:
There must be more to this. What exactly have you done with the phone? Need the details.
Never heard of of an X bricking by itself.
Click to expand...
Click to collapse
Or it is just a defective phone. It happens. He should just return the device.
KJ said:
There must be more to this. What exactly have you done with the phone? Need the details.
Never heard of of an X bricking by itself.
Click to expand...
Click to collapse
Nope, have not done anything, start up, google account, OS update, encrypt phone and use for one day, that's it. Crazy, right.
Defective device it is.
Related
Hi Guys,
I've done enough research, couldn't really find a legitimate answer. I have a rooted htc one m7 GSM. Rooted with cwm and cm 11 snapshot feb installed. Everything was fine. A few hours ago, I randomly got a "com.google.gapps" has stopped working. I pressed okay and it went away. A few minutes later I got 2-3 of those messages one right after another, and my google applications stopped working. Couldnt send texts, and log on to the play store.
I tried a few fixes and nothing worked. I decided to update my gapps, and while I'm at it install the new cm snapshot from march 17th.
I went into cwm and did wipe davlik and cache partition. Then was installing cwm. It took a while and about halfway through the phone randomly turned off. I knew I had about 50% battery so thats not an issue. I tried turning it back on and it wouldnt. I plugged it into the computer, the computer made the sound as if I plugged something in but nothing populated.
Tried vol up and down, power button alone. Saw a suggestion on here that said to use a bright light under the proximity sensor. Tried that as well.
The phone shows up as "qualcomm" in device manager when plugged in.
I CANNOT take this to HTC or the carrier for many reasons (no it is not stolen lol)
Help?
BlackMamba08 said:
Hi Guys,
The phone shows up as "qualcomm" in device manager when plugged in.
I CANNOT take this to HTC or the carrier for many reasons (no it is not stolen lol)
Help?
Click to expand...
Click to collapse
QHSUSB_DLOAD = hard brick, not possible to fix, needs a motherboard replacement
BlackMamba08 said:
I CANNOT take this to HTC or the carrier for many reasons (no it is not stolen lol)
Help?
Click to expand...
Click to collapse
Unfortunately thats your only option
I'm in Canada. The phone was originally with bell, but I did not buy it from them nor am I on their services currently. Phones boot loader was unlocked and so was its IMEI. Using on a different carrier.
What are my options in terms of htc repair?
BlackMamba08 said:
I'm in Canada. The phone was originally with bell, but I did not buy it from them nor am I on their services currently. Phones boot loader was unlocked and so was its IMEI. Using on a different carrier.
What are my options in terms of htc repair?
Click to expand...
Click to collapse
contact them from here http://www.htc.com/ca/support/service-and-repair/overview.html
and ask how much it will cost to replace the motherboard.
or try this:http://mobiletechvideos.mybigcommerce.com/htc-one-m7/
don't know if they can jtag your device to repair the qhusb brick, ask them.
My brother just bought a new in box Moto X off eBay (ruling out any warranty) about a week ago. Today it asked to update the OS, which he accepted. During the update (green android robot with blue swirly thing inside) the phone simply blinked off and ceased to respond. And I mean NO response. I don't get LED's, boot, fast boot, recovery, charge, ANYTHING. Plugging it into a computer also gives no response.
My bro didn't take note of the OS that it was updating to, but it was just an OTA. He had no suspicious apps, hadn't played with ROM's, just barely had his phone working before this happened.
I spent a long time googling for this same problem, but no results. Everyone at least gets SOME response out of their phone. I can't imagine this is a hardware problem, and I'm certain he had plenty of charge when he initiated the update (only half a day of use on the charge, should have been at %50-60 on the low side).
Anybody have an idea on how to proceed? Any info would be greatly appreciated, even a link to a helpful thread that I missed.
Phone is a 1st gen (2013) Moto X on AT&T.
Brett316 said:
My brother just bought a new in box Moto X off eBay (ruling out any warranty) about a week ago. Today it asked to update the OS, which he accepted. During the update (green android robot with blue swirly thing inside) the phone simply blinked off and ceased to respond. And I mean NO response. I don't get LED's, boot, fast boot, recovery, charge, ANYTHING. Plugging it into a computer also gives no response.
My bro didn't take note of the OS that it was updating to, but it was just an OTA. He had no suspicious apps, hadn't played with ROM's, just barely had his phone working before this happened.
I spent a long time googling for this same problem, but no results. Everyone at least gets SOME response out of their phone. I can't imagine this is a hardware problem, and I'm certain he had plenty of charge when he initiated the update (only half a day of use on the charge, should have been at %50-60 on the low side).
Anybody have an idea on how to proceed? Any info would be greatly appreciated, even a link to a helpful thread that I missed.
Phone is a 1st gen (2013) Moto X on AT&T.
Click to expand...
Click to collapse
I'm in the same boat... I recently bought a Moto X (2013) on eBay and having had the Atrix HD previously, I thought rooting should be simple.. yeah, no, it wasn't... i'm now hard bricked. I followed a guide about updating the driver and using the program that tricks the driver signing, and it all went as stated, except the phone still won't turn on. Adb can't see it, neither can mfastboot.. RSD Lite does see it tho it fails flashing.. I don't know what to do.. I don't have much $ and I had just saved up for awhile so any help would be appreciated
Brett and Elisha, are you running Windows? If so, when you connect your phone, does Windows chime as if it recognizes something is connected via USB?
platinumthomas said:
Brett and Elisha, are you running Windows? If so, when you connect your phone, does Windows chime as if it recognizes something is connected via USB?
Click to expand...
Click to collapse
ya exactly
i have the same problem but in my case the phone was good but while coping video the phone just turned off.
that's it after that im stuck at boot loader unlocked ...
pls somebody suggest me what to do to get back my moto x working
amg0005 said:
ya exactly
i have the same problem but in my case the phone was good but while coping video the phone just turned off.
that's it after that im stuck at boot loader unlocked ...
pls somebody suggest me what to do to get back my moto x working
Click to expand...
Click to collapse
I started here: http://forum.xda-developers.com/moto-x/general/moto-x-root-pogress-60-t3071602
After step 3, manually installing the unsigned drivers, I had to follow this: http://forum.xda-developers.com/moto-x/general/how-to-unbricked-hard-bricked-phone-t3146036
I skipped to "Now software part. Go to unzipped C:\Python27 folder, launch bat-file, and wait until finish:
RUN_blank_bootloader_flash.bat"
It took a bit of time, but the phone rebooted and I am rooted.
platinumthomas said:
Brett and Elisha, are you running Windows? If so, when you connect your phone, does Windows chime as if it recognizes something is connected via USB?
Click to expand...
Click to collapse
yes!! it does recognize when i connect it to the computer. can i do anything to get it on ???
sachinrao13 said:
yes!! it does recognize when i connect it to the computer. can i do anything to get it on ???
Click to expand...
Click to collapse
There's a thread on this forum titled 'Resurrecting a dead Moto X'. It describes your scenario in detail and explains a way to fix it.
Hello Moto,
So I got my Moto G5s Plus awhile back when it was still new and I tried to root it right off (I know...it was stupid, I realize I should've waited a little until the stock firmware was released and more guides were made), and basically I ended up hard bricking my device.
There are no lights, the screen is completely blank, and the power button does absolutely nothing.
I have heard of a way to revive it from level 0, however, and I was on the path to doing that until I realized that-for some reason-my laptop does not recognize my dead phone at all. In the guide (which I've long since lost the link to..) it said that my phone would appear in my device manager (>start>right click on Computer>manage) under the android tab after installing a bunch of ADB drivers and such, as "ADB-somethingsomething". No such thing happened; I couldn't even find the tab it was referencing. Even after uninstalling and reinstalling the drivers that it mentioned, I couldn't seem to get my laptop to recognize my phone.
Interestingly enough, or perhaps not, I plugged it into my brother's laptop and it recognized it just fine (note, he had the drivers already installed and has meddled quite a bit already in this area).
Anyway, so now I have a pretty much mint condition hardware Moto G5s Plus, and I kind of don't want to spent money on another phone unless I know for sure that I can't fix this one. Is there any way to revive it from the dead?
P.S. I've found the stock ROM for the phone...but there's several different packages. (like..NPS26.116-26; NPS26.116-45; NPSS26.116-45-5; etc...) This my be a very stupid question..but how should I know which one is the one I need to download?
Any and all advice/help would be appreciated.
Thank you
[SOLVED]
So I managed to get it working without using a virtual machine.
To address the first problem, my phone wasn't even charged. To solve this I took a rubber band and tied it around the power and volume down buttons and attached it to a wall outlet for about an hour. (The little white light was flashing to signal that it was receiving power...which was more than I had accomplished than..ever..really...)
The second problem was my computer. I still don't know why it worked out like this, but essentially my computer never recognized my phone as the HS-USB or anything. Instead, my computer recognized it as Motorola ADB Interface (even though it was technically off and hard bricked..). This made recovering it easy, as I simply could fastboot flash the correct stock rom to my phone and go from there.
After trying a few different stock ROMs, I finally got the right one, and could boot into bootloader. And thus, finally, I was able to install TWRP, the OS back, Xposed, and Magisk.
I've used my phone for a bit now and no problems have come up. Installing Xposed did take a bit longer than I thought it would, but other than that I got me phone back.
My moto g5s plus is completely dead even bootloader is not working nothing to show just blank how I can get the solution of this problem. Company is asking to change the motherboard. Help
jaura.mohit said:
My moto g5s plus is completely dead even bootloader is not working nothing to show just blank how I can get the solution of this problem. Company is asking to change the motherboard. Help
Click to expand...
Click to collapse
Are they charging u for the motherboard Change
Yes 18000 rupees
---------- Post added at 06:55 AM ---------- Previous post was at 06:29 AM ----------
yograjfire18 said:
Are they charging u for the motherboard Change
Click to expand...
Click to collapse
18000 rupees hel p me to recover my phone
Rooting is software based thing, which should not damage hardware to that level,, right?
The blank-flash stuff can be helpful for you guys, but we don't have blank-flash files for our device.
You can search, learn and manage how to do it.
EDIT: can you check what happens if you keep pressed powe key and volume- key for atleast 2 minuts ??
____Mdd said:
Rooting is software based thing, which should not damage hardware to that level,, right?
The blank-flash stuff can be helpful for you guys, but we don't have blank-flash files for our device.
You can search, learn and manage how to do it.
EDIT: can you check what happens if you keep pressed powe key and volume- key for atleast 2 minuts ??
Click to expand...
Click to collapse
Yea, no, this is 100% software damage. Like I said, I have a mint condition (hardware wise) phone. I'm pretty sure what I did to mess it up was overwrite the data files for the previous OS. I remember trying to get it back to stock ROM, but having a crap ton of trouble finding it...and then pretty much doing a fight or flight thing and trying a stupid and edgy alternative. (I also remember, even while the phone was still working, it only booted into TWRP once or twice, otherwise it would always come up with an error)
I feel like all I need to do is flash the stock ROM to the device...but without my laptop even recognizing it, I don't know how. Essentially, the question being, is there a way to flash the stock ROM to my device without TWRP, without bootloader, without using the device at all (just my laptop); and if there is...does anyone know how?
Pressing the power and volume buttons did nada.
[edit]
I did some searching and I actually found the two links that I used while trying to recover my phone from the dead.
http://www.aryk.tech/2017/09/moto-g5s-plus-unbrick-solutions.html
https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457
The difference for me is that I never got my laptop to recognize it as any of the "HS-USB Bulk, HS-USB QDLoad 9008, QHS-USB DLoad 9008"; that's where I stopped in the steps.
I'll be trying to follow the steps in the first link again, but this time through virtualbox (make sure there's no conflicting drivers and whatnot). I'll post back with results whenever I get around to it.
flash -61
used this thread to try and return to stock:
https://forum.xda-developers.com/moto-e4-plus/how-to/moto-e4-qualcomm-owens-completely-to-t3743441
My **** turned off, now it wont turn on period. Cant go into any kind of download mode NOTHING. I have no warranty, I got the phone off the street. Tried to flash a custom rom did it wrong then tried to return it to stock because I didnt make a backup. I'm ready to throw it at a wall.
It WAS a boost moto e4 plus owens xt1776
If it won't turn on, there's not much you can do. The battery is technically removable, so you COULD try removing it and putting it back in, but I doubt it will help. You might want to see if Motorola will repair it. It's a longshot, but they might help you. I wouldn't tell them you bought it off the street. Just say you don't have a receipt.
I know on older Motorola's, if you plugged them in and let it charge for a few hours, they would turn back on.
But I don't know what you did. It would help if you provided more info on what you did, so we could gain a better perspective.
ATTACK said:
I know on older Motorola's, if you plugged them in and let it charge for a few hours, they would turn back on.
But I don't know what you did. It would help if you provided more info on what you did, so we could gain a better perspective.
Click to expand...
Click to collapse
You're right, I forgot about that one..
ATTACK said:
I know on older Motorola's, if you plugged them in and let it charge for a few hours, they would turn back on.
But I don't know what you did. It would help if you provided more info on what you did, so we could gain a better perspective.
Click to expand...
Click to collapse
If he temper any of the device partition than probably it will be a soft brick and should be resolved by the service center guy like i did this before three times with my Moto E4 and it won't turn on. No fastboot mode, no recovery, Just the notification light when connecting to a power source and nothing else. I also got the new IMEI number.
TheHitMan said:
If he temper any of the device partition than probably it will be a soft brick and should be resolved by the service center guy like i did this before three times with my Moto E4 and it won't turn on. No fastboot mode, no recovery, Just the notification light when connecting to a power source and nothing else.
Click to expand...
Click to collapse
We don't know if he messed with his partitons, though. Without further details as to what he did, all we're doing is guessing.
Sorry about my delay had some stuff go down. Uhm, I followed that thread, ran the commands listed, used a sprint factory instead of a boost, from what i read in that thread, it should have worked. But now I dont even get a notification light when i charge.
I'm having the same problem as him and I feel like I'm making some progress, but I still can't fix it. Here's my posts on what I found from that thread. They are probably better suited here anyway. https://forum.xda-developers.com/showpost.php?p=76459007&postcount=21
doodalydoo said:
I'm having the same problem as him and I feel like I'm making some progress, but I still can't fix it. Here's my posts on what I found from that thread. They are probably better suited here anyway. https://forum.xda-developers.com/showpost.php?p=76459007&postcount=21
Click to expand...
Click to collapse
Don't forget that the OEM files are labeled differently for Boost Mobile users, messing that labeling up during fastboot will cause it not to boot as well..
bcrichster said:
Don't forget that the OEM files are labeled differently for Boost Mobile users, messing that labeling up during fastboot will cause it not to boot as well..
Click to expand...
Click to collapse
I have the carrier unlocked version. I think the way I bricked my phone is that I OTA updated my phone and then tried to revert back to stock. I've seen a video on youtube of somebody who did the exact same thing and was able to unbrick his phone. I think the main problem right now is I can't find the right firmware files to use in QFIL. The stock firmware zips don't have the right files that QFIL needs
Bricked Pixel 5a/QUSB code of death
Has anyone found a solution to the QUSB code of death? I entered the club last week. I was using my Pixel 5a as usual, scrolling through social media. Then suddenly, the screen freezes, the phone shuts off, reboots, freezes on the Google logo, then shuts off. Has not turned on since.
I have done all of the rudimentary “diagnostic solutions” but to no avail. When I plug the phone into my computer, the QUSB device code shows up in device manager.
I filed a request to obtain a replacement/repair with Google last week. They gave me the option to replace the device after determining it was bricked. However, Google seems to think it’s liquid damaged and ineligible for repair/replacement under the warranty. The phone has never had any sort of extensive liquid contact.
I am currently waiting to receive the same exact phone back. So far, I have not been able to find a legitimate solution other than sketchy “freezer” fixes and uncontrolled banging around the device with the hopes of it turning on again.
Has anyone figured out a legitimate solution to the same problem among multiple generations of Pixel devices?
can you get into bootloader? power on + vol down.
or a response when you have it plugged in with adb devices or fastboot devices?
or try a force off? power + vol down + vol up for about 30 seconds then try to power on again?
I have already tried those solutions. So far, nothing has worked.
wow. i don't know what's going on. mine did the same thing on sunday. got it to clean flash the official 13 with the chrome flash tool. was getting set back up and it happened again. and i just replied to another thread on here about someone it happened to. they better not tell me mine is suspected to be liquid damaged. but if they're not gonna replace it, i suppose you could try the freezer trick. and the best thing to do would probably buy a cheap 3a and trade it in for a 6a. maybe i shouldn't go with pixels anymore though. only had the 3a and now this one. they should get back to me tomorrow. i gave up trying to fix it the 2nd time it happened. wouldn't boot into userspace fastboot. never saw the qusb issue
Same thing just happened to my wife's 5a while she was browsing Facebook. There is no user accessible fix for this; while the QPST/QFIL programs may be found online, the MBN files necessary to reimage the device are not.
If you bought your device within the last 12 months, you should be able to get it repaired under warranty.
Here is the link for warranty repair.
V0latyle said:
Same thing just happened to my wife's 5a while she was browsing Facebook. There is no user accessible fix for this; while the QPST/QFIL programs may be found online, the MBN files necessary to reimage the device are not.
If you bought your device within the last 12 months, you should be able to get it repaired under warranty.
Here is the link for warranty repair.
Click to expand...
Click to collapse
My wife's phone now has this issue and we have important pictures on there we don't want lost. Is there a way to use the QPST program to get files off of the phone? Is there another way to get the files off of the phone when we cant get the device to even power on? When I plug it into a computer, I do get the QUSB device to appear.