yashsingh1/xdaforums huggingface dataset:
[Sony Xperia XZ2 Questions & Answers] ionSeven:
I'm thinking about sitting and learning everything I need to know about compiling for this phone, i.e. TWRP and Elemental X kernel, coming from the Nexus 5X I found that to be the best kernel on that device and would love it on the XZ2.

If I do decide and have the time to learn, I will...this phone has so much potential, but as usual, the manufacturer has limited it.

I shall open a new thread if and when I get started.
[Sony Xperia XZ2 Questions & Answers] mirhl:
I don't see why they shouldn't.

Anyway, long story short, with SELinux google restricted a lot /proc and /sys access in the last android releases (I don't see why QCA guys act like this was some novelty)

You can still retrieve the same information via BatteyManager class, or via command dumpsys (battery or batteryproperties)

...

As for compiling stuff for this phone, one should just check XZ1/XZp forums for basically a copycat of whatever will be needed to be done here.
[Sony Xperia XZ2 Questions & Answers] serajr:
You're damn right bro! :good:

https://xdaforums.com/showpost.php?p=76834316&postcount=13
[Sony Xperia XZ2 Questions & Answers] mirhl:
So.. I ask you here, rather than soiling pure dev exchanges

Is it just about using stock binaries, or does it make the step ahead of assuring same-quality too? (is the distinction even a thing in modern phones?)

Also, are you by any means planning to release the patcher as open source? Because it's a massive downer to see skilled people having to reinvent the wheel over and over again
[Sony Xperia XZ2 Questions & Answers] serajr:
I am, patcher itself is based on shell script commands! I didn't create new libs, so its creators are responsible for opening the source code or not!

I just created an easy installation method of the already known drmfix libs, and the secd binary that I patched is a copy of the stock one!

Do you have an unlocked XZ2? I still need confirmation of the last step (new selinux rule injection)!

Edit: Keep in mind... I still don't know if the old patching method will work or not in the 2018 devices. I'm just pushing the necessary files to the partition (/vendor), editing the calling rc files (at install time), and injecting new rule into the selinux, so that everything can work (or not).
[Sony Xperia XZ2 Questions & Answers] niaboc79:
Did you find someone to test?

Envoyé de mon H8266 en utilisant Tapatalk
[Sony Xperia XZ2 Questions & Answers] serajr:
Yes, only one mate is trying to help in this, but it seems like he doesn't have enough spare time to help out more, which is completely understandable (that's why things are lasting longer than we expected... or not... who knows?)! Have you already unlocked your xz2?

I won't unlock mine till I can backup its TA partition, and I need to say, maybe I'll never do it (I'm very pleased with my xz2 still locked, I didn't really miss root in it). I still own my old 'n' good unlocked/rooted x performance to play with!
[Sony Xperia XZ2 Questions & Answers] niaboc79:
I won't unlock my phone neither. I'm still waiting a working drm patch to do it.

As the camera is broken with unlocked bootloader I can't do it.

Envoyé de mon H8266 en utilisant Tapatalk
[Sony Xperia XZ2 Questions & Answers] Pandemic:
+1

Here also bro, i am not unlock my bl till we all know we can finally do it if we have a solution :)
[Sony Xperia XZ2 Questions & Answers] EternalSwift:
My mistake it was a late night.
[Sony Xperia XZ2 Questions & Answers] mirhl:
Not sure which part of Z-Z5 you missed.

Besides, that's not doing anything different from aforementioned secd patching.
[Sony Xperia XZ2 Questions & Answers] MartinX3:
Can someone test this twrp build for me?

https://xdaforums.com/xperia-xz2/development/recovery-twrp-3-2-2-0-touch-recovery-t3821597
[Sony Xperia XZ2 Questions & Answers] jbm76:
If you unlock the bootloader can it be re-locked?

