Database Info

fastboot oem unlock is not working

I try to fastboot oem unlock; but it doesn't say anything.
it's screen never change................
even i turn on 1 day. it wan not happen anything.
also, i try to change rom by odin.;
but also, odin didn't reposnd or any change at screen??
Anybody have same problem? or can be solve this problem??
thanks.

Do you get to the bootloader screen on your phone? Are you drivers recognized? Check the Windows device manager. Reinstall the drivers and make sure they are correct and recognized. What guide are you following and what version of the phone (see Hardware variants) are you using?

my phone doesn't woking..T.T
when i turn on the phone only shows google logo, so i going to recovery mode then connect computer then type fastboot oem unlock then phone screen shows up bootloader screen.
BUT, when i choose bootloader screen to "YES" then phone never change..T.T

Do u have the android sdk installed on your computer
Sent from my Google Nexus S 4G using xda premium

die4you said:
my phone doesn't woking..T.T
when i turn on the phone only shows google logo, so i going to recovery mode then connect computer then type fastboot oem unlock then phone screen shows up bootloader screen.
BUT, when i choose bootloader screen to "YES" then phone never change..T.T
Click to expand...
Click to collapse
recovery mode and bootloader are 2 different things ...
push volumen+ and power button about 5 seconds , you should go into bootloader
if you were able to get in recovery , you should have been through bootloader
connect to your PC when you are in bootloader , install driver and then type that command

yes, i installed sdk my computer. but still not working.
even i download PDA program for android driver. BUT STILL NO LUCK,.
Esteway.619 said:
Do u have the android sdk installed on your computer
Sent from my Google Nexus S 4G using xda premium
Click to expand...
Click to collapse

i did puch volum + and power button; then phone going to recovery mode then i connect the phone to computer.
Then I can go to boorloader mode from pc command mode type"fastboot oem unlock"
but screen shows nothing. T.T
qtwrk said:
recovery mode and bootloader are 2 different things ...
push volumen+ and power button about 5 seconds , you should go into bootloader
if you were able to get in recovery , you should have been through bootloader
connect to your PC when you are in bootloader , install driver and then type that command
Click to expand...
Click to collapse

=] go into my topic thread and follow the guide I posted... ^_^ its easy .. =] but view the YouTube video from the PC
Sent From In between Your Moms Boobies

die4you said:
i did puch volum + and power button; then phone going to recovery mode then i connect the phone to computer.
Then I can go to boorloader mode from pc command mode type"fastboot oem unlock"
but screen shows nothing. T.T
Click to expand...
Click to collapse
wait a second ...
vol+ and power ---> you just directly go to recovery mode ??????
you didn't / don't have to do anything it just directly go to recovery ???

qtwrk said:
wait a second ...
vol+ and power ---> you just directly go to recovery mode ??????
you didn't / don't have to do anything it just directly go to recovery ???
Click to expand...
Click to collapse
NONO, my mistake...
vol+ and power going to fastboot mode...
then phone connect to computer by usb.
after type fastboot oem unlock at command mode....
NOTHING HAPPEN...T.T

YourMainDude said:
=] go into my topic thread and follow the guide I posted... ^_^ its easy .. =] but view the YouTube video from the PC
Sent From In between Your Moms Boobies
Click to expand...
Click to collapse
Where???
Show the link.............

http://forum.xda-developers.com/showthread.php?t=1138755

die4you said:
Where???
Show the link.............
Click to expand...
Click to collapse
Click in my name on here... and go thru my topic thread
Sent From In between Your Moms Boobies

ka24e said:
http://forum.xda-developers.com/showthread.php?t=1138755
Click to expand...
Click to collapse
i did many times; watch different video.
but, it's samething....screen shows unlocker bootloader.
i choose "YES" then click power botton then nothing happening.T.T

YourMainDude said:
Click in my name on here... and go thru my topic thread
Sent From In between Your Moms Boobies
Click to expand...
Click to collapse
I did that way; but i couldn't find out what I want it.
T.T

Lol does it send u directly to fastboot again? If so then ur think should say unlocked ^_^ within the fastboot mode
Sent From In between Your Moms Boobies

YourMainDude said:
Lol does it send u directly to fastboot again? If so then ur think should say unlocked ^_^ within the fastboot mode
Sent From In between Your Moms Boobies
Click to expand...
Click to collapse
No, I mean when i vol+ and power bottom, phone will going to fastboot mode. after that i connect a phone to computer; then type 'fastboot oem unlock' at command mode at my computer.
After, phone will be shows up choose unlock bootloader screen for 'YES' or 'No', so i choose 'YES' and click power bottom.....
NOThing Happen Forever ......

