What's the latest on Unlocking the XZ3 Bootloader - DRM (EU model - Feb 19) - Sony Xperia XZ3 Questions & Answers

While I found some good info in the 'state of root for the XZ3' Q&A, that does not work well using the XDA Labs app, and I want to be sure I know what's going on before I do something stupid.
To my understanding from a news update on XDA here, the XZ3 camera does not break when unlocking. So, here are the steps I believe I need to take (EU version from Clove)
1) Unbox, connect to my wifi and run the updates. Update level I need is at least 52.0.A.84.
2) Checkbox for unlocking now available (under development section). Unlock the bootloader. (camera works after this)?
3) Update firmware to 52.0.A.126 via xperafirm
If I want TWRP / Root
4) Install TWRP per instructions (I read that this breaks Camera again)
5) Install TWRP camera fix
6) Install Magisk and the module to fix DRM.
As I understand it, even the DRM fix will not bring back some of the Sony stuff - Triluminous display settings, xreality, dynamic contrast enhancer, LDAC audio? and dolby ATMOS? If anyone can test those and see if they work, that'd be awesome.
Are my steps correct? Am I missing anything?
TIA!

charlatan01 said:
4) Install TWRP per instructions (I read that this breaks Camera again)
Click to expand...
Click to collapse
It is the unlocking step that breaks the camera, not TWRP/Magisk.
charlatan01 said:
As I understand it, even the DRM fix will not bring back some of the Sony stuff - Triluminous display settings, xreality, dynamic contrast enhancer, LDAC audio? and dolby ATMOS? If anyone can test those and see if they work, that'd be awesome.
Click to expand...
Click to collapse
Triluminos/X-Reality/Dynamic contrast are arguably "features" that you'd rather lose than keep. In 7 years of owning Xperia devices I have never used them. There is a generic "super-vivid" mode that replaces X-Reality after unlocking the boot loader:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LDAC doesn't appear to be affected, although I don't have a suitable device to test it with:
As for Atmos, I think I uninstalled that app immediately, and it looks like it's not available as an apk that I could find easily so I can't test it for you. I think it's unaffected by the unlock, though.
Glancing over at the camera fix thread on the XZ2 forum, it looks like 163 is safe to flash (instead of 126), but 202 is unknown. If you're unlocking anyway, you might want to test it and report back whether the camera fix still works on 202. If it doesn't, you can always use Newflasher to downgrade to 163. For the time being, I'm holding off on flashing anything as the main two things I would like are Resurrection Remix and a working port of GCam with Night Sight, both of which are unavailable for the XZ3 as of writing.

mufunyo said:
It is the unlocking step that breaks the camera, not TWRP/Magisk.
Click to expand...
Click to collapse
Right, sorry. I meant to ask... from my reading the camera 'shouldn't' break. I suppose it's okay if it does as long as I can fix it.
Thanks for posting the screens / functional differences.
mufunyo said:
I would like are Resurrection Remix and a working port of GCam with Night Sight, both of which are unavailable for the XZ3 as of writing.
Click to expand...
Click to collapse
Bingo! I would LOVE to have RR, or maybe Slim available.. and yeah, a working GCAM would be amazing.
Hoping as prices fall this device gets in the hands of some more folks in the modding community... not that I have any complaints with all the work that @MartinX3 and others are providing!

Working GCam will only be on AOSP-based ROMs like Lineage and RR, and depends on full Camera2 support.

So, it is officially supported by SONY https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
but which one are up to now the benefit we can get?

sev7en said:
So, it is officially supported by SONY https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
but which one are up to now the benefit we can get?
Click to expand...
Click to collapse
The warning is full of 'ifs' and 'may bes'. Honestly, there isn't much to dislike about Sony's ROM, so I really only want the unlocked bl to root and remove Facebook.
Root is becoming less of a requirement in my eyes, but you may find some need for it.

charlatan01 said:
The warning is full of 'ifs' and 'may bes'. Honestly, there isn't much to dislike about Sony's ROM, so I really only want the unlocked bl to root and remove Facebook.
Root is becoming less of a requirement in my eyes, but you may find some need for it.
Click to expand...
Click to collapse
I love that stock but I installed NOVA as now we lost also the themes...
I would get a better camera support as for the GCAM. The quality of the shoots of XZ3 is really poor. I did a comparison with my R1 and it is top-down everything.

