Develop Bugs

Any drawbacks of unlocking bootloader?

I plan to unlock my bootloader, but not rooting the phone yet, want to see if I can live without root. But in case I find out I couldn't I don't want to wipe my device again, thus unlocking now before actually moving all my stuff over from my old Nexus.
My question is, does it have any drawback to unlock bootloader? Does it actually affect anything (besides the hyper-annoying nag screen on boot), that would make it better just to leave it locked, and do the wipe and everything only if I ever decide to actually root it? Tough decision, I'd love to hear your opinions.
Thank you!

Assuming you aren't flashing TWRP, right?
Drawbacks... Security, maybe? Can't really think of anything else. OTAs will still work, as will all the usual upsides.
Upside, you can flash the latest factory images as soon as they are released.

PhoenixTank said:
Assuming you aren't flashing TWRP, right?
Click to expand...
Click to collapse
Yes, no flashing nothing, just a plain fastboot oem unlock, then pretending to be a basic user with a locked phone. I wonder if from the OS side anything can be perceived by apps, security/integrity checks, etc.

Yeah, then nothing in android will know, apart from the checkbox you need to enable in developer options.
Only when you change the boot or system images, does it really flag up anything. Hope that helps.

Addendum in case someone comes by this thread: unlocking makes you lose device protection features, or at least checking the box that lets you unlock does. Not sure what's going to happen with the checkbox after actually doing the unlock, will soon find out.

IVBela said:
Addendum in case someone comes by this thread: unlocking makes you lose device protection features, or at least checking the box that lets you unlock does. Not sure what's going to happen with the checkbox after actually doing the unlock, will soon find out.
Click to expand...
Click to collapse
It stays checked. I haven't tried to unchecked it yet

IVBela said:
Addendum in case someone comes by this thread: unlocking makes you lose device protection features, or at least checking the box that lets you unlock does. Not sure what's going to happen with the checkbox after actually doing the unlock, will soon find out.
Click to expand...
Click to collapse
What are these 'protection features' that we would be losing if checking the OEM Unlocking (I assume you mean?) box??

sordup said:
What are these 'protection features' that we would be losing if checking the OEM Unlocking (I assume you mean?) box??
Click to expand...
Click to collapse
This. So far this is the only drawback I found.

IVBela said:
This. So far this is the only drawback I found.
Click to expand...
Click to collapse
Not really sure what device protection does, as Android Device Manager still works.
Android Device Manager lets you remotely locate, lock, wipe, or ring your phone. So for example if someone stole your phone and you have Android Device Manager installed, you can locate it, and also lock it until the police can find it.

gleggie said:
Not really sure what device protection does, as Android Device Manager still works.
Android Device Manager lets you remotely locate, lock, wipe, or ring your phone. So for example if someone stole your phone and you have Android Device Manager installed, you can locate it, and also lock it until the police can find it.
Click to expand...
Click to collapse
It may work with casual thug. Sophisticated thief will turn device off, reboot into bootloader, wipe device and take possession. Device protection is meant to discourage theft.
https://support.google.com/nexus/answer/6172890?hl=en

I'm having some difficulty getting my Mac to recognize my 5x. I am able to connect to the phone with USB debugging normally when I first plug it in. The command ./adb devices lists the phone, and I am able to use adb reboot bootloader to reboot into fastboot mode. But once rebooted, the computer loses contact with the phone: ./adb devices returns nothing. Has anyone else seen this? Got a fix? Thanks. I should also note that I have enabled unlocking the bootloader in developer options.

Jemmy Ducks said:
I'm having some difficulty getting my Mac to recognize my 5x. I am able to connect to the phone with USB debugging normally when I first plug it in. The command ./adb devices lists the phone, and I am able to use adb reboot bootloader to reboot into fastboot mode. But once rebooted, the computer loses contact with the phone: ./adb devices returns nothing. Has anyone else seen this? Got a fix? Thanks. I should also note that I have enabled unlocking the bootloader in developer options.
Click to expand...
Click to collapse
There are three sets of drivers needed. One for fastboot, one for adb and one for MTP. When device is in fastboot mode you use command "fastboot devices" or Mac equivalent.

gleggie said:
Not really sure what device protection does, as Android Device Manager still works.
Android Device Manager lets you remotely locate, lock, wipe, or ring your phone. So for example if someone stole your phone and you have Android Device Manager installed, you can locate it, and also lock it until the police can find it.
Click to expand...
Click to collapse
This doesn't help if they get your device and factory reset it. If they factory reset it before you have a chance to lock it down then you are screwed. With device protection even when you factory reset it, it will prompt for the previous google account the phone was set up with. If your bootloader is unlocked and they are knowledgeable thieves then they can just reflash everything and wipe it out fully.
I work at Swappa and we see this all the time. Someone will sell their device, factory reset it and send it to the buyer. The buyer gets it and can't set it up because device protection was enabled and it prompts them for the previous google account info that was tied to the phone when they try to set it up

Jemmy Ducks said:
I'm having some difficulty getting my Mac to recognize my 5x. I am able to connect to the phone with USB debugging normally when I first plug it in. The command ./adb devices lists the phone, and I am able to use adb reboot bootloader to reboot into fastboot mode. But once rebooted, the computer loses contact with the phone: ./adb devices returns nothing. Has anyone else seen this? Got a fix? Thanks. I should also note that I have enabled unlocking the bootloader in developer options.
Click to expand...
Click to collapse
I tried using fastboot anyway, despite seeing no devices listed, and lo and behold, it worked. Bootloader unlocked for flashing.

HTC one m8 in a boot loop