die4you said:
No, I mean when i vol+ and power bottom, phone will going to fastboot mode. after that i connect a phone to computer; then type 'fastboot oem unlock' at command mode at my computer.
After, phone will be shows up choose unlock bootloader screen for 'YES' or 'No', so i choose 'YES' and click power bottom.....
NOThing Happen Forever ......
Click to expand...
Click to collapse
Weird u should have an Unlocked icon underneath the Google Logo when it reboots but I think it automatically sends you to fastboot mode and at the center in red should say unlocked... u should then opened command prompt and flash recovery. I use the thread I posted. This is what I did from the very beginning.
Cd c:\nexussrootnew (enter)
>fastboot devices (enter)
"Device serial number"
>fastboot OEM unlock
----yes----
"Reboots back into fastboot mode"
Command prompt again:
Cd c:\nexussrootnew (enter)
>fastboot devices
"Device serial number"
>fastboot flash recovery (space)
recovery3101.img
(Flashing device)
"Ok"
"Back to phone"
Enter into recovery and go into mount SD card ... once u mount u will then drag the superuser.zip "provided within the file it asks u to download in link provided in my thread" into root of SDcard ... unmount and go back until u see flash zip from SD ... enter and find the superuser.zip ... that's it your rooted =]
Sent From In between Your Moms Boobies

I have the same problem
I have the same problem...
- Phone is stuck on google screen
- Installed all drivers and fastboot recognizes the phone and shows its serial number
- Typing "fastboot oem unlock" in the command promt
- Reach the bootloader unlock screen, select YES
---> The phone is left stuck on the bootloader unlock screen...
Have tried this over and over again, always ends up getting stuck on the bootloader unlock screen...
I have rooted many phones and am knowledgeable on the rest of the process (root/recovery, rom etc...), but I just can't pass this one step which is suppose to be ridiculesly easy.
Any advice?

israellive said:
I have the same problem...
- Phone is stuck on google screen
- Installed all drivers and fastboot recognizes the phone and shows its serial number
- Typing "fastboot oem unlock" in the command promt
- Reach the bootloader unlock screen, select YES
---> The phone is left stuck on the bootloader unlock screen...
Have tried this over and over again, always ends up getting stuck on the bootloader unlock screen...
I have rooted many phones and am knowledgeable on the rest of the process (root/recovery, rom etc...), but I just can't pass this one step which is suppose to be ridiculesly easy.
Any advice?
Click to expand...
Click to collapse
have you had issues with our sd storage? it seems that when that internal sd card goes, this happens.

[Q] Stuck on Google logo. Unable to push image file to phone... Please help.

Tried various possible solutions and still can't get past the Google logo. Installed adb and Samsung driver but when executing commands such as "abd remount" or "adb push file.zip \sdcard\" in cmd I get an error saying "device not found".
Does anyone know how I could resolve this issue?
I tried clearing the cache and wiping the data from the phone, and even heating the phone with a hair dryer. I'd very much appreciate any help.

looks like you still be able to get in reovery ? if so , then nothing you should worry , just flash a new ROM

Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!

nodstuff said:
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
Click to expand...
Click to collapse
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.

leeroy88 said:
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
Click to expand...
Click to collapse
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...

leeroy88 said:
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
Click to expand...
Click to collapse
Hmmm try going to cmd prompt and typing in adb devices, if you get nothing then your adb isn't set up properly and you need to go into setting and change the path on your computer.
I know the details are sketchy but gimme a min and I will find you a link
---------- Post added at 03:05 AM ---------- Previous post was at 03:00 AM ----------
http://forum.xda-developers.com/showthread.php?t=1161776
Find the Android sdk folder in your computer, move it to the root of C.
I don't think adb is where this guide says it is, there is a read me in the folder where it was saying it has moved to the platform tools folder.
So anyway find the path to the file and put it where the guide says and you should be on the ball.

Forget adb. You need to use fastboot.
Open a command prompt in the directory with fastboot or cd into it.
Put phone in fastboot mode.
On the command prompt type fastboot devices.
You will see your serial number. If you don't recheck and make sure you did everything. Sdk PDA drivers if need be etc.
Fastboot flash recovery custom recovery img name.img
Boot into recovery
Mounts and storage.
Mount SD card
Put a rom for you device on there.
Unmount
Wipe everything but sdcard from recovery.
Flash the rom by going to install zip from SD card......

