Locked in "Device State: locked" - OnePlus 6T Questions & Answers

I flashed a ROM that got my device hard bricked in the process, I had to use MsmDownloadTool to recover and I indeed successfully unbricked my device. With stock OOS I enabled oem unlock from developer settings to root again but I can't pass from that, for some reason the bootloader doesn't want to unlock even though the option is enabled. I tried the command 'fastboot oem unlock' already, the device can't make fastboot connections. Help. Please.

vulkhead said:
I flashed a ROM that got my device hard bricked in the process, I had to use MsmDownloadTool to recover and I indeed successfully unbricked my device. With stock OOS I enabled oem unlock from developer settings to root again but I can't pass from that, for some reason the bootloader doesn't want to unlock even though the option is enabled. I tried the command 'fastboot oem unlock' already, the device can't make fastboot connections. Help. Please.
Click to expand...
Click to collapse
Reboot the computer.
Reboot the phone.
Try a different cable.
Try a different port.

tech_head said:
Reboot the computer.
Reboot the phone.
Try a different cable.
Try a different port.
Click to expand...
Click to collapse
Sadly didn't make a difference

vulkhead said:
Sadly didn't make a difference
Click to expand...
Click to collapse
Try "fastboot devices" to see if the phone is seen.

tech_head said:
Try "fastboot devices" to see if the phone is seen.
Click to expand...
Click to collapse
It doesn't, nothing shows up. All drivers are installed.

vulkhead said:
It doesn't, nothing shows up. All drivers are installed.
Click to expand...
Click to collapse
Is USB debugging on?

devilrulz4ever said:
Is USB debugging on?
Click to expand...
Click to collapse
Every basic step to root a device has not been left behind.

vulkhead said:
It doesn't, nothing shows up. All drivers are installed.
Click to expand...
Click to collapse
[~]#fastboot devices
83c709f4 fastboot
If it doesn't show up, forget about what the phone is doing.
You need to figure out the driver situation on your computer.
If you can try a different computer.
Are you using Windows? What version?
I'm on a Mac and have zero issues.

yep, its your driver that is the issue; un install what ever you have installed driver wise, and start again..
oh, and your phone isn't "hard" bricked, or even "soft" bricked; bricked con notates a DOA phone, and yours is neither..
that term is abused and misused here constantly..

Related

[Q] Used fastboot oem-off-mode charge 0, now won't charge

