Ok ive spent the last 2 hours trying to unlock my bootloader on my lg-h901. Ive done everything from adb to nexus root toolkit. Ive installed every lg samsung google and universal driver rebooted my computer and everything. I can reboot my device using adb and it shows adb devices connected. When i type fastboot oem unlock it stays on waiting for device for ever. What am i doing wrong?
dillonorden said:
Ok ive spent the last 2 hours trying to unlock my bootloader on my lg-h901. Ive done everything from adb to nexus root toolkit. Ive installed every lg samsung google and universal driver rebooted my computer and everything. I can reboot my device using adb and it shows adb devices connected. When i type fastboot oem unlock it stays on waiting for device for ever. What am i doing wrong?
Click to expand...
Click to collapse
Could be a bad cable.. Do you have OEM unlock checked in developer options.
Wait.... Are you typing fastboot oem unlock when connected to ADB? Because you need to be connected to Fastboot in the bootloader, not ADB in the OS to do an unlock
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! ?
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.
Hi guys,
Urgent help needed.
I got fedup from last 4 days trying to Unlock bootloader of my Redmi Note 3 Snapdragon (Kenzo). While unlocking bootloader getting error at 50% "Couldn't verify device (Not connected to Mi Phone)". Earlier I never faced this issue as Not connected to Mi Phone.
In August 2016, 1st time I unlocked bootloader officially. And after that more than 10 times I unlocked bootloader of my RN3.
From last 15 days I was using CM13.0, But 4 days ago I flashed Miui 8.0.1.0 via Edl method (Flash all selected), then tried to Unlock bootloader. Got the error "Couldn't verify device (Not connected to Mi Phone)"
Then flashed Miui 8.0.5.0 via Edl method (because unable to unlock bootloader). While unlocking bootloader, got the same error "Couldn't verify device (Not connected to Mi Phone)"
Tools / drivers installed on my Pc:
Mi flash 01.04.2016(64bit)
MiSetup3.2.1.3111_2717 (Mi PC Suite)
Adb driver adb-setup-1.4.3
& Already reinstalled the Adb driver adb-setup-1.4.3
Already searched on MI forum, couln't find any proper answer.
When I ran the same fastboot command (fastboot devices) on Zenfone 5 connected to Pc, it immediately shows Listed device.
But In fastboot mode, when I ran the command "fastboot devices" it shows nothing. [on my Redmi Note 3]
When I ran command "fastboot oem device-info" to check bootloader status, it shows Waiting for device.
Tried every possible way I know, but no success.
Kindly help me in this regard.
Thanks in advance.
Faruque007 said:
Hi guys,
Urgent help needed.
I got fedup from last 4 days trying to Unlock bootloader of my Redmi Note 3 Snapdragon (Kenzo). While unlocking bootloader getting error at 50% "Couldn't verify device (Not connected to Mi Phone)". Earlier I never faced this issue as Not connected to Mi Phone.
In August 2016, 1st time I unlocked bootloader officially. And after that more than 10 times I unlocked bootloader of my RN3.
From last 15 days I was using CM13.0, But 4 days ago I flashed Miui 8.0.1.0 via Edl method (Flash all selected), then tried to Unlock bootloader. Got the error "Couldn't verify device (Not connected to Mi Phone)"
Then flashed Miui 8.0.5.0 via Edl method (because unable to unlock bootloader). While unlocking bootloader, got the same error "Couldn't verify device (Not connected to Mi Phone)"
Tools / drivers installed on my Pc:
Mi flash 01.04.2016(64bit)
MiSetup3.2.1.3111_2717 (Mi PC Suite)
Adb driver adb-setup-1.4.3
& Already reinstalled the Adb driver adb-setup-1.4.3
Already searched on MI forum, couln't find any proper answer.
When I ran the same fastboot command (fastboot devices) on Zenfone 5 connected to Pc, it immediately shows Listed device.
But In fastboot mode, when I ran the command "fastboot devices" it shows nothing. [on my Redmi Note 3]
When I ran command "fastboot oem device-info" to check bootloader status, it shows Waiting for device.
Tried every possible way I know, but no success.
Kindly help me in this regard.
Thanks in advance.
Click to expand...
Click to collapse
Most probably your device is not recognized as a fastboot device.... please ensure that fastboot drivers for your kenzo are installed and not corrupted and if it does not help try on some other PC and don't forget to disable drive signature enforcement
Sent from my Redmi Note 3 using Tapatalk
Resolved
Torshak.mozyora said:
Most probably your device is not recognized as a fastboot device.... please ensure that fastboot drivers for your kenzo are installed and not corrupted and if it does not help try on some other PC and don't forget to disable drive signature enforcement
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
Hi,
Thanks for your helpful reply
Finally unlocked bootloader succesfully. The problem is with adb drivers on my Windows 10 64bit Pc. Earlier I had done with unlocking several times, never faced driver issue on fastboot mode. But from last 4-5 days suddenly my RN3 was not responding to any fastboot commands.
Followed this:
In Device Manager under Kedacom USB Device shows up. Under which, Android Bootloader Interface should be present. Installed minimalist ADB and fastboot (minimal_adb_fastboot_v1.3.1_setup) and right clicked Android Bootloader Interface. Clicked Update Driver Software, browsed computer, and then clicked the option to list driver files already present on my drive. It pulled up a fastboot driver that's an older version than the one I currently have. Installed that and fastboot commands started working again.
Hope this help other users also, who are facing (Not connected to Mi Phone) or Waiting for device when initiate fastboot command like "fastboot oem device-info".
Please close this thread.
Thanks
Faruque007 said:
Hi,
Thanks for your helpful reply
Finally unlocked bootloader succesfully. The problem is with adb drivers on my Windows 10 64bit Pc. Earlier I had done with unlocking several times, never faced driver issue on fastboot mode. But from last 4-5 days suddenly my RN3 was not responding to any fastboot commands.
Followed this:
In Device Manager under Kedacom USB Device shows up. Under which, Android Bootloader Interface should be present. Installed minimalist ADB and fastboot (minimal_adb_fastboot_v1.3.1_setup) and right clicked Android Bootloader Interface. Clicked Update Driver Software, browsed computer, and then clicked the option to list driver files already present on my drive. It pulled up a fastboot driver that's an older version than the one I currently have. Installed that and fastboot commands started working again.
Hope this help other users also, who are facing (Not connected to Mi Phone) or Waiting for device when initiate fastboot command like "fastboot oem device-info".
Please close this thread.
Thanks
Click to expand...
Click to collapse
THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU
Thank you a million times, you allowed me to finally unlock my bootloader. I love you, and I hope you and your children live long and fulfilling lives.
Faruque007 said:
Hi,
Thanks for your helpful reply
Finally unlocked bootloader succesfully. The problem is with adb drivers on my Windows 10 64bit Pc. Earlier I had done with unlocking several times, never faced driver issue on fastboot mode. But from last 4-5 days suddenly my RN3 was not responding to any fastboot commands.
Followed this:
In Device Manager under Kedacom USB Device shows up. Under which, Android Bootloader Interface should be present. Installed minimalist ADB and fastboot (minimal_adb_fastboot_v1.3.1_setup) and right clicked Android Bootloader Interface. Clicked Update Driver Software, browsed computer, and then clicked the option to list driver files already present on my drive. It pulled up a fastboot driver that's an older version than the one I currently have. Installed that and fastboot commands started working again.
Hope this help other users also, who are facing (Not connected to Mi Phone) or Waiting for device when initiate fastboot command like "fastboot oem device-info".
Please close this thread.
Thanks
Click to expand...
Click to collapse
Dude you are my hero, Thank you soo much...
privateriem said:
THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU
Thank you a million times, you allowed me to finally unlock my bootloader. I love you, and I hope you and your children live long and fulfilling lives.
Click to expand...
Click to collapse
Welcome bro
I'm glad and super happy, my method helped you. Enjoy.
Faruque007 said:
Hi,
Thanks for your helpful reply
Finally unlocked bootloader succesfully. The problem is with adb drivers on my Windows 10 64bit Pc. Earlier I had done with unlocking several times, never faced driver issue on fastboot mode. But from last 4-5 days suddenly my RN3 was not responding to any fastboot commands.
Followed this:
In Device Manager under Kedacom USB Device shows up. Under which, Android Bootloader Interface should be present. Installed minimalist ADB and fastboot (minimal_adb_fastboot_v1.3.1_setup) and right clicked Android Bootloader Interface. Clicked Update Driver Software, browsed computer, and then clicked the option to list driver files already present on my drive. It pulled up a fastboot driver that's an older version than the one I currently have. Installed that and fastboot commands started working again.
Hope this help other users also, who are facing (Not connected to Mi Phone) or Waiting for device when initiate fastboot command like "fastboot oem device-info".
Please close this thread.
Thanks
Click to expand...
Click to collapse
Thanks for your help dude finally unlocked and rooted my device
tried all methods but this unlock button remains inactive. please help
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.
This device uses the same command as the Pixel 2 to unlock the bootloader:
Code:
fastboot flashing unlock
So far I have not been able to successfully flash an entire factory image. I tried a single partition, /vendor, with success.
Let us know your results with flashing!
Does it require unlock_critical?
Is there a different set of update fastboot drivers needed to unlock the bootloader? My phone and cord are recognized for adb commands but nothing for fastboot ones? Never mind had to do it from a Windows shell as min fastboot would not work.
Archangel said:
Is there a different set of update fastboot drivers needed to unlock the bootloader? My phone and cord are recognized for adb commands but nothing for fastboot ones? Never mind had to do it from a Windows shell as min fastboot would not work.
Click to expand...
Click to collapse
I ran into the same issue and downloaded the latest platform tools and it unlocked fine. I just had to unplug the phone and replug it in while in fastboot for my laptop to recognize it.
Sent from my Pixel 3 using Tapatalk