After some googling it seems it can't be re-locked
[Sony Xperia XZ2 Questions & Answers] MartinX3:
It can't, until you find a hack to backup your DRM keys in your ta partition before unlocking.
[Sony Xperia XZ2 Questions & Answers] mirhl:
https://developer.sony.com/develop/open-devices/latest-updates

AOSP 4.9 binaries are out, finally.
[Sony Xperia XZ2 Questions & Answers] MartinX3:
Yes, but unfortunately we still can't compile the aosp image for the XZ2.
[Sony Xperia XZ1 Compact Questions & Answers] belzedj:
Any solution for simple root for our phone?
[Sony Xperia XZ1 Compact Questions & Answers] Didgesteve:
There is a way. sToRm//'s Sony Xperia XZ Premium TWRP + KERNEL + ROOT + DRM fix/restore is an app that works on our XZ1 compacts. But read the thread carefully before you decide if you want to continue. The app works, I have used it on my phone and everything works perfect, with root. But to get to the point where the app works perfectly is quite difficult. Reading the thread, lots of people have unlocked their phone, broken their camera and now can't get the fix to work.

Personally I wouldn't recomend it.

Edit: Take note that unlocking your phone (required to root) is one way and can NEVER BE UNDONE. You break your phone for forever, you then have to hope that the developer will support you through further firmware upgrades.
[Sony Xperia XZ1 Compact Questions & Answers] belzedj:
Kingroot or any apk?
[Sony Xperia XZ1 Compact Questions & Answers] Didgesteve:
Kingroot don't do the XZ series and if they did I still wouldn't recomend it. Some Kingroot users have reported that their IMEI number has been cloned.

