mi 8 lite does not co-operate with win 10 ver. 1803 - Xiaomi Mi 8 Questions & Answers

Hello everybody and thanks for accepting me in such a distinguished community!
I recently bought my mi 8 lite, which i must say, is much better than the reviews want it to be due to their own marketing reasons..........
However, as many people already did, I encountered issues when i tried to put it in fastboot mode and moved on, trying to unlock it.
My win 10 pc, only recognizes it as a Composite ADB Device and when i go into fast boot mode, the device manager goes crazy......it cycles and all of a sudden the device is gone in more or less 10 sec. The fast boot mode also dissappears from the device itself! Needless to say that even if the device is shown at the bottom of the PCs device list, it also vanishes in a few seconds!
I have gone through all possible ticks and workarounds but in vain....................!
For those who will ask, yes, i have activated debugging, yes, i have installed the correct (if existing for win 10) drivers and finally yes, I have tried to go in Test Mode, but again.......in vain! My PC denies everything.
So, i was directed by a friend to, and tried through win 7 and after doing everything i should, i got 274hrs from xiaomi untill it unlocks..........
Is there anybody to suggest anything else that i could possibly do, to make these two opponents, become friends???? (i mean win 10 and mi 8 lite)
Is any other co-forumist facing similar issues ?
Are we really able to overcome this or we should go back to 7?
The motherboard of my computer is only win 10 compatible (STUPID ME>>>>) and its is an ASROCK H310-HDV. I have also tried to find any hidden function, with -of course-dissapointing results.:crying::crying::crying:
Thanks in advance for any answer or effort made by anyone in here!
Respectfuly
ioannisthom

I have Windows 10 and driver get on Windows Update.

Related

Stuck on serial and version 2.08

Hi please help me , i'm stuck in boot loader mode trying to update my rom to windows 6.1 , i have vista on my computer .
I searched the forum but cant find any useful help.
I know lot many had this problem and have got sorted out , so please help me with clear instructions.
Thanks in advance,
shank
since you are using vista, it is very unlikely, that your device is actually stuck in bootloader mode, it was your pc, causing that error. because the device changes its identity, while upgrading, vista (and windows 7) seem to think, it is necessary to look for new drivers. maybe you saw the driver search in the bottom right corner of the task bar.
so, basicly you have 2 options to get your device back, either you get to a pc with xp and perform the upgrade properly, or you try the vista method.
for the xp way, have a look here:
http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel_WM6_WizzardUpgrade1_WM2003SE0
that is the first step in the tutorial on how to upgrade and i bet you didn't do that in your first attempt
for the vista way, refer to this page:
http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel_WM6_WizzardUpgrade4_Vista
or if you want it in pictures, this:
http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel_WM6_WizzardUpgrade4_Vista_Pic
i personally never got the vista way to work, not in vista home premium 32, nor in ultimate 64, and in windows 7 ultimate 64 it does not work for me neither.
the very best you can do in your situation is, try the vista method, and either it works, than proceed with the wizard i gave you as the xp link, or get to an xp computer and start with the wizard right away.
if your device really is stuck in bootloader (still unlikely), post back, and we try mtty
got the same problem but am working under windows 7 x64 so it willl be a serious issue
neverdmind fixed worked on my laptop with xp
I am still stuck
Can do nothing. Have this message on the screen and even then I try to connect it to my Vista there is no connection.
Is it that ****ty or something can be done
welcome to the forum!
your problem starts with v and ends with a (like so many evil things do): vista. ok, that was off, sorry, let's get to the facts now:
this is probably what you have experienced during the unlucky attempt to upgrade your device:
you start upgrading, everything looks fine, your pc's RUU (the rom upgrade utility, what you used to start the upgrade) is working fine, your device's screen said usb and v2.0X and then "upgrading" but then at some point, your pc said, "wait a minute, this is not the device i am used to, i cannot charge or sync it, and it also does not respond with the usual name!" so, vista is as 'smart' as trying to get a new driver for the device, making the sounds of a usb device unplugging, and a new one plugging in, that's when your connection is lost, and that is bad, because the wizzard told you before, to "never unplug the device, unless the upgrade process is over". you see, what happened there?
vista's ability, to make driver installation easier for the user has become bad for you in this situation, as you were relying on, say, windows xp's stubbornness.
ok, you say, why would he tell me all that? i saw that happening!
yes, but now you know what caused the problem. now we get on to solving it.
there is a nice tutorial in the wiki, where you can find a driver for vista x86 and x64, that will behave like the xp driver used to, it will charge the device, sync it, and still be able to upgrade, you find the wiki entry -=here=-, and -=here=- again with screenshots.
when you arrived at successfully having installed the driver, so making the screen on connection change from serial to usb, without vista searching for new drivers, you arrived at the point, from where on you can continue, or better restart, flashing the rom you originally intended to.
but let me say, after breaking rule 1, when it comes to flashing, may i advice you to read a little more about the general topic in the link -=here=-, because i can guarantee you, that that was not the last mistake you made with the upgrading process, and since you probably don't want to start from scratch again in a few days, you should ask yourself these questions:
have i formatted the extrom?
have i resized the partitions to gain storage space?
do i have a proper RUU?
did i pick the right rom?
what about sim unlock?
what about radio rom update?
do i know how to reset a device with a higher os than wm2003?
if to either of these questions, your answer was not a clear "yes!!", but a "no" or even "what is he talking about?" you should definetely make a little research before starting over, because you are breaking hardware limitations here, doing things, htc originally intended trained service professionals to do, not home users, this is something that could break your device or at least cost you a lot of time to repair, when done wrong, so please read the links i gave you, it will save a lot of your nerves. here you are again, -=the most important link=-
and -=another link with a common misunderstanding cleared up=-
have fun reading, you won't regret it.

