Database Develop

Free Screenshots using Dalvik - not rec my phone?

I tried to follow the steps from androidandme to set up my phone for screen shots. I got java, got the android sdk and unzipped everything (nothing was installed?), changed the path under advanced settings, dowloaded eclipse (why not) and all that jazz - full 9 yards.
However, when I run ddms.bat in the tools folder and Dalvik comes up it never recognizes my phone. I have tried with the g1 mounted, unmounted, usb debugging on/off (which I also do not know what this means).
Anyone have any thoughts? I did not get any prompts about drivers and I am mounted to my computer.

Read the guides on how to install ADB.

for some reason when i ever i use ddms to take screen shots, i can't just go to take a screenshot, i have to run a logcat first, it will bring up a popup that says "failed!" i then close that and it runs a logcat, after i do that, then i can use it to take a screen shot.

^^ not sure how that matters but I double clicked the adb.exe file, a dos prompt ran a lot of info and disappeared. Also, your signature has a link to SDK 1.5, not 1.6?
Tried DDMS again with no luck.
^ I tried to do a logcat, failed, SS with no luck... again though, the issue is that my phone is not being identified - it would make sense that it would not work if it doesnt even know my phone is hooked up.
Perhaps I will sleep on it as work is in a few hours. I would appreciate any help I can get.

s15274n said:
^^ not sure how that matters but I double clicked the adb.exe file, a dos prompt ran a lot of info and disappeared. Also, your signature has a link to SDK 1.5, not 1.6?
Tried DDMS again with no luck.
^ I tried to do a logcat, failed, SS with no luck... again though, the issue is that my phone is not being identified - it would make sense that it would not work if it doesnt even know my phone is hooked up.
Perhaps I will sleep on it as work is in a few hours. I would appreciate any help I can get.
Click to expand...
Click to collapse
Sorry if this is not relevant, but I had a ton of trouble until I had the newest jave runtime installed. I never had trouble, got a new laptop at work and had no clue why it would not run. the newest JRE fixed it right up. Maybe not your problem but...
Also I like the program "droid explorer". It has screenshot built in.
EDIT.
I have one more thought...I (always have one more thought) try starting your phone in fastboot (camera and power) then back button when the skaters come up) and see if it asks for drivers then.

s15274n said:
^^ not sure how that matters but I double clicked the adb.exe file, a dos prompt ran a lot of info and disappeared. Also, your signature has a link to SDK 1.5, not 1.6?
Tried DDMS again with no luck.
^ I tried to do a logcat, failed, SS with no luck... again though, the issue is that my phone is not being identified - it would make sense that it would not work if it doesnt even know my phone is hooked up.
Perhaps I will sleep on it as work is in a few hours. I would appreciate any help I can get.
Click to expand...
Click to collapse
adb.exe is a command line application, it doesn't have a GUI. To use an command line app you have to 'cd' to the directory where it's located and enter valid commands. I think you can type 'adb help' for a full list of commands.
Try reinstalling the drivers, it took me a few tries to get it working right on Vista (interestingly no drivers are needed for OS X )

Let me start very basic. Is there any "installing" of the SPK? Or, do I just extract the files? I extracted them and created a directory in PATH like the site said to do.
If there is no installation... are you saying for me to get in dos and just start keying commands, and not using any of the files from the zip?

There is no installation, but EVERYTHING for the sdk is ran in command prompt. Meaning click start, click run, type in cmd, then type cd path/to/your/toolsfolder/ then type adb remount see if it does, if not you NEED TO FOLLOW THE ADB INSTRUCTIONS FOR INSTALLING DRIVERS.

Getting Nexus One ADB/USB Mount working (Driver)

Download This file and extract.
hit Windows Key + r
Type in devmgmt.msc
right click on nexus one
click update
update from location on computer.
select that folder.
---------------Notes-------------
Be sure to enable debugging on your phone via Settings>Applications>Devlopment>USB debugging.
Confirmed working on:
Win 7 Ultimate x64/x86
Win 7 Home Edition x86?
Win Vista
XP Home x86
XP Pro x64/x86

O.S
What O.S you had this working on?

@th3fallen
143!!

I got it working on win7 Ultimate version

This works for Windows 7 Home Premium Edition as well.

