Database Develop

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!

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.

bootloader

Is it possible to unlock?

At this moment, no.

You will know as it'll be reported here very early. There are some third party companies that do it. Some are cheaper than others.
For the moment, there is nothing..
Sucks I know

I asked this before on another similar thread and didn't get a response. Is it possible to dump the bootloader from either an unlocked or locked phone to analyse it for potential vulnerabilities either in how it handles the unlock code, or more generally that would allow a user to soft-mod unlock the phone? I know for the 5th, 7th, and 9th gen Fire 7 tablets exploits were found in the LK part of the bootloader which eventually allowed for a customised version of TWRP to be flashed onto the devices, and later LineageOS. If we could dump the current Huawei bootloader surely we could try to find if there are any similar exploits?

I am found metod but it needs mrt dongle((

Tbh custom roms aren't really important anymore. Google is already ruining android everytime a new update comes around, like the overlay feature that was introduced in oreo but then removed for no reason.
Besides EMUI is already optimised for the chip so, again, no reason for custom roms and/or rooting (unless you want to remove bloatware but that can be solved via ADB)

The Restless Soul said:
Tbh custom roms aren't really important anymore. Google is already ruining android everytime a new update comes around, like the overlay feature that was introduced in oreo but then removed for no reason.
Besides EMUI is already optimised for the chip so, again, no reason for custom roms and/or rooting (unless you want to remove bloatware but that can be solved via ADB)
Click to expand...
Click to collapse
I am need it for root and lineage os

How to make copies of the firmware on your phone (brand new XZ1 Compact)

Hello,
I have a new XZ1 Compact that has never been updated. I only started using it last week even though I bought it at least a year or so ago. I was going to get around to updating, but I thought it would be a good idea to make copies of the firmware first.
Is it possible to do this? If so, how do I go about it?
At the moment the phone is on 47.1.A.2.324 and the region is 1308-4378_R11B (I believe this is Taiwan, but I'm using it in Australia). I have seen a few mentions of 47.1.A.16.20 being a good firmware version where people wanted it, but it can no longer be downloaded from Xperifirm.
Would old firmware versions be something people would be interested in?
Thanks in advance for any replies.

@patch18, trying to backup a copy of fw is not that useful, but it is possible, even if the phone is still locked - see here.
The fw version currently on your phone seems to be exactly one of the two versions supported by the renoroot exploit for xz1c, so you most likely would not even need to reflash it to use renoroot exploit.
The most important thing is to backup TA partition from your still locked phone in order to preserve sony drm keys that get lost if you eventually unlock bootloader of the phone (just follow the above linked guide for that, you may not finish by unlock if not desired, just backup the TA if you want to backup something important from your phone).
There are btw backup tools in the linked thread too that can backup all partitions of your phone, but the backup is not possible to restore easily, particularly not on locked phone.
Stock fw downloaded from sony (having .sin files in it) is more useful as that can easily be flashed even to a locked phone.
Your current version is also downloadable from the above linked thread - only in CE1 customization.
You may backup your 'oem' partition to preserve your current customization (possible to do with simple 'dd' command similarly as TA partition backup).

patch18 said:
At the moment the phone is on 47.1.A.2.324 and the region is 1308-4378_R11B (I believe this is Taiwan, but I'm using it in Australia). I have seen a few mentions of 47.1.A.16.20 being a good firmware version where people wanted it, but it can no longer be downloaded from Xperifirm.
Click to expand...
Click to collapse
It depends what you want. If you're not interested in rooting and modding your device, you don't need to do anything special. Just updtate your device trough regular OTA till you arrive to your desired firmware version. I.e. if you want that 47.1.A.16.20 just stop updating your phone after you receive it.
That 16.20 firmware is desired by many because it's bugfree and it's last Oreo firmware.
Saying that, it's also a good idea to first backdrop TA partition in case you change your mind in the future and decide to unlock and root it. j4nn explained that.

Hi guys,
Thank you both for your input. I have read over the link provided by j4nn. I think I understand it for the most part, but I will attempt it over the weekend in case something was to go wrong (highly likely with my luck).
I recalled when I had both Lollipop and Marshmellow on my Z3 Compact there was a way to make your own customised firmware and I was wondering if it was possible with the XZ1 Compact hence my original question. It seems like you can now only download Pie firmware from Xperifirm.