I Just got my V60 on EIP today from TMO, the oem switch was able to be toggled out the box after setup with my sim in it already. When i got home i made an LG Dev account and tried the steps but you can't access the bootloader, I was however able to type in cmd "adb reboot fastboot" which lead me to fastbootd and unable to get my device ID. So where do we go from here?
I couldn't even get to fastboot. It takes just restarted to the system.
matteosaeed said:
I couldn't even get to fastboot. It takes just restarted to the system.
Click to expand...
Click to collapse
Mine definitely reboots to "fastbootd" when i type adb reboot fastboot every time... I find it weird OEM unlock could be toggled out of box but i cant enter bootloader to unlock this phone
Some_Ghost said:
Mine definitely reboots to "fastbootd" when i type adb reboot fastboot every time... I find it weird OEM unlock could be toggled out of box but i cant enter bootloader to unlock this phone
Click to expand...
Click to collapse
Yeah since the G6, same thing. I did a thread back in the day, it even allowed you to do fastboot oem unlock but that didn't do anything.
matteosaeed said:
Yeah since the G6, same thing. I did a thread back in the day, it even allowed you to do fastboot oem unlock but that didn't do anything.
Click to expand...
Click to collapse
So do you think right now we are **** out of luck for unlocking our bootloader?
Some_Ghost said:
So do you think right now we are **** out of luck for unlocking our bootloader?
Click to expand...
Click to collapse
Yeah, I am going to return the phone. Screw LG. I'll wait for oneplus
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! ?
Hello
How to Relock bootloader for huawei mate 10 lite RNE-L21C185
Thanks
any answer
If it's anything like Mate 10 Pro, get into bootloader using adb or phones physical keys, confirm phone is connected to pc using 'fastboot devices' cmd, then type fastboot oem relock unlock_number. The unlock_number will be the number you used to unlock the bootloader in the first place.
Wezi said:
If it's anything like Mate 10 Pro, get into bootloader using adb or phones physical keys, confirm phone is connected to pc using 'fastboot devices' cmd, then type fastboot oem relock unlock_number. The unlock_number will be the number you used to unlock the bootloader in the first place.
Click to expand...
Click to collapse
Thank you for your answer i'm doing every think but at the end the mobile don't do the reset and stay
at the recovery page
Can you detail the steps you have taken, be a precise as possible. What do you mean you have tried everything?
chimere2016 said:
Thank you for your answer i'm doing every think but at the end the mobile don't do the reset and stay
at the recovery page
Click to expand...
Click to collapse
I have the same problem
Adrian2207 said:
I have the same problem
Click to expand...
Click to collapse
Have you found any solution for that issue?
My state:
Booloader: Unlocked
FRP Locked:
No OS booting (bootloop)
No TWRP recovery...
Action: Relock Bootloader
Fastboot - Command not Allow
fresh ideas. are needed...
Wezi said:
If it's anything like Mate 10 Pro, get into bootloader using adb or phones physical keys, confirm phone is connected to pc using 'fastboot devices' cmd, then type fastboot oem relock unlock_number. The unlock_number will be the number you used to unlock the bootloader in the first place.
Click to expand...
Click to collapse
Thanks mate, that kind of worked for me on my P20 Pro !!!
In bootloader mode it now reports Relocked and FRP as Unlocked. Not sure how to get FRP as Locked as 'm not sure what that relates too.
sudman said:
Thanks mate, that kind of worked for me on my P20 Pro !!!
In bootloader mode it now reports Relocked and FRP as Unlocked. Not sure how to get FRP as Locked as 'm not sure what that relates too.
Click to expand...
Click to collapse
Just boot phone and in developer options unmark enable OEM unlock.
So now i too am stuck at the recovery page and it will not boot any further.....any ideas?
Hey all i dont know what the deal is but ive got an lg g5 that just will not boot to the bootloader. I've tried factory resetting it and all the methods to get to bootloader just reboots the phone fully. Adb reboot booloader, key combos, nothing seems to work. Any ideas??
First, connect your smartphone with your PC; plug in the USB cord in order to establish the connection.
On your computer access the Android SDK folder.
From there open a command prompt window: press and hold the Shift keyboard key while right clicking on any blank space.
Next, in the cmd window type “adb reboot bootloader” and wait while the bootloader mode is displayed on your smartphone
That's basically what I did and worked first time..make sure the adb and fastboot package is installed and open the command window from that folder
russy23 said:
First, connect your smartphone with your PC; plug in the USB cord in order to establish the connection.
On your computer access the Android SDK folder.
From there open a command prompt window: press and hold the Shift keyboard key while right clicking on any blank space.
Next, in the cmd window type “adb reboot bootloader” and wait while the bootloader mode is displayed on your smartphone
That's basically what I did and worked first time..make sure the adb and fastboot package is installed and open the command window from that folder
Click to expand...
Click to collapse
Did all that.. I mean I've flashed custom recoveries and roms to other phones before and never really had a problem i couldn't google..this has me stumped. It simply refuses to even access the bootloader.
If it helps it was a koodo phone and is running the latest official patch from lg on nougat. The only thing i could find online was that sprint supposedly removed all access to the bootloader on theirs, but i cant find any real info on that either. It reboots when i send the adb reboot bootloader but its like fastboot just isn't there..?? It reboots right back to the android home screen. Ive tried all possible key combos as well... Ugh
Which model is it..mines the h850
Ive got the h831
I think I've sort of answered my own question. From browsing the forums it appears the Canadian variant has the bootloader locked down and inaccessible, which would explain a lot..lol.. I really hate when this kind of thing is done to the consumer...ugh. Back to xiaomi i guess lol
bproulx said:
... has the bootloader locked down and inaccessible, which would explain a lot..lol.. I really hate when this kind of thing is done to the consumer...ugh. Back to xiaomi i guess lol
Click to expand...
Click to collapse
Interesting - my xianomi hat an locked bootloader and i had to ask for permission (for the phone I bought!) to unlock the bootloader.
LG is also locked, but the unlocking procedure is way easier.
logg.sar said:
Interesting - my xianomi hat an locked bootloader and i had to ask for permission (for the phone I bought!) to unlock the bootloader.
LG is also locked, but the unlocking procedure is way easier.
Click to expand...
Click to collapse
Unless you're from Canada apparently ..lol
I flashed havoc os had some issues , tried restoring from my backup, got caught in a bootloop so i used lgup to flash a kdz and it worked.but now my enable oem unlock is turned off and it is greyed out. What can i do.
Mohammedbi said:
I flashed havoc os had some issues , tried restoring from my backup, got caught in a bootloop so i used lgup to flash a kdz and it worked.but now my enable oem unlock is turned off and it is greyed out. What can i do.
Click to expand...
Click to collapse
The same thing happens to me, I have not found much info about this, I hope you can help us.
Mohammedbi said:
I flashed havoc os had some issues , tried restoring from my backup, got caught in a bootloop so i used lgup to flash a kdz and it worked.but now my enable oem unlock is turned off and it is greyed out. What can i do.
Click to expand...
Click to collapse
I already found the solution, but it will erase your data.
with the adb commands you must restart the device in boorloader mode:
adb reboot bootloader
Then when I take you to the bootloader screen what you have to write next:
fastboot oem lock
(Remember the phone will be erased)
then to restart the device you have to:
fastboot reboot
And the device will reboot.
what you do is lock it, so that you can then unlock it in a simple way.
(If you do not know what the ADB is, warn man), I hope it helps you and those who enter here too :good:
@l3dson: Be careful before relocking the bootloader: The phone MUST be 100% stock or you will have a brick.
@Mohammedbi: Your bootloader is still unlocked, even after flashing the KDZ. It's just the newly flashed ROM doesn't know it, and you don't need it to.
Just go to fastboot (PowerOff, Vol- while plugging in cable) and flash TWRP. Follow ChazzMatt's root guide for the initial TWRP steps.
Have anyone found the solution for this problem...
vino90m said:
Have anyone found the solution for this problem...
Click to expand...
Click to collapse
What exactly is not working?
ADB doesn't require Enable OEM Unlock to be set. Just plug it in and ADB away - unless drivers or cable or port aren't working.
And your bootloader is still unlocked if it was unlocked before you flashed stock Oreo. You should be able to enter fastboot using the steps described in the post just before yours.
Edit: Of course you have to enable USB debugging in order to use ADB. I'm sure you knew that
l3dson said:
I already found the solution, but it will erase your data.
with the adb commands you must restart the device in boorloader mode:
adb reboot bootloader
Then when I take you to the bootloader screen what you have to write next:
fastboot oem lock
(Remember the phone will be erased)
then to restart the device you have to:
fastboot reboot
And the device will reboot.
what you do is lock it, so that you can then unlock it in a simple way.
(If you do not know what the ADB is, warn man), I hope it helps you and those who enter here too :good:
Click to expand...
Click to collapse
hey i have this same problem and been asking around... but the adb reboot command will not work because it says the phone must be "enabled oem unlock" mode before you can use adb commands... which is greyed out..so back to square one... how to enable it?? any suggestions on this??
Hello everybody,
My phone's battery died and I charged it. When I tried to turn it on, I saw this screen. I've tried clicking on the options but it's stuck in a loop and I don't understand what's happening.
If anyone has experienced this issue before, I'm reaching out for your help. Please assist me.
Flashing factory firmware in fastboot might be the only option. Doing such will wipe everything on your device though!
aimsjahan said:
Flashing factory firmware in fastboot might be the only option. Doing such will wipe everything on your device though!
Click to expand...
Click to collapse
Can't fastboot anything with a locked bootloader.Android flash tool might be the best way
sylveride08 said:
Hello everybody,
My phone's battery died and I charged it. When I tried to turn it on, I saw this screen. I've tried clicking on the options but it's stuck in a loop and I don't understand what's happening.
If anyone has experienced this issue before, I'm reaching out for your help. Please assist me.
Click to expand...
Click to collapse
Since your bootloader is locked the only way to flash the OS is to sideload the Full OTA via ADB or use Pixel Flasher to sideload it. If you happen to have OEM Unlocking enabled in Developer Options you can use Android Flash Tool as that will unlock your bootloader as long as OEM Unlocking is enabled. If it isn't, sideloading the OTA will be the only way to reinstall your OS to hopefully get you out of this.
shoey63 said:
Can't fastboot anything with a locked bootloader.Android flash tool might be the best way
Click to expand...
Click to collapse
Oops! You are right, mate.
Hello so I am stuck here
When I go to Android Flash Tool it's says :
"Device Unlock DisabledFor security reasons, you need to enable "OEM unlocking" in order to flash your device. "
And when I tape in CMD the command "faastboot falshing unlock" it says
"FAILED (remote: 'flashing unlock is not allowed')
fastboot: error: Command failed"
Is there a way to unlock the devices states I have seen a video when
when a guy is using a unlock.bin he download at LG offcial site. Does Google have an alternative where can I download this type of file for my Pixel 6.
Google doesn't have an alternative. If you can't flash the OTA, and apparently you can't because OEM unlocking wasn't enabled in developer options, you need to get a hold of Google and explain your situation to them. You'll likely have to send it back to them, if able to do so.
You can't enable OEM unlock by fastboot/recovery.
Can you boot into recovery?
If yes, then this is your only way out!
Link
Use image of OTA, not Full!
aimsjahan said:
You can't enable OEM unlock by fastboot/recovery.
Can you boot into recovery?
If yes, then this is your only way out!
Link
Use image of OTA, not Full!
Click to expand...
Click to collapse
Unfortunately, it is not possible as my phone is showing that it is locked and I am unable to access the settings to unlock the OEM, since I am stuck in fastboot mode. Guess it's dead only if there is a way to unlock the OEM without going to setting.
sylveride08 said:
Unfortunately, it is not possible as my phone is showing that it is locked and I am unable to access the settings to unlock the OEM, since I am stuck in fastboot mode. Guess it's dead only if there is a way to unlock the OEM without going to setting. View attachment 5885311
Click to expand...
Click to collapse
You misunderstood!
You don't get to do anything from fastboot with OEM locked.
I asked if you can enter RECOVERY mode?
If yes, then visit the link I shared.
btw, why on earth you are flashing 'adb'?
aimsjahan said:
You misunderstood!
You don't get to do anything from fastboot with OEM locked.
I asked if you can enter RECOVERY mode?
If yes, then visit the link I shared.
btw, why on earth you are flashing 'adb'?
Click to expand...
Click to collapse
Unfortunately, when I go into recovery mode, it keeps looping back to the original screen in an infinite loop.
I lost hope and went to a repair shop, but they told me to contact Google. The customer service will send me a package to return my phone. I didn't know that the OEM was so important, I will activate it next time. Tanks for your helps ...