[EOL][RECOVERY][Android 8 / 9][Stock/SODP][XZ2/c/p, XZ3] TWRP [UNofficial]

Search This thread

andreux481

Member
Sep 30, 2014
9
0
good evening,
I recently bought a sony xz2 compact and I would like to be root but I don't know where to start and reading the post I didn't understand.
Someone could write me the necessary steps and files please.
Is there still a risk of losing the camera functions etc?
Thank you all
 

levone1

Senior Member
Dec 28, 2014
3,767
1,452
good evening,
I recently bought a sony xz2 compact and I would like to be root but I don't know where to start and reading the post I didn't understand.
Someone could write me the necessary steps and files please.
Is there still a risk of losing the camera functions etc?
Thank you all

Instructions are simple, posted in post #3 of central project thread, linked in first post of this thread, (see screen shot). Assuming that you have adb/fastboot installed on your computer, and your bootloader is unlocked, just download the zip in post 3, and use the commands and instructions there.

As far as I know, there is no current method to backup ta for Xz2c. I did see a temp root solution in the xz1c thread, but didn't bother trying. To me it doesn't seem like as much of an issue as it has been in the past. I just went ahead and unlocked my bootloader, and I think the camera is still pretty nice
I just took the 2 pictures attached to test.

I did go ahead and do a dd dump of ta partition after unlocking, just to see what would happen, and I ended up with a 2mb file. I don't know if that means anything - maybe it's just empty space or something... Anybody else know?
 

Attachments

  • Screenshot_20190424-133631.jpg
    Screenshot_20190424-133631.jpg
    187.7 KB · Views: 398
  • DSC_0004.jpg
    DSC_0004.jpg
    259 KB · Views: 408
  • DSC_0001.jpg
    DSC_0001.jpg
    257 KB · Views: 397
Last edited:
  • Like
Reactions: MartinX3

levone1

Senior Member
Dec 28, 2014
3,767
1,452
The system and firmware dumps are usually the size of the respective partitions, regardless of the amount of space actually containing firmware.

Right..
I just remember from backing up my ta in the past on other Xperias, that the ta dump is always exactly 2mb, so when I saw that, I wondered if it was a valid dump, but not sure how that could be, since I already unlocked bl... Anyway, it's not so important now, as it was before - https://www.xda-developers.com/sony-xperia-android-pie-unlock-bootloader-drm-fix-camera/amp/
 

MurroFX

Senior Member
Nov 12, 2018
221
31
37
Kolvereid
Hello,

I own a XZ2 Compact (German version) and I want to root it. Is there a way to get root access with the latest build (52.0.A.8.25)???
After hours and hours of reading, trying, flashing etc. I com to the conclusion: This is quite difficult! Maybe anyone can help me with it.

At the moment I unlocked the bootloader and 52.0.A.3.84 is the build nr.

the code leads to the following message



After some looking/reading I found a thread that there is only one partition in pie, is that right?
So is there a way to have a second (recovery) partition?

Thx for any help!

Good question! I have the same problem.
I can fastboot boot twrp. IMG but it is encrypted, and can't find any files. ?

Have u found a solution? ?

Sent from my Sony H9436 using XDA Labs

---------- Post added at 03:49 PM ---------- Previous post was at 03:45 PM ----------

Hello,

I own a XZ2 Compact (German version) and I want to root it. Is there a way to get root access with the latest build (52.0.A.8.25)???
After hours and hours of reading, trying, flashing etc. I com to the conclusion: This is quite difficult! Maybe anyone can help me with it.

At the moment I unlocked the bootloader and 52.0.A.3.84 is the build nr.

the code leads to the following message



After some looking/reading I found a thread that there is only one partition in pie, is that right?
So is there a way to have a second (recovery) partition?

Thx for any help!



Good question! I have the same problem.
I can fastboot boot twrp. IMG but it is encrypted, and can't find any files. ?

Have u found a solution? ?

Sent from my Sony H9436 using XDA Labs
 

lba810701

Senior Member
Good question! I have the same problem.
I can fastboot boot twrp. IMG but it is encrypted, and can't find any files. ?

Have u found a solution? ?

Sent from my Sony H9436 using XDA Labs

---------- Post added at 03:49 PM ---------- Previous post was at 03:45 PM ----------





Good question! I have the same problem.
I can fastboot boot twrp. IMG but it is encrypted, and can't find any files. ?

Have u found a solution? ?

Hi!
I've got the same problem, until i booted up the newest twrp 3.3.1 solve that problem. Newest omnirom (0531) and the newest twrp (0601) are good together from Martin's server.
 
  • Like
Reactions: MartinX3

xarinatan