Just an update to my original post - .126 is the current US custom version. Because I want to use VOLTE on Tmobile, I'll be using that for my base. I'd like to update to 202, but I'll need to wait for Sony to catch up

Camera Noise reduction isnt affected?

Unlocking under 202 does not affect

Hello! I'm researching which camera features are missing after unlocking this device. What I found out is: We have full Camera 2 support including RAW. So is everything fine now or is the image quality still not as good as on an unlocked device? I can't find any comparison photos.
What I also don't know yet is: Is good photo quality bound to the sony camera app or some driver or service?
Also I read about upgrading or downgrading the firmware to a target firmware to save keys for future use. I found no way to do this without unlocking the bootloader first.

my phone get bootloader unlocked no a can unlokin or not

Related

[Q] Custom ROMs and Kernels and CM

Hi everybody!
Has there been any kernel and ROM development for the Z3 Compact, because I hope to buy it?
My second choice would be the S5 Mini but again I have not seen any development.
( Reasons for my choices are weight and size, being a girl I have seem to have been given smaller hands so giant sized phones have been dropped. )
Thanks lots and kind regards,
Soph.
P.S I'll post this on the s5 min forum also
Its kinda hard to develop for a phone which hasn't been released yet.
I can buy them here.
----
EDIT
no I cannot! I thought they'd released this. My apologies.
http://www.sonymobile.com/nl/products/phones/xperia-z3-compact/
This should be available in NL in 11 days, because when I try and place the order they say it won't ship for eleven day:
http://www.bol.com/nl/p/sony-xperia-z3-compact-groen/9200000032103951/?Referrer=ADVBETWE0020159200000032103951
and from here,
http://www.belsimpel.nl/Sony/Sony-Xperia-Z3-Compact-Green/abonnement
Fingers crossed that it will be supported by the CM team
forgetmyname said:
I can buy them here.
----
EDIT
no I cannot! I thought they'd released this. My apologies.
http://www.sonymobile.com/nl/products/phones/xperia-z3-compact/
This should be available in NL in 11 days, because when I try and place the order they say it won't ship for eleven day:
http://www.bol.com/nl/p/sony-xperia...3951/?Referrer=ADVBETWE0020159200000032103951
and from here,
http://www.belsimpel.nl/Sony/Sony-Xperia-Z3-Compact-Green/abonnement
Click to expand...
Click to collapse
If you don't live far away from the boarder, here in Germany it's available tomorrow.
forgetmyname said:
I can buy them here.
----
EDIT
no I cannot! I thought they'd released this. My apologies.
http://www.sonymobile.com/nl/products/phones/xperia-z3-compact/
This should be available in NL in 11 days, because when I try and place the order they say it won't ship for eleven day:
http://www.bol.com/nl/p/sony-xperia-z3-compact-groen/9200000032103951/?Referrer=ADVBETWE0020159200000032103951
and from here,
http://www.belsimpel.nl/Sony/Sony-Xperia-Z3-Compact-Green/abonnement
Click to expand...
Click to collapse
You need to be patient, developers need time, most people in north america who preordered from the UK retailers won't even get it until next week. I wouldn't expect boot loader unlocks or root until late next week at the absolute insanely earliest
Nuckin said:
You need to be patient, developers need time, most people in north america who preordered from the UK retailers won't even get it until next week. I wouldn't expect boot loader unlocks or root until late next week at the absolute insanely earliest
Click to expand...
Click to collapse
Actually you can already unlock the bootloader > http://developer.sonymobile.com/unlockbootloader/
I'm going to try it this evening. Afterwards maybe try Framaroot to see if the existing exploits to obtain Root access also work on this device.
I'm also personally waiting for CM; the xperia ROM feels really strange to use. Does anyone know roughly how long CM take to make a ROM for a new phone if they decide to support it?
Altitudes90 said:
Actually you can already unlock the bootloader > http://developer.sonymobile.com/unlockbootloader/
I'm going to try it this evening. Afterwards maybe try Framaroot to see if the existing exploits to obtain Root access also work on this device.
Click to expand...
Click to collapse
I have already unlocked and tried Framaroot, it does not work
kutaxov said:
I have already unlocked and tried Framaroot, it does not work
Click to expand...
Click to collapse
Have you tried Easy Root tool as well?
http://forum.xda-developers.com/showthread.php?t=2784900
Altitudes90 said:
Have you tried Easy Root tool as well?
http://forum.xda-developers.com/showthread.php?t=2784900
Click to expand...
Click to collapse
Does not work, hangs on the moment:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And your device is showing up when you use the "adb devices" command?
Altitudes90 said:
And your device is showing up when you use the "adb devices" command?
Click to expand...
Click to collapse
Yes
kutaxov said:
Yes
Click to expand...
Click to collapse
Too bad.
I dont think even the Z1C got an official CM release did it? And the one that was there broke all sensors when encryption was enabled
HosainH said:
I'm also personally waiting for CM; the xperia ROM feels really strange to use. Does anyone know roughly how long CM take to make a ROM for a new phone if they decide to support it?
Click to expand...
Click to collapse
SenK9 said:
I dont think even the Z1C got an official CM release did it? And the one that was there broke all sensors when encryption was enabled
Click to expand...
Click to collapse
A lot of it comes down to how many people (developers in particular) want or get the phone. I'm hoping that there will be a decent community behind the Z3C as many people don't want larger phones anymore and this still has decent specs and a great battery life. We'll have to wait and see, but CM isn't a necessity if you just want the options that CM exposes to the uses - there's plenty of ways to customise the device.
Personally, I'd be happy with root and a more vanilla android version without some of the Sony customisations.
SenK9 said:
I dont think even the Z1C got an official CM release did it? And the one that was there broke all sensors when encryption was enabled
Click to expand...
Click to collapse
Z1c has cm11 support officially.
Altitudes90 said:
Have you tried Easy Root tool as well?
http://forum.xda-developers.com/showthread.php?t=2784900
Click to expand...
Click to collapse
Even modified kernels with recovery from z1c and z2 not fit, and you somehow childish way want to get Root.
Joe_Mama said:
Even modified kernels with recovery from z1c and z2 not fit, and you somehow childish way want to get Root.
Click to expand...
Click to collapse
Jesus, don't get your panties all in a bunch.
Anyway, what makes you think that flashing a custom recovery is "easier" then getting root access?
Altitudes90 said:
Jesus, don't get your panties all in a bunch.
Anyway, what makes you think that flashing a custom recovery is "easier" then getting root access?
Click to expand...
Click to collapse
It is not easier. It is more reliable. And most importantly, even though I was doing something to get root, and do not sit in my panties like you in anticipation of a good magician.

