Database Develop

Help with Bootloader and Root. I'm stuck! XT1063

Hello!
I'm from Puerto Rico, my carrier is Claro PR. I've been trying to root my device but so far I haven't even been able to unlock the Bootloader. I get the annoying and indefinite < waiting for device > message on the Fastboot CMD screen. I have installed ADB drivers from Google and it didn't help since the Motorola drivers did not even recognize my device in Fastboot. It seems that the only time my device is recognized in Fastboot mode is when there are no ADB or Fastboot drivers installed and Device Manager lists it as a Fasboot Titan device. Quite honestly this is very frustrating since I've been searching for days to no avail. I do not wish to update to Lollipop(Until it is available officially in my area), which is what most articles I found are for. I just want root access. I'm beginning to doubt if my device is even supported and its just an extremely well made clone.
I was trying this on Windows 8.1 Pro x64. Some people told me Fastboot drivers had some issues with 8.1 so I did my best to clean out old drivers and plug the phone into different USB ports. At first I was trying on my USB 3.0 ports, people also told me USB 3.0 has issues with FB, so I used my 2.0 ports on the front of my computer case. Again, people told me that I had to use ports directly on the motherboard, so I plugged the phone into my PC's back USB ports. I also tried a different micro USB cable, same result. At that time I figured it was probably Windows causing the problems so I pulled a hard drive from and old PC, hooked it up to my own and installed my old copy of Windows 7 Ultimate x64. I installed all the essentials, from ADB to Motorola Device Manager for the drivers. My phone is still not being recognized, although I did get to have it listed under ADB Devices by using USB Debugging, yet it appears offline, as shown in the image below. I figured it was my particular PC because its custom built with salvaged parts from another PC, so I tried the procedure from my family's Dell Optiplex (running win7 Home Premium x32) only to hit the same dead-end. At this point I'm tearing off hair from my head. I don't want to be bald yet! I'm only just turning 20 at the end of the month!
A few details:
Device: Moto G 2014 16GB XT1063. Android Kitkat 4.4.4 (5.0 has yet to be released for my area)
System Version: 21.11.14.titan_amxpr.amxpr.en.PR amxpr
Build number: KXB21.85-14

Inquisitor956 said:
yet it appears offline
Click to expand...
Click to collapse
If you connect your device with usb-debugging enabled in the developer options, a dialog pops up, presenting a RSA fingerprint, asking to allow usb-debugging. If not, type "adb version" in your terminal. If version is below 1.0.31 you have to update adb.

doppelhelix said:
If you connect your device with usb-debugging enabled in the developer options, a dialog pops up, presenting a RSA fingerprint, asking to allow usb-debugging. If not, type "adb version" in your terminal. If version is below 1.0.31 you have to update adb.
Click to expand...
Click to collapse
Thanks solved a problem I had on other laptop that would not show phone

doppelhelix said:
If you connect your device with usb-debugging enabled in the developer options, a dialog pops up, presenting a RSA fingerprint, asking to allow usb-debugging. If not, type "adb version" in your terminal. If version is below 1.0.31 you have to update adb.
Click to expand...
Click to collapse
Thank you! The RSA Fingerprint popup never appeared on my phone. I kept toggling USB Debugging on and off until it did. I managed to get the keys. Now I hit another wall... (image below)
I also tried it onto the Latin America page. This time no matter how I paste my code whether manually typing it or just copy/pasting, it always returns a popup with "Your input text was not recognized as a valid dataset. Please try again." This happens on Chrome, Firefox and even Internet Explorer and combined with the really slow loading of any official Motorola page I try to enter I'm guessing the forces of life itself are preventing me from unlocking this particular phone's Bootloader.

Inquisitor956 said:
preventing me from unlocking this particular phone's Bootloader.
Click to expand...
Click to collapse
Please have a look here: https://forums.motorola.com/posts/f2061da875

doppelhelix said:
Please have a look here:
Click to expand...
Click to collapse
Thank you once again! My device IS unlockable, I was told to wait for some time before requesting my unique unlock key, since the page has been having a few hiccups. I will report back if I was successful or not.
Edit: I successfully unlocked bootloader, installed TWRP and rooted. Thank you for your assistance!

Sony XZ1 Compact Driver Fastboot

Hi everyone,
I would like to root my device but i need the drivers, i search and install what i find on the web and sony website but every time when my divice is in fastboot mode it not recognize by windows.
I think this thread can be usefull for many persons so i open it.
Mobile : Sony XZ1 Compact
This is a screenshot of my device when i plug it in fastboot mode :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks you :good:

Braindeadz said:
Hi everyone,
I would like to root my device but i need the drivers, i search and install what i find on the web and sony website but every time when my divice is in fastboot mode it not recognize by windows.
I think this thread can be usefull for many persons so i open it.
Mobile : Sony XZ1 Compact
This is a screenshot of my device when i plug it in fastboot mode :
Thanks you :good:
Click to expand...
Click to collapse
If you're stuggling to find the ADB drivers for your phone, I'm not sure that you should be trying to root your phone, no offence.
Rooting it will break the camera completely. There is a DRM fix, which does leave all the functions of the camera working. But I wouldn't go down that route personally. The 'fix' was actually stolen from another developer and released without permission. The Dev who's running the drm fix thread didn't build the fix and has no idea how it works. Read for yourself, support is very patchy, it's a difficult thing to get right. You need to apply the right patches in the right sequence on top of a 8.49 CE firmware build, or it wont work.
It's a fix not a workaround, you destroy your TA keys buy unlocking your phone and you will never get them back.
Also you're dependent on the Dev (sToRm//) compiling a new fix to go with any new firmware released.
You could never update again without his help, and right now, he's got the hump.

Didgesteve said:
If you're stuggling to find the ADB drivers for your phone, I'm not sure that you should be trying to root your phone, no offence.
Rooting it will break the camera completely. There is a DRM fix, which does leave all the functions of the camera working. But I wouldn't go down that route personally. The 'fix' was actually stolen from another developer and released without permission. The Dev who's running the drm fix thread didn't build the fix and has no idea how it works. Read for yourself, support is very patchy, it's a difficult thing to get right. You need to apply the right patches in the right sequence on top of a 8.49 CE firmware build, or it wont work.
It's a fix not a workaround, you destroy your TA keys buy unlocking your phone and you will never get them back.
Also you're dependent on the Dev (sToRm//) compiling a new fix to go with any new firmware released.
You could never update again without his help, and right now, he's got the hump.
Click to expand...
Click to collapse
Thanks you for you help, i think you are right but it's very difficult to tell me i don't "root" my phone because every smartphone i have in my life was root. I buy a Sony phone for the first time and maybe the last because it's what i like with Android, Root, change ROM, again and again. Maybe Modpunk release a stable LineageOS ?
I buy this phone because it is small, very small, snap 835, sd card, speakers on the front and fingerprint on the right but i hope Oneplus make a little phone like this a day
I feel like I'm in prison

Braindeadz said:
Thanks you for you help, i think you are right but it's very difficult to tell me i don't "root" my phone because every smartphone i have in my life was root. I buy a Sony phone for the first time and maybe the last because it's what i like with Android, Root, change ROM, again and again. Maybe Modpunk release a stable LineageOS ?
I buy this phone because it is small, very small, snap 835, sd card, speakers on the front and fingerprint on the right but i hope Oneplus make a little phone like this a day
I feel like I'm in prison
Click to expand...
Click to collapse
I know, every phone I've ever owned I rooted, it's almost a habit, but with this bootloader Sony is giving us the finger. The main reasons I wanted to root were usually to get a better battery and to mod the framework to make it look better, but the battery with this phone is already good, it doesn't need any help.
If you want to mod the looks then it's possible to do that too.
I don't want to be negative and put you off trying to do amazing things with your phone, but I thought you should know the details before you start.
Edit: yes, I think LineageOS is very close now, perhaps when that is working I might move to that.

Didgesteve said:
I know, every phone I've ever owned I rooted, it's almost a habit, but with this bootloader Sony is giving us the finger. The main reasons I wanted to root were usually to get a better battery and to mod the framework to make it look better, but the battery with this phone is already good, it doesn't need any help.
If you want to mod the looks then it's possible to do that too.
I don't want to be negative and put you off trying to do amazing things with your phone, but I thought you should know the details before you start.
Edit: yes, I think LineageOS is very close now, perhaps when that is working I might move to that.
Click to expand...
Click to collapse
Thanks for your tips, I'm waiting for LineageOs now, it seems like a better idea.
Thanks you Didgesteve

Braindeadz said:
Hi everyone,
I would like to root my device but i need the drivers, i search and install what i find on the web and sony website but every time when my divice is in fastboot mode it not recognize by windows.
I think this thread can be usefull for many persons so i open it.
Mobile : Sony XZ1 Compact
This is a screenshot of my device when i plug it in fastboot mode :
Thanks you :good:
Click to expand...
Click to collapse
I ran into a similar issue when trying to use Emma. It only runs on Windows, so I had to go through this as well.
First, download and install Android Studio for your OS:
developer . android .com/studio/ index. html
(Note: Android Studio is not required, just the SDK. But Android Studio will install the SDK for you in a standard location. This might make things easier for you.)
Once this is done, launch it to install the SDK. You can select all defaults.
Once the SDK is installed, click Configure in the bottom-right of Android Studio and select SDK Manager. On the first screen, select the SDK Tools tab in the middle. Here you will want to select Google USB Driver and click Apply. This should install the driver.
Then, go back to the device in the device manager and right-click the device and select Update Driver.
After that, I followed the steps here:
stackoverflow . com /questions/14559734/ install-adb-interface-driver-for-android
to get the driver installed. This was because I kept getting an error that the system could not find the Android ADB Interface.
For the record, the Google USB Driver was installed on a Windows 10 box in the following location:
%localappdata%\Android\Sdk\extras\google\usb_driver
Hope this helps you out..

