Database Users

[Q] EVo user trying to root my girls epic

Hey guys I an having the darnest time root this guy should be easy with these one clickers programs.
Pretty sure its a driver thing, note I can see the device when in cmd and doing the adb devices that shows up. just gets hung up at the end there.
attached a pic of what the cmd line looks like
anybody have the current drivers, googling for them just yields me to forum posts asking where the drivers are

thirty views and nothing

ok its not a driver issue if your loading root.sh (the big block of text) the issue is that the adb server isnt starting back up in time in order for your device to be recognized. solution? open up the bat file and copy and paste the commands one at a time; or if you have a linux/osx computer try doing it there with my scripts in my sig

couple ideas..
1.open up the run.bat file in notepad or similar and go through all the commands manually, that way you have control on speed of commands and allow enough time for adb to startup again.
2. open up the run.bat file and increase the wait time in the script.. -w 3000 or something like that..
i would suggest you do commands manually. The one-click root did not work for me but doing things manually worked right away.

How to do it
Hey man this is how I got it to work. I was having all the problems device not found etc etc. Have been trying since Sunday. What I finally did after installing the drivers was restart the computer and Phone. After that i tried to run the program it failed with device not found again so i unplugged the usb cable from the phone and closed the cmd window. And also brought up Task manager and killed the adb.exe process. then i reran the run.bat file and this time when it gets to the adb restart relogin apart i killed the SMALLEST ADB.EXE IN THE PROCESS TAB OF TASK MANAGER and that is when it finally got it to work. Had to do the same when I tested it with the uninstaller. So that seems to work. If anyone has any questions feel free to pm me.
But thank god it finally worked.
David
other people have done this and it worked for them also.

I tried all kinds of stuff ultimately I ended up using an xp machine. I later remembered the whole xp mode in windows 7 but didn't actually try it ... win7 just gave me a hard time although the post about changing the amount of time to restart adb makes sense
Sent from my SPH-D700 using XDA App

will try all of that thankyou gents

Anyone know of an idiots guide?

I've just about given up. I downloaded all these programs, drivers, other stuff. I thought I had all the required software. I tried to run adb.exe and it just opens a command prompt and closes right away. I've tried searching and all the guides says download this....this..and this..once you have it all. And it starts from there.
The problem is i downloaded everything and I don't know if its working properly to start adb.
I hate this.
I've even thought about downloaded a whole other OS and running it from my USB drive to see if it's easier.
Anyone know of a good how to video?
I know that's what i'll be making as soon as I get this up and running.

Are you actually running adb through a command prompt or just double clicking the exe?
Sent from my T-Mobile G2 using XDA App

CMP
take a look.
http://www.youtube.com/watch?v=-rTOy5oN0GM

use cmd to run it

Start -> Run -> Type cmd -> Enter
cd whatever/directory/adb.exe/is/in
adb

you should just add the android tools directory to your PATH makes life much easier.
Sent from my T-Mobile G2 using XDA App

Yep editing the path got it to work for me.
Sent from my T-Mobile G2 using XDA App

They are aren't they? The vid shows them in there.
Sent from my T-Mobile G2 using XDA App

if you are having that much issue setting the correct path, just go to your system 32 and copy over the CMD.EXE to the folder you are working in with Android. And then launch CMD from there.
Or just type into command prompt
PATH = %PATH%;C:/Android/Folder/Youre/Working/With/
EDIT:
I just watched your video. You have some problems in there
First, you aren't setting a new path, you are (attempting) to change your working directory in that video, however you are not doing it right.
You have to use the 'cd' command
C:\Current\Work\Space > cd C:\Change\to\this\space
C:\Change\to\this\space > adb devices
bleh bleh bleh bleh
But it would be better to just do the above method.

In most cases, the instructions are pretty clear. If you read the instructions on installing the SDK, it tells you how to set the path.
http://developer.android.com/sdk/installing.html
If you follow instructions, then you should be good to go.
If not, then you should be able to do something like a google query for "set path variable windows < whatever kind of windows you're running >"
If you're having a problem getting that stuff done, then maybe you should rethink rooting your phone. I don't know that anyone has bricked a G2 yet, but LOTS of folks bricked G1s. I think it's only a matter of time before someone figures out how to thoroughly break a G2.

