Go Back   Android Forums > Android Phones > HTC EVO 3D > (CDMA) EVO 3D - All Things Root

Get excited for the Samsung Galaxy S5! Find everything you need and discuss it in our Galaxy S5 Forum!

test: Reply
 
LinkBack Thread Tools
Old January 2nd, 2012, 06:33 PM   #1 (permalink)
New Member
Thread Author (OP)
 
Join Date: Jan 2012
Posts: 4
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default Help w HTCdev "waiting for device"

Hello, I'm completely phone ******ed, I'm trying to root the gf's evo 3d so she can use open garden tether. It took like 5 seconds with my evo 4g and I'm using the HTCdev unlock so it should be just as easy but I cannot get the last step to work.

I am supposed to put all the files into a folder and run the fastboot get cmd and I do that no problem but then instead of the token printing all I get is
<waiting for device>

the phone is sitting on the FASTBOOT USB screen, it is HBOOT 1.50. It says S-ON (I don't know what that means I just saw it referenced a lot) and it is connected via USB so I don't know why it isn't being recognized.

Thanks for any help.

kbakermemphis is offline  
Reply With Quote
sponsored links
Old January 2nd, 2012, 09:38 PM   #2 (permalink)
♡ Spidey Sense !! ♡
 
DonB's Avatar
 
Join Date: Nov 2009
Location: 18th Hole Of the Golf Course
Gender: Male
Posts: 18,102
 
Device(s): Moto X 16 GB / Stock all the way on AIO Wireless
Carrier: Aio Wireless

Thanks: 6,235
Thanked 6,729 Times in 3,975 Posts
Default

Make sure your USB debugging is check marked



Quote:
Originally Posted by kbakermemphis View Post
Hello, I'm completely phone ******ed, I'm trying to root the gf's evo 3d so she can use open garden tether. It took like 5 seconds with my evo 4g and I'm using the HTCdev unlock so it should be just as easy but I cannot get the last step to work.

I am supposed to put all the files into a folder and run the fastboot get cmd and I do that no problem but then instead of the token printing all I get is
<waiting for device>

the phone is sitting on the FASTBOOT USB screen, it is HBOOT 1.50. It says S-ON (I don't know what that means I just saw it referenced a lot) and it is connected via USB so I don't know why it isn't being recognized.

Thanks for any help.
__________________


Sticky: Lost/Stolen or Locked out of Device. Read Here!


Site Rules/Guidelines
If something needs attention, Report it .
If someone helped you, hit to show it.


DonB is online now  
Reply With Quote
Old January 3rd, 2012, 09:04 PM   #3 (permalink)
New Member
Thread Author (OP)
 
Join Date: Jan 2012
Posts: 4
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

Yeah it's checked.

Quote:
Originally Posted by DonB View Post
Make sure your USB debugging is check marked
kbakermemphis is offline  
Reply With Quote
Old January 3rd, 2012, 09:14 PM   #4 (permalink)
Senior Member
 
wake69's Avatar
 
Join Date: Jun 2010
Location: Georgia
Posts: 1,808
 
Device(s):
Carrier: Verizon

Thanks: 98
Thanked 516 Times in 399 Posts
Default

make sure all software is installed. install android sdk dont just unzip it also install jdk and htc sync

after you fully install android sdk, copy the files in the tools folder to the platform tools folder. the install should take between 20-45 mins
__________________
Phone: HTC One M8
Root Method: Not Yet
wake69 is offline  
Reply With Quote
Old January 8th, 2012, 08:08 PM   #5 (permalink)
New Member
Thread Author (OP)
 
Join Date: Jan 2012
Posts: 4
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

OK, so I figured out what the problem was. The fastboot I was trying to use was 69kb and there was another one that was 180kb and once I switched that one into the folder it worked. Now I'm at the point that I have downloaded and moved the .bin into the correct folder and run the unlock cmd and the print looks just like the example on the HTCdev site but I never got the "Unlock Bootloader" screen on the phone. Nothing happened at all. I turned it on thinking maybe it would pop up on reboot but nothing. I tried it again, nadda.

Any thoughts on this one?
kbakermemphis is offline  
Reply With Quote
Old January 9th, 2012, 06:51 AM   #6 (permalink)
♡ Spidey Sense !! ♡
 
DonB's Avatar
 
Join Date: Nov 2009
Location: 18th Hole Of the Golf Course
Gender: Male
Posts: 18,102
 
Device(s): Moto X 16 GB / Stock all the way on AIO Wireless
Carrier: Aio Wireless

Thanks: 6,235
Thanked 6,729 Times in 3,975 Posts
Default

If you are on HBoot 1.50 you will not get S-OFF but you will be rooted.


Quote:
Originally Posted by kbakermemphis View Post
OK, so I figured out what the problem was. The fastboot I was trying to use was 69kb and there was another one that was 180kb and once I switched that one into the folder it worked. Now I'm at the point that I have downloaded and moved the .bin into the correct folder and run the unlock cmd and the print looks just like the example on the HTCdev site but I never got the "Unlock Bootloader" screen on the phone. Nothing happened at all. I turned it on thinking maybe it would pop up on reboot but nothing. I tried it again, nadda.

Any thoughts on this one?
DonB is online now  
Reply With Quote
Old January 11th, 2012, 04:17 AM   #7 (permalink)
New Member
Thread Author (OP)
 
Join Date: Jan 2012
Posts: 4
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

[GUIDE] HTC Unlock Hboot 1.50 + TWRP Recovery + Root + Flash!! [9.11.11] - xda-developers <---the answer.
kbakermemphis is offline  
Reply With Quote
Old January 14th, 2012, 04:50 PM   #8 (permalink)
 
Join Date: Jun 2010
Location: North Richland Hills, TX
Posts: 999
 
Device(s): Samsung Galaxy S3; HTC Evo 3D (wife); HTC Evo 4G (gone)
Carrier: Not Provided

Thanks: 52
Thanked 198 Times in 149 Posts
Default

USB Debugging is checked and I have the 180kb version of Fastboot loaded in the folder. Still nothing. It always stops at the "<waiting for device>" prompt.
bvbull200 is offline  
Reply With Quote
Old March 19th, 2012, 02:22 AM   #9 (permalink)
New Member
 
Join Date: Mar 2012
Posts: 2
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 2 Times in 2 Posts
Default Fixed this on Mint 12 Lisa

I had this same issue after actually attaining root with my 3D. The device seems to have been recognized by the os, and was available to move files around on the SD, but running
Code:
./adb devices
only yielded:
Code:
<waiting for device>
So I scoured other forums about this, and it seems to be a general Linux issue, though it had escaped me at the time since I had previously successfully mounted a recover image and had root. The fix seems to be to updated the udev rules on your machine, then restart

First jump into root
Code:
su
The perform the following commands:

Code:
cd /etc/udev/rules.d
touch 51-android.rules
nano 51-android.rules
Can be simply
Code:
nano /etc/udev/rules.d/51-androidrules
Then entering the following line:d
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0e79", MODE="0666"
Ctrl+X to save, "y" to save changes. Then you need to reboot (really linux? fine.)

Once back up you need to get the phone into recovery with the power/volume down buttons again. Then check it out:
Code:
./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached 
HT16THX18787	device
Now, you can use the USB bootloader to flash your recover/other roms.

Reflashing or flashing a new recover allowed me to flash roms where I was previously unable to do so as well.

I would love to cite sources on this one so credit goes where due, but I understand there is no linking as a new poster, and I'd like to respect the rules of the forum. If allowed I will be happy to link.
champaine is offline  
Reply With Quote
The Following User Says Thank You to champaine For This Useful Post:
jerofld (March 20th, 2012)
Old March 19th, 2012, 09:15 AM   #10 (permalink)
Fixing stuff is not easy
 
Join Date: May 2011
Location: Over there <points>
Gender: Male
Posts: 7,690
 
Device(s): Samsung Galaxy S3; Asus Infinity
Carrier: Sprint

Thanks: 2,117
Thanked 4,311 Times in 2,513 Posts
jerofld
Default

The no linking on your first post is an anti-spam policy. You can posts URLs after your first post. But we do appreciate people citing their source.
jerofld is offline  
Reply With Quote
sponsored links
Old March 19th, 2012, 09:32 PM   #11 (permalink)
New Member
 
Join Date: Mar 2012
Posts: 2
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 2 Times in 2 Posts
Default Where it's due.

Quote:
Originally Posted by jerofld View Post
The no linking on your first post is an anti-spam policy. You can posts URLs after your first post. But we do appreciate people citing their source.
Glad to hear it

Stack overflow helped out a bit with general debugging mode:
android - Detecting device for debugging (ADB) does not work - Stack Overflow

Found the vendor information here: Setting Up ADB/USB Drivers for Android Devices in Linux (Ubuntu) Esau Silva

Also, there are a lot of useful adb commands on that page, makes a great reference.
champaine is offline  
Reply With Quote
The Following User Says Thank You to champaine For This Useful Post:
jerofld (March 20th, 2012)
Old March 10th, 2013, 12:29 PM   #12 (permalink)
New Member
 
Join Date: Mar 2013
Posts: 4
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default omg...

I don't mean to be annoying or sound like an idiot, but I'm COMPLETELY lost. I, too, am stuck at this point where it says "waiting for device" (I'm surprised I even made it this far) but as I read the replies to troubleshoot it, I'm baffled and don't understand a word. Is there a less advanced way of explaining how to fix this from this point? Thanks in advance for any and all help!
frutekake is offline  
Reply With Quote
Old March 10th, 2013, 12:30 PM   #13 (permalink)
New Member
 
Join Date: Mar 2013
Posts: 4
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

...and I just realized this thread is almost a year old... my bad.
frutekake is offline  
Reply With Quote
Old March 10th, 2013, 02:00 PM   #14 (permalink)
Senior Member
 
remanifest's Avatar
 
Join Date: Jan 2013
Posts: 839
 
Device(s): HTC Evo V 4G
Carrier: Virgin Mobile

Thanks: 213
Thanked 318 Times in 180 Posts
Default

You just need to be in your HBOOT to do this.

Pull your battery, hold the volume-down button, and press power. Then you can run the commands.

Way to resurrect the dead frutekake!
remanifest is offline  
Reply With Quote
Old March 10th, 2013, 04:46 PM   #15 (permalink)
New Member
 
Join Date: Mar 2013
Posts: 4
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

No, I'm already in "Fastboot" mode and it says "Fastboot USB" for a minute then my computer USB messes up says the device can't be recognized then goes back to "Fastboot" and my Command Prompt will get stuck at <waiting for device> ... does that make any sense?

P.S. Thanks for your reply regardless!
frutekake is offline  
Reply With Quote
Old March 11th, 2013, 02:14 PM   #16 (permalink)
Senior Member
 
MahaloCat's Avatar
 
Join Date: Aug 2010
Location: Honolulu
Posts: 1,934
 
Device(s): htc ONE ; JellyBeaned Acer A500 Tablet ; Sony Gen 2 Gtv; Ubuntu 13.04
Carrier: Not Provided

Thanks: 344
Thanked 460 Times in 343 Posts
Default

Frutetkake - what h-bbot - are you windows or linux?
MahaloCat is offline  
Reply With Quote
Old March 11th, 2013, 08:23 PM   #17 (permalink)
New Member
 
Join Date: Mar 2013
Posts: 4
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

windows.
frutekake is offline  
Reply With Quote
Old March 12th, 2013, 03:01 AM   #18 (permalink)
Senior Member
 
MahaloCat's Avatar
 
Join Date: Aug 2010
Location: Honolulu
Posts: 1,934
 
Device(s): htc ONE ; JellyBeaned Acer A500 Tablet ; Sony Gen 2 Gtv; Ubuntu 13.04
Carrier: Not Provided

Thanks: 344
Thanked 460 Times in 343 Posts
Default

hmmm can you confirm that fastboot is unchecked...
MahaloCat is offline  
Reply With Quote
Old September 5th, 2013, 09:53 AM   #19 (permalink)
New Member
 
Join Date: Nov 2011
Posts: 3
 
Device(s):
Carrier: Not Provided

Thanks: 2
Thanked 0 Times in 0 Posts
Default

Ok, I'm stuck on the same issue (Linux, trying to root a Droid Incredible 2). HTCDev website tells me to dl/unzip the adt-bundle, then run the "SDK Manager" to download a bunch of files, from where I get adb and fastboot. Thing is, in Linux there _is_ no "SDK Manager", so what do I run? Also, adb and fastboot are already present, so do I really need to run whatever the linux equivalent is?

@champaine - I don't really understand udev, but it seems like SYSFS has become ATTR. Can you explain what the "0e79" is in:

Code:
SYSFS{idVendor}=="0e79"
Is this idVendor the same for all HTC phones?
DiagonalArg is offline  
Reply With Quote
Reply
Tags
htcdev, waiting for device


Go Back   Android Forums > Android Phones > HTC EVO 3D > (CDMA) EVO 3D - All Things Root
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -5. The time now is 04:31 AM.
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.