I unlocked the bootloader successfully using my mac but now whenever i want to run adb devices it says "adb devices offline" please help!
Issue fixed by downloading newest version of adb and reauthorizing computer for adb privleges
Related
Hi, i install cannot turn on debbuging usb mode in my Defy 2.2 froyo movistar argentina.
Does anyone have any idea why? i turn on but when connecting to the PC no (!) icon shows.
Thanks!
btw, i belive is a device problem because before i install froyo work fine. And my drivers worked fine till i install froyo
Any idea? please help
Can you post the link/thread from where you downloaded the froyo ROM. Also ignore the ! icon, just check in ADB if debugging is working or not. Enable USB debugging in Settings and after plugging in the USB select "Charge Only" mode.
Open adb and type "adb devices"
if it shows one device, then you're all good.
PS: make sure you have Moto Driver v4.9 or above.
bikerabhinav said:
Can you post the link/thread from where you downloaded the froyo ROM. Also ignore the ! icon, just check in ADB if debugging is working or not. Enable USB debugging in Settings and after plugging in the USB select "Charge Only" mode.
Open adb and type "adb devices"
if it shows one device, then you're all good.
PS: make sure you have Moto Driver v4.9 or above.
Click to expand...
Click to collapse
Hi i'm using argentina movistar from http://and-developers.com/sbf:defy
I have tried what you 've told me and this is my cmd:
C:\Users\MaryPau\Documents\samsung\root>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
015F13B80600D025 device
C:\Users\MaryPau\Documents\samsung\root>adb shell
$ adb push Superuser.apk /sdcard/Superuser.apk
adb push Superuser.apk /sdcard/Superuser.apk
adb: permission denied
There's nothing wrong with USB debugging or your cell. It's just that you're using the wrong command syntax.
once you type "adb shell" you DO NOT have to type adb before every next command because you're already inside adb prompt.
Just write "push Xyz.apk /sdcard/Xyz.apk"
or
write this command when inside windows prompt , i.e when not inside "adb shell"
C:\>adb push xyz.apk /sdcard/xyz.apk
(notice it's C prompt)
Skip writing 'adb' before each command once you are inside adb shell
also, are you trying to root your Defy?
bikerabhinav said:
There's nothing wrong with USB debugging or your cell. It's just that you're using the wrong command syntax.
once you type "adb shell" you DO NOT have to type adb before every next command because you're already inside adb prompt.
Just write "push Xyz.apk /sdcard/Xyz.apk"
or
write this command when inside windows prompt , i.e when not inside "adb shell"
C:\>adb push xyz.apk /sdcard/xyz.apk
(notice it's C prompt)
Skip writing 'adb' before each command once you are inside adb shell
also, are you trying to root your Defy?
Click to expand...
Click to collapse
it worked tks a lotttttttttttttttttt
RSD Lite recognize my phone, but after connecting no other options in Phone....No portal, No mass storage...Nothing.... Can anyone help..
Whenever I try to flash TWRP to my phone it says "error: more than one device or emulator". Can someone help?
tyboxer13 said:
Whenever I try to flash TWRP to my phone it says "error: more than one device or emulator". Can someone help?
Click to expand...
Click to collapse
I'd guess it is some problem with the adb server. Close all cmd and open a new one. Navigate to your adb/fastboot folder and enter the following:
adb kill-server
adb start-server
adb usb
adb devices
If it starts up again and all is fine it should show your device after the last command.
Btw. why is everybody using an all in one toolkit instead of learning to work with adb fastboot properly and doing it the old fashioned way: reading all that's needed to know and start off step by step.
Sent from my HTC One_M8 using XDA Free mobile app
When in adb shell typing: adb devices, my device isn´t showing up. Am I missing something?
You can fix that by following this guideline: https://edwardsamuel.wordpress.com/...-found-with-nexus-5-devices-in-recovery-mode/
Basically the steps are the same.
I was reading through the methods of rooting and just figured out none of them works for me.
I can't seem to make my phone visible in adb while in the bootloader. No commands work because of this and when I do adb shell getprop, I see that ro.debuggable is 0.
How can I root my phone when I can't see it in the bootloader?
You mean you executed the command ”fastboot devices” and got nothing? Then you should probably chech if the adb driver is installed properly. Sometimes it gets little tricky during the driver installation.
I am using linux, when my device is booted, adb or fastboot devices returns it. When I'm on the bootloader, they don't show my device. That's the problem.
So, when entering "fastboot devices" when phone is in Download Mode, nothing.
When trying "fastboot oem get_identifier_token", it says waiting for devices.
Also, got this new error by "adb devices":
adb server version (31) doesn't match this client (39); killing...
error: could not install *smartsocket* listener: cannot bind to 127.0.0.1:5037: Only one usage of each socket address (protocol/network address/port) is normally permitted. (10048)
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
could not read ok from ADB Server
* failed to start daemon *
error: cannot connect to daemon
If you guys need anything else, just ask.
Thanks
You need to update your adb version on your computer.
Re: The thingy
BlockOfDynamite said:
You need to update your adb version on your computer.
Click to expand...
Click to collapse
For the ADB problem or both?
Probably both. The best thing you can do is to download the latest adb and go from there. If it fixes it, great, if it doesn't, then the problem can be diagnosed further.
BlockOfDynamite said:
Probably both. The best thing you can do is to download the latest adb and go from there. If it fixes it, great, if it doesn't, then the problem can be diagnosed further.
Click to expand...
Click to collapse
Got the latest adb from Google Platform Tools and the latest fastboot from the HTC dev instructions.
ADB works sometimes, but fastboot does nothing.
absp2006 said:
Got the latest adb from Google Platform Tools and the latest fastboot from the HTC dev instructions.
ADB works sometimes, but fastboot does nothing.
Click to expand...
Click to collapse
Reboot to bootloader using adb reboot-bootloader. Then try fastboot commands.
Everybody!!!
It turns out that by updating the drivers while the phone is in download mode got fastboot to work!!!