Okay still stuck trying to connect to my phone. I haven't been able to get my serial number show when typing fastboot devices in cmd. adb is set up and seems to be working but the list of devices is blank when I type in adb devices. The phone was put into fastboot mode both times. I get <waiting for device> when I try
fastboot flash recovery clockwork-5.0.2-crespo.img
I think the bootloader may be locked as it does say LOCKED under lock state, which is probably the reason why I can't get the recovery image to work. I couldn't install PDANet as it wanted to connect to my phone while in debugging mode at the end of the installation. Would it be possible that fastboot oem unlock won't work with without having PDANet installed? I'd really appreciate any further help on this topic.

You need the drivers.

albundy2010 said:
You need the drivers.
Click to expand...
Click to collapse
I have the Google USB driver package installed from SDK Manager. I had tried to install some other Samsung driver found on another post but it wouldn't install.

Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?

leeroy88 said:
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
Click to expand...
Click to collapse
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782

ismailham said:
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
Click to expand...
Click to collapse
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.

leeroy88 said:
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
Click to expand...
Click to collapse
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?

nodstuff said:
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
Click to expand...
Click to collapse
After typing fastboot oem unlock I get three dots ...
Pretty much straight away it fails and says something about "too many links".

Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?

kvaju said:
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
Click to expand...
Click to collapse
Thanks for your reply, I followed the steps just now and got the exact same error. Before I was trying fastboot oem unlock while in platform-tools but this time I had downloaded the nexussrootICS.zip file, and extracted it to the root of C. I tried fastboot devices and my serial shows up and after fastboot oem unlock I get "status read failed: too many links."
The only difference I seem to have is that in my device manager I have Android Device > ADB Interface, as opposed to SAMSUNG Android Device > ADB Interface.
Not a big difference but that's all I can think of.

the same issue for me. is there any working solution for that?

I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147

GnubbyaBush said:
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
Click to expand...
Click to collapse
Thanks! I'll try to do this fancy dancing

[Q] Stuck in boot loop, can't detect in ADB or fastboot

Hey guys, I really need some help here, I'm not good at any of this stuff - my OPO just randomly got stuck on a boot loop, I have never played with the USB debugging or any of that or tried to flash anything else, I was using just stock cyanogen.
I've been reading around and I've downloaded all the drivers but still can't detect the device when I do the Shift + Right Click --> Run CMD "fastboot devices" or "adb devices".
I never enabled options such as the USB debugging or anything else, can someone please help me out? I'm really clueless to all of this stuff.

You must first put your phone in fastboot mode.
To put your phone in fastboot mode, turn it off, and then hold power+volume down until you get a screen with only the cyanogenmod logo. If you get to this screen, you're in fastboot mode. If you have installed the proper drivers in your computer, you should be able to connect to the phone from your computer. Connect your usb cable to the phone and the computer, open a dos box and type "fastboot devices". If you get a series of letters and numbers then you're OK.

jchen221 said:
Hey guys, I really need some help here, I'm not good at any of this stuff - my OPO just randomly got stuck on a boot loop, I have never played with the USB debugging or any of that or tried to flash anything else, I was using just stock cyanogen.
I've been reading around and I've downloaded all the drivers but still can't detect the device when I do the Shift + Right Click --> Run CMD "fastboot devices" or "adb devices".
I never enabled options such as the USB debugging or anything else, can someone please help me out? I'm really clueless to all of this stuff.
Click to expand...
Click to collapse
joanquro said:
You must first put your phone in fastboot mode.
To put your phone in fastboot mode, turn it off, and then hold power+volume down until you get a screen with only the cyanogenmod logo. If you get to this screen, you're in fastboot mode. If you have installed the proper drivers in your computer, you should be able to connect to the phone from your computer. Connect your usb cable to the phone and the computer, open a dos box and type "fastboot devices". If you get a series of letters and numbers then you're OK.
Click to expand...
Click to collapse
This, except that's the wrong button combo (power + volume down is for recovery). Use power + volume up to get to fastboot mode and then try the "fastboot devices" command.

Heisenberg said:
This, except that's the wrong button combo (power + volume down is for recovery). Use power + volume up to get to fastboot mode and then try the "fastboot devices" command.
Click to expand...
Click to collapse
I'm sorry for this mistake.

