Database Info

[Q] About Unlocking, Flashing and Rooting

Hi, I am new to XDA and this is my first ever post, so Devs, be easy on me.
I own a Sony Xperia SP device (c5302) which is currently running Android 4.3 (12.1.A.1.201) and I want to gain root access on my device.
I looked at several tutorials and videos and found that I need to have the Bootloader unlocked first of all. I am not sure about the exact procedure as every tutorial follows a slightly differently process.
Here are my questions as a newbie.
I want to know that what losses can I have if I try to unlock my bootloader?
After rooting, will I be able to get the same android and build version running on my device i.e. Android 4.3 and build 12.1.A.1.201?
Will I be able to get future updates from Sony that are shown in the phone as notifications as and when the updates arrive?
Is it possible to bring my phone back to the same condition it is in today? Like it was never rooted or the bootloader was never unlocked, because I want to avail warranty as well?

1. Warranty
2. Ofcourse
3. I think this is device / manufacturer specific...
4. You can always reflash to stock ROM, talking about bootloader some bootloaders can be unlocked but can't be relocked this is again device / manufacturer specific.

Question: Will flashing stock and relocking the bootloader get my warranty back?

I can't seem to find the answer to this question anywhere on the moto g forum, so that means I'll have to ask you guys myself.
I purchased this device after having an s3 mini. On the s3 mini I was able to install the TWRP recovery and some custom roms like cyanogenmod. But if anything would go wrong I would just flash the stock rom and bring it over to the store for repairs.
But after looking on this forum, it seems that whenever you unlock the bootloader on the moto g3 your warranty is permanently voided. So here's my question:
If I unlock the bootloader and flash TWRP, cyanogenmod, etc. and my device breaks. Would flashing stock and relocking the bootloader get my warranty back? ( i don't know if it makes any difference but i live in the Netherlands )
I hope you guys will be able to help me answer this question because i really want to root my device and get cyanogenmod on it.

Warranty is legally void the moment you submit the unlock code to Motorola. They will update their database with your unlock code and provide you the unlock key.
So relocking bootloader or flashing stock rom won't restore your warranty legally. But if lucky, the motocare engineer might proceed to repair your phone by seeing stock rom on board. So keep stock while visiting motocare. But legally it doesn't renew your warranty.

The answer is simple and easy to find... No, once you accept Motorola's T&C for unlocking the bootloader, which are crystal clear if you even glance at them, and receive your unlock token your warranty is void, period. You don't even have to actually unlock the bootloader, just accepting the T&C is enough. At this point your serial number/IMEI are flagged as warranty void in Motorola's database. The actual state of your device doesn't even matter.
BTW, technically what you did with your S3 should have voided the warranty, but depending on who handled the warranty (carrier or Samsung) and their thoroughness, many got through anyway. To the best of my knowledge the only devices you can modify significantly and not void the warranty are Nexus devices.
Sent from my MotoG3 using Tapatalk

acejavelin said:
The answer is simple and easy to find... No, once you accept Motorola's T&C for unlocking the bootloader, which are crystal clear if you even glance at them, and receive your unlock token your warranty is void, period. You don't even have to actually unlock the bootloader, just accepting the T&C is enough. At this point your serial number/IMEI are flagged as warranty void in Motorola's database. The actual state of your device doesn't even matter.
BTW, technically what you did with your S3 should have voided the warranty, but depending on who handled the warranty (carrier or Samsung) and their thoroughness, many got through anyway. To the best of my knowledge the only devices you can modify significantly and not void the warranty are Nexus devices.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
I've already been to the motorola site for unlocking the bootloader before (xda won't let me post the URL) and I have followed the instructions up until step 6: "Check if your device can be unlocked by pasting this string in the field below, and clicking “Can my device be unlocked?”
After that I did NOT click the "REQUEST UNLOCK KEY" button. Is my warranty voided because of following the steps up until step 6?
(because if it is voided, I might as well just root it already)

