Related
Ok, I have a T-Mobile locked and branded Desire and so trying to create a Goldcard but it just gives me Permission Denied when trying to get the CID, what am I doing wrong? I have followed the steps to the T
try the goldcard program?
YES!! Please seriously need help aswell with this. Have a sim free desire and I get to the line of code in the command prompt with
"ADB shell cat/sys/class/mmc_host/mmc1/mmc1:*/CID" and it just says device not found.
I am new to android so i'm pretty clueless with this. Any help would be greatly appreciated.
Kleptomaniac said:
... and it just says device not found.
I am new to android so i'm pretty clueless with this.
Click to expand...
Click to collapse
So about 'device not found'. I had this 'issue' when rooting mine a few weeks ago, so here's what I had to do.
When rooting, you're gonna be using the ADB tools to interface with your phone through USB. This would mean that the computer needs specific drivers for ADB to work properly, which for some reason, did not install well. I'm running Win7 x64 and had a hard time setting it up initially.
SO what you want to do is to first go to Device Manager on the PC and uninstall the drivers for anything related to the phone - it'd probably show up under 'Other devices' with a driver issue. Do that and unplug the phone.
Next, go to install PdaNet. Just run the exe and it will install the drivers you need for ADB to work! Once this is all done you can uninstall the PdaNet program if you don't use it - the drivers will still remain.
When you plug in your phone (it might prompt during the installation, I don't remember) and head to device manager now, you'll see a new entry at the top called Android Phone, with a device called Android ADB Interface. Once you see this, then you're good to go with the rest of the goldcard instructions you were following.
Just to be sure, reboot the PC and go to the Android SDK\Tools in a cmd prompt and type in adb devices. It should return with the serial number of your phone.
That's it, hope it helps!
Thanks alot man its nice to know people here are willing to help. I didn get the drivers but I used HTC sync instead to get them up and running, then after awhile of it still not working I found the goldcard program and it worked! Now all I have to do is wait for this root download to finish...
I just unrooted and installed the leaked radio update so i would have less bugs with the froyo ROMS.
I installed the radio perfectly fine, but now unrevoked isn't working for me.
I deleted all of the previous files and reinstalled them (sdk folder, usb drivers, reflash)
when i run the reflash tool, it gets stuck after rebooting, says "waiting for reboot..."
any help or ideas?
EDIT: as the phone rebooted, it changed to "Flashing recovery image. Do not touch your phone!" but instead of going into recovery, it just continued to restart the phone as usual
What exactly did you do to make yr phone reboot? Manually power cycle? Battery pull?
IIRC, something very similar happened to me with unrev 3.0. I was sure I had the google sdk drivers on my xp box, so I just plugged 'er in and ran the rooting tool. Later I found out the htc drivers were there the whole time, which as we all know interferes with rooting.
So the first thing would be to double-check your drivers, eliminate other USB devices from the setup, disable doubletwist or other apps that talk to the phone.
I did get rooted with the wrong driver in place, but I had to help the process along at one point. I believe I did that by opening a dos box and doing 'adb reboot recovery' from \sdk\tools when the unrevoked script appeared to be stuck waiting for a reboot.
You do have to make sure it reboots to recovery, not normal OS, as recovery boot sequence is where the root exploit takes place...
Do you have HTC Sync installed on your computer? Remove it if so.
cantare said:
What exactly did you do to make yr phone reboot? Manually power cycle? Battery pull?
IIRC, something very similar happened to me with unrev 3.0. I was sure I had the google sdk drivers on my xp box, so I just plugged 'er in and ran the rooting tool. Later I found out the htc drivers were there the whole time, which as we all know interferes with rooting.
So the first thing would be to double-check your drivers, eliminate other USB devices from the setup, disable doubletwist or other apps that talk to the phone.
I did get rooted with the wrong driver in place, but I had to help the process along at one point. I believe I did that by opening a dos box and doing 'adb reboot recovery' from \sdk\tools when the unrevoked script appeared to be stuck waiting for a reboot.
You do have to make sure it reboots to recovery, not normal OS, as recovery boot sequence is where the root exploit takes place...
Click to expand...
Click to collapse
i didn't do anything to get it to reboot, the reflash tool rebooted the phone for me.
i'm 99% sure all other drivers are gone and only the google ones are there. I checked under device manager, but maybe i missed it? is there some secret spot they hide in? (thats not sarcasm btw lol)
I'm gonna try rebooting the phone from a dos box. when typing the commands.....
1-cd\sdk\tool
2-adb reboot recovery??
just wanna make sure.
thanks for your help too
douger1957 said:
Do you have HTC Sync installed on your computer? Remove it if so.
Click to expand...
Click to collapse
nope, i got rid of it as far as i know
Make sure you delete the RUU file on the SD card. Something like pb456img (can't remember the exact file name, and tapatalk search sucks).
Also, make sure you turn usb debugging back on as ruu turns it off I believe.
Sent from Incredible using Tapatalk.
got it! i did it all on another computer from scratch and it worked!
thanks for all of your help
JWorth said:
got it! i did it all on another computer from scratch and it worked!
thanks for all of your help
Click to expand...
Click to collapse
ya i had the same problem, tried unrevoked from a new machine, it worked. must have been old drivers or possibly some sync software. didnt' spend enough time to narrow it down because honestly, once I got re-root, who cares?!
glad you got it rooted!
a couple notes for anyone reading: first, unrevoked has its own set of modified drivers for their root tool... not the same as stock google sdk drivers, at least where the Bootloader ADB driver is concerned.
JWorth said:
i'm 99% sure all other drivers are gone and only the google ones are there. I checked under device manager, but maybe i missed it? is there some secret spot they hide in? (thats not sarcasm btw lol)
Click to expand...
Click to collapse
for future reference, getting rid of drivers in windows can involve a bit of blind faith (unless you know the registry etc. like the back of your hand). Often Windows will auto-install a driver you don't want if you let it do the 'automatic' wizard thing.
if you have a restore point from before any drivers were loaded, it's simplest to use that provided it doesn't screw up other things.
or you can use the uninstaller tool that came with the old drivers, and then the installer that comes with the new ones, and pray it worked.
ultimately, if there are still problems, best practice is to run device manager, turn on the "view->show hidden devices" option, plug in the device if it's removable, and then right-click & uninstall ALL related device entries. For the DInc that would include entries under Android-anything, HTC-anything, possible entries under Modems and Other/Unknown.
Then reboot, run whatever driver installer package you have, plug in the device again, and check that nothing fell under Other/Unknown Devices. If there are such entries in dev mgr, right-click each one to "update driver", then browse to the proper .inf file in your driver package folder. If Windows ever pops up the Driver Install Wizard, you choose the manual options (don't search/not this time/choose from list/Have Disk...) and navigate to the appropriate .inf.
I've been trying to follow the screenshot method with the Android SDK, but it never works. I get as far as opening the ddms tool, but my phone is never listed in there.
I've installed the JavaRE, and the AndroidSDK and the USB thing as instructed.
I tried going to Device Manager (Windows7), and updating the drivers for my phone to use the downloaded USB driver, but it won't have it, saying the best drivers are already installed (I have uninstalled, and reinstalled, and it won't accept it).
Any ideas?
I had this problem. Was something to do with my either my firewall or the tools. I updated the tools and it allowed me allow the connection for my firewall.
I have Avast Antivirus... is this anything to do with it?
No. If your trying to use adb commands for your phone and it isn't working, just update the platform-tools and see if that works. It worked for me when I did that because I couldn't get it to work initially. Am I completely wrong here?
Guys, I need a little help here. I've rooted my share of phones, and even some tablets, but the Evo i bought a few days ago has been a nightmare.
For some reason, and I can't tell why, this thing will not be recognized by Windows.
It always shows up as "Unknown Device" under the USB catagory on Device Manager.
I've tried different OS versions (Windows 7 64Bit, Vista 64bit, Even Mac). I've also pulled down every form of driver I can think of (SDK Orginal version, HTC Sync, Hboot Versions, etc.)
I just cannot get this thing to be recognized. And if I manually try to update the driver and point it to one that I've downloaded, Windows tells me that the most current driver is already installed.
The bottom line is that I need to be able to connect to the phone from the comp in order to push stuff via ADB and throw commands at it. The same unknown device situation happens when the phone is in bootloader or actually booted into Stock Froyo (2.2)
Has anyone ever seen anything like this? I know i haven't, and it's buggin me out.
buster3845 said:
Guys, I need a little help here. I've rooted my share of phones, and even some tablets, but the Evo i bought a few days ago has been a nightmare.
For some reason, and I can't tell why, this thing will not be recognized by Windows.
It always shows up as "Unknown Device" under the USB catagory on Device Manager.
I've tried different OS versions (Windows 7 64Bit, Vista 64bit, Even Mac). I've also pulled down every form of driver I can think of (SDK Orginal version, HTC Sync, Hboot Versions, etc.)
I just cannot get this thing to be recognized. And if I manually try to update the driver and point it to one that I've downloaded, Windows tells me that the most current driver is already installed.
The bottom line is that I need to be able to connect to the phone from the comp in order to push stuff via ADB and throw commands at it. The same unknown device situation happens when the phone is in bootloader or actually booted into Stock Froyo (2.2)
Has anyone ever seen anything like this? I know i haven't, and it's buggin me out.
Click to expand...
Click to collapse
I've never seen that before. Wish I had something for ya. Is the Evo brand new or used? Are you sure the usb cable is good? I've seen a bad cable cause some headaches before. Wish I had more for ya, sorry man.
Sent from my PC36100 using XDA App
EVO is not new. I bough it from cragslist a few days ago. It seems to work fine otherwise. Not rooted for sure, and running Sprint original 2.2.
I did try a couple of different USB cables just to be sure, and had the same results.
The funny thing is that even though I was never able to get it "recognized" on any of my machines, I was able to get ADB so "see" it for a while. I started the rooting process by pushing files to it via ADB and even sent a reboot command to it.
Once it rebooted, that's when it all went bad. It was still showing as unrecognized (just like before), but now ADB can't see it at all. Keeps telling me no devices are connected.
Even my friend's Mac Air (which supposedly doesn't need any kind of drivers to see the phone) can't see it either.
It's just weird...
perform a hard reset, maybe a rogue app or setting got messed up,
fastboot screen>clear storage>yes
Tried that as well. Sorry i didn't mention it in the original post.
I think I've pretty much tried everything that's somewhat logical at this point.
Now I'm looking for the "illogical" ideas.
Make sure usb debugging option is turned on in settings>applications>development and the phone is in charge only mode. Then it should be recognized and you should be able to use adb.
Debugging was turned on already. I made sure of that.
As for the mode of connection I've tried them all with mixed results.
Here's what I've seen so far...
Charge only - unrecognized device in Device manager, and ADB can't see it.
HTC sync - unrecognized device in Device manager, and ADB can't see it.
Disk Drive - unrecognized device in Device manager, and ADB can't see it.
Internet Sharing - never tried it.
Here's the weird part. If i uncheck Debugging and set the phone to HTC Sync, I am sometimes able to get ADB to see it.
This is just confusing...
What happens if you uninstall HTC Sync and just leave the drivers installed? Could work I suppose. I know unrevoked says to make sure you uninstall HTC Sync and install the ADB drivers.
try this. connect your evo to a machine running xp. i had the same problems rooting one evo using windows 7. connected to a machine running xp ,zipped right through without a hitch.
HOPE THIS HELPS YOU IN YOUR QUEST
Thats what I tried on the Vista box.removed HTC sync, and left the HTC drivers.when that failed I removed the drivers too and replaced them with several different ones I found online.none seemed to work.
The strangest part is that all guides seem to say that MAC OS should just see it without any drivers.
I borrowed friends MAC air and it didn't see it either.
I'm not sure which USB drivers you are using, but these work for me. Uninstall the drivers first, then install this. I hope it is legal to put these here and if not I am extremely sorry.
PS you could try a Linux Live CD and it will see it without drivers or go with Wubi which installs Ubuntu on your Windows hard drive and can be uninstalled just like any other program. It gives you the option to boot into Ubuntu or Windows on bootup. Neat little program and it is faster than using the live CD. Go to this link Wubi and click the Start Download button to download Wubi.
Those seem to be the same drivers I've tried (well those and a ton of others as well).
I'm gonna give that LiveCD idea a shot. Burning it now.
If not, I'm gonna try to find an XP machine somewhere.
I've got a couple of VM's on my machine running XP, but since the main Win7 Machine doesn't see it, it can't seem to pass the USB connection over to the XP VM.
Man, I have to say, this is just the most complicated rooting process I've ever seen. If this was my first root attempt, I'm pretty sure I'd leave Android forever
It usually is a painless operation to root the Evo. For some reason you are having a difficult time with driver installation. It seriously has to be something simple that has been missed, because I have rooted mine and several friends Evo's and it was very easy. I had a MyTouch 3g 3.5mm before this Evo and talk about a pain. Before the Universal Auto root app you had to make a gold card first and that in itself took over an hour. It was my first root and it was very difficult and time consuming, so to see how easy the Evo was no matter which way I do it made me very happy.
buster3845 said:
Thats what I tried on the Vista box.removed HTC sync, and left the HTC drivers.when that failed I removed the drivers too and replaced them with several different ones I found online.none seemed to work.
The strangest part is that all guides seem to say that MAC OS should just see it without any drivers.
I borrowed friends MAC air and it didn't see it either.
Click to expand...
Click to collapse
yes the mac doesn't require additonal drivers to run adb however u need to make sure the directory is properly set in terminal so adb knows where to pull commands from... on windows did u try uninstalling everything phone related? SDK, HTC Sync, the whole nine yards then try reinstalling only the sdk and the usb drivers? I know with the lastest SDK the usb driver is not included for some reason or at least it wasn't with mine... then one day my adb just randomly stopped working and a uninstall/reinstall cleared up everything... try this usb driver and see where it gets u. Don't know if it's any different that wat the guy above posted but worth a shot. Reinstall the appropriate SDK first then i would recommend plugging the evo into the pc with no usb drivers installed then when it cant automatically find the drivers direct it to the file u downloaded and it should pull the necessary drivers from there and see if that does the trick...
View attachment android-usb-driver.zip
No dice so far guys...but i have made progress in identifying the issue (sort of).
So here's the deal - the ONLY way the phone is recognized is if i toggle the "debugging" setting.
If i plug the phone in with the switch set on (meaning USB Debugging enabled) the phone is not recognized. Pointing the unknown device to the drivers (any drivers) does nothing.
However, if i plug the phone in with the switch set off, it finds a usb mass storage device. Then i turn the debugging switch on, and it finds the ADB Android phone with no issues. Then i can push commands via ADB without any problems.
The problem i have is that I cannot toggle that switch if i boot into HBOOT menu. So the comp never see's the phone.
I've tried this experiment on Win7-64bit, Vista-64bit, XP 32bit, and even MAC.
The same situation seems to apply everywhere, and with all of the drivers I've tried. None of them seem to allow the phone to be plugged in and automatically be found. The only way for the comp to see the phone is if i toggle the debugging switch off, then on.
At this point, I'm ready to put out a bounty on this. $20 via PayPal to anyone who can walk me through it. Bottom line is that I need to be able to see the phone without having to toggle the debugging switch. That will allow me to boot into HBOOT and still send commands to the phone via ADB.
Thanks for all the help guys. Hopefully, we can get this resolved.
**BUMP**
Anyone care to take a shot??
Ive looked all around and cant seem to find a solution so ill start a new thread. Im trying to root my new mt3gs after getting a replacement, and so far every time i try to connect the device it will not show up in the adb lists. I know its not a faulty anything because i can put my music or pictures on the phone, but for some reason it will not show up in the adb devices. If anyone has any suggestions i would much appreciate it.
if no devices is showing up when you "adb devices" you probably don't have the drivers.
Download pdanet and get the drivers from that(don't have to install whole thing just quit after drivers are installed)
btw, wrong forum, Q's should be in the Q&A.
-Get Android sdk
-try pdanet drivers
-use different usb port
Also there is more than 1 way to root, use one of the newer methods not the old one.
thanks ill try those and report back here. Also sorry for wrong forum.
yup android sdk works best