Member
Mar 8, 2018
33
11
I can't seem to get TWRP to work with the stock firmware from Emma. My process:
- flash android 9 firmware and data with Emma
- boot into system and adb reboot-bootloader
- fastboot flash vbmeta --disable-verity --disable-verification
- fastboot boot twrp-xz2c-stock.img
- install to recovery ramdisk -> twrp-xz2c-stock.img <-- I see a few mentions of 'Error getting bootctrl module'
- (with and without) wipe data, dalvik and internal storage
- reboot into recovery
- hangs on teamwin recovery project 3.3.1-0 logo forever.

what am I doing wrong?

edit: same happens with stock android 8. Also the OS still boots despite TWRP being broken.
 
Last edited:

ZioFrengo

Member
Nov 18, 2018
9
3
I can't seem to get TWRP to work with the stock firmware from Emma. My process:
- flash android 9 firmware and data with Emma
- boot into system and adb reboot-bootloader
- fastboot flash vbmeta --disable-verity --disable-verification
- fastboot boot twrp-xz2c-stock.img
- install to recovery ramdisk -> twrp-xz2c-stock.img <-- I see a few mentions of 'Error getting bootctrl module'
- (with and without) wipe data, dalvik and internal storage
- reboot into recovery
- hangs on teamwin recovery project 3.3.1-0 logo forever.

what am I doing wrong?

edit: same happens with stock android 8. Also the OS still boots despite TWRP being broken.
Mount vendor in the twrp to solve this problem
 
  • Like
Reactions: xarinatan

xarinatan

Member
Mar 8, 2018
33
11
Mount vendor in the twrp to solve this problem

Thanks! Strangely, this did make the 'Error getting module bootctrl' message disappear, however it still seems to stay stuck in the TWRP boot logo. I'm gonna try it again this time with a full data+dalvik+storage wipe to see if that has any effect..
Edit: wiping doesn't affect it. Here's dmesg from the recovery https://pastebin.com/JJJ7uf9G . don't see much special except that some process called 'keymaster' seems to be started/stopped a few times near the end of the log?
 
Last edited:

MartinX3

Recognized Contributor
Sep 14, 2014
5,716
2,826
Mars
martinx3.github.io
Thanks! Strangely, this did make the 'Error getting module bootctrl' message disappear, however it still seems to stay stuck in the TWRP boot logo. I'm gonna try it again this time with a full data+dalvik+storage wipe to see if that has any effect..
Edit: wiping doesn't affect it. Here's dmesg from the recovery https://pastebin.com/JJJ7uf9G . don't see much special except that some process called 'keymaster' seems to be started/stopped a few times near the end of the log?
The Bootctrl error was introduced with the June security patch.
Mounting vendor lets it using the file which is already copied into the ramdisk.
But it has no high priority, because it is only needed to switch the slots in twrp which can be done in fastboot too or by mounting vendor.

Emma shows a firmware version number.
Did you download the twrp with a matching number?
Or googles rollback protection denies the decryption.
 

xarinatan

Member
Mar 8, 2018
33
11
The Bootctrl error was introduced with the June security patch.
Mounting vendor lets it using the file which is already copied into the ramdisk.
But it has no high priority, because it is only needed to switch the slots in twrp which can be done in fastboot too or by mounting vendor.

Emma shows a firmware version number.
Did you download the twrp with a matching number?
Or googles rollback protection denies the decryption.

hmm, I downloaded the latest TWRP from your repository, with the latest firmware from Emma, I don't know where else to get TWRP, they don't list this device on their official website. Where can I see this version number in your TWRP builds?
 

MartinX3

Recognized Contributor
Sep 14, 2014
5,716
2,826
Mars
martinx3.github.io
hmm, I downloaded the latest TWRP from your repository, with the latest firmware from Emma, I don't know where else to get TWRP, they don't list this device on their official website. Where can I see this version number in your TWRP builds?
Emma shows the firmware version in the GUI and the twrp firmware number should be in the filename. :)
 
  • Like
Reactions: xarinatan

xarinatan

Member
Mar 8, 2018
33
11
it took me a while to find, but you're right on! the latest firmware which I got from Emma is 52.0.A.3.84 and the latest TWRP build in your repo is 52.0.A.8.83.. I guess I'll try see if I can even find the right firmware in Emma, otherwise I'll try xperifirm + newflasher for the first time I guess ...

it still surprises me that for the company that brags the most about 'open devices' they're definitely one of the hardest to deal with, I'm not going to buy more sony devices until they fix that, and I also set up a warranty repair to get the original firmware back on it so I can just sell the device. completely done with their bs tbh, it's nice that they fund an internal team to work on opensource versions of the ROM, but with their vicious DRM practices, the lack of cooperation between the 'closed' and 'open' teams, and seeming shortage of funding and time that the open team gets, they're basically one of the worst open devices on the market, if you can even call them that when half of the features outright stop working forever as soon as you unlock the bootloader. ugh.
 

MartinX3

