Quick Root for Sony Xz1 compact - Sony Xperia XZ1 Compact Questions & Answers

Any solution for simple root for our phone?

belzedj said:
Any solution for simple root for our phone?
Click to expand...
Click to collapse
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.

Kingroot or any apk?

belzedj said:
Kingroot or any apk?
Click to expand...
Click to collapse
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

What about xperifix ? see also

Oups, next time I'll put my brain "on" before posting

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?

zisforzorro said:
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?
Click to expand...
Click to collapse
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

zisforzorro said:
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?
Click to expand...
Click to collapse
I tried the 2.3 Update (https://forum.xda-developers.com/xp...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

I tried Xperifix 2.4 and still have .NET error. I contacted the developer but so far no solution.

To root or not
Didgesteve said:
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
Click to expand...
Click to collapse
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 ----------
TheDelta said:
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!!
Click to expand...
Click to collapse
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.

TheDelta said:
Any help is appreciated,
Click to expand...
Click to collapse
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.

To root or not to root
Didgesteve said:
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.
Click to expand...
Click to collapse
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?
---------- Post added at 04:52 AM ---------- Previous post was at 04:48 AM ----------
TheDelta said:
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?
Click to expand...
Click to collapse
I forgot to mention yesterday, I had checked on this phone. Boot loader unlock says allowed/yes. :highfive:

TheDelta said:
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).
Click to expand...
Click to collapse
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

Didgesteve said:
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
Click to expand...
Click to collapse
Bollocks!! I don't think i know how to go back to .75 then. Guess i just have to stay on stock till i get bored or xposed runs on .145 right? or whatever is newer out there. Apparently whenever i want to flash an OTA i still have to flash it in flashmode since i am on custom UK firmware so i think i will anyhow get bored and move onto custom pretty soon :fingers-crossed:
I haven't really been much of an OTA person. I usually keep formatting full phone to put new ROM or new release version every 3-4 months. I like a clean slate, keeps the phone in shape
Btw i did buy Storm's utility in morning so guess i am future proof :silly:
One question - I keep reading "you will lose DRM Keys" I thought it meant that Sony removes/disables/dissolves their own files which are required for apps/apks to run like camera. But is that something phone specific? like specific to me? The way everyone keeps saying you will lose that and you will never get it back - i want to know what it means. Like I cannot get it back for my specific phone? or Sony in General is not going to give it out but it is just a generic key/file. Sorry, just trying to understand what it exactly means. I earlier thought it is like that CID i had to backup for my motorola phone because it was my device ID number or a key file specific for my own personal device which once removed made it generic to flash.
---------- Post added at 01:02 PM ---------- Previous post was at 12:57 PM ----------
Didgesteve said:
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
Click to expand...
Click to collapse
Bollocks!! I don't think i know how to go back to .75 then. Guess i just have to stay on stock till i get bored or xposed runs on .145 right? or whatever is newer out there. Apparently whenever i want to flash an OTA i still have to flash it in flashmode since i am on custom UK firmware so i think i will anyhow get bored and move onto custom pretty soon :fingers-crossed:
I haven't really been much of an OTA person. I usually keep formatting full phone to put new ROM or new release version every 3-4 months. I like a clean slate, keeps the phone in shape
Btw i did buy Storm's utility in morning so guess i am future proof :silly:
One question - I keep reading "you will lose DRM Keys" I thought it meant that Sony removes/disables/dissolves their own files which are required for apps/apks to run like camera. But is that something phone specific? like specific to me? The way everyone keeps saying you will lose that and you will never get it back - i want to know what it means. Like I cannot get it back for my specific phone? or Sony in General is not going to give it out but it is just a generic key/file. Sorry, just trying to understand what it exactly means. I earlier thought it is like that CID i had to backup for my motorola phone because it was my device ID number or a key file specific for my own personal device which once removed made it generic to flash.
---------- Post added at 01:03 PM ---------- Previous post was at 01:02 PM ----------
Didgesteve said:
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
Click to expand...
Click to collapse
Bollocks!! I don't think i know how to go back to .75 then. Guess i just have to stay on stock till i get bored or xposed runs on .145 right? or whatever is newer out there. Apparently whenever i want to flash an OTA i still have to flash it in flashmode since i am on custom UK firmware so i think i will anyhow get bored and move onto custom pretty soon :fingers-crossed:
I haven't really been much of an OTA person. I usually keep formatting full phone to put new ROM or new release version every 3-4 months. I like a clean slate, keeps the phone in shape
Btw i did buy Storm's utility in morning so guess i am future proof :silly:
One question - I keep reading "you will lose DRM Keys" I thought it meant that Sony removes/disables/dissolves their own files which are required for apps/apks to run like camera. But is that something phone specific? like specific to me? The way everyone keeps saying you will lose that and you will never get it back - i want to know what it means. Like I cannot get it back for my specific phone? or Sony in General is not going to give it out but it is just a generic key/file. Sorry, just trying to understand what it exactly means. I earlier thought it is like that CID i had to backup for my motorola phone because it was my device ID number or a key file specific for my own personal device which once removed made it generic to flash.
---------- Post added at 01:04 PM ---------- Previous post was at 01:03 PM ----------
TheDelta said:
Bollocks!! I don't think i know how to go back to .75 then. Guess i just have to stay on stock till i get bored or xposed runs on .145 right? or whatever is newer out there. Apparently whenever i want to flash an OTA i still have to flash it in flashmode since i am on custom UK firmware so i think i will anyhow get bored and move onto custom pretty soon :fingers-crossed:
I haven't really been much of an OTA person. I usually keep formatting full phone to put new ROM or new release version every 3-4 months. I like a clean slate, keeps the phone in shape
Btw i did buy Storm's utility in morning so guess i am future proof :silly:
One question - I keep reading "you will lose DRM Keys" I thought it meant that Sony removes/disables/dissolves their own files which are required for apps/apks to run like camera. But is that something phone specific? like specific to me? The way everyone keeps saying you will lose that and you will never get it back - i want to know what it means. Like I cannot get it back for my specific phone? or Sony in General is not going to give it out but it is just a generic key/file. Sorry, just trying to understand what it exactly means. I earlier thought it is like that CID i had to backup for my motorola phone because it was my device ID number or a key file specific for my own personal device which once removed made it generic to flash.
---------- Post added at 01:02 PM ---------- Previous post was at 12:57 PM ----------
Bollocks!! I don't think i know how to go back to .75 then. Guess i just have to stay on stock till i get bored or xposed runs on .145 right? or whatever is newer out there. Apparently whenever i want to flash an OTA i still have to flash it in flashmode since i am on custom UK firmware so i think i will anyhow get bored and move onto custom pretty soon :fingers-crossed:
I haven't really been much of an OTA person. I usually keep formatting full phone to put new ROM or new release version every 3-4 months. I like a clean slate, keeps the phone in shape
Btw i did buy Storm's utility in morning so guess i am future proof :silly:
One question - I keep reading "you will lose DRM Keys" I thought it meant that Sony removes/disables/dissolves their own files which are required for apps/apks to run like camera. But is that something phone specific? like specific to me? The way everyone keeps saying you will lose that and you will never get it back - i want to know what it means. Like I cannot get it back for my specific phone? or Sony in General is not going to give it out but it is just a generic key/file. Sorry, just trying to understand what it exactly means. I earlier thought it is like that CID i had to backup for my motorola phone because it was my device ID number or a key file specific for my own personal device which once removed made it generic to flash.
---------- Post added at 01:03 PM ---------- Previous post was at 01:02 PM ----------
Bollocks!! I don't think i know how to go back to .75 then. Guess i just have to stay on stock till i get bored or xposed runs on .145 right? or whatever is newer out there. Apparently whenever i want to flash an OTA i still have to flash it in flashmode since i am on custom UK firmware so i think i will anyhow get bored and move onto custom pretty soon :fingers-crossed:
I haven't really been much of an OTA person. I usually keep formatting full phone to put new ROM or new release version every 3-4 months. I like a clean slate, keeps the phone in shape
Btw i did buy Storm's utility in morning so guess i am future proof :silly:
One question - I keep reading "you will lose DRM Keys" I thought it meant that Sony removes/disables/dissolves their own files which are required for apps/apks to run like camera. But is that something phone specific? like specific to me? The way everyone keeps saying you will lose that and you will never get it back - i want to know what it means. Like I cannot get it back for my specific phone? or Sony in General is not going to give it out but it is just a generic key/file. Sorry, just trying to understand what it exactly means. I earlier thought it is like that CID i had to backup for my motorola phone because it was my device ID number or a key file specific for my own personal device which once removed made it generic to flash.
Click to expand...
Click to collapse
Bollocks I wrote that so many times!!!

