This is a guide on how to get fastboot to work on any windows and any USB Port such as USB 3.0.
I have an ASUS N550JV that is running windows 8 64bit and only has USB 3.0 ports and I have successfully used fastboot on it.
I don't take any responsiblities for bricking your Phone/PC/Notebook although it has no risks at all. SO do as the instructions below and get yours to work too.
Here are the steps to do it:
1. Installing HTC Drivers on your windows:
* 1. a) If you are on windows 8 follow the instructions here. You can also download the drivers for windows 8 from the Attachments or Dev-Host.
* 1. b) If you are on windows 7 or XP just download this .exe file from the Attachments or Dev-Host and run it.
* 1. c) Restart your PC/Notebook
2. Relating to your USB port choose one below
* 2. a) If you have USB 2.0 ports on your PC/Notebook go to fastboot in your phone and plug it to your PC/Notebook. If "Fastboot USB" is shown on your phone's display without pressing any key, then you don't need to follow the steps below.
* 2. b) If you only have USB 3.0 port on your PC/Notebook follow the steps below.
* 2. c) If you want to use USB 3.0 on windows 7 follow the steps below.
3. Restart your PC and go to boot options.(Mine is by pressing the F2 key repeatedly before showing windows boot animation)
4. Go to Advanced> USB Configuration> XHCI and disable it. If you can't find it ask from your manufacturer about how to do it.
5. Restart your PC and enjoy
Credits
Hippie459MN for the HTC Drivers on win 8.
thom2k
Me (Taher Di) for searching alot and combining two guides.
If it worked for you just press the Thanks button.
Taher Di said:
This is a guide to get fastboot to work on windows 8 and USB 3.0
I have an ASUS N550JV that has only USB 3.0 ports and windows 8 64bit and I was trying to use fastboot on it.
I have tested it and it works perfect. So do as I did and get yours to work.
Here is the steps to do it:
1. Installing HTC Drivers on win 8: Follow the instructions here.(Thanks Hippie459MN)
2. Restart your pc and go to boot options.(Mine is by pressing the F2 key repeatedly before showing windows boot animation)
3. Go to Advanced>USB Configuration>XHCI and disable it.
4. restart your pc and enjoy
Credits
Hippie459MN for the HTC Drivers on win 8.
thom2k
Me (Taher Di) for searching alot and combining two guides.
If it worked for you just press the Thanks button.
Click to expand...
Click to collapse
You can add that on pcs with usb 2.0 ports, fastboot works without changing usb config.
Happy to help.
Far_SighT said:
You can add that on pcs with usb 2.0 ports, fastboot works without changing usb config.
Happy to help.
Click to expand...
Click to collapse
This guide is for those their laptop or pc doesn't have USB 2.0 ports.Just like my ASUS N550JV
Got it to work, but in a different way, but using the available drivers from this post..
Just pointing to the folder didn't work because I had to make it work with fastboot..
To fix that I just hit the right mouse button on "androidusb.INF", selected install, booted the phone as fastboot via "adb reboot bootloader", windows recognized the new device and now I have fastboot working fine..
Anyway, thanks for your Win8 driver.. it did the trick..
Edit:
FYI, the HTC One didn't work on my Series 8 Intel mobo with Win8/8.1 because of the "extensible usb driver" but it's now working without having to do that impossible plugable tutorial.. So, yes, this tutorial fixes several issues with several HTC phones on Windows 8... It's not restricted to "doesn't have USB 2.0 ports"...
Related
Hi Guys,
Most of us may know this method, but thought of putting it on the forum anyways.
Requirements:
1. You will need a Virtual PC for this method, either VMWare Workstation or MS Virtual PC. If you don't know how to use/setup Virtual PC, google it.
2. We will flash the Wizard by putting it in the bootloader mode.
Procedure:
1. Setup a Windows XP Virtual PC and start it.
2. Backup your phone.
3. Remove Memory and Sim card.
4. Remove phone battery and wait for 10-15 seconds.
5. Insert battery.
6. Press the power button for only a second.
7. Hold the camera button until you see the 3 band colored (red, green and blue) screen with the IPS/SPL info.
8. Connect the Wizard to your computer.
9. Windows 7/Vista (which is the primary/main Operating System) will add drivers, you may or may not get a message.
10. In the Virtual PC, goto the menu where you can connect/disconnect removable devices.
11. Here the Wizard will be listed as a USB device, you can identify it easily.
12. From here on you can flash the ROM, i recommend you follow the procedure listed in the "How to flash a new ROM to your Wizard... a little tutorial!" thread 298613.
Note: You may experience issues with this method. It is recommended to keep a copy of Virtual PC seperate.
1. Sometimes the flash progress may be stuck at 0%.
2. Shutdown the WinXP Virtual PC and try again.
3. It the Virtual PC doesn't starts, delete this Virtual PC file and use the backup (create a copy of the Virtual PC file first).
Happy Flashing.
Disclaimer: Info provided in good faith, I am not responsible for any damage/loss of any kind that you may experience following this procedure.
Your method is way too complicated. I flashed my wizard from windows 7 using this guide: http://forum.xda-developers.com/showthread.php?t=485293
Thanks
Thanks for the link, the RUU was able to flash the Hornet 5 ROM (thread 416636)perfectly, but it could not flash the RUU_TMobile_US_226102_22610105_022511_WWE_Ship, I got "file not found" error.
I wish there was a universal Windows 7/Vista compatible RUU for Wizard.
You are making it too hard! Download the Vista drivers I am uploading-its for Windows 64 bit. Restart your computer while holding down f8. Turn off digital signing of drivers. Put your Wizard in bootloader mode and connect to pc. Open (from the Start Menu) CONTROL PANEL>HARDWARE AND SOUND>DEVICE MANAGER. Find your ppc in the listed menu. Hit update driver. Just go through the menus hitting next until you get to an option where you hit "HAVE DISK". Hit browse, find where you have it on your computer and install. SEARCH IS YOUR FRIEND, TRY IT, USE IT, LOVE IT.
[Q] USB BOS descriptor failed, "waiting for device", "Device cannot start. (Code 10)"
Hello
The situation:
I'm trying to relock the bootloader and flash RUU, so that I can get rid of the tampered flag and start over.
I'm trying to use Hasoon2000's Toolkit to do this, but I'll try any method that sounds reasonable.
When I connect the HTC One S to the PC (running Windows 8) and select 'Mount as disk drive', the PC recognizes the device, and I can explore it. Using Hasoon's toolkit I select "Relock Bootloader" and click "Do Command". A first command prompt pops up, then my phone goes into fastboot, then I close the first prompt, then a second prompt follows and says "waiting for device".
I enter the Device Manager -> "Android USB Devices" -> "My HTC", -> Right click -> "Properties". In the Device Status field it says:
"This device cannot start. (Code 10) A request for the USB BOS descriptor failed."
EXTRA INFO:
I didn't use Hasoon's toolkit to unlock the bootloader, I actually used the platform-tools from the SKD bundle thru the terminal on a mac pc. Then I flashed CWM onto the One S using "./fastboot flash recovery recovery_thefilename.zip". Then I reloaded bootloader, selected Recovery, then my phone's screen went black, turned back on, and I saw the Red Triangle with the Exclamation mark. According to a "How to" blog, which I didn't read until after the fact, I was supposed to hold down the power button and volume button at that point in time, but I didn't. I had no idea what was going on. I pressed the power button and my phone restarted, and now every time I reboot to recovery mode, it just restarts the phone and says "This build is for development purposes only. Any redistribution will result in legal action." or something like that.
OK THAT'S ALL.
I appreciate any help!
jire
The text in red is normal if you have a custom recovery.
Just get the device in fastboot USB mode.
Check with command: fastboot devices
To see if it is connected. I should return you sn number.
(Since you manually unlocked, this should be easy for u.)
Then manually flash a correct recovery (or use the toolkit with the custom option). Reboot in recovery. Flash ROM.
Verstuurd van mijn One S met Tapatalk
Can you try to execute fastboot oem lock command on Windows OS which have hTC drivers installed? I guess that you using Linux OS now... Just install Windows in VM and hTC drivers, adb and fastboot you can download on htcdev.com or from android bundle package... I'm pretty sure that you have problem with your drivers...
Sent from quietly brilliant HTC One S
USB 3.0 might be the issue
Hey guys, thanks for trying to help me out here, I appreciate it a bunch!
Before I go any further. I think I've learned what the problem is. Well, first of all, if you didn't catch it, I've been working thru this on both win and apple computers.
Hasoon's toolkit is only available for windows. Therefore, if I said/say I did something with his toolkit, that means I was using my win computer, which is actually a Surface Pro, which has USB 3.0 === THE PROBLEM
According to this: http://forum.xda-developers.com/showthread.php?p=29286429
Unfortunately, I haven't been able to test this hypothesis, yet, because I first need to find a win pc with USB 2.0. [Fact: I couldn't get androidfiletransfer.app to recognize my htc one S on my mac. Coincidence?]
real187: When you say to install a "correct" recovery, are you implying I currently have an incorrect recovery on my phone?
mikronac: I have virtually no experience with command prompt. I just got my Surface Pro last week :laugh: and I'm geeking out...So, what I'm saying is I don't know how to do "fastboot oem lock command" ... The htc drivers are installed, up-to-date and operating without a hitch.
It can't be problematic your usb 3.0.
Please deinstall your phone drivers and install them again...
If you know how to navigate to platform tools folder in Windows Explorer, only what you need to do is to hold shift key on keyboard and right click on mouse and select option open command prompt here. Than you type :
Adb devices
Response should be serial number of phone
Adb reboot bootloader (uab debugging must be enabled)
When it reboot in fastboot, type in cmd:
Fastboot oem lock
Sent from quietly brilliant HTC One S
I can confirm: It is USB 3.0
Hi, today I faced similar problem while trying to put my Sony Xperia S into fastboot. Only after finding this topic and switching from USB3.0 port to USB 2.0 did I manage to boot into fastboot. I have not tested, if I can boot into fastboot now, that the driver has been correctly installed via USB 2.0, but to avoid any troubles I suggest everyone to stick with USB2.0 for now.
I found this topic as I had the exact same error in Device Manager as OP in this topic.
maatriks said:
Hi, today I faced similar problem while trying to put my Sony Xperia S into fastboot. Only after finding this topic and switching from USB3.0 port to USB 2.0 did I manage to boot into fastboot. I have not tested, if I can boot into fastboot now, that the driver has been correctly installed via USB 2.0, but to avoid any troubles I suggest everyone to stick with USB2.0 for now.
I found this topic as I had the exact same error in Device Manager as OP in this topic.
Click to expand...
Click to collapse
Thanks for this bro I tried usb 2.0 and it worked. I searched many tuturial how to access fastboot in my Win8 but no luck many thanks for this.
No USB 2.0
Aciong.Aksaya said:
Thanks for this bro I tried usb 2.0 and it worked. I searched many tuturial how to access fastboot in my Win8 but no luck many thanks for this.
Click to expand...
Click to collapse
Hi,
I don't have USB 2.0 in my laptop.
Could you please help me how to proceed with USB 3.0?
Thanks in advance
dsuresh89 said:
Hi,
I don't have USB 2.0 in my laptop.
Could you please help me how to proceed with USB 3.0?
Thanks in advance
Click to expand...
Click to collapse
Problem solved with USB 3.0.
uninstall your 3.0 USB xtensible host controller driver provided by microsoft and install driver from INTEL.
Enjoy...
dsuresh89 said:
Problem solved with USB 3.0.
uninstall your 3.0 USB xtensible host controller driver provided by microsoft and install driver from INTEL.
Enjoy...
Click to expand...
Click to collapse
hey
there is no driver for 3.0 USB xtensible host controller for windows 8
and I already have a usb 2 but I have the same problem
I think that it came from windows 8
Thanks in advance
Unable to fastboot in Windows 8.1
Aciong.Aksaya said:
Thanks for this bro I tried usb 2.0 and it worked. I searched many tuturial how to access fastboot in my Win8 but no luck many thanks for this.
Click to expand...
Click to collapse
Hey Bro,
I am facing the same issue. Unfortunately I don't have a USB 2.0 port in my computer. Im struggling to flash the boot file.
Please help
jire0006 said:
Hello
When I connect the HTC One S to the PC (running Windows 8) and select 'Mount as disk drive', the PC recognizes the device, and I can explore it. Using Hasoon's toolkit I select "Relock Bootloader" and click "Do Command". A first command prompt pops up, then my phone goes into fastboot, then I close the first prompt, then a second prompt follows and says "waiting for device".
I enter the Device Manager -> "Android USB Devices" -> "My HTC", -> Right click -> "Properties". In the Device Status field it says:
"This device cannot start. (Code 10) A request for the USB BOS descriptor failed."
jire
Click to expand...
Click to collapse
I know it has been a long time but I just encountered the same problem with fastboot, an HTC One S and Windows 8.1. These steps from Microsoft (a registry edit workaround) enabled my computer to recognize the device and got fastboot seeing it too:
http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx
I'll paste the workaround here in case Microsoft take the page down:
To apply the workaround for a specific device, add a REG_DWORD value named SkipBOSDescriptorQuery that has a value of 1 to the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\usbflags\vvvvpppprrrr
(where vvvv is the device's Vendor ID, pppp is the device's Product ID, and rrrr is the device's Revision number. You can get the VID/PID/REV numbers from the device manager's details tab. This number is encoded in the HardwareIDs of the device)
1. Click Start, click Run, type regedit in the Open box, and then click OK .
2. Locate and then click the following subkey in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\UsbFlags
3. On the Edit menu, point to New, and then click Key.
4.Type the name of the new key in the following form:
vvvvpppprrrr
where
vvvv is a 4-digit hexadecimal number that identifies the vendor (idDevice from the USB Deviceescriptor),
pppp is a 4-digit hexadecimal number that identifies the product (idVendor from the USB Device Descriptor)
rrrr is a 4-digit binary-coded decimal number that contains the revision number of the device
(bcdDevice from the USB Device Descriptor).
5. On the Edit menu, point to New, and then click DWORD (32-bit) Value.
6. Type SkipBOSDescriptorQuery for the name of the DWORD Value, and then press ENTER.
7. Right-click SkipBOSDescriptorQuery, and then click Modify.
8. In the Value data box, type 1 , and then click OK.
9. Exit Registry Editor.
10. Unplug and re-plug the device for the workaround to take effect.
Click to expand...
Click to collapse
On mine that meant editing a registry key called 0BB40FF00100 that already existed.
windows 8 have a issue with ville fastboot... please make you sure you have a fix
zoodles said:
I know it has been a long time but I just encountered the same problem with fastboot, an HTC One S and Windows 8.1. These steps from Microsoft (a registry edit workaround) enabled my computer to recognize the device and got fastboot seeing it too:
http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx
I'll paste the workaround here in case Microsoft take the page down:
On mine that meant editing a registry key called 0BB40FF00100 that already existed.
Click to expand...
Click to collapse
THANK YOU SO MUCH. Fixed for me on HTC Magic
..
Problem is caused by Windows 8 and Windows 10. Just no compatibility for old hardware.. I'm disappointed from Microsoft Windows.
---------- Post added at 10:41 PM ---------- Previous post was at 10:17 PM ----------
Problem is caused by Windows 8 and Windows 10. Just no compatibility for old hardware.. I'm disappointed from Microsoft Windows. Btw, I tried all methods in forums and in YouTube too (updating USB Root Hub drivers). Nothing helps, just "Failed device enumeration". Windows 10.. I will go back to Win7, fortunately I don't have license for 10.. Pray about these who has...
Bruh, this worked like magic on my HTC One X+ !!!
Using Windows 10 Enterprise Build 17134 by the way
Thanks a lot!
Thank you very much bro. HTC One V good working.
Hey there XDA. As you all know there is a problem with fastboot on Windows 8.1. There is a fix for people with Intel machines with USB 3.0 but your out of luck if you have AMD (like me). Luckily, I started searching the AMD website and found NON-Microsoft AMD USB 3.0 drivers that work with Windows 8.1 x64 (At least with my PC). So hopefully with a bit of editing from developers (I'm not one), that fastboot will be working on AMD USB 3.0 machines.
To install
1. Disable Driver Signature Enforcement. Tutorial here
2. Download amdxhc.inf
3. Press Windows key + R and type in devmgmt.msc
4. Expand Universal Serial Bus Controllers and right-click on where it says USB 3.0
5. Click Update Driver Software and click Browse My Computer for Driver Software
6. Click Let Me Pick from a List of Device Drivers on My Computer and select Have Disk
7. On the pop up window click Browse and find the file you downloaded (amdxhc.inf) and double-click on it
8. Press OK, click on AMD USB 3.0 Host Controller and click Next
9. Let it install and you are done
Hope this helps in any way
dd98 said:
Hey there XDA. As you all know there is a problem with fastboot on Windows 8.1. There is a fix for people with Intel machines with USB 3.0 but your out of luck if you have AMD (like me). Luckily, I started searching the AMD website and found NON-Microsoft AMD USB 3.0 drivers that work with Windows 8.1 x64 (At least with my PC). So hopefully with a bit of editing from developers (I'm not one), that fastboot will be working on AMD USB 3.0 machines.
To install
1. Disable Driver Signature Enforcement. Tutorial here
2. Download amdxhc.inf
3. Press Windows key + R and type in devmgmt.msc
4. Expand Universal Serial Bus Controllers and right-click on where it says USB 3.0
5. Click Update Driver Software and click Browse My Computer for Driver Software
6. Click Let Me Pick from a List of Device Drivers on My Computer and select Have Disk
7. On the pop up window click Browse and find the file you downloaded (amdxhc.inf) and double-click on it
8. Press OK, click on AMD USB 3.0 Host Controller and click Next
9. Let it install and you are done
Hope this helps in any way
Click to expand...
Click to collapse
your link to amdxhc.inf is locked or requires your auth for use.
I'm installing http://support.amd.com/en-us/download/chipset?os=Windows 7 which should include this same driver. I'll report back for anyone who wants the info
Hi all first off I'm sorry if this has been posted before but I'm having a problem unbricking an Asus transformer tf101 B60, I'll start with what's going on or not for that matter. lol
1. Boot to recovery is CWM-Based Recovery v5.5.0.4 roach-tf101-r2
2. will not see sd card / backup-restore= -2014-04-05.02.52.56 / no files found
3. Choose a zip = e: can't open /sdcard/update.zip
4.PC windows 7 pro 64 bit will not see the tablet when plugged into usb getting unrecognized device,force driver still getting yellow ding=device cannot start
if I plug in the usb and turn on the tablet windows does not even see that and unit sits on logo screen. and other screen the cold lynx boot that hangs there.
So in short I'm hitting a brick wall, windows won't see it, it won't see the SD card in recovery mode.
I've read in these posts how to fix this problem and have all the software / firmware you name it, but they all say almost the same thing, windows needs to see the device in order for any of these fixes to work, and thus is my wall I'm hitting.
Any help to find a solution to this problem would be oh so thankful to you all and call you Tablet Gods, this was a tablet given to me as a paper weight and I thought if it boots it can be fixed?
Thanks for your time and God like tablet knowledge.
Cheers.
Install the APX drivers (Universal Naked Drivers) and use the tool "Easyflasher" to flash TWRP recovery (Forget CWM) both from this link
http://forum.xda-developers.com/showthread.php?t=1688012
You might need to install the APX drivers manually using Device Manager
If you find that the PC still does not see the TF101, you might need a new cable
Driver Not Working
*Detection* said:
Install the APX drivers (Universal Naked Drivers) and use the tool "Easyflasher" to flash TWRP recovery (Forget CWM) both from this link
http://forum.xda-developers.com/showthread.php?t=1688012
You might need to install the APX drivers manually using Device Manager
If you find that the PC still does not see the TF101, you might need a new cable
Click to expand...
Click to collapse
I booted the unit into recover mode and windows sees unknown device..Ok
Tried to install new naked driver and getting a splash saying not compatible with windows 64 bit, I tried this on a brand new windows 7 pro 32 bit laptop and got the same results. I do have a brand new usb cable for it thinking that the old one was faulty, tried adb again same thing no device found, are there any commands in terminal emulator that can force the driver on the usb port? I'm thinking that if windows sees an unknown device then at least it sees something there just not whats there? Am i wrong in that somehow it's lost the usb firmware connection? so the driver will not install and if forced does not make the connection to the device? So this is my results.
So I'm ready to put gun in mouth over this, my laptops going to divorce me over driver abuse and the tablet mocks me with the frozen Asus logo.
Again Thanks for all the advice and i'll keep slugging it out.As this unit is in perfect condition outside of the Bricked part
You don't need to boot it into recovery mode to start with, just install the drivers normally first with the TF101 connected and booted normally
It's always going to say it can't find the device if the driver isn't installed
Focus on getting that APX driver installed and working, once you have that installed, Im pretty sure it will see the device fine
Asus TF101 B60 Softbrick? What Now?
Hello all.
I've been searching in vain for an answer to my Bricked Asus tf101? I'm just going to get right to the problem.
I can't get the tablet to be seen by windows 7 pro 64bit, Unknown device and yes I've tried everything, except asking if there's a way to force connection through a terminal like I've seen done with a router and a network switch to force a flash file so as to get at least a response after a reboot instead of just the Asus splash screen, here's a summary.
The Good.
1. I can boot to recovery CWM-based recovery v5.5.0.4 roach-tf101-r2 with menu's
Bad: Does not see sd card only see's internal and there's no file or folder error for backup/restore
2.Boots to screen with 2 icons data wipe and linix cold boot and goes nowhere from there just hangs.
So I'm stuck here, I have all to tools to do the job only if windows would see it, Adb does not see device which means the same thing no driver no fix,
Everywhere I read it says do this and that and it will restore to factory, that would be great if windows saw the thing, so I'm looking for a way to get the tablet to boot to something other than a loop. also tried the put the E101_SDUPDATE.zip in the root of the SD card and restart, does not see the card or file or both so it's not loading the file?
1. windows 7 not seeing device, will not take force drivers, Universal-Nvidia-Asus- MTP
2. recovery does not see sd card, so can't flash new anything?
3. So no communication from SD/USB
4. Is there a terminal command I can use to force a Blob or flash a recovery to the tablet when drivers and USB don't respond?
And to top that off my laptop filed for divorce for driver abuse..lol I'm not giving up.
Thanks to you all,
I want to thank you all for your time and advice it is very much appreciated, and I'll keep slugging away because I know there's a fix out there.
Cheers.
Drivers need to be signed in 64bit windows, use 32bit Win 7 either on another machine or in VMWare or Virtualbox etc
Then the drivers should install
Thanks
*Detection* said:
Drivers need to be signed in 64bit windows, use 32bit Win 7 either on another machine or in VMWare or Virtualbox etc
Then the drivers should install
Click to expand...
Click to collapse
Thanks for the Advice, Is there a thread outlining this so I can give it a try? I do have a new laptop I'm building out with windows 7 Pro 32bit as I've had so much trouble with the 64bit version.
If you're building a 32bit Win 7 laptop, then no need for virtual machines, just use that laptop, this is the Easyflasher thread, you should only need to follow the couple of simple instructions once you have 32bit Win 7 running
http://forum.xda-developers.com/showthread.php?t=1688012
Basically in a nutshell:
1) Plug in TF101 to PC and make sure ADB debugging is enabled in Dev options on TF
2) Drivers will/should fail to install
3) Open Device manager
4) Right click the ! missing driver
5) Update driver > Point to extracted Universal Naked Drivers from Easyflasher thread
6) Drivers should install
7) Leave TF plugged into PC
8) Power TF off
9) Hold Volume Up & Power until the PC sounds the USB connect sound
10) TF is now in APX mode (Nothing on TF screen yet) drivers should install, check Device Manager, if it doesn't install, point it to the extracted Universal drivers folder again until they are installed
11) Follow instructions to use Easyflasher
12) Done
*Detection* said:
If you're building a 32bit Win 7 laptop, then no need for virtual machines, just use that laptop, this is the Easyflasher thread, you should only need to follow the couple of simple instructions once you have 32bit Win 7 running
http://forum.xda-developers.com/showthread.php?t=1688012
Basically in a nutshell:
1) Plug in TF101 to PC and make sure ADB debugging is enabled in Dev options on TF
2) Drivers will/should fail to install
3) Open Device manager
4) Right click the ! missing driver
5) Update driver > Point to extracted Universal Naked Drivers from Easyflasher thread
6) Drivers should install
7) Leave TF plugged into PC
8) Power TF off
9) Hold Volume Up & Power until the PC sounds the USB connect sound
10) TF is now in APX mode (Nothing on TF screen yet) drivers should install, check Device Manager, if it doesn't install, point it to the extracted Universal drivers folder again until they are installed
11) Follow instructions to use Easyflasher
12) Done
Click to expand...
Click to collapse
I am trying to get mine out of the reboot loop and cant seem to get it into APX mode to install the drivers.....any idea how go from here and have been trying step 9 above.
Will keep on trying to see if I can get it to work
Sicknote said:
I am trying to get mine out of the reboot loop and cant seem to get it into APX mode to install the drivers.....any idea how go from here and have been trying step 9 above.
Will keep on trying to see if I can get it to work
Click to expand...
Click to collapse
Need more info
What happens when you try to enter APX mode?
Which OS are you running on the PC?
Do the APX drivers install ?
etc etc etc
*Detection* said:
Need more info
What happens when you try to enter APX mode?
Which OS are you running on the PC?
Do the APX drivers install ?
etc etc etc
Click to expand...
Click to collapse
When i try to put it in APX mode, the screen goes black but pc does not see it. I have tried this bit lots of times and not sure if I'm missing something...
Have the drivers in a folder on my desk top. Have watched videos on YouTube but what i see is not happening when i try it...
OS is windows 7.
Drivers don't install.
Sicknote said:
When i try to put it in APX mode, the screen goes black but pc does not see it. I have tried this bit lots of times and not sure if I'm missing something...
Have the drivers in a folder on my desk top. Have watched videos on YouTube but what i see is not happening when i try it...
OS is windows 7.
Drivers don't install.
Click to expand...
Click to collapse
You're not going to be able to put the tablet into APX mode till you get the drivers installed correctly.
With the tablet connected to the computer and the tablet on, download the naked driver package. open up device manager and right click on Other Devices - APX and chose update driver. Chose browse and then go to where you downloaded the naked driver package. If it complains that they aren't signed, click install anyway. If successful, you should now be able to put your tablet in APX mode.
Hey there people,
I can't find a solution for this one, so here I am!
I want to transfer files from my computer on Windows 11 to my original Pixel, but I can't find a way to install drivers for it:
Automatic driver install does not work
Google USB drivers aren't compatible with it according to the device manager
Google drivers from the full list of Windows drivers don't work either
The phone is detected as 4 Pixels in the device manager, as well as a disk which isn't readable and returns nothing in the disk management service of Windows.
Any tip will be really greatly appreciated!
Thanks in advance to you all
BTW I tried the usual fixes: original cable, other USB port, reboot, changing the USB management setting to PTP/MTP… nothing works.
follow these instructions brother. The fix for me was to put the phone in fastboot mode before trying to install the Google drivers. You do that by issueing the command "adb.exe reboot bootloader",