In order to get ADB working on Linux (Ubuntu 9.04) I had to edit /etc/udev/rules.d/51-android.rules (I may have created this file for the G1) and add:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
What I was seeing was the device would sort of show up when I ran adb devices, but it would list ????????? as the ID and no permissions.
~Kenny

I was able to access it by using dream, magic and adb testing device didnt need any specific driver.

I did this to get it working on win 7 ultimate x64

NexVision said:
I was able to access it by using dream, magic and adb testing device didnt need any specific driver.
Click to expand...
Click to collapse
You need the latest refresh of the drivers (and tools for updated fastboot, etc.) from the SDK. If you go to a Windows command prompt and run Android, assuming the tools directory is in your path, you can select the update for both. It will fail in updating tools, since you are using an app in it, but don't close the app, just reapply at that point and it will work on the second go. Then when you install the N1, you will have the drivers you need to install as before.

Not meaning to argue with you but what I was saying is I have had no issues doing anything via adb with it as a magic I have done fastboot as well hey maybe its just working for me.

kfk2 said:
In order to get ADB working on Linux (Ubuntu 9.04) I had to edit /etc/udev/rules.d/51-android-rules (I may have created this file for the G1) and add:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
What I was seeing was the device would sort of show up when I ran adb devices, but it would list ????????? as the ID and no permissions.
~Kenny
Click to expand...
Click to collapse
Hmm...I have that already in my /etc/udev/rules.d/51-android.rules (mine has .rules, not -rules...I'm assuming that's a typo in your post?) and I'm still coming up with ?????????? as the device and no permissions, all attempts to do anything with adb result in it telling me I don't have permission to do these things.

Swervo said:
Hmm...I have that already in my /etc/udev/rules.d/51-android.rules (mine has .rules, not -rules...I'm assuming that's a typo in your post?) and I'm still coming up with ?????????? as the device and no permissions, all attempts to do anything with adb result in it telling me I don't have permission to do these things.
Click to expand...
Click to collapse
Yah that was a typo.. The no permissions error appears to me that adb doesn't have access to the /dev/ devices used. I'm not at home so I cannot lookup what device is created and used in /dev/ for you to check the permissions. I know I killed the adb server and restarted it a few times while trying to get mine to work, along with updating to the latest sdk. So you may want to try those things, you could also try running adb as root and seeing if that fixes it (if so, then it's a simple permission error with udev not creating it with correct permissions).

Alrighty, I think I got it. I'm no udev expert (in fact, I'm rather useless at it), but this worked for me.
1) Make sure USB debugging is turned on on the phone.
2) Plug the phone into the USB port on the machine.
3) Make sure /etc/udev/51-android.rules has
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
Click to expand...
Click to collapse
in it.
4) run
adb kill-server
Click to expand...
Click to collapse
5) As root, run
service udev restart
Click to expand...
Click to collapse
6) run
adb start-server
Click to expand...
Click to collapse
Worked for me to get the device recognized.

Hey guys, I have the Android 1.5 SDK/ADB installed on my computer.. so I don't know what will happen when I mount my N1 (haven't tried yet). I want to be able to mount my N1 normally without ADB or anything, 'cause I'm not going to root it for a while. Thanks!

Confirmed on Vista
I can confirm that the instructions in the OP work on Vista. Thanks a lot, th3fallen.

Alleviate said:
Hey guys, I have the Android 1.5 SDK/ADB installed on my computer.. so I don't know what will happen when I mount my N1 (haven't tried yet). I want to be able to mount my N1 normally without ADB or anything, 'cause I'm not going to root it for a while. Thanks!
Click to expand...
Click to collapse
Nothing will happen, ADB doesn't start interacting with your phone without you explicitly telling it to. Also, if you don't have debugging turned on on your phone, then it won't even if you do explicitly tell it to. Feel free to mount the drive on it.

ADB and Root
Maybe I'm doing something wrong, but I can't get ADB to recognize my phone. ADB is all set up correctly, I have it updated (I believe) to the most recent version. I installed the updated USB driver and I see the "Android Phone" in my device manager. I have USB Debugging checked off in my phone settings. ADB worked fine for my G1, but it doesn't recognize my Nexus One.
I shouldn't have to root the phone to have ADB working should I? Can anybody think of something I overlooked? I am running Windows XP Professional SP3

