Database Info

[Q] ADB Recognizes device, but not fastboot. Can't seem to find a fix yet.

So I am trying to flash an updated recovery of ClockworkMod onto my device, rooted, bootloader unlocked, etc. and installed the Android SDK to use ADB and fastboot. My Samsung USB driver is installed obviously because when I type "adb devices" it pops up with a mix of numbers and letters, which I assume is my device plugged in. I use "adb reboot bootloader" to get into bootloader and once I am in there my device is not recognizable by fastboot. ADB and fastboot are in the same folder in the C:\ drive, and I have tried using PDAnet drivers as well. I could really use some help! USB Debugging is on in the settings as well.

Syflox said:
So I am trying to flash an updated recovery of ClockworkMod onto my device, rooted, bootloader unlocked, etc. and installed the Android SDK to use ADB and fastboot. My Samsung USB driver is installed obviously because when I type "adb devices" it pops up with a mix of numbers and letters, which I assume is my device plugged in. I use "adb reboot bootloader" to get into bootloader and once I am in there my device is not recognizable by fastboot. ADB and fastboot are in the same folder in the C:\ drive, and I have tried using PDAnet drivers as well. I could really use some help! USB Debugging is on in the settings as well.
Click to expand...
Click to collapse
The GS3 does not have fastboot. All flashing is done through odin.

ddggttff3 said:
The GS3 does not have fastboot. All flashing is done through odin.
Click to expand...
Click to collapse
Thanks! Also, how do I update ClockworkMod recovery to the newest one? I've used ODIN before but am not sure if it is capable of flashing .img files.
EDIT: Nevermind, I just downloaded ROM Manager and used that to flash 6.0.2.3

[Q] M4 soft-bricked! Cannot restore backup! Need help!!!

