adb not working - myTouch 3G, Magic General

Hey forum, I'm trying to get adb to work as part of rooting my new 1.2 mytouch. nothing will work. the phone will not show up, or the drivers arent working or something is wrong, im not sure. id appreciate any help. thanks.

is your problem that when you do adb devices nothing shows up?
I have that problem and i have installed drivers and everything correctly
Try just using everything anyway. I flash roms upgrade radio etc. even without it showing in devices. it works fine for me.

I had the same issue with that, try downloading htc sync for your phone and country and that includes the proper drivers, also make sure in the android sdk you have downloaded the usb plugin.

Related

[Request] Recovery/Cyanogen/adb

Hi,
I have been messing with this for a few weeks now.
I have a magic 32B, spl 0004
I don't know how but i got cyanogenmod 4.2.5 on my phone.
But then i tried to use the update app and it fails.
It seems that there are 2 problems.
1. my recovery is still the stock one
2. i just cant seem to get a good connection with my computer.
Every time i try something its waiting for device.
Or with adb devices its an empty list.
i used a windows vista machine and a windows 7 machine
Is there someone who is willing to help me get this done?
I checked threads about, usb drivers, installing adb, installing recovery.img, installing cyanogen.
But there is always a step that just doesn't go according to the manuals.
i was about to give up, but i just really want this to work.
As you have already stated you have a stock recovery.img on the phone, to get the cyanogenmod updater program to work you need a custom one, the instructions to install this can be found on cyanogenmod.com in the downloads section.
If you are having problems getting the phone to connect to the pc make sure the drivers have installed correctly, you can download them at the link bellow incase you cant find them, by default they dont download with the sdk anymore, dont know why :-|
http://rapidshare.com/files/315790307/usb_driver.rar.html
justbenjp said:
As you have already stated you have a stock recovery.img on the phone, to get the cyanogenmod updater program to work you need a custom one, the instructions to install this can be found on cyanogenmod.com in the downloads section.
If you are having problems getting the phone to connect to the pc make sure the drivers have installed correctly, you can download them at the link bellow incase you cant find them, by default they dont download with the sdk anymore, dont know why :-|
http://rapidshare.com/files/315790307/usb_driver.rar.html
Click to expand...
Click to collapse
I have tried to install a custom recovery, but when i follow the steps i cant seem to connect to my phone via CMD.
When i check the drivers.. i'm not sure its 100% correct.
I have installed the once before.
and now he doesn't ask me for the drivers anymore.
but neither do i see it in the devicemanager, the way its being described in the manuals.
just something else involving android, but not ADB
i have tried to follow the manual, and threats about how to get the driver right..
but with this, i also have had problems with the steps..
On your phone go into settings....applications....Development and make sure
you have USB debugging enabled
justbenjp said:
On your phone go into settings....applications....Development and make sure
you have USB debugging enabled
Click to expand...
Click to collapse
I have done this..
I will try again on a vista machine which i havent used for this yet
anheuer said:
I have done this..
I will try again on a vista machine which i havent used for this yet
Click to expand...
Click to collapse
Great.. it would not install the SDK..
So back on my windows 7 machine..
still getting device not found in CMD - adb devices
connected with usb debugging on..
cant see anything in device manager, but the system also doesnt ask for drivers...
I went into fastboot and then it asked me for drivers..
Now i do have
Android phone - Android Bootloader interface
but in any other situation, it does not show anything or ask anything.
I just keep getting device not found...

having trouble with usb drivers

