Rooting my new Xperia XZ1 Compact 47.2.A.8.24 - Sony Xperia XZ1 Compact Questions & Answers

Hi everyone,
Please forgive my ignorant post, it has been a very long time since I was here.
I've recently acquired an Xperia XZ1 Compact running Android 9 Pie 47.2.A.8.24. This phone has a stupid amount of bloatware and unnecessary apps that cannot be removed, so I was considering rooting it and then installing something like Titanium Backup, to remove all the rubbish.
After doing a bit of research, it seems rooting it can cause many problems, a big one being lack of or reduced camera functionality, among other things. This is a big issue and I don't want to dumb down the great specs of the phone. In the past I rooted phones with no consequences to functionality - it was only when custom ROMs were installed that problems started to occur.
So essentially my question is, how safe is it to root my XZ1C?
Cheers

Read this DRM backup/restore guide by j4nn: https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510
Read at least the first post CAREFULLY.
So basically you need to downgrade to an old firmware, backup the drm keys with j4nn's tools, unlock bootloader, restore the keys, update back to a new firmware with newflasher and install magisk to root (either via TWPR or with j4nn's modified kernel, which is prerooted via magisk: https://forum.xda-developers.com/xp...oted-kernel-hiding-bootloader-unlock-t3898711 ).
It might seem a lot to do but if you read the instructions, it's not hard. Just remember to back up the drm keys before unlocking bootloader. When you have the keys (TA-partition) backed up, you can restore them even if you make some mistake, but unlocking without backing them up will get them lost forever.

vofferz said:
Read this DRM backup/restore guide by j4nn: https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510
Read at least the first post CAREFULLY.
So basically you need to downgrade to an old firmware, backup the drm keys with j4nn's tools, unlock bootloader, restore the keys, update back to a new firmware with newflasher and install magisk to root (either via TWPR or with j4nn's modified kernel, which is prerooted via magisk: https://forum.xda-developers.com/xp...oted-kernel-hiding-bootloader-unlock-t3898711 ).
It might seem a lot to do but if you read the instructions, it's not hard. Just remember to back up the drm keys before unlocking bootloader. When you have the keys (TA-partition) backed up, you can restore them even if you make some mistake, but unlocking without backing them up will get them lost forever.
Click to expand...
Click to collapse
Thanks for the helpful info, I'll give that post a read. I'm not great with 'technology', so if it's too complex I'll just have to put up with the bloatware.
Is the information in the post still valid given that it's almost a year out of date?

jjl5590 said:
Thanks for the helpful info, I'll give that post a read. I'm not great with 'technology', so if it's too complex I'll just have to put up with the bloatware.
Is the information in the post still valid given that it's almost a year out of date?
Click to expand...
Click to collapse
The first post has been updated to contain all the newest information. That's why I don't recommend reading the whole thread, unless you want a historical study about the development of the process.
If it's just the bloatware you want to get rid of and don't need root access, you might be better off with disabling the apps. Some of them can't be disabled from settings, but you can do it via ADB. https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/

vofferz said:
Read this DRM backup/restore guide by j4nn: https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510
Read at least the first post CAREFULLY.
So basically you need to downgrade to an old firmware, backup the drm keys with j4nn's tools, unlock bootloader, restore the keys, update back to a new firmware with newflasher and install magisk to root (either via TWPR or with j4nn's modified kernel, which is prerooted via magisk: https://forum.xda-developers.com/xp...oted-kernel-hiding-bootloader-unlock-t3898711 ).
It might seem a lot to do but if you read the instructions, it's not hard. Just remember to back up the drm keys before unlocking bootloader. When you have the keys (TA-partition) backed up, you can restore them even if you make some mistake, but unlocking without backing them up will get them lost forever.
Click to expand...
Click to collapse
How to root android 9 xperia xz1 compact 2021

Related

Couple of questions before attempting root