"Just to add, if you take adb.exe and adbwinapi.dll and copy or move them to the \windows\system32 directory you can run adb from any dos directory prompt."
Also, add the "ADB" directory path as a system variable in windows...
To do this right-click on "My Computer" and select Properties. Next select the Advanced tab(Advanced Settings in Vista) then select Environment Variables.
Click "New" under System Variables and add the following:
Variable: adb
Value: C:\android\tools
If you happen to upgrade to Win7 you can easily open the CMD by shift right-click inside the window itself.....applying the path automatically for you.
You will also have too use these drivers located here: http://forum.xda-developers.com/showthread.php?t=802316
or
Use notepad++ to edit that file and add the following lines to the "google.ntxhe "" and the "google.ntamd64" sections:
Code:
;T-Mobile G2 %SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C91 %CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C91&MI_01 ;
Save the file, reinstall drivers, and done...
Click to expand...
Click to collapse

smasraum said:
In most cases, the instructions are pretty clear. If you read the instructions on installing the SDK, it tells you how to set the path.
http://developer.android.com/sdk/installing.html
If you follow instructions, then you should be good to go.
If not, then you should be able to do something like a google query for "set path variable windows < whatever kind of windows you're running >"
If you're having a problem getting that stuff done, then maybe you should rethink rooting your phone. I don't know that anyone has bricked a G2 yet, but LOTS of folks bricked G1s. I think it's only a matter of time before someone figures out how to thoroughly break a G2.
Click to expand...
Click to collapse
Thanks, looks like I'll be waiting it out. I didn't think it took this much know how to get sdk and adb running properly. I was able to change the path but ran into another brick wall. I type in abd devices to see if it was recognized and nothing. Like i said, I'll be waiting it out until a more permanent route can be found, and more support for rooting is available. Besides I don't think anyone wants to hold my hand and walk me thought the whole thing. It gets annoying, believe me I know. I'll be doing a how to video once I learn to get it all working and when a permanent root is available. I'll learn on XP and make the video using my Win 7.

ddgarcia05 said:
Thanks, looks like I'll be waiting it out. I didn't think it took this much know how to get sdk and adb running properly. I was able to change the path but ran into another brick wall. I type in abd devices to see if it was recognized and nothing. Like i said, I'll be waiting it out until a more permanent route can be found, and more support for rooting is available. Besides I don't think anyone wants to hold my hand and walk me thought the whole thing. It gets annoying, believe me I know. I'll be doing a how to video once I learn to get it all working and when a permanent root is available. I'll learn on XP and make the video using my Win 7.
Click to expand...
Click to collapse
The G2 isn't included in the current adb drivers that you download separately/with the SDK. You have to edit the inf file to have the G2 recognized. There has been at least 1, maybe a few threads with the lines to add here. I think there's a thread titled something like "I can't get adb to work with my phone" or something like that.

looks like i was doing it right. I was typing "abd" instead of 'adb" it founy device.
Now I guess the have to start sending the files over....
I typed "adb devices" and it picked up my device. with my phone's id number.

I am also about to give up. Some of us are new to Android.. we don't understand SDK and ADB and all these other programs. I do plenty enough reading.. but for some reason can't get these programs to run on Windows 7 x64.
I mean is their a newbs guide for the G2.. for rooting and such?

Yeah there is but you have to read like three guides and watch two videos to fnd everything you need. Ill try to make a quick how to after I finish up mine. I just have to push the apps/install the apps. Did you find the java jdk version. And do the commands on your computers cmp?
Sent from my T-Mobile G2 using XDA App

I always used this guide:
[GUIDE] ADB, Fastboot, and Nandroid for Noobs
Hope it helps
Use the drivers in post 11 in this thread
Unless you rooted your G2.........adb shell will NOT work.
ADB shell needs root access

Thanks, I have already rooted my phone. Unfortunately my wifi tethering doesn't work. It always says no network access so I'm just going to leave the phone as is until the update comes in.
Sent from my T-Mobile G2 using XDA App

ddgarcia05 said:
Thanks, I have already rooted my phone. Unfortunately my wifi tethering doesn't work. It always says no network access so I'm just going to leave the phone as is until the update comes in.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
why not use VISIONary app to root the phone for you?

konoplya said:
why not use VISIONary app to root the phone for you?
Click to expand...
Click to collapse
At the time it wasn't available, but I'm using it now.

[Q] ADB not recognizing, please help

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.

How to install LG G2 drivers

I am generally good at rooting any android phone. I am having a hard time locating the drivers for the VZW LG G2. I have the zip file from the post on how to root the phone, but I am not sure which file to install.
Any input would be appreciated.

