Is my phone's bootloader really unlockable? - AT&T Samsung Galaxy S6

Model Number - Samsung-SM-G920A
Android Version - 7.0
Android Security Patch Level - August 1, 2017
Baseband Version - G920AUCS6EQH1
Kernel Version - 3.10.61-10950877, [email protected] #1, Aug 10 2017
Build Number - NRD90M.G920AUCS6EQH1
Knox Version 2.7.1
So I've just finished spending about 6 hours trying to root this phone. I've tried about 8 different root methods involving one-click applications, odin, and minimal adb fastboot tool without any success. I've also tried installing several different S6 specific TWRP .tar files using odin without any success. At this point, I'm thinking all this failure has to be due to a locked bootloader, however, I also can't even successfully check the bootloader status. None of the service menu dial codes I've come across have opened a menu that has the "service info" option needed to check the bootloader status. And all the other methods for checking bootloader status involve putting the phone into fastboot mode, which I don't think this phone has (only odin mode and recovery mode). When I issue the "adb reboot bootloader" command into the adb it just restarts the phone normally (no fastboot mode). My developer options screen also doesn't have that "OEM unlocking" option I keep reading about.
So my question is - Is there some step I'm missing, or is this phone's bootloader just unlockable? And if it is unlockable, is there any other way I can root the phone? All I want to do is delete all the bloatware off the phone, nothing fancy. Thank you to whoever takes the time to offer their help

jbora1788 said:
Model Number - Samsung-SM-G920A
Android Version - 7.0
Android Security Patch Level - August 1, 2017
Baseband Version - G920AUCS6EQH1
Kernel Version - 3.10.61-10950877, [email protected] #1, Aug 10 2017
Build Number - NRD90M.G920AUCS6EQH1
Knox Version 2.7.1
So I've just finished spending about 6 hours trying to root this phone. I've tried about 8 different root methods involving one-click applications, odin, and minimal adb fastboot tool without any success. I've also tried installing several different S6 specific TWRP .tar files using odin without any success. At this point, I'm thinking all this failure has to be due to a locked bootloader, however, I also can't even successfully check the bootloader status. None of the service menu dial codes I've come across have opened a menu that has the "service info" option needed to check the bootloader status. And all the other methods for checking bootloader status involve putting the phone into fastboot mode, which I don't think this phone has (only odin mode and recovery mode). When I issue the "adb reboot bootloader" command into the adb it just restarts the phone normally (no fastboot mode). My developer options screen also doesn't have that "OEM unlocking" option I keep reading about.
So my question is - Is there some step I'm missing, or is this phone's bootloader just unlockable? And if it is unlockable, is there any other way I can root the phone? All I want to do is delete all the bloatware off the phone, nothing fancy. Thank you to whoever takes the time to offer their help
Click to expand...
Click to collapse
Mine is the same. However you can use minimal ADB Fastboot to manually uninstall most apps. I used the 'app inspector' app to see what to type to uninstall them. Be sure you know what you are uninstalling! .youtube.com/watch?v=VjDn56jNTbQ

Related

Unlocked Bootloader Error Message - System Update Failing

I am from India and I exchanged my iPhone 4S for a Moto X 2014 just this evening wanting to try my hands on the Android experience.
I do not know what the seller did to this phone but I now have two issues. I tried to call the seller immediately after I noticed these problems when I came home but the number is switched off. Shame on him!
After Google'ing I found this forum for android support so I hope posting the problems here would give me some solution
Problem #1: Every time when I boot my phone, it has the warning screen which says "Warning unlocked bootloader".
Problem #2: The warning went off and landed me on the home screen. I connected to my WiFi and saw that there is a software update. I downloaded it and chose to install it. It kept rebooting for 4-5 times and then said "System Update - Failed".
Can anyone please be patient enough to give me step by step solution with download links to get my Moto X2 back in shape as how it was out of the box?
I googled a lot for the keywords "relock bootloader moto x 2014", "unroot moto x 2014" and plenty of links with different download links came up. I do not know which one to trust. I am not dumb and I can easily follow instructions. So, please anyone wanna help?
If the OTA (software update) is failing, maybe it's because the firmware you have was installed via custom recovery, not stock, or even the firmware is custom too, that's why you get a bootloop if you try to install the update.
Can you post a screenshot of your "About phone"? (Settings>About phone).
Nek0x90 said:
If the OTA (software update) is failing, maybe it's because the firmware you have was installed via custom recovery, not stock, or even the firmware is custom too, that's why you get a bootloop if you try to install the update.
Can you post a screenshot of your "About phone"? (Settings>About phone).
Click to expand...
Click to collapse
Thank you for the reply. Attached the screenshot.
i64.tinypic.com/2nu3asn.png
I fiddled around to find out how to get into the Fastboot mode... and I observed something weird there..
AP Fastboot Flash Mode (S)
60.16 (sha-#some checksum number key with date 2015-04-02 and time#
CPU: MSM8974AC EA1.1
eMMC: 2048MB Samsung RV=07 PV=0B TY=57
Battery OK
Device i UNLOCKED. Status Code: 3
Software status: Official
I mean Seriously? I see the word Samsung in a Moto phone? I so regret buying from this seller... too much for a first Android phone :crying:
Well I also managed to Google more and installed the device drivers and the Fastboot software in my Windows PC.
Booted my device in fastboot mode and issues the below commands:
fastboot devices
#my device was shown#
fastboot oem lock
#told me to use the command with begin#
fastboot oem lock begin
#Said something like the image is ready#
Nothing happened then though. I powered on my device and I still see that warning. Still the software update is failing. :crying::crying::crying:
You don't need to unlock your bootloader, it is already unlocked, that's why the bootloader says that the "Device is unlocked", but also says your firmware is stock (Status software official).
If your firmware is stock, I don't know why its failing to apply the update, maybe is because your phone has a custom recovery. Try to enter into that option in the bootloader and see what happens.
Nek0x90 said:
You don't need to unlock your bootloader, it is already unlocked, that's why the bootloader says that the "Device is unlocked", but also says your firmware is stock (Status software official).
If your firmware is stock, I don't know why its failing to apply the update, maybe is because your phone has a custom recovery. Try to enter into that option in the bootloader and see what happens.
Click to expand...
Click to collapse
I am not trying to unlock my bootloader. I am trying to restore it back to the "out of the box" state. I mean I want to lock it and I want it to be in the state how it usually is when bought from the store.
Ok... I google'd how to go into the recovery mode and found this link (teamandroid.com/2015/01/08/enter-recovery-mode-moto-x/).
I followed those steps:
1. Turn OFF your phone.
2. Press and hold the Volume Down button for 2-5 seconds. While holding the Volume Down button, press the Power Button for 1-2 seconds and release.
3. I used the Volume down key to highlight "Recovery" and clicked on the power button to select it.
4. My screen went off. I mean the light gone.
Then I had to press and hold the power on button, it booted my phone with that warning unlocked bootloader message.
What am I doing wrong?
UPDATE:
I did a fastboot, connected phone to PC and issued the below command from PC and get below error:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
UPDATE 2:
I enabled the developers option (by tapping on the Build number multiple times)
So, I installed an app called MobileUncle Tools.
I then opened the app from my mobile and clicked on "Reboot into recover".
It says "Please root your Android first".
OK.. so looks like the phone is not rooted - which is good.
Only the bootloader is unlocked. All I need to figure out is - re-lock my bootloader and make the system update go through successfully.
Any help please?
You must unlock the Developer Options in your phone, and then activate the debugger mode to be able to use adb commands like "adb reboot recovery".
In the About phone menu in settings, press five times the option of "Build number", then the Developer options in settings will be available. Navigate to that menu and activate the Android debugging option, then you should be able to use adb from a command window in your PC.
EDIT: Also, you have to press the up volume button in the bootloader to choose an option, not the power button.
Having the bootloader unlocked doesn't affect system updates via OTA or anything if your firmware and recovery are stock. Your firmware seems to be stock, so there's no problem with it, but I'm not sure about your recovery.
Nek0x90 said:
You must unlock the Developer Options in your phone, and then activate the debugger mode to be able to use adb commands like "adb reboot recovery".
In the About phone menu in settings, press five times the option of "Build number", then the Developer options in settings will be available. Navigate to that menu and activate the Android debugging option, then you should be able to use adb from a command window in your PC.
EDIT: Also, you have to press the up volume button in the bootloader to choose an option, not the power button.
Having the bootloader unlocked doesn't affect system updates via OTA or anything if your firmware and recovery are stock. Your firmware seems to be stock, so there's no problem with it, but I'm not sure about your recovery.
Click to expand...
Click to collapse
I have one question for you:
What do you mean by "Your firmware seems to be stock, so there's no problem with it, but I'm not sure about your recovery".
My understanding is - you are saying my stock firmware is intact because it said Official in the fastboot screen. Right?
Ok... now back to the recovery check... I think I did it.
1. I went in the fastboot mode
2. Used volume down key to scroll down to Recovery option (2nd option)
3. Pressed Volume up key to select it
4. The phone rebooted (The white screen "warning unlocked bootloader" message was displayed this time too)
5. I saw a dead android symbol with the word "No command."
6. I pressed Power and Volume Up key. I saw the recovery screen I guess. There were many options - Wipe data, Wipe Cache, Install from SD, etc.
What do I need to check there?
EDIT:
Ok I noted this number from there:
Android system recovery <3e>
LPE23.32-25.1
followed by the options
reboot system now
apply update from sdcard
etc.
I think this is what has happened:
Google says "LPE23.32-25.1" is the Android 5.1 Lollipop update (v23.16.1, build LPE23.32-25.1)
However, the current Android version on my device "About" screen is 4.4.4
The OTA system update, my device telling me about is Android 5.0 Lollipop version: 22.21.19.en.EU (which is a lower version than my recovery's version)
My menu options look all white and after google'ing I realize that it has Android L's menu. Please see the screenshot i65.tinypic.com/14l4mmb.png
Could that be that reason? What can I do t rectify it?
1) You most likely will want to keep your bootloader unlocked, since it'll give you more freedom to deal with roms and flashing. It won't affect taking OTAs, in fact, I've just taken the 6.0 OTA and my bootloader is unlocked.
2) Don't worry about the Unlocked Bootloader Message. That can be fixed by flashing the correct logo.bin file.
3) If your device is in KitKat (4.4.4) but your bootloader is from Lollipop (5.0 or 5.1), DON'T TAKE THE OTA. There's one post here saying that it'll cause a hardbrick. Your solution will be to manually flash the correct firmware or use RSD Lite.
joseph_1802 said:
1) You most likely will want to keep your bootloader unlocked, since it'll give you more freedom to deal with roms and flashing. It won't affect taking OTAs, in fact, I've just taken the 6.0 OTA and my bootloader is unlocked.
2) Don't worry about the Unlocked Bootloader Message. That can be fixed by flashing the correct logo.bin file.
3) If your device is in KitKat (4.4.4) but your bootloader is from Lollipop (5.0 or 5.1), DON'T TAKE THE OTA. There's one post here saying that it'll cause a hardbrick. Your solution will be to manually flash the correct firmware or use RSD Lite.
Click to expand...
Click to collapse
THANK YOU SO MUCH for clearing that point 1 and 2. That is a relief!
Point #3 - "Your solution will be to manually flash the correct firmware or use RSD Lite."
What do I flash? OTA 5.1 (because my bootloader is from 5.1) or OTA 22.21.19.en.EU (because that is what I see in my phone's Software Update Available screen.
Where do I download those OTA files?
How do I flash using RSDLite? Any guide?
Thank you!
UPDATE:
Found the guide forum.xda-developers.com/showthread.php?t=2231249
I only need to know what I version I need to flash AND where can I download it from. Please?
Best option is flashing the entire firmware of your phone variant using RSDLite. The firmware you're looking for (based on what Google says) is VICTARA_RETEU_XT1092_5.1_LPE23.32-25.3
Can you confirm this? If it's correct, then the firmware is in this folder (Firmwares 5.1 stagefright solved): https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg
Nek0x90 said:
Best option is flashing the entire firmware of your phone variant using RSDLite. The firmware you're looking for (based on what Google says) is VICTARA_RETEU_XT1092_5.1_LPE23.32-25.3
Can you confirm this? If it's correct, then the firmware is in this folder (Firmwares 5.1 stagefright solved): https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg
Click to expand...
Click to collapse
My recovery screen showed LPE23.32-25.1
So there is just the last number change... the download link you gave is for the version ending with .3 where my recovery shows .1
That should not be a problem, or should it?
Flower07 said:
My recovery screen showed LPE23.32-25.1
So there is just the last number change... the download link you gave is for the version ending with .3 where my recovery shows .1
That should not be a problem, or should it?
Click to expand...
Click to collapse
No it's not a problem. This will give you the latest version with the stagefright patch.
Sent from my XT1095 using Tapatalk
It is .3 because it has the stagefright patch, the .1 version doesn't have that patch but both of them are basically the same, so there's no problem if you flash one or another.

Tutorial: Root LeEco S3

After seeing people not being able to root their S3 and rooting mine successfully, I have decided to make this tutorial to help those out there. This tutorial covers the procedures I took to successfully root my LeEco S3 US edition with EUI 5.8.018S and Snapdragon 652 processor. My phone is permantly rooted and has permanent TWRP recovery.
Make sure your phone has developer options and has usb debugging as well as the option to unlock the bootloader enabled
First off, download the AIO Toolkit created by Rishabh Rao here
Secondly, open the toolkit. Make sure to turn off your antivirus to avoid any interruptions. Once in the toolkit, select item 6 and allow the program to download necessary files. After the files have downloaded, select item 1 to install ADB/Fastboot USB drivers. During this process, PDA Net will prompt you to connect your phone to the computer. It will download the client onto your computer and install the PDA Net application onto your phone. When the drivers are fully installed, close the toolkit.
Open command prompt and run ADB. With your phone plugged in and in recovery mode, type fastboot oem unlock-go and you should see it attempting to unlock the bootloader. If you get a successful message of unlocking your bootloader, you are ready to move on to the next step as this is a temporary unlock. Close the command prompt.
Open the toolkit again, select item 6 and then select item 3 to unlock bootloader completely. When it has finished, go back to select item 4 to check and see if the bootloader has been unlocked. If so, move on to selecting item 5 to flash the latest TWRP recovery.
When the TWRP recovery has installed, if it has not booted into recovery by itself, hold down power + volume up to enter it. You will see the recovery all in the chinese language. Simply swipe the unlock to proceed and from the menu, select the box to the right and three down (which is settings). There, select the globe icon and scroll down to select the english language. Now that you can read what is there, go back to the main menu and select wipe to completely wipe the phone back to factory defaults. When it has finished, go back and select Advanced > Tools > Root Device. Your phone will now be rooted when you reboot and will have the latest TWRP recovery installed.
- If you receive the error message saying the device is locked while you are trying to unlock the bootloader from the toolkit, you need to run ADB again to temporary unlock the bootloader.
Quick question - will this only work on 18s and is it possible to update the firmware and keep root after doing this? Or would it work after updating to I think 21s which is the latest?
Thank you!
Hi
Can you break this down further with pictures too? How do I do the command prompt ABD thing?
Root
was this the easiest way? I'm going to try it in two days. Scared to mess my phone up though..
This method does not work on the 23s ROM. Does nothing
What's the best way? Simple way I mean?
Worked for anyone?
these instructions are for the le s3 with SNAPDRAGON processor, not for the MEDIATEK x20 that is where we have the problem
Just got this phone and gonna try this out, thanks ;p
---------- Post added at 11:06 AM ---------- Previous post was at 10:13 AM ----------
Actually Ima wait...I've never rooted using TWRP Recovery so not quite familiar with it after the phone's been rooted. I've only used a couple of the one-click root apps, KingRoot and KingoRoot, for a couple phones.
Rooted it fine, now I need to figure out what I can do ;P <--- noob
How were you able to successfully root the phone?
GWARslave119 said:
Rooted it fine, now I need to figure out what I can do ;P <--- noob
Click to expand...
Click to collapse
How were you able to successfully root the phone?
i dont know what to do,, it says "waiting for device" what should i do ? i already installed the 15 sec ADB something like that.. i need your help plsssss
Rooting Le S3.
XtraTerr3sTRiAL said:
After seeing people not being able to root their S3 and rooting mine successfully, I have decided to make this tutorial to help those out there. This tutorial covers the procedures I took to successfully root my LeEco S3 US edition with EUI 5.8.018S and Snapdragon 652 processor. My phone is permantly rooted and has permanent TWRP recovery.
Make sure your phone has developer options and has usb debugging as well as the option to unlock the bootloader enabled
First off, download the AIO Toolkit created by Rishabh Rao here
Secondly, open the toolkit. Make sure to turn off your antivirus to avoid any interruptions. Once in the toolkit, select item 6 and allow the program to download necessary files. After the files have downloaded, select item 1 to install ADB/Fastboot USB drivers. During this process, PDA Net will prompt you to connect your phone to the computer. It will download the client onto your computer and install the PDA Net application onto your phone. When the drivers are fully installed, close the toolkit.
Open command prompt and run ADB. With your phone plugged in and in recovery mode, type fastboot oem unlock-go and you should see it attempting to unlock the bootloader. If you get a successful message of unlocking your bootloader, you are ready to move on to the next step as this is a temporary unlock. Close the command prompt.
Open the toolkit again, select item 6 and then select item 3 to unlock bootloader completely. When it has finished, go back to select item 4 to check and see if the bootloader has been unlocked. If so, move on to selecting item 5 to flash the latest TWRP recovery.
When the TWRP recovery has installed, if it has not booted into recovery by itself, hold down power + volume up to enter it. You will see the recovery all in the chinese language. Simply swipe the unlock to proceed and from the menu, select the box to the right and three down (which is settings). There, select the globe icon and scroll down to select the english language. Now that you can read what is there, go back to the main menu and select wipe to completely wipe the phone back to factory defaults. When it has finished, go back and select Advanced > Tools > Root Device. Your phone will now be rooted when you reboot and will have the latest TWRP recovery installed.
- If you receive the error message saying the device is locked while you are trying to unlock the bootloader from the toolkit, you need to run ADB again to temporary unlock the bootloader.
Click to expand...
Click to collapse
Hi Everyone. I recently got a new le s3 x522. Its great only that sim 2 slot doesn't connect to mobile data. I have tried rooting so that I can use build prop editor to fix this, but rooting has become a real problem. I used Kingo root, framaroot but not successful. I have downloaded AIO toolkit on pc but installng is a problem. Please guide me on how to install AOI toolkit on pc. I pretty new to this things you know. Any help will be greatly appreciated.

Huawei P9 - Failed TWRP attempt

Hello friends, I'm Berat, living in Istanbul, Turkey.
I tried to install TWRP on my device (HUAWEI P9) for root yesterday. I couldn't go further from the Fastboot - ADB method. Although I do one-to-one with source videos from Youtube, I have encountered error messages. The phone is running like stable but I have a few problems with my phone.
1- I want to complete root if i can do that.
2- OEM Unlocking is unclickable now and this is disable now, and of course it can't be changed. :victory:
3- I wanted to go back to the original version but it doesn't work either, OEM Unlocking is same; unclickable. I did enter the Fastboot menu and i saw the last status: Phone - Unlocked / FRP - Locked
How should I proceed? Which one is the easier, ROOT or the original version?
Thank you!
beratkazal said:
Hello friends, I'm Berat, living in Istanbul, Turkey.
I tried to install TWRP on my device (HUAWEI P9) for root yesterday. I couldn't go further from the Fastboot - ADB method. Although I do one-to-one with source videos from Youtube, I have encountered error messages. The phone is running like stable but I have a few problems with my phone.
1- I want to complete root if i can do that.
2- OEM Unlocking is unclickable now and this is disable now, and of course it can't be changed. :victory:
3- I wanted to go back to the original version but it doesn't work either, OEM Unlocking is same; unclickable. I did enter the Fastboot menu and i saw the last status: Phone - Unlocked / FRP - Locked
How should I proceed? Which one is the easier, ROOT or the original version?
Thank you!
Click to expand...
Click to collapse
- Which stock Android do you have, Marshmallow, Nougat or Oreo
- Which TWRP are you flashing
EMUI versions are different, each has different organization of partitions (names and sizes, different encryption types).
You must use different port of TWRP for different version of stock Android.
Wrong TWRP may not work or may even cause a brick
For Nougat, instructions are in this thread:
https://forum.xda-developers.com/newreply.php?do=newreply&noquote=1&p=71244945
but a little bit newer version of TWRP for Nougat is in the post #1 here:
https://forum.xda-developers.com/p9/development/rom-huawei-p9-magicrainbow-v4-t3759292
---
For disabled and grayed out OEM Unlocking:
Boot to eRecovery (switch off, connect to charger, press and keep pressing Vol+, press Power).
From eRecovery, choose Download and Install latest firmware and recovery.
Upon installation (before booting to System), choose Factory reset and Clear Cache
You will need to enable again Developer options and OEM unlock (it should not be gray anymore).
If Bootloader will be locked, unlock with the same, previous code
zgfg said:
- Which stock Android do you have, Marshmallow, Nougat or Oreo
- Which TWRP are you flashing
EMUI versions are different, each has different organization of partitions (names and sizes, different encryption types).
You must use different port of TWRP for different version of stock Android.
Wrong TWRP may not work or may even cause a brick
For Nougat, instructions are in this thread:
https://forum.xda-developers.com/newreply.php?do=newreply&noquote=1&p=71244945
but a little bit newer version of TWRP for Nougat is in the post #1 here:
https://forum.xda-developers.com/p9/development/rom-huawei-p9-magicrainbow-v4-t3759292
---
For disabled and grayed out OEM Unlocking:
Boot to eRecovery (switch off, connect to charger, press and keep pressing Vol+, press Power).
From eRecovery, choose Download and Install latest firmware and recovery.
Upon installation (before booting to System), choose Factory reset and Clear Cache
You will need to enable again Developer options and OEM unlock (it should not be gray anymore).
If Bootloader will be locked, unlock with the same, previous code
Click to expand...
Click to collapse
Thank you for answer to me. But i have another problem... Visit here please: https://forum.xda-developers.com/p9/help/help-huawei-p9-device-unlocked-booting-t3932699
Thanks...

I broke my huawei p9 digitally!

Another help me post so please understand this is my last breath asking for guidance and advice, here goes.
I have a huawei p9 thats gotten an unlocked bootloader. in the past i added twrp and flashed a custom rom. somewhere down the line my its gotten really bad. i cannot select twrp recoverey mode nor can i manualy boot into twrp because my custom rom closes dev options in my settings. as i click it instantly closes. this happens to magisk and twrp app on the phone. so since i cannot enable oem unlock or usb debugging i cannot use my pc to harbour my device, adb shell wont recognise the device when opened in the adb directory using serveral guides.
here is a list of what i cannot do,
fastboot&rescue mode is it's only reboot function apart from loading custom firmware.
cannot access twrp thats on the device (used it to flash a firmware, also tried the .apk)
windows adb wont recognise the device neither will hisuite (huawei's windows device manager)
cannot load dev options even though i have it unlocked through clicking build 7-10 times. (opens and closes simultaneously)
i cannot enable usb debugging via dev options (custom firmware wont load it even though it's unlocked)
once phone reboot's into recovery mode it says android reason reboot; cold boot N/A (phone unlocked/FRP unlocked) no options to navigate from there.
KingBevster said:
Another help me post so please understand this is my last breath asking for guidance and advice, here goes.
I have a huawei p9 thats gotten an unlocked bootloader. in the past i added twrp and flashed a custom rom. somewhere down the line my its gotten really bad. i cannot select twrp recoverey mode nor can i manualy boot into twrp because my custom rom closes dev options in my settings. as i click it instantly closes. this happens to magisk and twrp app on the phone. so since i cannot enable oem unlock or usb debugging i cannot use my pc to harbour my device, adb shell wont recognise the device when opened in the adb directory using serveral guides.
here is a list of what i cannot do,
fastboot&rescue mode is it's only reboot function apart from loading custom firmware.
cannot access twrp thats on the device (used it to flash a firmware, also tried the .apk)
windows adb wont recognise the device neither will hisuite (huawei's windows device manager)
cannot load dev options even though i have it unlocked through clicking build 7-10 times. (opens and closes simultaneously)
i cannot enable usb debugging via dev options (custom firmware wont load it even though it's unlocked)
once phone reboot's into recovery mode it says android reason reboot; cold boot N/A (phone unlocked/FRP unlocked) no options to navigate from there.
Click to expand...
Click to collapse
There was another question and answer about the bricked phone with FRP locked in this same P9 Q&A subforum, see there for DC Phoenix
https://forum.xda-developers.com/showpost.php?p=80633145&postcount=2
zgfg said:
There was another question and answer about the bricked phone with FRP locked in this same P9 Q&A subforum, see there for DC Phoenix
https://forum.xda-developers.com/showpost.php?p=80633145&postcount=2
Click to expand...
Click to collapse
i have found it, thank you.

[MANUAL]Unlock bootloader for locked AT&T device

1. You need to join the beta testing program
2. You should receive an over-the-air update of ~ 250MB for Android 12L Beta 1, install the update.
3. After updating and rebooting the device, go back to the beta testing program website and click the "Disable" button.
4. You will again receive an update in the size of ~ 150 mb, this is a rollback to the stable assembly of Android 12 (SQ1A.211205.008). After installing this update, there will be a reboot and the phone will be automatically reset to factory settings.
5. We go through the initial setup, go to the settings and activate the developer mode (in the "About phone" item, tap 5 times on the build number). Go to the "For Developers" menu (Settings-> System-> For Developers).
6. Next, download the platform tools to your pc and unpack the folder to the C: \ drive. Installing the drivers.
7. We transfer the phone to fastboot mode, turn off the phone and hold down power + volume down, connect it to the PC.
8. Open the command line as administrator (Win + X-> Command line (administrator)).
cd C:\platform-tools
fastboot devices
fastboot flashing unlock
After the commands have been executed, the device will reboot and will be reset to factory settings.
We go to the settings and check
Bootloader is unlocked.
Source
dvrk__soul said:
1. You need to join the beta testing program
2. You should receive an over-the-air update of ~ 250MB for Android 12L Beta 1, install the update.
3. After updating and rebooting the device, go back to the beta testing program website and click the "Disable" button.
4. You will again receive an update in the size of ~ 150 mb, this is a rollback to the stable assembly of Android 12 (SQ1A.211205.008). After installing this update, there will be a reboot and the phone will be automatically reset to factory settings.
5. We go through the initial setup, go to the settings and activate the developer mode (in the "About phone" item, tap 5 times on the build number). Go to the "For Developers" menu (Settings-> System-> For Developers).
6. Next, download the platform tools to your pc and unpack the folder to the C: \ drive. Installing the drivers.
7. We transfer the phone to fastboot mode, turn off the phone and hold down power + volume down, connect it to the PC.
8. Open the command line as administrator (Win + X-> Command line (administrator)).
cd C:\platform-tools
fastboot devices
fastboot flashing unlock
After the commands have been executed, the device will reboot and will be reset to factory settings.
We go to the settings and check
Bootloader is unlocked.
Source
Click to expand...
Click to collapse
Hey,
I follow the instructions but when reboot after going back to Android 12 stable my bootloader still is locked. Could you help me please?
I unlocked the bootloader on my AT&T Pixel 4XL in March 2022 right after I called AT&T's (actually Asurion) support to have them carrier unlock the device. For the record, I was using the esim for my AT&T service and I had unlocked the developer options previously, but OEM unlocking was greyed out. I put in another carrier's SIM (Google Fi in case it makes a difference) and saw that it was picking up an LTE signal. I didn't have service with Fi, just a card kit I'd picked up for $2 on Amazon. I rebooted the device, checked the developer options and saw that OEM unlock was no longer greyed out. I activated it and rebooted fully back to system. Then I rebooted to the bootloader and "fastboot oem unlock"ed it. Fastboot mode shows the device state as "unlocked" in red. I was as surprised as anyone as I'd gotten the coral as a replacement from Asurion for my LG v20 two years ago and I wasn't sure the device could be bootloader unlocked.
That was lucky!
I have a 4XL which I bought second-hand. It was cheap, 180$ and the only problem was that it was locked to AT&T, and unfortunately the previous owner didn't pay the phone yet, so I am working on a method to unlock the bootloader of a locked phone.

Categories

Resources