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.

[Q] New to the Android world, i have afew questions for your

I'm totally new to the Android world and i spent many hours to read this forum to learn as much as possible about my device and what i can do with it. But now, i need your help on a few things.
KitKat vs Lollipop, does it make sense to upgrade to Lollipop now or should i wait? Is there any major know bugs?
Since that i only have a 8gb device, i would like to clean the apps as much as possible. There's many apps that i don't need but they can't be uninstalled. For example, all the Motorola apps (is there something that we really need from them?), a few google apps like Google+, Google Play Films, Hangouts, etc that i will never use.
I want a stable ROM that i don't need to patch every day to solves problems. When i read about CM12 for Moto G, i see people that have problems here and there and wait for the next daily build to give it a try. I don't want to play that game!
If i install a custom rom, i guest that future updates will not come from Motorola. How the updates work afterward?
It's ok if i must have my device rooted
I have read about stock lollipop optimized version by lost101 but it don't think that the versions currently available will work for me. I'm in Canada and the versions that i see is Brazil or Asia.
thank you for you help!

You have the xt1032? Is there any warranty left? If there is no warranty, I recommend unlocking the bootloader before doing anything. It is easier to restore a bricked phone if you have an unlocked bootloader.
If you intend to stay on stock, you need some of the Motorola apps in order to install OTA updates.

Well what I will say is. I'm in the uk using lost101s BR optimized and I'm very pleased with it.

audit13 said:
You have the xt1032? Is there any warranty left? If there is no warranty, I recommend unlocking the bootloader before doing anything. It is easier to restore a bricked phone if you have an unlocked bootloader.
If you intend to stay on stock, you need some of the Motorola apps in order to install OTA updates.
Click to expand...
Click to collapse
The phone is new but i don't care about the warranty. I've read that i can unlock the bootloader with the Motorola tutorial. I must be honest, i'm a little bit lost. I don't fully understand the difference between "unlocking bootloader" and "phone rooted"!
and yes the model i have is XT1032

skoub2 said:
The phone is new but i don't care about the warranty. I've read that i can unlock the bootloader with the Motorola tutorial. I must be honest, i'm a little bit lost. I don't fully understand the difference between "unlocking bootloader" and "phone rooted"!
and yes the model i have is XT1032
Click to expand...
Click to collapse
You must unlock boot loader first then flash a custom recovery (manually or there is a tool in the development section) then rooting next.

Unlocking the bootloader allows you to install non-Motorola software. With a locked bootloader, the only software that can be loaded on your phone would have to be digitally signed by Motorola.
Rooting gives you administrative access to the system files.
You may not need an unlocked bootloader to get root and you do not need root to unlock a bootloader.
Start here to get the bootloader unlock code: https://accounts.motorola.com/ssoau...ct/standalone/bootloader/unlock-your-device-b

I tried to install TWRP (any version available) but it take like 1 minutes to show the home screen and im not able to "swipe to unlock". So i have installed Philz recovery and then installed lost101 Retail Brazil 5.0.2 Stock ROM (Optimized) v1.1a. I'm playing with it right now and so far so good.

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

[UNLOCK] Bootloader Unlock Package

Introduction
This is the bootloader unlock from ZTE. It was provided to me in private email by a ZTE engineer.
Warning
This package is for the USA version of the Axon 7 Mini (tulip) running 7.1.1 b14 firmware. If you are running any other device or firmware version, it may not work.
Note
After some testing, it appears that the Axon 7 Mini is not locked in any way. In other words, apparently neither this package nor tuliptool's unlock are required to flash custom ROMs. The only apparent advantage to flashing this is to get access to fastboot, which provides a way to flash a custom boot and recovery (among other things).
Flashing Instructions
Place axon_mini_unlock.zip on the root of your sdcard.
Reboot into recovery.
Select "Apply update from SD card".
Select axon_mini_unlock.zip.
Usage Instructions
After the package is flashed, you may boot into the bootloader:
adb reboot bootloader
Once in the bootloader, you will see an on-screen menu. Additionally, you may access the typical fastboot commands:
fastboot oem device-info
fastboot oem unlock
fastboot flash ...
... etc ...
Download
axon_mini_unlock.zip
md5: ea8f1a21c8a46b3045d00f17a37fe359

So, after this is done, I can flash TWRP through fastboot and tuliptool is no longer necessary, correct?

Yes, that is correct.
JoeGatto said:
So, after this is done, I can flash TWRP through fastboot and tuliptool is no longer necessary, correct?
Click to expand...
Click to collapse

