Develop Bugs

Sony Based ROMs

Good Day.
Got my z1c a couple weeks ago and am loving it. Managed to root it. I have yet to pull the trigger on unlocking the bootloader. I have seen lots of AOKP and CM based roms but are there any Sony Based Modified Roms to keep the Camera processing intact? I am not the biggest fan of CM although I am sure its improved over the years but the camera and battery issues are of no interest to me that I keep reading in the majority of the roms posted. So can you please point me to some Sony Based Modified Roms (if they even exist)? Aslo, do I have to unlock the bootloader to put on another Sony based ROM? Lastly, I do have to unlock the bootloader if I want TWRP or CWM correct? TIA!

You can find some custom Sony Roms in original dev section. Usually you don't need unlocked bootloader for Sony roms.
You also don't need unlocked bootloader for recovery, see for example dualrecovery http://forum.xda-developers.com/showthread.php?t=2261606

You could try this if you're up to a bit of experimenting: http://forum.xda-developers.com/showthread.php?p=54330224
I've been using RomAur 9.1 for quite a while now without any issues, but with a locked bootloader you'd lose recovery if XZDualRecovery still isn't working. Somebody would have to try if a current version works, I'm using encryption which makes it a bit complicated for me otherwise I'd try it myself.

Thank you both for your help. I installed recovery without issue. Now to find a nice fluid ROM. It is difficult coming from Google Edition Roms!!!!

[Q] Arc S android update suggestions (for backup and space issues?) - noob :$

Hi,
I'm having problems with space and the general speed of my Xperia Arc S so the time has come to finally upgrade from Sony's version of Android 2.3 in hope that it will improve things.
I've kind of avoided this so far as I don't really know the best way to back-up things.
I want to back up to my computer - not to the internet.
I am guessing that for the applications that I would like to back up I would need to back up both their APK files and whatever their setting files are. I guess there are also some system settings to back up (but then these are less important).
A problem I have always had is space on the phone - it has very little storage space and although I try and move everything to the SD card, a lot of it doesn't seem to be able to be moved.
Things like simply the Google Play services take up loads of space! I don't even really have that much on there - mainly just whatsapp.
The phone is stock although I have checked in the service menu and it says that I can unlock the bootloader. Part of the reason I didn't upgrade to Sony's version of Android 4 was because I heard that it locks the bootloader and I didn't know if this was bad.
What is the bootloader unlock for? Is it for loading custom roms? As i thought you could do this even if it was locked? Or is it for rooting?
So yer, I guess I am looking for recommendations for a CFW to suit my needs. Priorities are that it works and i'm guessing the latest android version possible would be best as this will help with performance etc. Or is that a misnomer as newer android releases are generally geared for phones with higher specs? I've heard that some CFWs have problems with wifi etc so i'd like to avoid those as I certainly need that.
Overall there seem to be so many even on this forum that I don't really know which would be a best fit for my needs or this phone.
I also have an original San Francisco (zte blade) to update but will save that 'till I've done this one.
Hopefully I can get an understanding as to how all this CFW / Rooting / whatever business works and the best / latest way to do things, as as with everything, it all rapidly changes and you can find yourself looking out lots of outdated and now incorrect or superseeded information.
All a bit overwhelming really, which is why i've put it off so long!
Thanks for your time and help!

1. Q : For backup on ICS 4.0.4, right?
A : Unlock bootloader first -> root -> flash cwm - now u can backup everything from ur phone.
2. Q : Little storage, right?
A : After backup, reboot system.
Partition ur sdcard -> install link2sd. (google it for how to)
Link what do u want to link (google it for how to)
3. Q : Unlockbootloader, right?
A : It's for using custom kernel (google it for how to)
There's too many tutorial from all your question.
Read it again and again :good:

