Bootloader Unlock Allowed No

2 views
Skip to first unread message

Práxedes Jamal

unread,
Aug 3, 2024, 3:33:08 PM8/3/24
to ifmipare

Just realized something, the tablet belongs to the university and unlocking the bootloader will void any warranty also some apps and services will no longer work, and the DRM keys will be gone forever.

This part it's my opinion, I can't see any reason to unlock the bootloader other than use the tablet in a way that the University doesn't want you to use it, the solution buy an unlock tablet and you'll be able to unlock the bootloader, but do tell us why is it necessary to unlock the bootloader and or root the device?

To access the VPN (cisco) of the university a proxy needs to be used. I did not find a working (non-root) app yet which can do this. Any suggestions since rooting the device is no option because of the looked boot loader?

On a bit of a tangent, I can just see the absolute that will ensue when Sony decides to shut down its mobile division, leaving all of these "bootloader unlock allowed: no" devices any way to update to the latest most secure version of Android. To me, hardwiring a bootloader lock into a supposedly developer friendly device is completely moronic, and is definitely not "developer friendly" as Sony claims themselves to be.

I actually decided for Sony because of the good support for developers which I read in other forums. I like to control my devices myself, e.g. by using, cyanogenmod. The divice is not a branded device. It is a totally SONY issue and I am too would like to hear directly from SONY why they decided to lock the device.

I had the same issue with the locked bootloader. Have you got the "my Xperia" app enabled? If so, try to disable it and enter the Service Info to check the bootloader unlock status. Mine has changed to "Yes". I actually managed to fastboot a custom img file but I can not enter recovery mode in order to install superSU.

