• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[oreo]XZ1-drmfix-root-ricoff:o

Search This thread

pergoteborg

Senior Member
Feb 11, 2009
225
97
Göteborg
No, only unlock the bootloader then TWRP and with it the zip files for DRM fix.
That's was it.
Gesendet von meinem FRD-L19 mit Tapatalk
I have absolutely no idea how this can work for @FerrisBueller
I downloaded 47.1.A.12.34 with XperiFirm, removed Userdata.sin and flashed the rest with Newflasher. Rebooted and everything works fine with new FW as expected.
Flashed the TWRP with december security level (same as @FerrisBueller), boot into TWRP and as expected is the filesystem encrypted so I cannot flash. I cannot understand how @FerrisBueller succeeded, it seems totally impossible to me.
Now, I did this today since the good pal and community hero @modpunk says he´ll build an updated TWRP which will solve that part of the problem shortly :)
When that´s solved we´ll check if the current DRMFix actually work....which I sincerely doubt.....but we´ll know for sure shortly
 

pergoteborg

Senior Member
Feb 11, 2009
225
97
Göteborg
I forgot one point, because it didn´t work, so I was thinking that is not relevant.
Before I flash the TWRP image file, I flashed the file from this post: https://forum.xda-developers.com/showpost.php?p=75010319&postcount=53.
I made a misstake, so I flashed the bootANDROXZ1849DRM.img as recovery. :(
Is this the reason, why it worked on my phone???
If you somehow got that kernel in and the phone actually starts you ought to at least have non working DRM fix.
If you take a picture with the standard camera the resulting picture ought to be just a green square
 
Last edited:

pergoteborg

Senior Member
Feb 11, 2009
225
97
Göteborg
You´re a true hero :laugh::good:
After flashing matching recovery provided by @modpunk in the [RECOVERY] TWRP 3.2.1-0 thread
I can decrypt the filesystem and flash the fix according to this thread on the latest 47.1.A.12.34 firmware.
As expected did it not work.
It is possible to get the drmpatch.zip and the RicOff.zip through the flashing process with what seems to be a success (no errors or warnings during flashing). The fix does not, however, work. Camera still produce green squares.
The provided SuperSU.zip throws error during flashing process.

This outcome is exactly what was expected, so this is only a confirmation that the provided fix DOES NOT work on FW47.1.A.12.34.
 

N1ghtr08d

Senior Member
Feb 15, 2011
778
188
Dublin
This is rather disappointing I must say

---------- Post added at 11:18 PM ---------- Previous post was at 11:16 PM ----------

There may be hope if @janjan can create a working kernel for the xz1 like he has done for the xz1 compact on the latest firmware.
 

sToRm//

Senior Member
Jun 24, 2017
524
2,032
Munich
After flashing matching recovery provided by @modpunk in the [RECOVERY] TWRP 3.2.1-0 thread
I can decrypt the filesystem and flash the fix according to this thread on the latest 47.1.A.12.34 firmware.
As expected did it not work.
It is possible to get the drmpatch.zip and the RicOff.zip through the flashing process with what seems to be a success (no errors or warnings during flashing). The fix does not, however, work. Camera still produce green squares.
The provided SuperSU.zip throws error during flashing process.

This outcome is exactly what was expected, so this is only a confirmation that the provided fix DOES NOT work on FW47.1.A.12.34.
Can you please check if the drmfix libraries are in the environment variables?

adb shell or terminal emulator command:
printenv

I think it's not directly related to the fix. It's just a problem with the environment.
 

sToRm//

Senior Member
Jun 24, 2017
524
2,032
Munich
Do you need that done specifically on the new firmware or can it be done on any firmware for you? I'll help you any way I can.
Try it on 12.34 if you have it right there on your device. On XZP there is the same problem with the environment exports. That's a problem with the new firmware versions. If you printenv and there is no "ld_preload" with the fix libraries, then it's clear.
 

N1ghtr08d

Senior Member
Feb 15, 2011
778
188
Dublin
I have the 8.49 firmware and I ran the command just in case it helps, maybe as a comparison for what results from the new firmware.

G8341:/ $ printenv
_=/system/bin/printenv
ANDROID_DATA=/data
TMPDIR=/data/local/tmp
ANDROID_SOCKET_zygote_secondary=8
HOME=/data/user/0/yarolegovich.materialterminal/app_HOME
ASEC_MOUNTPOINT=/mnt/asec
EXTERNAL_STORAGE=/sdcard
ANDROID_ROOT=/system
ANDROID_BOOTLOGO=1
ANDROID_ASSETS=/system/app
LD_PRELOAD=drmfix.so:drm****.so
BOOTCLASSPATH=/system/framework/QPerformance.jar:/system/framework/QPerformance.jar:/system/framework/core-oj.jar:/system/framework/core-libart.jar:/system/framework/conscrypt.jar:/system/framework/okhttp.jar:/system/framework/legacy-test.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/telephony-common.jar:/system/framework/voip-common.jar:/system/framework/ims-common.jar:/system/framework/apache-xml.jar:/system/framework/org.apache.http.legacy.boot.jar:/system/framework/android.hidl.base-V1.0-java.jar:/system/framework/android.hidl.manager-V1.0-java.jar:/system/framework/tcmiface.jar:/system/framework/telephony-ext.jar:/system/framework/WfdCommon.jar:/system/framework/oem-services.jar
HOSTNAME=G8341
ANDROID_STORAGE=/storage
PATH=/sbin:/system/bin:/vendor/bin
SYSTEMSERVERCLASSPATH=/system/framework/services.jar:/system/framework/ethernet-service.jar:/system/framework/wifi-service.jar
DOWNLOAD_CACHE=/data/cache
TERM=screen
G8341:/ $

Oddly enough I just noticed one of those lines contains the F word, hence it got censored, lol
 

pergoteborg

Senior Member
Feb 11, 2009
225
97
Göteborg
Try it on 12.34 if you have it right there on your device. On XZP there is the same problem with the environment exports. That's a problem with the new firmware versions. If you printenv and there is no "ld_preload" with the fix libraries, then it's clear.
My 12.34 Clean as a baby, newly flashed without any tries to flash the fix.
Code:
.....irrellivant.....$

Maybe I should flash the DRMfix and RicOff (SuperSU fails anyway) and get the environment after flashing?
 
Last edited:

pergoteborg

Senior Member
Feb 11, 2009
225
97
Göteborg
Problem solved.
Fix works also for latest 12.34 kernel.
The error from the SuperSU-flashing gave me the lead to the problem. The new FW and/or TWRP does not provide unzip functionallity.
In order to get the fix in OP working on FW47.1.A.12.34 follow this procedure:
  1. Make sure you're on a clean stock kernel, FW47.1.A.12.34 with Jan 5, 2018 security level
  2. Flash twrp-3.2.1-0-poplar-2-patchlevel-2018-01-05.img by @modpunk as stated in the [RECOVERY] TWRP 3.2.1-0 thread
  3. Boot into recovery
  4. Push busybox and softlink unzip as stated by @N1ghtr08d here in the post#20 of the TWRP thread
  5. Flash according to OP
  6. Reboot and enjoy

A ton of respect and a busload of thanks to @sToRm// for his engagement and for pushing me in the direction of the solution (maybe without realizing it himself:)) by making me realize the flashing of the OP zips which did not give any errors still actually left the system unchanged. And a lot of thanks to @N1ghtr08d for pointing out the unzip problem earlier on. And certainly must also @ M-Rom be mentioned who have only the best of intentions. And of course @modpunk where further explaination is totally unnecessary. That´s what communities like this is all about. Get it or get out!

and remember.....Don´t bother me, I bother you :)
 
