Hello!
I wrote the following email to Sony Developer World, but they asked me to post it here.I don't know why I should do this because this page is not meintained by Sony. But hoping that Sony will give me a definitive answer I do as they asked me for:
[start of email]
I haven’t understood your risk explanation on your „Unlock your boot loader“ page because to my mind it is a little bit unprecise:
You wrote there:
“Risks
Please be aware that Sony cannot guarantee the full functionality, and will not be responsible, for any unsigned custom ROM being flashed to your device after the boot loader is unlocked. An unsigned custom ROM may not have gone through the thorough tests that we run for each device and software version that we release.
Also, a custom ROM might not work properly on your device, and certain functions and offerings may cease to work. The performance of the device might also be affected, and you may damage your device permanently. In worst case, unlocking the boot loader will cause physical injuries or material damage, for example, due to the device overheating.
Certain pre-loaded content on your device may also be inaccessible due to the removal of DRM security keys. For high-end devices running recent software versions, for instance Xperia Z3, the removal of DRM security keys may affect advanced camera functionality. For example, noise reduction algorithms might be removed, and performance when taking photos in low-light conditions might be affected. The secure user data partition may also become inaccessible, and you will not be able to get any more official software upgrades if you unlock the boot loader.
After unlocking your device, you should not enable My Xperia (found in the settings menu under security on some devices running Android 5.0) as this might cause the device to malfunction.”
I don’t understand the red marked sentence. So my question concerns the removal of the DRM security keys because I haven’t found out who and when they are removed:
WHO removes the DRM security keys? Is it done by SONY when unlocking the bootloader (and why do you do that?) or is it a risk caused by installing custom ROM’s or recovery images?
And what will happen if I’ll unlock the bootloader of my Sony Xperia Z5 compact via the integrated function “OEM unlock”? Will the DRM security keys deleted any way using this or will they be preserved? And will I be able to lock the bootloader again?
Regards
Ansgar
[end of email]
klausstoertebeker said:
WHO removes the DRM security keys? Is it done by SONY when unlocking the bootloader (and why do you do that?) or is it a risk caused by installing custom ROM’s or recovery images?
Click to expand...
Click to collapse
It's done automatically if you unlock the bootloader, i.e. "by Sony".
klausstoertebeker said:
And what will happen if I’ll unlock the bootloader of my Sony Xperia Z5 compact via the integrated function “OEM unlock”? Will the DRM security keys deleted any way using this or will they be preserved?
Click to expand...
Click to collapse
The DRM keys will be erased.
klausstoertebeker said:
And will I be able to lock the bootloader again?
Click to expand...
Click to collapse
Most likely, but the DRM keys cannot be restored. They are forever lost.
sorry, that's bull****.
remove the bootloader lock in developer settings and you will see, that Marlin, Widevine and CKB are still active and reported as "key ok"
and no, Sony does not remove them, you do it while flashing.
BTW. there are already early attempts in flashing, and yes they have deleted their DRMs. and no, there is no way to bring them back.
however, for the time being: keep the bootloader closed, as you've no benefits from unlocking it, yet.
Gesendet von meinem E5823 mit Tapatalk
basthet said:
sorry, that's bull****.
remove the bootloader lock in developer settings and you will see, that Marlin, Widevine and CKB are still active and reported as "key ok"
and no, Sony does not remove them, you do it while flashing.
BTW. there are already early attempts in flashing, and yes they have deleted their DRMs. and no, there is no way to bring them back.
however, for the time being: keep the bootloader closed, as you've no benefits from unlocking it, yet.
Gesendet von meinem E5823 mit Tapatalk
Click to expand...
Click to collapse
Dude, you should relax. There's no manure in my post.
You have misunderstood the toggle in the developer settings menu. It does NOT unlock the bootloader.
The toggle only disables some software features that would cause trouble if you actually choose to unlock the bootloader.
Bootloader in unlocked using fastboot oem unlock, as always.
Please read up:
http://forum.xda-developers.com/showpost.php?p=63216335&postcount=23
http://forum.xda-developers.com/showpost.php?p=63216352&postcount=24
http://forum.xda-developers.com/showpost.php?p=63343765&postcount=33 (quoting you)
http://forum.xda-developers.com/showpost.php?p=63299154&postcount=17
Well, I'm relaxed, but you help no-one in posting wrong stuff.
Lets make it simple:
Compare it with a simple door and a door guard.
The door guard has order only to let you in, having a specific key.
In order to get this key, e.g. for the z3 family:
Go to Sonys webpage, register, download the key.
procedure for the z5c:
go into developer settings, enable: OEM unlock.
This corresponds to: Tell the guard, no key is required anymore.
Setting the flag of making something accessible is called "unlock" - so: in fact you can call it "unlock the boot loader" by enable the "OEM unlock" in Developer Settings*.
fastboot oem unlock does much more.
In my example:
go to the door,
ask the guard: is door open / already unlocked?
[z3c: handover the key to the guard]
[z3c: Wait to get the "Ok" to pass - guard: unlock the door] -> correspond to: setting flag: accessible = unlock
pushing the door open,
hanging a fat note in the entrance hall telling "Door is open";
So: you did not miss understood what the toggle does, but the whole procedure.
And no: the toggle does not disable some software feature, it just removes the OEM specific key requirement by accessing the boot loader
*Note: I know, that was quite rough simplification, and to be absolute correct: the OEM unlock toggle in Dev. Setting does in fact not physically "unlock" the boot loader. It just removes the requirement for a key in the unlocking process. However, that correspond to an open boot loader, as all attempt to enter it, will not be denied.
basthet said:
Well, I'm relaxed, but you help no-one in posting wrong stuff.
Lets make it simple:
Compare it with a simple door and a door guard.
The door guard has order only to let you in, having a specific key.
In order to get this key, e.g. for the z3 family:
Go to Sonys webpage, register, download the key.
procedure for the z5c:
go into developer settings, enable: OEM unlock.
This corresponds to: Tell the guard, no key is required anymore.
Setting the flag of making something accessible is called "unlock" - so: in fact you can call it "unlock the boot loader" by enable the "OEM unlock" in Developer Settings*.
fastboot oem unlock does much more.
In my example:
go to the door,
ask the guard: is door open / already unlocked?
[z3c: handover the key to the guard]
[z3c: Wait to get the "Ok" to pass - guard: unlock the door] -> correspond to: setting flag: accessible = unlock
pushing the door open,
hanging a fat note in the entrance hall telling "Door is open";
So: you did not miss understood what the toggle does, but the whole procedure.
And no: the toggle does not disable some software feature, it just removes the OEM specific key requirement by accessing the boot loader
*Note: I know, that was quite rough simplification, and to be absolute correct: the OEM unlock toggle in Dev. Setting does in fact not physically "unlock" the boot loader. It just removes the requirement for a key in the unlocking process. However, that correspond to an open boot loader, as all attempt to enter it, will not be denied.
Click to expand...
Click to collapse
I can't argue with you. I'm not even sure where we agree and disagree.
For the sake of other users, here's the clarification:
Under Developer settings, there is a setting called "OEM Unlocking - Allow the bootloader to be unlocked".
This setting does not unlock the bootloader, it just enables the possibility to unlock. That's why it's called "Allow the bootloader to be unlocked".
No DRM keys will be deleted by toggling this setting.
After setting "Allow the bootloader to be unlocked", you can unlock the bootloader using fastboot.
When doing so, the DRM keys will be deleted and the bootloader will be unlocked.
Until you issue the fastboot command, you can't flash any unsigned code - as usual.
nilezon said:
I can't argue with you. I'm not even sure where we agree and disagree.
For the sake of other users, here's the clarification:
Under Developer settings, there is a setting called "OEM Unlocking - Allow the bootloader to be unlocked".
This setting does not unlock the bootloader, it just enables the possibility to unlock. That's why it's called "Allow the bootloader to be unlocked".
No DRM keys will be deleted by toggling this setting.
After setting "Allow the bootloader to be unlocked", you can unlock the bootloader using fastboot.
When doing so, the DRM keys will be deleted and the bootloader will be unlocked.
Until you issue the fastboot command, you can't flash any unsigned code - as usual.
Click to expand...
Click to collapse
We are not arguing here
I asked you to be more specific as unlocking a door does not mean opening it.
However - there is one important thing missing and quite profound error in your summary (beside the "unlock" wording stuff...).
Enabling the "OEM Unlocking" switch bears a high security risk. Unsigned software now can enter the TA.
In fact: you do not have to run the fastboot unlock by yourself. Any piracy software can now make irreparable damages to the phone!
basthet said:
We are not arguing here
I asked you to be more specific as unlocking a door does not mean opening it.
However - there is one important thing missing and quite profound error in your summary (beside the "unlock" wording stuff...).
Enabling the "OEM Unlocking" switch bears a high security risk. Unsigned software now can enter the TA.
In fact: you do not have to run the fastboot unlock by yourself. Any piracy software can now make irreparable damages to the phone!
Click to expand...
Click to collapse
You are saying that toggling the "OEM Unlocking" switch would make TA partition writeable (by any other user than root)?
Why would you assume that?
nilezon said:
You are saying that toggling the "OEM Unlocking" switch would make TA partition writeable (by any other user than root)?
Why would you assume that?
Click to expand...
Click to collapse
No, I'm not saying this.
But the reason for the OEM Lock is to ensure, only OEM signed software is able to be installed.
Enabling "OEM Unlocking" removes this check.
This implies:
- Nice people can now provide software to be installed -> custom roms.
- Bad people can now also install software, but to their needs.
To keep it simple: Let some evil person post any rom called "official Sony z5c Android 6.0".
Let this bad person make the appearance of this rom as any official Sony Update.
Users with the OEM lock in place will not be able to install it, as the OEM key from Sony is missing.
Users with the OEM lock removed will install it w/o any burden.
Do not forget:
Original OEM Software still is signed as original software.
To install the original software, you do not have to toggle the "OEM unlock" in the Developers Settings, as this ROM carries the original OEM key.
to install original software, you do not have to fastboot oem unlock
Removing the OEM-key check with the "OEM unlock" switch, makes the OEM-key obsolete. Hence bears a security risk.
basthet said:
No, I'm not saying this.
But the reason for the OEM Lock is to ensure, only OEM signed software is able to be installed.
Enabling "OEM Unlocking" removes this check.
This implies:
- Nice people can now provide software to be installed -> custom roms.
- Bad people can now also install software, but to their needs.
To keep it simple: Let some evil person post any rom called "official Sony z5c Android 6.0".
Let this bad person make the appearance of this rom as any official Sony Update.
Users with the OEM lock in place will not be able to install it, as the OEM key from Sony is missing.
Users with the OEM lock removed will install it w/o any burden.
Do not forget:
Original OEM Software still is signed as original software.
To install the original software, you do not have to toggle the "OEM unlock" in the Developers Settings, as this ROM carries the original OEM key.
to install original software, you do not have to fastboot oem unlock
Removing the OEM-key check with the "OEM unlock" switch, makes the OEM-key obsolete. Hence bears a security risk.
Click to expand...
Click to collapse
OMG dude. Where are you getting this?
You toggle that switch and install an unsigned ROM and I'll eat my shorts.
nilezon said:
OMG dude. Where are you getting this?
You toggle that switch and install an unsigned ROM and I'll eat my shorts.
Click to expand...
Click to collapse
You either learn this in school, or should find it s.w. in the Android docs.
And instead of flaming you should start reading and learn IT.
So be brave and toggle the switch, which by your interpretation has no meaning.
The rest of the user i can only advice to keep it locked and only enable in order to flash customs Roms.
Gesendet von meinem E5823 mit Tapatalk
@basthet:
So, if I get you right, I just need a customized firmware (e. g. a pre-rooted one), toggle that "OEM unlock" switch and install it via recovery mode? And that without loosing DRM keys? If it is so easy rooting is no problem, isn't it?
klausstoertebeker said:
@basthet:
So, if I get you right, I just need a customized firmware (e. g. a pre-rooted one), toggle that "OEM unlock" switch and install it via recovery mode? And that without loosing DRM keys? If it is so easy rooting is no problem, isn't it?
Click to expand...
Click to collapse
No, "OEM Unlock" is just a option to allow OEM unlock, so you have to unlock bootloader after enabling it (and you'll loose DRM key)
Related
Hi.
Before my question I'll write about my experience because I am sure it will help many many people.
As many of you, I always ROOT my smartphones.
Nowadays, the new phones, they come with this new technology to avoid root and other things called " OEM Lock " under the Developer's Options.
Following every step provided in the root guide for you phone, the new step to enable OEM Unlock under Developer Options
is a must!
The only thing that they don't say is that you MUST leave OEM Unlock ALWAYS ENABLED during and AFTER the root, and not only during the root
process.
Not knowing that, what did I do? Right After rooting my Samsung Note 5 I disabled the OEM Unlock. When I restarted the smartphone, it got into something called FAP Protection Black Screen where you are not able to leave not even if you try to root the phone again with the img file!
If you get in the FAP Protection Screen, like I did, despair will take over, I promise! And Google will not help you!
Is there a solution?
I found one, but not in any Google Page.
You need to download the firware img file for your phone, exactly same model,
in my case it was SM-N920G (Samsung Note 5), and for your specific country. Luckily for my phone it was not so hard to find, just hard to download (1,7GB with average 15 kB/s speed!). You will find different versions, some related to a Phone Company Operator that your country has, other related to no operator at all (sure I chose that).
After you get the firware file, just use Odin with that file to flash the phone, just like how you did to root the phone, but now, instead of using the root img file with Odin Software, you'll use the firmware file. That will not only solve the problem and give you access to your phone again, but in my case the Operator Flag disappeared and the data and apps installed miraculously were intact! I was pretty sure I was supposed to lose everything, but that didn't happen!
I'm sure what I wrote above will help many desperate people out there!
Now, my main question here:
You can never disable OEM Unlock in your life, with a rooted phone, period! So, it's really dangerous to leave the developer options enabled, allowing anyone that uses the phone to change it, even if by accident. In my case, as another example, besides rooting my phone, I rooted my father's phone too (because it was previously mine). I'd like to avoid by any means that by any chance me, or my father, disable to the OEM Unlock.
So, my question:
If I disable the Developer Option in order to "hide" it, will the changes that I did inside it remain working perfectly? I'm afraid that if I disable the developer options, somehow, it might take every option inside it back to the "default", just like it was before I enabled the developer Options, meaning in this case, OEM Unlock would get DISABLED again!
Is it safe to disable the Developer Options when OEM Unlock is Enable and MUST Remain like that?
Thank you.
Lost a night of sleep for the same problem with a Samsung S8.
This should be added to *every* mod guide.
In my case was worse too...if you root the phone and wipe data, when you open first time developer option you'll find "OEM Unlock" disabled (but I assume it's enabled at bootloader level). So when I check / uncheck it I doom my phone to lock on next restart...
how to get to boot menu on htc u12 plus, smallest width setting got adjusted wrong in developer options and power got cycled, all I can see on lock screen are 1,2 and 3 cant unlock, any ideas?
Good evening all.
I have an SGP771 which I have owned for over a year now. I have been reading up about rooting and flashing this device. At the moment I am in a quandary as to whether I can unlock the bootloader or not. When I enter. *#*#7378423#*#* into the dialer and look at the Configuration menu from the service menu the Rooting status reads as Bootloader Unlock Allowed: No. When I enter the Developer Options there is a toggle for OEM Unlocking - Allow the bootloader to be unlocked, which I have switched to on. Developer options are also switched on.
Can anyone tell me if there is any way to root and flash this device?
Many thanks.
Hello @weazil60
Did you make it unlocking your bootloader ? I ve got the same issue with my z4 tablet.
Maybe I am going to apply this guide https://forum.xda-developers.com/z4-tablet/general/guide-safe-bootloader-unlock-restore-t3362391 to see if I can unlock my bootloader that way (they did nt say there are cases it should not work) ...
I am interested in installing LineageOS but not sure if LineageOS plays well with the physical bkb50 bluetooth keyboard ...
Good evening Pierro78.
Unfortunately I received no replies and decided just to stick with using Firefox Focus to avoid ads (this was my main issue).
If you are successful with your modification please let me know.
Best of luck - weazil60.
Hi, I must send my Phone on warranty. I have unlock bootloader (official sony site), and this metod not copy my drm key, how lock bootloader?
you are confused
1.- unlock key = unlock code: is a code from sony by IMEI for unlock and relock bootloader
2.- DRM keys : "Digital Rights Management" and mainly is used with sold eBooks/PDFs and the like (and also for sold music files plus maybe even videos). Those keys are to identify your ID as to prove if you have permission to access those documents
drm keys they make the sony improvements work, like: triluminos, miracast, screen mirror, sound and camera quality, if you lose this keys poor of you, there is no way to recover them only with a new phone
if you lose the unlock key, only ask for them again
Zero-21XX said:
you are confused
1.- unlock key = unlock code: is a code from sony by IMEI for unlock and relock bootloader
2.- DRM keys : "Digital Rights Management" and mainly is used with sold eBooks/PDFs and the like (and also for sold music files plus maybe even videos). Those keys are to identify your ID as to prove if you have permission to access those documents
drm keys they make the sony improvements work, like: triluminos, miracast, screen mirror, sound and camera quality, if you lose this keys poor of you, there is no way to recover them only with a new phone
if you lose the unlock key, only ask for them again
Click to expand...
Click to collapse
but there is no way to relock the bootloader, with or without unlock key. there is no appropriate fastboot command (e.g. lock, relock or whatever...)
As far as i know, you can relock bootloader just reinstallig the original ROM with EMMA (there are some modified accessible version of this program online somewhere).
Tux111 said:
As far as i know, you can relock bootloader just reinstallig the original ROM with EMMA (there are some modified accessible version of this program online somewhere).
Click to expand...
Click to collapse
This doesn't work
https://www.teamandroid.com/2019/03/31/download-emma-sony-flash-tool/
It changed my device customisation from Singapore to Central Europe.
It didn't lock the bootloader for me either
leonaheidern said:
This doesn't work
https://www.teamandroid.com/2019/03/31/download-emma-sony-flash-tool/
It changed my device customisation from Singapore to Central Europe.
It didn't lock the bootloader for me either
Click to expand...
Click to collapse
Pretty curious, on z3 it works. Well, as far as i know, should exist a lock bootloader command for adb, search for it.
There's a "Relock" button in Flashtool by Androxyde, or you can try "fasboot oem lock"
Marek8299 said:
There's a "Relock" button in Flashtool by Androxyde, or you can try "fasboot oem lock"
Click to expand...
Click to collapse
You can't relock bootloader on xz1. If you can you will be the 1st one
I bought ANE-LX1 (P20 Lite) on June 2018 and immediately unlocked the OEM from the developer options (automatic factory reset was done then), but i never rooted or installed custom rom, recovery...etc.
All updates was normally arriving and i was updating my phone regularly (current build is: ANE-LX1 8.0.0.170(C185)).
I decided to root my device using fastboot, but when the device is in recovery mode i can see:
Code:
Phone Locked -- (in green font color)
FRP Unlock -- (in red font color)
When i try to flash using fastboot i got:
Code:
FAILED (remote: Command not allowed)
While searching online i found that Huawei decided to lock bootloader for all users (so we buy their hardware which contains an opensource software and then they lock it... PERFECT!), and it seems that the only way now is to get the unlock code by contacting third-party codes providers, pay money and they guarantee to provide the correct unlock code (pay and pray) + I will have to expose my device information.
My questions are:
-How can i see in the developer options that my OEM is already unlocked, while the recovery is not convinced?
-Do i really have to unlock it again with the code "after purchasing it ofcourse -- which i will never do" (e.g. using fastboot)?
-Is there any solution from xda experts for my case rather than buying codes and exposing my device information or stay with a Locked bootloader?
(attached evidence images for a clearer view)
drive.google.com/open?id=1e9CepsHp2O541ZKGS0E6uqS2hBwp8ry1
drive.google.com/open?id=119eCoO4Z0TvydupLIsEv-r5lsGHOD4o0
drive.google.com/open?id=1IBA1nYnw_PU25VLPTzqSLswTpGMQxuXP
Thanks in advance for your kind support.
and Thanks Huawei for putting us as a development community in this situation, where we have to pay for the black markets to unlock our own phones in an unofficial way.
Yes please, shoot some answers!
alimerdan said:
I will have to expose my device information.
Click to expand...
Click to collapse
What do you expose?
bouncingsoul said:
Yes please, shoot some answers!
What do you expose?
Click to expand...
Click to collapse
IMEI, product S/N (if i correctly understood the process, i have to provide my device info so they can extract the bootloader unlock key)
According to the information that's available, the code used to unlock the bootloader is unlocked in a very complicated way and it's basically unique for everyone. Now, I don't know how much this is true and how and why these people got their hands on the "method" of creating the code, but no one has been able to find a way that's guaranteed to work or even work at all, except for, of course, these sites that make you pay for it. I hope I'm not mistaken and forgive me if I am, but I don't think there is any way to obtain the bootloader code manually or without exposing your information to random strangers on the internet.
Need to unlock bootloader with dc unlocker to get unique unlock code. Look guide bootloader unlocking
Hi! My name is Bautista.
This is my first post well explained, I already asked this question before but I did not express myself well (I hope to do it correctly in this attempt)
My problem happens with my Samsung Galaxy A01 SM-A015M, Running on OneUI 2.0/Android 10 with 2gb of ram, a Snapdragon 439, the stock rom/firmware and 32GB of storage, from Argentina.
Things I tried so far, and didn't work for me:
Unlocking the bootloader by following the Gearallnews and Cyanogenmods guides to the letter.
When trying to unlock the bootloader with the guides on the aforementioned pages, when starting the device a sign should appear saying that the bootloader is unlocked, which did not appear.
The device started correctly in the process to configure the device the first time it is turned on, connect the wifi as the guides said. Followed by that I went to the developer options and the option "Oem unlock" was still activated and in blue (which should not happen, it should appear grayed) I heard that some Samsung devices with snapdragon processors had a bootloader that cannot be unlocked
Unlocking the bootloader using ADB AND Fastboot. (ADB detects my device fine, but fastboot doesn't detect it at all)
Using Fastboot from Windows 7, Windows 10, and Kali Linux.
Installing TWRP.
Use rooting apps. (the ones that appear on the XDA rooting page)
What I am going to with this thread, is:
Can my device's bootloader be unlocked? And if so, how?
If the bootloader cannot be unlocked, how can I root or install TWRP?
Please, if you don't understand something or need more information, let me know by replying to this thread or sending me a private message.
Look inside here.
jwoegerbauer said:
Look inside here.
Click to expand...
Click to collapse
it's the same as Gearallnews and Cyanogenmods guides, i already did that, it dont work
Like the original poster I also have a Samsung Galaxy A01 SM-A015M/DS, OneUI 2.0/Android 10, 2GB ram, 32GB storage, Snapdragon 439, stock firmware (TPA) Panama. I have gone through all the aforementioned procedure and the bootloader does not unlock. There is no bootloader unlock warning on reboot and the OEM Unlock in developer option does not grey out. Does the Snapdragon processor not allow bootloader unlock or is anyone aware of a solution. Thanks for any assistance.
@mullerh
If in Settings -> Developer Option the option "OEM unlock" is present then unlocking the bootloader obviously isn't denied by OEM/Carrier.
But you can check it at your own:
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
jwoegerbauer said:
@mullerh
If in Settings -> Developer Option the option "OEM unlock" is present then unlocking the bootloader obviously isn't denied by OEM/Carrier.
But you can check it at your own:
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
Click to expand...
Click to collapse
Thanks for your response and assistance. The command:
adb shell "getprop ro.oem_unlock_supported" returns a 1
I googled it but found no clarification but I assume that means it is supported.
Therfore there is something else that is blocking the bootloader from unlocking from the unlock mode screen and just prior to reset.
There is also no unlock bootloader warning during the reset.
The more I have Googled this problem the more it seems to indicate that many newer Samsung phones released in North/Latin America with Qualicom Snapdragon 439 processors, have the the bootloaders locked down with a new "security" feature called SecureBoot. Would be interested in getting the experience of others. Thanks
mullerh said:
Thanks for your response and assistance. The command:
adb shell "getprop ro.oem_unlock_supported" returns a 1
I googled it but found no clarification but I assume that means it is supported.
Therfore there is something else that is blocking the bootloader from unlocking from the unlock mode screen and just prior to reset.
There is also no unlock bootloader warning during the reset.
The more I have Googled this problem the more it seems to indicate that many newer Samsung phones released in North/Latin America with Qualicom Snapdragon 439 processors, have the the bootloaders locked down with a new "security" feature called SecureBoot. Would be interested in getting the experience of others. Thanks
Click to expand...
Click to collapse
Hi! Did you manage to find a way to unlock the bootloader?
I have not been able to unlock the bootloader on this SM-A015M/DS (Latin American) model with Snapdragon processor. I have done a lot of searching but found little info except articles stating Samsung had gone through some extra effort to secure their latest phones. That also means I can not root it. I was hoping to get some feedback from other who may have had a better experience,
have you tried using the twrp app to install twrp?
i had an old galaxy grand prime which was impossible to unlock, but the app worked without issues
the only thing i had to pay attention is to turn it off right before ir reboots after installing and then loading into recovery
letting the mobile startup without doing this overrieded the command to install twrp
Thanks for your response. It is my understanding (I could be wrong) that before TWRP can be installed the Bootloader needs to be unlocked. The older Samsung usually allowed the Bootloader to be unlocked even if there was difficulty in rooting them. It appears that some of the newer Samsung's with the Snapdragon processors have added an additional security feature called SecureBoot which blocks the Bootloader from being unlocked.
Does anyone have a definitive answer for how to turn the bootloader on? I recently purchased a SM-A015M/DS and didn't have issues with the OEM bootloader option appearing in the options. But when I enter fastboot mode it says my device status is locked. I can't work out if that means it's locked or not.
For what it's worth, when I flashed the firmware onto the phone in the first place, I had to enable the developer option manually- I did this by booting into download mode and then a long press on the volume up button when prompted by the menu. I don't see why this wouldn't work for other devices. There are youtube videos that explain in greater detail if you haven't tried this yet.
Newiser7 said:
Does anyone have a definitive answer for how to turn the bootloader on? I recently purchased a SM-A015M/DS and didn't have issues with the OEM bootloader option appearing in the options. But when I enter fastboot mode it says my device status is locked. I can't work out if that means it's locked or not.
Click to expand...
Click to collapse
Enabling OEM unlock option in Developer options does NOT UNLOCK the bootloader. Once you enable the OEM unlock on your device, the unlock ability flag is set to 1, which will allow users to use the fastboot flashing unlock command, the command what starts the "unlocking the bootloader" procedure.
FYI:
After the command is executed, you will see an option for bootloader unlock on your device’s screen.
Use the volume buttons to move up and down and select the option to unlock the bootloader.
A prompt will pop up, asking for confirmation. Use the power button to confirm your selection as yes, and you are done.
The phone will now reboot to fastboot mode. Enter the command “fastboot reboot,” and it will boot into PC.
jwoegerbauer said:
Enabling OEM unlock option in Developer options does NOT UNLOCK the bootloader. Once you enable the OEM unlock on your device, the unlock ability flag is set to 1, which will allow users to use the fastboot flashing unlock command, the command what starts the "unlocking the bootloader" procedure.
FYI:
After the command is executed, you will see an option for bootloader unlock on your device’s screen.
Use the volume buttons to move up and down and select the option to unlock the bootloader.
A prompt will pop up, asking for confirmation. Use the power button to confirm your selection as yes, and you are done.
The phone will now reboot to fastboot mode. Enter the command “fastboot reboot,” and it will boot into PC.
Click to expand...
Click to collapse
FYI:
Samsung devices do not support fastboot command, you use Odin or Heimdall to flash what you need.
The answer you provide is misleading
mullerh said:
FYI:
Samsung devices do not support fastboot command, you use Odin or Heimdall to flash what you need.
The answer you provide is misleading
Click to expand...
Click to collapse
You are right: I was mistaken.
Thank you for clarifying that the bootloader is still locked. But how can I unlock it? Odin will let me flash the files, but I keep getting AUTH errors when I try to flash magisk patched files to root the phone. I'm assuming this is because the bootloader preventing the files from transferring. Is there a way to unlock it using ADB without fastboot, or a way using Odin? It seems crazy that unlocking the bootloader is enabled but I am still unable to actually unlock it.
I have also tried the CROM Service app (couldn't get it to install on my phone, error 3003 with ADB install), as well as the bootloader unlock method where I boot into download mode, hold the volume up key, and unlock the bootloader that way. I have done the latter at least 5 times and the bootloader is still locked. Ridiculous.
This prop apparently only confirms that the phone supports being unlocked, not that it is actually unlocked.
adb shell "getprop ro.oem_unlock_supported"
Check a few others, also see the official docs.
sys.oem_unlock_allowed
androidboot.flash.locked (the docs say this, but I think Samsung uses something different)
ro.boot.flash.locked
ro.boot.other.locked
Maybe also check these:
ro.boot.verifiedbootstate
ro.boot.veritymode
The docs indicate that the verifiedbootstate should be orange if the bootloader is unlocked. I don't know much about it, though.
You can always use grep to search for any interesting values, like "lock" or "boot" or "flash":
adb shell getprop | grep lock
adb shell getprop | grep boot
adb shell getprop | grep flash
Maybe report any interesting values you have with and without OEM Unlock checked. Maybe someone smarter than us will find it useful.
I would really like to see an A01 root happen, it's such an affordable and accessible device for all sorts of things. Great as a backup device or for a project. You think someone would've released some goods for it by now. It's been out all year.
And for the 16GB model, it's absolutely terrible because Samsung eats up so much space, then has the nerve to remove the Adoptable Storage feature. So even if you get a fast SD card, you can't install apps on it. Other than that, it's a perfectly serviceable phone. I would think with root we could get Adoptable Storage working.
To summarize what has been previously stated the Samsung Galaxy A01, version SM-A015M/DS is the Latin American version of this cellphone. This cellphone has a Snapdragon processor. This version is very similar to the versions (also Snapdragon processors) used by some US Carriers. Many current versions of Samsung cellphones have an additional security feature called "SecureBoot" which blocks bootloader unlocking. Some say this features was added at the request of US Carriers
The Asian version of the A01 has a Exynos processor. It is my understanding that with these it is very easy to unlock the bootloader and root the phone using the usual conventional methods. The Asian variant unfortunately does not cover some of the wireless bands used in the US/Canada/Latin America.
I have a Samsung Galaxy A01 SM-A015M/DS, OneUI 2.0/Android 10, 2GB ram, 32GB storage, Snapdragon 439, stock firmware (TPA) for Panama.
My research indicates that there is not yet an available bootloader unlocking and easy root method for this (A01) phone. For some other current Samsung models there does appear to be a method of flashing certain custom ROMs without a bootloader unlock but they appear to come with problems which include loss of some cellphone functions and a reduction in the charged battery life. So it seems hardly worth it.
It also appears that it is current well known that all current Samsung phones with Snapdragon processors have not allowed bootloader unlocking and rooting due to the enhanced security feature.
At this time we can only complain and/or not buy any additional Samsung phones
Perhaps with time skillful developers will come up with a method to solve this problem with this inexpensive A01.
Please provide any new or updated info if you have it.
Any solution for rooting Galaxy A01 ?
I use A015f region SER (Russia) In Russia, too, the device is locked (bootloader) of course, give any solution
One thing I know is that a fellow SM-M015f, which is almost identical, which is with the same Snapdragon 439, except for the battery capacity and screen size and gigabytes of internal memory, successfully unlocks and gets Magisk root.
this phone actually has a fastboot mode, from recover mode select reboot to bootloader, it will boot to fastboot mode,but ive still been unsucessful in getting fastboot mode to work, devices manager reports device error,
I can start the unlock proccess.
But after it is done and the data is wipped,
It keeps locked.
Sad