So, I unlocked the bootloader and rooted my Moto G2, and installed a custom rom on it. I decided that I wanted to go back to stock Android but now my phone isn't recognized by the computer and when I turn it on it goes to Fastboot and I get the message "Fastboot Reason: Fall-through from normal boot mode" I can't do anything in Minimal ADB and Fastboot so im assuming my phone's dead? Any help would be appreciated.
I am having that trouble too, but mine is working fine, except for USB and fastboot mode
my phone also has the same problem.......on bootloader mode it is not recognised by any pc......
Related
Hellow. I have some problem with connection of my One. Atm i wanna s-off my phone.But can't.
After connecting phone to usb2.0 port win8 recognise it well (checked by "adb devices -l"). But when i try to reboot into bootloader i've got "waiting for device" (fastboot reboot bootloader). Ok i'm switch off the phone and boot in bootloader (fastboot mode). Phisical connection is good (fastboot usb). Try to check connection by "adb devices -l" and i got no one device connected. But in same time i can easy flash recovery by "fastboot flash recovery recovery.img". Btw when i put phone in fastboot mode my win8 told me that connected device not recognised and can't work good, but when i start android win8 got my phone well. I've check it with two original htc usb cables and one not original.
Any ideas?
Thx!
When the phone is in fastboot mode, you use the fastboot command, adb won't work. When the phone is not in fastboot mode, you use the adb command, fastboot won't work.
BenPope said:
When the phone is in fastboot mode, you use the fastboot command, adb won't work. When the phone is not in fastboot mode, you use the adb command, fastboot won't work.
Click to expand...
Click to collapse
ah i understand. tnx for reply
Hi,
I was on 5.0, running stock recovery and rooted. Today, installed TWRP for 5.0 on my device. I tried to flash the droid command center widget on my phone usng twrp, and it failed. I also hit the fix permissions option. After that the phone does not boot up, simply flashes the unlocked bootloader sign and shows the moto boot animation for a second or two before shutting down.
I can boot into recovery, and the computer detects the phone. But adb doesn't detect the device. I have the 1092 5.0 OTA on my computer and saved it on the phone in an attempt to flash it thru TWRP, but that failed with the message shown in the img attached. I also tried flashing stock 4.4.4, but that gave an error "Updating partition details" failed.
Can someone help me get back into my phone? :crying: ADB doesn't seem to be detecting my phone, else I'd have tried to install a rom via fastboot.
I have multi-tool v4.1 installed, would I be able to flash a rom (stock unrooted and full wipe is perfectly fine too) via that considering adb does not detect my phone, but the computer does?
Well, that looks annoying.
I've found myself in similar situations when I've accidentally flashed something I shouldn't have. The good news is that if you can boot to recovery you can also probably boot to the bootloader and use fastboot.
Have you tried wiping everything and going back to stock? It's time consuming but at least you'll end up with a working phone.
I had to do this when I put the wrong recovery on a phone and it mangled partitions. Device wouldn't boot.
There are instructions for the moto x here
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
oldcynic said:
Well, that looks annoying.
I've found myself in similar situations when I've accidentally flashed something I shouldn't have. The good news is that if you can boot to recovery you can also probably boot to the bootloader and use fastboot.
Have you tried wiping everything and going back to stock? It's time consuming but at least you'll end up with a working phone.
I had to do this when I put the wrong recovery on a phone and it mangled partitions. Device wouldn't boot.
There are instructions for the moto x here
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Click to expand...
Click to collapse
Thanks for the reply! Color me silly, but would I be able to use fastboot given that when I run adb the 'adb devices' command does not show my phone?
HAXTREME said:
Thanks for the reply! Color me silly, but would I be able to use fastboot given that when I run adb the 'adb devices' command does not show my phone?
Click to expand...
Click to collapse
Because fastboot mode can start on your device even before Android loads (and can even run when Android isn't installed at all), fastboot mode is useful for updating the firmware quickly, without having to use a recovery mode.
Adb relies on android booting and usb debugging being enabled and the computer being authorized for debugging (L feature). Fastboot does not. Try booting into the bootloader and then run "fastboot devices" . Mine shows up. I suspect yours will too. If it doesn't then I'm out of my depth here.
oldcynic said:
Because fastboot mode can start on your device even before Android loads (and can even run when Android isn't installed at all), fastboot mode is useful for updating the firmware quickly, without having to use a recovery mode.
Adb relies on android booting and usb debugging being enabled and the computer being authorized for debugging (L feature). Fastboot does not. Try booting into the bootloader and then run "fastboot devices" . Mine shows up. I suspect yours will too. If it doesn't then I'm out of my depth here.
Click to expand...
Click to collapse
Ah yes. For some reason, my fastboot file had gotten deleted from the folder and so the command didn't run. Everything went smooth once I noticed that. Had to downgrade to 4.4.4., but w/e. Thanks @oldcynic
Hello, I've a stock rooted moto g 2014 edition.
Today my phone started rebooting randomly. Half an hour ago it would restart after unlocking my device. Now it can't even get past the bootloader unlocked screen.
I've gone into fastboot and tried getting into recovery but it just reboots again after showing the TWRP splash.
I can't execute any commands through fastboot itself either, Minimal ADB and fastboot doesn't recognize the device.
Flash mode says battery low and asks me to connect the usb cable, but it already is and windows is prompting me "unknown usb device" even after the automatic fastboot driver install.
I haven't messed with any system files in a looong time.
Please help me, thanks.
EDIT: I had to get the drivers from the website, then all I had to do was erase userdata from fastboot.
Case solved =]
Hello, I have a problem with a motorola moto Z3 play of 128gb, as they tell me I was updating and ran out of battery and now starts in red letters that say the following:
Your device didin't start up succesfully
if this a Verizon device, use the Software Repair Asistant on computer to repair your device.
connect your device to your computer, to get the Software Repair Assistant.
if this is not a Verizon device, or Software Repair Assistant did not help for any reason, please contact your customer care center for further asistant.
AP Fastboot Flah Mode (Secure)
SSM: abl csv roll back 0.7
Not bootable A / B slot
Failed to boot Linux, Failling back to fastboot
Fastboot reason: Fail-trough from normal boot mode
when I want to connect it to flash it, the computer does not recognize me fastboot mode, nor adb, I put the commands "fastboot devices" or "ADB devices" and obviously it does not let me do anything, someone to help me out of that state or guide me a little to revive it, please !! ...
Sorry for my bad english.
Hi I have a problem where my pc does not detect my unlocked device in fastboot. This is a problem because I tried to update from global V10.3.3.0 to miui 11 but that did not work probably because there is not the right recovery on the device. So I can not get into the recovery and I can not get into the system this would of course be no problem because I can get into fastboot but my computer wont detect my device. How can I get my 9t pro to be detected in fastboot?
My device is unlocked. I did all that some time ago and it says so when I try to boot into system or recovery.
USB debugging is on. Idk if that is still there because I did try to update the system to miui11 but it was not detecting my phone in fastboot even before I did that update.
When I connected my phone to my computer when the system still worked I could use "adb devices" and that worked
I could also transfer files and stuff when my phone was connected to my laptop
So only when in fastboot my unlocked device is not detected if it was I could get back up there.
I really hope that this is some driver problem or something. Please help
Edit:
So at this point magically the system worked again! But I still can not use fastboot
I seem to have this problem:
https://forum.xda-developers.com/k20-pro/help/broken-fastboot-t3972697