Related
How to safely unlock the bootloader P9 ? Please for detailed instructions. Thanks.
I think people used DC unlocker..
So has anyone tried to relock the bootloader? It would be nice to know if there is a method to relock that can't be detected, so our warranty says intact. I've read that dc unlocker can do that but I've never seen confirmation.
clouds5 said:
So has anyone tried to relock the bootloader? It would be nice to know if there is a method to relock that can't be detected, so our warranty says intact. I've read that dc unlocker can do that but I've never seen confirmation.
Click to expand...
Click to collapse
I've just checked too on dc unlocker site and P9 results like the last added supported model with this features:
- direct unlock
- read bootloader code
- read unlock codes
- unlock FRP
So I just unlocked my Bootloader successfully with the DC unlocker tool and wanted to share the process with you guys. If you live in Europe and tried to get your unlock code directly from Huawei you may have run into some problems but this method works. My P9 is a EVA-L09 (europe single sim version).
Do this at your own risk.
You need this tool: https://www.dc-unlocker.com/ I did it with the most recent version as of now (V1.00.1290) which is the first that supports the P9.
Basically follow the instructions in the tool to get your device connected, it's straightforward. Then you need to make an account and _buy_ credits to read your unlock code. You need 4 credits so it will cost you 4 euro. This sucks, but it's no scam or anything. It works (as I just did it).
Just log in through the tool with the data provided after making an account and go to Unlocking -->"read bootloader code". Push the button and after a few secs your code appears. WRITE IT DOWN AND/OR COPY IT TO A .txt or something
[e] important: before you unlock/relock your phone or flash a custom recovery make sure that you go to developer settings and tick "enable OEM unlock". Missing this could lead to brick in certain situations, for more info read this article and do additional research.
Once you have the code you can start the unlocking process. This is the same for people that got their unlock code through other methods.
-Disconnect and power off your P9.
-Push volume down and connect it to your Computer, when the screen turns on you are in fastboot mode.
-Open any ADB/Fastboot tool (http://forum.xda-developers.com/showthread.php?t=2317790 <- i used this) and write:
"fastboot devices"
your device should be detected. Then write:
"fastboot oem unlock XXXXXXXXXXXXXXXXXXX" )X being the unlock code you got from DC unlocker)
It gives you a warning about warranty etc you have to comply and your bootloader is unlocked. As it warns you on the screen this will do a factory reset.
If you ever want to relock the bootloader put your phone in fastboot mode and type
"fastboot oem relock XXXXXXXXXXXXXXXXXX" the bootloader will be relocked but as far as we know it's detectable that it was unlocked before.
Hope this helps, cheers
clouds5 said:
So I just unlocked my Bootloader successfully with the DC unlocker tool and wanted to share the process with you guys. If you live in Europe and tried to get your unlock code directly from Huawei you may have run into some problems but this method works. My P9 is a EVA-L09 (europe single sim version).
You need this tool: https://www.dc-unlocker.com/ I did it with the most recent version as of now (V1.00.1290) which is the first that supports the P9.
Basically follow the instructions in the tool to get your device connected, it's straightforward. Then you need to make an account and _buy_ credits to read your unlock code. You need 4 credits so it will cost you 4 euro. This sucks, but it's no scam or anything. It works (as I just did it).
Just log in through the tool with the data provided after making an account and go to Unlocking -->"read bootloader code". Push the button and after a few secs your code appears. WRITE IT DOWN AND/OR COPY IT TO A .txt or something
Once you have the code you can start the unlocking process. This is the same for people that got their unlock code through other methods.
-Disconnect and power off your P9.
-Push volume down and connect it to your Computer, when the screen turns on you are in fastboot mode.
-Open any ADB/Fastboot tool (http://forum.xda-developers.com/showthread.php?t=2317790 <- i used this) and write:
"fastboot devices"
your device should be detected. Then write:
"fastboot oem unlock XXXXXXXXXXXXXXXXXXX" )X being the unlock code you got from DC unlocker)
It gives you a warning about warranty etc you have to comply and your bootloader is unlocked. As it warns you on the screen this will do a factory reset.
If you ever want to relock the bootloader put your phone in fastboot mode and type
"fastboot oem relock XXXXXXXXXXXXXXXXXX" the bootloader will be relocked but as far as we know it's detectable that it was unlocked before.
Hope this helps, cheers
Click to expand...
Click to collapse
Great to hear that I works!
Are you planning to flash twrp and root it?
Sent from my Nexus 5X
220volt said:
Great to hear that I works!
Are you planning to flash twrp and root it?
Sent from my Nexus 5X
Click to expand...
Click to collapse
Already rooted it with the guide from the root thread here. Was quick and worked great.
clouds5 said:
So I just unlocked my Bootloader successfully with the DC unlocker tool and wanted to share the process with you guys. If you live in Europe and tried to get your unlock code directly from Huawei you may have run into some problems but this method works. My P9 is a EVA-L09 (europe single sim version).
You need this tool: https://www.dc-unlocker.com/ I did it with the most recent version as of now (V1.00.1290) which is the first that supports the P9.
Basically follow the instructions in the tool to get your device connected, it's straightforward. Then you need to make an account and _buy_ credits to read your unlock code. You need 4 credits so it will cost you 4 euro. This sucks, but it's no scam or anything. It works (as I just did it).
Just log in through the tool with the data provided after making an account and go to Unlocking -->"read bootloader code". Push the button and after a few secs your code appears. WRITE IT DOWN AND/OR COPY IT TO A .txt or something
Once you have the code you can start the unlocking process. This is the same for people that got their unlock code through other methods.
-Disconnect and power off your P9.
-Push volume down and connect it to your Computer, when the screen turns on you are in fastboot mode.
-Open any ADB/Fastboot tool (http://forum.xda-developers.com/showthread.php?t=2317790 <- i used this) and write:
"fastboot devices"
your device should be detected. Then write:
"fastboot oem unlock XXXXXXXXXXXXXXXXXXX" )X being the unlock code you got from DC unlocker)
It gives you a warning about warranty etc you have to comply and your bootloader is unlocked. As it warns you on the screen this will do a factory reset.
If you ever want to relock the bootloader put your phone in fastboot mode and type
"fastboot oem relock XXXXXXXXXXXXXXXXXX" the bootloader will be relocked but as far as we know it's detectable that it was unlocked before.
Hope this helps, cheers
Click to expand...
Click to collapse
Thanks! I just unlocked my bootloader. It didn't work at first but this was because I had forgotten to enable OEM unlock in the settings: https://www.dc-unlocker.com/enable-oem-unlock
What are the benefits of unlocking the bootloader and are there any negatives?
Sent from my EVA-AL00 using Tapatalk
Milamber said:
What are the benefits of unlocking the bootloader and are there any negatives?
Sent from my EVA-AL00 using Tapatalk
Click to expand...
Click to collapse
The phone could become less secure, however after unlocking you should be able to install a modified recovery (twrp)
Do you still get automatic updates through the phone with an unlocked boot loader? I'm keen to put an English rom on my Chinese P9
Sent from my EVA-AL00 using Tapatalk
I've tried to unlock my P9 using the DC-Unlocker method but it's just saying "FAILED (remote: password wrong)"
Any ideas?
DreamHazard said:
I've tried to unlock my P9 using the DC-Unlocker method but it's just saying "FAILED (remote: password wrong)"
Any ideas?
Click to expand...
Click to collapse
Do you get that in the DC unlocker or when you actually type the unlock command in fastboot? DC unlocker is just for reading the bootloader code not the actual unlocking. If that makes sense.
Also don't forget to "enable OEM unlock" in the dev settings.
clouds5 said:
Do you get that in the DC unlocker or when you actually type the unlock command in fastboot? DC unlocker is just for reading the bootloader code not the actual unlocking. If that makes sense.
Also don't forget to "enable OEM unlock" in the dev settings.
Click to expand...
Click to collapse
I got the codes from DC unlocker, it's the response from fastboot oem unlock <code>. DC unlocker gave me four codes, I tried all of them. OEM Unlock is enabled in settings.
I have read elsewhere that the O2 handsets are bootloader locked, but mine came from the carphone warehouse, who usually send out carrier-free handsets (thus not O2 specific). Unfortunately I don't have a microsim from another network to test this, though there doesn't seem to be any O2 branding or apps.
EDIT: I've discovered the problem, I clicked "Read unlock codes" rather than "Read bootloader code" so the codes were obviously incorrect.
So even if we use dc unlocker to unlock our bootloader they can detect it???
Veretic said:
So even if we use dc unlocker to unlock our bootloader they can detect it???
Click to expand...
Click to collapse
DC unlocker doesn't actually unlock the bootloader, it's just an alternate way to get your specific unlock code. The actual unlocking is done with a command line.
clouds5 said:
DC unlocker doesn't actually unlock the bootloader, it's just an alternate way to get your specific unlock code. The actual unlocking is done with a command line.
Click to expand...
Click to collapse
I know it doesn't unlock it and only provides an unlock code but on other huawei phones it can relock the bootloader and leave the status locked instead of relocked.
Veretic said:
I know it doesn't unlock it and only provides an unlock code but on other huawei phones it can relock the bootloader and leave the status locked instead of relocked.
Click to expand...
Click to collapse
I've searched for that myself and found a post where someone said DC unlocker can relock the bootloader leaving the status "locked" instead of "relocked". But no confirmation if that is detectable or not and it was from a different device, so no guarantees it will work for the P9... So I guess we don't have a definitive answer how this affects your warranty and it may very well depend on the country you live in, as it usually does with warranty issues.
The official Huawei page states the following (link):
"Huawei will record your unlock request information; for software and hardware failures arising as a result of unlocking the bootloader, Huawei repair centers can provide repair services charged at the standard rate for repair work outside the scope of the warranty."
The way I interpret this it means that you only lose warranty if the damage is directly related to something you did by having the bootloader unlocked. If you have an unlocked bootloader and the camera module dies within the warranty period you should be fine unless they can prove that it died because of something you flashed through the unlocked bootloader. But as I said I think this is handled case by case and depends on your local warranty law.
I have an o2 P( bought in o2 store, used DC unlocker after some faffing with installing hisuite before DC unlocker would recognise my phone.
Got the unlock code unlocked bootloader, and restored 'most' of my data via the hisuite backup feature
I'm not doing anything else with it until I have all relevant files to recover from a sketchy flash or whatnot
clouds5 said:
So I just unlocked my Bootloader successfully with the DC unlocker tool and wanted to share the process with you guys. If you live in Europe and tried to get your unlock code directly from Huawei you may have run into some problems but this method works. My P9 is a EVA-L09 (europe single sim version).
Do this at your own risk.
You need this tool: https://www.dc-unlocker.com/ I did it with the most recent version as of now (V1.00.1290) which is the first that supports the P9.
Basically follow the instructions in the tool to get your device connected, it's straightforward. Then you need to make an account and _buy_ credits to read your unlock code. You need 4 credits so it will cost you 4 euro. This sucks, but it's no scam or anything. It works (as I just did it).
Just log in through the tool with the data provided after making an account and go to Unlocking -->"read bootloader code". Push the button and after a few secs your code appears. WRITE IT DOWN AND/OR COPY IT TO A .txt or something
[e] important: before you unlock/relock your phone or flash a custom recovery make sure that you go to developer settings and tick "enable OEM unlock". Missing this could lead to brick in certain situations, for more info read this article and do additional research.
Once you have the code you can start the unlocking process. This is the same for people that got their unlock code through other methods.
-Disconnect and power off your P9.
-Push volume down and connect it to your Computer, when the screen turns on you are in fastboot mode.
-Open any ADB/Fastboot tool (http://forum.xda-developers.com/showthread.php?t=2317790 <- i used this) and write:
"fastboot devices"
your device should be detected. Then write:
"fastboot oem unlock XXXXXXXXXXXXXXXXXXX" )X being the unlock code you got from DC unlocker)
It gives you a warning about warranty etc you have to comply and your bootloader is unlocked. As it warns you on the screen this will do a factory reset.
If you ever want to relock the bootloader put your phone in fastboot mode and type
"fastboot oem relock XXXXXXXXXXXXXXXXXX" the bootloader will be relocked but as far as we know it's detectable that it was unlocked before.
Hope this helps, cheers
Click to expand...
Click to collapse
I think this might be redundant, yesterday I contacted Huawei through their customer support form on their international page with my IMEI and S/No, and about 10hrs later got my bootloader unlock code with all the usual warnings about the warranty. I'm currently at work so I can't yet confirm if the code works or not but will update this post in a few hrs when I get home.
I was genuinely surprised that the person who contacted me via email was actually a finnish customer service agent, not some google translate-bot or anything.
My device is EVA-L09 and I live in Finland.
I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.
Do you use "fastboot flashing unlock_bootloader"? Do you have actual platform-tools?
# fastboot --version
fastboot version 27.0.0-4455170
depii said:
Do you use "fastboot flashing unlock_bootloader"? Do you have actual platform-tools?
# fastboot --version
fastboot version 27.0.0-4455170
Click to expand...
Click to collapse
Once it boots into fastboot, I enter "fastboot flashing unlock"
I have that same version of fastboot.
Is "Device State" locked or unlocked on bootloader screen? In Developer Options > OEM Unlocking for me is a second line with text: "bootloader already unlocked". What is yours?
Edit: Did you enable OEM Unlocking before fastboot flashing unlock?
depii said:
Is "Device State" locked or unlocked on bootloader screen? In Developer Options > OEM Unlocking for me is a second line with text: "bootloader already unlocked". What is yours?
Edit: Did you enable OEM Unlocking before fastboot flashing unlock?
Click to expand...
Click to collapse
Device state is locked
There's nothing under OEM unlocking saying that the bootloader is already unlocked.
Yes, I have enabled unlocking before booting into fastboot. I've done it five times now.
What's odd is if I use the unlock_critical command, I get "FAILED (remote: Device already : unlocked!)"
geicogecko said:
I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.
Click to expand...
Click to collapse
Facing the same issue in INDIA. Are you sure RMA is the only option ? I was hoping for Jan 2018 Security patch ! Worth to wait or RMA ?
rohanhole said:
Facing the same issue in INDIA. Are you sure RMA is the only option ? I was hoping for Jan 2018 Security patch ! Worth to wait or RMA ?
Click to expand...
Click to collapse
Nothing I did fixed the problem. You can keep fighting with it and hope it eventually works, and possibly end up with a permanently locked bootloader.
geicogecko said:
Nothing I did fixed the problem. You can keep fighting with it and hope it eventually works, and possibly end up with a permanently locked bootloader.
Click to expand...
Click to collapse
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?
rohanhole said:
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?
Click to expand...
Click to collapse
Hello All ,
I have succefully unlocked the bootloader with following command !!!!!! Pixel 2 128 GB
C:\platform-tools>fastboot flashing lock_critical
...
OKAY [ 9.054s]
finished. total time: 9.056s
I dont know but after reading latest post on XDA and other Android related tech sites ,
I performed the above command and it worked for me ! I was about to RMA but this is what i wanted ! so no need to RMA now.
Again not to confuse with VERIZON variant , as my device was Google store unlocked In INDIA ! Strange but worked.
rohanhole said:
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?
Click to expand...
Click to collapse
I first updated to 8.1 OTA, then unlocked.
rohanhole said:
Hello All ,
I have succefully unlocked the bootloader with following command !!!!!! Pixel 2 128 GB
C:\platform-tools>fastboot flashing lock_critical
...
OKAY [ 9.054s]
finished. total time: 9.056s
I dont know but after reading latest post on XDA and other Android related tech sites ,
I performed the above command and it worked for me ! I was about to RMA but this is what i wanted ! so no need to RMA now.
Again not to confuse with VERIZON variant , as my device was Google store unlocked In INDIA ! Strange but worked.
Click to expand...
Click to collapse
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.
geicogecko said:
I first updated to 8.1 OTA, then unlocked.
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.
Click to expand...
Click to collapse
Read the other threads or check the xda news portal. This command actually unlocks the pixel 2 not XL variant.
geicogecko said:
I first updated to 8.1 OTA, then unlocked.
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.
Click to expand...
Click to collapse
I really don't have any clue why it worked ! After reading latest post I executed the above command in leap of faith and it really worked ! Finally unlocked bootloader on pixel 2 128 Gb. But its strange as I don't have Verizon model , as I purchased the device from official google store in India ( flipkart.com )
Here is the XDA post : https://www.xda-developers.com/verizon-google-pixel-2-bootloader-unlock/
geicogecko said:
I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.
Click to expand...
Click to collapse
SkipSoft Download Page | SkipSoft.net
skipsoft.net
First of all: Is it normal for my OEM unlocking to be greyed out with status "Bootloader already unlocked" on this device after unlocking the bootloader? On my pixel2xl the option is not greyed out even after unlocking the bootloader, so I'm confused.
More info: Trying to set up a Pixel 2 64GB unlocked version from google store, it came on 8.0 November update. I was able to unlock the bootloader, had trouble flashing to the latest February 8.1 straight from November 8.0, but was able to boot back into 8.0 and let it do the OTA to 8.1 February update successfully. I factory reset after updating to 8.1 February update and have been connected to wifi and have a sim card in while setting up (if that matters), and now the option for OEM unlocking is still greyed out with status "Bootloader already unlocked". Not that it really matters I guess since I want the bootloader to remain unlocked, but the fact that it's different on my 2 pixel devices makes me think I did something wrong somewhere or misconfigured something.
KnifeSkills said:
First of all: Is it normal for my OEM unlocking to be greyed out with status "Bootloader already unlocked" on this device after unlocking the bootloader? On my pixel2xl the option is not greyed out even after unlocking the bootloader, so I'm confused.
More info: Trying to set up a Pixel 2 64GB unlocked version from google store, it came on 8.0 November update. I was able to unlock the bootloader, had trouble flashing to the latest February 8.1 straight from November 8.0, but was able to boot back into 8.0 and let it do the OTA to 8.1 February update successfully. I factory reset after updating to 8.1 February update and have been connected to wifi and have a sim card in while setting up (if that matters), and now the option for OEM unlocking is still greyed out with status "Bootloader already unlocked". Not that it really matters I guess since I want the bootloader to remain unlocked, but the fact that it's different on my 2 pixel devices makes me think I did something wrong somewhere or misconfigured something.
Click to expand...
Click to collapse
Dont worry, its normal.
shagbag913 said:
Dont worry, its normal.
Click to expand...
Click to collapse
But what if I need to re-lock my bootloader? Don't I need this switch available?
lucasdeeiroz said:
But what if I need to re-lock my bootloader? Don't I need this switch available?
Click to expand...
Click to collapse
Nope.
To lock the bootloader, connect via USB to a computer that has the SDK Platform Tools on it, and reboot to the bootloader.
Open a command prompt in your "platform tools" folder and type:
Code:
fastboot flashing lock
This will lock your bootloader and wipe the device. I believe this also sets the "get_unlock_ability" flag to 0 (which the OEM unlock switch corresponds to).
To explain this a little more simply:
There are three components in play here.
First, there is a firmware flag that determines whether the device can be unlocked at all: "ro.oem_unlock_supported". If this is set to 0, OEM Unlocking will be greyed out and unlocking is not possible.
Second, there is another firmware flag that determines whether the bootloader can be unlocked:
"get_unlock_ability". This corresponds to the OEM Unlocking switch - off is 0, on is 1. If the switch is on/flag is set to 1, the bootloader may be unlocked.
Third, there's the bootloader itself. If the "get_unlock_ability" flag is set to 0, the bootloader will refuse unlock commands. If the bootloader is already unlocked, it will override the flag.
Hope this helps and makes sense!
KnifeSkills said:
First of all: Is it normal for my OEM unlocking to be greyed out with status "Bootloader already unlocked" on this device after unlocking the bootloader? On my pixel2xl the option is not greyed out even after unlocking the bootloader, so I'm confused.
More info: Trying to set up a Pixel 2 64GB unlocked version from google store, it came on 8.0 November update. I was able to unlock the bootloader, had trouble flashing to the latest February 8.1 straight from November 8.0, but was able to boot back into 8.0 and let it do the OTA to 8.1 February update successfully. I factory reset after updating to 8.1 February update and have been connected to wifi and have a sim card in while setting up (if that matters), and now the option for OEM unlocking is still greyed out with status "Bootloader already unlocked". Not that it really matters I guess since I want the bootloader to remain unlocked, but the fact that it's different on my 2 pixel devices makes me think I did something wrong somewhere or misconfigured something.
Click to expand...
Click to collapse
SkipSoft Download Page | SkipSoft.net
skipsoft.net
i came here just to say that i love you, great tips
Hi guys,
Man oh man this phone...
So basically I'm trying to unlock my bootloader without waiting the 7 days, since I simply don't trust this phone to give me the OEM Unlock option after 7 days...
Before I decided to unlock my bootloader I had been using this phone for about 2 months like normal, sure I uninstalled a ton of bloatware and system apps that I didn't need which MIGHT have been the reason it didn't show the OEM Unlock after months, but the battery life was amazing.
But recently I've been considering rooting my phone, and before I started factory resetting and trying many different things to show the OEM Unlock option, keep in mind I've bee using this phone normally for a couple months, I checked the developer options and not a surprise, OEM Unlock wasn't there.
So ever since, I've tried sooo many things to show the OEM Unlock:
( I reflashed the stock firmware with Odin in between all these methods I've tried )
Also before I list everything I've tried heres the full specs of this phone and the drivers I've installed on my Windows 10
Samsung Galaxy A32 5G (SM-A326U)
T-Mobile, MTK, Network locked, No SIM, NOT Snapdragon
Drivers I've installed on my PC: Google USB Driver, ADB Interface, Samsung Android USB Driver, MTK Driver, USBDk and a few more can't remember the names...
1. Changing date, checking for an update and changing the date back, tried restarting the phone in between, tried turning wifi on and off in between.
2. Combination firmware, got unauthorized error on the download mode screen talking about the pit file.
3. Tried running:
adb reboot bootloader
fastboot devices (It successfully recognized my phone)
fastboot oem unlock: Unknown command
Didn't even run the command...
4. Since its a MTK CPU I had hope for mtkclient https://github.com/bkerler/mtkclient
It just kept asking to connect my phone, tried connecting with recovery mode, download mode and fastboot mode, none of them were recognized
The reason I need a quick way to unlock the bootloader, is cause I will be doing stuff with this phone that might result in me having to reflash the firmware which I can't risk it relocking and have to wait 7 days each time something goes wrong.
I heard that T-Mobile phones bootloader's are impossible to unlock, someone please tell me that is not true...
So basically,
Is there any way to unlock the bootloader? If not why and if yeah, what have I been doing wrong and how?
Thanks guys
7 days what? Tmo A326U doesnt have the option to unlock the bootloader, you need to pay the people here that provide the service. They are the only ones that seemingly know how to get it unlocked, and I can vouch for it.
Seriously... So there's no way to unlock for free, or by waiting...?
Not a bootloader unlock. Its not just Tmo that are locking these down tighter.
You can unlock it for free if you can figure out whatever they do ;-)
Nah idc about a network unlock since I don't have service for this phone, I just wanna know if its possible to unlock the bootloader... I've tried everything
Who is talking about a network unlock?
TimmyP said:
Who is talking about a network unlock?
Click to expand...
Click to collapse
You said not a "bootloader unlock" so I was assuming you're talking about network unlock... Sorry, but should I just give up, there's seemingly NO WAYY to unlock the bootloader of a T-Sh*t phone.
Oh just misunderstanding my bad. I meant you cant wait for a bootloader unlock, but you can wait and maybe they would carrier unlock it later... but thats not what you want anyways.
TimmyP said:
Oh just misunderstanding my bad. I meant you cant wait for a bootloader unlock, but you can wait and maybe they would carrier unlock it later... but thats not what you want anyways.
Click to expand...
Click to collapse
That's kinda sad, I think I'm gonna just give up, but thanks for the information... Hopefully something happens in the future that allows it to be unlocked soon... Thanks man
I doubt they'll bring it back. OEM unlock that is. My phone is over 7 days old and I did the factory reset by holding the volume down and power buttons and then the volume up and power button and did the full factory reset. OEM unlock is still gone. Yes I got the developer options turned on. I rooted a couple of Nexus 6p's which of course are obsolete now since they were 3G and there is no backward capability. At least I got them used, replaced the batteries myself and can use them as WiFi phones with Talkatone through my WiFi. Read some blurbs about Kingo root working but I'd like to see that someone has pulled it off with the A32. Am under a 2 year obligation but I bought a second one to experiment on. I did that before I found out there was no OEM unlock. Well, if I break one, I'll have a backup. Except the phone is tied to the SIMM and I'd have to bring the backup in to have it reprogrammed.
TimmyP said:
Who is talking about a network unlock?
Click to expand...
Click to collapse
Any good service to network unlock SM-A236U or U1. Flashed XAA t no avail the Carrier_ID stays at DSH...
iabhua said:
Any good service to network unlock SM-A236U or U1. Flashed XAA t no avail the Carrier_ID stays at DSH...
Click to expand...
Click to collapse
I am working on unlock for it but I need root or a device on low security update. I am almost close to an solution if your device security patch is low please let me know
TimmyP said:
7 days what? Tmo A326U doesnt have the option to unlock the bootloader, you need to pay the people here that provide the service. They are the only ones that seemingly know how to get it unlocked, and I can vouch for it.
Click to expand...
Click to collapse
Do you have any device with an unlock bootloader or unlock? I am trying to get a ram dimp for days nobody have an device.
andioshelp said:
I am working on unlock for it but I need root or a device on low security update. I am almost close to an solution if your device security patch is low please let me know
Click to expand...
Click to collapse
I have two SM-A236U’s but unfortunately one has binary 6 FW and the other binary 7.
1.fuxk_ said:
Hi guys,
Man oh man this phone...
So basically I'm trying to unlock my bootloader without waiting the 7 days, since I simply don't trust this phone to give me the OEM Unlock option after 7 days...
Before I decided to unlock my bootloader I had been using this phone for about 2 months like normal, sure I uninstalled a ton of bloatware and system apps that I didn't need which MIGHT have been the reason it didn't show the OEM Unlock after months, but the battery life was amazing.
But recently I've been considering rooting my phone, and before I started factory resetting and trying many different things to show the OEM Unlock option, keep in mind I've bee using this phone normally for a couple months, I checked the developer options and not a surprise, OEM Unlock wasn't there.
So ever since, I've tried sooo many things to show the OEM Unlock:
( I reflashed the stock firmware with Odin in between all these methods I've tried )
Also before I list everything I've tried heres the full specs of this phone and the drivers I've installed on my Windows 10
Samsung Galaxy A32 5G (SM-A326U)
T-Mobile, MTK, Network locked, No SIM, NOT Snapdragon
Drivers I've installed on my PC: Google USB Driver, ADB Interface, Samsung Android USB Driver, MTK Driver, USBDk and a few more can't remember the names...
1. Changing date, checking for an update and changing the date back, tried restarting the phone in between, tried turning wifi on and off in between.
2. Combination firmware, got unauthorized error on the download mode screen talking about the pit file.
3. Tried running:
adb reboot bootloader
fastboot devices (It successfully recognized my phone)
fastboot oem unlock: Unknown command
Didn't even run the command...
4. Since its a MTK CPU I had hope for mtkclient https://github.com/bkerler/mtkclient
It just kept asking to connect my phone, tried connecting with recovery mode, download mode and fastboot mode, none of them were recognized
The reason I need a quick way to unlock the bootloader, is cause I will be doing stuff with this phone that might result in me having to reflash the firmware which I can't risk it relocking and have to wait 7 days each time something goes wrong.
I heard that T-Mobile phones bootloader's are impossible to unlock, someone please tell me that is not true...
So basically,
Is there any way to unlock the bootloader? If not why and if yeah, what have I been doing wrong and how?
Thanks guys
Click to expand...
Click to collapse
There was a similar procedure to unlock bootloader on a samsung mtk (A125U) same carrier as yours (T-Mobile TMB and the same applies to MetroPCS TMB) basicaly, you had to flash BL files from the A125W (canadian version) then unlocking bootloader using testpoint (bootrom mode) then using any paid or free app (in my case i use a paid one because i run a repair shop). even if you unlock bootloader using paid tools, it gets locked again when it turns on. (i tested it without flashing BL files)
sadly, i dont have a A326U lying arround to test said procedure.
1.fuxk_ said:
Hi guys,
Man oh man this phone...
So basically I'm trying to unlock my bootloader without waiting the 7 days, since I simply don't trust this phone to give me the OEM Unlock option after 7 days...
Before I decided to unlock my bootloader I had been using this phone for about 2 months like normal, sure I uninstalled a ton of bloatware and system apps that I didn't need which MIGHT have been the reason it didn't show the OEM Unlock after months, but the battery life was amazing.
But recently I've been considering rooting my phone, and before I started factory resetting and trying many different things to show the OEM Unlock option, keep in mind I've bee using this phone normally for a couple months, I checked the developer options and not a surprise, OEM Unlock wasn't there.
So ever since, I've tried sooo many things to show the OEM Unlock:
( I reflashed the stock firmware with Odin in between all these methods I've tried )
Also before I list everything I've tried heres the full specs of this phone and the drivers I've installed on my Windows 10
Samsung Galaxy A32 5G (SM-A326U)
T-Mobile, MTK, Network locked, No SIM, NOT Snapdragon
Drivers I've installed on my PC: Google USB Driver, ADB Interface, Samsung Android USB Driver, MTK Driver, USBDk and a few more can't remember the names...
1. Changing date, checking for an update and changing the date back, tried restarting the phone in between, tried turning wifi on and off in between.
2. Combination firmware, got unauthorized error on the download mode screen talking about the pit file.
3. Tried running:
adb reboot bootloader
fastboot devices (It successfully recognized my phone)
fastboot oem unlock: Unknown command
Didn't even run the command...
4. Since its a MTK CPU I had hope for mtkclient https://github.com/bkerler/mtkclient
It just kept asking to connect my phone, tried connecting with recovery mode, download mode and fastboot mode, none of them were recognized
The reason I need a quick way to unlock the bootloader, is cause I will be doing stuff with this phone that might result in me having to reflash the firmware which I can't risk it relocking and have to wait 7 days each time something goes wrong.
I heard that T-Mobile phones bootloader's are impossible to unlock, someone please tell me that is not true...
So basically,
Is there any way to unlock the bootloader? If not why and if yeah, what have I been doing wrong and how?
Thanks guys
Click to expand...
Click to collapse
Did you tried, instead of fastboot oem unlock, fastboot flashing unlock
DjoFight said:
Did you tried, instead of fastboot oem unlock, fastboot flashing unlock
Click to expand...
Click to collapse
In case people need the procedures for those processes, I wrote this up recently to help others do it easier than it was for me to figure out.
How to un-freeze an unresponsive Samsung Galaxy A32 5G with reboot, reset, factory reset, odin mode, download mode, android recovery mode & debug mode
Has any one made any progress regarding the missing oem unlock? I know what parameters to add to our kernel v1 to v3 during building to enable oem unlock and add access to fastbootd. Because of project treble our options have changed.
Sources:
Moving Fastboot to Userspace | Android Open Source Project
source.android.com
Locking/Unlocking the Bootloader | Android Open Source Project
source.android.com
Sign in
DOCUMENTATION
Docs
More
Getting Started
Security
Core Topics
Compatibility
Android Devices
Reference
GO TO CODE ➚
Overview
Architecture
Overview
Hardware Abstraction Layer (HAL)
Kernel
HIDL (General)
HIDL (C++)
HIDL (Java)
Configuration
Device Tree Overlays
Vendor NDK
Vendor Interface Object
AIDL
Bootloader
Overview
Boot Reason
Boot Image Header
Implementing Bootconfig
Recovery Images
DTB Images
Supporting OTA Updates
Locking and Unlocking the Bootloader
Version Information in AVB Properties
Fastboot in Userspace
Partitions
Audio
Camera
Connectivity
Data
Display
Fonts
Graphics
Interaction
Media
Performance
Permissions
Power
Runtime
Settings
Storage
Virtualization
Tests
Updates
AOSP
Docs
Core Topics
Was this helpful?
Locking/Unlocking the Bootloaderbookmark_border
On this page
Unlocking the bootloader
Locking the bootloader
Setting lock/unlock properties
Protecting critical sections
By default, most Android devices ship with a locked bootloader, meaning that users can't flash the bootloader or device partitions. If needed, you (and device users with Developer options enabled) can unlock the bootloader to flash new images.
Unlocking the bootloaderTo unlock the bootloader and enable partitions to be reflashed, run the fastboot flashing unlock command on the device. After setting, the unlock mode persists across reboots.
Devices should deny the fastboot flashing unlock command unless the get_unlock_ability is set to 1. If set to 0, the user needs to boot to the home screen, open the Settings > System > Developer options menu and enable the OEM unlocking option (which sets the get_unlock_ability to 1). After setting, this mode persists across reboots and factory data resets.
When the fastboot flashing unlock command is sent, the device should prompt users to warn them that they might encounter problems with unofficial images. After the user acknowledges the warning, the device should perform a factory data reset to prevent unauthorized data access. The bootloader should reset the device even if it can't reformat it properly. Only after a reset can the persistent flag be set so that the device can be reflashed.
All RAM not already overwritten should be reset during the fastboot flashing unlock process. This measure prevents attacks that read leftover RAM contents from the previous boot. Similarly, unlocked devices should clear RAM at every boot (unless this creates an unacceptable delay), but should leave the region used for the kernel's ramoops.
Locking the bootloaderTo lock the bootloader and reset the device, run the fastboot flashing lock command on the device. Devices intended for retail should be shipped in the locked state (with get_unlock_ability returning 0) to ensure that attackers can't compromise the device by installing a new system or boot image.
Setting lock/unlock propertiesThe ro.oem_unlock_supported property should be set at build time based on whether the device supports flashing unlock.
If the device supports flashing unlock, set ro.oem_unlock_supported to 1.
If the device doesn't support flashing unlock, set ro.oem_unlock_supported to 0.
If the device supports flashing unlock, then the bootloader should indicate the lock status by setting the kernel command line variable androidboot.flash.locked to 1 if locked or to 0 if unlocked. This variable must be set in bootconfig instead of in the kernel command line in Android 12.
For devices that support dm-verity, use ro.boot.verifiedbootstate to set the value of ro.boot.flash.locked to 0; this unlocks the bootloader if the verified boot state is orange.
I have the A32 5G (64Gb Int. Stg.) & it's the Tracfone Only version or SM-S326DL. After recently receiving word that Android 13 was awaiting us, I quickly allowed my device to receive this very kool OTA operating system update. I mention this, because a week earlier I received an email from my prepaid wireless provider instructing me in detail how to manually unlock my A32 5G handset. So, to be clear, Tracfone notified me in their email how to unlock my device, but whan
this happens to often, to write this off as an app-mishap xda...why?!
(pls. explain this to me, what is really going on)?
evnStevn said:
I have the A32 5G (64Gb Int. Stg.) & it's the Tracfone Only version or SM-S326DL. After recently receiving word that Android 13 was awaiting us, I quickly allowed my device to receive this very kool OTA operating system update. I mention this, because a week earlier I received an email from my prepaid wireless provider instructing me in detail how to manually unlock my A32 5G handset. So, to be clear, Tracfone notified me in their email how to unlock my device, but whan
this happens to often, to write this off as an app-mishap xda...why?!
(pls. explain this to me, what is really going on)?
Click to expand...
Click to collapse
I'm wondering too. Could you please pm me what you were trying to post?
Help! I got the unlocked version and i updated it to android 11 and now oem unlock is greyed out. It says connect to internet or contact carrier and even though the internet is connected it is still greyed out someone please help me
smartasiankid said:
Help! I got the unlocked version and i updated it to android 11 and now oem unlock is greyed out. It says connect to internet or contact carrier and even though the internet is connected it is still greyed out someone please help me
Click to expand...
Click to collapse
Why is OEM Unlocking greyed out?
In theory, because you are already unlocked.
This happened to me flashing the stock 11 image over a DIY lineageos build (with the bootloader unlocked). The OEM unlock was in the "allow" position before flashing the stock image but, while running stock 11, I oberved it in the greyout "deny" position with text below it saying the the bootloader was unlocked.
After flashing lineageos, relocking my bootloader (this is a custom lineageos build that allows relocking), I could then toggle the allow OEM unlock back to the "allow" position.
Given that experience, you might be able to reboot into the bootloader, do `fastboot flashing lock` (which will wipe your data - be sure to back up before doing this), reboot and then toggle the OEM unlock to the "allow" position, and then unlock the device with `fastboot flashing unlock` (which will wipe data again). I doubt you will need any unlock code (if you have previously unlocked your device).
Note that I have NOT done this lock/OEM toggle/unlcok process with stock so proceed at your own risk.
Or you could just wait and see if moto does an update that "fixes" this behavior.
Edit: you don't say if your device was already unlocked before you updated to 11. If you never unlocked it, then just wait for a few days with your device connected to the carrier.
notmyrealhandle said:
This happened to me flashing the stock 11 image over a DIY lineageos build (with the bootloader unlocked). The OEM unlock was in the "allow" position before flashing the stock image but, while running stock 11, I oberved it in the greyout "deny" position with text below it saying the the bootloader was unlocked.
After flashing lineageos, relocking my bootloader (this is a custom lineageos build that allows relocking), I could then toggle the allow OEM unlock back to the "allow" position.
Given that experience, you might be able to reboot into the bootloader, do `fastboot flashing lock` (which will wipe your data - be sure to back up before doing this), reboot and then toggle the OEM unlock to the "allow" position, and then unlock the device with `fastboot flashing unlock` (which will wipe data again). I doubt you will need any unlock code (if you have previously unlocked your device).
Note that I have NOT done this lock/OEM toggle/unlcok process with stock so proceed at your own risk.
Or you could just wait and see if moto does an update that "fixes" this behavior.
Edit: you don't say if your device was already unlocked before you updated to 11. If you never unlocked it, then just wait for a few days with your device connected to the carrier.
Click to expand...
Click to collapse
i unlocked it on 10, got the retus 11 update, then locked it on 11. and now its greyed out
smartasiankid said:
i unlocked it on 10, got the retus 11 update, then locked it on 11. and now its greyed out
Click to expand...
Click to collapse
I'm not sure then.
If I was in your situation and I didn't mind wiping my data, I'd probably try booting into the bootloader and trying `fastboot flashing unlock` just to see what happens. If this command works, it will wipe your data so be sure about your backups. If it does unlock, you could try rebooting, check the OEM lock (I expect it will still be greyed out with an unlocked bootloader), and then relock and check again. Regardless if you can unlock inspite of the OEM toggle you shouldn't have much to worry about (at least until the next update).
If this doesn't work then I'd just wait a week or so. Alternatively, you could try the moto site, request your unlock key (again) and then wait a few days. It would be silly if this works, but maybe moto just needs to send a reminder to your device to enable the OEM unlocking toggle.
If none of this works, then I'd try posting to the moto official forums.
HTH
Never mind guys!! Just wait three maybe four days and it will automatically be toggle able again!! Thanks to all of those who tried to help me out!
Also a side note: to those of you who are looking to update to android 11, dont because you will not be able to change your preferred network type unlike on android 10 where you could.
smartasiankid said:
Also a side note: to those of you who are looking to update to android 11, dont because you will not be able to change your preferred network type unlike on android 10 where you could.
Click to expand...
Click to collapse
Click phone dialer
Dial. *#*#4636#*#*
A diagnostics menu will show
Choose phone information
Preferred network is in there
Default is the global setting
If your not sure what your doing, then don't change anything.
MrCamby said:
Click phone dialer
Dial. *#*#4636#*#*
A diagnostics menu will show
Choose phone information
Preferred network is in there
Default is the global setting
If your not sure what your doing, then don't change anything.
Click to expand...
Click to collapse
it is greyed out for me. i am on at&t network. it has been greyed out ever since android 11. not sure why that is happening.