[frustrating] HELP HD7 seen as "generic device" not as WP, drivers fail to install

[frustrating] HELP HD7 seen as "generic device" not as WP, drivers fail to install
So i got my wp7 today...i download zune on my windows7 pc, install, connect the phone....ERROR installing drivers, the phone is seen not as a mobile device, but as a generic usb composite device...in the device management window i have two "unknow device" icon...tried EVERY POSSIBLE SOLUTION i found on the internet...worked for others, not for me...
...then i think maybe it's my pc, so i try my xp netbook...SAME HAPPENS...
previous owner says he connected the phone to zune flawlessly on three different PCs...
i also did a full reset from the settings
HELP I'M DESPERATE
anyone?
It seems that your device is in diagnostic mode (the 2 unknown devices are typical for this...)
for now there is no way back, but if this is without you hacking something or so you could let it repair by warranty...
is it a complete new device?
thank you very much for the answer...
this is getting intresting
my situation is similar to his one
http://forum.xda-developers.com/showthread.php?t=937235
but that image isn't showing up on my hd7 and my two devices are "unknown devices" no shubert, just unknown device.
(EDITrobably because he has his pc set up to receive the phone in diagnostic mode, but my pc isn't)
Now what i think is that the previous owner did some tethering (he told me that), but didn't put it back into zune mode...then he did a hard reset before giving the phone to me...but i'm pretty sure the reset doesn't FLASH the plain rom, but only wipes data because it's too fast
so i'm stuck here with a half usable wp7...nice
elmerendeiro said:
thank you very much for the answer...
this is getting intresting
my situation is similar to his one
http://forum.xda-developers.com/showthread.php?t=937235
but that image isn't showing up on my hd7 and my two devices are "unknown devices" no shubert, just unknown device.
(EDITrobably because he has his pc set up to receive the phone in diagnostic mode, but my pc isn't)
Now what i think is that the previous owner did some tethering (he told me that), but didn't put it back into zune mode...then he did a hard reset before giving the phone to me...but i'm pretty sure the reset doesn't FLASH the plain rom, but only wipes data because it's too fast
so i'm stuck here with a half usable wp7...nice
Click to expand...
Click to collapse
Did you try right clicking the device in device manager and selecting update driver software, then click Search automatically for updated driver software?
Mine kind of did the same thing until I allowed it to connect to microsoft and got the driver from them.
Also you could also check HTC website for HTC HD7 driver software.
Yep, but it doesn't find any driver...even if i point it directly to the zune drivers folder...the only driver that seem to get installed is "windows phone USB device" or something like that..i have to install it manually, then one of the two unknown devices transforms into that wp USB..the other one remains unknown, unless i force it to install "Windows phone" from portable devices->microsoft...then it fails and give me error10, but still the icon changes to the portable device one...
From HTC i will probably get vague or dumb answers...like "try hard reset"
Tomorrow i will see the guy who sold me the hd7 and try to connect to zune on his pc...if it works i have to keep it otherwise he will refund me...he says he tried with hd2 to tether then uninstall the tether software without putting it back to zune mode and he says that it works with no issues...HELP
i maybe wrong, but maybe u can try to load one of those rom's for europe brands, it may re set all the settings on your hd7...
but the best will be for the first owner to show you the way he did it...
so when he didn't put it back into zune mode there is no way back at the moment..
i will tell you if i know more...
the diagnostic mode isn't set on your computer... it's on the Qualcomm SoC (System on a Chip)
The drivers you need are somewhere http://forum.xda-developers.com/showthread.php?t=922000 here (don't know exactly where)
but that won't help you much as you only get "HTC Diagnostic Interface" as Serial Device...
so you have to wait till there is a solution....
btw. I'm stuck in the same situation ;-) (Diagnostic Mode) xD
and there are lots of other people too, so you are not alone ^^
best regards
EDIT:
@truffle1234:
i tried flashing another rom a few weeks ago, but it didn't help...
so it's better for all to stay with the stock-rom at the moment because we cannot get back to it at the moment
it's better for warranty
So if the phone is in diagnostic mode, it shouldn't properly connect to zune on the previous owner's pc,right? Let's see
it shouldn't connect normally at any pc...
ok, did the same on his pc so i got refunded...now maybe i go omnia7...the loose volume rocker and the visible sim card through the back cover have really bugged me in just one day...in any normal company who's responsible for that crap would be insta fired...i mean, didn't they produce any test device before sending the papers to production???? meh...
wp7 was nice btw
got another hd7 (no see thru battery cover, and no loose volume rocker this time!) and connected to zune flawlessly...so definetly that one was stuck in diagnostic mode
Great news, hope you enjoy it. It's a decent device and a great OS!
jimbonics said:
Great news, hope you enjoy it. It's a decent device and a great OS!
Click to expand...
Click to collapse
well should be more than decent as it's supposed to be the top of htc wp7 line...but still...
i got a 2nd hd7 just because i hate big bezels around the screen...if omnia7 had a smaller case around that 4inch would definetly have been my choise
is there a fix for this? I feel like throwing my phone out the freaking window. ugh!!
What exactly is your problem turbo? What OS are you using, etc?
Here's what I can say about this.
Install Zune. Reboot your computer. Let your computer FULLY boot.
Plug in your phone. Seriously be patient and let your PC think for a good 3-5 minutes. The first time it goes through this it is NOT a quick process.

[Q] Update error 801812C

Hi
My beloved HTC HD7 on O2 (Unlocked now) advises me that their is an update.
I imagine this is the pre-update to the No-Do update
However everytime i try to install i get to stage 6 and then the error 801812C is reported.
I have searched this and found the same answer in every article regarding-
"During Step 6 (Rebooting your phone), your Windows OS detects your phone as a new device and starts searching for driver updates online. This can be seen when you click on the little indicator with a spinning green circle in the bottom-right corner of your desktop called the notification area (you might need to click on Show Hidden Icons if it's hidden)."
"You have to *immediately* click on "Skip Obtaining Device Software Online" or Zune will time-out and show error 801812C1"
However i see no option come up on XP to allow me to stop such device updates. And i definatly have no hidden icons!
Someone please help with a better solution...
Jayne (Yes i am a girl so be nice, so sartactic answers please, I am Tech savvy but this one eludes me)
From what you post, it sounds as if maybe you have to right-click the notification icon in the system tray for that option.
From what i understand from the OP's first post, she doesn't have the icon so can't right-click it.
I know it's not really a solution, but have you tried updating on a Windows 7 machine? I've always thought that windows 7 is more compatible with WP7. I know this isn't excplicitly mentioned anywhere, but why else would the Dev Tools only be available in Win7? strange....
Windows 7
Many thanks
Yes indeed no notification is showing and I have set the taskbar not to hide inactive icons so nothing can be lurking!
I will see if i can find someone with Windows 7 as i'm a XP user through and through lol
Many thanks for the ideas so far but if anyone has another brain wave please contribute, I don't want to miss out on the proper upgrade when it arrives..this week fingers crossed eh!
same error here
Hi Jayneh,
I too have an HD7 on o2 (Sim unlocked, but stock otherwise).
I am also an XP sp3 user, and I'm getting the same error as you, 801812c1.
The update fails at step six. The phone will reboot and then show a picture on the screen suggesting I connect my phone to the pc, despite the fact it is connected already. I've tried three times with no joy so far.
I've done some searching and as you say, the current theory is that after rebooting the phone, the pc doesn't recognise it as WP7, but Wm, and proceeds to hunt for the right drivers. This will of course fail, and the update times out.
Several users on different model of phone have reported the error and Microsoft are advising you hold off updating until the issue is investigated.
A number of users are saying they are using Windows 7, so it can't be an Xp specific problem.
Several fixes have been reported by some users which include unplugging and re connecting the phone quickly, or stopping the pc hunting for non existing drivers by clicking the update icon in the notification area. This does not seem to work for everyone.
I have tried unplugging which didn't work for me. I looked for the update icon but can't see one, but in anycase, my machine runs incredibly slowly during the whole process so doing anything at all is frustrating.
One thing I haven't seen anyone reporting is whether they use the same machine to sync a WM6.1/6.5 device or not. I do, but I'm just grasping at straws here.
I'm also slightly worried as I only have a little over 10GB left on the laptop.
Here's hoping NoDo isn't a NoGo for us.
Garrickus
Many thanks Garrickus, as long as i'm not alone with this and it is being looked at, hopefully if all else fails the fab developers on here will soon have us an update rom we can port straight to our HD7's. Fingers crossed and hope the sucking up to the developers speeds this along
One solution to the 801812C1 error code
jayneh & Garrickus,
Do you have windows automatic updates turned off?
I had automatic updates turned off (XP Home 2002) and I had the same problem when I first tried updating.
After reading something elsewhere, I turned automatic updates back on and tried updating again 24 hours later. It worked, with the update running smoothly through all 9 steps without a hitch.
I don't know if you have to wait after turning automatic updates on, I just thought it would be prudent.
I'm also using an HTC HD7 on the o2 network. I hope this information helps you like it helped me.
Ian.
Automatic updates
Hi Ian,
Thanks for your feedback regarding automatic updates.
Unfortunately, I have automatic updates turned on, and PC and Zune are fully up to date, so that's not an option for me.
Interestingly, Zune had a minor update after a couple of failed phone updates and now when the little bubble pops up it describes my device as 'Zune' not 'Windows Mobile', but still getting same error code and updates fails exactly the same.
I see their is no specific response to this error code from Microsoft as yet
Are you still experiencing problems Jayneh ?
Garrickus.
Update
I was still having problems and my PC was/is up to date and automatic updates is on.
I say was because i now have the NoDo update having followed the brilliant update method by Petbede for updating without a gold card.
It went smoothly and here i am with a speedy phone and cut and paste. My god bejewelled loads so much quicker
frustration
Im using Vista, have the same problem as Garrickus. HD7 on Vodafone network. After reboot the device pops up as Zune device and computer tries to look for Zune drivers, after some time it gives up. I have tried all ways of updating drivers, nothin works.
Hi everyone,
I experienced that problem today downgrading my HD7 with Zune installed on XP SP3, three times it didn't work...then i closed all running app like firefox & other utilities...and the downgrade process worked at least...
My advice : just be patient!
Update WP7 driver on PC before running the WP7 upgrade
The error '801812C1' appears when the phone is wrongly identified as a 'Zune' device (MS MP3 reader !) after the phone restarts at step 6 of the WP7 March 2011 upgrade.
In order to set the correct WP7 device on the PC:
1. Shut down the phone (press & hold the power button)
2. Restart the phone and press & hold the camera button
3. A black screen appears on the phone showing a device connected to a PC
4. Connect the phone to PC on USB port
5. Open Device Manager on PC and check the entry for Portable Device: 'Schubert' (= HD7) or other name (depends on your phone).
6. Shut down the phone (press & hold the power button) and restart it.
7. Connect the phone to PC and run the WP7 upgrade from Zune.
The error '801812C' no longer occurs at step 6.
Imerda said:
The error '801812C1' appears when the phone is wrongly identified as a 'Zune' device (MS MP3 reader !) after the phone restarts at step 6 of the WP7 March 2011 upgrade.
In order to set the correct WP7 device on the PC:
1. Shut down the phone (press & hold the power button)
2. Restart the phone and press & hold the camera button
3. A black screen appears on the phone showing a device connected to a PC
4. Connect the phone to PC on USB port
5. Open Device Manager on PC and check the entry for Portable Device: 'Schubert' (= HD7) or other name (depends on your phone).
6. Shut down the phone (press & hold the power button) and restart it.
7. Connect the phone to PC and run the WP7 upgrade from Zune.
The error '801812C' no longer occurs at step 6.
Click to expand...
Click to collapse
This worked perfectly!! Thank you!!
I got a error "801812C0" and it said device couldnt be updated. i took the battery out and restarted it and it was updated wtf lol

WPDR tool doesn't see my device. Because no Microsoft account present?

Hello again.
Windows Phone Developer Registration tool doesn't "see" my device. I've double checked all requisites (.net framework, IpOverUsbSvc, phone listed in file explorer, screen unlocked, correct time, internet connected, etc.) The only issue I can think of is the fact that I still haven't set up a Microsoft account in the phone; but... is this reason enough for the WPDR tool to not even see the phone?
Any hint appreciated. Thanks!
That's probably the cause, yeah. You could try setting up the account to see if it works, then...
Well, I've found something interesting: when I've plugged my device to a virtual machine running win8 and the full WP8 SDK, it recognized my phone instantly. So, now we know that a device that has not been set up with a Microsoft account can be dev-unlocked.
So, definitely there's something wrong with my installation of the hacked SDK-lite. Or maybe the drivers. I have a kind of mess in my laptop because of all the previous drivers and programs for Symbian and my Nokia C7. I still find it hard to get used to the idea that Nokia is not Nokia anymore, but Windows. I have to repeat to myself twice a day: "I don't own a Nokia Lumia, but a Microsoft Lumia".
Thanks for caring, GDTD.
zogoibi said:
Well, I've found something interesting: when I've plugged my device to a virtual machine running win8 and the full WP8 SDK, it recognized my phone instantly. So, now we know that a device that has not been set up with a Microsoft account can be dev-unlocked.
So, definitely there's something wrong with my installation of the hacked SDK-lite. Or maybe the drivers. I have a kind of mess in my laptop because of all the previous drivers and programs for Symbian and my Nokia C7. I still find it hard to get used to the idea that Nokia is not Nokia anymore, but Windows. I have to repeat to myself twice a day: "I don't own a Nokia Lumia, but a Microsoft Lumia".
Thanks for caring, GDTD.
Click to expand...
Click to collapse
Well maybe the virtual Win 8 OS with WP8 SDK recognized your phone because Win 8 has the winusb drivers build in. On Windows 7, you need to install these winusb driver (you normally have a unrecognized device called Windows Phone 8 in the Device Management).
Link to the drivers : http://catalog.update.microsoft.com/v7/site/Search.aspx?q=winusb http://catalog.update.microsoft.com...updateid=90462af8-f533-4522-9ad1-dcc969d94832
Hmm... Well, this is strange. My device seems to be perfectly recognized by the system. Actually, every time I plug the phone in I get a popup window listing it under "devices and printers" with the correct model (RM-892 | Nokia Lumia 925). In the device manager it appears as a Nokia USB device, with no exclamation marks nor any sign of "wrong driver". Yet, the hacked SDK insists in not finding it.
On the other hand, I've tried to install the "winusb" driver you mention, but the link you provide redirects me to somewhere where there is no such driver, and I haven't been able to find a download. In any case, there are at least five copies of winusb.sys in my system...
Don't know what am I doing wrong.
zogoibi said:
Hmm... Well, this is strange. My device seems to be perfectly recognized by the system. Actually, every time I plug the phone in I get a popup window listing it under "devices and printers" with the correct model (RM-892 | Nokia Lumia 925). In the device manager it appears as a Nokia USB device, with no exclamation marks nor any sign of "wrong driver". Yet, the hacked SDK insists in not finding it.
On the other hand, I've tried to install the "winusb" driver you mention, but the link you provide redirects me to somewhere where there is no such driver, and I haven't been able to find a download. In any case, there are at least five copies of winusb.sys in my system...
Don't know what am I doing wrong.
Click to expand...
Click to collapse
You need to visit the website with Internet Explorer. Go to google type "winusb windows phone microsoft update catalog" and go to the site with "catalog.update.microsoft.com" in the URL. If you don't see the download link of the driver type "winusb windows phone" in search. There should be an unrecognized device called "Windows Phone 8" in the device manager (start menu -> My Computer -> right mouse click -> Manage -> Device Manager in left context menu) for this driver to be installed, if not I can't help you further.
Thanks Bruce. I've done what you said and was able to download winusb. It's a .rar package containing two files, winusbcompat.cat and winusbcompat.inf. Now, if I'm not abusing your patience... what do I do with them?
[EDIT] Ok, don't bother. I figured out how. Actually this solved my problem. After properly installing the winusb driver, the WP8 SDK lite by Arnold Vink recognized my phone.
Thanks to everybody who helped me "out".
Now I wonder how could I mark this thread as "solved"...
Hi,
My Nokia Lumia 925 won't respond to anything (NSU, NSU->”My phone does not startup or respond”, Nokia Care Suite->recover phone, volume down + power button,…).
Already leave it charging for several hours. Can’t have any reply from the phone.
Now the phone is kind of dead. Can start it and the only thing I see Is a QHSUSB_DLOAD (Nokia Emergency Connectivity) in PC.
I have tried many things according to internet but i can't get any success windows device recovery tool is also not detecting my phone and it is not listed in it. i have tried thor command also not working it says invalid hex file.
Please help me to recover my phone from QHSUSB_DLOAD mode.

Bootloader/Fastboot With Windows 10

Hey all, I'm new to the forums and was wondering if anyone might have an answer to a problem I've been having.
I'm not too sure what information to provide, but just let me know what you need and I'll find it for you.
I've been using the HTC Desire C since September 2012 and lately I've been wanting more out of it since support has stopped, so naturally I wanted to find out how to root it. I began the process, but when I opened the bootloader/fastboot menus on my phone and plugged it in to my laptop (tried with the original micro USB cable too), Windows did not recognize the device. It does recognize it when the phone is booted normally. Now, I've had it working before, but I recently upgraded from Windows 7 to Windows 10 and I'm pretty sure that's where the problem started. I've tried downloading the latest sync manager from HTC, but that didn't help.
If anyone might have the slightest idea as to what might work, I'd be very happy. Unfortunately, using a different version of Windows or another OS isn't an option for me as all my family and friends have upgraded to WIndows 10 and I don't personally wish to roll back, so hopefully there's a solution out there that can work with Windows 10.
Thanks in advance for anyone willing and/or able to help me out.
http://forum.xda-developers.com/htc-desire-c/help/htc-desire-c-unknown-usb-devicedevice-t3212105 tested yesterday

Categories

Resources