Hi there:
I’ve got a second-hand Pixel 1 last week, I unlocked, installed TWRP and rooted yesterday, but I unrooted today because some reasons.
I did a wrong decision, I erased the phone by System Settings, and locked it.
After I locked it, when I boot it, it only have Google logo flash for about 0.1second then gone. I tried to flash the factory images from Google, but it requires unlock to flash it.
I even can’t unlock it now because I can’t get into the System to turn on “Allow unlock OEM loader”, so it got failed. I used fastboot OEM unlock and fast flashing unlock, they both doesn’t work.
I don’t really want to send the phone back to Google US because I doesn’t live in America, so it’s not really easy and really expensive to send it, and I also really need this phone because the battery of my old phone is almost dead. And the Google Support Team in my country/region says that I can’t send to the repair center locally because they only accept Pixel 3/3XL/3a/3aXL/4/4XL
Thanks the suggestions from you guys!
I have a similar issue.
I unlocked the bootloader via ADB but I couldn't even get a copy of TWRP to work at all. The phone also eventually stopped working on the stock install too but taking the option it presented of doing a full wipe and reset fixed at least THAT part.
Still can't get TWRP or Lineage up on it :/
Reboot to fastboot mode and flash stock recovery image (according to your os version).
OG Pixel from Verizon, had it for years, battery has been really ****ty lately. So I had to send my phone in to get a new battery, and the cost was similar to go thru google store, so I did. Wiped the phone, restored to stock android, but left bootloader unlocked. Got the phone back today and version of android was downgraded and bootloader was locked.
How ****ed am I and what are my recourses? Tried google support, they're nearly useless.
If you never booted the device yet you can try "fastboot flashing unlock" and it will just re-unlock. Other than that I don't think you will ever see a unlock status on that phone. This is why I do my repairs myself.
Fastboot flashing unlock was unsuccessful, but I suspect that was because the phone was booted up for "troubleshooting" with Google "support."
I assume then there's no way to return it to the post-flash pre-boot state without some closely guarded hardware and software?
Before updating in any way... Search Verizon unlock Pixel and see if that process will unlock. If you allow update past a certain level stuck with no options then if Verizon locked.
Oh, would never allow an update. I'm not crazy. Tried the unlock method with uninstalling the phone app before you get internet access the day I got it, still no dice. Thanks tho.
I just did a credit card chargeback as they sent me back my device in an unusable condition and refused to compensate for it. We'll see how it shakes out in a few weeks probably. Bought a refurb Pixel 3 in the meantime and it was already unlocked, so all is well.
Thanks for the replies though.
-N
n8lee said:
Fastboot flashing unlock was unsuccessful, but I suspect that was because the phone was booted up for "troubleshooting" with Google "support."
I assume then there's no way to return it to the post-flash pre-boot state without some closely guarded hardware and software?
Click to expand...
Click to collapse
Can you tell me what security patch you are on? If you are somewhere around Android 9 patch (potentially Android 10 early patches) you can re-unlock. If you try ticking the OEM unlock option in Dev options or if i heard correctly the phone wont boot? If you know your exact version you can try flashing it through recovery, or trying "fastboot unlock" after ticking the oem unlock. Also remember those old workarounds of removing android.phone and such? Yeah try those. Good luck. We'll try and get you unlocked again.
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?
HHello, I wanted to consult something before getting into a problem. I have the moto g100 with the challenge channel, since the Android 12 ota did not come out for this channel, I decided to install the Android 12 retail ota, Everything worked correctly, but now I want to install my original firmware which is RETAR and block the bootloader, so my question is the following, can I flash my original firmware and lock the bootloader?.
Yes if you flash ORGINAL ROM (Android Version) for your device you can LOCK bootloader for your device.
Lock the bootloader at your own risk, this forum has a thread full of people who have bricked their device after relocking.
Phone wouldn't boot into the system after bootloader locking back...
I wanted to help someone whose phone wouldn't boot into the system after bootloader locking back, phone hangs on a red warning. And in the process of experimenting myself got confused and got into the same situation. Unlocking the bootloader...
forum.xda-developers.com
The stock roms found on lolinet won't boot after relocking and you'll loose the ability to flash anything else. YOU HAVE BEEN WARNED! Also, you can't downgrade the bootloader. What this means is that if you flash older Android 11 stock image it may result in bootloop.
I have a G8 doha that was hard bricked a few years ago.. It did not show up in device manger at all, no matter how i tried. Not even the Qualcomm mode. This did happen after locking bootloader or change slot A/B. (Don't remember, sorry). The phone was totally dead, so it was just "archieved for later use".. Then one month ago i found a description on how to wake it up to qualcomm mode by shorting two points on pcb. I tried, and it did work. Phone showed up in device manager, and i flashed blankflash. After that i flashed stock rom. Phone is now working again. I had to do several tries to get it up running. The description on how to do it was not accurate, but i found a sequence to start it. Unfortunately i don't remember exactly. It is something with pushing/holding a button when connecting USB or shorting points on pcb.. Youtube link show how to do it..
GT
Somebody try relock bootloader on g100 and have succes ? I back to stock rom with Rescue and Smart Assistant tools but I am slightly afraid that the phone will not get up after relock the bootloader. :|
sp6ina said:
Somebody try relock bootloader on g100 and have succes ? I back to stock rom with Rescue and Smart Assistant tools but I am slightly afraid that the phone will not get up after relock the bootloader. :|
Click to expand...
Click to collapse
Yes I relock my bootloader on the Moto g100 the North American version. Right after I did it I tried to set up my phone and it wanted my last four digit Google pin code and if you didn't do it fast enough it kept rebooting so for a half hour I tried everything under the sun Google kept asking me I want to try another way. But I have two step verification on my Google account so it couldn't send me the code over my telephone number so after a couple tries using the recover my account option underneath which asked you like personal information like your name and everything it finally gave me three options of three different Google emails I have. I got my unlock code and unlock the bootloader without using a PC or a computer. I used bugjaeger. The premium app is well worth the $10 it works super easy and super efficient
sp6ina said:
Somebody try relock bootloader on g100 and have succes ? I back to stock rom with Rescue and Smart Assistant tools but I am slightly afraid that the phone will not get up after relock the bootloader. :|
Click to expand...
Click to collapse
Yes I relock my bootloader on the Moto g100 the North American version. Right after I did it I tried to set up my phone and it wanted my last four digit Google pin code and if you didn't do it fast enough it kept rebooting so for a half hour I tried everything under the sun Google kept asking me I want to try another way. But I have two step verification on my Google account so it couldn't send me the code over my telephone number so after a couple tries using the recover my account option underneath which asked you like personal information like your name and everything it finally gave me three options of three different Google emails I have. I got my unlock code and unlock the bootloader without using a PC or a computer. I used bugjaeger. The premium app is well worth the $10 it works super easy
sp6ina said:
Somebody try relock bootloader on g100 and have succes ? I back to stock rom with Rescue and Smart Assistant tools but I am slightly afraid that the phone will not get up after relock the bootloader. :|
Click to expand...
Click to collapse
Yes I relock my bootloader on the Moto g100 the North American version. Right after I did it I tried to set up my phone and it wanted my last four digit Google pin code and if you didn't do it fast enough it kept rebooting so for a half hour I tried everything under the sun Google kept asking me I want to try another way. But I have two step verification on my Google account so it couldn't send me the code over my telephone number so after a couple tries using the recover my account option underneath which asked you like personal information like your name and everything it finally gave me three options of three different Google emails I have. I got my unlock code and unlock the bootloader without using a PC or a computer. I used bugjaeger. The premium app is well worth the $10 it works super easy