yashsingh1/xdaforums huggingface dataset:
[EVO 4G Q&A, Help & Troubleshooting] Bleys43:
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.
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
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.
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
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
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
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.
[EVO 4G Q&A, Help & Troubleshooting] Stajdanley:
Try this thread. It has a lot of ADB info.

http://xdaforums.com/showthread.php?t=694250
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
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.
[EVO 4G Q&A, Help & Troubleshooting] Persnlmgr:
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. :D
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
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.
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
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.
[EVO 4G Q&A, Help & Troubleshooting] Persnlmgr:
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.
[EVO 4G Q&A, Help & Troubleshooting] Persnlmgr:
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).
[EVO 4G Q&A, Help & Troubleshooting] Persnlmgr:
Just saw this one...responses in Green

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...
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
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.
[EVO 4G Q&A, Help & Troubleshooting] Persnlmgr:
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...
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
Yea, I've been checking Unrevoked, I haven't seen anything updated for the evo yet, just the Incredible it looked like. I want to figure this **** out anyways, even if I wasn't going to root her phone. It is now a mission. Unfortunately, I just got called into work, which I didnt think would happen, cuz it's rainy here in Vegas as well, and I work outside. Oh well. I won't be able to finish figuring this out until a little later. Thanks again for your help, hopefully I can catch up with ya later on, let you know how I make out.

So, go here 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, eith 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.

confused. go where? eith? is that a typo for "edit"? just checkin. thanks dude.
[EVO 4G Q&A, Help & Troubleshooting] Persnlmgr:
it should have been either. DOH!:eek:

And, while you're at being safe, recopy the adb.exe file (remember, it'll show as adb but confirm it's the exe file) and the adbwinapi.dll file to the windows\system(32,64,?) or windows directory where you copied them last time. No harm in getting a completely fresh start.
[Vibrant Q&A, Help & Troubleshooting] xriderx66:
I'm running Ginger Clone R2 Rom.

the Stock launcher is a Gingerbread launcher, but the 3D app drawer is annoying, is there anyway i can remove that, because i jsut don't like it and when im in the middle of the list, and go back to home screen, and go back to app drawer, its back at the top, how can i stop it from happening or is there another replacement which looks like that but without 3D or that problem?
[Vibrant Q&A, Help & Troubleshooting] MWBehr:
Well there's a large number of launcher alternatives: LauncherPro, ADW, Zeam...

LauncherPro has a drawer nearly identical to the Gingerbread one (3D is a selectable option). I'm pretty sure that it saves your location in the scroll like you're wanting.
[Vibrant Q&A, Help & Troubleshooting] xriderx66:
But I like the feel of the homescreen but not the app drawer I wish I could have the *best of both worlds*
[Vibrant Q&A, Help & Troubleshooting] TJBunch1228:
So I recently started messing around with speedtest.net. When I'm in a strong 3G area I see around 5 mbps down. At home on wifi I see around 1.5 mbps down. At face value, it looks like my 3G is faster than my wifi. Can this be true? My ISP only offers up to 1.5 mbps in my area. Should I just get wifi tether and use my phone for internet at home, or do the stats from speedtest only tell a part of the story?
[Vibrant Q&A, Help & Troubleshooting] geocepe:
it is possible that your phone is faster. There are a few things to keep in mind though. How much data do you use? If it is more than 5 GB keep your DSL. The other is are you playing video games? If you are playing games that require a low ping then also stay with your DSL. If you are using low amounts of bandwidth and not playing games you might want to switch.
[Vibrant Q&A, Help & Troubleshooting] MWBehr:
It's certainly possible, but it doesn't neccessarily mean that your speeds will stay consistent or even be as fast when tethered. Also, your wifi speed will vary based on your distance from your router.

Also keep in mind that your 3G contract has a 5GB cap. From what I understand this simply means your speeds will be throttled down once you reach the cap (and there are some workarounds that may or may not work well out there).

3G is one of the most inconsistent broadband connection out there, so personally I'd never rely on it as my primary internet source, but it's up to you ;)
[Vibrant Q&A, Help & Troubleshooting] TJBunch1228:
Awesome answers, I appreciate the info!
[Vibrant Q&A, Help & Troubleshooting] iynfynity:
i would love to have a wifi instead of having a data connection. unfortunately my mom doesn't let mo do it.
[Epic 4G General] watermoore:
Okay So ever since I have gotten my Epic a week ago I have felt like a total Noob. I came from an HTC HERO which I rooted manually. My wife has an HTC EVO which I rooted using UNREVOKED ONE CLICK (I know I cheated but she doesnt care). This Epic has me heading back to my roots lol. Either I am a total Noob and this is a simple fix and my dumb ass keeps overlooking it (which at this point I am hoping for) or my Epic is Effed and I need to send it back before my 30 days is up.

Basically my problem is that I cant Adb remount or Adb push to save my life. When I use Adb devices it lists my device so I know my phone is talking with my computer correctly. I first Odin'd to DK28 with the root and clockwork etc. Everything seemed fine except I like to swap stock fonts for custom fonts via Adb, simple things like that. Since I cant remount I figured something was either wrong with the Rom or the Root. So I just tried to load a custom ROM up and try my luck seeing as thats pretty simple. I loaded Epic Experience 2.0.06 and got it all set up as my Daily. Then I got busy and just used it for a few days continuing to tweak my Rom and get it all dialed in for daily use.

