Skip to main content
edited tags; edited title
Link
Matthew Read
  • 50.7k
  • 30
  • 146
  • 273

Fastboot detects ADB does not detect my device but not adbwhile in Recovery Mode

Post Reopened by bmdixon, Matthew Read
added 141 characters in body
Source Link

I have a Moto G (Falcon-xt 1033).

Recently I successfully flashed cm 13 nighly on my device, everything worked fine, used the phone a little while, then flashed supersu and device went into a boot loop.

I had removed rom zip files from device storage, so I am trying to push rom zip into my device via adb. But the adb does not detect my device(nor does my laptop- running ubuntu 14.04). I tried a bunch of things from from trying all ports to updating adb version to creating 51-android.rules file under etc/udev/rules.d/ The recovery my device used is cwm.

I just cannot find a solutionwant to access the storage drive of my device either by adb or by any alternative to push the rom .zip and other files. How exactly can I go about solving this problem.

PLEASE HELP!

I have a Moto G (Falcon-xt 1033).

Recently I successfully flashed cm 13 nighly on my device, everything worked fine, used the phone a little while, then flashed supersu and device went into a boot loop.

I had removed rom zip files from device storage, so I am trying to push rom zip into my device via adb. But the adb does not detect my device(nor does my laptop- running ubuntu 14.04). I tried a bunch of things from from trying all ports to updating adb version to creating 51-android.rules file under etc/udev/rules.d/ The recovery my device used is cwm.

I just cannot find a solution.

PLEASE HELP!

I have a Moto G (Falcon-xt 1033).

Recently I successfully flashed cm 13 nighly on my device, everything worked fine, used the phone a little while, then flashed supersu and device went into a boot loop.

I had removed rom zip files from device storage, so I am trying to push rom zip into my device via adb. But the adb does not detect my device(nor does my laptop- running ubuntu 14.04). I tried a bunch of things from from trying all ports to updating adb version to creating 51-android.rules file under etc/udev/rules.d/ The recovery my device used is cwm.

I want to access the storage drive of my device either by adb or by any alternative to push the rom .zip and other files. How exactly can I go about solving this problem.

PLEASE HELP!

added 37 characters in body
Source Link

I have a Moto G (Falcon-xt 1033).

Recently I successfully flashed cm 13 nighly on my device, everything worked fine, used the phone a little while, then flashed supersu and device went into a boot loop.

I had removed rom zip files from device storage, so I am trying to push rom zip into my device via adb. But the adb does not detect my device(nor does my laptop- running ubuntu 14.04). I tried a bunch of things from from trying all ports to updating adb version to creating 51-android.rules file under etc/udev/rules.d/ The recovery my device used is cwm.

I just cannot find a solution.

PLEASE HELP!

I have a Moto G (Falcon-xt 1033).

Recently I successfully flashed cm 13 nighly on my device, everything worked fine, used the phone a little while, then flashed supersu and device went into a boot loop.

I had removed rom zip files from device storage, so I am trying to push rom zip into my device via adb. But the adb does not detect my device(nor does my laptop- running ubuntu 14.04). I tried a bunch of things from from trying all ports to updating adb version to creating 51-android.rules file under etc/udev/rules.d/

I just cannot find a solution.

PLEASE HELP!

I have a Moto G (Falcon-xt 1033).

Recently I successfully flashed cm 13 nighly on my device, everything worked fine, used the phone a little while, then flashed supersu and device went into a boot loop.

I had removed rom zip files from device storage, so I am trying to push rom zip into my device via adb. But the adb does not detect my device(nor does my laptop- running ubuntu 14.04). I tried a bunch of things from from trying all ports to updating adb version to creating 51-android.rules file under etc/udev/rules.d/ The recovery my device used is cwm.

I just cannot find a solution.

PLEASE HELP!

Post Closed as "Needs details or clarity" by Matthew Read
Source Link
Loading