Hi all.
I suspect this question has been asked before and I have found loads on how to do's, but I can't seem to achive what is needed, so any help, however small is greatly appriciated.... he goes.
Customer has brought in an HTC One M8. Details I can give from the Fastboot screen is:-=
***Software Status: Official***
***LOCKED***
M8_UL_CA PVT SHIP S-OFF
CID-111111111 (<---- 8X1'S)
HBOOT-3.10.0.0000
RADIO-1.29.214500021.12G
OpenDSP-V51.2.2-00593-M8974_FO.1015
OS-6.12.401.1
eMMC-boot 2048MB
Dec 17 2015,14:15:48.3
It is stuck in a boot loop that alsways shows the HTC boot screen, reboots to the HTC screen and promptly then to the Android recovery screen:-
Android Recovery
HTC/htc_m8/htc_m8
6.0/MRA58K/buildteam12171409
user/release-keys
Use volume up/down and power
Reboot system now
Reboot to bootloader
Apply update from ABD
Apply update from SD card
Wipe data/factory reset
Wipe cache partition
Power off
_________________________________
Supported API:3
handle_cota_install: install cwpkg to /cache/data/cwtemp/cwpkg.zip
handle_cota_install: install cwprop tp /cache/data/cwtemp/cw.prop
Write host_mode success
handle_cota_install: No CW files. Skip cw installation
Sorry to have to type this in as I cant seam to get images to upload.
Now, this seems to be a common problem and most suggestions are re flash the firmware using RUU. The first stumbling block I am hitting is the phone is not being detected on any PC that I use, by any cable I use, either by Windows ( USB detected sound plays and disconnected plays if I unplug but no detection in device manager, I have loaded the HTC ABD drivers, installed HTC manager and Android studio but again no detection) or on a Mac.
Question is, can I reset this phone back to a working state or should I direct the customer back to a HTC service centre?
BTW the phone phone is a European model and currently on 3.
Thanks in advance.
Marc

PC1staid said:
Now, this seems to be a common problem and most suggestions are re flash the firmware using RUU. The first stumbling block I am hitting is the phone is not being detected on any PC that I use, by any cable I use, either by Windows ( USB detected sound plays and disconnected plays if I unplug but no detection in device manager, I have loaded the HTC ABD drivers, installed HTC manager and Android studio but again no detection) or on a Mac.
Click to expand...
Click to collapse
Try another USB cable, and another port on the PC.
Also, go into bootloader, select fastboot (if not highlighted in red already) using vol keys, and confirm with power button. Then see if the phone's serial number is returned with the command: fastboot devices
PC1staid said:
Question is, can I reset this phone back to a working state or should I direct the customer back to a HTC service centre?
BTW the phone phone is a European model and currently on 3.
Click to expand...
Click to collapse
Its not the Euro version. Its US version, hacked to accept Euro software. Due to this, and SuperCID (11111111) its obviously been modified, and HTC won't honor any warranty (if that is what you are asking).
I also wouldn't be surprised if the back cover was replaced (again, voiding the warranty). What does the model number on the back say?

redpoint73 said:
Try another USB cable, and another port on the PC.
Attempted this with 2 PC's, 1 Laptop all running Windows 7 Pro with SP1 64 bit and a Mac. Tried the cable that came with my Samsung S5 ( Not the USB 3 cable) plus 2 other cables that I use in the workshop and the original cable suppled by the customer. Phone not detected in device manager on any of the PC's, however the plugged in and unplugged sounds do play. Mac sit's idoly twiddleing its thumbs...
Also, go into bootloader, select fastboot (if not highlighted in red already) using vol keys, and confirm with power button. Then see if the phone's serial number is returned with the command: fastboot devices
Went into bootloader and fastboot. only option I have to locate the S/N is via show barcodes. the S/N is:- HT444WM04348
Its not the Euro version. Its US version, hacked to accept Euro software. Due to this, and SuperCID (11111111) its obviously been modified, and HTC won't honor any warranty (if that is what you are asking).
I dont think it would be under warranty as customer reckons it is over 12 months old.
I also wouldn't be surprised if the back cover was replaced (again, voiding the warranty). What does the model number on the back say?
Click to expand...
Click to collapse
Shown on the back is OP6B110 M8x
Hope this gives some more helpfull info.

PC1staid said:
Shown on the back is OP6B110 M8x
Hope this gives some more helpfull info.
Click to expand...
Click to collapse
Now that you mention that, I think there may be an Australian variant (OP6B110) which also has the product ID (M8_UL_CA) indicated on the bootloader screen.
Either way, its not the Euro variant; and its been modified by a previous owner (as mentioned).
Any luck getting USB fastboot working? Once you do, do fastboot getvar all, and post the output (delete IMEI and serial number before posting) so we can verify the MID and make sure you are running the right RUU.

exactly the same problem
Hi.. I have also been facing the same problem since today morning. phone completely conked off and not connecting to pc either. the connecting and disconnecting sound is there but device driver error so not installed. pls help... phone model is OP6B100. Bought from US and being used in India

sonalgirdhar said:
Hi.. I have also been facing the same problem since today morning. phone completely conked off and not connecting to pc either. the connecting and disconnecting sound is there but device driver error so not installed. pls help... phone model is OP6B100. Bought from US and being used in India
Click to expand...
Click to collapse
No, its not the same problem. The OP is in a bootloop, which is very different from the screen not coming on.
Folks need to stop saying "same problem", because it really never never never is. Just a minor detail or 2 that is different, makes a huge impact on the condition and the way forward.
Leave the phone on charger for several hours, and then hold power for 30 seconds of so, and see if you can get the screen to come on.
If the screen doesn't come on, there isn't much we can do.

redpoint73 said:
No, its not the same problem. The OP is in a bootloop, which is very different from the screen not coming on.
Folks need to stop saying "same problem", because it really never never never is. Just a minor detail or 2 that is different, makes a huge impact on the condition and the way forward.
Leave the phone on charger for several hours, and then hold power for 30 seconds of so, and see if you can get the screen to come on.
If the screen doesn't come on, there isn't much we can do.
Click to expand...
Click to collapse
Sorry I meant I am also getting the same screen with phone stuck in bootloop amd not moving beyond this screen.

sonalgirdhar said:
Sorry I meant I am also getting the same screen with phone stuck in bootloop amd not moving beyond this screen.
Click to expand...
Click to collapse
"completely conked off" (your previous words) is not a good description of the above. Misleading, really.
Hold the vol down button during the bootloop cycle. Don't let go until you are on the bootloader screen. Then try to connect with fastboot.

My HTC is having same error after Android 6.0 update.
It's not getting connected to pc.. I bought my phone in USA and now using it in UK.
Called HTC and they said they will not accept US phone for repair even though it's in warranty..

tushard007 said:
My HTC is having same error after Android 6.0 update.
It's not getting connected to pc.. I bought my phone in USA and now using it in UK.
Called HTC and they said they will not accept US phone for repair even though it's in warranty..
Click to expand...
Click to collapse
Hi.. Did u find any solution to the problem. The service center here also refused to take a phone bought outside india.

Hi..
Please find attached the result of 'fastboot getvar all'. i had also shared the same with HTCDev team and the reply is as below:
"Hello Sonal
I sincerely thank you for sending us the information that was requested . According to the information you have provided, I was able to identify the reason why the device can not receive updates at this time. For your device to without any problem , it must have all the original software or settings and STOCK.
To begin , let me explain how our devices are distributed to security S -ON to protect your settings and to ensure proper operation. Security on your device has been disabled ( S -OFF) which has allowed the following parameters change at this time prevent the upgrade is installed
cidnum : 11111111 < ---- this parameter will not get your device updates
Here are the options for you:
Option 1 - Return all device settings to their original settings or STOCK. - First you must change the parameters specified as these were originally. Once this is done, now again to contact STOCK install the operating system.At this time, HTC doesn't officially support obtaining S-Off on our devices. Having said that, I'll be happy to take a look at what's going on and at least point you in the right direction. I know this may cause some limitations in the assistance I am able to provide to you but I am more than happy to do what I can to assist you through your issue . We are happy if you contact us about any problems you might, in any part of their development process. .To begin with, the following websites are some examples where we recommend you start your research on S-Off. http://forums.xda-developers.com http://www.androidcommunity.com http://androidforums.com Please note the above web sites are not operated by HTC. We can not validate or guarantee the information contained therein.
Do not hesitate to reach out to us if you have any questions. You can contact us back via email, using the second link listed below (The one at the end of the sentence "To send a reply to this message, please click here"). "
Can you please help with the next steps to get the phone working again.

sonalgirdhar said:
Please find attached the result of 'fastboot getvar all'.
Click to expand...
Click to collapse
Flash the 6.12.401.4 RUU.
See the download in Post #3 of the following thread, and instruction in Post #17 of that thread: http://forum.xda-developers.com/htc-one-m8/general/marshmallow-6-0-update-htc-m8-european-t3296141
sonalgirdhar said:
i had also shared the same with HTCDev team and the reply is as below:
Click to expand...
Click to collapse
Asking HTC for support by sharing info that indicates your phone was modded, was a bad idea. Of course they are going to say "we don't support this" and "return the phone to stock".
No need to go back s-on or change CID. Just run the RUU as I mentioned.
---------- Post added at 10:06 AM ---------- Previous post was at 10:04 AM ----------
tushard007 said:
My HTC is having same error after Android 6.0 update.
It's not getting connected to pc..
Click to expand...
Click to collapse
USB connection issues are usually due to issues on the PC, not the phone.
Try a different cable, different USB port (as I suggested in a previous post). Install (or re-install) HTC Sync. You may even need to try a different PC (Win7 and USB 2.0 get the best results).
Also, bear in mind that phone needs to be in bootloader-fastboot mode, for fastboot commands to work. Booted into OS or recovery for adb to work.

redpoint73 said:
Flash the 6.12.401.4 RUU.
See the download in Post #3 of the following thread, and instruction in Post #17 of that thread: http://forum.xda-developers.com/htc-one-m8/general/marshmallow-6-0-update-htc-m8-european-t3296141
Asking HTC for support by sharing info that indicates your phone was modded, was a bad idea. Of course they are going to say "we don't support this" and "return the phone to stock".
No need to go back s-on or change CID. Just run the RUU as I mentioned.
---------- Post added at 10:06 AM ---------- Previous post was at 10:04 AM ----------
USB connection issues are usually due to issues on the PC, not the phone.
Try a different cable, different USB port (as I suggested in a previous post). Install (or re-install) HTC Sync. You may even need to try a different PC (Win7 and USB 2.0 get the best results).
Also, bear in mind that phone needs to be in bootloader-fastboot mode, for fastboot commands to work. Booted into OS or recovery for adb to work.
Click to expand...
Click to collapse
@redpoint73 Thank you so much, have been able to update the RUU. Updating apps now

How to Enable OEM Unlock without enabling USB debugging/OEM status

didn't enable developer options on this phone seeing that I was primarily going to use this phone as my daily driver so I carried on using the phone as is. the next day my phone show me an error, it said "Your device is corrupt. It can't be trusted and may not work properly." (Red) and I proceeded to link it showed me to see what the problem might be.
A few minuets after it showed me that error my phone shut down and couldn't turn on. I tried everything to reboot it but to no success, I was able boot it in fastboot mode and downloaded all the appropriate tools to do a flash install of a factory default image,I got the default operating system that the phone came with, as well as adb-tools required to perform a system wide flash seeing as i didn't have that much data on it.
Once everything was set, I followed the step by step instructions that google provided me on the restore to factory setting pages "https://developers.google.com/android/nexus/images". Seeing as I didn't enable developer options when my phone was working, I run into a prerequisite that needed that before I could flash my device.
While running the commands in cmd as an administrator, I run the command -
fastboot flashing unlock command and the console responded with -
FAILED (remote: oem unlock is not allowed)
I went back and reread this step, which was step number 4, It indicated "If necessary, unlock the device's
bootloader by running" the command. so i figured maybe it isn't really necessary, I proceeded to run the flash-all.bat
script, and it FAILED at every step saying -
FAILED (remote: device is locked. Cannot flash) //corresponding .img file//
It failed to flash my nexus 5x at every stage. So I did some research and found out that the problem was
that in the fastboot menu, the Device state was locked in a very assuring green color, and every where I
searched it indicated that this option to unlock the device was in the developer settings in the phones
OS, which is rather odd to put such a feature in the phones OS and fail to include the option in the fastboot menu. I
couldn't find any tool or assistance change the status of the device state to unlocked.
Now my question is, how can I change the device state to unlocked without enabling this options prior in the OS seeing
as i cant do that because my phone isn't coming on at all. any assistance or help would be highly appreciated.
Point of clarification, I have tried everything in accordance to what google nexus support pages have showed
me to the letter.

You can't enable OEM unlock by fastboot/recovery.
But there's another way to rescue your phone.
So
Can you boot into recovery? (Bootloader mode switch to recovery mode using volume keys and press power to choose it)
If it started and you would see an Android with an red triangle press power and hit volume+ to turn on menu. If it works you are safe.
Then download OTA image from Android developers page (OTA, not factory), launch command line (I don't know how it works on Windows, I've never flashed anything on Windows )
And you will need to flash this OTA image by executing adb sideload nameofpackage.zip
Remember to choose adb sideload in recovery first and then executing a command. It should flash and your phone should work.
Good luck!
Wysłane z mojego Nexus 5X przy użyciu Tapatalka

I cant boot in recovery mode... When I tried to boot in recovery stuck in google logo then power off...

Oh that's not good.
Do you have warranty on your phone?
The last thing I keep in mind is flashing using LG tool, but I might take a look on it because I don't know how to use it.
Wysłane z mojego Nexus 5X przy użyciu Tapatalka

No not in warranty....
I contact in LG service center they said chage the motherboard and cost around 170$
That amount so big??

Is there any method to unlock in this case from fastboot?
I need to unlock for custom kernel to flash.
Im on bootloop and oem locked in the system (befor got bootloop)
Help

Domin_PL said:
Oh that's not good.
Do you have warranty on your phone?
The last thing I keep in mind is flashing using LG tool, but I might take a look on it because I don't know how to use it.
Wysłane z mojego Nexus 5X przy użyciu Tapatalka
Click to expand...
Click to collapse
try to >>>Nexus Root Toolkit<<<
Do you your computer can see phone

There where some hidden fastboot commands on XDA. Maybe you can try some of them to see if they can go around this limitation.
Sent from my Nexus 5X using Tapatalk

akins0405 said:
try to >>>Nexus Root Toolkit<<<
Do you your computer can see phone
Click to expand...
Click to collapse
I have the same issue mentioned above. Downloaded Nexus Root Toolkit and i have tried unlock through Nexus Root Toolkit. It seems failure. Because, After detecting my device it reboots and my phone reboots and shows the google logo and reboot again and again... My phone will not boot into recovery mode. While we click on it, it shows google logo and reboots again and again... Is there any solution for this?

OMG!!!
I Have the exact same issue with my bq aquaris x5
I really wish someone would find a solution for this

Seems options are very limited now
Having exact same issue with Huawei Y3. After spending the whole day, came to the conclusion that there is now only two options left: a) Replace the motherboard. b) pay £15 at dc unlock website to unlock oem. Not decided which one should i go for..

