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.
Related
Ok here's the story,
I had an older version of windows mobile, really buggy and kept freezing all the time. So I Figured let's upgrade to a newer version! YAY.... But that kinda failed miserably, and now my phone is stuck in bootloader.
I Tried the MTTY Stuff but that won't give an USB Port under ports.
I Tried flashing in bootloader mode but I kep getting Error 101 and 150, meaning wether it can't find the phone and if it can find it it tells me the rom version isn't right for me.
I'm really sure the rom version is right for me, and my windows Vista starts installing Mobile Device drivers as soon as I plug the phone in so that's connected and all.
Only it won't update. Took everything out too, no SD No sim .. nothing.
Anyone, please reanimate my phone
GWD said:
Ok here's the story,
I had an older version of windows mobile, really buggy and kept freezing all the time. So I Figured let's upgrade to a newer version! YAY.... But that kinda failed miserably, and now my phone is stuck in bootloader.
I Tried the MTTY Stuff but that won't give an USB Port under ports.
I Tried flashing in bootloader mode but I kep getting Error 101 and 150, meaning wether it can't find the phone and if it can find it it tells me the rom version isn't right for me.
I'm really sure the rom version is right for me, and my windows Vista starts installing Mobile Device drivers as soon as I plug the phone in so that's connected and all.
Only it won't update. Took everything out too, no SD No sim .. nothing.
Anyone, please reanimate my phone
Click to expand...
Click to collapse
"Windows Vista"..... uh huh
So it has been fixed, and yes I used windows Vista to do it... In your face vista uhuh guy!!!
I took the old windows XP drivers, deleted the vista one, installed the XP one, closed to device center, put it back on into boot mode.
Serial appeared, plugged in the USB and ran MTTY or something software. Selected USB that worked fine now
Typed the set 14 0 stuff pushed enter. shut down the program. and used the bootloader to install the latest and greatest Windows Mobile 6. All worked perfectly!!!!
So for the people with windows vista, just install the old windows XP drivers and you're ready to go, with out the loss of the latest technology
XP in Vista??
So, can you explain exactly how you installed the XP drivers into Vista... My Uni is pretty much the only reason I'm running a multi-boot system anymore!!
Any problems caused??
I tried to fight the Vista urge, but after having Ultimate installed on all the systems at work, I could fight no longer!!
GWD said:
So it has been fixed, and yes I used windows Vista to do it... In your face vista uhuh guy!!!
I took the old windows XP drivers, deleted the vista one, installed the XP one, closed to device center, put it back on into boot mode.
Serial appeared, plugged in the USB and ran MTTY or something software. Selected USB that worked fine now
Typed the set 14 0 stuff pushed enter. shut down the program. and used the bootloader to install the latest and greatest Windows Mobile 6. All worked perfectly!!!!
So for the people with windows vista, just install the old windows XP drivers and you're ready to go, with out the loss of the latest technology
Click to expand...
Click to collapse
i'll resist the urge to call you a "fool", but had you not put your foot in your mouth...i.e SEARCHED BEFORE WRITING...some one would have come to your help...
read this for upgrading in vista
http://forum.xda-developers.com/showthread.php?t=292631
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...
Okay so I am about to go insane trying to get this to work. I've got a MyTouch3g which I just flashed cyanogens 5.0.7 this past week and haven't been happier.
However I was trying to get ADB to work on my new laptop, as my desktop machine is out of commission at the moment. I remember how much of a pain it was to get working, but this is getting ridiculous.
I am running Win 7 64bit with all windows updates. I downloaded the Android SDK and followed all the instructions to the T from cyanogen wiki. Except when I plug my phone in, it reports USB device is not recognized and has 'malfunctioned'. I don't even get anything reported under Device Manager except 'Unknown Device'. From here I've tried updating the device via numerous google reports of 64 bit usb drivers to no success. I also tried the Motorola Droid drivers for the 64 bit via a installer and still no success. I even tried the HTC Sync which still, no success.
I tried using USBDeview and removing any HTC and going from those steps as well, there were two HTC devices listed from when it previously worked fine on my 4.2 cyanogens, and again this didn't help the matters.
At this point I am wondering if something is wrong with my phone? I cannot even mount my SDCard anymore.
So I had the dreaded Win 7 x64 crash. I uninstalled IE 9. No go. Used that DLL fix (which I can't remember where I found it). Still crashed. So here's how I got around the problem.
Note:
I'm just sharing what I found since none of the solutions I googled up worked for me (maybe I'm the only one). For those who wonder why anyone would bother with stock Froyo, I'm sure there are reasons. I just wanted to do some testing of the upgrade exactly as it came from Samsung. There's probably an Odin flashable package somewhere which may be bit-for-bit identical, but I didn't bother looking. I'm hoping this will work if another update comes down the pike (Ha!) and Kies is still broken.
Here's what worked for me. It may brick your phone so understand that before you start.
Step 1:
Load up Virtual PC.
In Virtual PC:
Install the Samsung drivers
Install Kies Mini
Install Samsung PC Studio (for Gadget Serial driver)
Step 2 - back to the phone:
Flash stock. I flashed one-click JF6, but use the right stock firmware for your phone (build 1010 and later phones should use something like this)
Step 3:
At this point you may want to make sure the Gadget Serial driver is loaded and working (if you one-click flashed JF6 skip to step 4), so put the phone into download mode and plug it into the PC.
In Virtual PC:
USB Menu->Gadget Serial Attach
Insure that driver is working. If it isn't then the update won't work because Kies Mini will not be able to communicate with the phone after it goes into download mode. If it works then skip to step 5. If not then do step 4.
Step 4:
Have CWM update.zip on you sdcard root directory
Reinstall packages
Reinstall packages again
Install zip from sdcard
Install sbl_CWM_update.zip (attached to this post)
Do the step 3 check. If that fails then the Gadget Serial driver isn't recognizing you phone and this isn't going to work unless you can fix it.
Step 5:
Reboot the phone, turn on USB debugging then plug it in to the PC.
In Virtual PC:
Start Kies Mini
USB->Samsung_Android Attach
Start the upgrade
Wait 12 years or so until the phone goes into download mode
USB->Gadget Serial Attach
The install should continue automatically. If it doesn't there is an upgrade button which should be enabled when driver is loaded and the phone is detected.
Wait for the install to finish, at which point to phone should boot into Froyo.
Done.
thanks
cool, i had tried all of the other ways of forcing kies to recognize my computer... but it always ended with the same crash, nice little white box where the program should be. so im trying this out but its taking forever to get xp virtual machine up and running. i will post again with my final results
ok now for my story
i have had flashed multiple versions of cognition on my phone and have become very familiar with the process. i do love cog 3.04 but the problem is that the swype that is loaded on the rom is a 60 day trial version and it ran out. so i wanted to try out the stock froyo and see what improvents i wanted so i could cook my own rom.
i went and got kies mini on the release date for froyo and it was crashing everytime i used it, giving me this lovely white box on my windows 7 x64 ultimate computer. i tried multiple work arounds and have never thought of virtual machine so thank you for that.
i want and ran my odin one click reflashed to jf6, then decided to see if kies recognized my phone. it imediately was recognized and started to update in the virtual machine.
it is currently downloading to my phone and i will repost again if my phone either becomes soft bricked or if the update goes through
Please help me find the Gadget Serial Driver for My Samsung Vibrant
I've been trying to Update my Samsung Vibrant from version KA2 to version KB5 using Samsung Kies mini to no avail. I am running Windows XP SP3.
I know, this is a developer site but I have a feeling I won't be able to develop at all because I when I try to update to (Official) Froyo (Provided through Kies mini), I get stuck in download mode with the yellow sign forever. Luckily I can restore by taking the battery out and rebooting my phone. This is problem is due to not having a Gadget Serial Driver installed. Now note, I have all the other USB drivers installed properly. They all show up in Device Manager, however the darn Gadget Serial Driver is MIA and Windows only notices that is missing the driver when the phone enters Download Mode. I have searched xda developers for this issue and I have seen a number of posts where other people have had the same issue and maybe a couple of people solved it by installing PC Studio. I have Googled up and down the internet, went to Samsung's website and even spoke to a Samsung Representative for a link to Samsung PC Studio. However all of the links I found were either dead, contained fake software or were just shady.
Samsung's site no longer contains an actual download link to PC Studio or New PC Studio (I don't know the difference). Can someone please help me get this Gadget Serial Driver or the PC Studio software which may solve this driver issue? Please don't point me to any "Samsung USB Drivers For Mobile Phones" links because I've downloaded that driver and it has solved nothing. Thanks in advance and sorry for sounding like a complete n00b.
privetKalla said:
I've been trying to Update my Samsung Vibrant from version KA2 to version KB5 using Samsung Kies mini to no avail. I am running Windows XP SP3.
I know, this is a developer site but I have a feeling I won't be able to develop at all because I when I try to update to (Official) Froyo (Provided through Kies mini), I get stuck in download mode with the yellow sign forever. Luckily I can restore by taking the battery out and rebooting my phone. This is problem is due to not having a Gadget Serial Driver installed. Now note, I have all the other USB drivers installed properly. They all show up in Device Manager, however the darn Gadget Serial Driver is MIA and Windows only notices that is missing the driver when the phone enters Download Mode. I have searched xda developers for this issue and I have seen a number of posts where other people have had the same issue and maybe a couple of people solved it by installing PC Studio. I have Googled up and down the internet, went to Samsung's website and even spoke to a Samsung Representative for a link to Samsung PC Studio. However all of the links I found were either dead, contained fake software or were just shady.
Samsung's site no longer contains an actual download link to PC Studio or New PC Studio (I don't know the difference). Can someone please help me get this Gadget Serial Driver or the PC Studio software which may solve this driver issue? Please don't point me to any "Samsung USB Drivers For Mobile Phones" links because I've downloaded that driver and it has solved nothing. Thanks in advance and sorry for sounding like a complete n00b.
Click to expand...
Click to collapse
This is for the flight II but the software has the PC Studio download. Good Luck!
http://www.samsung.com/us/support/downloads/SGH-A927ZAAATT
privetKalla said:
I've been trying to Update my Samsung Vibrant from version KA2 to version KB5 using Samsung Kies mini to no avail. I am running Windows XP SP3.
I know, this is a developer site but I have a feeling I won't be able to develop at all because I when I try to update to (Official) Froyo (Provided through Kies mini), I get stuck in download mode with the yellow sign forever.
Click to expand...
Click to collapse
Thanks man. That made my day. I needed that.
You can also get the Heimdall suite and open the drivers folder and run Zandig. Then connect your phone in download mode it should show gadget serial in the device window click install and it should complete and you're good to go, this is how I did it after 3 days trying to get my phone to stop showing the device malfunction error which is due to another problem on my main xp machine, a sony which I can't get usb 2.0 drivers for from sony or anywhere else to work correctly even though all 8 ports are 2.0 according to support, my manual, and previous xp install and that's after installing xp 4 times to get the graphics driver to install right so I could then install the right ati driver which everyone online with this model sony seems to have to do, but back on topic. I hopped on my windows server 2k3 machine which had correctly working usb 2.0 drivers ran zandig with my cappy in dl mode and BAM finally working gadget serial driver, just make sure you have zandig.exe open, and connect your phone in DL mode or you'll just install the equivalent of the standard samsung drivers which you prolly already have, I haven't been able to test this on a win7 machine but from what I've read the heimdall driver should work on them and worked great on both xp and server 2k3 on my home server machine.
Sent from my SAMSUNG-SGH-I897 using XDA App
Jsmokey said:
You can also get the Heimdall suite and open the drivers folder and run Zandig. Then connect your phone in download mode it should show gadget serial in the device window click install and it should complete and you're good to go, this is how I did it after 3 days trying to get my phone to stop showing the device malfunction error which is due to another problem on my main xp machine, a sony which I can't get usb 2.0 drivers for from sony or anywhere else to work correctly even though all 8 ports are 2.0 according to support, my manual, and previous xp install and that's after installing xp 4 times to get the graphics driver to install right so I could then install the right ati driver which everyone online with this model sony seems to have to do, but back on topic. I hopped on my windows server 2k3 machine which had correctly working usb 2.0 drivers ran zandig with my cappy in dl mode and BAM finally working gadget serial driver, just make sure you have zandig.exe open, and connect your phone in DL mode or you'll just install the equivalent of the standard samsung drivers which you prolly already have, I haven't been able to test this on a win7 machine but from what I've read the heimdall driver should work on them and worked great on both xp and server 2k3 on my home server machine.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Best first post I've seen in quite some time. Thanks for that.
boborone said:
Best first post I've seen in quite some time. Thanks for that.
Click to expand...
Click to collapse
Thanks I appreciate that I just wanna give back as much as I've received from the forums here its a great place to start. If anyone runs into any problem with this let me know and I'll see if I can reproduce and come up with something.
Sent from my SAMSUNG-SGH-I897 using XDA App
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