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.

Unsuccesasful NoDo update

Hi All,
I have been trying so hard past few days update my HD7 after getting notification. The update always suck at step two(downloading at 6%) and error code shown 801811A3. I have been installing Microsoft Fit for this code in Window 7, but still no luck to complete downloading. I have tried out more than 5 times and getting very annoy on this.Is out there anyone still facing this or anyone can help to share your experience, thanks a lot...

Your phone is jailbreak with chevronwp7?

semaka13 said:
Your phone is jailbreak with chevronwp7?
Click to expand...
Click to collapse
Yes. Jailbreak with lots of side loaded apps.

You cand find good tips here:
http://support.microsoft.com/kb/2484484/class=/en-us#801811A3_801811A8_8018119C
If you realy wanted, you know you cand hard reset, and all will go smoth. after that u will have to find a way to unlock it again.
If you already know this, tell us please how you solve the problem.

i had same problem...u should go to services and enable error reporting device...then connect with zune and update should work...worked for me...

barovidiu said:
You cand find good tips here:
http://support.microsoft.com/kb/2484484/class=/en-us#801811A3_801811A8_8018119C
If you realy wanted, you know you cand hard reset, and all will go smoth. after that u will have to find a way to unlock it again.
If you already know this, tell us please how you solve the problem.
Click to expand...
Click to collapse
Thanks for reply. I follow exactly the procedure of Microsoft Fix as mentioned should solve my problem, but yet no chance to get thru download state. This fix does not fix my PC, too bad.
I believe it is not my phone having problem, but the my PC (Zune software in particular) just could not get the file downloaded and complete the whole cycle...hard reset help?????

panicos michael said:
i had same problem...u should go to services and enable error reporting device...then connect with zune and update should work...worked for me...
Click to expand...
Click to collapse
Thanks for reply. Could you please be more specific guiding me the whole process of such setting on my PC. I m using Window 7 Home. Thanks in advance.

[q] somebody please help!!!!!

I am desperately trying to root my samsung nexus s and i am having trouble even getting started. My drivers wont install properly. If this is the wrong section i am sorry i am new to this and i would much appreciate someone private messaging me so i can give them my phone number so that they could get me started. Thank you to whoever helps me! God bless!!!!!!!

The stickies in this forum have multiple guides detailing how to root.
Sent from my Nexus S using XDA App

bcarle said:
I am desperately trying to root my samsung nexus s and i am having trouble even getting started. My drivers wont install properly. If this is the wrong section i am sorry i am new to this and i would much appreciate someone private messaging me so i can give them my phone number so that they could get me started. Thank you to whoever helps me! God bless!!!!!!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1067813
http://forum.xda-developers.com/showthread.php?t=1071500
^^Those two threads will have everything youll need or lead you to everything youll need. Google search for the Sammy drivers if you need them.

Most of the time it's just the location of the driver.
just go to device manager and look for "!" sign that says nexus s, right click and update the driver and point it to the driver located in your sdk folder (I assumed you have Android SDK)
C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver

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.

[Q] Bricked transformer, no nvflash, have APX mode

Hey guys,
I've got a TF300T running the 10.4.2.13 update (so the newest JB) without root, and no nvflash which is bricked.
I've got APX mode, but that's as far as I've got.
Any suggestions?
Help's much appreciated

jaysinclair said:
Hey guys,
I've got a TF300T running the 10.4.2.13 update (so the newest JB) without root, and no nvflash which is bricked.
I've got APX mode, but that's as far as I've got.
Any suggestions?
Help's much appreciated
Click to expand...
Click to collapse
Indeed that help much appreciated, but one question before:
Have you tried to search and read a little bit before to post your request? I don't think !!
Because if you had searched a bit, you would have seen that a few posts of this subject have previously posted.

