I wanted to root my razer phone 2 because I rooted my old Samsung, but after unlocking my bootloader I decided against it and now ive spent about 2 days trying to lock my bootloader again with no luck.
ive tried many different usb drivers and non of them show my device under the "fastboot devices" command in adb or fastboot but I can show the device under adb devices which im aware is rather easy
ive seen many people have this issue but they don't really show/tell how its fixed! ive tried different usb sockets too!
the device name in my device manager is "SAMSUNG Android Phone" (while the phone is in fastboot mode) with the sub driver called "Android Bootloader Interface" if anyone has any kind of advice or tips to get my bootloader locked again please share!
okay, so after a lot of looking around.. I found this.
"1) - To unlock the razer phone bootloader do the following
2) - Install ADB + Fastboot and google usb drivers
3) - Enable developer mode by going to settings, about phone and hitting build number a bunch of times. then go back to settings > developer options and check USB Debugging and OEM Unlock.
4) - Open a command prompt on your PC and connect the phone's usb cable to your computer. Accept the prompt on the phone for trusting the computer when plugged in.
5) - type the following in command prompt without quotes "adb reboot bootloader"
6) - You'll be at the download mode screen with the razer logo.
7) - Make sure the driver for ADB Bootloader Interface was installed. If not you'll probably have a device called Android under "Other devices" in device manager. If this is the case, install the google usb driver.
8) - In command prompt type the following without the quotes "fastboot -i 0x1532 devices" and make sure your device comes up and not just a blank response.
9) - If it came up now just type without the quotes "fastboot -i 0x1532 flashing unlock"
10) - This will bring up a prompt on the phone itself to unlock the bootloader, use the volume button to navigate to yes and press the power button to confirm.
11) - The phone will reboot and will show a message stating "Your device is unlocked and cannot be trusted" on each boot to show that it is unlocked."
FIX - it was the "fastboot -i 0x1532 devices" I was doing wrong.. I was not putting the "-I 0x1532" i now feel stupid.. but idc i locked my phone and im back to stock finally! (ill probably end up trying to root it again some point in the future :| )
Related
Hi all,
I got a refurb 8.9 HD for basically free, so I want to flash the best current ROM onto it (which it looks like is CM11 at the moment). I'm having a bit of trouble getting the device into fastboot mode:
What I've accomplished so far:
Have adb and fastboot working in the command prompt
Installed the amazon usb drivers, kindle shows as Android Composite ADB Interface in device manager
Device is recognized by adb devices (shows serial number + "device")
Turned "Enable ADB" to ON in security settings
However, when I unplug the kindle, execute the "fastboot -i 0x1949 getvar product" command, I do get the <waiting for device> message, but when I plug in the turned-off Kindle, I get two quick chimes, then a second later the "device disconnected" sound, then the kindle boots as normally, and nothing happens in the command prompt.
It may be worth noting that when I first connected the Kindle (after installing drivers) I didn't get the "Enable USB Debugging" pop-up that two guides mentioned. Thoughts?
You must be doing it in the wrong order
1. turn of your kindle
2. connect your wire
3. open cmd and type fastboot -i 0x1949 getvar product
now it should show
< waiting for device >
4. now turn on your device it should go into fastboot
Did you get it to work? And are you running 8.5.1? Because that's what I'm running and I'm having the same problem. I've seen solutions all over the place for 8.4, nothing for 8.5. Amazon seems to have a real lockdown on it.
I have somehow installed the fastboot drivers for my Pixel C (although ADB still doesn't work), and have successfully (?) unlocked the bootloader.
If I try to flash either the newest bootloader in order to install the N Developer Preview or a TWRP image, I get the following message:
FAILED (command write failed (No such device or address))
Click to expand...
Click to collapse
I tried different USB ports but the result was the same. I found somewhere about fwtool, but in order to use that I have to be rooted (if I understood correctly).
Any other ideas?
_Raziel666 said:
I have somehow installed the fastboot drivers for my Pixel C (although ADB still doesn't work), and have successfully (?) unlocked the bootloader.
If I try to flash either the newest bootloader in order to install the N Developer Preview or a TWRP image, I get the following message:
I tried different USB ports but the result was the same. I found somewhere about fwtool, but in order to use that I have to be rooted (if I understood correctly).
Any other ideas?
Click to expand...
Click to collapse
I'm assuming that since you were able to "successfully" unlock the bootloader that you can do this to check and see if your PC still recognizes your device. So, while you have you're Pixel C in fastboot and have it connected to your PC, open a command prompt and type the words fastboot devices and see if it returns your device serial number. Normally the command prompt will show that message when your device is not properly connected with the correct drivers installed. Also, if you have the correct drivers installed your ADB should work if you have enabled USB Debugging in developer options.
Sent from my Nexus 6 using XDA-Developers mobile app
Well, fastboot devices (and all fastboot commands) works. As for ADB it shows my device, but says unauthorized and never asks for my authorization.
But the thing is that I cannot flash anything.
_Raziel666 said:
Well, fastboot devices (and all fastboot commands) works. As for ADB it shows my device, but says unauthorized and never asks for my authorization.
But the thing is that I cannot flash anything.
Click to expand...
Click to collapse
Okay. If it will recognize fastboot commands let's start over from the beginning. Go to developer options and verify OEM Unlocking is checked and USB Debugging is checked. If you have the correct ADB drivers installed you will receive a pop-up message that says "This computers RSA key fingerprint is xxxxxxxxx. Check the box to always allow. Next, boot to the bootloader and type fastboot devices in a command prompt window. If it returns your device serial number then we are good to go.
Next, open a command prompt window and type fastboot flashing unlock. (may have to use fastboot OEM unlock) I've seen both work for some reason. If you are successful your Pixel will give you a message saying the bootloader is unlocked and OS verification is off. Once it's complete it will boot into the bootloader again. Once this happens, boot normally and hurry through the setup wizard so you can enable developer options and enable USB Debugging.
Now, once this is done boot to the bootloader and open another command prompt window and type fastboot devices to verify you are connected. If you are connected then you can fastboot flash the Android"N" bootloader and install the developer preview. Lemme know how you make out.
If you want to chat over Hangouts my email is [email protected].
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
Okay. If it will recognize fastboot commands let's start over from the beginning. Go to developer options and verify OEM Unlocking is checked and USB Debugging is checked. If you have the correct ADB drivers installed you will receive a pop-up message that says "This computers RSA key fingerprint is xxxxxxxxx. Check the box to always allow. Next, boot to the bootloader and type fastboot devices in a command prompt window. If it returns your device serial number then we are good to go.
Next, open a command prompt window and type fastboot flashing unlock. (may have to use fastboot OEM unlock) I've seen both work for some reason. If you are successful your Pixel will give you a message saying the bootloader is unlocked and OS verification is off. Once it's complete it will boot into the bootloader again. Once this happens, boot normally and hurry through the setup wizard so you can enable developer options and enable USB Debugging.
Now, once this is done boot to the bootloader and open another command prompt window and type fastboot devices to verify you are connected. If you are connected then you can fastboot flash the Android"N" bootloader and install the developer preview. Lemme know how you make out.
If you want to chat over Hangouts my email is [email protected].
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks for the very descriptive post. The thing is that I have already done all that, with the exception of using ADB, the pop-up never appeared and my Pixel C appears as unauthorized in adb devices.
I know for a fact that the bootloader is unlocked, because everything got wiped afterwards, and I also get the message saying that the bootloader is unlocked in every boot.
The thing is I cannot flash neither the developer preview nor the TWRP image. I read somewhere about a similar thing some users had on Pixel C, but the solution was to either do something via TWRP or use fwtool that needs root. And I can do neither.
So that's why I started this topic to see if anyone can think of anything else.
Sent from my A0001 using Tapatalk
On thing to try is to go into the settings Developer Options and "revoke USB debugging authorization". Connect to PC and you should then be asked to allow the "fingerprint". Hopefully that will fix it. I assume you've tried changing the connection type - charging, File transfer etc. If you are using W10 Pro then you may have driver issues. There are many posts on the net about that os and Google's driver but I've yet to find a definitive answer, I now use a USB C card see http://forum.xda-developers.com/pixel-c/help/windows-10-pixel-c-type-c-ports-t3414423
Hi.
Trying to flash a ROM to a Nexus 5X.
I have enabled OEM unlocking and USB debugging.
When I enter the command 'fastboot flashing unlock', I get '< waiting for device >' and it just stays there for ever and ever and ever.
I think this is happening because the computer isn't detecting the phone in bootloader mode. When the phone is on, in the normal Android state, my computer lists it when I type 'adb devices'. But when I put the phone in bootloader mode and type 'adb devices', nothing comes up.
Do I need to install different drivers?
Thanks.
Hiltil said:
Hi.
Trying to flash a ROM to a Nexus 5X.
I have enabled OEM unlocking and USB debugging.
When I enter the command 'fastboot flashing unlock', I get '< waiting for device >' and it just stays there for ever and ever and ever.
I think this is happening because the computer isn't detecting the phone in bootloader mode. When the phone is on, in the normal Android state, my computer lists it when I type 'adb devices'. But when I put the phone in bootloader mode and type 'adb devices', nothing comes up.
Do I need to install different drivers?
Thanks.
Click to expand...
Click to collapse
Replying to my own thread to say I figured it out
Although 'adb devices' didn't show the phone, 'fastboot devices' did
The problem wasn't that the computer wasn't seeing the phone; it was that I'd been using the wrong command. 'fastboot flashing unlock' didn't work, but 'fastboot oem unlock' did
You must reinstall fastboot drivers on computer.
I am trying to root LG G4 H811 (Tmobile).
I downloaded LGMobileDriver_WHQL_Ver_4.2.0.exe from LG web site and installed.
I enabled debug on phone.
Download and unzipped latest platform-tools-latest-windows (adb and fastboot) from https://developer.android.com/studio/releases/platform-tools.html
When I connect phone to laptop via USB and run adb devices, i see my phone
When i run "adb reboot bootloader" the phone does not boot into boot loader, but reboot normally.
So I powered off phone. Pressed up vol and connected USB. The phone shows "Download".
Now when I run fastboot devices, fastboot does not see the phone.
Please help me root my phone. I have tried this on two laptops, same result. Also I have tried USB2.0 and USB3.0 ports same result (fastboot cannot see the phone).
What else I can try?
Thanks
you must enable "Enable OEM Unlock" in the same menu of "USB Debug", then you can use "adb reboot bootloader".
Thank you, thank you, thank you. That did the trick. "adb reboot bootloader" is working and fastboot is able to see the phone.
Hello,
I've been trying for the past several hours to unlock the bootloader of my Moto Z2 Play (model:XT1710-09) by following different tuturials but fastboot don't seem to detect my phone, no matter what i do.
Nothing happens when i type “fastboot devices” in the command window.
I've noticed that my phone appear in the device manager in "other devices" as "Fastboot albus S" when it is in bootloader mode, which doesn't seems normal.
Edit: Some additional info: -i am on windows 10 pro
-ADB detect the phone whit no problem but Fastboot doesn't
-when connected with usb debugging enabled, windows detect it as "ADB interface" (which seems normal) and use "C:\\WINDOWS\system32\DRIVERS\winusb.sys" as driver (which seems less normal to me, i may be wrong)
-i tried installing Motorola specific drivers but i only found MotorolaDeviceManager, which doesn't seem to do anything, and no way to download the drivers manually
Edit 2: I still don't know why i can't get it to work on windows but i just managed to do it using a linux bootable usb, my device is unlocked \o/
If anyone know why fastboot doesn't wok on my windows and how to get it to work, i'm still interested