Okay, so I navigated to the "1.1-nexusone-superboot" folder in the command prompt and tried
Code:
adb-windows devices
and my device showed up. Now I want to move those files to where I originally had my adb files in C:\android-sdk-windows\tools so that all I have to type is
Code:
adb devices
to have my phone listed. I tried replacing the files in my \tools folder and renaming them to what they were named before, but that didn't work. Could somebody please help me get this set up properly?

ccunningham83 said:
Okay, so I navigated to the "1.1-nexusone-superboot" folder in the command prompt and tried
Code:
adb-windows remount
and my device showed up. Now I want to move those files to where I originally had my adb files in C:\android-sdk-windows\tools so that all I have to type is
Code:
adb devices
to have my phone listed. I tried replacing the files in my \tools folder and renaming them to what they were named before, but that didn't work. Could somebody please help me get this set up properly?
Click to expand...
Click to collapse
in your command prompt you have to be in the c:\android-sdk-windows\tools\ directory for it to work

ccunningham83 said:
Maybe I'm doing something wrong, but I can't get ADB to recognize my phone. ADB is all set up correctly, I have it updated (I believe) to the most recent version. I installed the updated USB driver and I see the "Android Phone" in my device manager. I have USB Debugging checked off in my phone settings. ADB worked fine for my G1, but it doesn't recognize my Nexus One.
I shouldn't have to root the phone to have ADB working should I? Can anybody think of something I overlooked? I am running Windows XP Professional SP3
Click to expand...
Click to collapse
I was having the same problem yesterday. But i'm on Vista. Nothing seemed to work, but ADB was working fine on my Mytouch. At any rate, I ended up going to download the most recent SDK and trying adb again from a command prompt @ the tools location of the newest SDK, and then everything worked. I don't know if that was something I should have done in the first place and I just didn't know it (duh), but that's what worked for me.

Setting up ADB? Windows 7

im trying to set up a adb so i can use my g1 as a webcam:
http://forum.xda-developers.com/showpost.php?p=4975656&postcount=17
however when i plug in my g1 it says everything was installed except the adb.

Do you have ADB setup on your computer in the first place? If not, http://forum.xda-developers.com/showthread.php?t=532719.

I installed the adb with the sdk as it was mentioned and my computer still doesnt show my phone as an adb device

Did you install the drivers for adb?

i cant find out how!

85Mario85 said:
i cant find out how!
Click to expand...
Click to collapse
a little search and VOILA!!!
http://forum.xda-developers.com/showthread.php?t=446274&highlight=64bit+usb
this works if you are running windoze 7 x64

i dont get how im supposed to put windows 7 on test mode =S

im getting this aswel "When running the command prompt adb install I receive an error dialog stating:
"This application has failed to start because AdbWinApi.dll was not found. Re-installing the application may fix this problem.""
im getting so frustrrated with thiss

bump! i dont get this =[

Search for pdanet and install it. That's how I set up adb for Windows. (Btw - get rid of Windows. Finally did my switch to ubuntu today - ahahahahahahaha I'm sad I ever even used Windows.)

Yea, but adb is kind of a ***** about permissions and such on ubuntu. But each has its quarks.
@85mario85 - You have to cd to the adb.exe in the tools folder ie. c:\sdk\tools\ then run adb. Or add it to the paths part, but I can't remember at the moment.

evilkorn said:
Yea, but adb is kind of a ***** about permissions and such on ubuntu. But each has its quarks.
@85mario85 - You have to cd to the adb.exe in the tools folder ie. c:\sdk\tools\ then run adb. Or add it to the paths part, but I can't remember at the moment.
Click to expand...
Click to collapse
adding it to the path just saves time. instead of having to cd all the time you can just run adb. i highly suggest it. and i agree - ubuntu is a ***** about permissions all the time. i love it, but i have to learn to use it. however, i'll probably always have a copy of windows in case i can't find out how to do something and have to have it done. better safe than sorry. =]

ADB problem and no OS on device