If they aren't auto detected and installed after a reboot with phone plugged in, goto device manager, locate the phone and manually update driver pointing it to the LG folder full of drivers. To get the adb interface working, you may need to be in the internet connection mode with the ethernet option selected. Can't remember if that was the case or not.

iowabowtech said:
If they aren't auto detected and installed after a reboot with phone plugged in, goto device manager, locate the phone and manually update driver pointing it to the LG folder full of drivers. To get the adb interface working, you may need to be in the internet connection mode with the ethernet option selected. Can't remember if that was the case or not.
Click to expand...
Click to collapse
I needed to install LG VZW_United_WHQL_v2.11.1 then go to LG website and download drivers from the G2 support page. I couldn't upload the exe file. Restart computer and all went well. I had same issue and struggled to solve.

So I figured out how to install the drivers but when I go to command prompt and type"adb devices" it does not recognize it as a command.

So I figured out how to install the drivers but when I go to command prompt and type"adb devices" it does not recognize it as a command.

Bxrider117 said:
So I figured out how to install the drivers but when I go to command prompt and type"adb devices" it does not recognize it as a command.
Click to expand...
Click to collapse
You must have the sdk with adb installed before you do that part. Browse to that directory, find adb, shift right click, open command prompt here. Then do 'adb devices'. You'll see serial # on left and 'device' on right. It's working then. If you get 'offline' on right, you need to update your adb.

i'm having the same issue. i'm trying to root, and it won't list it at all, and i'm not getting the debugging icon on top. no serial number popping up on the abd devices and i just tried with both 3.8 and 3.10 drivers. anything?

If I remember correctly I had to go to settings>pc connection>select USB connection method and then choose Internet connection, then choose modem in order to get the debugging icon to appear.
Sent from my VS980 4G using xda app-developers app

I'm having trouble with my PC not recognizing my phone at all. It says USB device not recognized. I'm on Windows 7 64bit if that matters.
Sent from my LG-D801 using xda app-developers app

thanks!

bigox said:
I'm having trouble with my PC not recognizing my phone at all. It says USB device not recognized. I'm on Windows 7 64bit if that matters.
Sent from my LG-D801 using xda app-developers app
Click to expand...
Click to collapse
Most likely it's because you don't have the right drivers installed. Try installing these http://g2-lg.com/download-lg-g2-android-usb-drivers-ver-3-10/.
Sent from my VS980 4G using xda app-developers app

The drivers aren't working for me so i will link where you can get the drivers from the actual website. Please note: this link is for Tmobile D801 but you can search for your device on there.
http://www.lg.com/us/support-mobile/lg-D801

LG's website has drivers for D800 and D801. I'm looking for D802 drivers. Where can I find them or which are compatible?

The Universal device drivers aren't universal?
Sent from my VS980 4G using xda app-developers app

cggorman said:
The Universal device drivers aren't universal?
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
Where can I find Universal drivers? Not on LGs website.

I installed this:
http://forum.xda-developers.com/showthread.php?t=1379875
And after that it worked fine. I have a ls980, so the att and t-mobile don't work for me. This did.

This took me a while to sort out. There is a certain driver package for the verizon phone. The drivers listed here dont seem to work for me. I'm using win 7. Here is what I needed to use, then everything just came together - LG VZW_United_WHQL_v2.11.1
These can be downloaded at LG's site. Make sure you search for drivers pertaining to the model number of your phone.
Hope this helps someone

EVOme said:
You must have the sdk with adb installed before you do that part. Browse to that directory, find adb, shift right click, open command prompt here. Then do 'adb devices'. You'll see serial # on left and 'device' on right. It's working then. If you get 'offline' on right, you need to update your adb.
Click to expand...
Click to collapse
I am having the same issue..what is the sdk with adb installed and what directory do i browse to? sorry for the noob questions, ive always had nexus's, so much easier to flash recoveries etc