joanquro said:
You must first put your phone in fastboot mode.
To put your phone in fastboot mode, turn it off, and then hold power+volume down until you get a screen with only the cyanogenmod logo. If you get to this screen, you're in fastboot mode. If you have installed the proper drivers in your computer, you should be able to connect to the phone from your computer. Connect your usb cable to the phone and the computer, open a dos box and type "fastboot devices". If you get a series of letters and numbers then you're OK.
Click to expand...
Click to collapse
Thanks for your advice. This is the big problem I'm having, I've downloaded the SDK slim, and the driver manager and the 15 second installer things and installed all of them but still can't manage to detect my phone on fastboot.

jchen221 said:
Thanks for your advice. This is the big problem I'm having, I've downloaded the SDK slim, and the driver manager and the 15 second installer things and installed all of them but still can't manage to detect my phone on fastboot.
Click to expand...
Click to collapse
What command are you using while in fastboot mode?

Heisenberg said:
What command are you using while in fastboot mode?
Click to expand...
Click to collapse
I'm using both
fastboot devices
adb devices
Fastboot devices comes back with nothing in the CMD box, ADB devices gives a message that says 'Devices:' but there are none listed.

jchen221 said:
I'm using both
fastboot devices
adb devices
Fastboot devices comes back with nothing in the CMD box, ADB devices gives a message that says 'Devices:' but there are none listed.
Click to expand...
Click to collapse
There's no point in using adb commands in fastboot because only fastboot commands work. What drivers do you have installed?
XDA Moderator
Transmitted via Bacon

Heisenberg said:
There's no point in using adb commands in fastboot because only fastboot commands work. What drivers do you have installed?
XDA Moderator
Transmitted via Bacon
Click to expand...
Click to collapse
I've looked around for all sorts of drivers, I have the universal ADB, android SDK slim or something, is there a specific one I need?

jchen221 said:
I've looked around for all sorts of drivers, I have the universal ADB, android SDK slim or something, is there a specific one I need?
Click to expand...
Click to collapse
Uninstall whatever drivers you have installed, reboot your PC, install these drivers, reboot your PC, connect your phone, test fastboot (fastboot devices).

Heisenberg said:
Uninstall whatever drivers you have installed, reboot your PC, install , reboot your PC, connect your phone, test fastboot (fastboot devices).
Click to expand...
Click to collapse
I tried that, but again no response in CMD when I type fastboot devices.
Although I just tried and am able to boot into recovery mode, would I be able to do some sort of factory reset there? I've already tried to wipe user data but I'm still getting a bootloop there.

jchen221 said:
I tried that, but again no response in CMD when I type fastboot devices.
Although I just tried and am able to boot into recovery mode, would I be able to do some sort of factory reset there? I've already tried to wipe user data but I'm still getting a bootloop there.
Click to expand...
Click to collapse
I can't remember what capabilities the stock recovery has, but if it's there it's worth trying.