so i am new to android and i decided " hey why don't i try to root my nexus" so i tried and i cant get any father that checking if the computer can see my device which it cant for some reason. so i went online i figured out that i don't have the usb driver for android. so after that i tried to down load then and i even installed them and restarted my computer and it still wont work. so if any one can help me with my problem it would be greatly appreciated.
On Home Screen, press menu>settings>applications>development and make sure USB debugging is checked.
What OS you running?
Specs would help, where did you get your drivers? What other software have you tried?
i turned on the debugging and it still hasnt worked
i am running xp. i downloaded the android sdk from here
developer.android.com
i just want to put the modaco desire rom on my phone that my onl reason for wanting to root. i really like the sense ui
I am having a similar problem, so i might as well use this thread instead of creating a new one.
I have a dual boot computer, win7 and fedora, both have SDK. I unlocked my nexus one with windows, as i noticed the commands were considerably easier, or at least they don't work when i plug the linux ones into fedora.
Last night i was going to push the undervolt kernel so i plugged my n1 while in win7, It instantly came up complaining about drivers, which i had already installed and had previously worked, i went to re-install them, and windows says they are up to date, but still no luck recognising the device (Debugging mode is definately on)
So i switched to fedora, no driver pop ups obviously, but when i try to push the kernel through, it does not recognise the device.
In the bootloader it says "fastboot usb" while plugged in.
I can't pinpoint when it stopped working, but the last time i used fastboot was to put the RA recovery, since then i flashed CM 5.0.2, CM 5.0.3.1, the desire rom, and used a nandroid restore to get back to 5.0.3.1
Anyone got any ideas? Without fastboot i am pretty much restricted to flashing .zip files from the recovery.
yeah i cant even unlock mine its so frustrating
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...
temperbad said:
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...[/QUOTE
Yeah I know how you feel its so frustrating I tried all day yesterdAY too
Click to expand...
Click to collapse
drbrendin said:
temperbad said:
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...[/QUOTE
Yeah I know how you feel its so frustrating I tried all day yesterdAY too
Click to expand...
Click to collapse
I tried all day too like a gazillion times.... and wonder does everyone have driver issues? I tried with my XP computer and windows 7, no go, then I read posts people having the same issue, then they just post " nevermind got it" and didn't even write what they did to get it.......
Click to expand...
Click to collapse
not everyone is a dev
Ok, I have my Nexus One set up so I can use with via Windows 7 (desktop) or Ubuntu (Laptop).
The Linux part is a bit more involved, but since everyone is running Windows (unless I missed something), I will work there.
First of all, your phone needs to be in Dev mode (which was covered earlier).
With the phone UNPLUGGED from the PC, uninstall any previous SDK installs you have and be sure to remove the directory.
Then, install the SDK found here: SDK
Install this SDK and let it complete the install, which will include downloading for a bit. You need to do this since the SDK package above does NOT include the right drivers!!!
Once this has been completed, plug your phone into the computer via USB. Your computer will find a new device, however, it cannot locate the drivers for it. Browse and point the installer to:
DRIVE:\PATH_TO_android-sdk-windows\usb_driver
Don't go any further than this!!
Now, let it do it's thing and you should have a new device in the device manager called:
Android Phone
...|_Android Composite ADB Interface
Now, go to the command prompt and change to the following directory:
DRIVE:\PATH_TO_android-sdk-windows\tools
There, you will find adb.exe
Type:
adb devices
and you should see:
List of devices attached
HT019P801614 device
If not, something got screwed up and would need to dig further to help ya.
Ok ill give this a try once get home from school
nexus one root.
Ok assuming that you have the android sdk installed correctly, try rooting your phone via the superboot method. The first link below has a full detailed guide for rooting the nexus one and I believe has all of the device drivers for those who have not been able to get them running well. If you still have trouble getting the drivers working checkout the second link. Anyone who is relatively new to working with the sdk and is not familiar with working the commands check out the third link. Read the entire thread! it is very helpful.
1) http://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
2) http://forum.xda-developers.com/showthread.php?t=613217
3) http://forum.xda-developers.com/showthread.php?t=619153
If you have any questions PM me on xda. I'll try and help in anyway, it took my like two days to actually root my nexus, I wasnt familiar with using ADB and Fastboot to root.
One thing I know I was having problems with since I came from the G1 was that the new SDK has to actually be installed via an .exe now. I was used to it all being in a zip so I kept trying to load up what I thought were the right USB drivers, but they were actually the 1.6 drivers I already had. So make sure to run the .exe that comes with the SDK.
ok so while i was downloading the sdk a notification came up that said that it could not rename the directory. is this bad?
i am having an issue with installing the right driver as well. my computer keeps installing the nexus one as a "mass storage device". i have uninstalled and reinstalled a few times but no luck. i have the phone set to debug mode, using XP btw. any help would be appreciated.

Trying to root my GT540, tried everything

