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!

Battery drain 10%/h and vibration not working

Hi everyone,
I tried to install the CM 13 in my moto X 2014, but I forgot to install Gapps before rebooting my phone. So I had to flash android 6.0 and try all over again. I dont´t know if my mistake in the procedure has something to do with the problems below.
I realized that my phone is not vibrating anymore and the battery drain has been drasticaly increased, like 10% per hour while in idle. When I use my phone (whatsapp, chrome etc) the battery drain seens to be like in idle (no apps running on background).
A full charge takes 4 hours with normal charger or 8 hours if connected to my computer.
I Tried android versions 4.4.4, 5.0, 5.1, 6.0, NX 10.1 and CM13. I don´t know what to do. Motorola assistance said the motherboard is the source of my problems just because i unlocked my bootloader.

Rodrigo_Codina said:
Hi everyone,
I tried to install the CM 13 in my moto X 2014, but I forgot to install Gapps before rebooting my phone. So I had to flash android 6.0 and try all over again. I dont´t know if my mistake in the procedure has something to do with the problems below.
I realized that my phone is not vibrating anymore and the battery drain has been drasticaly increased, like 10% per hour while in idle. When I use my phone (whatsapp, chrome etc) the battery drain seens to be like in idle (no apps running on background).
A full charge takes 4 hours with normal charger or 8 hours if connected to my computer.
I Tried android versions 4.4.4, 5.0, 5.1, 6.0, NX 10.1 and CM13. I don´t know what to do. Motorola assistance said the motherboard is the source of my problems just because i unlocked my bootloader.
Click to expand...
Click to collapse
What is currently installed on each of the phones partitions?

JnNn98 said:
What is currently installed on each of the phones partitions?
Click to expand...
Click to collapse
You mean the S.O. version?
I´ve flashed these firmwares via fastboot/RSD Lite 6.2.4.
mega.nz/#F!kd9WULBb!m_X_fQGJ6UnEOMJXzcv-Yw

Rodrigo_Codina said:
You mean the S.O. version?
I´ve flashed these firmwares via fastboot/RSD Lite 6.2.4.
mega.nz/#F!kd9WULBb!m_X_fQGJ6UnEOMJXzcv-Yw
Click to expand...
Click to collapse
I feel like it's possible that you downgraded the bootloader in the process, and that could be the only problem. In that case flash this to get stock, as it'll be the latest firmware.
http://www.filefactory.com/file/13ee8myr4sjh/VICTARA_RETBR_XT1097_6.0_MPE24.49-18_cid12_CFC.xml.zip
Use the instructions from this thread.
http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
Also check the cable you're using to charge the phone, with regards to the slow charging.
If there's still things wrong afterwards it is probably a hardware problem. Good luck.

JnNn98 said:
I feel like it's possible that you downgraded the bootloader in the process, and that could be the only problem. In that case flash this to get stock, as it'll be the latest firmware.
http://www.filefactory.com/file/13ee8myr4sjh/VICTARA_RETBR_XT1097_6.0_MPE24.49-18_cid12_CFC.xml.zip
Use the instructions from this thread.
http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
Also check the cable you're using to charge the phone, with regards to the slow charging.
If there's still things wrong afterwards it is probably a hardware problem. Good luck.
Click to expand...
Click to collapse
Sorry I did not reply you earlier, canaval holidays... back to real life today.
I tried what you suggested but without success.
When I try to execute "fastboot flash partition gpt.bin" it fails (I´m not at home right now and I don´t remember exactly the message I got), but all other commands runs like expected.
I saw this thread " forum.xda-developers.com/moto-x-2014/help/managed-to-screw-phone-bootloader-to-t3309241?nocache=1 ". It has a command that in the other you suggested has not.
"fastboot getvar max-sparse-size"
What is it for?

Rodrigo_Codina said:
Sorry I did not reply you earlier, canaval holidays... back to real life today.
I tried what you suggested but without success.
When I try to execute "fastboot flash partition gpt.bin" it fails (I´m not at home right now and I don´t remember exactly the message I got), but all other commands runs like expected.
I saw this thread " forum.xda-developers.com/moto-x-2014/help/managed-to-screw-phone-bootloader-to-t3309241?nocache=1 ". It has a command that in the other you suggested has not.
"fastboot getvar max-sparse-size"
What is it for?
Click to expand...
Click to collapse
The error for the flash partition may be a result of using fastboot and not motorola's own fastboot. I've attached a motorola fastboot in a zip, so you can try again using that fastboot file. The extra commands don't help with anything really because they do not affect the flashing of partitions.
The fastboot getvar command is literally "get variable", so in that case it would just return the maximum file size that can be flashed I believe, and in case you were wondering:
fastboot oem fb_mode_set - Makes the phone automatically reboot into bootloader mode.
fastboot oem fb_mode_clear - Just resets the above commands setting back to normal booting.

The message I mentioned when I execute the command "fastboot flash partition gpt.bin"
sending 'partition' <32KB>...
OKAY [ 0.030s]
writing 'partition'...
<bootloader> Preflash validation failed
FAILED <remote failure>
finished. total time: 0.130s