Hey guys,
So before I go ahead an attempt to unlock my bootloader and root my phone, just wanted to clear a couple of things up first.
This is my first Huawei device, previous one was a Sony, so I'm a little unfamiliar with a few things.
1. Is unlocking the bootloader required for root? If not, could someone point me in the direction of a guide to root only?
On the Sony, as long as I had a compatible firmware, I could root without unlocking the bootloader.
2. Will I lose any DRM Keys, proprietary features (Force Touch, Themes etc) through unlocking the bootloader and/or rooting? If so, can these be restored afterwards, while retaining root?
Again, with the Sony, unlocking the bootloader would result in losing DRM Keys related to visual enhancements, and were required to be backed up (via TABackup) prior to unlocking the bootloader. These could then be restored after root, and function as normal.
3. If you do lose features, and they can't be restored while keeping root. If I flash a stock ROM back on, losing root in the process, will these features also be restored?
Thanks
djyoshii said:
Hey guys,
So before I go ahead an attempt to unlock my bootloader and root my phone, just wanted to clear a couple of things up first.
This is my first Huawei device, previous one was a Sony, so I'm a little unfamiliar with a few things.
1. Is unlocking the bootloader required for root? If not, could someone point me in the direction of a guide to root only?
On the Sony, as long as I had a compatible firmware, I could root without unlocking the bootloader.
2. Will I lose any DRM Keys, proprietary features (Force Touch, Themes etc) through unlocking the bootloader and/or rooting? If so, can these be restored afterwards, while retaining root?
Again, with the Sony, unlocking the bootloader would result in losing DRM Keys related to visual enhancements, and were required to be backed up (via TABackup) prior to unlocking the bootloader. These could then be restored after root, and function as normal.
3. If you do lose features, and they can't be restored while keeping root. If I flash a stock ROM back on, losing root in the process, will these features also be restored?
Thanks
Click to expand...
Click to collapse
1) I used the SRK Tool (http://forum.xda-developers.com/p9-plus/development/tool-srk-tool-huawei-bootloader-root-t3405999) and it showed step by step on rooting. Unlocking bootloader seems to be one of the steps before rooting. Maybe you can ask somboons about it.
2) For me, unlocking the bootloader basically resets my phone. And added a warning just before the phone bootup to android (from cold state or off state) that the bootloader has been unlocked and the phone is not trusted now. Just need to restore the apps and other data through the HiSuite backups after unlocking and rooting seems to be fine. Not sure about DRM keys, and others as didn't try those out before doing bootloader unlock. But I did lost my remote set up as it was not part of the HiSuite's data backup.
3) Do a backup with HiSuite should be able to help you. Just need to identify in the HiSuite that the apps and their data is being backed up.
prismfire said:
1) I used the SRK Tool (http://forum.xda-developers.com/p9-plus/development/tool-srk-tool-huawei-bootloader-root-t3405999) and it showed step by step on rooting. Unlocking bootloader seems to be one of the steps before rooting. Maybe you can ask somboons about it.
Click to expand...
Click to collapse
Thanks mate, I did have a look at that thread as well, and another (less detailed) post. Was just wanting to confirm if there was any other method without need for bootloader unlocking. Figure the less things to modify, the less chance of something going wrong, which has worked well for me so far.
prismfire said:
2) For me, unlocking the bootloader basically resets my phone. And added a warning just before the phone bootup to android (from cold state or off state) that the bootloader has been unlocked and the phone is not trusted now. Just need to restore the apps and other data through the HiSuite backups after unlocking and rooting seems to be fine. Not sure about DRM keys, and others as didn't try those out before doing bootloader unlock. But I did lost my remote set up as it was not part of the HiSuite's data backup.
Click to expand...
Click to collapse
Any way to remove that message while retaining root? Sounds similar to the 'yellow triangle' back when I had an S2, but that was able to be removed, is this the same?
Not too worried about backing up apps & data at the moment, I haven't fully set up my phone as I realised it would most likely be lost upon rooting. But thanks for the heads up!
prismfire said:
3) Do a backup with HiSuite should be able to help you. Just need to identify in the HiSuite that the apps and their data is being backed up.
Click to expand...
Click to collapse
Sorry I was more thinking along the lines of, if any P9+ exclusive features were to be lost during root, could they easily be restored simply by flashing a stock ROM again? Apps & app data seem to be easy enough to restore via HiSuite/Titanium etc
djyoshii said:
Thanks mate, I did have a look at that thread as well, and another (less detailed) post. Was just wanting to confirm if there was any other method without need for bootloader unlocking. Figure the less things to modify, the less chance of something going wrong, which has worked well for me so far.
Any way to remove that message while retaining root? Sounds similar to the 'yellow triangle' back when I had an S2, but that was able to be removed, is this the same?
Not too worried about backing up apps & data at the moment, I haven't fully set up my phone as I realised it would most likely be lost upon rooting. But thanks for the heads up!
Sorry I was more thinking along the lines of, if any P9+ exclusive features were to be lost during root, could they easily be restored simply by flashing a stock ROM again? Apps & app data seem to be easy enough to restore via HiSuite/Titanium etc
Click to expand...
Click to collapse
The orange colored message i read from somewhere that it's Android security implementation standard or something. There's red message also which renders the whole phone can not boot in unless being reset.
In terms of the exclusive apps, not that I know of. Checked with my friend who kept her device as it is, without all the unlock and rooting, and compare with my device which went through and upgrade, unlock and a rooting process - no missing apps noticed.
Thanks guys
prismfire said:
The orange colored message i read from somewhere that it's Android security implementation standard or something. There's red message also which renders the whole phone can not boot in unless being reset.
In terms of the exclusive apps, not that I know of. Checked with my friend who kept her device as it is, without all the unlock and rooting, and compare with my device which went through and upgrade, unlock and a rooting process - no missing apps noticed.
Click to expand...
Click to collapse
I read ur conversation and I have been wondering if it's safe so thank you. But I still have 1 question "if I change my oem can I still use my 2 sims"?
prismfire said:
The orange colored message i read from somewhere that it's Android security implementation standard or something. There's red message also which renders the whole phone can not boot in unless being reset.
In terms of the exclusive apps, not that I know of. Checked with my friend who kept her device as it is, without all the unlock and rooting, and compare with my device which went through and upgrade, unlock and a rooting process - no missing apps noticed.
Click to expand...
Click to collapse
So i've successfully rooted the phone, and yeah I get that 'your device has been unlocked and isn't safe' message on boot. It's not too much of a bother, besides being unsightly, but I don't really reboot my phone too often anyway.
I haven't noticed anything missing either, a few minor bugs have started to appear, but that might have to do with Xposed (I would guess).
Thanks for the advice & help!
Abdo2 said:
I read ur conversation and I have been wondering if it's safe so thank you. But I still have 1 question "if I change my oem can I still use my 2 sims"?
Click to expand...
Click to collapse
Dear Abdo2,
I'm not knowledgeable about the term oem here.
But if it is an issue of dual sim usage, I presume it's built into the ROM? What I know is all P9+ are hybrid dual sim, so it should be part of the ROM that you have.
I'm using VIE-L29C636B170. And it have the dual sim support in-built...although I've not used it yet.
See if anyone knowledgeable to your question passing by here can answer you. If not, maybe you can try the question & answer thread. Or post as another new thread if really no one got your question.
Regards.
---------- Post added at 02:39 PM ---------- Previous post was at 02:29 PM ----------
djyoshii said:
So i've successfully rooted the phone, and yeah I get that 'your device has been unlocked and isn't safe' message on boot. It's not too much of a bother, besides being unsightly, but I don't really reboot my phone too often anyway.
I haven't noticed anything missing either, a few minor bugs have started to appear, but that might have to do with Xposed (I would guess).
Thanks for the advice & help!
Click to expand...
Click to collapse
Dear djyoshii,
Good to know.
About the security message, one of it is mentioned here:
https://source.android.com/security/verifiedboot/verified-boot.html
For minor bugs, I'm not sure what you have. I've 3 games and 1 app that behaves not like when I used my previous phone (on Android 5.0). That's around 3-5% of all the apps that I used (meaning, majority works fine). Of those some of them related to Android 6.0 issue (actually the apps not updated for the Android version well). So, for me generally I would think it's marshmallow thing.
Regards.
Hi,
long time htc user (always totally unlocked) but looking to get a p9 plus for my wife (this is the important part).
can someone give me a simple answer...
if i only root the phone (for titanium backup mainly and maybe some cosmetic mods) will i be able to unroot it and return it under warranty?
phones here in Dubai are all unbranded so no problems there.
I have no need to unlock bootloader (yet )
gazzacbr said:
Hi,
long time htc user (always totally unlocked) but looking to get a p9 plus for my wife (this is the important part).
can someone give me a simple answer...
if i only root the phone (for titanium backup mainly and maybe some cosmetic mods) will i be able to unroot it and return it under warranty?
phones here in Dubai are all unbranded so no problems there.
I have no need to unlock bootloader (yet )
Click to expand...
Click to collapse
Dear gazzacbr,
From what I tried (been a while since I last did this), one will have to unlock the bootloader first before rooting. Apparently rooting is the last step of the whole process (if you are using the SRK tools). Now, to go back to the status of unrooted, I just use the superSU's total unroot option to unroot. And to go further back to bootloader, there is an option within SRK tool but my last attempt failed to relock the bootloader back. Didn't spend so much time to play around with the unlocking the bootloader after that. So, I just use as is - unlocked bootloader with no root.
One thing you need to note, for titanium backup, I end up just using their own desktop application called HiSuite. It does backup app and app data for you. Not system apps' data though. For theme customisation, MIUI do have a friendly Themer app that you can use to change the look. The corresponding theme files (*.hwt) are zipped, so you can always use 7zip to open and edit the assets inside to the one that you want.
Ok, thanks for the good info @prismfire. As long as it could be rooted sometime later then thats fine. Will pick up one this weekend.
Am going to be jealous though as I guess it's a step up from my 'old' M8
Sent from my HTC One_M8 dual sim using XDA-Developers mobile app

