Database Users

Computer recognises phone but phone doesn't think it's connected?

I'm trying to unlock the bootloader so that I can flash a custom recovery.
I've enabled both unlocking the bootloader and USB debugging and the computer recognizes the phone when I type "fastboot devices" in the terminal. When on the bootloader screen i've wrote "adb devices" and the computer recognised the phone.
I've then typed "fastboot flashing unlock" and a list of commands come up. The same list comes up even when I type "sudo fastboot flashing unlock".
"sudo fastboot oem" unlock gives me a FAILED (remote: unknown command) message.
What can be the cause of this problem?
My linux computer recognizes my phone when I type fastboot devices, but judging by the last line on the bootloader the phone doesn't think it's connected to the computer.

tbh just use nexus root toolkit

CloudPaganini said:
I'm trying to unlock the bootloader so that I can flash a custom recovery.
I've enabled both unlocking the bootloader and USB debugging and the computer recognizes the phone when I type "fastboot devices" in the terminal. When on the bootloader screen i've wrote "adb devices" and the computer recognised the phone.
I've then typed "fastboot flashing unlock" and a list of commands come up. The same list comes up even when I type "sudo fastboot flashing unlock".
"sudo fastboot oem" unlock gives me a FAILED (remote: unknown command) message.
What can be the cause of this problem?
My linux computer recognizes my phone when I type fastboot devices, but judging by the last line on the bootloader the phone doesn't think it's connected to the computer.
Click to expand...
Click to collapse
Try fastboot oem unlock.

fastboot flashing oem unlock.
http://www.androidpolice.com/2015/1...become-common-for-many-devices-in-the-future/

Not able to Unlock BootLoader

HI
I need help unfortunately after flashing a ROM in my OP2 my recovery disappeared and I am stuck wid fastboot now and when I try to flash twrp in it it says locked so I try to unlock bootloader using "Fastboot OEM unlock" Says success but when I type in "Fastboot OEM Device-info" it shows Device Tampered : True and bootloader unlocked : False I have stuck in Fastboot for last 48 hrs pls help me bro.:crying:

Tharun Gowd said:
HI
I need help unfortunately after flashing a ROM in my OP2 my recovery disappeared and I am stuck wid fastboot now and when I try to flash twrp in it it says locked so I try to unlock bootloader using "Fastboot OEM unlock" Says success but when I type in "Fastboot OEM Device-info" it shows Device Tampered : True and bootloader unlocked : False I have stuck in Fastboot for last 48 hrs pls help me bro.:crying:
Click to expand...
Click to collapse
https://forums.oneplus.net/threads/mega-unbrick-guide-for-a-hard-bricked-oneplus-2.347607/
Here read my comment at page 15

Tharun Gowd said:
HI
I need help unfortunately after flashing a ROM in my OP2 my recovery disappeared and I am stuck wid fastboot now and when I try to flash twrp in it it says locked so I try to unlock bootloader using "Fastboot OEM unlock" Says success but when I type in "Fastboot OEM Device-info" it shows Device Tampered : True and bootloader unlocked : False I have stuck in Fastboot for last 48 hrs pls help me bro.:crying:
Click to expand...
Click to collapse
I have had the same problem, i have managed to solved it with this guide (method 3).
http://www.technobuzz.net/unbrick-oneplus-2/
Good luck

fastboot oem get_identifier_token not working

Hey guys! I just got and HTC U Ultra, and I'm trying to unlock the bootloader the same way I always have with any HTC. fastboot oem get_identifier_token. I'm using a command prompt from a Linux build OS, but the command keeps failing. FAILED (remote: unknown command). Any ideas?
EDIT: Never mind. There was a glitch that I worked out. Thanks anyways!

My PH-1 bricked ,I am so sad.What should I do?

question:
today I locked the booloader,but my PH-1 can't boot,it siad"Your devices is corrput,It can't be trusted and will not boot."
I use adb cant find devices.But it can use"fastboot decives".
"fastboot -w"is failed,the remote is "remote: Erase is not allowed in Lock State."
"fastboot flash boot.img" or "fastboot flash recovery twrp.img" also failed. the remote is "remote: Erase is not allowed in Lock State"
can anyone tell me how to get devices?
[IMG="https://drive.google.com/open?id=1cAIFNdksNV9-yUEQQBzwz7S1uDxgNhGp"]

[email protected] said:
question:
today I locked the booloader,but my PH-1 can't boot,it siad"Your devices is corrput,It can't be trusted and will not boot."
I use adb cant find devices.But it can use"fastboot decives".
"fastboot -w"is failed,the remote is "remote: Erase is not allowed in Lock State."
"fastboot flash boot.img" or "fastboot flash recovery twrp.img" also failed. the remote is "remote: Erase is not allowed in Lock State"
can anyone tell me how to get devices?
[IMG="https://drive.google.com/open?id=1cAIFNdksNV9-yUEQQBzwz7S1uDxgNhGp"]
Click to expand...
Click to collapse
Can you boot to recovery and factory reset?

ktmom said:
Can you boot to recovery and factory reset?
Click to expand...
Click to collapse
no,the phone can't do this

[email protected] said:
no,the phone can't do this
Click to expand...
Click to collapse
Have you tried unlocking again in fastboot?

ktmom said:
Have you tried unlocking again in fastboot?
Click to expand...
Click to collapse
Yes,but it failed. remote is Flashing Unlock is not allowed .

[email protected] said:
Yes,but it failed. remote is Flashing Unlock is not allowed .
Click to expand...
Click to collapse
It sounds like the OEM unlock was turned off in developer settings.
If you can't get to recovery and you can't boot to be able to unlock again, you're stuck [emoji17]

This is a warning to others. Don't lock bootloader. You can leave phone unrooted, no TWRP, and bootloader unlocked. It has the annoying warning splash screen with every reboot, but a lot safer than locking bootloader

HueyT said:
This is a warning to others. Don't lock bootloader. You can leave phone unrooted, no TWRP, and bootloader unlocked. It has the annoying warning splash screen with every reboot, but a lot safer than locking bootloader
Click to expand...
Click to collapse
Exactly. This has been highlighted many times - relocking the BL after unlocking it once is a bad idea...

Shoot me a msg I May Be of help

question:
today I locked the booloader,but my PH-1 can't boot,it siad"Your devices is corrput,It can't be trusted and will not boot."
I use adb cant find devices.But it can use"fastboot decives".
"fastboot -w"is failed,the remote is "remote: Erase is not allowed in Lock State."
"fastboot flash boot.img" or "fastboot flash recovery twrp.img" also failed. the remote is "remote: Erase is not allowed in Lock State"
can anyone tell me how to get devices?
Click to expand...
Click to collapse
For "Your devices is corrput,It can't be trusted and will not boot." Press power button?
Try
fastboot oem disable_dm_verity
Then
If able boot into recovery (hard reset button combination)
adb reboot "dm-verity enforcing"
Worth a shot ...

Aimless Rambler said:
For "Your devices is corrput,It can't be trusted and will not boot." Press power button?
Try
fastboot oem disable_dm_verity
Then
If able boot into recovery (hard reset button combination)
adb reboot "dm-verity enforcing"
Worth a shot ...
Click to expand...
Click to collapse
also failed……

i am getting strange error while trying unlocking my bootloader

I have a snip of error
even though 'fastboot devices' command is showing my device
but 'fastboot flashing unlock' is not working
If somebody knows why is this happening please help!
Thanks