Database Develop

[Q] [Help] Unique situation: root to unroot OR just unroot

Question/issues solved - thread done!
Picture of M7 screen with information: http://imgur.com/a/l6hIg
Basically, last year I traded this phone for my current phone at the time with a T-Mobile employee.
Got home and reset everything, setup everything to my liking, etc.
I then tried to go through the rooting process and all that but it didn't work (sadly, this was a while ago and I don't remember the exact issue...).
I tried everything I could but nothing worked and so I gave up since the phone was working fine other than it not being 'rootable'.
Fast forward to a couple days ago and I found a great deal on the M8 and have been using it to make sure it is everything the seller said it would be.
Then my friend said he wants to buy my M7 and I said sure but I need some time to backup my stuff and clear/reset the phone.
So the real details/interesting part of the situation is this:
Between when I got the M7 and a couple days ago the performance of the M7 has degraded and by this I mean that I have to restart the phone to get mobile data working (even though the symbol shows 4g/LTE), some apps have randomly crashed (namely Maps but it seems updates have fixed that). When I did try to root and all that, I installed TitaniumBackUp Pro and Root Explorer (here comes the interesting part) - sometimes TPUP has root access and sometimes it doesn't have root access; however, Root Explorer has always worked for what I needed (looking for downloaded files).
So is it possible to somehow properly root the phone and then unroot to make sure everything is good to go for my friend or do I need to just unroot the phone? Or do I simply need to do a factory reset (I am fine with this since I have all my contacts on the M8 already)? I haven't touched any software/rooting stuff since my 1 and only attempt to root the phone.
Sorry for the wall of text and I did try searching for similar posts/threads but couldn't (maybe I searched the wrong words?) and please feel free to ask questions for clarification and I will do my best to respond ASAP! Thank you in advance for your help.

CTR01 said:
Picture of M7 screen with information: http://imgur.com/a/l6hIg
Basically, last year I traded this phone for my current phone at the time with a T-Mobile employee.
Got home and reset everything, setup everything to my liking, etc.
I then tried to go through the rooting process and all that but it didn't work (sadly, this was a while ago and I don't remember the exact issue...).
I tried everything I could but nothing worked and so I gave up since the phone was working fine other than it not being 'rootable'.
Fast forward to a couple days ago and I found a great deal on the M8 and have been using it to make sure it is everything the seller said it would be.
Then my friend said he wants to buy my M7 and I said sure but I need some time to backup my stuff and clear/reset the phone.
So the real details/interesting part of the situation is this:
Between when I got the M7 and a couple days ago the performance of the M7 has degraded and by this I mean that I have to restart the phone to get mobile data working (even though the symbol shows 4g/LTE), some apps have randomly crashed (namely Maps but it seems updates have fixed that). When I did try to root and all that, I installed TitaniumBackUp Pro and Root Explorer (here comes the interesting part) - sometimes TPUP has root access and sometimes it doesn't have root access; however, Root Explorer has always worked for what I needed (looking for downloaded files).
So is it possible to somehow properly root the phone and then unroot to make sure everything is good to go for my friend or do I need to just unroot the phone? Or do I simply need to do a factory reset (I am fine with this since I have all my contacts on the M8 already)? I haven't touched any software/rooting stuff since my 1 and only attempt to root the phone.
Sorry for the wall of text and I did try searching for similar posts/threads but couldn't (maybe I searched the wrong words?) and please feel free to ask questions for clarification and I will do my best to respond ASAP! Thank you in advance for your help.
Click to expand...
Click to collapse
probably a better idea to reset the phone back to stock. can you post the output of "fastboot getvar all" except imei/serialno?