Last night, on TWRP I formated data on the SD card, which is why I have no OS. Now looking for how to fix this on xda/google, I get into the bootloader, have fastboot usb and try to adb shell but I keep getting the "error no device found". I already installed latest drivers from HTC on to my laptop and still nothing. Any other idea?

windows 8?

First off, make sure you have HTC Sync Manager installed because that will give you the proper drivers in order to be able to use ADB commands.
Afterwards, make sure you install Java JDK and Android SDK.
Just follow this tutorial here: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
Follow it word for word and make sure you install JDK X86 even if you have a X64 computer. And then download SDK Manager, put it in C:/ drive, open SDK Manager, and download the necessary tools (also all in the tutorial).
I was in the same position as you just before yesterday and I followed this tutorial with success.

skinsfanbdh said:
windows 8?
Click to expand...
Click to collapse
Windows 7, and mac.

Evolancer13 said:
Windows 7, and mac.
Click to expand...
Click to collapse
try downloading all in one toolkit and try that. just make sure to read the onscreen instructions as you go through the process

TarekElsakka said:
First off, make sure you have HTC Sync Manager installed because that will give you the proper drivers in order to be able to use ADB commands.
Afterwards, make sure you install Java JDK and Android SDK.
Just follow this tutorial here: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
Follow it word for word and make sure you install JDK X86 even if you have a X64 computer. And then download SDK Manager, put it in C:/ drive, open SDK Manager, and download the necessary tools (also all in the tutorial).
I was in the same position as you just before yesterday and I followed this tutorial with success.
Click to expand...
Click to collapse
skinsfanbdh said:
try downloading all in one toolkit and try that. just make sure to read the onscreen instructions as you go through the process
Click to expand...
Click to collapse
I'll look into both things, thanks.
EDIT: even on my mac adb does not see any devices, before when I entered ./adb devices it would show "list of devices:" and it would be blank.

Good luck, man. It's fairly easy once you read the tutorial carefully and follow all the steps to the word. After it's all done and the command prompt says Sideload 100%, boot into TWRP, tap INSTALL and then scroll down to sideload.zip and that's your ROM. Also after copying the desired ROM to platform-tools in the SDK folder, rename it to rom.zip, it seems to work 100% that way while it struggles a bit with long names.

TarekElsakka said:
Good luck, man. It's fairly easy once you read the tutorial carefully and follow all the steps to the word. After it's all done and the command prompt says Sideload 100%, boot into TWRP, tap INSTALL and then scroll down to sideload.zip and that's your ROM. Also after copying the desired ROM to platform-tools in the SDK folder, rename it to rom.zip, it seems to work 100% that way while it struggles a bit with long names.
Click to expand...
Click to collapse
Still getting the error: device not found.
I even ran the all in one tool kit and attempted the "ADB sideload a ROM" follow the steps but get an error on CMD "C:\users\(username) is not recognized as an internal or external command, operable program or batch file"
I really do not understand why adb is not working, I did s-off and supercid myself maybe less than a week ago.

Are you sure you followed all the steps in the tutorial including installing JDK, using SDK Manager to download some tools and such? And are you sure you have the proper drivers installed (e.g HTC Sync Manager)? I used to get that error before I installed it. Go to Device Manager while in ADB mode in TWRP and see if the device is recognized or if there's a yellow sign beside it indicating that there are no drivers for it.

TarekElsakka said:
Are you sure you followed all the steps in the tutorial including installing JDK, using SDK Manager to download some tools and such? And are you sure you have the proper drivers installed (e.g HTC Sync Manager)? I used to get that error before I installed it. Go to Device Manager while in ADB mode in TWRP and see if the device is recognized or if there's a yellow sign beside it indicating that there are no drivers for it.
Click to expand...
Click to collapse
It came up under Android USB Devices as My HTC. When I was following the steps on the link you provided, when I tried to update the drivers with the google usb driver wouldnt work, it would say "windows had determined the driver software for your device is up to date". When I go into My HTC properties says the driver version is 2.0.7.18.

The Google USB drivers did not work for me either, only the ones provided by HTC Sync Manager did. I have not experienced that problem, mate, so I do not know what to do at this point, I am very sorry. If you are not able to fix this, I suggest getting an OTG cable and directly loading the ROM from the PC to your SD card. I ordered one a couple of days ago and it is coming tomorrow, it's very helpful