TheDelta said:
Bollocks I wrote that so many times!!!
Click to expand...
Click to collapse
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.

Didgesteve said:
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.
Click to expand...
Click to collapse
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.

TheDelta said:
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.
Click to expand...
Click to collapse
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.

Didgesteve said:
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.
Click to expand...
Click to collapse
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

.75
Didgesteve said:
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.
Click to expand...
Click to collapse
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¿

Related

Need some help regarding Custom-ROMs and their consequences!

Hello, iam a Xperia-Z (C6603) User for a week or two and am now looking forward to a
Nice and clean custom-Rom without any bloatware which I hate(ultimate music Sony select,sonysocialfoo and Facebook and alike)
and I guess cm11nightly would fulfill my needs, as i would also really love a smartphone without gapps.
FIrst I thought it would basically be a decision between the to be flashed ROM but now
I read about the bravia-engine getting lost forever which would really suck, is this still
State-of-the-art? Or is there an Option to get it back, as far as I know the BE is basically still there but licensed over a key like the mpeg2-codec on the raspberry-Pi isn't there a possibility to back it up and still be able to use it when you revert back to stock for example?
You're in charge now, what do you suggest me? Iam still on 4.2.2 and would like to get everything up-to-date soon. Btw. I would want a Rom that is of the same color as stock 4.2.2 so basically black, a white theme would be hard to look at in dark conditions even when turned down to lowest brightness.
So to sum it up: NO bloatware (must), NO gapps(nicetohave), black theme like 4.2.2(must), still BEngine(nicetohave)
Btw. How's the image-quality with custom-Roms? It shouldn't get worse than it is in 4.2.2 stock if possible!
Thanks! :good::highfive:
luluchambler said:
Hello, iam a Xperia-Z (C6603) User for a week or two and am now looking forward to a
Nice and clean custom-Rom without any bloatware which I hate(ultimate music Sony select,sonysocialfoo and Facebook and alike)
and I guess cm11nightly would fulfill my needs, as i would also really love a smartphone without gapps.
FIrst I thought it would basically be a decision between the to be flashed ROM but now
I read about the bravia-engine getting lost forever which would really suck, is this still
State-of-the-art? Or is there an Option to get it back, as far as I know the BE is basically still there but licensed over a key like the mpeg2-codec on the raspberry-Pi isn't there a possibility to back it up and still be able to use it when you revert back to stock for example?
You're in charge now, what do you suggest me? Iam still on 4.2.2 and would like to get everything up-to-date soon. Btw. I would want a Rom that is of the same color as stock 4.2.2 so basically black, a white theme would be hard to look at in dark conditions even when turned down to lowest brightness.
So to sum it up: NO bloatware (must), NO gapps(nicetohave), black theme like 4.2.2(must), still BEngine(nicetohave)
Btw. How's the image-quality with custom-Roms? It shouldn't get worse than it is in 4.2.2 stock if possible!
Thanks! :good::highfive:
Click to expand...
Click to collapse
I would recommend Cyanogen Mod to most people. Honestly I can't live without the features these days!
Regarding the consequences.. Well there aren't really any.. Kinda.. You may or may not lose your warranty based on how stingy Sony are feeling at the time. Most of the BRICK warnings are just to cover developers if someone does something wrong or if your phone just so happens to die of something completely unrelated while installing the rom.
I would recommend trawling this forum for at least and hour or two just reading the various guides; How to backup your phone, How to unlock the bootloader and, most importantly, how to backup your TA partition.
It's quite a pain free process. It's just better to be aware of what could go wrong, so you are prepared and can easily apply the fix before panicking and messing something up
Good luck and happy trawling!
You only have to learn these things once. Once your rooted, unlocked and running a custom rom updating is easier than sonys
Hi, thank you for your reply.
I just looked up what exactly the "TA-Partition" is and i guess the only thing that was worrying me (loosing Bravia) is not up-to-date anymore
So lets get started, i looked up what i need to backup the "TA-Partition" and if i understood everything its basically having a rooted Xperia-Z and a double-click on a .bat-file?
So i guess the best would to not upgrade any of the shown OTA-Updates by Sony, and root the 4.2.2-Stock ROM that is on the device right now?
As far as i know rooting 4.2.2 isn't really a problem right now, agreed?
So after sucessfully rooting the Sony Xperia-Z its just backing up the "TA-Par tition" with "TA-Backup"-Script?
After that, its unlocking the Boot-loader over the Sony-Website (IMEI, Name, Email....) so that they send you the Unlock-Code, after that you'll have to use fastboot to finally unlock it?
(If i check the Service Menu "Rooting Status": there is nothing behind it, but the bootloader-unlock allowed: says yes, so no problem right?)
After that you most likely are done for the moment, until you decide if it should be CM10.1Stable or CM11Nightly, rig
How's the status of CM11 right now, any known major bugs?
Thank you already for your help :good:
luluchambler said:
Hi, thank you for your reply.
I just looked up what exactly the "TA-Partition" is and i guess the only thing that was worrying me (loosing Bravia) is not up-to-date anymore
So lets get started, i looked up what i need to backup the "TA-Partition" and if i understood everything its basically having a rooted Xperia-Z and a double-click on a .bat-file?
So i guess the best would to not upgrade any of the shown OTA-Updates by Sony, and root the 4.2.2-Stock ROM that is on the device right now?
As far as i know rooting 4.2.2 isn't really a problem right now, agreed?
So after sucessfully rooting the Sony Xperia-Z its just backing up the "TA-Par tition" with "TA-Backup"-Script?
After that, its unlocking the Boot-loader over the Sony-Website (IMEI, Name, Email....) so that they send you the Unlock-Code, after that you'll have to use fastboot to finally unlock it?
(If i check the Service Menu "Rooting Status": there is nothing behind it, but the bootloader-unlock allowed: says yes, so no problem right?)
After that you most likely are done for the moment, until you decide if it should be CM10.1Stable or CM11Nightly, rig
How's the status of CM11 right now, any known major bugs?
Thank you already for your help :good:
Click to expand...
Click to collapse
I've been using Cyanogenmod 11 nighties for months now, no obvious bugs
Some features aren't implemented yet and the occasional feature is broken.. Nothing really integral to the phone though
You've pretty much got the method down! Just ensure you use a root method for your sony firmware version (Android version). It should use some form of "Exploit" to avoid deleting the TA-Partition. Honestly I backed mine up and haven't ever wanted to restore it, the features are more of a gimmick than anything useful
Enjoy
A few more questions! (Iam sorry )
So as far as i can see, my smartphone is running "10.3.1.A.0.244" which is regarding to the post by DooMLord not exploitable.
I therefore have to flash the "10.3.A.0.423"-Kernel-Only so that the previously used exploit works again.
After that i'll have to restore the Kernel that was previously on the Smartphone therefore "10.3.1.A.0.244"
After that root should stay in intact, but what about the TA-Partion? Is it somehow affected by this?
Secound Question, is it crucial to have an micro-sdhc inserted to sucessfully flash CM11 onto the Xperia Z after backing up TA, or is it possible without?
And the Image-Quality (taking Pictures) should be kinda worse on CM11 than it is with Sony's Stock Firmware, is it possible to include(myself) the propritary firmware.blobs for the Camera as we do it with gapps, or will i have to live with the reduced image Quality?
Thanks!