I got the same issue.
Nexus 5X has no activated "Allow OEM Unlock".
I tried with the Nexus Root Toolkit.
When I try to unlock Bootloader or the option "Fix Bootloop" he wants me to put the phone into Fastboot.
When I put phone into Fastboot he recognizes it and then restarts the phone. From now on nothing more happens, because noe the bootloop is "active" again.
Recovery Mode is not working, too.
Before I can access it, bootloop starts.
Sound as the same issue as @tomsonmathewv has.
Can someone help me?
EDIT:
While I tried some other solutions my Nexus 5X booted and booted.
And suddenly it booted one time to the Pattern screen. I entered the pattern and waited again for the bootloop after google animation.
But then the google animation finished and a short black screen with s small blue line in the middle of the display appeared. Looked like a "graphics error". But then immediately the normal phone idle screen appeared. The phone started!
I immediately went to the DEV-Options and Allowed OEM-unlock. And I took screenshots of the current configuration.
The current Android is 8.1
Is it recommended to flash an older version of Android to prevent a new Bootloop?

I had the same issue after the latest Android update on my Nexus 5X.
Have you left the device in charge before it manage to start?
Thanks
EDIT: Solved leaving it unplugged.

Hey buddy try Nexus Root Toolkit v2.1.9 it will unlock your bootloader without turning your phone on it worked for me.

