Sorry if someone had posted this before.
I had my phone unlocked and rooted. It is running the latest noctural dirty rom. (I used the 1 click all in one)
Recently my computer crash and I had to do some restore and my htc stuff is wiped
I install HTC drivers again. But when I went to check my CID, fastboot, or do a command to go into bootloader/recovery, said device not found
I did have usb debugging checked, but it doesn't show the notification on status bar (I had the notify checked).
so i'm not sure if it's my computer or the rom that's not connecting.
anyone can help me? thanks.
Or maybe the cable..some cables connect me and some dont
very common problem. Probably on the computer end, and not the phone. Try a different USB port, try uninstalling the HTC drivers and installing again. Make sure its the latest version. Also try a different cable, as suggested. You might even have to try a different computer.
One of the above suggestions almost always solves the issue of the computer not "seeing" the phone.
What version of windows are you on?
Sent from my HTC One X using Tapatalk 2
Could you post a step by step of what you are doing? It would be easier to identify the problem.
Also check to see if your USB drivers are installed correctly. (If you have legit copy of windows and the driver CD for the target computer you should be good)
I had a legit copy of windows but lost the driver CD. I had to manually install them all
Sent from my HTC One XL using Tapatalk 2
Bricked HTC One and bootloop
How can I bring my HTC One back to Stockfactory
6 days old, messed up with rooting
Can start in bootloader
Rianta said:
How can I bring my HTC One back to Stockfactory
6 days old, messed up with rooting
Can start in bootloader
Click to expand...
Click to collapse
Much more information required. Do you really expect anyone to be able to help with just that? You're in the wrong forum anyway, so you need to go and ask in the HTC One forum. When you do, please provide every piece of relevant possible.
Sent from my Evita
Related
I am currently running Froyo 2.2 Red Glass Nov 2 Update using the Firerat Partition Mod. I am using Windows 7 Ultimate and I can't get ADB to work. It's something with the drivers. Does anyone have the drivers needed to get ADB working on Windows 7. I think it may be the updates Windows pushed down but it could be something else. Also I wanted to know, if there's a way to flash a recovery without using adb. My recovery is f*cked...I had RA-1.7 (Darch Unofficial) working properly, but wanted to see what was the benefit of using ClockWorks and I went from Clockwork to 1.6.2 and now I can't boot into recovery at all. If you need a log let me know. Thanks!
SN: I know this is in the wrong forum but I can't get my phone to boot into recovery nor use adb on my pc to flash a new recovery image. I need help because I'm gonna go crazy...AAAHHHH...wouldn't you do the same for your Hero???...lol...but seriously, I need help like yesterday if anyone has a solution please PM me or post. Thanks Guys...
I can't remember why but that happened to me. I'm running windows 7 64 bit. Try using the flash_image command and push a new recovery I always use amon ro 1.6.2. You can do that from terminal on your phone if you have to. I don't know if your s-off but if worse comes to worse then you could use a HERCIMG.zip Also another guy wrote about this in the q&a section. But it could have been deleted. I remember I ended up running the ruu at the end. It's not the computer it's the phone
WOW..you really need to search and put this in the right section. you even knew this was the wrong section and only posted cuz its a busier section!!
If you would have just even looked through this section a bit you wouldve found this thread that has the drivers.
http://forum.xda-developers.com/showthread.php?t=832240&highlight=drivers
Read this also it will help
http://www.xda-developers.com/announcements/a-reminder-from-the-xda-moderator-team/
As for your problem im sorry i cant help you out but if you post in the Q&A section like your supposed to then im sure someone there can figure it out. Possibly IMPALER as he seems to be on alot.
Good Luck with finding something out.
Correction for ^^^
t12icky0 said:
WOW..you really need to search and put this in the right section. you even knew this was the wrong section and only posted cuz its a busier section!!
If you would have just even looked through this section a bit you wouldve found this thread that has the drivers.
http://forum.xda-developers.com/showthread.php?t=832240&highlight=drivers
Read this also it will help
http://www.xda-developers.com/announcements/a-reminder-from-the-xda-moderator-team/
As for your problem im sorry i cant help you out but if you post in the Q&A section like your supposed to then im sure someone there can figure it out. Possibly IMPALER as he seems to be on alot.
Good Luck with finding something out.
Click to expand...
Click to collapse
I need x32 not x64...so I'm back at square one. Plus I did post in the right section in addition to this one. I got 41 views and no replies...that sucks right...
Try using Rom manager to re-flash clockwork?
Plan C: RUU your phone, and re-root and go from there...
There is no reason for him to reflash any recovery, as adb connectivity starts in recovery and drops when you pass it or reboot the phone and picks up from the rom itself (the adb communication interface is built into all versions of android)
Win7 32bit works fine with the 32bit ADB drivers, but just like the 64bit win7, it has hickups sometimes. That's your problem I am sure. Sometimes when you disconnect and reconnect a device (or it reboots) in windows 7 the drivers crash, and what win7 does as opposed to xp or vista, is sort of blacklisting the driver to stop it from crashing the rest of the windows system.
Ergo, you just need to reinstall the drivers you already have.. Have you tried that?
BTW, HTC Sync drivers are completely different than ADB drivers, and will cause conflicts. Did you install HTC Sync lately?
One last thing, you remember where you installed adb? Or rather your Android-sdk-Windows directory? From there it is in the usb_driver folder.
i.e. if you installed to the root of your drive, it would be in:
c:\android-sdk-windows\usb_driver\
The name of the file is android_winusb.inf
Well when you do, or either way, someone move this to the q-n-a section.
Problem solved.
"Gregory House 1, God 0" - Gregory House
B-Nice_88 said:
I need x32 not x64...so I'm back at square one. Plus I did post in the right section in addition to this one. I got 41 views and no replies...that sucks right...
Click to expand...
Click to collapse
Hows this going? Try pming carbon kang he had the same issue back in May it's happened to quite a few of us after using a different recovery and flashing this one rom. I know it sounds crazy and shouldn't be happening but it did. The thread that it was in got deleted probably by mistake.
I have a problem. I just got my Android a couple of days ago and I really badly want to root it. I've tried multiple different programs and with each one the problem I get is "Waiting for device" in the cmd/terminal (Tried on multiple platforms: Vista, Win7, Ubuntu). I've tried installing drivers too and still didn't work (maybe the wrong drivers?).
Yes I realize that I am a "noob", but I really need some help here.
Got USB Debugging enabled ??
Got the correct upto date drivers ?
You navigated to the right location in ADB ??
azzledazzle said:
Got USB Debugging enabled ??
Got the correct upto date drivers ?
You navigated to the right location in ADB ??
Click to expand...
Click to collapse
>Yes
>I think so, not positive.
> What do you mean?
bumpp someone help?
Well Redownload the drivers and see if that helps, You could try Hasoon2000's All In One Kit to help with this. http://forum.xda-developers.com/showthread.php?t=1604677
As for ADB, (Android Debug Bridge) you should have this already, You need it to get unlock the bootloader and flash superboot (root) http://forum.xda-developers.com/showthread.php?t=1583427
Be sure to check out those links and also look at my FAQ section http://forum.xda-developers.com/showpost.php?p=24884624&postcount=3
I have all the files that it says are necessary to unlock the bootloader. It's just when I type "fastboot oem get_identifier_token" it just sits there saying "waiting for device".
I've tried hansoon's all in one program as well and it didn't work either.
Well that means it cannot find your phone, So the issue lies with the drivers and/or the location from which the command prompt is opened..
Put all of the files into 1 folder called android or adb and move that 1 folder to the root of your C Drive..
This should make navigating easier. Also, In that folder should be adb.exe and fastboot.exe do you have these ?
I fixed this by just playing around with it a bit more. Thanks for the help, though.
infam0us me said:
I fixed this by just playing around with it a bit more. Thanks for the help, though.
Click to expand...
Click to collapse
what exactly did you do? I am stuck with this problem for a long time now. nothing seems to help. what does "playing around" mean?
windows 8.1
htc one s (c2)
morphication said:
what exactly did you do? I am stuck with this problem for a long time now. nothing seems to help. what does "playing around" mean?
windows 8.1
htc one s (c2)
Click to expand...
Click to collapse
Well man, I really wish I could help you out because I remember how frustrating this was for me. This post was 2 and a half years ago though. Just really make sure that your drivers are up to date. If I could remember my exact solution I would help you out for sure.
infam0us me said:
Well man, I really wish I could help you out because I remember how frustrating this was for me. This post was 2 and a half years ago though. Just really make sure that your drivers are up to date. If I could remember my exact solution I would help you out for sure.
Click to expand...
Click to collapse
ok. it was windows 8 not allowing unsigned drivers to install properly. note: not "not installing at all", but "not installing properly". meaning: htc drivers installed somehow, so I was able to see the device and copy files around, but it was not enough for flashing roms.
so I started this guide to disable driver signature:
https://www.youtube.com/watch?v=gmw86KplqmU
... but my laptop is a business laptop and this guide demands BitLocker key if hard drive is encrypted (mine is). I also have a windows 7 desktop machine. So I decided to go the easy and quick way of simply doing flashing on my desktop computer. Windows 7 worked like a charm. But I'm sure the guide above would've helped as well. If somebody tries that, please post results.
Hey Guys
I tried searching and saw a few people with my issue but no real solution. I just got a One S coming from Sprint (Evo4g) and enjoy the One S except for the no SD card thing. I have no issue connecting my phone to my windows 7 machine as a disk drive, but I have 2 computers at work with XP and both do not recognize my phone. I get a "USB device not recognized" message on my taskbar and when I click it, there is no driver installed for my phone. Same thing with both XP machines. OK, so I search the internet for an HTC USB driver, cant find one ANYWHERE, a few sites that seemed to have had them have removed them. HTC website is missing the One S support page entirely right now, awesome. So after I clicked around while I eventually found a link for HTC Sync software and tried installing that. Still no driver was installed and cannot connect that way either. At a loss here, any advice? If so does anyone have any links for actual things to install that can fix this issue?
Feel like a newb here but coming from the EVO i am very familiar with rooting, installing ROMs etc so find it hard to believe this is so difficult.
Thanks!
David
really nothing after a few days?
dskater411 said:
really nothing after a few days?
Click to expand...
Click to collapse
Maybe no one uses XP when there is nothing wrong with Windows 7 but if you rooted already you use Flash Image GUI for flashing boot.img then you wont need a PC to install a rom.
Hi there
I just got a new laptop running Window 8.1
I want to flash the latest TWRP to able to flash android 4.4 kitkat. But after i install "htc sync manager" and "htc sync", still dont have usb-driver on fastboot mode. So i cant flash the TWRP recovery.
Can any1 help me step by step how to get the fastboot-usb to install the TWRP on Window8?
My phone got everything already, just need the usb-driver, so in the fastboot can recognize the usb, so that i can flash latest TWRP.
(My phone running TWRP 2.3.3.0 already)
(My new laptop had Android-sdk already)
Thank for helping me guys :good:
Have you searched for a solution? I've seen a few threads discussing this problem.
Sent from my Evita.
timmaaa said:
Have you searched for a solution? I've seen a few threads discussing this problem.
Sent from my Evita.
Click to expand...
Click to collapse
i did, but not step by step, i quite noob, thats why i am asking man :crying:
If you found any thread that have a detail and step by step, please let me know
There are threads that detail it step by step but you need to find them.
Sent from my Evita.
lol, if i can do that, i am not spending my time to create this thread.
Any1 else please???
Surely you can use the XDA search feature and/or Google?
Sent from my Evita.
timmaaa said:
Surely you can use the XDA search feature and/or Google?
Sent from my Evita.
Click to expand...
Click to collapse
actually, i did that already, but after that, still nothing change. Even reinstall htc sync manager, but still when i reboot the phone to bootloader and go to fastboot, usb still not working. I dont know why, like i said, i am quite noob, thats why i am asking for some help if any1 know my problem.
Anyway, thanks alot for your help man, very appreciate but the problem still here
PS: another thing is my laptop using AMD cpu, and all of solution is just for intel-usb @[email protected] i cant follow someway, such as this:
http://forum.xda-developers.com/showthread.php?t=2347317&page=4
Unfortunately I don't run Windows 8 so I don't have any personal experience with getting it to work. The best solution I've seen people talk about is to use a different version of Windows.
Sent from my Evita.
Run a Linux live cd and use fastboot that way.
Sent from my iPhone using Tapatalk
There is no signed Windows 8.1 Android driver.
To make it work there is several hoops to jump through. Really its easier to just boot into Linux or use another computer.
Eg my Desktop runs Windows 8.1 but my laptop has Windows 7, so I use the laptop for fastboot.
thinhletien said:
Hi there
I just got a new laptop running Window 8.1
I want to flash the latest TWRP to able to flash android 4.4 kitkat. But after i install "htc sync manager" and "htc sync", still dont have usb-driver on fastboot mode. So i cant flash the TWRP recovery.
Can any1 help me step by step how to get the fastboot-usb to install the TWRP on Window8?
My phone got everything already, just need the usb-driver, so in the fastboot can recognize the usb, so that i can flash latest TWRP.
(My phone running TWRP 2.3.3.0 already)
(My new laptop had Android-sdk already)
Thank for helping me guys :good:
Click to expand...
Click to collapse
windows 8.1 wont recognize my htc one x with ICS rom. however when i updated to jellybean 4.1.1 and connected to the windows 8.1, it installed all the required drivers itself and now I am able to connect the phone/fastboot etc. I tried installing HTC Sync previously but that doesnt help cuz while the installation process the Htc Driver Installer fails to install.
Good morning everyone.
First of all I want to apologize for my english, that I'm afraid it's very poor.
My question goes next: I bought an used Samsung Galaxy tab 2 7'' p3100 3G and it has a very big problem. It can't be connected to any pc, windows or mac. It's not a drivers' problem, so when the device is connected, the pc does nothing. Not even a display in the device manager, or a noise. However, it usually charges. I say usually because sometimes the icon battery shows a red ray, but it charges spending more time. That's all. It has been proved with three different original cables in several computers running different SO.
I don't know if it's a connector problem or it's a Rom one. It has an operator locked SO with Android 4.0.4 that not even shows the OTA update option in the menu. And I cannot select the way I want to be connected by usb in the "Storage" options.
The fact is I cannot update the device and I cannot root it in order to install a better rom or an original stock one.
I've googled all I can do to find a way for rooting the device, but all the roads drive me to the same point: Odin. The software I cannot use because my device can't be connected to any Pc.
I know this forum is my last chance. There are some ways like z4root or framaroot that work in another devices (Galaxy S for example, I think), but they have not been ported to my device. I think my chances are to make it by an apk o perhaps flashing a signed file from the original recovery.
I just need to install a simple clockword mod or having the device temporary rooted to install and run the Odin's apk that allows me to install a pre-rooted rom, an open recovery... Just a simple step for one man, But the Colorado's Canyon for me in my situation.
If someone of you know any solution or want to help me, I'll be truly grateful. And I didn't even mind to pay him for his help.
Thank you very much in advance.
Even_Flow said:
Good morning everyone.
First of all I want to apologize for my english, that I'm afraid it's very poor.
My question goes next: I bought an used Samsung Galaxy tab 2 7'' p3100 3G and it has a very big problem. It can't be connected to any pc, windows or mac. It's not a drivers' problem, so when the device is connected, the pc does nothing. Not even a display in the device manager, or a noise. However, it usually charges. I say usually because sometimes the icon battery shows a red ray, but it charges spending more time. That's all. It has been proved with three different original cables in several computers running different SO.
I don't know if it's a connector problem or it's a Rom one. It has an operator locked SO with Android 4.0.4 that not even shows the OTA update option in the menu. And I cannot select the way I want to be connected by usb in the "Storage" options.
The fact is I cannot update the device and I cannot root it in order to install a better rom or an original stock one.
I've googled all I can do to find a way for rooting the device, but all the roads drive me to the same point: Odin. The software I cannot use because my device can't be connected to any Pc.
I know this forum is my last chance. There are some ways like z4root or framaroot that work in another devices (Galaxy S for example, I think), but they have not been ported to my device. I think my chances are to make it by an apk o perhaps flashing a signed file from the original recovery.
I just need to install a simple clockword mod or having the device temporary rooted to install and run the Odin's apk that allows me to install a pre-rooted rom, an open recovery... Just a simple step for one man, But the Colorado's Canyon for me in my situation.
If someone of you know any solution or want to help me, I'll be truly grateful. And I didn't even mind to pay him for his help.
Thank you very much in advance.
Click to expand...
Click to collapse
Have you manually installed the drivers? If not, download the samsung drivers, install and try again. Read through the link below to find the drivers.
http://forum.xda-developers.com/showthread.php?t=2510669
cwyman said:
Have you manually installed the drivers? If not, download the samsung drivers, install and try again. Read through the link below to find the drivers.
http://forum.xda-developers.com/showthread.php?t=2510669
Click to expand...
Click to collapse
Unfortunately yes. I've tried with several versions of Kies, by installing manually the drivers and it doesn't work. The fact is I connect the device and the pc does nothing. Not even the device manager shows a new device or is alterated in some way. It's like one data pin in the connector was damaged or the rom was corrupted and it doesn't let the device be recognized.
I think my only chance is to make everything inside the device. By sd in the boot manager or with an apk. If not, I'm condemned to an obsolete device that could not even be updated.
Thanks for trying to help me.
Even_Flow said:
Unfortunately yes. I've tried with several versions of Kies, by installing manually the drivers and it doesn't work. The fact is I connect the device and the pc does nothing. Not even the device manager shows a new device or is alterated in some way. It's like one data pin in the connector was damaged or the rom was corrupted and it doesn't let the device be recognized.
I think my only chance is to make everything inside the device. By sd in the boot manager or with an apk. If not, I'm condemned to an obsolete device that could not even be updated.
Thanks for trying to help me.
Click to expand...
Click to collapse
This may sound absurd, but try a different version of the drivers. I had to install like a dozen drivers before it worked
mirzafran said:
This may sound absurd, but try a different version of the drivers. I had to install like a dozen drivers before it worked
Click to expand...
Click to collapse
I agree. The drivers can be so touchy. I'd uninstall and reinstall drivers numerous times before giving up. Good luck!
Sent from my GT-p511x
your cable is faulty. Get another one on ebay cheap.
I'm afraid I've tried with three different cables, as I said (one of them original from Samsung and new), two Windows Pc's, one mac and about fifteen different drivers.
Believe me: I've rooted with no problem more than twenty different devices (and jailbreaked another ones ) and this is the first time I cannot make it.
Think it's a hardware problem or a corrupted rom one. In both cases I have to root it by an apk or a flash from the sd.
Anyway, I appreciate very much your help, boys.
Even_Flow said:
I'm afraid I've tried with three different cables, as I said (one of them original from Samsung and new), two Windows Pc's, one mac and about fifteen different drivers.
Believe me: I've rooted with no problem more than twenty different devices (and jailbreaked another ones ) and this is the first time I cannot make it.
Think it's a hardware problem or a corrupted rom one. In both cases I have to root it by an apk or a flash from the sd.
Anyway, I appreciate very much your help, boys.
Click to expand...
Click to collapse
I'm in a similar situation with a Galaxy Tab 2 p3113tsyxar
It is not recognized by any computer, and my next step is to try another cord manana. Until then (hopefully) I've got a nice paperweight.
You have not rooted ur tab till now......so u have not played with your firmwares! So its better to visit a samsung store. If you have warranty then they will do it in free.(And your android will also get updated!)
If I helped you, just press thanks!