Last edited:

N1ghtr08d

Senior Member
Feb 15, 2011
778
188
Dublin
Lol, the good old unzip. Well spotted sir!

---------- Post added at 01:36 AM ---------- Previous post was at 01:29 AM ----------

@modpunk Any chance you could rebuild the recovery and include the unzip? I hate to keep asking people to do stuff but nobody else here can do it... That I know of. @pergoteborg What happens if you try to install Magisk with that firmware and recovery installed? I'm wondering if we can get that DRM fix running with Magisk as someone said was possible on one of the other threads about the DRM fix when it got released.
We may need a new kernel to get Magisk running so that will be in the hands of @janjan once he's had some time to recover from the surgery he just had.
All of this is leading me to think we're not forgotten by the dev world with our device. Just imagine having the latest firmware, custom kernel, DRM fix, and Magisk all running in perfect harmony.....I really hope we can get there soon.
 

modpunk

Recognized Contributor
Oct 14, 2011
1,713
6,622
Sony Xperia XZ1 Compact
Samsung Galaxy S10
Lol, the good old unzip. Well spotted sir!

---------- Post added at 01:36 AM ---------- Previous post was at 01:29 AM ----------

@modpunk Any chance you could rebuild the recovery and include the unzip? I hate to keep asking people to do stuff but nobody else here can do it... That I know of. @pergoteborg What happens if you try to install Magisk with that firmware and recovery installed? I'm wondering if we can get that DRM fix running with Magisk as someone said was possible on one of the other threads about the DRM fix when it got released.
We may need a new kernel to get Magisk running so that will be in the hands of @janjan once he's had some time to recover from the surgery he just had.
All of this is leading me to think we're not forgotten by the dev world with our device. Just imagine having the latest firmware, custom kernel, DRM fix, and Magisk all running in perfect harmony.....I really hope we can get there soon.