TarekElsakka said:
The Google USB drivers did not work for me either, only the ones provided by HTC Sync Manager did. I have not experienced that problem, mate, so I do not know what to do at this point, I am very sorry. If you are not able to fix this, I suggest getting an OTG cable and directly loading the ROM from the PC to your SD card. I ordered one a couple of days ago and it is coming tomorrow, it's very helpful
Click to expand...
Click to collapse
Crap, I appreciate your help though.
EDIT: nevermind googled it, gonna pick one up. Phoneless till wednesday

I am sorry to hear that, but I suppose that's the only thing you can do at the moment. Even if somehow get ADB working, do not cancel your order because OTG cables aren't only used for mounting the device, but also for things like connecting gamepads and controllers to play games on your device.

USB 3
If you have USB3 port adb.exe wan't recognize your device.
I triend first on USB3 and after on other older computer on USB2 all was fine

Evolancer13 said:
Last night, on TWRP I formated data on the SD card, which is why I have no OS. Now looking for how to fix this on xda/google, I get into the bootloader, have fastboot usb and try to adb shell but I keep getting the "error no device found". I already installed latest drivers from HTC on to my laptop and still nothing. Any other idea?
Click to expand...
Click to collapse
You can't acces to "adb shell" without OS, there is special mode in adb named "adb sideload" , not shell !
1) Check version adb by "adb version" you need version 1.0.29 or higher
2) Check TWRP version (2.3 or higher) Go to TWRP recovery -> adb sideload
3) Connect PC to phone , at PC in device manager must be MY HTC device.
4) Type jn PC adb sideload /yourpath/yourrom.zip

tash2013 said:
You can't acces to "adb shell" without OS, there is special mode in adb named "adb sideload" , not shell !
1) Check version adb by "adb version" you need version 1.0.29 or higher
2) Check TWRP version (2.3 or higher) Go to TWRP recovery -> adb sideload
3) Connect PC to phone , at PC in device manager must be MY HTC device.
4) Type jn PC adb sideload /yourpath/yourrom.zip
Click to expand...
Click to collapse
check first with "adb devices" to see does your PC recognize your HTC

tash2013 said:
You can't acces to "adb shell" without OS, there is special mode in adb named "adb sideload" , not shell !
1) Check version adb by "adb version" you need version 1.0.29 or higher
2) Check TWRP version (2.3 or higher) Go to TWRP recovery -> adb sideload
3) Connect PC to phone , at PC in device manager must be MY HTC device.
4) Type jn PC adb sideload /yourpath/yourrom.zip
Click to expand...
Click to collapse
Tash2013 YOU ARE AMAZING! Got my One back up running!

Oh man I'm so glad it's working. I thought you already knew that it is sideload not shell lol.
Sent from my HTC One using Tapatalk 4 Beta

TarekElsakka said:
Oh man I'm so glad it's working. I thought you already knew that it is sideload not shell lol.
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
If I knew I would have tried lol, and it no one said anything about sideload but oh well.

Haha! Damn. I am glad it worked out, though.

[Q] Help with bricked HTC One

I've been a lurker for the last few years; never thinking I would need any help or assistance .. but I have a situation ..
My Sprint HTC One was working better than I had ever seen it just last Thursday. I was running CM11, with ART. I had an old version of SuperOne (Sense 5) backed up with TWRP. I thought I'd go ahead and load the backup, and update all the apps and then make another more recent backup before returning to CM11. I got as far holding the power button and selecting recovery. The phone locked up at that point.
It took 10 minutes to get it back to the screen where you can select fastboot, factory reset, etc. Interestingly I couldn't get into TWRP. The screen read "entering recovery" and nothing. It would just hang there.
I read that erasing the cache with fastboot might work, and it did. But when I was able to enter recovery, instead of restoring CM11, I thought, "well, maybe now it'll work", so I just rebooted. Wrong. Wouldn't boot. And, now running fastboot cache erase (or erase cache) doesn't do anything.
Now, by pressing the power button alone and holding it in I'm able to get to the fastboot, factory reset, etc screen. Went to fastboot usb, and fastboot commands work but ADB doesn't detect the device. I can't send ADB commands, but I can send ONE fastboot command. After sending any fastboot command, the phone locks up. Nothing from that point.
I tried installing a RUU. The .exe file detected the version on my phone, and everything went great until the program said it was booting to the bootloader. Locked it up. Nothing from that point.
I need help.
Thanks.
I uninstalled the HTC drivers and reinstalled them. A suggestion since ADB didn't work. And I can't get into bootloader. No difference.

