- The DRM Fix or Xperifix solve any feature problem or are there any functions that are irrevocably lost?
- Camera, Bravia engine, Track ID (this still available?), Noise Canceling, PS4, , Xreality, 4k video recording sony bass surround, screen mirroring and image enhancement have stopped working though when rooted?
- The OTA updates work?
- xPosed work?
- what is the benefit of using alpha Xperifix of other DRM fix rom?
- Do it is possible with XZP to downgrade to Android Marshmallow, backup drm and root it?
Dematen said:
- The DRM Fix or Xperifix solve any feature problem or are there any functions that are irrevocably lost?
- Camera, Bravia engine, Track ID (this still available?), Noise Canceling, PS4, , Xreality, 4k video recording sony bass surround, screen mirroring and image enhancement have stopped working though when rooted?
- The OTA updates work?
- xPosed work?
- what is the benefit of using alpha Xperifix of other DRM fix rom?
- Do it is possible with XZP to downgrade to Android Marshmallow, backup drm and root it?
Click to expand...
Click to collapse
The DRM keys on your phone are lost forever when you unlock it. The good news is that Xperiafix fools the phone into thinking that DRM is in place, so all the higher functions still work as stock.
DRM is broken or fixed, the camera is broken or fixed, it's common misconception to think that there's a half way point where there are bad or distorted pictures or loss of quality or service..
The down side to rooting is that updates are no longer automatic and any firmware update has to be completed manually, which involves flashing multiple files.
I have root on my XZ1 compact (thanks to sToRm//'s Xperiafix) everything works perfectly, but the proccess of chasing the various firmware updates is so tiresome that I have given up.
Xposed will only work on firmware from pre May 2018. So if you have the latest firmware on your phone you will need to use Emma to downgrade your phone to an earier firmware, this isn't so easy. Installing Xposed means that you will fail any sort of security check, don't complain when Googlepay doesn't work.
If you are determined to root your phone I would advise paying $20 for sToRm//'s Xperiafix. It's the simplest way to do it and his version 3 has come along leaps and bounds from the early versions and as long as you get the right drivers (err, no easy task) and can follow instructions, you'll get there.
There are other DRM fix options available, but they involve flashing multiple files and sometime the instructions are not so clear, or support not so good if you fail.
Whichever version of the fix you decide to use, you need to know that the developer is commited to supplying all the modified files for you to reflash every time there is a firmware update.
You can go back to an M build, using Emma, but I'm not sure you'll find ina DRMfix file for an old build and if you do it will be tied to a particular firmware/region/version number. This will be the most difficult bit.
There is no backing up the DRM!
Dematen said:
- The DRM Fix or Xperifix solve any feature problem or are there any functions that are irrevocably lost?
- Camera, Bravia engine, Track ID (this still available?), Noise Canceling, PS4, , Xreality, 4k video recording sony bass surround, screen mirroring and image enhancement have stopped working though when rooted?
- The OTA updates work?
- xPosed work?
- what is the benefit of using alpha Xperifix of other DRM fix rom?
- Do it is possible with XZP to downgrade to Android Marshmallow, backup drm and root it?
Click to expand...
Click to collapse
Hello,
It does not matter if you use xperifix or another, both work, the only thing that one is automatic and the other is manual.
Everything works once "Deceived the DRM", everything.
There is no software or system currently that allows you to save your DRM, even if you download MM.
Using xposed is not secure or stable. It also does not work in all versions.
With flashtool you can manually update to the desired version. Because it is newer it does not mean it is better, it will have security patches and some other change not communicated. Some versions work better than others.
Cheers ?
Enviado desde mi G8141 mediante Tapatalk
sam.foro said:
Hello,
It does not matter if you use xperifix or another, both work, the only thing that one is automatic and the other is manual.
Click to expand...
Click to collapse
That's not true. The files offered by other developers are very outdated. These are the files I developed and offered a long time ago in the first versions of XperiFIX. XperiFIX uses a different method since 2.0 and is flexible in terms of firmware and devices. It does not need a pre-customized kernel and does not depend on Sony's different firmware configurations.
What's more: Sony has made changes in the meantime, as you can already see on newer devices. XperiFIX adapts to these changes and will be able to handle the changed security features in the future. The outdated files will most likely stop working. It could even come to a brick because the old modified system file is no longer compatible with the changes. In another method, you could also find that the fix was only partially because it is integrated wrongly.
So there are very big differences in the methods. XperiFIX is now also so far that you can basically fix any device with current firmware versions (manual fix).
Thanks for the clarification, in your changelog you do not indicate anything of the mentioned here. And the truth is a great job but I think it's too expensive.
https://www.xperifix.com/download/xperifix-latest/
Enviado desde mi G8141 mediante Tapatalk
sam.foro said:
Thanks for the clarification, in your changelog you do not indicate anything of the mentioned here. And the truth is a great job but I think it's too expensive.
https://www.xperifix.com/download/xperifix-latest/
Enviado desde mi G8141 mediante Tapatalk
Click to expand...
Click to collapse
It's worth the cost compared to the other (non supported) and much more difficult solutions, that are not kept up to date with firmware rollouts.
Version 3 is so easy to use and requires no knowledge of firmware or TWRP or kernels.
Didgesteve said:
It's worth the cost compared to the other (non supported) and much more difficult solutions, that are not kept up to date with firmware rollouts.
Version 3 is so easy to use and requires no knowledge of firmware or TWRP or kernels.
Click to expand...
Click to collapse
Everyone is free to do what they want, the opinion is free and all are respected. If there is demand there is sale.
A user who does not know twrp, kernel or root should not manipulate the terminal, in my humble opinion. Stock is also good.
Enviado desde mi G8141 mediante Tapatalk
Related
Hi, I have D2403 with zexperience installed on it and I wanted to hear your guys oppinions on 5.1.I have locked bootloader and I can't unlock it and I dont understand is it safe to root now or no with Locked BL? Is it worth to update 5.1 or should i stay with my current system etc..?
cheers
Yes you can update of you want to, it does take up slightly more room than kk did. it took about two weeks for my battery life to settle down but once it does battery life is better than kk for me never get less than 5-6hrs screen time sometimes a bit more and that's with the zram as Sony intended. yes root is available for LB but only by flashing a pre-rooted zip via recovery on rooted kk and recovery is only available at the minute by using t2u nut dual recovery(not ideal but it does work). If you're totally stock and don't want root I'd update by Sony pcc. Only thing I'm really missing is xposed I think it was worth the wait myself.
D2303 5.1lollipop customised NCB rooted LB t2u nut dual recovery bravia engine+x-reality debloated
Weekend Offender said:
Hi, I have D2403 with zexperience installed on it and I wanted to hear your guys oppinions on 5.1.I have locked bootloader and I can't unlock it and I dont understand is it safe to root now or no with Locked BL? Is it worth to update 5.1 or should i stay with my current system etc..?
cheers
Click to expand...
Click to collapse
Rooting is as safe as ever. Just more complicate to enable it (basically start from KK, root it, install recovery, make PRF file with 5.1.1 system, flash PRF file from recovery, flash rooting zip from recovery, flash remaining 5.1.1 components with Flashtool and restart all over downgrading to KK if anything goes wrong).
Regarding if it's worth it.. The current issues are:
- The camera sucks for many. Even Xperia Blog reported it now.
- It uses more RAM (which is vey disappointing. I thought ART was going to need less memory?!). Disabling the zram and setting the minfree as they were in KitKat one gets nearly zero multitasking
- Frequent I/O wait even with the zram disabled (but not as bad as with the zram. Unfortunately see above)
- The WiFi has different functionalities from KK (it stays connected to the WiFi even if the AP drops the internet connection. The option to disable it has gone. In other cases it shows an exclamation mark due to something with Captive Networks)
- It seems to me it lags more. But I have plenty of apps installed.
- Few old apps perform poorly
- Many old KK Xperia themes won't work in full , yet (at least the ones I liked the most)
- Potential issues with the GPS (it seems to be a bug in Lollipop generally speaking)
- I hate the new notifications
The Pros:
- Better Stamina mode
- The slick new UI, I especially love the new open applications list (which finally puts a separate window for apps open inside other apps. IMDB from TV Sideview excluded, though)
- Some newer apps make full use of the Lollipop API and more will follow
IMO KitKat is more stable and efficient. But I like Lollipop nonetheless so I decided to stick with it. The few bugs around aren't a deal breaking to me.
Yes you should always upgrade to the newest android.
After battery drain,gps and camera issue I am back to 4.4.4 and ALL work fine and i am happy.
I'm holding back to see if we can get a working recovery (other than Nut's T2U) on a locked bootloader and hopefully then @linuxct will cook us up a new version of his Lite ROM based on 5.1.1 with all the kinks of the official software ironed out
gordonthegopher said:
I'm holding back to see if we can get a working recovery (other than Nut's T2U) on a locked bootloader and hopefully then @linuxct will cook us up a new version of his Lite ROM based on 5.1.1 with all the kinks of the official software ironed out
Click to expand...
Click to collapse
We (@AleksJ and I) are currently working on a fully functional recovery solution for both Lollipop and KitKat (No need to use T2U solutions anymore, which is quite RISKY as I explained in some threads before).
If there aren't any inconveniences, we should be releasing it soon. After that I'll start the Z4 eXPERIence 4.0 (it'll be a light edition) development.
Yea true, two days ago linuxct told me that he's found a way to use a good bueselinux module by zxz0O0 in our recovery installer.
Well fine the installer is back on the game, it can be used on the recent Android release with old recovery. But....recently we also noticed a very nasty touch screen issues the reasons for which are unclear for now.
p.s.
The PhilZ Touch project is "End Of Support", but believe or not with this recovery boot.img I can install and run on my unlocked M2 the latest Omnirom and CM (without sensors lib) in the same way as CWM and TWRP..)
Of course I can't and don't want to tell anyone what and how to do. Just share my opinion.
Hi, when can we expect the new Z4 eXPERIence 4.0to arrive? if You need some Beta testers, I would be happy to asign
(Sorry if this isn't the right thread for the question!)
@semil
Linuxct said he will work on updating that rom after he and AleksJ finish working on a legit recovery for LB.
Hi guys,
I have a Xperia Z5 running on Android 5.1.1, rooted but completely stock otherwise. The phone has been pestering me about the software update for a while now, but I've been putting it off.
I assume I cannot just use the OTA update to update a rooted phone, while keeping root, is that correct? If this is the case, how do I go about getting a newer version of Android on plus rooted? Is there any special steps I need to take to do this coming from a rooted phone as a base?
What about the DRM keys, there seems to be some new method of dealing with that while keeping X-reality and camera improvements, can I still do that even though I used the earlier workaround for the loss of DRM keys when flashing? (it was sometime like Dec. 2015 I rooted it, my memory on the process is rusty)
Finally, did anyone ever get Xposed working on this model of phone, coming from my Galaxy the one thing I really miss was the Youtube Adblocker module for Xposed, if I could get that back I'd love it!
I did have a search around for information on this, but most of the threads assume you're starting from a stock phone as a base, not a rooted phone, and I was not sure if the new DRM workaround was compatible with the other one... I'd like to not do something I shouldn't have and end up bricking the thing!
Any help would be appreciated. Thanks in advance.
flash latest marshmallow 32.2.A.5.11 and flash patched stock and flash supersu sr5 2.78 in twrp and you are good to go
Thanks mate, nothing to worry about then really?
Le_Petit_Lapin said:
Thanks mate, nothing to worry about then really?
Click to expand...
Click to collapse
nothing to worry about, plus patched kernel has all drm fixes so xreality, etc.. works
Hi guys, here is a fix for low sound that Xiaomi "fixed" for us.
Magisk module https://www.dropbox.com/s/jvejynqlw5gz0l6/soundfix_test.zip?dl=0
MD5: 64D9A517EBDD77D7EACD087E1A33FF07
Thanks to KatsonWatson from 4pda
Hi,
Can you tell me if it's working for you (and where is this from)? My phone is not rooted etc., but I can't stand this new poor audio on a pair of high impedance earphones.
Is it installed like a module from zip via recovery?
TheDoom said:
Hi,
Can you tell me if it's working for you (and where is this from)? My phone is not rooted etc., but I can't stand this new poor audio on a pair of high impedance earphones.
Is it installed like a module from zip via recovery?
Click to expand...
Click to collapse
Install and flash Magisk and then install the module vía Magisk interface.
Magisk Is systemless so it's safe to use.
Cant tell if this module works since i still didnt update may patch but dont be afraid to try. I used this to root and install GoogleCam, no issues so far.
Just remember to follow the instructions before installing new OTAs!!
Thanks for the help! So installing this means no more OTA for me? Because I guess that any other update that comes out will bring back the crappy sound.
BTW is Google Cam a huge improvement?
TheDoom said:
Thanks for the help! So installing this means no more OTA for me? Because I guess that any other update that comes out will bring back the crappy sound.
BTW is Google Cam a huge improvement?
Click to expand...
Click to collapse
Google cam is A LOT better than stock camera.
Wysłane z mojego Mi A1 przy użyciu Tapatalka
Yup, you'll need to root and ofc use magisk (because this is magisk module) and you can't do OTAs, but for the sound that our device has, it's worth it.
Deni_NS said:
Yup, you'll need to root and ofc use magisk (because this is magisk module) and you can't do OTAs, but for the sound that our device has, it's worth it.
Click to expand...
Click to collapse
Magisk does not prevent OTA updates, as long as you know what you are doing.
To wit: 0. disable automatic OTA updates, 1. leave the stock recovery alone (TWRP can be booted into without flashing), 2. make sure to check "systemless hosts" in Magisk Manager if you use AdAway or similar, so that you don't ever write to your actual /system partition, 3. leave your phone oem-unlocked (it's OK, /data is encrypted anyway), 4. when an OTA update is available, follow instructions (can't post a proper URL yet, sorry) at github.com/topjohnwu/Magisk/blob/master/docs/tips.md
cmmike1 said:
Magisk does not prevent OTA updates, as long as you know what you are doing.
To wit: 0. disable automatic OTA updates, 1. leave the stock recovery alone (TWRP can be booted into without flashing), 2. make sure to check "systemless hosts" in Magisk Manager if you use AdAway or similar, so that you don't ever write to your actual /system partition, 3. leave your phone oem-unlocked (it's OK, /data is encrypted anyway), 4. when an OTA update is available, follow instructions (can't post a proper URL yet, sorry) at github.com/topjohnwu/Magisk/blob/master/docs/tips.md
Click to expand...
Click to collapse
Yeah, but will another OTA overwrite my Magisk Sound Fix or Google Cam?
TheDoom said:
Yeah, but will another OTA overwrite my Magisk Sound Fix or Google Cam?
Click to expand...
Click to collapse
It won't, that's what "systemless" means.
Working fine, Thanks
Wysłane z mojego Mi A1 przy użyciu Tapatalka
I'm glad to hear that [emoji4]
I can confirm that it works on my phone also. Thank you very much!
May I ask what files the module touches? Also, what did Xiaomi change in the May update to reduce the volume?
Thanks
You can unpack module and see what is changed.
thanks, but when i enable this module the mi a1 hardware keys backlight doesnt work
deewfrank said:
thanks, but when i enable this module the mi a1 hardware keys backlight doesnt work
Click to expand...
Click to collapse
Work for me
Work fine! I love it
When I try to install it via Magisk Manager, it says it's not a magisk module. I don't have custom recovery to preserve OTA, can't it be flashed through magisk somehow?
Can someone confirm if this is working with the last 8.1 update? They improved audio a little bit compared to 8.0 but its nothing compared to the nougat ROM
AceStroke said:
Can someone confirm if this is working with the last 8.1 update? They improved audio a little bit compared to 8.0 but its nothing compared to the nougat ROM
Click to expand...
Click to collapse
Work on June and July update
I would like to install Netflix from the PlayStore and have it update from there like other apps. Is this possible after unlocking the bootloader? In case it isn't clear, I don't want to sideload it so please don't suggest that.
reiriop said:
I would like to install Netflix from the PlayStore and have it update from there like other apps. Is this possible after unlocking the bootloader? In case it isn't clear, I don't want to sideload it so please don't suggest that.
Click to expand...
Click to collapse
Obvious that is possible , I have Netflix and unlocked bootloader 1 thing don't have nothing to do with the other thing
Have you done anything other than unlock the bootloader? I'm not on a custom ROM or anything, I just mixed some stock firmware so I could get fingerprint sensor in the US. I also installed a kernel that hides bootloader unlock but in the PlayStore Netflix is listed as not compatible with my device.
reiriop said:
Have you done anything other than unlock the bootloader? I'm not on a custom ROM or anything, I just mixed some stock firmware so I could get fingerprint sensor in the US. I also installed a kernel that hides bootloader unlock but in the PlayStore Netflix is listed as not compatible with my device.
Click to expand...
Click to collapse
Don't worry about that, it's working
I installed the Magisk module 'liboemcrypto disabler' on Android Pie to be able to even see Netflix in the Playstore. Now Netflix works and updates from the Playstore as well. But I can't watch content in HD.
On Oreo Netflix worked in HD and HDR mode, but I had to install a DRM fix to achieve that.
ishemes said:
I installed the Magisk module 'liboemcrypto disabler' on Android Pie to be able to even see Netflix in the Playstore. Now Netflix works and updates from the Playstore as well. But I can't watch content in HD.
On Oreo Netflix worked in HD and HDR mode, but I had to install a DRM fix to achieve that.
Click to expand...
Click to collapse
Have you tried janjan's kernel with DRMfix built in?
works with Pie
Didgesteve said:
Have you tried janjan's kernel with DRMfix built in?
works with Pie
Click to expand...
Click to collapse
Thank you for the suggestion, but janjan's kernel only has a drm fix for Oreo if I understand correctly. I don't believe there is a DRM fix for Pie available (yet). I also don't think anybody is going to spend the time needed to create one, because now that the camera works, most people don't even notice that a DRM fix is necessary.
ishemes said:
Thank you for the suggestion, but janjan's kernel only has a drm fix for Oreo if I understand correctly. I don't believe there is a DRM fix for Pie available (yet). I also don't think anybody is going to spend the time needed to create one, because now that the camera works, most people don't even notice that a DRM fix is necessary.
Click to expand...
Click to collapse
Sorry, you're right, my bad. I have been using janjan's kernel on Oreo and it's been flawless. Given the amount of negative comments about Pie, are you not tempted to go back to something that works properly?
Didgesteve said:
Sorry, you're right, my bad. I have been using janjan's kernel on Oreo and it's been flawless. Given the amount off negative comments about Pie, are you not tempted to go back to something that works properly?
Click to expand...
Click to collapse
I actually love Pie. I removed most of my rooted apps because Pie has functionality built in that I really wanted on Oreo. Like choosing dns servers, dns over https, rotation icon in navigation bar, bluetooth device battery percentage and more things I can't remember. Battery life is good.. phone is stable... My only complaints are that Sony took out some of the things that make Pie more usefull. But besides that I'm happy.
ishemes said:
I installed the Magisk module 'liboemcrypto disabler' on Android Pie to be able to even see Netflix in the Playstore. Now Netflix works and updates from the Playstore as well. But I can't watch content in HD.
On Oreo Netflix worked in HD and HDR mode, but I had to install a DRM fix to achieve that.
Click to expand...
Click to collapse
This didn't work for me, still the same issue. I also tried flashing janjan's kernel but it didn't make a difference either and the ctsProfile is still false. Does anyone know if the ctsProfile being false would cause this?
Another thing that I think is separate but strange is that I have Magiskv19.0 installed but the Magisk Manager tells me Magisk is not installed and that v18.1 is the latest version.
reiriop said:
This didn't work for me, still the same issue. I also tried flashing janjan's kernel but it didn't make a difference either and the ctsProfile is still false. Does anyone know if the ctsProfile being false would cause this?
Another thing that I think is separate but strange is that I have Magiskv19.0 installed but the Magisk Manager tells me Magisk is not installed and that v18.1 is the latest version.
Click to expand...
Click to collapse
I think something went wrong flashing your system. I have magisk installed and ctsProfile: true. I would concentrate on that first. Fixing magisk and ctsProfile will probably fix Netflix as well. Good luck!
Ya, so before I flash the tmobile volte/wifi calling zip or flash my kernel .img the ctsProfile is true and I am able to install Netflix from the play store. As soon as I flash one of those though the ctsProfile check turns to false. I need to flash these though or I'm not able to get VoLTE, WiFi Calling, and without hiding the bootloader unlock with the kernel some of the Sony features don't work.
By all means, read @Neffy27 's FAQ if you are starting out. even as a refresher for stuff you may have forgotten.
-But do think a bit about what you are doing:
-Do not modify your phone unless you are willing to toss it into the trash, as that could well be the result, no matter how well planned.
-Always have a spare on hand. I used my old Moto G3 when my MZP died suddenly. Worked just fine. You know, things really haven't changed all that much since Gingerbread...
-If you are going to be getting the latest OTA stuff by doing a full flash you might want to reflect on just how much, or little, you would gain. We all like to think that if we have the latest security patch we are somehow more safe, though I don't believe I have ever heard of a phone being affected by something just because it is not on the latest patch. I was running my old Moto z play on an aug '18 (if I remember correctly) patch with no problems up until a few weeks ago when it was done in by an expanding battery envelope which cracked the display. Consider, also, that many of the custom roms that are available are not updated at all - it takes a ton of work to try to get/keep a custom ROM current, AND working! Yet you never hear of viruses or the like.
- Be aware that if you modify ANYTHING on your phone, even as little as a new boot logo to cover up the unlocked bootloader message, you will prevent your phone from taking any further OTA updates. Some mods, like adding TWRP, may still allow it to try to download and install an OTA, but when it reboots to finish that install, it will fail since it needs to re-boot through stock recovery to complete. And it will continue offering you that update.
- There is a difference between the partition structure in our phones on 8.x, and those on 9. 9 is not full Treble, only a "partial" Treble, and really only the addition of a second set of partitions which OTA updates can use to update the system - instead of modifying the single partition set, it modifies the other (a or b) set and boots to that on update completion. If it fails it can always boot the other set. Theoretically! Makes it safer than the old way of doing OTA updates, but this may cause problems if you try to flash a 2 partition set phone with a single partition set ROM. I don't believe anyone has run any experiments on this, so YOU, when you flash things without thinking about the situation, may get an unusable phone. I do not know the answer here. If you read these forums which detail other's problems, you may trod a bit more hesitantly!
-The idea here is to have fun, and sometimes to experiment with new things. To a newbie, losing the use of a $200 phone can be a tough life lesson. Let's help them out by helping them to be cautious!
Agreed. I've been running stock with January 2018 patch, TWRP installed and Magisk for root and successful safety net bypass.
I'm looking to see if running Lineage will help streamline any update processes. It looks like they have their own recovery too.
Maintaining root has become a pain in my ass the past few years.
Sent from my moto x4 using Tapatalk
SR3TLAW said:
Agreed. I've been running stock with January 2018 patch, TWRP installed and Magisk for root and successful safety net bypass.
I'm looking to see if running Lineage will help streamline any update processes. It looks like they have their own recovery too.
Maintaining root has become a pain in my ass the past few years.
Sent from my moto x4 using Tapatalk
Click to expand...
Click to collapse
I would be careful about lineage as folks don't seem to be able to get back to stock from it.
I agree about maintaining root. I will likely just stay on stock with this one.