As I am visiting my parents, my mother hands me her phone and says turn it on. I did all the normal hold down the power and volume down buttons for 15 secs all the way to 3 minutes, hoping to be greeted with the bootloader screen. I never was.
I have had the phone plugged into various wall chargers, and the phone vibrates every 1 minute i would say. The vibrating was taunting me so i unplugged it, and it still vibrated every minute or so. So i decided to try and charge it form a laptop, vibrating continues. I figured well lets see what happens when i try to boot into the bootloader while plugged into pc. I was surprised to hear that a devices was connected. On PC i entered the fastboot devices command and it is listed as connected (T070600102C). Only device connected so I know it is the moto x. I tried the reboot, and reboot bootloader command hoping to see the screen turn on, it never did. At this point I am stuck.
She said the device was not drained when it happened and was about 60% battery.
It was recently updated to android 5.1.1 a few days ago. The bootloader was never unlocked, nor were any system files tampered with or rooting.
I left the phone stock for her, and got her the dev edition to be able to fix any problems that may arise, but I do not know where to go from here.
I was going to try and flash the factory image but motorola does not have the 5.1.1 system images available for download
EDIT- the vibrating occurs every 40 seconds when not in the bootloader.
I'm wondering if maybe the battery has become defective and iff replacing the battery would solve this issue?
Please any information you can provide will be greatly appreciated.
I should also mention i purchased this device from motorola, on july 22 2014, thus being out of warrenty
I also need to ask this because i can;t remember. This moto X was on 5.1.1 if I attempt to flash the latest image available form motorola (MOTO X, GSM Dev Edition:
L-5.1-LPA23.12-15 (Retail) LMR1) which is older, will there be any problems? I requested the download form moto so it will be awhile before I get it. Just concerned if there are any issues from fastboot recovering from 5.1.1 to 5.1.
I should also note that the phone seems to respond well to fastboot commands. I was able to get OEM unlock data code, and may try to install 5.1
wow nothing?
I would certainly try mfastbooting the latest image. But since it is stock, go ahead and try to see if Motorola will help you. Just because it's out if warranty doesn't mean that they won't help you.
Sent from my Moto X using XDA Free mobile app
moto x 2013 doesnt have 5.1.1. Go ahead and flash 5.1 and you will get it back to life.
http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1
Related
So I obtained a phone that someone gave to me cause its not working. It will only turn on when I plug it up and it shows the motorola logo then it flashes bootloader mode and it says battery to low to program.
How can I fix this? This phone had never been rooted or flashed or anything. And I dont have a another battery for this phone to try with
i done a usb battery cable thing and got the battery issue fixed now when trying to reflash with rsd lite it stops at 99% sayiing switching to bp passthru mode
I'm sure if you took it into a store, they would replace it for you. If you are still within your 30 days, you will get a new device, otherwise it will be "certified like new".
jakson0100 said:
I'm sure if you took it into a store, they would replace it for you. If you are still within your 30 days, you will get a new device, otherwise it will be "certified like new".
Click to expand...
Click to collapse
I dont think u read my entire post....
For one It was giving to me from someone. 2 its looks older than a year for warrenty and 3 I DONT HAVE VERIZON
Hi,
I got a new Motox two days ago, I started it normally, updated the OS as asked and used it without GSM (I am waiting for my nano sim) until last night, when it froze and never came back on.
I tried to press the power button for a looong time, I tried power+volume down, I charged it all night (the led does not come on).
When I connect it to my Linux box it is detected as the Qualcomm QDL device.
I am probably sending it back, but I wonder if I no one knows a magic solution to this problem?
I saw a thread that talks of using the Qualcomm QDL interface to re-flash the bootloader, but that's Windows only and I do not have access to a Windows box.
Any suggestions?
Thanks,
There must be more to this. What exactly have you done with the phone? Need the details.
Never heard of of an X bricking by itself.
KJ said:
There must be more to this. What exactly have you done with the phone? Need the details.
Never heard of of an X bricking by itself.
Click to expand...
Click to collapse
Or it is just a defective phone. It happens. He should just return the device.
KJ said:
There must be more to this. What exactly have you done with the phone? Need the details.
Never heard of of an X bricking by itself.
Click to expand...
Click to collapse
Nope, have not done anything, start up, google account, OS update, encrypt phone and use for one day, that's it. Crazy, right.
Defective device it is.
My brother just bought a new in box Moto X off eBay (ruling out any warranty) about a week ago. Today it asked to update the OS, which he accepted. During the update (green android robot with blue swirly thing inside) the phone simply blinked off and ceased to respond. And I mean NO response. I don't get LED's, boot, fast boot, recovery, charge, ANYTHING. Plugging it into a computer also gives no response.
My bro didn't take note of the OS that it was updating to, but it was just an OTA. He had no suspicious apps, hadn't played with ROM's, just barely had his phone working before this happened.
I spent a long time googling for this same problem, but no results. Everyone at least gets SOME response out of their phone. I can't imagine this is a hardware problem, and I'm certain he had plenty of charge when he initiated the update (only half a day of use on the charge, should have been at %50-60 on the low side).
Anybody have an idea on how to proceed? Any info would be greatly appreciated, even a link to a helpful thread that I missed.
Phone is a 1st gen (2013) Moto X on AT&T.
Brett316 said:
My brother just bought a new in box Moto X off eBay (ruling out any warranty) about a week ago. Today it asked to update the OS, which he accepted. During the update (green android robot with blue swirly thing inside) the phone simply blinked off and ceased to respond. And I mean NO response. I don't get LED's, boot, fast boot, recovery, charge, ANYTHING. Plugging it into a computer also gives no response.
My bro didn't take note of the OS that it was updating to, but it was just an OTA. He had no suspicious apps, hadn't played with ROM's, just barely had his phone working before this happened.
I spent a long time googling for this same problem, but no results. Everyone at least gets SOME response out of their phone. I can't imagine this is a hardware problem, and I'm certain he had plenty of charge when he initiated the update (only half a day of use on the charge, should have been at %50-60 on the low side).
Anybody have an idea on how to proceed? Any info would be greatly appreciated, even a link to a helpful thread that I missed.
Phone is a 1st gen (2013) Moto X on AT&T.
Click to expand...
Click to collapse
I'm in the same boat... I recently bought a Moto X (2013) on eBay and having had the Atrix HD previously, I thought rooting should be simple.. yeah, no, it wasn't... i'm now hard bricked. I followed a guide about updating the driver and using the program that tricks the driver signing, and it all went as stated, except the phone still won't turn on. Adb can't see it, neither can mfastboot.. RSD Lite does see it tho it fails flashing.. I don't know what to do.. I don't have much $ and I had just saved up for awhile so any help would be appreciated
Brett and Elisha, are you running Windows? If so, when you connect your phone, does Windows chime as if it recognizes something is connected via USB?
platinumthomas said:
Brett and Elisha, are you running Windows? If so, when you connect your phone, does Windows chime as if it recognizes something is connected via USB?
Click to expand...
Click to collapse
ya exactly
i have the same problem but in my case the phone was good but while coping video the phone just turned off.
that's it after that im stuck at boot loader unlocked ...
pls somebody suggest me what to do to get back my moto x working
amg0005 said:
ya exactly
i have the same problem but in my case the phone was good but while coping video the phone just turned off.
that's it after that im stuck at boot loader unlocked ...
pls somebody suggest me what to do to get back my moto x working
Click to expand...
Click to collapse
I started here: http://forum.xda-developers.com/moto-x/general/moto-x-root-pogress-60-t3071602
After step 3, manually installing the unsigned drivers, I had to follow this: http://forum.xda-developers.com/moto-x/general/how-to-unbricked-hard-bricked-phone-t3146036
I skipped to "Now software part. Go to unzipped C:\Python27 folder, launch bat-file, and wait until finish:
RUN_blank_bootloader_flash.bat"
It took a bit of time, but the phone rebooted and I am rooted.
platinumthomas said:
Brett and Elisha, are you running Windows? If so, when you connect your phone, does Windows chime as if it recognizes something is connected via USB?
Click to expand...
Click to collapse
yes!! it does recognize when i connect it to the computer. can i do anything to get it on ???
sachinrao13 said:
yes!! it does recognize when i connect it to the computer. can i do anything to get it on ???
Click to expand...
Click to collapse
There's a thread on this forum titled 'Resurrecting a dead Moto X'. It describes your scenario in detail and explains a way to fix it.
Hello everyone,
I'm experiencing a pretty tough issue mith my beloved (and, so far, flawless) Nexus 6. It had root and a stock rom on it, 6.0.1 (MMB29V). I had unlocked the bootloader and rooted the phone right after buying it more than a year ago and I've been flashing new factory images a couple times (specifically when 6.0.0 and 6.0.1 were released). I usually do everything via Wugfresh's NRT, not because I can't use adb and fastboot, just because it works fine and I'm lazy.
Yesterday, while I was working, I used "Tiny Scanner Pro" to scan a document (legit copy bought on the store, as any other premium app in my phone) and it got stuck for a while, then a popup about Google Play Services came up. I dismissed it and another appeared, and it kept going like that. I was at a client's and I was in a hurry, so I took the pic with my tablet and forced the phone off. Later I turned it on, it seemed to boot regularly, but when the SIM unlock screen appeared and I entered the (right!) PIN, it said that no SIM was found, then the home screen appeared but after a while the screen went black and it started rebooting. Recovery (TWRP) and fastboot were working, so I decided to take it home and re-flash the stock rom: it had been a while since the last time anyway, a new version was out and the OTA update notification was getting annoying. I connected to my PC in recovery mode and transfered my pics and data via adb while I downloaded the latest stock rom (6.0.1 MOB30D). Then I user NRT to flash it (selecting "Soft-bricked/Bootloop" as current status). It appeared to work fine as it went through the usual copying and unpacking. Then, when the phone was supposed to reboot, it just blacked out. I waited a long time, in fact I went out and came back a few hours later, and it was still that way. Now it doesn't power up, no matter how long or hard I press any combination of the three buttons, adb and fastboot do not detect it in any way, of course, and it doesn't seem to charge either (i.e. I left it plugged to its original charger overnight and it still feels dead cold). By the way, the phone warranty shouldn't have expired, but I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
I've taken a look at similar threads but none of them describes the very same situation. Is there something, anything I can try to do before giving up? I hope somebody can help me. I thank you all very much in advance.
lupus
lupusyon said:
.... I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
Click to expand...
Click to collapse
Bricked!. When the phone is still under warranty send it for repair. Do not use arguments.
Just: phone will not switch on and does not charge.
Because this is a Nexus device, the custom recovery shouldn't affect your warranty. It is however, a moot point. The device is totally dead, and a call to Motorola is in order.
lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...
dahawthorne said:
lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...
Click to expand...
Click to collapse
I bought it on Amazon Italy Marketplace, I'm not sure if they're supposed to handle the thing or if I should contact Motorola. I'll just check with them first. Thank you everybody for the kind advice, I'll let you know how this turns out. :good:
I confirm what dahawthorne wrote above: it took them about a month but Motorola repaired my Nexus under warranty, no questions asked. It seems they replaced the Mainboard PCB.
Thanks everybody!
Hi i did something stupid with my moto x, i downgraded my moto to kitkat and i tried to update to lollipop so i installed the ota update for lollipop later it just turn off, it doesnt charge or turn on, i have a problem who can help me pls. Green light not works, i dont know what to do PLS HELP
Raulino4567 said:
Hi i did something stupid with my moto x, i downgraded my moto to kitkat and i tried to update to lollipop so i installed the ota update for lollipop later it just turn off, it doesnt charge or turn on, i have a problem who can help me pls. Green light not works, i dont know what to do PLS HELP
Click to expand...
Click to collapse
Try using a different charging cord, also just try plugging in and out a few times. Mine did the same thing (not due to update) but it turned out it was the charging cord was bad.
dtrud0h said:
Try using a different charging cord, also just try plugging in and out a few times. Mine did the same thing (not due to update) but it turned out it was the charging cord was bad.
Click to expand...
Click to collapse
Nothing man, but thanks for try
Exact same thing happened to me
After getting "update now or in <24hours" for the last 6 month I decided to properly re flash my phone to get the latest version so the update would go away.
I used this guide to install the recommended version 5.1.0-LPA23.12-15.0
http://forum.xda-developers.com/moto-x/general/xt1053-222-27-5-stagefright-ota-update-t3210786
only thing I did differently was use my already installed mfastboot which worked without error
Everything worked fine, battery at 90%. I downloaded the OTA update and rebooted to install and put the phone down and come back after a moment. Phone is black, try to power on with Power and Power + Vol Down. Nothing works. I also tried charging and charging and pressing the buttons.
As far as I know it's just ****ed and there is nothing to do about it but any suggestions I would be willing to try. For anyone else I would not recommend this just in case try the TWRP System Image or the newer builds.
Edit:
I made an error by updating to the more recent one before re-flashing to the recommended one, this is known to hard-brick your device. http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
Moto X won't charge or turn on
Raulino4567 said:
Nothing man, but thanks for try
Click to expand...
Click to collapse
My MOTO X xt1056 doesn't charge while it is off and the charger port is broken due to the plug becoming lose from daily use for 3+ years. The best bet to do is to return it to the store and tell them that it just stopped charging and they should replace it with the same device or a slightly used newer model.