Any suggestions
Any suggestions at all. I'm desperate.

Ogre77497 said:
Any suggestions at all. I'm desperate.
Click to expand...
Click to collapse
You can get into fastboot correct?

Fastboot - Yes .. Sorta
I can get into fastboot, but I copy anything to the phone via fastboot. I'm told "unable to write". Thanks.

Ogre77497 said:
I can get into fastboot, but I copy anything to the phone via fastboot. I'm told "unable to write". Thanks.
Click to expand...
Click to collapse
Ok it's probably a problem with your USB cable or USB port. Try using another PC and another cable.
If this doesn't work read some guide to properly set up ADB, uninstall all HTC stuff and install only the "naked driver" and than run the LATEST ruu. Maybe you have upgraded your firmware and can't flash older ruu's.
Sent from my HTCONE using Tapatalk

Will Try
I'll give that a try. I really appreciate the help. I run my whole business on that phone.

Just make sure you follow my suggestions properly. It should be just the cable, and I think you don't have the right drivers for ADB. Stay calm your phone is just soft bricked. You only need to be patient and read. Naked driver here http://forum.xda-developers.com/showthread.php?t=2263822
Sent from my HTCONE using Tapatalk

elvisypi said:
Ok it's probably a problem with your USB cable or USB port. Try using another PC and another cable.
If this doesn't work read some guide to properly set up ADB, uninstall all HTC stuff and install only the "naked driver" and than run the LATEST ruu. Maybe you have upgraded your firmware and can't flash older ruu's.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
+1
I did the same thing a few weeks ago and lost recovery in the process. The naked driver did the trick. Also the thread about restoring after a gsm rom install is a great. It's not a loss. Not having an sd card in the one made things a little different for me, but I was able to get everything back. These drivers suck!

Progress
I've followed your directions. I downloaded the naked driver, and the minimal ADT. I found the correct RUU (3.04.651.2) I attempted to relock the bootloader, but I got a message .. " Status read failed <no such file or directory>" Went ahead and tried flashing the RUU (fastboot flash zip ruu.zip), and got the message "FAILED Remote: not allowed"
The phone is unlocked, CID SPCS_001, and HBOOT 1.44
I wasn't able to access TWRP recovery earlier, so I tried reflashing the img file. Failed remote: image update error. I tried erasing the cache .. "Failed remote erasing error", but now I can get into TWRP.
TWRP says I have "0" internal storage. I also can't mount system, data or cache. The choices are there but can't be selected.
I can't use ADB (device not found). and the phone isn't detected by windows. I had installed the HTC drivers, but couldn't uninstall them, so I install HTC Sync manager and then uninstalled it. The program deleted the HTC drivers when I uninstalled it. When I plugged in the HTC One (with a new cable) nothing happened, so I used the windows hardware wizard to install the naked driver. The phone still isn't detected, but again I can issue fastboot commands. Well, one fastboot command and then the phone freezes up.
If I use filemanager within TWRP there's no emulated sd card. I really think that's where my problem is. No partitions are available. And, when I use TWRP to shut down, it warns me that no OS is installed.
Any other suggestions?
I sure appreciate all your help. Thanks.
elvisypi said:
Just make sure you follow my suggestions properly. It should be just the cable, and I think you don't have the right drivers for ADB. Stay calm your phone is just soft bricked. You only need to be patient and read. Naked driver here http://forum.xda-developers.com/showthread.php?t=2263822
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse

Are you Linux savvy at all? All this crap is far easier on Linux. I guarantee the drivers are absolute cakewalk -- there isn't a specific driver at all, just a rule to tell the kernel about the device.
I can give you the udev rule for the phone if you are sick of trying to get Windows to work. The Android SDK is also quite easy to install.
If you want to try, just install Ubuntu 12.04 LTS. Later versions also work, but that version is the current stable release. I can help from there.