alray said:
probably a better idea to reset the phone back to stock. can you post the output of "fastboot getvar all" except imei/serialno?
Click to expand...
Click to collapse
@alray:
Thanks for the quick reply. I will gladly just reset to stock if that's the easiest/best method.
I currently don't have ADB setup on either computer since I haven't been in the rooting game for a long while now.
As of now I'm on my MacBook Pro 13" with Retina display and Mac OSX 10.9.4 and internet connection.
My home Windows desktop currently doesn't have internet due to some issues at home...
So I'm guessing the first thing is to setup ADB on the Mac (if possible?), though I haven't done it before on a Mac.
Thanks.

CTR01 said:
@alray:
Thanks for the quick reply. I will gladly just reset to stock if that's the easiest/best method.
I currently don't have ADB setup on either computer since I haven't been in the rooting game for a long while now.
As of now I'm on my MacBook bla bla bla.
My home Windows desktop currently doesn't have internet due to some issues at home...
So I'm guessing the first thing is to setup ADB on the Mac (if possible?), though I haven't done it before on a Mac.
Thanks.
Click to expand...
Click to collapse
yes its also possible to have adb and fastboot on mac, just make a quick google search and you'll find a great thread how to setup fastboot/adb on mac.

alray said:
yes its also possible to have adb and fastboot on mac, just make a quick google search and you'll find a great thread how to setup fastboot/adb on mac.
Click to expand...
Click to collapse
@alray:
Great, thanks for that and I will be sure to update here as soon as it is all setup.

@alray:
I found this link from a Google search that showed me how to install adb/fastboot on Mac in less than 5 minutes and my M7 is showing up in the adb devices list.
Screen shot with all the info is attached.
Sorry for the delayed reply, had to eat dinner.

CTR01 said:
@alray:
I found this link from a Google search that showed me how to install adb/fastboot on Mac in less than 5 minutes and my M7 is showing up in the adb devices list.
Screen shot with all the info is attached.
Sorry for the delayed reply, had to eat dinner.
Click to expand...
Click to collapse
So you have probably unlocked the bootloader in your attempt to root the phone. When you unlock the bootloader, it wipe users data but it also wipe some preloaded app by HTC in /data/preload. Problem is your friend will not be able to install ota updates with those missing files.
Good news is that there is a ruu for your phone version you could use to reset the phone back to stock and it will also wipe all your personal data at the same time, like if the phone was new (no need to factory reset). The ruu is a .exe file so you'll need a windows computer and because of the hboot version on the phone (1.44) you can't use windows 8.1 to flash the ruu, you'll need windows 7. Because your phone is S-ON, you'll also need to relock the bootloader before flashing the RUU. After flashing it, the phone will be wiped from any user data and ready to take ota updates.
so
relock bootloader:
Code:
fastboot oem relock
download the 1.27.531.11 ruu.exe from here
with the phone booted in bootloader mode or booted in the OS and connected to the windows 7 pc, lauch the ruu.exe and follow simple instructions so the ruu.exe will flash the phone automatically.
sell the phone to your friend

alray said:
So you have probably unlocked the bootloader in your attempt to root the phone. When you unlock the bootloader, it wipe users data but it also wipe some preloaded app by HTC in /data/preload. Problem is your friend will not be able to install ota updates with those missing files.
Good news is that there is a ruu for your phone version you could use to reset the phone back to stock and it will also wipe all your personal data at the same time, like if the phone was new (no need to factory reset). The ruu is a .exe file so you'll need a windows computer and because of the hboot version on the phone (1.44) you can't use windows 8.1 to flash the ruu, you'll need windows 7. Because your phone is S-ON, you'll also need to relock the bootloader before flashing the RUU. After flashing it, the phone will be wiped from any user data and ready to take ota updates.
so
relock bootloader:
Code:
fastboot oem relock
download the 1.27.531.11 ruu.exe from here
with the phone booted in bootloader mode or booted in the OS and connected to the windows 7 pc, lauch the ruu.exe and follow simple instructions so the ruu.exe will flash the phone automatically.
sell the phone to your friend
Click to expand...
Click to collapse
@alray:
My first post has a link to a picture of what the current status is of my phone, if you missed it before.
I will look at this part in more detail after I'm done with work
I'll post asap when I get a chance. Thanks!