So I am installing the Nexus 7 in my car as the head unit, but am now stuck with this issue.
I unlocked, and rooted the device, and used the fastboot oem off-mode-charge 0 command and it worked.
Anytime the Nexus 7 receives power it turns on.
However the device battery died completely and now when I plug it in to charge, the screen stays black, buttons do nothing, and eventually it boots up, but immediatley powers off as the battery is at 0 % and has the red ! mark.
I can't even use the fastboot command to reverse it since the device can't stay on.
What the heck can I do?
Type the reverse command and it will say "waiting for device". Connect your device and booting into bootloader even for a split second should push the command.
Username invalid said:
Type the reverse command and it will say "waiting for device". Connect your device and booting into bootloader even for a split second should push the command.
Click to expand...
Click to collapse
That's what I thought and I tried it, but nothing happened. It stayed in bootloader for about a minute but the command prompt stayed at waiting for device.
I'm not 100% sure but I think I used Nexus Root Toolkit to go back to the stock rom, which would have unrooted the device.
Which also means debugging is not active.
Does it need to be rooted and debug active to be able to push?
I know the bootloader still says unlocked.
@Username invalid
Yes, but will the command be executed before the device dies again?
---------- Post added at 09:46 AM ---------- Previous post was at 09:44 AM ----------
When you're in bootloader, you don't need debugging enabled since the fastboot protocol comes into play, not ADB (which requires debugging to be enabled). Root is also unnecessary. At least that's what I have learnt in the past 5 months I have had this.
Jeremi1023 said:
That's what I thought and I tried it, but nothing happened. It stayed in bootloader for about a minute but the command prompt stayed at waiting for device.
I'm not 100% sure but I think I used Nexus Root Toolkit to go back to the stock rom, which would have unrooted the device.
Which also means debugging is not active.
Does it need to be rooted and debug active to be able to push?
I know the bootloader still says unlocked.
Click to expand...
Click to collapse
No, you do not need be rooted or have USB debugging enabled to use Fastboot. What Android Bootloader Interface driver version do you have installed on your computer? Did you check by typing "fastboot devices" if your device is being recognized?
sgt. meow said:
@Username invalid
Yes, but will the command be executed before the device dies again?
Click to expand...
Click to collapse
There is not enough time for me to set debugging on before the device dies. It stays on for maybe 5 seconds at the home screen then powers off.
Is there a way I could charge the battery a little bit bypassing the Nexus?
Can I splice in the pos and neg of the usb charger to the pos and neg of the battery?
I'd highly discourage the battery direct charging bit.
Username invalid said:
No, you do not need be rooted or have USB debugging enabled to use Fastboot. What Android Bootloader Interface driver version do you have installed on your computer? Did you check by typing "fastboot devices" if your device is being recognized?
Click to expand...
Click to collapse
I'm not sure at all.
I used the R3 Nexus 7 Superboot to push the original command. I had downloaded fastboot from somewhere else, and put it in the Superboot folder to get it to push the command.
By the way sorry for taking so long to reply in between. Since I am a new user, I have to wait the 5 minutes in between posts.
Jeremi1023 said:
That's what I thought and I tried it, but nothing happened. It stayed in bootloader for about a minute but the command prompt stayed at waiting for device.
I'm not 100% sure but I think I used Nexus Root Toolkit to go back to the stock rom, which would have unrooted the device.
Which also means debugging is not active.
Does it need to be rooted and debug active to be able to push?
I know the bootloader still says unlocked.
Click to expand...
Click to collapse
Since your device was able to stay in bootloader for a minute, did you check if it was being recognized by your computer?
Username invalid said:
Since your device was able to stay in bootloader for a minute, did you check if it was being recognized by your computer?
Click to expand...
Click to collapse
I am assuming it was, as Windows chimed in as soon as the device had enough juice to turn on.
Jeremi1023 said:
I am assuming it was, as Windows chimed in as soon as the device had enough juice to turn on.
Click to expand...
Click to collapse
Try booting into bootloader again then typing "fastboot devices". Also go to your computer Device Manager > Android Devices > Android Bootloader Interface > Properties.
Username invalid said:
Try booting into bootloader again then typing "fastboot devices". Also go to your computer Device Manager > Android Devices > Android Bootloader Interface > Properties.
Click to expand...
Click to collapse
I will do that and let you know what I see.
Just gotta wait for the thing to turn on. It's very random right now.
Okay, I was able to get into bootloader, and I I did "fastboot devices" and nothing came up.
Also checked device manager and no Android or anything like it in there.
Username invalid said:
Try booting into bootloader again then typing "fastboot devices". Also go to your computer Device Manager > Android Devices > Android Bootloader Interface > Properties.
Click to expand...
Click to collapse
I see that it is coming up as unknown device under the USB section
I have tried the Nexus toolkit guide for installing the drivers to no avail.
When I try to update the drivers for "unknown device" and go to the path where they are, windows said the best drivers are already installed.
Jeremi1023 said:
I see that it is coming up as unknown device under the USB section
I have tried the Nexus toolkit guide for installing the drivers to no avail.
When I try to update the drivers for "unknown device" and go to the path where they are, windows said the best drivers are already installed.
Click to expand...
Click to collapse
http://d-h.st/kDu
Username invalid said:
http://d-h.st/kDu
Click to expand...
Click to collapse
Even with those drivers, Windows still says the best ones are installed and refuses to use them.
Jeremi1023 said:
Even with those drivers, Windows still says the best ones are installed and refuses to use them.
Click to expand...
Click to collapse
Uninstall your current one first.
Username invalid said:
Uninstall your current one first.
Click to expand...
Click to collapse
What I have done is use Nexus Toolkit to uninstall, like it says, anything having to do with nexus, google, samsung, etc. I reboot the computer, wait for the tablet to turn on for a few seconds and then windows chimes in and says the usb device malfunctioned and could not be installed. It shows up in device manager as Unknown Device, and when I try to update the drivers, it says they are updated and won't use the ones I chose.
Have I not fully uninstalled the old ones?
Jeremi1023 said:
What I have done is use Nexus Toolkit to uninstall, like it says, anything having to do with nexus, google, samsung, etc. I reboot the computer, wait for the tablet to turn on for a few seconds and then windows chimes in and says the usb device malfunctioned and could not be installed. It shows up in device manager as Unknown Device, and when I try to update the drivers, it says they are updated and won't use the ones I chose.
Have I not fully uninstalled the old ones?
Click to expand...
Click to collapse
I'm not sure. I stopped using the toolkit and do pretty much everything I need now through ADB. Do you have another computer you can use?
Username invalid said:
I'm not sure. I stopped using the toolkit and do pretty much everything I need now through ADB. Do you have another computer you can use?
Click to expand...
Click to collapse
Yeah I have a desktop I could try it on.
I've never plugged the Nexus in to the desktop, so it should be a complete clean install of drivers.
If Windows recognizes the nexus on the desktop, what should I do?
Do I need to uninstall anything it may install on its own?
I figure I will end up installing the drivers you previously provided.

