Can't run RUU's or Sync using HTC sync - Hero CDMA General

For some reason my Heros won't sync when Using HTC sync tried all the driver hacks and stuff It worked with my first non rooted stock Hero and Right before I rooted my 2nd one. Now it won't sync with my moms stock non rooted or my rooted one. The RUU's can't identify them. When I run ADB it finds them just fine. Also, If I run ADB I can only run it once, before I need to reboot .

chococrazy said:
For some reason my Heros won't sync when Using HTC sync tried all the driver hacks and stuff It worked with my first non rooted stock Hero and Right before I rooted my 2nd one. Now it won't sync with my moms stock non rooted or my rooted one. The RUU's can't identify them. When I run ADB it finds them just fine. Also, If I run ADB I can only run it once, before I need to reboot .
Click to expand...
Click to collapse
Try this, it helped me out today.

Forgot OS is Win7 Ultimate 32bit

*Sigh* Did you try it? Im also on Win 7 32bit.

Darkshneider said:
*Sigh* Did you try it? Im also on Win 7 32bit.
Click to expand...
Click to collapse
I copied and pasted everything already... I currently don't ahve a phoen to try it on to see if it works.

I had a issue with this as well the only way around it for me was to fast boot the phone hold volume down when you power up then hit up and then run the RUU.

gizmo0681 said:
I had a issue with this as well the only way around it for me was to fast boot the phone hold volume down when you power up then hit up and then run the RUU.
Click to expand...
Click to collapse
yup I had that issue a month back...
If you don't have the HTC PC Sync software on your phone anymore (that was one of the first things I deleted when I rooted my phone), then you can't initiate the correct debug mode with the computer... or it may be because adbd runs as root... but going to fastboot usb mode and then running the RUU will work. and yes, it works on Win7.

Related

having trouble with usb drivers

so i am new to android and i decided " hey why don't i try to root my nexus" so i tried and i cant get any father that checking if the computer can see my device which it cant for some reason. so i went online i figured out that i don't have the usb driver for android. so after that i tried to down load then and i even installed them and restarted my computer and it still wont work. so if any one can help me with my problem it would be greatly appreciated.
On Home Screen, press menu>settings>applications>development and make sure USB debugging is checked.
What OS you running?
Specs would help, where did you get your drivers? What other software have you tried?
i turned on the debugging and it still hasnt worked
i am running xp. i downloaded the android sdk from here
developer.android.com
i just want to put the modaco desire rom on my phone that my onl reason for wanting to root. i really like the sense ui
I am having a similar problem, so i might as well use this thread instead of creating a new one.
I have a dual boot computer, win7 and fedora, both have SDK. I unlocked my nexus one with windows, as i noticed the commands were considerably easier, or at least they don't work when i plug the linux ones into fedora.
Last night i was going to push the undervolt kernel so i plugged my n1 while in win7, It instantly came up complaining about drivers, which i had already installed and had previously worked, i went to re-install them, and windows says they are up to date, but still no luck recognising the device (Debugging mode is definately on)
So i switched to fedora, no driver pop ups obviously, but when i try to push the kernel through, it does not recognise the device.
In the bootloader it says "fastboot usb" while plugged in.
I can't pinpoint when it stopped working, but the last time i used fastboot was to put the RA recovery, since then i flashed CM 5.0.2, CM 5.0.3.1, the desire rom, and used a nandroid restore to get back to 5.0.3.1
Anyone got any ideas? Without fastboot i am pretty much restricted to flashing .zip files from the recovery.
yeah i cant even unlock mine its so frustrating
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...
temperbad said:
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...[/QUOTE
Yeah I know how you feel its so frustrating I tried all day yesterdAY too
Click to expand...
Click to collapse
drbrendin said:
temperbad said:
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...[/QUOTE
Yeah I know how you feel its so frustrating I tried all day yesterdAY too
Click to expand...
Click to collapse
I tried all day too like a gazillion times.... and wonder does everyone have driver issues? I tried with my XP computer and windows 7, no go, then I read posts people having the same issue, then they just post " nevermind got it" and didn't even write what they did to get it.......
Click to expand...
Click to collapse
not everyone is a dev
Ok, I have my Nexus One set up so I can use with via Windows 7 (desktop) or Ubuntu (Laptop).
The Linux part is a bit more involved, but since everyone is running Windows (unless I missed something), I will work there.
First of all, your phone needs to be in Dev mode (which was covered earlier).
With the phone UNPLUGGED from the PC, uninstall any previous SDK installs you have and be sure to remove the directory.
Then, install the SDK found here: SDK
Install this SDK and let it complete the install, which will include downloading for a bit. You need to do this since the SDK package above does NOT include the right drivers!!!
Once this has been completed, plug your phone into the computer via USB. Your computer will find a new device, however, it cannot locate the drivers for it. Browse and point the installer to:
DRIVE:\PATH_TO_android-sdk-windows\usb_driver
Don't go any further than this!!
Now, let it do it's thing and you should have a new device in the device manager called:
Android Phone
...|_Android Composite ADB Interface
Now, go to the command prompt and change to the following directory:
DRIVE:\PATH_TO_android-sdk-windows\tools
There, you will find adb.exe
Type:
adb devices
and you should see:
List of devices attached
HT019P801614 device
If not, something got screwed up and would need to dig further to help ya.
Ok ill give this a try once get home from school
nexus one root.
Ok assuming that you have the android sdk installed correctly, try rooting your phone via the superboot method. The first link below has a full detailed guide for rooting the nexus one and I believe has all of the device drivers for those who have not been able to get them running well. If you still have trouble getting the drivers working checkout the second link. Anyone who is relatively new to working with the sdk and is not familiar with working the commands check out the third link. Read the entire thread! it is very helpful.
1) http://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
2) http://forum.xda-developers.com/showthread.php?t=613217
3) http://forum.xda-developers.com/showthread.php?t=619153
If you have any questions PM me on xda. I'll try and help in anyway, it took my like two days to actually root my nexus, I wasnt familiar with using ADB and Fastboot to root.
One thing I know I was having problems with since I came from the G1 was that the new SDK has to actually be installed via an .exe now. I was used to it all being in a zip so I kept trying to load up what I thought were the right USB drivers, but they were actually the 1.6 drivers I already had. So make sure to run the .exe that comes with the SDK.
ok so while i was downloading the sdk a notification came up that said that it could not rename the directory. is this bad?
i am having an issue with installing the right driver as well. my computer keeps installing the nexus one as a "mass storage device". i have uninstalled and reinstalled a few times but no luck. i have the phone set to debug mode, using XP btw. any help would be appreciated.