LG v40 T-mobile root?

I have a LG v40 by T-mobile is there a way to root the phone or convert it to a model that can be rooted?
I did it. It is possible but need soldering.
Vlaaaad said:
I did it. It is possible but need soldering.
Click to expand...
Click to collapse
Whats the possibility of being able to root the T-Mobile variant just normally in the near future? (Without hardware mods)
Is it being worked on?
Z3ROGRAV1TYx said:
Whats the possibility of being able to root the T-Mobile variant just normally in the near future? (Without hardware mods)
Is it being worked on?
Click to expand...
Click to collapse
I don't think that it will be available in near future
So you managed to root the tmobile variant with a little soldering? I wouldn't mind doing that. Is there a guide on how to do this? I've been dying to root my tmobile V40
rdtg said:
So you managed to root the tmobile variant with a little soldering? I wouldn't mind doing that. Is there a guide on how to do this? I've been dying to root my tmobile V40
Click to expand...
Click to collapse
Not little Needs completely remove memory chip and write to it directly. Flash eng boot and magisk directly. Stock Fastboot is useless even in unlocked state
Damn vlaaad, you killed all of our hopes in one post.
Any hope 2020nwill see root for Tmobile V40?
Bump
What is your need to root with Android 10 now available for this model?
Sent from my LM-V405 using Tapatalk
Cueball74 said:
What is your need to root with Android 10 now available for this model?
Sent from my LM-V405 using Tapatalk
Click to expand...
Click to collapse
Er...I'm thinking Viper4Android maybe? I won't even use a phone period that does not have Viper installed. I consider it useless I need my music above all else.
With Android 10, this phone does not need rooting. The quad DAC and native sound settings negate the need for V4A. If the sole decision to root is to install V4A, then you need an unlocked or international V40. You're SOL with the T-Mobile version.
Here's a decent review of the native sound settings:
https://youtu.be/77PaQW7rGaE
Sent from my LG V40 using Tapatalk
"The quad DAC and native sound settings negate the need for V4A."
According to who? Not to the audiophile not even remotely close. Laughable actually. I was however nearly able to reproduce V4A quality sound by using onboard audio with Jet Player and with all 5 Jet Player addons installed and running. Then I added a 6th outstanding EQ app. With all 6 apps running concurrently you can nearly equal v4A if you tweak it all just right. Photo shows the 5 Jet Audio addons which you can engage. They all can be found here:
https://play.google.com/store/apps/details?id=com.jetappfactory.jetaudio
https://play.google.com/store/apps/details?id=com.smartandroidapps.equalizer
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's pretty darn close I have another rooted phone with V4A to compare to.
Root is usefull if you want more storage available by installing a custom rom, freeing the phone of bloatware, installing custom kernels, freeing from thermal throttle.
Cueball74 said:
With Android 10, this phone does not need rooting. The quad DAC and native sound settings negate the need for V4A. If the sole decision to root is to install V4A, then you need an unlocked or international V40. You're SOL with the T-Mobile version.
Here's a decent review of the native sound settings:
https://youtu.be/77PaQW7rGaE
Sent from my LG V40 using Tapatalk
Click to expand...
Click to collapse
the main reason that I want to root my T-Mobile LG V40 is because the annoying airplane prompt message when I turn it on .
machhho said:
the main reason that I want to root my T-Mobile LG V40 is because the annoying airplane prompt message when I turn it on .
Click to expand...
Click to collapse
Airplane prompt as in it being stuck in Airplane Mode?
Go to Settings > System > About Phone > Software Info.
Does it show Android 10, August 1 2020 security patch?
Cueball74 said:
Airplane prompt as in it being stuck in Airplane Mode?
Go to Settings > System > About Phone > Software Info.
Does it show Android 10, August 1 2020 security patch?
Click to expand...
Click to collapse
yes I do , but I meant by message that in order to turn on the airplane mode , I have to confirm it by clicking on the turn on option in the prompt message which is so annoying to me
KouaV1 said:
Root is usefull if you want more storage available by installing a custom rom, freeing the phone of bloatware, installing custom kernels, freeing from thermal throttle.
Click to expand...
Click to collapse
I 100 percent agree. I have rooted and installed custom roms on every phone I have used. I am definitely a minimalist when it comes to my phone, and I abhor bloatware. I hate most of the google suite of garbage that just sucks up battery and cpu cycles. I bought my phone used and wasn't paying close attention to the fact that this submodel has onerous restrictions on rooting. My bad I guess... live and learn.
What exactly is the problem with rooting this phone? I thought it was just a given that any android phone could be rooted. I didn't think it was like trying to crack Denuvo....
Seems like the bootloader for the TMO variant is unlockable. As for ROMs, there is nothing based on Android 10. A handful of ROMS here at XDA and they're for Pie. Lineage has an Anroid 10 ROM one but you have to be on Android Pie firmware. So if you've already taken TMO's Android 10 OTA, you're SOL. This is the wrong phone to have if you want to root. I've had to root my previous phones (HTC One M8, HTC 10, HTC U11, ZTE Axon 7) to get the best use out of them. This one, however, is so good in stock form that there is little incentive to root it.
I have the US unlocked variant of the V40 and all the old firmwares KDZ are downgradable which is awesome so I can always go to pie and unlock bootloader then root or go back to oreo so I have the out of the box performance and speed since the phone was released on Oreo