LG Drivers failing to install
I Install LGUnitedMobileDriver_S50MAN310AP22_ML_WHQL_Ver_3.10.1.exe from LG website, it installs and I get a "successful" message from the software package. However, shortly after windows pops up a bubble with "not successful". Details:
Uninedntified Device - No Driver Found
Creative Game Port - Failed
Plug in phone and select “PC Software”, since none of the other options make any sense (USB charge, Media Transfer, Tethering, and Picture Transfer). Sidebar: None of the other options seem to change anything even when tried. "Media Transfer" is the only one that seems to actually install something successfully, but nothing changes with the device list. Back on track: Get a new windows “installing” bubble. Shortly after I get another “not successful” message with the following:
MTP USB Device – Failed
I go to Devices and Printers, select the phone, and look in the properties. Click “update driver” and pick the LG folder in Program Files. It says “driver already installed”.
Rebooting the computer accomplishes nothing.
I’ve tried several full uninstalls.
No matter what I try, if I run “adb devices”, I get “List of Devices Attached” then my prompt back, meaning none found I assume.
Yes I have turned on dev mode on the phone and I get the debugging icon when the USB cable is plugged in. I’m on Win7 64. WTF is wrong with this driver?
Thanks for any help you can give!

Uncheck usb debug? Had this on my htc one x. Maybe helps
Sent from my LG-D802 using XDA Premium 4 mobile app

VS980 root troubles

Hey guys ive been pretty stoked to root and rom my g2 now that im bored of LG's UI haha i have been trying to use the IOroot method but something about the drivers is giving me such a hard time! i installed them but every time i open a command window and type in "adb devices" nothing is coming up so obviously its not being able to read my device which isnt alowing me to root my phone any help would be greatly appriciated! thanks in advance

I was having trouble, finally went to LG site to download drivers
Sent from my VS980 4G using XDA Premium 4 mobile app

adb is a special android thing. You need to install it to just use it anywhere. Do this:
1. Create a folder on your desktop (you can call it root or whatever you want).
2. Extract IORoot into folder created in step one.
3. SHIFT RIGHT CLICK and do "open command window here" (This is the most important).
4. type
Code:
adb devices
5. if you devices shows run the root.bat file to root your device.
Look at this for a little more help.
http://forum.xda-developers.com/showthread.php?t=2515978

djraimondi said:
adb is a special android thing. You need to install it to just use it anywhere. Do this:
1. Create a folder on your desktop (you can call it root or whatever you want).
2. Extract IORoot into folder created in step one.
3. SHIFT RIGHT CLICK and do "open command window here" (This is the most important).
4. type
Code:
adb devices
5. if you devices shows run the root.bat file to root your device.
Look at this for a little more help.
http://forum.xda-developers.com/showthread.php?t=2515978
Click to expand...
Click to collapse
IVe done this so many times haha... the problem is when i type that into the command window nothing comes up under listed devices and ive downloaded and installed the drivers from several different locations including the LG website... could it be the ethernet thing that im missing? because thats the only thing i dont believe ive done cause this is a hastle xD ive had no problems rooting in the past

Cyko.Tech67 said:
IVe done this so many times haha... the problem is when i type that into the command window nothing comes up under listed devices and ive downloaded and installed the drivers from several different locations including the LG website... could it be the ethernet thing that im missing? because thats the only thing i dont believe ive done cause this is a hastle xD ive had no problems rooting in the past
Click to expand...
Click to collapse
Do you have the phone listed correctly for what mode to be in when you plug in the USB cord???

hd-renegade said:
Do you have the phone listed correctly for what mode to be in when you plug in the USB cord???
Click to expand...
Click to collapse
i have tried both with Charge only mode and MTP

Cyko.Tech67 said:
i have tried both with Charge only mode and MTP
Click to expand...
Click to collapse
This is just a thought, but maybe, power the phone off, power the PC off. Turn them both back on, re-read the instructions on how to root the phone. It sort of sounds like you could be missing just a little thing on the instructions. You may also try a different USB port on your PC too. I rooted mine back on iRoot 6 so I would have to think that iRoot 10 should be better then what I used.

hd-renegade said:
This is just a thought, but maybe, power the phone off, power the PC off. Turn them both back on, re-read the instructions on how to root the phone. It sort of sounds like you could be missing just a little thing on the instructions. You may also try a different USB port on your PC too. I rooted mine back on iRoot 6 so I would have to think that iRoot 10 should be better then what I used.
Click to expand...
Click to collapse
I just dont think im installing the drivers right because ive tried everyone and their mothers usb ports and ive tired it on 4-5 computers there has to be something im missing with the drivers because the process just wont start Daemon will succsesfully start running than nothing...

Cyko.Tech67 said:
I just dont think im installing the drivers right because ive tried everyone and their mothers usb ports and ive tired it on 4-5 computers there has to be something im missing with the drivers because the process just wont start Daemon will succsesfully start running than nothing...
Click to expand...
Click to collapse
It has been a while sense I rooted mine, but I think the fix for me was getting the drivers from the LG Site and using the LG Flash tool.

