Related
I am a proud owner of the AT&T Xperia Ion and am getting sick being unable to download the apps i want and i have read around here i can flash the international firmware so i could have ICS on my phone. Well as a noob to androids i am obviously nervous as to the effects of flashing. so i would like to know the risks of flashing it are. Once the official AT&T firmware is released can i switch to it? Will all the data stored in my phone be erased? Will i be able to use LTE? Will the warranty be voided? i would also like to know if there are other things i should know about, as well as the process in which i can carry out the flashing. thank you everybody
1. Just flash back to stock att ftf, and you should get the update. Or, flash the att ICS ftf when it becomes available.
2. It's a good idea to wipe between flashes, so if you did, all your data will be gone. I backup contacts and calendar through Google, so getting data back for me is easy. App data on the other hand will be gone. Or, risk it and don't wipe, but you will likely get some stability issues.
3. You can get lte.
4. If you flash back to stock before taking your phone for service, there should be no warranty issues. Is you take it in with Chinese firmware, that'll likely be a problem.
Sent from Rooted LT28at with ICS.
misterwhales said:
I am a proud owner of the AT&T Xperia Ion and am getting sick being unable to download the apps i want and i have read around here i can flash the international firmware so i could have ICS on my phone. Well as a noob to androids i am obviously nervous as to the effects of flashing. so i would like to know the risks of flashing it are. Once the official AT&T firmware is released can i switch to it? Will all the data stored in my phone be erased? Will i be able to use LTE? Will the warranty be voided? i would also like to know if there are other things i should know about, as well as the process in which i can carry out the flashing. thank you everybody
Click to expand...
Click to collapse
I'm also a noob in Android. Last weekend flashed ICS on my Xperia, following the procedure for rooting. It took me maybe two hours to get all the instructions and download everything I needed. You´ll basically need the firmwares, Android SDK (the link is in the post with instructions, second one in the thread), Flashtool (the latest Windows version, which comes with the drivers for Ion, is in http://androxyde.github.com/Flashtool/). I followed everything from the instructions, but wasn't getting the same response from the ADB commands, it still worked.
Two things are missing from those instructions:
1. To have hotspot activated, you'll need to first flash the international GB firmware, wiping everything in your device (be sure to make backups of everything you´ll want, don´t trust Google backup).
2. Right after flashing ICS, Flashtool won't recognize your phone, even if you have the USB debugging option on. You'll have to update your PC drivers by going to Control Panel, Device Manager, and choose to have Windows search for updated drivers (while the phone is connected, of course). You´ll know you got it right when Device Manager displays a different name for your phone, and Flashtool is able to tell you the software version. At that point you can run the second part of the rooting procedure.
Mmh...
Hello!
When will be released the official ice cream sandwich for my xperia ion lt28i? (international version, bought from Hong Kong)
No time given really. I am guessing at the same time the US releases their's so will the European (International) Version. So maybe September / October time frame, could be earlier.
I have a note 10.1 2014 SM-P600 which has never been rooted . Currently it's running a fairly recent "netherlands" android 5.1.1 build from early this year, but I was thinking of doing the minor update to the latest Polish build. This is the kind of thing I've done for years (actually far more with 3rd party roms in the past on multiple devices... but need to use too many things now that block rooted devices!)
However I've just encrypted my device. Of course things are backed up, but I wondered how risky/workable was doing the odin update now? Should it work? Or is there no-chance? I presume there's no way to reverse encryption without a full reset?
planetf1 said:
I have a note 10.1 2014 SM-P600 which has never been rooted . Currently it's running a fairly recent "netherlands" android 5.1.1 build from early this year, but I was thinking of doing the minor update to the latest Polish build. This is the kind of thing I've done for years (actually far more with 3rd party roms in the past on multiple devices... but need to use too many things now that block rooted devices!)
However I've just encrypted my device. Of course things are backed up, but I wondered how risky/workable was doing the odin update now? Should it work? Or is there no-chance? I presume there's no way to reverse encryption without a full reset?
Click to expand...
Click to collapse
I did this twice using odin - just because OTA is not working on encrypted devices and I can't decrypt because of some regulations of my employer.... I guess the encrypted part (data) is not touched by the update, but the downloaded OTA-update would be there and therefore not accessible during the update process...
Never run into a problem with flashing complete firmware in Odin.
Thanks
Sent from my iPhone using Tapatalk
I have a Sim Free HTC M9 running Android 7.0 (HTC update 4.14.401.7). I am in the UK with EE as my carrier. My phone has been requesting I download 4.28.401.3 but fails at 25% to the red exclamation mark. From the Bootloader I can see: ***Software status: Official***, ***LOCKED***, ***S-ON*** and know that it has never been modded as I've owned it from new.
I know that someone posted here about 2 months ago with the same problem and I've had several replies from people on other forums, all with stock phones, with the same exact update problem.
The Readme on this forum suggests that: "If you never modified your phone and didn't buy it second-hand then this problem might be a precursor of the NAND death." - Is this always the case or does the fact that other people with unmodified phones are having the same problem mean it might be a problem with the update itself and HTC's end?
After contacting HTC support they seemed to lose interest after I told them that a factory reset didn't work and instead offered a repair. However, as the retailer I bought the phone from in Nov 2015 (within the 2 year warranty period) didn't include the IMEI number on the receipt, it seems that the date of manufacture would be used to determine warranty start date, which means it is just out of warranty.
I have no idea how much an out of warranty repair of this type would cost as HTC wouldn't give me an estimate, but I don't feel confident to attempt anything myself. Would it be worth sending it anyway?
The dead nand issue happens on modified phones as well as on unmodified ones independently of the currently installed firmware version. Since more and more nands die, chances are high that the aborted OTA indicates a future nand death.
The update itself is probably fine since a lot of people could install it without any issues.
It's the nature of block-based OTAs to abort the update if the phone that should get updated doesn't pass the security checks. They check the whole system partition and not only single files like the OTAs of the pre-Android-L-era. That's why already the slightest change to the partition leads to an abortion of an OTA.
If your system partition is modified and you didn't do it manually and the phone didn't get bought second hand then the only plausible reason that I can see is that your phone has problems with reading the system partition correctly (=nand issue precursor).
You can restore an untouched system image. The instructions can be found in the ReadMe thread. This way you should restore the ability to install OTAs. However, you need to be aware that the hardware of your phone might stop working sooner or later.
Edit: The main problem with that issue is that it doesn't happen on every M9 and that the trigger is still unknown. I for example had installed an incredible amount of OTAs for a whole bunch of firmware versions when I created my backup collection. That's everything else than a nand-friendly usage of this phone. However, I could install all OTAs without issues, so far, and my phone is working just fine. Nevertheless, I periodically backup the most important data on my phone since in most cases the nand issue happens without any foreshadowing.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
The dead nand issue happens on modified phones as well as on unmodified ones independently of the currently installed firmware version. Since more and more nands die, chances are high that the aborted OTA indicates a future nand death.
The update itself is probably fine since a lot of people could install it without any issues.
It's the nature of block-based OTAs to abort the update if the phone that should get updated doesn't pass the security checks. They check the whole system partition and not only single files like the OTAs of the pre-Android-L-era. That's why already the slightest change to the partition leads to an abortion of an OTA.
If your system partition is modified and you didn't do it manually and the phone didn't get bought second hand then the only plausible reason that I can see is that your phone has problems with reading the system partition correctly (=nand issue precursor).
You can restore an untouched system image. The instructions can be found in the ReadMe thread. This way you should restore the ability to install OTAs. However, you need to be aware that the hardware of your phone might stop working sooner or later.
Edit: The main problem with that issue is that it doesn't happen on every M9 and that the trigger is still unknown. I for example had installed an incredible amount of OTAs for a whole bunch of firmware versions when I created my backup collection. That's everything else than a nand-friendly usage of this phone. However, I could install all OTAs without issues, so far, and my phone is working just fine. Nevertheless, I periodically backup the most important data on my phone since in most cases the nand issue happens without any foreshadowing.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Thanks for the comprehensive advice! I'd definitely rather avoid a hardware failure so I guess I'll have to send it to HTC, even if it is out of warranty.
Last year, I bought my first ever Android - a Galaxy S7 Snapdragon. Unfortunately, I soon learned that without root & Titanium, Android provides no way to do a proper/complete backup (i.e. SmartSync doesn't backup any app data, & Helium backs up some but misses many - WhatsApp, LINE, Viber, etc). Thus I returned the S7, took a brief hiatus, & am now eagerly awaiting the arrival of a brand new Exynos S9
I wanted to ask for any quick advice as to the "suggested" approach for rooting, so I can hit the ground running as soon as this thing arrives. As I understand it, there are 3 main approaches:
1) Install TWRP, stick with the stock Samsung ROM & flash SuperSU
2) Install TWRP, stick with the stock Samsung ROM & flash Magisk
3) Install TWRP, flash a custom ROM that's already rooted
Between 1 & 2, my understanding is that Magisk is preferable to SuperSU as it essentially accomplishes the same thing but without necessarily blocking OTA updates or some financial applications from working. True? So is there even any reason to consider #1? If not, any insight as to choosing between #2 vs (any specific custom ROMs)?
My long-term priorities are simply for the phone to run as well as possible, with as little maintenance as possible (i.e. as far as ease of getting security updates goes). I'm not really into lots of customization, experimenting, etc - I'd prefer to just get something up & running, stable, & stick with it. I will be using T-Mobile though, so I guess in either case I'll need to install this to get WiFi calling & VoLTE working. Also, I want to make sure that whichever root solution I choose, it can coexist with Secure Startup (the S7 Snapdragon's root couldn't, which was a dealbreaker for me).
Any insight would be greatly appreciated. The phone arrives Tuesday, I can't wait to get started!
As soon as you flash twrp your not going to get OTA updates nevermind root.
sent from my Pixel 2 XL or Note FE
Unfortunately i made a silly mistake, i wiped the EFS partition of my G960FD once rooting the device while not having any backup for it
i tried flashing official rom, combined roms, cutoms roms; but always, i have the same problem "unknown IMEI and Baseband"
even, i tried to use ODIN Nand Erase All and installing new fresh official rom and also, have the same problem
is there any recommendations, please?
hanymedic said:
Unfortunately i made a silly mistake, i wiped the EFS partition of my G960FD once rooting the device while not having any backup for it
i tried flashing official rom, combined roms, cutoms roms; but always, i have the same problem "unknown IMEI and Baseband"
even, i tried to use ODIN Nand Erase All and installing new fresh official rom and also, have the same problem
is there any recommendations, please?
Click to expand...
Click to collapse
Samsung repair centre
*Detection* said:
Samsung repair centre
Click to expand...
Click to collapse
They asked me to pay 400$ for replacing the mother board
that's why i asked for having any solution
hanymedic said:
They asked me to pay 400$ for replacing the mother board
that's why i asked for having any solution
Click to expand...
Click to collapse
when you say combined roms do you mean the factory binary firmwares? because if flashing the combination firmware/factory binary followed by the usual rigmarole factory reset, nd reflash official fw doesnt work you could try rebuilding the partition using adb shell (root access needed for this though)
https://forum.xda-developers.com/note-4/general/fix-drk-dm-verity-factory-csc-serial-t3422965
this link isnt for the s9 smg960f but it did work for me when trying to solve the same issue on the sm-g950f,
anyway hope this helps in some way
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