Just bought Mi 9 Lite and I have some questions

Everytime I have had an android smartphone, I unlocked and rooted straight away. I know what benefits unlocking the bootloader and rooting the ROM bring to the whole experience of using the smartphone but I have never actually looked or thought about the negative effects of unlocking and rooting.
I just received my Mi 9 Lite last night and I am just about the unlock its bootloader and get Magisk flashed. But before I do that, I am interested in people's opinion about what they think of rooting their phone.
- Can I root the stock ROM without unlocking the bootloader? I have heard this is possible but no idea how! If yes, does it have any limitations or is it the same as rooting after unlocking the bootloader?
- Does anyone have any other valid reason for not unlocking their device except warranty and maybe system updates? They always warn you about security, system updates and finger print sensors not working etc... is this true?
About the system updates, usually Xiaomi publishes the flashable ROM on their website which I can download and flash it manually so I don't have to worry about missing out on ROM updates.
Warranty wise, I am not too concerned either.
Security wise, I don't think this is an issue too as I always know what I would be flashing and installing on my phone.
Thank you.
I used some rooted device before . Don't no what you need, but, with this phone WITH NO ROOT, it's possible to uninstall or freeze some app, using blokada, you can stop/ block many thing.... and keep a clean and fresh device, with no mod, like out of the box ; )
I'm also getting this phone, can anyone from Europe confirm if Mi 9 Lite supports Carrier Aggregation? (LTE+)
k3lcior said:
I'm also getting this phone, can anyone from Europe confirm if Mi 9 Lite supports Carrier Aggregation? (LTE+)
Click to expand...
Click to collapse
Had the 4g+ logo out and about yesterday if that's what you mean?
technotika said:
Had the 4g+ logo out and about yesterday if that's what you mean?
Click to expand...
Click to collapse
Yes, but are you from Europe?
k3lcior said:
Yes, but are you from Europe?
Click to expand...
Click to collapse
For the time being - 'UK'
got the 4G+ in France too
4G+ in Sweden as well
Skickat från min Mi A2 via Tapatalk
Welp. I tried unlocking yesterday and I got the message saying I need to wait 168 hours. Damn.
One reason to maybe not root/unlock is it can stop NFC payments being made?
Just got my phone and i'm super impressed so far (especially by screen), the performance is surprisingly good aswell. Now waiting 168h for bootloader unlock..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And...what are the questions now?
@Jeanz Sensation, also expecting mine next year and ll be pleased if you or someone can tell me what's the actual available internal memory in 128gb version?.........thanks in advance.
Jeanz Sensation said:
I just received my Mi 9 Lite last night and I am just about the unlock its bootloader and get Magisk flashed. But before I do that, I am interested in people's opinion about what they think of rooting their phone.
Click to expand...
Click to collapse
Please tell us, why you could unlock the bootloader without 168 hours of waiting?
Jeanz Sensation said:
Everytime I have had an android smartphone, I unlocked and rooted straight away. I know what benefits unlocking the bootloader and rooting the ROM bring to the whole experience of using the smartphone but I have never actually looked or thought about the negative effects of unlocking and rooting.
I just received my Mi 9 Lite last night and I am just about the unlock its bootloader and get Magisk flashed. But before I do that, I am interested in people's opinion about what they think of rooting their phone.
- Can I root the stock ROM without unlocking the bootloader? I have heard this is possible but no idea how! If yes, does it have any limitations or is it the same as rooting after unlocking the bootloader?
- Does anyone have any other valid reason for not unlocking their device except warranty and maybe system updates? They always warn you about security, system updates and finger print sensors not working etc... is this true?
About the system updates, usually Xiaomi publishes the flashable ROM on their website which I can download and flash it manually so I don't have to worry about missing out on ROM updates.
Warranty wise, I am not too concerned either.
Security wise, I don't think this is an issue too as I always know what I would be flashing and installing on my phone.
Thank you.
Click to expand...
Click to collapse
Don't try to flash or modify anything on an Xiaomi with locked bootloader, you have many different ways to hardbrick device xD ?

