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

[M-Rom]

[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.

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

 

[luigi92034]

前來支持個~~
謝馬大

 

[sofyanpall]

How do I get root and Kernel to xperia xz1 g8342 ?

How do I get root and Kernel to xperia xz1 g8342 ?

 

[pergoteborg]

How do I get root and Kernel to xperia xz1 g8342 ?

Unlocked bootloader and as it says here gives you root on stock kernel.
Use [RECOVERY] TWRP 3.2.1 twrp-3.2.1-0-poplar-1-patchlevel-2017-12-01.img from just that post if you´re at FW 47.1.A.8.49 due to EXT4 File Based Encryption (FBE)
If you´re on older FW use twrp-3.2.1-0-poplar-patchlevel-2017-11-05.img
or simply upgrade to 47.1.A.8.49 before proceeding

 

[sofyanpall]

thank you for your reply Senior Member

Unlocked bootloader and as it says here gives you root on stock kernel.
Use [RECOVERY] TWRP 3.2.1 twrp-3.2.1-0-poplar-1-patchlevel-2017-12-01.img from just that post if you´re at FW 47.1.A.8.49 due to EXT4 File Based Encryption (FBE)
If you´re on older FW use twrp-3.2.1-0-poplar-patchlevel-2017-11-05.img
or simply upgrade to 47.1.A.8.49 before proceeding

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

 

[pergoteborg]

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

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

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

 

[Araa01]

Next maybe custom rom?

Wysłane z mojego G8342 przy użyciu Tapatalka

 

[N1ghtr08d]

Hopefully

 

[enjelpuspa]

Any chance to backup TA Partition?

 

[sofyanpall]

root xperia xz1 g8342

.
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

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

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

Thank you so much pergoteborg
I followed the instructions and my phone works well and the camera works without problems
Before the operation you have repaired the phone system on a program ( emma )
:good::good::good:
The only remaining problem is developer options and not a necessity

 

[pergoteborg]

Thank you so much pergoteborg
I followed the instructions and my phone works well and the camera works without problems
Before the operation you have repaired the phone system on a program ( emma )
:good::good::good:
The only remaining problem is developer options and not a necessity

Go into settings -> system -> about phone and click repeatibly on version at the bottom to open up developer options

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Send from my Xperia XZ1 Dual (G8342) using Tapatalk

 

[sofyanpall]

root xperia xz1 g8342 47.1A.2.374

Go into settings -> system -> about phone and click repeatibly on version at the bottom to open up developer options

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Send from my Xperia XZ1 Dual (G8342) using Tapatalk

I changed the phone language from Arabic to English and the developer options worked well

 

[CoinsClassic]

I can confirm that the method of M-Rom works perfectly fine for my G8341 Xperia XZ1 with Android 8.0.0.

Additionally I wanted to add: For those who did not already solve the Google USB driver phenomenon for fastboot to detect Sony devices: See here: https://forum.xda-developers.com/xperia-u/issues/guide-how-to-install-fastboot-xperia-t2170114. This is the guide I followed to do it. You can get the file needed for that guide here, as the link provided there is no longer active: https://developer.sonymobile.com/downloads/drivers/fastboot-driver/

Thanks a bunch M-Rom and sToRm// for saving my phones life (and mine, too :good: )

 

[georgesalo]

Hello guys, can someone explain me how to install TWRP?
unlock bootloader from developed options?
after flashing twrp via fastboot? like fastboot flash recovery (recovery name.img)??
and what the features of drmfix ricoff?
does google camera HDR+ works?

Thanks!

 

[N1ghtr08d]

Hello guys, can someone explain me how to install TWRP?
unlock bootloader from developed options?
after flashing twrp via fastboot? like fastboot flash recovery (recovery name.img)??
and what the features of drmfix ricoff?
does google camera HDR+ works?

Thanks!

Yes, you're exactly right. Boot into the unlocked bootloader:

Adb reboot bootloader
(Next command)
Fastboot flash recovery name/and/location/of/recovery/image.img

Not sure if hdr+ works as I believe it uses api2 (I could be way wrong on that name) but I believe it uses something that this device doesn't support but I could be wrong.
DRM ricoff reactivates the Sony features and the Sony camera to full functionality. Basically once you've flashed TWRP then you can flash the root and DRM fix and you have root and fully working camera and features even though you've lost the DRM keys. The only difference between this method and the method created by Storm for the XZP is that on the XZP you can backup the TA partition whereas we haven't figured out how to do that yet but the result is still exactly the same.

 

[Gnome1911]

Hey, can i flash Magisk instead of SuperSU, or does the DRM Fix need SuperSU to work?

 

[N1ghtr08d]

Unfortunately the DRM fix needs SuperSU to work, the package comes with a special version of SuperSU to make it work. Hopefully if @aledoom gets some time he can try build a new version of the Andro+ kernel for our phone running the latest 8.49 firmware that will support Magisk and the DRM fix. He doesn't own an xz1 himself so testing isn't easy butt I'm sure one of us will be happy to help with that. I know I will for sure.
If he gets a working kernel built then we can have the DRM fix with Magisk instead of SuperSU, which I think we all would love.
The problem is that Magisk doesn't work on the stock kennel. In fact it causes a bootloop so don't try flashing it.

 

[xFirefly93]

[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.

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


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

Is this DRM-fix/patch working on the latest XZ1 firmware?

 

[CoinsClassic]

Is this DRM-fix/patch working on the latest XZ1 firmware?

Yes, it is working. Tested it with my G8341 XZ1 with latest firmware on 8.0.0.

Camera works again and you can set the X-Reality display saturation again.

 

[pbarrette]

I can confirm that the method of M-Rom works perfectly fine for my G8341 Xperia XZ1 with Android 8.0.0.

Additionally I wanted to add: For those who did not already solve the Google USB driver phenomenon for fastboot to detect Sony devices: See here: https://forum.xda-developers.com/xperia-u/issues/guide-how-to-install-fastboot-xperia-t2170114. This is the guide I followed to do it. You can get the file needed for that guide here, as the link provided there is no longer active: https://developer.sonymobile.com/downloads/drivers/fastboot-driver/

Thanks a bunch M-Rom and sToRm// for saving my phones life (and mine, too :good: )

If you're having trouble installing the fastboot / flashmode drivers from Sony because of driver signing issues, the answer should never be to disable driver signing altogether.

Instead you should look at the answer here and use the open-source tool it describes to install the driver with a self-signed certificate.

Of course, Sony should be doing a better job and releasing signed drivers so we wouldn't be in this situation to begin with.