Database Info

[Q] ADB & Windows 7??!!!

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.

Waiting for Device?

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.

[Problem] AT&T Windows8 Fastboot ADB

Hello everyone its your friendly neighborhood hero..... Nah jk.
Anyways to the point, I would like to unlock and root my phone through my own computer an ASUS G75VW-BBK5 upgraded to Windows8 :highfive: So I installed Hasoon's All-in-One toolkit for the AT&T HTC One X, also got my HTC Drivers installed on my moms Windows7 and brought them over to my Windows8, installed successfully, I think. I have the Android development kit and all those proper files installed. I do the easy way of going into bootloader by using Hasoon's toolkit. I click volume down once on the fastboot and then it says fastboot usb. So then I try to get my bootloader unlock code and everything... But it says it failed on Hasoon's and waiting for device just by using the command prompt. So then I go back to my moms computer and copy my previous version of the Unlock_code.bin then bring it to my computer. It didn't work. I think I heard also that it doesn't work with USB 3.0's. Well in that case I'm doomed because my computer has four of them.
Problem relating to CM10 installation. I have had TWRP and my bootloader unlocked and relocked before. I had Viper XL on it before for one day until I decided I wanted to go to CM10 Nightlies. That's when all this happened. When I did try to flash CM10 downloaded on my unlocked booloader with SU it kept getting stuck in the endless spiral of CM10 doom. Which in my opinion <----- I blame on AT&T. Can someone please help me get my device be able to properly fastboot usb to my Windows8 with usb 3.0's and help me get CM10. Sorry for all this but once I do it once I should be able to do it again.:highfive:
Tommorow I well come back and check on the post with my phone ATM relocked and RUU'd. Also please wish me luck on the drivers test for the official licence. :good:
-Sincerely: Techinstein

Device not found, HTC driver installed and ADB is running

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

Trying to update twrp..."trying"

I was trying to update this Nexus S, used to be mine but gave it away to someone, now is back and I was trying to update the whole thing, recovery, Os, yet I can't find a proper way to update the recovery and also I have Win8...when I got this phone rooted I had a Win7 machine, life was great, now with Win8 some things seem far from easy.
So I wonder if any kind soul could assist me as to lend me a hand about updating TWRP 2.3 to 2.7 so I can install a fresh rom, i have tried TWRP manager (useless as it can't find the proper device), Flashify is useless also as it can't find the img file and only shows TWRP 2.1 (why the fk do I need 2.1 when I have 2.3 ?), and Rashr is no good (it simple doesn't do anything at all... )
Any help is welcome.

fenrry said:
I was trying to update this Nexus S, used to be mine but gave it away to someone, now is back and I was trying to update the whole thing, recovery, Os, yet I can't find a proper way to update the recovery and also I have Win8...when I got this phone rooted I had a Win7 machine, life was great, now with Win8 some things seem far from easy.
So I wonder if any kind soul could assist me as to lend me a hand about updating TWRP 2.3 to 2.7 so I can install a fresh rom, i have tried TWRP manager (useless as it can't find the proper device), Flashify is useless also as it can't find the img file and only shows TWRP 2.1 (why the fk do I need 2.1 when I have 2.3 ?), and Rashr is no good (it simple doesn't do anything at all... )
Any help is welcome.
Click to expand...
Click to collapse
Google "Nexus Root Toolkit". Works great with Windows 8.1.

rhyang said:
Google "Nexus Root Toolkit". Works great with Windows 8.1.
Click to expand...
Click to collapse
I found something after a lot of searching and reading around back and forth on different places, thanks, I will keep it in mind anyway cause right now there is not that many sources for info on Nexus S.

fenrry said:
I found something after a lot of searching and reading around back and forth on different places, thanks, I will keep it in mind anyway cause right now there is not that many sources for info on Nexus S.
Click to expand...
Click to collapse
I have uploaded TWRP v2.8.0.1 flashable zip. Flash it like any normal ROM in the existing recovery.
Link: http://forum.xda-developers.com/showpost.php?p=55616780&postcount=115
Also, let me if you need help in installing drivers in Windows 8. I too am using Nexus S on Windows 8.1

smit.sanghavi said:
I have uploaded TWRP v2.8.0.1 flashable zip. Flash it like any normal ROM in the existing recovery.
Link: http://forum.xda-developers.com/showpost.php?p=55616780&postcount=115
Also, let me if you need help in installing drivers in Windows 8. I too am using Nexus S on Windows 8.1
Click to expand...
Click to collapse
Thanks so much fo the Zip, is way easier to just have this done via TWRP/ZIP, than trying to install drivers and so on, it becomes a pain when one thing fails and then u have to start downloading files drivers and more.
Now I'll just start checking roms!

fenrry said:
I was trying to update this Nexus S, used to be mine but gave it away to someone, now is back and I was trying to update the whole thing, recovery, Os, yet I can't find a proper way to update the recovery and also I have Win8...when I got this phone rooted I had a Win7 machine, life was great, now with Win8 some things seem far from easy.
So I wonder if any kind soul could assist me as to lend me a hand about updating TWRP 2.3 to 2.7 so I can install a fresh rom, i have tried TWRP manager (useless as it can't find the proper device), Flashify is useless also as it can't find the img file and only shows TWRP 2.1 (why the fk do I need 2.1 when I have 2.3 ?), and Rashr is no good (it simple doesn't do anything at all... )
Any help is welcome.
Click to expand...
Click to collapse
Hi There,
The latest Recovery for Nexus S is TWRP v2.8.x. Well u will need to flash the Twrp v2.8.x using fastboot because if you try installing the recovery using the TWRP Manager it will crash. I have a guide on how to root nexus s in the nexus s development section..Go through it . If you have a rooted Nexus S then skip to contect showing how to flash a custom recovery using Fastboot in my guide go through it and Enjoy..
Happy Flashing.
Good Luck

fenrry said:
I was trying to update this Nexus S, used to be mine but gave it away to someone, now is back and I was trying to update the whole thing, recovery, Os, yet I can't find a proper way to update the recovery and also I have Win8...when I got this phone rooted I had a Win7 machine, life was great, now with Win8 some things seem far from easy.
So I wonder if any kind soul could assist me as to lend me a hand about updating TWRP 2.3 to 2.7 so I can install a fresh rom, i have tried TWRP manager (useless as it can't find the proper device), Flashify is useless also as it can't find the img file and only shows TWRP 2.1 (why the fk do I need 2.1 when I have 2.3 ?), and Rashr is no good (it simple doesn't do anything at all... )
Any help is welcome.
Click to expand...
Click to collapse
Hi there,
i just made a .doc in which i have briefly described how to flash twrp on nexus s just download the file and go through it.

Thanks!, I forgot to reply about this, I managed to get things working, I really don't know how it happened but after repeating the steps several times something must have kicked and things finally worked.

fenrry said:
Thanks!, I forgot to reply about this, I managed to get things working, I really don't know how it happened but after repeating the steps several times something must have kicked and things finally worked.
Click to expand...
Click to collapse
Ok Brother, Chill and Enjoy.