Related
I'm searching the threads for info on unlocking my phones? failing! I can't understand most of what I'm reading and I'm not sure this is something I can do myself. I purchased 3 of these SX56 in a lot and all are asking for a SIM PIN with my AT&T sim card.
I'm clueless and quite ignorant on the subject. I seen on thread saying to copy a link to the phone and run it?????? I don't know how to do that and I don't want to screw this up. any advice for a newbie?
freek2fast said:
I'm searching the threads for info on unlocking my phones? failing! I can't understand most of what I'm reading and I'm not sure this is something I can do myself. I purchased 3 of these SX56 in a lot and all are asking for a SIM PIN with my AT&T sim card.
I'm clueless and quite ignorant on the subject. I seen on thread saying to copy a link to the phone and run it?????? I don't know how to do that and I don't want to screw this up. any advice for a newbie?
Click to expand...
Click to collapse
Welcome to the forum
Hope this helps: http://wiki.xda-developers.com/index.php?pagename=BA_Unlock_Sim
Good luck,
freek2fast said:
I'm searching the threads for info on unlocking my phones? failing! I can't understand most of what I'm reading and I'm not sure this is something I can do myself. I purchased 3 of these SX56 in a lot and all are asking for a SIM PIN with my AT&T sim card.
I'm clueless and quite ignorant on the subject. I seen on thread saying to copy a link to the phone and run it?????? I don't know how to do that and I don't want to screw this up. any advice for a newbie?
Click to expand...
Click to collapse
First and foremost, you either have an SX56 or a Blue Angel. The Blue Angel is the SX66, the SX56 is an older device called by the name of Wallaby. Please specify which one you did get exactly so that we can direct you to the right place for help.
The sx56 is the phone that is SIM locked. I tried the XDA developers ROM for wallaby last night and failed. Now one of the phones are stuck in the "upgrading" mode and I'm afraid it's hopeless. any idea if it can be recovered? I think the problem was with the activesync, it wasn't current enough and I was required to get a newer version. I downloaded the latest free version and it said my phone was updating but it didn't??????
freek2fast said:
The sx56 is the phone that is SIM locked. I tried the XDA developers ROM for wallaby last night and failed. Now one of the phones are stuck in the "upgrading" mode and I'm afraid it's hopeless. any idea if it can be recovered? I think the problem was with the activesync, it wasn't current enough and I was required to get a newer version. I downloaded the latest free version and it said my phone was updating but it didn't??????
Click to expand...
Click to collapse
All phones are SIM locked (unless it is unlocked by either manufacturer or by the user). If the phone was SIM locked and you tried to upgrade it without unlocking, then you might be in trouble. Now, your phone is in "upgrading mode", and what you are trying to say is that the phone is in bootloader mode... if it can access bootloader, then you still have a fighting chance.
First of all, we agree that you have a Wallaby and not a Blue Angel, correct? (the one with the big black external antenna that houses the stylus). If that is not the case, now would be a good time to let us know.
Second, your message wasn't exactly clear. what did you exactly do to your phone to get it stuck in bootloader? Please go step by step on what you did...
My phones are the Wallaby SX56, these are SIM locked but the carrier is AT&T according to the logo on the front of the phone. I put my AT&T SIM card in the phone and it asked me for a SIM PIN.
Here's the steps I took to get where I am currently,
went to Wiki XDA Developers and found my device "Wallaby" Clicked the link to unlockwiz and chose my device "I have a Wallaby" Next question asked if my ROM version was on te list, it was not and I choose accordingly. I did not have a serial cable and I choose not to back up my current ROM to opt for the "special edition" by XDA Developers This is a new phone to me and I had no need of any saved contact info, next I clicked the link download and install "special edition ROM" Here's the link I used
: http://www.romkitchen.de/tools/special_rom_1.2.exe.zip
***I think I just found my failure, under readme: system requirements do not include Vista! I went to microsoft and downloaded a newer version of activesync and it was not compatible with Vista. I ran a program there to fix the compatiblity issue and it said download complete.***
the phone recognized the USB connection last night and I started the download, during the download I got an error message that the COMM/USB port connection had failed and to check the connection in device manager.
at the time device manager was showing the HTC device but now it's not. I cannot find the activesync program on my computer and my device is not showing up anywhere when I connect it to the computer.
I noticed at the bottom of my screen, the "safely remove hardware" Icon used to stay on the bar until I clicked it to remove the device, now the icon closes after a few seconds when the device hasn't been disconnected. not sure if this is important or not but maybe helpful.
currently the phone is in bootloader and when I connect it to the USB it shows up in the device manager but status is "the device cannot start" code 10 please check for solution with microsoft.
It's obvious that I'm not smart enough to be attempting a fix________Nice Siemens SX56 for sale for parts only, make an offer?
http://wiki.xda-developers.com/index.php?pagename=XDAunlock
try the exe version
I don't know how to "try" anthing from where I'm at, My activesync is missing, the phone is not recognizing the USB link, vice versa. where do I start?
I'm only kidding about selling the phone for parts but I might not have a choice. I need recovery
I've got activesync again but not sure whats next, I get an error in windows mobile trying to connect to one of the other wallabies. I need to know how to recover the bootloader phone?????
Try to do it with a XP computer rather than a Vista one. It is not only a matter of ActiveSync, but the way the OS works with the flashing...
I had a feeling that was coming!
So tell me where to start once I get to an XP machine. I'm in bootloader so do I start the entire process over as if I weren't in bootloader? and am I using the right link "unlockWiz" to do what I need?
freek2fast said:
I had a feeling that was coming!
So tell me where to start once I get to an XP machine. I'm in bootloader so do I start the entire process over as if I weren't in bootloader? and am I using the right link "unlockWiz" to do what I need?
Click to expand...
Click to collapse
Just follow the steps in the wiki (exactly as you see them). I'll try to see if I can go back and check on the whole procedure (I have a Wallaby myself, which I haven't used since 2005, but I saved it from becoming a paperweight after a bad flash).
Try to see if you can flash the original rom with the XP machine. If you can't, then you may want to try the SD flash method... that's the one that saved mine.
Report back to see if it worked.
Good luck!
Wow, I can't find an XP machine anywhere???
I hope you like stories because I like telling them.
So, I've been trying to get this phone to work for several weeks now and I'm hoping someone here can help. The backstory is going to make me sound really stupid, but here you go. I bought this phone initially to replace my old Nokia Lumia 710 which is still *functioning*, but lets be honest it needs to be replaced. It cost me $150 if I remember correctly. Well, it worked fine for about a week and then I dropped it and shattered the screen through the LCD layer. I backed up the contents while there was still enough LCD fluid for me to see what I was doing before the whole screen went black.
I then proceeded to take the phone to a repair place where they charged me $200 dollars to replace the screen. Yes, I know I could have just as easily bought one brand new, but the half-off sale was over and I've always been one to fix things instead of replacing them. Of course maybe that will change with this experience. Anyway, when they finally got it back to me and when I turned it on it said there was a software update available. So, I followed the standard procedure and allowed it to download and restart. . . but it got stuck in a loop on the restart. At this point I knew very little about the phone, so I left it at home to die and switched the SIM card back to my Nokia.
Later that day I researched how to 'reset' it, which gave me the instructions for how to put it into bootloader/download mode, and I thought "Well, it still works, I bet they can fix this at the phone repair place". So I charged it, brought it there and showed them that it still worked -sort of- and they told me they would fix it in a day for $30.
A week later they called and said "We can't fix this thing, take it back free of charge". It didn't make any sense to me because the internet made it sound like a 'soft brick' was easy to fix. So I took it back and decided to try fixing it on my own. I downloaded the HTC drivers and got to work. The first thing I found was the HTC official RUU.exe and I tried using it to fix the phone. However, it returned with a 'signature error', which I researched and as far as I can tell it's because the official RUU is nougat and my firmware has the key for marshmallow.
I looked for a RUU.exe that was a marshmallow version, but HTC took down all the downloads that I found links to and no ones seems to have saved it anywhere. Instead I found directions to update manually using a combination of ADB/fastboot/htc_fastboot. I set them up to work on the command line and they all recognize that the phone is connected. I downloaded a marshmallow RUU.zip and tried to flash it, but it failed with the message "main version NOT ALLOWED". I searched around and supposedly it's because the only zips I could find are lower versions than the broken version installed on mine. (something about s-on?)
I then thought that maybe I could update the firmware and then use the official RUU to get it working again. From what I could tell getting a TWRP recovery on there would give me enough access to the phone to allow firmware to be updated. I searched all over for ways to install TWRP, but it failed to flash also. Supposedly I need the bootloader unlocked.
I got an account on HTCDev and started following the directions but the command:
fastboot oem get_identifier_token
Returns an error "last byte is 0x00, disable unlock"
So I guess I can't unlock the bootloader either. . .
The current state of the phone is:
Software Status: Official
Locked
S-ON
Which seems to be the worst case scenario for trying to fix it. Also, just some other info, the OS version is 1.55.617.4
and it's a USA Unlocked version, if that wasn't already described by the OS version. . .
Oh and it's encrypted.
So yeah, I'm giving up today. I already ordered a new phone, however I still think it would be really satisfying to get it working again. You guys are the pros and I am in posession of the most defiant piece of non-functional silicon to ever exist, so if you can tell me how to beat it into submission I will be very happy. Thanks!
-Corneilius
Corneilius said:
I hope you like stories because I like telling them.
So, I've been trying to get this phone to work for several weeks now and I'm hoping someone here can help. The backstory is going to make me sound really stupid, but here you go. I bought this phone initially to replace my old Nokia Lumia 710 which is still *functioning*, but lets be honest it needs to be replaced. It cost me $150 if I remember correctly. Well, it worked fine for about a week and then I dropped it and shattered the screen through the LCD layer. I backed up the contents while there was still enough LCD fluid for me to see what I was doing before the whole screen went black.
I then proceeded to take the phone to a repair place where they charged me $200 dollars to replace the screen. Yes, I know I could have just as easily bought one brand new, but the half-off sale was over and I've always been one to fix things instead of replacing them. Of course maybe that will change with this experience. Anyway, when they finally got it back to me and when I turned it on it said there was a software update available. So, I followed the standard procedure and allowed it to download and restart. . . but it got stuck in a loop on the restart. At this point I knew very little about the phone, so I left it at home to die and switched the SIM card back to my Nokia.
Later that day I researched how to 'reset' it, which gave me the instructions for how to put it into bootloader/download mode, and I thought "Well, it still works, I bet they can fix this at the phone repair place". So I charged it, brought it there and showed them that it still worked -sort of- and they told me they would fix it in a day for $30.
A week later they called and said "We can't fix this thing, take it back free of charge". It didn't make any sense to me because the internet made it sound like a 'soft brick' was easy to fix. So I took it back and decided to try fixing it on my own. I downloaded the HTC drivers and got to work. The first thing I found was the HTC official RUU.exe and I tried using it to fix the phone. However, it returned with a 'signature error', which I researched and as far as I can tell it's because the official RUU is nougat and my firmware has the key for marshmallow.
I looked for a RUU.exe that was a marshmallow version, but HTC took down all the downloads that I found links to and no ones seems to have saved it anywhere. Instead I found directions to update manually using a combination of ADB/fastboot/htc_fastboot. I set them up to work on the command line and they all recognize that the phone is connected. I downloaded a marshmallow RUU.zip and tried to flash it, but it failed with the message "main version NOT ALLOWED". I searched around and supposedly it's because the only zips I could find are lower versions than the broken version installed on mine. (something about s-on?)
I then thought that maybe I could update the firmware and then use the official RUU to get it working again. From what I could tell getting a TWRP recovery on there would give me enough access to the phone to allow firmware to be updated. I searched all over for ways to install TWRP, but it failed to flash also. Supposedly I need the bootloader unlocked.
I got an account on HTCDev and started following the directions but the command:
fastboot oem get_identifier_token
Returns an error "last byte is 0x00, disable unlock"
So I guess I can't unlock the bootloader either. . .
The current state of the phone is:
Software Status: Official
Locked
S-ON
Which seems to be the worst case scenario for trying to fix it. Also, just some other info, the OS version is 1.55.617.4
and it's a USA Unlocked version, if that wasn't already described by the OS version. . .
Oh and it's encrypted.
So yeah, I'm giving up today. I already ordered a new phone, however I still think it would be really satisfying to get it working again. You guys are the pros and I am in posession of the most defiant piece of non-functional silicon to ever exist, so if you can tell me how to beat it into submission I will be very happy. Thanks!
-Corneilius
Click to expand...
Click to collapse
There are still several option to fix this phone.
might want to try flashing a newer ruu that is still Marshmallow version like this one https://androidfilehost.com/?fid=24459283995314374 or his one https://androidfilehost.com/?fid=24399994186368579
htc_fastoot oem rebootRUU
htc_fastboot flash zip 2PQ9IMG_HIA_AERO_UL_M601_SENSE7GP_1.56.617.1_signed.zip
htc_fastboot reboot
and there is still the possibility to update your firmware to 2.xx.617.x using a singed firmware.zip file making your phone accept the new ruu signature implemented in Nougat ruu.
Btw you can't unlock your BL because the "allow oem unlock" option was not previously turned on from the "developer option" (this requires a booting OS).
Sweet, you found a Marshmallow ruu!
I'll try it, thanks!
-Corneilius
Just to preface, I'm not a total noob when it comes to android, but I'm definitely not savvy or knowledgeable in any way either.
I purchased a Motorola p50 a while ago from a seller on Aliexpress, and when booting the phone I get a message saying that the bootloader is unlocked. Going into the developer settings shows the OEM unlock option is in the off position, greyed out and with a message saying that the bootloader is already unlocked. However, booting into fastboot and running 'fastboot oem lock' gives me an error message telling me to enable unlocking in the developer options... which I can't do, because it's greyed out. Running 'fastboot oem unlock' tells me that the bootloader is already unlocked. From what I can tell the phone is running the stock android 10 motorola ROM, and I would like to lock the bootloader so that I can use google pay, as the phone supports NFC.
According to settings, the model is "motorola one vision", the hardware version is PVT, the SKU is XT1970-5 and the software channel is 'retcn'
Any help on how I can lock the bootloader, or even just get google pay working would be greatly appreciated.
There exists many threads on xda about this issue and it all boils down to this: your Bootloader thinks you're running modified software, hence locking it will hard brick your device (at least there is a possibility). According to the above linked thread, here's what you can do to troubleshoot this (in order of what could work):
Factory reset your device from Settings. (Relocking will erase your data anyways, Backup is advised)
Flash The Stock Firmware and attempt the lock process again.
Flash Magisk and enable Magisk Hide (this one is dangerous, since a modified boot.img while relocking can hard brick your device as well, do it at your own risk!!!)
Pass Safetynet check by flashing latest Magisk canary, enabling Magisk Hide and flashing this Universal Safetynet fix.
Step 4 is what I would do if I were you, however, advising people on the internet to root in order to solve this problem is not very wise, hence it being the last step.
Alright, I might give the last one a go since I don't know what the stock firmware for the phone is supposed to be. Thanks a lot for your help
Update: after attempting to install magisk with little success, I eventually found a single russian article that solved the issues I was having with magisk. I installed that plugin you linked, and success! Google pay now works without issue. Your help is greatly appreciated
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?
I have an old Asus Zenfone 4 that randomly got stuck in a boot loop while it was recharging, and now I don't know how to fix it, or even if it is possible to fix. The only thing that still works is fastboot mode (recovery mode doesn't work either, so SD cards are out of question).
I have tried a number of things to factory reset the phone and see if it changes anything, but it seems impossible to unlock its partitions for flashing: commands such as fastboot flashing unlock, fastboot oem asus-go or anything similar just throw errors saying that the command doesn't exist, or if it does, that I don't have permission to run them. For this same reason, I couldn't use things such as TWRP as I can't flash any of the partitions on my phone. Additionally, I have tried to enable adb through fastboot oem, but even though the command is successful, whenever I get the system info, it says that adb debugging is still off.
Does anyone know a way to either unlock this device or factory reset it without unlocking?
Another old-ish device killed by the silent OTA update of the OEM!
The deadly mistake of connecting an old-ish device to OEM servers for fresh install.
Check with unauthorized service centers who have <Miracle Box> if they can flash with fastboot. Or authorized service centers might charge but they could revive the device.
OldNoobOne said:
Check with unauthorized service centers who have <Miracle Box> if they can flash with fastboot. Or authorized service centers might charge but they could revive the device.
Click to expand...
Click to collapse
By what you are saying... Is it actually impossible for me to unlock the bootloader? I have no problem with service centers, but it would be much better and quicker if there was was a way for me to unlock it.
rafk12 said:
By what you are saying... Is it actually impossible for me to unlock the bootloader? I have no problem with service centers, but it would be much better and quicker if there was was a way for me to unlock it.
Click to expand...
Click to collapse
I threw away two old chaina phones just because I made the mistake of reflashing the original OS and tried to update from OEM servers..BOOM! Dead Phone!
The moment OEM servers detect an old device connected to their servers for an update, they kill the device so that new devices can be sold in the market, why would this happen to a device which was working perfectly under a Custom ROM before? I dont update the device from OEM channelsbecause OEM might try to kill the device after warranty period, instead I update through the Custom ROM channel.
Maybe some chip got fried while charging the device, among the asian brands shamshung & WonPlus have durable components but other asian brands maximum 4 years before the components like display etc. or even the chipset components begin to fail. Or it could be the OEM update thing too