I have just picked up an LG V10 which is running the latest T-Mobile firmware. I have been trying to unlock the boot loader for a while now with no luck. I have tried installing numerous drivers and the android sdk with no real luck. I am running Windows 10, and when I try and adb works fine, and let's me reboot to the bootloader but fastboot refused to work. It just does not detect the device in fastboot mode, and if I try "fastboot oem unlock" then I am given a message saying waiting for device no matter what I try.
I have enabled debugging mode And the Oem unlock toggle from developer options as well. Any help would be very appreciated.
theinspector said:
I have just picked up an LG V10 which is running the latest T-Mobile firmware. I have been trying to unlock the boot loader for a while now with no luck. I have tried installing numerous drivers and the android sdk with no real luck. I am running Windows 10, and when I try and adb works fine, and let's me reboot to the bootloader but fastboot refused to work. It just does not detect the device in fastboot mode, and if I try "fastboot oem unlock" then I am given a message saying waiting for device no matter what I try.
I have enabled debugging mode And the Oem unlock toggle from developer options as well. Any help would be very appreciated.
Click to expand...
Click to collapse
Give it a try on some other PC.
Waxim1 said:
Give it a try on some other PC.
Click to expand...
Click to collapse
I should have put this, but I did do this as well with another PC this time on Windows 7 which ended up having the same problem unfortunately.
Related
I have the tmobile lg v10 h901. I'm trying to unlock the boot loader. I have adb and fastboot files installed and the lg drivers. I have the oem. Unlock and usb debugging checked in the setting. I can open the command prompt and use adb devices and it sees my device. I can use adb reboot bootloader and it will take me to the fastboot bootloader unlock screen. From here the command prompt no longer sees my device. I type fastboot oem Unlock and it says waiting on device... Any one have a idea what's going on. Am I missing something?
Try booting into fastboot manually by turning off the phone and holding vol down while plugging it in,then try it but make sure you fastboot devices first to make sure its even detecting it
No that didn't work. When the phone is on adb devices it sees the phone I type fastboot devices and it does nothing. But when the phone goes to fastboot even volume down then plug the phone In it won't recognize the phone just says <waiting on device>
Yeah I keep uninstalling everything and reinstall everything fast boot threw cmd fastboot with the volume button and always get waiting on device when I get to the "fastboot oem Unlock"
So sad ...
Use nexus toolkit for it all. I did. Works great.
Exconvict said:
Use nexus toolkit for it all. I did. Works great.
Click to expand...
Click to collapse
Wugs nexus toolkit ? That will work with the v10?
cwalton4077 said:
Wugs nexus toolkit ? That will work with the v10?
Click to expand...
Click to collapse
I used Mfastboot and it worked like a champ. Could not get nexus toolkit to see my device.
Yes. It boots temp recovery,flashes recovery and root. Also used it to relock the boot loader for sh*ts and giggles. To get it to see my phone I had to download LG bridge on my computer and run it.
I have tried mfastboot and the nexus toolkit and both stop working when it gets to the fastboot oem Unlock. Waiting on device. I have not installed lg bridge so I will try that later and see if that helps.
If you run Windows, you may be missing the USB driver for fastboot. If possible, use Linux where all the USB drivers are included from the start.
I'm having the same problem as well.
cwalton4077 said:
I have tried mfastboot and the nexus toolkit and both stop working when it gets to the fastboot oem Unlock. Waiting on device. I have not installed lg bridge so I will try that later and see if that helps.
Click to expand...
Click to collapse
When starting all of this (essentially becoming addicted to learning rooting) I noticed that no one mentioned to make sure to enable the "usb tethering" option on their device!! Once I did that, an entire plethora of additional options opened up. That being said, this option won't necessarily make rooting possible, but I think it may help out in this particular situation.
? I really hope this works for you.
1500 years ago, everybody "knew" that the earth was the center of the universe. 500 years ago, everybody "knew" that the earth was flat. And 15 minutes ago, you "knew" that humans were alone on this planet. Imagine what you'll "know" tomorrow.
-Kay
I got it working I had to go to device manager on the pc then put the phone in boot loader. Then on device manager the phone changed to Android unknown so I set the drivers to Android adb services and it worked fastboot would see the phone and I got root on the v10
cwalton4077 said:
I got it working I had to go to device manager on the pc then put the phone in boot loader. Then on device manager the phone changed to Android unknown so I set the drivers to Android adb services and it worked fastboot would see the phone and I got root on the v10
Click to expand...
Click to collapse
Glad you got it rooted
Great!
cwalton4077 said:
I got it working I had to go to device manager on the pc then put the phone in boot loader. Then on device manager the phone changed to Android unknown so I set the drivers to Android adb services and it worked fastboot would see the phone and I got root on the v10
Click to expand...
Click to collapse
Now can you post a YouTube vid for us who are still having this issue! ?
Hey all,
So Ive tried to unlock my bootloader but its not working, ive followed the steps from this site to unlock it but its stuck on the unlock bootloader screen. I have two options to choose from yes or no I click yes but it doesnt work, yet I click no and it takes me back to choose from fastboot, recovery and normal. My phone is a Alcatel Pixi 4.
I have enabled developer mode enabled usb debugging. I also have confirmed the RSA fingerprint for the computer. Also I have enabled OEM unlock in dev settings. This is what my cmd prompt window loooks like. I will also take a photo of my alcatel frozen on bootloader screen.
C:\Users\Dan\AppData\Local\Android\android-sdk\platform-tools>adb devices
List of devices attached
5HQGTCEQCAVS7TTS device
C:\Users\Dan\AppData\Local\Android\android-sdk\platform-tools>adb reboot-bootloader
C:\Users\Dan\AppData\Local\Android\android-sdk\platform-tools>fastboot oem unlock
...
This is what my phone looks like that im stuck on.
https://s11.postimg.org/8e2cjxooj/IM...129_172555.jpg
does anyone know why this is happening or know how to fix?
Issue has been solved as the bootloader is unlocked this process is not necessary.
My Z5 compact was updated to Nougat using the OTA service.
The bluetooth integration to my car stopped working and I read that this was a noted problem I decided to flash my phone back to Marshmallow.
I'd installed custom ROMs on previous HTC phones following info from XDA so was pretty confident.
After following the Sony guidelines and obtaining my unlock key I am unable to get it to work in fastboot mode.
I suspect that it is a USB problem at one end or another.
If I connect up the phone to the PC using the original lead I can find it using adb devices and the device is showing up as error free "Sony sa0113 ADB Interface Driver" in Windows 10 device manager.
However the phone isn't charging and I can't get it into Fastboot by holding the up vol key and plugging in the USB lead.
I can get a black screen with the blue led by running adb reboot bootloader and the phone is recognised from fastboot devices but when I try to unlock the bootloader I get an error:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0fce oem unlock 0xB4D9AxxxxC359F2C
...
FAILED (remote: Command did not succeed)
finished. total time: 0.042s
Any help appreciated.
PhilG57 said:
My Z5 compact was updated to Nougat using the OTA service.
The bluetooth integration to my car stopped working and I read that this was a noted problem I decided to flash my phone back to Marshmallow.
I'd installed custom ROMs on previous HTC phones following info from XDA so was pretty confident.
After following the Sony guidelines and obtaining my unlock key I am unable to get it to work in fastboot mode.
I suspect that it is a USB problem at one end or another.
If I connect up the phone to the PC using the original lead I can find it using adb devices and the device is showing up as error free "Sony sa0113 ADB Interface Driver" in Windows 10 device manager.
However the phone isn't charging and I can't get it into Fastboot by holding the up vol key and plugging in the USB lead or by running adb reboot fastboot
If feels like I haven't go the fastboot USB drivers but I can't see how or where I can add them.
Any help appreciated.
Click to expand...
Click to collapse
Disable driver signature enforcement then reinstall sony drivers
tapiwasam said:
Disable driver signature enforcement then reinstall sony drivers
Click to expand...
Click to collapse
Thanks. I think I am OK there because I accepted the drivers from an unverified source during installation.
Also I can see the phone with both adb devices and fastboot devices
However when I run adb reboot bootloader the phone reboots but comes up with a blank screen with the blue led.
adb reboot bootloader just goes into bootloader mode and not fastboot mode which is needed to unlock it. Go directly into fastboot by typing adb reboot fastboot
Then when your phone led is flashing blue, run your fastboot "oem unlock" command.
Saw now that you already tried that sorry about that.
Tried running cmd with admin privileges to see if that shows any difference?
Also from sony:
Please note! It will only be possible to unlock the boot loader for certain releases. You can check if it is possible to unlock the boot loader of your device in the service menu by following the steps below:
In your device, open the dialler and enter *#*#7378423#*#* to access the service menu.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
Click to expand...
Click to collapse
PhilG57 said:
My Z5 compact was updated to Nougat using the OTA service.
The bluetooth integration to my car stopped working and I read that this was a noted problem I decided to flash my phone back to Marshmallow.
I'd installed custom ROMs on previous HTC phones following info from XDA so was pretty confident.
After following the Sony guidelines and obtaining my unlock key I am unable to get it to work in fastboot mode.
.... snip....
Click to expand...
Click to collapse
You don't need to unlock your bootloader to simply downgrade to official MM! Just use flashtool to flash the appropriate MM ftf. There are plenty guides available on XDA and elsewhere.
I'm lost in your explanation.
You wanted to unlock your bootloader to be able to downgrade your phone? That's right? And it's fine to me, but you don't need to do that if you don't feel like. Unlocking your bootloader is nog necessary to downgrade to MM via flashtool.
So you tried to unlock your bootloader. But what you write what happened afterwards is completely unclear to me, because it contradicts itself.
-->> "Also I can see the phone with both adb devices and fastboot devices"
Fine. This means your connected with your phone and fastbook recognizes your phone. So bootloader is unlocked and software to control that works fine.
-->> "However when I run adb reboot bootloader the phone reboots but comes up with a blank screen with the blue led."
Fine, so you unlocked your bootloader, and rebooted in fastboot.
-->> Obviously. It's an unlocked bootloader, you can double unlock it or something like that. You can relock it if you want (which doesn't make any difference for what you want to do) but that's a different method.
Is there any reason that you absolutely need to a second method to enter fastboot mode? Or any fastboot mode? It could be possible with another kernel, but I don't see the point to flash another kernel. I would just leave it like it is.
PhilG57 said:
Thanks. I think I am OK there because I accepted the drivers from an unverified source during installation.
Also I can see the phone with both adb devices and fastboot devices
However when I run adb reboot bootloader the phone reboots but comes up with a blank screen with the blue led.
Click to expand...
Click to collapse
that is notmal behaviour, that is fastboot mode, indicated by that blue LED
Thanks for the clarification that I don't need to unlock the bootloader to downgrade using flashtool. What I didn't say was that I couldn't reinstall Nougat using the Sony tool software restore option or get anywhere with flashtool because the phone won't go into the blue led mode by inserting the USB and holding the up vol button. I did try running flashtool in one window and the command line tools in another with the idea of running flashtool first and then unplugging the phone and replugging it to use command line to get the blue LED state, but that doesn't work because the command line tools can't see the phone once flashtool is running and has addressed the phone.
From what i read, i assume you are on nougat and want to go back to MM, right?
So you would need flashmode instead of fastboot mode.
You get there with holding Vol down button and plugging in USB cable on turned off phone.
Flashmode also shows a green notification light instead of the blue one.
If you having Problems to get there, please check following:
make sure to have latest version of flashtool installed http://www.flashtool.net/downloads.php
install drivers from your flashtool\drivers folder
don't use an USB 3.0 port or cable(have heard of some people having trouble with)
PhilG57 said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0fce oem unlock 0xB4D9AxxxxC359F2C
...
FAILED (remote: Command did not succeed) <- this
finished. total time: 0.042s
Any help appreciated.
Click to expand...
Click to collapse
OP, I had the exact same problem as you. At the time I tried absolutely everything but never found the culprit. So after several months I actually succeeded today
This is the guide I followed - https://forum.xda-developers.com/z5-compact/general/guide-how-to-root-z5c-painful-using-t3549388 and it worked perfectly.
A few pointers:
- Go to the service menu (*#*#SERVICE#*#*) before you begin, before you turn OEM Unlocking ON from Dev Options .
- Take note of what it says in Configuration and Firmware.
- Now enable OEM Unlocking and take note again, it should say stuff like Model Number: Unknown and other unknown stuff.
- Reboot - IMPORTANT.
- Use the guide I gave you and you will be fine, it took me ages to find a solution but now I'm on MM and rooted
Hope I helped :fingers-crossed::fingers-crossed::fingers-crossed:
At first, I installed the Windows 10 drivers and the first time I put my phone in Fastboot & Rescue mode it showed up on the ADB and I could unlock the bootloader, then I wanted to install TWRP but now the device doesn't show up anymore in the bootloader mode... Any ideas? I also tried Ubuntu with no success But I can clearly see it in the device manager.
What does the command "fastboot devices", when in fastboot obviously, return?
Estatus del problema
Hi i have the same problem can you to resolve it???
m4xxi said:
At first, I installed the Windows 10 drivers and the first time I put my phone in Fastboot & Rescue mode it showed up on the ADB and I could unlock the bootloader, then I wanted to install TWRP but now the device doesn't show up anymore in the bootloader mode... Any ideas? I also tried Ubuntu with no success But I can clearly see it in the device manager.
Click to expand...
Click to collapse
I got to the fastboot screen on my ZTE K87CA tablet, but when I try to type the command "fastboot flashing unlock" or "fastboot oem unlock", it just shows "waiting for devices". I have searched quite a bit over the web but I have not found a post where someone actually was able to unlock the bootloader on this device.
This is my first time rooting a device
I am trying to find ways to speed up this tablet and free up ram and stuff and rooting the device seemed to be necessary.
If you have answers to my problem please say so.
Coke3 said:
I got to the fastboot screen on my ZTE K87CA tablet, but when I try to type the command "fastboot flashing unlock" or "fastboot oem unlock", it just shows "waiting for devices". I have searched quite a bit over the web but I have not found a post where someone actually was able to unlock the bootloader on this device.
This is my first time rooting a device
I am trying to find ways to speed up this tablet and free up ram and stuff and rooting the device seemed to be necessary.
If you have answers to my problem please say so.
Click to expand...
Click to collapse
Have you enabled OEM unlock in stock rom developer options first with stock rom booted?
Also when device is in bootloader type fastboot devices to see if it is registering your device. If it isn't try getting latest fastboot tools from Android sdk and turning off secure boot if you are on windows 11.
toolhas4degrees said:
Have you enabled OEM unlock in stock rom developer options first with stock rom booted?
Also when device is in bootloader type fastboot devices to see if it is registering your device. If it isn't try getting latest fastboot tools from Android sdk and turning off secure boot if you are on windows 11.
Click to expand...
Click to collapse
I did all the developer settings like usb debugging and and oem unlock.
When the tablet was on normally running, I did "adb devices" and it showed my tablet, but when it was in fastboot mode I did "fastbook devices" and it didn't show anything.
I think I might have thought of something though. When I downloaded the the usb drivers or something; I downloaded the K87CC instead of the K87CA because I couldn't find one for it so that might be the problem
Look into turning off secure boot if using windows 11, and download latest fastboot sdk package
I'm kind of new to this and don't really know where to download all this stuff. could you send me a link?
Not sure if this is the right place to ask this question, but, have you had any chance to find and install any custom rom in ZTE K87CA? My tablet has become extremely slow and I would like to install something lighter.
thanks.