Just picked up this device, any tips?

So I've been out of the Android Phone loop for a while and was just wondering if there were any general tips or things to know about the Z3C? Any essential apps or features?
I've not updated to Marshmallow yet (running 5.1.1) and I don't really feel the need to, If I'm not mistaken it makes the root process a bit more fiddly, though the non-removable notification is somewhat annoying. Can it be turned off?
Quick question on root too, which I assume can only be achieved through unlocking the bootloader. Will it void my warranty with Sony? Given the issues with cracked screens and phones not really being waterproof, I'm not sure if it's actually worth doing.
I've got the Phone through Vodafone, is there anyway to remove the SIM lock myself?
I've been through the Stickies and whilst they contain useful information that'll surely come in handy later, the FAQ section is pretty limited, so I figured I'd ask here
Thanks in advance
UndisputedGuy said:
So I've been out of the Android Phone loop for a while and was just wondering if there were any general tips or things to know about the Z3C? Any essential apps or features?
I've not updated to Marshmallow yet (running 5.1.1) and I don't really feel the need to, If I'm not mistaken it makes the root process a bit more fiddly, though the non-removable notification is somewhat annoying. Can it be turned off?
Quick question on root too, which I assume can only be achieved through unlocking the bootloader. Will it void my warranty with Sony? Given the issues with cracked screens and phones not really being waterproof, I'm not sure if it's actually worth doing.
I've got the Phone through Vodafone, is there anyway to remove the SIM lock myself?
I've been through the Stickies and whilst they contain useful information that'll surely come in handy later, the FAQ section is pretty limited, so I figured I'd ask here
Thanks in advance
Click to expand...
Click to collapse
You don't need to unlock the bootloader to be able to root your phone. A good place to start is the thread on how to back up your TA partition and rooting (don't be tempted by Kingroot)
Unless you want a custom CM rom I wouldn't bother trying to unlock your bootloader, it disables features on the phone, starting with breaking the camera.
This thread about going from a rooted phone back to stock is interesting. I'd say you don't need to root your phone, but it gets a lot more interesting when you do.
The top app for if you get root is Titanium Backup, it lets you control individual apps, 'freezing' them so they stop working, but not actually uninstalling them. Great for getting rid of all the bloatware that comes with phone providers (like Sim Lock), or even manufacturers. It also lets you back up an app and all the associated data that goes with it, so if you wipe you phone to change the rom, you can put all the apps back and the state they were in at the touch of a button. There's lots of other cool root apps, but TA is my favourite.
As long as you stick to stock then you can't go wrong, don't be afraid to play, there's plenty of people on the thread here to give you a hand.
SLIM 5 is a good stock 5.1.1 rom with lots of cool tweeks and doesn't mean you have to unlock your bootloader.
Edit: Rooting your phone doesn't void your warranty. But if you face any problems with your phone that means it's going back to the service centre, just put a stock build back on (no root) and do a factory reset. That way they cannot complain about the software config. They will do a factory reset anyway, before they send it back, along with an update to the latest rom. So be prepared and take everything off your phone beforehand.
Man, that's pretty much all the information I need in one post. Thanks a bunch man, I'll read through the links in some more detail.
I did see that Rooting guide earlier, but given how it mentioned using Flashtool and DRM Keys, I thought it'd surely void my warranty so didn't have a proper look.
SLIM also seems like a good shout, though I'm assuming I'd lose access to Sony's OTA updates if I were to flash it and there doesn't seem to be a Marshmallow version yet. Actually, that said, would I even have access to OTA updates if I stay stock but rooted?
Thanks again
UndisputedGuy said:
Man, that's pretty much all the information I need in one post. Thanks a bunch man, I'll read through the links in some more detail.
I did see that Rooting guide earlier, but given how it mentioned using Flashtool and DRM Keys, I thought it'd surely void my warranty so didn't have a proper look.
SLIM also seems like a good shout, though I'm assuming I'd lose access to Sony's OTA updates if I were to flash it and there doesn't seem to be a Marshmallow version yet. Actually, that said, would I even have access to OTA updates if I stay stock but rooted?
Thanks again
Click to expand...
Click to collapse
Marshmallow has only been out a few weeks, so it's still full of bugs and problems at the moment. I would stick to 5.1.1. for at least another month, or until 6.1 reaches the Z3c.
No, if you install a custom rom then you wont get Sony OTA updates, but most rom developers base their builds on the latest firmware releases anyway, usually adopting a new release within one or two weeks.
Slim 5 is possibly the best stock Lollipop build there is and there will be no more updates for Lollopop now. There is a Slim MM build, but even though Wajk has been working his magic, it still has several bugs that need to be ironed out. If you are going down the MM route, don't be tempted by Concept or Beta, that need you to unlock your bootloader to root. Stick with a pre-rooted stock or a customised stock with root built in.
Appreciate the assistance, going to go ahead and root now and then perhaps try out SLIM 5. Some of the MEGA links seemed to be down so I just grabbed a Global FTF, couldn't seem to find an unbranded UK one.
I shouldn't have updated immediately once I got the phone
UndisputedGuy said:
Appreciate the assistance, going to go ahead and root now and then perhaps try out SLIM 5. Some of the MEGA links seemed to be down so I just grabbed a Global FTF, couldn't seem to find an unbranded UK one.
I shouldn't have updated immediately once I got the phone
Click to expand...
Click to collapse
For the purposes of downgrading so you can root, it really doesn't matter which build you choose.
Didgesteve said:
For the purposes of downgrading so you can root, it really doesn't matter which build you choose.
Click to expand...
Click to collapse
Just a quick question, at Step 26 could I just use SLIM 5? Seems much more convenient if that's the case.
Oh, and using OTA updates is going to lose me my root now, right?
UndisputedGuy said:
Just a quick question, at Step 26 could I just use SLIM 5? Seems much more convenient if that's the case.
Oh, and using OTA updates is going to lose me my root now, right?
Click to expand...
Click to collapse
Yes, once you have recovery you can download Slim onto your phone and flash that. Don't forget to update SuperSU from the playstore.
No, you wont get any OTA updates with a custom stock, but Slim is up to date with the most recent Lollipop build.
Sony PC Companion will not update your phone either once you have a custom rom on. If you flash stock and then connect it, it will push MM onto it. But you will loose root and there's no easy way to get it working.
Stick with 5.1.1. for another month, wait for 6.1 to come out, and then possibly a couple of weeks after that Wajik will have made an incredible MM rom to flash, that will be as up to date as they come, then just flash that in exactly the same way.
Edit: Once you start to follow a developers thread, they announce updates to roms almost as quick as the Sony release, so don't worry that it will get out of date, just make sure to subscribe to the thread where your rom comes from. Slim 5 for example releases an OTA update, to move from 4.9 to 5, it's a lot smaller than the entire rom and only has updates, but flashes the same way.
Can only thank you again, successfully rooted and got recovery. Not sure how much I'm really fond of SLIM, just had a very brief mess around but something felt a bit off about the Launcher and the icons even after messing with the settings. It was only very brief though, perhaps there's more useful stuff there.
Might go simply stock/rooted but given there isn't a simple .zip for it it's a bit long winded
Thanks for all your help here, this is pretty much the ideal state I wanted my phone to be in upon receiving it, had no idea unlocking the bootloader wouldn't be necessary. Guys like you help make this site in my opinion, I half just expected a couple of snide answers telling me to just read the forum
Think I will be moving back to stock, just a question on the front though
Am I going to have to build my own pre rooted image (steps 27-32) each time there's an OTA update and I want rooted stock?
Sorry, hopefully that's the last thing from me
Sent from my D5803 using XDA-Developers mobile app
UndisputedGuy said:
Think I will be moving back to stock, just a question on the front though
Am I going to have to build my own pre rooted image (steps 27-32) each time there's an OTA update and I want rooted stock?
Sorry, hopefully that's the last thing from me
Sent from my D5803 using XDA-Developers mobile app
Click to expand...
Click to collapse
There are several 'stock' options, that are flashable zips
Pre-Rooted Firmwares-Recovery-SuperSU, although you need to click on 'older files'
Or another stock thread here
But by now you should be able to start finding these threads on your own
Yeah, I've time to have a proper look through now so will do that. I saw the thread earlier, but didn't seem to notice a pre rooted .zip for the latest 5.1.1 firmware in the OP. There was one in the comments though, thanks once again

