As i wrote in the title.
I'm facing the impossibility to istall driver needed for flashtool usage.
I already istalled flashtool and driver (located inside driver folder)
To do this i have used the "disable driver signing enforce" mode in windows 10.
But when i connect my XZ premium in flashmode i still have an unrecognised device in system.
And i receive the same error "windows found the driver but an error occured" if i try to manually istall SOMC flash device driver
this happen in normal mode and with driver verify mode disabled.
ADB and fastboot havw the same problem but i solved it disabling the driver signature verification
Still can't solve the problem with flashtool driver
Evil_Sephiroth said:
As i wrote in the title.
I'm facing the impossibility to istall driver needed for flashtool usage.
I already istalled flashtool and driver (located inside driver folder)
To do this i have used the "disable driver signing enforce" mode in windows 10.
But when i connect my XZ premium in flashmode i still have an unrecognised device in system.
And i receive the same error "windows found the driver but an error occured" if i try to manually istall SOMC flash device driver
this happen in normal mode and with driver verify mode disabled.
ADB and fastboot havw the same problem but i solved it disabling the driver signature verification
Still can't solve the problem with flashtool driver
Click to expand...
Click to collapse
You need more than one USB driver, there is the Sony drivers, as well as the Google ADB driver, if you're going to go into recovery.
It's really tiresome all these different drivers and sometimes Windows just picks the wrong one at random. So don't be surprised that the driver that windows says you need has to be forced manually into something different.
Didgesteve said:
You need more than one USB driver, there is the Sony drivers, as well as the Google ADB driver, if you're going to go into recovery.
It's really tiresome all these different drivers and sometimes Windows just picks the wrong one at random. So don't be surprised that the driver that windows says you need has to be forced manually into something different.
Click to expand...
Click to collapse
i have done it, fastboot work fine, i also istalled twrp without problem..but i'm now without system and i need flashtool to flash a stock ftf or a zip to flash in recovery.
and it seems i can't use flashtool no matter what
{
"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 error i get....phone connected in flashmode but no way to fix that driver error.
Evil_Sephiroth said:
i have done it, fastboot work fine, i also istalled twrp without problem..but i'm now without system and i need flashtool to flash a stock ftf or a zip to flash in recovery.
and it seems i can't use flashtool no matter what
this is the error i get....phone connected in flashmode but no way to fix that driver error.
Click to expand...
Click to collapse
You go to the device drivers, while the phone is plugged in, update the driver, then add a different driver using the .inf file from from a different driver folder.
As I said, Windows chooses the wrong driver by default nd you have to manually correct it.
You don't have a device that's different from everyone else, so you just need to experiment until it works, don't give up.
Edit: but if you're having this much trouble installing drivers, should you really be trying to force new firmware on your phone?
If flashing goes wrong you can brick your phone, just sayin.
Didgesteve said:
You go to the device drivers, while the phone is plugged in, update the driver, then add a different driver using the .inf file from from a different driver folder.
As I said, Windows chooses the wrong driver by default nd you have to manually correct it.
You don't have a device that's different from everyone else, so you just need to experiment until it works, don't give up.
Edit: but if you're having this much trouble installing drivers, should you really be trying to force new firmware on your phone?
If flashing goes wrong you can brick your phone, just sayin.
Click to expand...
Click to collapse
i've done it till 10 days ago....and now i have this problem, and i don't know why
Btw it's already without system, but i still have a working twrp and unlocked bootloader.
Even selecting different driver i still receive that error.
Didgesteve said:
You go to the device drivers, while the phone is plugged in, update the driver, then add a different driver using the .inf file from from a different driver folder.
Click to expand...
Click to collapse
sorry to revive this but how one is supposed to add the .inf from a diff driver folder? you mean from here?:
Related
Only For Xperia Devices
Intro :
If you are trying to flash custom Kernal/ROM and getting an error of your device not been detected by your PC running on windows 8 then you will need to install the USB/ADB/Device drivers for your handsets.
This can be done by using following tutorial.
!! UPDATE !!
Date : 20 - April - 2014
Those who are on windows 8.1 and having trouble to install drivers will have to download and install windows 8.1 update from here http://support.microsoft.com/kb/2917929 and once you install that you can follow this guide.
Step 1 :
Suppose you are trying to install custom Kernal on windows 8 and you stuck at this screen and nothing happens even if you connect your device in fastboot mode then its due to missing drivers.
{
"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"
}
Step 2 :
So now lets get started. Press "Start Key/Windows Key + C" or move your cursor to top right corner of the screen to activate the Charm Bar and click on "Settings Button" as shown in following figure.
Step 3 :
Now the setting panel will open. Click "Change PC Settings" from the bottom as shown.
Step 4 :
Now you will have this PC Settings screen.
Now click on General Tab. and scroll down to the bottom to find "Advance Start up Option" as shown below and click on Restart. This is immediate restart so make sure all programs are closed and saved.
Step 5 :
Your PC will reboot into Advance Start Up option. And you will see following screen. Now simply press on "Troubleshoot" option.
Step 6 :
In troubleshoot click on "Advance Options" .
Step 7 :
In advance option select "Start-Up Settings" .
Step 8 :
Now just press restart button in Start-Up settings as shown below. Your system will reboot in Start-Up Option Mode.
Step 9 :
Now after your system is rebooted you will get this following screen. Here to choose options we have to use function keys. Now press "F7" to select "Disable Driver Signature Enforcement" .
Now your PC will boot with Disabled Driver Signature Enforcement and you will be able to install Flashtool/Fastboot drivers.
You can get this drivers from Post #2.
Flashtool/Fastboot Drivers
Installing Flashtool/Flashboot Drivers
Step 1 :
Download the Flashtool/Fastboot Drivers from this link.
[Xperia Device] Flashtool & Fastboot Drivers.zip
And extract it using winRAR or 7zip software.
Click on "[Xperia Device] Flashtool & Fastboot Drivers.exe".
Step 2 :
Setup will start, Click Next.
Step 3 :
Scroll down in selection panel and tick Fastboot dirvers and flastool drivers and click Next.
Step 4 :
Now pop up drivers installation menu will appear. Click Next to proceed.
A red alert Allow box will appear, simply allow it and install the drivers. Do this until the driver installation finishes.
Finally, check which drivers are succeeded in installation from final screen, it will have green right tick if installation is succeeded.
Thank You Very Much
Nice to see you around btw
@neroyoung
the wuala link is dead, could you please reload ?
irontech said:
@neroyoung
the wuala link is dead, could you please reload ?
Click to expand...
Click to collapse
Link Updated
i didi it ..... tanQ
cant find a word to thank you enough, i am so grateful
I did everything and it didn't work
I'm on windows 8.1
Yap - in win 8.1 RTM - this trick didn't work - still "enumeration failed".
Anyone found a solution for Win 8.1 RTM ?
me to waiting for 8.1 otherwise have to go back to previous version
I need this for Win 8.1
i have revert back to 8. but just now saw a post in xda below. can someone try and post feedback here?
" I think I found a solution, at least for my case with a Rockusb device and windows 8.1:
It seems that there is a usb root hub driver for every usb connected device. after I connect mine and disable driver signature it says device not recognized, so I uninstall the corresponding "USB-Root-Hub" under "USB-Controller" in device manager. my corresponding "USB-Root-Hub" was, for some reason that I don't know, the 3rd one from the bottom. as soon as i deleted it, it recognized the device normally and I can use fastboot again with windows 8.1."
http://forum.xda-developers.com/showpost.php?p=44288852&postcount=24
ok good new guys!!!!!!!!!!!!!!!!!!!!!! i did install 8.1 and tried the method i have posted above. and it did work not the 3rd USB-Root-Hub worked for me but i did uninstall several and even mouse stared not working but then it did work. so i repeat what i did..
first thing after flash 8.1 was i went to disable driver signature . then went into device manage and turn off my phone and connect it. as usual message came "device not recognized," so i did uninstall the Usb controll. u can see triangular mark there. then uninstall USB-Root-Hub. i didn removed several then i install flashtools and then installed drivers inside flashtools. yeahhhhhhhhhh and all works now
try your self guys
I tried the above method.
Phone is connected in flashmode but not in fastboot.
Am I doing something wrong ? Is there any way to flash kernel in flashmode ?
mathewgx said:
I tried the above method.
Phone is connected in flashmode but not in fastboot.
Am I doing something wrong ? Is there any way to flash kernel in flashmode ?
Click to expand...
Click to collapse
u need fastboot to flash kernel. are u sure u installed fastboot drivers??
Yes , I installed flashmode and fastboot drivers , from drivers folder of flashtool directory. But , my phone is only recognized in flashmode , even if I connect it while pressing up volume button ( that is fastboot for xperia ray).
mathewgx said:
Yes , I installed flashmode and fastboot drivers , from drivers folder of flashtool directory. But , my phone is only recognized in flashmode , even if I connect it while pressing up volume button ( that is fastboot for xperia ray).
Click to expand...
Click to collapse
Well i know this is some confusing. anyway my phone is RAY too. after doing above mentioned method mine is working fine. by the way i did it in a fresh install of Win 8.1. and the first thing after install i did it to check if it work or not. so i dont know if u can do the same.
suggest you to try again. if u can post a screen pic of you device manager
When I connect my RAY , is always recognized as flashmode (SEMC flash device at device manager).
But in win 8 , there is a Sony Ericsson seehcri Control Device at device manager when in fastboot. So , I think that is the river i'm missing.
guyss help... i have successfully flashed the mobile.... but when i try to switch it on.. the red led blinks but the mobile doesnt start up... when i put it in charge, green light is on.. i tried powering on while charging still no luck...
I've been trying to root for ages, but no matter what I do I can't get ADB to recognize my device. I've tried reinstalling the drivers from I don't know how many sources as well as adb/fastboot several times, but I always get the same result:
{
"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"
}
In the device manager I get a yellow flag on the ADB interface:
I honestly don't think there's any way I can do it unless I get some help from you guys. So please? How do I get my computer to recognize my OPO once and for all?
I'm following this guide FYI (must be the fifth I try): http://android.stackexchange.com/questions/106856/how-to-root-oneplus-one
Thanks to the kind souls willing to give a hand.
Seleuco said:
I've been trying to root for ages, but no matter what I do I can't get ADB to recognize my device. I've tried reinstalling the drivers from I don't know how many sources as well as adb/fastboot several times, but I always get the same result:
?
In the device manager I get a yellow flag on the ADB interface:
In the device manager I get a yellow flag on the ADB interface:
?
I honestly don't think there's any way I can do it unless I get some help from you guys. So please? How do I get my computer to recognize my OPO once and for all?
I'm following this guide FYI (must be the fifth I try): http://android.stackexchange.com/questions/106856/how-to-root-oneplus-one
Thanks to the kind souls willing to give a hand.
Click to expand...
Click to collapse
Honestly you don't need adb portion working to do this. Have you tried seeing if your computer recognizes your opo in fastboot mode?
Turn your phone off hold volume up and power button it will boot into fastboot. Then plug your phone into your computer let it install drivers then open command prompt where your fastboot file is and type fastboot devices if it shows something your good to go follow the rest of the guide unlock bootloader and install a custom recovery and SuperSU to root.
Also if its me I would install twrp recovery.
you sure you got the right drivers?
@Seleuco try this tutorial and also check Y for install adb drivers
http://forum.xda-developers.com/showthread.php?p=48915118
the easiest method for having adb everywhere
You need to install divers first, look at your screenshot, you have no driver installed for adb device.
giaur said:
You need to install divers first, look at your screenshot, you have no driver installed for adb device.
Click to expand...
Click to collapse
Honestly I don't even know at this point, I tried deleting and installing them a dozen times from different sources, but it doesn't recognize them. Do you know any idiot-proow way of installing the drivers?
wulsic said:
@Seleuco try this tutorial and also check Y for install adb drivers
http://forum.xda-developers.com/showthread.php?p=48915118
the easiest method for having adb everywhere
Click to expand...
Click to collapse
Thanks, but I actually took the screenshots right after running that program
Seleuco said:
Thanks, but I actually took the screenshots right after running that program
Click to expand...
Click to collapse
Did you also tried to install the driver manually in device manager?
See this link how you can do that:
http://www.technobuzz.net/install-nexus-5-driver-adb-fastboot-unlock-bootloader/
If these drivers don't work and or can't install then just extract Snoop05's adb installer and use those drivers :good: hope this would work now,
the issue is probably that there are so many drivers installed that they are conflicting with each other and windows is just deciding which one is better, so manually overriding it should fix it and else I guess you have to remove the old adb drivers with an program but first try these easy methods
Hi dear friends. I have a interesting problem with Flashtool and Sony's last OREO update.
I want to flash 41.3.A.2.58 with flashtool. If I use old version of flashtool v0.9.23.2, I can connect my phone flash mode, but I can't flash last oreo update from Sony I get "NULL" error.. If I use newest version of flashtool 0.9.24.2, The FW was preparing to flash but my phone doesn't connect with flash mode so this time I get this "ERROR - Device connected in flash mode but driver is too old". I installed driver which is in the folder of newest Flashtool.I didn't understand what I did wrong. I am using Flashtool many years but I can't solve this problem. Please check the pictures.
FLASHTOOL v0.9.23.2
{
"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"
}
FLASHTOOL v0.9.24.2
There is an update for flashtool. I suggest you update and try again
v9.24.2 is the latest version. You may update your drivers from C:\Flashtool\drivers\Flashtool-drivers.exe and select the correct drivers you need (capture in attachment).
Tonio78r said:
v9.24.2 is the latest version. You may update your drivers from C:\Flashtool\drivers\Flashtool-drivers.exe and select the correct drivers you need (capture in attachment).
Click to expand...
Click to collapse
I am using last version too. And I installed last version driver but no luck you can see the pictures up
koekoek91 said:
There is an update for flashtool. I suggest you update and try again
Click to expand...
Click to collapse
I am using last version also but I get old driver error...
Mazellat said:
I am using last version also but I get old driver error...
Click to expand...
Click to collapse
Oh nevermind I now see your second screenshot is from the latest version.
Have you tried reinstalling drivers?
And have you tried redownloading the firmware or a different firmware maybe?
koekoek91 said:
Oh nevermind I now see your second screenshot is from the latest version.
Have you tried reinstalling drivers?
And have you tried redownloading the firmware or a different firmware maybe?
Click to expand...
Click to collapse
Bro I tried to install again and again Flashtool and drivers. But no luck...
Best to use flashtool version 0.9.24.2 to flash version 41.3.A.2.24_R3E(or equivalent) and then wait for an OTA to the latest version (41.3.A.2.58).
okubax said:
Best to use flashtool version 0.9.24.2 to flash version 41.3.A.2.24_R3E(or equivalent) and then wait for an OTA to the latest version (41.3.A.2.58).
Click to expand...
Click to collapse
I have unlocked bootloader So I think I can't use OTA update
boot ur phone in to download (flash) mode, go to device manager, expand universal serial bus controllers, then find somc device. "uninstall" delete the driver software. than unplug usb and repeat againg, boot into flashmode (not need flashtool any time) go into device manager, expand universal s b c, look for somc devices, or "semc device" if find delete again, if u see in un/recognized "android" u are done. now go to drivers from flashtool and install flashmode... i was installed flashmode and fastboot. while u installing that drivers look at "Android" now is again "somc device" and already version like a last flashmode driver. but different now is, now u can flash ur phone with latest flashtool by "ANDROXYDE" sorry about bad english, but i hope u understand me.
As G-Un1t say, start in flash mode and unistall all "semc" devices, and do that until u get the "semc" unrecognized, then disconnect, reinstall the flashmode and fastboot drivers again and then once again connect in flash mode.
Works for me on triying upgrade a Sony C5 Ultra(for latin america) From Lollipop to Mashmallow.
U have to repeatedly uninstall the SOMC devices, then SEMC devices till you see an "Android Driver" with a yellow ? mark..... Your are good to go after that...... thanks G-UN1T
Try this one
1. Download the relevant driver package from developer.sonymobile.com/downloads/drivers/. Make a note of the package folder name and of where you unzip the files.
2. Open Device Manager. You can do this by clicking Start, and then typing device manager. Then click Device Manager.
3. In Device Manager, right-click the name of your computer at the top of the device list, then click Add legacy hardware.
4. In the Welcome to the Add Hardware Wizard dialog, click Next.
5. Select the Install the hardware that I manually select from a list option, and then click Next.
6. Highlight Show All Devices and click Next.
7. Click Have Disk....
8. In the Install From Disk dialog, click Browse, and then find (see your note from step 1) and select the driver file ending with adb (written as xxxxxadb, where xxxxxx is the unique file name). Click Open.
9. In the Install From Disk dialog, click OK.
10. Highlight the Sony xxxxxx ADB Interface Driver file, then click Next twice. The installation starts.
11. Click Finish and then restart your computer.
hope this one help you guys
on this thread i finally found my problem solver for Device connected in flash mode but driver is too old, thank you
i just deleted SEMC driver on Device Manager of my 7-64bit, install driver from the folder of Flashtool,
Checklist Fastboot, Flashmode Drivers, and also Xperia Z3+ drivers, followed the instruction about 2012 method, and its worked
mine is E6553 Single...almost lost hope and thinking about suicide.
solved my undetected Sim Card problem too, after trying many Custom ROMs without any luck..
but some problem of noise sounds like sound of mouse while accessed internet or transmitted data was still unsolved
im using this one..E6553_32.3.A.0.372_R3D_Customized RU_1295-0592.ftf
all Nougat custom roms that i found cannot solved my undetected simcard was RR, and LA
now im going to put TWRP and root this one...
btw, i found that this Stock Rom made my Z3+ coolest that any Nougat Custom Roms, is so conform like never before
I had similar issue last week, turns out the cable was connected to the usb3 port on my laptop. once I plug it into usb2 port then it was fine.
Mazellat said:
Hi dear friends. I have a interesting problem with Flashtool and Sony's last OREO update.
I want to flash 41.3.A.2.58 with flashtool. If I use old version of flashtool v0.9.23.2, I can connect my phone flash mode, but I can't flash last oreo update from Sony I get "NULL" error.. If I use newest version of flashtool 0.9.24.2, The FW was preparing to flash but my phone doesn't connect with flash mode so this time I get this "ERROR - Device connected in flash mode but driver is too old". I installed driver which is in the folder of newest Flashtool.I didn't understand what I did wrong. I am using Flashtool many years but I can't solve this problem. Please check the pictures.
FLASHTOOL v0.9.23.2
FLASHTOOL v0.9.24.2
Click to expand...
Click to collapse
I have the same issue! ERROR - Device connected in flash mode but driver is too old.
Flashtool old drivers fix
I had the same problem with latest flashtool tool 0.9.24.4 but was fixed. Just go to Sony developer page and download and install Sony flash tool (emma), as simple as that and that error is gone
https://developers.sony.com/file/download/flash-tool-for-experia-devices/
Same problem (ERROR - Device connected in flash mode but driver is too old) with flashtool-0.9.24.2, I will try flashtool-0.9.24.4 today.
Thanks.
Hi, I had the same issue. I solved it by plugging into a USB 2.0 port instead of 3.0. I 'm not sure why but this is what works for me all the time. Hope it works for someone too.
Tonio78r said:
v9.24.2 is the latest version. You may update your drivers from C:\Flashtool\drivers\Flashtool-drivers.exe and select the correct drivers you need (capture in attachment).
Click to expand...
Click to collapse
Thank you so much for your great work:good::good:
Hi!
Yesterday, I received my brand new Fairphone 3 and I wanted to install /e/OS on it. However, I have some struggles with enabling fastboot on Windows 10. Hopefully someone can help me.
First, it is important to state that I was able to unlock the bootloader with fastboot on Windows 10, by following the official Fairphone guideluines; I unlocked dev settings and enabled usb debugging properly.
Next, after resetting everything to factory settings, I was able to boot in fastboot mode, whereafter I was trying to run ‘fastboot -w’ (which is the first step in order to flash /e/OS, according to the docs). After this, the terminal session hanged on ‘< waiting for any devices >’. Also, ‘fastboot devices’ did not reveal anything.
The following things I have tried to fix fastboot -w (all without success):
- Install Universal ADB Drivers
- Trying to change the driver in device settings. Even after removing the driver and rebooting Windows 10, the driver pops up as ‘FP3’ when I plug in the phone by usb (I do not understand why, maybe Windows is installing drivers in the background?)
- Installed the SDK 9.0 via Android Studio. After this, the phone is known as Samsung device (?)
- Toggling USB Preferences in Android between File Transfer and PTP
- Tried all USB ports on my computer
- Full phone factory reset
{
"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"
}
Can someone point me into the right direction?
Nijs said:
Hi!
Yesterday, I received my brand new Fairphone 3 and I wanted to install /e/OS on it. However, I have some struggles with enabling fastboot on Windows 10. Hopefully someone can help me.
First, it is important to state that I was able to unlock the bootloader with fastboot on Windows 10, by following the official Fairphone guideluines; I unlocked dev settings and enabled usb debugging properly.
Next, after resetting everything to factory settings, I was able to boot in fastboot mode, whereafter I was trying to run ‘fastboot -w’ (which is the first step in order to flash /e/OS, according to the docs). After this, the terminal session hanged on ‘< waiting for any devices >’. Also, ‘fastboot devices’ did not reveal anything.
The following things I have tried to fix fastboot -w (all without success):
- Install Universal ADB Drivers
- Trying to change the driver in device settings. Even after removing the driver and rebooting Windows 10, the driver pops up as ‘FP3’ when I plug in the phone by usb (I do not understand why, maybe Windows is installing drivers in the background?)
- Installed the SDK 9.0 via Android Studio. After this, the phone is known as Samsung device (?)
- Toggling USB Preferences in Android between File Transfer and PTP
- Tried all USB ports on my computer
- Full phone factory reset
Can someone point me into the right direction?
Click to expand...
Click to collapse
When you boot into fastboot mode and connect to PC, open device manager and see if it lists the driver as "Android Bootloader interface".
If it isn't showing android bootloader interface, you will have to manually select the bootloader interface driver by right clicking on the driver showing for your device. Then select update driver. Then choose the options that let choose drivers from resources already installed on your PC, when you get to where it shows a list of drivers to choose from, find the bootloader interface driver and select it then see if the PC recognizes the device while in fastboot mode.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
When you boot into fastboot mode and connect to PC, open device manager and see if it lists the driver as "Android Bootloader interface".
If it isn't showing android bootloader interface, you will have to manually select the bootloader interface driver by right clicking on the driver showing for your device. Then select update driver. Then choose the options that let choose drivers from resources already installed on your PC, when you get to where it shows a list of drivers to choose from, find the bootloader interface driver and select it then see if the PC recognizes the device while in fastboot mode.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I do not see the interface you mention, however, I see 'Android' under 'other devices' and 'FP3' under 'portable devices' and 'Google Nexus ADB Interface' under SAMSUNG Android Phone (I did not install this, I assume Windows did this in the background).
Which option should I select to install the driver manually? Or none of them?
Hi all,
I am trying to convert my T-Mobile IN2017 OnePlus 8 to have a global rom. I am currently on 10.5.7.IN55CB and I am following this tutorial here. My bootloader is unlocked (by using the official binaries I got emailed from OnePlus). My PC has driver signature verification off and is in test mode. It seems that my installer is stuck at this point:
{
"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"
}
because the driver is not installed for recovery I think:
I have tried installing/reinstalling the OnePlus drivers to no avail. The installer runs perfectly fine while in fastboot mode, but does not work once rebooted into recovery. If someone can send me the driver or show what I am doing wrong, it would be much appreciated!
Costik said:
Hi all,
I am trying to convert my T-Mobile IN2017 OnePlus 8 to have a global rom. I am currently on 10.5.7.IN55CB and I am following this tutorial here. My bootloader is unlocked (by using the official binaries I got emailed from OnePlus). My PC has driver signature verification off and is in test mode. It seems that my installer is stuck at this point:
View attachment 5499393
because the driver is not installed for recovery I think:
View attachment 5499395
I have tried installing/reinstalling the OnePlus drivers to no avail. The installer runs perfectly fine while in fastboot mode, but does not work once rebooted into recovery. If someone can send me the driver or show what I am doing wrong, it would be much appreciated!
Click to expand...
Click to collapse
See my post here:
https://forum.xda-developers.com/t/...with-bootloader-re-lock.4345305/post-86144965
You're having the same issue I had. You need to install the fastboot drivers while it's connected in that state from your screenshot. Grab the drivers from Foxy Drew's post (linked in mine above), run the installer until it hangs, then update the drivers on the PC. When I did this the flash-all installer immediately kicked back into gear and finished the process.
The problem, I, think, is that you need to install adb drivers and fastboot drivers while the phone is in 3 different boot modes: normal, fastboot/recovery, and bootloader. So you need to get the phone to be recognized in all of those states so you can apply the drivers to the device the PC "sees" when it's connected in each of those states. Every boot mode basically presents itself as a different device to the PC, and that 3rd fastboot mode is hidden until you get to the spot you show in your screenshot.
Hope that works for you.
SilverZero said:
See my post here:
https://forum.xda-developers.com/t/...with-bootloader-re-lock.4345305/post-86144965
You're having the same issue I had. You need to install the fastboot drivers while it's connected in that state from your screenshot. Grab the drivers from Foxy Drew's post (linked in mine above), run the installer until it hangs, then update the drivers on the PC. When I did this the flash-all installer immediately kicked back into gear and finished the process.
The problem, I, think, is that you need to install adb drivers and fastboot drivers while the phone is in 3 different boot modes: normal, fastboot/recovery, and bootloader. So you need to get the phone to be recognized in all of those states so you can apply the drivers to the device the PC "sees" when it's connected in each of those states. Every boot mode basically presents itself as a different device to the PC, and that 3rd fastboot mode is hidden until you get to the spot you show in your screenshot.
Hope that works for you.
Click to expand...
Click to collapse
Thank you so much for your help! I was actually able to get it to work by doing something really similar. I'll post what I did just in case someone runs into this exact issue:
1) I made sure that I had all the drivers installed
2) I did the entire process over again until I got to that part where my device was no longer recognized
3) I went into device manager > IN2017 > update driver > drivers installed on this pc > chose from a list > Android phone > Android bootloader interface
I did this all while the converter was running and my phone was plugged into my pc. Once I did this, the program continued and I was able to finish the install.
Costik said:
Thank you so much for your help! I was actually able to get it to work by doing something really similar. I'll post what I did just in case someone runs into this exact issue:
1) I made sure that I had all the drivers installed
2) I did the entire process over again until I got to that part where my device was no longer recognized
3) I went into device manager > IN2017 > update driver > drivers installed on this pc > chose from a list > Android phone > Android bootloader interface
I did this all while the converter was running and my phone was plugged into my pc. Once I did this, the program continued and I was able to finish the install.
Click to expand...
Click to collapse
Yep, I think that's exactly what I did. I can't remember which fastboot drivers I updated to bit I'll bet they're both the same, and that's the point in the process where I updated drivers as well.
Cheers!