What version of stock rom do you use?

Hello everyone, I got few questions.
As the title says, which version of stock rom do you use? Does it have any issues, are you rooted or not, green camera even with TA keys provisioned? Asking because, while I was following tutorial I couldn't pull out TA-unlocked.img, it said that file doesn't exist. I pulled entire /data/local/tmp folder and it showed 3 renoroot files and one "g+fffffffffffffff+fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff" file which is 12kb in size. I have green camera in Oreo, so Oreo is no go for me. Looking for decent stock Pie version, because latest one has touchscreen issues, it becomes unusable for 5-6 seconds and then works and stops working. Also, someone mind directing me to which TWRP should I use for PIE to install Magisk and other things, would be really nice. Any help is wellcome.
The last pie stock "2.2.8 should not have touchscreen issues, or any other firmware. If you have issues, and you still have warranty, try to send it it. Sony, in my opinion, is notorious for their touchscreen issues. I experienced touchscreen issues on z3 compact and z5 compact EOL. I suspect the same will happen with xz1 compact, unfortunately. However I am on my 3rd original screen repair/replacement , so hopefully it will last a bit longer this time.
mcmanuf said:
The last pie stock "2.2.8 should not have touchscreen issues, or any other firmware. If you have issues, and you still have warranty, try to send it it. Sony, in my opinion, is notorious for their touchscreen issues. I experienced touchscreen issues on z3 compact and z5 compact EOL. I suspect the same will happen with xz1 compact, unfortunately. However I am on my 3rd original screen repair/replacement , so hopefully it will last a bit longer this time.
Click to expand...
Click to collapse
Phone is not under warranty, so that is out of question, also don't want to lose waterproofing. This touchscreen issue happens only on Pie, currently I can find only latest pie and latest LineageOS, who aswell have that issue, while no issue occurs on stock Oreo, besides green camera.
Frano35 said:
Asking because, while I was following tutorial I couldn't pull out TA-unlocked.img
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
adb pull /data/local/tmp/TA-locked.img
Have you done a full wipe when installing the latest ROM? I've updated 3 times to Pie and come back to Oreo within hours due to certain issues so you may live to regret not following the guide properly.
SXUsr said:
adb pull /data/local/tmp/TA-locked.img
Have you done a full wipe when installing the latest ROM? I've updated 3 times to Pie and come back to Oreo within hours due to certain issues so you may live to regret not following the guide properly.
Click to expand...
Click to collapse
I did as the guide said, and I have done it all on Oreo. I have pulled TA-Locked.img and later it said to pull TA-Unlocked.img and push TA-Locked.img. I tried pulling out entire tmp folder but it had only renoroot files and weirdly named one. Then I pushed back locked img and did rest as guide says. I have attest key provisioned but not SOMC Fido and SOMC Attest. Any idea if I can still fix it?
Frano35 said:
Any idea if I can still fix it?
Click to expand...
Click to collapse
If you still have your TA-Locked.img then yes, the unlocked one is for "(for future comparisons)".
Start from scratch with the guide and redo the restoration of the locked TA img. If it doesn't work you're doing something wrong.
SXUsr said:
If you still have your TA-Locked.img then yes, the unlocked one is for "(for future comparisons)".
Start from scratch with the guide and redo the restoration of the locked TA img. If it doesn't work you're doing something wrong.
Click to expand...
Click to collapse
Do I need to flash back to Oreo or I can do it from LOS16?
Frano35 said:
Do I need to flash back to Oreo or I can do it from LOS16?
Click to expand...
Click to collapse
You tell me.

