[Q] Adb Working, Fastboot not (Tried everything) - G 2014 Q&A, Help & Troubleshooting

Hello,
I have a Moto G 2014 (XT1069), I installed the Lollipop 5.0.1 Stock ROM via TWRP but I had some problems and I did some sh*t (I wiped the /system/ partition and had to install everything again).
Anyway, I've been using my phone without problem for a couple of weeks but now, it keeps restarting or freezing. So I want to install a new ROM (Quantum LP). So I tried to get TWRP recovery mode and it shows the Android with red exclamation sign. Then I re-downloaded the TWRP v.2.5.0 but when I try to run "fastboot devices" my device doesn't show!
What I already did?
I installed the Google USB Drivers, Motorola USB Drives (Device Manager), re-installed the drivers, installed the "minimal usb drivers, 15s installation tool" that I downloaded here on XDA. Without success. ADB Shows, but Fastboot don't.
There is any error?
Yes, there is one. I searched the devices management at Windows Control Panel and found: "fastboot titan s drivers not installed", I tried to search for the drivers without success again.
What can I do?
I didn't found any thing related to this problem. Everyone is saying: "install drivers" but I've installed. Adb shows, fastboot don't.
My Moto G 2014 is the DTV one (with TV..., but I really don't care about this feature).
Anyone knows a fix to this?

I ran into the same problem...

Related

Need help sideloading with TWRP (don't think it's recognizing the driver)

I'm stuck on the Moto boot screen for a XT1032 after trying to flash a stock kernel (had previously successfully installed ParanoidAndroid ROM and then deleted the ROM from the device).
Trying to install a rom or stock via ADB sideload but it's not doing it because it doesn't recognize the device. Moto Drivers are installed. XT1032 shows up in device manager with a yellow exclamation point. I downloaded that USB_Driver folder for standard adb but it says it can't install the driver because it's not for the device or something.
Hi, I am having similar problem. When I try to start adb sideload from within TWRP 2.8.6.0, it just says starting ADB sideload but gets stuck there. I even flashed stock recovery and tried to get into recovery and holding Vol+ for 15 secs and power up doesn't work from there.
Did you solve this issue???
Sportfreunde said:
I'm stuck on the Moto boot screen for a XT1032 after trying to flash a stock kernel (had previously successfully installed ParanoidAndroid ROM and then deleted the ROM from the device).
Trying to install a rom or stock via ADB sideload but it's not doing it because it doesn't recognize the device. Moto Drivers are installed. XT1032 shows up in device manager with a yellow exclamation point. I downloaded that USB_Driver folder for standard adb but it says it can't install the driver because it's not for the device or something.
Click to expand...
Click to collapse
What recovery are you using ? Also try downloading drivers from official motorola website .
@Sportfreunde Just in case you didn't know this is the Moto G 2014 part of the forum. This is for XT1063/64/68/69. I think you are looking for is http://forum.xda-developers.com/moto-g/

[Q] Moto g 2 stuck in bootloop, haven't done anything though?

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 =]

Fastboot Problem (Freezing, probably not drivers)

Hello,
I've got a problem when trying to load fastboot that I haven't been able to find a solution for here. I'm hoping someone else has run into this and can help. My phone (H811) seems to freeze upon entering fastboot mode. I have...
Flashed 20i using TWRP
Enabled OEM Unlock and Debugging
Uninstalled and Reinstalled drivers in every imaginable configuration over the past two days
Flashed (and completely wiped internal storage) the 20i KDZ
Continued to muck around with drivers
Everything is fine when connecting to my PC, ADB has no issues. I run into trouble when rebooting (via ADB) and the phone freezes. The power button is unresponsive and I have to pull the battery to exit fastboot. My device manager shows -something- is connected after entering fastboot, but so far I haven't been able to find a working driver for that.
Thanks

Help me please, I don´t have gapps installed...