hd-renegade said:
It has been a while sense I rooted mine, but I think the fix for me was getting the drivers from the LG Site and using the LG Flash tool.
Click to expand...
Click to collapse
whats the flash tool for?

I think I ended up flashing back to LG stock. Sorry it has been a while sense I played with that stuff.
Sent from my VS980 4G using Tapatalk HD

I had the same issue. I installed these lg drivers, not sure if they had anything to do with it because it still didn't work. What finally worked was when I turned off debug and may have been in mtp connection. Obviously after you have to put back in debug and ethernet connection to follow the ioroot method.

dp917 said:
I had the same issue. I installed these lg drivers, not sure if they had anything to do with it because it still didn't work. What finally worked was when I turned off debug and may have been in mtp connection. Obviously after you have to put back in debug and ethernet connection to follow the ioroot method.
Click to expand...
Click to collapse
alright one more question and thanks for the fast replies guys! i appriciate it but im not to nifty with computer tech as i am Smartphone xD laptops still have an ethernet mode correct? and if so where do i go to enable it?

Cyko.Tech67 said:
alright one more question and thanks for the fast replies guys! i appriciate it but im not to nifty with computer tech as i am Smartphone xD laptops still have an ethernet mode correct? and if so where do i go to enable it?
Click to expand...
Click to collapse
Ethernet mode is in enabled in your phone. Settings > scroll to bottom "pc connection."

dp917 said:
Ethernet mode is in enabled in your phone. Settings > scroll to bottom "pc connection."
Click to expand...
Click to collapse
awesome thanks so much guys a thanks to both of you ill try it when i get home and let ya know how it went

Cyko.Tech67 said:
awesome thanks so much guys a thanks to both of you ill try it when i get home and let ya know how it went
Click to expand...
Click to collapse
Let the folks here know how you make out.

hd-renegade said:
Let the folks here know how you make out.
Click to expand...
Click to collapse
unfortunatly with ethernet on i am still getting the same results... its just not recognizing my device? at least now in the notification bar i get the notification that USB debugging is on so i guess im making progress? uggh this is getting pretty annoying any thoughts guys?

Run it directly from local drive root. IE C:/ Windows 7? Control alt delete. End the stale adb process, you should see two, one not performing sitting around 2000 kb ram and the other using ram. End that and it should force adb to kick in. I had to do this on win 7 multiple times with dif phones. It's like it locks up when finding the com port or whatever the hell it's doing. I take no blame if you screw up your device this way. I have resorted to a virtual xp for all my phone needs as not everything works in Linux.

Here's how rooted my phone with IORoot:
Unzipped IORoot to root of my hard drive
Plugged in phone with usb (make sure debug mode is enabled). When prompted to choose connection, choose modem. You should see debug icon appear in status bar. If not, choose Ethernet.
Opened IORoot folder. Hold down shift and right click an empty area and choose 'open command window'
Type adb devices. If device shows up, proceed. With normal root procedure.

Steamer86 said:
Run it directly from local drive root. IE C:/ Windows 7? Control alt delete. End the stale adb process, you should see two, one not performing sitting around 2000 kb ram and the other using ram. End that and it should force adb to kick in. I had to do this on win 7 multiple times with dif phones. It's like it locks up when finding the com port or whatever the hell it's doing. I take no blame if you screw up your device this way. I have resorted to a virtual xp for all my phone needs as not everything works in Linux.
Click to expand...
Click to collapse
simon_lefisch said:
Here's how rooted my phone with IORoot:
Unzipped IORoot to root of my hard drive
Plugged in phone with usb (make sure debug mode is enabled). When prompted to choose connection, choose modem. You should see debug icon appear in status bar. If not, choose Ethernet.
Opened IORoot folder. Hold down shift and right click an empty area and choose 'open command window'
Type adb devices. If device shows up, proceed. With normal root procedure.
Click to expand...
Click to collapse
Not sure if it matters but I am running 64 bit Windows 8
- In the instructions didn't you have to change a setting for the Com Port to get it to see the phone??
- Did you ever get the prompt on your phone to accept the Connection. I can not remember what it was, but it only comes up once, and I am not referring to the USB connection IE Ethernet??
- Are you sure you have Developer Options turned on?? The step where you keep tapping on the Developer thing and then the phone finally gives you the Developer Options??