Recognized Contributor
Sep 14, 2014
5,716
2,826
Mars
martinx3.github.io
it took me a while to find, but you're right on! the latest firmware which I got from Emma is 52.0.A.3.84 and the latest TWRP build in your repo is 52.0.A.8.83.. I guess I'll try see if I can even find the right firmware in Emma, otherwise I'll try xperifirm + newflasher for the first time I guess ...

it still surprises me that for the company that brags the most about 'open devices' they're definitely one of the hardest to deal with, I'm not going to buy more sony devices until they fix that, and I also set up a warranty repair to get the original firmware back on it so I can just sell the device. completely done with their bs tbh, it's nice that they fund an internal team to work on opensource versions of the ROM, but with their vicious DRM practices, the lack of cooperation between the 'closed' and 'open' teams, and seeming shortage of funding and time that the open team gets, they're basically one of the worst open devices on the market, if you can even call them that when half of the features outright stop working forever as soon as you unlock the bootloader. ugh.
About being stuck in the twrp logo.
That's googles fault (google rollback protection).
The Sony firmware just implements the newest google requirements.

Emma just contains the latest firmware tested by the "open" team.
Of course the are not a big team, so they can't test every firmware, but at least is a team better than no team.

Xperifirm let's you download the newest firmware and newflasher let you flash it. :)
Maybe the xperia companion works too.

The "closed" and the "open" team can't work together because there are parts of the firmware Sony isn't allowed to use in open source projects. License requirements. Maybe too because they want to hide their intelligence property like the other companies.
But at least they pay the "open" team resources and equipment.
They can develop their own closed source hardware for the "open" team ROMs.
Of course closed because of the licenses of the hardware vendors. But at least the Sony employee part if the team is allowed to access it (under NDA contracts).


PS: Sony weaks the DRM protection with every new Android version.
 
  • Like
Reactions: mirhl

xarinatan

Member
Mar 8, 2018
33
11
About being stuck in the twrp logo.
That's googles fault (google rollback protection).
The Sony firmware just implements the newest google requirements.

Emma just contains the latest firmware tested by the "open" team.
Of course the are not a big team, so they can't test every firmware, but at least is a team better than no team.

Xperifirm let's you download the newest firmware and newflasher let you flash it. :)
Maybe the xperia companion works too.

The "closed" and the "open" team can't work together because there are parts of the firmware Sony isn't allowed to use in open source projects. License requirements. Maybe too because they want to hide their intelligence property like the other companies.
But at least they pay the "open" team resources and equipment.
They can develop their own closed source hardware for the "open" team ROMs.
Of course closed because of the licenses of the hardware vendors. But at least the Sony employee part if the team is allowed to access it (under NDA contracts).


PS: Sony weaks the DRM protection with every new Android version.

thank you for the explanation, however I personally believe the intellectual property defense is overkill, and I also feel like (almost) every OEM out there is actually managing to release a working opensource ROM or at least a dump with all the kernel-related source codes, as that is a hard requirement due to the Linux kernel being GPLv2 licensed.
So on one hand yes, Sony is definitely helping out the industry by paying for an opensource team to work exclusively on opensource roms, but on the other hand they're sneakily getting away with a very poor opensource experience and fierce DRM practices that technically have little right to exist at all on the Android ecosystem due to its GPL requirements..

Of course I do hope Sony continues their opensource team, but I really want to see them release more of their 'closed' ROM for public use, they're already requiring you to install a gross blob of binaries for the phone to work at ALL even with opensource ROMs, so I don't see any reason why they're so fierce on keeping their stuff to themselves, besides feeling like they could squeeze out a few extra pennies at the cost of the end user, and that disgusts me TBH.

Companies these days are grossly greedy, from aggressive datamining practices to vicious DRM, to dark design patterns to trick you into agreeing to stupid ****, and the whole reason I went with Sony is because they always had some promise to have open devices and it actually WORKED back with the xperia pro mk16i, Z, Z1 compact, and Z5 compact that I all still own, but then when I tried the XZ2 I was shocked to find how far it degraded its abilities, completely and entirely crippling the camera! And the only reason they get away with it is because they're still using that same old disclaimer that it's 'your own risk' .. NO dear Sony, it's not my own risk, these are YOUR official instructions that always worked, YOU decided that this time the camera was an optional feature, and I decided as such that Sony is an optional vendor of devices for me, unless they're going to change their ways.

..also, ugh, why does xperifirm fail to unpack things on linux? doesn't matter if i use wine or mono, it just craps out with the mysterious and extremely helpful message that 'An error occurred during unpacking', like wow gee thanks that's one hell of a debug report, I bet if I sacrifice two goats and burn a bunch of incense and candles it'll magically work. ****ing windows 95 level bs here, all developers around mobile devices seem like they're completely new to the programming. sigh. Almost tempted to just go with that raspi + screen + mobile internet dongle + battery bank idea, then at least I'll have myself to blame when something breaks and I'm not stuck screaming at a wall of comfortably settled lawyers with their ass on "intellectual property" like the wheel and sliced bread :silly:
 