What is the best Android version for Z3 Compact?

Hi
My first post here and wondered if any of you would have a neat answer for me.
I am considering getting a Z3 Compact, and have been reading about it and it seems there may have been some issues with Android updates affecting thing slike battery life, etc. I know it can be taken as far as MARSHMALLOW, but some people say it is better to stay at LOLLIPOP, and I have found still other owners saying that they have flashed their phones back to KITKAT, and that this is the best match for the phone.
I am wondering if there is a best answer for what is the best version of Android to be using with this phone?
Thanks!
Robert
It's a very difficult question since it depends on what you mean what best is since the term is very subjective. IIf battery life is all you care about then I heard Kitkat is the best because they crippled the Stamina mode in later versions. But that means you will have a hopelessly outdated software when it comes to security updates, which I would think is more important than battery life. But if you want to software thats up to date then you cant be using stock ROM but which means you have to unlock the bootloader which leads to degradation in camera quality. So there are lots of factors to consider.
BrotherZero said:
It's a very difficult question since it depends on what you mean what best is since the term is very subjective. IIf battery life is all you care about then I heard Kitkat is the best because they crippled the Stamina mode in later versions. But that means you will have a hopelessly outdated software when it comes to security updates, which I would think is more important than battery life. But if you want to software thats up to date then you cant be using stock ROM but which means you have to unlock the bootloader which leads to degradation in camera quality. So there are lots of factors to consider.
Click to expand...
Click to collapse
Thanks BrotherZero
That's useful to hear. My preference would be to have the most recent OS available, which looks like MARSHMALLOW (I don't want to change bootloader and good camera is important)
My concern was just that battery life would be really poor with that. If it's still good I have no issue.
Worry has arisen because I had one for a couple of days that I sent back because the battery was draining very quickly indeed, and I am trying to work out if it is an OS issue before buying again (I really liked the phone)
If its just "not quite as good battery life on Marshmallow, but still very decent" then that's fine.
Thanks
R
rdpxi said:
Thanks BrotherZero
That's useful to hear. My preference would be to have the most recent OS available, which looks like MARSHMALLOW (I don't want to change bootloader and good camera is important)
My concern was just that battery life would be really poor with that. If it's still good I have no issue.
Worry has arisen because I had one for a couple of days that I sent back because the battery was draining very quickly indeed, and I am trying to work out if it is an OS issue before buying again (I really liked the phone)
If its just "not quite as good battery life on Marshmallow, but still very decent" then that's fine.
Thanks
R
Click to expand...
Click to collapse
I have flashed Kitkat, but I never used it for an extensive period (my phone was delivered with LP). I heard from numerous sources that battery life was exceptional on Kitkat, but it was really good on LP too for mer, so It wasn't like I needed better batterylife and add that Kitkat looked really outdated. With Marshmallow I thought I could slightly worse batterylife, but it wasnt a huge degradation either. So I think you will be fine on that.
About the camera, I don't know how good the quality is now on either LIneage OS or OmniROM (these are the ROMs I'm looking to flash my Z3c with now, they have the most up to date software right now and are also open source, Jaguar looks very interesting too, but the dev just dropped the project a month or so ago) but i felt the camera wasn't that good to begin with on Z3c any way. My LG phones (G2 and G4) always blew it out of the water and I don't think I ever seen a sony phone with a really good camera (which is weird since they make the sensor for everybody else). That's why I dont have any qualms abuot unlocking bootloader anymore.
BrotherZero said:
I have flashed Kitkat, but I never used it for an extensive period (my phone was delivered with LP). I heard from numerous sources that battery life was exceptional on Kitkat, but it was really good on LP too for mer, so It wasn't like I needed better batterylife and add that Kitkat looked really outdated. With Marshmallow I thought I could slightly worse batterylife, but it wasnt a huge degradation either. So I think you will be fine on that.
About the camera, I don't know how good the quality is now on either LIneage OS or OmniROM (these are the ROMs I'm looking to flash my Z3c with now, they have the most up to date software right now and are also open source, Jaguar looks very interesting too, but the dev just dropped the project a month or so ago) but i felt the camera wasn't that good to begin with on Z3c any way. My LG phones (G2 and G4) always blew it out of the water and I don't think I ever seen a sony phone with a really good camera (which is weird since they make the sensor for everybody else). That's why I dont have any qualms abuot unlocking bootloader anymore.
Click to expand...
Click to collapse
Thanks again
What I am hearing is that if I buy one, I can upgrade it to MMallow and all will be fine, which is kind of what I was hoping to hear.
I've spent three years with an S4 Mini, so I think the camera will be a huge step up whatever I do to it!!
R
After the last marshmallow update the battery life seems the same if not better with lollipop also the Phone is faster. Just Do a full repair to be sure after updating it to the last Version from sonys tool.
I would unlock the bootloader and install new LineageOS,I am running it and it is amazing,camera is rock solid and performance is amazing
rdpxi said:
Thanks again
What I am hearing is that if I buy one, I can upgrade it to MMallow and all will be fine, which is kind of what I was hoping to hear.
I've spent three years with an S4 Mini, so I think the camera will be a huge step up whatever I do to it!!
R
Click to expand...
Click to collapse
S4 mini's camera is really cool ( had that phone before my z3 compact too! )
For months, I've been using the 4.4 version for my Z3 Compact, cause I sipmly find the camera tons better than Marshmallow! ( Haven't tried Lollipop, I bought the phone with Marshmallow installed! )
On Marshmallow , while you're on the viewfinder, the touch to focus function doesn't work for me! ( I have to tap on the screen to choose where I want to focus, and then use the camera dedicated button, so that the camera starts focusing, while on Kitkat, I just tap , and it focuses immidiately)
Auto focus while video recording is horrible as well, while on Kitkat the autofocus is really fast.
I even found playing GTA San Andreas smoother at 4.4.
What I want to say is that staying at old versions isn't always bad. Sometimes old is gold.
Thanks to all of you responding.
Couple of things:
1 . what do you mean by "do a full repair" after updating?
2. how difficult is doing something like fiddling wth bootloader and installing Lineage? (I probably wouldn't go that far TBH)
On the second question, and also because you're concerned about the camera, if you unlock the bootloader the phone wipes DRM keys that are needed for integration with various functionns. The camera quality will be greatly reduced, audio effects will be reduced, and some other stuff that I was never concerned with and thus don't know what they are. You can backup the DRM keys and restore them after relocking the bootloader for use on a stock ROM, which is a process you'de need to search and find out how to do and isn't too complicated at the moment, however running anything that isn't stock, Lineage, Jaguar, Cyanogenmod, etc, requires an unlocked bootloader and camera quality is going to suffer on these ROMs. Also, if you don't back up the DRM keys properly and unlock the bootloader, you're screwed when it comes to getting them back; they will be deleted forever.
As for fiddling with the bootloader and installing a ROM goes, you need to go to a Sony webpage to unlock it. This voids your warranty. You then use fastboot to install a custom recovery, TWRP usually, and flash the ROM. You can relock it using a tool called Flashtool, which is found in the Z3 compact section somewhere, but you can't use a custom ROM while the bootloader is locked nor use the full features that are included with the stock ROM and will have reduced camera quality and a sligtly distorted image; relocking the bootloader is for the purpose of using Flashtool to put a stock ROM back and restore the (hopefully backed up) DRM keys.
Keep in mind that there are stock ROMs that have been modified to have a locked bootloader, root, implement TWRP where it isn't detected by the phone (so DRM keys still work), xposed can be flashed, etc, etc.
All of this would be a little daunting for someone swithing to the phone right now because the frustrations and progress have been incremental and there isn't a really clear thread I know of that lays it all out, like Backup DRM keys like this, Unlock the Bootloader like this, Install TWRP like this, Download Flashtool here, Relock the bootloader like this, Install a Stock ROM like this, Restore DRM keys like this, Install a rooted stock ROM like this, etc. That said, if you've been on the forum for any length of time it should go okay, the main concern is backing up your DRM keys and once that is done the only concern is, like any other phone, bricking it. If you don't need root and want a good camera, then the question is if you're content with Marshmallow and the fact that there aren't any future updates, or more acurately, you can have root on Marshmallow and a good camera (the current method on the latest stock Marshmallow is the easiest its ever been to get root), but there aren't any future updates.
Hi PantsDownJedi, could you pls share the link to the safest method to get root on Marshmallow, leaving the locked bootloader untouched? Thanks!
---------- Post added at 11:04 PM ---------- Previous post was at 10:17 PM ----------
PantsDownJedi said:
On the second question, and also because you're concerned about the camera, if you unlock the bootloader the phone wipes DRM keys that are needed for integration with various functionns. The camera quality will be greatly reduced, audio effects will be reduced, and some other stuff that I was never concerned with and thus don't know what they are. You can backup the DRM keys and restore them after relocking the bootloader for use on a stock ROM, which is a process you'de need to search and find out how to do and isn't too complicated at the moment, however running anything that isn't stock, Lineage, Jaguar, Cyanogenmod, etc, requires an unlocked bootloader and camera quality is going to suffer on these ROMs. Also, if you don't back up the DRM keys properly and unlock the bootloader, you're screwed when it comes to getting them back; they will be deleted forever.
As for fiddling with the bootloader and installing a ROM goes, you need to go to a Sony webpage to unlock it. This voids your warranty. You then use fastboot to install a custom recovery, TWRP usually, and flash the ROM. You can relock it using a tool called Flashtool, which is found in the Z3 compact section somewhere, but you can't use a custom ROM while the bootloader is locked nor use the full features that are included with the stock ROM and will have reduced camera quality and a sligtly distorted image; relocking the bootloader is for the purpose of using Flashtool to put a stock ROM back and restore the (hopefully backed up) DRM keys.
Keep in mind that there are stock ROMs that have been modified to have a locked bootloader, root, implement TWRP where it isn't detected by the phone (so DRM keys still work), xposed can be flashed, etc, etc.
All of this would be a little daunting for someone swithing to the phone right now because the frustrations and progress have been incremental and there isn't a really clear thread I know of that lays it all out, like Backup DRM keys like this, Unlock the Bootloader like this, Install TWRP like this, Download Flashtool here, Relock the bootloader like this, Install a Stock ROM like this, Restore DRM keys like this, Install a rooted stock ROM like this, etc. That said, if you've been on the forum for any length of time it should go okay, the main concern is backing up your DRM keys and once that is done the only concern is, like any other phone, bricking it. If you don't need root and want a good camera, then the question is if you're content with Marshmallow and the fact that there aren't any future updates, or more acurately, you can have root on Marshmallow and a good camera (the current method on the latest stock Marshmallow is the easiest its ever been to get root), but there aren't any future updates.
Click to expand...
Click to collapse
Hi PantsDownJedi, could you pls share the link to the safest method to get root on Marshmallow, leaving the locked bootloader untouched? Thanks!
liviugi said:
Hi PantsDownJedi, could you pls share the link to the safest method to get root on Marshmallow, leaving the locked bootloader untouched? Thanks!
---------- Post added at 11:04 PM ---------- Previous post was at 10:17 PM ----------
Hi PantsDownJedi, could you pls share the link to the safest method to get root on Marshmallow, leaving the locked bootloader untouched? Thanks!
Click to expand...
Click to collapse
Recovery & Root for MM .575 & .291 LB
https://forum.xda-developers.com/showthread.php?t=3418714
Gesendet von meinem D5803 mit Tapatalk

The great adventure of rooting the XZ1C

Hello everyone,
I have to say I am completely lost regarding the whole rooting process for the XZ1C. I usually manage to get where I want just by carefully reading the forums, but with this device, I feel overwhelmed by information. And I sometimes feel like what I am reading contradicts what I though I understood from previous reads...
I will try to sum up what I know so far.
First of all, I have a just-out-of-the-box Sony model G8441 with firmware 47.1.A.12.179 / Oreo 8.0.0 (never been connected to the outside world yet), and I want to properly root the device and install TWRP with no loss of feature.
What I think I understand:
To root, I first need to unlock the bootloader, which seems to be a trivial operation. However, this will break some functionalities due to DRM keys being erased. Once it is done, there is no way, ever, to get them back. There are however ways to "trick" DRM-related functionalities into believing DRM keys are still there.
Alternatively, there seems to be a way to backup the DRM keys prior to unlocking the BL, and this backup can somehow be reused and injected back into the unlocked device. If true, then this would certainly be a preferable method than the previous one, which would then be obsolete. However, it obviously doesn't look obsolete when I read the related topics, so I must be missing something...
Another thing I noted (but do not quite understand): There are ROMs for this device that "include" a DRM fix.
Last important thing I read: there is a paid "do-it-all" tool which takes my locked device and, with one click, makes it unlocked - rooted - DRM-fixed - TWRP-enabled. Now that sounds really good! Maybe too good?
As far as i know (but I learn new stuff every day on this topic) this DRM stuff is the main difficulty here. I understand that the rest of the process (root + TWRP) will be much simpler (although I'm old-school and completly missed all this magisk trend...!)
What I don't understand:
I read that some people downgrade to Oreo to be able to root properly, and at the same time, I read that Pie removed the restrictions on unlocked bootloader. So I still have no idea if I should connect and receive Sony updates, or avoid them.
Another thing I don't get, is how many ways do we have to root this thing? In the past, I was used to see, for a specific device, always one major and widly used rooting method. Here I fail to identify it...
What I think I will do:
1. Backup TA partition with j4nn's tool. This will probably imply flashing an older firmware right? Is there any link that could help me with this flashing process? (I only know Odin - did I mention old-school?) I saw this page for generic sony Z devices, but the thread is from 2013 and now closed. Is it still up-to-date or is there a newer thread?
2. Unlock bootloader and restore TA partition.
3. Wait for Sony updates? Or should I first hide unlock status?
3bis. Alternaltively to waiting for updates, maybe I can just flash the latest build? (47.2.A.8.24 if I am not mistaken)
4. Flash modpunk's TWRP.
5. Flash janjan's Boot.img to get root functionalities?
Alternaltively to all the above (except maybe step 1 that I will probably do in any case), buy the paid all-in-one tool (Xperifix), plug, click and wait... But will I really end up the same as with the manual way?
I saw a few other methods in the forums but it seems my brain is currently refusing to bring them back...
That's all I have right now. I would really appreciate if you guys could share some insight and tell me what you think about this, whether there are missing steps, useless steps, incorrectly ordered steps, silly steps, or if I'm just completely wrong about the whole thing.
Feel free also to correct me on the assumptions I made at the beginning.
Thank you very much for reading this repulsive piece of text.
SunJu22 said:
I would really appreciate if you guys could share some insight and tell me what you think about this
Click to expand...
Click to collapse
By the looks of it you have done a great deal of research on the project.
Yes, go down the route of backing up your TA partition first, but that is not a small step in itself, it's pretty complicated and if you get that working then the rest of the project will be a breeze.
You don't say what version of firmware you want to end up on. If you want to end up on Pie then forget the DRMfix . But if you're staying on Oreo and can't be bothered with lots of files & flashing, then this is the easy way out, I bought the paid version and can verify it works.
More recently I ended up janjan's kernel (Oreo build). Hidden root (Google Pay works), lots of performance tweaks, DRM completely working.
It's unlikely that anyone will bother making a DRM fix for Pie as the camera works and there are only a couple of other features that get disabled.
It sounds like you're not the sort of person who's only going to read the first couple of pages of a thread (or the last) flash the xxxxxx and then complain when it's broken.
The people on the forum here are very helpful and if you go into any of the threads you mentioned in your post with a question, you'll get a reply.
Good luck.
I agree, there is a lot of information out there and different methods of achieving what you want - very confusing if you have not been following the threads since the beginning.
In my opinion, the preferred method is j4nn's method outlined here: https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510
Use that post as your main guide (the final step in that guide, #13, is how you will achieve root). You will use Newflasher to flash the various firmwares along the way (this is linked from j4nn's procedure in step #2). User munted made a very detailed pdf file that fills in some of the details on j4nn's procedure - see the following post and download the pdf attached: https://forum.xda-developers.com/showpost.php?p=78255334&postcount=382
Most of the other methods out there came before j4nn's work - they didn't include DRM backup/restore.
If you follow j4nn's procedure, you won't need to use the janjan kernel as you assumed - janjan method is different and does not overlap with j4nn.
SunJu22 said:
Feel free also to correct me on the assumptions I made at the beginning.
Click to expand...
Click to collapse
Sorry, I didn't point out that I was one of the early 'jumpers' who unlocked their bootloader without any backups, so I have been forced into always using fixes and all the information I have is based on having to fix your phone for it to work, but that's all changed now. I'm so out of date :-/
 @camaro322hp is right, if you follow j4nn's method correctly you'll be rooted with no DRM loss. All of the other stuff is not required.
Thank you Digesteve and camaro322hp for your help.
From what I understand the XZ1C didn't get as much love as other devices, thus there was a long period of tinkering before a "do-it-all guide" could be considered "the" solution. That could explain all these different approaches that are proposed. Like you said camaro322hp it's rather difficult to jump on this train, and I can only guess how interesting this ride has been.
Anyway, I didn't see that the TA backup thread from j4nn also encompassed all the information I needed; I am glad to finally know that there is indeed a centralized "do-it-all guide" . To make it easier for XZ1C newcomers, I think j4nn should update his opening post to make this clearer.
Since I managed to grab the attention of 2 XZ1C power users, I would like to ask you: Did you keep stock? Did you try alternative ROMs? Do you like some of them? Do you prefer Oreo or Pie?
For information, the most up-to-date experience I have on a Android phone is my LG90 with CyanogenMod 11 (KitKat 4.4.4! Yes sir!). I heard that it's becoming less and less useful to flash a custom ROM due to major OS improvements, but I would still enjoy the simplest and lightest Android possible.
SunJu22 said:
Did you keep stock? Did you try alternative ROMs?
Click to expand...
Click to collapse
I've always been on stock, the camera is an important part of what I want from my phone and although there's lots of alternative camera apps, there's no competition to the stock camera app. Then I theme it black with swift installer and just uninstall or freeze any apps I don't want with Titanium Backup. I have stuck with Oreo, everything works perfect and I remember seeing so many people jumping to 9 then wanting to go back to 8 because they didn't like it. Something about changing the way the drop down menu works, among other things, but having never installed it, I'm not the person to comment on if it's any good or not.
I have been watching the XZ1c thread and Lineage is gaining ground, it even has a stock camera now. I would have thought something like that with miniGapps is going to be pretty lightweight and very similar to your carbon rom of before. At the moment this is based on 8, but is working well. Depends how keen you are to move to Pie.
Thank you Digesteve.
One thing I still don't understand. Part of the process is to hide unlock status. If I do this, FOTA will be applied and I will automatically end up on Pie, right? Should I skip this step if I want Oreo?
EDIT: when you say "a stock camera", you mean the Sony camera?
@SunJu22 I've stuck with the Sony ROM. A rooted stock ROM meets all my needs, so I've never felt the need to experiment with custom ROMs. There are some custom options out there that people seem fairly happy with, so if that's your thing, I'd encourage it.
Without going into too much detail, I'm still on Oreo for the moment, for a variety of reasons, but I don't know of anything that would keep me from recommending Pie.
One thing you should note is that once you unlock, there is no going back. AFAIK there is no known or working method to relock the bootloader.
SunJu22 said:
FOTA will be applied and I will automatically end up on Pie, right? Should I skip this step if I want Oreo?
EDIT: when you say "a stock camera", you mean the Sony camera?
Click to expand...
Click to collapse
Yes, I'm not entirely sure why having your rooted phone try and update itself is an advantage, but something I'd recomend avoiding.
Stock camera is the Sony camera, yes.
Thank you everyone, I believe I now have enough information to jump into this with confidence. The adventure begins, and will be reported in this thread for future reference, in the hope that it will help others like me!
Well, I am a bit sad... I wanted to report my "adventure" here in detail, but I'm afraid I have nothing to say.
Indeed, following the procedure from j4nn with a printed copy of munted's awesome guide, I managed to do all I wanted on the first attempt.
I don't have anything to add to this guide, everyone wanting to root their XZ1C can do it just by reading the opening post from j4nn and the mentioned guide. It takes a bit of time but nothing complicated thanks to the clear and detailed explanations.
I now have a fully functional rooted XZ1C (including camera) on Pie with Magisk root and TWRP.
Thank you all again from pointing me to the right direction.
I however have a slight disappointment. I wanted to start with Oreo and make an Nandroid backup before moving to Pie, but I didn't find Oreo builds on Xperifirm. So I jumped straight to Pie.
In case I want to test Oreo, I read that a downgrade is more complicated than an upgrade, but apart from the fact that a factory reset is needed for downgrade, I couldn't find an explanation for this. Any idea?
Last but not least: I looked for the latest Oreo build version number but couldn't find it. Do you guys know what it is and where I can download it?
I guess this will be all for this thread after this. Although it is very convenient to have my own thread to ask questions rather than finding the relevant page for each one, I don't want to annoy you too much...
EDIT: Please ignore the last question. I found out last Oreo build is 47.1.A.16.20, and I found the files via the download link in the opening post of the Lineage thread.
SunJu22 said:
In case I want to test Oreo, I read that a downgrade is more complicated than an upgrade, but apart from the fact that a factory reset is needed for downgrade, I couldn't find an explanation for this. Any idea? Lineage thread.
Click to expand...
Click to collapse
There is an easy solution to downgrade:
Newflasher
Hi, I've been thinking about rooting my XZ1c for a long time now. So, do I understand correctly that the ONLY disadvantage compared to non-rooted device is not possible to receive the OTA updates from Sony anymore?
mEREHAIGE said:
Hi, I've been thinking about rooting my XZ1c for a long time now. So, do I understand correctly that the ONLY disadvantage compared to non-rooted device is not possible to receive the OTA updates from Sony anymore?
Click to expand...
Click to collapse
No, you can flash a kernel to hide the bootloader unlock flag, this will mean that you will receive OTA updates, although depending on how you're rooted an update will most likely break your phone, so not that useful.
*made a thread*
Thanks--rooted withOUT adventure too
Very happily rooted now. Just wanted to say a quick thanks and add a few notes:
1. j4nn's renoroot to enable TA key backup and restore is fantastic. My advice: use and donate
2. munted's guide is excellent. clear and thorough...a rare combination.
3. do expect that renoroot may need to be restarted a couple of times. it took me 3 or 4 attempts to get temp root to pull the TA keys, although it took only 1 effort to get root back to restore.
4. topjohnwu's magisk is, of course, a key component to all this. Thx and $s there too.
I did a few things slightly differently/additionally than SunJu22.
5. I am on T-Mobile US, so I opted to create a hybrid Pie FW to get wifi calling and VoLTE. There are a number of discussions on this. I did it by combining the vendor**.sin and system**.sin files from custom-CH FW with the other files from custom-US FW. Of course (a) use IDENTICAL release numbers only, e.g. 47.A.2.10.28 w/ 47.A.2.10.28 and (b) you still need to delete .TA and persist files from the hybrid before you flash it.
Note: I don't really care about these features, but I have *heard* that T-mobile won't allow BYOD on their band-12 sites if they don't have VoLTE. Don't know if it is true (or where it is true) but figured why not?
6. I decided (for now, at least) to leave boot and recovery stock. So, I am using fastboot to run TWRP or a rooted kernel. Thanks again to j4nn for the method.
Note: I don't plan on allowing FOTA upgrades---I just like passing all the security checks and being able to *see* if updates are available.
That's all. Fine work in development and guides has made life simple and happy for me
kirkzp said:
Very happily rooted now. Just wanted to say a quick thanks and add a few notes:
1. j4nn's renoroot to enable TA key backup and restore is fantastic. My advice: use and donate
2. munted's guide is excellent. clear and thorough...a rare combination.
3. do expect that renoroot may need to be restarted a couple of times. it took me 3 or 4 attempts to get temp root to pull the TA keys, although it took only 1 effort to get root back to restore.
4. topjohnwu's magisk is, of course, a key component to all this. Thx and $s there too.
I did a few things slightly differently/additionally than SunJu22.
5. I am on T-Mobile US, so I opted to create a hybrid Pie FW to get wifi calling and VoLTE. There are a number of discussions on this. I did it by combining the vendor**.sin and system**.sin files from custom-CH FW with the other files from custom-US FW. Of course (a) use IDENTICAL release numbers only, e.g. 47.A.2.10.28 w/ 47.A.2.10.28 and (b) you still need to delete .TA and persist files from the hybrid before you flash it.
Note: I don't really care about these features, but I have *heard* that T-mobile won't allow BYOD on their band-12 sites if they don't have VoLTE. Don't know if it is true (or where it is true) but figured why not?
6. I decided (for now, at least) to leave boot and recovery stock. So, I am using fastboot to run TWRP or a rooted kernel. Thanks again to j4nn for the method.
Note: I don't plan on allowing FOTA upgrades---I just like passing all the security checks and being able to *see* if updates are available.
That's all. Fine work in development and guides has made life simple and happy for me
Click to expand...
Click to collapse
Now riddle me this cause I'm on Tmo USA as well and I did the hybrid work fine as well but heres the question, does googlepay and banking apps still work with a unlocked bootloader or did you flash a modified kernel to hide the unlocked status.
Sitting on the fence about unlocking mine so I can do a full nandroid before trying out some gsi pie roms infact this is the first phone I haven't unlocked or least put twrp on since my samsung sidekick 4g o.o
kernel with hide-unlock
T_Tank said:
Now riddle me this cause I'm on Tmo USA as well and I did the hybrid work fine as well but heres the question, does googlepay and banking apps still work with a unlocked bootloader or did you flash a modified kernel to hide the unlocked status.
Sitting on the fence about unlocking mine so I can do a full nandroid before trying out some gsi pie roms infact this is the first phone I haven't unlocked or least put twrp on since my samsung sidekick 4g o.o
Click to expand...
Click to collapse
Full disclosure: I don't use Google pay or too many banking apps, so YMMV. But, I am using j4nn's kernel with unlock hidden. (See link in my note 6.) You can flash this, or you can leave in your stock kernel and merely fastboot to this. From what I have seen, it hides most - if not all -- indicators that the phone is rooted and the BL in unlocked.
Does somebody has :
G8441_1310-7123_47.1.A.16.20-R7B_Customized_CE1.ftf ?
Only backup i did not make, and its gone from XperiFirm.
Still have the feeling battery life was better in Oreo, and would be nice for experimenting.
Would be nice.
Thanks in advance.

2020 Guide to Root the XZ1C ?

Hi there !
So for the first time in years of ownership, I am interested in Rooting.
Naturally I searched around here, but could only find 2017 and 2018 threads with many problems and various bugs.
For an April 2020 guy, rooting is stock latest ROM, and interested in keeping stock but go rooted (mostly to block some Android trash) - What is the easiest way, can I have a link that is updated, or a paid tool I can buy and not mess with anything ?
Thanks a lot !
baboon23 said:
What is the easiest way, can I have a link that is updated
Click to expand...
Click to collapse
Crack on - https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510
SXUsr said:
Crack on - https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510
Click to expand...
Click to collapse
Too much mess for my blood !
How much would It be to hire your service via screenshare ?
PM me please
Keep in mind I only want a root so I can disable some stock google trash with F-Droid apps.... I don't really need a new ROM, or do I ?
I rooted mine on stock just a few weeks ago.
All I did was unlock the bootloader, flash TWRP, then flash the latest magisk. I then used Titanium Backup to remove the bloat. It was quick and painless.
Thanks !
Which thread did you use as guide/link glossary ?
I didn't use a guide, just did it based on experience rooting my Sony devices from before. But I can write up something brief. How much knowledge do you have rooting devices?
baboon23 said:
Too much mess for my blood !
How much would It be to hire your service via screenshare ?
Click to expand...
Click to collapse
I wouldn't want to do it that way, and if you do it yourself you'll gain a little experience which makes restoring or further modding easier.
baboon23 said:
Keep in mind I only want a root so I can disable some stock google trash with F-Droid apps.... I don't really need a new ROM, or do I ?
Click to expand...
Click to collapse
If you want to root you need to unlock the bootloader, if you're unlocking your BL then it's advised to backup your DRM keys and restore them after unlocking your BL which is a one time process. Everything you need is in the thread I've linked to above.
Thanks SX. I have seen a lot of your work around here doing searches, and I'm honored that you reply to my question
I will have a crack at it, I have done those things before but I remember not leaving the house for a few days, so it scarred me a bit
Haha
One last question if I may.... Do you believe that installing Lineage with no google on the xz1c is worth it? I guess it's a general question, but what I'm really asking is, should I even bother with rooting for privacy if my end goal isn't to flash Lineage ?
OK, after some more research, I have decided that what I really want to do is just install the 17v LineageOS version for the XZ1C.... It is my understanding it is possible without a root. ?
For sure the bootloader needs unlocking and TWRP to backup/flash correct ?
Super SU, does that make my procedure easier in any way ?
It is my understanding that if I flash a Lineage OS after unlocking via code and flashing TWRP, then the camera and all will still work.
Considering I don't mind binning that phone if I get sick of Lineage (I have like four of those in a box) - Can I skip the TA backup and restore ?
Apologies for the newb questioning, just trying to "get the hang" of it so I actually understand what i'm doing rather than just follow guides.
I'm a bit older than all you guys so forgive me
I'm running lineage 16.1 on root with unlocked bootloader without restoring TA. But I didn't care about preserving the keys. Yes camera works great and everything is super stable.
You don't have to root lineage so if you need help best to narrow down what exactly you want to do as there are many possibilities.
betacrypt said:
I'm running lineage 16.1 on root with unlocked bootloader without restoring TA. But I didn't care about preserving the keys. Yes camera works great and everything is super stable.
You don't have to root lineage so if you need help best to narrow down what exactly you want to do as there are many possibilities.
Click to expand...
Click to collapse
Absolutely, you're right !
I will be as specific as I can:
Sony abandoned the XZ1C, so I want to swap to Lineage OS with a full heart with no Gapps (i'll manage).
Here is what I understand tell me if I am correct:
1. Unlock bootloader via sony website
2. Flash latest TWRP
3. Use it to flash 17.1 Lineage OS from the genius dude (mod punk?)
4. Happy days
5. If modpunk updates it, will I be able to update with no reformatting ?
baboon23 said:
Absolutely, you're right !
I will be as specific as I can:
Sony abandoned the XZ1C, so I want to swap to Lineage OS with a full heart with no Gapps (i'll manage).
Here is what I understand tell me if I am correct:
1. Unlock bootloader via sony website
2. Flash latest TWRP
3. Use it to flash 17.1 Lineage OS from the genius dude (mod punk?)
4. Happy days
5. If modpunk updates it, will I be able to update with no reformatting ?
Click to expand...
Click to collapse
Yep that's about right. Unlock bootloader with Flash Tool by getting unlock code from Sony. Flash TWRP in fastboot mode. Boot to TWRP and flash lineage 17.1. If you don't need gapps you're good to go.
As for lineage updates probably best to check with the thread. Usually you can dirty flash, i. e. flash new version over the old and it should be ok. Lastly check to see if they're are any major bugs with 17.1. Since it's so new there could be issues. 16.1 is smooth fast and stable if you ever need to go back to it.
betacrypt said:
Yep that's about right. Unlock bootloader with Flash Tool by getting unlock code from Sony. Flash TWRP in fastboot mode. Boot to TWRP and flash lineage 17.1. If you don't need gapps you're good to go.
As for lineage updates probably best to check with the thread. Usually you can dirty flash, i. e. flash new version over the old and it should be ok. Lastly check to see if they're are any major bugs with 17.1. Since it's so new there could be issues. 16.1 is smooth fast and stable if you ever need to go back to it.
Click to expand...
Click to collapse
Superb, thank you so much ! What a wonderful community. I feel like im stealing. I will be sure to donate !
One question, may I use adb tools for the bootloader ?
No problem. That one I'm not sure about. I've only used flash tool myself but adb tools should work with the right commands.
Yay for me !
Bootloader unlocked, onto recovery and LOS
I did it !
Thanks yall
I get this horrible " please lock the bootloader" greeting when I turn on the device, for 5 seconds.
Is that normal for everyone ?
baboon23 said:
Considering I don't mind binning that phone if I get sick of Lineage (I have like four of those in a box) - Can I skip the TA backup and restore ?
Click to expand...
Click to collapse
You've got 4 XZ1Cs in a box?
baboon23 said:
I get this horrible " please lock the bootloader" greeting when I turn on the device, for 5 seconds.
Is that normal for everyone ?
Click to expand...
Click to collapse
It is yes, you'll have to live with that unfortunately. In regards to the TA, I would have taken the time to back them up, that'll matter should you wish to return to stock. It's better to have it and not need it than to need it and not have it. But you've achieved what you wanted to which is all that matters. :good:
Thank you sir !
You're probably right, I just couldn't be bothered... Sometimes 20 minutes more is like a life long more
Well, now that all is installed....
So when modpunk stopps working on the project (like sony stopped working on the xz1) - Will it be safe to just continue using the phone without updates at all ?
Or is the eventual doom of all ROM Flashers is to come back to stock (but then, it doesn't get updates anymore also...)
So does it matter in which platform I remain outdates ?
Re the XZ1's, I knew that this was going to be the last proper small phone so I made sure to stock. I plan to carry these into 2022 …….
Problem is, I think even in box without, the batteries will die out. So I'm not sure how smart I was when I got several.
All in all, for all phones I paid less than one iPhone so I'm pretty happy, but hopefully a lab can change the batteries on them.
baboon23 said:
Thank you sir !
You're probably right, I just couldn't be bothered... Sometimes 20 minutes more is like a life long more
Well, now that all is installed....
So when modpunk stopps working on the project (like sony stopped working on the xz1) - Will it be safe to just continue using the phone without updates at all ?
Or is the eventual doom of all ROM Flashers is to come back to stock (but then, it doesn't get updates anymore also...)
So does it matter in which platform I remain outdates ?
Re the XZ1's, I knew that this was going to be the last proper small phone so I made sure to stock. I plan to carry these into 2022 …….
Problem is, I think even in box without, the batteries will die out. So I'm not sure how smart I was when I got several.
All in all, for all phones I paid less than one iPhone so I'm pretty happy, but hopefully a lab can change the batteries on them.
Click to expand...
Click to collapse
I believe it is recommended to charge lithium-ion batteries fully every other month or so to keep it healthy.
If you are rooted I recommend checking out the ACC magisk module and controller app. This allows the phone to stop charging when the battery level has reached a certain level. In the long run keeping your device charged between I think 80% - 20% will increase your battery longevity by 200% (sorry I don't remember the exact study this was from).
And I agree the XZ1c is the last proper small phone. I've rebuilt mine from one sold for parts from eBay and now it feels like new.
About the security:
If you want to you can keep a look out for specific vulnerabilities in Android after the last security patch released for the custom rom.
https://source.android.com/security/bulletin
But in general by not connecting to sketchy WiFi hotspots, being un-rooted, having se-linux on enforcing, and running af-wall (requires root permissions) or another firewall you should be good for a while.
I think it really depends on what security issues get discovered in the future and what vulnerabilities your specific use case opens you up to.
Hi guys !
What about DRM key backup ?
I need help if you have a solution
https://forum.xda-developers.com/xp...de-to-install-lineageos-17-1-scratch-t4136195
Thanks you !

Categories

Resources