Related
My phone connects fine with adb. I tooted with towelroot, i have the D415 (see screenshot) i have run the commands on a pc several time with no errors. I tried it with my terminal emulator severaIm times and it says "decixe not found) HAHHA its just funny to me. I want to unlock this bootloader i even tried a factory cable (for kindle and only once) no dice. I get download mode and thats it. I know I must be doing somethimg wrong but damned if i can figure what. Pc is windows 764 bit. I like to have a custom rexovery and i have heard i can put onw like this (locked) but i did that to another device and to make it short it sits in a drawer being brand new and broken. Apparently those instructioms are correct because there are many success stories. I followed the directions like this is my last phone for a whi
PHP:
le. Can someone help me out please? Thank you
Holy....... 64bit! Im not futureman!!!!
Do you need to unlock the bootloader on d415? I taught you could flash a custom recovery without unlocking... (I don't own one!)
I ave twrp on it. So far i havent been able to do anything but a nandroid and restore with it. I am now at a pc so i can dl from devhost. We shall see, (i doubt it,)
whodisname said:
I ave twrp on it. So far i havent been able to do anything but a nandroid and restore with it. I am now at a pc so i can dl from devhost. We shall see, (i doubt it,)
Click to expand...
Click to collapse
The bootloader on the LG-D415 is unlocked out of the box.
Wow, and all these instructions!! I figured after i put twrp on it it was cool but it didnt flash the rom, omly had one cuz dev host doesnt dl on cell phones so well,
whodisname said:
My phone connects fine with adb. I tooted with towelroot, i have the D415 (see screenshot) i have run the commands on a pc several time with no errors. I tried it with my terminal emulator severaIm times and it says "decixe not found) HAHHA its just funny to me. I want to unlock this bootloader i even tried a factory cable (for kindle and only once) no dice. I get download mode and thats it. I know I must be doing somethimg wrong but damned if i can figure what. Pc is windows 764 bit. I like to have a custom rexovery and i have heard i can put onw like this (locked) but i did that to another device and to make it short it sits in a drawer being brand new and broken. Apparently those instructioms are correct because there are many success stories. I followed the directions like this is my last phone for a while. Can someone help me out please? Thank you
Click to expand...
Click to collapse
For starters, you need the fastboot executable for Windows to unlock the device, not ADB. The minimal ADB version, also applies to fastboot, is 1.0.31. Secondly, you must enable fastboot mode on the device beforehand. Thirdly, unless LG has changed things in the last month or so, the bootloader on the LG-D415 is unlocked.
To enable fastboot mode, see http://forum.xda-developers.com/lg-l90/general/guide-fastboot-l90-d415-t2827825
To unlock the bootloader, see http://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-t-mobile-l90-t2836457. Shouldn't be necessary tho . Won't hurt anything to go thru the process however.
Thank you, i have fastboot and adb (fixed a bricked kindle last week!!) I wasnt sure about the bootloader and iwasnt gunna be without a recovery like i was with my lg lucud!!!
And excuse my unintelligible post above. New size screen?
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!
Need some help. This is my 3rd Moto g 2014 XT1063 and my drivers have been removed and r-installed and every time I get the following when trying to get my code to unlock the bootloader
C:\adb>fastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 0.144s
its driving me nuts since I have done this before with no issues
Im using wind 8.1 64bit
tested alternate usb also
Tested 32 and 64bit drivers also
debug is on, drivers work with other devices. I dont know
Also when doing adb devices nothing shows
C:\adb>adb devices
List of devices attached
but I can boot into fastboot using adb commands when phone is plugged in and turned on
when you use the command "adb devices" your device should be listed
its driver issues. Try Motorola Device Manage
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
I did and hot the same results
This was bugging me so I tried the following.
I had an old computer so I freshly installed Windows 8.1 with all the windows updates and installed nothing else other than Firefox.
I installed the ADB drivers as usual and install the Motorola drivers directly from Motorola's website.
The exact same issue occurred with all the commands.
Not sure if this makes a difference for the device was a replacement from Motorola so I'm not sure they could have locked this or something else.
I'm not too sure what to do at this point.
Do you have a solution?
Android51 said:
Do you have a solution?
Click to expand...
Click to collapse
No I was not able to root it
You were not able or your device? Are you stil testing?
Android51 said:
You were not able or your device? Are you stil testing?
Click to expand...
Click to collapse
Testing what? Like I said I was not able to root the phone and after a while I stopped trying. Can't expect a different result after a few days of trying
I have the same problem. But my device is a Moto X Play. In that area, there is nobody with the same problem. So I think there is a way to get the unlock data. In the next few day, I'll try to get the unlock data on a different Laptop/pc.
Today, i have tried it on an another Laptop. Both of the Laptops run Windows 10. It was not successful. Which Software are you running? Maybe the reason is Windows 10?!
By the way, I have contacted the Motorola Support. They wanted to have a Screenshot of the cmd console. I'm waiting for the answer.
Android51 said:
Today, i have tried it on an another Laptop. Both of the Laptops run Windows 10. It was not successful. Which Software are you running? Maybe the reason is Windows 10?!
By the way, I have contacted the Motorola Support. They wanted to have a Screenshot of the cmd console. I'm waiting for the answer.
Click to expand...
Click to collapse
Tested 8.1 and 7.
Im fed up of dealing with Motorola.
I sent my XT1064 for repairs and they sent back a XT1063
I spent 2 hours explaining telling them I needed an XT1064 back since I need the 1700 band
The didn't know what frequencies where and I spoke with 3 people
Are there any follow-ups on this? I have the exact same problem. Been trying to unlock for nearly three months now. Motorola had me send the phone in three times - to no avail.
No, I sold the device to a friend, who doesn't want to root the device. Yesterday, he told me that the normal OTA Update to Android 6.0 Marshmallow doesn't appear. Far as I know, Motorola is already rolling out Android 6.0.1.
Do you get the OTA Update?
Any1 gt out of this issue ?
Hello everyone,
I've decided to unlock my device to flash vanilla android but I couldn't unlock it. I've tried almost everything but even the latest MiUnlock doesn't recognize my device on fastboot, the PC itself recognizes it before and after getting into fastboot, I hear usb device connected sound and can see the phone under Windows devices.
Adb devices command works if the phone is switched on, my dev settings are ok, oem unlocking and adding account under dev settings are ok, I've tried it with disabled windows signature enforcement too but nothing happened. MiUnlock simply doesn't want to see the device on fastboot.
Can anybody help me, please?
abstra said:
Hello everyone,
I've decided to unlock my device to flash vanilla android but I couldn't unlock it. I've tried almost everything but even the latest MiUnlock doesn't recognize my device on fastboot, the PC itself recognizes it before and after getting into fastboot, I hear usb device connected sound and can see the phone under Windows devices.
Adb devices command works if the phone is switched on, my dev settings are ok, oem unlocking and adding account under dev settings are ok, I've tried it with disabled windows signature enforcement too but nothing happened. MiUnlock simply doesn't want to see the device on fastboot.
Can anybody help me, please?
Click to expand...
Click to collapse
The issue that you are experiencing is strictly with your PC.
You need to ensure that you are using an account that has admin privileges, and be sure that you antivirus is not neutering your usb drivers and Miflash program.
Next, if you are using a newer computer with usb 3 ports, you will need to use a USB hub ( USB 2 is your best option.) , then the phone will be seen in fastboot. As long as you have setup developer options, and your MiCloud account is setup.
Finally, it will take 2 weeks to unlock the bootloader , after your first request. Some people who had been syncing the phone to MiCloud for some time before attempting were able to immediately unlock. Personally we have 3 Mi8's in our house and I had to wait 2 weeks on each one.
To reiterate, your main issue is probably the usb ports, and your antivirus the the 2nd most likely culprit. Worst case use another computer. The process is much easier on older PC's.
you can use the the All in one tool to double check that your drivers, adb , and system wide privileges are up to date and setup correctly. https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
Instructions are available on that thread.
Thanks for your help, I've already tried almost everything you've said up there and even gave a try on virtualbox Windows 7 with USB 2.0 setup.
I remember I've unlocked my friend's device last year on an only USB 2.0 computer, my laptop has unfortunately only two 3.0s and one USB-C. The phone can be seen under fastboot devices command if MiUnlock is not running, if I click on that cr*p program my device either falls from fastboot devices list or says press any key to shutdown.
The main problem is the ports and that damned program itself, how come it lockdowns the connection and after that pc couldn't even show my phone in devices list but can be seen in device manager. I'm literally shocked by the cheapness of this very software.
abstra said:
Thanks for your help, I've already tried almost everything you've said up there and even gave a try on virtualbox Windows 7 with USB 2.0 setup.
I remember I've unlocked my friend's device last year on an only USB 2.0 computer, my laptop has unfortunately only two 3.0s and one USB-C. The phone can be seen under fastboot devices command if MiUnlock is not running, if I click on that cr*p program my device either falls from fastboot devices list or says press any key to shutdown.
The main problem is the ports and that damned program itself, how come it lockdowns the connection and after that pc couldn't even show my phone in devices list but can be seen in device manager. I'm literally shocked by the cheapness of this very software.
Click to expand...
Click to collapse
Again the issue is with windows, I have personally dealt with the exact same issue. That is why I recommended using an older computer that has not been recently updated.
But you are absolutely right, Xiaomi has not made any development improvements with their desktop applications in over a year and that is ridiculous.
I would suggest using alternate versions of the software : I just did a google search and on this link people were saying just one week ago that this linked software worked for them, note its a video, the software link is in the description : https://www.youtube.com/watch?v=l_PEAJ-n2_c
Finally, I am personally using this version of Mi Flash : https://androidfilehost.com/?fid=11410932744536991669 on a brand new intel PC.
and the last time that I unlocked a xiaomi phone I used unlocker software from here ( Note the multiple versions at bottom of page)
https://mi-globe.com/download-xiaomi-mi-unlock-tool-all-versions/
If one doesn't work try another. just be sure that you have developer options setup correctly and that you are signed in a syncing with mi-cloud. You will get it unlocked eventually. I can assure you that it was a Pain in the A*$ for me too!
Thanks man, these are the exactly same links I’ve found and checked out while trying to connect my phone but I just gave up after three days of struggling and pressing volume+power buttons and ordered a USB 2.0 hub online. Unfortunately there are no older computers around me or anyone I can ask for because of you know, the quarantine. I’m actually using cloud actively, so I should better be prepared for an immediate unlocking, and backup my data beforehand as usual.
Just wanted to write about the news, I've backed up my data and connected my device to MiUnlock on USB 2.0 Hub and ta-da it's immediately unlocked without any waiting time. That was a smooth process, I'm shocked but happy.
abstra said:
Just wanted to write about the news, I've backed up my data and connected my device to MiUnlock on USB 2.0 Hub and ta-da it's immediately unlocked without any waiting time. That was a smooth process, I'm shocked but happy.
Click to expand...
Click to collapse
Nice, so my original suggestion about using 2.0 usb was correct. I am glad that you have the issue sorted. I am also surprised about you being able to avoid the wait time. That is a nice break. Enjoy your phone.
PS: Be sure to make a full TWRP backup and save it to your desktop. That backup will save you if you ever experience a bad issue.
tsongming said:
Nice, so my original suggestion about using 2.0 usb was correct. I am glad that you have the issue sorted. I am also surprised about you being able to avoid the wait time. That is a nice break. Enjoy your phone.
PS: Be sure to make a full TWRP backup and save it to your desktop. That backup will save you if you ever experience a bad issue.
Click to expand...
Click to collapse
Thanks man, and yes that was all about fastboot which is written to be used with older usb versions. After plugging in the hub, it’s connected directly in just milliseconds. I am surprised that I’ve really skipped the waiting for two weeks or maybe more and yeah it makes me happy.
I made a full data backup before unlocking and then all the dangerous partitions including modem, efs and bluetooth in TWRP to avoid any irreversible loss. I never skip my recovery backups since 2010 and my first Android smartphone which was an HTC Desire A8181, I learned it in a hard way to never skip them, if you do, you either lose your data or your mobile device identification. :victory:
A question from a Xiaomi-newbie; If I run clean all and lock command on MiFlash, should I wait for an unknown time to unlock the device again? Or does Xiaomi let users to lock/unlock their devices anytime without waiting if you’ve unlocked your bootloader once before?
abstra said:
Thanks man, and yes that was all about fastboot which is written to be used with older usb versions. After plugging in the hub, it’s connected directly in just milliseconds. I am surprised that I’ve really skipped the waiting for two weeks or maybe more and yeah it makes me happy.
I made a full data backup before unlocking and then all the dangerous partitions including modem, efs and bluetooth in TWRP to avoid any irreversible loss. I never skip my recovery backups since 2010 and my first Android smartphone which was an HTC Desire A8181, I learned it in a hard way to never skip them, if you do, you either lose your data or your mobile device identification. :victory:
A question from a Xiaomi-newbie; If I run clean all and lock command on MiFlash, should I wait for an unknown time to unlock the device again? Or does Xiaomi let users to lock/unlock their devices anytime without waiting if you’ve unlocked your bootloader once before?
Click to expand...
Click to collapse
I have only unlocked my device once. But I wouldn't think there would be an issue to unlock a second time. In fact, I have read about some people needing to wait 72 hours to unlock it again after relocking. if using Mi-Flash just try to be sure uncheck that lock bootloader box, that is unless you want it locked.
One last thing, if you ever decide to restore the phone using the flashall.bat method, the bootloader stays unlocked.
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.