MartinX3

Recognized Contributor
Sep 14, 2014
5,716
2,826
Mars
martinx3.github.io
thank you for the explanation, however I personally believe the intellectual property defense is overkill, and I also feel like (almost) every OEM out there is actually managing to release a working opensource ROM or at least a dump with all the kernel-related source codes, as that is a hard requirement due to the Linux kernel being GPLv2 licensed.
So on one hand yes, Sony is definitely helping out the industry by paying for an opensource team to work exclusively on opensource roms, but on the other hand they're sneakily getting away with a very poor opensource experience and fierce DRM practices that technically have little right to exist at all on the Android ecosystem due to its GPL requirements..

Of course I do hope Sony continues their opensource team, but I really want to see them release more of their 'closed' ROM for public use, they're already requiring you to install a gross blob of binaries for the phone to work at ALL even with opensource ROMs, so I don't see any reason why they're so fierce on keeping their stuff to themselves, besides feeling like they could squeeze out a few extra pennies at the cost of the end user, and that disgusts me TBH.

Companies these days are grossly greedy, from aggressive datamining practices to vicious DRM, to dark design patterns to trick you into agreeing to stupid ****, and the whole reason I went with Sony is because they always had some promise to have open devices and it actually WORKED back with the xperia pro mk16i, Z, Z1 compact, and Z5 compact that I all still own, but then when I tried the XZ2 I was shocked to find how far it degraded its abilities, completely and entirely crippling the camera! And the only reason they get away with it is because they're still using that same old disclaimer that it's 'your own risk' .. NO dear Sony, it's not my own risk, these are YOUR official instructions that always worked, YOU decided that this time the camera was an optional feature, and I decided as such that Sony is an optional vendor of devices for me, unless they're going to change their ways.

..also, ugh, why does xperifirm fail to unpack things on linux? doesn't matter if i use wine or mono, it just craps out with the mysterious and extremely helpful message that 'An error occurred during unpacking', like wow gee thanks that's one hell of a debug report, I bet if I sacrifice two goats and burn a bunch of incense and candles it'll magically work. ****ing windows 95 level bs here, all developers around mobile devices seem like they're completely new to the programming. sigh. Almost tempted to just go with that raspi + screen + mobile internet dongle + battery bank idea, then at least I'll have myself to blame when something breaks and I'm not stuck screaming at a wall of comfortably settled lawyers with their ass on "intellectual property" like the wheel and sliced bread :silly:

I prefer open source too, but sadly the company or the hardware vendor doesn't want it, because the opposite companies may steal the know how and produce cheaper products (because no research costs) and the original company would maybe go bankrupt (means no more innovation).

as i said, the drm gets weakend with each new android version (and device).
The xperia 1 is the first xperia with camera 2 api RAW support.

The sony "open" team camera experience is okay too, they put all the things in they can achieve without firmware/hardware hacks the stock firmware contains (because it only needs to survive 2 years warranty).
The xz2 was the first device with the new qualcomm forced camera framework, so it needs much basic work to do. But will receive better results in the end.
The "open" team developments on the xperia 1 (uses the same camera framework) will go into the xz2(c)/xz3 too.

And I don't see custom rom disadvances. No bloat apps and a faster experience.
I bought the xz2 because sony is the only company paying an open source team (plus IP rating against water, a sdcard slot and the ultra durability).
At the other vendors it only gets worse and you don't get updated hardware drivers except the ones in the device stock firmware update which ends too.
And because the "open" team is so open, they are forced to use standards and no hacks like the closed source stock roms.
Everyone profits from it.

Btw you can buy a fairphone if you want open source components.
A raspi3 battery bank combo would be very bulky.
I want to put my phone into my jeans, not my backpack. :p


Ah, thje xperifirm error.
Sadly the software is closed source, the dev don't say why (maybe he is scared to loose his intellectual properties.).
He said GTFO and find a solution your self, he won't support linux and macos and it is only the mono fault that this error happens.
(Ignoring the fact that only he knows which source code functions he use to unpack the stuff).
Wine uses mono, it is open source and wine needs a .net framework to run .net applications.

Btw let me help you making a black mess, sacrificing goats and praise to Satan, our true lord and savior. <3
 
  • Like
Reactions: levone1

xarinatan

Member
Mar 8, 2018
33
11
I prefer open source too, but sadly the company or the hardware vendor doesn't want it, because the opposite companies may steal the know how and produce cheaper products (because no research costs) and the original company would maybe go bankrupt (means no more innovation).

as i said, the drm gets weakend with each new android version (and device).
The xperia 1 is the first xperia with camera 2 api RAW support.