@alray:
So I tried the bootlock command but then got the following error/problem (see screen shot).
I was either in the wrong mode or did stuff in the wrong order...
What I did:
1) open Terminal app
2) move to the adb/fastboot folder on Mac
3) type in the fastboot oem relock command
4) then received the attached screen shot error/problem.
I have a feeling the problem is going to be a bit tougher to solve than anticipated...
EDIT:
I have managed to screw up my device by doing factory reset and getting rid of the OS
EDIT 2:
I have managed to solve the above issue of no OS by getting CM 10 installed and working.
Now I need to get things back to stock to sell to my friend.
Thanks!

CTR01 said:
@alray:
So I tried the bootlock command but then got the following error/problem (see screen shot).
I was either in the wrong mode or did stuff in the wrong order...
What I did:
1) open Terminal app
2) move to the adb/fastboot folder on Mac
3) type in the fastboot oem relock command
4) then received the attached screen shot error/problem.
I have a feeling the problem is going to be a bit tougher to solve than anticipated...
EDIT:
I have managed to screw up my device by doing factory reset and getting rid of the OS
EDIT 2:
I have managed to solve the above issue of no OS by getting CM 10 installed and working.
Now I need to get things back to stock to sell to my friend.
Thanks!
Click to expand...
Click to collapse
sorry mate, my bad! The correct command is "fastboot oem lock" not "fastboot oem relock"

alray said:
sorry mate, my bad! The correct command is "fastboot oem lock" not "fastboot oem relock"
Click to expand...
Click to collapse
@alray:
No worries, I'll try that and get back to you.
Thanks.
Sent from my HTC One_M8

@alray:
So quick recap:
1) use the fastboot oem lock command
2) install the RUU.exe that you linked to me (I have it downloaded) on a Windows 7 computer (which I have)
3) then everything should be good to go and I can sell to my friend
Question:
Do I need to have HTC Sync Manager and/or USB drivers installed on the Windows 7 computer for the above process to work?

CTR01 said:
@alray:
So quick recap:
1) use the fastboot oem lock command
2) install the RUU.exe that you linked to me (I have it downloaded) on a Windows 7 computer (which I have)
3) then everything should be good to go and I can sell to my friend
Question:
Do I need to have HTC Sync Manager and/or USB drivers installed on the Windows 7 computer for the above process to work?
Click to expand...
Click to collapse
yes you need the drivers, but better to have htc sync uninstalled

alray said:
yes you need the drivers, but better to have htc sync uninstalled
Click to expand...
Click to collapse
Great, thanks for that clarification. I'll update you when I get a chance to run through the steps!

@alray:
I don't think that the M7 is communicating with the computer/adb based on the screen shot attached and that after typing in the command to lock the bootloader, it keeps waiting for device.
Thoughts?
Sent from my HTC One_M8

CTR01 said:
@alray:
I don't think that the M7 is communicating with the computer/adb based on the screen shot attached and that after typing in the command to lock the bootloader, it keeps waiting for device.
Thoughts?
Sent from my HTC One_M8
Click to expand...
Click to collapse
driver installed incorrectly? Is the phone listed in windows device manager when booted in bootloader?

alray said:
driver installed incorrectly? Is the phone listed in windows device manager when booted in bootloader?
Click to expand...
Click to collapse
@alray:
Yeah, the drivers installed just fine.
However, I actually just showed my friend the phone with CM10 on it and told him the pros/cons and he was just fine with everything since he just wanted a phone that would work and not freeze/lag like his current phone does.
So thank you for your help and the situation has been solved!

bootloader unlock is NOT working

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?

Bootloader unlock problems, OSX, have tried for almost 5 hours now with no luck