Djurre2709 said:
I've already been to the motorola site for unlocking the bootloader before (xda won't let me post the URL) and I have followed the instructions up until step 6: "Check if your device can be unlocked by pasting this string in the field below, and clicking “Can my device be unlocked?”
After that I did NOT click the "REQUEST UNLOCK KEY" button. Is my warranty voided because of following the steps up until step 6?
(because if it is voided, I might as well just root it already)
Click to expand...
Click to collapse
No, not yet... I don't remember the step #, but Until you accept the T&C and request the unlock token, your warranty is good.
Sent from my MotoG3 using Tapatalk

acejavelin said:
No, not yet... I don't remember the step #, but Until you accept the T&C and request the unlock token, your warranty is good.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Thanks for the help!
I have desided to request the key, I'll be rooting my device very soon.

Djurre2709 said:
Thanks for the help!
I have desided to request the key, I'll be rooting my device very soon.
Click to expand...
Click to collapse
I'm facing the same problem as you. What made you choose to unlock it?
Envoyé de mon MotoG3 en utilisant Tapatalk

vinz244 said:
I'm facing the same problem as you. What made you choose to unlock it?
Envoyé de mon MotoG3 en utilisant Tapatalk
Click to expand...
Click to collapse
I decided to root my device because on my other devices I use cyanogenmod as a daily driver. Because of this I'm used to the advantages it has, and the freedom you have over your device. I don't have my warranty anymore, but the fact that my s3 mini actually faced the same problems and I was able to get it repared by just flashing stock made me think that the risk isn't that big. Also the other dude said that by flashing stock the device might stil be repaired. So I decided to take the risk and root my device. After that I flashed cyanogenmod on it and now I use this as daily driver on my Moto G 2015 too.
So the chances are that eventhough my warranty is voided legally, they might stil fix my device if broken. Because of the fact that they did this with my other device once I thought it wouldn't do any harm to root this device too.
Some tips if you do decide to root your device;
go over to the FAQ tab on this forum to find yourself the link to the TWRP recovery. This is as far as I know the best custom recovery for the Moto G 2015.
Also on the beginning of the FAQ it says you need to find out what device you have (personally I've got the XT1541), look this up for your own case and do your research before you start unlocking the bootloader.
After you've unlocked the bootloader your device will be factory reset, so make sure you back up all your data.
When you have installed the TWRP, make sure to make a 'nandroid backup' from your stock rom in case you fail to install any other rom (might you intend to do so). Keep this nandroid backup stored on your computer too.
If you decide to install cyanogenmod (certainly as a beginner) I would recommend to install a snapshot instead of a nightly. Also don't install an unofficial except if your absolutely shure you want to do this.
For the original download page of cyanogenmod go to download.cyanogenmod.org and search for the device 'osprey'
When you install gapps I strongly suggest to install the nano package (the other packages didn't work for me)
Go to opengapps.org and select ARM - 5.1.1 (or 6.0 depending on the android version) - nano
Just a few tips for you ( unfortunately I had to find out some of these things the hard way, so that's why I thought I would leave them here for you )
Good luck with whatever you intend to do with your device and I hope my opinion and knowledge might help you to decide what you want to do with your device

Djurre2709 said:
I decided to root my device because on my other devices I use cyanogenmod as a daily driver. Because of this I'm used to the advantages it has, and the freedom you have over your device. I don't have my warranty anymore, but the fact that my s3 mini actually faced the same problems and I was able to get it repared by just flashing stock made me think that the risk isn't that big. Also the other dude said that by flashing stock the device might stil be repaired. So I decided to take the risk and root my device. After that I flashed cyanogenmod on it and now I use this as daily driver on my Moto G 2015 too.
So the chances are that eventhough my warranty is voided legally, they might stil fix my device if broken. Because of the fact that they did this with my other device once I thought it wouldn't do any harm to root this device too.
Click to expand...
Click to collapse
(Sigh)... Of course they will fix your device, just not under warranty and not for free. I don't know how much clearer Motorola can be, if you accept the T&C and get the unlock token, your warranty is void. Period.
Your ESN & serial number are flagged in Motorola's database as no warranty, the actual state of the device is not relevant, they don't care, even if you never actually unlock or modify the device... This is not Samsung, LG, HTC, or any other company, this is Motorola and it's how they do it. They are very clear and don't try to hide it or fudge it, it just is and they make sure you know it.
But at the same time, the failure rate of the Moto G is extremely low, so your probably fine anyway.
Sent from my MotoG3 using Tapatalk

Djurre2709 said:
I decided to root my device because on my other devices I use cyanogenmod as a daily driver. Because of this I'm used to the advantages it has, and the freedom you have over your device. I don't have my warranty anymore, but the fact that my s3 mini actually faced the same problems and I was able to get it repared by just flashing stock made me think that the risk isn't that big. Also the other dude said that by flashing stock the device might stil be repaired. So I decided to take the risk and root my device. After that I flashed cyanogenmod on it and now I use this as daily driver on my Moto G 2015 too.
So the chances are that eventhough my warranty is voided legally, they might stil fix my device if broken. Because of the fact that they did this with my other device once I thought it wouldn't do any harm to root this device too.
Some tips if you do decide to root your device;
go over to the FAQ tab on this forum to find yourself the link to the TWRP recovery. This is as far as I know the best custom recovery for the Moto G 2015.
Also on the beginning of the FAQ it says you need to find out what device you have (personally I've got the XT1541), look this up for your own case and do your research before you start unlocking the bootloader.
After you've unlocked the bootloader your device will be factory reset, so make sure you back up all your data.
When you have installed the TWRP, make sure to make a 'nandroid backup' from your stock rom in case you fail to install any other rom (might you intend to do so). Keep this nandroid backup stored on your computer too.
If you decide to install cyanogenmod (certainly as a beginner) I would recommend to install a snapshot instead of a nightly. Also don't install an unofficial except if your absolutely shure you want to do this.
For the original download page of cyanogenmod go to download.cyanogenmod.org and search for the device 'osprey'
When you install gapps I strongly suggest to install the nano package (the other packages didn't work for me)
Go to opengapps.org and select ARM - 5.1.1 (or 6.0 depending on the android version) - nano
Just a few tips for you ( unfortunately I had to find out some of these things the hard way, so that's why I thought I would leave them here for you )
Good luck with whatever you intend to do with your device and I hope my opinion and knowledge might help you to decide what you want to do with your device
Click to expand...
Click to collapse
Thanks I still need time to decide but interesting! My best experience with support is probable with Archos. I sent them my phone bricked 3 times because of bad flashed rom and they would send me a new one
Envoyé de mon MotoG3 en utilisant Tapatalk

T-Mobile D6616 Xperia Z3 - Are we completely stuck on the latest T-Mobile ROM?

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.

Unable to get OTA updates on Xperia Z5

Hello! I'm new here and actually the main purpose of my registration on this wonderful website is the amount of helpful and skillful people I saw in various threads I read before, giving me hope for the solution of my problem.
As stated in the title, I'm currently unable to get OTA updates on my phone.
Some time ago I unlocked the bootloader (so my bl is unlocked now) in order to have my Z5 rooted. Apparently something went awfully wrong while flashing the TWRP or perhaps I was just awfully stupid and missed a step... Anyways I ended up without any OS and started searching on the web for some solutions.
I came across FlashTool and XperiFirm, then downloaded and flashed the (at the time) latest firmware, which is the one i currently have (Service Menu shows "GENERIC_32.2.A.0.224"). So now my phone seems perfectly fine: stock rom, no custom recovery (as far as I know), no root privileges. The only problem it shows is the fingerprint hardware that stops working every once in a while; something a simple reboot fixes.
But I have been unable to update since then, with my "software update" tab showing no available updates (nor could I get one via Sony PC Companion, furthermore getting errors while trying fo repair software) while under "diagnostics" it clearly says "new software available".
I just want to get everything back as it was before, and to get my OTA updates to work; I'm not interested in custom ROMs or custom recoveries or SU.
I apologize in advance in case an identical thread had already been opened and closed; I hope you guys can help me solve this mess I did.
Thanks a lot

I found out my problem is connected with the DRM Keys loss caused by unlocking the bootloader. I'll try this out: http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605

scacio said:
I found out my problem is connected with the DRM Keys loss caused by unlocking the bootloader. I'll try this out: http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
Click to expand...
Click to collapse
Once you have unlocked the Bootloader ota updates don't work EVER only manually flashing the ftf via flashtool will get you updated. If you unlocked the Bootloader without backing up the drm/ta keys then re-lock the Bootloader ota updates will Not work. If you unlock the Bootloader and then re-lock with previously backed up drm/ta keys ota updates WILL work.
The drm fix does NOT replace the missing drm/ta keys it merely tricks the device into thinking that those required for x-reality, low light conditions, and noise reduction in the camera are there to reactivate those features.
Also DO NOT try to use a other Xperia devices drm/ta keys on your own unless you want a permanent paperweight.
Sent from my Xperia XA using XDA Labs

Ah, so I should have backed those up before unlocking the bootloader. It seems I'll have to spend a few minutes on flashtool every once in a while to get updates, nevermind.
Anyway is it worth it to try this DRM fix? I did not notice any changes to the quality of the camera.
And another noob question: if I flash this "modified kernel" will my device be wiped? Or I just flash it, reboot the phone and enjoy DRM features?

Just a quick update to let you know, I have installed the drm fix and rooted, the funny thing is that now I receive ota updates.. But of course I'm unable to install them. Not that I want them anyway, so no problem. I have reconsidered the potentiality of a rooted device and started to appreciate the benefits; thanks for the help

What does it mean to have an Upgraded Unlocked Bootloader?

I've started learning about custom firmware and Xperia Z3 customization a day ago, since I couldn't stand the stock firmware. My current goal is to flash Lineage OS 14.1 on my D6603. And in the post it says it require an Upgraded Unlocked Bootloader. Now I do understand the Unlocked Bootloader part, but I'm not sure about the Upgraded part. And I've done some read around the forum and found one that refers to it but I'm not sure. Doing Google search didn't show too much information about it? The reason that I'm not doing more research is I'm kinda tight on time these day. So much appreciate to anyone can help.
Also my D6603 is currently running the latest MM build with Root access and Dual recovery installed.

The updated part refers to the latest official bootloader from the Sony Firmware .291.
It requires Sony Software called "EMMA" (instructions are easy to find).
Connect your device and flash the latest firmware to get the bootloader on your device.
Backup all your data in case something gows wrong (especially the one on internal storage as it gets wiped in the process I think).

Omario-242 said:
The updated part refers to the latest official bootloader from the Sony Firmware .291.
It requires Sony Software called "EMMA" (instructions are easy to find).
Connect your device and flash the latest firmware to get the bootloader on your device.
Backup all your data in case something gows wrong (especially the one on internal storage as it gets wiped in the process I think).
Click to expand...
Click to collapse
Really appreciate your reply. Would that allow my phone's bootloader to be unlocked too? Because I've just read around a bit and according to the Sony's UnlockBootloader site, I can't unlock it. And I just don't want to be stuck with MM build.

inSecured said:
Really appreciate your reply. Would that allow my phone's bootloader to be unlocked too? Because I've just read around a bit and according to the Sony's UnlockBootloader site, I can't unlock it. And I just don't want to be stuck with MM build.
Click to expand...
Click to collapse
if it says "unlockable - no " in your secret menu I guess it isn't ... but I never had to investigate this.