The sony "open" team camera experience is okay too, they put all the things in they can achieve without firmware/hardware hacks the stock firmware contains (because it only needs to survive 2 years warranty).
The xz2 was the first device with the new qualcomm forced camera framework, so it needs much basic work to do. But will receive better results in the end.
The "open" team developments on the xperia 1 (uses the same camera framework) will go into the xz2(c)/xz3 too.

And I don't see custom rom disadvances. No bloat apps and a faster experience.
I bought the xz2 because sony is the only company paying an open source team (plus IP rating against water, a sdcard slot and the ultra durability).
At the other vendors it only gets worse and you don't get updated hardware drivers except the ones in the device stock firmware update which ends too.
And because the "open" team is so open, they are forced to use standards and no hacks like the closed source stock roms.
Everyone profits from it.

Btw you can buy a fairphone if you want open source components.
A raspi3 battery bank combo would be very bulky.
I want to put my phone into my jeans, not my backpack. :p


Ah, thje xperifirm error.
Sadly the software is closed source, the dev don't say why (maybe he is scared to loose his intellectual properties.).
He said GTFO and find a solution your self, he won't support linux and macos and it is only the mono fault that this error happens.
(Ignoring the fact that only he knows which source code functions he use to unpack the stuff).
Wine uses mono, it is open source and wine needs a .net framework to run .net applications.

Btw let me help you making a black mess, sacrificing goats and praise to Satan, our true lord and savior. <3

Every code contains hacks, there's no obligation not to do so in opensource projects, it just looks better if you don't ;) but with devices like this it's unavoidable, and that's fine, because at the end of the day it's about a working device and as much shared code as possible, they still have dependencies on closed source binaries that are injected with the OEM package, otherwise it just doesn't do anything. They've already said that they're not going to even support 960FPS mode, not even in the future, because it's infeasible to do so with the current resources the 'open' team has at their disposal, which upsets me, not because the open team isn't doing their job, but because the higher up managers and investors and decision makers are squeezing the money flow to make some extra dimes at the cost of the end user. I didn't buy a 600 euro device just to be told what I can and can't do with it, if I buy a windows PC and install Linux on it I expect everything to work, if not then I've chosen the wrong vendor.

Also yes, the fairphone 3 once it's released is very likely to be my next phone, however that'd be more expensive than I'm comfortable with, especially considering how little the hardware costs, I understand that R&D costs a ton, and that you have to stay alive as a company, but how is it possible that PCs get this down just fine and smartphones don't?- Actually I have the answer to that, it's quite simple, PCs, or Personal Computers, were a project by IBM that was from the start meant to be customizable by the end user and open for anyone else who wanted to develop such a thing, however the current type of 'smart' phone is nothing short of a degenerate ipod touch with a modem built in; it's an appliance, a throw-away shiny plaque of expensive materials that has grown far past its initial goals, causing people to be frustrated and angry with the fact that the things they build on for their day to day use are doomed to last mere years, or less if you didn't buy it right when it was released. Imagine if cars were like that and you'd have to buy a new car every few years just because they released a newer car that uses slightly different fuel and they don't plan on making the old type fuel anymore, everyone would resort to building their own contraptions to get to where they need to be or start building explodey distillation facilities to be able to re-use their 'old' car they bought last year. It's crazy that we're letting this sort of thing happen, General Purpose computers shouldn't be limited by an OEM's lack of vision and imagination, they should run software, any software, as computers do, otherwise you don't own a computer but a.. limited media device, an appliance, like a tivo.

As for Xperifirm, wine uses mono but introduces a different environment to e.g cope with slash vs backslash differences and default locations etc. Functionally Mono should be exactly the same as .NET, I've been a .NET developer myself and so far all my old applications always worked flawlessly on Mono without a single edit. I wouldn't be surprised if he's afraid of actions from Sony, otherwise he's probably mostly scared of people finding out his code is messy, as most developers are, especially when working with incredibly hacky crap like smartphones. I've opened it up with DnSpy, and it appears he's even attempted to obfuscate the code, but you can still read it as you can't really make .NET truly obfuscated as it's not a binary but interpreted bytecode that's run through a framework. Same as Java basically.

And as for the sacrificial rituals, I'm going to delay those until they're denying my warranty, then maybe leaving a beheaded goat and some candles on their doorstep could have some impact :eek:

edit: welp, still no working camera with xperifix, could've sworn that worked before, but not anymore I guess, oh well, at least it boots now, the camera may be either the equivalent of a 1999 feature phone potato or completely broken, but it boots. Now I'm just going to wait for their response to the warranty request, I should still have warranty, if not I'm going to sell the device at a reduced price, it's costed me FAR more hours than its worth to me, every device I own has a better opensource experience than this one, and all of that because I immediately choked on their abominable set of spyware system apps like Facebook. NEVER buying Sony again unless some miracle happens on their end.
 
Last edited:
  • Like