Try another cable maybe it's faulty. Uninstall all the HTC crap, run some cleaner app like ccleaner (maybe there are leftovers) and install only the naked driver. Your phone should be detected. Make sure you have the latest version of ADB. here's the latest http://click.xda-developers.com/api...n 1.1.3 Here&jsonp=vglnk_jsonp_13877458281136
The ruu is not to be flashed with fastboot commands, you must run the exe file
Here's the latest ruu
http://click.xda-developers.com/api....05.651 .5&jsonp=vglnk_jsonp_138775039936710
-extract zip to a folder on your pc
-using fastboot, type this cmd: fastboot oem lock this will relock the bootloader
-from pc, run ARUWizard.exe from the extracted folder. it will run the RUU utility & flash back to stock
Sent from my HTCONE using Tapatalk

Installing Ubuntu
Not Linux savy at all, but I'll install Ubuntu. I'll let you know when I'm able to boot into it. Thanks.
tdhite said:
Are you Linux savvy at all? All this crap is far easier on Linux. I guarantee the drivers are absolute cakewalk -- there isn't a specific driver at all, just a rule to tell the kernel about the device.
I can give you the udev rule for the phone if you are sick of trying to get Windows to work. The Android SDK is also quite easy to install.
If you want to try, just install Ubuntu 12.04 LTS. Later versions also work, but that version is the current stable release. I can help from there.
Click to expand...
Click to collapse

Ogre77497 said:
Not Linux savy at all, but I'll install Ubuntu. I'll let you know when I'm able to boot into it. Thanks.
Click to expand...
Click to collapse
When you get it installed, login and open a terminal windows (it'll install Unity by default, so click on the first button on the left sidebar and search for terminal, then click on it), then type exactly the following (cut/copy/paste should do it too) noting that the first command will make you give your password since sudo requests root level access:
sudo apt-get update -y
sudo apt-get install -y wget openjdk-7-jdk
wget http://dl.google.com/android/android-sdk_r22.3-linux.tgz
mkdir ~/bin
cd ~/bin
tar xvzf ~/android-sdk_r22.3-linux.tgz
cat >> ~/.bashrc <<EOF
if [ -d ${HOME}/bin/android-sdk-linux ]; then
PATH+=":${HOME}/bin/android-sdk-linux/tools"
PATH+=":${HOME}/bin/android-sdk-linux/platform-tools"
fi
export PATH
EOF
exit
That last command will exit the terminal. Start another and it'll read the .bashrc file and presto -- you have SDK access from everywhere.
Then, type this command:
android
That will bring up the SDK UI -- let it download/install all of the latest stuff (r22 of the tools and whatnot).
When done, close the android SDK window.
Type adb (bet it works), but fastboot will require root access (I'm not going to teach you how to get around that yet -- no problem, you just run sudo and I'll show that in a sec).
Finally, plug in your HTC One and type adb devices and let's see if it didn't just know it already.
Lemme know.

Ubuntu 12.04 LTS Installed
I have Linux running on my Dell laptop. No internet though. Something about installing broadcom drivers ..
What do I need to do, sir?
tdhite said:
Are you Linux savvy at all? All this crap is far easier on Linux. I guarantee the drivers are absolute cakewalk -- there isn't a specific driver at all, just a rule to tell the kernel about the device.
I can give you the udev rule for the phone if you are sick of trying to get Windows to work. The Android SDK is also quite easy to install.
If you want to try, just install Ubuntu 12.04 LTS. Later versions also work, but that version is the current stable release. I can help from there.
Click to expand...
Click to collapse

Ogre77497 said:
I have Linux running on my Dell laptop. No internet though. Something about installing broadcom drivers ..
What do I need to do, sir?
Click to expand...
Click to collapse
Check PM

bigdaddy619 said:
Check PM
Click to expand...
Click to collapse
@bigdaddy619 probably got you covered, but if not, let me know. Your friend for Broadcom chips on Dell boxes is here:
https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx
The gist is pretty simple. If you don't know which wireless you have, do this:
1) widen your terminal window so you have ample room (good and wide);
2) run sudo lspci -v
Hunt down the Broadcom info -- it'll say which device is your broadcom wifi. Just need the numbers.