Hello to everyone.
I hope somebody to help me, last night i tried to update mi Lineage OS 16 (from erfanoabdi).
My device is unlocked bootloader, and i used the rom from nightly build (2018-21-09), it works fine and everything, the issue becomes when i look what was avaible a new update, so downloaded and install the new rom.
I do full wipe, after that i install the new rom, at this point everything its working fine, but after that when i changed the partition slot from A to B.
When i started to install the gapps they closed because it says what i am running Android 8.0, but its a mistake so i think that reboot the phone without install the gapps. So the phone starts well, so i decide again to boot into recovery (TWRP) to install the missing gapps.
When the device reboot in fastboot and i chosee the recovery option, the surprise was that TWRP was reemplaced by the stock recovery, and when i tried to flash the TWRP.img my device wont appear in fastboot mode, stays finding device and Windows wont recognized my phone.
I think the rom still no have usb adb support, so i cant flash TWRP
My device its unlocked and i was running the rom (but another nightly) .. without issues for a week ago... until i flashed this one
Now i have Lineage OS without GAPPS, without USB mode... Like the update from OPW 27 or 28 idk remember.
Its possible to fix? or my phone its ****ed, or there is one form to installl the gapps from anoter form?
Thanks for read this i hope somebody can help me.
My device its a XT1900-4 in Android 9.0 without google apps, only have the essencial apps like phone dialer , sms, the very very essencials app. Like an phone from 2008 jhaha
i offer some pay.
Update:
I attach some information photos from the Rom that im running:
(System Running) fine thanks
https://ibb.co/bXC7ye
(ADB is switched on, but no appears nothing)
https://ibb.co/exGpBz
(I tried with everyone of the opcions
https://ibb.co/ekv5jK
and this is my currently fastboot:
AP Fastboot Flash Mode (Secure)
BL: MBM-3.0-uefi-641a15b-180224
Baseband: M660_7042.27.01.74R PAYTON_LATAM_CUST
Product/Variant: payton xt1900-4 32GB P4
CPU: SDM630 1.0 (6)
Console [NULL]: null
Tools Mode Config: DISABLED
POWER OK
flashing_unlocked
Software status: Official
Transfer Mode: USB Connected
At this point my windows so says to my device is Error in a request for the USB device descriptor.
i tried last_usb_google driver.
Motorola Device manager 2.5.4
Minimal adb fastboot 1.4.2
and nothing works fine.
In my recovery appears this:
Android Recovery
motorola/payton/payton
8.0.0/OPW27.57.25-6-10/12
user/release-keys
Use volume to...etc and then i used the (Apply update from adb)
says:
Supported API: 3
Stopping adbd. . .
Now send the package you want to apply to the device with "adb sideload <filename>"
Help me pls:crying:
I have a Nokia 7 plus which is also a A/B device. I have observed many times that the fastboot mode isn't detected by the pc. Sometimes when I have a bootloop during experimentation, I force reboot into bootloader mode but it's not recognised. I reboot into recovery and select "reboot to bootloader", and this time it's recognised. Maybe these issues are related to A/B system, I'm not sure.
I think you should have the Motorola device manager installed if you're working on Windows. It contains the necessary drivers. I can't remember if it contains adb and fastboot executable files, but if it does then try using them (launching command prompt from there).
Broadcasted from Zeta Reticuli
Gravemind2015 said:
I have a Nokia 7 plus which is also a A/B device. I have observed many times that the fastboot mode isn't detected by the pc. Sometimes when I have a bootloop during experimentation, I force reboot into bootloader mode but it's not recognised. I reboot into recovery and select "reboot to bootloader", and this time it's recognised. Maybe these issues are related to A/B system, I'm not sure.
I think you should have the Motorola device manager installed if you're working on Windows. It contains the necessary drivers. I can't remember if it contains adb and fastboot executable files, but if it does then try using them (launching command prompt from there).
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
thanks for quicky reply, but i tried that and it doesnt work for me... :c
the motorola device manager its installed correctly, but i think the usb in the Android 9 it´s no working on running s.o and even in fastboot.
vmmiguel said:
thanks for quicky reply, but i tried that and it doesnt work for me... :c
the motorola device manager its installed correctly, but i think the usb in the Android 9 it´s no working on running s.o and even in fastboot.
Click to expand...
Click to collapse
My windows cmputer says that my device doesnt works properly, i read all night about this and i think when i some point i made wipe /system so i delete the twrp and the rom doesnt have usb adb i think so hahaha, i think now my x4 will stuck on only aosp 9.0 without g services :crying::crying::crying:
id start with a flash all of the latest stock firmware to clean it up. then start over
edufur said:
id start with a flash all of the latest stock firmware to clean it up. then start over
Click to expand...
Click to collapse
I tried but i have only stock recovey, and the usb adb it's not working, i think that i need to flash stock rom from stock recovery, but i dont know...
vmmiguel said:
I tried but i have only stock recovey, and the usb adb it's not working, i think that i need to flash stock rom from stock recovery, but i dont know...
Click to expand...
Click to collapse
You have to flash stock rom from fastboot. Try removing "fastboot erase userdata" from script flash-all.
Comby_sk said:
You have to flash stock rom from fastboot. Try removing "fastboot erase userdata" from script flash-all.
Click to expand...
Click to collapse
Hello Buddy, i tried that but doesnt work, recently i discover that my usb default mode is gray so i think i cant switch beetwen the usb option, and i tried ADB over network, in terminal emulator to run adbd service but it crash :c
@erfanoabdiadbi plz you cant help me, i really i was enjoying you excelent deveploment, but now in stuck in this without essencial apps like whatsapp, my smartphone works like only phone without been smart jajaja:crying::good:
Anyone?
vmmiguel said:
Anyone?
Click to expand...
Click to collapse
Read through this thread carefully...
https://forum.xda-developers.com/moto-x4/development/rom-lineage-16-0-developer-preview-t3849699
I have more or less the same problem.
I am stuck in LineageOS 15.1 and for some reason Windows does not recognize my phone (it does with other x4 phone from a friend).
I also don't have GApps installed and also don't have root access. Since I can't connect my phone, I can't root or flash some custom recovery.
I really need some help.

Solved: Can't pass fastboot commands to bootloader

Hi guys,
I've got a real head-scratcher over here. I followed every guide to a T, but I can't get my computer to detect my device in fastboot.
I installed the Xperia companion. I tried to manually install the Google USB drivers, and the sony OEM drivers. Still, no matter what, when I enter, what is supposedly fastboot, it never shows up. When the phone is on ADB devices shows it just fine. I am at a total loss!
To enter fastboot, I am shutting down the phone, pressing the volume up button, and plugging it in, then I get a black screen and a blue LED, which supposedly is correct? I've personally never seen anything like this before. Device manager does detect it as an unknown Android device, however, if I try to apply any drivers to it Windows simply informs me I already have the latest ones installed.
Thanks
SOLUTION: It was a driver issue after all. Windows 10 would not detect any drivers, nor let me install any drivers manually from files, however, it did let me select built-in drivers from my computer. YMMV, but If you are running into this issue try this:
1) Put your phone into bootloader mode.
2) Open device manager.
3) Right-click the device called "Android" with the yellow question mark, and select "update driver."
4) Click the "Browse my computer" option.
5) Click "Let me pick."
Note: There are several categories here, I suggest you try them all: portable devices, android devices, and in my case, Samsung devices. In one of the categories, you will find Google listed as a manufacturer.
6) In one of the categories, you will find Google listed as a manufacturer (in my case it was under the "Samsung Devices" category).
7) Select Google and then select the newest fastboot driver listed (in my case it was dated 2016), and install that driver.
8) Go back to PowerShell and run "fastboot devices." With a little luck, it will work!
Previous steps:
Edit: I had the thought of trying
Code:
adb reboot fastboot
and that got me into fastbootd, and then my PC detected it, however, the phone did not accept the unlock command.
Code:
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
I rebooted into the bootloader from here, got the same black screen, blue LED as above, and my phone is still not detected by fastboot.
Make sure you open cmd window in fastboot folder...i hope this is help
Sony fastboot mode is different I think. It was odd to me but doesn't show anything on screen when I went to fastboot to flash US firmware
mehdi_s82 said:
Sony fastboot mode is different I think. It was odd to me but doesn't show anything on screen when I went to fastboot to flash US firmware
Click to expand...
Click to collapse
I live in Boston and got the the XQ-AT51 (despite the fact that B&H was originally selling the 52... so in a few months I'm going to have to flip this phone ), do I have to reflash a stock firmware before I can unlock the bootloader? I do have it from XperiFirm.
Edit: This was dumb of me as you can't flash anything onto the phone unless the bootloader is already unlocked.
Edit: I don't want to double post, but I managed to solve the problem, and added the solution to the OP.
THANK YOU VERY MUCH FOR THIS GUIDE. I was struggling for hours on end with the "Unable to open fastboot HAL" error message, but followed the steps outlined in your guide a little differently than you, since I'm on windows 7. I believe that the root cause of my issue was that I actually used the down volume button instead of the volume up, believing that it was weird for the screen to show nothing except for the blue notification LED.
Here is what I did just in case for people who might encounter the same issue in the future. Be warned though that I'm not an english native so the options won't be accurately translated but I'll try to do my best nonetheless.
1) Put your phone into bootloader mode (volume UP + power button, not down.) Don't be afraid if nothing shows up, it's actually normal
2) Open device manager
3) Right-click the device called "Android" with the yellow question mark, and select "update driver."
4)ISelect "Look for drivers on my computer (manual install option)
5)Select "Choose from a list of drivers installed on this computer"
6)Scroll down through the manufacturers and such until you find "sony sa0200"
7)Install it
Normally everything should be working fine with fastboot. What a relief
I have a similar problem, but my device manager does not show any android device from the bootloader. I've tried multiple cables and everything works fine in adb mode.
EDIT: Nevermind. It ended up being multiple bad cables. They all worked in ADB/booted but not in Fastboot/bootloader. Tried one more it it worked completely
I have same issue with my Poco X3 Pro, the device working fine and is recognized as ADB composite when i'm under MIUI, but when i launch the device in fastboot mode, the ADB composite disappear and a generic "android" device appear and i'm not able to install any drivers, no qualcomm, no xiami, no generic google usb, nothing.
Following the tips above, nothing work. I'm under windows 7.
Any tips?
Thx everyone for pointing me to the right direction. Flashing latest twrp was the final step. Recovery is back to now .

Categories

Resources