crummmcakes said:
I ran into a similar issue when trying to use Emma. It only runs on Windows, so I had to go through this as well.
First, download and install Android Studio for your OS:
developer . android .com/studio/ index. html
(Note: Android Studio is not required, just the SDK. But Android Studio will install the SDK for you in a standard location. This might make things easier for you.)
Once this is done, launch it to install the SDK. You can select all defaults.
Once the SDK is installed, click Configure in the bottom-right of Android Studio and select SDK Manager. On the first screen, select the SDK Tools tab in the middle. Here you will want to select Google USB Driver and click Apply. This should install the driver.
Then, go back to the device in the device manager and right-click the device and select Update Driver.
After that, I followed the steps here:
stackoverflow . com /questions/14559734/ install-adb-interface-driver-for-android
to get the driver installed. This was because I kept getting an error that the system could not find the Android ADB Interface.
For the record, the Google USB Driver was installed on a Windows 10 box in the following location:
%localappdata%\Android\Sdk\extras\google\usb_driver
Hope this helps you out..
Click to expand...
Click to collapse
Unfortunately, these drivers do not contain the correct drivers. I do not have any idea, I've been desperate.

hage_JK said:
Unfortunately, these drivers do not contain the correct drivers. I do not have any idea, I've been desperate.
Click to expand...
Click to collapse
What do you mean by "these drivers do not contain the correct drivers"? Did they fail to install for you?
I just spun up a new Windows 7 VM to test this out again, and it worked for me.
What steps are you taking exactly?
Did you receive any errors when you tried to install the driver this way?
How is your device appearing in the device manager?

crummmcakes said:
What do you mean by "these drivers do not contain the correct drivers"? Did they fail to install for you?
I just spun up a new Windows 7 VM to test this out again, and it worked for me.
What steps are you taking exactly?
Did you receive any errors when you tried to install the driver this way?
How is your device appearing in the device manager?
Click to expand...
Click to collapse
The device in fastboot will appear in the device manager as Android as the first stick.
Drivers dowload from Sony developed or Android SDK reports not found driver.
Drivers from Sony or Google they work in USB debugging but not driver in fastboot, still reports Android without drivers.
Testing on Windows 10 x64 and Windows 7 x32
Thank you in advance for any ideas

Hi, is there a solution to this? I am also looking for the fastboot driver. I have no issue with ADB driver... its just fastboot. My Z5 with fastboot is ok.... but Z1C not. Im running windows 10

Dean F said:
Hi, is there a solution to this? I am also looking for the fastboot driver. I have no issue with ADB driver... its just fastboot. My Z5 with fastboot is ok.... but Z1C not. Im running windows 10
Click to expand...
Click to collapse
Sometimes the drivers don't install properly in Windows 10, although it doesn't tell you they failed to install (helpful). You need to start Windows in safe mode and look for 'Disable driver signing'
Also, if you've used your computer for another device, then it's likely those drivers are still in it kicking about and probably getting in the way. You might have better luck going to another computer that has never been used for ADB and starting fresh.

Hi everyone,
Dunno if this is the right thread to post my question but the subject is Fastboot so I am trying my luck. Want to unlock the bootloader of my phone via Sony website... step 1 and 2 are no problem and I have my unlock code. Unfortunately I can't get my phone into FASTBOOT mode. Connected cable to laptop, hold volume button up and connected phone to cable but nothing happens. Is there anyone that can help me out?
thnx!

van_vugt said:
Hi everyone,
Dunno if this is the right thread to post my question but the subject is Fastboot so I am trying my luck. Want to unlock the bootloader of my phone via Sony website... step 1 and 2 are no problem and I have my unlock code. Unfortunately I can't get my phone into FASTBOOT mode. Connected cable to laptop, hold volume button up and connected phone to cable but nothing happens. Is there anyone that can help me out?
thnx!
Click to expand...
Click to collapse
It's been mentioned before on a different thread.

Didgesteve said:
It's been mentioned before on a different thread.
Click to expand...
Click to collapse
Thnx... overlooked that thread. Will try that!

hage_JK said:
The device in fastboot will appear in the device manager as Android as the first stick.
Drivers dowload from Sony developed or Android SDK reports not found driver.
Drivers from Sony or Google they work in USB debugging but not driver in fastboot, still reports Android without drivers.
Testing on Windows 10 x64 and Windows 7 x32
Thank you in advance for any ideas
Click to expand...
Click to collapse
Did you use the standalone SDK, or did you use Android Studio?
If you used Android Studio, what do you see in: %localappdata%\Android\Sdk\extras\google\usb_driver\
If you did not use Android Studio, would you be willing to try it? I only suggest it since it installs everything to specific locations, so perhaps removing an additional variable could be useful.
Otherwise, Didgesteve's suggestion seems like a good next step.

I have the exact same problem. Sony driver and Google driver both don't work. Driver sign in Windows 10 is disabled. How can I don now?
Edit: After followed the steps showed in this video the drivers are successfully installed but when unlocking the bootloader it says "command not allowed". Do I have to unlock it if I want to root my phone?

