Hello,
I just got my new Xperia Z having used my ancient Iphone 1G for the last 4 years and I have no experience with Android and anything related to it what so ever. I've spent the last 2 days tirelessly working my way through various forums, guides, wikis to get an idea what I'm dealing with here and where to start, but there's an important decision that I could really use your thoughts and tips on.
After reading up on it, I decided I want to root my phone and this seems to be somehow connected to unlocking the bootloader and this is where I'm worried. I read the guide on how to unlock the bootloader and the warning about losing DRM Keys and the consequences of this scared me away from it. Now I'm left wondering, and this is my actual question here:
What is the difference between unlocking the bootloader and rooting my phone and simply rooting without unlocking the bootloader?
And in case the things I want to do are only available with an unlocked bootloader: how damaging is it to lose DRM keys and therefore the bravia engine and gracenote? What made you decided for or against unlocking the bootloader?
Thanks!
Hi,
maybe I can help you.
Bootloader is like the BIOS of a PC. It checks everything at start up.
Locked Bootloader only allows to run the Stock FW and in this case the DRM-Keys are working (everything is checked and safe)
Unlock the Bootloader means you were able to install an modified / other FW and then you loose the DRM-Keys (the manufacturer hasn´t checked the FW and it is in the eyes of an manufacturer "not safe". You will also loose your warranty.
If you unlock the bootloader Root is always possible as I know.
In this case the system is not from the manufacturer and unofficial modification could be done to the system. Normally all modified Systems have Root access. So you were able to do things that the manufacturer has normally not allowed. Modify system files or something like that. Also it could be possible to copy for example a downloaded and payed movie to another device. This is why you were not able to download a movie on the Play Store if you have root. On a locked bootloader the FW (system) does not give you the possibility to copy the movie to an other device and everything is "safe" (from the view of companies). No illegal copies are possible. (DRM-Keys)
Since some days Root is also possible on a locked bootloader.
The bootloader is checking the status (locked) .. then checking the FW (stock) ... DRM-Keys still valid.
But due to the root access you were also able to modify system files and apps can recognize that you have root access. So you can still use the bravia engine for example (DRM-Keys are ok). But the Google Play Store will still recognize that you have root and will not let you download movies.
This is my experience with Root ... If something is not correct, please correct me
UserX10 said:
Hi,
maybe I can help you.
Bootloader is like the BIOS of a PC. It checks everything at start up.
Locked Bootloader only allows to run the Stock FW and in this case the DRM-Keys are working (everything is checked and safe)
Unlock the Bootloader means you were able to install an modified / other FW and then you loose the DRM-Keys (the manufacturer hasn´t checked the FW and it is in the eyes of an manufacturer "not safe". You will also loose your warranty.
If you unlock the bootloader Root is always possible as I know.
In this case the system is not from the manufacturer and unofficial modification could be done to the system. Normally all modified Systems have Root access. So you were able to do things that the manufacturer has normally not allowed. Modify system files or something like that. Also it could be possible to copy for example a downloaded and payed movie to another device. This is why you were not able to download a movie on the Play Store if you have root. On a locked bootloader the FW (system) does not give you the possibility to copy the movie to an other device and everything is "safe" (from the view of companies). No illegal copies are possible. (DRM-Keys)
Since some days Root is also possible on a locked bootloader.
The bootloader is checking the status (locked) .. then checking the FW (stock) ... DRM-Keys still valid.
But due to the root access you were also able to modify system files and apps can recognize that you have root access. So you can still use the bravia engine for example (DRM-Keys are ok). But the Google Play Store will still recognize that you have root and will not let you download movies.
This is my experience with Root ... If something is not correct, please correct me
Click to expand...
Click to collapse
Hi and thanks a lot for your reply, helped me understand the difference of both better!
If I only root but do not unlock my bootloader will I be able to do anything other than using custom firmware (ROMs)? Will I be able to install Apps that require root or install custom modification like the ones offered on this forum that need to be "flashed in recovery" if I only root not unlock my bootloader?
Also, still looking for some pros and cons (my second question in the original post).
Appreciate all your help!
root will give you access to recovery (in time - still in development) and you can install apps that require root access
custom mods - yes you can install them via recovery and some can be installed with root access and without recovery
if u unlock bootloader you will lose bravia engine not sure bout gracenote as i dont use it
you can check this thread http://forum.xda-developers.com/showthread.php?t=2154310 too see what have people wrote bout
rooting with unlocked bootloader
The main thing pointing me towards unlocking bootloader (I'm already rooted on locked bootloader) is being able to install kernels and major roms.
For example, you could flash Doomlords kernel and over clock the processor a bit, but you could also reduce power and save battery
The major roms I speak of are the ones that are kinda cross device: CyanogenMod and Paranoid Android to name 2. CM is based on pure android, no Sony changes so we can't flash that on locked bootloaders as it requires changing kernel. PA is same.
As for the downsides. I'm not too bothered about DRM keys. I use Spotify for music so don't think I need gracenote. Never watched a movie on my phone. BE2 isn't my cup of tea... Over saturates everything.
I'm going to look into DRM keys more tomorrow, but if someone can correct anything I've written then please do
Not being able to restore via Sony tools... Isn't that bad as you're going to be using flash tool a lot so you'll be used to that. Just keep a generic stick firmware .ftf around in case something goes horrendously wrong (usually recovery backup is enough I think).
Sent from my C6603 using Tapatalk 2
Nice thread, I had this question too
It's my first android and I guess I should unlock the bootloader and then root, this way I won't have to wipe my data later when I decide to try cyanogenmod or something else?
Also what happens if sony release 4.2? Will I lose my bootloader unlock and root?
Al Gore said:
Nice thread, I had this question too
It's my first android and I guess I should unlock the bootloader and then root, this way I won't have to wipe my data later when I decide to try cyanogenmod or something else?
Also what happens if sony release 4.2? Will I lose my bootloader unlock and root?
Click to expand...
Click to collapse
I would say root without unlock for now.
When you want to try cyanogenmod or others. Just backup everything using titanium backup and then u can restore after unlocking.
Rooting with a locked bootloader means sony are not aware your bootloader is unlocked
Sent from my C6603 using xda premium
Thanks for all your replies, helped me out a ton!
I think Im gonna root without unlocking bootloader for now to get my feet wet and get a grasp of it's capabilities and limits. Can always restore the phone if I screw up and can always unlock bootloader later if I need it.
Al Gore said:
Nice thread, I had this question too
It's my first android and I guess I should unlock the bootloader and then root, this way I won't have to wipe my data later when I decide to try cyanogenmod or something else?
Also what happens if sony release 4.2? Will I lose my bootloader unlock and root?
Click to expand...
Click to collapse
If you unlock Bootloader, you shouldn't update from Sony. Since you've (hypothetically) already unlocked, you already have 4.2 avaliable from FXP and if you really want the Sony Update maybe you could flash it via flash tool. Bootloader unlock will never be lost (until someone can create an explicit relock file, but customs roms won't relock it). Root maybe lost if you flash a rom without it but you should be able to get it back easy.
With locked bootloader, we have to wait for Sony to bring 4.2 as we can't access the kernel, but we retain the ability to use the official updates. If we're rooted and we update, we are no longer rooted and we may be unable to use the same exploit.
Sent from my C6603 using Tapatalk 2
hello everyone.
i bought my phone from china, arrived yestarday all jolly good, it came with 4.2.2 rooted and bootloader locked (i presume because BE was working, i never bothered checking).
the shinese version it came with was bloated with baidu and chinese stuff so i decided to flash it with a new rom.
followed the guide to get a rooted 4.2.2, first i installed HK version of fw 310, installed cwm flashed system rom etc...
everything worked perfectly fine and now i have a clean original rooted with cwm 4.2.2 firmware.
BUT i discovered BE is gone and when i go to *#*#service#*#* it sais my bootloader is unlocked! although i never did anything to unlock it!
now, i did do a TA backup before i flashed the new rom and backup went fine, but when i try to relock it goes through the proccess, sais everything went fine but nothing happens.... BE is still gone and service menu still sais i have unlocked bootloader...
EDIT:
i had a cwm backup from the original rom, i restored it, bootloader is not unlocked there, BE is gone... the first time i used it it was there.
tried to restore TA to that state which is the one i took the TA backup in and nothing happens...
On configuration (Service menu) does it says Bootloader unlock allowed: Yes? or it says Bootloader unlocked: Yes?
sijav said:
On configuration (Service menu) does it says Bootloader unlock allowed: Yes? or it says Bootloader unlocked: Yes?
Click to expand...
Click to collapse
Bootloader unlocked: Yes
I'm thinking now mybe the seller sold it to me unlocked in the first place :/
a little bummer, but since the only lost is BE in pictures gallery (BE for videos still works) it's no big loss.
for pictures it's better to see them how they really are, for videos BE is actually cool, it improves them.
Hiya! I was in the process of unlocking my bootloader. I flashed a 28.0.A.8.266_R12A_Hong King Generic rom and on the process of fastbooting to unlock the bootloader. I have tried both methods for the command prompt as well as using the flashtool versions 0.9.19 and 0.9.23, to no avail. I've already acquired my key from sony, and respectively replaced the usb driver file indicated to be replaced, disabled my xperia and did the appropriate steps and it says:
FAILED <remote:Command not allowed>
I have already checked with the configuration wherein the rooting status indicates that Bootloader unlock allowed:Yes
I have been scouring the whole day for any plausible solution, right now I have flashed a 6.0.1 and have lost my capabilities of connecting to my mobile internet for some apparent reason and my network/signal has become mundane. Which my case is very similar to the gentleman that posted this Link
Any plausible assistance or solution would be very welcome and very much appreciated. Thank you so much in advance!
On another note, I was wondering if the region of the firmware affects any of the configuration of the signal acquisition or what not, it has been very disheartening to lose my mobile network. But then again thank you very much for any insight whatsover.
EDIT: Solve - Please take down if necessary
Updated to latest firmware in Nougat. It currently has an enable oem to unlock bootloader in developer options. Tick that off then try unlocking bootloader again once all initial conditions are met.
[E6533] Boot Loader Unlock: FAILED <remote:Command not allowed
try this
https://www.youtube.com/watch?v=Qkl9UyrQKSo
try to disable driver check signature
use the lastest update of flashtool
avid_reader said:
Hiya! I was in the process of unlocking my bootloader. I flashed a 28.0.A.8.266_R12A_Hong King Generic rom and on the process of fastbooting to unlock the bootloader. I have tried both methods for the command prompt as well as using the flashtool versions 0.9.19 and 0.9.23, to no avail. I've already acquired my key from sony, and respectively replaced the usb driver file indicated to be replaced, disabled my xperia and did the appropriate steps and it says:
FAILED <remote:Command not allowed>
I have already checked with the configuration wherein the rooting status indicates that Bootloader unlock allowed:Yes
I have been scouring the whole day for any plausible solution, right now I have flashed a 6.0.1 and have lost my capabilities of connecting to my mobile internet for some apparent reason and my network/signal has become mundane. Which my case is very similar to the gentleman that posted this Link
Any plausible assistance or solution would be very welcome and very much appreciated. Thank you so much in advance!
On another note, I was wondering if the region of the firmware affects any of the configuration of the signal acquisition or what not, it has been very disheartening to lose my mobile network. But then again thank you very much for any insight whatsover.
EDIT: Solve - Please take down if necessary
Updated to latest firmware in Nougat. It currently has an enable oem to unlock bootloader in developer options. Tick that off then try unlocking bootloader again once all initial conditions are met.
Click to expand...
Click to collapse
Have you checked the "USB debugging mode". it should be on
Follow this Link: Link
Hiya all!
Thanks for responses! I've actually resolved it for the e6533. I've updated to the latest firmware via the xperia companion and then in the developer options they have a new option which is unlock oem which permitted me to unlock bootloader through fastboot. Thank you again for the ideas!
I have rolled back from Anddroid 7.0 Nougat with EMUI 5.0 to Android 6.0 with EMUI 4.1.1, Now i want to go back to latest Android 7.0 , I dont know how to do it. Update app/HiSuit/HiCare app Says no update available.
My current Build is EVA-L19C185B180
md sabuj said:
I have rolled back from Anddroid 7.0 Nougat with EMUI 5.0 to Android 6.0 with EMUI 4.1.1, Now i want to go back to latest Android 7.0 , I dont know how to do it. Update app/HiSuit/HiCare app Says no update available.
My current Build is EVA-L19C185B180
Click to expand...
Click to collapse
Download from Firmware Finder and install by DLOAD FullOTA-MF-PV (PV is important) EVA-L19c185b385, as on the screenshot
Or, follow the guide to rebrand to c432 and upgrade to Noogat (unlocked Bootloader is required):
https://forum.xda-developers.com/showpost.php?p=72153575&postcount=2
zgfg said:
Download from Firmware Finder and install by DLOAD FullOTA-MF-PV (PV is important) EVA-L19c185b385, as on the screenshot
Or, follow the guide to rebrand to c432 and upgrade to Noogat (unlocked Bootloader is required):
https://forum.xda-developers.com/showpost.php?p=72153575&postcount=2
Click to expand...
Click to collapse
I have successfully upgraded to Android 7.0 Nougat by the help of firmware finder app .
My current Build is EVA-L19C185B403.
Is there anyway to upgrade to Oreo without unlocking Bootloader? I don’t have a card to buy code from DCunlock.
md sabuj said:
I have successfully upgraded to Android 7.0 Nougat by the help of firmware finder app .
My current Build is EVA-L19C185B403.
Is there anyway to upgrade to Oreo without unlocking Bootloader? I don’t have a card to buy code from DCunlock.
Click to expand...
Click to collapse
No, you cannot flash TWRP and from TWRP the oeminfo and no-check recovery, network patch... without the unlocked Bootloader
zgfg said:
No, you cannot flash TWRP and from TWRP the oeminfo and no-check recovery, network patch... without the unlocked Bootloader
Click to expand...
Click to collapse
I have found some videos and Threads saying some Huawei's Tool can read Bootloader Code.
Is it true?
md sabuj said:
I have found some videos and Threads saying some Huawei's Tool can read Bootloader Code.
Is it true?
Click to expand...
Click to collapse
I don't know anything about 'some' such tools
DC Unlocker for 4 Euros will work for EMUI 5
zgfg said:
I don't know anything about 'some' such tools
DC Unlocker for 4 Euros will work
Click to expand...
Click to collapse
Thank you?
zgfg said:
I don't know anything about 'some' such tools
DC Unlocker for 4 Euros will work for EMUI 5
Click to expand...
Click to collapse
How much credits I have to buy from DC Unlocker for bootloader code?
md sabuj said:
How much credits I have to buy from DC Unlocker for bootloader code?
Click to expand...
Click to collapse
4 Euros was enough for me two years ago (also P9).
Don't know if prices changed, but they have contact page and ask them directly
zgfg said:
4 Euros was enough for me two years ago (also P9).
Don't know if prices changed, but they have a contact page and ask them directly
Click to expand...
Click to collapse
Brother, I have bought 4 credits from Dc Unlocker and successfully read Bootloader Code, Now will you please guide me on how to unlock the bootloader and rebrand for upgrading to Oreo?
md sabuj said:
Brother, I have bought 4 credits from Dc Unlocker and successfully read Bootloader Code, Now will you please guide me on how to unlock the bootloader and rebrand for upgrading to Oreo?
Click to expand...
Click to collapse
First, keep your code (on several places, even printed on the paper), it is good for relocking/unlocking (you never know, some actions may lock the Bootloader back) for the lifetime of your phone.
You don't want to go buying the same thing again
Assuming you know how to enable OEM Unlock in Developer's menu and you are a little familiar with Fastboot, it is simple to unlock the Bootloader
Code:
fastboot oem unlock <your code>
If not familiar, and if not clear as below, search on Google how to:
- enable Developer menu by clicking 7 times to the build number in Settings/About
- enable OEM unlock in Developer menu
- install "Minimal ADB and Fastboot" to Windoze (smallest, self containing package with everything for ADB and Fastboot)
- reboot to Fastboot: keep pressing Vol-, then Pow button
Unlocking Bootloader triggers hard-reset, wiping also Internal memory. Backup as much as you can - use Google account, HiSuite, WA own chat backup, copy DCIM to PC, Contacts can be exported to vcard file, etc
Rebranding to AL10c00, upgrading to b540 Oreo, applying the neccesary Network patch to make SiM card(s) working - all is in deep details explained in the OP posts:
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
Read two times before you start, and keep the instructions opened on the PC while doing - wrong moves can cause (soft) bricks
zgfg said:
First, keep your code (on several places, even printed on the paper), it is good for relocking/unlocking (you never know, some actions may lock the Bootloader back) for the lifetime of your phone.
You don't want to go buying the same thing again
Assuming you know how to enable OEM Unlock in Developer's menu and you are a little familiar with Fastboot, it is simple to unlock the Bootloader
Code:
fastboot oem unlock <your code>
If not familiar, and if not clear as below, search on Google how to:
- enable Developer menu by clicking 7 times to the build number in Settings/About
- enable OEM unlock in Developer menu
- install "Minimal ADB and Fastboot" to Windoze (smallest, self containing package with everything for ADB and Fastboot)
- reboot to Fastboot: keep pressing Vol-, then Pow button
Unlocking Bootloader triggers hard-reset, wiping also Internal memory. Backup as much as you can - use Google account, HiSuite, WA own chat backup, copy DCIM to PC, Contacts can be exported to vcard file, etc
Rebranding to AL10c00, upgrading to b540 Oreo, applying the neccesary Network patch to make SiM card(s) working - all is in deep details explained in the OP posts:
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
Read two times before you start, and keep the instructions opened on the PC while doing - wrong moves can cause (soft) bricks
Click to expand...
Click to collapse
Thank you, Brother, I have done all procedure and my device is now at Oreo, Build EVA-AL10 8.0.0.540(C00).
After doing all the required steps I have flashed Huawei's Official Recovery and enabled OTA, after that I have received an OTA update of 3 MB, Should I install the update or not?
SCREENSHOT
https://drive.google.com/file/d/1s9c7zZoN8fJ3Xq62DW1GAL2P_9maq1Bn/view?usp=sharing
md sabuj said:
First, keep your code (on several places, even printed on the paper), it is good for relocking/unlocking (you never know, some actions may lock the Bootloader back) for the lifetime of your phone.
You don't want to go buying the same thing again
Assuming you know how to enable OEM Unlock in Developer's menu and you are a little familiar with Fastboot, it is simple to unlock the Bootloader
Thank you, Brother, I have done all procedure and my device is now at Oreo, Build EVA-AL10 8.0.0.540(C00).
After doing all the required steps I have flashed Huawei's Official Recovery and enabled OTA, after that I have received an OTA update of 3 MB, Should I install the update or not?
SCREENSHOT
https://drive.google.com/file/d/1s9c7zZoN8fJ3Xq62DW1GAL2P_9maq1Bn/view?usp=sharing
Click to expand...
Click to collapse
It is safe, just some Patch02 (never found exactly what for).
If you don't mind, you can skip (you can disable OTA - see in OP)
If you go for, you must first flash back the stock Recovery, hence not having TWRP. Not sure anymore, maybe also stock Ramdisk, hence not Magisk
Patch02 will not affect Network Patch or Face Unlock (cool add-on, see OP)
If you didn't apply Network patch yet, etc - then accept Patch02 and continue with OP instructions.
If you already rooted by Magisk, then don't bother with Patch02, too much trouble preparing clean sheet for OTA and rooting again
zgfg said:
It is safe, just some Patch02 (never found exactly what for).
If you don't mind, you can skip (you can disable OTA - see in OP)
If you go for, you must first flash back the stock Recovery, hence not having TWRP. Not sure anymore, maybe also stock Ramdisk, hence not Magisk
Patch02 will not affect Network Patch or Face Unlock (cool add-on, see OP)
If you didn't apply Network patch yet, etc - then accept Patch02 and continue with OP instructions.
If you already rooted by Magisk, then don't bother with Patch02, too much trouble preparing clean sheet for OTA and rooting again
Click to expand...
Click to collapse
I have already applied Network Patch, See my both SIM is working.
Right now I don’t need Root so I'm skipping Magisk.
I just want to disappear the update available Notification, if the update is Safe I'll go for it.
zgfg said:
It is safe, just some Patch02 (never found exactly what for).
If you don't mind, you can skip (you can disable OTA - see in OP)
If you go for, you must first flash back the stock Recovery, hence not having TWRP. Not sure anymore, maybe also stock Ramdisk, hence not Magisk
Patch02 will not affect Network Patch or Face Unlock (cool add-on, see OP)
If you didn't apply Network patch yet, etc - then accept Patch02 and continue with OP instructions.
If you already rooted by Magisk, then don't bother with Patch02, too much trouble preparing clean sheet for OTA and rooting again
Click to expand...
Click to collapse
I'm from Bangladesh, some Operator in our country introduced VoLTE.
It seems there is an option called VoLTE after upgrade to Oreo. Is it really works?
md sabuj said:
I'm from Bangladesh, some Operator in our country introduced VoLTE.
It seems there is an option called VoLTE after upgrade to Oreo. Is it really works?
Click to expand...
Click to collapse
Nope, VoLTE does not work.
Everything else, like location sharing and Ok Google are fixed with Network patch, but not VoLTE.
The guy who did the whole majestic work went tired (although he believed he was close to fix VoLTE) and gave up. Later he upgraded to newer Huawei devices with Pie, etc, and eventually moved away from XDA
zgfg said:
Nope, VoLTE does not work.
Everything else, like location sharing and Ok Google are fixed with Network patch, but not VoLTE.
The guy who did the whole majestic work went tired (although he believed he was close to fix VoLTE) and gave up. Later he upgraded to newer Huawei devices with Pie, etc, and eventually moved away from XDA
Click to expand...
Click to collapse
???
zgfg said:
Nope, VoLTE does not work.
Everything else, like location sharing and Ok Google are fixed with Network patch, but not VoLTE.
The guy who did the whole majestic work went tired (although he believed he was close to fix VoLTE) and gave up. Later he upgraded to newer Huawei devices with Pie, etc, and eventually moved away from XDA
Click to expand...
Click to collapse
Brother, How to remove the warning when Phone boots "Your device has been unlocked and can't be trusted"??
md sabuj said:
Brother, How to remove the warning when Phone boots "Your device has been unlocked and can't be trusted"??
Click to expand...
Click to collapse
It's not possible to remove the warning on booting "Your device has been unlocked and can't be trusted" (IMO, it must have been commented somewhere in the OP) - that's price for the unlocked Bootloader.
But you must not relock Bootloader - it would trigger Hard reset, removing Network patch (even worse, it could also cause soft brick if TWRP or Magisk are installed)
15 credits for unlock in fastboot mode (not pay over sms)