Hey guys. Please forgive anything dumb I might say, and also that I've searched a bit for this, on google and on xda, but seem to be getting a bit confused. First, let me say, I rooted my evo months ago, using Unrevoked 3.21. I never really have had to use ADB for anything, I use terminal emulator or Root Explorer for anything I have needed to do. My friend just got an Evo today, and I'm assuming it will come with 3.70 software and hboot 2.1. She wants me to root it for her, which I will do, once I feel comfortable with the steps I need. I have followed ziktroniks thread of how to root the new hboot since it was called "like a boss" edition, and I feel like I shouldn't have a problem doing that. I can follow instructions pretty well. The problem I'm having is, since I rooted using Unrevoked 3.21, and I've never had to use ADB, I'm a little confused about what I need to do, and what drivers I need to install to get ADB working. I know that at the time I rooted, I installed Unrevoked hboot drivers on my computer. I downloaded the android SDK tools, but am having trouble getting it set up. When I try to run the installer, it says "android SDK relies on the Java SE Development Kit (JDK). Then it provides a link to the java website, and I downloaded and installed the JDK that it pointed me to. However, when I try to set up the android SDK, it brings me to same prompt, saying android SDK relies on Java SE Development Kit, and that i need to install it first, which I thought I already have. I'm sure it's something stupidly simple, and I feel embarassed that I haven't yet got ADB set up, but hey, I guess there's a first for everything. So if anyone could be so kind to help point me in the right direction to getting ADB set up, I'd be very gratefull for that. I've gone long enough without knowing how to use ADB, and I'd really like to get this ironed out.
My computer is running windows vista, 64 bit system, if that helps out at all.
Thanks in advance.
I just came over to check out your question from Myn's thread... I did not have the problem you mention when I set up ADB, so I cann't be of much use there.
I noticed you have WIN 64bit. You may have a hard time finding the drivers you will need for the computer to recognize your phone. If you end up needing them, PM me and I can throw them in dropbox and get a link for you. Good luck with everything.
Yeah, getting the 64 bit drivers might be a problem, but when you do it'll be easy if you remember this:
If you've used Terminal Emulator then ADB is demystified. Once you confirm the drivers are working, ADB is just Terminal Emulator on your computer.
I use Vista (I actually like it!), but I assume you have a Start Menu on W7...open it and at the bottom is the Start Search box. Type cmd and an old-style DOS prompt/box will come up. Once you've used the commands to log onto the phone (sorry I forgot them, but I'm sure they're in the directions, if not PM me and I'll look 'em up) that DOS box is exactly like Terminal Emulator.
And the rest should be easy to follow. It'll make you smile the first time the phone reboots after you issue a command on the 'puter, it did me.
Hope this helps...
[EDIT] here y'go...this is a good one...
http://forum.xda-developers.com/showthread.php?t=502010
Thanks for the quick responses guys, I've made some progress. I will post back in a few and let you know how I'm making out. Thanks again.
k2buckley said:
Hey guys. Please forgive anything dumb I might say, and also that I've searched a bit for this, on google and on xda, but seem to be getting a bit confused. First, let me say, I rooted my evo months ago, using Unrevoked 3.21. I never really have had to use ADB for anything, I use terminal emulator or Root Explorer for anything I have needed to do. My friend just got an Evo today, and I'm assuming it will come with 3.70 software and hboot 2.1. She wants me to root it for her, which I will do, once I feel comfortable with the steps I need. I have followed ziktroniks thread of how to root the new hboot since it was called "like a boss" edition, and I feel like I shouldn't have a problem doing that. I can follow instructions pretty well. The problem I'm having is, since I rooted using Unrevoked 3.21, and I've never had to use ADB, I'm a little confused about what I need to do, and what drivers I need to install to get ADB working. I know that at the time I rooted, I installed Unrevoked hboot drivers on my computer. I downloaded the android SDK tools, but am having trouble getting it set up. When I try to run the installer, it says "android SDK relies on the Java SE Development Kit (JDK). Then it provides a link to the java website, and I downloaded and installed the JDK that it pointed me to. However, when I try to set up the android SDK, it brings me to same prompt, saying android SDK relies on Java SE Development Kit, and that i need to install it first, which I thought I already have. I'm sure it's something stupidly simple, and I feel embarassed that I haven't yet got ADB set up, but hey, I guess there's a first for everything. So if anyone could be so kind to help point me in the right direction to getting ADB set up, I'd be very gratefull for that. I've gone long enough without knowing how to use ADB, and I'd really like to get this ironed out.
My computer is running windows vista, 64 bit system, if that helps out at all.
Thanks in advance.
Click to expand...
Click to collapse
I didn't use windows to root my evo, I used a mac, and I do all my java development on a debian linux box, but I think the problem may have to do with your computer using the wrong java by default. On mac and linux, this is controlled by the environmental variable $JAVA_HOME, on windows, I have to assume there is a similar variable, or registry entry - I am looking it up on google right now...
Here we go, I found it - try the directions on this page:
http://confluence.atlassian.com/display/DOC/Setting+the+JAVA_HOME+Variable+in+Windows
hopefully this helps
oh, one other thing, I noticed you said she has hboot 2.10, and I think "like a boss" technique is for hboot 2.02. I think for 2.10 you need to find a thread entitled something like "like wood on fire", or something - although I may be wrong, maybe they updated the "like a boss" thread to cover hboot 2.10 also. Just wanted to make sure you double-check.
Good luck.
Bleys43 said:
oh, one other thing, I noticed you said she has hboot 2.10, and I think "like a boss" technique is for hboot 2.02. I think for 2.10 you need to find a thread entitled something like "like wood on fire", or something - although I may be wrong, maybe they updated the "like a boss" thread to cover hboot 2.10 also. Just wanted to make sure you double-check.
Good luck.
Click to expand...
Click to collapse
Thanks for the heads up. Yea, that thread has been updated and the name has changed nearly daily. Right now it just changed to something else "The final edition" or something like that, yesterday it was "yea, yes im on top" or something like that. ha. I feel confident that I can execute the necessary commands, once i get this damn ADB up and running. I find myself getting confused. I got the java issued figured out, and installed the Android SDK started package. Im reading more before I attempt anything, but the problem I find is that half or more of the stuff I find while searching, is out dated I think. I keep landing threads and such from june and july, and i'm not sure if that's current or obsolete. **** changes so much. So where I'm at now, is the android SDK tools windows is installed, and I'm kinda at a standstill right now. Lol. I see a late night this evening.
And just to mention, to my surprise, her brand new white evo came with : hardware 004, hboot 2.02, software 3.30. I would've thought it'd come with the latest OTA update and hboot etc. Guess I was wrong. Anyways, shouldn't affect much I don't think, if I can ever get ADB to set up correctly. Any other/additional advice is more than welcomed. My pm inbox has plenty of room. THanks
Alright, I am kind of stuck here, I believe that I have everything installed and all the drivers I need, following the links you guys posted here. I open a command prompt, and when it opens initially, it reads : C:\Users\Kyle> Then I enter C:\ android-sdk-windows\tools Then the initial prompt changed from C: \users\kyle> to C:\android-sdk-windows\tools> Thats as far as I get. I tried typing adb devices, and I got 'adb' is not a recognized as an internal or external command.
Im not sure where to go from here. If anyone could point me in the right direction from here, it would be super appreciated. I feel like I'm getting very close here, I just don't know what to check next?? Thanks in advance.
Try this thread. It has a lot of ADB info.
http://forum.xda-developers.com/showthread.php?t=694250
damn, well I think I'm at a standstill for tonight. All the info you guys have posted has been very helpful, however I'm still unable to get it working. I'm pretty sure I have all the drivers that I need installed. I have usb debugging checked on the phone. HTC sync is installed, along with some other drivers that I have found while researching adb. I'm either missing something big, or I'm making stupid mistakes. I just can't seem to get it to work. Any time I type anything 'adb' into the command prompt, it says that adb is not a recognized command, internal or external. So I'm assuming that I must not have the right drivers. Also, just so I understand, if anyone could confirm this. While trying to use adb, does the phone have to be in bootloader? recovery? Booted into the OS, connected as charge only? I seem to be finding conflicting information.
First, I believe you need to get rid of HTC Sync, or at very least make absolutely certain it isn't running...it conflicts with adb.
Second, when it's plugged into USB, make sure your phone's in the "Charge Only" mode.
Third, make sure that under "Settings, Applications, Development" you've got "USB Debugging" checked.
Ok, so when SDK installed itself it should have created a sub-directory (I'm using your screen name as 2nd directory, but substitute the correct one)
C:\Users\K2Buckley\android-sdk-windows\platform-tools
In this directory should be 2 files: "adb.exe" and "adbwinapi.dll". Copy them to your windows\system32 (64?) folder. This will/should allow you to run ADB from any directory, and eliminate the need for you to add anything to your Environment Variables.
Now, if your drivers are running properly and your phone's plugged in, open the Command Prompt by going to the Start Menu, and in the Start Search box at bottom type CMD.
No matter which directory it opens in you should be able to run adb, so as a test, type
adb devices
If it's working, (and it should be), you'll see your phone's ID come up.
You can then do a directory change to whatever directory on your puter you have put all the files you're going to need for your process. For instance I would type
cd c:\users\neil\evo-rooting
That command prompt should pop up. From that point on follow your directions to push, pull, reboot, etc. whatever is called for right from that command prompt. As an example, if I wanted to "push" the file "warm22rom.zip" from that directory to the "zip" directory on my sd card, from that C:\USERS\NEIL\EVO-ROOTING command prompt I'd type
adb push warm22rom.zip sdcard/zip
And if I wanted to reboot my phone from the computer, from that command prompt I'd type
adb reboot
In fact, try that one as a test (be patient, it takes about 20-30 seconds to execute but it's a trip when your phone boots...).
I've just run through this whole process myself just to make sure it works. It does. So if it doesn't work for you, it's gotta be the drivers.
2 other quick checks:
In your computer's Device Manager should be "Android Phone" with "Android Composite ADB Interface" listed if you click the plus sign...
and/or
In Vista, when I plug the phone into the USB port, a little gray square with a white check in a green circle pops up on the right side of my task bar (you should have something similar). This is the "Safely Remove Hardware" icon, and if I double click it it opens a box that shows me what devices/drivers are installed. In that box are 2 things you need to look for: a single line that says "Android Composite ADB Interface" and a short "tree" that reads "USB Mass Storage Device, HTC Android Phone USB Device, Generic Volume - J" (this is my SD Card designation).
If you see these things, or something close, you've got it all installed right.
It's up to you now...go forth and Root, and ADB to your heart's content.
Good luck, I hope this helped.
Fail for me. I feel like a moron. Still can't get this going. Don't know what the hell I'm missing. Anything special that I'm missing about using a 64 bit system? I'm officially stumped. I don't know how much it matters, but can't seem to find any threads/guides specific to the Evo. I keep finding them for moto droid, g1, vibrant. I must be too tired and not thinking straight.
I also keep finding information saying that there should be an adb.exe file in the tools folder, as well as a couple .dll files. I can't find any anywhere on my computer, not even when I search. So does this mean I have either not extracted to the right place or something? Now I'm more lost. F*_k.
Persnlmgr said:
First, I believe you need to get rid of HTC Sync, or at very least make absolutely certain it isn't running...it conflicts with adb.
Second, when it's plugged into USB, make sure your phone's in the "Charge Only" mode.
Third, make sure that under "Settings, Applications, Development" you've got "USB Debugging" checked.
Ok, so when SDK installed itself it should have created a sub-directory (I'm using your screen name as 2nd directory, but substitute the correct one)
C:\Users\K2Buckley\android-sdk-windows\platform-tools
In this directory should be 2 files: "adb.exe" and "adbwinapi.dll". Copy them to your windows\system32 (64?) folder. This will/should allow you to run ADB from any directory.
Now, if your drivers are running properly and your phone's plugged in, open the Command Prompt by going to the Start Menu, and in the Start Search box at bottom type CMD.
No matter which directory it opens in you should be able to run adb, so as a test, type
adb devices
If it's working, (and it should be), you'll see your phone's ID come up.
You can then do a directory change to whatever directory on your puter you have put all the files you're going to need for your process. For instance I would type
cd c:\users\neil\evo-rooting
That command prompt should pop up. From that point on follow your directions to push, pull, reboot, etc. whatever is called for right from that command prompt. As an example, if I wanted to "push" the file "warm22rom.zip" from that directory to the "zip" directory on my sd card, from that C:\USERS\NEIL\EVO-ROOTING command prompt I'd type
adb push warm22rom.zip sdcard\zip
And if I wanted to reboot my phone from the computer, from that command prompt I'd type
adb reboot
In fact, try that one as a test (be patient, it takes about 20-30 seconds to execute but it's a trip when your phone boots...).
I've just run through this whole process myself just to make sure it works. It does. So if it doesn't work for you, it's gotta be the drivers.
2 other quick checks:
In your computer's Device Manager should be "Android Phone" with "Android Composite ADB Interface" listed if you click the plus sign...
and/or
In Vista, when I plug the phone into the USB port, a little gray square with a white check in a green circle pops up on the right side of my task bar (you should have something similar). This is the "Safely Remove Hardware" icon, and if I double click it it opens a box that shows me what devices/drivers are installed. In that box are 2 things you need to look for: a single line that says "Android Composite ADB Interface" and a short "tree" that reads "USB Mass Storage Device, HTC Android Phone USB Device, Generic Volume - J" (this is my SD Card designation).
If you see these things, or something close, you've got it all installed right.
It's up to you now...go forth and Root, and ADB to your heart's content.
Good luck, I hope this helped.
Click to expand...
Click to collapse
Whoa, thanks dude. I'm going to try that right now. I made my last post as you were typing that up apparently, I was ready to throw in the towel, but I'm going to try what you said. Thats very very close to what i was doing, out of all the different tutorials i was trying to follow.
I still couldn't find the .exe or .dll files, so I have no clue what happened there. I'm going to try re installing sdk all together and see if I can get this. Thanks again dude, I know it's late, I appreciate you taking the time to type that up.
. I'm going to give this a try.
And yes, by the way, the drivers listed in my "safely remove hardware" are the same as what you have there. I'm reinstalling the sdk tools now. Hopefully that adb.exe file is there. Before, all that was there was 'adb', among some other folders. I'm assuming there needs to be one that is actually 'adb.exe', correct? when i clicked on the properties of that 'adb' one that was there, it said 'file type: .exe (application)'. Is that what I'm looking for?
http://developer.android.com/sdk/index.html
that is the site I downloaded the sdk tools from, the one for windows that says 'installer ro8 windows.exe (recommended) Does that appear to be the correct one? Once i downloaded that, the installer popped up, installed everything, then sdk manager popped up, requested that I download and install some stuff (android platforms?). Once that's finished, that should be it, right? Just want to make sure I haven't been missing a step or something.
(and thanks for your patience with me, I'm learning though. all the flashing I've done in the past few months, still can't believe that I never took to the time to learn adb. now I know why people are against Unrevoked, cuz I didn't learn sh!t by doing that. A few clicks and I was rooted and flashing away!)
well. I fubared something, ha. This is becoming comical. I followed what you said. The only thing is, which I'm sure this is the issue...after sdk tools installed again, there was still no 'adb.exe' folder in platform-tools. just 'adb'. The adbwinapi.dll was there, and i copied it to "windows/system32" I copied the 'adb' to that folder as well. So either the 'adb' that i copied was incorrect, and I have no idea where that damned 'adb.exe' is at, or i was supposed to move or cut them, rather than copy. either way, i give up for tonight, need some sleep.
when I opened a command prompt, and typed 'adb devices', a windows error with a red x pops up (outside the command prompt) that reads "this application has failed to start because AdbWinApi.dll was not found. Re installing the application may fix the problem". Then I click ok.. Then it says "adb.exe has stopped working, a problem caused the program to stop working correctly. windows will close the program and notify you if a solution is available" HA. DAMn I suck.
Not thinking clearly right now, need some sleep. Thanks again, hopefully we can get this straightened out tomorrow, or later today i guess it is now, damn its late.
Edit!! whoa! My final attempt was to copy the adbwinapi.dll to windows\system (instead of system32), and i believe that worked. I typed in adb devices, and I got "list of devices attached HT0###L00069 device" I assume that's my Evo? Hooray! Thank you so much man, I cannot express how happy I am right now, ha. That adb reboot kicked ass, lol. Now I can learn some stuff.
Finally, last question. My friend (who's phone I was going to root) had to leave hours ago. I was using my phone to do this and get it working. When I go to root her phone, in theory, should it connect to adb just fine at this point? Thanks again man, you were a huge, massive help.
I suck. I had it working. For some reason, through my tiredness and confusion, I thought I had to type "adb kill-server" to exit adb. After I did that, now if I type anything starting with adb, it says:
"daemon not running. starting it now on port 5037
CreateProcess failure, error 2
failed to start daemon
error: cannot connect to daemon"
Have no idea what the eff I did. Tried doing some research, will have to check more tomorrow. I tried adb start-server, and got the same message. Rebooted phone and computer, same thing. So i messed something up. Anyone know what I did and what i could try to get it working again? damn i suck.
k2buckley said:
I suck. I had it working. For some reason, through my tiredness and confusion, I thought I had to type "adb kill-server" to exit adb. After I did that, now if I type anything starting with adb, it says:
"daemon not running. starting it now on port 5037
CreateProcess failure, error 2
failed to start daemon
error: cannot connect to daemon"
Have no idea what the eff I did. Tried doing some research, will have to check more tomorrow. I tried adb start-server, and got the same message. Rebooted phone and computer, same thing. So i messed something up. Anyone know what I did and what i could try to get it working again? damn i suck.
Click to expand...
Click to collapse
The "kill-server" should not have completely disabled ADB. Relax until you get her phone, then do everything you did to yours to hers. It should re-start. Yes, "adb.exe" was the proper file (not folder) to have moved into your computer windows\system(32,64,-) directory, as was the dll file. Obviously. Or it never would've told you the device ID.
You're on the right track.
And, when in doubt, issue that "adb reboot" command. It's not gonna hurt the phone and it'll let you know if ADB is working... Just don't do it halfway through any process.
And stop experimenting with things like adb kill-server, dummy!!! The only way you need to know to STOP adb is you DON'T NEED TO STOP ADB! It's not like a background program that you need to kill when you're done.
The way to "stop" or "kill" ADB is simply not to issue ADB commands. And when you close that Command Prompt box, ADB IS closed.
Okay, I just tried issuing the adb kill-server command. It takes me back to a DOS prompt with no notes. Then I typed ADB and my daemon started back up. I then issued adb start-server and it took me back to a blank (no notes) command prompt.
Don't know why it completely shut down your ADB, but I think when you plug her phone in you'll have a fresh start and it'll all work.
Start with adb devices, then if it shows her ID, issue adb reboot. If the phone reboots, you're good to go forward.
[EDIT] Okay, I just tried something I should've told you to try: without the phone plugged in, open the Command Prompt and type adb devices. Prompt should come back up as below. I then issued adb kill-server. Again, see below, nada. But then I issued adb start-server and got what you see in the string below:
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Neil>adb devices
List of devices attached
[blank, so none]
C:\Users\Neil>adb kill-server
[blank]
C:\Users\Neil>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Users\Neil>[blank]
Yours should look and work like this. If it does, plug in the phone and get started.
If not, pull out that .38 on the top shelf of your closet. Put in only 1 bullet. Spin chamber. Point at head. Pull trigger.
If you're still standing, (that's a good sign), go back to step one (unplug phone, reboot phone and computer), and try, try again. (Or Google Chat me...I PMd my screen name to you).
Just saw this one...responses in Green
k2buckley said:
Whoa, thanks dude. I'm going to try that right now. I made my last post as you were typing that up apparently, I was ready to throw in the towel, but I'm going to try what you said....
I'm assuming there needs to be one that is actually 'adb.exe', correct? when i clicked on the properties of that 'adb' one that was there, it said 'file type: .exe (application)'. Is that what I'm looking for?
YES INDEED!!
that is the site I downloaded the sdk tools from, the one for windows that says 'installer ro8 windows.exe (recommended) Does that appear to be the correct one? Once i downloaded that, the installer popped up, installed everything, then sdk manager popped up, requested that I download and install some stuff (android platforms?). Once that's finished, that should be it, right? Just want to make sure I haven't been missing a step or something.
All Good
(and thanks for your patience with me, I'm learning though. all the flashing I've done in the past few months, still can't believe that I never took to the time to learn adb. now I know why people are against Unrevoked, cuz I didn't learn sh!t by doing that. A few clicks and I was rooted and flashing away!)
We all have to start somewhere. And I used Unrevoked, too, so had to go back and learn ADB
well. I fubared something, ha. This is becoming comical. I followed what you said. The only thing is, which I'm sure this is the issue...after sdk tools installed again, there was still no 'adb.exe' folder in platform-tools. just 'adb'. The adbwinapi.dll was there, and i copied it to "windows/system32" I copied the 'adb' to that folder as well. So either the 'adb' that i copied was incorrect, and I have no idea where that damned 'adb.exe' is at, or i was supposed to move or cut them, rather than copy. either way, i give up for tonight, need some sleep.
when I opened a command prompt, and typed 'adb devices', a windows error with a red x pops up (outside the command prompt) that reads "this application has failed to start because AdbWinApi.dll was not found. Re installing the application may fix the problem". Then I click ok.. Then it says "adb.exe has stopped working, a problem caused the program to stop working correctly. windows will close the program and notify you if a solution is available" HA. DAMn I suck.
No you don't. You're doing good...
Not thinking clearly right now, need some sleep. Thanks again, hopefully we can get this straightened out tomorrow, or later today i guess it is now, damn its late.
Edit!! whoa! My final attempt was to copy the adbwinapi.dll to windows\system (instead of system32), and i believe that worked. I typed in adb devices, and I got "list of devices attached HT0###L00069 device" I assume that's my Evo? Hooray! Thank you so much man, I cannot express how happy I am right now, ha. That adb reboot kicked ass, lol. Now I can learn some stuff.
Agreed. Totally trippy when you type on the 'puter and the phone reacts
Finally, last question. My friend (who's phone I was going to root) had to leave hours ago. I was using my phone to do this and get it working. When I go to root her phone, in theory, should it connect to adb just fine at this point? Thanks again man, you were a huge, massive help.
Click to expand...
Click to collapse
YES INDEED IT SHOULD CONNECT, and you're very welcome!!
I still really don't understand why anyone has to install SDK if they're only going to tweak their phone and not write programs. That's what SDK is for. I think the whole SDK Install thing is just to get those f-ing USB drivers...which seems patently absurd.
SO FORGET SDK AND JUST CONCENTRATE ON ADB...
Persnlmgr said:
Okay, I just tried issuing the adb kill-server command. It takes me back to a DOS prompt with no notes. Then I typed ADB and my daemon started back up. I then issued adb start-server and it took me back to a blank (no notes) command prompt.
Don't know why it completely shut down your ADB, but I think when you plug her phone in you'll have a fresh start and it'll all work.
Start with adb devices, then if it shows her ID, issue adb reboot. If the phone reboots, you're good to go forward.
[EDIT] Okay, I just tried something I should've told you to try: without the phone plugged in, open the Command Prompt and type adb devices. Prompt should come back up as below. I then issued adb kill-server. Again, see below, nada. But then I issued adb start-server and got what you see in the string below:
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Neil>adb devices
List of devices attached
[blank, so none]
C:\Users\Neil>adb kill-server
[blank]
C:\Users\Neil>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Users\Neil>[blank]
Yours should look and work like this. If it does, plug in the phone and get started.
If not, pull out that .38 on the top shelf of your closet. Put in only 1 bullet. Spin chamber. Point at head. Pull trigger.
If you're still standing, (that's a good sign), go back to step one (unplug phone, reboot phone and computer), and try, try again. (Or Google Chat me...I PMd my screen name to you).
Click to expand...
Click to collapse
Well I'm awake and rested! Now that I'm not stupidly tired, I think I remember something bad. For some reason, I'm thinking I might've, just possibly, typed adb kill. as opposed to adb kill-server. I probably did just that, killed adb! But yea, even with the phone disconnected, if I type adb devices, i get the same error message, failed to start daemon. Crap. Wonder if I should start all over? Or if "kill adb' did something worse. The reason I tried to do that (which I know I shouldn't have, and I've learned a lesson from it) is because when I tried to removed the device, from the "safely remove hardware", it wouldn't let me stop the "adb compositte interface" because it said something was still using it. I had everything closed, no windows of any sort open. I thought to myself, "hmm, adb must still be connected to my phone somehow, perhaps i need to kill it before I can unplug the phone." So, that was my dumbass reasoning. But I do think I typed "adb kill" When I typed that, no errors came up, and it did indeed allow me to stop the device. However, it's just when I try any other adb commands now. If I type "adb", it pops up a crapload of information, looks like it shows me a bunch of different adb commands. but as soon as I type anything after "adb" such as "adb devices," "adb start-server" or whatever, it gives me the error message and says failed to start daemon. So I believe i effed something up.
k2buckley said:
Well I'm awake and rested! Now that I'm not stupidly tired, I think I remember something bad. For some reason, I'm thinking I might've, just possibly, typed adb kill. as opposed to adb kill-server. I probably did just that, killed adb! But yea, even with the phone disconnected, if I type adb devices, i get the same error message, failed to start daemon. Crap. Wonder if I should start all over? Or if "kill adb' did something worse. The reason I tried to do that (which I know I shouldn't have, and I've learned a lesson from it) is because when I tried to removed the device, from the "safely remove hardware", it wouldn't let me stop the "adb compositte interface" because it said something was still using it. I had everything closed, no windows of any sort open. I thought to myself, "hmm, adb must still be connected to my phone somehow, perhaps i need to kill it before I can unplug the phone." So, that was my dumbass reasoning. But I do think I typed "adb kill" When I typed that, no errors came up, and it did indeed allow me to stop the device. However, it's just when I try any other adb commands now. If I type "adb", it pops up a crapload of information, looks like it shows me a bunch of different adb commands. but as soon as I type anything after "adb" such as "adb devices," "adb start-server" or whatever, it gives me the error message and says failed to start daemon. So I believe i effed something up.
Click to expand...
Click to collapse
Okay, well as I said, **** SDK, it's irrelevant.
"You need the driver only if you are developing on Windows and want to connect an Android-powered device to your development environment over USB."
So, go here ( http://developer.android.com/sdk/win-usb.html ) to get and (re)install the ADB Composite drivers. You should not have to do anything else. If they ask WHERE you want to install them, either direct them to the root of your harddrive, likely C:\ , or if you can set the directory where the DRIVERS (not the program) goes, choose WINDOWS.
Then you should be ready to go back and follow the rest of my instructions easily.
BTW, I assume you've checked UNRevoked.com to see if they have a fix for their super easy, automatic Root process to accomodate the new HBoot?
Jus' askin...
Keep me posted, or GChat me. I'm at my desk...
Hello there.
I have been having the 'stupidly set baseband to USA and unable to change back' issue with my Nexus 5x, using a European version. I live in Croatia, so as you would imagine this has meant a complete loss of signal/mobile operator/3g etc.
As per my other thread in Nexus 5x help and troubleshooting,
http://forum.xda-developers.com/nexus-5x/help/usa-baseband-set-european-model-t3252879
I have exhausted other options and have come to the realisation that as per other users issues with other phones that the use of QPST tools and using a clean QCN file to inject into my phone is the only course of action left. However, I have no knowledge of such things (not to say that I am unable to inform myself).
I emailed a developer with regards to users issues with Nexus 5 phones (not 5x), and he said that I need to enter this mode on my phone.
Could anyone help me out with this, and in general with this issue? As some have tried to help but unfortunately my thread has more of my own replies than other users. (In elaborating on steps taken to resolve my misery).
I am not looking for a 'one button fix', I have educated myself far and beyond with regards to this issue, I just need some more expert help so that I can sort this out myself.
Please, anyone?
Marko
Thank God.
I can actually get a new phone. Help not needed in the end.
Thanks anyway.
Marko
was.once.dead said:
Thank God.
I can actually get a new phone. Help not needed in the end.
Thanks anyway.
Marko
Click to expand...
Click to collapse
glad you got your probelm fixed dont know if this will help you or others but if you press *#*#4636#*#* your phone will enter a radio diagnostics tool where you can set your preferred network type and also select your radio baseband by using the 3 dots at the top. For my 5X i can select USA BAnd or Band mode 6, Band mode 7.
sorry if this is OT and not related to your issue.
Thank you for your input. However my phone does not have those options. Only USA band, which led to this week long stress for me. Im going to be able to get a replacement device in the end, so im happy about that, but this issue is unfortunately somewhat of a one way street wherin the usual simple solutions or even more complex adb, fastboot, etc etc things do not bring about any resolutions.
Again, thanks for trying to help but its a phone to phone kind of thing.
Marko
Best advice I can give. Don't mess with the basebands
zelendel said:
Best advice I can give. Don't mess with the basebands
Click to expand...
Click to collapse
Best advice ever...
But.... If you are really hot on getting the 5x into diagnostic mode to run QPST, QXDM, etc., do this. (I did this on my 5x to obtain the QCN file to check out the NV and EFS items, grab QXDM logs, etc.)
1. Use Heisenberg's most excellent step-by-step tutorial on unlocking the boot loader, rooting the phone, and installing super user apk.
2. Once rooted, connect the phone to a PC and open up adb, then issue the adb shell command.
3. Once in adb shell, type: su -c 'setprop sys.usb.config diag,adb'
4. At this point, you should see a pop up on the phone to authorize super user access. Click to allow access.
5. Now you will probably have to load a driver on the computer for diag access. I got lucky (since I have a mess of drivers on my computer) and the driver loaded automatically. As I recall, my computer selected qcusbser.sys. Seems to be a pretty generic QCOM driver vs. an LG specific driver.
6. You now have diag access. You will have to run steps 2 - 3 after each phone reboot. In other words, these steps aren't "sticky" between reboots.
7. ????
8. Profit
I did this and it worked for me.
clivemckracken said:
Best advice ever...
But.... If you are really hot on getting the 5x into diagnostic mode to run QPST, QXDM, etc., do this. (I did this on my 5x to obtain the QCN file to check out the NV and EFS items, grab QXDM logs, etc.)
1. Use Heisenberg's most excellent step-by-step tutorial on unlocking the boot loader, rooting the phone, and installing super user apk.
2. Once rooted, connect the phone to a PC and open up adb, then issue the adb shell command.
3. Once in adb shell, type: su -c 'setprop sys.usb.config diag,adb'
4. At this point, you should see a pop up on the phone to authorize super user access. Click to allow access.
5. Now you will probably have to load a driver on the computer for diag access. I got lucky (since I have a mess of drivers on my computer) and the driver loaded automatically. As I recall, my computer selected qcusbser.sys. Seems to be a pretty generic QCOM driver vs. an LG specific driver.
6. You now have diag access. You will have to run steps 2 - 3 after each phone reboot. In other words, these steps aren't "sticky" between reboots.
7. ????
8. Profit
I did this and it worked for me.
Click to expand...
Click to collapse
Please give me the global version of rfnv files:good:
Please give me the global version of rfnv files
Sorry, bro. I only have the values from my US version.