Related
Can u belive it ... i just got done doing a 2.1 ruu and reroot to try to fix a problem with not being able to get adb with certain roms including zens .9.6 builds ..kangslayer..newest buffed.. SO i figured let me ruu to take care of this ...WRONG...... I only can get adb from zen.9.5 and < fresh 2.12< does anybody have any input..YES DEBUGGING is enabled
Not having any issues with adb using stock or darch.
Can you run adb shell?
no that is the problem
Error device not recgonized
Trouble shooting would say to check you hardware first:
Comp usb port
Usb cable (broken bent or missing pins or torn wires)
Phone usb port
But sense you can access adb shell on other roms its not any of those.
Soo next up would be to check the roms them selves.
Maybe redownload the roms and do a full wipe before flashing ( don't forget to back up)
And see I'd the problem persists
thanks for the input but i have stressed all those options... I might be ebaying the hero earlier than expected... This is a asurion issued phone..my orginal was stolen 2 months ago
Sorry about the theft.
It'd be a shame if you sold your phone and there was a simple fix ):
Hmmm...
Do you have the sdk located in c?
What recovery are you running?
I think i'm having the same issue, but it could just be that i am very novice with the command line in general. I haven't tried to push anything through adb since i did the initial root a few months back. Now if i type in "adb shell" at the C:\ i get the error "adb is not recognized as an internal or external command, operable progam or batch file" What am i missing? Fresh 2.1.2
Okay
Your suppose to be in C:\android-sdk-windows\tools\
Just cd to the above mentioned
Thank you. That was quick and easy.
Your very welcome.
Enjoy the awesomeness that is adb shell
well u can enjoy the shell but i cant.... Im gonna wait for flips to release a new version of toast or fresh...then ill determine what im gonna do
now im thinking that this is only a problem with overclocked kernals....
To my knowledge dd2.7 is oc'd and and works with it fine on my end. Do you have the HTC drivers installed?
damiandarkwater said:
To my knowledge dd2.7 is oc'd and and works with it fine on my end. Do you have the HTC drivers installed?
Click to expand...
Click to collapse
Yes again because everything works with other roms..i think there is a problem on my end with the phones hardware and the OC kernals..
Try these commands:
adb kill-server
adb start-server
adb devices
See if your device shows up.
mickdubs said:
well u can enjoy the shell but i cant.... Im gonna wait for flips to release a new version of toast or fresh...then ill determine what im gonna do
Click to expand...
Click to collapse
I'm having the same problem. I believe (a somewhat educated guess), the boot process is locking before the adb software on the phone is loaded. if someone can help to get a console output on the screen during boot rather than the green/white htc screen would help.
tkirton said:
Try these commands:
adb kill-server
adb start-server
adb devices
See if your device shows up.
Click to expand...
Click to collapse
Yes i have tried that with no luck...
Somewhere in the boot process adb is lost like this was said above.
Im just keeping my fingers crossed for adb with the newsest fresh that should be released shortly
so i just flashed the newest (old) version of damage control. NON OC kernal and i got adb access.. So im convinced that this phone is a lemon becuase it was asurion issued and i loose adb with OC kernals. I did have OC kernals running fine on my previous hero that was stolen.
**UPDATE 3:34AM
so after testing out dc.. i tried to flash the newest OC kernal made for DC. Right after flash i lost adb...
Why is the phone loosing ADB on OC KERNALS.. Where phones patched!?
damiandarkwater said:
Your very welcome.
Enjoy the awesomeness that is adb shell
Click to expand...
Click to collapse
Orrrr. You can download and install Regaw's toolbox and it'll make it so you can run abd commands from ANY directory in command box... pretty sweet
But yes, otherwise you need to be in the c:\android-sdk-windows\tools\ folder to run adb commands (or where ever you saved the sdk at)
Am I the only one having issues with adb?
I managed to get it working once yesterday night. adb logcat output was very helpful to fix the FC 'parameters' issue with libcamera under Eclair but I couldn't get it working after that. Also, when it did work, I couldn't get /system to remount rw.
I had to manually start adbd on the vogue but after I rebooted to test the new libcamera libs, I couldn't get it to work anymore, even after restarting adbd. I can see a HTC Android device in /proc/bus/usb/devices on my linux dev computer but 'adb devices' doesn't show any devices.
This was under VaniljEclair RLS6.
I did a quick search in 'Touch CDMA Android Dev' and 'Tilt Android Dev' forums, also search in google but couldn't find any quick answer.
I don't have much time (as everybody I guess) to mess with Android Dev so I would much rather spend the little time I have on something productive instead of searching for answers that somebody else might already have.
I don't mind switching to another Eclair ROM/build if I have to but I would appreciate if anybody could give me a few pointers to get adb working under eclair.
Thanks.
dlepage said:
Am I the only one having issues with adb?
I managed to get it working once yesterday night. adb logcat output was very helpful to fix the FC 'parameters' issue with libcamera under Eclair but I couldn't get it working after that. Also, when it did work, I couldn't get /system to remount rw.
I had to manually start adbd on the vogue but after I rebooted to test the new libcamera libs, I couldn't get it to work anymore, even after restarting adbd. I can see a HTC Android device in /proc/bus/usb/devices on my linux dev computer but 'adb devices' doesn't show any devices.
This was under VaniljEclair RLS6.
I did a quick search in 'Touch CDMA Android Dev' and 'Tilt Android Dev' forums, also search in google but couldn't find any quick answer.
I don't have much time (as everybody I guess) to mess with Android Dev so I would much rather spend the little time I have on something productive instead of searching for answers that somebody else might already have.
I don't mind switching to another Eclair ROM/build if I have to but I would appreciate if anybody could give me a few pointers to get adb working under eclair.
Thanks.
Click to expand...
Click to collapse
Are you using the Latest Kernel? Adb is supposed to be fixed with eclair a kernel or 2 ago. If so, Im no sure what the probem is.
Are you running windows, ubuntu ect...?
The adb problem is in the build itelf. As soon as I installed my adb quit working I went back to incubus build but it just gets really quirky after a while. I use Vanilj eclair for speed but really miss adb. And yes I am using the latest kernel I also tried troubleshooting by flashing other nbh files to no avail
incubus26jc said:
Are you using the Latest Kernel? Adb is supposed to be fixed with eclair a kernel or 2 ago. If so, Im no sure what the probem is.
Are you running windows, ubuntu ect...?
Click to expand...
Click to collapse
Eum, I'll have to check for the kernel version. It is the one included with KK VaniljEclair RLS6. The date of zImage is 24/06/2010. What was the issue again, /dev major/minor conflict between adb and 3d hardware? Is there a way to check if this is the issue from within my phone (with terminal)?
I am running Fedora Core 13 as a VirtualBox guest hosted on Windows 7 x64. As I can see a HTC Android device in /proc/bus/usb/devices in linux, I would say that VirtualBox usb passthru is not the issue but then again, I could be wrong.
Before I setup VirtualBox usb passthru, I was also having issues under Windows: it installed a few drivers but I still couldn't see the phone as Mass Storage under Windows. Is there a way to install Android Windows driver without installing the Android SDK under Windows? Since Windows is not supported for AOSP dev, I'd prefer to keep my Windows 'Android free' as far as SDK,tools, etc goes except for 'Mass Storage' access.
Hope I am making sense... As I said, all this Android business is new to me, I am probably forgetting something trivial in my setup.
Yes it is a issue in /dev with 3d hardware. You can flash latest nbh without reinstalling all system so i think that you go faster in this way.
dlepage said:
Eum, I'll have to check for the kernel version. It is the one included with KK VaniljEclair RLS6. The date of zImage is 24/06/2010. What was the issue again, /dev major/minor conflict between adb and 3d hardware? Is there a way to check if this is the issue from within my phone (with terminal)?
I am running Fedora Core 13 as a VirtualBox guest hosted on Windows 7 x64. As I can see a HTC Android device in /proc/bus/usb/devices in linux, I would say that VirtualBox usb passthru is not the issue but then again, I could be wrong.
Before I setup VirtualBox usb passthru, I was also having issues under Windows: it installed a few drivers but I still couldn't see the phone as Mass Storage under Windows. Is there a way to install Android Windows driver without installing the Android SDK under Windows? Since Windows is not supported for AOSP dev, I'd prefer to keep my Windows 'Android free' as far as SDK,tools, etc goes except for 'Mass Storage' access.
Hope I am making sense... As I said, all this Android business is new to me, I am probably forgetting something trivial in my setup.
Click to expand...
Click to collapse
There is a makedev script in the initrd.gz that differs between the initrd.gz originally included with the haretinstall.zip and the one I use. I use the initrd.gz that dzo shared here: http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
But first try the latest zImage from that site. If it still fails, try using the initrd.gz from this zip-file: http://sourceforge.net/projects/androidhtc/files/2010-02-20/haretinstall.zip/download
kallt_kaffe said:
There is a makedev script in the initrd.gz that differs between the initrd.gz originally included with the haretinstall.zip and the one I use. I use the initrd.gz that dzo shared here: http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
But first try the latest zImage from that site. If it still fails, try using the initrd.gz from this zip-file: http://sourceforge.net/projects/androidhtc/files/2010-02-20/haretinstall.zip/download
Click to expand...
Click to collapse
Did some more test.
adbd is not running under Android (VaniljEclair RLS6). Using Terminal emulator, I manually start adbd on the phone. Then, I connect the USB cable. From this point adb works from linux. Is it normal that adbd is not running after a fresh boot of the phone?
This is using the zImage and initrd from your androidinstall.tar, as far as I can see by the dates and files size. I am running from the sdcard, in case it matters.
No sweat though, I now have a work around so it is no big deal.
dlepage said:
Did some more test.
adbd is not running under Android (VaniljEclair RLS6). Using Terminal emulator, I manually start adbd on the phone. Then, I connect the USB cable. From this point adb works from linux. Is it normal that adbd is not running after a fresh boot of the phone?
This is using the zImage and initrd from your androidinstall.tar, as far as I can see by the dates and files size. I am running from the sdcard, in case it matters.
No sweat though, I now have a work around so it is no big deal.
Click to expand...
Click to collapse
Strange, this should be controlled by this in sysinit.rc:
Code:
# adbd is controlled by the persist.service.adb.enable system property
service adbd /sbin/adbd
disabled
# adbd on at boot in emulator
on property:ro.kernel.qemu=1
start adbd
on property:persist.service.adb.enable=1
start adbd
on property:persist.service.adb.enable=0
stop adbd
And the persist.service.adb.enable property should be enabled by default.
i don't want to put root on my vibrant. i previously had a nexus one and all i had to do was plug it in and turn on debugging mode and i could test out my apps and debug them just fine.
with the vibrant I get the following error when trying to debug apps:
[2010-07-25 21:40:58 - ApiDemos] Failed to upload ApiDemos.apk on device 'T959xxxxxxxxxxx'
[2010-07-25 21:40:58 - ApiDemos] java.io.IOException: Unable to upload file: timeout
Is adb push disabled?
edit: my bad. i didn't sign with a debug certificate.
so adb install works, but for some reason the eclipse says failed to upload when you try to use the 'run' or 'debug' build in eclipse. any ideas?
it looks like eclipse will do the run/debug fine after manually installing with adb install on the command line. that's a little annoying, but a reasonable workaround. i wish i knew the root cause though...
I thought I was the only one having this problem! But it looks like it's the vibrant, not me or eclipse. Has anyone been able to find a fix for this issue? I've tried different versions of eclipse and java but no luck. So far my experience with the vibrant as a developer has been really ****ty. Especially since my mac (my main computer) doesn't recognize it in any way. If anyone has some sort of solution to this that would be great
So I have to say that I cannot get my Vibrant to work either. Of course I can't seem to get the emulator working also. So far I am dead in the water on Android development. Sucks.
I've been deving just fine on my vibrant no issues whatsoever. the only problem i had was that adb didn't detect the vibrant at all till i updated my sdk, are you guys using the latest adb?
i can run and debug just fine from eclipse, just the same as it works on my g1. i tried it on both windows and linux.....
Freedomcaller said:
I've been deving just fine on my vibrant no issues whatsoever. the only problem i had was that adb didn't detect the vibrant at all till i updated my sdk, are you guys using the latest adb?
i can run and debug just fine from eclipse, just the same as it works on my g1. i tried it on both windows and linux.....
Click to expand...
Click to collapse
Yea I've been using my vibrant as my development phone without a problem. Just make sure you have the correct adb drivers. I found them online somewhere
Netbeans sends apks to my Vibrant fine, even before I was rooted. In fact, I can ONLY get Netbeans to send to the Vibrant... it completely ignores the Emulator if the Vibrant is plugged in w/USB Debugging on.
Might be something with Eclipse. I've had tons of problems with it.
Eclipse has been working perfectly for me on my Vibrant...
RE: Possible New Rooting Method!
can't post to thecubed's original thread on the development subforum (not enough posts)....
http://forum.xda-developers.com/showthread.php?t=1127223
received replacement phone yesterday (had usb issues). it did not yet have the update installed....was still running V4. performed these steps...
1. installed verizon usb drivers
2. obtained adb access (needed to toggle usb debugging--device originally showed as offline)
3. verified # (see thecubed's post)
4. adb push su /system/bin/su
5. adb shell
6. # mount -o remount,rw -t ext3 /dev/mmcblk0p12 /system
7. # chmod 6755 /system/bin/su
8. verified correct permission on su
9. # reboot
10. downloaded superuser from market
easy as pie....no exploit required!
Only workrd on v4 though? Not v6?
i unfortunately did not attempt it on my original phone....only the new (v4) one.
I tried it on a version 6 phone and it does not work.
Ahh shucks....
Sent from my VS910 4G using xda premium
Help!
Hi all -I have been up all night , I will admit I am new at this , and I have been reading and researching on this forum for a bit now -but I need a hand if anybody is interested in helping....I am mid-trying to root my LG revolution , V6.....I have gotten into a few different steps/methods and I think they are correct for the most part - but I am a little hazy about a few things.... I installed android-sdk-windows , then opened up the .exe SDK manager, and installed some revisions? Then went into cmd and did a few steps theads- I did the shortcut posted on this thread - and then tried the longer version and now I am stuck in the middle of both! LOL
mikeymax said:
Hi all -I have been up all night , I will admit I am new at this , and I have been reading and researching on this forum for a bit now -but I need a hand if anybody is interested in helping....I am mid-trying to root my LG revolution , V6.....I have gotten into a few different steps/methods and I think they are correct for the most part - but I am a little hazy about a few things.... I installed android-sdk-windows , then opened up the .exe SDK manager, and installed some revisions? Then went into cmd and did a few steps theads- I did the shortcut posted on this thread - and then tried the longer version and now I am stuck in the middle of both! LOL
Click to expand...
Click to collapse
You cannot root your v6 phone at this time. You will have to down grade the phone to v4 then root it. Every attempt to root the v6 with the v4 methods results in "permissions denied"
v6 fixed the exploit used to allow root.
?????????? insufficient permissions.
this is the message you get in linux when adb and fastboot have trouble detecting your device. im no guru. so you will have to bear with me. this procedure will work on most devices. and most debian or ubuntu based distros. but i am giving it for detecting htc vivid setup on ubuntu 10.10
after u recieve the error in terminal type in command (lsusb)
the terminal will spit out vendor id's for all usb devices attatched. on the vivid it is 0bb4:0cbb
then you need to create a new file (sudo gedit /etc/udev/rules.d/51-android.rules)
your vendor id is added to that file (SUBSYSTEMS==”usb”, ATTRS{idVendor}==”0bb4″, ATTRS{idProduct}==”0c01″, MODE=”0666″) save and exit
fix permissions to the file just in case (chmod a+r /etc/udev/rules.d/51-android.rules) i found i needed this.
then kill the adb server (./adb kill-server)
have at it again and you should be all good. (./adb devices) should show up now.
like i said im not hardcore. it took me some serious googling to get over this hump for me. i was wondering if this should be stickied so linux users with this issue can get passed it quickly. this is the first device i have owned that my ubuntu box didnt natively detect.
drwario said:
?????????? insufficient permissions.
this is the message you get in linux when adb and fastboot have trouble detecting your device. im no guru. so you will have to bear with me. this procedure will work on most devices. and most debian or ubuntu based distros. but i am giving it for detecting htc vivid setup on ubuntu 10.10
after u recieve the error in terminal type in command (lsusb)
the terminal will spit out vendor id's for all usb devices attatched. on the vivid it is 0bb4:0cbb
then you need to create a new file (sudo gedit /etc/udev/rules.d/51-android.rules)
your vendor id is added to that file (SUBSYSTEMS==”usb”, ATTRS{idVendor}==”0bb4″, ATTRS{idProduct}==”0c01″, MODE=”0666″) save and exit
fix permissions to the file just in case (chmod a+r /etc/udev/rules.d/51-android.rules) i found i needed this.
then kill the adb server (./adb kill-server)
have at it again and you should be all good. (./adb devices) should show up now.
like i said im not hardcore. it took me some serious googling to get over this hump for me. i was wondering if this should be stickied so linux users with this issue can get passed it quickly. this is the first device i have owned that my ubuntu box didnt natively detect.
Click to expand...
Click to collapse
This is all very basic for setting up adb on linux. I believe its even in the instructions for installing adb on Google's website
Sent from my HTC PH39100 using xda premium
you are correct. but some people, me especially dont understand any of that stuff. so i look for little copy paste procedures anywhere i can. so long as i can find them i dont ask for help. so i thought i would throw it out there for the people who dont look outside of xda for anything. so i hope its both accurate and usefull
This should be in the general Vivid forum. Moderator please move.
Sent from my HTC Vivid using XDA Premium.