I have done what was on the HTCDev website, no luck. I have done all I can and haven't been able to succeed. I'm ranging across a plethora of problems, sometimes I can't get the phone to be recognized through fastboot, other times I can't get the authorization to work the chmod 777 command to allow for access, most of the time I just keep getting the "command not found" or things of that sort. I'm getting so furious at this process because this is the ONLY phone i've ever had any problem trying to root and I can't even get past the damn bootloader. Wtf?! Doesn't anyone have a program or something I can use besides have to screw around with Terminal constantly?
Model: opcv1
Software: 1.48.652.2
Android 4.4.2
HTC Sense 6.0
Provider: Boost Mobile

GGwhatYoNameIs said:
I have done what was on the HTCDev website, no luck. I have done all I can and haven't been able to succeed. I'm ranging across a plethora of problems, sometimes I can't get the phone to be recognized through fastboot, other times I can't get the authorization to work the chmod 777 command to allow for access, most of the time I just keep getting the "command not found" or things of that sort. I'm getting so furious at this process because this is the ONLY phone i've ever had any problem trying to root and I can't even get past the damn bootloader. Wtf?! Doesn't anyone have a program or something I can use besides have to screw around with Terminal constantly?
Model: opcv1
Software: 1.48.652.2
Android 4.4.2
HTC Sense 6.0
Provider: Boost Mobile
Click to expand...
Click to collapse
Did you turn the USB debugging mode on in the phones settings? You know you have to enable developer options?

MrMike2182 said:
Did you turn the USB debugging mode on in the phones settings? You know you have to enable developer options?
Click to expand...
Click to collapse
Yeah, i've done that.

if your on linux,you need to do sudo fastboot whatever. post some errors,ill try and help you.

HTC Desire 626s Reset Issue

Hello,
Phone: HTC Desire 626s Metro PCS
htc_a32eul
Bootloader: unlocked
Recovery: Stock
I was trying to reset using TWRP. I selected everythign and wiped it. Rookie Mistake. After doing that my device no longer shows up when trying to use adb. So i reset recovery to stock. Im not sure how to fix this. I have tried to load ruu thru adb but phone just stops on htc logo and ruu installer stops after accepting terms and hitting next. Please help. If there is any information I can provide that will help figure this out I will post it immediatley.
So i figured out that i wasnt running the adb cmd promt as administrator and that was making a big difference.
My only issue now is i need the rom to flash back onto the device. I extracted the rom.zip from the RUU.exe but I ran into a error when tryign to install it. Is anyone familiar with the process involed to make the file ready for install. The error was wrong header.
The zip.rom has 15 zip files there are two with signed_boot.img files inside.
If someone can guide me on the process of making this ready for install it would be appreciated. When tryign to fastboot oem rebootRUU then runnign the ruu on the pc the ruu stops and shuts down after accepting the agreement and hitting next. Any input on why this is happening would be of great help.
If anyone has a backup of the stock rom I would gladly pay for it to be uploaded for me to use.

I have the stock RUU from the htc website but cant get the rom extracted so i can install from sd card. My device is not recognized my my pc untill i boot into twrp. Does anyone have any advice.

Ok I figured it out just thought i would post what was happenign incase anyone else was having the same issue.
First I wasn't starting the cmd promt as administrator. As soon as I did I had no more issues with adb.
Second the RUU for the HTC Desire 626s for METRO PCS that I downloaded from the HTC Dev website would open then just stop after accepting the user agreement. That was fixed by installing:
Microsoft Visual C++ 2008 Redistributable Package (x86)
http://www.microsoft.com/en-us/download/confirmation.aspx?id=29
From there I ran CMD as admin
cd c:\path where adb.exe is stored
fastboot oem rebootRUU whith device in download mode
Then ran the RUU for the HTC Desire 626 Metro PCS
Voila it worked. This trouble i had was most likely rookie mistakes that seem like common knowledge to some but for me I wasnt aware. Thank you xda! I was only able to figure this out because of other posts and information I found on XDA.

Hi!
Do you have an stock ROM backup you can send me?

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.