adb issues

having trouble with ADB
i sold my nexus one, so my computer is setup for ADB devices but for some reason it doesn't find the vibrant...also tried to root using method in android developement and it didn't work
any ideas?
Going to assume that your phone is rooted. Go into settings -> applications -> development and make sure that USB debugging is enabled as well as Allow mock locations
then try it in ADB and it should detect your Vibrant.. make sure that drivers for the phone are also installed
phones not rooted yet...does it need root to use adb? which phone drivers u talkin about the usb for androidsdk or is there something else?
fordstang99 said:
phones not rooted yet...does it need root to use adb? which phone drivers u talkin about the usb for androidsdk or is there something else?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=728929 Those drivers.
And uhm.. I don't know if it needs root to use ADB but it would make sense to be rooted so you can have ADB without any restrictions.
Was USB debugging enabled?
ok well i put the update.zip file on the root of the internal memory and hold down the volume up and down and it just boots normally
ok adb is working....i didn't see those drivers thanks
now just the update.zip, cant seem to get into recovery, i geta Downloading....Do not turn off target !!!
ok got everything working
thanks
Same Problem USB DEBUGGING
I just want to be able to use the USB Debugging feature. Is this something that is unly available with root? If so then I have no problem, if now I am not able to have the pc detect my Vibrant when in USB Debugging mode. It will connect without it so I'm curious as to my first question. I am not rooted, but plan to soon.
Thanks for any help
CRX
[EDIT]: Phone rooted and still have same problem!!!
Any help would be appreciated!!
Crx
bump for assistance
Is there no one who is not having trouble connecting to ADB. I have seen many posts of those who have ADB working flawlessly. I am running xp pro and have connected both my G1 and Mytouch through this machine, but I was able to use the ADB Debugging option. I cant seem to get this working.
I would greatly appreciate a little help.
Crx
crxforya said:
Is there no one who is not having trouble connecting to ADB. I have seen many posts of those who have ADB working flawlessly. I am running xp pro and have connected both my G1 and Mytouch through this machine, but I was able to use the ADB Debugging option. I cant seem to get this working.
I would greatly appreciate a little help.
Crx
Click to expand...
Click to collapse
I had a few issues getting adb to work also. Turns out my adb server was out of date. Once I downloaded the sdk all over again it works fine. If you haven't done that try it because I was stuck and could connect to my other phones, but not this one.
Why would you use winblues os to run adb? Use the real OS that underlines your Android phones!
lqaddict said:
Why would you use winblues os to run adb? Use the real OS that underlines your Android phones!
Click to expand...
Click to collapse
I dont know what ur talking about. Nobody on this thread said anything about winblues???
ISprayCandy said:
I had a few issues getting adb to work also. Turns out my adb server was out of date. Once I downloaded the sdk all over again it works fine. If you haven't done that try it because I was stuck and could connect to my other phones, but not this one.
Click to expand...
Click to collapse
Thank you for this info, ill give it a shot
crxforya said:
I dont know what ur talking about. Nobody on this thread said anything about winblues???
Click to expand...
Click to collapse
crxforya said:
I am running xp pro and have connected both my G1 and Mytouch through this machine, but I was able to use the ADB Debugging option. I cant seem to get this working.
I would greatly appreciate a little help.
Crx
Click to expand...
Click to collapse
you need winblues drivers for sammy, search for samsung kei software
The updating of my SDK made the difference. I was able to install the correct driver and now ADB is working smoothly again. Thanks for all your help.
Crx

