HI guys. I recently needed to reformat my 2HIX WINTAB, I installed a brand new windows 10, and without any kind of support on the controllers from the vendor, i managed to get everthing installed, even the touchscreen... The problem here is that i´ve installed various drivers with the same Hardware ID and each one of them gives me diferent calibration problems and i can't manage to get the correct one.
Is ther anyone with a solution for the touch, or even better, a stock ISO with windows 10? All the help you can give me is welcome :good:
Same here. Used the windows install pendrive to install windows fresh and cleared up. Installed Windows and did not install any device.
No driver support anywhere.
Been playing it for a 1/4 of a day.
It seems we can use drivers from other makers.
I had a toshiba wt7-c and it kinda uses same hardware.
So what we need is the intel platform installer for windows 8.1 and it should install drivers for almost everything and show the hidden devices. Strangely windows 10 didnt download any drivers as far i could see through windows update.
I have the same problem... any solution so far? thanks in advance
Hello Sir,
Yesterday I had the same problem, no touch screen and no sound after clean install of windows 10 in that tablet, 2hix... did you managed a solution? Will you please share? Thanks!
Also, do you still have android running? i lost mine.
(2hix tablet was dual boot from factory with win10/android 4)
Thanks again,
Pluda
Related
Hi
Just for the fellas having problems when upgrading to a custom or signed ROM on the HTC FUZE on a computer with windows 7 and windows mobile device center.
you MUST be online at the time of installing a new rom
so the windows update downloads the " qualcomm cdma technologies msm" driver that recognizes your FUZE when windows mobile " is not present ".
I don't think I was connected when I did mine.
And that was flashing the Energy rom onto my Fuze.
I can't remember 100%, but I'm ~80% sure I wasn't. Maybe I just got lucky?
EDIT: Though that wasn't the first time I'd flashed. Maybe that was the differentiating factor.
alfmetal said:
Hi
Just for the fellas having problems when upgrading to a custom or signed ROM on the HTC FUZE on a computer with windows 7 and windows mobile device center.
you MUST be online at the time of installing a new rom
so the windows update downloads the " qualcomm cdma technologies msm" driver that recognizes your FUZE when windows mobile " is not present ".
Click to expand...
Click to collapse
i'm guessing this is the first time you're flashing for W7, the phone goes to bootloader mode and requires drivers that can be gained from Windows Update... after the first time, if you flash again using the same USB port, you'll be fine... using another USB port requires installing drivers again but you'll have the drivers saved in the windows folder
Is there some trick to get customruu.exe working?
Also i have problem syncing, i can only get it working if i disable fast data syncing.
I'm running latest energyrom and win7 ultimate x64 rtm
BigJayDogg3 said:
I don't think I was connected when I did mine.
And that was flashing the Energy rom onto my Fuze.
I can't remember 100%, but I'm ~80% sure I wasn't. Maybe I just got lucky?
EDIT: Though that wasn't the first time I'd flashed. Maybe that was the differentiating factor.
Click to expand...
Click to collapse
yeah, i think thats the difference, i was using a tmobile MDA with WM 5 like 2 years ago, and used to install custom roms but back in the time i had dsl so i never had a problem doing it.
so, BTW, how fast is the Energy rom?
the one i have looks nice but i feel is very slow
paperWastage said:
i'm guessing this is the first time you're flashing for W7, the phone goes to bootloader mode and requires drivers that can be gained from Windows Update... after the first time, if you flash again using the same USB port, you'll be fine... using another USB port requires installing drivers again but you'll have the drivers saved in the windows folder
Click to expand...
Click to collapse
i wonder if there is an offline mode to do this?, without an internet connection.
Daniehabazin said:
Is there some trick to get customruu.exe working?
Also i have problem syncing, i can only get it working if i disable fast data syncing.
I'm running latest energyrom and win7 ultimate x64 rtm
Click to expand...
Click to collapse
not that i know, but i have win7 32 bits version, so maybe its has something to do with the 64 version
It could be that there are no 64bit drivers for the phone available. I use Win7 x32 and it is a hassle getting it first sync'd up. What I normally do is just put the phone in bootloader mode before plugging in the USB cable. That way it only downloads the drivers it needs the first time.
Usually takes me a few resets of the PC and a couple Mobile Device Center restarts to get it to start ticking. Perhaps try downloading the latest Mobile Device Center, even if yours is the latest... just install over the existing installation. That's worked for me a few times.
Is it your first time flashing? Is it a newer Fuze? Because the latest Fuze's have a newer bootloader that is 1.95 (vs 1.90). I haven't found a way around it yet unless perhaps flash an official AT&T rom that has the 1.90 bootloader that may downgrade it... then HardSPL.
Just to add, windows 7 64bit here and haven't noticed one difference or problem with anything.
player911 said:
It could be that there are no 64bit drivers for the phone available. I use Win7 x32 and it is a hassle getting it first sync'd up. What I normally do is just put the phone in bootloader mode before plugging in the USB cable. That way it only downloads the drivers it needs the first time.
Usually takes me a few resets of the PC and a couple Mobile Device Center restarts to get it to start ticking. Perhaps try downloading the latest Mobile Device Center, even if yours is the latest... just install over the existing installation. That's worked for me a few times.
Is it your first time flashing? Is it a newer Fuze? Because the latest Fuze's have a newer bootloader that is 1.95 (vs 1.90). I haven't found a way around it yet unless perhaps flash an official AT&T rom that has the 1.90 bootloader that may downgrade it... then HardSPL.
Click to expand...
Click to collapse
Nah, had my raphael a long time, have flashed a couple of roms before, i'll try to put it in bootloader mode and let it install the driver, i'll keep searching for a customruu that works for 7 x64, Thanks for the reply
i got syncing working, uninstalled the driver for the mobile remote adapter, and let it download a new one from windows uppdate, and now it works, stange since it's the same driver as before...
I was having the same problem with windows 7 x64 and the fuze... found my solution elsewhere so i thought i'd post it here in case someone checks here first like me... I needed to install Windows Mobile Device Center to get the driver to work correctly with an active sync connection =)
I have W7 ultimate x64 and I can't flash either. But I don't mind. I just put the .nbh on the memory card, start up customRUU and it puts my phone in boot loader itself then installs the ROM off th ememory card.
even there's already a WMDC on win7, I tried to download it again from brothersoft, then it's update the driver..... done!
btw I'm using win7 x86, so I haven't tried on x64...
img707.imageshack.us/img707/3830/51947559.jpg
I can't post a pic or link...
Ok, here's the situation:
I have a ZT-180 10" tablet, the 256MB RAM 2G version, 1024x600.
I have flashed it a few times last year until I was OK with it in sept/oct, but now I'd like to go with Android 2.2
I've always used my Vista laptop to flash before, so I went to do it again but had to reload the drivers (not a huge deal), and then was able to start the flash.
I left it for a while because I read somewhere that it takes up to 10mins to finish the SPL update, but when I came back to it, it ended up booting up into the old firmware.
I figured it must have simply failed, so I tried it again, but again had to reinstall the drivers, but this time, when I tried to update the "Unknown Device" driver, I got this message when trying to choose the new one:
"the specified location does not contain information about your hardware"
I have since tried on three other computers, Vista and WinXP with the same result.
Now unfortunately I saw that there's some kind of issue with Vista SP2, which I have since checked, and yes, my laptop must have updated since the last time I've flashed.
Also, my firmware is not new enough to do the SD flashing, so I must get the USB method to work at least once.
The only fortunate thing about this it seems is that my tablet WILL fully boot and function on the old firmware, I am just not able to upgrade it.
I'd really like to get my tablet flashed, so if anyone has any suggestions, I'd greatly appreciate it. I have access to WinXP Pro&Home 32bit, Win Vista Home 32bit, Win Vista Home 64bit, Win 7 Pro 32bit, and Win 7 Home 64bit, as well as Ubuntu 10.10 32bit.
InfoTM Update Wrap tools - IUW Version 1.2
mcleania said:
I figured it must have simply failed, so I tried it again, but again had to reinstall the drivers, but this time, when I tried to update the "Unknown Device" driver, I got this message when trying to choose the new one:
"the specified location does not contain information about your hardware"
I have since tried on three other computers, Vista and WinXP with the same result.
Now unfortunately I saw that there's some kind of issue with Vista SP2, which I have since checked, and yes, my laptop must have updated since the last time I've flashed.
Click to expand...
Click to collapse
There is also a new version of the InfoTM Update Wrap tools - IUW Version 1.2. While the drivers may not have been updated you could attempt with this version and the included drivers.
Search for all instances of the two files listed below and remove before attempting to re-install again using the ones included in the archive of the updated utility attached in post #2 infoTMIC Hardware ID's "hwver" and updates (*.ius)
Code:
secbulk.inf
secbulk.sys
Eureka! Long way around, but here's what I did.
I removed both those files on my XP SP3 32Bit laptop (old 1GHz Toshiba), and at first I was getting the same result, where I couldn't update the driver.
Then I tried the other USB port, and it actually installed correctly!
From there, I got the green light on BurnTool, however when I tried to flash, it gave me another error where "[0][get otg state 0x0]" was all I was getting, then it would boot (which is I think what happened to me originally).
I searched around to find out what that means, and people suggested another cord/USB port.
Tried a couple different cables I had, still getting the same, then I remembered that one of my gf's laptops was a 32bit Vista, so I verified and it was still SP1.
Download everything to it, configure the burntool, plug'er in and boot to flash mode, reinstalled the driver (worked!), got a green light, and when I initiated the flash, stuff actually came up on the ePad!
Unfortunately the flash apparently failed, so I tried again with only flashing the SPL and Boot, and that seemed to work, then I was able to do the rest via SD (no more USB drivers to deal with... yay).
Now my only issue is that I've tried about 5 different roms, and so far the only one that'll boot is from Jan. After flashing 0603, it was boot cycling, after 0324/0326 it just sat on the Android bootup screen, i think the 05 was the wrong screen resolution because I ended up with a bunch of funky colours.
01 at least boots into a usable UI at least, so I hope my experience may help someone else scratching their head. (it helps having access to like a dozen laptops at home)
More good news.
It seems after 0120 installed correctly, now I'm able to get 0603 flashed properly.
Now the only hitch is that I can't seem to access my device on the Market website to remote install programs, but I can still access the Market on the tablet itself, so it's ok.
VTL Launcher is slick btw. I'm liking it, now I just havta do the battery upgrade.
Hey guys. I just got this chinese tablet that is really god at hardware level but i cant install his drivers on my computer. Already searched in many sites but none of the drivers founded were good, can someone help with this one? Does someone have one of this? (is not the deluxe version)
Cheers
For what purpose do you want to connect it to your PC ?
To flash another rom, update to ics.
When i put the tablet into flash mode and plug in to the pc, it tries to install the drivers but dont succed.
I've tried some drivers that i found but nothing. (i saw some good stuff on http://www.slatedroid.com/topic/24356-window-n12-firmware-extracted-rooted-and-slightly-customized/ but i cant donwload the files, forum is too confuse)
P.s: plugging with tablet on it works fine but with access to files.
So before installing Windows 8.1, adb and fastboot worked beautifully, however after grabbing the update from the Metro store, fastboot doesn't work, my phone isn't recognized. It says something about "failed enumeration" in the device manager. I've tried reinstalling HTC Sync and redownloading it from HTC's site ti get the latest drivers (after which I uninstall HTC Sync of course)
I've also tried Koush's drivers but neither installs the fastboot driver.
Theshawty said:
So before installing Windows 8.1, adb and fastboot worked beautifully, however after grabbing the update from the Metro store, fastboot doesn't work, my phone isn't recognized. It says something about "failed enumeration" in the device manager. I've tried reinstalling HTC Sync and redownloading it from HTC's site ti get the latest drivers (after which I uninstall HTC Sync of course)
I've also tried Koush's drivers but neither installs the fastboot driver.
Click to expand...
Click to collapse
I have been trying to get it recognized in fastboot for pas four hours without any luck.. Prior to this, I also had W8 with working fastboot and now I get the same error as well. I tried numerous times, even uninstalled all my drivers (except for display and mouse) to do a clean driver reinstall, but without luck :/
Theshawty said:
So before installing Windows 8.1, adb and fastboot worked beautifully, however after grabbing the update from the Metro store, fastboot doesn't work, my phone isn't recognized. It says something about "failed enumeration" in the device manager. I've tried reinstalling HTC Sync and redownloading it from HTC's site ti get the latest drivers (after which I uninstall HTC Sync of course)
I've also tried Koush's drivers but neither installs the fastboot driver.
Click to expand...
Click to collapse
rs70 said:
I have been trying to get it recognized in fastboot for pas four hours without any luck.. Prior to this, I also had W8 with working fastboot and now I get the same error as well. I tried numerous times, even uninstalled all my drivers (except for display and mouse) to do a clean driver reinstall, but without luck :/
Click to expand...
Click to collapse
Hi, can you guys try this method if you still in windows 8.1???
I personally having a samsung phone and I also having this problem after upgraded to windows 8.1 but now I'm back to windows 8 so I just cannot test it. After test please report back the results to me and I really hope it works. Thanks~
By the way, can you guys tell me your phone model???
DreamerTKM said:
Hi, can you guys try this method if you still in windows 8.1???
I personally having a samsung phone and I also having this problem after upgraded to windows 8.1 but now I'm back to windows 8 so I just cannot test it. After test please report back the results to me and I really hope it works. Thanks~
By the way, can you guys tell me your phone model???
Click to expand...
Click to collapse
Well, I tried something similar, but whenever I uninstalled the usb port from device manager, it reinstalled back and reported that the device is not recognized..
I've got HTC One and its drivers don't work on 8.1. However, I installed HTC drivers (by installing and uninstalling HTC Sync Manager - possibly the lamest method that exists) on Vista and it instantly recognized the phone. So the five hours on 8.1 could have been saved by spending circa 3 minutes on Vista.
But on some forum somebody mentioned that you can use live CD of linux and it will get recognized easily
rs70 said:
Well, I tried something similar, but whenever I uninstalled the usb port from device manager, it reinstalled back and reported that the device is not recognized..
I've got HTC One and its drivers don't work on 8.1. However, I installed HTC drivers (by installing and uninstalling HTC Sync Manager - possibly the lamest method that exists) on Vista and it instantly recognized the phone. So the five hours on 8.1 could have been saved by spending circa 3 minutes on Vista.
But on some forum somebody mentioned that you can use live CD of linux and it will get recognized easily
Click to expand...
Click to collapse
Thanks for your fast reply. Seems that even Microsoft is providing free update for windows 8 but a phone that unable to flash by using bootloader is kinda useless for unofficial ROM users like us.
I have something don't understand from your post. You mentioned that install and uninstall the sync manager on Vista but why not back to 8? The drivers will work on 8 right? I formatted my computer back to 8 and now finally the windows recognize back my phone.
Other than that, do you still have the link to the live CD forum??
DreamerTKM said:
Thanks for your fast reply. Seems that even Microsoft is providing free update for windows 8 but a phone that unable to flash by using bootloader is kinda useless for unofficial ROM users like us.
I have something don't understand from your post. You mentioned that install and uninstall the sync manager on Vista but why not back to 8? The drivers will work on 8 right? I formatted my computer back to 8 and now finally the windows recognize back my phone.
Other than that, do you still have the link to the live CD forum??
Click to expand...
Click to collapse
Well, my primary PC is my laptop with 8.1, but I've got desktop as well with dual-booting Vista and 8.1 and it is way faster to do it on vista, than to partition HDD and install Windows 8. Also I'm not dev or some tinkerer, so I don't need to use fastboot that often.
To answer the second question, I closed all tabs regarding the drivers on 8.1 as soon as I did what I needed on Vista, so I'm afraid I don't have the link. I could probably find it somehow using my internet history, but I spent several hours browsing various forums, so it would take me an eternity...
Hi folks,
wasn't really sure where to post this thread as my phone doesn't have a separate section and since this is more of a general issue rather than one related to a specific phone model, thought I'd try my luck here.
Anyways onto the problem - was gifted a Micromax A092 a few days back. Worked fine until last night when Windows stopped detecting it. When this issue first cropped up, a few times of disconnecting & reconnecting the USB cable got the phone working again but after I plugged in another phone to transfer data and reconnected mine, the issue became permanent and continues to persist.The phone charges when connected to the wall but doesn't charge nor does it get detected when plugged into the PC.
Now when I pull the USB cable and stick it into a different port on the PC, for a second or two, the "connected in charging mode" message appears in the pull down menu and Windows detects phone memory/storage briefly before both disappear. I haven't had the opportunity to plug it into a different machine to check whether its being detected but I can assure you that the USB cable isn't the issue as every other phone in the house works with all the cables I have been using ( 3 to be precise - 2 Micromax and a Sony cable).
Another strange thing I think I should mention in the hope that it could lead to a resolution is that ever since this issue started, none of the phones are being detected by fastboot/adb and don't appear in Device Manager under Android Device as Android ADB Interface. Just two days back, I flashed an Xperia M with fastboot but now the phone doesn't show up under Android Devices, just as Sony 0104 or something. Same with a Galaxy Star Pro. I have reinstalled Android SDK, usb drivers, fastboot/adb but no dice. Opening up the command prompt in the adb/fastboot folder and typing fastboot devices doesn't list any of these phones either.
So can someone please help me in determining whether this is a software or a hardware issue? Any suggestions are welcome and truly appreciated. Thanks.
If you updated your Windows to Windows 8.1 than have following problem:
Since Windows 8.1 MS expects a USB BOS descriptor - USB 2.0/3.0
see htthttp://blogs.msdn.com/b/usbcoreblog/archive/2013/11/26/why-does-my-usb-device-work-on-windows-8-0-but-fail-on-windows-8-1-with-code-43.aspx
There is a dirty solution which works on updated Windows 8.1 update 1:
http://forum.xda-developers.com/showthread.php?t=2598155
Maybe you need a reboot.
fanmile said:
If you updated your Windows to Windows 8.1 than have following problem:
Since Windows 8.1 MS expects a USB BOS descriptor - USB 2.0/3.0
see htthttp://blogs.msdn.com/b/usbcoreblog/archive/2013/11/26/why-does-my-usb-device-work-on-windows-8-0-but-fail-on-windows-8-1-with-code-43.aspx
There is a dirty solution which works on updated Windows 8.1 update 1:
http://forum.xda-developers.com/showthread.php?t=2598155
Maybe you need a reboot.
Click to expand...
Click to collapse
Thanks for the reply
No I haven't updated Windows. Mine's a standalone Win 8.1 installation that's been running for a good few months now.
Like I said, w/o any rhyme or reason, it stopped working in the middle of the night and so did fastboot/adb. I remember typing fastboot devices and having the phone detected just prior to Windows acting up and in following time period, I don't remember installing any software or applying any Windows updates. This issue basically just came out of nowhere.
I'll take a look at the links but will it work for someone who was already using 8.1?
XenolithicYardZone said:
I'll take a look at the links but will it work for someone who was already using 8.1?
Click to expand...
Click to collapse
These work arounds are only for Windows 8.1. The MS Patch should work, if you have not the latest patches. I have the latest patches installed and I cannot install the patch. I need the dirty solution for my old samsungs galaxy models and HTC One X with cyanogenmod 11 - M8.
At the moment I have no further ideas to help you.
fanmile said:
These work arounds are only for Windows 8.1. The MS Patch should work, if you have not the latest patches. I have the latest patches installed and I cannot install the patch. I need the dirty solution for my old samsungs galaxy models and HTC One X with cyanogenmod 11 - M8.
At the moment I have no further ideas to help you.
Click to expand...
Click to collapse
No worries man....guess what? On a whim, I plugged it back in and voila...there was detection. I have no idea how it started working but I have been at it all day and something probably did the trick though I have no clue what it was which is annoying me because if this were to happen again, I would be back to square one.
Ah I see...I did download the patch you had linked to but before I could get around to installing it, this thing started working again. Anyways good to know it won't work with the latest updates as I installed the latest Windows update just this morning myself.
Although now my phone's being detected, the fastboot problem still persists. Neither my phone or any other phones I have access to are detected via fastboot. They all show up under Device Manager as Android ADB Interface but are not recognized by fastboot. Its really irritating me because only 2 days back I flashed the Xperia M on the same damn OS but no dice now. I applied the Windows update hoping it would fix this issue but no luck so far. No software installations, no Window's tweaking...nothing. Hell I haven't even rebooted the PC in the last few days until this started happening. Strange. More research....yay
If you happen to recollect or come across any other workarounds, please do let me know.
use this driver worked for me
download these driver this is only driver fault
d-h.st/ZUh
copy link and download lenovo.zip and in device manager select android and use update driver option to install driver and its done try it works for me
get drivers from
micromax official website