I have searched the forums and cannot find a soultion to my problem
I have an O2 XDA II with works well. This was on ActiveSync 3.7. It now also works well on ActiveSync 4.0
However my new mini XDA (Wizard) is not detected by active sync 4.0. It comes up with generic rndis driver not found.
The software from O2 hangs in the install process and although 4.0 is installed i think that i'm missing a driver somewhere???
I think someone suggested deleting all possible drivers in the driver manager and re-install ActiveSync from the cd to see if ti picks up the driver. but I'm unwilling to do this without knowing which driver it could be?
note: firewall is off
does anyone know how to fix this? is there a patch or how do i get the driver to be picked up off of the CD.
HELP PLEASE?
Just for starters 4.0 has all sorts of problems so you should download 4.1 from the microsoft site http://www.microsoft.com/windowsmobile/downloads/activesync41.mspx and install that first. Thats not to say 4.1 isn't a crock as well but it's less of a crock.....
Just got on a plane and found out that the WM 6.1 update seems to have killed my HTC remote control for controlling Audio Manager or Windows Media.
It's one of these: http://www.negrielectronics.com/product_info.php?currency=USD&products_id=1067.
Anyone else run into this? Theres posts on installing the audio driver for other phones, but I don't find one for the Kaiser floating around out there.
There is an updated remote control driver for WM6.1. It can be donwloaded from HTC e-club.
Ah. For anyone that's also looking, it's not on the HTC US site. You have to hit the HTC Europe page and then it will show up.
Interesting. I grabbed the driver and ran the install and the app tells me I have the latest version installed. Won't overwrite or let me reinstall.
Anyone else having this issue? The control still isn't working and I can't tell what the cab files are looking to overwrite to force the install through.
Same issue after new HTC rom update
Any solution ?
Michael
mdorchain said:
Same issue after new HTC rom update
Any solution ?
Click to expand...
Click to collapse
Instal the WM 6.1 compatible driver from HTCs website off the bat or if the old version is installed first, hard reset and then install just the latest driver. Why anyone would want the current HTC official WM 6.1 'upgrade' (at least a WWE version) is an important question.
hi Flying Kiwi, I guess the main reason of the upgrade is bug fixing which I guess now is solving some adding others
I'm a new HTC user more used to symbian devices before.
The nokia updates are always good, so I thought it was the same for HTC.
I guess I was wrong.
I followed many times the installation procedure, but I always get the same result :
- Drivers already existing on the PC
- GetDeviceInfo.exe error on the Touch pro.
I guess the GetDeviceInfo error is the source of the pb. Maybe a pb with the ROM itself.
Thanks
Michael
mdorchain said:
I followed many times the installation procedure, but I always get the same result :
- Drivers already existing on the PC
- GetDeviceInfo.exe error on the Touch pro.
I guess the GetDeviceInfo error is the source of the pb.
Click to expand...
Click to collapse
Sorry I don't have one of these remote devices to test with - I just assumed (and we know what that results in) that from gauntman's post there was a WM 6.1 compatible driver but all I've been able to find is a very elderly cab (after renaming the file to have a zip extension) - gauntman please point us to a new version that does work if you know of it.
IF you have a stock ROM/Radio/SPL and the remote isn't working and installing the driver doesn't fix it or results in an error installation then my suggestion is to try the headphones that come with the remote and ensure they're fully plugged in. If that still doesn't work then it's time to contact HTC!
I tried this updated version found Here,
But the problem described is the one described.
Is there anyway to uninstall a driver without rebuilding the ROM ?
Sorry for the newbie question, but just an idea.
Maybe I should go for a stable cooked ROM and install the drivers on it.
But if not working i will cry lol
Michael
mdorchain said:
I tried this updated version found Here,
But the problem described is the one described.
Click to expand...
Click to collapse
That's the one I was referring to, maybe gauntman knows of something newer.... In the meantime have you tried what I suggested ie restoring it to a stock HTC state and testing again with the headphones that came with the remote fully plugged in? If that doesn't work then it's fair and square a HTC issue to resolve.
Thanks I really appreciate your feedback.
Yes I actually did a hard reset.
The stock headphone is working fine.
So far the RC E100 has no sound problem, just the button issues.
I guess not a mini usb issue, but really a driver pb.
I contacted HTC about the last ROM and their accessory, let's see if the reputation of their technical support is as good as their product
Thanks
Michael
hi, im trying to install drivers for android in XP there are plenty drivers and guides here. so now i really dont know which one install. i got latest hardspl, dwang-v1.10 rom, g1.
there are drivers in
- SDK\usbdrivers\
this one
http://dl.google.com/android/android_usb_windows.zip
then updated driver
http://sapphire-port-dream.googlecode.com/files/usb_driver_updated.zip
so wich one choose, and then phone online state: install driver? if so which one?
bootloader? fastboot which one install?
i doing this because im trying to connect in bootloader mode. phone says fastboot usb i can see my phone in device manager installed fine but no adb devices or fastboot devices.
thanks for help.
There is a newer SPL that has additional keypresses for rebooting the phone, as well as progress indicators while flashing. It is located here
If you use the above SPL you will need new drivers for Windows. They are located here
Click to expand...
Click to collapse
The 'updated' driver is only for 1.33.2005 SPL, not Hard SPL.
Use the first one.
Well, Paul from Modaco isn't really keen on rooting the 2.03 since he is preoccupied with the new devices. I wonder if anyone from XDA is working on it.
Because i really want to use custom roms instead of the stock rom. Didn't like the HTC sense, because it suck up so much ram.
Hopefully, anyone from xda can give us Legend owners some answers.
Have you looked at this forum topic about downgrading HBOOT and RUU? The procedure is for the Desire, but it might work on the Legend too.
I have tryed to downgrad hboot by "The procedure for the Desire" ,but is't not work ,because it's only for rooted phone .
without root ,we can't downgrad hboot
without downgrad hboot ,we can't root
This method should supposedly work on any HTC 2.1 device. If that one doesn't, this one should.
EDIT: typo.
Thanks for the links, I tried about 30 times trying to get the loop exploit to work. Just never would show in devices in recovery mode, followed both guides.
Tamimego said:
Thanks for the links, I tried about 30 times trying to get the loop exploit to work. Just never would show in devices in recovery mode, followed both guides.
Click to expand...
Click to collapse
Damn. I was sure one of these was gonna work, since they're both based on the HTC Legend OTA exploit. Just a stupid question, but do you have HTC Sync installed (I think it provides some of the needed drivers)?
I tried both methods on FW 2.03.405.3 but it seems like it does not work in this particular firmware.
device just won't be detected in recovery mode.
what windows version are you using? and what version 32 or 64 bit ?
i had an issue on my hero, i had to use htc 64 bit driver when it couldn't find the phone. I had to go to device manager and select the android driver manually...
yep. Both methods do NOT work with the Bell/Virgin Legend... Device is unable to connect while in recovery mode. Even tried updating/changing the driver... no go. (win7 x64)
that does not work at home either with the 2.03
"error: device not found"
schpinn said:
Damn. I was sure one of these was gonna work, since they're both based on the HTC Legend OTA exploit. Just a stupid question, but do you have HTC Sync installed (I think it provides some of the needed drivers)?
Click to expand...
Click to collapse
Windows 7 x32 with latest HTC Sync from the website.
i read that if you try downgrading using an official rom from htc to 1.31 of htcs website or somewhere on the forum it will work.
once downgraded to 1.31 you can root and install whatever roms you want.
where ??????
it is impossible
it will work, only if you done the update over OTA. If you done it over RUU it won't work due to the bootloader being upgraded.
masterbalby said:
that does not work at home either with the 2.03
"error: device not found"
Click to expand...
Click to collapse
Just wait for 10 - 15 second after the device connect to PC, it always work for me. PC will load the driver first, and of course you already install HTC syn.
like i said
If you've done an update from version 1.31.xx.xx to 2.03.xx.xx over the air you can downgrade with the RUU file.
If like me you've used the 2.03 RUU file,well...your screwed,just like me
at this time there is no solution for it yet, and honestly, i don't see anyone bothering with it,trying to find a solution except for all of us legend users. I know that lots of us are attempting to follow every single root guide there is on the web, but the result will always be the same...no success untill a new rooting guide or bootloader downgrade possibility appears... it's sad dude
Did anyone try this method? It's a new method for the Droid Eris, but it should work on all HTC phones with Android 2.1. It's worth a shot..
where did you see that it should work for everybody?
i've been searching the threads and don't see anything about it.
schpinn said:
Did anyone try this method? It's a new method for the Droid Eris, but it should work on all HTC phones with Android 2.1. It's worth a shot..
Click to expand...
Click to collapse
Giving it a shot. Why not, eh?
me also...
Running Win7, HTC Sync installed and a NEW Hero with .6. According to all i read I need to RUU to the .5 version, I try, I follow the instruction but keep getting a USB connection error when it is looking for the boot loader...UGH, I need help. Im on Gtalk at jwkoppe...thanx
Is your phone showing in adb .... adb devices.
It sounds like your usb driver is not setup correctly, wi7 seems to have an issue with this.