So on my old Moto X 2014 2nd gen (I have a new phone now), the battery stopped charging, so the phone will no longer charge. All I am able to do is get it into fastboot mode if it is plugged in. I have tried several suggestions from here and other places, and have given up on fixing it.
However, is there any way that I would be able to get the data off of it? Either through fastboot somehow or some other method, its out of warranty so I don't exactly mind, as it doesn't have any resell value.
Hi! Can you boot into recovery?
If not, have you considered changing the battery, getting your stuff back and reselling it?
Related
Hello,
My wife dropped her moto X last night.
It is bone stock and on kitkat.
The screen is now black and has no use. nothing has brought it up including fast reboot.
When I plug it into the computer I get unknown device called fast reboot. I do have the motorola driver software installed.
I took the phone to a repair shop, I also have a moto X and they took both phones apart and plugged her motherboard into my screen. From there he said it was an android logo with a question mark and the phone is screwed.
Having gone through issues with my tf101 in the past and learning info on this site, I have brought stuff from the dead before and dont believe it is totaled.
Seeking threads for similar issues on how to get into the hard drive and move photos and etc to my computer even while screen is dead and cannot turn on USB debugging if any are out there.
The photos on the phone are every single photo my wife has taken of our 3 month old baby including her first thanksgiving. She is devastated and I have to find a solution. Motorola will likely replace it for free but I need the data first.
I am in Tempe.
Hi,
I will have your thread moved to your device section. But I'll say that unless your computer can see it as a storage device, there will be nothing you can do unfortunately.
Hopefully someone has some ideas though. And always backup pics to computer or online storage down the road... Using phones as permanent storage is far too risky...
Good luck!
The simple solution would have been what you already tried, switching the motherboard over. Assuming that is for sure not an option then only thing I can think of is trying to get data off of the Nand flash chip, depending on how far you want to go with it.
- See the Moto X iFixit teardown article, Step 15 : https://www.ifixit.com/Teardown/Motorola+Moto+X+Teardown/16867
- Watch YouTube videos like this one: http://m.youtube.com/watch?v=37wHcIQKUlk
- Read a similar question on iFixit: https://www.ifixit.com/Answers/View/112224/Can+memory+on+board+(16GB)+be+removed+and+accessed
So far information suggests it's doable. But maybe not diy. In that case, look for companies that do this kind of thing. Google search something like "nand flash data recovery" get a few results like: http://www.eprovided.com/nand-flash-data-recovery.php
Good luck.
Note: I've never tried this myself. I have my data in double backups. terabytes of external storage are cheap nowadays.
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.
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
They changed the name and what it does.
You might want to try it if you have a hosed X4.
I had a X4 on -8 rooted with Magisk and TBP frozen Moto update and it didn't care, it just factory flashed it to -9.
Some 50 things needed updating so connect it to wifi and update all.
Credit for this goes to @redwoodie - thanks!
Pay special attention to the instructions: from power-off, hold vol-dn while connecting USB to PC. (do NOT press power-on) You get a different line on the fastboot screen.
Can we relock the bootloader after using the rescue feature?
why would you want to relock your phone and render it worthless? just drop it in the wastebasket!
That reminds me - recently I happened to pick up a used G5 from ebay. It was locked but showed a bad fastboot footprint. It was very obvious that it had been unlocked, modified, and then relocked. Worthless. I of course returned it and got my money back. The seller lost big time - shipping both ways + phone + bad review. You can't cover your tracks. Locking means nothing.
Bricked Pixel 5a/QUSB code of death
Has anyone found a solution to the QUSB code of death? I entered the club last week. I was using my Pixel 5a as usual, scrolling through social media. Then suddenly, the screen freezes, the phone shuts off, reboots, freezes on the Google logo, then shuts off. Has not turned on since.
I have done all of the rudimentary “diagnostic solutions” but to no avail. When I plug the phone into my computer, the QUSB device code shows up in device manager.
I filed a request to obtain a replacement/repair with Google last week. They gave me the option to replace the device after determining it was bricked. However, Google seems to think it’s liquid damaged and ineligible for repair/replacement under the warranty. The phone has never had any sort of extensive liquid contact.
I am currently waiting to receive the same exact phone back. So far, I have not been able to find a legitimate solution other than sketchy “freezer” fixes and uncontrolled banging around the device with the hopes of it turning on again.
Has anyone figured out a legitimate solution to the same problem among multiple generations of Pixel devices?
can you get into bootloader? power on + vol down.
or a response when you have it plugged in with adb devices or fastboot devices?
or try a force off? power + vol down + vol up for about 30 seconds then try to power on again?
I have already tried those solutions. So far, nothing has worked.
wow. i don't know what's going on. mine did the same thing on sunday. got it to clean flash the official 13 with the chrome flash tool. was getting set back up and it happened again. and i just replied to another thread on here about someone it happened to. they better not tell me mine is suspected to be liquid damaged. but if they're not gonna replace it, i suppose you could try the freezer trick. and the best thing to do would probably buy a cheap 3a and trade it in for a 6a. maybe i shouldn't go with pixels anymore though. only had the 3a and now this one. they should get back to me tomorrow. i gave up trying to fix it the 2nd time it happened. wouldn't boot into userspace fastboot. never saw the qusb issue
Same thing just happened to my wife's 5a while she was browsing Facebook. There is no user accessible fix for this; while the QPST/QFIL programs may be found online, the MBN files necessary to reimage the device are not.
If you bought your device within the last 12 months, you should be able to get it repaired under warranty.
Here is the link for warranty repair.
V0latyle said:
Same thing just happened to my wife's 5a while she was browsing Facebook. There is no user accessible fix for this; while the QPST/QFIL programs may be found online, the MBN files necessary to reimage the device are not.
If you bought your device within the last 12 months, you should be able to get it repaired under warranty.
Here is the link for warranty repair.
Click to expand...
Click to collapse
My wife's phone now has this issue and we have important pictures on there we don't want lost. Is there a way to use the QPST program to get files off of the phone? Is there another way to get the files off of the phone when we cant get the device to even power on? When I plug it into a computer, I do get the QUSB device to appear.