Nevermind... I was trying to flash an old gpt.bin.
I guess that's the end, I give up. I don't know what to do, nothing works.
I'm thinking of buying an used device with broken screen for 1/3 of the price of a new one (350 reais, almost 100 dollars), disassemble everything and assemble only the motherboard in my device.
I really appreciate your help but I guess I need the Blanckflash and I searched and no one has it because motorola did not released for us.

Moto X Dev Edition stuck in fastboot

I get this error on my moto x dev edition with verizon xt1060 in fastboot. i cant flash any images. i was told to use rsd lite but it doesnt detect my phone.
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
CID Read Failure
Invalid CID status 0x69
CustomerID error. Contact Dealer: 0xdead

RandyThor said:
I get this error on my moto x dev edition with verizon xt1060 in fastboot. i cant flash any images. i was told to use rsd lite but it doesnt detect my phone.
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
CID Read Failure
Invalid CID status 0x69
CustomerID error. Contact Dealer: 0xdead
Click to expand...
Click to collapse
Do you install Motorola drivers..?

Salik Iqbal said:
Do you install Motorola drivers..?
Click to expand...
Click to collapse
yes the newest drivers are installed. It shows up in device manager as "MOT Single ADB Interface". I can also detect it in fastboot, though most commands won't work.

i had a similar kind of problem on my ghost. Firmware crash, due to which phone was stuck at the bootloader. No recovery nor did any fastboot worked at that time. I referred this and this. It worked for me.

