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..
Hi guys,
After a lot of trouble (I will not mention them but it was a long pain for me and my desire!) I've finally unbricked my phone BUT usb doesn't work anymore.
I learn that it's called usb-brick.
Sadly, Exhausted from this fight with my device, I've mistakenly installed RUU from htc with gingerbread. And with the new bootloader 1.02.0001.
Problem: I have not find any method to root the phone without the need of usb link with the installed rom.
I hoped to do it when I read about Gingerbreak but infortunatly, it doesn't work with htc version of GB.
Moreover, because the exploit of revolutionary is not known I can not exploit it directly on the phone.
So, I need root for usb unbrick, but I need usb for having root :'(
Is there a way to root my device without needing this usb link?
(Of course, I can access fastboot usb.)
Have anyone an idea?
I know, it's a tricky question... But I have really no idea what to do...
Thanks,
Dvad'
My problem is solved if I can become s-off.
Do I really need a rom with usb connection working in order to S-off my devices?
Fastboot via USB isn't enough? I tried with revolutionary says "waiting for device" forever.
Try following bortak's Troubleshooting Guide
http://forum.xda-developers.com/showthread.php?t=1275632
ROOT WITHOUT USB CONNECTION
Thank for answering.
I read this method but, it works on froyo build only. And I've gingerbread.
davmoi said:
Thank for answering.
I read this method but, it works on froyo build only. And I've gingerbread.
Click to expand...
Click to collapse
Do this:
-extract this on ur computer (its a "portable" version of adb)
-install this widget from the market, it allow to use adb over wifi (without cable)
-try this local root exploit by revolutionary (its work even on 2.3)
after u get temp root, use the flash_image method to flash the misc partition (as for every guide for usb brick fix)
EDIT: Sorry the widget on the market requires root to work..hmm
send it to htc repair, tell they after the upgrade with their 2.3.3 ruu, ur usb stopped working..maybe u get free repair under warranty
My problem is solved!
In fact andQlimax were right! The idea is to run adb with a wifi connection.
Wifi over adb needs root. I don't understand why because this method doesn't need root:
1° Type this In android terminal. it configure the phone to run adb over tcp.
setprop service.adb.tcp.port 5555
stop adbd
start adbd
Click to expand...
Click to collapse
2°Connect your htc on a wifi network
3° on the pc run:
adb tcpip 5555
adb connect ip-of-the-phone-on-your-wifi-network:5555
Click to expand...
Click to collapse
You can access adb shell, have Temp root with zergRush, and flash your mtd0.img.
Problem solved!
davmoi said:
My problem is solved!
In fact andQlimax were right! The idea is to run adb with a wifi connection.
Wifi over adb needs root. I don't understand why because this method doesn't need root:
1° Type this In android terminal. it configure the phone to run adb over tcp.
2°Connect your htc on a wifi network
3° on the pc run:
You can access adb shell, have Temp root with zergRush, and flash your mtd0.img.
Problem solved!
Click to expand...
Click to collapse
Then u just did that and solved? Cool
I shall bookmark this for future reference
I've got this exact problem, but I can't get the WiFi ADB to work. I've got the official Gingerbread RUU installed and the USB is dead outside of fastboot. The terminal on the phone accepts the commands without issue and connecting to WiFi is fine, but my PC just won't find it for some reason. Ideas? I don't fancy an out-of-warranty repair.
seekified said:
I've got this exact problem, but I can't get the WiFi ADB to work. I've got the official Gingerbread RUU installed and the USB is dead outside of fastboot. The terminal on the phone accepts the commands without issue and connecting to WiFi is fine, but my PC just won't find it for some reason. Ideas? I don't fancy an out-of-warranty repair.
Click to expand...
Click to collapse
any firewall/antivirus blocking the port 5555?
what the result of "adb devices" from ur computer after the above procedure?
andQlimax said:
any firewall/antivirus blocking the port 5555?
what the result of "adb devices" from ur computer after the above procedure?
Click to expand...
Click to collapse
Nope, nothing like that is even installed on my PC at the moment. adb devices gives me "List of devices attached" and then an empty line. Is the terminal on the phone meant to return anything when you enter above commands? For me, it simply goes to an empty line when enter the command and doesn't state whether or not is was successful.
seekified said:
Nope, nothing like that is even installed on my PC at the moment. adb devices gives me "List of devices attached" and then an empty line. Is the terminal on the phone meant to return anything when you enter above commands? For me, it simply goes to an empty line when enter the command and doesn't state whether or not is was successful.
Click to expand...
Click to collapse
well, after searching this on internet seems that to be able to do this:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
you need root...so I don't know how the previous user, davmoi, managed to do that..
so in my opinion there is no way to use adb over wifi without root..and there is no way to root the desire with gb 2.3.3 without adb..and without root there is no way to restore usb brick..
call htc and say they that after the 2.3.3 update ur usb is gone..(as u was just flashing their ruu, u should get repair under warranty)
andQlimax said:
well, after searching this on internet seems that to be able to do this:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
you need root...so I don't know how the previous user, davmoi, managed to do that..
so in my opinion there is no way to use adb over wifi without root..and there is no way to root the desire with gb 2.3.3 without adb..and without root there is no way to restore usb brick..
call htc and say they that after the 2.3.3 update ur usb is gone..(as u was just flashing their ruu, u should get repair under warranty)
Click to expand...
Click to collapse
Pretty much what I figured.
I've spoken to HTC and apparently they consider use of the 2.3.3 update to void the warranty as they've put up several warnings and such on the website... which is pretty crap. I'm guessing it won't be too much work for them to just re-flash it though. As long as I can make this phone last until MSM8960 chips hit the market, I'm happy. Never using Amon Ra again though.
Cant enable adb-WIFI connection. List of devices is empty. Think u need root
Need solution without root!
I have no bill (EBay..) to send it to HTC.
Strange, I swear I was not rooted when I used these command lines. (Superuser and titanium was saying that.And it was on a stock 2.3 rom so....
I simply enter them in Android terminal emulator with a user shell.
Can you ping your phone on your wifi network from your computer?
Dvad'
Edit: I think that if we needed root the phone would say "operation not permitted" when you enter the command. The problem seems to be elsewhere.
davmoi said:
Strange, I swear I was not rooted when I used these command lines. (Superuser and titanium was saying that.And it was on a stock 2.3 rom so....
I simply enter them in Android terminal emulator with a user shell.
Can you ping your phone on your wifi network from your computer?
Dvad'
Click to expand...
Click to collapse
ur phone was rooted, that commands requires root permission
Maybe, but in that case, I was able to root a completly stock Gingerbread RUU without adb... And without knowing it!
:/
And if it is the case I can not say how, because I have done a lot of tries with my phone, and I don't remember all of them..
davmoi said:
Maybe, but in that case, I was able to root a completly stock Gingerbread RUU without adb... And without knowing it!
:/
And if it is the case I can not say how, because I have done a lot of tries with my phone, and I don't remember all of them..
Click to expand...
Click to collapse
out of curiosity ur phone was s-offed when u run the 2.3 ruu?
No... it was not soff anymore. Hboot version was stock 1.02
Sent from my HTC Desire using Tapatalk
I could establish wifi connection on GB 2.3.3, HBoot 1.02, not rootet and s-on as described! ADB Shell worked fine. But: when I try to launch command "flash_image mtd0.img" the permission is denied! In ADB Shell on PC I have the "#" instead of the "$". On phone in Terminal Emulator I have only "$"!
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
I recently updated to Android 5.0.1 on my M8 GPe and it seems to work just fine. Today I wanted to flash a custom recovery but I couldn't get any connection between the phone and the computer. When I enter fastboot I don't get "fastboot usb" as I usually do.
Do I need new drivers or something? I have both Windows 7 and OS X 10.10 so a solution for either is ok.
djr83 said:
I recently updated to Android 5.0.1 on my M8 GPe and it seems to work just fine. Today I wanted to flash a custom recovery but I couldn't get any connection between the phone and the computer. When I enter fastboot I don't get "fastboot usb" as I usually do.
Do I need new drivers or something? I have both Windows 7 and OS X 10.10 so a solution for either is ok.
Click to expand...
Click to collapse
I was also unable to get fastboot working.
For custom recovery I used adb shell and used the dd cmd, worked fine
Heisenberg420 said:
I was also unable to get fastboot working.
For custom recovery I used adb shell and used the dd cmd, worked fine
Click to expand...
Click to collapse
I don't think I get any connection with adb either? But I'll try that. What command should I use to flash the recovery image in adb?
Edit: adb devices shows an empty list.
djr83 said:
I don't think I get any connection with adb either? But I'll try that. What command should I use to flash the recovery image in adb?
Edit: adb devices shows an empty list.
Click to expand...
Click to collapse
Connect via USB
To see if you have a connection type
Adb devices
U should see a device
Then follow these directions
http://www.teamw.in/project/twrp2/225
You should copy and paste the dd cmd directly into terminal, if you typo that one u may brick ur device
Heisenberg420 said:
Connect via USB
To see if you have a connection type
Adb devices
U should see a device
Then follow these directions
http://www.teamw.in/project/twrp2/225
You should copy and paste the dd cmd directly into terminal, if you typo that one u may brick ur device
Click to expand...
Click to collapse
Exactly, I'm not getting any devices.
djr83 said:
Exactly, I'm not getting any devices.
Click to expand...
Click to collapse
Have u enabled USB debugging in developer options?
Heisenberg420 said:
Have u enabled USB debugging in developer options?
Click to expand...
Click to collapse
Yes. And nothing has changed on the computer since before I updated to 5.0.1.
Edit: Tried another USB port on the computer and it's working now.
djr83 said:
Yes. And nothing has changed on the computer since before I updated to 5.0.1.
Click to expand...
Click to collapse
I'd say its the drivers. Try to reinstall
You can try adb over WiFi without the drivers, download an adb wireless app from the market, enable it, get the IP address of your phone in the app, then connect through adb
Adb connect <IP[emoji14]ORT HERE>
then try adb devices
I am running lineageOS on a rooted firestick. I am using ADB on the Firestick to control it via Homeassistant. The problem is that the adb debugging does not automatically work on reboot. Everytime i reboot i have to manually go to the menu turn off the ADB debugging and then turn in back on. After doing this i am able to reconnect adb via network (i.e, on homeassistant).
I want to ask is there any way i can use a script to automatically do this on restart of firestick. I have tried creating a script in init.d with the following contents but it doesn't seem to work.
adb tcpip 5555
I have added the following line to build.prop but this doesn't seem to work too
service.adb.tcp.port=5555
On restart the adb debugging is on in the developer tools but somehow it doesn't connect (either to Homeassistant or to my laptop), what seems to make it work is toggling it off and then back on.
Have you tried persist, so that the setting sticks between reboots?
Code:
ADB shell setprop persist.adb.tcp.port 5555
Just tried it. Still not working after reboot.
I there any command i can use to toggle the adb debugging via a startup script or crontab?
symbiansucks said:
Just tried it. Still not working after reboot.
I there any command i can use to toggle the adb debugging via a startup script or crontab?
Click to expand...
Click to collapse
Be sure you are running the above command as root user. Type su at the shell prompt, then type whoami to confirm you are root.
I guess you could make a script to run the following on each boot if the above doesn't work:
Code:
settings put global adb_enabled 1
setprop service.adb.tcp.port 5555
stop adbd
start adbd
exit 0
But I don't think this should be necessary.
Finnzz said:
Be sure you are running the above command as root user. Type su at the shell prompt, then type whoami to confirm you are root.
I guess you could make a script to run the following on each boot if the above doesn't work:
Code:
settings put global adb_enabled 1
setprop service.adb.tcp.port 5555
stop adbd
start adbd
exit 0
But I don't think this should be necessary.
Click to expand...
Click to collapse
Thanks. yes the command was run as root. Can i ask you one more thing, whats the best place to put the startup scripts in? I have tried init.d/ directory but the scripts don't get loaded from there i believe?
I have set permissions to chmod 755 for the script.
You can follow this guide,
Android (LineageOS 16) Execute Script on Start Up | sqall's blog
but it seems like there should be a much easier way to make ADB tcpip persist between reboots. I don't want to steer you wrong. @Sus_i would know better, he uses your build of LineageOS, and may have a cleaner solution.