Question Widevine

Hi guys. Can you do me a favour and check your widevine version please. Cause I haven't done anything to my phone like rooting or unlocking and got downgraded to L3 from the factory L1. System version: 30.11.51.115
L1 here, rooted with magisk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Unluck then. I've read an article saying this kept happening with the ROG5 and Zenfone 7 in the past. Hope they fix it soon. Thanks for the reply!
L1 is what you want to play 1080 content on netflix. no?
Yes
[email protected] said:
Hi guys. Can you do me a favour and check your widevine version please. Cause I haven't done anything to my phone like rooting or unlocking and got downgraded to L3 from the factory L1. System version: 30.11.51.115
Click to expand...
Click to collapse
hey,
there´s a bug on qcom side, that caused qcom based devices to randomly fall back to widevine L3 when rebooting on previous gen qcom SoCs. It happened to me too on ZF7 since I probably booted a few hundred times during development of my kernel.
It might be that qcom didn´t fix this issue and it still can happen on the sd888. It´s triggered by just a reboot, doesn´t matter if unlocked, locked, unrooted or rooted.
Could you please post your issue on zentalk? Just a thread stating which firmware you´re using, that your phone is locked was never rooted and the issue happened out of the blue to you. It´s important so Asus can investigate and acknowledge that bug. They fixed it on ROG3 and Zenfone 7 too, so they might have to do the same here.
ZenFone 8
zentalk.asus.com
Freak07 said:
Could you please post your issue on zentalk?
ZenFone 8
zentalk.asus.com
Click to expand...
Click to collapse
I would also recommend to send technical request to their support. They'll send it directly to software devs.
Usually I do it in two ways (zentalk + technical support). And for example my last request was fixed in .115 update which means that they at least read our inquiries
By the way, how to check mine status of widevine? Is it some SW or I can do that with terminal (Termux for example) ?
dron39 said:
I would also recommend to send technical request to their support. They'll send it directly to software devs.
Usually I do it in two ways (zentalk + technical support). And for example my last request was fixed in .115 update which means that they at least read our inquiries
By the way, how to check mine status of widevine? Is it some SW or I can do that with terminal (Termux for example) ?
Click to expand...
Click to collapse
DRM Info - Apps on Google Play
Shows DRM information (Widevine, PlayReady, etc) from Android DRM Framework
play.google.com
Devcheck app can also display it.
Or check logcat when opening an app that request widevine status.
Freak07 said:
hey,
there´s a bug on qcom side, that caused qcom based devices to randomly fall back to widevine L3 when rebooting on previous gen qcom SoCs. It happened to me too on ZF7 since I probably booted a few hundred times during development of my kernel.
It might be that qcom didn´t fix this issue and it still can happen on the sd888. It´s triggered by just a reboot, doesn´t matter if unlocked, locked, unrooted or rooted.
Could you please post your issue on zentalk? Just a thread stating which firmware you´re using, that your phone is locked was never rooted and the issue happened out of the blue to you. It´s important so Asus can investigate and acknowledge that bug. They fixed it on ROG3 and Zenfone 7 too, so they might have to do the same here.
ZenFone 8
zentalk.asus.com
Click to expand...
Click to collapse
Yes I saw an article stating that that happened with the ROG5 and ZF7 but nona of those described why and how it happened. I didn't want to make another account for the forums so I used the app on the phone to contact them and got a reply from a representative with some instructions. ( Basically factory reset)
dron39 said:
I would also recommend to send technical request to their support. They'll send it directly to software devs.
Usually I do it in two ways (zentalk + technical support). And for example my last request was fixed in .115 update which means that they at least read our inquiries
By the way, how to check mine status of widevine? Is it some SW or I can do that with terminal (Termux for example) ?
Click to expand...
Click to collapse
Thanks and that's what I did. I've used the built-in bug report app. Will it reach the devs? Cause I've been having another strange bug with playback and probably should report it.
[email protected] said:
Yes I saw an article stating that that happened with the ROG5 and ZF7 but nona of those described why and how it happened. I didn't want to make another account for the forums so I used the app on the phone to contact them and got a reply from a representative with some instructions. ( Basically factory reset)
Thanks and that's what I did. I've used the built-in bug report app. Will it reach the devs? Cause I've been having another strange bug with playback and probably should report it.
Click to expand...
Click to collapse
If you can spare the time open a topic on zentalk. It's the best way to really reach them.
I suppose it's still at L3 even after factory reset.
You can mention that on zentalk too.
Ok ok I'll do that this weekend. Thanks for the help!
morpheus302 said:
L1 here, rooted with magiskView attachment 5409075
Click to expand...
Click to collapse
Stupid question but the bootloader is unlocked, right?
Userspace said:
Stupid question but the bootloader is unlocked, right?
Click to expand...
Click to collapse
On ZF8 bootloader unlocking doesn't downgrade it.

Categories

Resources