Hey guys,
I seriously need help with my M4. I think I might have soft-bricked it :crying:
Here's what I have done:
I unlocked it and installed TWRP 2.7.1.1 to install a custom ROM. The thing is, I didn't know it was branded (as I found out too late, the CID is VODAP102), so the ROM wouldn't install. Now, I tried to change the CID to a SuperCID (11111111) but ran out of luck. So I thought I'd simply revert to Stock. So far, so good. Yesterday I got an update notification for a Sense 6.0 update but it wouldn't install. So I successfully flashed the stock recovery but the installation of the update halted (red exclamation mark). I then went back to flashing the boot.img too (from an UL rom, unfortunately) and relocked the bootloader. Still the same error. Then I read I should factory reset in the bootloader. So I did and the result was I got stuck on the bootscreen!! So I unlocked it again, re-installed the TWRP recovery to at least get back to the backup I made before, but the thing is: My storage got wiped and TWRP won't mount OTG-USB!!! I guess it's that some partitions/files are now messed up. Now I cannot do anything anymore. I don't have the stock ROM as a flashable zip, only the TWRP backup.
Here's what still works:
Fastboot & Recovery
What doesn't work:
ADB (because phone won't boot), ExtSDcard (naturally!) and flashing ROMs via fastboot because I need one that matches that damn Vodafone CID
I think if someone could upload their Vodafone Germany M4 ROM as a zip or exe, I could manage it. If someone has it, PLEASE give it to me!
If someone has any other idea how to get this phone to work, or at least get TWRP to mount the USB-stick, please HELP!!! I'm totally at a loss :crying:

You can ADP from TWRP so all is not lost

apjashley said:
You can ADP from TWRP so all is not lost
Click to expand...
Click to collapse
Well, if I start ADB sideload in TWRP, it says it is starting but then nothing happens. Or does it take more than 5 minutes? Because cmd says no devices found :/

It doesn't have to be sideload. You could ADB any old ROM from any screen, and then install it. It would at least get you back on your feet.

apjashley said:
It doesn't have to be sideload. You could ADB any old ROM from any screen, and then install it. It would at least get you back on your feet.
Click to expand...
Click to collapse
Could you explain this? I go into TWRP while connected to the PC and then? When I type 'adb devices' it shows nothing, so I though I need to go into 'Adcanced > ADB sideload' in TWRP...

kumpelfred said:
Could you explain this? I go into TWRP while connected to the PC and then? When I type 'adb devices' it shows nothing, so I though I need to go into 'Adcanced > ADB sideload' in TWRP...
Click to expand...
Click to collapse
What does your Windows device manager show when you're in TWRP but not sideload mode?
I've been wrong before but I believe from sideload mode "adb push firmware.zip /sdcard/" should work as normal.

Hi, thanks for your reply.
The device manager lists it as HTC One Mini but with a yellow question mark. When I plug it in, it recognizes it and installs all the drivers with the exception of the MTP driver, and it won't let me manually install it. In fastboot, it is listed as "MyHTC".
When I go into adb sideload mode in TWRP it gets stuck on telling me it starts the service but nothing happens. "adb devices" remains empty in the cmd console.
As I said, I DO have a backup, only I cannot restore it as TWRP is unable to mount the USB-OTG. I simply cannot check the box (all other partitions data, system etc. work)! I tried 3 different sticks and TWRP versions 2.6.3, 2.7.1.0 & 2.7.1.1. On a friend's M7 TWRP loads that stick in a few seconds. ADB is not working as I said, otherwise I could simply push the file to the internal SD and see if I can restore it from there :/ I think it may have something to do with TWRP not being able to fix permissions, too (it tells me to boot the system once after factory reset, which I cannot do of course!) but I'm not sure....
What I have also tried is setting back the phone (relocked, stock recovery, cache erased) via rebootRUU and a Vodafone DE firmware zip but it tells me "read zipped android info fail" and aborts. Probably because I'm on a higher hboot version than the one in the firmware zip and I cannot go S-OFF without ADB working -.-
I'm struggling with this for 3 days now... Is there nothing I can do to get it booted into anything???

Duh! The Mini is back to life! Weirdly, when I uninstalled the HTC drivers and installed an older package, my device - in recovery mode - showed up under 'adb devices' and I pushed the whole TWRP backup to the sdcard, did a restore and there it is! The only thing that bothers me is that now the Windows device manager shows a yellow question mark on 'CDC Serial'. What does that mean? And why is my device not listed under 'adb devices' anymore after restoring? Very weird
But thanks again!!! Very happy now :good:

kumpelfred said:
Duh! The Mini is back to life! Weirdly, when I uninstalled the HTC drivers and installed an older package, my device - in recovery mode - showed up under 'adb devices' and I pushed the whole TWRP backup to the sdcard, did a restore and there it is! The only thing that bothers me is that now the Windows device manager shows a yellow question mark on 'CDC Serial'. What does that mean? And why is my device not listed under 'adb devices' anymore after restoring? Very weird
But thanks again!!! Very happy now :good:
Click to expand...
Click to collapse
could u share that drivers pls. i have same problem ((

[email protected] said:
could u share that drivers pls. i have same problem ((
Click to expand...
Click to collapse
Hey, I was wrong about the HTC drivers, this was not the issue. The issue was that the latest TWRP recovery (2.7.1.1) did not work in adb mode for whatever reasons. The solution was not older drivers (as they update anyway) but to install an older TWRP version (2.6.3.0 worked for me).
This is only when you cannot boot into your system and have to adb push something to your sdcard. If the phone is not recognized when connected with a booted system running, the only fix is to remove drivers and programs that could interfere (Samsung Kies, HTC Sync, e.g.), reboot, reinstall the drivers, plug your phone into a different USB port and just hope 'adb devices' gets a result, otherwise try all over again.

[Q] Device not found after wiping data (trying to flash CM)

Hi,
I am not sure if I can ask about upgrading to CM here? Today I tried to follow their guide from their wiki and now my I can't access anything but recovery, and adb won't work.
I installed the recovery using fastboot and unlocked the device. That worked.
After that, I wiped data/factory reset and the next stage is to push CM to my device, but the device isn't recognized by the PC (when I type adb devices no devices appear).
Now I don't have an os and cannot do anything outside of recovery. I tried clicking on mount USB storage but it doesn't open my storage on my computer. When I connect the device my computer makes sound that a USB is connected.
I tried to /mount data and pretty much everything.
Any ideas?
Sorry for bad English.

I assume you installed TWRP recovery. If yes,
click on MOUNT option,
check SYSTEM option,
disable MTP and then
Enable MTP
.. now you should be able to see the device in your computer. Copy the zip file and flash it through recovery.

schmos said:
I assume you installed TWRP recovery. If yes,
click on MOUNT option,
check SYSTEM option,
disable MTP and then
Enable MTP
.. now you should be able to see the device in your computer. Copy the zip file and flash it through recovery.
Click to expand...
Click to collapse
No, I have CW recovery (I thought I wrote that, sorry).

You need to get adb drivers sorted out, I believe there's a guide for it on General forum.

beekay201 said:
You need to get adb drivers sorted out, I believe there's a guide for it on General forum.
Click to expand...
Click to collapse
Are you talking about this? http://forum.xda-developers.com/showthread.php?t=2588979
Because if yes it didn't change anything. In bootloader my pc recognizes my phone as "Android" but I still can't do anything.

Mr Light said:
Are you talking about this? http://forum.xda-developers.com/showthread.php?t=2588979
Because if yes it didn't change anything. In bootloader my pc recognizes my phone as "Android" but I still can't do anything.
Click to expand...
Click to collapse
You previously wrote, and I quote, "I installed the recovery using fastboot and unlocked the device. That worked."
^ This means to me that the connection between your bootloader (fastboot client) and your computer (fastboot host/server) is working, from which we can assume drivers FOR FASTBOOT are correctly setup.
You previously wrote, and I quote, "but the device isn't recognized by the PC (when I type adb devices no devices appear)"
^ This means to me that the connection between adb (on the phone) and adb (on the pc) is not working.
Now, if you are in a custom recovery, hook up the usb to the pc, start adb server on the pc, and you still don't see your device sn appear on the output of 'adb devices', then it means that the drivers FOR ADB aren't setup correctly.
Running a tool and then coming back saying it didn't work... That's not helpful at all. How did it not work? What version of the tool did you use? 1.4.2? 1.3? Keep in mind that you need (more likely than not, since you're probably running latest recovery versions) updated adb and fastboot binaries to API 21 version (Android 5.0). v1.3 of that tool doesn't seem to support API 21 yet.
Learn how to ask for help, please. Also, read the entire first post of this thread please: http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
If you still can't get it to work, there's a thread to help out troubleshooting drivers stuff, check it out at http://forum.xda-developers.com/goo...nosing-usb-driver-adb-issues-windows-t2514396

Ok... Sorry for making you confused, it's not easy for me to communicate in English.
Anyway I managed to flash twrp which is much friendlier than CWM, and then I had access to my storage again. Thanks (solved).

[SOLVED] Unable to ADB Sideload

Hey guys, I may have completely stuffed this up, I got a 2nd hand Nexus 5 I was going to give to my mum. I was going to put the Chroma custom rom on it so firstly I unlock the bootloader and installed a 3.0 TWRP. After this is all done I was planning on using ADB sideload to install the custom rom, I wanted everything to be fresh and clean. So I wiped everything off it (including \system), after I done this, I realised I forgotten to enable USB debugging.
ADB works perfectly fine, so when I do ADB devices, I can see my device, I even double check that its set up correctly by using the Nexus Toolkit and ran the driver test. So when I tried to go and adb sideload chroma.zip, it says device error: no devices found. So I double check again by using adb devices and it says XXXXXXXXXXXX sideload. So its definitely there. So chances are, its because USB debugging is not enabled and this is screwing me over.
Anyone here is able to assist me with this? is there a way to enable USB debugging from TWRP (I tried to look for build.prop but that file is missing).
EDIT: Ohh, I forgot to mention that I got the latest Google drivers installed and the lastest SDK as well.

Z-Blade said:
Hey guys, I may have completely stuffed this up, I got a 2nd hand Nexus 5 I was going to give to my mum. I was going to put the Chroma custom rom on it so firstly I unlock the bootloader and installed a 3.0 TWRP. After this is all done I was planning on using ADB sideload to install the custom rom, I wanted everything to be fresh and clean. So I wiped everything off it (including \system), after I done this, I realised I forgotten to enable USB debugging.
ADB works perfectly fine, so when I do ADB devices, I can see my device, I even double check that its set up correctly by using the Nexus Toolkit and ran the driver test. So when I tried to go and adb sideload chroma.zip, it says device error: no devices found. So I double check again by using adb devices and it says XXXXXXXXXXXX sideload. So its definitely there. So chances are, its because USB debugging is not enabled and this is screwing me over.
Anyone here is able to assist me with this? is there a way to enable USB debugging from TWRP (I tried to look for build.prop but that file is missing).
EDIT: Ohh, I forgot to mention that I got the latest Google drivers installed and the lastest SDK as well.
Click to expand...
Click to collapse
usb debugging is automatically enabled while being into TWRP. I didn't try adb sideload with TWRP 3.0 so I can't confirm that the feature is working as it should be. Did you try with a previous version of TWRP? Did you enable adb sideload from TWRP before typing your command?

Primokorn said:
usb debugging is automatically enabled while being into TWRP. I didn't try adb sideload with TWRP 3.0 so I can't confirm that the feature is working as it should be. Did you try with a previous version of TWRP? Did you enable adb sideload from TWRP before typing your command?
Click to expand...
Click to collapse
Yes, I actually tried it with the previous version first due to the fact that 3.0 is new and may have bugs in it, but since that didn't work, I tried 3.0 afterwards. However, I was able to get MTP working while it was in Recovery. So I copied the files from my computer directly into the Nexus using MTP, for some reason, copying over the ROM and GApps took me over 13 hours to transfer. I didnt care how long it took at least it got it on there.
I was able to flash Chroma and GApps onto the phone so its now all good.

No OS... TWRP won't display files on otg/sd

I had a bit of a problem with CM and it kept saying trebuchet had stopped working. (This is after the phone had been running fine for a whole year with CM. Then the phone kept restarting and saying trebuchet had stopped working and it would constantly restart until it calmed down. I decided to install and alternative launcher but the problem didn't totally go.
Thereafter I decided to delete trebuchet from root and boom the phone never calmed down and kept restarting. Eventually I tried restoring factor settings and it says now that there's no OS.
I had TWRP installed before but now when I've tried to install the latest one, it doesn't show any files on the OTG. I've put twrp on the SD along with a rom as well but nothing shows at all.
Can someone help in simple terms?

emmpii said:
I had a bit of a problem with CM and it kept saying trebuchet had stopped working. (This is after the phone had been running fine for a whole year with CM. Then the phone kept restarting and saying trebuchet had stopped working and it would constantly restart until it calmed down. I decided to install and alternative launcher but the problem didn't totally go.
Thereafter I decided to delete trebuchet from root and boom the phone never calmed down and kept restarting. Eventually I tried restoring factor settings and it says now that there's no OS.
I had TWRP installed before but now when I've tried to install the latest one, it doesn't show any files on the OTG. I've put twrp on the SD along with a rom as well but nothing shows at all.
Can someone help in simple terms?
Click to expand...
Click to collapse
Use adb commands to flash TWRP (Put your TWRP image in the same folder on your pc as your adb and enter each command separately):
adb reboot bootloader
fastboot flash recovery twrp.img (latest version is 3.1.1-0-peregrine, remame it to twrp.img - if that doesn't work rename twrp to recovery.img and try that).
fastboot reboot
If that works, restore you last known good working backup or try re-installing your stock rom.

sdembiske said:
Use adb commands to flash TWRP (Put your TWRP image in the same folder on your pc as your adb and enter each command separately):
adb reboot bootloader
fastboot flash recovery twrp.img (latest version is 3.1.1-0-peregrine, remame it to twrp.img - if that doesn't work rename twrp to recovery.img and try that).
fastboot reboot
If that works, restore you last known good working backup or try re-installing your stock rom.
Click to expand...
Click to collapse
I've installed fastboot onto my PC. Now i'm trying the adb commands but my phone isn't showing up
Tried a new cable.. so far it's started to recognise. I'll update this if theres news.
*adb command doesn't work... says no devices. Fastboot seems to work

ive managed to get the latest twrp on.. now I cant seem to adb sideload the rom nor does it show via otg.. ADB sideload disconnects and says invalid zip file

emmpii said:
I've installed fastboot onto my PC. Now i'm trying the adb commands but my phone isn't showing up
Tried a new cable.. so far it's started to recognise. I'll update this if theres news.
*adb command doesn't work... says no devices. Fastboot seems to work
Click to expand...
Click to collapse
Install or re-install your Motorola Device Manager on your pc from this link: https://mobilesupport.lenovo.com/us/en/solution/MS88481
Check in your pc Device Manager to see if your device is connected and recognized properly when you plug in the USB cable.
In the folder where your adb and fastboot files are, open a command prompt and enter adb devices to see if the phone is recognized now in adb. If it is, proceed as suggested earlier.

sdembiske said:
Install or re-install your Motorola Device Manager on your pc from this link: https://mobilesupport.lenovo.com/us/en/solution/MS88481
Check in your pc Device Manager to see if your device is connected and recognized properly when you plug in the USB cable.
In the folder where your adb and fastboot files are, open a command prompt and enter adb devices to see if the phone is recognized now in adb. If it is, proceed as suggested earlier.
Click to expand...
Click to collapse
shows up in device manager as android usb device, Still not showing on adb

I managed to get the device to finally track on with adb. It tracks fine now. However I can't seem to flash a rom on regardless of whether its OTG or sideload...

emmpii said:
shows up in device manager as android usb device, Still not showing on adb
Click to expand...
Click to collapse
Go to this link (https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816) and download the correct untouched rom for your phone model and transfer it to your sd card or internal memory.
Then try this command: fastboot boot recovery.img or fastboot boot twrp.img
and follow the directions exactly in the op in that thread to flash the rom.

sdembiske said:
Try this command: fastboot boot recovery.img or fastboot boot twrp.img
Go to this link (https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816) and download the correct untouched rom for your phone model and transfer it to your sd card or internal memory.
Then try this command: fastboot boot recovery.img or fastboot boot twrp.img
and follow the directions exactly in the op in that thread to flash the rom.
Click to expand...
Click to collapse
Absolutely no idea how but I managed to get one of the CM roms sideloaded and even though when i chose to reboot it said no OS. I've got it going, however I've forgotten to put gapps on so I'll try that now. Later on I'll try sideload stock rom or something and see how that goes. Thanks for the help so far! :good:

emmpii said:
Absolutely no idea how but I managed to get one of the CM roms sideloaded and even though when i chose to reboot it said no OS. I've got it going, however I've forgotten to put gapps on so I'll try that now. Later on I'll try sideload stock rom or something and see how that goes. Thanks for the help so far! :good:
Click to expand...
Click to collapse
The problem with CM roms is they're not really being updated anymore - just one of the problems I have with a lot of custom roms besides the bugs, etc., etc.
If you're hell bent on a custom rom, I would check out this one: [ROM][OFFICIAL][Peregrine][7.X] LineageOS 14.1 at https://forum.xda-developers.com/moto-g/4g-development/rom-cyanogenmod-14-0-t3469103
Lineage is the new go-to from CM. I personally would go back to stock first, however, to ensure everything is restored properly before installing it.
It's being updated regularly currently.

I just had a old CM rom downloaded from before hence I went to that lol. I'm trying lineage for now but I've also downloads the stock ROM. Whatever will keep the phone going