[Q] Trouble getting "Android 1.0" driver in XP can't get fastboot to work

Problem 1: (trying to get fastboot to work)
I downloaded the latest SDk and used the drivers in there. When I goto "update" my Android ADB driver and point it to the the google usb driver, it tell me to go jump off a bridge.. Though I fail to see how that will make my driver install
Anyway that's where i'm stuck, i've tried replacing the .sys files and blew up my XP blue screen at boot which was awsome..
I'm trialing a Streak to replace my iPhone4, This seamed to be the only phone so far that really WOWed me, that was until I used it, with 1.6 it's no iPhone killer..
I am also a previous HTC Advantage user, so i like big phones...
Any Ideas? Maybe i need the old 1.6 SDK Drivers?
This is all to get FastBoot to work, so i can start installing roms.
Problem 2:
Is there anything that I need to be careful of having an ATT phone over an 02?
try dell's drivers.
I found that using XP I had to install the drivers multiple times for it to register the Android 1.0 or whatever.
I simply used the QDL Tool on my locked-to-contract AT&T Streak 1.6. Like I said, I had to install the ADB drivers multiple times (I think that is their name) for it to finally go through. And then on the 4th time or so, it all went smoothly and I'm now running the "official" 2.2
I did nothing special. Just ran the Tool, installed the drivers, if it failed, I installed the drivers again, and ran the Tool again. I think maybe 4th time of installing drivers was the trick. I don't know what I did differently on the last time, but it worked just fine.
subvecto said:
try dell's drivers.
Click to expand...
Click to collapse
Tried that as well, no dice...
stang393 said:
Tried that as well, no dice...
Click to expand...
Click to collapse
That is strange... I was able to get dell recognized by win7 only via drivers that was installed via dell PC sync software...
Sent from my Dell Streak using Tapatalk

Debugging - Download mode / usb not recognized

