I am using a MacBook (OS 10.6.8) with fastboot installed. It works when I use it with a Kindle Fire. I have not one, but three, factory cables, all of which (1) work with the Kindle Fire and (2) seem to work with my two broken-touchscreen a855 droids. I'm pretty sure that I've been able to get the droids into fastboot mode with the factory cable (and, in one case, without it) since (a) the info shown for the droids by System Profiler on the MacBook is very different when I boot with the factory cable (or boot holding down the volume down button) than what it is when I boot normally and connect with a normal cable and (b) I can boot with the factory cable without the battery installed.
But when I run fastboot the way I successfully run it to access the Kindle Fire, it doesn't recognize that the Droid is there. I've tried:
Code:
fastboot devices
fastboot -i 0x22b8 reboot
fastboot -i 0x22b8 reboot-bootloader
fastboot -i 0x22b8 getvar product
and all of the last three without '-i 0x22b8' as well.
It hangs either with no message or with the line:
< waiting for device >
until I press ^c, and sometimes I actually have to close the Terminal window to get out of it.
Is there something different I need to do to get fastboot on the Mac to recognize the Droids?
BTW, I can't use adb yet on these Droids because, without touch, I can't get to the setting to 'allow USB debugging'. Or is there a way to navigate the settings using the keyboard? (I would also need a way to get past the locked startup screen.)
CORRECTION noted on 2012/10/03: My point (a) above is only true in a certain situation. At times, perhaps depending on the battery status, and not when using a factory cable, System Profiler will show one of my Droids as SE Flash OMAP3430 MI rather than as Motorola A855, and the screen of the Droid will show, in plain white text on black:
Code:
Bootloader
2C.7C
[farther down:]
Battery OK
OK to Program
Transfer Mode:
USB
[With cable disconnected, the last two lines become:]
Connect USB
Data Cable
The A855 Droid does not support fastboot. If you're trying to flash a new image it either has to be done through a custom recovery or by using RSD Lite.
Isn't the A855 the same as the 'Droid 1'?
Dave Lister said:
The A855 Droid does not support fastboot. If you're trying to flash a new image it either has to be done through a custom recovery or by using RSD Lite.
Click to expand...
Click to collapse
Isn't the A855 the same thing as the Droid 1? If it is, then it is included in user SkOrPn's list of devices for which his factory cable works. Since he has probably sold hundreds of such cables, he would almost certainly know by now if he's wrong about that.
It's possible that I'm wrong about the identity of the A855 with the Droid 1. But if I'm not, my next guess is that you are wrong about the A855 not supporting fastboot. What are your sources for that assertion?
aarons510 said:
Isn't the A855 the same thing as the Droid 1? If it is, then it is included in user SkOrPn's list of devices for which his factory cable works. Since he has probably sold hundreds of such cables, he would almost certainly know by now if he's wrong about that.
It's possible that I'm wrong about the identity of the A855 with the Droid 1. But if I'm not, my next guess is that you are wrong about the A855 not supporting fastboot. What are your sources for that assertion?
Click to expand...
Click to collapse
The A855 is the Droid 1. What a factory cable allows you to do w/ an A855 is power the device even when the battery is dead due to the device only charging when the phone is fully booted, not in recovery or bootloader modes. I am my own source for this, as I have owned an A855 since it was released in November 2009 and was on the DroidMod ROM team for a time. The phone simply does not support fastboot.
Thanks for the clarification. I have downloaded RSD Lite 5.7 from tucows, but I have no idea what to do with it! (It's a zip file, but the contents is a single file with the .msi extension, which probably means I'll have to borrow access to a windoze machine to run it. I have and use a Mac.) Can you point me to a guide or the most compact compendium of info on using RSD Lite (or not having to use it!) that you know about that I can refer to without getting lost in hundreds or thousands of posts?
BTW, can I do these things without having a functioning touch screen? I already have one new digitizer ready to install, but I'd rather not install it until I have a good idea that the Droid will work reasonably well with it.
Finding an RSD Lite alternative for Linux/Mac took about 2 seconds of googling: http://www.atrixforums.com/forum/mo...h-any-sbf-file-without-rsdlite-mac-linux.html
And you don't need a working touchscreen for flashing RSDs or Custom Roms.
I had forgotten about the Linux/Mac alternative to RSD Lite. To put the phone into bootloader mode, press and hold "up" on the D-pad and then turn on the phone. You can then flash any .sbf file intended for the A855. I believe there are still some floating around that only flash a custom recovery image, which you can then use to install a new ROM off the SD card. Navigation in recovery is done w/ the power and volume buttons.
I've had some limited success. I downloaded sbf_flash, added .sh to the name and made it executable, then downloaded "VZW_A855_FRG01B_QSC6085BP_C_01.43.01P_SW_UPDATE_01.sbf" (a.k.a. 'FRG83G') from Peter Alfonso's site. I managed to get each of my two broken-touch droids (ignoring a third one I have with a broken USB/charge port!) into the mode with 'OK to Program' on the screen, and ran 'sudo ./sbf_flash.sh *.sbf' from the directory containing the two downloads. This got both of them into a state where I was supposed to 'touch' a green android, but couldn't, so I don't even know what ROM I have installed and whether it is rooted or not.
Any suggestions as to what further testing I can do on these Droids before deciding which to take apart and install the new digitizer on? Any way to get into USB Debugging mode without navigating with a touch screen?
BTW, one of the Droids also has a very unreliable (i.e., nearly useless) power button, so I got that one into the bootloader mode by (1) removing the battery, (2) connecting a factory cable to the Droid and then to the computer while holding down the 'up' button on the D-Pad, and (3) replacing the battery. Then I removed the factory cable and replaced it with a standard one before running sbf_flash. (Maybe I could have done it with the factory cable left in, but I didn't try.)
Related
I have a conglomeration of issues with my Kindle Fire HD 7. I'm currently in the process of ordering a factory cable from SkOrPn, but wanted to make sure there are no other avenues for me to attempt.
I'm very noob here, so bear with me. I've searched around, and attempted all the fixes that I've found, but for some reason, none are working.
My KFHD7 is currently stuck at the boot logo, non-animated. It came back to my company this way, so I'm not sure exactly what the person that had it before me was attempting to do with it. If I plug it into my PC, with Windows 8 Pro, I do NOT hear anything that tells me that the computer recognizes that the device is connected. I also do NOT see the device in the Device Manager. I attempt to install the drivers from the KFU, but for some reason, those fail every time.
I've installed Ubuntu, to attempt Soupkit, and Firekit. It isn't detected there, either.
Do I have any other options, or is a factory cable the way to go? Also, if/when I order the factory cable, will my computer then be able to detect the KFHD7?
I'm sorry if this question has been answered a hundred times already, but after searching for 3 days, and attempting everything I saw, I've reached the end of my rope.
Boot into the Ubuntu that you have SoupKit installed (will eliminate Windows driver problems), open a terminal and enter the following:
Code:
fastboot -i 0x1949 getvar product
Then reboot (hold power button for 10 seconds) when you see "waiting for device". That will get you into fastboot. From there you can flash a system.img and restore your device. Onemelia has a system.img restore tool in the HD7 dev forum that has a system image included so check it out.
[Edit:] Considering you don't know exactly what was done to the device, you should probably restore the stock recovery and boot partitions too. I've had situations where I've installed Hashcode's stack override, along with the custom boot and recovery images and my device acted the same way. Since the stack is on the system partition, overwriting it with a new system partition and leaving the custom boot and recovery partitions in place would presumably put the device in a hard bricked state, from which there is no recovery.
Will it be a problem that I have Ubuntu 12.10 installed, rather than 12.04 that you reference? Maybe that was half of my issue there.
Ok, scratch my last. Removed 12.10, and put 12.04 on instead. I did as you said, and after initial reboot after the fastboot command, it's still sitting at waiting for device. It's been about 3 minutes. Advice?
honberiz said:
Ok, scratch my last. Removed 12.10, and put 12.04 on instead. I did as you said, and after initial reboot after the fastboot command, it's still sitting at waiting for device. It's been about 3 minutes. Advice?
Click to expand...
Click to collapse
Get the cable. It's worth way more then the price. After you get it, check out the first aide link in my signature. Good Luck!
I was actually JUST reading about your program. To perform a system restore, I'd need a clean backup, wouldn't I? This came to me borked, so I don't have a backup of it. Are there backups that are available for download?
honberiz said:
I was actually JUST reading about your program. To perform a system restore, I'd need a clean backup, wouldn't I? This came to me borked, so I don't have a backup of it. Are there backups that are available for download?
Click to expand...
Click to collapse
Onemelia's system.img restore tool in the development section has a system image...I'm not sure about the boot and recovery images though. If not, PM me and I'll send you copies.
As far as which version of Ubuntu, it shouldn't matter. The key packages are 'dpkg' which comes with all Debian based distros that I know of, and 'apt-get' which comes standard on all Ubuntu based distros I believe, so you should be fine either way. If you're using a 64bit install, I'd suggest you switch to a 32bit install. And make sure you aren't using a USB 3.0 port. As a matter of fact, you should probably switch to a dedicated usb port rather than a hub. A good way to check to see if Linux can even see your device is with the 'lsusb' command...you should see a device called "Lab 126".
Hey all,
So I have few questions about using the factory cable to fix my soft-bricked KFHD. If you want to read what I did to mess it up and what I've tried so far that's here in this thread but the TLDR is that I messed up my rooted kindle, won't boot, won't show up when plugged in (presumably ADB is off now) and so I ordered a factory cable from SkOpRn. I should get my cable today/tomorrow and I had a few questions before I start blundering about like a bull in a china shop. I've tried to read all the relevant threads here but some of the information seems conflicting/unclear. Here are my two clarification questions:
1) As I understand it, by plugging the device in with the factory cable I should be able to force it into a fastboot mode that allows me to issue commands. Assuming this works, do I continue to use the factory cable for the restore process or is the cable just a one-time "plug in" after which I use the standard cable to restore?
2) I was running 7.2.3 before things got messed up, so once I am able to get it to accept fastboot commands do I use kffirstaide to actually do the restore (Option 4: Completely Restore the KFHD 7.2.3)? I'm thinking along the lines of this guide here and using "Option 4" in "Step 16".
I'm probably over-complicating things but I hate to make things any worse by doing something wrong.
Thanks!
MightyBraeburn said:
As I understand it, by plugging the device in with the factory cable I should be able to force it into a fastboot mode that allows me to issue commands. Assuming this works, do I continue to use the factory cable for the restore process or is the cable just a one-time "plug in" after which I use the standard cable to restore?
Click to expand...
Click to collapse
The fastboot cable is just a trigger. It tells the device to start up differently by powering a pin that does not normally have power. Once you see the fastboot screen, I recommend changing back to a normal cable. You really don't want that extra power hanging out ready to wreak havoc if there's any unexpected fault in the cable (especially if you got one from a random person on eBay).
With standard cable.If the device is recognized by adb then you can use this command:
Code:
adb shell su -c "reboot bootloader"
See the status kfHD have fastboot and you can go from there .
psych0phobia said:
The fastboot cable is just a trigger. It tells the device to start up differently by powering a pin that does not normally have power. Once you see the fastboot screen, I recommend changing back to a normal cable. You really don't want that extra power hanging out ready to wreak havoc if there's any unexpected fault in the cable (especially if you got one from a random person on eBay).
Click to expand...
Click to collapse
Agreed once in fastboot u can user standard kindle micro USB cable also if your kindle is recognised in any way by your PC in device manger even if its an unions p unknown device u should be able to voice force install the drivers for it if u need help and this is the case pm me
Sent from my KFTT
I don't know about kffaide but the restore tool in the dev section claims it replaces the boot loader when you flash 7.2.3
Sent from my GT-P3110 using xda app-developers app
Thanks everyone all for the help! In case anyone else stumbles across this thread with a similar problem, let me summarize what I did to fix my KFHD7:
1. I used SkOrPn's factory cable to get the device into fastboot mode (I just plugged it in for a few seconds until fastboot came up and then switched to the standard USB cable).
2. Once in fastboot mode it was detected by my computer with no problems and I could issue fastboot commands.
3. As soon as I could issue commands I took no chances and used kffirstaide to flash 7.2.3. kffirstaide must provide the stock image because it installed and rebooted fine except without root. I do remember seeing somewhere in a dev forum an image of 7.2.3 that came pre-rooted but I couldn't find it easily. Since I had already rooted it once before it was no big deal to root again.
I can't believe I went from a soft-brick (not even being detected via usb) back to normal so easily! Thanks again for all the help and suggestions!
Bricked my droid bionic about a day ago, and have been looking across the web to find a fix. Here is the current information I have on it:
- Low battery
- Boot mode selection menu 0a.53 (assuming stock recovery)
- Stock recovery options with 'apply update from sd, wipe data/factory reset, and wipe cache partition
- apply update with just about any zip returns 'E: Signature verification failed', including the ROM previously used.
- Able to enter BP sbf flash mode, but decide cannot communicate (maybe cable)
- Able to enter ap fastboot mode, and usb transfer mode is obtainable. Before battery was on low, could program. Now get 'cannot program'.
- In ap fastboot mode, with usb transfer mode active, PC unable to communicate. Attempted with apk, apktoolkit, and RSDlite
- Have backups made by clockwork recovery of the whole device
- Have copy of ROM zip used for previously running android instance.
- XT875 model
Willing to do just about anything to unbrick this phone. I love the phone, and I don't want to replace it. Unfortunately, my job requires me to be in constant communication so I've a need to fix it ASAP.
Edit:
Tried flashing multiple stock ROMs and other things from stock recovery with little luck, most returning invalid signature
Use an exact Moto cable. No substitutes! Check PC drivers or Moto Device Manager.
Sent from my GT-P3110 using Tapatalk
unbrick
zaros104 said:
Bricked my droid bionic about a day ago, and have been looking across the web to find a fix. Here is the current information I have on it:
- Low battery
- Boot mode selection menu 0a.53 (assuming stock recovery)
- Stock recovery options with 'apply update from sd, wipe data/factory reset, and wipe cache partition
- apply update with just about any zip returns 'E: Signature verification failed', including the ROM previously used.
- Able to enter BP sbf flash mode, but decide cannot communicate (maybe cable)
- Able to enter ap fastboot mode, and usb transfer mode is obtainable. Before battery was on low, could program. Now get 'cannot program'.
- In ap fastboot mode, with usb transfer mode active, PC unable to communicate. Attempted with apk, apktoolkit, and RSDlite
- Have backups made by clockwork recovery of the whole device
- Have copy of ROM zip used for previously running android instance.
- XT875 model
Willing to do just about anything to unbrick this phone. I love the phone, and I don't want to replace it. Unfortunately, my job requires me to be in constant communication so I've a need to fix it ASAP.
Edit:
Tried flashing multiple stock ROMs and other things from stock recovery with little luck, most returning invalid signature
Click to expand...
Click to collapse
You are going to need rsd lite on your PC. The fxz files for your current build. A Motorola brand USB cord. And the latest Motorola drivers.
---------- Post added at 05:02 PM ---------- Previous post was at 04:43 PM ----------
http://forum.xda-developers.com/showthread.php?t=2728352
See post #7 for the fxz build you will need to use.
Did fxz work for you?
Unbricking
I ran into same problem before, with Motorola it's a pain to do anything especially charging the batteries on it once it's been brick. If you search around this forum you can find a little article about a guy tweaking his ps3 controller to charger his battery. I wouldn't recommend doing this if you don't know what you're doing. But what I did was buy this little device that charges any phone battery I'm not sure if I can link a photo but i'll try it, not i'll give a name. In order to RSD and use ab fastboot mode on the xt875 you'll need at least 70-80 percent battery life, at least that's what the guys here on the forum recommend. But I've been able to unbrick my device only 40 percent battery life. Now once that battery is charge to a reasonable charge. You'll have to download the cdma targa file for your phone. I don't think anyone matters as long as it's the exact same or newer of your phone's original firmware. Extract the targa file and then run RSD lite click the ... button to open file and locate your extracted cfc file. Now you may run into some flashing issues with failure in step 5/10 and if you don't, don't worry about it. but if you do you'll have to open up the cfc file with wordpad and remove a few lines from. here are the lines that need to be removed; <step operation="oem" var="fb_mode_set" /> AND <step operation="oem" var="fb_mode_clear" />....there's another fail that happens but I haven't found anyone that had experience this problem. it seem like I was the only one that experience it. it has to do with something with the fail flash.bin or something I'm not sure. But I left a comment about this fix on this forum somewhere if you care to search for it. once you edit and remove those above mention lines save and run it again and it should operate flawlessly. I have also left a link down there for the edit cfc file and pictures of the device I was referring to about charging your batteries directly.
also you mention that it could be a cable thing. I read a lot of this but I've use the cable wires from my Samsung without any mishaps besides the above mention issues with 5/10 but this was a common problem that even thoses with a Motorola cable had faced. from what I know theses wires are exactly they're usb 2.0 wires and couldn't differ from each other that much. but it is probably better to use the exact cable than a non exact one. the reason it won't communicate is the battery is low as I have mention you'll have to charge this battery of yours to a decent 40 and up for it to run cause the process of re flashing can take anywhere 10-15 minutes and you don't want it to die in the middle of flashing your firmware. cause this I believe can lead to a hardbrick. the stock verification recovery will always have that return that value even from stock roms. Therefore it is recommend to use the RSD lite so you won't face that problem. I hope this helps.
Bricked
I thought my phone was history. The solution was using an actual Motorola USB cable. It made all the difference.
Maybe you installed an incorrect driver.
Hello everyone,
I've just tried installing twrp-3.0.2-3-thea.img (md5sum: 35c37561f0c22bfe23cd01b5c388e8b5) and BETA-SuperSU-v2.62-3-20151211162651.zip (md5sum: 7fcb30bcbcd18b5f0b0f5848a096d4ed) on a Moto G LTE 2014 "Thea".
Unfortunately something didn't work. The device first was stuck in the boot animation, then started booting correctly a few times, but now it's completely bricked:
I've been unable to turn the phone on using either pressing power+button down for 10 secs or just pressing the power button for 2 mins while being connected to an usb charger. Obviously it won't connect to adb/fastboot/etc.
I'm really puzzled. Is it even possible to brick a device like this just by trying to root it? Any suggestions?
Alright, found the issue - it seems that for some reason or another flashing TWRP or SuperSu caused fastboot to stop working, hence the hard brick. Now It shows up as "qhsusb_bulk" - unfrotunately there's no way to fix this by myself given that the only fastboot images ( "MBM-CI") available are for Android 4.4.4.
If your bootloader is unlocked you shouldn't have any problems reflashing. You do however have to make sure you are flashing the correct recovery IMG for your phone there are a very large number of ROMS and each is device specific. Try leaving LTE out of your search criteria when searching for images to flash with, rather just Moto G 2nd gen 2014 and you will be on your way to finding the correct IMG. I found a Titan IMG that works with my XT1072 and believe you me that was after the 5th/6th time of reflashing! Another handy tip is that in order to enter into fast boot or recovery mode there's are a few things to consider, namely
The version of fastboot adb you have installed on your PC, some versions behave strangely? Don't ask me I know nothing!
Secondly and very importantly you need to have latest drivers for your make and model of phone installed on your PC.
Thirdly before you connect your phone via its USB cable to PC you must first start up fastboot if you are just using fastboot. I have mine sitting as shortcut on desktop right next to adb shortcut for convenience.
Fourth: hold power button plus vol down for about 3-5 seconds, continue to hold vol- button but let go of power button (this is an important detail that many people on the forum forget to mention) with Motorola specifically!!!! Trust me do it this way and you will almost certainly always boot into recovery/fastboot mode
5th connect your phone to your PC ( not to teach your grama how to suck eggs but don't forget to select USB debugging under dev options on your phone) hopefully you did this??? Otherwise I don't know what the work around is for that, other than factory reset and start over?!
Anyway after connect to PC in the shell terminal run the adb devices command if you are in adb or
run the fastboot devices if you are in fastboot to see if your computer can detect your device? This is a clear indication of whether or not your bootloader is unlocked and/or whether USB Debugging is selected, shouldn't be hard to work out which device is yours as only one device should then show up. There are threads on XDA about how to unlock BL. Aquire root and flash recovery images, obviously, but I couldn't begin to tell you how to do that as each scenario is so different from the next, best of luck!:good:
None of those solutions would obviously work, considering the bootloader/fastboot partition has been altered to the point the device won't boot at all, forget about Drivers or USB Debugging.
By the way, I've just got my device from motorola, after roughly two months since they took it to the repair centre. Their official response has been "We won't fix devices who had been tampered with".
Oh well. When I got it back the clerk could only congratulate me for my really nice new paperweight.
The phone isn't starting at all? It shows something on the screen or acts just like powered off?
Now It shows up as "qhsusb_bulk"
Click to expand...
Click to collapse
You mean the PC isn't recognizing the phone at all and just shows an USB device with that identifier?
LuuchoRocha said:
The phone isn't starting at all? It shows something on the screen or acts just like powered off?
Click to expand...
Click to collapse
Completely blank screen. No response whatsoever.
You mean the PC isn't recognizing the phone at all and just shows an USB device with that identifier?
Click to expand...
Click to collapse
That's right. It's the same error which occurs on some MSM89xx SoCs when the bootloader/blankflash gets steamrolled. But contrary to what happens to some devices like the Galaxy SIII, there are no available bootloader image files available anywhere, and it looks like the SoC used on mot g devices does not provide any failsafe boot mode from sd.
In other words, it's a really nice paper weight until a disgruntled Lenovo employee leaks the required files somewhere. Actually, according to the Motorola tech guy I've spoken to, there's the chance that clearing the bootloader triggers an efuse making it impossible to recover from altogether, but I really hope this is not the case.
I'll start out by saying I was careless and had not read various threads before flashing things and causing my issues. I've already bought a replacement phone but I'd like to see if there's any chance to revive the Moto X or not.
What happened:
I had unlocked the bootloader years ago. I was running the (mostly) stock Lollipop 5.1 with XPosed, and got noticed of a security update.
After fully charging the battery, I flashed stock recovery over my custom recovery (TWRP) and then, without thinking, got the latest image from Motorola without realizing it was a 4.4.4 image.
I flashed the system partition using this image thinking it would remove SU and that I could install the update - this soft-bricked the phone when I tried to boot.
Too late, but at this point I re-flashed TWRP and ran a backup. I used adb to extract the backup and my other files from the /sdcard partition.
Factory Reset. The phone boot up at this point.
I tried flashing the logo, gpt.bin (I forgot that Lollipop changed how partitioning worked) and then did another Factory Reset. Phone boots fine.
I then tried restoring the data from my nandroid backup. Rebooted once, and phone seemed to start. And then it went black.
At this point, the phone does not appear to boot at all. I can't use Vol Down + Power to boot into Fastboot, and if I connect to a computer, it does not see the device... USUALLY.
If I connect via USB to my Windows computer, and try to boot into Fastboot, the green LED behind the volume will flash once and my computer will signal the "Hardware connected" sound. I can try to run 'adb reboot bootloader' but adb reports that it doesn't see any devices. My system events note a USB Input Device was added but don't get any further. Within 5 seconds, the "hardware disconnected" sound fires. About 20 seconds later, this will repeat on its own.
I just tried making a fastboot cable from a spare micro usb cable... I may have done it wrong - but it does not seem to have had any effect. The result is the same. It's possible I didn't solder the connection well, though (it was difficult exposing the terminals on my particular cable).
The screen is always black and never lights up in any way.
It kind of makes me think that the device is attempting to boot, fails, and cycles. Is there anything I can do?
At this point I am able to get into fastboot after bricking my XT1060DEV in a similar way. Follow the guide as best as you can in this post. Toward the end of that thread you can see the sequence of events that led me to at least fastboot mode.
Awaiting a response from someone who might know which gpt.bin and bootloader I can flash to have more than a blank phone. I'll try to keep you updated.
EDIT:
You might find it easiest to get QHUSB set up using this guide. This guide has been superseded by the previously posted one, but some people still report success following it.
PiArc said:
At this point I am able to get into fastboot after bricking my XT1060DEV in a similar way. Follow the guide as best as you can in this post. Toward the end of that thread you can see the sequence of events that led me to at least fastboot mode.
Awaiting a response from someone who might know which gpt.bin and bootloader I can flash to have more than a blank phone. I'll try to keep you updated.
EDIT:
You might find it easiest to get QHUSB set up using this guide. This guide has been superseded by the previously posted one, but some people still report success following it.
Click to expand...
Click to collapse
I may not have a chance for a few days, but I will try this. I did try to download the software on the second link you provided and some of the links on that page were broken.
I'm not going to lie, navigating those threads is harsh.
Towards the end of the first linked thread you can see a post with what ended up getting me into fastboot. It might be a decent little roadmap to guide you in the right direction (plus, I think the files I indicate in that particular post are all still up).
Keep us updated!
ohioDroid said:
I'll start out by saying I was careless and had not read various threads before flashing things and causing my issues. I've already bought a replacement phone but I'd like to see if there's any chance to revive the Moto X or not.
What happened:
I had unlocked the bootloader years ago. I was running the (mostly) stock Lollipop 5.1 with XPosed, and got noticed of a security update.
After fully charging the battery, I flashed stock recovery over my custom recovery (TWRP) and then, without thinking, got the latest image from Motorola without realizing it was a 4.4.4 image.
I flashed the system partition using this image thinking it would remove SU and that I could install the update - this soft-bricked the phone when I tried to boot.
Too late, but at this point I re-flashed TWRP and ran a backup. I used adb to extract the backup and my other files from the /sdcard partition.
Factory Reset. The phone boot up at this point.
I tried flashing the logo, gpt.bin (I forgot that Lollipop changed how partitioning worked) and then did another Factory Reset. Phone boots fine.
I then tried restoring the data from my nandroid backup. Rebooted once, and phone seemed to start. And then it went black.
At this point, the phone does not appear to boot at all. I can't use Vol Down + Power to boot into Fastboot, and if I connect to a computer, it does not see the device... USUALLY.
If I connect via USB to my Windows computer, and try to boot into Fastboot, the green LED behind the volume will flash once and my computer will signal the "Hardware connected" sound. I can try to run 'adb reboot bootloader' but adb reports that it doesn't see any devices. My system events note a USB Input Device was added but don't get any further. Within 5 seconds, the "hardware disconnected" sound fires. About 20 seconds later, this will repeat on its own.
I just tried making a fastboot cable from a spare micro usb cable... I may have done it wrong - but it does not seem to have had any effect. The result is the same. It's possible I didn't solder the connection well, though (it was difficult exposing the terminals on my particular cable).
The screen is always black and never lights up in any way.
It kind of makes me think that the device is attempting to boot, fails, and cycles. Is there anything I can do?
Click to expand...
Click to collapse
Try reflashing twrp via fastboot, install custom ROM -OR- download latest XML for your variant flash via rsd lite or manual flash.
Note: When using the XML you will lose everything, including data on internal storage.
Hopefully this helps ?
Also, if your phone stays black it's likely the battery is dead. Leave it hook up for awhile or keep trying to boot into fastboot(while plugged into outlet, not PC) and leave it for a couple of hours, should charge.
I'm speaking from personal experience, just without having Xposed framework, lol.
Sent from my Moto X using Tapatalk