This package is for the USA version of the Axon 7 Mini (tulip) running 7.1.1 b14 firmware. If you are running any other device or firmware version, it may not work.
Click to expand...
Click to collapse
Is this something your contact mentioned or something that you believe based on your experience?
Any harm in trying it on verdandi/other versions without any risk of bricking?
After some testing, it appears that the Axon 7 Mini is not locked in any way. In other words, apparently neither this package nor tuliptool are required to flash custom ROMs. The only apparent advantage to flashing this is to get access to fastboot.
Click to expand...
Click to collapse
Any way to confirm this is also the case with other versions as well?
Thanks TDM.... you're going to have a lot of Canadians asking about verdandi as it is quite cheap here at the moment. Better get those questions out of the way early. The source is released, same kernel version as the U.S. one with some small differences with drivers (from what I can see) and I am sure that if people know that custom roms are possible on that version (not bootloader locked forever) it would be appreciated.

trpn111 said:
Is this something your contact mentioned or something that you believe based on your experience?
Any harm in trying it on verdandi/other versions without any risk of bricking?
Any way to confirm this is also the case with other versions as well?
Thanks TDM.... you're going to have a lot of Canadians asking about verdandi as it is quite cheap here at the moment. Better get those questions out of the way early. The source is released, same kernel version as the U.S. one with some small differences with drivers (from what I can see) and I am sure that if people know that custom roms are possible on that version (not bootloader locked forever) it would be appreciated.
Click to expand...
Click to collapse
Yeah...verdandi is stuck on Marshmellow. But since it has different hardware it could brick if this is tried.

The ZTE engineer is USA based, he is not on the China development team (read: probably a support engineer). He said: "I attached the unlock update zip package, please try it. It is based on B14 build."
Sorry, that's all I have to go by for "official" information.
I do not want to be responsible for anyone bricking their device, so I cannot claim that this bootloader will work with anything other than a tulip device running 7.1.1 b14.
If you want to try and report back, I'm sure others will appreciate it. But I can't be responsible for the results.
trpn111 said:
Is this something your contact mentioned or something that you believe based on your experience?
Any harm in trying it on verdandi/other versions without any risk of bricking?
Any way to confirm this is also the case with other versions as well?
Thanks TDM.... you're going to have a lot of Canadians asking about verdandi as it is quite cheap here at the moment. Better get those questions out of the way early. The source is released, same kernel version as the U.S. one with some small differences with drivers (from what I can see) and I am sure that if people know that custom roms are possible on that version (not bootloader locked forever) it would be appreciated.
Click to expand...
Click to collapse

Oh, and here is some more information to help you decide...
The volume key combo to enter EDL is handled by aboot (bootloader, eg. the thing we are flashing). This means even if you aren't currently able to use the key combo, you should be able to use it with the new aboot here. And if you can get to EDL, you can never really brick the device.
The volume key combo is detected very early in the aboot code. Like, first thing after basic platform init. So even if this isn't compatible with your device, it's likely we could restore the old aboot (assuming you back it up first, of course).
I'm convinced that the tulip is not locked based on my investigation today. So I have no idea if this aboot is properly signed. If your device is locked and this aboot is not signed properly, the lower boot loader won't load it. I'm not quite sure if that kicks you into EDL or not.
Not sure if that makes the decision easier or harder...

How did you come to the conclusion that tulip is not locked to begin with? If we don't need tuliptool or this aboot, how can I check verdandi if the device is the same 'locked but not really locked' state?
I will have a read about backing up aboot and see what I come up with concerning getting into edl.

So here's the deal...
I initially assumed the bootloader was locked because... well... it's supposed to be. So I found the place in aboot code where it checks the lock flag in the devinfo partition. I used the firehose to write unlocked to that flag. Then I built TWRP, flashed it and it booted. So I assumed everything was working just as I expected.
Today, I flashed the aboot with fastboot support and ran "fastboot oem device-info". It said that my device was locked. So I went to look and, sure enough, my devinfo partition flag was still set. Hmm, that's odd.
So I wrote locked back to the flag. TWRP still booted. Now things are looking pretty suspicious.
But maybe the new aboot doesn't even support locking? So I flashed the original b14 version of aboot and TWRP still booted.
That's pretty hard evidence that aboot is ignoring the lock flag. I don't know what they did -- whether they just removed the code that reads the lock flag or introduced a bug or what.
This does not necessarily mean that the lower layers are unlocked. That is, the lower boot loader may still required a properly signed aboot. I don't know, and I'm not ready to brick my device trying to find out.
trpn111 said:
How did you come to the conclusion that tulip is not locked to begin with? If we don't need tuliptool or this aboot, how can I check verdandi if the device is the same 'locked but not really locked' state?
I will have a read about backing up aboot and see what I come up with concerning getting into edl.
Click to expand...
Click to collapse

Hmm... Looks like this package incompatible with ZTE/P852A11/tulip.
Got error while trying to flash it by stock recovery. Error message says that it is for A12 version of tulip.

Ah, yes, you have the euro model. See the "calling all mini owners" thread, posts #76 and #77.
maestromony said:
Hmm... Looks like this package incompatible with ZTE/P852A11/tulip.
Got error while trying to flash it by stock recovery. Error message says that it is for A12 version of tulip.
Click to expand...
Click to collapse

i get a message saying "cant update from sd card?"