Working ..
I feel like I'm making some progress here, but it's still not being recognized. Everything worked great up until ...
After closing the SDK window, I connected the HTC One, and "Fastboot USB" came up on my phone. I typed adb devices and got a line "List of Devices attached" by nothing was showing as being attached.
If I enter a fastboot command, it hangs saying "waiting on device".
tdhite said:
When you get it installed, login and open a terminal windows (it'll install Unity by default, so click on the first button on the left sidebar and search for terminal, then click on it), then type exactly the following (cut/copy/paste should do it too) noting that the first command will make you give your password since sudo requests root level access:
sudo apt-get update -y
sudo apt-get install -y wget openjdk-7-jdk
wget http://dl.google.com/android/android-sdk_r22.3-linux.tgz
mkdir ~/bin
cd ~/bin
tar xvzf ~/android-sdk_r22.3-linux.tgz
cat >> ~/.bashrc <<EOF
if [ -d ${HOME}/bin/android-sdk-linux ]; then
PATH+=":${HOME}/bin/android-sdk-linux/tools"
PATH+=":${HOME}/bin/android-sdk-linux/platform-tools"
fi
export PATH
EOF
exit
That last command will exit the terminal. Start another and it'll read the .bashrc file and presto -- you have SDK access from everywhere.
Then, type this command:
android
That will bring up the SDK UI -- let it download/install all of the latest stuff (r22 of the tools and whatnot).
When done, close the android SDK window.
Type adb (bet it works), but fastboot will require root access (I'm not going to teach you how to get around that yet -- no problem, you just run sudo and I'll show that in a sec).
Finally, plug in your HTC One and type adb devices and let's see if it didn't just know it already.
Lemme know.
Click to expand...
Click to collapse

Ogre77497 said:
I feel like I'm making some progress here ....
Click to expand...
Click to collapse
Hang in, writing you some instructions, just a few minutes -- just need to get a udev rule into place but I want to make it easy for you.
---------- Post added at 08:18 PM ---------- Previous post was at 07:50 PM ----------
tdhite said:
Hang in, writing you some instructions, just a few minutes -- just need to get a udev rule into place but I want to make it easy for you.
Click to expand...
Click to collapse
Actually -- let's walk before we run. I loaded up Ubuntu real quick to assure I can duplicate what I want you to see. So, do this:
1) connect (if not already connected) the HTC to the usb port so you get 'fastboot (usb)' as normal;
2) type the following:
sudo su
lsusb -v >/tmp/lsusb.txt
chmod 666 /tmp/lsbusb.txt
exit
Now, edit that file in the text editor (just search for 'edit' like you did for 'termina' and select the "Text Editor". When you get that open, have it "File | Open" the file above -- /tmp/lsusb.txt
Then look through for text similar to what I give below. If we get that -- I need the idVendor line -- it should read: "idVendor 0x0bb4 High Tech Computer Corp."
I copied some sample output from my own machine so you can see how it should look:
--------
probably a bunch of stuff we don't care about, then something like...
Bus 001 Device 005: ID 0bb4:0ff0 High Tech Computer Corp.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0bb4 High Tech Computer Corp.
idProduct 0x0ff0
bcdDevice 1.00
iManufacturer 1 htc, Inc
iProduct 2 Android 1.0
iSerial 3 XXXXXXXXXXXX (I X'd this out -- it'll be your device serial id).
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
and a bunch more stuff...
If we don't see that, we got troubles. If we do -- we'll make a udev rule to load it up for adb and fastboot.

It appears he's bricked, when we first mounted the phone to the PC and it tried to install drivers we got QHSUSB_DLOAD which usually indicates a brick.
The strange thing was we could still access fastbootusb and the PC would recognize it being in fastboot. But any other command then fastboot devices would lock up the bootloader and fail.

Getting Closer
That's exactly it. "idVendor 0x0bb4 High Tech Computer Corp."
Finally, something worked. Thanks.
Now, edit that file in the text editor (just search for 'edit' like you did for 'termina' and select the "Text Editor". When you get that open, have it "File | Open" the file above -- /tmp/lsusb.txt
Then look through for text similar to what I give below. If we get that -- I need the idVendor line -- it should read: "idVendor 0x0bb4 High Tech Computer Corp."