jchen221 said:
I tried that, but again no response in CMD when I type fastboot devices.
Although I just tried and am able to boot into recovery mode, would I be able to do some sort of factory reset there? I've already tried to wipe user data but I'm still getting a bootloop there.
Click to expand...
Click to collapse
Heisenberg said:
I can't remember what capabilities the stock recovery has, but if it's there it's worth trying.
Click to expand...
Click to collapse
I managed to get it to work after resetting a bunch of the options, thanks so much for your help with this (even if I didn't get it to fastboot mode)

I have the same problem.
jchen221 said:
I managed to get it to work after resetting a bunch of the options, thanks so much for your help with this (even if I didn't get it to fastboot mode)
Click to expand...
Click to collapse
Hey bro, I have the same problem. Can you please explain me how did you resolve it? This would be of great help. Thanks.

pavanakshay said:
Hey bro, I have the same problem. Can you please explain me how did you resolve it? This would be of great help. Thanks.
Click to expand...
Click to collapse
for me too bro same problem please help me
---------- Post added at 08:28 AM ---------- Previous post was at 08:25 AM ----------
Heisenberg said:
Uninstall whatever drivers you have installed, reboot your PC, install these drivers, reboot your PC, connect your phone, test fastboot (fastboot devices).
Click to expand...
Click to collapse
i too having the same problem bro the driver link is not working please send me the link thankyou in advance

i am also facing the same problem that phone loops into fast boot mode whenever turned on i do totally every kind of drivers softwares and etc like tenorshare but all in vain i guess at last that phone must be enabled usb debuging in order to be detected as a active adb device,i pratically do this stuff by using another phone with enabled debuging and it was an active device andd can be processed further but when i disabled the usb debugging of same phone it was not working with adb interface i hope you understand,,,,but a miracle happenend i removed the battery for about a week and suddenly i pluged and try to turn it on hola it starts from roms boot logo

HELP!!!!! Stuck on bootloop and fastboot not working
i was flashing twrp on infinix s4 withfast boot. after flashing the device is stuck on bootloop. the recovery is not accessible (i press the key combo nothing happens) and fastboot combination is also not working. i tried connecting it with adb cmd and ran the command "adb reboot bootloader" but no device is detected.
ps: the link for drivers is broken

Possible Way to Unlock Bootloader?

I wrote this earlier in the Bounty page for the bootloader unlock, but just so other people can see this as well, here is it in post form! This is the way to unlock bootloader on G3 so if anyone is on lollipop and is rooted, could they try it?
-- STEP 1: Remove LG Download mode (laf)
Important! You’ll need root access to remove (laf), so make sure you’ve rooted before proceeding with the steps below:
Download ADB files:
Prepare your phone:
Enable developer options: Go to your phone’s Settings » select About phone » Scroll to the bottom and tap on “Build number” seven times to enable developer options
Enable USB Debugging: Open phone’s Settings » select Developer options » Tick the “USB debugging” checkbox (under Debugging section)
Connect your phone to PC with a USB cable and if/when a pop-up screen shows up on Phone asking you to ‘Allow USB debugging?‘ for the computer, make sure you tick the checkbox and tap OK
Now type/paste the following ADB commands to backup LG Download Mode (laf), so you can restore it later when necessary
Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/sdcard/laf.img
Now run the following command to remove laf and reboot your phone
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
exit
adb reboot
Your phone will now reboot
Now to go into fastboot
adb reboot bootloader
Unlock bootloader!
fastboot oem unlock
or
fastboot flashing unlock
I took this info from original source listed below and made a few changes..
http://forum.xda-developers.com/tmobile-lg-g3/general/how-to-boot-lg-g3-fastboot-mode-t3087445

Good..but there is no fastboot in g flex 2.. Even if there was no fastboot commands would work..
So thats that

adds08 said:
Good..but there is no fastboot in g flex 2.. Even if there was no fastboot commands would work..
So thats that
Click to expand...
Click to collapse
My point is that the G3 also can't go into fastboot until you do this. So I just want people to see if it'll work, cause I'm on Linux and marshmallow so I can't test it. I think the G Flex 2 is more similar to the G3 than the G4 so that's why I'm asking for people to try it out

People already managed to enter fastboot, but no fastboot commands works.

I m going to try it but I need the commands to reflash download mode.
And then how do I know I succeeded?
I mean,with bootloader unlock,is there any way to flash a custom recovery to see if it works?

Pungasul said:
I m going to try it but I need the commands to reflash download mode.
And then how do I know I succeeded?
I mean,with bootloader unlock,is there any way to flash a custom recovery to see if it works?
Click to expand...
Click to collapse
Checking Bootloader Unlock : fastboot oem device-info
reflashing download mode : dd if=/sdcard/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf

Aboot fastboot commands are all disabled.. For g3 wasnt it bump tht unlocked the bootloader?
Bt i have already tried nuking the laf and using fastboot commands many months ago..

adds08 said:
Aboot fastboot commands are all disabled.. For g3 wasnt it bump tht unlocked the bootloader?
Bt i have already tried nuking the laf and using fastboot commands many months ago..
Click to expand...
Click to collapse
Just out of curiosity, but what commands did you use?

adds08 said:
Aboot fastboot commands are all disabled.. For g3 wasnt it bump tht unlocked the bootloader?
Bt i have already tried nuking the laf and using fastboot commands many months ago..
Click to expand...
Click to collapse
Because the Nexus 6P is known for saying unknown command if you type fastboot oem unlock instead of fastboot flashing unlock

Try it... But dont forget to backup laf in case of failure .. I have done every possible commands new or old

Hi,
I tried this and erased the LAF. Then when you hold "Vol+" and plug-in USB cable you will see "[310] Fastboot mode started".
In Windows device manager I got "Marshall London Bootloader Interface" ... can't remember that I installed any driver but this is the LG G Flex 2.
Unfortunately it seams that there are no fastboot commads are working. I tried this with Android 5.0.1 because this was the only version I got rooted.
So this looks good to me but also it seams an dead end at the moment.
Best regards

CryptMan said:
Hi,
I tried this and erased the LAF. Then when you hold "Vol+" and plug-in USB cable you will see "[310] Fastboot mode started".
In Windows device manager I got "Marshall London Bootloader Interface" ... can't remember that I installed any driver but this is the LG G Flex 2.
Unfortunately it seams that there are no fastboot commads are working. I tried this with Android 5.0.1 because this was the only version I got rooted.
So this looks good to me but also it seams an dead end at the moment.
Best regards
Click to expand...
Click to collapse
i have a 950 that died on me some months ago and now i get Fastboot mode started but no commands work .
maybe if i put the LAF back on it it will boot ?

caesar170988 said:
maybe if i put the LAF back on it it will boot ?
Click to expand...
Click to collapse
I don't think so.
But with LAF back and started you should be able to use "LG UP" to flash a new firmware.
I can't tell you how you will be able to do that if it is not booting.

Cannot lock bootloader

So I'm trying to re-lock my bootloader,
I already looked up how to lock the bootloader and you can do that by booting in to fastboot and locking the bootloader from there. My OP6 was rooted but I removed all root related applications, I even reinstalled android.
I tought it would be as simple as unlocking the bootloader, but whatever I try I can't get my device to show up in the command promt when using the "adb devices" command while in fastboot. I tried reinstalling the ADB, fastboot and OP drivers a couple times but it doesn't help. I tried everything possible but I can't lock the bootloader.
Could somebody please help me with this?

ian_99 said:
So I'm trying to re-lock my bootloader,
I already looked up how to lock the bootloader and you can do that by booting in to bootloader and locking the bootloader from there. My OP6 was rooted but I removed all root related applications, I even wiped android.
I tought it would be as simple as unlocking the bootloader, but whatever I try I can't get my device to show up in the command promt when using the "adb devices" command. I tried reinstalling the ADB, fastboot and OP drivers a couple times but it doesn't help. I tried everything possible but I can't lock the bootloader.
Could somebody please help me with this?
Click to expand...
Click to collapse
You have to be in fastboot mode ( power off phone, hold power and volume up til you see fastboot on screen) on your phone to do want to want, if you cant do it that way,you can try this tool, https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892 , it will return your phone to stock factory fresh. It will be back on 5.1.5 software. Good luck

in fastboot mode just type without quote"fastboot oem lock"

MrSteelX said:
in fastboot mode just type without quote"fastboot oem lock"
Click to expand...
Click to collapse
I can boot into fastboot mode (I said bootloader instead of fastboot, my bad), but the command promt does NOT show any devices, so I can't use this command. All drivers are correctly installed.

Did you enable USB debug?

whizeguy said:
Did you enable USB debug?
Click to expand...
Click to collapse
Yes I did
And I tried updating to android P but now I can't even access fastboot!
[UPDATE:]
I can finally boot into fastboot again, the only way to do this was to first boot into recovery and restart to fastboot from there.
And my device is still not detected by adb in fastboot

u do fastboot devices not adb devices

I just tried doing this in a Windows 7 virtual machine, but it gives the exact same results, I really don't know what is cousing this

Then take tool all in one

Well.... Use msm download tool then.. Since you can go to fastboot, it will reset everything and lock the BL.

whizeguy said:
Well.... Use msm download tool then.. Since you can go to fastboot, it will reset everything and lock the BL.
Click to expand...
Click to collapse
What a coincidence, I am watching a video on how you can fix a bricked OP6, wich does exaclty what you said.
Thanks!

ian_99 said:
I tought it would be as simple as unlocking the bootloader, but whatever I try I can't get my device to show up in the command promt when using the "adb devices" command while in fastboot.
Click to expand...
Click to collapse
You should do "fastboot devices" in fastboot mode!
I see thay you're doing "adb devices" instead which is wrong.

rhai said:
You should do "fastboot devices" in fastboot mode!
I see thay you're doing "adb devices" instead which is wrong.
Click to expand...
Click to collapse
Oh god that actually worked, how could I have forgotten I had to use the "fastboot" command.
I can't thank you enough :victory:

ian_99 said:
Oh god that actually worked, how could I have forgotten I had to use the "fastboot" command.
I can't thank you enough :victory:
Click to expand...
Click to collapse
No worries. Cheers!