I wanted to try ViperRom and see what that was all about so I made a backup in Clockwork and loaded ViperROM with no problem. While ViperROM is pretty snappy its not really my taste so I figured I would wipe and restore my EE backup. No matter how many times I did the data wipe, cache, davlik etc my restore would boot up greeting me with force close after force close. So I ODIN'd back to stock 2.2 then used the one click root exploit to get root. it seems like it worked but still ADB problems continue to persist. I have tried everything I can possibly think or research via XDA but now I am out of ideas.

I have uninstalled and reinstalled ANDROID SDK 3 times 2 twice with "Accept-All" radio ticked and once with just the 2.1 and 2.2 goodies.

I have tried different cables none of which are stock. on every usb port on my computer all replicate the same issues: Adb devices shows up right but will not remount only run in shell. and when i run Adb shell it responds with $ first needing me to open su just to get the # symbol.

Any input is incredibly appreciated.
[Epic 4G General] decalex:
you know, I've had the same problem lately. --curious to know what's causing it.
[Epic 4G General] watermoore:
Its good to know I am not the only one out there with this issue maybe someone can chime in with a fix. or some insight at least to what the problem may be.
[Epic 4G General] watermoore:
Still no response.... Bump?
[Epic 4G General] DevinXtreme:
su
remount rw

We have a different method than the Hero did. If you've already tried that, lemme know. Works fine for me on stock rooted, Nebula, and (now) Bonsai.

Also, if that doesn't work, try it from a terminal app on the phone. I use it there more than anything.
[Epic 4G General] watermoore:
Hey man thanks for your input, I really appreciate it. That didnt work either, on ADB or on Terminal Emulator. It responds correctly from both sources with:

remount rw
Remounting /system </dev/st19> in read/write mode

I am wondering if it has anything to do with the fact that the 64bit drivers dont install totally. this module called the "Abstract Control Module" hangs forever and doesn't install. However I ran over to my wifes 32 bit vista laptop where the drivers will install totally with no success either.
[Epic 4G General] DevinXtreme:
Hrm... That's very strange. It's telling you that it is working. What is the error you get when trying to move stuff from there? So, after remount rw'ing, cp something into a system folder and post those results.

Your output for remount rw is correct, so let's see where that goes.
[Epic 4G General] watermoore:
Okay so here is what happened.

I just made a simple text file that was entitled "movetest.txt". I placed the file on the sdcard and used terminal emulator to push the files successfully to /system/etc

then I placed it in my C:/Android/tools dir and tried to adb push with no success so I ran shell and was able to succeed via shell here to the fonts dir in system.... here is the code:

c:\Android\tools> adb push movetest.txt /system/fonts
failed to copy 'movetest.txt' to '/system/fonts/movetest.txt': Permission denied

c:\Android\tools>adb shell
$ su
su
# cp /sdcard/movetest.txt /system/fonts
cp /sdcard/movetest.txt /system/fonts
#
[Epic 4G General] watermoore:
Bump again

Sent from my Epic
[Epic 4G General] watermoore:
Okay since I'm not getting much love from the forum I'm guessing this is an uncommon occurance, in which case I am going to try one more thing before I send it back for a replacement. I am planning on going back to DI18 via odin then one click rooting. Then flashing the modem and other nessecary files to run 2.2 epic experience. Its the only possible thing I can think of that I haven't tried to address my problem. Thanks for the feedback I have gotten thus far.

Sent from my Epic
[Epic 4G General] mirth18:
This post helped me: http://xdaforums.com/showpost.php?p=8723568&postcount=2
[Epic 4G General] A_Flying_Fox:
The e0pic and hero are way differentwhen it comes to adb

I was the same way lol I don't think adb works

Like I think the only way is to cp things
[Epic 4G General] DiGi760:
That last one appears to have worked. Check and see if movetest.txt is in /system/fonts. If so, then you're in business. Just copy stuff across as root instead of pushing.
[Epic 4G General] watermoore:
Well now I can use ADB fully. I odined back to stock then used the one click clockwork 3.0.0.05 ext4 batch then flashed Truley Epic Rebirth 1.2 and was able to remount correctly, push and pull all the way down to the root dir. I am not sure what changed but it just all of the sudden started working.... I'll take that lol
[Epic 4G General] watermoore:
Well my issue was a bit different. I could get it show up with the "devices" command. When I tried to "adb remount" it would deny me. It would reply with "device not found". Which is really wierd because I could ADB shell with root access any day of the week. I just had to change my process to accommodate the limitation.

I would just ADB push files to the sdcard, mount into shell to gain full root permissions then finish my work.

Kind of a strange round about way of going about it but I learned quite a bit more linux commands that way lol
[Epic 4G General] mirth18:
Fyi.. I am using ubuntu 11.04
[Epic 4G General] Seanc13:
Is it possible
[Epic 4G General] gTen:
obviously its possible..but no one has released it yet...
[Epic 4G General] flopez76:
A team of people are working on it, but haven't heard from them in a while
[Epic 4G General] gTen:
If you are talking about the team I think you are, they said they are waiting for official froyo to do it..
[Epic 4G General] XtaC318:
Once official froyo source drops. Things will go more smoothly.. its amazing that our devs here have made the progress they have given the lack of necessity available.