jaysinclair said:
Hey guys,
I've got a TF300T running the 10.4.2.13 update (so the newest JB) without root, and no nvflash which is bricked.
I've got APX mode, but that's as far as I've got.
Any suggestions?
Help's much appreciated
Click to expand...
Click to collapse
Jay, I think what the gentleman above was trying to say (in a more POLITE MANNER) was that it is preferable to post a question after taking some initial steps to Google and search the forums. It's OK to post a question, but people just want to see that you've done some work beforehand. UNFORTUNATELY, various forum communities seem to antagonize new posters by harassing them to search, without really answering the question.
Try reading Here to see if anyone has had a similar problem?
Sorry I can't provide more links, as I don't know what nvflash/APX is, nor have I had a need to use it. Perhaps someone else can post some helpful links?

opethfan89 said:
Jay, I think what the gentleman above was trying to say (in a more POLITE MANNER) was that it is preferable to post a question after taking some initial steps to Google and search the forums. It's OK to post a question, but people just want to see that you've done some work beforehand. UNFORTUNATELY, various forum communities seem to antagonize new posters by harassing them to search, without really answering the question.
Try reading Here to see if anyone has had a similar problem?
Sorry I can't provide more links, as I don't know what nvflash/APX is, nor have I had a need to use it. Perhaps someone else can post some helpful links?
Click to expand...
Click to collapse
That's exactly what I mean and what I write
jaysinclair said:
Hey guys,
I've got a TF300T running the 10.4.2.13 update (so the newest JB) without root, and no nvflash which is bricked.
I've got APX mode, but that's as far as I've got.
Any suggestions? Help's much appreciated
Click to expand...
Click to collapse
And it's a good day for you
Try this:
-use unlock tool
-boot tablet into USB MODE
(it will say fastboot mode,waiting)
-using the steps,copying over the fastboot files to one folder, with TWRP as the recovery, run fastboot command.
-done successfully,you be good
Click to expand...
Click to collapse
I'm not the author of this process, but apparently it works.
I haven't tried, because I use terminal emulator for my adb command

Hi guys, thanks for the input;
I failed to mention I spent a fair while (to no avail) searching for anything relevant to sort my tablet out, had only come up with "send to ASUS for repair" - so that's my bad for not clearing that up
philos - it's 2:41am here, I'll give your suggestion a go in the morning and let you know how it goes!
opethfan - I'm in the same boat for not having a clue what APX or nvflash do, nor have I needed them in the past...
I find it weird that my tablet just /died/ one day. Kind of unfair!
Anyway, I'll have a crack in the morning - thanks for the input gentlemen!
UPDATE: No dice, I'll need to install Windows 7 on a virtual machine to get the correct APX drivers working for my tablet, good thing that I don't have uni tomorrow! Round two tomorrow!

jaysinclair said:
Hi guys, thanks for the input;
UPDATE: No dice, I'll need to install Windows 7 on a virtual machine to get the correct APX drivers working for my tablet, good thing that I don't have uni tomorrow! Round two tomorrow!
Click to expand...
Click to collapse
You will find Asus drivers for Win7 in my index (click on my sig)

philos64 said:
You will find Asus drivers for Win7 in my index (click on my sig)
Click to expand...
Click to collapse
Cheers, yeah I'm running Windows 8 at the moment and it spat the dummy trying to install them, which I find weird because every other driver under the sun is backwards compatible...
Just installing Windows 7 now Keen to get this working!

jaysinclair said:
Cheers, yeah I'm running Windows 8 at the moment and it spat the dummy trying to install them, which I find weird because every other driver under the sun is backwards compatible...
Just installing Windows 7 now Keen to get this working!
Click to expand...
Click to collapse
And unfortunately no dice with Windows 7, so at this stage I think it's fairly safe to assume it's a hardware failure with my tablet. Called ASUS and they pick it up tomorrow, very friendly customer service!
Thanks for the help guys, when I find out what they determined to be wrong with the tablet, I'll be sure to post the result in here to let you know.