So I just got my phone today and I was trying to root it (with magisk boot patch) but after using the unlock app and enabling USB debugging fastboot still wasn't showing the device.
There was no option in the developer settings for OEM unlock..
I don't know if it is a bug or am I just missing something, is there anyone who can help me ?
Did you connect to wifi or mobile networks?, you need to be online
NisseGurra said:
Did you connect to wifi or mobile networks?, you need to be online
Click to expand...
Click to collapse
Yes of course otherwise the app won't unlock
*Is it ok for there to be no OEM unlcok option in the developers settings ?
danielbr14 said:
Yes of course otherwise the app won't unlock
Click to expand...
Click to collapse
Unlocked, rebooted, full wiped and add network again?
NisseGurra said:
Unlocked, rebooted, full wiped and add network again?
Click to expand...
Click to collapse
Yes, when I boot it clearly states that the bootloader is unlocked yet I don't have the OEM unlock option in the developers settings..
But if the bootloader are unlocked why you need the oem toggle?, Did you try to flash magic?
NisseGurra said:
But if the bootloader are unlocked why you need the oem toggle?, Did you try to flash magic?
Click to expand...
Click to collapse
Because the device still doesn't show up on fastboot (it does on ADB)
{
"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"
}
Did you try "fastboot devices"?
windows driver correct?
NisseGurra said:
Did you try "fastboot devices"?
windows driver correct?
Click to expand...
Click to collapse
No I tried to install everything that this guide says to, but the phone still shows up with an incorrect driver
Try the google drivers
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
NisseGurra said:
Try the google drivers
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
Click to expand...
Click to collapse
I tried it but When I point it to the driver it says it can't find a driver for my device
danielbr14 said:
I tried it but When I point it to the driver it says it can't find a driver for my device View attachment 5681607
Click to expand...
Click to collapse
And if you try to install it from device manager?
NisseGurra said:
And if you try to install it from device manager?
Click to expand...
Click to collapse
That's what I did, is there a way to install it without the device manager?
danielbr14 said:
That's what I did, is there a way to install it without the device manager?
Click to expand...
Click to collapse
I would delete all installed drivers for Zenfone 9, reboot, change usb-port and install googles drivers.
But as this more an windows issue its difficult to assist remote
NisseGurra said:
I would delete all installed drivers for Zenfone 9, reboot, change usb-port and install googles drivers.
But as this more an windows issue its difficult to assist remote
Click to expand...
Click to collapse
I already tried it, and to be honest I don't think it is something that I am doing. adb detects the phone is both when it isbooted and when it is in the bootloader. Its only during fastboot that windows shows a missing driver the device...
The OEM Unlock toggle is usually unavailable (grayed out) when the bootloader is unlocked. It's possible this is the reason why it doesn't show up.
As for being unable to issue fastboot commands, it sounds to me like a driver issue, like others have stated.
OK, Finally managed to track down the correct driver thanks to this post and download this driver
FYI for anyone who encounters the same issue just open device manager and right click on your unrecgonized device (needs to be already in fastboot mode) the click update and select the driver from the zip file you just downloaded according to your PC then just finish installing it and everything should work.
danielbr14 said:
View attachment 5681497
No I tried to install everything that this guide says to, but the phone still shows up with an incorrect driver
Click to expand...
Click to collapse
Check windows update then optional update. There will be an Asus ADB driver to install.
danielbr14 said:
OK, Finally managed to track down the correct driver thanks to this post and download this driver
FYI for anyone who encounters the same issue just open device manager and right click on your unrecgonized device (needs to be already in fastboot mode) the click update and select the driver from the zip file you just downloaded according to your PC then just finish installing it and everything should work.
Click to expand...
Click to collapse
Just the answer I was looking for. Thank you for sharing!
Quite counter-intuitive that the trcick is to install Win8 drivers for Win10, but presumably they are the same but should have been downloaded automatically in Win10.
mickey36736 said:
Check windows update then optional update. There will be an Asus ADB driver to install.
Click to expand...
Click to collapse
Hopefully this is an option for most people, but, for the record, this did not work for me.
Windows 10 had a bunch of suggestions there but none of them were from Asus.
Perhaps it's glitched and they are in an invisible overflow - my optional driver section has exactly 10 entries. no more and no less, which I find a little suspicious.
Related
I've tried everything. IT WILL NOT recognize my phone.
When trying to install the drivers it says the Authenticode does not have permission. I got the damn drivers directly from Android.com but it still doesn't think its authentic. Because of this, o cannot get the computer to recognize it as an adb device to root the phone.
I'm going nuts now. 2 days with literally 8 to 10 hours of trying with no success.
Can someone please please PLEASE help me?
I was having the same issue. Install PDAnet. Works like a charm. The program installs the drivers for you. You can uninstall the program after you get the drivers working if you'd like.
http://www.junefabrics.com/android/
rk0 said:
I was having the same issue. Install PDAnet. Works like a charm. The program installs the drivers for you. You can uninstall the program after you get the drivers working if you'd like.
http://www.junefabrics.com/android/
Click to expand...
Click to collapse
Didn't work.
During "installing drivers" it gave me this error (err=0xe000023f).
uoY_redruM said:
Didn't work.
During "installing drivers" it gave me this error (err=0xe000023f).
Click to expand...
Click to collapse
http://www.junefabrics.com/android/driver.php
Tried USBDeview, doesn't seem to let me uninstall anything even though it says you can.
Nothing appears to work.
This is what I keep getting, no matter what I do:
{
"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"
}
and what makes no sense is when trying to manually install new hardware, it SHOWS there are authenticodes for those drivers:
theres a way of turning off driver signature checks, try that
http://www.google.com/search?q=windows+7+disable+driver+signature
Are you on Vista or a Windows server version?
I had the same issue, turned out it was a hardware bug.
I sent it to the repair center at HTC in United Kingdom and i had it returned 5-6 days after, working and with locked bootloader
britoso said:
theres a way of turning off driver signature checks, try that
http://www.google.com/search?q=windows+7+disable+driver+signature
Are you on Vista or a Windows server version?
Click to expand...
Click to collapse
Vista.
I've tried a few of those suggestions and non of worked. Most involved the bcedit trick but its disabled or doesn't exist in the newer security updates.
Vista 32 bits or Vista 64bits ?
in hardware management console what do you see ? yellow question mark ?
Sometimes you need to go in it and find your device to check the HID number and copy it manually in the driver *..inf files to be detect by your OS.
I remembered doing this for my G1 long time ago (years).
If you can, get your hands on another n1 or android device to see if its a hardware problem with the phone, which i doubt. Also try a diff OS.
uoY_redruM said:
I've tried everything. IT WILL NOT recognize my phone.
Click to expand...
Click to collapse
This is for windows 7 64bits : http://tinyurl.com/2548qh4
take a look @ post #4
Hope you solve your problem !
In case you have Windows 7 you can try the following.
http://www.killertechtips.com/2009/...gning-in-windows-7-using-group-policy-editor/
Are you installing the usb drivers using the utility in ADB? If not, delete the drivers in hardware manager, and try installing them with the utility.
I had no problems doing this on Vista, but I prefer to use ADB on Linux.
Sent from my Nexus One using XDA App
hey .
maybe i´ve got something for you.
download my file here
install the binaries and then reboot (i said you don't have to, but i think in your case it would be better)
EDIT: is the debug function enabled in your device?
OK, after a few hours and still no success with Vista, I went to storage and pulled out my personal PC I built that hasn't run in a few years thanks to corrupt hard drives.
I spent 4 hours repairing and fixing the hard drives and SUCCESS, I got it to detect it on my Windows XP PC.
NOW! Still not working! In the command prompt, it shows adb devices as one connected but still when I do an adb push nothing happens. Just recycles the adb menu....
Any suggestions?
Your first mistake is using a PC that you know is not working properly. Try a known working pc.
Sent from my Nexus One using XDA App
Try using a Linux distribution. Saves a lot of time and headache.
or just reinstall your windows. win7 would be better than vista.
malevolent000 said:
Your first mistake is using a PC that you know is not working properly. Try a known working pc.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
The PC I'm using now IS working. It recognizes adb device but wont push the flash images or anything.
Two days ago I tried to use Easy Root ToolV11 to root my device that's running 14.1.1.A.0.402 Model D6503, it said "waiting for device".
I looked something up a bit and tried to install ADB driver, but nothing shown up in my detected ANDROID device list even though it was already plugged in to my PC.
I also tried to set up ADB PATH by following a tutorial in this thread http://forum.xda-developers.com/showthread.php?t=2559009 but it didn't work.
In my device manager my device is under "portable devices" instead "android devices"
I also tried towelroot on my phone. It said that my phone is rooted, but root checker said "This device does not have proper root access"
Ps. usb debugging mode and unknown sources are enabled
edit:
The driver that was install for my device is from microsoft. (see pictures below)
I uninstalled the driver and it was reinstall again every time i plugged my device in. I tried to update the driver, but it said that my driver is already up to date.
GalosSide said:
Two days ago I tried to use Easy Root ToolV11 to root my device that's running 14.1.1.A.0.402 Model D6503, it said "waiting for device".
I looked something up a bit and tried to install ADB driver, but nothing shown up in my detected ANDROID device list even though it was already plugged in to my PC.
I also tried to set up ADB PATH by following a tutorial in this thread http://forum.xda-developers.com/showthread.php?t=2559009 but it didn't work.
In my device manager my device is under "portable devices" instead "android devices"
I also tried towelroot on my phone. It said that my phone is rooted, but root checker said "This device does not have proper root access"
Ps. usb debugging mode and unknown sources are enabled
Click to expand...
Click to collapse
Are you using Windows 8?
cpumaster said:
Are you using Windows 8?
Click to expand...
Click to collapse
im using windows 7 sp1
also I just realize that i cannot use Sony PC Companion to do anything with my device it said that internet connection is required, but I am already connected.
Not sure but perhaps the drivers were not correctly installed. Try this?
http://forum.xda-developers.com/showthread.php?t=2635830
hush66 said:
Not sure but perhaps the drivers were not correctly installed. Try this?
http://forum.xda-developers.com/showthread.php?t=2635830
Click to expand...
Click to collapse
I'm still getting the same problem with the driver install.
I think i know what the problem is right now. The driver that was install for my device is from microsoft. (see pictures below)
{
"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"
}
I uninstalled the driver and it was reinstall again every time i plugged my device in. I tried to update the driver, but it said that my driver is already up to date.
Well, I just plugged in my Z2 to my PC and checked the driver details and it's exactly the same as yours. So it might not be an issue with the driver after all.
You mentioned that you have already done the ADB setup but it didn't work. When you said "it didn't work", do you mean the ADB couldn't be setup, or did you mean you still got the "waiting for device" message? To check if your ADB has been setup properly, go into the command prompt and type adb devices. You should see a serial number (of your phone) as the response.
And you should also have had the fastboot drivers installed. Use this tool to install fastboot drivers: http://forum.xda-developers.com/showthread.php?t=2588979
hush66 said:
Well, I just plugged in my Z2 to my PC and checked the driver details and it's exactly the same as yours. So it might not be an issue with the driver after all.
You mentioned that you have already done the ADB setup but it didn't work. When you said "it didn't work", do you mean the ADB couldn't be setup, or did you mean you still got the "waiting for device" message? To check if your ADB has been setup properly, go into the command prompt and type adb devices. You should see a serial number (of your phone) as the response.
And you should also have had the fastboot drivers installed. Use this tool to install fastboot drivers: http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Finally it work!!!!
I'm rooting right now and it's stuck at cleaning up......what do i do now
GalosSide said:
Finally it work!!!!
I'm rooting right now and it's stuck at cleaning up......what do i do now
Click to expand...
Click to collapse
restart the install.bat file.. happens from time to time that it get stuck on cleaning up.
Check the official thread about Easy Root and you'll see loads of people had the same problem.
Just re-run the program and it will work.
Frantiic87a said:
restart the install.bat file.. happens from time to time that it get stuck on cleaning up.
Check the official thread about Easy Root and you'll see loads of people had the same problem.
Just re-run the program and it will work.
Click to expand...
Click to collapse
I did and it said "insmod: init_module '/data/local/tmp/wp_mod.ko' failed (File exists)"
edit:
I restart my phone and root again. It's finally rooted.
Thank you every one for helping me.
Thank you!
sorry we facing the same problem so please tell me if found a solution
ADB FASTBOOT Drivers
Nothing worked for me accept this one.
I went there downloaded this driver installed it and it did its magic.
https://www.driveridentifier.com/sc...14379&scanid=92D42FEE7DDD4826835F8C3C3611A400
Hi all. I have encountered error as below screenshot when I tried to flash stock rom Pixel 6. I have tried multiple times and stuck with the same error. Appreciate your kind advice.
{
"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"
}
firdayus said:
Hi all. I have encountered error as below screenshot when I tried to flash stock rom Pixel 6. I have tried multiple times and stuck with the same error. Appreciate your kind advice.
View attachment 5509157
Click to expand...
Click to collapse
1. Make sure you are using the latest Platform Tools (31.0.3)
2. Make sure you are using a good USB A to C cable.
3. Switch cables and ports
4. Make sure you have all the necessary files in your Platform Tools folder (If you extracted them from the zip there should be 6 of them).
Lughnasadh said:
1. Make sure you are using the latest Platform Tools (31.0.3)
2. Make sure you are using a good USB A to C cable.
3. Switch cables and ports
4. Make sure you have all the necessary files in your Platform Tools folder (If you extracted them from the zip there should be 6 of them).
Click to expand...
Click to collapse
yeah. I am using the latest Platform Tools, running on original USB-A to USB-C cable. Tried few ports and encountered the same issue.
I also noticed that my Pixel boot into fastbootd instead of normal fastboot mode.
firdayus said:
yeah. I am using the latest Platform Tools, running on original USB-A to USB-C cable. Tried few ports and encountered the same issue.
I also noticed that my Pixel boot into fastbootd instead of normal fastboot mode.
Click to expand...
Click to collapse
It will boot into fastbootd midway through the flashing, but should start off in fastboot.
Do you have the latest USB drivers installed? https://developer.android.com/studio/run/win-usb
Lughnasadh said:
It will boot into fastbootd midway through the flashing, but should start off in fastboot.
Do you have the latest USB drivers installed? https://developer.android.com/studio/run/win-usb
Click to expand...
Click to collapse
Yes. the USB driver successfully installed.
firdayus said:
Yes. the USB driver successfully installed.
View attachment 5509165
Click to expand...
Click to collapse
Does that mean you did install the driver from the link I gave you? Yours looks a little different than mine.
Also, are these 6 files in you Platform Tools folder? (see screenshot)(of course yours would be Oriole)
Lughnasadh said:
Does that mean you did install the driver from the link I gave you? Yours looks a little different than mine.
Also, are these 6 files in you Platform Tools folder? (see screenshot)(of course yours would be Oriole)
Click to expand...
Click to collapse
The USB driver package was download directly from Google website.
Yes, all of the 6 files available and intact and inside the Platform Tools folder.
USB drivers is a common issue with the Pixel 6.
You must use Google official drivers with the P6.
For the past Pixels, universal was okay.
firdayus said:
The USB driver package was download directly from Google website.
Yes, all of the 6 files available and intact and inside the Platform Tools folder.
View attachment 5509179
View attachment 5509181
View attachment 5509183
Click to expand...
Click to collapse
I would try a different cable then. Lots of people have found switching cables helped them with this problem. Other than that I can't think of anything else off the top of my head. But you could flash it using the Android Flash Tool if the flash-all.bat method isn't working for you. This is really an almost foolproof method of flashing.
Android Flash Tool
flash.android.com
Lughnasadh said:
I would try a different cable then. Lots of people have found switching cables helped them with this problem. Other than that I can't think of anything else off the top of my head. But you could flash it using the Android Flash Tool if the flash-all.bat method isn't working for you. This is really an almost foolproof method of flashing.
Android Flash Tool
flash.android.com
Click to expand...
Click to collapse
Okay sure, will do. Changing to different original Pixel cable now and reboot my machine. Seems to be running and able to boot. Thanks for your kind advice. Bravo!
vandyman said:
USB drivers is a common issue with the Pixel 6.
You must use Google official drivers with the P6.
For the past Pixels, universal was okay.
Click to expand...
Click to collapse
Thanks for your kind advice. I have changed to different original Google cable and reboot machine. Seems to be working fine now.
firdayus said:
Okay sure, will do. Changing to different original Pixel cable now and reboot my machine. Seems to be running and able to boot. Thanks for your kind advice. Bravo!
View attachment 5509195
Click to expand...
Click to collapse
Awesome!
Hello! I've posted this due to no one having any compatibility with TCL, I'm attempting to root my device.
Device Info: TCL 30T (Android 12, Model T603DL)
This is what I've attempted so far:
1: Enabled all settings for the preparation (Enabled Developer Mode and enabled USB Debugging and OEM Unlocking)
2: Tried KingoRoot (failed at 90%, no compatibility)
3: (On Pc) Tried ADB, installed it directly from Android (the Platform-Tools), and the device was found when typing (ADB Devices) through CMD
4: Tried to do a flash-boot but failed, I've also looked into Device Manager and it registers (TCL 30 T) as a "Portable Device", not sure if that's an issue
5: Tried some other one-touch rootings and failed, when trying to even do a flash it would say "command unknown" or "waiting for devices" and be on an infinite wait
I'm fairly new to android, though I've spent days on this. I'd love some guidance if you can, I can't find any tutorial for my device anywhere. Thank you!
Is your BL unlocked?
Arealhooman said:
Is your BL unlocked?
Click to expand...
Click to collapse
I don't believe it is, I don't know the abbreviation "BL". But I doubt I have it unlocked
LocalGrandpa020290293 said:
I don't believe it is, I don't know the abbreviation "BL". But I doubt I have it unlocked
Click to expand...
Click to collapse
Bootloader
Arealhooman said:
Bootloader
Click to expand...
Click to collapse
Yea I don't think I do, even so where can I get it unlocked/what do I download to unlock it? (Links to sites that can help are good or downloads too)
LocalGrandpa020290293 said:
Yea I don't think I do, even so where can I get it unlocked/what do I download to unlock it? (Links to sites that can help are good or downloads too)
Click to expand...
Click to collapse
I can’t find any guides for your device, but here si a general guide that works for most devices: https://www.droidwin.com/unlock-bootloader-android-device/
{
"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"
}
This is the issue, once it's rebooting I run the fastboot flashing unlock, and it says waiting for device, after such nothing happens (never finds it), and then the device just boots up normally, nothing special. What do you think is the issue?
LocalGrandpa020290293 said:
View attachment 5785985
This is the issue, once it's rebooting I run the fastboot flashing unlock, and it says waiting for device, after such nothing happens (never finds it), and then the device just boots up normally, nothing special. What do you think is the issue?
Click to expand...
Click to collapse
do you have Adb debugging enabled? Is your device on? Run “fastboot devices”
Arealhooman said:
do you have Adb debugging enabled? Is your device on? Run “fastboot devices”
Click to expand...
Click to collapse
I don't have that setting, I did see "Wireless Debugging" (had something to do with ADB's), so I enabled it, and retried all the steps, still nothing. What is to note is that when running the command 'fastboot devices', it returns an empty line in the console and thats it.
EDIT: Yes my device is on when attemping this, I believe that fastboot can't find my device
Double check? It should be a bit under wireles. You need it to operate form the BL
Arealhooman said:
Double check? It should be a bit under wireles. You need it to operate form the BL
Click to expand...
Click to collapse
Not sure I get the last part. I turn on my phone and enabled all that needed to be enabled. I then plug my phone to my PC via charger/USB. Then I run the command prompt and you saw the picture (phone already backed up). Wdym under wireless?
On the list
Unless you are booted, wireless doesnt work
Arealhooman said:
Double check? It should be a bit under wireles. You need it to operate form the BL
Click to expand...
Click to collapse
Do you have discord or something for instantaneous messaging? I can provide a live video too and upload to YouTube real quick
Arealhooman said:
Unless you are booted, wireless doesnt work
Click to expand...
Click to collapse
Booted as in the phone on and loaded (past lock screen), right? And no in device manager its labeled under Portable Devices
LocalGrandpa020290293 said:
Booted as in the phone on and loaded (past lock screen), right? And no in device manager its labeled under Portable Devices
Click to expand...
Click to collapse
It always does
just you need wired
LocalGrandpa020290293 said:
Do you have discord or something for instantaneous messaging? I can provide a live video too and upload to YouTube real quick
Click to expand...
Click to collapse
Arandomhooman#0001
Arealhooman said:
Arandomhooman#0001
Click to expand...
Click to collapse
Sent a request, should be named Blef or something
LocalGrandpa020290293 said:
Sent a request, should be named Blef or something
Click to expand...
Click to collapse
Hey, won’t be able to talk or accept the request now, but will later today kr tomorrow.
Hi all,
first of all: yes, I've used the search function but I couldn't find a solution.
I have a Nord 2 5G device and want to install Evolution X Custom ROM.
I followed the instructions in this forum (and other websites) and managed to downgrade to OOS 11 in order to get into fastboot. The adb command to boot into fastboot mode also worked and my device is saying
fastboot_unlock_verify ok
The device is in fastboot mode which is only for debug Android devices. If you want to exit fastboot mode, please long press volume up and power buttons simultaneously.
Click to expand...
Click to collapse
However, the fastboot command to flash TWRP does not work. On the command line I can only see
< waiting for any device >
Click to expand...
Click to collapse
and I continuously hear the Windows device attached/device detached chime. The device manager shows this:
{
"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"
}
After opening the properties, I can see this:
As it's German. It says:
The drivers for this device have not been installed. (Code 28).
There are no compatible drivers for this device.
Click to expand...
Click to collapse
So obviously I need additional drivers. I have downloaded the USB drivers from this website: https://developer.android.com/studio/run/win-usb, chose install from hard drive and pointed to the directory I have unzipped the driver set but Windows can't install them. I have also downloaded the OnePlus driver set from https://oneplusdriver.com/download-oneplus-driver and installed them.
Still, it doesn't work.
I am at the end of my rope now. What did I do wrong?
Thanks in advance!
I have same problem did you find solution
mckinley87 said:
Hi all,
first of all: yes, I've used the search function but I couldn't find a solution.
I have a Nord 2 5G device and want to install Evolution X Custom ROM.
I followed the instructions in this forum (and other websites) and managed to downgrade to OOS 11 in order to get into fastboot. The adb command to boot into fastboot mode also worked and my device is saying
However, the fastboot command to flash TWRP does not work. On the command line I can only see
and I continuously hear the Windows device attached/device detached chime. The device manager shows this:
View attachment 5835135
After opening the properties, I can see this:
View attachment 5835137
As it's German. It says:
So obviously I need additional drivers. I have downloaded the USB drivers from this website: https://developer.android.com/studio/run/win-usb, chose install from hard drive and pointed to the directory I have unzipped the driver set but Windows can't install them. I have also downloaded the OnePlus driver set from https://oneplusdriver.com/download-oneplus-driver and installed them.
Still, it doesn't work.
I am at the end of my rope now. What did I do wrong?
Thanks in advance!
Click to expand...
Click to collapse
Have you try to use platform-tools? It has adb and fastboot. I have always used that and no problem
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Look in Eigenshaften > Details > "Device instance path" (k.A. Gerätepfad?).
What's the VID/PID?
Is that in the stock INF file in android_winusb.inf?
If you want, you can just use Zadig drivers. I can give you "fastbogus.exe".
https://zadig.akeo.ie/
Select "WinUSB".
HamdiPiixel said:
I have same problem did you find solution
Click to expand...
Click to collapse
Yes, the thing is, I've installed the drivers in the wrong way. I'll try to give a step-by-step guide:
Go to Device Manager and find the Device (will have the yellow triangle. Right-click on it and choose upgrade driver (hope that's what's shown in the english version of Win 11). You'll see this:
Click the second option. You'll see this:
Here, choose the second option at the bottom. That's where I did it wrong. I selected the drivers in the dropdown menu and that doesn't work.
Click there...
and click there to select the diver *.inf file in the usb_driver folder.
That should work. It's important that you use the official Google Drivers (at least it was important here).
Hope that works.
mckinley87 said:
Yes, the thing is, I've installed the drivers in the wrong way. I'll try to give a step-by-step guide:
Go to Device Manager and find the Device (will have the yellow triangle. Right-click on it and choose upgrade driver (hope that's what's shown in the english version of Win 11). You'll see this:
View attachment 5856845Click the second option. You'll see this:
View attachment 5856867
Here, choose the second option at the bottom. That's where I did it wrong. I selected the drivers in the dropdown menu and that doesn't work.
View attachment 5856869
Click there...
View attachment 5856871
and click there to select the diver *.inf file in the usb_driver folder.
That should work. It's important that you use the official Google Drivers (at least it was important here).
Hope that works.
Click to expand...
Click to collapse
Hi,
I managed to install the ADB google drivers so I can now at least see Fastboot devices response properly but I do not know how to unlock the bootloader as the command "fastboot oem unlock" is not recognized and there is still no menu for the bootloader unlock (only the message on the black screen)
If anyone could help I would be be very grateful.
Thank you.
Best Regards
Lad