[Q] Do I have my facts straight? - Xperia Z3 Q&A, Help & Troubleshooting

Could someone just confirm that I got this right:
-if I want reaver on my phone, I have to root it
-if I root it, I lose low light camera quality
So I have to choose between rooting the phone (for installing reaver, airmon and apps like that, I don't need anything else) and having great low-light camera?

Yep.

It was true 2 weeks ago.
Now that the root method for locked bootloader becomes avaiable so you won't lose the drm keys if you root..

freddy1991 said:
It was true 2 weeks ago.
Now that the root method for locked bootloader becomes avaiable so you won't lose the drm keys if you root..
Click to expand...
Click to collapse
What do you mean?
Is it already available or?....

http://forum.xda-developers.com/showthread.php?t=3011598

To clarify:
Unlocking the bootloader wipes your DRM keys and losing those is what reduces the camera quality (among other things)
Previously, the only way to get root was to unlock the bootloader.
It is now possible (via giefroot exploit) to get root WITHOUT unlocking the bootloader. This means your DRM keys are unaffected.
Once you have root you can actually backup your DRM keys so you are then free to unlock the bootloader if you want (for customer kernels and stuff) and restore your DRM keys afterwards

3Shirts said:
To clarify:
Unlocking the bootloader wipes your DRM keys and losing those is what reduces the camera quality (among other things)
Previously, the only way to get root was to unlock the bootloader.
It is now possible (via giefroot exploit) to get root WITHOUT unlocking the bootloader. This means your DRM keys are unaffected.
Once you have root you can actually backup your DRM keys so you are then free to unlock the bootloader if you want (for customer kernels and stuff) and restore your DRM keys afterwards
Click to expand...
Click to collapse
Yes, but people should also know that restoring your DRM keys relocks the bootloader.
So, you can either have an unlocked bootloader without DRM keys (You can boot a custom kernel so can run CM etc)
or
a locked bootloader with DRM keys. (You cannot boot a custom kernel so are stuck to stock firmware)
You cannot have an unlocked bootloader with DRM keys.

Ah, thanks for the clarification, I didn't realise that. I've not unlocked my BL as I'm happy with root on stock.
Do you need to unlock for a custom rom and, if so, can you unlock, install the rom, and then relock?

3Shirts said:
Ah, thanks for the clarification, I didn't realise that. I've not unlocked my BL as I'm happy with root on stock.
Do you need to unlock for a custom rom and, if so, can you unlock, install the rom, and then relock?
Click to expand...
Click to collapse
If the custom rom relies on a custom kernel then yes you have to unlock. Custom kernels can only boot on an unlocked bootloader.
However, once you relock (Or restore the TA partition containing the DRM keys, this also relocks the boot) then you cannot boot a custom kernel so you get a bootloop until you either unlock again or restore a stock rom.
Locked bootloader = stock kernel only (Custom kernels will cause a bootloop)
Unlocked bootloader = any modified kernel and stock kernel (No DRM keys)

Here's one last question before following this guide http://forum.xda-developers.com/crossdevice-dev/sony/giefroot-rooting-tool-cve-2014-4322-t3011598
If something happens to my phone and I need to get it serviced, is it possible to remove root? Will there be any traces of root, or nobody'll ever know it'd been rooted?

David47 said:
Here's one last question before following this guide http://forum.xda-developers.com/crossdevice-dev/sony/giefroot-rooting-tool-cve-2014-4322-t3011598
If something happens to my phone and I need to get it serviced, is it possible to remove root? Will there be any traces of root, or nobody'll ever know it'd been rooted?
Click to expand...
Click to collapse
Flash a FTF or force repair with pccompanion.
That's removes root and no one can tell.

Related

[Q] Any other method to root without unlocking the bootloader..??

What is a bootloader(tell me in simplest way)....Is unlocking the bootloader really required...? If not then please post another method for root......
ak_wolf007 said:
What is a bootloader(tell me in simplest way)....Is unlocking the bootloader really required...? If not then please post another method for root......
Click to expand...
Click to collapse
watch this video to unlock it https://www.youtube.com/watch?v=iIdJg7KNH3A
and a bootloader allows you to flash kernels/recovers/ and other custom things but only if it is unlocked.
with custom recovery you can install roms,make full system backup,and other things.
a custom kernel wil allow you to overclock cpu/gpu and more.
a custom recovery can be used to flash root.update zip.
but after unlocking bootloader you void your warranty . and your device got hard reset(factory reset)
it can be only unlocked if it is allowed to be unlocked.
android-vinay said:
and a bootloader allows you to flash kernels/recovers/ and other custom things but only if it is unlocked.
Click to expand...
Click to collapse
Not entirely true, at least to all devices. I have a Moto Defy which also has a locked bootloader, no way to unlock, running KK CM11. Developer @pedrodh has managed to create an app called "2ndinit" (1) which allows a second kernel to boot on top of the locked one, allowing to flash new builds despite the locked bootloader. Because of this, Defy is known as unbricable. Similar approach could be used on E3 if some devel take a look into this.
(1) http://forum.xda-developers.com/showthread.php?t=1032212
Regards,
mmerlone said:
Not entirely true, at least to all devices. I have a Moto Defy which also has a locked bootloader, no way to unlock, running KK CM11. Developer @pedrodh has managed to create an app called "2ndinit" (1) which allows a second kernel to boot on top of the locked one, allowing to flash new builds despite the locked bootloader. Because of this, Defy is known as unbricable. Similar approach could be used on E3 if some devel take a look into this.
(1) http://forum.xda-developers.com/showthread.php?t=1032212
Regards,
Click to expand...
Click to collapse
this required root.
for now you need to unlockbootloader to root xperia.
root ur device without unlocking
vinay said:
this required root.
for now you need to unlockbootloader to root xperia.
Click to expand...
Click to collapse
just use kingoroot or kingroot to root ur device no need to unlock boot loader for running those you will have root access but can't do the flashing part

Restoring Drm Keys on Custom Rom's Like Cyanogenmod

I have got a Z3.If we will be able to root without unlock bootloader, i will restore my drm keys.And i will unlock my bootloader and flash cyanogenmod.And i will relock bootloader, restore my drm keys on cyanogenmod.Is it possible?Sorry for bad english?
Not possible. Only a Sony rom can take use of the DRM keys. Cyanogen doesn't use Sonys algorithms.
If we are able to root without unlocking BL, we can backup the TA partition with the DRM keys and you will be able to restore them but as dashrink said, custom Roms which are not based on Sony's official firmware won't be able to use them. But you could always go back to an official (based) firmware and restore the TA partition with the DRM keys.
Well, what can we do for camera's quality on custom rom's?
LeonidasTurk said:
I have got a Z3.If we will be able to root without unlock bootloader, i will restore my drm keys.And i will unlock my bootloader and flash cyanogenmod.And i will relock bootloader, restore my drm keys on cyanogenmod.Is it possible?Sorry for bad english?
Click to expand...
Click to collapse
Once you relock the bootloader CM will not boot.
You need to keep the bootloader unlocked for custom kernels to boot
gregbradley said:
Once you relock the bootloader CM will not boot.
You need to keep the bootloader unlocked for custom kernels to boot
Click to expand...
Click to collapse
What about Xposed? I don't have to change ROM, therefore can I install Xposed and then restore DRM keys? :fingers-crossed:

[Q] DRM Keys Restore

After rooting 4.4.4 I backed up my DRM Keys. Unlocked my bootloader and switched to 5.0.3 with twrp. After that I restored my DRM Keys and now it says "unlock allowed: yes"
First question: does that mean now my bootloader is locked again
Second: how can I be 100% sure if the keys are restored. Because I see no difference in photos and x reality.
Anyone can tell me how to be 100% sure about it.
D6603
Lollipop 5.0.2 stock
Rooted
Locked bootloader
Yes it is locked
Restoring your drm keys automatically rocks your bootloader

Question about keys

so I've become aware you can install recovery even with a locked bootloader.
Is it possible to boot Cyanogen mod (or other custom roms) and then go back to a stock build and still have access to the keys and other default apps or would this require unlocking the bootloader?
Snow_fox said:
so I've become aware you can install recovery even with a locked bootloader.
Is it possible to boot Cyanogen mod (or other custom roms) and then go back to a stock build and still have access to the keys and other default apps or would this require unlocking the bootloader?
Click to expand...
Click to collapse
You cannot install cyanogenmod with a locked bootloader
But with an unlocked bootloader, then yes you can backup DRM keys, install CM, then if you want to go back to stock you can restore the DRM keys after re-locking the bootloader

Does SafetyNet detect bootloader unlock? How about SuperSU systemless root?

I am on the Google variant. I'm curious whether simply unlocking the bootloader will prevent me from using Android Pay (and similarly protected apps). And same question for SuperSU systemless root?
As a bonus, if I were to unlock, root, modify a file (like hosts), then unroot and relock, would it complain?
NegativeOne said:
I am on the Google variant. I'm curious whether simply unlocking the bootloader will prevent me from using Android Pay (and similarly protected apps). And same question for SuperSU systemless root?
As a bonus, if I were to unlock, root, modify a file (like hosts), then unroot and relock, would it complain?
Click to expand...
Click to collapse
If you modify the system and relock the bootloader, you risk bricking the device entirely, if it won't accept fastboot commands
NegativeOne said:
I am on the Google variant. I'm curious whether simply unlocking the bootloader will prevent me from using Android Pay (and similarly protected apps). And same question for SuperSU systemless root?
As a bonus, if I were to unlock, root, modify a file (like hosts), then unroot and relock, would it complain?
Click to expand...
Click to collapse
First question, I think on some firmware, custom Kernel with root is allowing Android Pay for some users on some carriers. I wouldn't universalize, you have to try.
However, only unlocking bootloadet doesn't work, but in addition a custom kernel can fix what breaks is needed.
ndarkside93 said:
If you modify the system and relock the bootloader, you risk bricking the device entirely, if it won't accept fastboot commands
Click to expand...
Click to collapse
Second question:
EXACTLY: the bootloader detects changes in the system partition away from pure stock, so if you change things, that signals "corruption" to the bootlader so it will PREVENT boot and as ndarkside says, RISK OF BRICK
Sent from my sailfish using XDA Labs
nednednerb said:
First question, I think on some firmware, custom Kernel with root is allowing Android Pay for some users on some carriers. I wouldn't universalize, you have to try.
However, only unlocking bootloadet doesn't work, but in addition a custom kernel can fix what breaks is needed.
Second question:
EXACTLY: the bootloader detects changes in the system partition away from pure stock, so if you change things, that signals "corruption" to the bootlader so it will PREVENT boot and as ndarkside says, RISK OF BRICK
Click to expand...
Click to collapse
Very true, but on the pixel with the November update, safety net checks for bootloader unlock, but I think Franco kernel can hide it to pass the check, if there is no root.

Categories

Resources