varunpilankar said:
i had a similar kind of problem on my ghost. Firmware crash, due to which phone was stuck at the bootloader. No recovery nor did any fastboot worked at that time. I referred this and this. It worked for me.
Click to expand...
Click to collapse
when following the second link steps i get stuck at step 8. Im not sure what he means by click on the device. does he mean the 'Mot Single ADB Interface' device? i clicked properties on that then i clicked update and i selected the folder where i kept the signed sys files. there was nothing about QHSUSB_DLOAD as it said in the tutorial though. anyway afterwards there was no port called Qualcomm HS-USB QDLoader 9008 so i couldn't get a portnumber to continue the process.
The other link you gave i assumed id go to Moto X BE\1_Repair_Boot (RSD Lite)\1060 and flash the gpt.bin and the motoboot.img but i got this error:
C:\Users\Jake\Desktop\New folder\Moto X BE\1_Repair_Boot (RSD Lite)\1060>mfastboot flash partition gpt.bin
sending 'partition' (32 KB)...
OKAY [ 0.290s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.210s
C:\Users\Jake\Desktop\New folder\Moto X BE\1_Repair_Boot (RSD Lite)\1060>mfastboot flash motoboot motoboot.img
sending 'motoboot' (1604 KB)...
OKAY [ 0.420s]
writing 'motoboot'...
Motoboot: Unknown partition name
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.700s

I'm in basically the same situation with my XT1060 Developer Edition. Tried a long list of fixes, none has done the trick. All I have available is the fastboot menu. Phone won't boot into OS, won't go into recovery, hasn't accepted any flashes or erases. This happened because after downgrading to 4.4.4 I allowed an OTA update to 5.1. Phone rebooted and hasn't left the flashboot menu since. I, too, am looking for any help I can get on the matter.
Just like you, I tried that trick involving the fancy drivers, but my phone shows up as "Mot Single ADB Interface" in device manager, so that fix doesn't apply. If my phone reported as QHSUSB_DLOAD in device manager, it would be a different story. Though my phone was rooted and unlocked before downgrading to 4.4.4, at this point it's locked (happened without my knowledge), which I believe is why I can't reflash a recovery image.
It seems pretty clear to me that the phone has either an absent or corrupted partition scheme, as gpt.bin won't flash AND my phone doesn't acknowledge the existence of partitions. I suspect my phone began writing the 5.1 OTA update before erroring out, thus leaving me in a limbo mode halfway between 5.1 and 4.4.4. If anyone out there has experience with this seemingly unique brick situation, I would appreciate it. OP, good luck with your phone.

OrlandoAlex said:
I'm in basically the same situation with my XT1060 Developer Edition. Tried a long list of fixes, none has done the trick. All I have available is the fastboot menu. Phone won't boot into OS, won't go into recovery, hasn't accepted any flashes or erases. This happened because after downgrading to 4.4.4 I allowed an OTA update to 5.1. Phone rebooted and hasn't left the flashboot menu since. I, too, am looking for any help I can get on the matter.
Just like you, I tried that trick involving the fancy drivers, but my phone shows up as "Mot Single ADB Interface" in device manager, so that fix doesn't apply. If my phone reported as QHSUSB_DLOAD in device manager, it would be a different story. Though my phone was rooted and unlocked before downgrading to 4.4.4, at this point it's locked (happened without my knowledge), which I believe is why I can't reflash a recovery image.
It seems pretty clear to me that the phone has either an absent or corrupted partition scheme, as gpt.bin won't flash AND my phone doesn't acknowledge the existence of partitions. I suspect my phone began writing the 5.1 OTA update before erroring out, thus leaving me in a limbo mode halfway between 5.1 and 4.4.4. If anyone out there has experience with this seemingly unique brick situation, I would appreciate it. OP, good luck with your phone.
Click to expand...
Click to collapse
For both of you.. @RandyThor and @OrlandoAlex check thread after 12hrs.. i have something for you which may hopefully fix thay issue.

I'm in the same boat. At least I've finally learned why I always refuse OTA updates (until now it hadn't really dawned on me that I had to blankflash because I downgraded after having updated official firmware).
A solution would be much appreciated, as nothing I've done has worked to this point. I'll read more on here to see whether someone has already posted a solution, and I should be able to check back on this thread in a couple of hours.
EDIT:
It does not look like there is a common solution, from what I can tell in the Q&A. Will search elsewhere next.

PiArc said:
I'm in the same boat. At least I've finally learned why I always refuse OTA updates (until now it hadn't really dawned on me that I had to blankflash because I downgraded after having updated official firmware).
A solution would be much appreciated, as nothing I've done has worked to this point. I'll read more on here to see whether someone has already posted a solution, and I should be able to check back on this thread in a couple of hours.
EDIT:
It does not look like there is a common solution, from what I can tell in the Q&A. Will search elsewhere next.
Click to expand...
Click to collapse
Was busy and forgot that sorry, i put alarm for that now will update this thread in some hours.

Salik Iqbal said:
Was busy and forgot that sorry, i put alarm for that now will update this thread in some hours.
Click to expand...
Click to collapse
No worries. Whenever you get the chance.

RandyThor said:
No worries. Whenever you get the chance.
Click to expand...
Click to collapse
Try this.. 2 things you must needed:
rsd lite too flash xml
battery should be 30%+ means battery okie when you put cable in it.
Caution:
Dont flash it with mfastboot, use Rsdlite to flash the xml. hope your device will boot.
cheers..
https://drive.google.com/open?id=0BxZBxVJDPGZjaUFlSmt4cDFLYW8

@Salik Iqbal, you've done it! Can you tell me exactly why that worked? Which version of the bootloader was that? Also, THANK YOU!

PiArc said:
@Salik Iqbal, you've done it! Can you tell me exactly why that worked? Which version of the bootloader was that? Also, THANK YOU!
Click to expand...
Click to collapse
It was from att latest firmware gpt and aboot.

Salik Iqbal said:
Try this.. 2 things you must needed:
rsd lite too flash xml
battery should be 30%+ means battery okie when you put cable in it.
Caution:
Dont flash it with mfastboot, use Rsdlite to flash the xml. hope your device will boot.
cheers..
https://drive.google.com/open?id=0BxZBxVJDPGZjaUFlSmt4cDFLYW8
Click to expand...
Click to collapse
you are the GOAT my friend

Salik Iqbal said:
Try this.. 2 things you must needed:
rsd lite too flash xml
battery should be 30%+ means battery okie when you put cable in it.
Caution:
Dont flash it with mfastboot, use Rsdlite to flash the xml. hope your device will boot.
cheers..
https://drive.google.com/open?id=0BxZBxVJDPGZjaUFlSmt4cDFLYW8
Click to expand...
Click to collapse
One last thing. The phone is working fine now but recovery doesn't seem to work. I've tried reflashing it and it works but when i enter recovery i just get that dead android guy with the error symbol. Any ideas?

RandyThor said:
One last thing. The phone is working fine now but recovery doesn't seem to work. I've tried reflashing it and it works but when i enter recovery i just get that dead android guy with the error symbol. Any ideas?
Click to expand...
Click to collapse
Oh nevermind i apologize. My recovery was working fine i forgot i have to hold vol up and tap power to get to the recovery options...
Anyway thanks again you're a life saver!!!!!

RandyThor said:
Oh nevermind i apologize. My recovery was working fine i forgot i have to hold vol up and tap power to get to the recovery options...
Anyway thanks again you're a life saver!!!!!
Click to expand...
Click to collapse
So lets close the thread by requesting moderator..

Salik Iqbal said:
So lets close the thread by requesting moderator..
Click to expand...
Click to collapse
do i have to do that lol? im a noob

New G4 Bootloader Unlock issues

I just got an LG G4(H811) from T-Mobile yesterday. The box says it was manufactured 06/2016. I spent several hours yesterday trying to get the bootloader unlocked. I have LG drivers downloaded, LG bridge, Google adb drivers, fastboot/adb installed, tried on two PCs(USB 3 and 2) two different USB cables. For the life of me I can't get past "fastboot OEM unlock" it just says waiting for device. When booted in fastboot I see the driver listed as a kedacom device with the Google ADB drivers being used. Any possibility my device is not unlockable. I really dislike LGs skin, so installing CM was something I really wanted. I haven't updated to 20p. Still on 20i. Any help or advice is appreciated. I'm just frustrated cause I have done everything I know how to do.
Thanks

lg g4
go here it will help you http://forum.xda-developers.com/tmobile-g4/help/fastboot-waiting-device-t3489789

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.