Hey guys, got myself in bit of a bind. I just recently rooted using the 1 click tool and also installed CWM with it. Later, I tried to install TWRP through goomanager on top of that. It rebooted to recovery, and the recovery seems to not have installed properly. It just stays stuck at the TEAMWIN screen and flashes. Even after powering it off and back on, it goes straight to the teamwin screen. The only way for it to boot properly is to voldown+power and then let it cold boot.
So, I tried installing TWRP 2.5.0.0 over that, but instead of rebooting properly (after I follow the instructions from the twrp website) it reboots straight into the recovery still.
I tried using the 1 click tool to try to reinstall CWM, but now it no longer works. The command prompt just disappears after the driver installation part. After that, I tried easy flasher. Wasn't able to install Rogue or TWRP. They state that they have been installed correctly, but when I boot up the tablet it goes straight to the teamwin screen and stays stuck there.
Anyone else have any ideas? I honestly feel like I've tried everything. I haven't tried wiping it yet, but only because I don't feel safe wiping it without a recovery installed.
Using EasyFlasher, did you see any text on the screen? If not, it did not install.
Also, do you know how to use ADB?
If so, run try this:
Plug tablet to PC via USB
After the device was detected, Settings - Developer Options - Debugging (tick the box).
It should install new hardware and show 2 devices, an MTP and an ADB device.
Update the driver in the Device Manager on the windows machine to the Naked Drivers
Once that is updated, I downloaded ADB from the Android SDK. You really only need three files, available here: https://www.dropbox.com/s/h61zwmzaynouc1k/adb.zip
Unzip these files to a folder called c:\adb
Open a command prompt and type the following:
Code:
c:
cd c:\adb
adb devices
It should show a device connected. It may error out when restarting the daemon, but keep trying and see if it can find your tablet.
If you cannot get the ADB driver installed or updated, my guess is that you have a bad USB cable. Yes, it IS possible to have a bad cable for data transfer that STILL charges your tablet. I have even had that happen to me.
If you got this far, then here is what to do next:
Download your favorite recovery. I strongly recommend TWRP. The latest official release is here: http://techerrata.com/file/twrp2/tf101/openrecovery-twrp-2.3.2.3-tf101.blob
Save this at c:\adb\TWRP.blob. You can use a different recovery method if you have the blob file (such as CWM) but TWRP is far superior unless you are looking to install Android Revolution HD.
Code:
adb push TWRP.blob /sdcard/
adb shell
dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4
Wait until you see it succesfully transfer data.
Then:
Code:
adb reboot
exit
Once it reboots, you should see a progress bar at the ASUS screen. Once this completes you will have TWRP (or some other custom recovery installed)
With easyflasher I just hit flash and it says it worked correctly. Nothing appears on the tablet or anything.
I'm a newbie at adb, but I spent mostly all of yesterday learning it. After looking at your guide, I can say I was doing everything correct yesterday. I followed these same steps and still was sent back to the teamwin flashing screen after the reboot. There was no loading bar asus screen. I'm not sure what the problem is. Adb is working fine, it recognizes the device, it pushes the TWRP.blob, it goes through all the commands without error. Should I not be in a cold boot when entering this? Should I be in APX mode?
{
"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 wasn't able to get it working with your adb download however, I'm using the adb provided with the SDK manager. Not sure if that makes a difference. And could it be my drivers? I believe I installed the asus sync for my drivers, so when trying to update to naked drivers it just says it's already up to date. Also, I really appreciate the guide you wrote up, it really helped me cement that I'm doing everything right.
Very very weird.... I just fixed it, I think. I guess my drivers were bad, because I was able to update them to the naked drivers when in APX mode. Then I was able to use easy flash to reflash rogueCWM. After rebooting however, TWRP 2.5.0.0 was installed! Very very weird.
Related
Hi all,
Well my adventure started last night when I went to return my Nexus S to stock. I did so and it worked well. Then I tried to re-root the device.
After doing so, it now will not boot past the google boot screen (with the unlock icon). It just sits there, even after battery pulls and additional attempts to start up. I can reboot into recovery (fastboot) as shown on the attached images. After hours of reading, it seems I need to flash CWM recovery.img to get the phone to boot. Ok, not a problem. So I installed the android sdk, google and samsung phone drivers and my phone is recognized in device manager.
When I go to flash the recovery.img via fastboot, it just sits there on "waiting on device" and ever goes anywhere. I also have a message on the bottom of the Nexus screen that says "FASTBOOT STATUS - FAILInvalid Command"
I'm at a point where googling is doing no good. Please help.
How can I get my phone to boot? How can I successfully flash the recovery image so I can go forward with root and be done with it?
Thanks.
{
"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"
}
First step is get fastboot to recognize the phone.
Until the command fastboot devices brings up your serial number you can't flash. Your issue is either you don't got the fastboot driver installed ( does not install correctly by itself on windows 7 64bit) Or your in the wrong directory in fastboot. Or both.
Quides are on the forum how to do everything.
albundy2010 said:
First step is get fastboot to recognize the phone.
Until the command fastboot devices brings up your serial number you can't flash. Your issue is either you don't got the fastboot driver installed ( does not install correctly by itself on windows 7 64bit) Or your in the wrong directory in fastboot. Or both.
Quides are on the forum how to do everything.
Click to expand...
Click to collapse
Ok, how does one go about doing this on Win7x64?
Quides are on the forum? No idea what that means.
The forum is the place you're on right now. Read the stickies/how to's or just use the search feature.
albundy2010 said:
The forum is the place you're on right now. Read the stickies/how to's or just use the search feature.
Click to expand...
Click to collapse
Believe me, I've done that. Hours and hours worth.
Anyone care to help since apparently this information is so easy to locate? Fastboot simply isn't communicating with my phone and it will not boot past the google boot screen.
After many hours of trying, I figured it out. It had to do with the PDA net drivers. Basically, my phone would not boot up, preventing me from finishing the PDA net install. It kept hanging on "Installing PDA net to your phone" because, well, it couldn't install to my phone (since it was in fast boot mode).
I kept clicking on OK on the dialogue box and it would roll back, uninstalling the PDA net drivers. This was why fast boot could not communicate via cmd.
How I worked around this was by NOT clicking ok, hence not uninstalling the drivers.
It was an epiphany. And a pain in the arse.
So, if you have a similar issue, don't click ok on the dialogue. Leave it in limbo and work your command line magic!
On friday i booted down my TF101 B70 and when i booted it back up could not get into Android, tried Cold Boot Linux tried Wipe Data. Did not work.
I do still have my ClockworkMod Recovery v5.5.0.4 which i keep booting into.
The problem is I am able to access the interal memory but my superwipe and Revolution HD files are not on there (if this is fixed, i will never make that mistake again)
I formatted my 2gb micro sd and loaded superwipe and revolutionHD, but cwm recovery does not see it.
I hooked up the TF101 to my pc to see if there was any way I can get access to the internal SD but i cannot connect as it is an unknown device on Win 7 64bit, which i cannot find drivers for. (Tried Asus Sync, Tries Asus' page for usb, even tried the APX drivers)
My question is how can i gain access to the internal SD to place my superwipe and revolution hd to flash and save my beloved TF101? is there a way i can access it with ADB? im pretty sure mine is the SDKv2 which is not accessible (sorry if i wrote that wrong)
any insight will help. Thanks!
use adb push command to send giles from the pc to the main storage or use gnufabio's recover install http://forum.xda-developers.com/showthread.php?t=1346180 to install a cwm version which could access external sd card
do i do adb push from and set the tf101 into apx mode or while in cwm recovery?
BiohazardPL said:
do i do adb push from and set the tf101 into apx mode or while in cwm recovery?
Click to expand...
Click to collapse
You can use ADB in recovery. DO NOT put the Superwipe script back in because once you use it, it will wipe everything again. Just ADB push your ROM file to internal sd and use option inside CWM to wipe your TF.
when i am in APX mode, usind adb shell i get " error: device not found"
when i am in recovery, win7 cannot find the right driver for the device. it just sits in "other devices" in device manager as "Transformer"
btw, thank you guys for your input.
{
"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"
}
Here is what Win 7 64bit shows when I am in ClockworkMod Recovery v5.5.0.4
I've never really used adb under win. have you installed the dev drivers from asus site? i don't have theexact url at the moment, i'm sorry.
from asus' site i only tried the asus sync and ASUS_Android_USB_drivers_for_Windows. i will see if they have dev drivers on their page.
Nothing that i could find on the Asus site:
http://support.asus.com/Download.aspx?SLanguage=en&m=Eee+Pad+Transformer+TF101&p=20&s=16
I also installed from SDK Manager "Google USB Driver" still nothing
Try the driver out of ViperMod.
http://forum.xda-developers.com/showthread.php?t=1427125
When you're in the Device manager right click and chose update driver.
Point it to the driver location.
tried those, still will not accept those tried from within the "Driver" folder and Android MTP and tethering each one by itself.
This driver business is driving me nuts.
What about ASUS sync? That's what work for me
yep same issue. I just tried on a win xp 32bit netbook.
when i connect the TF101 it shows up as an Unknown device but the device name is "Transformer" and no matter what driver i try, it does not install the driver.
maybe is there something weird about Clockwork Mod Rocovery v5.5.0.4
installed Asus sync on win xp 32, did not update the drivers, also went directly into c:\program files\ASUS\ASUS Drivers for Windows\ that also didnt like it.
what is it with this ver of CWM that it wont like the drivers?
BiohazardPL said:
yep same issue. I just tried on a win xp 32bit netbook.
when i connect the TF101 it shows up as an Unknown device but the device name is "Transformer" and no matter what driver i try, it does not install the driver.
maybe is there something weird about Clockwork Mod Rocovery v5.5.0.4
Click to expand...
Click to collapse
But people with that CWM used ADB to fix the same problem you are having though.
Can you find someone in real life who already has transformer and adb drivers working on their computer? You should plug your TF into their computer and see if ADB works. If adb still doesn't work, then it's safe to say you are screwed I think.
Or find a working transformer and plug that into your computer and see what happens with drivers.
there is something weird about it that i have never experianced using cwm on a sgs2 and sgs.
when i go into CWM, and try for instance "install from sd card" then "choose file from sdcard" it takes a good 5 minutes to pull up anything, all you see for a while is the cwm logo in the center, then after about 5 6 minutes all the folders i have on there appear.
another thing i just noticed right now, after i reboot from cwm there a destinct click from the device on the back where the camera is....
this is not looking good
EDIT: nvmd supposedly this is normal
http://www.transformerforums.com/forum/asus-transformer-general-discussions/761-click-noise-2.html
horndroid said:
But people with that CWM used ADB to fix the same problem you are having though.
Can you find someone in real life who already has transformer and adb drivers working on their computer? You should plug your TF into their computer and see if ADB works. If adb still doesn't work, then it's safe to say you are screwed I think.
Or find a working transformer and plug that into your computer and see what happens with drivers.
Click to expand...
Click to collapse
will try that as soon as i have access to one
Another uopdate,
I booted with the Up Vol + Power to Coldboot linux, after letting it sit there for about 10 mintes the MTP driver popped up on my win 7 64. the driver installs, but in device manager it says the "device cannot be started"
So, during the "updating apps" screen, the phone ran out of battery. When starting the phone, the M logo and spinning animation appear, but then the screen gets black. Fastboot works, but recovery and factory reset don't.
Here's what I did:
- bootloader is version 41.1A
- I unlocked the bootloader
- phone was on Android 5.1 before the problem
- I have flashed several images following this guide
- finally one worked without any errors: XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xml.zip, but unfortunately the phone behaves the same (logos and then black screen)
- when connecting the phone to a Windows 10 PC: In Fastboot it shows up in the tray as "Fastboot Falcon S" and "Motorola ADB Interface" in "Device Manager "; When I turn on the phone normally and the screen goes black it appears as "XT1033" in the tray and "Portable Devices > MTP USB device" in Device Manager. Despite this it doesn't appear in Windows Explorer and I can't copy files to it.
- recovery shows a dead android and No Connection
- I tried to press Volume up for 15 seconds and then power but nothing happens
- next, I tried to flash TWRP and CWM (various versions) - the same happens - although there are no errors when flashing, the dead android shows up. And Vol UP+Power doesn't work
I really don't know what else to do and I want to throw the phone through a window. Please help. Thanks
Use mfastboot.
It would help to see a log of the firmware flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
lost101 said:
Use mfastboot.
It would help to see a log of the firmware flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Click to expand...
Click to collapse
Yup, I've been using mfastboot.
Here's what was displayed on the phone during flashing:
{
"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"
}
Here's the command log:
View attachment 3815001
Thanks
When flashing a firmware image makes no difference, it's a classic sign of emmc corruption. It happens often with phones as they get old. I'm not aware of any solution to this corruption, however it may be possible to flash a custom ROM (CM13 or Stock) via TWRP.
mfastboot boot twrp.img
You could try booting into Linux (via LiveCD if necessary) and this will give you access to recovery mode ADB. You can also backup your internal storage (photos etc) with adb pull /sdcard/ c:/motog_backup/
sudo fastboot boot twrp.img
Then do the following wipe:
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22
pandronic said:
So, during the "updating apps" screen, the phone ran out of battery. When starting the phone, the M logo and spinning animation appear, but then the screen gets black. Fastboot works, but recovery and factory reset don't.
Here's what I did:
- bootloader is version 41.1A
- I unlocked the bootloader
- phone was on Android 5.1 before the problem
- I have flashed several images following this guide
- finally one worked without any errors: XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xml.zip, but unfortunately the phone behaves the same (logos and then black screen)
- when connecting the phone to a Windows 10 PC: In Fastboot it shows up in the tray as "Fastboot Falcon S" and "Motorola ADB Interface" in "Device Manager "; When I turn on the phone normally and the screen goes black it appears as "XT1033" in the tray and "Portable Devices > MTP USB device" in Device Manager. Despite this it doesn't appear in Windows Explorer and I can't copy files to it.
- recovery shows a dead android and No Connection
- I tried to press Volume up for 15 seconds and then power but nothing happens
- next, I tried to flash TWRP and CWM (various versions) - the same happens - although there are no errors when flashing, the dead android shows up. And Vol UP+Power doesn't work
I really don't know what else to do and I want to throw the phone through a window. Please help. Thanks
Click to expand...
Click to collapse
Hi Pandromic I have almost identical issue as yours and now I am tired of using different roms. Although my phone is unrooted and the phone is stuck on the main screen with warning bootloader unlocked screen. If you succeed in finding any solution do let me know ! Thanks in advance
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 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!