k_basara said:
I have the exact same problem. Sony driver and Google driver both don't work. Driver sign in Windows 10 is disabled. How can I don now?
Edit: After followed the steps showed in this video the drivers are successfully installed but when unlocking the bootloader it says "command not allowed". Do I have to unlock it if I want to root my phone?
Click to expand...
Click to collapse
Yes, unlocking your phone is the first part of rooting your phone. Unlocking is a one way process, you can't ever undo it and it will break your camera, completely. Be aware of that before you continue, the threads are full of people crying about broken phones that can't be re-locked.
It might be your phone is not allowed to be unlocked. Some phone providers in the UK sell phones that cannot be unlocked, mostly because they don't want the headache of people claiming unlocked phones be repaired.
Type *#*#7378423#*#* into your phone dialer to access the service menu.
Then look under Service info/configuration.
Under Rooting Status it should say Bootlock unlock allowed - yes.
If it says no then forget it.
Edit: you also need to allow OEM unlocking in the developer options

Didgesteve said:
Yes, unlocking your phone is the first part of rooting your phone. Unlocking is a one way process, you can't ever undo it and it will break your camera, completely. Be aware of that before you continue, the threads are full of people crying about broken phones that can't be re-locked.
It might be your phone is not allowed to be unlocked. Some phone providers in the UK sell phones that cannot be unlocked, mostly because they don't want the headache of people claiming unlocked phones be repaired.
Type *#*#7378423#*#* into your phone dialer to access the service menu.
Then look under Service info/configuration.
Under Rooting Status it should say Bootlock unlock allowed - yes.
If it says no then forget it.
Edit: you also need to allow OEM unlocking in the developer options
Click to expand...
Click to collapse
Yes, I forgot to allow OEM unlock in my phone settings.
I gave up unlocking my phone anyway, compare to years ago, stock rom nowadays isn't that unacceptable after all.

Hi - after months I finally solved the fast boot issue by using the above mentioned video: https://www.youtube.com/watch?time_continue=105&v=nQjg6ePnGAc
Basically - the key is that there are 2 steps:
1. Connect phone in usb debugging mode - then install sony adb driver using device manager and "have disk"
2. Boot into fastboot - and again install sony adb driver using device manager and "have disk"
Result = fastboot now working!

today I root my XZ1C
I have lots of problems with fastboot and i have other solution
for ADB i use driver from Sony ( installed by device manager )
but for fastboot
I use "Android ADB Interface" installed with Android Studio (you can choose it device manager --> update driver --> manual install --> installed on pc --> google or on my PC it was Samsung and there was google --> Android ADB Interface )
thats was only think that work for my device
I lost today 3/4h for this one think
maybe it will help someone to safe this time
Enjoy !

Unlock Pixel Bootloader

Hello all!
Recently I bought a Pixel 4 XL on ebay. Loving the phone, however it turned out to be from AT&T. When it arrived I had a lot of issues, the SIM I use on Spain wouldn't work, and the 2x camera didn't work as well. After a bit of research I find a way to fix those 2 problems, but now I want to flash magisk to improve motion sense gestures, however I can't unlock the Bootloader. I think if I can find where that information about the Bootloader is stored I could try to modify it through the computer. It must be somewhere on the phone, so if I find the file I can unlock it. If anyone has any idea, please let me know.
Thanks in advance

@mcl Enable oem unlocking. It's greyed out in your screenshot you posted. Try enabling developer options and USB debugging on phone, disable any lock screen you have set up, set lock screen to NONE in security settings on phone aaaannd change default USB configuration from "charging" to "transfer files" then plug it up to you computer with latest ADB and Fastboot installed and attempt to unlock your bootloader by typing in terminal: sudo adb reboot bootloader (enter) watch your phone close and if a small box pops up when you do this or when you first connect to PC pc
Checkmark it rreally quickly on your phone screen. That allows PC to communicate with your device, send commands, etc...If all has gone well up to now you should now be in "Fastboot mode" aka: bootloader mode on your phone screen. A black screen with "Fastboot mode" in red letters and the word "START" kinda in center of your screen on phone. Now just go back to terminal and type: sudo fastboot flashing unlock (enter) return to device use volume keys to go up or down and confirm unlocking bootloader by pressing power once on the "yes unlock bootloader" thingy. Soon as you push power to confirm bootloader unlock you will reboot automatically and you will bootloader unlocked. Keep in mind unlocking and locking your bootloader can and will factory reset your device. No pics or anything will be on phone, all will be wiped and there's no way to prevent that. Cheers.
If by some crazy situation something I've mentioned above does NOT work like I've said let me know and I'll help best I can. I use Linux Ubuntu on my laptop 18.04.5 LTS. I stopped using Windows MAAAANNNYYY years ago so I'm inexperienced when it comes to setting up adb and fastboot tools on Windows. I do know that the USB driver's used to always be a real pain in the ass to get right for me. I'd have to reboot by computer a few times and update them in device manager to get it working which I don't have to do anything using Ubuntu my PC just automatically sees my phones. Yay!!!
I hope this helps. Feel free to hmu any time. Remember im on central time in the USA.
To get your enable oem unlocking to become not stuck where it's greyed out like yours is you may have to factory reset your device before you do what I've mentioned above. Just factory reset in settings on your device but afterwards make sure you enable developer options and USB debugging and make sure you flip on the "enable oem unlocking" switch towards the top of developer options on your device

