Aosp android 6.0 marshmallow - Xperia Z4 Tablet General

Sony released binaries and build instructions for aosp 6.0 android for our xperia z4 tablet.
What else is necessary for developers to build AOSP android 6.0 for our sgp771 devices?
Here are the links:
http://developer.sonymobile.com/downloads/tool/software-binaries-for-aosp-m-android-6-0/
https://github.com/sonyxperiadev/device-sony-karin
Please developers build AOSP android 6.0 for our devices
Enviado de meu SM-N920G usando Tapatalk

Really, we beg you to build some more customs roms for our device, because now it even useless to root our device as there is no roms and we lose drm keys((((((((

I don't understand why Sony posts AOSP source code, build instructions, but no AOSP binaries.
I'm keeping an eye out on the FXP Marshmallow page, but so far it's been empty.

alex009988 said:
Really, we beg you to build some more customs roms for our device, because now it even useless to root our device as there is no roms and we lose drm keys((((((((
Click to expand...
Click to collapse
Whether you root or not does not depend on a custom rom. It depends on what apps you want to use. If you want to use apps like Titanium Backup, Adaway and so on you need root. And root can be achieved quite easy.

akxak said:
Whether you root or not does not depend on a custom rom. It depends on what apps you want to use. If you want to use apps like Titanium Backup, Adaway and so on you need root. And root can be achieved quite easy.
Click to expand...
Click to collapse
But currently that means losing the TA partition doesn't it, from what I have been reading?

scoobydu said:
But currently that means losing the TA partition doesn't it, from what I have been reading?
Click to expand...
Click to collapse
If that's where the drm keys are, yes... but not due to rooting, but due to unlocked bootloader.

akxak said:
If that's where the drm keys are, yes... but not due to rooting, but due to unlocked bootloader.
Click to expand...
Click to collapse
Sure but in order to root you need to unlock the bootloader which in itself is fine, but you'll lose the TA and yes the DRM keys in the TA.

scoobydu said:
Sure but in order to root you need to unlock the bootloader which in itself is fine, but you'll lose the TA and yes the DRM keys in the TA.
Click to expand...
Click to collapse
Sorry can someone explain to me what is the TA and DRM keys? I had samsung tablet before xperia z4 tablet. I can not understand those terms. What will I lose if I install aosp android? Will I be able to reflash stock Sony firmware if I want to roll back? Where can I get the original firmware and flash tools for Windows so that I can revert back from aosp install to stock Sony firmware? And finally what will I lose after aosp android install?
Can you guys post a video of aosp android running in your xperia z4 tablet?
Enviado de meu SM-N920G usando Tapatalk

calj17 said:
Sorry can someone explain to me what is the TA and DRM keys? I had samsung tablet before xperia z4 tablet. I can not understand those terms. What will I lose if I install aosp android? Will I be able to reflash stock Sony firmware if I want to roll back? Where can I get the original firmware and flash tools for Windows so that I can revert back from aosp install to stock Sony firmware? And finally what will I lose after aosp android install?
Can you guys post a video of aosp android running in your xperia z4 tablet?
Enviado de meu SM-N920G usando Tapatalk
Click to expand...
Click to collapse
I have only just received my Z4 yesterday but very much assume its the same as my Z3, Z3Tab, Tab and Ultra.
Sony keep the DRM keys in a special TA partition to allow their proprietary technologies to work, eg their barvia engine for the screen and audio codecs for sound.
If you unlock the bootloader it will remove this partition and your device specific keys will be lost.
Those keys are yours alone and you cannot recover from someone elses.
There have been some apps to try and reinstate those keys, but I have never used them, so cannot comment if they are good.
I usually try and root without unlocking the bootloader, so you can then save your TA partition off device and then unlock.
That way if you want to relock you can reinstate the TA partition and the tech that goes with it.
As there is no root with a locked bootloader currently, that is your only option for the moment if you want root.
I plan on waiting for MM and hoping a common vunerability is present for multple devices, as that was the way I rooted my Z3 Tab, by loader the Z3 phone firmware, rooting and then reloading the Z3 Tab firmware back.

scoobydu said:
I have only just received my Z4 yesterday but very much assume its the same as my Z3, Z3Tab, Tab and Ultra.
Sony keep the DRM keys in a special TA partition to allow their proprietary technologies to work, eg their barvia engine for the screen and audio codecs for sound.
If you unlock the bootloader it will remove this partition and your device specific keys will be lost.
Those keys are yours alone and you cannot recover from someone elses.
There have been some apps to try and reinstate those keys, but I have never used them, so cannot comment if they are good.
I usually try and root without unlocking the bootloader, so you can then save your TA partition off device and then unlock.
That way if you want to relock you can reinstate the TA partition and the tech that goes with it.
As there is no root with a locked bootloader currently, that is your only option for the moment if you want root.
I plan on waiting for MM and hoping a common vunerability is present for multple devices, as that was the way I rooted my Z3 Tab, by loader the Z3 phone firmware, rooting and then reloading the Z3 Tab firmware back.
Click to expand...
Click to collapse
So in your opinion we should not unlock bootloader to install aosp. In resume what changes of I unlock bootloader install aosp and loose this DRM keys ? Won't I be able to reflash stock Sony firmware back and get tablet working as it was before installing aosp?
Enviado de meu SM-N920G usando Tapatalk

calj17 said:
So in your opinion we should not unlock bootloader to install aosp. In resume what changes of I unlock bootloader install aosp and loose this DRM keys ? Won't I be able to reflash stock Sony firmware back and get tablet working as it was before installing aosp?
Enviado de meu SM-N920G usando Tapatalk
Click to expand...
Click to collapse
You will irreversibly lose Sony-proprietary functionality. I cannot provide a full list of what that is because I don't have the complete knowledge, but you will lose camera denoising, PS4 remote play and, as scoobydu mentions, image 'enhancement' functions (X-Reality). There's more, I read it somewhere here on XDA.

what you can find in the SONY fora
jelbo said:
There's more, I read it somewhere here on XDA.
Click to expand...
Click to collapse
[Knowledge Base] Introduction to the Sony (-Ericsson) Xperia Galaxy
Why an exploit seems inmpossible
read the whole thread (altough some outdated infos and offtopic posts)
or the intro to
Custom kernel Z3+ E6553 - Nuke Verity / Sony RIC and allow SELinux permissive
Loss of DRM Keys

ive builded android 6.0 yesterday for the xperia z4 tablets.
when im back home, ill upload the images for android 6.0 for the lte and wifi version

Hundsbuah said:
ive builded android 6.0 yesterday for the xperia z4 tablets.
when im back home, ill upload the images for android 6.0 for the lte and wifi version
Click to expand...
Click to collapse
And how well does it work, camera and so on?))) IS it worse then cyanogenmod, I mean stability?

Hundsbuah said:
ive builded android 6.0 yesterday for the xperia z4 tablets.
when im back home, ill upload the images for android 6.0 for the lte and wifi version
Click to expand...
Click to collapse
Thank you friend. Could you upload a video tutorial on how to install the rom and show it running in your tablet?[emoji1]
Enviado de meu SM-N920G usando Tapatalk

Haven't tested much. I'm back to v5 because I'm not at home and have no mobile data left. So I restored my backup. Wifi was working because I searched for wifi networks

Hundsbuah said:
Haven't tested much. I'm back to v5 because I'm not at home and have no mobile data left. So I restored my backup. Wifi was working because I searched for wifi networks
Click to expand...
Click to collapse
Tell me. After install a aosp rom like yours how can I roll back and install Sony stock firmware back? What will change after this rollback to stock? People at forum told that because is necessary to unlock bootloader to install aosp rom we would lose DRM partition information that has xreality data and tablet profiles so after rolling back to oem flashing the stock firmware is the tablet the same as before? Working fine?
Enviado de meu SM-N920G usando Tapatalk

I restored my system partition with the Linux dd command in twrp via adb shell. Yes u need an unlocked bootloader and the ta partition etc is gone

Hundsbuah said:
I restored my system partition with the Linux dd command in twrp via adb shell. Yes u need an unlocked bootloader and the ta partition etc is gone
Click to expand...
Click to collapse
Great to hear you were running Android 6.0 on your Z4. Mine just arrived today
You seem to have found a way to restore TWRP backups using the dd command. Could you please share the used commands? Because AndroPlus' TWRP build has broken restore functionality, a functional workaround would be more than welcome for us flash-happy xda'ers

calj17 said:
Tell me. After install a aosp rom like yours how can I roll back and install Sony stock firmware back? What will change after this rollback to stock? People at forum told that because is necessary to unlock bootloader to install aosp rom we would lose DRM partition information that has xreality data and tablet profiles so after rolling back to oem flashing the stock firmware is the tablet the same as before? Working fine?
Enviado de meu SM-N920G usando Tapatalk
Click to expand...
Click to collapse
If you are not convinced by others input to your questions, perhaps you should go back over Xperia Z, Z1, Z2, Z3 and Z4 forums to double check.
We would all love to unlock and not lose TA, but its been a 'feature' of Xperia for some time, but I am sure we are all happy to be corrected if Sony have changed things.
If you continually need a video to implement, then perhaps you should not be trying? Just a thought.
Merry Christmas.

Related

[4.4.4] for [SGP521]

Is this Android 4.4.4 to SGP521?
Link
Exciting!
Yes, it is 4.4.4, and it will bring us the new Z3 UI, and some Z3 features.
Bird40 said:
Is this Android 4.4.4 to SGP521?
Link
Click to expand...
Click to collapse
Sure you are not being a bit previous? My Z2 is SGP512, not SGP521! Hope you are right though
UPDATE: Doh! Just realized that both are valid
Very good news
Finally!
Sent from my SGP521 using Tapatalk
The rumour-mill has gone scarily quiet.. I don't understand why, having subscribed to a "premium" product, we don't get "premium" service. Anyone prepared to stir the pot and get the rumours going again?
pdes said:
The rumour-mill has gone scarily quiet.. I don't understand why, having subscribed to a "premium" product, we don't get "premium" service. Anyone prepared to stir the pot and get the rumours going again?
Click to expand...
Click to collapse
Ok, try this one. They're not going to push the 4.4.4 and will go straight to 5L next year
New version
New version
Link
Has anyone been able to update? Mine just failes
Sent fra min D6503 via Tapatalk
Installed and working properly, we only need to root :good:
Bird40 said:
Is this Android 4.4.4 to SGP521?
Link
Click to expand...
Click to collapse
yes, i already got it, any one has recovery?
I managed to install it with dual recovery but I am having issues on mounting the system. Does anyone know how to?
chesterr said:
I managed to install it with dual recovery but I am having issues on mounting the system. Does anyone know how to?
Click to expand...
Click to collapse
But it is compatible? Now try but could
So, what do you guys think about this update? Is it really worth it? Curious to know.
The biggest reason for me to change was to get Remote Play to link with my PS4. Also, the applications button is now shifted to the middle of the bottom edge. Other than that, I haven't noticed any huge changes that blew me away.
Remote Play is pretty cool though, tried it out for a little bit last night and it was good enough to play Call of Duty campaign mode.
chesterr said:
I managed to install it with dual recovery but I am having issues on mounting the system. Does anyone know how to?
Click to expand...
Click to collapse
Need to modify the kernel ramdisk to make it insecure.
Moscow Desire said:
Need to modify the kernel ramdisk to make it insecure.
Click to expand...
Click to collapse
Yea it did ask me about ramdisk btw, guess I'm just gonna wait till PRF Creator tool to be updated,
chesterr said:
Yea it did ask me about ramdisk btw, guess I'm just gonna wait till PRF Creator tool to be updated,
Click to expand...
Click to collapse
Well, technically, it's not such a big deal, to swap kernels/ramdisk with an unlocked bootloader. It's a simple edit. But, at this point, it would mean unlocking bootloader, and losing DRM keys (still not sure what functions besides some lost advanced camera functions, not that anybody uses the camera anyhow except for skype).
Under the old rooting, it used an exploit to modify ramdisk, (and install the necessary apps), without unlocking bootloader via an exploit.
As for me, I will wait a couple weeks and see if there's a new exploit. If not, well, I will do the above method.
Moscow Desire said:
Well, technically, it's not such a big deal, to swap kernels/ramdisk with an unlocked bootloader. It's a simple edit. But, at this point, it would mean unlocking bootloader, and losing DRM keys (still not sure what functions besides some lost advanced camera functions, not that anybody uses the camera anyhow except for skype).
Under the old rooting, it used an exploit to modify ramdisk, (and install the necessary apps), without unlocking bootloader via an exploit.
As for me, I will wait a couple weeks and see if there's a new exploit. If not, well, I will do the above method.
Click to expand...
Click to collapse
Basically DRM keys are used to see if you have unlocked the device (in the past). So mainly for Sony to check if your warranty is still valid.
There is a tool that will backup your DRM keys though, and can restore it too. You just need root for that (just downgrade, root, backup keys and upgrade again) Just Google Xperia DRM backup and you're bound to find out

DRM Function Restore

http://forum.xda-developers.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672
This page contains the latest zip file to restore drm functions. All you need to do now is to do a factory reset and flash the zip,no more back and forth with firmware versions and such.
Like so many others, I unlocked my Z3 D6653's bootloader before Sony made the announcement on their page that unlocking the bootloader will result in losing DRM keys and therefore also losing nice phone features like x-reality, super vivid, low light camera algorithms, Bravia Engine etc..
After a few months of waiting, someone from here actually may have found some sort of solution (or workaround) .. view full thread here if you're interested: http://forum.xda-developers.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672
The instructions for Sony Xperia's vary.. but after a handful of trial and error, I managed to get mine to work by following this instruction from the same thread above:
Quote:
Originally Posted by boolee
1.Flash ftf file "23.0.1.A.5.77" by Flashtool. - Wipe appslog, cache, data - and reset customizations
2.Relock bootloader by Flashtool.
3.Flash ftf file "23.0.1.A.5.77" by Flashtool AGAIN. - Wipe appslog, cache, data
4.Unlock bootloader by Flashtool.
5.Flash boot.img "AndroPlusKernel v12" by Fastboot.
6.Install DRM restore zip by TWRP.
7.reboot.
Requirements:
Unlocked bootloader
flashtool
.77 based firmware for D6653 (I tried several firmwares but the one that worked for me was the .77 firmware for PH market downloaded from flashtool)
AndrosPlusKernel v15 (extracted boot.img from the zip to be flashed)
DRM restore zip from that original thread above (placed in sd card)
Note - Key here is to not restart/boot the phone after each step in the instructions above. Just keep phone off and unplugged after each step. I realized that leaving the phone connected in flashmode for a while will make it boot, so I just unplugged it while waiting for flashtool to prepare FTF for flashing. Then plug it in again with vol down button pressed.
Results:
Unlike my previous attempts of trying to recover DRM functions, I did not see any difference using the Album app, no matter what settings I changed in display. (xreality, super vivid etc) But after following the steps above, I immediately see changes when I change the display settings. Changing the settings and going back to the Album app, I see that the pictures will darken or lighten a bit depending on what I choose. I have yet to try Miracast or PS4 remote as I do not have any of those hardware to test.
Warning:
Now, I am not saying that this will work for everybody. It worked for me and hopefully it will also work for those who have gone and unlocked their BL and ended up with a phone with lesser features. I am not saying that you should go ahead and unlock your BL.
Notes:
If you're willing to try the steps, you may want to thank the original thread starter from the link above. Also, please post feedbacks here and give info of what version of Z3 you are using. The original thread is a bit of a jungle with all Z users posting all sorts of info.
I am not taking any credit for the instructions or tools, just merely passing information along to my fellow z3 users.
The drm function has also worked for me on. 77 firmware.
Thanks mate taking your time to post instructions for others benefit
Sent from my D6653 using XDA Free mobile app
If I haven't unlocked my bootloader how do I unlock without losing drm Keys?
Sent from my D6653 using XDA Free mobile app
veeny101 said:
If I haven't unlocked my bootloader how do I unlock without losing drm Keys?
Sent from my D6653 using XDA Free mobile app
Click to expand...
Click to collapse
As of the moment, there is no way of unlocking BL without losing drm keys.
So I have to unlock, lose my drm Keys then follow this steps to get it back?
Sent from my D6653 using XDA Free mobile app
veeny101 said:
So I have to unlock, lose my drm Keys then follow this steps to get it back?
Sent from my D6653 using XDA Free mobile app
Click to expand...
Click to collapse
Wait for more feedback from other users before you go ahead and do that.
veeny101 said:
So I have to unlock, lose my drm Keys then follow this steps to get it back?
Click to expand...
Click to collapse
This is NOT really restore DRM !
Once you UL all DRM will be destroy.
This only copy a patched drm lib so the drm function work again, so drm "function" restore.
Ok. So how's the low light camera?
Sent from my D6653 using XDA Free mobile app
johan8 said:
This is NOT really restore DRM !
Once you UL all DRM will be destroy.
This only copy a patched drm lib so the drm function work again, so drm "function" restore.
Click to expand...
Click to collapse
Any way to compare DRM vs. patched DRM?
Due to it being unique for every device, it will always compare differently.
I have seen this a couple of days ago, I was actually wondering if Remote Play (PS4) gets restored as well. I know it is not specified in the patch thread, but would be the only feature left out from this fix! Has anyone tried to use it?
do we really need AndroPlusKernel v12 kernel for this?
I can confirm PS4 Remote play doesn't work after doing this, it still shows C-80F80A01 error.
hackarchive said:
do we really need AndroPlusKernel v12 kernel for this?
Click to expand...
Click to collapse
not really..you can try experimenting with a rom of your choice..
yikuncc said:
I can confirm PS4 Remote play doesn't work after doing this, it still shows C-80F80A01 error.
Click to expand...
Click to collapse
Thanks for the update..
That's good to know I paid $630 for this phone and even though I'm not a gamer I don't want to lose any features that are built in.
Sent from my D6603 using XDA Free mobile app
Where I can find the (.77 FTF) for D6603. 93? Thank you!
Note 4, SM-910C Model.
charlypaez said:
Where I can find the (.77 FTF) for D6603. 93? Thank you!
Note 4, SM-910C Model.
Click to expand...
Click to collapse
Just use flashtool
dashrink said:
Just use flashtool
Click to expand...
Click to collapse
I'm trying to do a restore of DRM Functions with @AndroPlus Steps.. But I don't know where I can find the FTF file for this... My Model is D6603 (.93)...
yikuncc said:
I can confirm PS4 Remote play doesn't work after doing this, it still shows C-80F80A01 error.
Click to expand...
Click to collapse
Mine also after doing this. All other features are pretty much useless for me. X reality and super vivid only works using the stock album but i use third party aps to view pictures. And i dont take pictures at dark places. It is not worth the effort if you dont use these features. I want the remote play fixed
Sent from my D6633 using Tapatalk 2
After numerous tries i finally successfully restored DRM functions - the trick for me was to not turn the device on.
Now i'm wondering, can i flash new versions of the kernel(Andro) and other flashables, without losing the DRM funcions. Should i reflash the DRM.zip every time i flash some a new version of the kernel or it's just 1 time thing?

Xperia Z4/Z3+ Root Discussion

There appears to be no discussion thread about root for the Z4/Z3+, so I thought one was in order.
I'm currently about as useful as a snooze button on a smoke alarm in terms of obtaining root. I'm curious - is there any development going on to root our devices? I'd love to donate and what not to possibly speed it up.
Let's talk!
BL unlock is not listing this device on Sony open devices
Flashtool from androxyde doesn't have the device listed as well, so I doubt BL could be unlocked.
Regarding development
I managed to unpack the blog_fs FILE'S from Emma so there we have the kernel.sin maybe we could unpack it with Android image kitchen, but I didn't succeed, Android magic was missing or something like that!?
If that could be possible, then we could repack twrp radish with zimage of the kernel.sin and perhaps have a working recovery maybe as FOTAkernel.
But that's just wishful thinking
First we need unlocked BL
And then we also have all the loss of DRM keys. TA partition and all that also needs to be in place, unless we're willing sacrifice a bit hehe...
Sent from my E6553 using XDA Free mobile app
I'm also interested in Rooting my device, but the question is; would the dual Sim (E6533) be different than the single Sim device (in terms of rooting of course)?
Sent from my E6533 using XDA Free mobile app
I unlocked my Z4T SGP712 (WiFi)
Could it work as well?
You can unlock your device by chosing Z3... No need for Z4/Z3+ on Sony Unlock page.
GhostLeader said:
I unlocked my Z4T SGP712 (WiFi)
Could it work as well?
You can unlock your device by chosing Z3... No need for Z4/Z3+ on Sony Unlock page.
Click to expand...
Click to collapse
Even with a bootloader unlock, is there any custom recovery for the Z3+?
Sent from my Xperia Z3+ E6553
Did any one try to unlock their Sony Xperia Z+ yet? Or any one try to see if it is unlockable by following steps.
You can check if it is possible to unlock the boot loader of your device in the service menu by following the steps below: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.
I am going to build a custom recovery incase the bootloader unlock allow says Yes..
Update: Yes it is allow to unlock the bootloader. I am waiting for my device then start working
Sent from my LG-H815 using Tapatalk 2
janjan said:
Did any one try to unlock their Sony Xperia Z+ yet? Or any one try to see if it is unlockable by following steps.
You can check if it is possible to unlock the boot loader of your device in the service menu by following the steps below: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.
I am going to build a custom recovery incase the bootloader unlock allow says Yes..
Update: Yes it is allow to unlock the bootloader. I am waiting for my device then start working
Sent from my LG-H815 using Tapatalk 2
Click to expand...
Click to collapse
Yup, mine allows the bootloader to be unlocked too. I would think that the international version should allow for that
Look forward to your custom recovery then!
boo85 said:
Yup, mine allows the bootloader to be unlocked too. I would think that the international version should allow for that
Look forward to your custom recovery then!
Click to expand...
Click to collapse
I'm quite looking forward to it as well. If we can get a custom recovery going, then we'll be able to get root right? It's just a matter of being able to flash SuperSU through the custom recovery? Pardon my ignorance.
AhsanU said:
I'm quite looking forward to it as well. If we can get a custom recovery going, then we'll be able to get root right? It's just a matter of being able to flash SuperSU through the custom recovery? Pardon my ignorance.
Click to expand...
Click to collapse
Its a step but we need to find a root exploit too
Sent from my E6553 using Tapatalk
Ok, got mine a few days ago. Tranfer of apps and data was sh**** as hell without titatnium backup!
I don't have any usable knoledge in programming, but if there's something to test or try, I'm volunteering
If some of the devs for other xperias has any idea, I'll test it.
Hoping to get root, very soon.
the_brad said:
Ok, got mine a few days ago. Tranfer of apps and data was sh**** as hell without titatnium backup!
I don't have any usable knoledge in programming, but if there's something to test or try, I'm volunteering
If some of the devs for other xperias has any idea, I'll test it.
Hoping to get root, very soon.
Click to expand...
Click to collapse
Yup, same here. I'll test if needed =)
xDope said:
Yup, same here. I'll test if needed =)
Click to expand...
Click to collapse
Me too! Single SIM Z3+.
my Dual Sims E6533 says that bootloader unlock is not allowed. Does that mean my phone cannot be rooted? I think its the HK version, I got it on Amazon in the USA. Any tips or advices would be greatly appreciated. Thanks!
projectseahorse said:
my Dual Sims E6533 says that bootloader unlock is not allowed. Does that mean my phone cannot be rooted? I think its the HK version, I got it on Amazon in the USA. Any tips or advices would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
By right if the bootloader unlock is stated as not allowed, you can only root your phone through an exploit. Other xperia phones exploits have been found (like my previous z2, i rooted it without unlocking the bootloader), I most certainly do hope one can be found for z3+ as it would allow all the DRM stuff to be backed up and its "neater" imo.
Otherwise, if no exploit is found, then no, you would not be able to root without unlocked the bootloader to install a custom rom.
However please check if you signed in to myXperia service. If you did, you just need to sign out and reboot, then your status would be back to allowed. That is only if originally the bootloader is allowed to be unlocked.
boo85 said:
By right if the bootloader unlock is stated as not allowed, you can only root your phone through an exploit. Other xperia phones exploits have been found (like my previous z2, i rooted it without unlocking the bootloader), I most certainly do hope one can be found for z3+ as it would allow all the DRM stuff to be backed up and its "neater" imo.
Otherwise, if no exploit is found, then no, you would not be able to root without unlocked the bootloader to install a custom rom.
However please check if you signed in to myXperia service. If you did, you just need to sign out and reboot, then your status would be back to allowed. That is only if originally the bootloader is allowed to be unlocked.
Click to expand...
Click to collapse
Thanks! My dual E6533 is not allow unlock too. Than I sign out myXperia and reboot, It becomes to Yes.
boo85 said:
By right if the bootloader unlock is stated as not allowed, you can only root your phone through an exploit. Other xperia phones exploits have been found (like my previous z2, i rooted it without unlocking the bootloader), I most certainly do hope one can be found for z3+ as it would allow all the DRM stuff to be backed up and its "neater" imo.
Otherwise, if no exploit is found, then no, you would not be able to root without unlocked the bootloader to install a custom rom.
Click to expand...
Click to collapse
At this point, I see no mention of anyone working on any sort of exploit for the Z3+, this is a bit disheartening! I'm considering the new OnePlus device at this point since I'm sure root will not be an issue for that phone. It'd be a shame if it came to that since I love the feel of the Z3+
Sent from my Xperia Z3+ E6553
mine said no. Does that mean I can never install a custom recovery and custom ROMS?
boo85 said:
Yup, mine allows the bootloader to be unlocked too. I would think that the international version should allow for that
Look forward to your custom recovery then!
Click to expand...
Click to collapse
GCbard said:
mine said no. Does that mean I can never install a custom recovery and custom ROMS?
Click to expand...
Click to collapse
Did you activate your MyXperia app? If so, this could result in your phone indicating that the bootloader is not unlockable, even though it actually is. If you didn't activate this app and it still says no, then yes, it's not unlockable and you will not be able to install custom kernels / ROMs. Note that custom recovery can still work on rooted phones with locked bootloaders.
hush66 said:
Did you activate your MyXperia app? If so, this could result in your phone indicating that the bootloader is not unlockable, even though it actually is. If you didn't activate this app and it still says no, then yes, it's not unlockable and you will not be able to install custom kernels / ROMs. Note that custom recovery can still work on rooted phones with locked bootloaders.
Click to expand...
Click to collapse
i looked into my applications and did not see a myxperia app. Just xperia lounge. I did install the current firmware using sony pc companion.
I am new to xperia. I had htc one and google nexus phones prior to this that I have rooted and such. I am experience but not in xperia. Any suggestions for rooting that you know works>
uhm where is this myXperia app you guys are talking about? I searched the app store and the phone and cannot find it. Under settings, there is a "Xperia Connectivity" section, but no option to sing out.
Googling the app did give some results and I did land on this page, which I was logged into. I logged out and rebooted the phone, still says "No" to unlock bootloader.

[WIP] [LB] [TEMP ROOT] Z5/Z5C Backup of TA Partition / DRM Keys

Hello to everybody!
::::: A FEW WORDS BEFORE YOU ASK 100 TIMES THE SAME ;-P :::::
It has been told widely in these forums that permanent root on LB is impossible due to Verified Boot process implemented by Sony (and now by other vendors. Future for LB devices seems to be "Live root" approach). What we would like to achieve is temporary root privileges using some exploit in order to backup the TA partion, for warranty purposes and for complete stock DRM restore.
THIS ARTICLE IS A WONDERFUL ENTRY POINT IF YOU WANT MORE INFORMATION[/B]
Guys, i am very proud that we could win user zxz0O0 for trying out abilities to use the CVE-2015-1805 security vulnerability to get temporary privileges for i. e. backup of TA Partition of our Xperia Z5/Z5C/Z5P.....
For those who want to know a little bit more of what about we are discussing/ testing here:
Android Security Advisory — 2016-03-18: https://source.android.com/security/advisory/2016-03-18.html
CVE: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1805
German article from t3n.de: http://t3n.de/news/google-android-sicherheitsluecke-691418/
CURRENT STATUS:
- ZXZ0O0 HAS FINISHED HIS WORK +++ Release for Z5/ Z5C/ Z5P coming soon!
You will need to flash build 32.0.A.6.200 kernel or lower!
LET US THANK:
- ZXZ0O0 FOR HIS AMAZING EFFORTS AND HIS PASSION INTO THIS
- IDLER1984 FOR HIS TESTCODE
- FOR TESTING ZXZ0O0's BUILDS: NINESTARKOKO, RIMMEDA, NILEZON AND ALL OTHERS IF I FORGOT SOMEONE
Greets and Cheers, Your Flummi.FFM
Well, we got Linux Kernel 3.10, which is affected by this exploit. This could make root possible, but we have to know how the root app is called ?
i will look as soon as i have time here
Lurking
old news mate.
http://forum.xda-developers.com/xperia-z5/general/root-using-vulnerabilities-snapdragon-t3338173
another forummer already pinted this out.
unless you know how to roll back old linux kernel and over come SElinux
Flummi.FFM said:
Good morning to everyone!
Just a few minutes ago on the way to my workplace i just found an article about the CVE-2015-1805 security issue.
Sources:
Android Security Advisory — 2016-03-18: https://source.android.com/security/advisory/2016-03-18.html
CVE: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1805
German article from t3n.de: http://t3n.de/news/google-android-sicherheitsluecke-691418/
Is THIS what we all waited for to get root on Locked Bootloader? Is here maybe someone who is able to say something about these articles?
Or maybe it is even worth to be evaluated in other device's threads to get people in knowledge of this "security issue"?
Full of hope that someone here is able to workout something on this base, Greets and cheers....
Click to expand...
Click to collapse
Sony released MM firmware with this CVE already being fixed.
frostmore said:
old news mate.
http://forum.xda-developers.com/xperia-z5/general/root-using-vulnerabilities-snapdragon-t3338173
another forummer already pinted this out.
unless you know how to roll back old linux kernel and over come SElinux
Click to expand...
Click to collapse
In the other thread they Talk about CVE-2016-0819 and CVE-2016-0805 which affects specially snapdragon soc's......
The articles which i found are talking about CVE-2015-1805......
I dont think that we are talking about the same. CVE-2015-1805 affects possibly every Kernel Version 3.4, 3.10 and 3.14.....
If Sony already has fixed the 2015-1805 even while Google itself "forgot", could you tell me where i can find Information about a fix By Sony?
Tommy-Geenexus said:
Sony released MM firmware with this CVE already being fixed.
Click to expand...
Click to collapse
Flummi.FFM said:
If Sony already has fixed the 2015-1805 even while Google itself "forgot", could you tell me where i can find Information about a fix By Sony?
Click to expand...
Click to collapse
Simple: I just tried to patch the kernel, and found it has already included the fix.
The patch exists since mid-2015, it's just that devices were recently exploitet using this regression, and Google reacted.
Thx then for your reply......
Tommy-Geenexus said:
Simple: I just tried to patch the kernel, and found it has already included the fix.
The patch exists since mid-2015, it's just that devices were recently exploitet using this regression, and Google reacted.
Click to expand...
Click to collapse
I found out that in the source of Release 32.0.a.4.11 the issue IS NOT fixed.......
Maybe a Base for a root solution after downgrade?
Flummi.FFM said:
I found out that in the source of Release 32.0.a.4.11 the issue IS NOT fixed.......
Maybe a Base for a root solution after downgrade?
Click to expand...
Click to collapse
Hi man!!
How did you see it?
I asked about it. Maybe zxz0o0 a dev of z3 will help us. I hope he see it
Crossfingers
Enviado desde mi E6653 mediante Tapatalk
uripiruli said:
Hi man!!
How did you see it?
I asked about it. Maybe zxz0o0 a dev of z3 will help us. I hope he see it
Crossfingers
Enviado desde mi E6653 mediante Tapatalk
Click to expand...
Click to collapse
I downloaded the source Code of the 32.0.a.4.11 build and compared the pipe.c File with the fix commit and the fixed version in the 32.1.a.1.163 build.
The result was that the older Version is Not fixed.
I also thought one hour ago of asking zxz000 Team.....
If we can win them it would be great!!!
I asked few minutes ago in two z3 threads for help.....
I hope so much that someone will be able to make something finally.....
How about dm-verity? How can you pass this?
You can probably get "root" using this exploit but it will only be temporarily and you can't write /system because of dm-verity. So the only usecase I see is to backup TA partition.
anno2070 said:
How about dm-verity? How can you pass this?
Click to expand...
Click to collapse
zxz0O0 said:
You can probably get "root" using this exploit but it will only be temporarily and you can't write /system because of dm-verity. So the only usecase I see is to backup TA partition.
Click to expand...
Click to collapse
Unfortunally i dont have the knowledge to make something by myself.....
In my opinion ta Backup is more than nothing for the Moment.....
Maybe if all of you professionals like Tobias.waldvogel and monx and you of the z3 community are working and thinking together about it then it will happen one Day?
You see i spend all my free time on searching for abilities and holes to use......
But due to my very basically knowledge of programming i am not able to implement something on my own.
Edit: my idea was to achieve root By this hole, then get a prerooted and DM verity disabled kernel before Reboot..... Isnt that possible?
Flummi.FFM said:
Unfortunally i dont have the knowledge to make something by myself.....
In my opinion ta Backup is more than nothing for the Moment.....
Maybe if all of you professionals like Tobias.waldvogel and monx and you of the z3 community are working and thinking together about it then it will happen one Day?
You see i spend all my free time on searching for abilities and holes to use......
But due to my very basically knowledge of programming i am not able to implement something on my own.
Edit: my idea was to achieve root By this hole, then get a prerooted and DM verity disabled kernel before Reboot..... Isnt that possible?
Click to expand...
Click to collapse
You cant flash any other Kernel beside Sony Original Kernel on Locked Bootloader and with dm-verity enabled its nothing you can do to root LB Z5. The only possible way is to unlock your Bootloader but with locked Bootloader you have no Chance as you cant flash any modified Kernel. We only archieved Root on Z3 because it has dm-verity disabled in Original Sony Kernel.
zxz0O0 said:
You can probably get "root" using this exploit but it will only be temporarily and you can't write /system because of dm-verity. So the only usecase I see is to backup TA partition.
Click to expand...
Click to collapse
Thanks for your answer.
If we rooted our Phone with a temporaly root with this xploit, then we do ta backup. Finally unlock de bootloader, root with the actually tools that we have... And then restore our ta backup with our Sony features. Is this possible??? Or i am dreamming????[emoji16]
Enviado desde mi E6653 mediante Tapatalk
uripiruli said:
Thanks for your answer.
If we rooted our Phone with a temporaly root with this xploit, then we do ta backup. Finally unlock de bootloader, root with the actually tools that we have... And then restore our ta backup with our Sony features. Is this possible??? Or i am dreamming????[emoji16]
Enviado desde mi E6653 mediante Tapatalk
Click to expand...
Click to collapse
you cant restore your ta backup on unlocked bootloader. So you are in the start point. Unless you get something to disable dm-verity you can not get root on lock bootloader
You can "restore" drm keys on unlocked bootloader now. I dont get it why do you want to backup them so much? You can have all drm features working on UB.

QuadRooter vulnerability

I guess most of you have learned of the recently discovered vulnerability affecting over 900m Qualcomm devices. Apparently even after Google's latest July patches, the vulnerability persists, allowing root access to affected handsets. Pretty much the entire Xperia line using Qualcomm SOCs is affected.
My question is: will we see a rooting method based on this exploit? I know that unlocking the BL is the most straight forward way to root, however me and others I believe, would like to have a backup of their TA partition first. Ivyroot apparently works on older firmwares (not with .253), but as with BackupTA there's always some risk involved when restoring.
Perhaps a bounty is the proper way to go?
expecting security patch by Google!
meanwhile i have installed zonealarm...
Though if we could get a temp root on LB we could always refine the method for a permanent root on LB. Then, on the post from whichever genius makes the permanent root, have a damn neon flashing sign saying "OKAY, GO PATCH THIS NOW" via another kernel or a software fix as part of the "tutorial" post that would eventually be made.
pattmyn said:
Though if we could get a temp root on LB we could always refine the method for a permanent root on LB. Then, on the post from whichever genius makes the permanent root, have a damn neon flashing sign saying "OKAY, GO PATCH THIS NOW" via another kernel or a software fix as part of the "tutorial" post that would eventually be made.
Click to expand...
Click to collapse
permanent root on LB cannot be done post 5.1.1 (android). it will be same as finding loop wholes in system and vulnerabilities of MM. atleast SONY don't support such methods where SONY RIC protects device to the level of putting it in to bootloops rather than allowing root access (when tried rooting on LB and DM-VARIETY+SONYRIC on).
the permanent solution ? either
1. switch to devices which allow PREROOTED O/S
2. UB and flash Kernal /ROMS as your own
YasuHamed said:
permanent root on LB cannot be done post 5.1.1 (android). it will be same as finding loop wholes in system and vulnerabilities of MM. atleast SONY don't support such methods where SONY RIC protects device to the level of putting it in to bootloops rather than allowing root access (when tried rooting on LB and DM-VARIETY+SONYRIC on).
the permanent solution ? either
1. switch to devices which allow PREROOTED O/S
2. UB and flash Kernal /ROMS as your own
Click to expand...
Click to collapse
Well that's a depressing way to start my day lol. I love this damn phone but there's some rooted apps I miss dearly.
pattmyn said:
Well that's a depressing way to start my day lol. I love this damn phone but there's some rooted apps I miss dearly.
Click to expand...
Click to collapse
i know what you mean! Xperias are my personal addiction!
i made deal with devil and lost drm keys and took security risks over my Z5 in exchange of rooted device.
in my opinion its matter of time, sooner or later you will also root your device!
YasuHamed said:
i know what you mean! Xperias are my personal addiction!
i made deal with devil and lost drm keys and took security risks over my Z5 in exchange of rooted device.
in my opinion its matter of time, sooner or later you will also root your device!
Click to expand...
Click to collapse
Not with a locked bootloader that can't be unlocked, I ain't. Unless you know some magical people at Sony that could override that lol
pattmyn said:
Not with a locked bootloader that can't be unlocked, I ain't. Unless you know some magical people at Sony that could override that lol
Click to expand...
Click to collapse
well one LONG workaround for you will be
via flashtool, (xperifirm) select z5p , select "INTERNAL" in the country list and download .170 version (android 5.0.2) the version at which it left sony factory.
flash it, Root it via kingroot (where kingroot is considered unsafe) , extract DRM KEYS
https://github.com/DevShaft/Backup-TA/releases
once u have those, upgrade to 6.0.1 and unlock the bootloader, flash it with custom kernal and relock the boot loader.
this way atleast you will have your ORIGINAL z5p KEYS with you for any future times
However relocking the BL with root will result in bootloop, since file system hash won't match the bootup check. However, with a TA partition backup, running an unlocked BL is much safer, for when you need to relock BL, and send the phone in for repairs etc.
YasuHamed said:
well one LONG workaround for you will be
via flashtool, (xperifirm) select z5p , select "INTERNAL" in the country list and download .170 version (android 5.0.2) the version at which it left sony factory.
flash it, Root it via kingroot (where kingroot is considered unsafe) , extract DRM KEYS
https://github.com/DevShaft/Backup-TA/releases
once u have those, upgrade to 6.0.1 and unlock the bootloader, flash it with custom kernal and relock the boot loader.
this way atleast you will have your ORIGINAL z5p KEYS with you for any future times
Click to expand...
Click to collapse
Not all bootloaders can be unlocked. Some specifically can't be because Sony made them that way because the carriers wanted it that way...
Sent from my SGP311 using XDA Free mobile app
guhvanoh said:
Not all bootloaders can be unlocked. Some specifically can't be because Sony made them that way because the carriers wanted it that way...
Sent from my SGP311 using XDA Free mobile app
Click to expand...
Click to collapse
agree, i believe z1 and z tablets in USA (versions) were falling in the catagory you mentioned.
if the bootloader cannot be locked then.... betty buy blackberry
---------- Post added at 11:30 AM ---------- Previous post was at 11:29 AM ----------
guhvanoh said:
Not all bootloaders can be unlocked. Some specifically can't be because Sony made them that way because the carriers wanted it that way...
Sent from my SGP311 using XDA Free mobile app
Click to expand...
Click to collapse
agree, i believe z1 and z tablets in USA (versions) were falling in the catagory you mentioned.
if the bootloader cannot be locked then.... betty buy blackberry
guhvanoh said:
Not all bootloaders can be unlocked. Some specifically can't be because Sony made them that way because the carriers wanted it that way...
Sent from my SGP311 using XDA Free mobile app
Click to expand...
Click to collapse
What he said.
pattmyn said:
What he said.
Click to expand...
Click to collapse
he is referring to some sony devices who's bootloader was denied unlocking.
but don't worry, most of the devices (outside USA) has bootunlocking ALLOWED
Per-purchase question .....
YasuHamed said:
he is referring to some Sony devices who's bootloader was denied unlocking.
but don't worry, most of the devices (outside USA) has boot unlocking ALLOWED
Click to expand...
Click to collapse
My GF's M4 Aqua had the option to unlock the bootloader in the dev settings. It still couldn't have the BL unlocked (E2306), but the other 2 variations could, the E2303 and the E2353.
The E2306 was subsidized and discounted by Sony and mass distributed by lower end carriers here in Canada, hence the unlockable BL.
This model has the E6833 and the E6883, which one has the BL that can be/is unlocked?
UnableToResetOldProfile said:
My GF's M4 Aqua had the option to unlock the bootloader in the dev settings. It still couldn't have the BL unlocked (E2306), but the other 2 variations could, the E2303 and the E2353.
The E2306 was subsidized and discounted by Sony and mass distributed by lower end carriers here in Canada, hence the unlockable BL.
This model has the E6833 and the E6883, which one has the BL that can be/is unlocked?
Click to expand...
Click to collapse
the OEM UNLOCKING allowed in Developer options is just an extra step.
my z5dual was giving one IMEI however with flashtool i was getting TWO IMEI numbers, both different and with the second imei i was able to unlock.
is yours M4aqua Dual

Categories

Resources