Related
Hello everyone, I'm using Redmi Note 3 and I have tried rooting it several times.
I have unlocked the bootloader. I have also installed the adb drivers.
When I connect phone in fastboot mode and write 'fastboot devices' in cmd it doesn't return anything. But when I connect when its on, adb devices returns the device code.
Please help.
Same, happens to mine too. Used to work with a previous install of windows, but now, nope.
Had this issue too.
Try going to Device Manager and check to see if Kedacom USB Device shows up. Under which, Android Bootloader Interface should be present. Install minimalist ADB and fastboot and right click Android Bootloader Interface. Click Update Driver Software, browse computer, and then click the option to list driver files already present on your drive. It should pull up a fastboot driver that's an older version than the one you currently have. Install that and fastboot will work again.
Doesn't work
Can you please link the files for download when we're updating the driver software.
Hi guys,
Urgent help needed.
I got fedup from last 4 days trying to Unlock bootloader of my Redmi Note 3 Snapdragon (Kenzo). While unlocking bootloader getting error at 50% "Couldn't verify device (Not connected to Mi Phone)". Earlier I never faced this issue as Not connected to Mi Phone.
In August 2016, 1st time I unlocked bootloader officially. And after that more than 10 times I unlocked bootloader of my RN3.
From last 15 days I was using CM13.0, But 4 days ago I flashed Miui 8.0.1.0 via Edl method (Flash all selected), then tried to Unlock bootloader. Got the error "Couldn't verify device (Not connected to Mi Phone)"
Then flashed Miui 8.0.5.0 via Edl method (because unable to unlock bootloader). While unlocking bootloader, got the same error "Couldn't verify device (Not connected to Mi Phone)"
Tools / drivers installed on my Pc:
Mi flash 01.04.2016(64bit)
MiSetup3.2.1.3111_2717 (Mi PC Suite)
Adb driver adb-setup-1.4.3
& Already reinstalled the Adb driver adb-setup-1.4.3
Already searched on MI forum, couln't find any proper answer.
When I ran the same fastboot command (fastboot devices) on Zenfone 5 connected to Pc, it immediately shows Listed device.
But In fastboot mode, when I ran the command "fastboot devices" it shows nothing. [on my Redmi Note 3]
When I ran command "fastboot oem device-info" to check bootloader status, it shows Waiting for device.
Tried every possible way I know, but no success.
Kindly help me in this regard.
Thanks in advance.
Faruque007 said:
Hi guys,
Urgent help needed.
I got fedup from last 4 days trying to Unlock bootloader of my Redmi Note 3 Snapdragon (Kenzo). While unlocking bootloader getting error at 50% "Couldn't verify device (Not connected to Mi Phone)". Earlier I never faced this issue as Not connected to Mi Phone.
In August 2016, 1st time I unlocked bootloader officially. And after that more than 10 times I unlocked bootloader of my RN3.
From last 15 days I was using CM13.0, But 4 days ago I flashed Miui 8.0.1.0 via Edl method (Flash all selected), then tried to Unlock bootloader. Got the error "Couldn't verify device (Not connected to Mi Phone)"
Then flashed Miui 8.0.5.0 via Edl method (because unable to unlock bootloader). While unlocking bootloader, got the same error "Couldn't verify device (Not connected to Mi Phone)"
Tools / drivers installed on my Pc:
Mi flash 01.04.2016(64bit)
MiSetup3.2.1.3111_2717 (Mi PC Suite)
Adb driver adb-setup-1.4.3
& Already reinstalled the Adb driver adb-setup-1.4.3
Already searched on MI forum, couln't find any proper answer.
When I ran the same fastboot command (fastboot devices) on Zenfone 5 connected to Pc, it immediately shows Listed device.
But In fastboot mode, when I ran the command "fastboot devices" it shows nothing. [on my Redmi Note 3]
When I ran command "fastboot oem device-info" to check bootloader status, it shows Waiting for device.
Tried every possible way I know, but no success.
Kindly help me in this regard.
Thanks in advance.
Click to expand...
Click to collapse
Most probably your device is not recognized as a fastboot device.... please ensure that fastboot drivers for your kenzo are installed and not corrupted and if it does not help try on some other PC and don't forget to disable drive signature enforcement
Sent from my Redmi Note 3 using Tapatalk
Resolved
Torshak.mozyora said:
Most probably your device is not recognized as a fastboot device.... please ensure that fastboot drivers for your kenzo are installed and not corrupted and if it does not help try on some other PC and don't forget to disable drive signature enforcement
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
Hi,
Thanks for your helpful reply
Finally unlocked bootloader succesfully. The problem is with adb drivers on my Windows 10 64bit Pc. Earlier I had done with unlocking several times, never faced driver issue on fastboot mode. But from last 4-5 days suddenly my RN3 was not responding to any fastboot commands.
Followed this:
In Device Manager under Kedacom USB Device shows up. Under which, Android Bootloader Interface should be present. Installed minimalist ADB and fastboot (minimal_adb_fastboot_v1.3.1_setup) and right clicked Android Bootloader Interface. Clicked Update Driver Software, browsed computer, and then clicked the option to list driver files already present on my drive. It pulled up a fastboot driver that's an older version than the one I currently have. Installed that and fastboot commands started working again.
Hope this help other users also, who are facing (Not connected to Mi Phone) or Waiting for device when initiate fastboot command like "fastboot oem device-info".
Please close this thread.
Thanks
Faruque007 said:
Hi,
Thanks for your helpful reply
Finally unlocked bootloader succesfully. The problem is with adb drivers on my Windows 10 64bit Pc. Earlier I had done with unlocking several times, never faced driver issue on fastboot mode. But from last 4-5 days suddenly my RN3 was not responding to any fastboot commands.
Followed this:
In Device Manager under Kedacom USB Device shows up. Under which, Android Bootloader Interface should be present. Installed minimalist ADB and fastboot (minimal_adb_fastboot_v1.3.1_setup) and right clicked Android Bootloader Interface. Clicked Update Driver Software, browsed computer, and then clicked the option to list driver files already present on my drive. It pulled up a fastboot driver that's an older version than the one I currently have. Installed that and fastboot commands started working again.
Hope this help other users also, who are facing (Not connected to Mi Phone) or Waiting for device when initiate fastboot command like "fastboot oem device-info".
Please close this thread.
Thanks
Click to expand...
Click to collapse
THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU
Thank you a million times, you allowed me to finally unlock my bootloader. I love you, and I hope you and your children live long and fulfilling lives.
Faruque007 said:
Hi,
Thanks for your helpful reply
Finally unlocked bootloader succesfully. The problem is with adb drivers on my Windows 10 64bit Pc. Earlier I had done with unlocking several times, never faced driver issue on fastboot mode. But from last 4-5 days suddenly my RN3 was not responding to any fastboot commands.
Followed this:
In Device Manager under Kedacom USB Device shows up. Under which, Android Bootloader Interface should be present. Installed minimalist ADB and fastboot (minimal_adb_fastboot_v1.3.1_setup) and right clicked Android Bootloader Interface. Clicked Update Driver Software, browsed computer, and then clicked the option to list driver files already present on my drive. It pulled up a fastboot driver that's an older version than the one I currently have. Installed that and fastboot commands started working again.
Hope this help other users also, who are facing (Not connected to Mi Phone) or Waiting for device when initiate fastboot command like "fastboot oem device-info".
Please close this thread.
Thanks
Click to expand...
Click to collapse
Dude you are my hero, Thank you soo much...
privateriem said:
THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU
Thank you a million times, you allowed me to finally unlock my bootloader. I love you, and I hope you and your children live long and fulfilling lives.
Click to expand...
Click to collapse
Welcome bro
I'm glad and super happy, my method helped you. Enjoy.
Faruque007 said:
Hi,
Thanks for your helpful reply
Finally unlocked bootloader succesfully. The problem is with adb drivers on my Windows 10 64bit Pc. Earlier I had done with unlocking several times, never faced driver issue on fastboot mode. But from last 4-5 days suddenly my RN3 was not responding to any fastboot commands.
Followed this:
In Device Manager under Kedacom USB Device shows up. Under which, Android Bootloader Interface should be present. Installed minimalist ADB and fastboot (minimal_adb_fastboot_v1.3.1_setup) and right clicked Android Bootloader Interface. Clicked Update Driver Software, browsed computer, and then clicked the option to list driver files already present on my drive. It pulled up a fastboot driver that's an older version than the one I currently have. Installed that and fastboot commands started working again.
Hope this help other users also, who are facing (Not connected to Mi Phone) or Waiting for device when initiate fastboot command like "fastboot oem device-info".
Please close this thread.
Thanks
Click to expand...
Click to collapse
Thanks for your help dude finally unlocked and rooted my device
tried all methods but this unlock button remains inactive. please help
Hello,
I have just bought a oneplus 7t Pro
I would like to root it but first I need to unlock it.
But impossible to get it detected in fastboot while it works with adb (it finds my device).
I have installed the driver from the attached "cd" repertory, nevertheless the devices manager shows an "android" device which is not correctly installed.
I tried to install the driver manually by slecting it in the oneplus folder in program files, but it says that the driver "OnePlus android bootloader interface" cannot be installed as the hash file is missing.
anyone can help?
Thanks
get the fastboot driver from google. easy to find, then unzip it and select it when installing drivers for oneplus fastboot in device manager.
so yea get either the google fastboot driver or the OEM drivers found there too
DeeZZ_NuuZZ said:
get the fastboot driver from google. easy to find, then unzip it and select it when installing drivers for oneplus fastboot in device manager.
so yea get either the google fastboot driver or the OEM drivers found there too
Click to expand...
Click to collapse
Hello,
This what I tried and it worked! Using generic driver instead of ... weird. Anyway now everything is fine.
Thanks.
I have the following devices installed ( I enabled show hidden devices ) .
Although my phone still wont be recognized after a qualcomm crash dump
can anyone pls help with how to root the Lenovo TB-x306f
i already unlocked the bootloader but that's as far as i was able to go with it.
i want to also like to install a recovery to flash the evolutionx rom if someone can pls help me and others that needs the same help.
GOD BLESS
I second that. There's nothing out there.
What I tried was to download the original ROM patch the boot.img with magical, replace in LMSA download folder and start a rescue. Didn't help. Got boot loop.
Ok, maybe a bit more details on what I tried already:
1. Enabled developer options. Good.
2. OEM unlocked. ADB connected. Good.
3. Boot to bootloader working. Good.
4. fastboot not listing the device after fastboot devices. Not good.
5. Googling around, found an universal root method with Magisk. Good.
6. Donwloaded, installed and ran RSA (Lenovo Rescue and Smart Assistant). Connected to device. Good.
7. Entered Rescue and using that downloaded the original ROM. Good.
C:\ProgramData\LMSA\Download\RomFiles\TB_X306F_S100134_210120_BMP
8. Copied boot.img to device, installed MagiskManager, patched image with magisk, downloaded the image to PC, replaced the original boot image with the patched one. Good.
9. Started the Rescue procedure in RSA. Rom flased. Good.
10. Bootloop. Bad.
No idea why would that not work, any help, pointers, ideas appreciated.
EDIT: There's a new ROM version now: TB_X306F_S100152_210205_BMP
For a preface, I have the same Tablet as OP. I tried to unlock the bootloader, following seemingly every guide out there but, no success so far. I've enabled debugging, activated OEM unlock and, adb detects my device but, after I send it to fastboot (adb reboot bootloader), no more commands work. I've updated the driver in Manager as one guide suggested but, still nothing.
I used command (fastboot OEM unlock) to continue but nothing. What am I doing wrong?
So just a tip for those that are looking for a guide to do a complete bootloader unlock for TB-X306F, there isn't one. I found a bunch of different ways to go about unlocking the bootloader from different Lenovo devices. First thing is that you need Minimal ABD Fastboot v1.4.3 if Platform Tools or LeTools doesn't work. Use CMD with admin rights, not PowerShell.
Everything else to unlock it is the same from all the guides out there. Make sure to use "fastboot flashing unlock" when unlocking instead of "fastboot oem unlock" or "fastboot oem unlock-go" if they dont work.
Second tip is for root when installing the Magisk patched boot image. While you're getting the boot.img, make sure to also grab the vbmeta.img from the ROM folder and place it in the Minimal ADB Fastboot folder where you will be using CMD. Do all the steps to get the patched boot image. Once you got the boot.img patched, enter fastboot then enter the command "fastboot --disable-verification flash vbmeta vbmeta.img" This will disable verification needed to boot correctly. After that, enter the command "fastboot flash boot <name of .img>" like normal to flash the patched boot.img from magisk. Then fastboot reboot.
This is what I did to get my TB-X306F unlocked and rooted. YMMV.
Different threads that I read to get to where I got, credit goes to them:
LENOVO Tab M10 Plus
After receiving my LENOVO Tab M10 Plus TB-X606F I tried to root my tablet. my Firmware version is TB-X606F_RF01_200103 - loaded the Lenovo Rescue and Smart Assistant (V5.0.0.25) - enabled OEM unlock - downloaded magisk - installed ADB now my...
forum.xda-developers.com
Lenovo M10 HD 2nd Gen X306F boot loop if boot.img is patched - android 10 · Issue #3832 · topjohnwu/Magisk
I recently installed magisk manager and extracted the boot.img from tb-x306f_rf01_200926 upon doing a fastboot flash boot magisk_patched.img , the machine goes into a boot loop. Am I doing somethin...
github.com
TWRP for LENOVO Tab M10 FHD - TB-X606F?
Hello, Possessing two tablets of this brand, I was wondering if a custom recovery existed for this one, I can look everywhere on all the forums, Russian, English, etc ... But, I do not find. If anyone can create one with this SOURCE CODE from...
forum.xda-developers.com
Lenovo tab m8
Hello, Any root and custom ROM available for the Lenovo tab m8 tb8505 variant? The stock rom feels good for the price but if something better to make the tab feel nicer.. Thanks :) :)
forum.xda-developers.com
By any chance can u pls.... Make a video on the steps u explained including on where to get that file needed. Pls thank u and GOD BLESS YOU. If u can find the time to do it .
I apologize for asking for so much help on this.
I too would very much care to see a video of the process but, I have no problem trying it first hand to myself. This tablet is just weird. It can be detected but, as soon as I boot into fastboot, it can't pick it up anymore even though, I had grabbed all of the recommended tools so far such as the fast Boot and the bundle.
A detailed guide would be good enough too
Following @doink_doink 's post (and some bootloops after...) I finally managed to root my Lenovo M10 HD 2 gen (TB-X306X) with magisk. I'll attempt to write a simple guide for who's still interested with rooting this kind of devices since there's not much literature online.
Rooting Lenovo M10 X306X (should also work for other models)
I am by no means held responsible for eventual damage you can inflict on your device, follow the underlying steps of your own accord.
Desktop Tools:
Minimal ADB and Fastboot
Lenovo Rescue Smart Assistant (LRSA from now on)
MTK (Mediatek) Preload Drivers (If your device isn't listed in fastboot)
Mobile Tools:
Magisk Manager App
Steps:
1 - From LRSA click on "Rescue" Tab
2 - Select the model of your tablet and then download
3 - From "Downloads" in the top right corner of the LRSA, click on "Open" to go into the LRSA download folder
4 - Connect your device and set it into USB Debugging and File Transfer
5 - Copy boot.img from LRSA download folder into the device's download folder
6 - Run Magisk Manager App on your device
7 - From Magisk Manager App choose "Install" on the right side of Magisk
8 - Choose the only option "Select and patch a file"
9 - Choose the boot.img you previously copied into the device's download folder
10 - Copy the new file "patched_boot.img" or similar name to the folder where Minimal ADB and Fastboot was installed
11 - Copy the file vbmeta.img from LRSA download folder to Minimal ADB and Fastboot folder
12 - From your device's settings enable developer options and enable OEM Unlock
13 - Execute a cmd session with administrator privileges
14 - Execute in the cmd: adb reboot bootloader (if everything went right the device should reboot in fastboot mode)
15 - Execute in the cmd: fastboot flashing unlock
16 - Execute in the cmd: fastboot --disable-verification flash vbmeta vbmeta.img
17 - Execute in the cmd: fastboot flash boot patched_boot.img
18 - Execute in the cmd: fastboot reboot
The device should correctly reboot and everything should be good to go now.
If something bad happens, like a bootloop or something, turn off the device and use the LRSA to rescue your device.
I don't get around to checking my email as often as I used to so I just now got around to seeing this but, I will try this after I get home from work in 10 hours plus time. If I can get this to successfully work, I will be flat out amazed. I had gotten to the point where I had just given up any and all hope that I would get it to work.
Show
Chairos said:
Following @doink_doink 's post (and some bootloops after...) I finally managed to root my Lenovo M10 HD 2 gen (TB-X306X) with magisk. I'll attempt to write a simple guide for who's still interested with rooting this kind of devices since there's not much literature online.
Rooting Lenovo M10 X306X (should also work for other models)
I am by no means held responsible for eventual damage you can inflict on your device, follow the underlying steps of your own accord.
Desktop Tools:
Minimal ADB and Fastboot
Lenovo Rescue Smart Assistant (LRSA from now on)
MTK (Mediatek) Preload Drivers (If your device isn't listed in fastboot)
Mobile Tools:
Magisk Manager App
Steps:
1 - From LRSA click on "Rescue" Tab
2 - Select the model of your tablet and then download
3 - From "Downloads" in the top right corner of the LRSA, click on "Open" to go into the LRSA download folder
4 - Connect your device and set it into USB Debugging and File Transfer
5 - Copy boot.img from LRSA download folder into the device's download folder
6 - Run Magisk Manager App on your device
7 - From Magisk Manager App choose "Install" on the right side of Magisk
8 - Choose the only option "Select and patch a file"
9 - Choose the boot.img you previously copied into the device's download folder
10 - Copy the new file "patched_boot.img" or similar name to the folder where Minimal ADB and Fastboot was installed
11 - Copy the file vbmeta.img from LRSA download folder to Minimal ADB and Fastboot folder
12 - From your device's settings enable developer options and enable OEM Unlock
13 - Execute a cmd session with administrator privileges
14 - Execute in the cmd: adb reboot bootloader (if everything went right the device should reboot in fastboot mode)
15 - Execute in the cmd: fastboot flashing unlock
16 - Execute in the cmd: fastboot --disable-verification flash vbmeta vbmeta.img
17 - Execute in the cmd: fastboot flash boot patched_boot.img
18 - Execute in the cmd: fastboot reboot
The device should correctly reboot and everything should be good to go now.
If something bad happens, like a bootloop or something, turn off the device and use the LRSA to rescue your device.
Click to expand...
Click to collapse
Hi I have the same device I have my patched boot.img and vbmeta.img but when I adb reboot bootloader fastboot commands don't work anymore fastboot flashing unlock says <waiting for device> and every other command. I have latest fastboot drivers google USB drivers I've done everything I have no hope please reply and help me
Hello231 said:
Show
Hi I have the same device I have my patched boot.img and vbmeta.img but when I adb reboot bootloader fastboot commands don't work anymore fastboot flashing unlock says <waiting for device> and every other command. I have latest fastboot drivers google USB drivers I've done everything I have no hope please reply and help me
Click to expand...
Click to collapse
* I have the TB-X306F***
Hello231 said:
Show
Hi I have the same device I have my patched boot.img and vbmeta.img but when I adb reboot bootloader fastboot commands don't work anymore fastboot flashing unlock says <waiting for device> and every other command. I have latest fastboot drivers google USB drivers I've done everything I have no hope please reply and help me
Click to expand...
Click to collapse
I'm currently experiencing the same issue. I have done everything, followed every step provided by Chairos and it wont surpass beyond the <Waiting for device> message. I just got this device today for a fair price, hoping I could root the device, and typical me forgot to research if it was officially compatible with TWRP.
cratee said:
I'm currently experiencing the same issue. I have done everything, followed every step provided by Chairos and it wont surpass beyond the <Waiting for device> message. I just got this device today for a fair price, hoping I could root the device, and typical me forgot to research if it was officially compatible with TWRP.
Click to expand...
Click to collapse
I got it for free for online classes but that's not the problem twrp is out for this device unofficialy but many say that it works, anyways good luck on u mate I gave up on rooting this device I can't do it anymore I've been trying for 4 months but nothing still if I had the Chance and the correct guide I would definitely do it
cratee said:
I'm currently experiencing the same issue. I have done everything, followed every step provided by Chairos and it wont surpass beyond the <Waiting for device> message. I just got this device today for a fair price, hoping I could root the device, and typical me forgot to research if it was officially compatible with TWRP.
Click to expand...
Click to collapse
Make sure you have the latest MTK usb drivers.
Hello Everyone,
I apologize for the delay but I didn't get notified of your replies.
I also got the waiting for device problem, but as @Yahoo Mike says, it's the MTK USB drivers that are used to communicate with the device in fastboot mode. Latest drivers should do.
Let me know if you're still experiencing the problem after installing the latest MTK drivers, since it depends on which motherboard the tablet has but all models should use mediatek.
Worked like a charm! Thanks.
Can anyone please confirm if there is a TWRP even unofficial IMG out there? And if any kind soul could share the file too I would be so grateful thanks
worked beautifully ...
just the installation of the latest MTK drivers is not very typical. however, you can follow this guide to install MTKL drivers and disable the driver signature enforcement
Download MTK USB Drivers for Windows 11, 10 - Driver Easy
To flash files to your MediaTek chipset phones, you need to have the latest MediaTek drivers installed. We'll show you how to install the MTK driver easily.
www.drivereasy.com
When you Restart: go to Advanced Options to find the Driver Signature Disablement option
I received yesterday my TB-X306X, with Android 10 and with software version S100184_210325_BMP. First thing to do was to unlock and root the tablet, without any issue, thanks to clear indications found on this thread.
Has anybody been able to find working TWRP for this tablet ?
I've been trying to unlock the bootloader in my phone (OnePlus7T Pro).
I can't see my phone when booted into fasboot mode or recovery mode (I can see the phone while normally working).
The command: fastboot devices shows no device. The same with adb devices command.
I think I need a proper driver for the device. I've already tried UniversalAdbDriverSetup.msi, but with no success.
I use PC with Ryzen processor and Win10.
Could you suggest a solution, please?
The UniversalAdbDriverSetup you referred to is not of any use. You instead have to install the Android USB Driver suitable to your phone:
Download OnePlus USB Driver for Windows (Latest Driver)
Download the latest and original OnePlus USB Driver to connect your OnePlus Smartphone to the Windows Computer quickly and easily.
androidmtk.com
kamien8 said:
I use PC with Ryzen processor and Win10.
Could you suggest a solution, please?
Click to expand...
Click to collapse
This might help...
[FIX] Fastboot issues on Ryzen based PCs
AMD has been known for it's notorious fastboot issues in the custom ROM community, especially with Xiaomi devices. I was trying to unlock the bootloader of my Redmi Note 5 Pro the other day and I encountered with an issue where Mi Unlock Tool...
forum.xda-developers.com
Thanks for information.
I can see the device when it is up and running. Still nothing when it is in FB mode, however I can see the Widnows sound of a connected device.
jwoegerbauer said:
The UniversalAdbDriverSetup you referred to is not of any use. You instead have to install the Android USB Driver suitable to your phone:
Download OnePlus USB Driver for Windows (Latest Driver)
Download the latest and original OnePlus USB Driver to connect your OnePlus Smartphone to the Windows Computer quickly and easily.
androidmtk.com
Click to expand...
Click to collapse
I uninstalled the previous drivers and installed the right one from the link. I also have used your version of adb and fastboot.
CXZa said:
This might help...
[FIX] Fastboot issues on Ryzen based PCs
AMD has been known for it's notorious fastboot issues in the custom ROM community, especially with Xiaomi devices. I was trying to unlock the bootloader of my Redmi Note 5 Pro the other day and I encountered with an issue where Mi Unlock Tool...
forum.xda-developers.com
Click to expand...
Click to collapse
Yes, I've heard about the fix. Run it, but still nothing happened.
Maybe I have to find somebody with Intel processor.
Because your phone's Android is version 10 try this
Code:
adb reboot fastboot
fastboot reboot fastboot
fastboot devices
....
jwoegerbauer said:
Because your phone's Android is version 10 try this
Code:
adb reboot fastboot
fastboot reboot fastboot
fastboot devices
....
Click to expand...
Click to collapse
Hi, I'm half way.
I checked on Intel proc, and I can see bootloaded phone in fastboot. ADB still can't see the device.
I was trying to re-install drivers, but no changes.
Unfortunately I need working ADB as I have to sideload an image.
I've since years a laptop powered by AMD Ryzen 5 in use: Fastboot always works like a hell. Hence I'm pretty sure that it doesn't matter whether Fastboot is run on an Intel or AMD powered computer.
If ADB isn't working as expected my guess is that "USB debugging" didn't get enabled on phone and phone didn't get re-booted afterwards.
USB debugging is enabled. When the phone is started normally, ADB works fine (for example I can use adb reboot bootloader command)
I thought, maybe there is a mess with the drivers in the device. Can it cause the issue?
So to confirm, this is the only one drivers package I need to run OnePlus (7T Pro) in bootloader and use fastboot and adb commands?
OnePlus 7T Pro USB Driver for Windows
Download the latest OnePlus 7T Pro Driver for Windows Computer. You can use the latest OnePlus Driver to connect OnePlus Device to the Computer.
oneplusdriver.com
Command
Code:
adb reboot bootloader
since Android 10 is incorrect: I've already told you this in a previous post.
jwoegerbauer said:
Command
Code:
adb reboot bootloader
since Android 10 is incorrect: I've already told you this in a previous post.
Click to expand...
Click to collapse
Yes, you're right.
adb reboot bootloader command works. Once I am in bootloader I still can connect phone via adb but fastboot doesn't work. That was my question, if the highlightet drivers are the only one I need.
Is it possible, that there is something wrong with the phone?
If ADB successfully connects to phone then your phone isn't booted into its bootloader, but into Android OS.