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.
Hello, yesterday I got my xperia x to get on Sailfish OS, but it turns out Bootloader unlocking is not allowed on this device. Is there anything I can do, flashing a certain firmware, or anything to get the bootloader to unlock? I am of course getting the "command not allowed" fastboot error, and I've enabled OEM unlocking in dev settings.
Check your fastboot/flashmode drivers.
I did, they seem fine. I followed the instructions that jolla provided. I even tried a different USB port. I'd really like to avoid returning it if it's possible.
Are you sure that bootloader unlocking is not allowed? If that's the case, then you can't do anything but return it. Try not to buy carrier specific devices for bootloader unlocking.
I have Sony Xperia X (F5121) bootloader current unlocked and I followed this Article.
https://www.getdroidtips.com/unlock-bootloader-sony-xperia-x-f5121f5122/
Why not go straight to the source, the Sony unlock bootloader page? Fill in the required info and if they send you the unlock code your good to go and follow the directions on the page, if they don't then you know it can't be in theory...
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
I am sure if you have found this forum, you are also looking for the ability to root the LG K92. Unfornatuely, it looks like as it stands currently there is no known way to root the K92.
There was one glimmer of hope on another thread https://forum.xda-developers.com/t/root-aquired.4253159/ but it looks like that may have been a dead end as well.
Am I understanding, unless there is a exploit to gain root access from the Android 10 OS, the only possible way would be to get the bootloader unlocked. I have a K929AM (LG K92 from AT&T) and, as I am sure you already know, LG does not have that on the supported list for bootloader unlocking. In fact, it looks like all of the K series phones do not have bootloader unlocking supported. When you try to boot to Bootloader, it boots into the OS and if you boot to fastboot, you get fastbootd where the OEM unlock does not even appear to work.
According to https://lgk20.com/lg-k92-5g-root-bootloader-unlock-twrp-custom-rom-lmk920am/ (scroll to the bottom) we would expect to see a "bootloader unlock page" but I am not even sure if the LG K92 has one of these and, even if it does, if it would be accessible.
Does anyone have any suggestions on any unsupported methods on how to unlock the bootloader on this phone? I would be happy to test anything at this point. If we can somehow figure this out, this method may work on other K-series devices which would be a big win. So far, the only menus I can access are FASTBOOTD and Download Mode.
To add to this, it looks like it is possible to access the Bootloader (bootloader unlock page) from the LG K20. https://lgk20.com/lg-k20-plus-unlock-bootloader-metropcs-mp260-t-mobile-tp260/2/
I am wondering if it is possible to somehow force the K92 into this menu even if short circuiting something on the board.
Anyone have any ideas?
After rooting my Z2 and backing up the TA partition, I've discovered that the bootloader is not unlockable (it's a Vodafone branded device).
Is there a nefarious way in which to bypass this? I understand that the whole point is to keep it locked, but it's an old enough device so I may have missed where it's possible.
Otherwise what are my options for an up-to-date custom rom? As indicated, I've already achieved root and have TWRP installed. I tried flashing Lineage via recovery but got an E: unknown command [log] error.
I'm in the same boat unfortunately. I bought a used phone that had Vodafone UK. It was marked as SIM-unlocked, and that seems to be true; the service info doesn't show any filled checkmarks nor counters in SIM lock information. However, bootloader seems to be locked forever - flashtool reports "Bootloader status : NOT_ROOTABLE" and phone's service menus also say that rooting status is "bootloader unlock allowed: no".
I wasn't even aware there are Sony phones that are not SIM-locked but are still boot-locked without any way to unlock.
I would really want to upgrade from Android 6 to at least 7 because there are some specific apps that work only from A7. Wondering if there is any custom ROM that would run on stock A6 kernel but with everything else from A7? It should be possible to install such a ROM even on a bootlocked device, right?
Since posting I've discovered some answers. The bad news is that, no, custom ROMs are limited without an unlocked bootloader.
The potentially good news is that you can pay for an aftermarket SIM unlock, which has the side effect of also allowing the bootloader to be unlocked.
I've not tried it myself, but do a search for "Sony cable unlock credits" for some leads.
Yea I also am stumbling upon this same news, in my city there are some shady areas so I will ask around and see if anyone is capable of doing it and will let you know.
So far my phone has bootloader locked, sim locked with 3 attempts left so I will work on unlocking those and then rooting the phone and digging deep after
Lets cross our fingers that somethings comes up
So far online , I find only old videos and outdated information, websites down and nothing else.
One thing is for sure, if your bootloader can be unlocked, you just go to sony official website and follow their instructions and its free and easy,
But if it says ""bootloader unlock allowed: no" then...lets see what can we do.
Hey I am willing to pay, why not if its going to unlock the bootloader 100%