ok so I have a locked bootloader Xperia Z and was in the process of flashing an FTF from here. I have read that an unlocked bootloader would ruin the TA partition containing BA2 / DRM keys. I did not unlock the bootloader but when I flashed using flashtool I am not really sure if I ticked the Exclude (TA) from under the EXCLUDE. Does this mean that I erased the TA partition If anyone of you could be kind enough to tell me....
1. How do I know if BE2 is still working?
2. How do I know if I still have the DRM keys?
Thanks in advance and sorry for my noob question.
Alcatrazx said:
ok so I have a locked bootloader Xperia Z and was in the process of flashing an FTF from here. I have read that an unlocked bootloader would ruin the TA partition containing BA2 / DRM keys. I did not unlock the bootloader but when I flashed using flashtool I am not really sure if I ticked the Exclude (TA) from under the EXCLUDE. Does this mean that I erased the TA partition If anyone of you could be kind enough to tell me....
1. How do I know if BA2 is still working?
2. How do I know if I still have the DRM keys?
Thanks in advance and sorry for my noob question.
Click to expand...
Click to collapse
Flashtool will never erase or overwrite the DRM keys and other important details in your TA partition, even if you don't tick 'TA' under 'Exclude'.
1. When switching BE2 on/off, you will clearly see the difference on pictures in your Album app.
2. Go to your service menu (dial *#*#7378423#*#*) > Service tests > Security. If your DRM keys are okay, both MARLIN and WMLA will show up as [Key OK]. If they are erased, they would show up as [Unknown Error].
Apollo89 said:
Flashtool will never erase or overwrite the DRM keys and other important details in your TA partition, even if you don't tick 'TA' under 'Exclude'.
1. When switching BE2 on/off, you will clearly see the difference on pictures in your Album app.
2. Go to your service menu (dial *#*#7378423#*#*) > Service tests > Security. If your DRM keys are okay, both MARLIN and WMLA will show up as [Key OK]. If they are erased, they would show up as [Unknown Error].
Click to expand...
Click to collapse
Perfect and straight to the point So no need to tick the exclude TA then ?
One last question is there some way of unlocking booloaders which are locked from carriers?
Alcatrazx said:
Perfect and straight to the point So no need to tick the exclude TA then ?
Click to expand...
Click to collapse
Correct!
One last question is there some way of unlocking booloaders which are locked from carriers?
Click to expand...
Click to collapse
No, if you have a bootloader that is not allowed to be unlocked (by carrier), then there is no way to unlock your bootloader sorry.
Apollo89 said:
Flashtool will never erase or overwrite the DRM keys and other important details in your TA partition, even if you don't tick 'TA' under 'Exclude'.
1. When switching BE2 on/off, you will clearly see the difference on pictures in your Album app.
2. Go to your service menu (dial *#*#7378423#*#*) > Service tests > Security. If your DRM keys are okay, both MARLIN and WMLA will show up as [Key OK]. If they are erased, they would show up as [Unknown Error].
Click to expand...
Click to collapse
Nice info
Sent from my C6603 using xda premium
Related
i have used many custom roms but atlast i came back to stock rom and when i flashed the stock rom, my DRM keys restored itself. i have to do nothing. happpy!!!!
How do you see your drm is restored?
Send with tapatalk pro
jindal_bharat said:
i have used many custom roms but atlast i came back to stock rom and when i flashed the stock rom, my DRM keys restored itself. i have to do nothing. happpy!!!!
Click to expand...
Click to collapse
No
Your DRM keys didn't restored. If bravia engine work so that's not mean the DRM keys are back
Flashtool just restore the TA partition not DRM keys
Tapatalk'ed from my Xperia™ Z (C6602) running Dirty Unicorns ROM!
If you did not backup your ta partition when u first rooted the keys are gone forever.
androidfreak70 said:
No
Your DRM keys didn't restored. If bravia engine work so that's not mean the DRM keys are back
Flashtool just restore the TA partition not DRM keys
Tapatalk'ed from my Xperia™ Z (C6602) running Dirty Unicorns ROM!
Click to expand...
Click to collapse
daniel2728255 said:
If you did not backup your ta partition when u first rooted the keys are gone forever.
Click to expand...
Click to collapse
+2
Kinda useles to open a new thread about that in my case !
Send from my XZ With My Own Personal Modified MoonWalker SuperB !
androidfreak70 said:
No
Your DRM keys didn't restored. If bravia engine work so that's not mean the DRM keys are back
Flashtool just restore the TA partition not DRM keys
Tapatalk'ed from my Xperia™ Z (C6602) running Dirty Unicorns ROM!
Click to expand...
Click to collapse
then what r drm keys for ?
as my be2, xloud, trackid, ota updates everything is working .
Check the service menu: dial *#*#7378423#*#* (i.e. *#*#SERVICE#*#*) and choose 'Service tests' > 'Security'. If your DRM keys are okay, both MARLIN and WMLA will show up as [Key OK]. If they are erased, they would show up as [Unknown Error].
DRM keys are unique for each device, so they are not contained in any firmware download. Once they are erased, there is no way to get them back, unless you made a backup of the Trim Area (TA) before unlocking your bootloader.
jindal_bharat said:
then what r drm keys for ?
as my be2, xloud, trackid, ota updates everything is working .
Click to expand...
Click to collapse
DRM keys for warranty only
Those days and other things work when the TA partition restored not DRM keys
Xperia™ Z (C6602) with Tapatalk!
Ok thanks man
Sent from my C6603 using XDA Free mobile app
DRM restored
Mine was also restored.
Tho the mess over here, on a Xperia Z2, was absolutely a little mistake that costed the phone's life: I changed dpi setting under /system/build.prop and couldnt get the phone to startup properly (bootloop). So to get it connected to the PC, the only exit was to unlock the bootloader and flash some 3rd party recovery mode. By doing so I knew I was gonna lose DRM keys, TA Partition was gonna be screwed... anyway, I had to do it. So I got into the OS partitions, I copied (too late) the TA Partition that was still there, and I could make a backup of not much things... the recovery did some backup, I'll check later its contents. Very complicated to explain details of what I did, but after it, to get the phone back working, I downloaded a brand new stock firmware, which also restored my TA Partition and my DRM keys somehow...
I made a test. I used a tool (Backup-TA-9.11) that downloaded from the phone the new TA Partition. And then I compared it to the old one (using same tool), and I saw that the old one was totally f***d up!
I'm also happy I have my DRM Keys back with the TA Partition working!
Good luck people
mandibox said:
Mine was also restored.
Tho the mess over here, on a Xperia Z2, was absolutely a little mistake that costed the phone's life: I changed dpi setting under /system/build.prop and couldnt get the phone to startup properly (bootloop). So to get it connected to the PC, the only exit was to unlock the bootloader and flash some 3rd party recovery mode. By doing so I knew I was gonna lose DRM keys, TA Partition was gonna be screwed... anyway, I had to do it. So I got into the OS partitions, I copied (too late) the TA Partition that was still there, and I could make a backup of not much things... the recovery did some backup, I'll check later its contents. Very complicated to explain details of what I did, but after it, to get the phone back working, I downloaded a brand new stock firmware, which also restored my TA Partition and my DRM keys somehow...
I made a test. I used a tool (Backup-TA-9.11) that downloaded from the phone the new TA Partition. And then I compared it to the old one (using same tool), and I saw that the old one was totally f***d up!
I'm also happy I have my DRM Keys back with the TA Partition working!
Good luck people
Click to expand...
Click to collapse
HOW did you do that? are you sure about that? please check your service test/security if both first three lines are Ok.
xerwudjohn said:
HOW did you do that? are you sure about that? please check your service test/security if both first three lines are Ok.
Click to expand...
Click to collapse
Hello!
Sorry for the late response
I now figured out the DRM Keys are not really restored.
At the time I did not know about them, and lost them by mistake.
But I found another post that kinda helped me getting them back: http://forum.xda-developers.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672
Apollo89 said:
Check the service menu: dial *#*#7378423#*#* (i.e. *#*#SERVICE#*#*) and choose 'Service tests' > 'Security'. If your DRM keys are okay, both MARLIN and WMLA will show up as [Key OK]. If they are erased, they would show up as [Unknown Error].
DRM keys are unique for each device, so they are not contained in any firmware download. Once they are erased, there is no way to get them back, unless you made a backup of the Trim Area (TA) before unlocking your bootloader.
Click to expand...
Click to collapse
Man I restored them twice and it still gives me the :/
Sent from my C6603 using XDA Free mobile app
One question, is it possible to have your DRM keys intact with a locked bootloader, and be able to access fastboot?
I know for a fact that in Flashtool, it stated that fastboot features were accessible.
So, this whole time I thought that I might have accidentally unlocked my bootloader until I came across this thread.
I remember when I first got the phone, I was unable to access Fastboot mode due to a locked bootloader, but now I am able to.
Code:
20/001/2015 19:01:57 - INFO - Device connected with USB debugging on
20/001/2015 19:01:57 - INFO - Connected device : Sony Xperia Z
20/001/2015 19:01:57 - INFO - Installed version of busybox : BusyBox v1.20.2-jb static (2012-11-25 17:47 +0100) multi-call binary.
20/001/2015 19:01:57 - INFO - Android version : 4.4.2 / kernel version : 3.4.0-perf-g32ce454 / Build number : 10.5.A.0.230
20/001/2015 19:01:57 - INFO - Checking root access
20/001/2015 19:01:58 - INFO - Root Access Allowed
20/002/2015 19:02:27 - INFO - Please wait device is rebooting into fastboot mode (via ADB)
20/002/2015 19:02:28 - INFO - Device will soon enter fastboot mode
20/002/2015 19:02:28 - INFO - Device disconnected
20/002/2015 19:02:41 - INFO - Device connected in fastboot mode
20/002/2015 19:02:45 - INFO - Device Status: FASTBOOT mode
20/002/2015 19:02:47 - INFO - Fetching fastboot version info from connected device
20/002/2015 19:02:47 - INFO - FASTBOOT version info: [ version: 0.5 ]
{
"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"
}
-NEVERMIND, just tried flashing XzKernel-26 by alnikki25k, and it didn't boot.
Personally, I can't understand how other people is possible to bring their DRM keys without having TA-Partition. It's all fictive information and I'm totally sure, that no one have restored DRM keys within new ROM installation. And I can bet 100% that it doesn't matter - is it STOCK or CUSTOM ROM. Your DRM Keys aren't going to be restored within new ROM. It's impossible. The only way to get your DRM keys back is to restore your own TA-Partition (flashing any other person's TA-Partition will definitely brick your device), where DRM keys are located at.
Locking your bootloader doesn't restore your DRM keys. All you can do for now is to temporarily get some functions working only with some MODS, which are located somewhere in XDA.
my drm keys are lost after re locking BL. now i want to unlock it again but it fails every time i enter the unlock code.. is this because of lost drm keys? any assistance please?
WARNING: This instruction may brick your device permanently. I am not
responsible for any your loss or damage.
The following is the instruction to get root for SGP611 with giefroot(http://forum.xda-developers.com/crossdevice-dev/sony/giefroot-rooting-tool-cve-2014-4322-t3011598)
Requirement:
Bootloader Locked Z3 Tablet Compact Wi-Fi 16GB (SGP611)
D6603(Generic GLOBAL 23.0.A.2.93) firmware (You can got it from XperiFirm)
Flashtool
Install driver included in Flashtool
Patched version of giefroot_v3 (View attachment giefroot_v3_sgp611_fix1.zip)
Download:
View attachment giefroot_v3_sgp611_fix1.zip
Small Instruction:
1.Backup
2.Flash SGP611 firmware (23.0.1.A.0.167) if other version is installed
3.Flash D6603 system partition (23.0.A.2.93)
4.Enable [USB Debug] and [mock locations] and [Unknown Source] , then run install.bat in (View attachment giefroot_v3_sgp611_fix1.zip)
5.You got root!
6.Backup TA, Back to SGP611 firmware
Instruction:
1. Backup all your data (including application data and internal storage)
2. Get SGP611(23.0.1.A.0.167) firmware
3. Get D6603 firmware(Generic GLOBAL 23.0.A.2.93 ftf) from somewhere
4. If firmware version of your device is not 23.0.1.A.0.167, then flash all
contents of ftf to back to 23.0.1.A.0.167
(Start Flashtool and click "flash device", then choose "Flashmode".
On "Firmware Selector" select SGP611 firmware.
Uncheck APPSLOG, CACHE, DATA in Wipe menu.
Check all checkbox in Exclude menu.
Unckeck KERNEL in Exclude menu.
Then click Flash button.
Shutdown your device and connect USB on holding volume down.
Wait 20minute or more to finish.
)
5. Flash only system partition of D6603 (23.0.A.2.93)
(Open "Firmware Selector" with same instruction above.
select D6603 firmware.
Uncheck APPSLOG, CACHE, DATA in Wipe menu.
Check all checkbox in Exclude menu.
Unckeck SYSTEM in Exclude menu.
Then click Flash button.
And flash with same instruction above.
)
6. Power on your device, then enable [USB Debugging] and [Allow mock
locations] in Developer options. And enable [Unknown sources] in Security
setting.
Added:
Disable [Verify apps over USB] in Developer options, and disable [Verify apps] in Security setting.
Thanks kvi!
7. Install usb driver included in Flashtool
8. Download giefroot_v3_sgp611.zip and extract zip
9. Run install.bat in extracted folder, then wait for about 1minute
10. You got root!
11. Backup TA
12. Restore stock firmware by following insruction of this thread http://forum.xda-developers.com/z3-...-to-rooted-stock-sgp621-firmware-drm-t3015494
(replace SGP621 to SGP611 in the instruction)
Thanks to zxz0O0 for giefroot and some other tools.
zxz0O0 spend so much time to make giefroot work on SGP611 kernel.
Thanks to lowtraxx for root instruction for SGP621.
(http://forum.xda-developers.com/z3-...t/root-root-locked-bootloader-sgp621-t3013534)
Thanks to CubicU07 for instruction to restore stock firmware.
The old version (giefroot_v3_sgp611.zip) does not work.
Please try new version (View attachment giefroot_v3_sgp611_fix1.zip).
I'm sorry.
For me its not working:
Got a Z3TC 16GB WIFI, installed the Z3TC ftf, then flashed the system from the Z3, then used the tool but always get a device not rooted error
moritz31 said:
For me its not working:
Got a Z3TC 16GB WIFI, installed the Z3TC ftf, then flashed the system from the Z3, then used the tool but always get a device not rooted error
Click to expand...
Click to collapse
It may not succeed in one time.
Plaese try again 3 or 4 or more times.
If you still fails, please let's me know results of commands below.
Code:
adb shell cat /data/local/tmp/giefrootlog
adb shell cat /data/getrootlog
adb shell ls -l /data/local/tmp/scsi_wait_scan.ko
rurie said:
It may not succeed in one time.
Plaese try again 3 or 4 or more times.
If you still fails, please let's me know results of commands below.
Code:
adb shell cat /data/local/tmp/giefrootlog
adb shell cat /data/getrootlog
adb shell ls -l /data/local/tmp/scsi_wait_scan.ko
Click to expand...
Click to collapse
hey, i got it the problem seems to be on one site windows10,
on my mac i had to unplug replug the device after reboot before pressing continue
I noticed a mistake.
I fixed and upload again. (giefroot_v3_sgp611_fix1.zip)
Please try new file.
This file fixes both exploit itself and install.sh(for Linux/OS X).
rooted OK disabling all options for check/verify apps ! (1 option in security + 1 option in Developer options) , Backup TA OK
TA restored on rooted stock firmware , drm keys OK
Thx!
kvi said:
rooted OK disabling all options for check/verify apps ! (1 option in security + 1 option in Developer options) , Backup TA OK
TA restored on rooted stock firmware , drm keys OK
Thx!
Click to expand...
Click to collapse
Thanks for confirming
kvi said:
rooted OK disabling all options for check/verify apps ! (1 option in security + 1 option in Developer options) , Backup TA OK
TA restored on rooted stock firmware , drm keys OK
Thx!
Click to expand...
Click to collapse
Thank you for reporting and information!
I added your information to the instruction.
FtF global z3 or z3 tablet?
edited:
I was asking if need to build de ftf firmw using z3 as device or z3 tablet, but It works with z3
Works for me, actually running stock android with root and TA partition restored.
THANKS A MIL!
I do not speak English, I use google translator
Do not know which section you mean, 5 or 12. If I did 5 you see in this picture
http: // oi59.tinypic.com / 2my85qc.jpg
Root with the bootloader intact, that is amazing! Will this also work on the WiFi 4G version? That's the one I have and I don't want to mess it up.
Angelusz said:
Root with the bootloader intact, that is amazing! Will this also work on the WiFi 4G version? That's the one I have and I don't want to mess it up.
Click to expand...
Click to collapse
Just scroll one line up in general forum you have the post for the SGP621 (LTE version) here
enjoy!
Oh, I missed that one, thanks!
Does it void warranty? As the DRM keys and still there and how to do you restore the DRM keys
Copy apps in SDcard.
If you already gained root access, can you copy all apps to SDcard? What apps you guys recommend? Thanks in advance.
Does this method erase all data in internal card?
Has anyone got this working with SGP612 yet? (32gb Wifi only version). I have't seen this mentioned anywhere, but it should be similar to SGP611?
I'm a bit confused at step 12 : first thing to do when following CubicU07 instructions is to follow ... lowtraxx instructions...
If we follow CubicU07 thread, we first have to back up TA, but that was step 11 of this current thread. sso I guess we should follow lowtraxx instructions, but this one specifies that it won't work for SGP611, and sends us to this thread. Back to square one, then.
My guess is that we have to follow CubicU07 thread, no matter what he says first (so, I won't follow lowtraxx instructions).
Could you please be more specific for step 12 ? Do we finally have to use Advanced stock kernel, PRFCreator, SonyRICDefeat, ... as described in CubicU07 thread (which also involves unlocking BL) ?
Thank you.
Where can I get the firmware from step 3?
It's written : install XperiFirm and download it with this software.
Here we are with a new tool. Ready for modding our ZS570KL/PRO
This is a batch modder with all files for modding our device into it.
How to use:
Extract the zip in a folder, then make sure you have all required drivers for fastboot/adb. Then enable USB Debugging into your phone and open the tool.
Functions:
Check connection status
Bootloader Unlocker
Flash TWRP
Root Flasher
ADB Shell
Erase /system, /data and /cache
DPI Changer
Resrart Menu
Download:
Zenfone3 Deluxe Toolkit 1.0
Changelog
Post #2
Based Tool
Zenfone3 Toolkit
Credits:
@Chainfire for SuperSu
Forum OneTeam
V1.0
Turkish English Language choose Added.
Added Dictation on opening.
Added Fastboot Connection Setup.
Added OEM Locker Acme.
TWRP Setup Added.
Root Throw Added.
Drivers Added.
/ System, / data, / oncache Clear Added.
Changes Added.
Added Referral to Forum.
Theme Color Changed.
Sizes Adjusted Repeatedly.
Two pictures added.
Modifications Added Files And Code.
All Codes Created For Both ZS570KL/PRO
Reserved
Picking either language brings up some error then exits out. I'm pretty sure I have everything downloaded for drivers and also have the debugging on.
Yep I had the same problem upon language selection it just crashed
Question
EypCnn said:
Reserved
Click to expand...
Click to collapse
I have a TIM-branded SKU on my ZS570KL, will these tools work for me?
Can you help me unbrand the phone? I have found two forums, but unfortunately both lack the info I need to feel certain enough to try this.
It's possible to relock the bootloader?
Ryder. said:
It's possible to relock the bootloader?
Click to expand...
Click to collapse
Hi Ryder, why do you need relock the bootloader?, for send to repair in warranty maybe, but I think relock is not an option for send to repair in warranty.
Sent from my ASUS_Z016D using Tapatalk
sat182 said:
Hi Ryder, why do you need relock the bootloader?, for send to repair in warranty maybe, but I think relock is not an option for send to repair in warranty.
Sent from my ASUS_Z016D using Tapatalk
Click to expand...
Click to collapse
No, it's just for sell the device if i want
When I choose 1 or 2 I have a message error wiyh "goto"
Serves for the ZE552KL (Z012DC)?
THIS IS JUST SHARE HOW I SUCCESS BRING BACK MY SONY APPS WORK LIKE A CHARM, DRM REALY FIXED
I realize that since Oreo, when I flash drmfix.zip shared in this forum I dont realy get drm fixed, just get camera working, not for other apps like X-Reality, Super-vivid and Sony Services (for loging in Xperia Longe) and mybe other related with sony feature.
After some research, evidently Oreo move some files from boot.img to system partition, this files in important for patching so that drm fix work. I followed tutorial in Xperia Z5 thread and get an idea for try to aplicated for XZs and its work like a charm.
I don't own anything for this tool so you can just go to this thread and follow every single instruction in there.
What I get after followed that method :
- dm-verity (disabled) > now I can do debloat system apps
- Sony RIC (disabled) > as above function
- force-encrypt (disabled) > /data fully decrypted, no red message anymore in TWRP
- DRM Loader Patched to boot.img > Flashing drmfix.zip now will bring back Sony Apps Feature (X-Reality, Vivid Mode, Xperia Account Services)
Credit goes for him : serajr
But if you are helped by this information then don't hesitate to click thanks button...
THIS METHOD SHOULD WORK ON LATEST OFFICIAL STOCK ROM [ G823X_41.3.A.2.234 ], AND MAYBE WORK ON NEXT UPDATE
Last thing.... DO WITH YOUR OWN RISK
Screen mirroring not working on xperia xzs
XtremE16 said:
Screen mirroring not working on xperia xzs
Click to expand...
Click to collapse
Never do mirroring cause I dont have devices to cast my XZs, so I have no idea abut that.
Hey guys need a quick help!!
Trying to see this used X Compact still has all the DRM keys. I have:
------------------------------------------------------------------------------------------
WIDEVINE [Key OK][Active]
CKB [Key OK][Active]
HUK: XXXXXXXXXXXXXXXX
PRODID_AID: XXXX
OTP_LOCK_CONFIG: XXXX
OTP_LOCK_STATE: LOCKED
AUTH_ENABLE: XX
DEVICE_ID: XXXXXXXX
FIDO_KEYS: Provisioned
Factory Reset Reason: MasterClearConfirm,2019-08-xx xx:xx:xx GMT
--------------------------------------------------------------------------------------
Is this all I should have for a DRM intact, bootloader locked device?
I notice that not all entries have [Key OK][Active] next to it.
Does that mean the device has been unlocked before and keys are gone now?
And, why does it say something about Factory Reset?
Also, I don't quite know the meaning of some entries (well, if not all).
What does the numbers mean following:
PRODID_AID:
OTP_LOCK_CONFIG:
AUTH_ENABLE:
Although these might not have any significance.
Well, what do you think, guys?
Any help will be much appreciated!!
tapa_t said:
Hey guys need a quick help!!
Trying to see this used X Compact still has all the DRM keys. I have:
------------------------------------------------------------------------------------------
WIDEVINE [Key OK][Active]
CKB [Key OK][Active]
HUK: XXXXXXXXXXXXXXXX
PRODID_AID: XXXX
OTP_LOCK_CONFIG: XXXX
OTP_LOCK_STATE: LOCKED
AUTH_ENABLE: XX
DEVICE_ID: XXXXXXXX
FIDO_KEYS: Provisioned
Factory Reset Reason: MasterClearConfirm,2019-08-xx xx:xx:xx GMT
--------------------------------------------------------------------------------------
Is this all I should have for a DRM intact, bootloader locked device?
I notice that not all entries have [Key OK][Active] next to it.
Does that mean the device has been unlocked before and keys are gone now?
And, why does it say something about Factory Reset?
Also, I don't quite know the meaning of some entries (well, if not all).
What does the numbers mean following:
PRODID_AID:
OTP_LOCK_CONFIG:
AUTH_ENABLE:
Although these might not have any significance.
Well, what do you think, guys?
Any help will be much appreciated!!
Click to expand...
Click to collapse
I'm pretty sure that 'ok' in the first 2 lines, plus fido keys provisioned, means that you're good.
Not sure what all that other stuff means ...
levone1 said:
I'm pretty sure that 'ok' in the first 2 lines, plus fido keys provisioned, means that you're good.
Not sure what all that other stuff means ...
Click to expand...
Click to collapse
Hey, thank you man!
I also found some screen shots in this threads:
https://forum.xda-developers.com/x-compact/how-to/backup-ta-drm-using-dirty-cow-t3514482
but I wasn't sure if those are "after" they've unlocked the bootloader, and since some of them shows FIDO "not provisioned"...
Anyway, I appreciate your input!