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.
Hi, happy new year! : )
i bought a used Xperia 10 Plus (dual SIM) with Android 10 and wanted to install Sailfish on it. But i am unable to unlock the bootloader as described in your guide: jolla[DOT]com/install-sailfish-x-xperia-10-windows/
Try #2) Unlock bootloader with general Sony instructions from here, hoping that the Sailfish tools are just incompatible due to the android version: developer.sony[DOT]com/develop/open-devices/get-started/unlock-bootloader/how-to-unlock-bootloader/
i came across these articles before. The reseller originally stated that the device was without branding and locks and if there is one it is not visible through the interface. But to be sure i sent the reseller an e-mail asking specifically for this. i hope they have an answer.
Although this resource concerns XA2 it shows the same sort of chain of issues, which were eventually resolved for OP: _xperia_xa2_bootloader_unlock_fails/
I would have a look at Flashtool as contains all necessary drivers:
I looked at similiar topics in this forum, and wanted to flash my sony with the jolla. I got my unlock code, followed the instructions given here -windows-instructions-xa2/and tried to unlock the bootloader but i received the error: FAILED ("command not allowed")
The CDA code ("Cellular Digital Accessory") should tell for what market are your phone is customized to. The code is in form of 1312-8563 and should be on the package the phone came in. This code should tell you if unlocking is (dis)allowed.
I understand it should be only certain operators on whose devices the unlocking of the bootloader is not allowed. Apparently in these cases you should be able to install the firmware (?) of a CDA version that does have unlocking allowed on your device, and you can proceed with the unlocking after that.
Just a little update: after I did not manage to get my xperia running again with the advice and instructions i've received from the forum here, I decided to take my chances and send in my phone to sony. sony's website points out that you loose your warranty if you unlock the bootloader and also some of you pointed out that could be a problem. but i figured I could argue I only tried to unlock it, but did actually not manage :)after all Sony sent me back my phone repaired and without any comments or complains.
since this morning i don't even get the sony loading screen anymore. when i turn on the phone i get the message that "this device is corrupted and can not be trusted anymore. it will not boot" (not the exact words, but almost) ..and it shuts off after 5 seconds.
but regarding your advice. does this help me if my bootloader is not unlocked? because since i get the message "command not allowed" when i run the "fastboot.exe oem unlock....". or do i interpret this wrong?and/or can i just ignore it and anyway run the flash-on-windows.bat?
yes, i used that fastboot command line with my unlock code i got with my imei number. and the message i get is "FAILED: (remote: Command not allowed)" .. that means that the bootloader is not unlocked .. (at least that's what I assume, and what others in response to my post also suggested).
At first, I thought I could reflash it with a clean CyanogenMod image.This would free my phone of all the Sony bloatware, and save some precious memory I'm sure.But at the moment of this writing, the best I could find is an unofficial ROM,and it's still under development. Some things don't work yet.For those interested it's available here:
-cyanogenmod-12-1-for-sony-m4-aqua/
So I thought the best was to stick with the official Sony firmware,and to uninstall all the bloatware. But you can't do that out of the box.The stock apps can't be uninstalled, only disabled. They still use memory.The reason, as far as I understand, is quite simple. Stock apps are installedon the system partition, and this partition can't be modified without having root access.For a quick overview of Android partitions scheme, refer to:
-partitions-explained-boot-system-recovery-data-cache-misc/
Since I'm a very newb with smartphone in general, and Android in particular,it took me quite a while to understand the whole procedure needed to removethis stock apps. I loosely followed this tutorial:
-developers.com/m4-aqua/general/tut-blu-twrp-root-xperia-m4-aqua-t3238962
With Marshmallow comes a feature named Adoptive Storage,which allows you to use part of your SD-Card as system storage. It's all transparent to the system,so it's really an extension of the internal memory.
But cheer up, it's not that hard to do, and every Android hacker has to start from here I guess.There are hundreds of tutorials on the net, but most of them are very quickly written,and only describe the steps without explaining much. But I like to speak and explain stuff,so hopefully here you'll get to understand what you're doing.
So we're gonna do all these things to your Android device. I have a Sony Xperia M4 Aqua,but I guess the same steps work more or less for most of the Android devices.You just have to ensure, each time, that you're device is compatible with the tools you're using.
At first, you should know, right now, that unlocking the bootloader will wipe your phone.Erase all the data. That's it. It may not be obvious at first, since there seem to beno relation between the bootloader and the data on your phone. However, from a securitypoint of view, it makes sense. Here's a good discussion about that:
First, turn on USB debugging by going to Settings > Developer options and click to enable USB debugging.As of Android Jelly Bean 4.2 the Developer options are hidden by default.That's why you don't see it anywhere...To enable them tap on Settings > About Phone > Build Version multiple times.Then you will be able to access the Settings > Developer options.
Press (and keep pressed) the volume up button, and connect the device to your computer with the USB cable.This prevent the device from starting normally, instead it will just sit in the bootloader mode and wait.The LED next to the USB connector turns red, then blue, and remains blue like that.
We need a custom recovery software to install a superuser app.There seem to be many custom recovery for Android. We have to pickup one of them.We're gonna install TWRP, as it seems to be fairly popular.
SuperSU is available from the Google Playstore, so you could install it like any other app,however if you do so you will only have the frontend. The backend (the su command)can't be installed that way, it needs to be installed using a custom recovery software.
Now, let's boot your Xperia M4 in recovery mode. To do that,I had to turn off the Xperia, then turn it on by holding power buttonand volume down button simultaneously. Doing that, the phone boots inrecovery mode, and we get a nice screen from TWRP.
Before doing anything foolish, I backed up my fresh Android on the SD-Card with TWRP.You should do the same, since now we start doing things that may break the system.Well, it's no big deal, I guess you can always re-install a clean Sony Xperia M4 firmwareif you mess up the phone. But backing up with TWRP saves time.
Yeah, that's a bit disappointing... Well we can rejoyce by remembering that we also saved some RAM,therefore some CPU, therefore some battery life. But how much exactly, no idea. Probably very little.
Sony Mobile is one of the most open source and developer friendly OEMs out there with programs like Hero Open Source Developer and Sony Open Devices. Sony has published guides on how to build the Linux 4.4 kernel or the latest Android release, and even how to unlock the bootloader of their devices. Unfortunately, unlocking the bootloader of any Sony Xperia device leads to a lot of undesirable outcomes. For instance, the camera is totally broken, resulting in nothing but green pictures. Other software features like Sony's video and audio enhancements are also broken, even if you stick to the stock ROM. Losing Sony's video and audio tweaks are one thing, but having to deal with a broken camera is a trade-off that many are unwilling to make. Fortunately, it seems that the Android Pie update no longer breaks the camera on Xperia devices with unlocked bootloaders.
4a15465005