So I want to root my phone, but I cannot get ANY computer to recognize the phone when it is in either download mode, or debug mode.
I'm running Sprints stock EB13 right now.
I've downloaded the samsung drivers and installed them.
I've tried 3 computers -- A XP 32bit, a vista 64bit, and a 7 64bit system. I've also tried 3 different cables. Nothing works.
The phone is recognized fine in mass storage mode.
Tried restarting the phone many times, removing the battery, etc.. same with the computer side of things.
I'm out of ideas to try and can't find a good post with a fix.
Thanks for any input!
syntax_erorr said:
So I want to root my phone, but I cannot get ANY computer to recognize the phone when it is in either download mode, or debug mode.
I'm running Sprints stock EB13 right now.
I've downloaded the samsung drivers and installed them.
I've tried 3 computers -- A XP 32bit, a vista 64bit, and a 7 64bit system. I've also tried 3 different cables. Nothing works.
The phone is recognized fine in mass storage mode.
Tried restarting the phone many times, removing the battery, etc.. same with the computer side of things.
I'm out of ideas to try and can't find a good post with a fix.
Thanks for any input!
Click to expand...
Click to collapse
what are you running on your PC that you want to connect to the phone with?
Odin (in download mode?)
ADB in debugging mode?
What exactly are you trying to run ??
jdelano said:
what are you running on your PC that you want to connect to the phone with?
Odin (in download mode?)
ADB in debugging mode?
What exactly are you trying to run ??
Click to expand...
Click to collapse
I wanted to use Odin to go back to DI18 at first. After that didn't work I tried ADB in debug mode, and that no longer works!
I know ADB in debug mode used to work when I was on DI18 because I used it before when I first got my phone. Now I've upgraded to EB13 from the file samsung provided on their website. I've also tried a hard re-set of the phone and that didn't help either.
I had a similar issue. I was able to resolve it by creating a fresh user in windows and then running it from there.
Sent from my SPH-D700 using XDA Premium App
iil said:
I had a similar issue. I was able to resolve it by creating a fresh user in windows and then running it from there.
Click to expand...
Click to collapse
umm..yeah three complete different computers?...I don't think thats the case.
syntax_erorr said:
So I want to root my phone, but I cannot get ANY computer to recognize the phone when it is in either download mode, or debug mode.
Click to expand...
Click to collapse
I had this exact problem with my Epic also. I tried rooting my fone too, for like 2 months straight, with no luck... Tried every technique, software, and trick in the book and nothing worked...
2 days ago though, I finally rooted it using this solution:
Forget about trying to "root" it.
Instead, flash the "Stock EB13 Deodexed EXT4 + CW 3.0.0.6" to your fone (search the forum, you'll find it and the thread that explains how to do it).
It's pre-rooted too!
It worked fabulous for me. I am now rooted and well on my way to fully customizing my fone.
Odin is finicky though... I had to switch the usb cord around to several different ports before it recognized my fone. Also, it kept locking up at a certain point in the flashing process, but after moving the image from "Phone" to "PDA" (you'll know what these are once you open up Odin), it worked brilliantly.
Try it, it works!
P.S. Just in case this helps anyone; I should note that originally I upgraded from Eclair to the official unrooted straight from Samsung (before they pulled it) stock Froyo. I loved it, but wanted it rooted.
I read somewhere that it was easier to root it if you reverted back to Eclair first. So I did (search forum for uninstalling Froyo).
And from Eclair, I flashed to the above mentioned rooted and deodexed version of Froyo (EB13).
Hope it helps!
syntax_erorr said:
I wanted to use Odin to go back to DI18 at first. After that didn't work I tried ADB in debug mode, and that no longer works!
I know ADB in debug mode used to work when I was on DI18 because I used it before when I first got my phone. Now I've upgraded to EB13 from the file samsung provided on their website. I've also tried a hard re-set of the phone and that didn't help either.
Click to expand...
Click to collapse
Might try looking at the usb on the phone to check for something preventing a good connection; I've read where people have found bent connectors and were able to fix it.
Good luck; that has to be extremely frustrating.
I tried everything like you, multiple cables, multiple computers, EVERYTHING!!!
I finally broke down and took it to sprint and they couldnt even get it to connect or fix the problem so i got a new epic. You might just want to take it back and get another one. Im on my 3rd epic now so that should tell you something about these ****TY phones...

Trying to root my GT540, tried everything

Hi.
I know it's been talked about a thousand times alreay, I hate to open a new thread, but I really tried every option I've found to root my new GT540g
Z4root Androot and SuperOneClick, none works
I put my phone in "USB debug" but it seems like none of this programs are realizing that
I also tried with the root.bat (http://forum.xda-developers.com/showthread.php?t=803238) method, and nothing
When I connect my phone, if I start the LG Mobile Update program, it can see my phone
but when I ask adb to do the same, like with a simple "adb devices" it cannot find it
I'm on Win7 x64, and have already reinstalled the drivers a LOT of times, even switching between the oficial and some drivers I've seen on the forum
Please, help me
Is there an error message?
in adb it just says "device not found"
switch off the 'mass storage only' option if it is on
I've tried with both mass storage on and off
this is puzzling
hey ive got the same issue
so ive decided the gt540 is not worth owning and bought a desire Z
i will trade my gt540 in for £21, mine randomly crashes, turns it self off, freezes etc. im glad i only paid £35 for it initially.
edit: enough about how rubbish the phone is, for what its worth im using win 7 x64 too, i wonder if that is our issue
try universal androot it works apparently
Doughnut said:
hey ive got the same issue
so ive decided the gt540 is not worth owning and bought a desire Z
i will trade my gt540 in for £21, mine randomly crashes, turns it self off, freezes etc. im glad i only paid £35 for it initially.
edit: enough about how rubbish the phone is, for what its worth im using win 7 x64 too, i wonder if that is our issue
Click to expand...
Click to collapse
I'm sorry, the GT540 wasn't worth it o.o how is a phone not worth it just because you can't root it. Also, if your sick of crashing then change the software install Cyanogen or other roms.
Anyway you should try device manager and see if the device is fully detected.
Jack
Have you installed the adb drivers? Without them adb can't see the phone. Even if you put it in "Debug mode". You can download them with google's android sdk package.
Well, I'm from Argentina, so the cost of the phone is pretty high, I had to pay almost $ 200, and they won't change it
Anyway, I think I've come to a solution. I've installed the adb drivers, I tried with every driver that appeared on the GT540 FAQ, but nothing worked
Yesterday, I went the opposite way, I cleaned every LG driver I could find, and just let the LG Mobile Update app install whatever stock drivers it wanted
I didn't add the Virtual Modem, or any of the other drivers, rebooted, and voila, adb started seeing my phone
I'll try to flash the Europe ROM with fastboot and report
Thanks to everyone for the helping hand!
Mitalca said:
Well, I'm from Argentina, so the cost of the phone is pretty high, I had to pay almost $ 200, and they won't change it
Anyway, I think I've come to a solution. I've installed the adb drivers, I tried with every driver that appeared on the GT540 FAQ, but nothing worked
Yesterday, I went the opposite way, I cleaned every LG driver I could find, and just let the LG Mobile Update app install whatever stock drivers it wanted
I didn't add the Virtual Modem, or any of the other drivers, rebooted, and voila, adb started seeing my phone
I'll try to flash the Europe ROM with fastboot and report
Thanks to everyone for the helping hand!
Click to expand...
Click to collapse
good you sorted it, sounds like you had driver overload
JackG256 said:
I'm sorry, the GT540 wasn't worth it o.o how is a phone not worth it just because you can't root it. Also, if your sick of crashing then change the software install Cyanogen or other roms.
Anyway you should try device manager and see if the device is fully detected.
Jack
Click to expand...
Click to collapse
Easy, because its not to my expectations.
So I deem it unworthy, its a matter of opinion rather than fact, so probably pointless debating.
Someone has messaged me from this forum asking to buy it for £21, they're welcome to do so.
try this : http://www.4shared.com/file/p3TR1eih/autorootapp2sd.html
Hmm. I'm assuming you are on 2.1.
I happened to see people come across problems on Win7x64. I'd highly recommend you try it on WinXPx32.
z4root works perfect.
http://forum.xda-developers.com/showpost.php?p=9109591&postcount=1
I have tried both root.bat method and z4root. Both worked fine for me. However, I personally prefer root.bat.
Pretty much any rooting app that supports Rage Against The Cage exploit would work on GT540.
Use my information at your own risk!
And, like Mitalca suggested, you might want to try uninstalling all drivers and a clean reinstall to prevent driver conflicts.
In any case, more than the LG drivers, you'd need ADB drivers.
Mitalca said:
in adb it just says "device not found"
Click to expand...
Click to collapse
Try to remove sdcard or disable it from menu storage.
why don't you try a custom ROM such as LewaOS or SDSL... Just flash it and your phone would be rooted already, and it's much featureful and runs faster than the stock ROM
Glad to see your sorted
I would have said it works on Win 7 x64 because I use it
I also use ubuntu on the same pc, but thats besides the point.
Anyways, glad to see your sorted, and enjoy your phone!
Try to change rom
Try z4root for rooting your GT540. It works fine on our phone.

Categories

Resources