Hey all,
I've been rooting phones for a little bit, so when I got my Nexus 7 a couple weeks ago and found that it was as simple as "fastboot oem unlock", I was thrilled. However, it ended up not being that simple, of course.
At first I couldn't get the device to show up for ADB or fastboot at all, even though Windows recognized the device. I downloaded the zip file of the drivers from Google, no luck. Downloaded a new version of the Android SDK, and used the adb/fastboot from it, and then ADB was able to see the N7 and was able to reboot it into the bootloader. However, once in the bootloader, it stops recognizing that the N7 is connected again. Trying "fastboot oem unlock" just causes the program to display <waiting for device> indefinitely.
So that's where I'm stuck now, I haven't been able to find any concrete details on this that are for the N7 2013 (pretty much everything I've found has either not been helpful or has been related to the original N7). Anyone able to help from here? Thanks!
Do u have USB debugging enabled in developer settings? Try turning your USB computer connection to PTP from MTP if you haven't already in storage settings. Then a pop-up will come on your n7 asking to approve your computer to see it. Tell it yes
>^.^< Sent From Meow HTC One
DowntownJeffBrown said:
Do u have USB debugging enabled in developer settings? Try turning your USB computer connection to PTP from MTP if you haven't already in storage settings. Then a pop-up will come on your n7 asking to approve your computer to see it. Tell it yes
>^.^< Sent From Meow HTC One
Click to expand...
Click to collapse
Thanks for the suggestions. Alas, I tried these things. The problem exists now when I'm in the bootloader, which is where fastboot won't recognize that the device is attached.
tigerxchaos said:
Thanks for the suggestions. Alas, I tried these things. The problem exists now when I'm in the bootloader, which is where fastboot won't recognize that the device is attached.
Click to expand...
Click to collapse
When you have the device connected to your computer when it's at the Bootloader screen, what does Device Manager show on your computer? Does it recognize the tablet but doesn't know what it is? You may need to install the drivers when you have the device in the Bootloader menu. I use the Google USB Driver (which you can download in the SDK Manager), right click on the device in Device Manager, select "Update Driver Software", "Browse my computer for driver software", "Let me pick from a list of device drivers on my computer", then browse the list. It may be listed under Android Device, Google...just look down the list, then select the appropriate driver. I believe from there you can select "Android Bootloader Interface", and that should let fastboot commands work.
You may need to reboot the computer.
Make sure you are using the usb cable that came from asus.
Thanks for the help. I tried the process again on a different computer, and eventually got it to work. I was able to unlock bootloader and flash TWRP 2.6.3.0. However, I was only able to mount System, Cache, and USB-OTG as partitions in TWRP, so I couldn't figure out where to drop the SuperSU binary .zip file. I tried rebooting, and (this may have been a mistake) installed the TWRP SU binaries on the way out. Now the device is stuck in a bootloop. Not sure if it was related to the SU binaries or the fact that I couldn't load any sort of data partition. Any thoughts?
EDIT: Apparently the root instructions don't make it clear that you will lock your data partition if you don't boot the device after unlocking the bootloader. I went straight into TWRP from the bootloader after unlocking it, and got a password request. Hit "Cancel" and it let me into TWRP, but factory reset failed. I had to wipe data, wipe cache, then reboot, then do a factory reset and now I'm back in.
Related
hi everyone, i'm trying to install CM9 on my LT15i, i've tried using the CM wiki instructions and both the following guides...
androidauthority.com/xperia-arc-lt15i-root-android-4-0-ics-80265/
and
androidforums.com/rezound-all-things-root/506466-scottys-noob-friendly-root-guide-start-finish.html
the phone is already fully unlocked and has CM 7.2.0 anzu installed. i've tried simply using the clockwork recovery mod bootloader to wipe the phone and install CM 9.0.0, but on reboot the phone gets past the boot logo then just shows a black screen, so i assumed i needed to flash an appropriate ROM for CM9; this is where my problem begins.
every forum i've read about this process says i must enable usb debugging (done) and "disable fastboot" under settings>power, i do not have a "power" option in my settings and cannot find anything related to fastboot on the phone; although i'm not sure this is the problem. when android is running normally and i attempt to list devices with adb.exe on windows, it successfully returns the phone's serial number. when i shut the phone down, hold the menu button and plug in the usb cable, fastboot mode appears to work correctly as the LED comes on blue and "android adb device" appears in the windows device manager (i've tried installing the arc usb/adb drivers from various sources, they all seem to work correctly). but when i attempt to list devices after restarting in fastboot mode, adb.exe says it cannot find any device. fastboot.exe has not communicated with the device whatsoever, but i assumed i might need to get the adb.exe usb daemon/server running correctly first for this to work.
i did this process once already when i installed CM7, it was successful the first time and everything went smoothly. from what i recall i just did exactly as described above and fastboot.exe was able to find the device no problem. but that was a number of months ago, hopefully i'm just missing some obvious step.
cheers
WookieInHeat said:
every forum i've read about this process says i must enable usb debugging (done) and "disable fastboot" under settings>power, i do not have a "power" option in my settings and cannot find anything related to fastboot on the phone;
Click to expand...
Click to collapse
There is no such thing. And USB debugging is only required if you want to root stock ROM, every other action can be done without it.
WookieInHeat said:
although i'm not sure this is the problem. when android is running normally and i attempt to list devices with adb.exe on windows, it successfully returns the phone's serial number. when i shut the phone down, hold the menu button and plug in the usb cable, fastboot mode appears to work correctly as the LED comes on blue and "android adb device" appears in the windows device manager (i've tried installing the arc usb/adb drivers from various sources, they all seem to work correctly). but when i attempt to list devices after restarting in fastboot mode, adb.exe says it cannot find any device. fastboot.exe has not communicated with the device whatsoever, but i assumed i might need to get the adb.exe usb daemon/server running correctly first for this to work.
i did this process once already when i installed CM7, it was successful the first time and everything went smoothly. from what i recall i just did exactly as described above and fastboot.exe was able to find the device no problem. but that was a number of months ago, hopefully i'm just missing some obvious step.
cheers
Click to expand...
Click to collapse
Drivers, drivers, drivers.
If your phone is in fastboot mode, make sure drivers are installed. Proper drivers.
You do not need ADB server for installing a kernel.
Just open up Command Prompt and install the kernel with command
Code:
fastboot flash boot boot.img
.
Assuming boot.img is in the same folder as fastboot.exe.
Someguyfromhell said:
Drivers, drivers, drivers.
If your phone is in fastboot mode, make sure drivers are installed. Proper drivers.
Click to expand...
Click to collapse
thanks for the reply someguyfromhell. i've tried every "android adb interface" driver under the sun for the S1 fast boot device that appears in the windows device manager when i put the phone in fastboot. when i try to send any command with fastboot.exe it just hangs at "waiting for device", i've fiddled with this stuff every which way and just cannot get fastboot.exe to see the phone. i've tried switching up the usb ports on this computer, but haven't had the opportunity to try a second computer. you've let me know i'm going in the right direction at least, if i have the same results on a second machine i'll pursue the issue further.
thanks again
wookie
WookieInHeat said:
thanks for the reply someguyfromhell. i've tried every "android adb interface" driver under the sun for the S1 fast boot device that appears in the windows device manager when i put the phone in fastboot. when i try to send any command with fastboot.exe it just hangs at "waiting for device", i've fiddled with this stuff every which way and just cannot get fastboot.exe to see the phone. i've tried switching up the usb ports on this computer, but haven't had the opportunity to try a second computer. you've let me know i'm going in the right direction at least, if i have the same results on a second machine i'll pursue the issue further.
thanks again
wookie
Click to expand...
Click to collapse
You need to unlock bootloader, if you want to install CM ROM. Arc S can only have bootloader unlocked via official method, there you can also download the correct driver which you need.
http://unlockbootloader.sonymobile.com/
Someguyfromhell said:
You need to unlock bootloader, if you want to install CM ROM. Arc S can only have bootloader unlocked via official method, there you can also download the correct driver which you need.
the bootloader is already unlocked, as i said, the phone has CM7 on it currently.
Click to expand...
Click to collapse
Windows 7 x64
Galaxy Nexus i515, BROKEN SCREEN, USB DEBUGGING WAS NOT TURNED ON. The phone is completely stock I just turned it on and used it until I broke my screen. Screen lock is on.
I have been trying to access my phone, using Fastboot, to wipe it before I send it in for warranty. I can not seem to do this at all. It seems that I can not install the drivers because I have not enabled USB debugging. Is this true? I have been following this guide : http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sdk/2/ When i go to manually install the drivers, from SDK, I get, "The folder you specified does not contain a compatible software driver for your device. If the folder contains a driver, make sure that it is designed to work with Windows for x6-based systems." I then tried the driver from Samsung and got the same response.
So then I hold VOL+ _ VOL- and Power and tried to install the drivers for Fastboot with the same outcome as above. Also when I boot in Fastboot mode the drivers that are installed make my phone a modem. The driver is called, "SAMSUNG Mobile USB Modem." I can not get this to change.
So to summarize I can not get the ADB Drivers to install, because I do not have USB Debugging enabled, that in return will not allow me to install Fastboot Drivers because when I plug the phone in the computer sees it as a Modem.
Any suggestions? I am just trying to erase the info on my phone I have given up all hope of recovering any data.
Thanks,
qualm
USB debugging drivers/interface have nothing to do with fastboot drivers/interface. What's a screen lock?
a manta wrote this.
beekay201 said:
USB debugging drivers/interface have nothing to do with fastboot drivers/interface. What's a screen lock?
a manta wrote this.
Click to expand...
Click to collapse
I meant a screen pattern lock. When you wake up the screen you have to connect the dots in a certain pattern before your screen unlocks and you can use the phone.
As far as, USB debugging drivers/interface having nothing to do with fastboot drivers/interface, then what am I doing wrong? I can not get my computer to see my phone as an android device.
_qualm_ said:
I meant a screen pattern lock. When you wake up the screen you have to connect the dots in a certain pattern before your screen unlocks and you can use the phone.
As far as, USB debugging drivers/interface having nothing to do with fastboot drivers/interface, then what am I doing wrong? I can not get my computer to see my phone as an android device.
Click to expand...
Click to collapse
I know what a screen pattern lock is.
Uninstall all drivers, reboot pc.
Assuming device is off: press power+vol up+vol down, until you feel the vibration. Wait 2 secs or so. Device will be in fastboot mode.
Read this thread, i say again, READ this thread, obviously start with the first post! - http://forum.xda-developers.com/showthread.php?t=1812959
Thanks for the link. I read it and followed instructions for installing the drivers. Here is what I did:
1.Uninstalled all drivers
2.Rebooted my PC
3.Downloaded these Drivers, as suggested: http://forum.xda-developers.com/showthread.php?t=1379875
4.Followed these instructions, on how to install the driver without windows trying to find one automatically: http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
Everything seemed to go well under the Device Manager, when I plug my phone in in fastboot mode, it shows Android Phone -> Samsung Android Interface. This is way better than what I had before, when it was showing up as a Modem. Now when I try to use fastboot.exe and I type "fastboot devices" nothing shows up. I reset the computer and replugged in my device, in fastboot, and the same thing nothing shows up in fastboot.
Thanks for you help.
Did you miss the part about having to feed windows the same driver again, when connecting the device for the first time, in FASTBOOT MODE?
a maguro wrote this.
beekay201 said:
Did you miss the part about having to feed windows the same driver again, when connecting the device for the first time, in FASTBOOT MODE?
a maguro wrote this.
Click to expand...
Click to collapse
Not sure if I understand what your asking.
I followed all of the steps here: http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735 I connected the phone booted normally and let windows find a driver so that the driver reads Portable Devices -> Galaxy Nexus. Then I unplugged the Nexus and booted it in fastboot mode and plugged it in. Next I followed the directions to install the Universal_Naked_Driver, in fastboot mode. I can not install the driver for ADB because I can not enable USB Debugging with my broken screen.
Thanks Again.
Why is it so difficult for people to understand that USB debugging has nothing to do with anything outside the booted OS?
Sent from my Galaxy Nexus
W8 a sec, do you even have your bootloader unlocked???
You said you're running stock, so that should have been my first question, because to unlock your bootloader through the usual way, you need to confirm a dialog on the device... which in your case, doesn't have a working screen.
_qualm_ said:
Not sure if I understand what your asking.
I followed all of the steps here: http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735 I connected the phone booted normally and let windows find a driver so that the driver reads Portable Devices -> Galaxy Nexus. Then I unplugged the Nexus and booted it in fastboot mode and plugged it in. Next I followed the directions to install the Universal_Naked_Driver, in fastboot mode. I can not install the driver for ADB because I can not enable USB Debugging with my broken screen.
Thanks Again.
Click to expand...
Click to collapse
....
Lets see:
That post shows how it's done, correctly. (I think, from what i've read)
pay attention to part 3)
3)
NOTE:
- The method described here can be used to install the "Samsung Galaxy Nexus ADB Interface" driver as well as the "Samsung Galaxy Nexus Bootloader Interface" driver.
- Differences between the two procedures. One is done with the phone booted up normally and "USB Debugging" is enabled, and the other is done when the phone is in fastboot. I will cover the "USB Debugging" part here.
Click to expand...
Click to collapse
then...
We will now install the two drivers that efrant talked about in his post.
A) (FOR ADB - WHEN RUNNING ANDROID OS):
Enable USB debugging on your device
- Goto Settings > Developer Options > Check "USB Debugging"
- Connect device, manually update driver to Naked driver by 1wayjohny, done. On 4.2 and above, you'll need to confirm that you accept the host's (your pc) RSA key.
B) (FOR FASTBOOT - WHEN RUNNING FASTBOOT MODE)
boot into fastboot mode - power off phone and hold vol up + vol down + power
Click to expand...
Click to collapse
Both for A) and B), you need to do the "Update drivers manually" part!
Right now, your only option is B), that is to use fastboot to either:
- Flash stock images.
- To get your data back, boot a custom recovery (which won't require the RSA key confirmation for ADB) from fastboot, then use ADB to pull your /sdcard/ or whatever.
Pirateghost said:
Why is it so difficult for people to understand that USB debugging has nothing to do with anything outside the booted OS?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I am learning this ^. I am having trouble getting my computer to see my phone, in fastboot mode. All of the instructions that I have read start with installing drivers for ADB, which requires the phone to be USB debugging mode, and then the drivers for fastboot. So I thought my trouble was, since I can not install the drivers for ADB, and that I was having trouble with all of my drivers, that it was probably the fact that my phone can not be put into USB debugging mode. I now realize that USB debugging has nothing to do with fastboot, as fastboot is before the OS is booted. I am still just having trouble with my fastboot driver and seeing my phone with fastboot.exe.
beekay201 said:
W8 a sec, do you even have your bootloader unlocked???
Both for A) and B), you need to do the "Update drivers manually" part!
Right now, your only option is B), that is to use fastboot to either:
- Flash stock images.
- To get your data back, boot a custom recovery (which won't require the RSA key confirmation for ADB) from fastboot, then use ADB to pull your /sdcard/ or whatever.
Click to expand...
Click to collapse
No my bootloader is not unlocked. Is this the reason that my phone is not detected by fastboot.exe? Do I need to unlock my bootloader?
I have been trying option B, as I know this is my only option. I have been doing the "Update drivers manually" part I even tried on another PC with windows 7, to no avail. What ever I seem to do I can not see my device in fastboot.exe.
_qualm_ said:
No my bootloader is not unlocked. Is this the reason that my phone is not detected by fastboot.exe? Do I need to unlock my bootloader?
I have been trying option B, as I know this is my only option. I have been doing the "Update drivers manually" part I even tried on another PC with windows 7, to no avail. What ever I seem to do I can not see my device in fastboot.exe.
Click to expand...
Click to collapse
No. Fastboot should be able to see your device if the proper drivers are installed. Fastboot is REQUIRED to unlock the bootloader
Sent from my Galaxy Nexus
Pirateghost said:
No. Fastboot should be able to see your device if the proper drivers are installed. Fastboot is REQUIRED to unlock the bootloader
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
If you used odin to flash something, that will unlock the bootloader. Flashing a section of edited param using OMAP flash will also unlock the bootloader.
Beamed from my Maguro.
I also have the same problem with my galaxy C5.
_qualm_ said:
No my bootloader is not unlocked. Is this the reason that my phone is not detected by fastboot.exe? Do I need to unlock my bootloader?
I have been trying option B, as I know this is my only option. I have been doing the "Update drivers manually" part I even tried on another PC with windows 7, to no avail. What ever I seem to do I can not see my device in fastboot.exe.
Click to expand...
Click to collapse
My galaxy C5 is also not recognized as a bootloader interface while in fastboot mode, after installing all the drivers correctly. Samsung usb driver v1.5.63.0 makes the changes i think, and it makes it as a modem instead of bootloader. maybe the solution is i have to manually update the driver of that modem into bootloader, right click on the modem in device manager and change it's driver into bootloader of your phone, maybe it works. I will try it this way.
Let me know if this solution has worked for someone.
Thanks
I unlocked, and rooted my nexus 7 using the Nexus Root Toolkit.
Everything was good until, after a few days, I tried turning on my device but got stuck on the "X" loading screen. After googling for a bit, I figured a factory reset would do the trick. I tried to factory reset the device in TWRP, but was confused by the two buttons and accidentally wiped everything (in adv wipe with everything checked).
Now the next problem is that I don't have USB debugging enabled (I recall turning it off for some reason). When i run "adb devices", nothing comes up and so i can't push anything to the device (and everything is wiped). Is there a command i can run, or file i can edit while in TWRP recovery mode to enable it? It seems i can't do anything without it enabled.
I did the same thing. This will help you get back to square one.
http://forum.xda-developers.com/showthread.php?t=2382618
Sent from my Nexus 7 using Tapatalk 2
poootythang said:
Now the next problem is that I don't have USB debugging enabled (I recall turning it off for some reason). When i run "adb devices", nothing comes up and so i can't push anything to the device (and everything is wiped). Is there a command i can run, or file i can edit while in TWRP recovery mode to enable it? It seems i can't do anything without it enabled.
Click to expand...
Click to collapse
Regarding how to most quickly get you back up and running, it is probably easier to just flash the stock images as mentioned above.
Regarding your adb issue, if you can boot into TWRP and are using a known good USB 2.0 port (sometimes 3.0 gives issues), then adb should already be running (ie what usb debugging enables is running)
You probably don't have drivers installed for adb running under recovery. The regular drivers don't work.
See this post:
http://forum.xda-developers.com/showthread.php?t=2391236
The ADB drivers from SDK is only for when in Bootloader and booted into ROM for needing USB Debugging. This is the driver you need in addition to what you have you've already installed to use ADB while in recovery otherwise you will see "Flo" under Unknown Devices in your computer Device Manager.
Thank you everyone. The new drivers and restore guide worked perfectly.
Ok so I'm trying to flash L. All of my drivers are updated, I downloaded them again and installed just to be sure, but when I have my Nexus plugged in it still isn't detected, and yes USB debugging is on. I tried adb reboot bootloader and nothing, then I manually went into the bootloader and typed the flash-all command and it stayed stuck on waiting for device. Very frustrating, any help is appreciated.
C-4Nati said:
Ok so I'm trying to flash L. All of my drivers are updated, I downloaded them again and installed just to be sure, but when I have my Nexus plugged in it still isn't detected, and yes USB debugging is on. I tried adb reboot bootloader and nothing, then I manually went into the bootloader and typed the flash-all command and it stayed stuck on waiting for device. Very frustrating, any help is appreciated.
Click to expand...
Click to collapse
Try changing to PTP.
FWIW, I solved my driver issue this way. And mine works with ptp, mtp, debugging on or off.
You can also try using Koushs drivers, but it only is a half-measure fix.
Also sometimes you have to revoke usb auths, and unlock the device and look for the key fingerprint prompt when you first plug it into usb, and reaccept it.
mdamaged said:
Try changing to PTP.
FWIW, I solved my driver issue this way. And mine works with ptp, mtp, debugging on or off.
You can also try using Koushs drivers, but it only is a half-measure fix.
Also sometimes you have to revoke usb auths, and unlock the device and look for the key fingerprint prompt when you first plug it into usb, and reaccept it.
Click to expand...
Click to collapse
Didn't work, followed your steps in the other thread. I guess I'll just have to wait until a flashable zip for L :/
edit- And btw I tried it on both of my hard drives, one with windows 8 and one with windows 7, didn't work on either.
C-4Nati said:
Ok so I'm trying to flash L. All of my drivers are updated, I downloaded them again and installed just to be sure, but when I have my Nexus plugged in it still isn't detected, and yes USB debugging is on. I tried adb reboot bootloader and nothing, then I manually went into the bootloader and typed the flash-all command and it stayed stuck on waiting for device. Very frustrating, any help is appreciated.
Click to expand...
Click to collapse
These are the steps that I've used and have never had any problems with drivers. My brother had the same problem that your having a while back and these steps cleared up his driver problems. Maybe it's worth a shot.
First of all I NEVER let windows automatically install drivers except for a very short time period after a clean install of windows. It makes life easier if windows doesn't jump the gun and try to install what it thinks will work. I always get drivers directly from the manufacturer. After you stop windows from trying to do it's automatic driver install thing plug in your N7 to your computer and open device manager (I usually just type dev in the start search box of W7), find your device, right click and choose Uninstall, check the box for Delete the driver software for this device. When it finishes doing that reboot your computer and unplug your N7. Once your computer has completely booted back up plug in your N7 and open the device manager again. Find your N7 again, right click Update driver software then choose Browse my computer. Find your folder (including the subfolders) with the drivers and let it install, once it finishes unplug your N7 for a few seconds then plug it back in and hopefully it should be all good. If your want it I have a copy of the usb drivers at dropbox from my recently updated sdk install. I would just extract the folder and point the install to the whole folder, if you included subfolders at the install it will find what it needs inside the folder. Make sure you authorize your computer with usb debugging. Good luck! ; )
wantabe said:
These are the steps that I've used and have never had any problems with drivers. My brother had the same problem that your having a while back and these steps cleared up his driver problems. Maybe it's worth a shot.
First of all I NEVER let windows automatically install drivers except for a very short time period after a clean install of windows. It makes life easier if windows doesn't jump the gun and try to install what it thinks will work. I always get drivers directly from the manufacturer. After you stop windows from trying to do it's automatic driver install thing plug in your N7 to your computer and open device manager (I usually just type dev in the start search box of W7), find your device, right click and choose Uninstall, check the box for Delete the driver software for this device. When it finishes doing that reboot your computer and unplug your N7. Once your computer has completely booted back up plug in your N7 and open the device manager again. Find your N7 again, right click Update driver software then choose Browse my computer. Find your folder (including the subfolders) with the drivers and let it install, once it finishes unplug your N7 for a few seconds then plug it back in and hopefully it should be all good. If your want it I have a copy of the usb drivers at dropbox from my recently updated sdk install. I would just extract the folder and point the install to the whole folder, if you included subfolders at the install it will find what it needs inside the folder. Make sure you authorize your computer with usb debugging. Good luck! ; )
Click to expand...
Click to collapse
Thanks mate, didn't work though so I'm not sure what is going on. I'll just wait until zips get created but thanks for the help guys.
Howdy,
I'm trying to get my phone unlocked and rooted. As the first step, of course, I'm trying to get the Google USB drivers to install, but I simply can't. I feel like I'm the only person having this issue, though because I cannot find a solution... The steps I'm following:
Downloaded the latest driver zip from Google
Open Device Manager
Expand Portable Devices
Right-click on the Phone entry (notice, that's the entry, "Phone". Not Razer.)
Choose Update Drivers
Browse my way to the drivers folder and click Next.
Windows then returns immediately "The best drivers for your device are already installed", and shows that it's an MTP USB Device.
I noticed that under USB devices, there's an ADB Interface device listed, and I get the same results when I try to update that, too (excepting it says it's an "ADB Interface" device, of course). I have tried uninstalling both devices to get the drivers to install, but no such. I've rebooted both phone and computer as well.
On the phone, USB Debugging is turned on, and USB mode is set to MTP file transfer.
Please help!
Figured it out...
tkarakashian said:
Howdy,
I'm trying to get my phone unlocked and rooted. As the first step, of course, I'm trying to get the Google USB drivers to install, but I simply can't. I feel like I'm the only person having this issue, though because I cannot find a solution... The steps I'm following:
Click to expand...
Click to collapse
In case anyone else is seeing the same issues, I wanted to put my resolution up: I'd been trying to install the drivers with the Razer booted. On a whim, I rebooted it into Download Mode using "adb reboot bootloader". Once there, I had an Android Device listed in Device Manager. I ran the driver update wizard, and installed the "USB ADB Interface" option from the choices presented. I was then able to run the OEM unlock command and received the confirmation prompt on the Razer. Yay!
Now, since it's been so long, I've got to re-back-up everything so I can actually do this thing. LOL
Here's the PDF from Razer's how to install a factory image over PC guide. It explains how to do it all
s3.amazonaws(.)com/cheryl-factory-images/How_to_Install_Android_Fastboot_Drivers_on_Windows.pdf (remove parantheses)