I have the same problem. Your career force-locked the phone, meaning that you cannot unlock it normally, only temporarily (that means when you do it the second time it says OKAY but when you reboot the device its gonna be locked again)
Some careers (like mine, Orange) trick the user, they say Unlock Allowed: Yes. It's actually kinda true, because you can temporarily unlock it, but thinking about it our situation is the same as if that message would say No. If there would be test points on the E1 maybe we could unlock it like the older devices, but I'm not sure as it's quite old. Maybe if someone can make a hack to set the flag of locking to unlocked or make a 2ndinit ability to load a second kernel on the bootup process.
You need to reflash the firmware. Kizoky will sure add that later on.
If you brick your phone, you can always reflash the Firmware, or use the backup method which is found in PhilZ recovery.
As far as I know if it's says Allowed: Yes, as long as you obtain to code to unlock, along with using xperia flasher or fastboot tools to correctly unlock then it's should stay unlocked. An unlock allowed: No should not allow a request for unlock code via sony developer world site.
I made a backup zip, that way if you use fastboot tools to flash the boot.img, then the kernel has the philz recovery 6 that can install the clone rom.zip file.
Some careers like Orange in Slovakia trick the user(or use a different force method) that the bootloader can be unlocked by saying Yes in the service menu, but cannot unlock with the Sony Bootloader Unlock code, due to Command did not succeed error. I think they either have a custom code, or as they said in the email I sent to them: we have something Orange(or other career-related) firmware on our device that blocks unlocking. Or maybe it's just a 0-1 flag. (like ForceLockUnlock=1)
I hate companies who force-lock their phones. I can understand why they block other SIM cards, but come on, let the bootloader unlocked for geeks/devs
I think there's some kind of a 'flag' or something in the TA that blocks us. Or maybe it's something /dev related. If the test point unlocking would work, I would be very happy. Though I don't think it would work with newer phones and it's old.
Well I have three xperia E1's that I obtained off network along with this E3 that are all sim unlocked and fully bootloader unlockable. All the E1's are rooted with jelly bean or kit kat flashed via xperia flasher, with bootloader unlock: Yes. I find the 4.3 jb build to be the most responsive for D2005 handsets.
Jelly Bean for the Xperia E1 (the official Sony one) is way too much unstable. KitKat is more stable. I've had random reboot issues and freezing issues (especially when playing games) on JB, while everything is much better on KitKat (there are still some lags and it takes some time to boot up but everything else is fine.)
You can decrease the boot time, If you delete the unnecessary apps (Google+, Google Books, etc..) And the apps you can't delete, or you are afraid, you can just disable them.
Well I rarely play games on any of my devices, however you are correct in that Jb does reboot more than kitkat does. When trying to control the kernel better for jelly bean, I did encounter freezing, however once I got the correct configuration it was fine.
I would love to say everything is better, however rooting is more of a challenge for some of the kitkat builds and installation of supersu was more tricky/ time consuming. Have to delete apks to speed up kitkat too.
I hope too. But we'll not get an Official Lollipop provided by Sony
