Related
I have a samsung on7, SM-G600FY
I installed TWRP on it and rooted it. It worked perfectly fine, with no issues whatsoever.
However, i later disabled the OEM unlock option in developer options and a week(ish) later i switched off my phone. On trying to turn it on, i get a screen with an exclamation with the following on the top of the screen:
[WHITE] CUSTOM BINARY BLOCKED BY FRP.
[RED] SECURE FAIL : KERNEL
I think this is due to oem being locked, which is not allowing the OS to load, maybe?
Is there any way to enable it via CMD on the computer? Thanks
JimbakBoomA said:
I have a samsung on7, SM-G600FY
I installed TWRP on it and rooted it. It worked perfectly fine, with no issues whatsoever.
However, i later disabled the OEM unlock option in developer options and a week(ish) later i switched off my phone. On trying to turn it on, i get a screen with an exclamation with the following on the top of the screen:
[WHITE] CUSTOM BINARY BLOCKED BY FRP.
[RED] SECURE FAIL : KERNEL
I think this is due to oem being locked, which is not allowing the OS to load, maybe?
Is there any way to enable it via CMD on the computer? Thanks
Click to expand...
Click to collapse
i looked it further and due to the oem lock, it seems to be more hardware related than software? How can i flash/program the processor..?
Im 99% sure you need to download the firmware from sammobile and flash it with odin i don't think there are any other options other than that,
Maybe someone else could "chip in" to clarify it ?
Once you get your phone up and running again it's worth mentioning that when rooting you have to have "allow the device to be OEM unlocked" to the switched on position or you will just trip the FRP again
Hi7m3up said:
Im 99% sure you need to download the firmware from sammobile and flash it with odin i don't think there are any other options other than that,
Maybe someone else could "chip in" to clarify it ?
Once you get your phone up and running again it's worth mentioning that when rooting you have to have "allow the device to be OEM unlocked" to the switched on position or you will just trip the FRP again
Click to expand...
Click to collapse
well, i tried using odin to try and reflash the twrp again, but it failed and i got a tiny message on the phone screen that frp blocked it.
I don't believe that i will be able to flash the custom rom either, if my phone isn't allowing it...?
By the way, is it possible for you to share the link? I would like to give that a try too. Thanks!
JimbakBoomA said:
well, i tried using odin to try and reflash the twrp again, but it failed and i got a tiny message on the phone screen that frp blocked it.
I don't believe that i will be able to flash the custom rom either, if my phone isn't allowing it...?
By the way, is it possible for you to share the link? I would like to give that a try too. Thanks!
Click to expand...
Click to collapse
Go to https://www.sammobile.com download the correct firmware for your phone (important that it is the right firmware for your model) If your phone is unlocked to any network then it doesnt matter which country he firmware is from if your phone is locked to a specific carrier then you will need to make sure that the firmware you download is for your country and your carrier . You will need to register with sammobile but it's free download your firmware and flash using the most up to date odin you can get ,,you can find plenty of tutorials on how to do this using your search engine ..Dont worry if you dont manage the first go you can always try again. if you do all that right then your phone will boot normally after that . Be patient it can take 10-15 mins sometimes to flash then the first boot of your phone can take a while too..
Make sure usb debugging is on and most importantly that this time keep enable oem unlock at the switched on position (allow the device to be oem unlocked) or you will only trip the FRP and have to flash firrmware again
Your firmware package is around 2 gig so it will take a while to download and flash
make sure usb debugging is on also
I got S7 SM-G930L with a port Rom from S8 (https://forum.xda-developers.com/s7-edge/development/rom-s8-port-s7-s7-edge-ambasadii-t3619548). When I power on the phone I get a message: Custom binary blocked by FRP Lock.
I would like to get rid of the FRP Lock without losing my data.
I saw a video https://www.youtube.com/watch?v=VdAhu45UPsU According to the comments 40% lost their data and 60% didn't.
Could you please advise how to make sure that my data won't be lost?
Blackion said:
I got S7 SM-G930L with a port Rom from S8 (https://forum.xda-developers.com/s7-edge/development/rom-s8-port-s7-s7-edge-ambasadii-t3619548). When I power on the phone I get a message: Custom binary blocked by FRP Lock.
I would like to get rid of the FRP Lock without losing my data.
I saw a video https://www.youtube.com/watch?v=VdAhu45UPsU According to the comments 40% lost their data and 60% didn't.
Could you please advise how to make sure that my data won't be lost?
Click to expand...
Click to collapse
If there's an option for OEM Unlock in developer settings enable that to disable FRP
But how do I boot my phone? Now I'm getting a red message: Custom binary blocked by FRP Lock and the phone is not booting past that. It will not even let me in TWRP.
Blackion said:
But how do I boot my phone? Now I'm getting a red message: Custom binary blocked by FRP Lock and the phone is not booting past that. It will not even let me in TWRP.
Click to expand...
Click to collapse
reflash the stock fw using odin
Not sure
I was said that because I'm using a port of S8 on S7, after I'll reflash stock ROM the data might be lost due to differences of memory formats.
Is it true?
Blackion said:
I was said that because I'm using a port of S8 on S7, after I'll reflash stock ROM the data might be lost due to differences of memory formats.
Is it true?
Click to expand...
Click to collapse
If you haven't backed up your data, it will be lost.
When you get yourself back out of this mess, don't touch that OEM unlock toggle again...
Blackion said:
But how do I boot my phone? Now I'm getting a red message: Custom binary blocked by FRP Lock and the phone is not booting past that. It will not even let me in TWRP.
Click to expand...
Click to collapse
(sorry for the english but i'm italian) hi. i have the same problem, can you help me? i root my phone and after i unroot, but now the phone don't boot, it say custom binary blocked by frp, i understand that my bootloader is lock by oem, there is a way to unlock by odin or others method? i can't have access to recovery and the phone don't boot, what can i do?
corvasce03 said:
(sorry for the english but i'm italian) hi. i have the same problem, can you help me? i root my phone and after i unroot, but now the phone don't boot, it say custom binary blocked by frp, i understand that my bootloader is lock by oem, there is a way to unlock by odin or others method? i can't have access to recovery and the phone don't boot, what can i do?
Click to expand...
Click to collapse
I used smartswitch when I encountered frp lock
https://www.blogtechtips.com/2017/06/24/easily-restore-samsung-device-firmware-with-smart-switch/
1eStar said:
If you haven't backed up your data, it will be lost.
When you get yourself back out of this mess, don't touch that OEM unlock toggle again...
Click to expand...
Click to collapse
@1eStar
Firstly I have a question regarding the OEM unlock as I just came out of the FRP Lock. Do I turn on OEM unlock or does it have to be turned off? Last time I had this FRP Lock was a year ago though did it again(the mistake with the OEM unlock) as I had forgotten it(Lots of grey hair)
Just don't know if it has to be on or off?
Secondly I have managed to come out of it(so far , hopefully) without wiping data with this guide
kiwigi said:
@1eStar
Firstly I have a question regarding the OEM unlock as I just came out of the FRP Lock. Do I turn on OEM unlock or does it have to be turned off? Last time I had this FRP Lock was a year ago though did it again(the mistake with the OEM unlock) as I had forgotten it(Lots of grey hair)
Just don't know if it has to be on or off?
Secondly I have managed to come out of it(so far , hopefully) without wiping data with this guide
Click to expand...
Click to collapse
To unlock your device by frp lock you must flash the stock firmware when you are in bootloader mode you see custom binary blocked by frp,if you try to flash a random firmware(always of your device) the operation may not be a good end and device say an error with this:
Knumber) Snumber) Bnumber)
When you go to download the stock firmware you must see the "code" Of the firmware with write the same S or B number
If you Don't understand see the 10th post of this thread
https://forum.xda-developers.com/galaxy-s8+/help/custom-binary-blocked-frp-lock-regular-t3745085
corvasce03 said:
To unlock your device by frp lock you must flash the stock firmware when you are in bootloader mode you see custom binary blocked by frp,if you try to flash a random firmware(always of your device) the operation may not be a good end and device say an error with this:
Knumber) Snumber) Bnumber)
When you go to download the stock firmware you must see the "code" Of the firmware with write the same S or B number
If you Don't understand see the 10th post of this thread
https://forum.xda-developers.com/galaxy-s8+/help/custom-binary-blocked-frp-lock-regular-t3745085
Click to expand...
Click to collapse
@corvasce03
Thanks.
I think I got back allright except this here and I used exactly the same stock(file) as a year ago
Someone Help My Soul!!!
Guys, I'm scared to death on letting my phone reboot, I have been told to never let my phone restart unless my google account has been removed, can someone please explain how this FRP block really works?
Am I at risk at every given point of phone restart for real?
Cirphrank said:
Guys, I'm scared to death on letting my phone reboot, I have been told to never let my phone restart unless my google account has been removed, can someone please explain how this FRP block really works?
Am I at risk at every given point of phone restart for real?
Click to expand...
Click to collapse
It stops someone stealing your phone, wiping it, installing new firmware and using it as if it was new. If you know the gmail and password you put on the phone to access the play store then you just need to re-enter it after the phone restarts. FRP will only kick in if you have flashed new firmware to the phone.
I have a new firmware flashed on the phone.
And I'm using a new gmail with is, not some one July bro used on it.
What am I to do now? I have developer settings OEM unlock toggled on already.
Cirphrank said:
And I'm using a new gmail with is, not some one July bro used on it.
What am I to do now? I have developer settings OEM unlock toggled on already.
Click to expand...
Click to collapse
I'm not sure what you mean. If you have a Google account on the phone that you know the email and password to, then just reboot the phone. FRP lock will only activate if you flash new firmware to the phone without removing the Google account first.
Your device should only have 1 Google account registered on the device which let's you access Play store etc. If there is more than one, you need to delete the ones you don't know the email and password to.
Okay...
Oh, okay, now I am getting the rationale.
Albeit, when I flashed in the new custom firmware, it started give me the undo changes by restarting your phone notification, like it did the first time ever that I got the lock. I didn't click it, activated an app that discarded the notification rather.
Now it makes me doubt if I had really removed my mail before flashing the phone.
hey
i have got the same problem. when i deleted xposed installer, my device rebooted. every time i try to turn it on, it says in top left corner 'custom binary blocked by frp lock'. i tried 3 diff rom to flash, no succes. i tried to acces twrp (my device is rooted) but again no succes. can you guys help me?
i have a G930F
thanks.
stasikkk777 said:
i have got the same problem. when i deleted xposed installer, my device rebooted. every time i try to turn it on, it says in top left corner 'custom binary blocked by frp lock'. i tried 3 diff rom to flash, no succes. i tried to acces twrp (my device is rooted) but again no succes. can you guys help me?
i have a G930F
thanks.
Click to expand...
Click to collapse
Yeah you've messed it up by not signing out of account before unistalling xposed. When you say 3 different rom's do you mean stock or custom?
Even in this state you should be able to flash a stock rom to the device with Odin and it will ask you to type the google email and password after boot.
Always turn off FRP lock before modifying the phone, it's a really annoying feature.
I have a SM-G930VL and have seen many threads from 2016-now that have been able to flash the 930U firmware but anytime I try flashing it can not get it to boot. I'm either in a bootloop or a recovery loop where it will never boot into recovery. Any help would be appreciated! I can answer almost any questions but I don't want to list them in case anything important gets lost in the list.
damion675 said:
I have a SM-G930VL and have seen many threads from 2016-now that have been able to flash the 930U firmware but anytime I try flashing it can not get it to boot. I'm either in a bootloop or a recovery loop where it will never boot into recovery. Any help would be appreciated! I can answer almost any questions but I don't want to list them in case anything important gets lost in the list.
Click to expand...
Click to collapse
Yes but you still need the correct G930U firmware for your region/country.
Your phone needs OEM and usb debugging enabled, not essential when flashing firmware but often helps.
cooltt said:
Yes but you still need the correct G930U firmware for your region/country.
Your phone needs OEM and usb debugging enabled, not essential when flashing firmware but often helps.
Click to expand...
Click to collapse
I am flashing the version for track-fone off of sam mobile and enabled OEM and Usb debugging
You'll need a patched Odin to flash G930U on a different model, otherwise you get mismatch errors. You can get it from here: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
The OEM unlock step only applies to Exynos since that unlocks their bootloader, the toggle does nothing on USA/Snapdragon devices.
Beanvee7 said:
You'll need a patched Odin to flash G930U on a different model, otherwise you get mismatch errors. You can get it from here: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
The OEM unlock step only applies to Exynos since that unlocks their bootloader, the toggle does nothing on USA/Snapdragon devices.
Click to expand...
Click to collapse
I feel like such a dunce...........I used this one to flash the 930U onto my 930A model so I even already had it. I just thought I had already tried it. After ~8 hours of working on this, it is done. Thank you so much!! I guess if you thought you tried something always try it again to be sure haha.
So you got the Edge S and want GApps? Basically you unlock your bootloader, root with Magisk, then install MagiskGApps.
DISCLAIMER: UNLOCKING YOUR BOOTLOADER MAY VOID YOUR WARRANTY, AND DOING ALL THESE THINGS IN THIS GUIDE MAY RESULT IN DAMAGE/BRICKING YOUR PHONE. I AM NOT RESPONSIBLE FOR ANYTHING YOU DO TO YOUR PHONE. PROCEED AT YOUR OWN RISK.
1. Unlock the bootloader: that should be doable with their global bootloader unlock website here.
2. Download Lenovo Motoroa Smart Assistant (Rescue and Smart Assistant), and follow its instructions to "rescue" your device. It will lead you to boot into bootloader mode and download the firmware. Find the firmware file via the LMSA's downloads (should have a "show folder" button). You'll need the boot.img file for Magisk.
3. Download Magisk, then follow its instructions. You'll have to copy the boot.img to your device, then use Magisk to patch the boot file, then copy the modified one to your PC.
4. You'll need fastboot. If you don't have it already, you can download the Android SDK platform tools here. Then go into the folder, Shift+Right Click the folder, then "Open Command Prompt" or "Open PowerShell," you should have something close to one of those two. Copy your Magisk modified .img file to that folder, then you'll want to input:
fastboot flash boot [modified .img file]
Once that completes, you should see in large text, "Start" on your phone next to the power button. Press the power button, and it should boot, and you should have root now.
5. Download MagiskGApps to your phone, open Magisk on your phone, click the button that looks like a puzzle piece at the bottom of the screen, "Modules." Click "Install from storage," locate the MagiskGApps file, and install it. After that it will ask you to restart your phone, do that, then you'll just have to be patient as it takes time once its restarted to load everything. You also may need to update some or all of the apps, then you should be able to use the notification to finish setting up the phone with Google Setup.
Thanks to Motorola for making it easy to unlock their bootloaders
Thanks to the whole Magisk team for making an easy, awesome root (and more!)
Thanks to Wacko1805 (and team?) for making MagiskGApps. This is really awesome.
unlock the BL and get root is will make some apps fingerprint and face ID fail?
kimker said:
unlock the BL and get root is will make some apps fingerprint and face ID fail?
Click to expand...
Click to collapse
Magisk has a "Magisk Hide" which will allow it to pass SafetyNet, and most things which check on device security will think the device is secure. But unlocking BL and rooting does make the device less secure, and therefore incurs its own risks apart from bricking or damaging the device.
HopelesRomantc91 said:
Magisk has a "Magisk Hide" which will allow it to pass SafetyNet, and most things which check on device security will think the device is secure. But unlocking BL and rooting does make the device less secure, and therefore incurs its own risks apart from bricking or damaging the device.
Click to expand...
Click to collapse
yes, i knew the unlock and root will take risk.. but not sure is Payment business apps using fingerprint will work normal.
kimker said:
yes, i knew the unlock and root will take risk.. but not sure is Payment business apps using fingerprint will work normal.
Click to expand...
Click to collapse
Google Pay works. But according to the Motorola website you should be able to relock the bootloader if yours doesn't work. But there's never any guarantee. If you need your device secure, recommend don't unlock bl or root, or wait to see if there's a root option without bootloader unlock that can be easily undone.
HopelesRomantc91 said:
Google Pay works. But according to the Motorola website you should be able to relock the bootloader if yours doesn't work. But there's never any guarantee. If you need your device secure, recommend don't unlock bl or root, or wait to see if there's a root option without bootloader unlock that can be easily undone.
Click to expand...
Click to collapse
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
kimker said:
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
Click to expand...
Click to collapse
That's not good. Hopefully they can restore it back somehow. With this guide to unlock and flash gapps why would you need to flash G100 though? This seems to be itright now without one of rom developer's releases to get root & apps. For me this is all i would look for. Titanium backup on it and restore.. done until PE rom comes out.
kimker said:
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
Click to expand...
Click to collapse
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
thank you. They did not ask for help. It seems that the lock BL is a self-verification switch, and then performs a verification system integrity.
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
I'm curious,If you unlock and flash other firmware and then flash back to the original firmware, can it be locked again?
Mine doesn't let me unlock its BL. I've got unlock code from moto and did a factory reset with SIM card in slot 1. After enabling developer mode and debugging the switch still is greyed out. So no chance to unlock it.
Has anyone got an idea what to try now?
Moto support answered yesterday to my request but also no solution since I told them that it doesn't work
Device is not branded. I got it from Amazon so no provider branding.
If this won't be able to be unlocked and rooted I'll have to return it and switch to a Google Pixel.
kischde said:
Mine doesn't let me unlock its BL. I've got unlock code from moto and did a factory reset with SIM card in slot 1. After enabling developer mode and debugging the switch still is greyed out. So no chance to unlock it.
Has anyone got an idea what to try now?
Moto support answered yesterday to my request but also no solution since I told them that it doesn't work
Device is not branded. I got it from Amazon so no provider branding.
If this won't be able to be unlocked and rooted I'll have to return it and switch to a Google Pixel.
Click to expand...
Click to collapse
I had the same issue, you need to factory reset WITH your sim card in the phone, this will let you open the OEM unlock slide thing in the dev mode.
Then once its done you can fastboot and unlock the bootloader.
I did so, maybe I explained not so well. SIM was inserted and then I did factory reset by starting it from settings. After restart it's still the same - switch / unlock slider greyed out.
kischde said:
I did so, maybe I explained not so well. SIM was inserted and then I did factory reset by starting it from settings. After restart it's still the same - switch / unlock slider greyed out.
Click to expand...
Click to collapse
On my OG Pixel XL, I had to wait 7 days for the slider to become normal. By the time I got around to do it on the Edge S it was about the same time.... could be related
Now as you said that I remember that thingy with another device. Maybe a Xiaomi I think... With that I had to wait several days until the unlock code was delivered.
But there was a message, too, when trying to get it sooner, which said you needed to wait some more time.
Not sure if it's the the same for Moto devices? Then again, when thinking that you experienced the same with a Pixel, too...
Did anyone else make such an experience with his/her g100?
kischde said:
Now as you said that I remember that thingy with another device. Maybe a Xiaomi I think... With that I had to wait several days until the unlock code was delivered.
But there was a message, too, when trying to get it sooner, which said you needed to wait some more time.
Not sure if it's the the same for Moto devices? Then again, when thinking that you experienced the same with a Pixel, too...
Did anyone else make such an experience with his/her g100?
Click to expand...
Click to collapse
Make sure your on the latest OTA, Lenovo made a mistake on previous versions with the OEM Unlocking function not being enabled. They fixed it in latest ota.
RSA tool said the file I uploaded yesterday is the latest one available (and it's exactly the same as the installed version).
The device was released just a few days ago in Europe. Perhaps they fixed the unlock switch in other regions and still need to fix it in Europe..
Will wait until weekend if they come up with a solution. If not I'm afraid I have to return the device as I need it personally AND professionally, too - I'm field agent, so.... :/
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
The poor guy whose phone turned bricks went to the after-sales department of moto, and the answer was that he needed to replace the phone motherboard. .
kimker said:
The poor guy whose phone turned bricks went to the after-sales department of moto, and the answer was that he needed to replace the phone motherboard. .
Click to expand...
Click to collapse
Ouch...
kimker said:
I'm curious,If you unlock and flash other firmware and then flash back to the original firmware, can it be locked again?
Click to expand...
Click to collapse
I would assume so, but I don't really know why anyone would want to relock.
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?