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
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
Hello,
I'd like to preface this to say I've searched through this and other sites but have not found quite the same problem. I also apologise for the small wall of text. I just want to post everything that seems relevant.
Several weeks ago I unlocked my phone and flashed the latest stable Cyanogenmod. This has all gone fine. I decided today I wanted to try something else and settled on TeamAsylum's 4.4 rom.
Downloaded a whole bunch of stuff and was a little confused as the flashing process seemed a bit different and I didn't fully understand it. I booted into Clockwork Recovery and inadvertently flashed the raw kernel from here, which I downloaded in my searches earlier thinking I needed it. I rebooted the recovery but now I get nothing from the phone. No lights, no display, no vibrations.
I have tried a reset (Power+Volume UP). I have tried using SUS and Flashtool but both get to the same point and stop (hole Volume DOWN and plug USB in). Nothing happens after this. The only thing telling me the phone is alive is when I plug it in, Windows makes the detected sound. If it's plugged in when I hold power+Volume UP it repeats the detection sound as if the phone is trying to boot over and over.
I realise I have ****ed up by flashing the kernal of a different phone. I'm hoping someone can help me or guide me in the right direction.
Thank you.
Nightstaar said:
Hello,
I'd like to preface this to say I've searched through this and other sites but have not found quite the same problem. I also apologise for the small wall of text. I just want to post everything that seems relevant.
Several weeks ago I unlocked my phone and flashed the latest stable Cyanogenmod. This has all gone fine. I decided today I wanted to try something else and settled on TeamAsylum's 4.4 rom.
Downloaded a whole bunch of stuff and was a little confused as the flashing process seemed a bit different and I didn't fully understand it. I booted into Clockwork Recovery and inadvertently flashed the raw kernel from here, which I downloaded in my searches earlier thinking I needed it. I rebooted the recovery but now I get nothing from the phone. No lights, no display, no vibrations.
I have tried a reset (Power+Volume UP). I have tried using SUS and Flashtool but both get to the same point and stop (hole Volume DOWN and plug USB in). Nothing happens after this. The only thing telling me the phone is alive is when I plug it in, Windows makes the detected sound. If it's plugged in when I hold power+Volume UP it repeats the detection sound as if the phone is trying to boot over and over.
I realise I have ****ed up by flashing the kernal of a different phone. I'm hoping someone can help me or guide me in the right direction.
Thank you.
Click to expand...
Click to collapse
Try this:
Open flashtool
Hold volume up and insert usb cable( you will enter fastboot )
then select fastboot and flash a good kernel for CM.
let me know it this works
RaZieLRaH said:
Try this:
Open flashtool
Hold volume up and insert usb cable( you will enter fastboot )
then select fastboot and flash a good kernel for CM.
let me know it this works
Click to expand...
Click to collapse
Hi,
I tried what you said. When holding Volume UP and inserting cable, literally nothing happens. I don't even get a sound from Windows detecting it.
Whilst trying this several times though I did notice if I press Power the phone seems to stay on for 30-60 seconds. If I press Power and plug it in, Windows will make a sound. It will then make another sound after 30-60 seconds as if the device has been removed or turned off.
no clue then sorry can't help
Nightstaar said:
Hi,
I tried what you said. When holding Volume UP and inserting cable, literally nothing happens. I don't even get a sound from Windows detecting it.
Whilst trying this several times though I did notice if I press Power the phone seems to stay on for 30-60 seconds. If I press Power and plug it in, Windows will make a sound. It will then make another sound after 30-60 seconds as if the device has been removed or turned off.
Click to expand...
Click to collapse
Just for giggles, check your device manager to see if you have an unknown device... (you may need to install the fastboot drivers...) I've bootlooped my phone a couple of times while putzing with my phone... And can normally get back into flash mode and fast boot mode...
Sent from my Xperia ZL using Tapatalk
scifan said:
Just for giggles, check your device manager to see if you have an unknown device... (you may need to install the fastboot drivers...) I've bootlooped my phone a couple of times while putzing with my phone... And can normally get back into flash mode and fast boot mode...
Sent from my Xperia ZL using Tapatalk
Click to expand...
Click to collapse
I did check this. There are no unknown devices. I did install the Xperia Z/fastbot/flashboot drivers from the flashtool folder. When it does make the detection sound Device Manager does 'reset' as if something has connected as well, although I can't find the device.
Most other similar issues have an LED or some type of display and generally are responsive to flashmode.
Note1 boot partition is the XZ's SBL3 (bootloader) partition. So you have effectively flashed a Note1 boot.img to your bootloader. Phone will never boot again once bootloader is hosed. Sorry about your loss
Sent from my C6603 using xda app-developers app
Shoey is right, your Z is toast now, sorry; the only solution here is to replace the MoBo, and that costs a pretty penny.
But why did you download stuff from the n7000 forum? Didn't everything said there sound unfamiliar and therefore suspicious enough for you
to double-check which forum you were in exactly?
I thought as much. I dun goof'd
Thanks for your help.
@chasmodo: Well I started in the N7000 thread and downloaded all the stuff and copied it to my SD card. I then realised I was in the wrong forum and switched to the relevant thread. All the stuff for the N7000 and the Z were both on my SD card, so it was just a stupid mistake really. Everything on both forums sounded a little unfamiliar. As I mentioned I was a bit cofused on the TWRP section. I should done more research before proceeding.
Do you think there is any use for the phone now? Do you know of anywhere/anyone I can donate it to for spare parts or something?
Nightstaar said:
Do you think there is any use for the phone now? Do you know of anywhere/anyone I can donate it to for spare parts or something?
Click to expand...
Click to collapse
As I said, you can get it fixed by replacing the MoBo, but I don't know how much that costs in your country. Google a little, contact someone, get the info and then decide what to do.
chasmodo said:
As I said, you can get it fixed by replacing the MoBo, but I don't know how much that costs in your country. Google a little, contact someone, get the info and then decide what to do.
Click to expand...
Click to collapse
I did have a look around and had trouble finding a main board in particular. I contacted Sony as well and they said it was quite expensive to replace.
I contacted my carrier and it appears getting a new phone is a lot cheaper than anything I've looked into so far.
Thanks for your help.
The next time you decide to flash your phone , make sure your in the correct forum. Lesson learned
Sent from my C6603 using XDA Premium 4 mobile app
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,
I installed CM12 Stock ROM into the slot by mistake (yes kill me now PLEASE).
This supposedly changed the bootloader so I need to update jellybean bootloader to install something 2.x.
I had prepared the phone in Fastboot and before I downloaded bootloader the phone turned off, and now it won't do absolutely anything.
No combination of keys won't turn it on.Display does not come on after connecting to the USB / wall socket - not even the green light.
I tried a my friend's battery (fully charged) and also nothing.
Can I do anything at this moment except just throw it away ? (I am in CZ so visit Verizon is out of question).
I read there should be some special USB cable from Morotola and it allows flash without batteries (stupid?).
Thanks for the tips.
n31k said:
Hello,
I installed CM12 Stock ROM into the slot by mistake (yes kill me now PLEASE).
This supposedly changed the bootloader so I need to update jellybean bootloader to install something 2.x.
I had prepared the phone in Fastboot and before I downloaded bootloader the phone turned off, and now it won't do absolutely anything.
No combination of keys won't turn it on.Display does not come on after connecting to the USB / wall socket - not even the green light.
I tried a my friend's battery (fully charged) and also nothing.
Can I do anything at this moment except just throw it away ? (I am in CZ so visit Verizon is out of question).
I read there should be some special USB cable from Morotola and it allows flash without batteries (stupid?).
Thanks for the tips.
Click to expand...
Click to collapse
Cm12 does not change the bootloader, stock slot or not.
Cm12 installs fine on stock slot, if done correctly.
Sometimes when the Droid 4 is in AP fastboot mode it will power off after a few minutes of no activity.
Don't know what is causing the no boot option, if battery is charge.
the most common cause that hard bricks the Droid 4, is Flashing official firmware for a Razr xt912
Did you install Motorola Drivers?
Does Droid 4 show up in Device Manager?
See
Moto Drivers, RSD Lite, and other Unbricking Tools
http://forum.xda-developers.com/general/rooting-roms/motorola-usb-drivers-rsd-lite-firmware-t3042687
Sent from my XT912 using Tapatalk
Thats the thing, the phone is not visible anywhere (Windows device manager, Linux lsusb).
I think that in this case none of the tools would help me (or it will ?)
n31k said:
Thats the thing, the phone is not visible anywhere (Windows device manager, Linux lsusb).
I think that in this case none of the tools would help me (or it will ?)
Click to expand...
Click to collapse
If Droid 4 will not connect to pc, you cannot flash firmware.
You can try a fastboot cable, but don't think that will help.
Motorola Fastboot/Factory Programming Cables Links
Sent from my XT912 using Tapatalk
Well I guess that changing the board is a way to go
If you press "Down", "Up" and "On" button - do you have menu?
Fervi
Hi please i need a help. I bricked my droid by Flashing official firmware for a Razr xt912 now the phone don't boot help please.
patsonator said:
Hi please i need a help. I bricked my droid by Flashing official firmware for a Razr xt912 now the phone don't boot help please.
Click to expand...
Click to collapse
Which bootloader version was on the phone?
Edit: Miss read thread title,
If you flashed droid razr firmware on your droid 4, there is no fixing
Sent from my Atom using XDA Labs
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 !