aadeekhan79 said:
Hey buddy try Nexus Root Toolkit v2.1.9 it will unlock your bootloader without turning your phone on it worked for me.
Click to expand...
Click to collapse
NRT isn't going to work unless you previously allowed for oem unlock in developer options. If you haven't done that and you can't boot into recovery or the system you're kind of sol.
Sent from my [device_name] using XDA-Developers Legacy app

Shuhan44 said:
Having exact same issue with Huawei Y3. After spending the whole day, came to the conclusion that there is now only two options left: a) Replace the motherboard. b) pay £15 at dc unlock website to unlock oem. Not decided which one should i go for..
Click to expand...
Click to collapse
does that software (dc unlocker) actualy works? i've got the same issue with honor 8 pro, which opt. you have selected.

In my case before my N5X started bootlooping I allowed OEM unlock but didn't enabled USB Debugging Mode in Developer options. Is there a way to unlock bootloader with USB Debugging Mode disabled? I want to try the UNBLOD tool, but unlocked bootloader is a requirement.

xrehpicx said:
OMG!!!
I Have the exact same issue with my bq aquaris x5
I really wish someone would find a solution for this
Click to expand...
Click to collapse
Hi
I also need help of a slightly different nature. I'm somehow locked out of my Huawei P10 whereby my unlock pattern is no longer recognized. USB debugging is not enabled. What are my option as i really do not want to factory reset the phone, did not backup data. Coincidentally enough, this occurred after the latest software update. Please can someone help me.

Thanks
Thanks

