Does anyone have the drivers or recovery image for the Hipstreet W10 Pro? I tried using HP Stream 7 Drivers but the touch screen isn't working properly (I think it's not calibrated propperly) along with the screen rotation. I tried contacting Hipstreet but they appear to have gone into administration.
Related
Has anyone managed to find drivers for the huawei hsusb device for windows 7 x64 ?
Has anyone managed to make the ideos x5 phone to work with the huawei's pc suite in windows 7 x64 via usb?
Check this out:
http://forum.xda-developers.com/showpost.php?p=13306262&postcount=14
I know this is alittle late, but this doesnt work for me.
It says Windows could not find driver software for your device, all though i've downloaded the right drivers and followed the toturial.
My guess is the drivers are outdated or MIUI isnt compatable with this drivers.
Thanks
Jacky444 said:
I know this is alittle late, but this doesnt work for me.
It says Windows could not find driver software for your device, all though i've downloaded the right drivers and followed the toturial.
My guess is the drivers are outdated or MIUI isnt compatable with this drivers.
Click to expand...
Click to collapse
Thanks
try these drivers
http://www.mediafire.com/?g0tt1te1o2to25n
the drivers are working on me, on a device based on msm7630 soc with msm8255 1.4ghz cpu which has the HSUSB activated, the method is the same as on huawei, press the volume - + and power in the same time for 5 seconds, and it enters in the hsusb state.
What is hsusb?
Sorry for the noobish
it`s a downloading/uploading mode, from which you can re-write all the information of the phone.
I'm trying to follow the "Retail 3.1 CWM Recovery, Root..." instructions from the dev forum and have hit a big roadbump. I'm trying to install CWM and root using XP via Parallels from my iMac (which I've read others have done before) but for some reason XP is not recognizing the APX device (and the device is indeed in APX mode because a pop up comes up on the Mac). The other odd thing is that when the tab isn't in APX mode, it connects just fine in Windows, and I can even access it through adb. I'm hoping maybe someone has a tip or trick on how I can get Windows to recognize the device in APX mode so that I can then point it in the direction of the proper drivers, and eventually flash CWM. Any ideas?!?!
anybody?
Ugh...
Hmm, now I've connected and apparently successfully flashed CWM...but when I go to reboot to recovery via ADB, it just sits at that huge battery graphic on the black background. WTF
I could never get windows xp running in vmware (on a windows 7 x64 box) to recognize my tab.
Hi guys,
I want to go back to stock since 4.4 is coming. However, when I try to flash the stock rom+ with Nexus Root Toolkit 1.7.3, I get stuck at the whole fastboot part. Fastboot IS working on my Nexus, but the drivers cause a lot of trouble. Installing the drivers when my device is running normally ( so no fastboot mode or whatsoever) works fine.
I have followed the Full driver installation guide where I tried options 1 till 4 but they all get stuck at the point where my device reboots into fastboot mode. At this point, my computer doesn't recognize my device and gives me an error. My nexus is shown in the device manager as unknown device and updating the drivers manually by redirecting my computer to the NRT drivers does not work. It says it cannot find drivers for the device. Does anyone know what I might have done wrong?
Or is it possible to flash a stock rom through twrp? like this one? http://forum.xda-developers.com/showthread.php?t=2376881
TL;DR: use a machine with Windows 7 installed. Or boot ubuntu from a usb stick.
I've researched a lot about this, I had to downgrade my dad's phone with Flashtool (for Xperias), and after trying about every tutorial I encountered (removing drivers, installing different drivers, changing ports, disabling driver signature verification in Windows, I installed android studio, adb separately, running everything in administrator mode), I remembered I have a W7 machine on the other desk, it worked like a charm.
W8 (or 8.1, it's the same thing) is bad for flashing, I don't know when they're going to fix it.
issak42 said:
TL;DR: use a machine with Windows 7 installed. Or boot ubuntu from a usb stick.
I've researched a lot about this, I had to downgrade my dad's phone with Flashtool (for Xperias), and after trying about every tutorial I encountered (removing drivers, installing different drivers, changing ports, disabling driver signature verification in Windows, I installed android studio, adb separately, running everything in administrator mode), I remembered I have a W7 machine on the other desk, it worked like a charm.
W8 (or 8.1, it's the same thing) is bad for flashing, I don't know when they're going to fix it.
Click to expand...
Click to collapse
Yeah, I tried the same things you did, including disabling driver signature verification but it won't work. I'll try a windows 7 machine.
Thanks for your answer!
Hey guys,
So i got a 1 day old 32GB Asus T100 (Windows 10 Home) + 500GB HDD Keyboard. All was well, installed my apps and most softwares, kb and touchpad drivers (except BIOS drivers).
So the issue started as i rebooted my Asus T100 for all my settings and drivers to take place. However, when it restarted, it went back on with the stock Asus logo and then "Diagnosing your PC" message. It then lead me to recovery mode where i simply restart the pc again and STILL, it didn't go back to Windows. I had to reset the PC in order to get to Windows again. I don't remember seeing any "Refresh PC" button when i was at Recovery.
Any solutions? Could this problem be in the un updated bios? Or maybe the keyboard? Thanks
Sent from my GT-I9195 using XDA Free mobile app
Unable to to get ADB to work with "any" drivers I've found using W10 Pro 64-bit v1607 or v1703 but works on W7 Pro 64-bit. Has anyone gotten ADB to work on the lastest W10 Pro builds?? Get Code 10 as if device isn't connected but Fastboot works just fine as the boot loader drivers install automatically.
A long journey but the short version is it was my mistake due to forgotten basic usage.