Cannot get past "adb devices" command line

I have followed Heisenbergs instructions to the letter but when I issue the adb devices command it just returns the string "list of devices" and that's it. Fastboot devices doesn't work either.
So I'm stuck at the start. Can anyone help me? From what I can tell I may need drivers but I'm new to this so I don't know.
I can give anyone more info if they need it.
I believe part of the instructions are to install the Platform Tools, which should include drivers. Try running the SDK Manager and updating or installing the drivers again. Also ensure you have USB Debugging ON in your Developer settings and OEM Unlocking enabled. Lastly, tap the notification in your shade about the USB connection (I think it defaults to Charging Only) and change it to various modes. Mine seems to only work on PTP mode. When you run the adb devices command you will need to authorize the connection on the phone end the first time by clicking OK so make sure the screen is on and unlocked so you can see it.
Hope this helps.
peckaldee said:
I have followed Heisenbergs instructions to the letter but when I issue the adb devices command it just returns the string "list of devices" and that's it. Fastboot devices doesn't work either.
So I'm stuck at the start. Can anyone help me? From what I can tell I may need drivers but I'm new to this so I don't know.
I can give anyone more info if they need it.
Click to expand...
Click to collapse
u enable OEM Unlock under developer settings?
You enable USB debugging?
Me personally do not get any strings of data returned when im on fastboot
i open CMD, run ADB DEVICES, get message saying the port is opening, and then listing devices... which is empty
but i am able to flash anything i want using fastboot....
try this command and see if it works after that... fastboot reboot-bootloader
it should reboot bootloader for u.. thats a easy way to know its responding to u
Is the device showing properly in the Device Manager when it's connected to your system?
hEaTLoE said:
Is the device showing properly in the Device Manager when it's connected to your system?
Click to expand...
Click to collapse
It shows up in windows explorer as "Nexus 6p" when I plug in the USB cable.
I have USB debugging and unlock bootloader checked in settings.
My fastboot devices command returns nothing.
peckaldee said:
It shows up in windows explorer as "Nexus 6p" when I plug in the USB cable.
I have USB debugging and unlock bootloader checked in settings.
My fastboot devices command returns nothing.
Click to expand...
Click to collapse
Did you change the USB mode? Mine shows in Explorer as you described but won't work in ADB/Fastboot until I change it to PTP.
fury683 said:
Did you change the USB mode? Mine shows in Explorer as you described but won't work in ADB/Fastboot until I change it to PTP.
Click to expand...
Click to collapse
Yeah I tried every option. Nothing.
The instructions say the fastboot devices command should return my serial number and it does not.
When booted into the bootloader one it tells me on one line phone LOCKED and on another line says download mode DISABLED.
Don't know if this has anything to do with my problems but I still cannot get a return on the fastboot devices command in order to proceed with the unlock command of "fastboot flashing unlock"
remember that u need latest fastboot for this to work.
did u updated the SDK manager to the latest? i had to do that in order to work for 6P
chaco81 said:
remember that u need latest fastboot for this to work.
did u updated the SDK manager to the latest? i had to do that in order to work for 6P
Click to expand...
Click to collapse
I'm using sdk manager revision 24.4.1
peckaldee said:
I have followed Heisenbergs instructions to the letter but when I issue the adb devices command it just returns the string "list of devices" and that's it. Fastboot devices doesn't work either.
So I'm stuck at the start. Can anyone help me? From what I can tell I may need drivers but I'm new to this so I don't know.
I can give anyone more info if they need it.
Click to expand...
Click to collapse
I had the same issue ,it was down to when I plugged the phone into the PC for the first time,it installed the Google.USB driver ,but it didn't install the driver for the adb interface,I had to download it from Google and install it manually
I also had the same issue, I had an old Clockworkmod generic driver that I was using for my Samsung Galaxy S5 installed.
Go to Device manager (either type it in the start menu, or: right click This PC, click manage, and click device manager), plug in your unlocked Nexus 6P phone and watch for a new item to pop up. If it says android something, uninstall it. I had to uninstall 3 times, then reinstall the drivers from the SDK before it would work.
I used the skipsoft toolkit to install the fb drivers; worked for me. http://forum.xda-developers.com/nex...ol-skipsoft-android-toolkit-nexus-6p-t3234159
but like others said, you may have to manually remove any that are already installed in windows, although I think that is one of the options in the toolkit.
mbonus said:
I used the skipsoft toolkit to install the fb drivers; worked for me. http://forum.xda-developers.com/nex...ol-skipsoft-android-toolkit-nexus-6p-t3234159
but like others said, you may have to manually remove any that are already installed in windows, although I think that is one of the options in the toolkit.
Click to expand...
Click to collapse
This worked. Now my commands in terminal are working correctly. thanks all for the help
Got A device to pop up under the command adb devices, but nothing under fastboot devices. Any tips? Had to follow the skipsoft instructions to install adb/fastboot devices. Yes USB Debugging is on and the OEM unlocking is set to allow..
Christ I'm retarded. Sorry boys, thought my phone was in the bootloader when I was trying this command LOL
Same problem
peckaldee said:
When booted into the bootloader one it tells me on one line phone LOCKED and on another line says download mode DISABLED.
Don't know if this has anything to do with my problems but I still cannot get a return on the fastboot devices command in order to proceed with the unlock command of "fastboot flashing unlock"
Click to expand...
Click to collapse
I'm having the same problem. Did you ever figure out what was wrong?
mbonus said:
I used the skipsoft toolkit to install the fb drivers; worked for me. http://forum.xda-developers.com/nex...ol-skipsoft-android-toolkit-nexus-6p-t3234159
but like others said, you may have to manually remove any that are already installed in windows, although I think that is one of the options in the toolkit.
Click to expand...
Click to collapse
Solved my problem as well. Thanks!