I would recommend to use Magisk instead of SuperSU. Also the drmfix should be done differently. The ricoff stuff disables selinux! I would not use a device without selinux ...
 

Gnome1911

Member
Dec 4, 2013
49
9
Reutlingen
plus.google.com
You can easyily flash ZIP's on encrypted devices, if you put the files to the external SD. The external SD is not encrypted!

Tested with TWRP december security level and FW 47.1.A.12.3 (January security level).

I have absolutely no idea how this can work for @FerrisBueller
I downloaded 47.1.A.12.34 with XperiFirm, removed Userdata.sin and flashed the rest with Newflasher. Rebooted and everything works fine with new FW as expected.
Flashed the TWRP with december security level (same as @FerrisBueller), boot into TWRP and as expected is the filesystem encrypted so I cannot flash. I cannot understand how @FerrisBueller succeeded, it seems totally impossible to me.
Now, I did this today since the good pal and community hero @modpunk says he´ll build an updated TWRP which will solve that part of the problem shortly :)
When that´s solved we´ll check if the current DRMFix actually work....which I sincerely doubt.....but we´ll know for sure shortly
 

pergoteborg

Senior Member
Feb 11, 2009
225
97
Göteborg
You can easyily flash ZIP's on encrypted devices, if you put the files to the external SD. The external SD is not encrypted!
Tested with TWRP december security level and FW 47.1.A.12.3 (January security level).
And TWRP can still write to system when flashing?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Send from my Xperia XZ1 Dual (G8342) using Tapatalk
 
Last edited:

Gnome1911

Member
Dec 4, 2013
49
9
Reutlingen
plus.google.com
And TWRP can still write to system when flashing?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Send from my Xperia XZ1 Dual (G8342) using Tapatalk

