Missing USB driver "Cherry Trail Tablet" while on bootloader - Lenovo Yoga Book Questions & Answers
Hello everyone ! First post here.
I've bought yesterday this amazing machine, and bought the Android version. But I wished to directly install a Windows 10 version to replace Android, but I didn't thought it would be this... complicated. >.<
In order to have access to boot menu (then boot on a Windows 10 install USB drive), it seems we have to root Android.
That's what I'm doing. But I'm stuck with a stupid driver...
I've followed the steps from thread https://forum.xda-developers.com/yoga-book/how-to/root-yb1-x90l-how-to-t3534268, and got to install ADB and reboot to the bootloader. But once at the "fastboot flashing unlock" step, the command waits for the device.
In the device manager, the Yoga Book driver is installed if plugged while turned on normally (thus ADB sees it), however it is missing while on bootloader (thus Fastboot can't see it) - the manager recognizes it as "Cherry Trail Tablet" with a warning sign over it.
Once I'll get to install the missing driver, I'll get to keep going.
Does anyone know what exactly to download and install to fix this ?
P.S. : I tried the common Google "usb_driver", but it is not recognized as a correct driver directory.
Totjoss said:
Hello everyone ! First post here.
I've bought yesterday this amazing machine, and bought the Android version. But I wished to directly install a Windows 10 version to replace Android, but I didn't thought it would be this... complicated. >.<
In order to have access to boot menu (then boot on a Windows 10 install USB drive), it seems we have to root Android.
That's what I'm doing. But I'm stuck with a stupid driver...
I've followed the steps from thread https://forum.xda-developers.com/yoga-book/how-to/root-yb1-x90l-how-to-t3534268, and got to install ADB and reboot to the bootloader. But once at the "fastboot flashing unlock" step, the command waits for the device.
In the device manager, the Yoga Book driver is installed if plugged while turned on normally (thus ADB sees it), however it is missing while on bootloader (thus Fastboot can't see it) - the manager recognizes it as "Cherry Trail Tablet" with a warning sign over it.
Once I'll get to install the missing driver, I'll get to keep going.
Does anyone know what exactly to download and install to fix this ?
P.S. : I tried the common Google "usb_driver", but it is not recognized as a correct driver directory.
Click to expand...
Click to collapse
For me windows didn't recognise the Yoga in bootloader mode automatically. I had to install the adb driver manually. Just use the android composite adb driver. Worked like a charm. Used this package as posted earlier: https://forum.xda-developers.com/showthread.php?t=2588979
vogemic said:
For me windows didn't recognise the Yoga in bootloader mode automatically. I had to install the adb driver manually. Just use the android composite adb driver. Worked like a charm. Used this package as posted earlier: https://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Indeed, it works like a charm. Thank you very much !
Totjoss said:
Hello everyone ! First post here.
I've bought yesterday this amazing machine, and bought the Android version. But I wished to directly install a Windows 10 version to replace Android, but I didn't thought it would be this... complicated. >.<
In order to have access to boot menu (then boot on a Windows 10 install USB drive), it seems we have to root Android.
That's what I'm doing. But I'm stuck with a stupid driver...
I've followed the steps from thread https://forum.xda-developers.com/yoga-book/how-to/root-yb1-x90l-how-to-t3534268, and got to install ADB and reboot to the bootloader. But once at the "fastboot flashing unlock" step, the command waits for the device.
In the device manager, the Yoga Book driver is installed if plugged while turned on normally (thus ADB sees it), however it is missing while on bootloader (thus Fastboot can't see it) - the manager recognizes it as "Cherry Trail Tablet" with a warning sign over it.
Once I'll get to install the missing driver, I'll get to keep going.
Does anyone know what exactly to download and install to fix this ?
P.S. : I tried the common Google "usb_driver", but it is not recognized as a correct driver directory.
Click to expand...
Click to collapse
I can't find the way to unlock the bootloader as my laptop (using Windows 10) does NOT recognize my Yoga Book in Fastboot Mode. I've tried everything (or so) to get it but I couldn't. I have reinstalled ADB and Fastboot several times and restarted my laptop but nothing works... When I type "Fastboot devices" nothing happens and of course when I type "Fastboot flashing unlock" it keeps waiting for the device.
Any other possible solution? I'm feeling quite frustrated. I know this would be much easier running Ubuntu as I've done it before but I haven't got any laptop (I borrowed this one)
I know the answer is a bit late, @alvarogr91, but since I had the same problem, yesterday, I think it's worth answering nonetheless:
You need to follow the instructions of the howto_driver.zip that is located in the ADB/Fastboot thread that already got mentioned in post #2 of the Q&A thread we're currently writing in. Although I had to choose Lenovo ADB Device instead of Android Device on the Select your device's type from the list below screen, the Yoga Book got recognized without any issues, in the end.
no encuentro Lenovo ADB Device
Flippy498 said:
I know the answer is a bit late, @alvarogr91, but since I had the same problem, yesterday, I think it's worth answering nonetheless:
You need to follow the instructions of the howto_driver.zip that is located in the ADB/Fastboot thread that already got mentioned in post #2 of the Q&A thread we're currently writing in. Although I had to choose Lenovo ADB Device instead of Android Device on the Select your device's type from the list below screen, the Yoga Book got recognized without any issues, in the end.
Click to expand...
Click to collapse
hola, hice lo que dijiste pero a la hora de actualizar en controlador no pude encontrar android device y mucho menos lenovo ADB device, tambien busque con otros nombres pero no hay nada, alguna ayuda con esto, gracias
Lo siento mucho pero no tengo ninguna idea porque no puedes ver tu yoga book.
Por favor no olvide que este sitio de web utiliza la lengua ingles. Por eso necesitas escribir en ingles. Si no sabes hablar ingles puedes utilizar google para traducir. Puedes postar la mensaje original en este caso, tambien.
I'm sorry but I have no clue why you can't see your yoga book.
Please don't forget that this is an English website. Therefore, you need to write in English. If you don't speak english you can use Google for translating. You're allowed to post the original message, too, in that case.
Sent from my HTC One M9 using XDA Labs
a possible solution
Well, for future people who have the same problem, a fairly simple solution that worked for me after trying with everything is to install Lenovo_suite
For anyone having this problem, you need these drivers: https://software.intel.com/content/...les/intel-usb-driver-for-android-devices.html
maicol07 said:
For anyone having this problem, you need these drivers: https://software.intel.com/content/...les/intel-usb-driver-for-android-devices.html
Click to expand...
Click to collapse
This did and didn't work for me. After installing this I am now able to confirm communication with the yb and am able to use ADB to restart to the bootloader...but same as the original post, I get the, "waiting for the device" prompt when actually trying to unlock the bootloader. Any ideas on where I messed up?
P.S. I'm running ADB from my lenovo Yoga 910 laptop running Win 10 Pro. Connecting to the YB using USB-A to Micro USB cord. I do have a USB-A/Micro-USB thumb drive I can connect directly to the YB as needed.
Unconquerable1 said:
This did and didn't work for me. After installing this I am now able to confirm communication with the yb and am able to use ADB to restart to the bootloader...but same as the original post, I get the, "waiting for the device" prompt when actually trying to unlock the bootloader. Any ideas on where I messed up?
P.S. I'm running ADB from my lenovo Yoga 910 laptop running Win 10 Pro. Connecting to the YB using USB-A to Micro USB cord. I do have a USB-A/Micro-USB thumb drive I can connect directly to the YB as needed.
Click to expand...
Click to collapse
Update: Eventual Success. Windows says that it has installed this Intel driver and it is a signed driver...Apparently Windows was lying. I restarted using boot options and disabled the requirement for driver signing. I then selected update driver from device manager and select the intel driver and Windows warned me it wasn't a signed driver. I confirmed I wanted to install it...Now Fastboot works and my yb bootloader is unlocked.
Related
Rooting my Tab 10.1 LE running 3.1
Hello... I would have preferred to have posted this to one of the existing threads in the development forum but apparently new accounts are not permitted to do so. Anyways, I've had a hell of a time rooting my I/O edition tab because I had updated it to 3.1. I'm pretty sure from reading through other threads that there are people having the same issues so I would like to share my experience in hope that it will help others. So, like I mentioned above, the biggest (only) problem with rooting my tab was that I was unable to boot into recovery mode. Nothing at all worked - adb, fastboot, etc. I was sure I had all my drivers installed correctly but when I ran "adb reboot recovery" I ended up at the battery screen - this is apparently due to the 3.1 update. When I ran "fastboot boot someimg.img" it hung with the "waiting for devices" message. This was indicative of a fastboot driver issue so I reinstalled the driver a few times, then tried an older version of the fastboot executable, then tried a different machine... all to no avail. Then I stumbled upon mention of a fastboot driver included with PdaNet. It was a bit of a pain to get Windows to install the new driver but I eventually got it to work. First I downloaded and installed PdaNet and said yes to replace all of my existing Android drivers. I then tried updating the fastboot driver through device manager but it wouldn't let me, it just kept saying the most current driver was installed. So I uninstalled the existing fastboot driver through device manager (also checked the box to delete the driver software, just so that it didn't install the same driver again) and then unplugged/replugged in the Tab (in fastboot mode) to reinstall the driver. The actual driver that it ended up installing was an ADB driver which I found a bit odd (the earlier one was "Nvidia fastboot" or something), but lo and behold running "fastboot devices" showed my tab and I was able to run "fastboot boot" on the CWM image and from there it was a snap (following instructions from http://forum.xda-developers.com/showthread.php?t=1130574). PdaNet - http://www.junefabrics.com/android/ Hope this experience is helpful to someone else having problems rooting their Tab!
this is why everyone should have a linux box.
Usb device not recognized for samsung galaxy y pro duos
Please i need your help. My PC keeps telling me 'USB device not recognized', anytime i connect my phone(Samsung Galaxy Y Pro Duos, GT-B5512) to my PC through the USB cable. This way i can't use the Samsung KIES on my PC because the KIES doesn't detect the phone. The PC and the KIES used to detect the phone before and that's not possible now. I want to root my phone but i can't do that with this situation. Please kindly proffer solutions. thank you.
USB shosky said: Please i need your help. My PC keeps telling me 'USB device not recognized', anytime i connect my phone(Samsung Galaxy Y Pro Duos, GT-B5512) to my PC through the USB cable. This way i can't use the Samsung KIES on my PC because the KIES doesn't detect the phone. The PC and the KIES used to detect the phone before and that's not possible now. I want to root my phone but i can't do that with this situation. Please kindly proffer solutions. thank you. Click to expand... Click to collapse Por favor verifique as portas USB do seu PC, veja no gerenciador de dispositivos, o aplicativo easy drive pode ajudar na correção.
Google usbdeview.exe un install all moto drivers reboot computer. Plug phone in let computer reload all the drivers. http://www.nirsoft.net/utils/usb_devices_view.html ——— Screwed by Google. Canceled ICS upgrade on my Moto Photon. No Wow for us.
Need help - OP 6t not recognized in fastboot
Hello, a few weeks ago i got my OP 6t. Due to my positive experience from my previous phones (LG G3 and G5) and what i heard from OP i tried to flash twrp and planned to install magisk. I followed the instructions here on xda to unlock the bootloader, it got recognized as device in adb and i could reboot it into the bootloader, but then it didnt recognized it in fastboot, it looks like im missing some sort of drivers, because when im in fastboot in the win 10 device manager its called "android" with a yellow triangle, i tried multiple guides already, but i had no success. Its the unbranded version with 8 gigs and 128 gig. I can provide more info if needed. Help would be very appreciated.
Did you follow funkwizard's guide in the guides/news/discussion forum? It's stickied at the top. Anyhow, if you followed the guide, he provides this link (https://drive.google.com/file/d/1L7EZGx5mgeQYXO19Vsp9FWu9GXhF45Qs/view?usp=drivesdk) for the OP6T drivers that need it be installed. He then provides this link (https://drive.google.com/file/d/1-uWQn-oHu_ROuDVCzIyrExoRbsSBYTtU/view?usp=drivesdk) to update your ADB/fastboot to the latest version. Complete both of those steps and your phone SHOULD be recognized in fastboot. Good luck.
I have read his complete thread and im still stuck with the same problem. I deinstalled all phone related driver and only installed the one from the thread, opened the command prompt via admin and under device manager is still the yellow triangle beside the android device. I tried to install the driver manually via the google universal driver, but windows never found any compatible drivers.
And just to be certain, do you have USB Debugging enabled in developer options?
Pain-N-Panic said: And just to be certain, do you have USB Debugging enabled in developer options? Click to expand... Click to collapse Yupp, but i have to say that i had to tap it four to five times until the confirmation window popped up.
I had this problem few hours ago, and this is W10 fault. For me solution was that: instal drivers from guide, enter fastboot mode, remove phone from device manager and unistal drivers, replug phone, let windows find drivers automaticly when in fastboot mode. And that's it, fasboot comands works now.
Bartuc666 said: I had this problem few hours ago, and this is W10 fault. For me solution was that: instal drivers from guide, enter fastboot mode, remove phone from device manager and unistal drivers, replug phone, let windows find drivers automaticly when in fastboot mode. And that's it, fasboot comands works now. Click to expand... Click to collapse Thanks for the try, but still no change.
lubal21 said: Thanks for the try, but still no change. Click to expand... Click to collapse forget all the other tips, install the Google USB drivers with the batch file by entering Y on every question. select install driver in the device manager by selecting manually install. in the list presented select on the left Google Inc and on the right the fastboot driver. finish setup and fastboot should work now
lubal21 said: Hello, a few weeks ago i got my OP 6t. Due to my positive experience from my previous phones (LG G3 and G5) and what i heard from OP i tried to flash twrp and planned to install magisk. I followed the instructions here on xda to unlock the bootloader, it got recognized as device in adb and i could reboot it into the bootloader, but then it didnt recognized it in fastboot, it looks like im missing some sort of drivers, because when im in fastboot in the win 10 device manager its called "android" with a yellow triangle, i tried multiple guides already, but i had no success. Its the unbranded version with 8 gigs and 128 gig. I can provide more info if needed. Help would be very appreciated. Click to expand... Click to collapse Probably this shall help: How to Fix OnePlus Device not showing in Fastboot Mode In this detailed guide, we will show you the steps to fix the OnePlus Device not showing in the Fastboot Mode on Windows 10 PC. www.droidwin.com
Fastboot Not Recognized
I am not able to get Fastboot to reconginze my One Plus 6T. I have reinstalled the drivers numerous times to no avail. I have changed ports to no avail. I have change USB cables to no avail. Is anyone else having a similar problem and if so, any solution? BTW, I am using a Windows 10 computer. Also, I was able to install the International Version on my TMO variant One Plus 6T via the MSM tool method, so the drivers appear to be installed correctly. Thank you in advance for any assistance.
phaino00 said: I am not able to get Fastboot to reconginze my One Plus 6T. I have reinstalled the drivers numerous times to no avail. I have changed ports to no avail. I have change USB cables to no avail. Is anyone else having a similar problem and if so, any solution? BTW, I am using a Windows 10 computer. Also, I was able to install the International Version on my TMO variant One Plus 6T via the MSM tool method, so the drivers appear to be installed correctly. Thank you in advance for any assistance. Click to expand... Click to collapse Delete the drivers you have installed, boot into fastboot and have Windows automatically detect and install for you. Have you tried that? What source did you get your fastboot drivers from?
phaino00 said: I am not able to get Fastboot to reconginze my One Plus 6T. I have reinstalled the drivers numerous times to no avail. I have changed ports to no avail. I have change USB cables to no avail. Is anyone else having a similar problem and if so, any solution? BTW, I am using a Windows 10 computer. Also, I was able to install the International Version on my TMO variant One Plus 6T via the MSM tool method, so the drivers appear to be installed correctly. Thank you in advance for any assistance. Click to expand... Click to collapse Msmdownload drivers are not the same at all, they are Qualcom drivers. Uninstall your fastboot drivers and let windows install them
phaino00 said: I am not able to get Fastboot to reconginze my One Plus 6T. I have reinstalled the drivers numerous times to no avail. I have changed ports to no avail. I have change USB cables to no avail. Is anyone else having a similar problem and if so, any solution? BTW, I am using a Windows 10 computer. Also, I was able to install the International Version on my TMO variant One Plus 6T via the MSM tool method, so the drivers appear to be installed correctly. Thank you in advance for any assistance. Click to expand... Click to collapse Oh man, I had issues getting my 6t to connect to my PC when I first got my 6t. The answer for me was to plug my phone into a USB 2.0 port on the BACK of my PC instead of the front USB ports my PC has. Try using the back USB ports and let me know if that works for you!
Thank you all. I will try these suggestions later today and report back.
I tried the suggestions and still no success in fastboot connecting with my device. Thanks again for the suggestions.
After trying to multiple times reinstall the drivers, manually selecting "Android Bootloader Interface" did the trick for me on win10: wtfandroid.com/fix-fastboot-device-not-recognised-problem/
Issue resolved. Selected Android Bootloader Interface in Device Manager and fastboot recognized my device. Unlocked Bootloader, installed TWRP and Magisk. Root achieved. Thank you all!!!
jullev said: After trying to multiple times reinstall the drivers, manually selecting "Android Bootloader Interface" did the trick for me on win10: wtfandroid.com/fix-fastboot-device-not-recognised-problem/ Click to expand... Click to collapse Thank you! I can't believe I didn't think to check that.
it is solved for me oneplus 6t not recognized in fastboot { solved for me } hello brother, i got this problem also my head was about to explosing, install/uninstall drivers and adb drivers also, without any success, when the device is on normal mod the adb terminal can recognize it and in fastboot mod not recognize my devie (the list empty). i was trying to install TWRP, so i have reboot my device to fastboot mod, and i didn't think about List of devices (because it not show my device) i wrote the comand to install TWRP directly so it success to install 100%, so no need to write : adb devices when your device is in fastboot mod, it will not show you in the list, but you can apply what you want normally good luck
hichemkanon said: { solved for me } hello brother, i got this problem also my head was about to explosing, install/uninstall drivers and adb drivers also, without any success, when the device is on normal mod the adb terminal can recognize it and in fastboot mod not recognize my devie (the list empty). i was trying to install TWRP, so i have reboot my device to fastboot mod, and i didn't think about List of devices (because it not show my device) i wrote the comand to install TWRP directly so it success to install 100%, so no need to write : adb devices when your device is in fastboot mod, it will not show you in the list, but you can apply what you want normally good luck Click to expand... Click to collapse Hello. I am having the same issues. But can you provide more steps on how to install TWRP. Can you provide the command/steps used to directly install TWRP? Thank you.
phaino00 said: Issue resolved. Selected Android Bootloader Interface in Device Manager and fastboot recognized my device. Unlocked Bootloader, installed TWRP and Magisk. Root achieved. Thank you all!!! Click to expand... Click to collapse Did this and still not able to recognize it in fastboot mode
sonice43 said: Hello. I am having the same issues. But can you provide more steps on how to install TWRP. Can you provide the command/steps used to directly install TWRP? Click to expand... Click to collapse Rijul30 said: Did this and still not able to recognize it in fastboot mode Click to expand... Click to collapse This is why I use Linux in my LOS Install Guide. You can boot Linux from a USB without installing it. Fastboot and ADB just work, without any drivers. Install TWRP, reboot and your PC will be back to windows. My guide covers installing TWRP.
Really need help. I'm going in circles and wasting a lot of time: I'm attempting to root a OP6T A6013. Its already been unlocked. My device is recognized when powered up as an ADB device. But when i boot into the bootloader it isnt recognized as a fastboot device, and my laptop (Win 8.1) shows ""device malfunctioned. USB not recognized". I've also been trying to install the OP driver but I'm not sure its working correctly. But would that cause the problem with recognizing fastboot? I've root my OP7Pro (twice, actually) and though I had some driver issues then eventually figured it out. But I never had issues with fastboot. Any tips or direction?
Hey all , replying to share my solution to this exact problem I was having.. My OP6T (T-Mobile converted to international) was not showing in fastboot devices but showed in ADB.. after hours of searching google and XDA , I ended up just plugging my 6T into another computer and it worked! , instantly recognized my device without hassle. So just a fyi, it could be something simple as switching USB ports or even another computer. hopefully this helps if someone get's stuck at this point.
I had this issue with a OP8Pro... I went to Windows Update and selected View Optional Updates and found Android Bootloader Device on the list. I selected this to download, and then fastboot worked perfectly.
OhioYJ said: This is why I use Linux in my LOS Install Guide. You can boot Linux from a USB without installing it. Fastboot and ADB just work, without any drivers. Install TWRP, reboot and your PC will be back to windows. My guide covers installing TWRP. Click to expand... Click to collapse sudo fastboot oem unlock worked in linux in first shot while windows was unable to recognize the device. Thanks a ton. EDIT : Just to add .. this linux was in VM
OhioYJ said: This is why I use Linux in my LOS Install Guide. You can boot Linux from a USB without installing it. Fastboot and ADB just work, without any drivers. Install TWRP, reboot and your PC will be back to windows. My guide covers installing TWRP. Click to expand... Click to collapse I agree. Linux is far better when flashing android phones
anonymoustl said: I had this issue with a OP8Pro... I went to Windows Update and selected View Optional Updates and found Android Bootloader Device on the list. I selected this to download, and then fastboot worked perfectly. Click to expand... Click to collapse This worked for my OnePlus 9 Pro running Windows 10. Happy modding!
[Answered] Oneplus 8 Pro ReLock Bootloader
Q : so I'm trying to relock my bootloader since I can't run some of my banking apps, I followe this link. the problem is when the phone is in fastboot mode, my pc can't detect my device, and I've tried with some cables and still nothing. can someone please help me? thanks A : Somehow my pc's fastboot driver is not working, so I decided to use my laptop and it works
B1nz said: Q : so I'm trying to relock my bootloader since I can't run some of my banking apps, I followe this link. the problem is when the phone is in fastboot mode, my pc can't detect my device, and I've tried with some cables and still nothing. can someone please help me? thanks A : Somehow my pc's fastboot driver is not working, so I decided to use my laptop and it works Click to expand... Click to collapse Hi there is some guides how to get this driver installed on Xda. If your computer can see adb then you will be okay. When you plug in you'll see a one plus box pop up and you click on that and hit install. Then under device manager you can manually select the driver under c:/ programfiles or (something like that) just to give you the idea. You might have to turn on unsigned drivers in windows (command+reboot) to install the driver, but I just wanted to let you know mostly everyone has been through this ( and so no surprise), and there is a guide on Xda that can do a much better job explaining what to do.