Abigail said:
1. Q : For backup on ICS 4.0.4, right?
A : Unlock bootloader first -> root -> flash cwm - now u can backup everything from ur phone.
2. Q : Little storage, right?
A : After backup, reboot system.
Partition ur sdcard -> install link2sd. (google it for how to)
Link what do u want to link (google it for how to)
3. Q : Unlockbootloader, right?
A : It's for using custom kernel (google it for how to)
There's too many tutorial from all your question.
Read it again and again :good:
Click to expand...
Click to collapse
I have android 2.3 - is this a problem?
I thought that the Sony ICS 4.0 update made it so you could not unlock your bootloader?
Hmm if you unlock your bootloader, it will also root the phone, correct?
But it seems that using the Sony tool will wipe my phone developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
So i saw there is the S1tool but then people said that it does not work with the Arc S.
Is this still the case? What is the reason? is it impossible?
So, you say that in order to back up my applications and things, i need to unlock my bootloader. The official way seems to wipe my phone though - so then i can't back up :S
Hmm, see, i am confused about the order i should do things. Also i've heard that if you use the Sony tool then you cannot use OTA updates which seems like it could be problematic? Mind you i guess CFW cannot use OTA either - so how do you update? You must check for updates on your PC and reflash your phone regularly? Or are there ways for Stock android CFW to support OTA updates?
So, does the Sony ICS update stop you unlocking the bootloader?
I guess there are 2 options. Update using that and then install helium OR root and then use titanium backup.
Not sure which to try.
Thanks!

1. Unlock bootloader is only affected by the phone manufacture date, check the battery compartment and see if the date is before 12W11. Any date after this means the phone can't be unlocked.
2. Software does not affect the unlocking of bootloader, like I mentioned earlier check the battery compartment.
3. Unlocking your bootloader does not mean you have rooted your phone. It just means you can flash custom kernels onto your phone.
4. It's not that S1tool doesn't work, if I told you the entire process of doing it you wouldn't want to do it either.
5. Sony last stopped the update at 4.0.4, no need to concern yourself with future updates.
6. If you use CFW, refer to the thread for instructions on how to install updates.
7. Like I mentioned, ICS update does not affect bootloader unlock, only the manufacture date does. Furthermore, if you update from stock to a CFW, you will not be able to restore your data from the old software. You will have no choice but to start with a clean slate.

I am on Sonys 2.3, build 4.0.2.A.0.62 and i read that i cannot root this version.
I can't use backup software as i can't root to use titanium and helium doesn't support 2.3.
Sony back also apparently doesn't support my phone.
Basically, my apps are outdated due to me not having enough space to update them.
I think that updating to Sony's ICS update might enable me to use these programs and root so that i can backup, then unlock the bootloader and use cfw. (i checked and my s# is older than 12W11 so that's fine).
However, i am worried that if i try to update to Sony's ICS update that i will either lose my applications or the data that is stored with them (whatsapp history, game saves, app config etc etc) - particularly as they are not up to date.
Is this the case? Is there anything i can do?
Thanks