Hi.
I know it's been talked about a thousand times alreay, I hate to open a new thread, but I really tried every option I've found to root my new GT540g
Z4root Androot and SuperOneClick, none works
I put my phone in "USB debug" but it seems like none of this programs are realizing that
I also tried with the root.bat (http://forum.xda-developers.com/showthread.php?t=803238) method, and nothing
When I connect my phone, if I start the LG Mobile Update program, it can see my phone
but when I ask adb to do the same, like with a simple "adb devices" it cannot find it
I'm on Win7 x64, and have already reinstalled the drivers a LOT of times, even switching between the oficial and some drivers I've seen on the forum
Please, help me
Is there an error message?
in adb it just says "device not found"
switch off the 'mass storage only' option if it is on
I've tried with both mass storage on and off
this is puzzling
hey ive got the same issue
so ive decided the gt540 is not worth owning and bought a desire Z
i will trade my gt540 in for £21, mine randomly crashes, turns it self off, freezes etc. im glad i only paid £35 for it initially.
edit: enough about how rubbish the phone is, for what its worth im using win 7 x64 too, i wonder if that is our issue
try universal androot it works apparently
Doughnut said:
hey ive got the same issue
so ive decided the gt540 is not worth owning and bought a desire Z
i will trade my gt540 in for £21, mine randomly crashes, turns it self off, freezes etc. im glad i only paid £35 for it initially.
edit: enough about how rubbish the phone is, for what its worth im using win 7 x64 too, i wonder if that is our issue
Click to expand...
Click to collapse
I'm sorry, the GT540 wasn't worth it o.o how is a phone not worth it just because you can't root it. Also, if your sick of crashing then change the software install Cyanogen or other roms.
Anyway you should try device manager and see if the device is fully detected.
Jack
Have you installed the adb drivers? Without them adb can't see the phone. Even if you put it in "Debug mode". You can download them with google's android sdk package.
Well, I'm from Argentina, so the cost of the phone is pretty high, I had to pay almost $ 200, and they won't change it
Anyway, I think I've come to a solution. I've installed the adb drivers, I tried with every driver that appeared on the GT540 FAQ, but nothing worked
Yesterday, I went the opposite way, I cleaned every LG driver I could find, and just let the LG Mobile Update app install whatever stock drivers it wanted
I didn't add the Virtual Modem, or any of the other drivers, rebooted, and voila, adb started seeing my phone
I'll try to flash the Europe ROM with fastboot and report
Thanks to everyone for the helping hand!
Mitalca said:
Well, I'm from Argentina, so the cost of the phone is pretty high, I had to pay almost $ 200, and they won't change it
Anyway, I think I've come to a solution. I've installed the adb drivers, I tried with every driver that appeared on the GT540 FAQ, but nothing worked
Yesterday, I went the opposite way, I cleaned every LG driver I could find, and just let the LG Mobile Update app install whatever stock drivers it wanted
I didn't add the Virtual Modem, or any of the other drivers, rebooted, and voila, adb started seeing my phone
I'll try to flash the Europe ROM with fastboot and report
Thanks to everyone for the helping hand!
Click to expand...
Click to collapse
good you sorted it, sounds like you had driver overload
JackG256 said:
I'm sorry, the GT540 wasn't worth it o.o how is a phone not worth it just because you can't root it. Also, if your sick of crashing then change the software install Cyanogen or other roms.
Anyway you should try device manager and see if the device is fully detected.
Jack
Click to expand...
Click to collapse
Easy, because its not to my expectations.
So I deem it unworthy, its a matter of opinion rather than fact, so probably pointless debating.
Someone has messaged me from this forum asking to buy it for £21, they're welcome to do so.
try this : http://www.4shared.com/file/p3TR1eih/autorootapp2sd.html
Hmm. I'm assuming you are on 2.1.
I happened to see people come across problems on Win7x64. I'd highly recommend you try it on WinXPx32.
z4root works perfect.
http://forum.xda-developers.com/showpost.php?p=9109591&postcount=1
I have tried both root.bat method and z4root. Both worked fine for me. However, I personally prefer root.bat.
Pretty much any rooting app that supports Rage Against The Cage exploit would work on GT540.
Use my information at your own risk!
And, like Mitalca suggested, you might want to try uninstalling all drivers and a clean reinstall to prevent driver conflicts.
In any case, more than the LG drivers, you'd need ADB drivers.
Mitalca said:
in adb it just says "device not found"
Click to expand...
Click to collapse
Try to remove sdcard or disable it from menu storage.
why don't you try a custom ROM such as LewaOS or SDSL... Just flash it and your phone would be rooted already, and it's much featureful and runs faster than the stock ROM
Glad to see your sorted
I would have said it works on Win 7 x64 because I use it
I also use ubuntu on the same pc, but thats besides the point.
Anyways, glad to see your sorted, and enjoy your phone!
Try to change rom
Try z4root for rooting your GT540. It works fine on our phone.

Wiped Phone, OS is gone and phone is unrecognized

Hello everyone,
I have wiped everything using the TWR recovery boot option in a really poor attempt to unroot my phone since it was behaving strangely.
Now it look like my OS is gone and the phone cannot be recognized anymore by my PCs even if I install the appropriate drivers manually.
Since it is no longer possible for me to attempt to flash the phone with a stock firmware using odin, I have attempted transfering the file on the phone using the sd card and installing it through the TWR recovery menu however it does not seem to be a possible option.
Does anyone have any advice to propose to restore the phone with a working OS?
It should still be able to load a recovery file from TWR, I am just unsure where I could get these since they differ from ROMs available everywhere else, I can also make change directly to the device drive using the file explorer so worst case scenario, I suppose it could be possible to copy past all the content of an image over there via the sd card.
Thanks
what happens when you put it into download mode and connect it to a computer? can you even get to odin mode? there is a way to ADB an OS onto it , but its pretty particular and usually not necessary.
youdoofus said:
what happens when you put it into download mode and connect it to a computer? can you even get to odin mode? there is a way to ADB an OS onto it , but its pretty particular and usually not necessary.
Click to expand...
Click to collapse
The download mode seems functionnal on the phone, however the phone is not recognized by any PC which render it useless. My guess is that some files or driver on the phone side got deleted and it is no longer sending the right information to the machines it connects to.
Loading ADB into the OS seems like a neat idea, I didnt know it was possible. I am just unsure if flashing from within the phone is functionnal, my guess is that it probably work, but it is perhaps just a little riskier than doing it from an external device.
Thanks, I will try that, if you have any further advice, let me know
Edit : Oh I just realized you said to ADB an OS into it, yeah I don't thinks its possible, since nothing recognize the phone.
Have you uninstalled and reinstalled the drivers on your computer? Tried a few different computers? And, more likely to be successful, a few different cables?
youdoofus said:
Have you uninstalled and reinstalled the drivers on your computer? Tried a few different computers? And, more likely to be successful, a few different cables?
Click to expand...
Click to collapse
Yes, it also worked perfectly fine a minute before everything get wiped. I am pretty confident the only way to get it back working would be to copy the files into the phone manually, I am just unsure what files I should copy to the root since I have never seen how it usually look.
That's weird because I don't know of a way to wipe stuff in such a way to remove the capability of Odin connecting to a computer
youdoofus said:
That's weird because I don't know of a way to wipe stuff in such a way to remove the capability of Odin connecting to a computer
Click to expand...
Click to collapse
Hmmm I went on cyaogenMod and installed it on my device using the sdcard. Unsure why the stock OS wouldn't work, but at least now the phone is functional.
The phone is still not recognized but it seems like it is slightly better, it now displays as Unknown USB Device (Device Descriptor Request Failed). Which is better than getting disconnected right away from the computer. Now it probably just is a matter of fixing the drivers or the phone further since I have messed around a lot since everything stopped working.
Alright thanks a lot, it didnt occur to me that I probably could install other roms. Im still unsure whether or not I should stick with it but thats the least of my worries right now
garett_ said:
Hmmm I went on cyaogenMod and installed it on my device using the sdcard. Unsure why the stock OS wouldn't work, but at least now the phone is functional.
The phone is still not recognized but it seems like it is slightly better, it now displays as Unknown USB Device (Device Descriptor Request Failed). Which is better than getting disconnected right away from the computer. Now it probably just is a matter of fixing the drivers or the phone further since I have messed around a lot since everything stopped working.
Alright thanks a lot, it didnt occur to me that I probably could install other roms. Im still unsure whether or not I should stick with it but thats the least of my worries right now
Click to expand...
Click to collapse
have you tried a different version of odin? or at least a new download of it? does your computer recognize it when its booted up?

Drivers on Windows 10

First, I'm not a newb, but I'm at my wits end so I'm swallowing my pride and posting this here.
I recently wiped my hard drive and reinstalled Windows 10. Prior to that Windows could see my v20, I could transfer files and ADB worked fine.
I installed command line tools to install ADB/drivers and tried both LG mobile 4.20 drivers and even tried the Intel drivers. Along the way I dusted off usbdeview to clear out the drivers and start over so likely further screwed things up.
I was able to eventually get ADB functional but no matter what I did the device wouldn't show up as a portable device under My PC.
I've finally said screw it and am currently reinstalling windows 10 from scratch for a fresh start.
So, looking for input as to the best way to proceed on fresh Windows install. Is best way to install adb/adb drivers by installing command line tools rather than full android studio? Does it matter what order I install LG drivers/ADB?
I'm running the notsostock 5.5 dirtysanta rooted on a verizon v20.
Thanks.
I haven't been able to get it to show as a portable device since flashing the NotSoStock rom. I'm on Windows 7, it was visible just fine prior to flashing and I haven't done anything to the computer in the meantime.
I've been assuming it was something goofy in the rom rather than windows drivers... It just hasn't been a big enough deal for me to monkey with, I don't often need that, and adb still works fine so I just push/pull stuff if I need to move anything...
ZachJohnson said:
I haven't been able to get it to show as a portable device since flashing the NotSoStock rom. I'm on Windows 7, it was visible just fine prior to flashing and I haven't done anything to the computer in the meantime.
I've been assuming it was something goofy in the rom rather than windows drivers... It just hasn't been a big enough deal for me to monkey with, I don't often need that, and adb still works fine so I just push/pull stuff if I need to move anything...
Click to expand...
Click to collapse
I came to the same conclusion about 4 hours ago. It was the NotSoStock rom that broke it. I wiped my v20 and installed the WETA rom and everything works perfectly. The dialer lock issue I had with that rom is gone. The hotspot issue is gone, etc. I've only been on it for a few hours, but it's definitely better than what I was on before.

Categories

Resources