Soft brick, no fastboot or adb in bootloader mode. $25 bounty

The phone is in bootloop. I believe that the partition for system and other things were formatted. I can access the bootloader, however when I plug into PC it is not detected. (I have reinstalled drivers to make sure there is no issue) My PC recognizes my nexus 5x just fine. I can boot into recovery as well but pc does not detect the device even when I go to ADB side load. If the phone is off and I plug into the PC phone shows charging but nothing happens on the PC. Any ideas or help would be appreciated. $25 bounty the person with the magic answer.
What does the CMD output when you type in "fastboot devices", while your device is connected in bootloader mode?
P.S. You might want to remove the bounty. There is no need for that. People here can and will help you for free. :good:
DJBhardwaj said:
What does the CMD output when you type in "fastboot devices", while your device is connected in bootloader mode?
P.S. You might want to remove the bounty. There is no need for that. People here can and will help you for free. :good:
Click to expand...
Click to collapse
It looks for the devices, then a blank space then back to the cmd prompt.
ppbatman said:
It looks for the devices, then a blank space then back to the cmd prompt.
Click to expand...
Click to collapse
Just to confirm, while you do this, your device is in bootloader mode?
Also, have you tried it on another PC?
DJBhardwaj said:
Just to confirm, while you do this, your device is in bootloader mode?
Also, have you tried it on another PC?
Click to expand...
Click to collapse
Yes sit, in bootloader mode. Have tried 3 PC's all the usb ports and 2 usb cables. Im stumped.
ppbatman said:
Yes sit, in bootloader mode. Have tried 3 PC's all the usb ports and 2 usb cables. Im stumped.
Click to expand...
Click to collapse
While your device is connected, do you see anything unusual in Control Panel > Device Manager?
---------- Post added at 08:41 PM ---------- Previous post was at 08:40 PM ----------
ppbatman said:
Yes sit, in bootloader mode. Have tried 3 PC's all the usb ports and 2 usb cables. Im stumped.
Click to expand...
Click to collapse
Also, have you tried a factory reset from within the stock recovery?
DJBhardwaj said:
While your device is connected, do you see anything unusual in Control Panel > Device Manager?
---------- Post added at 08:41 PM ---------- Previous post was at 08:40 PM ----------
Also, have you tried a factory reset from within the stock recovery?
Click to expand...
Click to collapse
I can't see anything come up in device manger at all. There is no stock recovery it has cyanogen recovery, I did factory reset from this recovery multiple times to no avail. I
ppbatman said:
I can't see anything come up in device manger at all. There is no stock recovery it has cyanogen recovery, I did factory reset from this recovery multiple times to no avail. I
Click to expand...
Click to collapse
That drives me clueless too. It most probably seems like a driver issue. You might want to dig in more?
DJBhardwaj said:
That drives me clueless too. It most probably seems like a driver issue. You might want to dig in more?
Click to expand...
Click to collapse
I appreciate the help. I have tried multiple different drivers with multiple tools. I might try it on a mac to see if I can get it to recognize the phone. Could it be something where the phone was not put into debug mode and not stuck that way?
ppbatman said:
I appreciate the help. I have tried multiple different drivers with multiple tools. I might try it on a mac to see if I can get it to recognize the phone. Could it be something where the phone was not put into debug mode and not stuck that way?
Click to expand...
Click to collapse
Also, I have access to an Octobox through a friend of mine. I wouldn't know where to begin but, I know these are used in some cases to recovery phones.
I suggest you to try with a Linux or Mac machine, as drivers are not required in such cases.
Are you sure you don't have a defective cable?
Cero92 said:
I suggest you to try with a Linux or Mac machine, as drivers are not required in such cases.
Are you sure you don't have a defective cable?
Click to expand...
Click to collapse
I agree.
Sounds like a defective cable.
I have a Mac so I never worry about drivers and such.
Can you remove all drivers and what not that you've installed, all tools and everything, reboot your PC.
Install this: http://forum.xda-developers.com/showthread.php?p=48915118
Say YES to all options, install the drivers it asks you too.
Reboot your PC again.
Plug device in, while in bootloader mode, try "fastboot devices" again. If nothing happens, reboot-bootloader again from the phone, while keeping the device plugged in.
ppbatman said:
Also, I have access to an Octobox through a friend of mine. I wouldn't know where to begin but, I know these are used in some cases to recovery phones.
Click to expand...
Click to collapse
I would say, first check on a Mac or other Windows machines. See if Device Manager shows anything?
Wiltron said:
Can you remove all drivers and what not that you've installed, all tools and everything, reboot your PC.
Install this: http://forum.xda-developers.com/showthread.php?p=48915118
Say YES to all options, install the drivers it asks you too.
Reboot your PC again.
Plug device in, while in bootloader mode, try "fastboot devices" again. If nothing happens, reboot-bootloader again from the phone, while keeping the device plugged in.
Click to expand...
Click to collapse
I will definitely try this tonight when I get home from work. Thanks very much for the suggestion.
tech_head said:
I agree.
Sounds like a defective cable.
I have a Mac so I never worry about drivers and such.
Click to expand...
Click to collapse
I don't think the cable is defective, I've tried 3 cables not so far and they all work with other devices.
ppbatman said:
I will definitely try this tonight when I get home from work. Thanks very much for the suggestion.
Click to expand...
Click to collapse
If it does work, I don't want the $25.
I want you to donate the $25 to @BeansTown106 - preferably under my name, but that last bit isn't required
For those who are unaware, Beans is the developer of PureNexus ROMs.
Wiltron said:
If it does work, I don't want the $25.
I want you to donate the $25 to @BeansTown106 - preferably under my name, but that last bit isn't required
For those who are unaware, Beans is the developer of PureNexus ROMs.
Click to expand...
Click to collapse
No problem at all, it will be the best $25 I even spent. Not having this phone work is major butt hurt
tech_head said:
I agree.
Sounds like a defective cable.
I have a Mac so I never worry about drivers and such.
Click to expand...
Click to collapse
Plugged it in to the mac and still nothing. Mac has fastboot and adb installed, confirmed it working with nexus 5x. Im at a loss here.
ppbatman said:
Plugged it in to the mac and still nothing. Mac has fastboot and adb installed, confirmed it working with nexus 5x. Im at a loss here.
Click to expand...
Click to collapse
You might wanna take it to the service center. Of course, tell them that it just didn't reboot after an OTA installation.

[HELP]Device not detecting in fastboot mode

I had installed Moto drivers and also enabled the usb debugging but my my device is not showing in fastboot mode.
Seriously need help.
Thank you.
Just to clarify, when you reboot your device into the bootloader (fastboot), if you type the command 'fastboot devices' (without quotes) in ADB, you get nothing showing up in the device list?
Which Moto drivers are you using, what device do you have and are you issuing the commands via minimal ADB or another ADB command tool?
echo92 said:
Just to clarify, when you reboot your device into the bootloader (fastboot), if you type the command 'fastboot devices' (without quotes) in ADB, you get nothing showing up in the device list?
Which Moto drivers are you using, what device do you have and are you issuing the commands via minimal ADB or another ADB command tool?
Click to expand...
Click to collapse
I am using Motorola device manager drivers and using minimal adb tools
When I type command mfastboot devices nothing shows.
And I am trying to flash TWRP recovery it's saying waiting for device
Robinson#2 said:
I am using Motorola device manager drivers and using minimal adb tools
When I type command mfastboot devices nothing shows.
And I am trying to flash TWRP recovery it's saying waiting for device
Click to expand...
Click to collapse
Turn on your phone and run " adb devices " then see if it's getting connected in power on mode or not.. if not then try to install Adb Drivers..
Tried with ADB drivers still not working. I think its a driver problem how to reset drivers in Windows 10 machine
Robinson#2 said:
Tried with ADB drivers still not working. I think its a driver problem how to reset drivers in Windows 10 machine
Click to expand...
Click to collapse
It's same as you do in other Windows, go to "Device Manager" you will find device related name in that Tree,
Uninstall it and update again..
____Mdd said:
It's same as you do in other Windows, go to "Device Manager" you will find device related name in that Tree,
Uninstall it and update again..
Click to expand...
Click to collapse
Tried that but didn't worked
Robinson#2 said:
Tried that but didn't worked
Click to expand...
Click to collapse
Is it same computer that you used to unlock?
Had it worked to get unlock data and for unlocking..?
____Mdd said:
Is it same computer that you used to unlock?
Had it worked to get unlock data and for unlocking..?
Click to expand...
Click to collapse
Yes it's the same computer I used to unlock bootloader and flashed stock nougat with fastboot method 3 months back.
Robinson#2 said:
Yes it's the same computer I used to unlock bootloader and flashed stock nougat with fastboot method 3 months back.
Click to expand...
Click to collapse
If installing drivers again, use of different USB port, different data cable don't work then better to use different PC..
____Mdd said:
If installing drivers again, use of different USB port, different data cable don't work then better to use different PC..
Click to expand...
Click to collapse
I am going to try with a bootable pendrive with linux mint.
Robinson#2 said:
Tried with ADB drivers still not working. I think its a driver problem how to reset drivers in Windows 10 machine
Click to expand...
Click to collapse
If you're on Windows 10 with an UEFI firmware, I recall you need to disable driver signature enforcement if you wish to use fastboot. Credit to: https://forum.xda-developers.com/showpost.php?p=70792544&postcount=2028
Hopefully it'll work with the Linux distro though
echo92 said:
If you're on Windows 10 with an UEFI firmware, I recall you need to disable driver signature enforcement if you wish to use fastboot. Credit to: https://forum.xda-developers.com/showpost.php?p=70792544&postcount=2028
Hopefully it'll work with the Linux distro though
Click to expand...
Click to collapse
This was very helpful. Took me hours to find it but glad I did. On to step 2. lol How I was able to fix not being able to load anything in fastboot was this.
1. I right clicked on the Motorola_Mobile_Drivers_64bit.msi and selected uninstall. Repair did nothing.
2. Rt click view properties of Motorola_Mobile_Drivers_64bit.msi.
3. On the general tab I noticed it was blocked so I unblocked it.
4. Then switched to Compatibility tab.
5. Selected run compatibility mode, any previous version of windows.
--This stops the version checker
6. Hit apply save and ran it.
MrTwigglesworth said:
This was very helpful. Took me hours to find it but glad I did. On to step 2. lol How I was able to fix not being able to load anything in fastboot was this.
1. I right clicked on the Motorola_Mobile_Drivers_64bit.msi and selected uninstall. Repair did nothing.
2. Rt click view properties of Motorola_Mobile_Drivers_64bit.msi.
3. On the general tab I noticed it was blocked so I unblocked it.
4. Then switched to Compatibility tab.
5. Selected run compatibility mode, any previous version of windows.
--This stops the version checker
6. Hit apply save and ran it.
Click to expand...
Click to collapse
Bro i didi not detecting please help

Bootloader no longer seen in 'adb devices'

After moving to Lineage 14 from stock 21s, I came to realize Android Pay will not work if the bootloader is unlocked.
So I went to go and lock the bootloader (with TWRP and Lineage still installed) and for some reason when I do a "adb devices" the phone is not seen.
I uninstalled the driver, reinstalled.
Tried unplugging, launching ADB, then plugging in..
Plugging in then launching ADB...
Then i put ADB on my wife's laptop (A PC I have never plugged the leeco pro 3 on to), then plugged in for the first time already in fast boot. Still no dice.
Anyone have any ideas?
How about using Magisk to bypass SafetyNet check instead of locking your bootloader?
kaneorotar said:
How about using Magisk to bypass SafetyNet check instead of locking your bootloader?
Click to expand...
Click to collapse
That is what I am doing, but I am still concerned about the ADB not seeing the phone in fastboot mode. If I have some type of catastrophic issue where i need to restore from fastboot i will be screwed.
ekeefe41 said:
That is what I am doing, but I am still concerned about the ADB not seeing the phone in fastboot mode. If I have some type of catastrophic issue where i need to restore from fastboot i will be screwed.
Click to expand...
Click to collapse
If you boot into fastboot mode (Volume Up + Power), does the phone show up in 'fastboot devices'?
If so, then IMHO you should be fine in catastrophic situation.
kaneorotar said:
How about using Magisk to bypass SafetyNet check instead of locking your bootloader?
Click to expand...
Click to collapse
kaneorotar said:
If you boot into fastboot mode (Volume Up + Power), does the phone show up in 'fastboot devices'?
If so, then IMHO you should be fine in catastrophic situation.
Click to expand...
Click to collapse
No, that is the issue, lol
Do you have adb drivers, and did you try completely deleting your device drivers from Device Manager, then reinstalling them by plugging your phone in via USB Debugging? Are you using the platform-tools package? Did you connect via USB Debugging, and did you authorize the computer (the message should pop up on your phone)? I can't fathom why your phone wouldn't be recognized...
sk8223 said:
Do you have adb drivers, and did you try completely deleting your device drivers from Device Manager, then reinstalling them by plugging your phone in via USB Debugging? Are you using the platform-tools package? Did you connect via USB Debugging, and did you authorize the computer (the message should pop up on your phone)? I can't fathom why your phone wouldn't be recognized...
Click to expand...
Click to collapse
Yes to everything, lol
And when I am connected to the phone while in the OS, ADB works fine, shows in when I "ADB devices"
Where'd you get your phone from? Banggood, Geekbuying, Gearbest? Did it come with a vendor ROM? Did it not pass SafetyNet on the original ROM it came with?
Are you following these instructions? Of course, replace the required stock ROM with the one for your version (x720 or x727). So does the issue come up when you reboot the phone via ADB while in the OS?
In any case, try asking on the http://www.leeco.re/ forums as well.

Categories

Resources