oneNight1 said:
I am on Sonys 2.3, build 4.0.2.A.0.62 and i read that i cannot root this version.
Click to expand...
Click to collapse
Take a look at the tool namend one click root (this thread: http://forum.xda-developers.com/showthread.php?t=2219781), your build should be root-able, just read carefully and decide if you wanna try...
I used this tool on stock sony ics 4.0.4 build and it worked nicely, haven't tried it on stock sony gb 2.3 build though.
Good luck! :good:

BadGround said:
Take a look at the tool namend one click root (this thread: http://forum.xda-developers.com/showthread.php?t=2219781), your build should be root-able, just read carefully and decide if you wanna try...
I used this tool on stock sony ics 4.0.4 build and it worked nicely, haven't tried it on stock sony gb 2.3 build though.
Good luck! :good:
Click to expand...
Click to collapse
Thanks for the tip! It worked!
If you do it twice it relocks your phone. Took some google translate to find out what the chinese was saying hehe.
I'm now on stock 4.0.3 (4.1.A.0.562).
Doesn't seem a great deal better than 2.3, i guess i need to find out what a good lightweight CFW is really. Firefox for android constantly crashes so i tried naked browser and that does too. Wish there was a good selective script blocker for mobile browsers - that would help a lot. Noscript for firefox would be a possibility but the problem is it crashes a lot even with javascript disabled.
So yer not sure where the problems are coming from, maybe due to the low RAM in this phone. That's why i was thinking a lightweight CFW might help matters but not sure if it's best to go with a 5.1 one that breaks 720p recording and has issues with things like turning off GPS.
Or it might be better to go with the latest type that doesn't break anything. I'm guessing that is a 4.0.4 CFW? Or maybe 4.4? I know stock only goes up to 4.0.4 but i think i read something about being able to get CFW based on stock so HDMI, FM radio, 720p recording etc etc won't be broken?
Thanks anyway!

oneNight1 said:
Or it might be better to go with the latest type that doesn't break anything. I'm guessing that is a 4.0.4 CFW? Or maybe 4.4? I know stock only goes up to 4.0.4 but i think i read something about being able to get CFW based on stock so HDMI, FM radio, 720p recording etc etc won't be broken?
Click to expand...
Click to collapse
Well, I haven't tried 5.1 so far, only following the 5.1-threads to see how it's going on.
HDMI is only working up to 4.0.4 roms, FM radio is working in 4.1 roms too, and you'll get 720p recording also in 4.4.4 roms. If you want all things working your phone is able to you will have to use roms based on stock GB or ICS. Therefore I'm using a stock based ICS rom most of the time (T-Rom).

By T-Rom for Arc S, i assume that you mean this? http://forum.xda-developers.com/showthread.php?t=1746508
Or if not then this port of it? http://forum.xda-developers.com/showthread.php?t=2239187
Sounds like something worth trying to see if it helps!
Thanks!

oneNight1 said:
By T-Rom for Arc S, i assume that you mean this? http://forum.xda-developers.com/showthread.php?t=1746508
Or if not then this port of it? http://forum.xda-developers.com/showthread.php?t=2239187
Sounds like something worth trying to see if it helps!
Thanks!
Click to expand...
Click to collapse
For Arc S the first link is the matching one. I think it's the most recently updated ICS rom for our device :good:

Upgrade to Nougat from roote MM

From what i see here on xda, seems to be no way of upgrading a rooted MM to Nougat?
All i can find is flashing a stock MM and sideloading the OTA.
Is it accurate, or is there a way to preserve current ROM?
Flashing the stock kernel / recovery perhaps?
On the other hand is there a real advantage of N over MM, other than the higher version number?
I am pretty satisfied with MM, but the temptation is high
Thank you!

dyonissos said:
From what i see here on xda, seems to be no way of upgrading a rooted MM to Nougat?
All i can find is flashing a stock MM and sideloading the OTA.
Is it accurate, or is there a way to preserve current ROM?
Flashing the stock kernel / recovery perhaps?
On the other hand is there a real advantage of N over MM, other than the higher version number?
I am pretty satisfied with MM, but the temptation is high
Thank you!
Click to expand...
Click to collapse
If you are happy and everything is working the way you want, leave it alone. I do not see a great advantage of Nougat over MM. I have had N on a couple of my other phones and it made no real daily difference. There are a couple of customer oms based on N, you can flash just to scratch that itch.

Try Epsilon ROM

Just to clarify, i am only interested in the stock rom, but thank you for the suggestion.
I am quite upset Motorola did not release a recovery image for Z Play, as they did for the X, but i will get over it.

mahdif62 said:
Try Epsilon ROM
Click to expand...
Click to collapse
Isn't that based on NT? So even not an option for MM users...

Usually it should be possible to do OTA.
Root is usually systemless, so system is not modified.
Twrp only gets booted not flashed, so recovery is not modified.
Logo is not modified.
If you did not use the power of root to modify something, only modified part is boot partition. It was said some years ago that it would not be checked, but this may have changed.
I'll try it in some weeks. Don't have the time currently. Doing Nandroid backup is time consuming, and restoring system if something is not working also. OTA is supposed to work without problems, and it should revert to a usable (not updated) state if it doesn't, but I wouldn't bet on it.

XZ1 Compact - Pie to Oreo downgrade

Hi all,
I'm in need of some guidance with regards to a downgrade that I'd like to perform.
About 1 week ago the phone updated itself OTA. I don't remember which version was last before this update .. but what I remember is that the download was quite consistent (over 1G) and then the update took a while. Everything went by without any errors, but at the end I got Android Pie ... and I don't like it.
Reading through the forums I found that flashing a Xperia is doable .. with the right care and tools. So I started to get acquainted with newflasher and Xperifirm - but for now not connecting the phone and / or trying anything and here are the questions for anyone who might guide me a bit:
1. the phone is warranty (about 4-5 months old in fact). I believe the latest firmware that it was running with Oreo was 47.1.A.16.20-R6B. Reference = h**ps://xpericheck.com/cda/1310-4373. I don't see that version in Xperifirm => how can I get access to it for re-flashing?
2. as far as I read, I don't need to root it or unlock the boot loader. Just flashing would be enough to go back one firmware "edition".
3. backing up user data does not interest me so much. I have a list of all apps that are currently installed and within a few hours of tinkering I could get them all re-installed.
4. Would the process of downgrading be visible afterwards? - i.e. warranty would be "bye-bye", right?
.. any other comment / note / reference or observation is highly appreciated.
Best wishes!

metalik said:
Hi all,
I'm in need of some guidance with regards to a downgrade that I'd like to perform.
About 1 week ago the phone updated itself OTA. I don't remember which version was last before this update .. but what I remember is that the download was quite consistent (over 1G) and then the update took a while. Everything went by without any errors, but at the end I got Android Pie ... and I don't like it.
Reading through the forums I found that flashing a Xperia is doable .. with the right care and tools. So I started to get acquainted with newflasher and Xperifirm - but for now not connecting the phone and / or trying anything and here are the questions for anyone who might guide me a bit:
1. the phone is warranty (about 4-5 months old in fact). I believe the latest firmware that it was running with Oreo was 47.1.A.16.20-R6B. Reference = h**ps://xpericheck.com/cda/1310-4373. I don't see that version in Xperifirm => how can I get access to it for re-flashing?
2. as far as I read, I don't need to root it or unlock the boot loader. Just flashing would be enough to go back one firmware "edition".
3. backing up user data does not interest me so much. I have a list of all apps that are currently installed and within a few hours of tinkering I could get them all re-installed.
4. Would the process of downgrading be visible afterwards? - i.e. warranty would be "bye-bye", right?
.. any other comment / note / reference or observation is highly appreciated.
Best wishes!
Click to expand...
Click to collapse
There is a post in different thread that should answer all of your questions. I couldn't write it better myself, so here you go https://forum.xda-developers.com/xperia-xz1-compact/development/help-t3889845/post78673359
I hope it helps.

Hello,
Thanks for the quick reply.
For sure it confirms my understanding of the process.
Would there by any chance to find my Oreo 8 previous firmware (47.1.A.16.20) but for my "Customized DE" version?
It intrigued me that Xperifirm has just the latest one.

metalik said:
Hello,
Thanks for the quick reply.
For sure it confirms my understanding of the process.
Would there by any chance to find my Oreo 8 previous firmware (47.1.A.16.20) but for my "Customized DE" version?
It intrigued me that Xperifirm has just the latest one.
Click to expand...
Click to collapse
I don't think there will be any difference between customised DE and customised UK, there will be VoLTE and fingerprint enabled.
If you have to start asking other xda users for historical firmware then you can't guarantee its validity.
All the firmwares on Xperiafirm are direct from Sony servers.

Didgesteve said:
I don't think there will be any difference between customised DE and customised UK, there will be VoLTE and fingerprint enabled.
If you have to start asking other xda users for historical firmware then you can't guarantee its validity.
All the firmwares on Xperiafirm are direct from Sony servers.
Click to expand...
Click to collapse
I secured the Oreo firmware (customized UK) and the Pie firmware (customized DE) .. using xperifirm. I downloaded Pie just to have the current release that's running on the phone nearby, in case any of my attempts go bad and I'd need to restore it.
By chance, I have for about 2 weeks the possibility to have a non-branded original "Customized UK" XZ1c. As far as I've seen, there 1 app only that's different compared with my original customized DE. I might flash this one to Oreo and back to Pie ... just to learn the process ... and only afterwards to get to work on mine.
I also took my time to look around the web before jumping into flashing.
There are topics which I don't quite grasp yet .. like DRM .. or attest keys.
The thing is that I don't want to break anything in doing this downgrade to Oreo. I don't need to root it, to unlock the boot loader, to break any X-Reality or other functionality. I'm truly amazed by the battery life, btw: I get 3 1/2 days plus with Stamina activated non-stop. The phone is very snappy even with Stamina ... and that's another issue: by downgrading, I wouldn't like to ruin anything of the battery management internal apps / features.
Another thing is this: i don't intend to preserve any data. Whatever I have as apps, currently, will be backed-up and re-installed from scratch + restore of personal data.
I'm now at the point of going through:
1. flashing with flash tool + xperifirm
OR
2. flashing with newflasher.
Basically, I'm trying to understand what the differences (risks) are and what's the safest to use.
Any advice from the XDA community is welcome on this one.
Best wishes,

@metalik download the firmware with xperifirm and from settings select to decrypt/decompress (don't remember how it is). Then delete all .ta files from the folder and persist*.sin (to avoid losing android attest keys and flash with newflasher.
Flashtool has some problems with newer phone models so it's not recommended for xz1c.

the right question would be, how to get the latest security patches but staying with oreo?

vofferz said:
@metalik download the firmware with xperifirm and from settings select to decrypt/decompress (don't remember how it is). Then delete all .ta files from the folder and persist*.sin (to avoid losing android attest keys and flash with newflasher.
Flashtool has some problems with newer phone models so it's not recommended for xz1c.
Click to expand...
Click to collapse
gentlemen,
your input is highly appreciated.
aside from the persist*.sin and all .ta files .. should I take care of anything else?
P.S. I followed this tutorial (link) and it clearly indicates that warranty would not be voided if I would attempt such a re-flashing. Is it true?
P.S. the last question in the thread remains valid: how to apply the upcoming patches on top of Oreo? .. can those be obtained and flashed in a similar way? ... I doubt it would be a good approach because Sony is supposed to take the Google patches and make sure they integrate properly in their Android customization ...

metalik said:
I secured the Oreo firmware (customized UK) and the Pie firmware (customized DE) .. using xperifirm. I downloaded Pie just to have the current release that's running on the phone nearby, in case any of my attempts go bad and I'd need to restore it.
By chance, I have for about 2 weeks the possibility to have a non-branded original "Customized UK" XZ1c. As far as I've seen, there 1 app only that's different compared with my original customized DE. I might flash this one to Oreo and back to Pie ... just to learn the process ... and only afterwards to get to work on mine.
I also took my time to look around the web before jumping into flashing.
There are topics which I don't quite grasp yet .. like DRM .. or attest keys.
The thing is that I don't want to break anything in doing this downgrade to Oreo. I don't need to root it, to unlock the boot loader, to break any X-Reality or other functionality. I'm truly amazed by the battery life, btw: I get 3 1/2 days plus with Stamina activated non-stop. The phone is very snappy even with Stamina ... and that's another issue: by downgrading, I wouldn't like to ruin anything of the battery management internal apps / features.
Another thing is this: i don't intend to preserve any data. Whatever I have as apps, currently, will be backed-up and re-installed from scratch + restore of personal data.
I'm now at the point of going through:
1. flashing with flash tool + xperifirm
OR
2. flashing with newflasher.
Basically, I'm trying to understand what the differences (risks) are and what's the safest to use.
Any advice from the XDA community is welcome on this one.
Best wishes,
Click to expand...
Click to collapse
First take a screenshot of your current keystore status by typing this in the dialler *#*#7378423#*#*, then go to Service tests or Service info -> Security
I used newflasher since it's the last updated software for flashing.
Extract your ftf if required, put only the required files to downgrade in newflasher's folder. For me I only used kernel, system, userdata and cache.
Boot to flash mode, flash using newflasher, reboot and done! Make sure your keystore is intact by comparing the status of all keys with your screenshot.
I've used this method to downgrade temporarily, get temp root, backup my TA partition and then go back to current firmware. All keys intact.

metalik said:
gentlemen,
your input is highly appreciated.
aside from the persist*.sin and all .ta files .. should I take care of anything else?
P.S. I followed this tutorial (link) and it clearly indicates that warranty would not be voided if I would attempt such a re-flashing. Is it true?
P.S. the last question in the thread remains valid: how to apply the upcoming patches on top of Oreo? .. can those be obtained and flashed in a similar way? ... I doubt it would be a good approach because Sony is supposed to take the Google patches and make sure they integrate properly in their Android customization ...
Click to expand...
Click to collapse
I would flash everything else but the .ta and persist*.sin to ensure it works as intended with all files from the firmware you're using. Of course that resets all your userdata, but I guess a downgrade would require that anyway.
Warranty should be just fine - you're still just using official Sony firmware without any modifications to the device or system.
I don't think it will be possible to stay in official Oreo fw with locked bootloader and get recent security patches.
Sony will most probably implement the new patches only into the latest fw version - and that's Pie.
And if someone would make a custom rom with the latest patches on Oreo, you won't be able to install it with a locked bootloader.

Hello again,
what's the impact of flashing persist*.sin ... I believe that's connected with the attest keys, right?
Later edit: I downgraded from Customized DE Pie to Customized UK Oreo. I used newflasher, deleted all *.ta from the root & boot folder ... but by mistake I forgot about the one small persist*.sin file.
Long story short: yes, leaving persist*.sin file in the folder and flashing with newflasher destroyed the Attest keys (I get them as NOT provisioned).
The phone seems to work without problems nevertheless. I re-flashed to an older Customized DE Pie and got the last valid OTA update. Going back to Customized UK Oreo did remove everything from the Service Tests > Security (it showed "none"). But on that the Xperia Companion did the trick (software repair). So it's back on the initial Customized UK Oreo - just attest key shows NOT provisioned ... so
Lessons learned: /*.ta + /persist*.sin + /boot/*.ta must be removed before flashing with newflasher.

Hey, sorry to bring up this old thread but I don't suppose you still have a copy of 16.20? I've been looking for a working copy of it everywhere and I'm getting desperate

Joecalone said:
Hey, sorry to bring up this old thread but I don't suppose you still have a copy of 16.20? I've been looking for a working copy of it everywhere and I'm getting desperate
Click to expand...
Click to collapse
Hey,
sorry for the late reply ...
I kept everything that I (historically) downloaded with Xperifirm ...
I just checked and one folder is this "G8441_Customized UK_1310-6856_47.1.A.16.20_R18B" ... about 2.55 GB in size.
the content of fwinfo.xml is this:
<?xml version="1.0" encoding="utf-8"?>
<fwinfo>
<project>Lilac</project>
<product>Xperia XZ1 Compact</product>
<model>G8441</model>
<market>United Kingdom</market>
<operator>Customized UK</operator>
<swId>1307-7511</swId>
<swVer>47.1.A.16.20</swVer>
<cda>1310-6856</cda>
<cdfVer>R18B</cdfVer>
<fsVar>GENERIC</fsVar>
</fwinfo>
and update.xml is this:
<?xml version="1.0" encoding="utf-8"?>
<UPDATE>
<SYSTEMPARTITIONIMAGE>partition.zip</SYSTEMPARTITIONIMAGE>
<BOOT>boot.zip</BOOT>
<NOERASE>appslog_X-FLASH-ALL-C93B.sin</NOERASE>
<NOERASE>diag_X-FLASH-ALL-C93B.sin</NOERASE>
<NOERASE>ssd_X-FLASH-ALL-C93B.sin</NOERASE>
<NOERASE>Qnovo_X-FLASH-ALL-C93B.sin</NOERASE>
<FACTORY_ONLY>persist_X-FLASH-ALL-C93B.sin</FACTORY_ONLY>
<NOERASE>userdata_X-FLASH-CUST-C93B.sin</NOERASE>
<SIMLOCK>simlock.ta</SIMLOCK>
<NOERASE>cust-reset.ta</NOERASE>
<NOERASE>master-reset.ta</NOERASE>
<RESETNONSECUREADB>reset-non-secure-adb.ta</RESETNONSECUREADB>
<NOERASE>reset-wipe-reason.ta</NOERASE>
</UPDATE>
in a nutshell: I can zip the folder and find a way to send it to you.
Best regards,

Joecalone said:
Hey, sorry to bring up this old thread but I don't suppose you still have a copy of 16.20? I've been looking for a working copy of it everywhere and I'm getting desperate
Click to expand...
Click to collapse
I have my copy of 16.20 and related firmware. They are all Generic Latin America versions.

Xperia XZ1 Compact 47.1.A.16.20 Firmware Search
metalik said:
in a nutshell: I can zip the folder and find a way to send it to you.
Click to expand...
Click to collapse
Shahnewaz said:
I have my copy of 16.20 and related firmware. They are all Generic Latin America versions.
Click to expand...
Click to collapse
Great! I have also been searching desperately for a G8441 47.1.A.16.20 firmware. The country doesn't matter.
If either of you are able to send a zip, I would love to host it on my drive for anyone else who comes looking.

@cynthi4 Customized NOBA (nordic/baltic) latest Oreo: http://aeitis.org/xz1c/
It's downloaded and decrypted via xperifirm and zipped.
I'll keep it there for a while, but might remove soon.

cynthi4 said:
Great! I have also been searching desperately for a G8441 47.1.A.16.20 firmware. The country doesn't matter.
If either of you are able to send a zip, I would love to host it on my drive for anyone else who comes looking.
Click to expand...
Click to collapse
Here you go:
https://bigboidrive.duckdns.org/nextcloud/s/ZW4FQmqBE8Dfcp2

Hello, I just got a xz1c and I'm on 47.1.a.2.281. I haven't updated because of reported battery drain issues. Should I stick with this? Do you recommend pie at all? If not, what's the most stable build you'd recommend?

moist_line said:
Hello, I just got a xz1c and I'm on 47.1.a.2.281. I haven't updated because of reported battery drain issues. Should I stick with this? Do you recommend pie at all? If not, what's the most stable build you'd recommend?
Click to expand...
Click to collapse
Unless you have any specific issues with Oreo or see some advantage with upgrading to Pie, I wouldn't. I am not a big fan of Pie and went through this downgrade to 47.1.A.16.20 to avoid it. If you're interested in custom ROMs, I am running LineageOS 15.1 on my xz1c and it's been great!

That's strange. Being still happy with my locked device, I've always regretted switching to pie so today I actually did the whole process to restore Oreo: downloaded the latest Costumized NOBA oreo the user few posts above linked, deleted *persist.sin and every *.ta files in the folder (even the one inside boot folder), run newflasher and then reboot. Too bad I found stock camera broken
I re-checked multiple times searching for those *.ta files to be sure to avoid this issue, but that's it: I got Oreo but now I have lost stock camera and who knows what else.
Does it mean I've lost those functionality forever? Is there any way to restore stock camera? Happy to see this thread still active

H8324 Rooted Android 9, how to update to latest Android 10 rooted version ?

Hello,
I currently have a XZ2 compact H8324 rooted
Build number : 52.0.A.3.126
I rooted it some years ago and to be honest I don't remember well what I used to do it. I just remember DRM are safe.
The bootloader is unlocked if I remember well (warning message at boot)
Could someone please tell me how to update to latest Android version still rooted ?
I don't care about format it, but I would like it to work as usual (camera stuff) with root.
Is there some kind of precautions ? tools ?
Thank you.
Edit : downloading 52.1.A..3.49 with XperiFirm currently

Xperifirm might work. You can also try Emma (Sony's official flashing tool) which is easier to use but will wipe your device and uninstall any custom recovery you have installed. Your bootloader will remain ulocked, and your DRM keys intact, so you can always reinstall custom recovery after that.
You can also install LineageOS. They have an official 17.1 (Android 10) build for the XZ2 Compact, so it should be very stable and have minimal issues. I'd recommend installing LineageOS after flashing the latest firmware with Xperifirm/Emma because the stock ROM doesn't play nice if you have root or TWRP installed.

Thanks @dankcuddlybear for your answer.
I don't care about custom recovery and data as long as I'm able to flash back custom recovery and root after flash.

If your current Pie variant is fast, stable and is fulfilling its mission, be happy and leave it be.
Q is using cpu cycle wasting scope storage and is a downgrade in many ways from Pie.
Being rooted means you could (?) overcome many of these limitations but how much is your time worth?
Android 10,11(Apple) woke, go broke

blackhawk said:
If your current Pie variant is fast, stable and is fulfilling its mission, be happy and leave it be.
Q is using cpu cycle wasting scope storage and is a downgrade in many ways from Pie.
Being rooted means you could (?) overcome many of these limitations but how much is your time worth?
Android 10,11(Apple) woke, go broke
Click to expand...
Click to collapse
It is not... screen hangs for no reason and needs to switch it off and on
And last week i had to force hardware button reboot as it was stuck

Orphee said:
It is not... screen hangs for no reason and needs to switch it off and on
And last week i had to force hardware button reboot as it was stuck
Click to expand...
Click to collapse
Not good. Pie should be rock solid stable.
It sounds like it's fixing to crash and burn.
Look at the launcher and other 3rd party apps you're using. That load maybe corrupted or the original firmware was flawed.