flash713 said:
@mcl Enable oem unlocking. It's greyed out in your screenshot you posted. Try enabling developer options and USB debugging on phone, disable any lock screen you have set up, set lock screen to NONE in security settings on phone aaaannd change default USB configuration from "charging" to "transfer files" then plug it up to you computer with latest ADB and Fastboot installed and attempt to unlock your bootloader by typing in terminal: sudo adb reboot bootloader (enter) watch your phone close and if a small box pops up when you do this or when you first connect to PC pc
Checkmark it rreally quickly on your phone screen. That allows PC to communicate with your device, send commands, etc...If all has gone well up to now you should now be in "Fastboot mode" aka: bootloader mode on your phone screen. A black screen with "Fastboot mode" in red letters and the word "START" kinda in center of your screen on phone. Now just go back to terminal and type: sudo fastboot flashing unlock (enter) return to device use volume keys to go up or down and confirm unlocking bootloader by pressing power once on the "yes unlock bootloader" thingy. Soon as you push power to confirm bootloader unlock you will reboot automatically and you will bootloader unlocked. Keep in mind unlocking and locking your bootloader can and will factory reset your device. No pics or anything will be on phone, all will be wiped and there's no way to prevent that. Cheers.
If by some crazy situation something I've mentioned above does NOT work like I've said let me know and I'll help best I can. I use Linux Ubuntu on my laptop 18.04.5 LTS. I stopped using Windows MAAAANNNYYY years ago so I'm inexperienced when it comes to setting up adb and fastboot tools on Windows. I do know that the USB driver's used to always be a real pain in the ass to get right for me. I'd have to reboot by computer a few times and update them in device manager to get it working which I don't have to do anything using Ubuntu my PC just automatically sees my phones. Yay!!!
I hope this helps. Feel free to hmu any time. Remember im on central time in the USA.
To get your enable oem unlocking to become not stuck where it's greyed out like yours is you may have to factory reset your device before you do what I've mentioned above. Just factory reset in settings on your device but afterwards make sure you enable developer options and USB debugging and make sure you flip on the "enable oem unlocking" switch towards the top of developer options on your device
Click to expand...
Click to collapse
Hey thanks for the very detailed guide, however I run into a few problems. First I factory reset(also, after that it wouldn't allow me to enable OEM unlock) the device and disable any lock screen, as you told me and set the usb configuration to data transfer. Later I enable USB Debugging and checked the box to allow my computer to connect to the phone. Finally I run the command to reboot into the boot loader, which worked but the 2 command, to unlock the bootloader show an error(see screenshot). Any idea what could have happened?
I tried this on my MacbookPro 13" Late 2013 with Catalina and the latest version of ADB from google. The phone is running android 11, with the July security Patch.

#mcl said:
Hey thanks for the very detailed guide, however I run into a few problems. First I factory reset(also, after that it wouldn't allow me to enable OEM unlock) the device and disable any lock screen, as you told me and set the usb configuration to data transfer. Later I enable USB Debugging and checked the box to allow my computer to connect to the phone. Finally I run the command to reboot into the boot loader, which worked but the 2 command, to unlock the bootloader show an error(see screenshot). Any idea what could have happened?
I tried this on my MacbookPro 13" Late 2013 with Catalina and the latest version of ADB from google. The phone is running android 11, with the July security Patch.
Click to expand...
Click to collapse
Honestly I have no idea. What I know is Linux and what's worked for me. My first assumption is that adb and fastboot need to be updated to the latest release if they are not at this time. That error you are showing in terminal sounds like something is wrong either maybe in your USB cable connecting to your PC or it needs to be updated ooorrr it's some sort of USB driver issue. Unless we are both crazy and somehow your device was already rooted and has an unlocked bootloader and that's how it was when you purchased it used online.. Download a root checker app and see what it says maybe. Also try booting stock recovery and factory reset front it and then reboot and see if anything changes...I know absolutely NOTHING about MacOS or OSX or anything otter than Linux because that's what I've used for eight or nine years now. I'm attaching a picture of my current updated adb and fastboot tools to show what latest release is. Maybe try different ports and USB cables just to see if anything changes. You are running the bootloader unlock command as root correct?
Adb and fastboot latest version: 31.0.3-7562133
I updated mine yesterday to that version from here: https://developer.android.com/studio/command-line/sdkmanager

You are doing everything exactly how it shows here:: https://www.xda-developers.com/google-pixel-4-root-magisk/ ?
and using the latest adb and fastboot on PC? Does Mac have to have any extra USB driver's like Windows needs to allow fastboot and adb to work or.no? I guess you would know that just type : sudo adb devices (enter)with phone plugged in and on. Maybe reboot bootloader/fastboot mode and run: fastboot devices (enter) and see if your terminal replies with your phones serial number in your terminal? If it does not than something isn't correctly setup because this should work. Did you use homebrew to setup platform tools on your Mac or no? Usually when I can't figure something ike this out it's the most random basic thing like a reboot or something and BOOM it works. Try running the commands again from your PC and see if anything happens. If you can type ./adb devices then hit enter while you are plugged in and slap a pic up of what it tells you like you did before. This is all stuff I would do if I were in the situation that you're in. I'm going to read up more on Mac now. You said you factory reset your device in settings on phone and the greyed out "enable oem unlocking" didn't change to where you can tap the switch and choose to either enable it or not? If it did not change after factory reset and maybe trying factory reset in stock recovery then it sounds like something else could be wrong with your device. I believe you will figure it out. When you did the while process did you ever checkmark a pop up box on phone screen whole you were plugged in to your PC??

Hey!
Ok so first I downloaded the latest ADB for Mac, but I am unsure of the version I have of Fastboot. Do I need to update it on the phone or download something else? What I did was download the latest version of the SDK from Google to my Mac as you show me on the screenshot, and on their webpage they say I don't need to do anything else, like installing USB drivers on windows. Also if I run Fastboot devices command I can see my phone on the terminal. The cable is working I think, but I may try to change it just in case and also change the port I am using. Also I downloaded and app to check if the device is rooted, and unfortunately it isn't. I will boot into recovery and try to do a factory reset from there, but I don't believe it will work as I believe I already try that before.
The commands I run correct, just copy and paste what you wrote before and the computer asked me my user password. However I didn't use homebrew at any moment, directly downloaded the SDK from google and got a zip file, then extracted it to my desktop and open a terminal window, then use cd to get to that folder directory as I used to do in my Windows PC and start using the commands. Until now it worked great because in order to get my SIM working I needed to use ADB to uninstall an app that came with phone, otherwise my SIM wouldn't work, as theoretically the phone should only accept only AT&T SIM, but I am currently using a Vodafone SIM. Also I am leaving a screenshot of what you asked me.
Yeah after factory reset I doesn't allow me to enable OEM Unlock, still grey out.
Finally yes, when I plugged my phone into the computer I got a window asking to allow the computer to connect to phone to debug, and I allow it.
Sooo here is what I think is happening. This phone was bought by someone at an AT&T store. Then the guy sold the phone and I ended up buying it. The problem, according to my findings, are that carriers usually lock down the bootloader and for you to get it unlocked you need to talk with them. Obviously I can't do that, as I would have to do an international call, and I don't even know if the buyer end the payment of the phone. I already got into AT&T webpage and try to get the phone unlock but get always and error. So researching more I found a command that you can use on Fastboot mode, "Fastboot flashing get_unlock_ability"(enter) and the result I got was 0. According to this page, if you get 0 means you need to go on settings and enable OEM unlocking, which changes the value from 0 to 1. So what I need to do is to find where this info is stored, which I suppose is on the bootloader partition, as on Fastboot mode it was able to tell me the value. Once I find it I just need to change it to 1, and then I would be able to unlock the bootloader.
Also thanks for all the help until now, I really appreciate it

I may try this on other OS just in case. Do you know if I can do this on Kali Linux? I already have it download ed but never try it.

#mcl said:
I may try this on other OS just in case. Do you know if I can do this on Kali Linux? I already have it download ed but never try it.
Click to expand...
Click to collapse
Pretty sure you can. I've never used Kali , yet but I've used ARC, Morrodoca, Ubuntu, Mint and Fabian and tried a few of the super private distros as well. Pretty cool! Linux rules and is made for this.
I almost said something about carriers encryption bootloader's on devices when we started this but idk I assumed it was a factory unlocked unit. I've had to repeat commands more than once before and things have ended up working. Worth a shot.
I say if you can't get it sell it online and grab a factory unlocked model. If the carrier encrypted the bootloader I don't believe it's possible to get it out of that without their code ever used to do it. Then again I do recall another Pixel model that Google was actually sending users refurnished units that had encrypted bootloader's. That would have really pissed me off. I believe Pixel 2/2XL was that way. But the Pixel 2XL/2 that Verizon sold , Verizon locked the bootloaders and for a long time there was no possible way to get around it. I recall reading many posts all over about people buying them and being told they were unlocked Pixels only to discover later they had encrypted bootloader's and Verizon did it. Shortly after this someone on XDA found a way to bypass it and unlock bootloader and root rge Verizon encrypted models but the phones had to be on a specific older firmware and if they'd been updated past it it didn't work. I'll go find this thread and link you. May have some good info but unless you come up with a back to get around it if bootloader has been locked bt carrier I believe it's a no go. Also careful because messing with encrypted things can cause your device ti bootloop and seeing how your NOT bootloader unlocked that wouldn't be good if that happened. I'll go find this link to what I'm referring to. Brb.
Here was the work round for Verizon for a while on Pixel 2 that had been carrier bootloader locked: https://www.xda-developers.com/how-to-unlock-bootloader-verizon-google-pixel-xl-running-android-10/
Actually this is Pixel 2XL, was P2 work around for this: https://forum.xda-developers.com/t/...-google-ver-refurb-devices-look-here.3763443/

Pixel 2XL some users report they had to be connected to the net to toggle their allow oem unlocking switch in dev options. On 4XL one of the "How to Root, unlock .." threads says if it's greyed out that factory resetting is mandatory to allow the ability to enable oem unlocking switch.. A couple people claimed once they reset they could flip it. Also I have also read where people used different bootloop unlocking terminal commands and they worked. On 4xl and older Pixies. How long have you had fastboot already installed to your MacBook? Only reason I ask is they must be manually updated or sometimes will not work right. I've had that happy once. Linux has a very similar adb and fastboot tools install as Mac does. I did this process I'm about to mention yesterday to get my adb and fastboot updated because I saw it was on a previous version. I just grab the adb and fastboot from my screenshot from like I posted back some posts ago here then go to where I have adb and fastboot installed already open terminal where I've downloaded and extracted fastboot and adb on PC and reinstalled adb and fastboot using these commands:
sudo install adb dmtracedump e2fsdroid etc1tool fastboot hprof-conv make_f2fs mke2fs mke2fs.conf sload_f2fs sqlite3 /usr/local/bin (Enter)
sudo mkdir -p /usr/local/lib64 (enter)
sudo install lib64/libc++.so /usr/local/lib64 (enter)
Then make sure it did it's thing and updated property. sudo adb --version (enter)
sudo fastboot --version (enter)
And it showed newer version of both so done. I use Nathanchnace's Pixel 2xl guide to learn this at first from here in his op:
[GUIDE] Unlock/Flash/Root for the Pixel 2 XL (taimen)
Introduction Hello everyone, this is a guide to assist you with customizing your Pixel 2 XL! I will be going over installing fastboot and adb, unlocking your bootloader, how to flash the factory images for clean flashes and upgrades, and how to...
forum.xda-developers.com

flash713 said:
Pretty sure you can. I've never used Kali , yet but I've used ARC, Morrodoca, Ubuntu, Mint and Fabian and tried a few of the super private distros as well. Pretty cool! Linux rules and is made for this.
I almost said something about carriers encryption bootloader's on devices when we started this but idk I assumed it was a factory unlocked unit. I've had to repeat commands more than once before and things have ended up working. Worth a shot.
I say if you can't get it sell it online and grab a factory unlocked model. If the carrier encrypted the bootloader I don't believe it's possible to get it out of that without their code ever used to do it. Then again I do recall another Pixel model that Google was actually sending users refurnished units that had encrypted bootloader's. That would have really pissed me off. I believe Pixel 2/2XL was that way. But the Pixel 2XL/2 that Verizon sold , Verizon locked the bootloaders and for a long time there was no possible way to get around it. I recall reading many posts all over about people buying them and being told they were unlocked Pixels only to discover later they had encrypted bootloader's and Verizon did it. Shortly after this someone on XDA found a way to bypass it and unlock bootloader and root rge Verizon encrypted models but the phones had to be on a specific older firmware and if they'd been updated past it it didn't work. I'll go find this thread and link you. May have some good info but unless you come up with a back to get around it if bootloader has been locked bt carrier I believe it's a no go. Also careful because messing with encrypted things can cause your device ti bootloop and seeing how your NOT bootloader unlocked that wouldn't be good if that happened. I'll go find this link to what I'm referring to. Brb.
Here was the work round for Verizon for a while on Pixel 2 that had been carrier bootloader locked: https://www.xda-developers.com/how-to-unlock-bootloader-verizon-google-pixel-xl-running-android-10/
Actually this is Pixel 2XL, was P2 work around for this: https://forum.xda-developers.com/t/...-google-ver-refurb-devices-look-here.3763443/
Click to expand...
Click to collapse
OK thanks! Yeah I saw a few things only about the Pixel 2 Verizon case, but I am going to have a deep look into it. I can't sell this phone and buy an unlocked version, I bought this one because it was over 100 euros cheaper than what I could found here on Europe, so that's not an option.
Also, If I manage to use a Vodafone SIM on this AT&T phone without unlocking I am confident I will manage to find a way to fix the locked bootloader. It may take time and effort, but I will keep trying.
Right now I found there are ways to get root without unlocking the bootloader, its safer but posible. And if I get root access I am confident I would be able to unlock the bootloader. Anyway thanks for all!!!

flash713 said:
Pixel 2XL some users report they had to be connected to the net to toggle their allow oem unlocking switch in dev options. On 4XL one of the "How to Root, unlock .." threads says if it's greyed out that factory resetting is mandatory to allow the ability to enable oem unlocking switch.. A couple people claimed once they reset they could flip it. Also I have also read where people used different bootloop unlocking terminal commands and they worked. On 4xl and older Pixies. How long have you had fastboot already installed to your MacBook? Only reason I ask is they must be manually updated or sometimes will not work right. I've had that happy once. Linux has a very similar adb and fastboot tools install as Mac does. I did this process I'm about to mention yesterday to get my adb and fastboot updated because I saw it was on a previous version. I just grab the adb and fastboot from my screenshot from like I posted back some posts ago here then go to where I have adb and fastboot installed already open terminal where I've downloaded and extracted fastboot and adb on PC and reinstalled adb and fastboot using these commands:
sudo install adb dmtracedump e2fsdroid etc1tool fastboot hprof-conv make_f2fs mke2fs mke2fs.conf sload_f2fs sqlite3 /usr/local/bin (Enter)
sudo mkdir -p /usr/local/lib64 (enter)
sudo install lib64/libc++.so /usr/local/lib64 (enter)
Then make sure it did it's thing and updated property. sudo adb --version (enter)
sudo fastboot --version (enter)
And it showed newer version of both so done. I use Nathanchnace's Pixel 2xl guide to learn this at first from here in his op:
[GUIDE] Unlock/Flash/Root for the Pixel 2 XL (taimen)
Introduction Hello everyone, this is a guide to assist you with customizing your Pixel 2 XL! I will be going over installing fastboot and adb, unlocking your bootloader, how to flash the factory images for clean flashes and upgrades, and how to...
forum.xda-developers.com
Click to expand...
Click to collapse
The SDK I downloaded this week, Monday I think, so it should be up to date, but I will make sure to check if this is the case. If you get any idea on how to unlock the bootloader, please let me know

Also if anyone was able to unlock a Pixel 4/Pixel 4 XL from any carrier, let me know how you did, maybe I can replicate the process and unlock my bootloader too!

#mcl said:
Also if anyone was able to unlock a Pixel 4/Pixel 4 XL from any carrier, let me know how you did, maybe I can replicate the process and unlock my bootloader too!
Click to expand...
Click to collapse
@#mcl
Not gonna happen. Sorry to hear you got a carrier locked AND bootloader locked phone. Unfortunately there is nothing you can do. There are some shady online unlockers that claim to be able to do this remotely (remote unlock) but you will probably be ripped off.

Find X5 Lite: fastbootd/OEM unlock problems

Hello!
First of all: I know I am asking about the Lite, not the Pro - but there was no dedicated device listing for it, so I went for the next best thing I could find. I apologize in advance.
I have a highly visually impaired friend for whom reading a lot of text is very taxing. I, too, am visually impaired, but I practically live in a terminal - it's totally fine for me. However, we live all across the country (Germany). Basically, he lives in Berlin and I in Frankfurt. Thats a long way apart. So, the best I can help him with is by logging in via Parsec; hence, I have to ask him to do any hardware-related handling.
The TL;DR is: His device defaults to fastbootD, refuses both "flashing unlock" and "oem unlock" after toggling it in Developer options. Variations of adb/fastboot "reboot bootloader/recovery" all did not result in full fastboot. We were trying to extract the boot image to use with Magisk.
The long story: Late last year, he bought the phone off eBay once he heared that Oppo phones were no longer allowed to be sold in stores here in Germany and wanted to root it to see what he could do with it. Since it is a MediaTek device, I told him that hopes for a LineageOS port would be slim, considering MediaTek's history with OSS. So first we went on a hunt for the stock ROM to just grab the boot image off there. No luck; the only seemingly viable listing - a Google Drive link - has become completely unavailable (traffic limit reached). So the next best thought was to grab it off the device itself.
So I went to his maschine via Parsec and set up adb and fastboot and configured the proper Fastboot driver (the official Google one) and made sure the device was recognized as an Android Bootloader Device. Fastboot could also list it, so I was all set up. From there I made a dump of "get-var all" and sure enough, "unlock" was "no". So I sent his phone to reboot and him on his merry way to head into the Developer options and find OEM Unlock. And, it is indeed there. Once he enabled that, I attempted to unlock that bootloader. But I always get errors that the HAL can not be loaded or that the command would not be found. And, whilst researching more, I learned that fastboot can also load in userspace as fastbootd. Sure enough, I had him send me a photo of what the bootloader looked like, and in big bold letters it does indeed read "FASTBOOTD".
After looking up several guides and information, I have not managed to get anywhere at all untill I found this post: https://forum.xda-developers.com/t/...access-for-oppo-phones-starting-2016.3348114/
I could not find any verification that his phone is also affected, meaning that he might have a "castrated" bootloader alltogether - or fastboot, at least.
The model identifies itself as: CPH2371
If you have any possible ideas, please do let me know. Personally, I am at the end of my ideas. Rooting, and sub-sequently installing LineageOS, was astoutly simpler on my Razer Phone 2.
Thank you very much in advance - and, again, apologies for posting in the wrong thread, a proper X5 Lite one was nowhere to be seen.
Kind regards,
Ingwie
PS: The "vars.txt" attached was pre-OEM unlock setting.

any news? root possible?

I've forgot me pattern lock, when I tried to enter in recovery mode, my phone keep restarting again & Again what should I do, I need to reset my pattern, GMAIL ID method also not working....

Where to get Nokia Drivers for Linux?

Got an old Nokia 8 that I wish to flash. The instruction says first I need to get Nokia drivers and unlock but the link provided requires NextCloud login. I googled and only found "Nokia USB Drivers for Windows". I'm using a Linux machine and I'm not sure whether this "USB drivers" is what I need. Help please?

All you need are "adb" & "fastboot" drivers. You can get them from your package manager.
EDIT: Those are used for flashing. For unlocking the bootloader I have no idea.

To unlock the bootloader the manufacturer-Nokia no longer supports this terminal, it no longer supported it in December 2021 when I wanted to unlock the bootloader of my Nokia 8 TA-1052, I unlocked mine through a website called techmesto .com. It's been commented on this forum about it.