Related
This thread has been moved to http://forum.xda-developers.com/xperia-e1/general/xperia-e1-rooting-flashing-recovery-t3051225
Xperia E1 has his own Subforum now, Thank you XDA!
If any moderator sees this, please close this thread!
Hello there!
First of all really thank you for making this topic, it will really help people who wants to customize their Xperia E1.
I really appreciate your action.
Secondly, I wanted to ask more help with the bootloader unlock.
I do exactly what you do but it always comes the following result;
First, when I click on unlock it gives me Failed error.
When I click on unlock for second time, it gives me Okay, meaning that successfully unlocked.
After, I'm booting into system but it stack at the boot animation.
Some people called this bootloop but I don't know what to do to fix it.
Flashing again a stock firmware fixes this but no unlocked bootloader at all.
Repeating this will give the same results.
I would like some help on it, I remember somehow I had successfully unlock the bootloader without stack at boot animation.
At service menu was saying boot loader unlock: Yes
Instead of bootloader unlock allowed: Yes
I'm able to give any information about my phone so we can fix the problems, I'm not going to buy another phone anyways
Sent from my D2005 using XDA Free mobile app
Kizoky said:
Now hold the following buttons on the phone: POWER+VOLUME DOWN
Do this until the LED turns GREEN.
Great, the phone is now in Flashmode!
Click to expand...
Click to collapse
You are supposed to VOLUME DOWN + CONNECT USING USB and you should NOT hold the power button.
---------- Post added at 10:11 AM ---------- Previous post was at 10:09 AM ----------
GiorgosGRN said:
Hello there!
First of all really thank you for making this topic, it will really help people who wants to customize their Xperia E1.
I really appreciate your action.
Secondly, I wanted to ask more help with the bootloader unlock.
I do exactly what you do but it always comes the following result;
First, when I click on unlock it gives me Failed error.
When I click on unlock for second time, it gives me Okay, meaning that successfully unlocked.
After, I'm booting into system but it stack at the boot animation.
Some people called this bootloop but I don't know what to do to fix it.
Flashing again a stock firmware fixes this but no unlocked bootloader at all.
Repeating this will give the same results.
I would like some help on it, I remember somehow I had successfully unlock the bootloader without stack at boot animation.
At service menu was saying boot loader unlock: Yes
Instead of bootloader unlock allowed: Yes
I'm able to give any information about my phone so we can fix the problems, I'm not going to buy another phone anyways
Sent from my D2005 using XDA Free mobile app
Click to expand...
Click to collapse
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)
I got an email from my career, and they say the reason why I cannot unlock it is because of the firmware. I'm starting to think they don't know a thing about bootloaders.
God..So we will never unlock the bootloader of force locked E1 devices?
Edit: I read that force locked bootloaders come with the message at service menu:
Bootloader Unlock Allowed: No
My phone says:
Bootloader Unlock Allowed: Yes
Any ideas? Am I wrong?
Sent from my D2005 using XDA Free mobile app
GiorgosGRN said:
God..So we will never unlock the bootloader of force locked E1 devices?
Edit: I read that force locked bootloaders come with the message at service menu:
Bootloader Unlock Allowed: No
My phone says:
Bootloader Unlock Allowed: Yes
Any ideas? Am I wrong?
Sent from my D2005 using XDA Free mobile app
Click to expand...
Click to collapse
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.
I think it would be possible, but it would require a lot of work and a large knowledge of our device (in a deeper meaning)
My phone says:
Bootloader unlock allowed: No.
So i can't unlock?
What should i do if i stuck on bootloop with unlocked bootloader, for some reason?
Need tutorial for this..
Thanks.
mire777 said:
My phone says:
Bootloader unlock allowed: No.
So i can't unlock?
What should i do if i stuck on bootloop with unlocked bootloader, for some reason?
Need tutorial for this..
Thanks.
Click to expand...
Click to collapse
You need to reflash the firmware. Kizoky will sure add that later on.
mire777 said:
My phone says:
Bootloader unlock allowed: No.
So i can't unlock?
What should i do if i stuck on bootloop with unlocked bootloader, for some reason?
Need tutorial for this..
Thanks.
Click to expand...
Click to collapse
If you brick your phone, you can always reflash the Firmware, or use the backup method which is found in PhilZ recovery.
I'll do a tutorial on this too soon
So..uhm.. Any chance I can root my phone without bricking it with this bootloader stuff ?
Was rooted using Kingo, latest update (20.A.1.2.14) removed root, prevents kingo and all other apps from rooting again.
GiorgosGRN said:
God..So we will never unlock the bootloader of force locked E1 devices?
Edit: I read that force locked bootloaders come with the message at service menu:
Bootloader Unlock Allowed: No
My phone says:
Bootloader Unlock Allowed: Yes
Any ideas? Am I wrong?
Sent from my D2005 using XDA Free mobile app
Click to expand...
Click to collapse
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.
---------- Post added at 08:09 PM ---------- Previous post was at 07:55 PM ----------
Kizoky said:
If you brick your phone, you can always reflash the Firmware, or use the backup method which is found in PhilZ recovery.
I'll do a tutorial on this too soon
Click to expand...
Click to collapse
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.
image45 said:
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
Click to expand...
Click to collapse
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)
How unhelpful of them, that's why I started obtaining off network handsets from 2010 on wards. SIM UNLOCKED ? and fully bootloader unlockable.
image45 said:
How unhelpful of them, that's why I started obtaining off network handsets from 2010 on wards. SIM UNLOCKED and fully bootloader unlockable.
Click to expand...
Click to collapse
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
Kizoky said:
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
Click to expand...
Click to collapse
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.
---------- Post added at 02:54 PM ---------- Previous post was at 02:52 PM ----------
Also @Kizoky how are you planning to add more tutorials? Are you going to edit the first post or add a new post each time?
xezrunner said:
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.
---------- Post added at 02:54 PM ---------- Previous post was at 02:52 PM ----------
Also @Kizoky how are you planning to add more tutorials? Are you going to edit the first post or add a new post each time?
Click to expand...
Click to collapse
I'm gonna do It tomorrow
Kizoky said:
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
Click to expand...
Click to collapse
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.
image45 said:
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.
Click to expand...
Click to collapse
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.)
The only thing I loved about the JB build was the Notification Shade and the fast bootup time.
xezrunner said:
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.)
The only thing I loved about the JB build was the Notification Shade and the fast bootup time.
Click to expand...
Click to collapse
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.
xezrunner said:
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
Click to expand...
Click to collapse
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.
xezrunner said:
everything is much better on KitKat (there are still some lags and it takes some time to boot up but everything else is fine.)
The only thing I loved about the JB build was the Notification Shade and the fast bootup time.
Click to expand...
Click to collapse
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.
Hope we do get a stable lollipop ROM for the E1.
image45 said:
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.
Hope we do get a stable lollipop ROM for the E1.
Click to expand...
Click to collapse
I hope too. But we'll not get an Official Lollipop provided by Sony
We'll have to wait for experienced Devs.
Well, hello to everyone. I bought Sony Xperia Z3 and bought code to unlock it for all sim cards and it works. When i visited Sony's site for unlocking bootloader i came across this post:
In your device, open the dialler and enter *#*#7378423#*#* to access the service menu.
Tap Service info > Configuration > Rooting Status. 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.
Well, my device cannot be unlocked because it says No..
so what can i do to unlock it?
Info
mi-smozadrani said:
Well, hello to everyone. I bought Sony Xperia Z3 and bought code to unlock it for all sim cards and it works. When i visited Sony's site for unlocking bootloader i came across this post:
In your device, open the dialler and enter *#*#7378423#*#* to access the service menu.
Tap Service info > Configuration > Rooting Status. 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.
Well, my device cannot be unlocked because it says No..
so what can i do to unlock it?
Click to expand...
Click to collapse
it s better not to try it
it can hard-brick ur device if attempt to unlock bootloader
:good:
Geeks Empire said:
it s better not to try it
it can hard-brick ur device if attempt to unlock bootloader
:good:
Click to expand...
Click to collapse
What? Do you know what you are taking about..
Anyway, if the service menu says you cannot do it then it is impossible to unlock it.
Info
gregbradley said:
What? Do you know what you are taking about..
Anyway, if the service menu says you cannot do it then it is impossible to unlock it.
Click to expand...
Click to collapse
yeah i knew it but if user want to use some tools or something like this it can destroy the phone
:good:
i just need to know what to do to unlock it?
Why unlock it? You will lose your DRM keys if you do..
mi-smozadrani said:
i just need to know what to do to unlock it?
Click to expand...
Click to collapse
For your device it is not allowed, so you can't unlock the bootloader.
/I've read some threads about trying to unlock the bl although service says "no" on other Devices like z Ultra:
It's not impossible to unlock the bl with official method if you know your device earlier had status allowed "yes".
Sindroid said:
Why unlock it? You will lose your DRM keys if you do..
Click to expand...
Click to collapse
I dont care about drm keys. I want to install new custom roms on my phone. So.can.you point me to a link where i can unlock bootloader?
You cannot unlock it if it says bootloader unlock allowed: no
Sindroid said:
Why unlock it? You will lose your DRM keys if you do..
Click to expand...
Click to collapse
its necessity if you want an aosp rom .....
Stock basted Roms on most Sony devices are pretty fast and solid in my opinion no need to really unlock unless your desperate for cm
So that's it? If the bootloader can't be unlocked officially, I'm stuck on Sony roms forever?
Wouldn't bother me so much but my Z3 has a horrible bug where it doesn't work with the bluetooth in my car without rebooting first every time. Was hoping to install CM12.
Could be a hardware fault the Bluetooth
srw985 said:
I'm stuck on Sony roms forever?
Click to expand...
Click to collapse
Why did you get a Sony phone then
mickyw1980 said:
Why did you get a Sony phone then
Click to expand...
Click to collapse
It's not that I have any major issues with Sony roms, I'd just like to be able to flash other stuff in the future, should I want to.
I'm still going to keep the Z3, such a nice phone, nothing else really comes close to it for me yet. Maybe the M9, but I just got the Z3 for £260 from o2 and had it network unlocked, probably have been looking at least double that for the HTC.
You can still root the device and customize it. Tools like the XPosed framework are great at modifying specific parts of the ROM.
But to confirm: you're stuck. You can't unlock Sony's unlockable bootloader. I've heard of people trying to unlock it, I've never heard of a successful case.
Enjoy the phone, it's among the best available right now (imho).
So this is my first xperia device since the Xperia Arc was released way back when, and I have been using HTC phones. Which are WAY different in terms of Rooting / Unlocking / Etc.
So long story short, What I want to know is what Can I currently do to the Xperia Z5? I see there's no custom ROM's yet which is expected , but I see mixed results about unlocked BootLoader & Root , the main thread says that a bootloader hasn't been achieved, yet there's a few root methods which have been successfully completed , requiring an unlocked bootloader, so naturally you could see the confusion..... Can someone point a SONY noob towards the right direction in terms of bootloader unlock / rooting? Running the E6653 ( not sure if there's variants )
Basically you currently need to unlock the bootloader to to get root. And doing so loses some features which u may possibly never get back. So most people are currently waiting for another way around to be figured out
Sent from my Xperia z5 using Tapatalk
well ****...
Ben36 said:
Basically you currently need to unlock the bootloader to to get root. And doing so loses some features which u may possibly never get back. So most people are currently waiting for another way around to be figured out
Sent from my Xperia z5 using Tapatalk
Click to expand...
Click to collapse
My heart literally dropped as I read this..... Because I already unlocked the bootloader. I'm assuming it's the bootloader unlocking that destroys some features? If so , which ones?
And how can I tell if they were actually destroyed / bootloader unlock actually worked
Unlocking the bootloader on Xperias will delete the device's DRM keys. These keys are unique per device and once gone are gone forever. They're needed for Image enhancements like X-Reality/Bravia/Super-Vivid and some camera features too - low light and noise reduction algorithms I think. Sound improvements (ClearAudio+...) too.
ricodredd said:
Unlocking the bootloader on Xperias will delete the device's DRM keys. These keys are unique per device and once gone are gone forever. They're needed for Image enhancements like X-Reality/Bravia/Super-Vivid and some camera features too - low light and noise reduction algorithms I think. Sound improvements (ClearAudio+...) too.
Click to expand...
Click to collapse
Well crap lol, is there any way to actually make sure that the DRM's were deleted or if the bootloader unlock was actually successful? I still have a few days to swap the phone out if anything goes wrong ( Bell wouldn't be able to tell a bootloader unlock ) , I haven't had enough play time with the phone before the process to actually see a difference with the camera, I read somewhere that if TrackID works, than it's not unlocked, is that true?
Do us T-Mobile D6616 Xperia Z3 owners have any options to install a different Sony ROM from another variant that has a newer Android version (Marshmallow)? Our bootloader is locked but it's my understanding that the bootloader doesn't need to be unlocked to install another Sony Xperia ROM from the same variant. The question is: although it might be expected/understandable, what is the root cause as to why our D6616 soft bricks when trying to installing the ROM from another Z3 variant (eg. D6653)? Is there a certain piece of the ROM such as the baseband that causes the soft brick, in which case wouldn't it be possible to just remove the baseband from the ROM/FTF and it would work?
Are there any Devs willing to explore this or already know? I just want to know if us T-Mobile Xperia Z3 owners are completely screwed with no options?
By the way, Des from the product team at T-Mobile said that Sony dropped Dev support for the T-Mobile Xperia Z3... How lovely...
s1dest3pnate said:
Do us T-Mobile D6616 Xperia Z3 owners have any options to install a different Sony ROM from another variant that has a newer Android version (Marshmallow)? Our bootloader is locked but it's my understanding that the bootloader doesn't need to be unlocked to install another Sony Xperia ROM from the same variant. The question is: although it might be expected/understandable, what is the root cause as to why our D6616 soft bricks when trying to installing the ROM from another Z3 variant (eg. D6653)? Is there a certain piece of the ROM such as the baseband that causes the soft brick, in which case wouldn't it be possible to just remove the baseband from the ROM/FTF and it would work?
Are there any Devs willing to explore this or already know? I just want to know if us T-Mobile Xperia Z3 owners are completely screwed with no options?
By the way, Des from the product team at T-Mobile said that Sony dropped Dev support for the T-Mobile Xperia Z3... How lovely...
Click to expand...
Click to collapse
Without an unlocked bootloader, there's not really much to be done. You're at T-Mobile's mercy for updates. You cannot install a ROM for any other variant than the D6616. There is a check that happens in the bootloader when you turn the device on. If a non-D6616 firmware is detected, it will refuse to boot until it detects the correct one. This is easily bypassed with an unlocked bootloader, which is not available for the T-Mobile variant.
In short, yes, D6616 owners are indeed screwed. Don't buy carrier models whenever possible.
There are unlocked versions now available. I unlocked my version and tried to flash another room but didn't work.
I would love to know more specifics on how to bypass the check. Is part of it replacing the phone ID?
---------- Post added at 06:52 PM ---------- Previous post was at 06:06 PM ----------
Here is the partition files if that helps
https://docs.google.com/document/d/1Nl5Egwt4ubXDRpLNOEzVQRu0gNk2lxO2ad7nUkNTkD0/edit?usp=sharing
A quick note from the battlefront. Both Sony and TMO are pointing at eachother. The one constant is not owning up to orphaning the TMO variant less than a year into its product cycle. It's actually quite amusing to see the non-statements from both parties. A simple "It ain't happening" statement would shut the door.
Here's hoping someone with a lot of time on his/her hands can jailbreak the D6616 variant.
The partition layout is the same. If every partition was pulled from a D6603 with adb or fastboot. I theoretically should be possible to flash them one by one to a D6616 if done in the correct order. A jtag cable may be necessary.
So you are saying the only way to do it is getting a copy of someones phone partions and installing them individually?
/u/cajunflavoredbob @cajunflavoredbob Any further suggestion from your end?
odunke01 said:
So you are saying the only way to do it is getting a copy of someones phone partions and installing them individually?
/u/cajunflavoredbob @cajunflavoredbob Any further suggestion from your end?
Click to expand...
Click to collapse
The bootloader for the D6616 is not the same as on the other unlocked models. You can bypass the bootloader lock and write directly to the partitions using a jtag box or similar hardware, but there's a very real chance that it will still not boot up, since the bootloader checks for firmware verity on boot. As I mentioned before, take this as a lesson not to buy carrier branded models in the future, or at least those without a bootloader unlock method. I know the temptation is there to get the device cheaper through the carrier, but you're getting what you pay for.
@cajunflavoredbob the device I have is unlocked. It is not from tmobile directly.
When I purchased it the phone was branded as a D6603.
So with the knowledge that this phone does have an unlocked bootloader. Is there a non hardware related method?
odunke01 said:
@cajunflavoredbob the device I have is unlocked. It is not from tmobile directly.
When I purchased it the phone was branded as a D6603.
So with the knowledge that this phone does have an unlocked bootloader. Is there a non hardware related method?
Click to expand...
Click to collapse
You're in the wrong forum then. This is for the T-Mobile version (D6616). With an unlocked bootloader, you can pretty much flash whatever you want.
I am annoyed as when I purchased the phone it was branded as a D6603 (packaging and advertising) but is truly a D6616 as stated in the phones internals.
When I originally got the phone I upgraded it using xperia companion and it installed D6616 firmware, that was the first time i realised something was different with it.
The IMEI numbers match and sony recognises it as a proper IMEI.
I checked the bootloader status using *#*#7378423#*#* and it stated "Bootloader unlock allowed: yes"
I then proceeded to Sonys website to unlock the bootloader and it changed to "Bootloader unlocked: yes"
Flashing a normal d6603 firmware (rom or ftf) doesn't work, only d6616
There are also others who have stated that they have unlockable versions of the d6616, it isnt just me.
So repeating my question, is there something that can be done?
I think we need to try the Non-T-Mobile US Model (D6646) ROM. It's the closest to our T-Mo model.
Ok, so I tried again.
Checked my bootloader staus again, it still says unlocked:yes
Tried flashing niabocs existenz rom - > softbrick (blackscreen, no logo)
Reflashed the stock 4.4.4 FTF
Rooted, recovery etc.
rechecked bootloader, still unlocked: yes
Tried Slimm rom from Wajk - factory reset etc
- > softbrick (blackscreen, no logo)
What step am I missing?
Do i need to flash the D6603 FTF first?
---------- Post added at 09:44 AM ---------- Previous post was at 09:34 AM ----------
Ok, so that didn't work
03/041/2016 11:41:47 - INFO - Opening TA partition 2
03/041/2016 11:41:47 - INFO - Writing TA unit 00002774. Value : 01
03/041/2016 11:41:47 - INFO - Closing TA partition
03/041/2016 11:41:48 - INFO - Processing partition-image.sin
03/041/2016 11:41:48 - INFO - Checking header
03/041/2016 11:41:48 - ERROR - Processing of partition-image.sin finished with errors.
---------- Post added at 09:46 AM ---------- Previous post was at 09:44 AM ----------
Do I need to extract the files and create a PRF, leaving the bootloader from D6616 in it?
Screenshots to show it is a D6616 with an unlocked bootloader
@cajunflavoredbob Hate to bother you still, but you mentioned it was easy to bypass the check on boot.
I haven't been able to find that searching on XDA or google.
How would I got about it.
As you can see above, I DO have a D6616 and it has an unlocked bootloader.
As I mentioned, you can bypass the bootloader by writing directly to the partitions through a jtag box or similar. However, you would still likely have an issue when you reboot due to the bootloader verifying the system on each boot.
It seems like your device took the wrong firmware update, though. I have not come across any D6616 devices with an unlockable bootloader. If you say that the packaging labeled it a D6603, and it later turned into a D6616 with an unlockable bootloader, this backs up my theory.
You could try unlocking the bootloader and flashing whatever you want, but the issue now is that you have a D6616 bootloader looking for the same system image.
Long story short, it is easy to bypass the bootloader, but only if you have the hardware to do so. Honestly, I would argue that it's better to just pick up a new device at this point. The G4 can be had for under $200, for example, and that's about what a jtag box is going to cost you.
Unless someone creates a tool to unlock the D6616 bootloader or to replace it with one of another model, there's really nothing you can do. Carrier branded devices suck.
Ok, thanks mate. Thought you meant there was a software coded way of bypassing.
That sucks.
Oh well, no idea why it changed to a D6616 firmware, but i'm stuck with it now. Its still a good phone and I can do enough manually, it was just easier to use someone elses hardwork through an already modded rom.
Thanks for the reply.
@odunke01: I have D6616 with Bootloader unlock allowed: yes, same as yours. I think that like me, you purchase your phone from non-authorized distributor. I found that DRM Key has [Unknown error]. Though I do think that the phone originating US T-Mobile D6616 and has been modified (may be illegally). This modification is to unlock SIM card that allow the phone working with free SIM.
well if ur package labels as d6603 then u need to recover it to this version somehow else this mobile will be no fun for ya. miht an mod cn be done for an recovery to cheat on the kernel and insall the right kernel above it and sin error can apear when ur download have problems. ps if uinstall an costumrom then install one wich is ful and before that delete everything on ur phne except the fota partition. mch easier to avoid darkness of death. it should work.
Hello,
I recently bought a Sony Xperia Z5 Compact (E5823), and was instantly appalled by the amount of pre-installed bloatware that I can't get rid of. I am now trying to root my phone in order to do so. There is however a lot of information to take in on the matter, and a lot of it seems conflicting to a newbie like myself when so much is dependant on device and android version.
Some info on my phone
Sony Xperia Z5 Compact (E5823)
Android version: 6.0.1
Kernel version: 3.10.84-perf-gf1cfa5f, [email protected] #1, Mon May 30 18:41:52 2016
Build number: 32.2.A.0.253
Rooting status: Bootloader unlock allowed: No
Basically - just out of the box, updated to the latest firmware, a couple of downloads from the app store, and that's it.
Does my "Bootloader unlock allowed: No" status mean that I cannot unlock the bootloader by any means? According to http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/ the Z5 should be allowed to do so, why isn't mine?
Ultimately what I want to do for the moment is rooting my phone. Nothing more, and with as little change as possible. Ideally I'd like not to lose any functionality either (read about losing several camera and image related features due to DRM, amongst others). I found this thread http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605 - is this the best suited guide for me? And will it definitely work on my phone, despite the Service Menu telling me that I cannot unlock the bootloader?
In such a case that the above guide is what I'm looking for - once done and if successful, will I be able to download firmware updates as my phone notifies me about them, without further messing around? (the normal/traditional way)
Thanks in advance,
Chris.
ps: I'm not worried about voiding the warranty, and I'm used to poking around in untraditional areas, albeit not on Android thus far.
You cannot unlock your bootloader or root so all guides are useless. Sony say the Z5 bootloader is unlockable however they lock some on carriers request. You want to try a different firmware I find that nordic has less bloat. You can also disable most apps aswell
Sent from my E6653 using Tapatalk
That's unlikely to be the reason in my case - my phone was bought retail through Amazon, not with a carrier contract.
Is there nothing that can be done to change the bootloader unlocking permissions?
ChrisMB said:
That's unlikely to be the reason in my case - my phone was bought retail through Amazon, not with a carrier contract.
Is there nothing that can be done to change the bootloader unlocking permissions?
Click to expand...
Click to collapse
You can't do anything about it, but I suppose you could ask Sony if they'll unlock it for you, or contact Amazon and ask if they'll swap it for an unlockable unit.