thank you for this valuable advise. Getting SU to work would be essential for my problem though. The CISCO android client cannot configure proxies. Without this, no VPN :-(. Anyway, thanks for your support. Getting the bootloader unlocked is the first step. Will try it out.

I have recently bought my xperia m4 aqua from my carrier(Telenor Bulgaria). I tried to unlock bootloader, but fastboot oem unlock(with the code provided from sony site) gave me command not allowed(I've checked enable oem unlocking in developer settings). Then I checked and in Service Info it said "bootloader unlock allowed: no" . After reading in internet they said that is because carrier locked the device, but I wrote an email to my carrier and they said they haven't done such a thing. So this means it has been locked by sony, not my carrier. What can I do now to unlock bootloader? I tried flashing ftf for Switzerland via FlashTool, but status is the same.

Hello, I know many threads exist with the same problem. However, my question is different. It is said that the operator can decide whether to lock bootloader. Now, I contacted them and they said they don't do such things, so sony has locked the bootloader for unknown reasons. Now, my contract has ended, so even if my carrier had locked the phone, I should be able to unlock it. I found this thread(which is too old now) - -developers.com/xperia-u/general/dev-reloading-kernel-rebooting-t2053466 There have been guys who have managed to solve the dreaded "bootloader unlock allowed: no" problem, but for old devices. Now, I have xperia M4 aqua and wanted to ask, can the sony developers do something similar? From what I gathered from the thread the problem is a code which should be overwritten, but the key for generating this code is only available to sony developers. I am willing to do whatever is required, just please help me unlock my bootloader!

lol everything is about this app "my xperia" just disable it there nothing to do with carrier or sony
here how to do
thanks for the guy who mentioned about that app he is a genies i was looking for hours but didnt thought about inter app

To get rid of the bloatware you need to root your phone and flash the bootloader. If the bootloader is locked it is only a matter of hacking it. You have the hardware in your hand so it is possible...

I understand that you might assume that, but that's not accurate; The only way to do so is to replace the motherboard, which will cost almost the same as a new device. Let's not spread misinformation, keep it friendly, constructive and helpful.

I used Unlock Ninja for a Samsung a few months ago, and it was successful, and their service and communication was good, and the price was way less than others, (I think under $20, but it took about a week.

Would be interesting to know which Telco device locked to as certainly from UK perspective always been a problem that carrier branded device(s) previously had locked bootloader. Should you wish to flash generic firmware be aware that Androxyde Flashtool does carry .fsc script for Xperia 10 I4113 Dual Sim

Got a new Xperia X via Amazon.de . Followed the guides. Updating Android to the latest andgreatest version is really a lengthy process. Then I tried to do the unlock instructions, and here comes the surprise:In the service menu:Service info > Configuration > Rooting Status it simply says "No".

Please note that SIM lock is a totally different thing from an unlockable bootloader. You'll probably find a lot of simlock-free retail devices, which may be some refurbished operator devices with an unlockable bootloader. I received one myself from Amazon.

@ghling on Amazon you mean a phone sold and shipped by Amazon? or by a third party seller (marketplace)? I did also buy a phone on amazon but the box is still sealed as I was waiting the release before installing it

Sony's instructions are pretty clear: If the service menu does not say "Bootloader unlock allowed: Yes" then you can't unlock the bootloader (regardless of the "OEM unlock" setting in der developer menu). I'm not aware of any possibility to circumvent this "security feature". I know this sucks (because I also got a locked device from Amazon and had to sent it back), but I'd rather send it back and buy it somewhere else than risking bricking the phone with some obscure "unlock method" (if there is any).

In my case, the "my Xperia" was never activated. I never intended to use the Android system. The "my Xperia" app needs google accounts and other stuff. So my conclusion -> I got a "Bootloader unlock allowed: No" phone. I will send it back to Amazon (BTW, I realized that I got it from "Smart Tech Electronics" shipped by Amazon). -- Sending it back ordering the next one. Though it feels stupid since you never know what you will get.

In Sony's unlock instructions is stated:If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.

It's worth a try to disable the "my Xperia" app and see if that changes anything (and fully unlocks the phone). But the xda link only points to some website asking money to provide you with some images that should unlock the phone!? That's what I meant with "obscure". I definitely wouldn't use such a service (and pay additional money for a feature that should be available from the start) if I can just send the device back and get a full featured one.

The phones you are talking about have provider branding and they are not prepared for unlocking, even if it possible. Amazon or media market or similar do not sell branded phones. Ebay sellers mostly sell these kind of phones, these mostly cheaper. The mistake here is not on Sony's responsibility, providers only buy from manufactures who gave them the power to rule about the devices.

I am also having issues with locked boot loader - I was not aware of this issue when ordering my phone from my local outlet. Reading through this post, it looks like there is no way of solving this. Huh! Found this 1302-7210_R5D customization thing in the sim-menu.

So, I have more or less wasted 250$ on nothing (+the Jolla license fee)! I do not think it will be possible for me to return the phone after unpacking the hardware, ect. (not to mention the hours gone into doing OTA upgrades on the Android). Why should the dealer allow me to return the phone when there is nothing wrong with it?!

I will also use this opportunity to criticize the quality of the upgrade instructions - it sure looks like they have been written by engineers to engineers (the worst part is that I am one myself :-)). Well, I managed to get through to step 4 after reading the the guide again and again - and just to realize that I have wasted my time because of the boot loader issue. I still do not get section 1 option A/B?! Whats up with the Emma tool - is it just a short-cut to get the newest version of Android or what?

Try to return it. -- E.g. I returned mine. I bought it through Amazon. Though I noticed later that I actually bought it from "Smart Tech Electronics" and it was only "handled" by Amazon. However with that I can take advantage of Amazon's return policy. That is, I can give it back if you do not like it. It worked. I will get my next one in a day. From Amazon and really form Amazon.

I'd try returning the phone. Buying a device full price at a retailer, I would expect to receive a phone without any restrictions - the unlockable bootloader of an operator device clearly is a big (unexpected) restriction from my point of view. The fact that you found out about that only now during the attempt to flash SFOS does not change that the vendor sold you a somewhat crippled device. Of course I don't know the return policy of your dealer (this may make things easier or harder), but I'd start by kindly asking to exchange the device for one which allows to unlock the bootloader (now you know how to check that).

I went to install a Debian instance on Windows Hyper-V client in Windows 10. However, when I attempted to start the VM, it would not boot from the cd. Eventually the Hyper-V BIOS gave me a failure to start screen that listed boot devices and their status. The status of the SCSI-DVD device said: "The unsigned image's hash is not allowed (DB)".

c80f0f1006
Reply all
Reply to author
Forward
0 new messages