[GUIDE][SOLUTION]MediaTek SPFlashTool failure - Disconnect after 2 sec is by design! - Upgrading, Modifying and Unlocking
Hey everyone
This mostly applies to those of us that have a bricked MediaTek device. Yes the ones amongst us that are the most desperate I am sorry to say. Some of you laugh at that cause your Flashing experience has worked perfectly from the get go and you have flashed successfully with functioning device. Well that's great. Good for you! You're awesome. Sooner or later you are going to make a mistake and panic is going to set in and you will be where I have been. I am sorry to say that is not a very nice place.
For me it was not my device which makes matters worse. I was translating a device for an older gentleman who purchased it from Alibaba; it's an MTK6589 device to be precise.
Anyway I am sure a lot of you out there are frustrated with why your device is doesn't work with SPFlashTool even though you have been following the most of the tutorials to a T? Why your device disconnects from device manager 2 seconds after you plug the thing in and it disappears out of the device list? Like WTF right? Well would you look at me strangely if I said that this is actually by design? That yup your MediaTek device is actually meant to do that?!
If you have experienced this, then I have answers for you and I have an explanation as to why your MediaTek device is doing this, and why your device has not been able to be flashed by SPFlashTool.
Really we are our own worst enemy when it comes to this MediaTek woes; Why? Cause we are impatient and we go off looking for answers in the wrong direction when in fact they are right in front of us all along. Here I will hopefully expand your understanding about these devices and why/how things work so that you can apply it in the future.
I will explain my situation and what I discovered in the process. Hopefully it sheds some light on disconnect device driver situations and lays some thing to rest....hey maybe even some of you who had given up and tossed your cheapo China phone in the bedside draw cause nothing worked and it wasn't worth the price to send back, maybe you guys might want to give this a go and revive your MediaTek device?
Follow this guide step by step BUT READ EVERY STEP EVER SO CAREFULLY.... also take note of the points below that I am going to emphasise that AREN'T emphasised anywhere in this tutorial nor any other tutorials I have followed, so pay attention.
http://forum.xda-developers.com/showthread.php?t=1982587
The part that is not emphasised is this
Turn off your phone, remove the battery and replace it after some seconds (and don't turn on the phone).
Press F9 (or hit Download button) and connect your phone into the computer via USB data cable.
The process will start and a red progress bar will appear.
Click to expand...
Click to collapse
In both cases the word 'and' should be replaced with the word 'THEN' so that people will understand.
What isn't really mentioned on any tutorials is that the MTK6589 is different to how you flash other mediatek devices with SPFlashTool; why? Because you MUST put the battery back in before you flash unlike other MTK devices where they explicitly say DO NOT put it in and/or that you should flash without the battery in place. THIS IS INCORRECT!
Next thing to emphasise is this: You must have the phone disconnected when you click on the download button inside SPFlashTool. You press download then you put the battery back in your phone with the USB connected to the phone., wait and when the download part finishes (only a few seconds) THEN you plug the phone in to the computer (yes with the battery still in place) but do not switch the phone on.
When the phone is detected by Windows and starts to load the drivers like it usually does and then disconnects...well what happens now is that when it loads drivers for a second SPFLashTool engages the phone and holds open the connection. It will pause for a couple of seconds (but you will notice it doesn't disconnect) and then SPFlashTool will show a red/orange progress bar that goes quickly....then it will write the firmware when you see the yellow progress bar.
Something to note here (I downloaded literally hundreds of drivers by the way) that you only need 1 driver and that is the one mentioned in the tutorial.
You don't need to do all the bullsh!t with device manager and removing drivers etc with USBDview....this should only be if the phone doesn't read initially as MTK65xx preloader OR doesn't end up registering as MediaTek DA USB VCOM.
So I will explain...when you plug it in on a clean WIndows 7 PC for he first time it will appear as MTK65xx preloader under device manager under unknown device and Windows will attempt to download the correct drivers and then fail. This is normal.
DO NOT GO AND INSTALL PDANET DRIVERS!!! This doesn't work.
Yes the drivers ARE more stable and don't disconnect nearly as much as the other MediTek drivers, however what this does is register the devices as an Android ADB device, and allows you to use ADB. We want to use SPFlashTool, not ADB at the moment.
Installing other MediaTek drivers after PDANet for some reason causes a conflict and interferes with communication with the device?? I suspect that this is what was causing much of the issues I was experiencing? You may use the PDANet drivers after you have flashed via SPFlashTool if you cannot get an ADB connection, however in my case once the new firmware was written to the device and it was restored and fully functional; when I plugged it in the ADB drivers loaded automatically anyway
Ok next points to make. Unplug your device. Install the drivers (I have attached the ones that worked for me). NOTE: You may need to log in allowing unsigned drivers as mentioned in other tutorials. To do this you can use EasyBCD, go into advanced settings for the Windows 7 bootmenu entry and allow the use of unsigned drivers and put a wait of say 10seconds on the menu count down (in stock form Windows has assigned 30 seconds but standard it bypasses the boot menu - this makes it harder to press the F8 key during boot up). After finishing in EasyBCD reboot and when you come to the Windows boot menu press F8 anyway and choose allow use of unsigned drivers. This is a just in case thing.
Get EasyBCD from HERE
Once in Windows, plug in your device WITH THE BATTERY IN and device switched off. Open Windows device manager (a quick way is type devmgmt.msc in Start menu or Run menu from the start menu - if you search for the management console by full file name you can right click the devmgmt.msc and pin it to the Start menu this is what I have done).
In device manager you NEED to see the device registered as MediaTek DA USB VCOM. If it is not appearing push the volume up button + but keep the phone OFF. When it appears for just a second make sure it is MediaTek DA USB VCOM. *This is important* It must NOT be registered as Preloader or any other MediaTek driver ie. Preloader USB VCOM port OR MediaTek USB VCOM (Android) etc. IT MUST BE MediaTek DA USB VCOM Just look for the one that has DA in the name and is a VCOM driver. This is the driver we want:good:
Ok here is where I will mention that USBDview removal of drivers is not necessary and does absolutely nothing anyway because Windows 7 remembers every single driver you have installed regardless of the fact that you have removed/uninstalled and even checked the box delete drivers or what ever. It doesn't matter...every driver you have ever tried will be in the device driver list. USBDview is only good for unregistering the device association with a registered driver. It doesn't remove drivers.
So now where was I? Ahh right, yep. When you plug in your device (switched off and the battery in place) and it appears momentarily in device manager it must be MediaTek DA USB VCOM, If not Or if it disappeared too fast; just push the volume up button again and this time as it appears quickly, click to expand the (PORTS COM &LPT) listing, then quickly right click the MediaTek listing and go to Update Driver Software. You may need to do this several times to get it. Unplugging the USB from the PC and plugging it back in again may help.
Resist the urge to search for new drivers as the device IS actually detected but not as a PORTS COM &LPT, and doing so will be fruitless as you will only assign the incorrect drivers to the incorrect function. So unplug and replug it in again pressing volume up.
Note: It does not matter if the device disconnects and disappears out of Device Manager when you are in the Upgrade Device Driver software menu....this is normal. The most important point here is that the correct driver is being registered to the correct device protocol (pressing the volume up button to get COM&LPT).
The device needs to appear as MediaTek DA USB VCOM and this must be registered specifically to the (PORTS COM &LPT) in device manager. If it lists elsewhere as a USB device and has the MediaTek DA USB VCOM driver assigned to it, then you need to uninstall the driver from the device listing and start again. Don't go looking for more drivers PLEASE!
Click for explanation
Ok I will digress again for a moment to explain why all this is so important and what many of us are not realising especially with all the tutorials around; the important point here is that MediaTek devices may be listed many numerous devices in device manager and this is normal. They could be an ADB android device, a MediaTek USB Port version etc and these are not the functions we want to use for flashing with SPFlashTool are they? I know when I plug in my Galaxy S3 it loads at least 5 different drivers! Same with these devices.
We need to have the (PORTS COM &LPT) registered as MediaTek DA USB VCOM and this ONLY achieved when we press the volume up button!! If the device disappears from the list after plugging it in and appears as something else and then we register the MediaTek DA USB VCOM driver to this function we are likely trying to use the MediaTek DA USB VCOM driver to load the MediaTek USB Port function and this is obviously NOT the protocol that SPFlashTool is using to communicate with the device to write new firmware.
Ok I will continue now, once you have got into the Upgrade Driver Software menu,
Go to 'Browse my computer for device software',
Then select the second option 'Let me pick from a list of device drivers on my computer', just choose the 'show all' at the top of the list
Next you *should* see MediaTek DA USB VCOM listed in amongst various MediaTek drivers., select this one.
* However if you do not see MediaTek DA USB VCOM listed in the list there then uncheck the box next to 'Show compatible drivers' and it should now show a few more drivers.
You may need to scroll in the right menu bar down to MediaTek.
You will be hit with an overwhelming list of MediaTek drivers! See Pic for reference
Select the required MediaTek DA USB VCOM driver from the list. If its not there (then and only then) you should try install another set of drivers and restart the process again. Try the drivers I have attached below first though.
At this point please resist the urge to click 'Have disk' then 'Browse' to and go scouting for a specific driver in the hopes that this will be the one; THIS IS WRONG! and should not be recommended like it is in just about every tutorial I have seen so far.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's funny how even the drivers you previously removed are included in that list eh? You know...the ones that everyone told you, you need to delete bla bla bla...THEY ARE STILL THERE DAMN IT!
Once you have selected the driver as MediaTek DA USB VCOM and closed out of the menu you will notice that it has actually gone from the list in device manager? This is normal. The driver is only meant to appear when we do a specific thing and that is pressing the volume up button to write firmware using SPFlashTool and nothing else.
As I mentioned earlier, this is by design. You will note that MediaTek devices, have these protocols USB Mass Storage, MTP, PTP, ADB and COM &LPT.
Now unplug your device. I would at this point do a reboot of Windows (again ensuring unsigned drivers by pressing F8 - just incase)
Once you're back inside Windows, open device manager again.
Keep the device off and have the battery in.
Plug the MicroUSB end into the device first (it's easier - trust me you will understand when I explain).
Now keeping it switched off but press and hold the the volume up button and then plug the cable into the PC USB port; watch as it registers inside device manager as MediaTek DA USB VCOM.
When it does, disconnect the cable from the USB port. - You are now good to go
Now Open SPFlashTool.
Select the scatter file.
Uncheck the following from the list (Preloader, MBR1, EBR1, Uboot, Sec_Ro, Logo, EBR2 and FAT - note fat is for the internal sdcard). We want to write to system, recovery and boot pretty much. If you have ruined your device with the incorrect preloader,
Keep the device UNplugged. Click the download button. You will see the purple progress bar but for only a very brief moment. This is ok and is normal.
IF you have completely obliterated your device by flashing an incorrect preloader click below
I have been advised that you may need to first flash the Preloader, MB1, EBR1,Uboot and EBR2) to setup the partitioning again. The preloader I assume is similar to a PIT file for Samsung devices?
Now we do as we did before. Plug the MicroUSB end in first to your device. Have it switched off but with the battery in place. Press and hold the volume up + button and then plug the cable in to the PC USB port again.
At this point you will hear the device register with Windows as you normally would however you should notice that it doesn't disconnect straight away like it normally does?
This is because the MediaTek DA USB VCOM is registered to the PORTS COM &LPT and SPFlashTool is listening on this port.
Then shortly after progress with a Red/Orange bar.
It will pause for a what seems like a long time..... but please leave the device plugged in! [shouldn't be longer than 10min - if it is you've done something wrong, disconnect and do the process again and read making sure you understand every one of the points I have made in this post]
Once you see the yellow progress bar you can breath with relief.
Congratulations you have just revived your bricked device! :good:
Additional Info: After a reboot when you plug the device into the PC USB port again you should start to see Windows identify the extra protocols associated with your MediaTek device. I noted than this one I was working on appeared back as an MTP Portable device, also as an ADB Android device further up the list and as an MTK USB Port when the volume up button is pressed (I guess now Windows knows what it is it is assigning it a different driver?)
But what if it doesn't disappear? I have the problem with ZTE V967s that i cannot flash it (probably dead), because I have "ENABLE DRAM FAILED (4032)" issue.
This is probably because the phone cannot exit the VCOM status, it is visible under this state for many minutes in device manager. Do you have any ideas how to solve this problem?
How i unbricked my Lenovo K3 Note (MTK6752)
Hi,
First of all I am thanking God Jesus Christ for helping me find a solution.
My Lenovo K3 Note was hard bricked when i accidently unplugged it while sp flash tool was flashing the firmware. The screen was not at all lighting up(Not even boot logo). When battery is inside and press power button i could see a feable red colour light near the proximity sensor. When i connect my phone to PC without battery (As many sp flash tool procedures says us to remove battery and connect) , it was not at all being detected by pc. This was my condition..!!!
I searched tried a lot for 5 hrs.. Continously.. Yes literally..
At last I started my own experiments. I downloaded complete stock firmware. and loaded it to sp flashtools by selecting scatter file. I selected the format+download option in sp flash tools. I clicked download button in sp flashtool. Now sp flash tool is waiting for my phone to get connected.
I removed the battery of phone, then i pressed the volume buttons, power buttons etc.. to remove static charges if present (for 10 seconds). "Then i put the battery back to the phone. "
I connected the usb cable to phone ,keep pressed the volume up key, then the other end was connected to the computer. SP flashtool detected my phone and flashing started(Now i released volume up key press). Wait for sometime till flashing completed and we get OK pop up in sp flash tool. Wait for some 10 seconds . Dont remove phone from computer. Press and hold the power button for switching on the phone without removing from computer.
If screen doesnot light up, release the buttons, remove the phone from computer . Press the power button two three times(Dont hold). Now press and hold power button to switch ON your phone. Thank God and Be happy seeing your phone booting up. :laugh::laugh:
if cant non-removeable battery(0% battery) for mtk phone. what shoud i do? power + volup ??? or something
Related
|GUIDE| PC Does Not Recognize Note 2
If you get the errors that state that your phone is not recognizable or the drivers on your new PC is A. Cannot be found B. Any other message that doesnt state "Your Device Is Ready To Be Used" Then follow this guide 1. This is really simple and easy, CHANGE THE CABLE. Maybe the cable you are using cannot transfer data correctly or its just broken or it just doesn't like you. 2. Some have reported that using a USB 3.0 port on the PC in question may not work correctly. Try using a USB 2.0 port instead if possible. 3. Now this is what works the best if you use custom cooked roms. -Launch the phone key pad on your note and press *#7284# (don’t forget to start with that * symbol!) -When you press the last pound sign (#) this will bring up an option that will allow you to change your USB connection settings (modem or PDA) – change it to PDA. -At the bottom there is a button that says Qualcomm USB. Click on it. -In that menu click on MTP + ADB option. -Save and reset. -Wait for your phone to restart. -Plug the micro USB cable to the Note 2 and the the other end to your PC or Mac -Let your computer down load and install drivers. -Once installing is done, unplug then replug phone. -There should be a USB symbol on your phone in the status bar - click on it. It should ask if you wsnd to use mtp or ptp. Click MTP -At this point your PC should open the phone’s folders in explorer similar to the screenshot above. Do a little dance, make a little love, get down tonight. i do not take credit finding all of this by my own, i used google.
problem install driver MOOREFIELD
Hi everyone, My zenfone 2 ZE551ML is bricked, so i followed this guide http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256 The problem comes when i arrived to the step of IntelSoc: I install it, no problem until here, i got IntelSoc driver in my device manager . But when i want to have the MOOREFIELD driver, I cant get it. Following this perfectly Ash back to the Zenfone 2, shutdown, press simultaneously the key "source" + "volume +", of course you will see a screen hanging cables( I don't have hanging cables though, I just have the Logo Asus and write on the top in blue Fastboot mod !!!). -Connect to your computer via USB cable, to standard Intel SOC driver position, wait a few seconds if the current add an item immediately below another MOOREFIELD new devices is successful. -If You have not been, the test performed as follows: turn off the machine, plug the cable into the computer, press the power button until the device vibrates slightly, then release. If you have an idea can you help me please. I think this is the only thing who blocks me in repairing my phone... Thank you
Yea that problem also persists with my zenfone 2,cant install moorefield 'cause pc cant recognize my phone. Somebody please help us out.
Anagh21 said: Yea that problem also persists with my zenfone 2,cant install moorefield 'cause pc cant recognize my phone. Somebody please help us out. Click to expand... Click to collapse it is clearly instructed in that thread you mentioned. just keep few things in mind.. uninstall every mobile related driver before installing isoc. uninstall xFSTK tool if you already installed it before installing isoc. third as you are concerned about the line you mentioned morefield under intel soc. well during soc install you will see windows like attached below. at this stage you need to power cycle your device . ( turn off your device holding power button for 10 sec. then connect to pc and turn on. leave connected to pc and turn off again and turn on second time to make sure so driver are installed) don't worry if you don't see morefield under soc now. just go ahead and install xFSTK. now your concern that your device don't stays in morefield download stage ( i mean it appears in device manager and disapear) . after installing xFSTK. run it as administrator and load files. and change gp flag value. also change device detection timeout to 120. now click begin download it will start waiting for device. now turn off your device completely and connect to pc and turn on. xFSTK will force it to stay in required mode. if download do not starts. just power cycle the device while being connected to the tool. ( note: it is strongly recomended that you install isoc and connect mobile before installing. if you have already installed xFSTK then plz uninstall it and install it after performing above said steps. remove all other mobile related drivers also and if you are using windows 8 or 10 disable driver signature enforcement again even if you did it earlier)
The problem with asus flash tool solved Solution : Open device manager i.r. Windows + X .... if your phone is not being detected... switch it on and off ... there will be ( other devices menu ) that will show your phone there.. right click on the phone , click update drivers, ofcoarse no drivers online, locate the drivers manually , wherever your bootloader file is i.e. the 1 gb file you download or the raw file as we can speak ... i didn't pin pointed it ... my file was on the desktop so I just chose desktop and it searched it and installed it. After that the phone was successfully in the computer and being detected by the flash tool.
No Command, No ADB, No Fastboot Nexus 5X
So I updated my phone to fix "critical bugs". The phone turned off went into TWRP, restarted and I was met with "no command". Oh great I forgot I was rooted again. So I open up TWRP, connect to my computer and try adb, oh it didn't work. I played with the drivers for literally forever installing the google driver, and various third party ones, reading every online tutorial. No work. I purchased a new high quality cord with charging+sync. It still did not work, at this point I decided that I would use ubuntu instead of windows, I have more experience doing this stuff in ubuntu anyways. Well it still did not work, the same error. No Device Found. I went through a few tutorials on some other troubleshooting, I used nirsofts usbinfo tool and I also used lsusb in ubuntu, and I could not find my phone connected. I could plug it in and out and the lsusb would look the same either way. Though my phone was still charging. I then tried on another computer with ubuntu as well and the same problem then too. Any ideas?? I am kinda on vacation and it was my source of data+contacting people. Also somewhat concerned about the new system where they check your electronic devices at border security, when it doesn't work they definitely will think its a bomb.
Le bump??
Bump, does anyone have any ideas???
My Nexus 5x randomly stopped working on ADB saying devices not found earlier this year. That device bootlooped and received my replace a couple weeks ago and decided to finally setup and not sell it. The same thing was happening to my replacement device so I knew it was the drivers on the computer since my Sony Xperia X was able to ADB and all that. I finally setup my phone today and updated the firmware and found the issue. This is what ended up working. Steps: 1) Uninstall old drivers by going to Windows key + R key together. Type devmgmt.msc and hit enter to open Device Manager. 2) Click on Android device or Portable Device and find your device, right click and uninstall driver. 3) Download/Update Google USB driver through SDK manager and install. 4) Connect your phone with the cord and it should install its own drivers. 5) Windows key + R key again, devmgmt.msc to go to Device Manager. 6) Go to Android Device or Other and right click on your phone and update driver software. 7) Click on Browse my computer from driver software. 8) Click on Let me pick from a list of device drivers on my computer. 9) There should be 1 or 2 lists under Model. Double click on the first one and it will update it. After that finishes, go back to step 6 and until you get to step 9 to double click and update the other item on the list to update. 10) Reboot computer and connect your device and it should work. If you don't see Android Device > ADB interface in Device manager when you update the Google USB drivers, click on Portable > Nexus 5x and update drivers and just follow steps 6-9, then update the Android Device under Device Manager. Once thats all done ADB should work, for me it did today but the android with no command showed up. For that when your at that screen, Hold power button + tap volume UP once (don't hold it, just tap and let go) and it should bring you to recovery screen with the choices.
Riverdales27 said: My Nexus 5x randomly stopped working on ADB saying devices not found earlier this year. That device bootlooped and received my replace a couple weeks ago and decided to finally setup and not sell it. The same thing was happening to my replacement device so I knew it was the drivers on the computer since my Sony Xperia X was able to ADB and all that. I finally setup my phone today and updated the firmware and found the issue. This is what ended up working. Steps: 1) Uninstall old drivers by going to Windows key + R key together. Type devmgmt.msc and hit enter to open Device Manager. 2) Click on Android device or Portable Device and find your device, right click and uninstall driver. 3) Download/Update Google USB driver through SDK manager and install. 4) Connect your phone with the cord and it should install its own drivers. 5) Windows key + R key again, devmgmt.msc to go to Device Manager. 6) Go to Android Device or Other and right click on your phone and update driver software. 7) Click on Browse my computer from driver software. 8) Click on Let me pick from a list of device drivers on my computer. 9) There should be 1 or 2 lists under Model. Double click on the first one and it will update it. After that finishes, go back to step 6 and until you get to step 9 to double click and update the other item on the list to update. 10) Reboot computer and connect your device and it should work. If you don't see Android Device > ADB interface in Device manager when you update the Google USB drivers, click on Portable > Nexus 5x and update drivers and just follow steps 6-9, then update the Android Device under Device Manager. Once thats all done ADB should work, for me it did today but the android with no command showed up. For that when your at that screen, Hold power button + tap volume UP once (don't hold it, just tap and let go) and it should bring you to recovery screen with the choices. Click to expand... Click to collapse There is no android device or portable device, I have used many oem cables too.... Using usb diagnostic tools it doesn't even show it as plugged in, though it still is getting a charge. The positive and negative wires still are supplying electricity but the sync wires are not working, though it doesn't seem to matter what cable I use. With the second part, do you mean with using the SDK tool? I was just installing the google drivers from the standalone installer.
I don't know then. You have usb debugging enabled on developers option.
Do you have the "Qualcomm HS-USB QDLoader 9008" ? In the com ports? If so jump to this thread nexus-5x/help/finding-solution-qualcomm-hs-usb-t364828
OP3 shutdown and not turning on anymore, VolumeUP doesn't show it in device manager
While listening to some music and a normal usage my OP3 strangely got freezed for a second and then shutdown itself. The phone was recently unplugged so it was almost fully charged, I'm running TWRP with Magisk on top of a stock ROM. I've tried to follow the mega unbrick guide but my device doesn't even show up upon pressing the VolumeUp for 10 seconds so I really don't know what to do. I've browsed the "similar threads" suggested without any improvement. I'm open to any redirect or suggestion to at least troubleshoot the issue because as of now I don't even know what's wrong.
Maxiride said: While listening to some music and a normal usage my OP3 strangely got freezed for a second and then shutdown itself. The phone was recently unplugged so it was almost fully charged, I'm running TWRP with Magisk on top of a stock ROM. I've tried to follow the mega unbrick guide but my device doesn't even show up upon pressing the VolumeUp for 10 seconds so I really don't know what to do. I've browsed the "similar threads" suggested without any improvement. I'm open to any redirect or suggestion to at least troubleshoot the issue because as of now I don't even know what's wrong. Click to expand... Click to collapse One issue may be the drivers. If on Win 10, it becomes trickier. You have to disable the driver signing before attempting to install drivers. If the drivers are properly installed, then power off the phone and hold the Power button down for 40+ seconds. Then hold down the Volume Up button for 10 seconds and then without letting go of the button, connect the phone to PC and wait till the phone appears on the PC before releasing the Volume Up button. Try it a few times if unsuccessful at the first instance. I have successfully gone through this earlier and now maintain all the drivers including adb, fastboot, Qualcom etc on the Laptop by periodically checking my phone's connectivity. I don't want to be faced with a situation like yours.
I've done the mentioned steps for Windows 10 but the guides says: Step 5 :- Press only volume up button for 10 seconds and while keeping it pressed,connect your phone to PC.Keep volume up pressed till your device shows in device manager as [Unknown Device,QHUSB_BULK (under Unknown Devices) or Qualcomm HS USB ...... (under COMs and Ports)]. Step 6 :- Right Click on your device in the device manager and select Update Device Software. Choose the .inf file manually from x86 or x64 folder as the case implies and select Qualcomm 9008 from the listed devices.If you are unable to see 9008,see the end of post for various other methods to show Qualcomm 9008. Click to expand... Click to collapse I can't even show my phone in the device manager, hence I cannot even proceed with the driver installation (i've disabled the signature already).
Maxiride said: I've done the mentioned steps for Windows 10 but the guides says: I can't even show my phone in the device manager, hence I cannot even proceed with the driver installation (i've disabled the signature already). Click to expand... Click to collapse If it is not showing up at all, then it may mean that the procedure for 40 sec and 10 sec has not been done properly or that you have a hardware issue. Did you install the drivers first, after disabling driver signature verification?
tnsmani said: If it is not showing up at all, then it may mean that the procedure for 40 sec and 10 sec has not been done properly or that you have a hardware issue. Did you install the drivers first, after disabling driver signature verification? Click to expand... Click to collapse Tought about it and repeat it several times. I've disabled the verification before attempting the install. As an additional info when plugging the device to the original wall charger the led doesn't turn on liked it is supposed to do when charging.
Maxiride said: Tought about it and repeat it several times. I've disabled the verification before attempting the install. As an additional info when plugging the device to the original wall charger the led doesn't turn on liked it is supposed to do when charging. Click to expand... Click to collapse Install Dview in your PC and see whether all the drivers you installed are reflected there. Also check which, if any, driver becomes green when you try to connect. If necessary (as there may be a clash between the drivers) delete all USB drivers in Dview, Google drivers will install automatically. Then reinstall OnePlus drivers.
tnsmani said: Install Dview in your PC and see whether all the drivers you installed are reflected there. Also check which, if any, driver becomes green when you try to connect. If necessary (as there may be a clash between the drivers) delete all USB drivers in Dview, Google drivers will install automatically. Then reinstall OnePlus drivers. Click to expand... Click to collapse What's Dview ? Google it but I have mixed results of different things.
Maxiride said: What's Dview ? Google it but I have mixed results of different things. Click to expand... Click to collapse Sorry, should have been more explicit. USBDview shows all the drivers installed in your PC. This is it https://usbdeview.en.softonic.com/
Pixel 2 XL isn't detected on my PC [help]
After upgrading to Android Q suddenly my pc can't recognize my pixel as a android device also i can't connect any wired things such as dongle jack or USB Transfer (USB charging options disappeared). Planning to downgrade to Pie but the problem is my device can't be detected on my pc. Any solutions? Thanks
If you're using a Microsoft Windows machine, I would suggest uninstalling any "Android" drivers from the Device Manager. Then restart the PC, then turn off "USB debugging" and back on for the Pixel, and even "Revoke authorizations" in hopes that it will re-alert & request another authorization and, therefore, verify it being connected and detected on the PC.... After all that -- or if you can only enter in Bootloader Mode -- type the command "fastboot devices" and say here what it outputs. If anything, while in Bootloader Mode, do what I previously said, but look for anything "Android" and "Bootloader" and uninstall those device drivers... Good luck and hope this helps!
simplepinoi177 said: If you're using a Microsoft Windows machine, I would suggest uninstalling any "Android" drivers from the Device Manager. Then restart the PC, then turn off "USB debugging" and back on for the Pixel, and even "Revoke authorizations" in hopes that it will re-alert & request another authorization and, therefore, verify it being connected and detected on the PC.... After all that -- or if you can only enter in Bootloader Mode -- type the command "fastboot devices" and say here what it outputs. If anything, while in Bootloader Mode, do what I previously said, but look for anything "Android" and "Bootloader" and uninstall those device drivers... Good luck and hope this helps! Click to expand... Click to collapse Thanks for replying, i already tried to uninstall android driver, but when i try to reconnect, my pc recognize my device as "unknown device"
blancheSX said: Thanks for replying, i already tried to uninstall android driver, but when i try to reconnect, my pc recognize my device as "unknown device" Click to expand... Click to collapse what about the other things I suggested? Or, so it can be clearer, are you in the System/OS when plugging/reconnecting or in Bootloader Mode?
I ran across the same issue..I followed this video to get rid of the old USB drivers and updated to the new Android driver.. Now my window 10 recognize my pixel 2xl storage completely. https://youtu.be/Zc_dhxc8iJU
I have this issue before, and after all i got my phone detected. But when i flash it, it say unbootable slot in fastboot screen. After couple onf time, it cant be flashed again and die.... My phone cant turn on in fastboot mode again, it bricked
I had to use the USB dongle to connect a flashdrive to my phone, wait for it to recognize the drive, then unplug the drive and dongle... Then connect phone to PC... Profit!
If anyone is still having the issue of PC not recognizing device in fastboot, please be sure you have UNinstalled the older version(s) of SDK Tools from yhour PC and make sure to INSTALL the latest versions. You can find the latest version linked in the 9x guide in my signature. Also, make sure you have both older and newer USB cables handy. The Pixel has a nasty reputation for being finicky with USB cables, try diff cables and different USB ports on your PC. There is also a basic troubleshooting guide in the same link in my sig. Best regards!
simplepinoi177 said: what about the other things I suggested? Or, so it can be clearer, are you in the System/OS when plugging/reconnecting or in Bootloader Mode? Click to expand... Click to collapse i did in 2 conditions, first one is my device turned On (adb is not detected) also 2nd one is my device in bootloader mode (fastboot devices is not detected too) been trying to update my driver but i always got (error code : 10, device cannot started) i dunno what to do right now
dallas90733 said: I ran across the same issue..I followed this video to get rid of the old USB drivers and updated to the new Android driver.. Now my window 10 recognize my pixel 2xl storage completely. https://youtu.be/Zc_dhxc8iJU Click to expand... Click to collapse i tried those tuturial and ended in error code : 10, device cannot started.
SageWilliams said: I had to use the USB dongle to connect a flashdrive to my phone, wait for it to recognize the drive, then unplug the drive and dongle... Then connect phone to PC... Profit! Click to expand... Click to collapse whenever i try to connect a flashdrive with my dongle, there is no option or something, it's just usb charging option appeared.
blancheSX said: i did in 2 conditions, first one is my device turned On (adb is not detected) also 2nd one is my device in bootloader mode (fastboot devices is not detected too) been trying to update my driver but i always got (error code : 10, device cannot started) i dunno what to do right now Click to expand... Click to collapse blancheSX said: whenever i try to connect a flashdrive with my dongle, there is no option or something, it's just usb charging option appeared. Click to expand... Click to collapse So…without you being too definitive…it seems that you’re able to get into your OS… What I’d like you to do is uninstall and remove Google usb drivers on your computer. Then, download it again HERE: https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip . And, in case things don’t work out this time around, if you can please save the (.zip) file on your Desktop or root folder (usually the C: drive). I might have you direct the device detected to the files in this .zip directly. Then, after installing the USB drivers, I’d like you to uninstall and remove any/all things that are named “platform-tools” (so there will only be ONE "platform-tools" after you re-download it in this step) on the whole device. After, I’d like you to download the latest Windows version HERE: https://developer.android.com/studio/releases/platform-tools . Again, to simplify things, if you can extract it either in your Desktop or root folder (C: drive). Again, like I mentioned before, I would like for your device to request authorization for your computer again, so if you can please go to the Developers option, and select “Revoke USB debugging authorizations” as well as double-checking you have "USB debugging" enabled… Only THEN, once these two things are extracted and installed (as is the case in the first step) and you revoked the authorizations, can you plug in your device and USB cord. Watch your phone/device, as it will ask for authorization to connect to your computer, and you’ll have to make sure the box is checked that says “don’t ask this every time” or “remember this device” – I can’t recall off-hand – and then make sure to “Allow” it. By doing this, you can be sure that your computer and device are talking correctly. *One suggestion that isn’t mandatory is that you select where it says “USB charging” and change it to “MTP” or “file-sharing” (sorry, again, I can’t recall specifically off the top of my head…) If all things are working well, if you can open up a command prompt (a.k.a. “cmd”, and also make sure you are running it “As an administrator”) and direct it to the platform-tools directory (hopefully you followed my suggestion and kept it simple so it will either be at the root “C:\” or on your Desktop “C:\Users\[username]\Desktop” so it won't be too difficult directing it there...), and run the commands Code: adb devices and Code: fastboot --version . Hopefully, if you do all of these things, it might get things reset and working from a stable established set up. If it somewhat works, but the device in your "Device Manager" is showing up something "funky", then it'll take a rather nuanced Windows troubleshooting technique to resolve where I would have you correct the wrong entry/driver in the "Device Manager" and have it specifically point to one of the contents of the .zip files; shown prior.... We'll tackle that if need be and if all this initial beginning troubleshooting doesn't pan out... Let me/us know how it works out, good luck, and hope this all ends up being helpful…
simplepinoi177 said: So…without you being too definitive…it seems that you’re able to get into your OS… What I’d like you to do is uninstall and remove Google usb drivers on your computer. Then, download it again HERE: https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip . And, in case things don’t work out this time around, if you can please save the (.zip) file on your Desktop or root folder (usually the C: drive). I might have you direct the device detected to the files in this .zip directly. Then, after installing the USB drivers, I’d like you to uninstall and remove any/all things that are named “platform-tools” (so there will only be ONE "platform-tools" after you re-download it in this step) on the whole device. After, I’d like you to download the latest Windows version HERE: https://developer.android.com/studio/releases/platform-tools . Again, to simplify things, if you can extract it either in your Desktop or root folder (C: drive). Again, like I mentioned before, I would like for your device to request authorization for your computer again, so if you can please go to the Developers option, and select “Revoke USB debugging authorizations” as well as double-checking you have "USB debugging" enabled… Click to expand... Click to collapse thanks for ur explanation, and i'm sure i already did this 100% as you mentioned before. looking for solution and i found this at pixel community thread : https://support.google.com/pixelphone/thread/14477635?hl=en and btw when i try to disable and back to enable (again) USB debugging, there's no pop up or something like that, just nothing appear. so i just realized why i got error code : 10 is just because my phone still not detected by PC also i tried in other computer (with windows 8.1 installed) my device is got detected but as "device descriptor request failed" not as an android device. Hopefully next update google will fix this "bug". Once again thank you very much
blancheSX said: thanks for ur explanation, and i'm sure i already did this 100% as you mentioned before. looking for solution and i found this at pixel community thread : https://support.google.com/pixelphone/thread/14477635?hl=en and btw when i try to disable and back to enable (again) USB debugging, there's no pop up or something like that, just nothing appear. so i just realized why i got error code : 10 is just because my phone still not detected by PC also i tried in other computer (with windows 8.1 installed) my device is got detected but as "device descriptor request failed" not as an android device. Hopefully next update google will fix this "bug". Once again thank you very much Click to expand... Click to collapse Yeah...I figured as much...I was just making sure to lay down the "ground work" before proceeding... If you're still willing....what I had planned next was to walk you through manually updating/"editing" the driver (on the PC) to directly look at the Google usb drivers specifically to try and get around the whole "device descriptor" and other (detection) error codes.......
Might want to try uninstall the SDK toolkit, reboot PC, then install the latest SDK toolskit. Also having both USB 2.0 and 3.0 cables saved me more than once, and is a known thing on the 2XL.