yeshivabachur said:
i get a message saying "cant update from sd card?"
Click to expand...
Click to collapse
Make sure battery level is at least 30% before applying any update. It's a standard protection feature.

JoeGatto said:
Make sure battery level is at least 30% before applying any update. It's a standard protection feature.
Click to expand...
Click to collapse
My battery was 80%+ mine still said can't update from sdcard

Aries2010 said:
My battery was 80%+ mine still said can't update from sdcard
Click to expand...
Click to collapse
Try turning on the OEM unlock setting in developer settings.

JoeGatto said:
Try turning on the OEM unlock setting in developer settings.
Click to expand...
Click to collapse
Thank you so much that worked I appreciate the it . Now I have one more question I have been searching for a way to root stock rom but I can't find any instructions on it. Could you walk me through it or post a link for me if possible? I have the USA mini 7 with B14 firmware

Aries2010 said:
Thank you so much that worked I appreciate the it . Now I have one more question I have been searching for a way to root stock rom but I can't find any instructions on it. Could you walk me through it or post a link for me if possible? I have the USA mini 7 with B14 firmware
Click to expand...
Click to collapse
Rooting the stock ROM will require that you remove verity, so that the OS won't refuse to boot once you've made any changes to the system partition. You'll need to use tuliptool to flash a new boot image, which you can find in this section of the forum. Then, you could either install TWRP through fastboot or using tuliptool.

JoeGatto said:
Rooting the stock ROM will require that you remove verity, so that the OS won't refuse to boot once you've made any changes to the system partition. You'll need to use tuliptool to flash a new boot image, which you can find in this section of the forum. Then, you could either install TWRP through fastboot or using tuliptool.
Click to expand...
Click to collapse
Thank you sir I appreciate it I shall try it tomorrow.

here's a stupid question.... I have only dealt with Samsung devices so, I have trouble understanding any other kind of process that is not Samsung. If a new update comes out while my device is bootloader unlocked can i update it? or will it brick my device?

The "standard" (not Samsung) method of updating via OTA is to ship:
1. Full images of any firmware partitions (rpm, tz, aboot, etc.)
2. Full image of boot.
3. A delta (patch) to system.
Also note that custom recoveries generally do not work with vendor OTA's.
This means that if you wish to apply an OTA, you must first have stock recovery and a completely pristine, unmodified system partition. The rest doesn't matter.
yeshivabachur said:
here's a stupid question.... I have only dealt with Samsung devices so, I have trouble understanding any other kind of process that is not Samsung. If a new update comes out while my device is bootloader unlocked can i update it? or will it brick my device?
Click to expand...
Click to collapse

Locked Bootloader, Config Says "No" Can't Unlock, But Have Root... Am I stuck?

Locked Bootloader, Config Says "No" Can't Unlock, But Have Root... Am I stuck?
Hey everyone,
Well, I had to pull out my previous phone, my Tmo D6616 Xperia Z3. I replaced it when the battery was all bloated and could explode, etc. I replaced it with an LG G5. And, I have the horrible GPS issue with my G5 that just doesn't work well at all. This bugs me. I travel with my family enough that I use it and has caused some wrong turns, etc. I want to replace it, but don't see any good deals in my situation since I have no number to port-in or a new person to bring on the plan.
So, here I am checking on what I can do with my Z3. I've replaced the battery, got a new case, and also replaced the screen protector... just like a brand new phone, except the ROM is really outdated. It is currently on the latest OTA from Sony, Android 5.0. I did check to see if there is a more recent stock ROM and there isn't.
I want to install a new ROM, in which I should be able to backup the TA partition since I am rooted.
When I do the *#*#.... code, then check to see if the bootloader can be unlocked, it says no. Because of that, am I out of luck?
Am I able to use root to unlock the bootloader and install another ROM?

Same question here...
johnathanamber said:
Am I able to use root to unlock the bootloader and install another ROM?
Click to expand...
Click to collapse
I also want this answer.

If it says "no" to unlock the bootloader, then you can not unlock the bootloader.
You can, however, use root and recovery.
Check out https://forum.xda-developers.com/z3/general/guide-rootrecovery-how-to-root-install-t3017056. Just stick it to xperia Roms. Search the forum, I think Marshmallow is the latest.
As far as I know, other Roms than Xperia are not recommended for a locked bootloader. But there are other, xperia roms, for a locked bootloader Z3.
Good luck.

DolDrum said:
If it says "no" to unlock the bootloader, then you can not unlock the bootloader.
You can, however, use root and recovery.
Check out https://forum.xda-developers.com/z3/general/guide-rootrecovery-how-to-root-install-t3017056. Just stick it to xperia Roms. Search the forum, I think Marshmallow is the latest.
As far as I know, other Roms than Xperia are not recommended for a locked bootloader. But there are other, xperia roms, for a locked bootloader Z3.
Good luck.
Click to expand...
Click to collapse
I was able to get recovery installed, thanks for that. I am not so sure about the MM rom, however. I haven't seen one for the D6616. That would at least make it a little better to work with.