Reactions: levone1

MartinX3

Recognized Contributor
Sep 14, 2014
5,716
2,826
Mars
martinx3.github.io
Every code contains hacks, there's no obligation not to do so in opensource projects, it just looks better if you don't ;) but with devices like this it's unavoidable, and that's fine, because at the end of the day it's about a working device and as much shared code as possible, they still have dependencies on closed source binaries that are injected with the OEM package, otherwise it just doesn't do anything. They've already said that they're not going to even support 960FPS mode, not even in the future, because it's infeasible to do so with the current resources the 'open' team has at their disposal, which upsets me, not because the open team isn't doing their job, but because the higher up managers and investors and decision makers are squeezing the money flow to make some extra dimes at the cost of the end user. I didn't buy a 600 euro device just to be told what I can and can't do with it, if I buy a windows PC and install Linux on it I expect everything to work, if not then I've chosen the wrong vendor.

Also yes, the fairphone 3 once it's released is very likely to be my next phone, however that'd be more expensive than I'm comfortable with, especially considering how little the hardware costs, I understand that R&D costs a ton, and that you have to stay alive as a company, but how is it possible that PCs get this down just fine and smartphones don't?- Actually I have the answer to that, it's quite simple, PCs, or Personal Computers, were a project by IBM that was from the start meant to be customizable by the end user and open for anyone else who wanted to develop such a thing, however the current type of 'smart' phone is nothing short of a degenerate ipod touch with a modem built in; it's an appliance, a throw-away shiny plaque of expensive materials that has grown far past its initial goals, causing people to be frustrated and angry with the fact that the things they build on for their day to day use are doomed to last mere years, or less if you didn't buy it right when it was released. Imagine if cars were like that and you'd have to buy a new car every few years just because they released a newer car that uses slightly different fuel and they don't plan on making the old type fuel anymore, everyone would resort to building their own contraptions to get to where they need to be or start building explodey distillation facilities to be able to re-use their 'old' car they bought last year. It's crazy that we're letting this sort of thing happen, General Purpose computers shouldn't be limited by an OEM's lack of vision and imagination, they should run software, any software, as computers do, otherwise you don't own a computer but a.. limited media device, an appliance, like a tivo.

As for Xperifirm, wine uses mono but introduces a different environment to e.g cope with slash vs backslash differences and default locations etc. Functionally Mono should be exactly the same as .NET, I've been a .NET developer myself and so far all my old applications always worked flawlessly on Mono without a single edit. I wouldn't be surprised if he's afraid of actions from Sony, otherwise he's probably mostly scared of people finding out his code is messy, as most developers are, especially when working with incredibly hacky crap like smartphones. I've opened it up with DnSpy, and it appears he's even attempted to obfuscate the code, but you can still read it as you can't really make .NET truly obfuscated as it's not a binary but interpreted bytecode that's run through a framework. Same as Java basically.

And as for the sacrificial rituals, I'm going to delay those until they're denying my warranty, then maybe leaving a beheaded goat and some candles on their doorstep could have some impact :eek:

edit: welp, still no working camera with xperifix, could've sworn that worked before, but not anymore I guess, oh well, at least it boots now, the camera may be either the equivalent of a 1999 feature phone potato or completely broken, but it boots. Now I'm just going to wait for their response to the warranty request, I should still have warranty, if not I'm going to sell the device at a reduced price, it's costed me FAR more hours than its worth to me, every device I own has a better opensource experience than this one, and all of that because I immediately choked on their abominable set of spyware system apps like Facebook. NEVER buying Sony again unless some miracle happens on their end.

if unlocked in oreo, you need to use xperifix in oreo plus magisk permissive.zip i bundled in my TWRP.
If unlocked in a newer PIE, just use PIE.
If upgrading to PIE from a xperifixed Oreo, please use my bundled camerafix.zip. :)
 

xarinatan

Member
Mar 8, 2018
33
11
if unlocked in oreo, you need to use xperifix in oreo plus magisk permissive.zip i bundled in my TWRP.
If unlocked in a newer PIE, just use PIE.
If upgrading to PIE from a xperifixed Oreo, please use my bundled camerafix.zip. :)