What's the easiest way if you only want root access, nothing else?

First of all, I have been using custom kernels and later rooting since Pocket PC 2002/Merlin, and I now have bought my first Sony (after just about every other brand of Android phone, no particular reason why I never had a Sony since the SE T68) because it's the only phone I can use with salt water spray on the screen and wet fingers. I do a lot of lobster, crayfish and crab fishing with traps and use an app called Fishing Poins to keep track of my pots and what I get where. Coming from Samsung (S5 was the latest I had) the rooting of a Sony seems rather cumbersome, but I have a few apps that need root access. LIke Air Audio to play music through an Airplay system. DLNA is useless to me, I want to stream the audio that I'm using on the phone directly to the whole house systen.
So can somebody please tell me what I do to get root access on Nougat (which my phone upgraded to before I saw that's what was happening, and no, I'm not big on reading long explanation screens, if it's a new phone and an official upgrade I am used to just doing it before I root on Samsung phones, since I have to unroot to install them later) and nothing else? For now I don't want to use any custom kernels or recovery, if I can avoid it. Just stock, rooted, like I could on my S5 (and Note 2, S4 Active and so on), please!
I did attempt the KingRoot app, but it didn't work. Also I have read a bit about that app that doesn't seem to good (Chinese spy fator app), so I did a full reset after the failed attempt. But if there's something similar that would be the perfect way of doing this. Of course I'm no stranger to ADB, so hooking it up to my pc is not a problem either.
1. Downgrade to any version of stock Marshmallow firmware with Xperifirm and Flashtool. Wipe everything and Exclude nothing (but *.ta - if any). Do not use FSC script! << FSC is now mandatory!
2. Backup your device's TA partition with Universal TA Backup tool.
3. Flash Nougat firmware (again with Xperifirm and Flashtool). Wipe everything and Exclude nothing (but *.ta - if any).
4. Unlock your device's bootloader
5. Follow this instructions to create/flash a custom kernel with root, and also DK.ftf (to fully reactivate sony's drm keys, which is wiped when bootloader is unlocked).
Anyway, try it at your own risk!
Thanks! So that's the method, which of course means deleting everything I've set up on the phone. Is there a chance there may be an easier, less destructive way during the next month or so? I can do without root access for that long.
oh, btw, by "custom kernel" do you mean that it will not be the original setup for the phone? I've been betatesting kernels on many devices, but nowadays I only want a phone that works without any hitches, and I want access to the official updates. That was easy on the Samsung phones, but maybe Sony is more different than I thought?
Oh, btw, maybe it is explained in the long post you directed me to, but I recently had an eye operation, and I would appreciate a shorter answer, before I get to the "how to", which takes me a while to read right now...
NEVER MIND THIS MESSAGE! Now I understand what Xperfirm is...
Also where would be a safe place to download ROMs from? Both the downgrade ROM and the Nougat ROM? I now really wish I hadn't let the thing upgrade before I took the TB backup (I'm still a bit unsure as to why I need that, I don't use any media with any form for DRM, but I guess better safe than sorry).
Mastiff said:
NEVER MIND THIS MESSAGE! Now I understand what Xperfirm is...
Also where would be a safe place to download ROMs from? Both the downgrade ROM and the Nougat ROM? I now really wish I hadn't let the thing upgrade before I took the TB backup (I'm still a bit unsure as to why I need that, I don't use any media with any form for DRM, but I guess better safe than sorry).
Click to expand...
Click to collapse
As far as I know there's no danger to download through Xperifirm, you need TA for guarantee reasons (if your phone need repair, not everywhere but for safety)
THanks, yeah. I have managed to read a bit and found out that Xperifirm downloads from the official Sony servers. Pain in the ass downloading, it breaks the download every couple of minutes. But that's probably Sony's servers, not the program. As for warranty, that's no problem in Norway since we have very strong consumer rights here. If an error can not be prooven to stem from rooting or other software stuff, it will be fixed. If I remember correctly Apple tried really hard to battle with the consumer rights officials about jailbreaking, but they had a very bloody defeat.
Seems like I have a problem. The Telenor Nougat ROM doesn't have a loader, according to Flashtool. Neither do the two other ROMs I have downloaded so far, but I'm trying again with a third, which doesn't have the "customised" moniker. So I hope that has a loader. But how do I upgrade again to Nougat, with the Norwegian version, when the Telenor ROM doesn't have a loader?
Mastiff said:
Seems like I have a problem. The Telenor Nougat ROM doesn't have a loader, according to Flashtool. Neither do the two other ROMs I have downloaded so far, but I'm trying again with a third, which doesn't have the "customised" moniker. So I hope that has a loader. But how do I upgrade again to Nougat, with the Norwegian version, when the Telenor ROM doesn't have a loader?
Click to expand...
Click to collapse
if your phone is locked(Bootloader),fix it using Xperia Companion..that way it upgrades automatically to Nougat.
if not,lock it using Flashtool first.
Well, the message was kind of badly worded, because I need to downgrade first of all. So I'm at the moment trying to get it to MM without messing up the TA partition. So anyway, this thread has been followed by others, I think this can be considered solved since there is only one way to get root on these phones.
What would be the best approach to rooting if you unlock your bootloader before learning about TA backup? I have since downgraded, done TA backup, upgraded, flashed TWRP, flashed SU/Magisk/phhSu, and saw two green checks in Magisk. Tried to continue to get the three checks by installing Sony framework v1 through Magisk and then Andros plus kernel, but got stuck on Sony screen on boot up. So I repeated steps and stopped after I got two checks, however after long use and simple phone restart, I lost root. Please HELP!

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.

Can't restore DRM functions after unlocking bootloader, backingup DRM and flashingrom

Hi,
So I've tried every tutorial that has been published out there in regards to restoring the DRM functions on my Xperia Z3+ (Single Sim version) but to no avail.
I tried the method posted by najoor https://forum.xda-developers.com/xperia-z4/general/guide-safe-bootloader-unlock-restore-t3386915 followed every step (Managed to back up my DRM keys, unlocked bootloader successfully). I then flashed a stock Marshmallow rom that was posted on the thread by wolfaas12345 https://forum.xda-developers.com/xperia-z4/general/nougat-firmware-z3-e6553-6533-t3545481 (I flashed the 32.1.A.1.185 one that's posted there).
Then I followed the instructions to emulate the DRM keys as posted in the najoor thread (2- How to emulate DRM keys and/or root and/or add recovery after unlocking the bootloader.). It looks like everything seems to be working (I'm able to go to Recovery etc). But then when I go check to see my DRM functions, they aren't restored. (Camera is still emitting lots of noise, x-reality isn't added back). I double check it by going into Service Mode by dialing *#*#7378423#*#* then into Service Tests -> Security and still see the errors there.
I gave up using this method eventually, then found out another thread posted by jimRnor https://forum.xda-developers.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672 that has a drmrestore zip file for xperia z3+. I flash it using TWRP recovery and it looked like it was flashed successfully, yet when I go check whether the DRM functions are restored, they aren't.
I'm at a loss here now. I don't know where am I going wrong or what step am I doing wrong. I would greatly appreciate any help here if someone can guide me to the correct steps to restoring my DRM functions on my phone.
Thanks!

Full backup and restore of ROM and data

Hi, I'm looking for an overall guide how to do a full backup and restore of a currently running ROM which includes also all data.
I want to be able to do some tryouts with another ROM and if anything fails or doesn't suite my needs I would like to simply go back to my current setting.
With some research in this forum I already found the follwing related threads. As this seems to be a quite generic topic I did the research mainly in the "crossdevice" section.
Backuping & Restoring IMG files W/O PC
requires root; guide without root is announced but not mentioned
some hints in the direction of "nandroid" but no detailed workflow
Lock/Unlock/Relock Bootloader Using TWRP With DRM keys
only about the bootloader
obviously there are more specific guides in the XZ1c section
All Things XPERIA; Debranding; Rooting & More...
good overview of basic skills regarding flashing, rooting, backup TA, etc.
nothing about full backup data or current ROM
nothing about restore a full backup
Backup your stock ROM without flashing Custom Recovery.
good short description to backup ROM
does this also work for data?
unsure if this is directly applicable to XZ1c
nothing about restoring ROM or data
I would be very pleased if someone who are familiar with this device can give some hints for my questions.
The long story:
Since Sony stopped to distribute security updates for XZ1c I feel forced to consider an alternative OS. I would like to give LinageOS 17.1 a try. Two years ago I had some good experience with that OS on a Z3c, but with th XZ1c it seems to be more complex especially regarding DRM keys etc.
I'm also using banking and payment apps which often stop working with alternative ROMs. Maybe there are some tricks to pass safetynet but at the end you have to really evaluate all your apps to be sure that all is running as expected. If that evaluation fails I don't want to spend much time to return to the current setting which I'm actually very satisfied with. Only missing security updates makes me think more and more of an alternative.
Thank you very much for any hint.
Best regards,
Leo
Maybe someone read this and can at least answer some questions. I'm completely not familiar with the processes so maybe my questions sound stupid. Sorry for that.
Is it possible to use fastboot to boot (not install) into TWRP and perform a complete Backup of data there without unlocking bootloader?
Gesendet von meinem G8441 mit Tapatalk
The easiest and fastest way is to perform a full backup using TWRP and you need an unlocked bootloader to do that.
Thank you for that answer.
I've read in Lock/Unlock/Relock Bootloader Using TWRP With DRM keys
Note - Unlocking bootloader for first time will wipe out your whole data including internal memory
Click to expand...
Click to collapse
So the "easy" way using TWRP seems not to work for my use case. I really want to backup the data before wipe
leo2100 said:
Thank you for that answer.
I've read in Lock/Unlock/Relock Bootloader Using TWRP With DRM keys
So the "easy" way using TWRP seems not to work for my use case. I really want to backup the data before wipe
Click to expand...
Click to collapse
You'll need to use Xperia Backup and/or Googles backup feature. A whole rom backup without root or unlocking the bootloader isn't an option.
SXUsr said:
A whole rom backup without root or unlocking the bootloader isn't an option.
Click to expand...
Click to collapse
So is it generally not possible to backup my data before first time flashing a custom ROM to restore it later to the current "official" state?
What about the temp root exploit? May this also allow a dump of the data partition like it does with the TA partition?
j4nn said:
Tools to backup TA partition (drm keys) of Xperia XZ1 Compact
View attachment 4633124
by j4nn
https://j4nn.github.io/
​
Click to expand...
Click to collapse
Gesendet von meinem G8441 mit Tapatalk
@leo2100, you can backup data (or firmware partitions) via an exploit having bootloader still locked. But for that you need to run exploitable fw version.
If you are on pie, you would need to downgrade to oreo and that would result with full data erase. You could backup few partitions that are not part of stock fw.
It is question if there is anything useful apart from TA partition - maybe persist partition, but I am not sure if it is possible to restore it.
There is a new temp root exploit that allows to get temp root with the latest oreo firmware (47.1.A.16.20):
https://forum.xda-developers.com/cr...1c-xz1-xzp-temp-root-exploit-via-cve-t4046641
j4nn said:
If you are on pie, you would need to downgrade to oreo and that would result with full data erase.
Click to expand...
Click to collapse
Damn, that is not what I wanted to read
Ok, so at all I need to backup my data with the stock Pie built in abilities. So even if I return back to the stock Pie ROM I have to setup all apps again (of course depending on backup abilities of each app).
Is it correct, that once I did the backup of TA partition and restored it after unlock, I can also flash stock pie again but with the ability to boot into TWRP with fastboot?
Do I have to expect any restrictions compared to my current setup (running last Pie with locked boot loader)?
I ask this because I've had many troubles with my Z3c regarding safety checking apps like banking or 2FA (two-factor-authentification).
You see, I'm still not very confident to do this irreversible step of unlocking
@leo2100, you may get trouble to pass google/playstore certification - see here for more details.
If that is important to you, you may be better not to unlock BL.
Thank you for the hint.
The reason why I still worry about unlocking is that it is irreversible and may causes issues that I cannot see at the moment [emoji53].
So as this is really only a one way thing, I still will stay with the current setup and stop this "project", at least for now.
leo2100 said:
will stay with the current setup and stop this "project", at least for now.
Click to expand...
Click to collapse
That is a wise decision in your case! I can tell you that the custom ROMs for the XZ1 are not at the same level as Lineage for the old Sony smartphones were. Do yourself a favor and stay stock and you will have no problems with banking apps.
I came up to the same problem!!
I am trying to undelete some accidentally deleted photos and using aany undelete comerscal utility expects a rotted phone in order to see internal XZ1 memory!
Any ideas? as I cannot see a solution how to get DRM keys backup before OEM UNLOCK!!

Categories

Resources