Yes, i flashed all 3 files from the DRM fix on this way and the DRM Fix and SuperSU were working.
You have simply to "swipe to enable system modifications" on TWRP startup, without password
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 16
    [oreo]XZ1-drmfix-root-ricoff
    Available for any version of the official 8.0 oreo
    First you have twrp https://forum.xda-developers.com/xperia-xz1/development/twrp-t3716488

    Be sure to use the zip I provided,Make sure your rom is clean.If you want wipe data,cache and dalvik, please execute it first.

    1,flash drmpatch.zip
    2,flash SuperSU.zip
    3,flash RicOff.zip
    4,reboot

    Perfect, please enjoy.:D

    download
    https://mega.nz/#F!s8QlGD7S!cSlNJcZArwwdvZGGE5sVdA


    drmfix.so/drm****.so thank @sToRm// :good:

    The secd of 47.1.A.12.34 is the same as 47.1.A.8.49.
    secd original file(G8441_47.1.A.8.49_CE) https://mega.nz/#!IpYg1Q4Q!ONXXqHoP6JkrFQ9jGUHMMXlzHcPAfog3ISrMgogO8go
    modify
    E803003206000014E8031F3204000014E807003202000014E8031E32
    for
    08008052060000140800805204000014080080520200001408008052

    drmpatch.zip
    Install XperiFIX
    In C:\XperiFIX\DATA\XZP\G8142\Oreo2
    Modify the update binary
    ui_print "******************************"
    ui_print "Sony XZ Premium *OREO* DRM restore by //sToRm"
    ui_print "******************************"
    change
    ui_print "******************************"
    ui_print "Sony XZ1/XZ1C *OREO* DRM restore by //sToRm"
    ui_print "******************************"

    / system
    change
    /vendor

    And replace secd


    SuperSU.zip
    Modify init.supersu.rc.24 and init.supersu.rc.24.bindsbin

    on post-fs
    exec u:r:supersu:s0 root root -- /sbin/fbe_bypass.sh
    export LD_PRELOAD drmfix.so:drm****.so

    #RIC disable
    mount securityfs securityfs /sys/kernel/security nosuid nodev noexec
    write /sys/kernel/security/sony_ric/enable 0

    RicOff.zip
    The status of SELinux changes to permissive

    The original machao44 account is lost
    I do not know how to misunderstand me
    5
    Totally agree, but as of today we do not have a working solution for the DRMFix and Magisk, we have unfortunatly to choose. We can flash a working Magisk, but then the current DRMFIx does not work.
    Fortunately there is talented persons working with the issue and hopefulle we will be able to run Magisk with working camera shortly :)

    I'm already on my way. :cowboy:
    3
    I opened bootloader , my phone 47.1.A.2.374 I tried to flash 47.1.A.8.49 flashtool does not work in xperia g8342 :(
    At the start of the show the message glows ( your device hes been unlocked and can"t be trusted - your device will boot in 5 Seconds ) Currently I can not access developer options and the camera picks up green images
    What should I do؟
    all Respect and appreciation for you Senior Member
    .
    Green pictures are because you unlocked bootloader. Will be fixed by DRMFix.
    your device hes been unlocked and can"t be trusted-message will allways be there on unlocked BL
    Download G8342_MY_47.1.A.8.49 .rar according to this post, it contains latest ROM and newflasher

    You need to install drivers for flashtool. It may be a little tricky and it was soooo long ago I set it up myself I simply do not remember. Google it. Maybe This or http://www.**********.com/setup-androxyde-flashtool-sony-xperia-devices-windows/may help.

    With drivers installed:
    Turn off phone. Hold Vol down while connecting USB to computer (Green light on phone). Open commandprompt on computer and cd to unpacked G8342_MY_47.1.A.8.49 .rar directory. Run
    Code:
    newflasher.exe
    .
    This installs lastest stock kernel and firmware.
    When finished reboot phone

    Download DRMPatck package , unpack it and move the three zip files to phone

    Turn off phone

    Download twrp-3.2.1-0-poplar-1-patchlevel-2017-12-01.img and move the file to the same directory on computer where flashtool is installed
    Commect the phone to computer USB while holding Vol UP (Blue light on phone)
    Open commandprompt on computer and cd to flashtool directory (where also twrp-3.2.1-0-poplar-1-patchlevel-2017-12-01.img exists)
    Run command
    Code:
    fastboot flash recovery twrp-3.2.1-0-poplar-1-patchlevel-2017-12-01.img
    Disconnect phone.
    Hold Vol Down while starting the phone which brings you to TWRP.
    Flash DRMFix according to OP.
    DONE
    3
    Problem solved.
    Fix works also for latest 12.34 kernel.
    The error from the SuperSU-flashing gave me the lead to the problem. The new FW and/or TWRP does not provide unzip functionallity.
    In order to get the fix in OP working on FW47.1.A.12.34 follow this procedure:
    1. Make sure you're on a clean stock kernel, FW47.1.A.12.34 with Jan 5, 2018 security level
    2. Flash twrp-3.2.1-0-poplar-2-patchlevel-2018-01-05.img by @modpunk as stated in the [RECOVERY] TWRP 3.2.1-0 thread
    3. Boot into recovery
    4. Push busybox and softlink unzip as stated by @N1ghtr08d here in the post#20 of the TWRP thread
    5. Flash according to OP
    6. Reboot and enjoy

    A ton of respect and a busload of thanks to @sToRm// for his engagement and for pushing me in the direction of the solution (maybe without realizing it himself:)) by making me realize the flashing of the OP zips which did not give any errors still actually left the system unchanged. And a lot of thanks to @N1ghtr08d for pointing out the unzip problem earlier on. And certainly must also @ M-Rom be mentioned who have only the best of intentions. And of course @modpunk where further explaination is totally unnecessary. That´s what communities like this is all about. Get it or get out!

    and remember.....Don´t bother me, I bother you :)
    2
    Any chance to backup TA Partition?