I had it working before with xperifix in the default rom, but I went to omni after that because I realized how much I hated the default rom, but then I couldn't get that to work with gapps because I was installing TWRP the wrong way and therefore couldn't use TWRP, and when I did manage to get it working with TWRP I think I didn't manage to get the camera fully working with TWRP, so I installed oreo to try that fix to get the camera working fully again, but realized I couldn't find a working TWRP for that ROM so I had no idea how to deploy xperifix to that, decided to install pie again, installed xperifix again, and that's where we're at now, with the camera not working.
Also appears TWRP stopped working again after I installed Xperifix? TWRP isn't booting and if I try to adb shell into it it says
Code:
[[email protected] alex]# adb shell
* daemon not running; starting now at tcp:5037
* daemon started successfully
CANNOT LINK EXECUTABLE "/sbin/sh": library "drmfix.so" not found
linker: CANNOT LINK EXECUTABLE "/sbin/sh": library "drmfix.so" not found
[[email protected] alex]#
tbh I think this phone is just cursed as long as it's in my possession, no amount of beheaded goats and candle circles is going to fix this, it needs to go directly to Sat- I mean Sony ;) or someone else who's karma around this is still clear :p
I'd keep it around until the software is better but I just need a working phone, and if this thing can fund me halfway to a proper phone then I won't even need this thing in the future, so I think it's better to sell either way. maybe someone else has more luck with it, the hardware isn't bad, just everything underneath makes me scream right now, though that's not uncommon for smartphones in general because they're pieces of **** :silly:

I have a boring nightshift or two coming up though so I might just throw some more time at it to at least get it to a somewhat working state with Omni on it. Thanks for the help.
 

MartinX3

Recognized Contributor
Sep 14, 2014
5,716
2,826
Mars
martinx3.github.io
I had it working before with xperifix in the default rom, but I went to omni after that because I realized how much I hated the default rom, but then I couldn't get that to work with gapps because I was installing TWRP the wrong way and therefore couldn't use TWRP, and when I did manage to get it working with TWRP I think I didn't manage to get the camera fully working with TWRP, so I installed oreo to try that fix to get the camera working fully again, but realized I couldn't find a working TWRP for that ROM so I had no idea how to deploy xperifix to that, decided to install pie again, installed xperifix again, and that's where we're at now, with the camera not working.
Also appears TWRP stopped working again after I installed Xperifix? TWRP isn't booting and if I try to adb shell into it it says
Code:
[[email protected] alex]# adb shell
* daemon not running; starting now at tcp:5037
* daemon started successfully
CANNOT LINK EXECUTABLE "/sbin/sh": library "drmfix.so" not found
linker: CANNOT LINK EXECUTABLE "/sbin/sh": library "drmfix.so" not found
[[email protected] alex]#
tbh I think this phone is just cursed as long as it's in my possession, no amount of beheaded goats and candle circles is going to fix this, it needs to go directly to Sat- I mean Sony ;) or someone else who's karma around this is still clear :p
I'd keep it around until the software is better but I just need a working phone, and if this thing can fund me halfway to a proper phone then I won't even need this thing in the future, so I think it's better to sell either way. maybe someone else has more luck with it, the hardware isn't bad, just everything underneath makes me scream right now, though that's not uncommon for smartphones in general because they're pieces of **** :silly:

I have a boring nightshift or two coming up though so I might just throw some more time at it to at least get it to a somewhat working state with Omni on it. Thanks for the help.

Pllllllz don't use any xperifix/camerafix on the custom roms. :)

And yes, there is a TWRP for STOCK ROMs and a TWRP for SODP ROMs, because there are differences (in DTBO).

OREO TWRP's are on android file host in the ANDROID_8 root folder.

Xperifix is at the moment not PIE compatible as written in the latest xperifix news post about XZ2 compatibility. :)

In OREO you just give xperifix the magisk 18.1 zip file and it does everything for you. (Or install it manual as A/B, VENDOR).
Don't give it a twrp.img.

Just carefully follow the instructions and scarify goats to break the curse. :silly:

I can confirm that the stock firmware & camera works (I used it with the existenze rom for xz2 and xz2c) and since the end of april I use OmniROM (without problems).
Of course the camera is under constructions and I am excited if the OEMv10 may bring a camera update with the current development snapshot of the closed source camera drivers.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    There always people complaining, regardless what you do.

    I use only phones where I can get custom rom updates over a long time period.
    I am very happy about my first time with a xperia smartphone and the possibilities.
    For other vendors you are forced to use the stock firmware to create a custom rom.
    Here you can choose between the stock firmware or the SODP AOSP firmware developed from scratch without hacks and focused on stability and free from bloatware.
    Here you have the possibility to help as a volunteer and take part in which direction the SODP AOSP firmware gets developed.

    About the stock DRM, yes, I hate it, too.
    But Sony does move away from it.
    They did weak it with Oreo and further with PIE (more features without DRM allowed get used) and the Xperia 1 is now the beginning of xperia smartphones with camera RAW support on stock, not only SODP AOSP based ROMs.
    So it goes in the right direction and is very promising for the future.
    Maybe on xperias starting with Q/R the DRM will disappear.
    2
    There always people complaining, regardless what you do.

    I use only phones where I can get custom rom updates over a long time period.
    I am very happy about my first time with a xperia smartphone and the possibilities.
    For other vendors you are forced to use the stock firmware to create a custom rom.
    Here you can choose between the stock firmware or the SODP AOSP firmware developed from scratch without hacks and focused on stability and free from bloatware.
    Here you have the possibility to help as a volunteer and take part in which direction the SODP AOSP firmware gets developed.

    About the stock DRM, yes, I hate it, too.
    But Sony does move away from it.
    They did weak it with Oreo and further with PIE (more features without DRM allowed get used) and the Xperia 1 is now the beginning of xperia smartphones with camera RAW support on stock, not only SODP AOSP based ROMs.
    So it goes in the right direction and is very promising for the future.
    Maybe on xperias starting with Q/R the DRM will disappear.

    I am very glad to hear they're slowly moving away from it, it would make their 'open' device program much more open :)

    But yes, people will always complain, it is how progress happens, if there's no complaints there's nothing to improve ;) it's not necessarily a bad sign! it means people are using your device!

    I do agree the open device program with its dedicated developers and community input is pretty unique and amazing to have, which is exactly why I've stayed with them for so long, but I simply didn't have a choice this time around, I needed a working phone with my own software on it, and I just couldn't get it working the way I did with all my other phones. It might even be that the phone itself is broken, but I can't exactly make use of the warranty anymore, which also bothers me because OnePlus seems to be willing to replace your device just fine.
    All in all I was very disappointed and angry this time around with the experience I got, and I will stand by my words as long as they continue this behavior. So I do hope they will continue removing their hardware DRM ;)

    Preach, brother. I have been making this very argument for years, starting when HTC on Verizon started making life impossible for those who wanted root access. My attitude has always been, "it's MY damn phone; I want to do with it what I want." Although I don't tend to root every handset anymore (confession, I usually have multiple handsets, and one of them is almost always rooted), your position is precisely mine, and while I fancy the notion of a rooted X2C Compact, there's no way I want to deal with the BS hurdles Sony has thrown up to this supposedly "open" device.
    There are definitely even worse smartphone OEMs to pick than Sony, Apple for instance haha, and perhaps Samsung and HTC and Huawei (who seems to have removed the unlock ability from their website entirely), and I will *never* buy devices from them as long as they think they can own the device AFTER you bought it.
    It's not even that I care about root access, I usually have that disabled entirely for safety reasons, it's just that I don't trust the default software on any device, one of the first things I do when I buy a new computer is wipe it, and Lenovo's Superfish debacle and HP's exploitable system tools/drivers have firmly confirmed to me that this is the right thing to do (plus I run Linux/Arch/etc, couldn't care less about ConsoleOS 10).
    Not to mention I would've never bought the Oneplus if I couldn't do that, because I know exactly how much China loves to put backdoors in things, hell even the USA does that (remember PATRIOT anyone? or what about the whole shadowbrokers dumb with exploits that the NSA kept to themselves for years? Entire reason WannaCry existed!), so while some people may call me paranoid, I think it's my right to be able to change the software on the computers that I buy, whether they fit in my pocket or not :)
    Edit: and of course the fact that your device stops working as soon as the OEM stops supporting it of course, I think it's beyond strange that governments aren't calling a halt to that, the amount of electronics waste is massive, and this kind of scammy 'oh guess your device is useless now and you'll have to buy a new one<3' behavior when opensource roms could easily keep your device running for years after makes me want to run political campaigns.
    2
    Hi everyone, not sure if this is the right place, but I have a question...
    What if I want to use TWRP purely for backup functionality on XZ2 compact? No intention to install any custom roms yet.. no need
    Is it possible to simply have TWRP only for backups? I do not even plan to root it.. is something like that possible without breaking something? Like DRM for camera etc?
    Thanks.
    You need to unlock the phone and break the Sony DRM.
    Or you can't flash stuff on the phone
    2
    That was the official pie rom :p and like I said it worked before! I guess with the amount of ROM switching some other files got lost somewhere.
    As for Omni, it seems like it doesn't like my NFC chip and occasionally seems to crash with opengapps (stock) installed.. I've been trying to get TWRP to work with my own compiled AOSP ROM, but I might just try put Stock on it again to the best of my abilities with your above instructions tonight, if not I'll probably invest in something like a google pixel 3 which also has a snapdragon 845, would be nice to compare the opensource experience with that one :p at least the build instructions seem pretty straightforward https://source.android.com/setup/build/building.html or perhaps a oneplus device or something non-waterproof with a waterproof case.. or a raspi 4 with screen/bat/4g and a bunch of ducttape until it's waterproof :D not like there's anything that's not made of glue these days anyway, except maybe the fairphones :cyclops:

    thanks for those instructions though! I'll try them out tonight. and thanks for not turning your back on me because of my frustrated responses, I know I'm not an easy customer, but you gotta admit the smartphone world is more voodoo than logic with the amount of bugs and workarounds and bugs in workarounds and so forth :p

    you could also just execute my build environment on github to build the stuff :p

    No problem, you're welcome :D
    Customer care is the hardest care. :silly:
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone