Database Develop

[Q] Updating a holiday nexus one

Hello, I have a Holiday Nexus one and I'm trying to get froyo on it but it didn't update .
Things I've tried:
1) Calling the support HTC line.. they told me to move the date to a future date and wait a couple days... that failed.
2)I've tried manual updating using the bootloader/recovery method but all the files I've tried I get a corrupt/invalid file
3)I've also tried dialing *#*#CHECKIN#*#* on my phone and waiting.. I've done this everyday since I've had my phone (2 weeks)
The guy at HTC suggested I call AT&T and have them push the update to me but I want to know if there's any other options I have? I will try to call them tomorrow but I've a feeling they're not going to be of much help. Thanks in advance.
Also I saw the thread on this forum but the files were corrupt so maybe I can get a new link or something maybe?
Any help appreciated thanks
Always include:
Carrier: AT&T
Country / Language: US
OS / Browser / build number (if applicable):ERD56C (Holiday Nexus One this is still a 2.1 build)

Holiday Nexus? And you're looking to update? Are you serious?
Boot into fastboot
fastboot oem unlock
fastboot flash recovery <download and put Amon_RA's 1.9.0-alpha here>
fastboot reboot recovery
Download FRF91 stock PASSIMG
Copy to SD card
Install through recovery
Reboot
You're done, wait for 2.2.1 update.
Or instead, just download a custom ROM of your choice, which might prove a much better option.
Whenever you feel you don't like the lock sign, fastboot oem lock
Read my signature and use the suggestion.

[Q] razr i problems - fastboot menu

Hi guys, I am having an issue i cant seem to resolve on my razr i. apologies if this has already been covered in another thread (or 10, which is usually the way with these things because nobody reads the other threads) I have been through a load of other threads but cannot seem to resolve my issue so i started my own.
Right, I have switched from iphone to razr and am not stupid when it comes to jailbreaking etc so thought rooting the razr wouldnt be a problem. when trying to root it it failed and i am stuck at the fastboot menu, however, everything on the menu is disabled so i cant use it. i get the usual message:
fastboot reason: flash failure
fastboot max download size: 100mb
usb connected
if i try to use anything on the menu i get the following message:
fastboot menu disabled.
my phone is not unlocked and not rooted. i have barely done anything to it other than install a couple of free apps. i am unable to progress past this screen. the phone is GB and is on 4.0.4
any help you guys can give would be greatly appreciated. again, apologies if this has already been covered, none of the solutions i found were able to resolve my issue. as i said, i had no problems jailbreaking my old iphone, i am a bit of a n00b when it comes to droids...

AW: [Q] razr i problems - fastboot menu
Are you able to run fastboot commands ? Cause in that case you might be able To unlock bootloader and reflash the software .
Sent from my XT890 using xda premium

xX_Alex_Xx said:
Are you able to run fastboot commands ? Cause in that case you might be able To unlock bootloader and reflash the software .
Sent from my XT890 using xda premium
Click to expand...
Click to collapse
I am not able to do anything. if i scroll to any of the options on the menu as soon as i hit the volume up key it just returns a message advising the fastboot menu is disabled.
**edit
ah commands not menu options. not sure how i go about doing that. i am 100% new to droid...

ged flanders said:
Hi guys, I am having an issue i cant seem to resolve on my razr i. apologies if this has already been covered in another thread (or 10, which is usually the way with these things because nobody reads the other threads) I have been through a load of other threads but cannot seem to resolve my issue so i started my own.
Right, I have switched from iphone to razr and am not stupid when it comes to jailbreaking etc so thought rooting the razr wouldnt be a problem. when trying to root it it failed and i am stuck at the fastboot menu, however, everything on the menu is disabled so i cant use it. i get the usual message:
fastboot reason: flash failure
fastboot max download size: 100mb
usb connected
if i try to use anything on the menu i get the following message:
fastboot menu disabled.
my phone is not unlocked and not rooted. i have barely done anything to it other than install a couple of free apps. i am unable to progress past this screen. the phone is GB and is on 4.0.4
any help you guys can give would be greatly appreciated. again, apologies if this has already been covered, none of the solutions i found were able to resolve my issue. as i said, i had no problems jailbreaking my old iphone, i am a bit of a n00b when it comes to droids...
Click to expand...
Click to collapse
Had the same problem, I used the recommendation in this thread, 5th post and it worked, but afterwards need to re-download apps from PlayStore:
http://forum.xda-developers.com/showthread.php?p=36612151
Follow the instructions exactly - you need the drivers and RSD lite on Windows PC, then connect the phone via usb cable that came with it; and you'll need a full unzip program (cost) so you can move the unzipped files into RSD lite. Get the right flash file though - there's a list in the linked post if you don't want GB retail which I used. Important: this only works for ICS 4.0.4 and don't try to downgrade to an earlier version than what's currently on your phone e.g. v.39 to v.31, for example.
Good luck.

AW: [Q] razr i problems - fastboot menu
If the solution from mervluk does not work (It didn't work for me either) , you should try if you are able to use the fast boot commands .
To do that simply connect your phone to the PC. Then download fast boot , if you do not already have that. It is in the .zip from the RAZR I root thread.
The go to the downloaded folder. There hold shift and perform a right mouse click. Then choose" start a command prompt here "or something similar (don't know how the option is called in English).
Then type in
fastboot reboot
When the phone reboots you might be able to unlock your phone and flash the software.
BUT BE AWARE! YOU WILL LOSE YOUR WARRANTY!!
So you better try the other solution first. This should be your last option.
If you don't know how to unlock the bootloader look in the RAZR I forum or pn me .
Alex
Sent from my XT890 using xda premium

mervluk said:
Had the same problem, I used the recommendation in this thread, 5th post and it worked, but afterwards need to re-download apps from PlayStore:
http://forum.xda-developers.com/showthread.php?p=36612151
Follow the instructions exactly - you need the drivers and RSD lite on Windows PC, then connect the phone via usb cable that came with it; and you'll need a full unzip program (cost) so you can move the unzipped files into RSD lite. Get the right flash file though - there's a list in the linked post if you don't want GB retail which I used. Important: this only works for ICS 4.0.4 and don't try to downgrade to an earlier version than what's currently on your phone e.g. v.39 to v.31, for example.
Good luck.
Click to expand...
Click to collapse
thanks buddy. i will give this a whirl and let you know how i get on. fingers crossed!

mervluk - your advice worked a treat. i got it working again. thanks !
now i am working again, what cool tricks do people advise. is it worth rooting it ? what can i do once it is rooted? am i able to network unlock it myself ?

ged flanders said:
mervluk - your advice worked a treat. i got it working again. thanks !
now i am working again, what cool tricks do people advise. is it worth rooting it ? what can i do once it is rooted? am i able to network unlock it myself ?
Click to expand...
Click to collapse
Glad about that. This phone can be a bit of a so-and-so. ics is being updated ota to Jelly Bean 4.1.2, which I've avoided so far to keep fm (although not activated on the supplied software). I did succeed with unlocking the bootloader (loose warranty - important) following the whole complicated procedure on Moto's website - but couldn't myself use the shortcuts on here. (Then had to set up again and re-download everything from the PlayStore). It required the Moto-supplied key. I then rooted, though I think the JB ota download unroots again? You can't use RSD lite with JB.
With JB the procedures are different, and a modified JB European (not for use with GB) firmware is now available on another thread which is impressing some posters. But I think just be a bit cautious as there does not appear to be any fix for the "service code corrupt" bootloader error yet. Looks like the options are very restricted whilst no-one understand the interaction between Google Android and the intel atom chipset.
I have a network unlock key from one of the commercial suppliers (cellunlocker.net), but haven't needed to try and use it yet!

bootloader not allow

I have T-Mobile G1 . I suffered a lot from the old 1.0 android . specially when I wipe my phone
today I flashed a cupcake official rom . but I am stuck on the activation screen
i tried this
http://forum.xda-developers.com/showthread.php?t=1098899
but I CAN'T FLASH THE BOOTLOADER IMAGE . always it says . checking .......... not allow . then it returns to the rainbow screen
I tried all the DREAIMG.nbh images I found on the internet . the same message
I need to know what I did wrong?
I only flashed an update.zip package . may it raised my firmware no . but why this deny my trials to downgrade ? I did before smoothly . but now noooo
the problem is when I tried to write down the code <enter>setprop persist.service.adb.enable 1<enter> nothing happened . but before it worked with me
Do I need to goldcard?
please help me . I am turning angry from this phone

Firstly wrong section, this should be in general section not dev section, remember that for next time you post
Secondly - the standard hboot on 1.5 won't let you flash an unsigned/unchecked boot loader so you don't brick your device
Thirdly, there is a guide on skipping activation, follow that, it let's you enable ADB, then let's you enable wifi so you can login to a Google account without mobile data, the command you typed only enables ADB - it wont do anything else, you need ADB on your PC to open WiFi settings
I suggest you try using the 'Search' function on xda to find the guide on that
I know some people struggle with the concept of a search function so try this link:
http://forum.xda-developers.com/showthread.php?t=452316
Sent from my Desire HD using xda app-developers app

If you are on Android 1.5, you could also use *flashrec* to flash a custom recovery and then flash the appropriate radio & bootloader images from there. If you would like to go for the "new" radio/bootloader combination (Radio: 2.22.28.25 SPL: 1.33.0013d) to get additional 14MB of memory, follow Terry's instructions (a link you can find in my signature).
If you are not able to get the phone running and you want to flash the dreaimg.nbh, you need to have a goldcard because the bootloader is checking the signature.

[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!

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.