No apks :(

No quick easy root
[Sony Xperia XZ1 Compact Questions & Answers] knutlegrand:
What about xperifix ? see also
[Sony Xperia XZ1 Compact Questions & Answers] knutlegrand:
Oups, next time I'll put my brain "on" before posting :)
[Sony Xperia XZ1 Compact Questions & Answers] zisforzorro:
Has anyone tried xperifix 2.2 / 2.3? Supposedly some XZ1 compact updates were made.

You mentioned "to the point where the app works perfectly is quite difficult", which issues did you have?
[Sony Xperia XZ1 Compact Questions & Answers] Didgesteve:
Xperiafix 2.2 works and I used it to root my phone. But I'm now on out of date firmware (.75) as OTA stops as soon as you are rooted.

Also, I am sticking with .75 for the moment as it's the last build that Xposed works with and I have some Xposed modules that I am fond of.

The issues I had with the software were to do with getting the right drivers installed, particularly the USB drivers needed when you plug the phone in with TWRP running. Windows chooses the wrong drivers by default and you have to manually assign them or it’ll never work.

The software itself works, but ignore the progress meter built in. There are lots of posts on the Xperiafix thread of how to, so I’d say just read up first and you should be fine.

Xperiafix 2.3 is now the only option if you want up to date firmware on your phone, but it’s €20 and several users have had problems getting it to work, I’m sure the Dev will fix it soon.

So just be aware that if you buy into Xperiafix, you are dependent on the Dev for the rest of the life of your phone and forced to pay whatever he charges for the Xperiafix program
[Sony Xperia XZ1 Compact Questions & Answers] Raz0Rfail:
I tried the 2.3 Update (https://xdaforums.com/xperia-xz1-compact/help/xperifix-47-1-12-145-aka-april-patch-t3777185 last entry).

I had some trouble with it, because I needed several tries and everytime I had to force close XperiFix.exe, adb.exe and fastboot.exe.

The Problem for me was, the downloaded Temp TWRP for XZ1C doesn't worked with the XperiFIX process.

If I used the downloaded temp TWRP it didn't happened nothing inside twrp.

So I had the installer from XperiFix 2.2 and extracted the Temp TWRP which I knew it would work.

I tried different ways to download the extracted TWRP into the XperiFIX.exe 2.3.

At first I got the MiniWeb HTTP Server, copied my TWRP Files into it and started the miniweb Server.

Then I Created the correct URL for me and I could download my twrp into XperiFix after I edited the devsettings.xpf file.

With my modified TWRP the installation of XperiFIX inside TWRP worked, and now I have the new magisk and XperiFIX working.

I uploaded my Files for you to get XperiFix working on XZ1C (G8441) .145 firmware.

Download it:

https://www115.zippyshare.com/v/Guov8WiU/file.html

Extract it into C:\XperIFix, Overwrite DATA/devsettings.xpf.

Start "C:\XperiFIX\miniweb\miniweb.exe"

Accept the Firewall Rule.

Start XperiFix.exe

Shutdown your Phone.

Plug in your PC and hold Volume UP to get into bootloader.

Set the Hook in XperIFIX and click on "Fix my Device".

And after 2 Minutes you have XperiFIX and magisk 16.3 working on your XZ1C (G8441) .145 FW.

At last close XperiFIx and miniweb.exe

Best regards.

Raz0Rfail
[Sony Xperia XZ1 Compact Questions & Answers] ArdW:
I tried Xperifix 2.4 and still have .NET error. I contacted the developer but so far no solution.
[Sony Xperia XZ1 Compact Questions & Answers] TheDelta:
To root or not

Hey man,

I lost my phone last week and finally bought XZ1c. XDA is not allowed at work and i am having trouble doing research and going through the threads to understand what all to do. Since I am not getting time to do research but i want to be able to start using the phone for now, do you think it is easy/worth it to root? from what you wrote it seems difficult and not a good idea for now but our goals are same because i want it solely to be able to run xposed. I had been using moto phones for the last 7 years now, so i know how bootloaders/rooting/flashing etc works. But i am completely new to the sony world so i was wondering on what is the downside (or what i lose) of me trying to go through a lot of trouble to get xposed working, and how much time will it take me overall to get there.

Any help is appreciated, I know it sounds like a lazy man asking for a hand holding, but apologize in advance!!

---------- Post added at 02:44 PM ---------- Previous post was at 02:41 PM ----------

I forgot to mention that I am already going to flash the .145 UK firmware today to get fingerprint on my US phone (to be used in India). I got a link from reddit where that guy has done a lot of times so i am going to trust him on it and follow his steps.
[Sony Xperia XZ1 Compact Questions & Answers] Didgesteve:
Not much has changed since I first wrote on this thread to be honest.

It depends on what you do with your phone to say if you need to root it or not. In the past you needed to root it to kill the battery hungry apps, but that's long gone these days. The other reason for rooting was customising your phone, but you can do that without root. So to be honest, if I were to come down on one side or the other I'd say don't bother. You also need to check that you can unlock your bootloader, as some phones bought from a provider are locked and this can't be circumnavigated. (type *#*#7378423#*#* in your phone to get the service menu and then service info/configuration)

Sony have given developers the finger with this bootloader, unlocking breaks the phone, you lose your TA keys, no way to back up and lots of functions stop working, like the, err, camera.

The good news is that there's a DRM fix out there, one that will work with the latest .145. There's no loss of quality on the camera, everything is as stock.

The bad news is that the developer sToRm// has put his DRM fix app to be paid for. This app works and as long as you have the right drivers is relatively easy.

There are a couple of people who have posted a free DRM fix for XZ Premium, but as yet, there's no one has posted a free fix that works with the .145 firmware for the XZ1 compact, although there might be some tips on the previous page, you'll still need a copy of Xperiafix

There are a couple of roms that have the DRM fix built in that are good daily drivers. Check out ResurrectionRemixOreo or LineageOS 15.1 UNOFFICIAL.
[Sony Xperia XZ1 Compact Questions & Answers] TheDelta:
To root or not to root

Yeah, for me rooting is so that i can use xposed, i have a couple of modules that i need almost daily. (used to :'( )

Thanks for the info, i think this is what i get -

1. I can just stay stock (and flash the UK .145 firmware and get fingerprint)

2. I can use xperifix, pay that guy and get root and xposed along with a good drm fix. Down side is that i will not have any OTA or anything like that and will have to stay on .145 itself as long as i want to keep this option.

3. I can go all the way custom with DRM fix and not use stock sony at all and directly start using custom roms where everything will work (i am assuming camera and fingerprint will work as well there).

Well, i've used RR before so i would very much like the option 3. I have always felt restricted in stock in any phone i've used, i have been so used to custom roms i like it. But since the phone is new, i do want to see what sony offers. So i think i am good with no ota .145 paid option as i will only have to pay it one time now. And then i am good for at least 3-4 months (post which i will mostly get bored and move to a custom rom). Thoughts? :cool:

---------- Post added at 04:52 AM ---------- Previous post was at 04:48 AM ----------

I forgot to mention yesterday, I had checked on this phone. Boot loader unlock says allowed/yes. :highfive:
[Sony Xperia XZ1 Compact Questions & Answers] Didgesteve:
Xposed won't work with .145, it's a know issue with no workaround as yet.

.75 is the last firmware that Xposed works with.

Edit: sToRm// says that paying for Xperiafix will mean that it will stay up to date with any future firmware releases, so you will be able to go beyond .145, but not until the problems with Xposed are fixed
[Sony Xperia XZ1 Compact Questions & Answers] Didgesteve:
There is a partition on your phone called the TA partition with a set of encrypted keys on it that are unique to your phone. So far no one has worked out how to copy the partition and backup the keys. The keys engage with the DRM software and enable higher function apps, like the camera, X-Reality, etc etc.

Unlocking your phone deletes that partiton, you can't get your keys back, gone forever.

Xperiafix engages with the DRM software and fools it into thinking keys are present, all higher funtion apps work as per usual.

Lots of people who don't understand suggest a loss in quality of the camera, but it doesn't work like that. DRM is broken or fixed, the camera is broken or fixed. Simple.

Edit: Magisk 16.4 is working and that has many modules you can add that are similar to Xposed modules. Just don't try adding Xposed until there is a new build released.
[Sony Xperia XZ1 Compact Questions & Answers] TheDelta:
That actually makes sense now. Reminds me of the time when my moto razr was not allowed to unlock bootloader so a hijack was invented and it did so much just like a normal unlock!

yeah, i got bored of the fingerprint scanner in like <24 hours. Guess it is not for me :silly:

I feel like i like I might get bored of sony pretty soon and just get RR. although would you know if people have found a way to keep the 3d creator or sony camera app etc on custom roms? or what exactly do people use as camera app? I feel like other app should still do pretty much same things for taking the photo as hardware is same? Anyhow i will finally get some time over weekend to research all that before taking the plunge. So far only the 3d creator impressed me, camera settings seem pretty same as other phones so probably won't loose much by going custom?

I did not know magisk had modules, that's new. Will research on that over weekend, who knows maybe it will get me what i need :fingers-crossed:

BTW, sorry i am asking more questions, but do you know if i can install 2nd rom? I mean with recovery i should be able to dual boot right? The idea would be to keep primary stock with rooted .145 without xposed to go back to whenever i want to do the 3d stuff and use custom rom as daily driver. Do you know if that is still possible? I do have a spare 64 GB card from my gopro that i can use here to get more space for other stuff.
[Sony Xperia XZ1 Compact Questions & Answers] Didgesteve:
Apparently Open Camera has lots of good reviews as an alternative to the stock.

Speaking from personal experience, the 'superior auto' isn't all that good, sort of ok if you're in a hurry. But most of the time is doesn't shoot HDR and for some reason a lot of the pictures are 'soft'. So manual is the way to go, HDR on and try and drop the ISO down to 200 and the shutter speed down to 1/15, which is pretty slow, so you might need to rest it on something. Sounds daft saying a mobile phone camera works best if you tripod it, but there we are. Turn of the object tracking and shoot in native 19Mp, edit it to letterbox later if you want that shaped picture, but at least shoot one to one pixel ratio.

No 2nd rom boot option for Oreo TWRP as far as I'm aware. I'm not even sure you can do a successful restore from TWRP, maybe the data partition, but you can't restore a build, there's something to do with encryption that gets in the way. I'm not an expert, maybe ask on the TWRP thread. So TWRP is really just a way of flashing stuff, I don't think you can use it for backup/restore, but I'd love someone to correct me on that.
[Sony Xperia XZ1 Compact Questions & Answers] TheDelta:
Finally weekend is here!!

I agree on the camera thing you are saying although I don't get what shaped photos mean. I haven't used letter box.

You brought up backup restore, you thought I am talking about switching ROMs using backup restore ?? Yeah I don't think I will) go through that much pain if I cannot just dual boot.

I am just thinking j will read up through the threads this weekend and put lineage or rrr based on what I find out :cool:
[Sony Xperia XZ1 Compact Questions & Answers] TheDelta:
.75

I think I will stay on stock to see how much I enjoy the 960 fpsmode. Do you think I can flash .75 over

145 ? Any risks maybe?? Using xperifirm I can if I have files right?? Any chance you have the .75 version that you can upload or gdrive for me¿
[Sony Xperia XZ1 Compact Questions & Answers] belzedj:
Any news for simple root?
[Sony Xperia XZ1 Compact Questions & Answers] InteRadek:
@janjan created a working root with DRM fix. It works like a charm and [MENTION=490110]janjan[/MENTION] keeps it up-to-date

https://xdaforums.com/xperia-xz1-co...nel-sony-xz1-compact-16-january-2018-t3736068

@N1ghtr08d created a detailed installation instruction

https://xdaforums.com/xperia-xz1/how-to/guide-how-to-persistant-root-xperia-xz1-t3718375
[Planet Gemini PDA Accessories] jbej:
Very curious to see if pebble (or maybe rebble) will be able to run in sailfish, either with the android layer or this: https://github.com/abranson/rockpool
[BLISS ROMS Discussion] sbaloch:
Hello all,

I love Bliss OS. Unfortunately, I can't get Android-x86 to boot from my X64 machine. I've researched and tried a number of options but nothing seems to work. I installed it on my single NTFS drive in my laptop busing the Androidx86-Installv26.0003 executable. All seem to go fine. However, when I select the Android entry in UEFI, I get a permanent and repeating "Detecting Android ......" output. Here is some info which may help with troubleshooting.

1. Android in installed on my C:\ drive in a folder called "AndroidOS". The size of the folder is 60.7 GB and holds the following files ...

android.boot - 16 B

data.img - 60.1 GB

initrd.img - 1.3 MB

kernel - 6.4 MB

ramdisk.img - 1.7 MB

system.sfs - 690 MB

2. The EFI entry for AndroidOS in my system partition is ....

Description:Android-OS

GPT partition GUID:{0001208F-8310-EE75-9BD4-D73B1E410200}

Partition number:2

Partition starting sector:999804928

Partition ending sector:1000214527

File path:\EFI\boot\grubx64.efi

3. The cfg file in EFI has the syntax shown in my picture attachment.

I know I'm missing something small or an error in syntax, please review and offer any suggestions you might have.

Thank you in advance
[BLISS ROMS Discussion] electrikjesus:
try to make sure your bios has secure boot and bitlocker disabled. if so, try a build using a different kernel
[BLISS ROMS Discussion] hunnia41:
I have the same problem.
[BLISS ROMS Discussion] ElfinJNoty:
[MENTION=928479]electrikjesus[/MENTION] is he missing androidboot.hardware=android_x86_64

??
[BLISS ROMS Discussion] electrikjesus:
Yes he is missing that
[BLISS ROMS Discussion] Hardexz:
i same problem

how to fix this problem

please help me,,,
[Mogul, XV6800 ROM Development] azclown:
Peeps - There in an Official Kitchen.... It has been released by the FINE folks over at

http://www.ppckitchen.org/

Please check it out....

Thx to all those responsible for this release.... You are very exceptionally talented people to whom we owe a debt a gratitude too.....
[Mogul, XV6800 ROM Development] silentbenton:
What are the advantages/disadvantages of using this kitchen over DCDs 3.0.1?
[Mogul, XV6800 ROM Development] blakksmiff:
Isnt this an Apache kitchen?
[Mogul, XV6800 ROM Development] 1999TL:
Looks like the apache kitchen. Which reminds me how slow that PPC used to be. Then last night, I was playing around with the Touch. No keyboard was horrible, but it was so much faster. Didn't suffer from memory problems. If only the Mogul had 128 MB ram...
[Mogul, XV6800 ROM Development] wondabwoy:
Titan compatible or NOT?

Ok, have you used this to build a rom for the titan? it only builds for apache, one good thing though, I'm able to get updated and new oem's which I'm able to use in DCD's kitchen.
[Mogul, XV6800 ROM Development] jjlwork:
I have been following this it is supposed to eventually be a universal kitchen for multipple devices, checking it out tonight perhaps they have included the titan now.
[Mogul, XV6800 ROM Development] jjlwork:
Yup, looking at their main page they are thanking No2Chem for the titan kitchen, looking to see if I can find it now, perhaps DCD will be releasing his a compatible version of his kitchen, he and No2Chem seem pretty tight.

EDIT: Not quite ready for Titan yet here is a chat transcript from their chatroom>

<jjlwork> I noticed you are thanking no2chem for the titan kitchen, but i do not see anywhere to d/l throguh the updater, am I missing something?

<naigaman> jjlwork we are working on releasing that soon

So stay tuned!
[Mogul, XV6800 ROM Development] silentbenton:
It looks like a pretty intuitive kitchen, I hope we can get it released for the Titan, but until then DCD all the way.
[Mogul, XV6800 ROM Development] Jaquers:
If you read the full article HERE, You can see the dropdown box for what device your cooking for - I'm assuming there's a Titan device available, as dcd is listed in the credits aswell. In anycase I can't wait to try it tonight when I get home!
[Mogul, XV6800 ROM Development] jjlwork:
Don't waste your time, titan is not an option yet.
[Mogul, XV6800 ROM Development] azclown:
Damm, finally got back to my PC after the updater finished and alas....... IT IS NOT FOR THE TITAN.... When I read the read more section, down at the bottom I saw it say No2Chem for Titan Kitchen and bout pissed myself... SORRY to everyone who got too excited by my overzelous post........
[Mogul, XV6800 ROM Development] Jaquers:
Damn, that sucks. I went and got all excited... Really the only functionality I want from that is the ability to change the boot & splash screens. :(
[Mogul, XV6800 ROM Development] x10dude:
Just recently coming from the 6700/Apache camp I can tell you how much I MISS the Apache kitchen. It was nothing short of a ROM addicts dream...

I got kind of spoiled using the kitchen and the Apache. Yeah, the 6700 was a somewhat limited device compared to the 6800 but it's the Kitchen that really made it compelling and seriously, probably kept it going for so long (and still going...)

Hopefully the Mogul development will eventually get there, but for now you can always dream....
[Mogul, XV6800 ROM Development] Jaquers:
i actually just spoke with gguruUSA and he said that the noChem's titan kitchen has been implemented, but the only delay is with the release of the new official rom, so they're working to make everything compatible. So, hopefully soon we'll be cooking roms apache style.
[Mogul, XV6800 ROM Development] juneau_shublik:
I don't know if anyone cares, but it seems there is now a version for the Titan.