Dear all,
I am new on Android, the Nexus 5 is my first android device. I freshly come from a 5 years old iPhone 3G.
2 Weeks ago I unlocked the bootloader of my device and rooted it following the tutorials provided by the XDA community without any problem.
Today, I saw that the OTA to upgrade from the Android version 4.4 to the version 4.4.2 was available directly from the device.
Since I did not want this update to be a problem with my rooted device, I downloaded the following apps: BootUnlocker for Nexus Devices and OTA RootKeeper (I do realize using RootKeeper was stupid since anyway the last update was released on July 25, 3 months before KitKat...). But anyway, this is what I did. I used those apps to Lock my Bootloader and unRoot my phone, thinking that this will reduce the chances of potential conflict with the OTA update.
Afterward, I downloaded and tried to instal the OTA directly from the Nexus 5. It ends up that I got stuck on the recovery menu. It was then impossible to get back on android and I did not know what to do.
This is where I did something totally crazy. Usually I spend time reading tutorials and finding information before doing anything that I do not fully understand. But at this stage I simply thought that the update could not properly instal due to the root. So I went on Advanced Wipe, I ticked all the options (data, system, Cash, Dalvik... all of them), and wiped the device.
As a result, my Nexus 5 has currently a Locked Bootloader and no OS installed. This means that I cannot activate the developer menu (no OS) to tick the option USB debugging. Thus, I cannot unlock my bootloader and in consequence I cannot instal the factory image and get back to stock.
Please, If you can give me some advice, explain me how can I unlock the bootloader in these conditions. Let me know... I really don't know what to do now.
PS: sorry my english is not perfect but I do hope you clearly understand my problem.
Yoyo-san said:
Dear all,
I am new on Android, the Nexus 5 is my first android device. I freshly come from a 5 years old iPhone 3G.
2 Weeks ago I unlocked the bootloader of my device and rooted it following the tutorials provided by the XDA community without any problem.
Today, I saw that the OTA to upgrade from the Android version 4.4 to the version 4.4.2 was available directly from the device.
Since I did not want this update to be a problem with my rooted device, I downloaded the following apps: BootUnlocker for Nexus Devices and OTA RootKeeper (I do realize using RootKeeper was stupid since anyway the last update was released on July 25, 3 months before KitKat...). But anyway, this is what I did. I used those apps to Lock my Bootloader and unRoot my phone, thinking that this will reduce the chances of potential conflict with the OTA update.
Afterward, I downloaded and tried to instal the OTA directly from the Nexus 5. It ends up that I got stuck on the recovery menu. It was then impossible to get back on android and I did not know what to do.
This is where I did something totally crazy. Usually I spend time reading tutorials and finding information before doing anything that I do not fully understand. But at this stage I simply thought that the update could not properly instal due to the root. So I went on Advanced Wipe, I ticked all the options (data, system, Cash, Dalvik... all of them), and wiped the device.
As a result, my Nexus 5 has currently a Locked Bootloader and no OS installed. This means that I cannot activate the developer menu (no OS) to tick the option USB debugging. Thus, I cannot unlock my bootloader and in consequence I cannot instal the factory image and get back to stock.
Please, If you can give me some advice, explain me how can I unlock the bootloader in these conditions. Let me know... I really don't know what to do now.
PS: sorry my english is not perfect but I do hope you clearly understand my problem.
Click to expand...
Click to collapse
You've got it all wrong. You do not need USB debugging to unlock bootloader. to unlock bootloader you must use FASTBOOT commands, which means you MUST be in the bootloader itself. USB debugging ONLY works in android.
rootSU said:
You've got it all wrong. You do not need USB debugging to unlock bootloader. to unlock bootloader you must use FASTBOOT commands, which means you MUST be in the bootloader itself. USB debugging ONLY works in android.
Click to expand...
Click to collapse
Dear RootSU,
So this means that I am not stuck at all and that I am simply limited by my current knowledge about android?
If this is the case, then "alleluia"! I will document myself to be able to fix this thing.
Yoyo-san said:
So this means that I am not stuck at all and that I am simply limited by my current knowledge about android?
Click to expand...
Click to collapse
Pretty much
You should be able to unlock the bootloader as you did before.
Boot phone to fastboot mode, download fastboot and adb kit to you computer... it can be found here on forums easy, and in comand line to unlock bootloader you need type "fastboot oem unlock".
More complete guide you can find here http://forum.xda-developers.com/showthread.php?t=2507905 =)
rootSU said:
Pretty much
You should be able to unlock the bootloader as you did before.
Click to expand...
Click to collapse
It's ok now!
As you said, I could unlock the Bootloader the same way I did before. Then I install the factory image 4.4.2, which I rooted directly.
Thanks a lot RootSu, you've shown me my mistakes and put me on the way to fix my problem.
Thanks also for your concern Biggreen. =)
Problem solved!
rootSU said:
You've got it all wrong. You do not need USB debugging to unlock bootloader. to unlock bootloader you must use FASTBOOT commands, which means you MUST be in the bootloader itself. USB debugging ONLY works in android.
Click to expand...
Click to collapse
Dear RootSU,
One more question, could you explain me why I got stuck into the recovery menu when I first tried to update via the OTA? Will I get the same kind of problem when I'll update with the v4.4.3 in the future?
Thanks
Yoyo-san said:
Dear RootSU,
One more question, could you explain me why I got stuck into the recovery menu when I first tried to update via the OTA? Will I get the same kind of problem when I'll update with the v4.4.3 in the future?
Thanks
Click to expand...
Click to collapse
I am not sure on the extact reason. OTA itself will not install with a custom recovery. You have to download the OTA and boot to recovery then manually flash.
There is a good "OTA Helpdesk" sticky thread in general you should read as theres lots of advice there
hi there...i've got the same problem... i wiped everythink and now i'm not able to switch on my phone....i just want to get out of this somehow...i'm very much new to this and i just want to get my stock android back that's it...somebody please help....
Do you see the battery icon when you connect the phone to a charger? Does the LED turn red when you connect the phone to a charger? Maybe leave the phone connected for a couple of hours and then try to power on?
I opened up the developer options on my Moto G Stylus and went under OEM Unlocking and selected the allow the bootloader to be unlocked option. That was either last week or a few weeks ago because I wanted to root it and put a custom rom on it. I didn't rooted it yet because I'm not sure what roms are good, I only had cyanogin mod roms on my other phones and I'm not sure which rom is the safest and best to use so I still use the stock rom. I turned on Pandora to play music before I went to sleep. When I woke up my phone was in some kind of recovery mode and said something like the operating system failed to boot. Two options were available, 1- to try booting again, and 2-factory reset the phone which would erase all data. I selected 1, and my phone booted up. Could this be because the bootloader is unlocked? Does having the bootloader unlocked leave it suspectable to being hacked? Could my phone have been hacked?
Switching OEM Unlocking is not enough to unlock, you then must on motorola unlock webpage paste code from your phone and, wait for unlock code in email, via fastboot with this unlock code doing finaly real umlocking...
k3dar7 said:
Switching OEM Unlocking is not enough to unlock, you then must on motorola unlock webpage paste code from your phone and, wait for unlock code in email, via fastboot with this unlock code doing finaly real umlocking...
Click to expand...
Click to collapse
Would selecting the bootloader option to be unlocked in the developer options make my phone more vulnerable to be hacked?
A few hours later my phone did the same thing and went into recovery mode saying that my phone could not load the OS and might be infected or something. I had the same options to either try to load the OS again or factory data reset the phone. How could this happen?
I factory data reset my phone this time. I just hope I don't have some kind of malware.
Mine was hacked like this. Changed stuff so it won't boot back to original. Got into system files and remote control my phone. Is there a way to get back to original without computer? It's useless now
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 Samsung J3 Eclipse (SM-J327V) that has no OEM Unlock in Developer Options. The phone is approximately 5 years old. I would like to unlock the bootloader on it. I'v tried the suggestions listed on the forum, but they are for new phones to bypass the 7 day waiting period and enable the OEM unlock. I tried them anyway, and they don't work on my J3.
Seems to me that I read that Samsung started hiding the OEM Unlock with Android version 8.0
I was thinking of loading some old version of the official firmware that was Android 7.0 or earlier (if I can find it). Then, hopefully there would be an OEM Unlock that would enable me to unlock the boot loader. Once unlocked, I could flash back to Android 8.1 (newest version for this old device). Would that work? Can you use Odin to downgrade the version of Android?
Comments welcome from all. Thanks!
I've tried following every youtube video and posting on the internet for how to get the hidden OEM unlock back into developer options. None of them work. I swear I have done the process of date resetting dozens of times and it still doesn't work.
Can anybody help? Please! I'd really like to unlock the bootloader. Is there any other way to do this?
delete
insert your sim card. worked for me
actually you only need to set time forward a week or more
Win_7 said:
actually you only need to set time forward a week or more
Click to expand...
Click to collapse
idk. for me i had to insert my simcard
ElitePrime said:
idk. for me i had to insert my simcard
Click to expand...
Click to collapse
i think theres many ways to do it
setting time forward is the easiest