Roshan0746 said:
didn't enable developer options on this phone seeing that I was primarily going to use this phone as my daily driver so I carried on using the phone as is. the next day my phone show me an error, it said "Your device is corrupt. It can't be trusted and may not work properly." (Red) and I proceeded to link it showed me to see what the problem might be.
A few minuets after it showed me that error my phone shut down and couldn't turn on. I tried everything to reboot it but to no success, I was able boot it in fastboot mode and downloaded all the appropriate tools to do a flash install of a factory default image,I got the default operating system that the phone came with, as well as adb-tools required to perform a system wide flash seeing as i didn't have that much data on it.
Once everything was set, I followed the step by step instructions that google provided me on the restore to factory setting pages "https://developers.google.com/android/nexus/images". Seeing as I didn't enable developer options when my phone was working, I run into a prerequisite that needed that before I could flash my device.
While running the commands in cmd as an administrator, I run the command -
fastboot flashing unlock command and the console responded with -
FAILED (remote: oem unlock is not allowed)
I went back and reread this step, which was step number 4, It indicated "If necessary, unlock the device's
bootloader by running" the command. so i figured maybe it isn't really necessary, I proceeded to run the flash-all.bat
script, and it FAILED at every step saying -
FAILED (remote: device is locked. Cannot flash) //corresponding .img file//
It failed to flash my nexus 5x at every stage. So I did some research and found out that the problem was
that in the fastboot menu, the Device state was locked in a very assuring green color, and every where I
searched it indicated that this option to unlock the device was in the developer settings in the phones
OS, which is rather odd to put such a feature in the phones OS and fail to include the option in the fastboot menu. I
couldn't find any tool or assistance change the status of the device state to unlocked.
Now my question is, how can I change the device state to unlocked without enabling this options prior in the OS seeing
as i cant do that because my phone isn't coming on at all. any assistance or help would be highly appreciated.
Point of clarification, I have tried everything in accordance to what google nexus support pages have showed
me to the letter.
Click to expand...
Click to collapse
Every phone have boot. Img system . I also have a same fault redmi k20 pro. But i succeed to give rebirth it. Try to using fastboot commands only and flash fastboot flash boot boot. Img it will work definitely

Unlock Bootloader & Root Moto Z2 Force

To unlock Bootloader:
On Phone:
Open Developer Mode: Settings>System>About Phone>Click "Build Number" Seven Times
Go back to System>Developer Options>Turn on: OEM Unlocking & USB Debugging
On PC:
Do Google Search for Downloads:
Download: adb and fastboot
Download: appropriate phone drivers
Connect Phone to PC
Open: adb & fastboot Folder>open Command Prompt/PowerShell
Type:
adb devices (Pop-up will appear on phone to allow USB debugging)
re-type adb devices (you should see your device)
adb reboot bootloader
fastboot devices
fastboot oem get_unlock_data (this data is used in the Motorola Website: https://motorola-global-portal.custh...-your-device-a)
Once logged in, put in above unlock data in to see if phone is able to be unlocked...click unlock.
You'll receive a unique unlock code via email....copy unlock code.
Go back to Command Prompt/PowerShell
Type:
fastboot oem unlock (unique unlock code) (type in twice to confirm unlocking)
(NOTE: ALL DATA WILL GET DELETED-BACK IT UP!)
If this isn't working, what hiccups are you running into?
To Root your device:
On Phone:
Make sure: Developer Options on>OEM Unlocking & USB Debugging turned on (steps above)
Connect (turned on) Device to PC
On PC:
download (TWRP file specific to phone: https://twrp.me/Devices/): EXAMPLE: twrp-3.2.3-0-nash.img
Open/Create new/clean adb/fastboot folder
place TWRP img file INTO the above folder
Download: Magisk-V18.0.zip (https://forum.xda-developers.com/app...mless-t3473445)
Place Magisk-V18.0 Zip file into adb/fastboot folder
Once all files within adb/fastboot folder, open Command Prompt/PowerShell
adb devices
adb reboot bootloader
fastboot devices
fastboot boot twrp-3.2.3-2-nash ((add: .img)) Phone should open Team Win Recovery
ON PHONE: Swipe to "Allow Modification"
adb devices (should show "recovery")
adb push Magisk-V18.0.zip /sdcard
adb shell twrp install /sdcard/Magisk-V18.0.zip (phone should show installation)
adb reboot
On Phone:
Open: Magisk Manager
select lines in upper left hand corner>Settings>Automatic Response>Grant
Open "Root Checker App" to verify root (i.e., Root Checker Pro, Root Checker Advanced)

JTC Intl said:
To unlock Bootloader:
[NOTE: device with root access no longer receives official update notifications from the manufacturer)
Click to expand...
Click to collapse
Mine did until I went into Developer Setting and un ticked automatic software updates..

I thought I had found the perfect Z2 for me. Ordered on eBay for $130 with no scratches and very slight screen burn-in. I don't worry about light burn-in as I always use Substratum and turn all my screens amoled black with light text, I never notice the burn-in anyway.
Only problem was it being a T-Mo version but I couldn't unlock the bootloader. I did all that was required to receive the Unlock Code, however, when I input it the second time, it states "code verification failure." Verifed correct code multiple times and upon checking the Motorola unlock help thread, there is a list at the beginning with CID #s of bootloaders that can be unlocked and those that can not. Any CID not listed as "can be unlocked" are unable to be unlocked even if the # does not appear under "cannot be unlocked" list. My CID of 0x0015 was not on either list, therefore deemed unlockable.
I saw someone else inquire about his 0x0015 CID and was told pretty much that same thing, so I didn't add to the thread and just returned the phone. Now I am looking to purchase another T-Mo phone from a different seller with hopes of receiving a compatible CID, but I'm kinda concerned about running into the same issue. Are you aware if there are large group of these T-Mobile phone who's bootloaders can't be unlocked or did I just get a one off CID#. Or should I be looking at rooting a Sprint version and trying to change it to a GSM Unlocked or are there Sprint version with unlockable bootloaders as well? Any advice as how you think I should proceed would be most helpful as I would like to order the replacement phone today or tomorrow. TIA

MrBrazil1911 said:
I saw someone else inquire about his 0x0015 CID and was told pretty much that same thing, so I didn't add to the thread and just returned the phone. Now I am looking to purchase another T-Mo phone from a different seller with hopes of receiving a compatible CID, but I'm kinda concerned about running into the same issue. Are you aware if there are large group of these T-Mobile phone who's bootloaders can't be unlocked or did I just get a one off CID#. Or should I be looking at rooting a Sprint version and trying to change it to a GSM Unlocked or are there Sprint version with unlockable bootloaders as well? Any advice as how you think I should proceed would be most helpful as I would like to order the replacement phone today or tomorrow. TIA
Click to expand...
Click to collapse
If you're a T-Mobile/Metro user the TMO model is ideal. It packs every Magenta band aside from B71. The Sprint version will affect your experience on T-Mobile, as it only possesses 2, 4, and 12. So no LAA, 66, nor LTE-U. B46, aka LAA is stupid fast. I've heard U is good too, but availability is limited.
Now, if you use ATT, VZ, or Sprint you won't miss out on anything by buying the Sprint version.
All things considered, I'd gamble with the former. Playing the TMO lottery is definitely worth it. In fact, I bought a 2nd one and will see what happens in a few days.

Ace42 said:
If you're a T-Mobile/Metro user the TMO model is ideal. It packs every Magenta band aside from B71. The Sprint version will affect your experience on T-Mobile, as it only possesses 2, 4, and 12. So no LAA, 66, nor LTE-U. B46, aka LAA is stupid fast. I've heard U is good too, but availability is limited.
Now, if you use ATT, VZ, or Sprint you won't miss out on anything by buying the Sprint version.
All things considered, I'd gamble with the former. Playing the TMO lottery is definitely worth it. In fact, I bought a 2nd one and will see what happens in a few days.
Click to expand...
Click to collapse
Thanks for the feedback. I am primarily a T-Mo network user. I use Google Voice and just grab cheap MVNO sims from eBay and will occasionally use an AT&T sim card. So if I manual unlock it myself from instructions I've seen here, will I still retain the above bands you mentioned?

MrBrazil1911 said:
Thanks for the feedback. I am primarily a T-Mo network user. I use Google Voice and just grab cheap MVNO sims from eBay and will occasionally use an AT&T sim card. So if I manual unlock it myself from instructions I've seen here, will I still retain the above bands you mentioned?
Click to expand...
Click to collapse
Bands stay following SIM and Bootloader unlocks. But, when the modem of another model is flashed access to LTE is lost.

Trying to do this and can't get unlock code. When I type in command i just get . . . in the cmd prompt

mike2246 said:
Trying to do this and can't get unlock code. When I type in command i just get . . . in the cmd prompt
Click to expand...
Click to collapse
Make sure you're using up to date adb/fastboot files and a 2.0 usb port. If no 2.0 ports try using a hub to bring the 3.0+ ports down.

41rw4lk said:
Make sure you're using up to date adb/fastboot files and a 2.0 usb port. If no 2.0 ports try using a hub to bring the 3.0+ ports down.
Click to expand...
Click to collapse
I have used usb 3.0 all the time. Was never be a problem. But I would try, too :good: Wish the person luck

allrightlite said:
I have used usb 3.0 all the time. Was never be a problem. But I would try, too :good: Wish the person luck
Click to expand...
Click to collapse
3.0 ports won't be a problem for everyone, but for some it is. Some have only been able to use one port on their pc for flashing, some have had to use hubs to dumb their ports down. That's why it is generally recommended to use 2.0 port. Saves having to repeat the same info 100x in every other post.

This worked perfectly until the last step for my Sprint version of Z2 Force. Kudos to JTC Intl for crystal clear instructions.
When I launch the Magisk Manager , it asks me if I want to "Upgrade to full Magisk to finish set up. Download and install?" I respond OK, then after sometime, it says "There was a problem parsing the package".
Instead of v18 of Magisk, I downloaded v22 that too not as a ZIP, but it was only available as an APK from their GITHub. (https://github.com/topjohnwu/Magisk/releases/tag/v22.1)
EDIT - I tried the troubleshooting suggestions for this problem in their wiki ( clearing cache, clearing data, reinstalling etc). Did not help.
Please help. I'm almost there.
Thank you.

hi i need help is there any other way i can unlock the boot loader because when i enter my code it says device not eligible....

JTC Intl said:
To unlock Bootloader:
On Phone:
Open Developer Mode: Settings>System>About Phone>Click "Build Number" Seven Times
Go back to System>Developer Options>Turn on: OEM Unlocking & USB Debugging
On PC:
Do Google Search for Downloads:
Download: adb and fastboot
Download: appropriate phone drivers
Connect Phone to PC
Open: adb & fastboot Folder>open Command Prompt/PowerShell
Type:
adb devices (Pop-up will appear on phone to allow USB debugging)
re-type adb devices (you should see your device)
adb reboot bootloader
fastboot devices
fastboot oem get_unlock_data (this data is used in the Motorola Website: https://motorola-global-portal.custh...-your-device-a)
Once logged in, put in above unlock data in to see if phone is able to be unlocked...click unlock.
You'll receive a unique unlock code via email....copy unlock code.
Go back to Command Prompt/PowerShell
Type:
fastboot oem unlock (unique unlock code) (type in twice to confirm unlocking)
(NOTE: ALL DATA WILL GET DELETED-BACK IT UP!)
If this isn't working, what hiccups are you running into?
To Root your device:
On Phone:
Make sure: Developer Options on>OEM Unlocking & USB Debugging turned on (steps above)
Connect (turned on) Device to PC
On PC:
download (TWRP file specific to phone: https://twrp.me/Devices/): EXAMPLE: twrp-3.2.3-0-nash.img
Open/Create new/clean adb/fastboot folder
place TWRP img file INTO the above folder
Download: Magisk-V18.0.zip (https://forum.xda-developers.com/app...mless-t3473445)
Place Magisk-V18.0 Zip file into adb/fastboot folder
Once all files within adb/fastboot folder, open Command Prompt/PowerShell
adb devices
adb reboot bootloader
fastboot devices
fastboot boot twrp-3.2.3-2-nash ((add: .img)) Phone should open Team Win Recovery
ON PHONE: Swipe to "Allow Modification"
adb devices (should show "recovery")
adb push Magisk-V18.0.zip /sdcard
adb shell twrp install /sdcard/Magisk-V18.0.zip (phone should show installation)
adb reboot
On Phone:
Open: Magisk Manager
select lines in upper left hand corner>Settings>Automatic Response>Grant
Open "Root Checker App" to verify root (i.e., Root Checker Pro, Root Checker Advanced)
Click to expand...
Click to collapse
Does rooting the phone work for an AT&T Moto Z2 force phone?

Locked bootloader, cannot OEM Unlock or access USB Debugging

Short version of question: How can I unbrick my ONEPLUS 3 (A3000) if I cannot boot to Android and OEM Unlock AND USB Debugging both have not been enabled?
Long version: Phone was recently purchased second hand from a third-party market (Kijiji, kind of like craigslist for Canadians). Person I bought it from claimed in the ad that the device was in a bootloop and couldn't access the OS. I had in the past successfully saved a ONEPLUS 1 from bricked status, so I didn't feel a simple bootloop would pose much of an issue. That, and at the price he was selling I really couldn't turn it down.
I tried various different methods of restoring the phone's partitions, OS, and firmware to stock/custom, but had no real luck with any (I will list below what I have attempted). If there was a root cause of this, I believe it's due to the fact that some part of the phone's storage partition (boot or system if I had to guess) had become corrupted at some point. Given the volume of threads I've seen here and elsewhere online, I wouldn't rule out a bad OTA flash, but doesn't really matter. What does matter, however, is that the Android OS is inaccessible despite my best efforts, and the bootloader is set to locked and ADB Debugging remains off.
Generally speaking, is there a way to access Developer Options to correct both these issues through terminal or a tool? I'm confident that I can get my device working again if I could access this menu, but as of yet I have had no luck.
Methods used to restore/info worth mentioning
While I don't doubt their effectiveness at large, for whatever reason I have yet to find a tool/guide that yields the anticipated results upon completion. MSM Download Tool (V3 and V4) have both been downloaded, executed, and completed numerous times, but will still not boot past the loading screen upon completion.
According to Unified Android Toolkit, my device build is being detected as "OnePlus3 7.0 NRD90M" and All-in-One Toolkit is showing that Android 6.0.1 is installed.
Drivers are all installed correctly, as proven both via tools downloaded and through Windows CMD terminal (adb devices, fastboot devices, adb get-state, etc)
Stock recovery and bootloader modes can both be reached through both hardware keys and software commands. I will note that it seems to take longer than I'd expect to boot to either of these modes using hardware keys.
I have utilized multiple USB ports, Type-C cables, different OS' on two laptops (MS Windows 10 and 7, FWUL Linux). I usually have no problem with the device being detected by the system. When I have, it usually involved one pesky USB cord.
common commands used and their effects:
fastboot OEM unlock: fails, cannot be done remotely
fastboot flash x: fails, remote: flashing partitions not allowed
ADB push: fails. cannot access partition
ADB devices: device is seen by system with serial and state
fastboot devices: device is seen by system with serial
ADB sideload: varying results. Some will fail at 0% citing "total xfer: 0.00x", some will reach 47% and fail (always exactly 47% oddly). Generally if the sideload operation passes 47% it will complete.
fastboot format/erase x: fails, partition formatting/erasing not allowed
fastboot continue: executes, but does not help with android bootloop issue as I had hoped
While I searched for an answer online, I did come across an infosec whitepaper regarding ONEPLUS 3 vulnerabilities, though it was over a year old. To my surprise, the command they had been entering works on my device, but I'm not sure how to properly use it effectively. The command used was fastboot OEM boot_mode [rf/wlan/ftm/normal]. Now, I was unable to determine what each of the triggers does, but what I did discover is that with boot_mode set to rf, my device would display chinese/korean lettering in lieu of the usual ONEPLUS logo with "powered by Android" below. This is also how I managed to have my device show up in CMD terminal for ADB commands to be issued. To the best of my knowledge though, there doesn't seem to be much point to it as I couldn't push/pull any files. Does anybody know where I could find more info on this command, as I'd like to know what the other triggers accomplish.
I've just about exhausted every available resource looking for an answer, but im still coming up short. I've gone as far as contacting ONEPLUS directly, but without proof of purchase they can't (more accurately won't) help me. And while it's not a business practice I would personally support, I can understand why they have it implemented. I've contacted a few phone shops in the area, but none have been able to assist me further than I've already gotten in this process.
I apologize again for creating a new thread about this, but I felt my circumstances warranted a new thread due to the bulk of the others having either an unlocked bootloader or TWRP installed, neither of which I do.
So, can anybody offer their help or suggest something I haven't already tried? Or should I be on EBAY looking for motherboards? Thanks in advance.

Calgary84 said:
Short version of question: How can I unbrick my ONEPLUS 3 (A3000) if I cannot boot to Android and OEM Unlock AND USB Debugging both have not been enabled?
Long version: Phone was recently purchased second hand from a third-party market (Kijiji, kind of like craigslist for Canadians). Person I bought it from claimed in the ad that the device was in a bootloop and couldn't access the OS. I had in the past successfully saved a ONEPLUS 1 from bricked status, so I didn't feel a simple bootloop would pose much of an issue. That, and at the price he was selling I really couldn't turn it down.
I tried various different methods of restoring the phone's partitions, OS, and firmware to stock/custom, but had no real luck with any (I will list below what I have attempted). If there was a root cause of this, I believe it's due to the fact that some part of the phone's storage partition (boot or system if I had to guess) had become corrupted at some point. Given the volume of threads I've seen here and elsewhere online, I wouldn't rule out a bad OTA flash, but doesn't really matter. What does matter, however, is that the Android OS is inaccessible despite my best efforts, and the bootloader is set to locked and ADB Debugging remains off.
Generally speaking, is there a way to access Developer Options to correct both these issues through terminal or a tool? I'm confident that I can get my device working again if I could access this menu, but as of yet I have had no luck.
Methods used to restore/info worth mentioning
While I don't doubt their effectiveness at large, for whatever reason I have yet to find a tool/guide that yields the anticipated results upon completion. MSM Download Tool (V3 and V4) have both been downloaded, executed, and completed numerous times, but will still not boot past the loading screen upon completion.
According to Unified Android Toolkit, my device build is being detected as "OnePlus3 7.0 NRD90M" and All-in-One Toolkit is showing that Android 6.0.1 is installed.
Drivers are all installed correctly, as proven both via tools downloaded and through Windows CMD terminal (adb devices, fastboot devices, adb get-state, etc)
Stock recovery and bootloader modes can both be reached through both hardware keys and software commands. I will note that it seems to take longer than I'd expect to boot to either of these modes using hardware keys.
I have utilized multiple USB ports, Type-C cables, different OS' on two laptops (MS Windows 10 and 7, FWUL Linux). I usually have no problem with the device being detected by the system. When I have, it usually involved one pesky USB cord.
common commands used and their effects:
fastboot OEM unlock: fails, cannot be done remotely
fastboot flash x: fails, remote: flashing partitions not allowed
ADB push: fails. cannot access partition
ADB devices: device is seen by system with serial and state
fastboot devices: device is seen by system with serial
ADB sideload: varying results. Some will fail at 0% citing "total xfer: 0.00x", some will reach 47% and fail (always exactly 47% oddly). Generally if the sideload operation passes 47% it will complete.
fastboot format/erase x: fails, partition formatting/erasing not allowed
fastboot continue: executes, but does not help with android bootloop issue as I had hoped
While I searched for an answer online, I did come across an infosec whitepaper regarding ONEPLUS 3 vulnerabilities, though it was over a year old. To my surprise, the command they had been entering works on my device, but I'm not sure how to properly use it effectively. The command used was fastboot OEM boot_mode [rf/wlan/ftm/normal]. Now, I was unable to determine what each of the triggers does, but what I did discover is that with boot_mode set to rf, my device would display chinese/korean lettering in lieu of the usual ONEPLUS logo with "powered by Android" below. This is also how I managed to have my device show up in CMD terminal for ADB commands to be issued. To the best of my knowledge though, there doesn't seem to be much point to it as I couldn't push/pull any files. Does anybody know where I could find more info on this command, as I'd like to know what the other triggers accomplish.
I've just about exhausted every available resource looking for an answer, but im still coming up short. I've gone as far as contacting ONEPLUS directly, but without proof of purchase they can't (more accurately won't) help me. And while it's not a business practice I would personally support, I can understand why they have it implemented. I've contacted a few phone shops in the area, but none have been able to assist me further than I've already gotten in this process.
I apologize again for creating a new thread about this, but I felt my circumstances warranted a new thread due to the bulk of the others having either an unlocked bootloader or TWRP installed, neither of which I do.
So, can anybody offer their help or suggest something I haven't already tried? Or should I be on EBAY looking for motherboards? Thanks in advance.
Click to expand...
Click to collapse
Thanks for the exhaustive description. You seem to have covered every known method. If the MSM Tool also fails, I think that it is a hardware issue and you are better off searching for a new motherboard instead of wasting further time on trouble-shooting.
Best of luck!

tnsmani said:
Thanks for the exhaustive description. You seem to have covered every known method. If the MSM Tool also fails, I think that it is a hardware issue and you are better off searching for a new motherboard instead of wasting further time on trouble-shooting.
Best of luck!
Click to expand...
Click to collapse
I was afraid of that..... is there a way to test a given hardware component?

Have you tried the unbrick tool FULL updated: https://mega.nz/#!NmhhgZyB!CM7Fw8VjECiMIhh4gRXUx24QVCiE599_ZFAPDf08AiM

acetone802000 said:
Have you tried the unbrick tool FULL updated: https://mega.nz/#!NmhhgZyB!CM7Fw8VjECiMIhh4gRXUx24QVCiE599_ZFAPDf08AiM
Click to expand...
Click to collapse
Indeed I have, dozens of times between the full and mini versions. I've even gone as far as running the toolkits featuring MSMDownloadTool v4.0 to see if it achieved different results (it did not). The mini tool would finish doing its thing (turned the text green upon completion),but I would face varying partitions not being flashed correctly. The full version completes and does not have these varying partitions missing, but the device would then be either stuck in a bootloop where it will eventually reboot itself, or would hang indefinitely on the "swirling dots" loading screen. I tried the remedy of deleting cache in recovery, but this did not help.

deleted

***UPDATE*** - As I mentioned in this thread earlier, I noticed a discrepancy between the variant type listed on my actual device and the variant type returned when queried via fastboot. This got me thinking, and to make a long story somewhat shorter, I found that while most stock Oxygen images I attempt to sideload onto the device fail (at precisely 47%, oddly), I was able to sideload two different Hydrogen images without any resistance at all. I'm guessing something to do with the eMMC vs UFS file storage systems and how each OS uses them.
So I got Hydrogen flashed onto my my device. Smooth sailing, right? Afraid not. Despite fastboot's output clearly stating it was a successful transfer, and the stock recovery on the device echoing this, I still cannot get the OS to load. Now i' stuck with the loading screen hanging indefinitely prior to animation occurring, so basically the static ONEPLUS logo. Factory resets and cache wipes have done nothing to help the situation along. Conventional wisdom from the threads here seem to say using the MSMTool is the right answer..... and thus the circle of frustration is complete with me arriving back where I started. Does anybody have another suggestion I can try out? Still can't flash/boot to TWRP, unlock bootloader, or access Android to activate USB Debug/OEM Unlock either btw.

Have you tried flashing just the firmware, i havent flashed in years but i would assume you could sideload the firmware as well?

voodooline said:
Have you tried flashing just the firmware, i havent flashed in years but i would assume you could sideload the firmware as well?
Click to expand...
Click to collapse
Guess who didn't read? And after a year without flashing + a lack of reading skills, you still think you could solve this case? That's a spirit.
===
You better do pm some devs in dev section and point them to this thread and see if they can help, if you are still curious.
My guess is dead emmc, it can be replaced without buying the whole board.

150208 said:
Guess who didn't read? And after a year without flashing + a lack of reading skills, you still think you could solve this case? That's a spirit.
===
You better do pm some devs in dev section and point them to this thread and see if they can help, if you are still curious.
My guess is dead emmc, it can be replaced without buying the whole board.
Click to expand...
Click to collapse
I did read it, its funny always someone who has to be a **** about things. I should have been more specific. He was able to flash h2os. So he could try to flash the firmware for h2os to see if that gets it to boot.

voodooline said:
I did read it, its funny always someone who has to be a **** about things. I should have been more specific. He was able to flash h2os. So he could try to flash the firmware for h2os to see if that gets it to boot.
Click to expand...
Click to collapse
Magnificent, bro.
You're a truly genius.