Related
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
dear, sorry the English, but I need a help from you.
I made the installation of IMG extracted the KDZ and did flash the recovery, however, now my machine not the sign of life, the computer does not detect the device, the device does not turn on, not of any sign of life. already tried in various corners anything to help me have some solution. I did the procedure based on the stock rom flash D405 with img extracted files. After that the only active device the display if I put to load without the battery, which displays the battery with a question mark. The device does not enter download mode, does not go into recovery, does not display anything, as if completely dead. Does anyone have aware and know any solution to the problem? Note: I've tried the LG flahs tools, it does not detect the device.
You have probably the worst case of them all. I suggest you to take your phone to warranty and see if they can replace it (because there probably isn't any way to fix it). If your warranty is void, then, I'm afraid, you will have to get a new device. I have had this issue myself, and it was solved only by replacing whole internals of the phone. Good thing that I still had my warranty, so it didn't cost anything. Good luck.
linasj said:
You have probably the worst case of them all. I suggest you to take your phone to warranty and see if they can replace it (because there probably isn't any way to fix it). If your warranty is void, then, I'm afraid, you will have to get a new device. I have had this issue myself, and it was solved only by replacing whole internals of the phone. Good thing that I still had my warranty, so it didn't cost anything. Good luck.
Click to expand...
Click to collapse
but this happened to you because of flash ROMS? How long on average it took for you to get the unit back?
wmosquini said:
but this happened to you because of flash ROMS? How long on average it took for you to get the unit back?
Click to expand...
Click to collapse
Yes. I tried to flash a ROM (which requires an unlocked bootloader), but for some reason the bootloader wasn't actually unlocked, and flashing a ROM caused the device to be bricked. This is probably what you would call a hard-brick.
In my case, replacement took a little more than a week. But this could differ from country to country.
linasj said:
Yes. I tried to flash a ROM (which requires an unlocked bootloader), but for some reason the bootloader wasn't actually unlocked, and flashing a ROM caused the device to be bricked. This is probably what you would call a hard-brick.
In my case, replacement took a little more than a week. But this could differ from country to country.
Click to expand...
Click to collapse
But in time to take the assistance, you said what about it? The unit stopped working alone?
wmosquini said:
But in time to take the assistance, you said what about it? The unit stopped working alone?
Click to expand...
Click to collapse
Exactly. Since the device cannot be turned on, I don't think they have any way of checking if it was rooted or tampered with in any way. So your best bet is to just play dumb and tell them your phone doesn't boot up. That helped me to get it fixed for free.
linasj said:
Exactly. Since the device cannot be turned on, I don't think they have any way of checking if it was rooted or tampered with in any way. So your best bet is to just play dumb and tell them your phone doesn't boot up. That helped me to get it fixed for free.
Click to expand...
Click to collapse
Legal, tomorrow I will even take the guarantee to solve as fast as possible. Really the device not the sign of life at all. I will inform you that the device was carrying at night and just when I catch him in the morning, he was like that.
Thank you for your help. : D
My first L90 didn't have a functional GPS, was brand new (1 week), problem was I rooted in the first day
Factory reset, hid superuser app, got a new l90
Gud luck
bacitoto said:
My first L90 didn't have a functional GPS, was brand new (1 week), problem was I rooted in the first day
Factory reset, hid superuser app, got a new l90
Gud luck
Click to expand...
Click to collapse
hard reset does not remove all traces of root. There is RCT checking. u can be sure that have no traces of root when RCT was reset. On kit kat we have chance to reset it without reflashing. But on 5.0 only reflash
---------- Post added at 11:17 ---------- Previous post was at 11:11 ----------
wmosquini said:
dear, sorry the English, but I need a help from you.
I made the installation of IMG extracted the KDZ and did flash the recovery, however, now my machine not the sign of life, the computer does not detect the device, the device does not turn on, not of any sign of life. already tried in various corners anything to help me have some solution. I did the procedure based on the stock rom flash D405 with img extracted files. After that the only active device the display if I put to load without the battery, which displays the battery with a question mark. The device does not enter download mode, does not go into recovery, does not display anything, as if completely dead. Does anyone have aware and know any solution to the problem? Note: I've tried the LG flahs tools, it does not detect the device.
Click to expand...
Click to collapse
Did u flash it from 5.0 or 4.4? This problem may have solve without service center. But if u have warranty, it must not worry u.
@linasj
Hello, I just want to know that while booting, did your phone show the message "Secure booting error"?
I am getting this message at the LG logo and then device just shuts off.
No, I don't think I ever got this message.
Sent from my LG-D405N using XDA Free mobile app.
pick.orion said:
@linasj
Hello, I just want to know that while booting, did your phone show the message "Secure booting error"?
I am getting this message at the LG logo and then device just shuts off.
Click to expand...
Click to collapse
In my case, the device did not care and neither carried, gave no sign of life. I sent him for assistance in less than one week they made the repair by warranty.
Actually my friend bricked his phone, he flashed the 5.1 bootloader and radio.then somehow he flasheed back to 5.0.1 stock. then he flashed Euphoria again. The phone rebooted fine and he went to sleep. Then woke up and found out his phone was dead. And all buttons combo didn't work at all. It's just a piece of dead body.When plugging into the PC, it shows qhsusb_bulk. There were devices that had same problems but they managed to unbrick it, But those methods don't apply to Shamu. Odd thing is I did the same thing so far my Nexus 6 is fine .I've started worrying, tho. We bought it from amazon.fr and I'm sure i dont want to send it back all the way from China to France.
Also , i read some dudes encountered the same problem after flashing Cm12 with 5.1 BL. I really need your help.
I tried Nexus Root Toolkit to flash the factory image, it didnt work. It's still using the fastboot, and ofc i don't get to go there.
I've installed the Qualcomm_QHSUSB_driver, but it doesn't seem to fix anything.
no one?
Mine has done the same thing. Went to flash 5.1 nexus image from the google dev site. The flash did boot and radio and failed size on system ( even re-downloaded). I plug my N6 into my linux machine and this what I get on lsusb "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)". I am also in need of help.
This updates been a nightmare
synapses said:
Mine has done the same thing. Went to flash 5.1 nexus image from the google dev site. The flash did boot and radio and failed size on system ( even re-downloaded). I plug my N6 into my linux machine and this what I get on lsusb "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)". I am also in need of help.
Click to expand...
Click to collapse
So you're like me, no way to enter bootloader right? I've seen some other phones with the same problems but they figured a way out to solve it. I don't know we'll get that
beachbum40 said:
This updates been a nightmare
Click to expand...
Click to collapse
I'm not sure it has anything to do with the update. My friend didn't flash the 5.1 google factory image . He flashed the 5.1 BL on a 5.0.2 aosp based rom then went back to stock 5.0.1 then flashed the same 5.0.2 aosp rom. Now it ends up dead.
This happened on Samsung devices too and it was a emmc issue, so the internal drive among others was no longer readable and writable and hardware like buttons was not working either. Unless someone comes with the golden tip you`ll have to turn it in for repair. Good luck guys
randy6644 said:
So you're like me, no way to enter bootloader right? I've seen some other phones with the same problems but they figured a way out to solve it. I don't know we'll get that
Click to expand...
Click to collapse
doing some reading and it seams to be a broken bootloader.
synapses said:
doing some reading and it seams to be a broken bootloader.
Click to expand...
Click to collapse
I'm also a g2 owner, some just broke their devices and ended up sth similar. But they managed to unbrick it. I don't know if we stand a chance to bring it back to life.
I'm still stuck. Any progress ?
synapses said:
doing some reading and it seams to be a broken bootloader.
Click to expand...
Click to collapse
Any progress? I tried several ways and none of them worked
I had to RMA
randy6644 said:
Actually my friend bricked his phone, he flashed the 5.1 bootloader and radio.then somehow he flasheed back to 5.0.1 stock. then he flashed Euphoria again. The phone rebooted fine and he went to sleep. Then woke up and found out his phone was dead. And all buttons combo didn't work at all. It's just a piece of dead body.When plugging into the PC, it shows qhsusb_bulk. There were devices that had same problems but they managed to unbrick it, But those methods don't apply to Shamu. Odd thing is I did the same thing so far my Nexus 6 is fine .I've started worrying, tho. We bought it from amazon.fr and I'm sure i dont want to send it back all the way from China to France.
Also , i read some dudes encountered the same problem after flashing Cm12 with 5.1 BL. I really need your help.
I tried Nexus Root Toolkit to flash the factory image, it didnt work. It's still using the fastboot, and ofc i don't get to go there.
I've installed the Qualcomm_QHSUSB_driver, but it doesn't seem to fix anything.
Click to expand...
Click to collapse
Something should be able to be done using QPST (i.e., to force flash the bootloader), but that is above my level of knowledge.
efrant said:
Something should be able to be done using QPST (i.e., to force flash the bootloader), but that is above my level of knowledge.
Click to expand...
Click to collapse
I'm going through similar with a dead Nexus 7. I think the eMMC died in it though, as it just went out without any tinkering. No sign of life on the device, but is picked up as a Qualcomm modem port and detected by QPST in download mode. I don't have/can't find the hex files required by QPST to flash it though.
I theorize that if a working device can be put in QPST "diag" mode, then QPST will allow exporting the storage contents in a flashable hex file, and that file could be used to restore the boot partitions on the dead device. I haven't been able to find information about this "diag"nostic mode, however.
Same issue guys, Upgraded to 5.1 OTA rooted and flashed cm12 tried to reboot. Nothing. Stuck in "Qualcomm HS-USB QDLoader 9008" QPST will recognize it in Download mode. If we can get these Hex files I will give it a shot. Thanks!
http://bbs.gfan.com/forum.php?mod=viewthread&tid=7863761
found sth here dont know if its useful, all written in Chine
randy6644 said:
http://bbs.gfan.com/forum.php?mod=viewthread&tid=7863761
found sth here dont know if its useful, all written in Chine
Click to expand...
Click to collapse
Cant find much relating to our issue but there may be relevant info there, we cant download or make an account on that site due to our american IP anyway.
i will upload them when im home. i read sth about qc diag interface,qcn stuff. but this thread is a tutorial for cracking the China Telecom band. Dont know if theres anything useful
randy6644 said:
i will upload them when im home. i read sth about qc diag interface,qcn stuff. but this thread is a tutorial for cracking the China Telecom band. Dont know if theres anything useful
Click to expand...
Click to collapse
If you are able to export the Hex file with everything we need to restore through QPST you will be saving alot of peoples ass as the number of hard bricks are growing hourly now! Or at least the threads being started about hard bricks are! Appreciate the help brother. AdA
im not sure if i can find the useful files you need. just trying my best to contact that op , if he knows sth. my ass will ne saved. but its 1 .30 am in China.i dont think hes awake. i will keep an eye on that.
Hello,
Yesterday @alray was helping me reboot my phone since I was stuck on the Bootloader and it kept rebooting to "no
command" I ended up installing the RUU via the adb htc_fastboot, and it worked!
Here is the link to that thread: http://http://forum.xda-developers.com/htc-one/help/htc-one-m7-gpe-command-t3151389/page3#post61741252
So when I started my phone and I started to register my account again since everything was wiped clean, everything was fine then all of a sudden the phone froze and then it completely turned off. I do not know why. I was in the settings page when it froze. Now it will not turn on anymore. I have no idea why it's doing this. When I plug in the charger, no green light indicator comes on. It all seemed fine. Your help would be greatly appreciated!
LATOKYO said:
Hello,
Yesterday @alray was helping me reboot my phone since I was stuck on the Bootloader and it kept rebooting to "no
command" I ended up installing the RUU via the adb htc_fastboot, and it worked!
Here is the link to that thread: http://http://forum.xda-developers.com/htc-one/help/htc-one-m7-gpe-command-t3151389/page3#post61741252
So when I started my phone and I started to register my account again since everything was wiped clean, everything was fine then all of a sudden the phone froze and then it completely turned off. I do not know why. I was in the settings page when it froze. Now it will not turn on anymore. I have no idea why it's doing this. When I plug in the charger, no green light indicator comes on. It all seemed fine. Your help would be greatly appreciated!
Click to expand...
Click to collapse
Is it detected when you connect it to your computer? What does it says when you go in windows device manager with the phone connected?
alray said:
Is it detected when you connect it to your computer? What does it says when you go in windows device manager with the phone connected?
Click to expand...
Click to collapse
It's really Interesting. Each time I plug in the device, this comes up:
Forge HS-USB QDLoader 9008 (COM4) Installed
LATOKYO said:
It's really Interesting. Each time I plug in the device, this comes up:
Forge HS-USB QDLoader 9008 (COM4) Installed
Click to expand...
Click to collapse
Then its really bad news, sorry.
If your phone randomly shut down and now detected as dload mode its an hardware failure.
alray said:
Then its really bad news, sorry.
If your phone randomly shut down and now detected as dload mode its an hardware failure.
Click to expand...
Click to collapse
But why? It was completely fine yesterday. The battery was perfect. Why does it completely fail after I do the RUU?
alray said:
Then its really bad news, sorry.
If your phone randomly shut down and now detected as dload mode its an hardware failure.
Click to expand...
Click to collapse
There needs to be a way to solve this issue. It cannot be coincidental that it just fails now.
LATOKYO said:
But why? It was completely fine yesterday.
Click to expand...
Click to collapse
No it wasn't completely fine yesterday, don't you remember why you had to flash a ruu? Your phone, for an unknown reason, randomly shut down and was only able to boot in recovery mode. Maybe the emmc chip was starting to act weird and some data got corrupted, flashing the ruu fixed that until the emmc died completely today, that is one possibility.
The battery was perfect. Why does it completely fail after I do the RUU?
Click to expand...
Click to collapse
If it had something to do with the RUU, the phone wouldn't have booted and it would still be stuck at the same point it was yesterday.
---------- Post added at 01:52 PM ---------- Previous post was at 01:39 PM ----------
If you want you can try the unbrick project but like explained in that guide, it will only work if the phone went in this mode directly after flashing an incompatible firmware which is not possible on your phone since it's S-ON. Anyway it worth a try before sending it for repair / garbage but don't expect this to work....
alray said:
No it wasn't completely fine yesterday, don't you remember why you had to flash a ruu? Your phone, for an unknown reason, randomly shut down and was only able to boot in recovery mode. Maybe the emmc chip was starting to act weird and some data got corrupted, flashing the ruu fixed that until the emmc died completely today, that is one possibility.
If it had something to do with the RUU, the phone wouldn't have booted and it would still be stuck at the same point it was yesterday.
---------- Post added at 01:52 PM ---------- Previous post was at 01:39 PM ----------
If you want you can try the unbrick project but like explained in that guide, it will only work if the phone went in this mode directly after flashing an incompatible firmware which is not possible on your phone since it's S-ON. Anyway it worth a try before sending it for repair / garbage but don't expect this to work....
Click to expand...
Click to collapse
I am not going to accept the fact that it has completely failed interns of hardware. I will find a solution.
LATOKYO said:
I am not going to accept the fact that it has completely failed interns of hardware. I will find a solution.
Click to expand...
Click to collapse
Do you even know what is qualcomm download mode? It mean that the phone can't boot because of hardware damage (probably the emmc) or corrupted bootloader. To possibly fix a corrupted bootlaoder on a M7 you'll need to send your phone to a JTAG service, if its an hardware failure you'll need a new motherboard. You are not the first one in this situation, hundred of M7 died this way here and same for other devices using qualcomm's chipset. Unfortunately, I never heard of someone being able to push a new bootloader using QPST like its possible on some other qualcomm devices to fix a possibly corrupted bootloader.
alray said:
Do you even know what is qualcomm download mode? It mean that the phone can't boot because of hardware damage (probably the emmc) or corrupted bootloader. To possibly fix a corrupted bootlaoder on a M7 you'll need to send your phone to a JTAG service, if its an hardware failure you'll need a new motherboard. You are not the first one in this situation, hundred of M7 died this way here and same for other devices using qualcomm's chipset. Unfortunately, I never heard of someone being able to push a new bootloader using QPST like its possible on some other qualcomm devices to fix a possibly corrupted bootloader.
Click to expand...
Click to collapse
I know it's happened before, but ill try everything before I have to acquiesce. I also read posts with how some people their phone did not turn for 2 days, but then all of a sudden, it comes back on. I am being super optimistic as you can tell.... I am not mad at you or anything, I truly appreciate your help.
I will let you know if anything updates after tonight or tomorrow.
LATOKYO said:
I know it's happened before, but ill try everything before I have to acquiesce. I also read posts with how some people their phone did not turn for 2 days, but then all of a sudden, it comes back on. I am being super optimistic as you can tell.... I am not mad at you or anything, I truly appreciate your help.
I will let you know if anything updates after tonight or tomorrow.
Click to expand...
Click to collapse
Don't worry, I wasn't thinking that you was mad at me, I know its frustrating when an expensive piece of hardware fails....
I also read posts with how some people their phone did not turn for 2 days, but then all of a sudden, it comes back on.
Click to expand...
Click to collapse
Yep and in some cases also went back again in dload mode later....
Anyway good luck
alray said:
Don't worry, I wasn't thinking that you was mad at me, I know its frustrating when an expensive piece of hardware fails....
Yep and in some cases also went back again in dload mode later....
Anyway good luck
Click to expand...
Click to collapse
So now when I plug in the device, it says " USB input device"
Good news, bad news?
Hi All,
i was installing in past a developer preview of Android M on my Nexus 6 but something went wrong, and my phone ist bricked.
I tried to flash a new firmware with NExus tools but it is saying that device is locked, it wont upload any files to it.
i get DEVICE IS LOCKED. Status Code: 2
Is there anyone that had a similar problem? Can it be repaired somehow? Please help. THX
I
michalchovanak said:
Hi All,
i was installing in past a developer preview of Android M on my Nexus 6 but something went wrong, and my phone ist bricked.
I tried to flash a new firmware with NExus tools but it is saying that device is locked, it wont upload any files to it.
i get DEVICE IS LOCKED. Status Code: 2
Is there anyone that had a similar problem? Can it be repaired somehow? Please help. THX
Click to expand...
Click to collapse
If you have TWRP recovery:
1) you can try a factory reset.
2) If that doesn't work, connect to your PC and transfer a ROM.
If you have stock recovery, you can try a factory reset. If that doesn't work there's nothing you can do. RMA (return it to Motorola for repair/replacement).
none
check this out. I really doubt your bricked
http://androidforums.com/threads/help-please-re-lock-nexus-6.891724/