I was rooting my 4.4 Moto Verizon from MotoMaker using Moto X Toolkit. My device was already Write-protect Off (0). So I skipped the MotoWpNoMo step and went to downgrading my Moto to 4.2.2 (Post-camera). I was in bootloader during the downgrading. Here's where I bricked.
Are you in bootloader or android?:android
Your device will now reboot to bootloader.
Press any key to continue . . .
< waiting for device >
...
OKAY [ 0.363s]
finished. total time: 0.364s
sending 'partition' (32 KB)...
OKAY [ 0.240s]
writing 'partition'...
This may take a few seconds, if a
different partition table is being
flashed since we need to backup
and restore a few partitions
FAILED (status read failed (Too many links))
finished. total time: 117.843s
sending 'motoboot' (1588 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.002s
sending 'logo' (2563 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.003s
< waiting for device >
Click to expand...
Click to collapse
Once failed on partition, a window popped up saying "qhsusb_dload failed to install driver"
Now my phone is just black screen. I didn't see what happen to my phone because I was reading the window popup. I believe my phone is still on, just with a black screen and no buttons work.
I tried holding the power button for 5 seconds, for 1 minute. Both didn't work
Tried Power + Vol down for 5 seconds. Didn't work.
Is this hardbrick? What to do? Does MotoMaker offer warranty? I purchased device Jan 20.
HeresOtis said:
I was rooting my 4.4 Moto Verizon from MotoMaker using Moto X Toolkit. My device was already Write-protect Off (0). So I skipped the MotoWpNoMo step and went to downgrading my Moto to 4.2.2 (Post-camera). I was in bootloader during the downgrading. Here's where I bricked.
Once failed on partition, a window popped up saying "qhsusb_dload failed to install driver"
Now my phone is just black screen. I didn't see what happen to my phone because I was reading the window popup. I believe my phone is still on, just with a black screen and no buttons work.
I tried holding the power button for 5 seconds, for 1 minute. Both didn't work
Tried Power + Vol down for 5 seconds. Didn't work.
Is this hardbrick? What to do?
Click to expand...
Click to collapse
Sorry Its a expensive paper weight as soon as you see qhsusb_dload, its toast, if you can't access the fast boot screen it done
Sent on my Moto X
HeresOtis said:
I was rooting my 4.4 Moto Verizon from MotoMaker using Moto X Toolkit. My device was already Write-protect Off (0). So I skipped the MotoWpNoMo step and went to downgrading my Moto to 4.2.2 (Post-camera). I was in bootloader during the downgrading. Here's where I bricked.
Once failed on partition, a window popped up saying "qhsusb_dload failed to install driver"
Now my phone is just black screen. I didn't see what happen to my phone because I was reading the window popup. I believe my phone is still on, just with a black screen and no buttons work.
I tried holding the power button for 5 seconds, for 1 minute. Both didn't work
Tried Power + Vol down for 5 seconds. Didn't work.
Is this hardbrick? What to do?
Click to expand...
Click to collapse
by Post do you mean you installed the 4.2.2 and not the 4.2.2 camera update.
this is the 4.2.2 ota
Android 4.2.2
Blur_Version.139.10.53.ghost_verizon.Verizon.en.US
This is the 4.2.2 Camera Update
Android 4.2.2
Blur_Version.139.15.1.ghost_verizon.Verizon.en.US
which one did you try and install. if you installed just the 4.2.2 firmware then from what i have read yes it dose cause issues with your phone and there is no fix for it other then getting it replaced if you cant get back into the bootloader.
i would first try plugging your phone into a wall charger and see if you can get it to boot into bootloader via Volume up + Power.
if you still think your phone is on plug it into your computer and see if it picks it up.
Best way is to open a command promote windows and Cd to your adb directory an type below command
Code:
adb devices
if it picks it up try
Code:
adb reboot bootloader
if none of the above works time for a replacement sorry to say
I was using VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-57-X-1_CFC_1FF.xml.zip.
When I plug my phone into computer, I can hear the usb sound come on, but it's not the regular plug-in sound. And when I disconnect, its the regular disconnect usb sound.
EDIT:
I think it's the no driver usb plug-in sound.
I believe my laptop is still searching for the QHSUSB_DLOAD driver, but can't find any in Windows Update. When I scan for hardware changes in Device Manager, it searches for the driver and I can hear the no driver sound again.
adb devices shows blank list
HeresOtis said:
I was using VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-57-X-1_CFC_1FF.xml.zip.
When I plug my phone into computer, I can hear the usb sound come on, but it's not the regular plug-in sound. And when I disconnect, its the regular disconnect usb sound.
Click to expand...
Click to collapse
yes she is gone sorry
Edit: so i have done some reading and other phones have had this issues and have fixed it but it would take alot of playing around and the knowledge to fix it. i would just call your carrier tell them you was on 4.2.2 and took the 4.2.2 camera update and now your phone wont boot and get your phone replaced for free
flashallthetime
hasn't this happened to just about anyone who flashes the 4.2.2 OTA instead of the 4.2.2 camera update.
dray_jr said:
yes she is gone sorry
Edit: so i have done some reading and other phones have had this issues and have fixed it but it would take alot of playing around and the knowledge to fix it. i would just call your carrier tell them you was on 4.2.2 and took the 4.2.2 camera update and now your phone wont boot and get your phone replaced for free
flashallthetime
hasn't this happened to just about anyone who flashes the 4.2.2 OTA instead of the 4.2.2 camera update.
Click to expand...
Click to collapse
Yap, my recommendation is not to flash back to 4.2.2 . it really makes no difference in the battery life to a large degree and avoids hard bricking you're device. I also only recommend flash any sbf firmware with rsdlite a it does check which bootloader version you're running an will safely fail with gpt.bin failed. Really hate giving people bad news. Also if you're the type of person who tinkers please don't purchase a Motorola device unless you can unlock you're bootloader. Samsung is also going the root of impossible unlocked bootloaders with the Knox bootloader
Sent on my Moto X
flashallthetime said:
Yap, my recommendation is not to flash back to 4.2.2 . it really makes no difference in the battery life to a large degree and avoids hard bricking you're device. I also only recommend flash any sbf firmware with rsdlite a it does check which bootloader version you're running an will safely fail with gpt.bin failed. Really hate giving people bad news. Also if you're the type of person who tinkers please don't purchase a Motorola device unless you can unlock you're bootloader. Samsung is also going the root of impossible unlocked bootloaders with the Knox bootloader
Sent on my Moto X
Click to expand...
Click to collapse
i just dont tinker with my personal device lol. but yea i ran into a S3 and a Note 2 with Knox Ugly little bootloader even thou they have root on the devices just makes things a pain. normally i could root and flash a recovery on any Samsung in 5 mins. just aint that easy anymore. have the time you have to run the process 2-3 times just to get it to work right.
dray_jr said:
i just dont tinker with my personal device lol. but yea i ran into a S3 and a Note 2 with Knox Ugly little bootloader even thou they have root on the devices just makes things a pain. normally i could root and flash a recovery on any Samsung in 5 mins. just aint that easy anymore. have the time you have to run the process 2-3 times just to get it to work right.
Click to expand...
Click to collapse
I feel for you, there's just so much miss information, duplicate and triplicate threads that its no wonder more folks haven't hard bricked their devices, all I can suggestvis call Verizon and tell them that you took an ota, actually I believe 4.4.2 is now happening and your phone won't turn on at all
I'm lucky as my boot loader is unlocked which means I can flash 4.4.2 ROMs , saying that 4.4.2 makes no difference to android OS useage , its still second for battery useage
Sent on my Moto X
If I didn't have or want an unlocked boot loader, I wouldn't tinker. Too risky and too limiting.
But that's just me. If someone is a flashaholic, get a nexus. Or if you just want root to tinker....use a device that has an unlocked boot loader....anything less and you're just hacking and exploiting and one mistake away from doom.
Sent from my Moto X cellular telephone...
My computer somewhat detects my phone still. Is there a driver for qhsusb_dload?
Or is there a way to pull the battery?
HeresOtis said:
My computer somewhat detects my phone still. Is there a driver for qhsusb_dload?
Or is there a way to pull the battery?
Click to expand...
Click to collapse
Ghsusb_dload means its hard bricked, everyone who's had that pop up has had a hard bricked device unfortunately. To date no one AFAIK has recovered their moto from a hard brick. All I can say is Google is your friend
Sent on my Moto X
flashallthetime said:
Ghsusb_dload means its hard bricked, everyone who's had that pop up has had a hard bricked device unfortunately. To date no one AFAIK has recovered their moto from a hard brick. All I can say is Google is your friend
Sent on my Moto X
Click to expand...
Click to collapse
He is right the phone is done you are better off getting it replaced.
Is Motorola going to fix it them selfs yes because they have the files, hardware and, software
there have been other phones that have had this issue and they have fixed it but it is hit or miss and never a for sure thing. no one has worked on fixing this issue on the moto X so again i would just get it replaced. i would look into a possible way to fix it but im not going to break my phone just to try and find a fix. let me break it down like this
Is it fixable Maybe.
is it worth trying to fix if you can just get it replaced for free?
the answer is NO it could take days, weeks, months for someone to find away to fix this error and it might never happen.
i would just work on getting it replaced so you can have your phone back.
But if you want to tinker here is a link to a possible driver and other threads with this issue.
driver:
http://forum.xda-developers.com/showthread.php?t=2226445
Random Threads with this Error:
http://forum.xda-developers.com/showthread.php?t=2156231
http://forum.xda-developers.com/showthread.php?t=1522351
http://forum.gsmhosting.com/vbb/f802/qhsusb_dload-driver-need-1321152/
these are not for the Moto X and i don't know if the driver is either but it is somewhere to start. Good Luck
Again i dont recommend tinkering with it. Just get it replaced. But i will say if you end up getting a new Moto X and you dont have to return the bricked one i would love to get my hands on it and see if i cant get it back up and running for other people who have this issue
Related
I recently bought this Nexus off eBay and it worked fine.
Owner said it had problems with the SD card, but it seemed to be working, for they said it wouldnt read, when it does.
Anyway, it had cyanogen mod 6.1.1 on it, and I hate the setup...so i changed roms. That was a success, but when i flashed a sense rom thru clockwork(most updated) it said:
E:Error in /sdcard/N1Sensation_v0.4.zip
(Status 0)
Installation aborted.
Now, when i flash any roms, whether it says it installed correctly, it doesnt change anything. Now it's stuck at the 4 color x with the unlock icon. Any advice is good advice!
In my hboot, it says:
*** UNLOCKED ***
NEXUSONE PVT SHIP S-ON
HBOOT-0.35.0017
MICROP-0b15
TOUCH PANAL-SYNT0103
RADIO-5.00.00.04
Oct 12 2010, 14:33:16
HBOOT
Etc. Etc. Etc.
Thanks for any help!
Edit: I fixed the issue with why it failed, was my fault, didnt partition the card...but i was flashing a stock rom and it said complete and when i rebooted it stayed at the X and then powered off. Since then has never turned on. I don't know what to do. Nothing will turn it back on. I have a universal charger that charges the battery and it said the battery is full. I need help!
Ok lets see here try this plug in the charger then pull the battery place it back in wait a few seconds and repeat until you see the splash screen (the static X). This could get the phone to at least boot.
But just to check did you flash a radio in all that stuff??
Dude Random21 said:
Ok lets see here try this plug in the charger then pull the battery place it back in wait a few seconds and repeat until you see the splash screen (the static X). This could get the phone to at least boot.
But just to check did you flash a radio in all that stuff??
Click to expand...
Click to collapse
That did not work. I work at a cellphone repair store, but im yet to open it up. But i flashed a sensation rom...
http://forum.xda-developers.com/showthread.php?t=1083035
After then i got stuck on the X
Then i used... well i cant find the link, but it's PureGoogleMod.
From what I saw, there was no radio or kernal being flashed. I just know i flashed a rom, it said completed, then went to the X, rebooted, but never turned on. And ive tried other batteries.
matistight said:
That did not work. I work at a cellphone repair store, but im yet to open it up. But i flashed a sensation rom...
http://forum.xda-developers.com/showthread.php?t=1083035
After then i got stuck on the X
Then i used... well i cant find the link, but it's PureGoogleMod.
From what I saw, there was no radio or kernal being flashed. I just know i flashed a rom, it said completed, then went to the X, rebooted, but never turned on. And ive tried other batteries.
Click to expand...
Click to collapse
Try flashing CM7. Also...before you do...you may want to search for a format.zip from a member named temasek. It'll wipe your phone...clean. Real clean. Then flash CM7. try that.
also....those sense roms sometimes take at least 5 minutes to boot. Sometimes it'll stay on the X screen for 5 minutes or it'll stay on the bootanimation screen for 5 minutes. FYI.
SiNJiN76 said:
Try flashing CM7.
those sense roms sometimes take at least 5 minutes to boot. Sometimes it'll stay on the X screen for 5 minutes or it'll stay on the bootanimation screen for 5 minutes. FYI.
Click to expand...
Click to collapse
I can't flash anything. Phone wont react to anything anymore. Hoping one of my family members can fix it. But if I get it on I will try that.
I am pretty sure i waited long enough, but who knows. I didn't partition my card, which may have been the problem. And also it was S-On....which i thought was odd when it had a custom firmware.
Unlock bootloader. Flash recovery. Boot into recovery. Wipe everything. Flash rom.
Why do you guys keep suggesting software stuff when it's probably a hardware problem he can't get the phone to boot up so he can't do any of that.
Although there is one thing I want you to try before your family take a crack at it to take it apart and what not, it's a long shot but it's your last chance if it's software. Hold down trackball and press power keep holding trackball for another 5-10 seconds (better to long then to short) then connect it to the computer via USB you could see a popup notification saying that it's looking for driver software if you do then it's software and we need to reflash everything and might need to unlock the bootloader. Now if you don't see a popup notification I would still go check in the device manager and check for an unidentified device probably in other (it should be extracted so that you can see it).
If this doesn't work then sorry but I think it's a brick
Because in order to find out if its truly a hardware problem you need to try every software fix first.
Op mentioned nothing of trying fastboot as well. Software fix is free hw is not. That is why we suggest software fixes.
Sent from my Nexus S using XDA App
Let me remind you guys, THE PHONE WONT TURN ON AT ALL REGARDLESS OF WHAT I DO. I can post a YouTube video to show everything. It'd be very random for it to be hardware because it just turned off and will not turn back on. If there is any software like an RUU out there, that would help, if not, ill have to buy a bottom piece and warranty it out. But I'd feel bad because that isn't the right thing to do.
I don't expect you guys to fix it and I and very thankful of your help! But the phone won't turn on at all. So telling me to flash roms doesn't work. Imagine it as flashing a rom with the battery out of your phone. I am wondering if there's an adb way or something to get it to turn on and restore to stock?
With all that said, any help is amazing help and I am very grateful that this isn't a post I have to bump! Thank you so much, when I go on the PC, ill thank the helpful posts
Sent from my (finally) permanent root Sensation 4G
Then it is a brick if it won't turn on at all. The entire getting stuck at the x thing confused me to think it was powering on.
You have me confused sir, I'm not quite sure what good it is your looking for a RUU for. If the phone truly won't turn on/go past the X screen and you have it on a charger with no LED notification, then the phone is bricked. When you said you flashed a Sensation rom, I truly hope you just meant a Sense rom. If you can still get to the bootloader screen then you are not bricked and should retry everything from scratch.
Thread Closed
xsnipuhx said:
When you said you flashed a Sensation rom, I truly hope you just meant a Sense rom.
Click to expand...
Click to collapse
Sensation based, but it was a Sense rom
Confirmed it is bricked.
Sold on eBay for $100
Bought for $77
Semi-Winning.
Thread Closed
I have a droid 4 that ended up with bad software. Simple issue is I got no bootloader, no power, no nada. When I connect a regular USB i get a green light in the corner but no activity and no detect. Needless to say, bootloader is corrupt at this point. Sent it back to Moto Repair and they claim physical damage (though I know for a fact there is none) so I'm looking to Flash the bootloader myself. I'm aware it's going to have to be a low level NAND flash. Anyone familiar with this process? Computer does not detect. Does anyone have the latest A.074 Bootloader file I can grab? Need to get this guy running. Any help would be greatly appreciated.
Thanks
Oh, and yes I have a factory programming cable if I can make use of it somehow......
queberican351 said:
I have a droid 4 that ended up with bad software. Simple issue is I got no bootloader, no power, no nada. When I connect a regular USB i get a green light in the corner but no activity and no detect. Needless to say, bootloader is corrupt at this point. Sent it back to Moto Repair and they claim physical damage (though I know for a fact there is none) so I'm looking to Flash the bootloader myself. I'm aware it's going to have to be a low level NAND flash. Anyone familiar with this process? Computer does not detect. Does anyone have the latest A.074 Bootloader file I can grab? Need to get this guy running. Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
How did the bootloader get corrupted? I was under the impression the phone would not allow you to flash another bootloader unless it was signed... You should ask Moto what was physically damaged, if it was a simple flash they should be able to fix it easily for you.
NEED DD
That was my thoughts exactly. But they claim liquid damage. I've since then opened the phone and inspected all the stickers....no sign of liquid damage. I would think a 2 minute bootloader flash wouldn't constitute this much despair (on Motorola's part) but such is life. Now I'm just looking to get the first couple Mb in a device dump so I can write it to an sdcard and attempt to boot from there and repair the bootloader. It has to be a device dump from a D4 running the a.074 bootloader. Any takers?
You could try looking in the fastboot files, they're on the Droid 4 development boards, they have both Gingerbread ones
D4 6.16.215 MBM files
Here are the D4 6.16.215 mbm.bin and other low level boot files from the leaked OTA update.zip.
I don't think they are going to help you given that there is no way that I am aware of to boot from the sdcard on a Motorola device.
There is a USB boot option for loading a factory I/O image(pre firmware basic input/output interface), but I don't know how you would initialize it nor do I have the factory image for the D4.
It is most likely a touchpoint on the board that needs to be shorted while the factory cable is inserted and that would bypass the EMMC and initialize the USB boot.
I am just guessing here...good luck!
if you somehow unlock it too, let us know what you did
SD Card boot didn't work and couldn't get it to detect on my windows or linux pc's. Therefore OMAPboot was out of the question. So I parted it out. I've acquired another D4 and I'm curious as to what if any advancements have been made on getting them to work on US GSM carriers? If we're still stuck I'm more than willing to jump into Dev on this and open to suggestions. My new D4 is running bone stock GB. I'm going to keep looking into the SD or USB possible fix's for hardbricks.
Thanx for the replies and thanx to [mbm], Jonpry, PhareignQ (think I mightta spelled that wrong), and HashCode for their knowledge, help, and suggestions along the way.
Hey man! You're the second one with same issue. I'm looking to buy new motherboard for droid 4 with same crapped bootloader + broken cdrom partition
For those who is interesting in, motorola factory cable doesn't work with droid 4 for some strange reason.
I can attest to the fact that the factory cable does, indeed, work with the D4 just like the Razr and other Motorola models.
I am not sure why yours doesn't or what condition your phone is in at this point, but the factory cable will power the device directly, bypassing the battery/charging circuit and allow you to flash it as long as the bootloader and mbmloader are not corrupt.
In that case, when the mbmloader fails, then nothing happens on the device at all unless a factory cable is connected, then it will flash the LED white just once as the cable is inserted and then loop continuously trying to load an interface and fails. The screen does nothing and the device is dead except pressing all 3 hardware buttons will arrest then restart the cycle of failed interface initialization once released.
I have a Razr in this state that I unfortunately attempted to flash some unknown files we received that we foolishly believed may have been an OEM bootloader unlock.
If you flash a corrupt image to the mbmloader the device is toast, AFAIK, although I do believe they have ways to recover them and in the past those methods often involved shorting a set of pads on the board with a paperclip while inserting the factory cable, initializing a timed event where the EMMC was bypassed and and factory I/O file could be loaded via a USB boot option.
I don't know if any of these methods could actually save any of our phones in this state, but I would like to believe its possible!
I just wanted to clarify about the factory cable.
Yup, what @Cellzealot said. I've removed the battery from the D4 and the factory cable works as intended. To be frank I had a moment of ignorance. I had just gotten my D4 (used) and was attempting to try and find a solution for the US GSM band unlock. In reading through the post about the Bionic I found that there was alot of talk about needing to be on bootloader 0A.72 or something to the fact of having success with that. The kid I got it from had already installed the ICS leak. So I paid no attention to the fact that the bootloader on MY phone was 0A.74....so I opened RSD and attempted to send mbm and mbmloader from 0A.72. It failed and that was the last thing ever "sent" to that phone. As soon as I disconnected it the phone powered down and never did anything after that.......
So I pursued the Boot from SD theory to no success, though I believe it is plausible, however probably still required a short to enable it. And Linux and Windows wouldn't even detect the OMAP4430 (as I've heard some people had luck with). So OMAPboot (boot from usb) was out too.
Finally got another D4, and being the phone soldier I try to be, Went right back to town attempting to get this thing to run on AT&T. So far no luck. I've been trying radio's and rom's from different devices and brandings that are running 2.3.6 (I left this one on the stock Gingerbread)
Willing to undertake any suggestions as long as "bootloader" is nowhere in the equation,
queberican351 said:
Yup, what @Cellzealot said. I've removed the battery from the D4 and the factory cable works as intended. To be frank I had a moment of ignorance. I had just gotten my D4 (used) and was attempting to try and find a solution for the US GSM band unlock. In reading through the post about the Bionic I found that there was alot of talk about needing to be on bootloader 0A.72 or something to the fact of having success with that. The kid I got it from had already installed the ICS leak. So I paid no attention to the fact that the bootloader on MY phone was 0A.74....so I opened RSD and attempted to send mbm and mbmloader from 0A.72. It failed and that was the last thing ever "sent" to that phone. As soon as I disconnected it the phone powered down and never did anything after that.......
So I pursued the Boot from SD theory to no success, though I believe it is plausible, however probably still required a short to enable it. And Linux and Windows wouldn't even detect the OMAP4430 (as I've heard some people had luck with). So OMAPboot (boot from usb) was out too.
Finally got another D4, and being the phone soldier I try to be, Went right back to town attempting to get this thing to run on AT&T. So far no luck. I've been trying radio's and rom's from different devices and brandings that are running 2.3.6 (I left this one on the stock Gingerbread)
Willing to undertake any suggestions as long as "bootloader" is nowhere in the equation,
Click to expand...
Click to collapse
Any solution on black screen and broken bootloader?
Here I have black screen with AC adapter connected. If I connect the phone to PC, I have green led indicator, but still black screen. Buttons have no reactions.
Anything new? Two users on a German bulletin board do have the same issue. I will get one Droid 4 of them in the next few days to have a look at it. But this thread sounds like there is no solution?
http://db.tt/u31VG45D
http://forum.xda-developers.com/showthread.php?t=2055839
The first link is to the most recent level 4 bootloader repair kit that we have for the Maserati/Droid 4 which is 0a.6c from pre ICS builds.
It is possible you may be able to use the pbrdl.bin and brdl.bin from those files with the mbmloader.bin and mbm.bin from a more current build to restore your device.
Again, these files are a year old now and may not work but you have little to lose in trying.
Use the method in the second link in Linux to try to restore your bootloader with the omapflash-lnx binary from that thread.
This is very likely to fail if the device has a recent firmware build on it but we don't have any of these repair kits for the newer bootloaders.
Good luck!
Thanks.
I got one of these phones. But it isn't even recognized via USB So I can't use these tools...
Is there any way to flash it via JTAG/ISP/...? Maybe this is the last chance - or this phone is dead ^^
I have a VZW Retail Moto X that was rooted with pwnmymoto a while back. At one point there were some issues with the device (it became completely unstable and unusable, had to switch phones for a while). I was not able to factory reset the device because whenever I entered bootloader selecting any option would just reboot the device normally. I have not been able to fastboot the device because RSDLite will not recognize that it is connected. I was able to reset the device over ADB in Linux and it ran without too many issues for a while but yesterday the OTA update failed during installation and is now fraught with issues again. Once again I was not able to flash it back to stock with RSD as the device isn't getting recognized.
Does anyone know how I can get this thing completely back to stock and then get it on 4.4? I am not concerned about saving any data that is on the device.
Have you looked at the other threads? I'm pretty sure this was already covered...
I'm working so I don't have a chance to scan, but check these two threads...
http://forum.xda-developers.com/showthread.php?t=2534060
http://forum.xda-developers.com/showthread.php?t=2525495 (start at the back and work your way front because of some of the fluff from before the OTA hit)
KidJoe said:
Have you looked at the other threads? I'm pretty sure this was already covered...
I'm working so I don't have a chance to scan, but check these two threads...
http://forum.xda-developers.com/showthread.php?t=2534060
http://forum.xda-developers.com/showthread.php?t=2525495 (start at the back and work your way front because of some of the fluff from before the OTA hit)
Click to expand...
Click to collapse
I've done a ton of Googling and haven't found anything that matches my issue but I haven't dug through those threads yet, thank you. I apologize if this has already been covered.
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
Hi guys, i hope someone can help. I have the XT1092 variant of the Moto X with Kitkat out of the box, i upgraded to lollipop 5.0 then to 5.1 all via OTA. I then ulocked the bootloader , rooted the device and installed unofficial version of Euphoria 5.1.1 unfortunately i never backed up the stock rom. I then ran into some issues with call quality, no matter who i spoke to they all complained that my voice was fading in and out. I also noticed that whilst on a call whenever i spoke over the top of someone they were also fading in and out like the volume increased via the earpiece every time i spoke. I believed this to be a hardware issue but wanted to confirm this by going back to stock. So i managed to find the EU version of kitkat 4.4.4 which matched my device, using mfastboot i proceeded to flash each file individually which it happened to be that the downgrade went well, but this still did not fix my issue with the fading in and out during calls. I then had the OTA update come through on the device so i decided to go back to stock lollipop 5.0 in hope that this would fix the issue, the download went well the phone then rebooted and started the installation. About half way through i noticed that the screen was black so i naturally pressed the power button but no response, i have tried everything from here that i can think off. I have tried hard reseting using the ppower button and volume button to access bootloader i have also attempted adb & fastboot commands but my device is not registering on the pc the only prompt that came up after plugging it in to my pc was an installation of some foreign driver known as 'Forge HS-USB QDLoader 9008 (COM4)'??? The only response i now get from my MotoX is a green led that comes on for a few seconds and disappears shortly after, and that's only when i hold the power button down for 10 secs to perform a hard reset and only when it is connected to a power outlet or my pc otherwise doing the hard reset unplugged i dont even get the green led at all. The device had almost 100% battery when i performed the upgrade. Have i bricked my device, is there any hope in getting it back up again? Is there a toolkit or something i can use to revive it. Your help would be really appreciated it, ive only had the device for approx 2 weeks and it was purchased on ebay from a private seller brand new sealed in the box, so no warranty
this is the version of kitkat i downgraded with, i took a screenshot before i upgraded again via OTA to lollipop.
occtec said:
Hi guys, i hope someone can help. I have the XT1092 variant of the Moto X with Kitkat out of the box, i upgraded to lollipop 5.0 then to 5.1 all via OTA. I then ulocked the bootloader , rooted the device and installed unofficial...(
Click to expand...
Click to collapse
Unfortunately, you have a brick. That USB QDloader registering on your PC is a dead giveaway. We have no way of helping you recover from this.
Sent from my XT1095 using Tapatalk
dustin_b said:
Unfortunately, you have a brick. That USB QDloader registering on your PC is a dead giveaway. We have no way of helping you recover from this.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
bummer, cheers
Why did you downgrade to KitKat when you have lollipop images ???
Sent from my XT1092 using XDA Free mobile app
Unfortunately, its hard brick and up until now there is no solution yet for this problem, untill someone leak the blank flash file for moto x 2014.
Sent from my XT1095 using Tapatalk
I'm surprised that the phone didn't brick the first flash back to kit kat. Ya the mistake was not downgrading the bootloader first, which can be risky
---------- Post added at 10:20 AM ---------- Previous post was at 10:16 AM ----------
If I were you I would sell for parts on eBay, or even buy a cracked moto x and take your screen. I did that when my WiFi and Bluetooth went, just bought a cracked screen moto x for 50 bucks. Moto x screens are over 200$ and there is a lot of broken phones
Or sell my your screen for my xt1092 phone make my happy !