Related
I've posted this inside another thread but decided to make a new one so others can see.
To all of you guys who are giving up - DON'T !
Here's how I finally got root on my DINC after about 3 days of trying.
I've read and watched almost every post and walk-throughs available in this forum and few others and was still unable to get into ADB Shell using any of the methods and tricks available and even though none of them worked I kept trying until I found a post on adndroidforums.com by Centsy. So along with his instructions and combination of many others here's how I achieved root:
1. Download the file from the 10 minute incredible root video on YouTube by mejdam. (can't post the link cause I'm new to the forum).
2. Unzip the file and run SDK setup.
3. As soon as SDK setup runs it gives an error message. Close it. then hit Cancel on next window.
4. While still in Android SDK and AVD Manager click on Available Packages (on the left) and then hit the plus sign in the right window for the repository. It will give you a list of packages available. Download the very last one which is the USB_Driver. It will add 'usb_driver' folder to your SDK folder where you ran sdk setup from.
5. Modify android_winusb.inf file inside the 'usb_driver' folder by adding these lines at the end of [Google.NTx86] and [Google.NTamd64] sections:
;HTC Incredible
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0C94
6. I used the 2 gig Sandisk memory card that came with the phone. Had it FAT32 full formatted on the pc.
7. insert the card into the phone wait for it to be recognized
8. connect the phone to the pc and use the modified inf file of Android SDK usb_driver to get the phone connected and drivers installed. Note that I do not have HTC Sync installed on my pc.
9. on the phone go to settings->applications->development->turn on USB Debugging. wait for the phone to be recognized
10. open command prompt, navigate to your SDK\Tools folder and type in: adb devices. when you hit enter it should list your phone as being connected.
11. at the prompt type: adb reboot recovery, hit enter
12. as soon as the prompt is back type: loop and hit enter to start the adb shell loop. As soon as the loop starts running, the phone should show the white HTC Incredible screen, start clicking in and out the sd card before you hear the device disconnected sound on your pc. keep clicking the card in and out until you hear device connected sound on you pc. If you still don't see THE message we are looking for after another 10, 15 seconds stop clicking the card. take the battery out of the phone, put it back in, wait for it to reboot and repeat steps 11 and 12.
I had to do steps 11 and 12 about 3 times when I said to myself - next time is the last time and if it doesn't work then I'm going to get the 2gig PNY card that everyone is saying helps them achieve root. Then all of the sudden it took a little longer for the device connected sound to come up and the mouse cursor turned to the Waiting Hour-Glass and as soon as I heard the sound I saw the good old error message we are all striving to see. After that I just followed the instructions on the 10 minute root video to get the phone rooted.
Never give up, Never surrender !
Hopefully this will help some of you guys to achieve root and thanks to everyone who's hard at work on getting this great phone rooted.
Hi,
Having issues with your Step #12. You say to click the card in and out when the white HTC screen comes up and do it till the first disconnect sound. Then you go on to say keep clicking untill it connects. Then you says 10-15 seconds after the connect sounds keep clicking. Don't you mean to say keep clicking from white HTC screen till 10-15 seconds after the 2nd sound(the connect sound) So basically clicking for over 30seconds.
Please clarify as I'm thinking you meant differently thne what you typed. I too have a stock 2G sandisk card that came with my phone and so want to get this rooted without buying a PNY card hah.
- Pete
sonypete said:
Hi,
Having issues with your Step #12. You say to click the card in and out when the white HTC screen comes up and do it till the first disconnect sound. Then you go on to say keep clicking untill it connects. Then you says 10-15 seconds after the connect sounds keep clicking. Don't you mean to say keep clicking from white HTC screen till 10-15 seconds after the 2nd sound(the connect sound) So basically clicking for over 30seconds.
Please clarify as I'm thinking you meant differently thne what you typed. I too have a stock 2G sandisk card that came with my phone and so want to get this rooted without buying a PNY card hah.
- Pete
Click to expand...
Click to collapse
Basically once the white screen comes up, start clicking the card in and out until about 10, 15 seconds after the 2nd connect sound that windows give you. However, you MUST start pushing the card in and out before the 1st disconnect sound.
Okay cool. Fingers crossed I have been trying since yesterday and about to jump out the window hah.
- Pete
Wow, I got it first time with this method! Thanks a lot! I am also using the stock 2gb card that came with the phone.
Thanks man. I got this to work twice in about 4 tries. 1st time it worked I accidently selected reboot option. So had to retry this method. My clicks were medium speed not very fast and not excessively slow in case that helps anyone. About 1 a second.
- Pete
(2G Sandisk Rooter hehe)
Hey this method worked to get the error but I can not write to the SDCard, I get the following when I try to push something: failed to copy 'busybox' to 'sdcard/busybox: Permission Denied
It is the same with any file and I did Apply sdcard:update.zip
Please help!
I think this will help
KingJ50 said:
Hey this method worked to get the error but I can not write to the SDCard, I get the following when I try to push something: failed to copy 'busybox' to 'sdcard/busybox: Permission Denied
It is the same with any file and I did Apply sdcard:update.zip
Please help!
Click to expand...
Click to collapse
Once you get error, I believe that you need to run the "apply update.zip" once and let it fail. Then you can adb to the sdcard.
PS, this method never worked for me, no matter how much I tried.
dreamersipaq said:
Once you get error, I believe that you need to run the "apply update.zip" once and let it fail. Then you can adb to the sdcard.
PS, this method never worked for me, no matter how much I tried.
Click to expand...
Click to collapse
Same here, i still can't get to adb shell . . .
I got into adb doing the click on the 3d try but it kept failing to push the payload and then I accidentally restarted the phone. AHHHH, just spent 30 minutes doing the same thing and couldn't get back in.
Awesome, I got it to work using your method.
First I tried the "10 min..." video, but it was unclear in some areas. I had to try a few times (10+) to get it to work. Problem for me was the speed at which I was putting in and out the SD Card. I did it at some odd pattern like In (4 sec), out (.5 Sec), in (4 sec), etc. Then all of a sudden it worked.
Got it rooted .
Thanks again!
Finally got it. Thanks
Spent probably 6 hours messing with it. Not worth it anymore.
What does this mean:
8. connect the phone to the pc and use the modified inf file of Android SDK usb_driver to get the phone connected and drivers installed.
Click to expand...
Click to collapse
I've connected the phone, it shows up when I type "adb devices", but I have no idea how to "use the modified inf file... to get the phone connected and drivers installed."
dmauro said:
What does this mean:
I've connected the phone, it shows up when I type "adb devices", but I have no idea how to "use the modified inf file... to get the phone connected and drivers installed."
Click to expand...
Click to collapse
if your phone shows up then you may proceed further. Howerver if after quite a few tries you still can't root then you should try updating the driver with the modified inf file.
go to your device manager, you should see the very first item should be Android Phone. right click on the phone and choose update driver and point to the modified INF file.
if your pc tells you that it cannot find a better driver, just uninstall the phone from device manager (right click and choose uninstall), unplug the phone from the pc, wait about a minute and plug the phone back in - but use a different usb port just in case. Then when found new hardware manager comes up point it to the modified INF file.
Good luck.
Doesnt work for me. annoying
*edit* Finally got it 7 seconds awesome
I cannot get my inc to take the driver .inf file. I have edited it correctly, tried forcing the driver to it, and it keeps telling me that the driver is not valid for a 64-bit os. Tried doing it as a legacy device as well.
Win 7 ultimate 64-bit
dont see the plus sign
hit the plus sign in the right window for the repository well for some reason i dont see any plus sign in there to hit tell me what i might be doing wrong
Please Help If You Can
I am logged in; got the recovery; followed the instructions, and it didn't say unrevoked. so i did it again and
did a whole bunch of things
Finding update packge
opening update package
verifying update package
installing update
veridying curernt system
unpacking patches
removing unneeded files
patching system fioles
symlinks and permission s...
then I got
e:multiple firmware images
e: can't store zip image
installation aborted
Now I also cant get into ADB SHELL
when I type adb shell I get
- exec '/system/bin/sh' failed: No such file or directory (2) -
but no prompt
I will try to stay logged in and everything BUT PLEASE HELP. What do I do?
Thanks for these instructions, Op.
I was successful by exactly following your steps.
Edit to provide additional details -- I tried unsuccessfully upwards of 100 times following the instructions in the 10min video. A couple things that probably attributed to the success of this method for me:
1) Formatted 2GB card to FAT32 (4096) as recommended.
2) Uninstalled HTC Sync / HTC Driver Installer. I used the "SDK Setup" to download the USB drivers.
A tip if you're having trouble getting the USB drivers to download... I had to go to the "Settings" menu in the Android SDK and AVD Manager, and check the "Force https://... sources to be fetched using http://..." otherwise the Available Packages menu would fail to get the repository.xml.
I then applied the recommended changes to android_winusb.inf in C:\sdk\usb_driver\ and used this .inf as the Android Phone driver. It was possible to assign the driver after setting to "Debug" mode in the OS.
3) I started clicking the SD card as soon as the white screen would come up, instead of waiting for a few seconds after it appeared. I used a 2 seconds in, .5 seconds out, 2 seconds in, ... pattern.
4) After each failed attempt, instead of pulling the battery and holding volume- + pwr, I went with the ops method. This was to abort the "loop" tool on the PC, pull the battery, boot the phone normally to the OS, verify the phone was recognized by typing "adb devices" on the PC cmd prompt, commanding "adb reboot recovery" to reset the phone into recovery mode, starting "loop" as soon as the command prompt came back, and finally clicking the SD card as described above.
Hope this isn't a post that will really piss everyone off, but I'm not sure really where to go from here. Tried about 20 times. I run the loop command, it shows up for about 1 line and goes away.
I am still getting an Android 1.0 error of some sort. I've been reading about how to get this driver installed correctly. I uninstalled everything and started over (USBDeview, HTC Sync...The one for the Slide, SDK, Updated it with SDK Updater)
Windows 7 x64
Just went to Computer> right click> Manage> ABD Testing Interface....
I have a little yellow exclamation point next to this... Tried updating the driver. Not really sure though what driver I need or where it's at or the place I need to download it.
You ever feel like you've surfed cyberspace to the end of the megacluster? Yeah that's pretty much where I'm at frustrated, broken hearted, and wanting a one-click root procedure like the g1/mytouch.
Is it rude to wave money in developers faces for help? Does this make you feel like a stripper?
Ahhhh I'm just stuck.... Help would be so awesome.
I'm not a dev but I do feel like a stripper, but for unrelated reasons... Anyways. On my win7 64 I had to use pdanet and actually have the program running. For whatever reason when I tried closing pdanet it wouldn't work, so give that a shot. It also stopped the android 1.0 driver issues. I also gather from wes garners' twitter page he's working on a method of rooting that runs the adb scripts and **** for you. Maybe just wait it out.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
DaemionIX said:
Fermunky, I've been following your problem because I was having it too. What finally got it for me was, I formated a different sd card, put it in the phone, removed all software ( htc sync, pdanet) and removed all drivers I could find using usbdeview. Then rebooted with phone unplugged, installed pdanet following all their instructions, then the loop worked perfect. Good luck
Tl;dr version, i tried it all at the same time and it worked
Click to expand...
Click to collapse
That was on a win x64 system. Honestly I think it was the sd card, as weird as that sounds, because I tried all the usb stuff for about 4 hours to no avail, swapped out the sd card, rooted the first try.
I'll give all this a try. Do you use PDANet with or without HTC Sync? I was pretty tired last night when I tried and eventually gave up.
Hence all the stripper references.
I have an extra SD Card from my original Mytouch. I'll give it a try and let you know how it goes.
2Noob4U said:
I'll give all this a try. Do you use PDANet with or without HTC Sync? I was pretty tired last night when I tried and eventually gave up.
Hence all the stripper references.
I have an extra SD Card from my original Mytouch. I'll give it a try and let you know how it goes.
Click to expand...
Click to collapse
Just pdanet
Alright I'll give it a whirl. I'll let you know how it goes.
-------------------------------------
Sent via the XDA Tapatalk App
Took me a day to figure this out too. Uninstall all the drivers then install pda net and reboot .. you must reboot .. then try the process . I wasn't rebooting after removing drivers and it wouldn't work until I did ..
-------------------------------------
Sent via the XDA Tapatalk App
You should really have looked at the other thread on this already. Any driver will work, as long as you can get "adb devices" to show your phone when the phone is booted normally. Whats worked for many others, especially myself after 4 days of trying, was using a different, freshly formatted SD card. Good luck.
To no avail!
Just tried again. Tried without rebooting the computer the first time and "offline" would hang for a little longer than before. Still wouldn't stay. Should I have tried recovery a few more times? (I did try about three times.)
Uninstalled and reinstalled everything. Then tried "loop". "offline" doesn't even show up. Tried an old SD card too after I reformatted it. Does it matter the size of the SD card?
fermunky- I've been following your posts pretty regularly and I think I'm having the same problem. Yes I do have ADB devices showing up if the phone is on normally and running through the SDK. Had a problem for a while where it wouldn't recognize the device, but it does now.
C:\>cd android\tools
C:\Android\tools>adb devices
List of devices attached
HT05PPS07559 device
If I do figure this out I want to post up a step-by-step in this thread of what exactly I did to make it easier on people like myself.
It goes like this
C:\Android\tools>adb devices
List of devices attached
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
HT05PPS07559 offline
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
HT05PPS07559 offline
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
HT05PPS07559 offline
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
HT05PPS07559 offline
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
HT05PPS07559 offline
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
HT05PPS07559 offline
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
Is there a way to catch it offline?
It is a hit or miss deal. Some times it works, some times it doesn't. I ran into the issue while rooting mine and just kept at it till I succeeded. One plus is that after you root you never have to worry about it not detecting the device properly.
sk8rbebop said:
It is a hit or miss deal. Some times it works, some times it doesn't. I ran into the issue while rooting mine and just kept at it till I succeeded. One plus is that after you root you never have to worry about it not detecting the device properly.
Click to expand...
Click to collapse
Am I doing it right overall though.
1. Switch out SD card right before getting into recovery so there is absolutely nothing on the SD Card. (I've noticed if you let it boot it puts a LOS.DIR file or something of that sort.
fermunky had a similar problem and said once he installed everything a certain way he got it "offline" right away.
Is there a step-by-step I should be trying? Maybe another post I haven't read yet?
I'll keep trying, but it's kind of seeming like a lost cause. I've only been trying 2 days (Ha ha) After I surpass 4 days or so I'll give up and wait for Wes for the hook up.
Money for him!
Ultimate fix for device detection!!!
Uninstall EVERY driver (USBdeview) for anything android, i mean everything.
Installl HTC SYNC for espresso(any other software, PDAnet, Android Explorer.... needs to go). Dont let any drivers install while the phone is on!
Power off the phone and then plug your usb into it (phone needs to be usb debugg on and in sync mode).
Boot phone into the bootloader and the only driver it will install is the ADB driver which , without loop or multiple recovery boots or anything the phone will be detected.
I tried EVERY method in these forums and this worked perfect , went straight to pushing files, and only took 20 minutes to get it all the way to slidemeroot2. works great and everytime i need clockwork i can push the update without the problem of the device not being detected even after all the other drivers installed when i rebooted the phone. It seems that the other drivers were killing the adb function???? dunno, but i no longer have an undetected device, ever!
Also, i suggest if you want to get back into clockwork easily, plug in the phone while in normal operation mode and the adb reboot recovery that joker.
Hope this helps some, and thanks to all that have gotten us this far.
Thanks
mtjnkee said:
Uninstall EVERY driver (USBdeview) for anything android, i mean everything.
Installl HTC SYNC for espresso(any other software, PDAnet, Android Explorer.... needs to go). Dont let any drivers install while the phone is on!
Power off the phone and then plug your usb into it (phone needs to be usb debugg on and in sync mode).
Boot phone into the bootloader and the only driver it will install is the ADB driver which , without loop or multiple recovery boots or anything the phone will be detected.
I tried EVERY method in these forums and this worked perfect , went straight to pushing files, and only took 20 minutes to get it all the way to slidemeroot2. works great and everytime i need clockwork i can push the update without the problem of the device not being detected even after all the other drivers installed when i rebooted the phone. It seems that the other drivers were killing the adb function???? dunno, but i no longer have an undetected device, ever!
Also, i suggest if you want to get back into clockwork easily, plug in the phone while in normal operation mode and the adb reboot recovery that joker.
Hope this helps some, and thanks to all that have gotten us this far.
Click to expand...
Click to collapse
Haven't tried this yet.
Do it in a few hours. I've been at this all day and need some food and beer! Beer always makes computer/smartphone problems disappear.
sorry to be "that guy" but there are already 5 threads about this issue also, there is a questions and answers thread that this should have been posted in instead.
Straight to "recovery" not "offline"!
Ok is this good or bad? It's not what the video nor website says, but it's different and different is good!
Just lists the HT........ recovery over and over??? Can I start everything from here?
Dude if this works I'll buy you a beer!
I'd be glad to move it.
HighRidas said:
sorry to be "that guy" but there are already 5 threads about this issue also, there is a questions and answers thread that this should have been posted in instead.
Click to expand...
Click to collapse
No biggie man. Just wanna figure it out and you can move this at will if you like.
If you have it in recovery, hit volume up and power. It should display the recovery menu. Try pushing the update file over.
-------------------------------------
Sent via the XDA Tapatalk App
sk8rbebop said:
If you have it in recovery, hit volume up and power. It should display the recovery menu. Try pushing the update file over.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Tried... It wouldn't push said failed
Then it is an issue with your PC. Do what mtjnkee said and uninstall everything Android. Then use HTC Sync's drivers.
okay, I devoutly hope someone can help me here, because I'm at my wit's end with this. I'm using windows 7x64. I followed the instructions in THIS thread first(after installing the android sdk directly from the main website ), and got through everything okay, but when I try to do anything with adb(adb devices, for example) I get
"
*Daemon not running, starting it now on port 5037*(this does successfully start the adb.exe process)
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon*
"
Here's what I've tried so far:
1. Killing and restarting the adb.exe process, both with task manager and with adb kill-server(which is the only adb command I've found that does anything other than return an error message)
2. reinstalling both the drivers posted in this thread and those at nookdevs
3. rebooting both the computer and the nook color multiple times.
4. deleting all SDK files and both re-downloading and re-installing.
5. deleting every file I could find and the drivers and following the Nookdevs instructions. same problem
6. using the adb_wireless app, where it tells me to use adb connect <iP address> after running the app. same error message appears. Because of this step I'm less inclined to believe that it's a driver error, since the wifi app bypasses the USB driver, at least as far as I understand. I do, however, believe my drivers are installed correctly, I have ADB Composite android device in the device manager
The only google results I got with this error(for different devices) referred to the port adb needs being locked in to something else, but that doesn't appear to be the case here, I see nothing running on port 5037 in netstat
Thank you for taking the time to read my short novel, and I appreciate the help.
*shameless bump*
seriously though, 65 views and not a single person with even a suggestion? would this be better off in a different portion of the forums? Any advice at all?
dumb question, but with out the NC plugged in, when you type in "adb devices", what get's returned?
if you get that error message, than that's a config symptom.
Hey i'm no pro and got adb to work on accident...What i found is that the android sdk folder needs to be in your user folder. So when i go to start and click my user name my android sdk folder is in there with my downloads folder, desktop folder, and music folder. Makes sense? ALso any thing i push to my device i put into that folder in the tools directory. I found that that fixed most of my problems as i had the folder in the root of my c drive. Let me know if that helps.
No luck there, but thanks for the reply anyway. gives me the same error. I suspect in your case that you were not getting into the c:\android-sdk-windows folder and moving it to your username folder fixed that problem because that's the default path when you open a cmd prompt. Thanks for trying, though
Last thing i can think of is maybe your firewall? Kill it for a few mins and see what happens.
Still happens when the device isn't connected. I agree that its a config error rather than a driver issue. Also, disabling my firewall has no effect. Thanks for the suggestions though
Sent from my NookColor using XDA App
I have the same
nicbennett said:
*Daemon not running, starting it now on port 5037*(this does successfully start the adb.exe process)
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon*
Click to expand...
Click to collapse
W7/64.
ADB worked for me for months. I used it regularly. The last thing I did was *trying* to use Wireless ADB Widget and issueing ADB TCPIP command. I have made no changes to the system.
The error occurs when no device device connected. Same error when device IS connected.
-Downloaded ADB/SDK again to a different directory, same error
-Updated USB driver and SDK components, same error
-Disabled all firewall/anti-malware/anti-virus, same error
-Rebooted multiple times, same error off boot
-Port 5037 is not bound by any app or process
-ADB, upon failed load, is not listed in Taskmgr, nothing to kill
-Deleted temp files
-Issued at prompt: ADB Disconnect, ADB USB, ADB devices: All return same error as above
-Issued at prompt: ADB kill-server, only prompt returns
Read lots of posts on the web, nothing helps.
I am really interested in a solution and would like to understand what is causing the problem. If in fact it is a configuration issue, where is the ADB config file?
Thanks.
Edit: I am running the command prompt as an administrator.
not sure what was causing the issue, I ended up reformatting my HD and re-installing, it worked fine after. Sorry I couldn't be of more help, I looked everywhere for about 2 weeks and didn't find a thing that worked
nicbennett said:
not sure what was causing the issue, I ended up reformatting my HD and re-installing, it worked fine after. Sorry I couldn't be of more help, I looked everywhere for about 2 weeks and didn't find a thing that worked
Click to expand...
Click to collapse
Wow... I would hate to have to rebuild my computer just to get ADB back. I will post this in the Evo forum and see if there is some help.
Edit: Started a new thread in Evo forum:
http://forum.xda-developers.com/showthread.php?p=10730809#post10730809
Okay, I have a permarooted MT4G with S=Off, and I want to use the gfree method to unlock my SIM and get the universal CID while I'm still on the stock kernel. All of the guides I see for that push the gfree files using the ADB.
Problem: I cannot get the Android SDK to recognize my MyTouch 4g. (SEE UPDATE)
I followed this guide http://forum.xda-developers.com/showthread.php?t=834748 to try and set up the ADB to no avail. This is what I did:
-- Downloaded the SDK, booted it up, let it update. Booted it up again, let it update EVERYTHING (took like 30 minutes) again. It has no more updates to install.
-- I tried adding adb as an environmental variable in windows, but the command prompt, no matter where I start it from, does not recognize 'adb' as "an internal or external command, operable program, or batch file." (works now)
-- The HTC Drivers that came with my device have been installed on my computer. So, I uninstalled them, only to have windows reinstall them as soon as I plug the device in (I'm running Windows 7 x64 home edition, Build 7601).
I tried going here http://forums.t-mobile.com/t5/HTC/HOW-TO-Get-ADB-to-recognize-your-myTouch-4G/m-p/540017 and using their technique, no dice. My computer has the exact same drivers as when I started, and I have a digital paperweight of a SDK. (see update)
UPDATE: I now have a working ADB (big thanks to TrueBlue_Drew and his guide for us noobs) that recognizes my MT4G, but I have another issue:
FINAL QUESTION: Now that my MT4G is showing up in ADB, I realized I screwed up again when I discovered a "Android 1.0" item in the misc. section of my Devices window in Control Panel. It currently says that Android 1.0 needs troubleshooting and the drivers aren't working. I tried to direct windows to the usb drivers I downloaded from the both of the guides I've used, but windows wouldn't accept either one. Am I using the wrong drivers? Which ones should I tell windows to install? Should I even worry about it since adb is working? Any help on that end would VERY MUCH appreciated.
If you are using true blues method are you changing your target folder to c:\adb?
Sent from my HTC Glacier using Tapatalk
neidlinger said:
If you are using true blues method are you changing your target folder to c:\adb?
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
Do you mean the target of the environmental variable? If so, then no, because the name of the folder is android-sdk-windows, making the target C:/android-sdk-windows/tools, unless I'm totally off-base, which is probably what's happening.
Still, I don't think the target is C:\adb, cause I don't have anything in the root of my C drive that's named adb
corruptsmurf said:
Do you mean the target of the environmental variable? If so, then no, because the name of the folder is android-sdk-windows, making the target C:/android-sdk-windows/tools, unless I'm totally off-base, which is probably what's happening.
Still, I don't think the target is C:\adb, cause I don't have anything in the root of my C drive that's named adb
Click to expand...
Click to collapse
Is the adb.exe file in your tools folder? Also you should change the name of your SDK folder just so that its easier to type in the terminal. I made mine simply ANDROIDSDK.
Sent from my HTC Glacier using XDA App
Have you installed the drivers successfully? Here's what I do and it's worked on multiple computers and on both Windows 7 and XP:
- Install SDK
- Turn on USB Debugging on the phone.
- Plug the phone into the computer and let it try to install some stuff. Ignore any dialogs saying there were errors
- Mount the SD card and run the HTCDriver.exe file that came on the sd card when you got the phone.
- Unplug it from the computer and plug it in again.
- Open a command prompt and navigate to the tools subfolder of the android sdk. Run adb devices. (Even if the first time doesn't return your device's serial number, it should say that it's installing more drivers. Once that completes, adb devices should return your S/N and you should be good to go.)
So close, yet...
TJBunch1228 said:
Is the adb.exe file in your tools folder? Also you should change the name of your SDK folder just so that its easier to type in the terminal. I made mine simply ANDROIDSDK.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Actually no, adb.exe isn't It has a .txt named "Adb has moved," not really sure how to proceed from here; I downloaded the SDK that was in the topic I linked above, and just allowed it to update. More below, and thanks for the response.
jdkoren said:
Have you installed the drivers successfully? Here's what I do and it's worked on multiple computers and on both Windows 7 and XP:
- Install SDK
- Turn on USB Debugging on the phone.
- Plug the phone into the computer and let it try to install some stuff. Ignore any dialogs saying there were errors
- Mount the SD card and run the HTCDriver.exe file that came on the sd card when you got the phone.
- Unplug it from the computer and plug it in again.
- Open a command prompt and navigate to the tools subfolder of the android sdk. Run adb devices. (Even if the first time doesn't return your device's serial number, it should say that it's installing more drivers. Once that completes, adb devices should return your S/N and you should be good to go.)
Click to expand...
Click to collapse
Yeah, the problem is that my PC doesn't list any errors when I plug it in. BUT BIG NEWS, I followed the ADB for noobs guide (http://forum.xda-developers.com/showthread.php?t=928370), and I realized, as I said above, that my adb.exe file was nowhere to be found, so I used the one from the noob guide, and it could recognize my device in ADB. BUT it could not recognize my device in fastboot, so after much frustration, I decided to uninstall the drivers and reinstall using pda.net. Whatever it did, it worked, because adb and fastboot both show my serial number under devices. Thanks to the both of you for your help.
FINAL QUESTION: Now that my MT4G is showing up in ADB, I realized I screwed up again when I discovered a "Android 1.0" item in the Misc. section of my Devices window in Control Panel. It currently says that Android 1.0 needs troubleshooting and the drivers aren't working. I tried to direct it to the usb drivers listed in the both of the guides listed above, but windows wouldn't have it. Am I using the wrong drivers? Which ones should I tell windows to install? Should I even worry about it since I can use adb anyhow? Any help on that end would VERY MUCH appreciated.
I am trying to root my D802 device according to the following thread.
http://forum.xda-developers.com/showthread.php?t=2448887
I can find my device with adb devices. good. Then leaving the cmd window open, I double click root.bat: a new window pops up asking me to press any key. Doing so immediately closes the root.bat window and of course doesn't root the device. Does anyone has any clue what's wrong?
I have D802. Windows xp. Installed usb drivers. Enabled debugging mode.
I have tried to run the bat as administrator as well as limited privilege user. No difference.
PLEASE HELP!!!!
Same Problem
I am having same exact issue..windows 7 would love some help on this! Just need root for adblock and I am set this device rocks! +rid bloatware but thats a given.
eadred said:
I am trying to root my D802 device according to the following thread.
http://forum.xda-developers.com/showthread.php?t=2448887
I can find my device with adb devices. good. Then leaving the cmd window open, I double click root.bat: a new window pops up asking me to press any key. Doing so immediately closes the root.bat window and of course doesn't root the device. Does anyone has any clue what's wrong?
I have D802. Windows xp. Installed usb drivers. Enabled debugging mode.
I have tried to run the bat as administrator as well as limited privilege user. No difference.
PLEASE HELP!!!!
Click to expand...
Click to collapse
Well, glad to not be the only one. Let's find what we have in common, maybe we'll find where it comes from. Do you also have windows xp? Have you by any chance windowblinds installed? Have you run as administrator? Anything particular otherwise?
Same Problem
I have Windows 7 and no windows blinds...I have tried different ports and also ran as administrator. I have successfully rooted OG Droid, Droid Bionic , and Galaxy Nexus. I think I got spoiled by how easy the Nexus was to root and change roms. Love the G2 just need to get the root to stick. Every time I hit a key to continue from root bat the command window closes. I was able to read quickly a line that says unknown error has occured. Not sure why this is happening. I have tried two different drivers LG VZW_United_WHQL_v2.11.1.exe and LGUnitedMobileDriver.exe with no luck.
Using the application usbdeview, I can't see the lg driver even though I have installed it. Is it the same for you?
Actually a lg driver is indeed listed
LGE Android Phone AndroidNet Sooner Single ADB Interface Vendor Specific No Yes No No 02231cddcf4eb680 19.10.2013 19:25:05 19.10.2013 23:37:42 1004 631f 2.32 ff 42 01 andnetadb ADB Interface DriverNet lgandnetadb.sys USB Google, Inc AndroidNet Sooner Single ADB Interface 3.10.0.0 USB\Vid_1004&Pid_631f\02231cddcf4eb680
Same Problem
The drivers say installed correctly......in the command window after you check adb devices it comes back with model number and more numbers. When it looks for the device and carrier I get /f was unexpected at the time. Thinking about uninstalling all the drivers and trying for the umteenth time. You running any virus protection wonder if that has any effect?
maclv said:
The drivers say installed correctly......in the command window after you check adb devices it comes back with model number and more numbers. When it looks for the device and carrier I get /f was unexpected at the time. Thinking about uninstalling all the drivers and trying for the umteenth time. You running any virus protection wonder if that has any effect?
Click to expand...
Click to collapse
Not sure what you mean. On my side, if I write adb devices in a command prompt, I only get one line of numbers and beside it: 'device'. And that's it. Do you get additonal infos?
When I run the root.bat, I can hardly read the text before it closes, but from what I saw and completing with the text that you can get by editing the root.bat, I tend to think that the following is written before it closes:
Looking for device...
.\adb.exe wait-for-device
Determining carrier...
On a chat before, someone suggested me to right click the root.bat and clic edit to view the content of the bat. And then manualy reproduce in adb by pushing the necessary files and such... But I haven't yet given hope that it works with the bat. But maybe you feel like giving it a shot.
I have ESET as antivirus
Same Problem
No luck manual editing the root bat. When I type adb device it list VS980_4G - and a set of numbers
I was wondering if I should try another root method. I have seen on an italian forum someone who rooted with a chinese method. I have no time right now, but I might test it in a few days.
http://translate.google.com/transla...&hl=en&langpair=auto|en&tbb=1&ie=windows-1252
Btw in which country are you? I bought my mobile phone from digitec in switzerland.
I bought mine from Verizon in the US. Deleted all previous drivers....trying fresh install see if that helps
Sent from my VS980 4G using Tapatalk
maclv said:
I bought mine from Verizon in the US. Deleted all previous drivers....trying fresh install see if that helps
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
please let me know if you get through. I'm stuck and willing to return the device. it's killing me
Tried on another computer. Was done within second. It will remain a mystery why it didn't work on mine. But hey, done is done! :good:
I will try on another cpu hmmmm
Sent from my VS980 4G using Tapatalk
hit windows key+r,enter cmd then hit run.
then navigate via cd c:\folder\folderthatcontainsroot.bat
then open root.bat by typing it in cmd.
that should stop tje autoclosing of cmd when opening via windows Explorer.
Sent from my LG-D802
Thank you for the tip. I was able to get root switching to a different cpu. .but glad I will be able to use my main cpu in the future. Thank you both for the help.
Sent from my VS980 4G using Tapatalk