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
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'm new to the flexibility of Android as a user of Blackberry 10. I have always run beta leaks in the BB world and have been reading and learning on the android world but there is so much diversity I am tentative.
I have a ZL that was a Bell Mobility locked phone. I purchased unlock code (took a few days from a reputable provider) and I have a bunch of those code groups, one of which was used as directed to unlock successfully. I am using it on Rogers and am running the latest 10.3.A.0.423.
I have installed the flash tools etc. My intent is to root in order to rid the phone of Bell crap and other nuisance things that I don't want around and hopefully get more flexibility in power consumption changes.
Can someone point me in the right direction? I had tried the root process that is posted here but find that it hangs on the "display" part of the process on a white screen and doesn't go further. My conclusion was that the process isn't supporting the firmware level that I am at.
cwoodffr said:
I'm new to the flexibility of Android as a user of Blackberry 10. I have always run beta leaks in the BB world and have been reading and learning on the android world but there is so much diversity I am tentative.
I have a ZL that was a Bell Mobility locked phone. I purchased unlock code (took a few days from a reputable provider) and I have a bunch of those code groups, one of which was used as directed to unlock successfully. I am using it on Rogers and am running the latest 10.3.A.0.423.
I have installed the flash tools etc. My intent is to root in order to rid the phone of Bell crap and other nuisance things that I don't want around and hopefully get more flexibility in power consumption changes.
Can someone point me in the right direction? I had tried the root process that is posted here but find that it hangs on the "display" part of the process on a white screen and doesn't go further. My conclusion was that the process isn't supporting the firmware level that I am at.
Click to expand...
Click to collapse
For the .423 firmware you can use DoomLord's Easy Rooting Toolkit v17, found in this thread: http://forum.xda-developers.com/showthread.php?t=2332407
If you decide to flash a newer stock firmware (.244 or .67 - which I advise you to do, after you get yourself acquainted with Android, Xperia and, of course, your ZL), the rooting process is different - until firmware .423 there was an exploit used to root our devices, but, since firmware .244, this exploit has been fixed by Sony. This rooting process is described in this thread: http://forum.xda-developers.com/showthread.php?t=2458268
Best regards and welcome to the Android world.
Tiu Fiu said:
For the .423 firmware you can use DoomLord's Easy Rooting Toolkit v17, found in this thread: http://forum.xda-developers.com/showthread.php?t=2332407
If you decide to flash a newer stock firmware (.244 or .67 - which I advise you to do, after you get yourself acquainted with Android, Xperia and, of course, your ZL), the rooting process is different - until firmware .423 there was an exploit used to root our devices, but, since firmware .244, this exploit has been fixed by Sony. This rooting process is described in this thread: http://forum.xda-developers.com/showthread.php?t=2458268
Best regards and welcome to the Android world.
Click to expand...
Click to collapse
Thanks so much for the reply. So you would say to flash .67 as my next level of "maturation" prior to messing with rooting? I assume as that is what you are running per your sig.
Oh, and will I have an issue with these things if the phone has been unlocked by an on-line provider?
cwoodffr said:
Thanks so much for the reply. So you would say to flash .67 as my next level of "maturation" prior to messing with rooting? I assume as that is what you are running per your sig.
Oh, and will I have an issue with these things if the phone has been unlocked by an on-line provider?
Click to expand...
Click to collapse
Technically once the unlock code has been accepted, that is it, it is unlocked and it is supposed to stay that way. In any case, it would be wise to keep the unlock code safe somewhere, just in case.
I said that because, with DoomLord's v17 rooting toolkit for the .423, it is basically a one click, straight-forward operation. However, for the .67, things get a tiny bit more complicated (it will seem very simple once you get familiar with flashing firmwares with Flashtools, trust me).
Anyway, I do advise you to flash .67 since it is a far more mature firmware than .423 (and by mature, I mean less bugs and a more optimized and stable OS, just as is expected of a newer firmware). You need to keep a close eye to your ZL model (C6502, C6503 or C6506). I don't know which one Bell/Rogers sells, but it is easy to find out (Settings -> About the phone -> Model Number). Flashing a firmware created for a device different than yours might be troublesome and, though I've read from time to time about people using different firmwares on different models without any problems (e.g. flashing a C6503 firmware on a C6502 ZL), I definitely advise against it.
Either way, the one true rule here is to take your time to read the info/guide/tutorial threads around in the forum.
Tiu Fiu said:
Technically once the unlock code has been accepted, that is it, it is unlocked and it is supposed to stay that way. In any case, it would be wise to keep the unlock code safe somewhere, just in case.
I said that because, with DoomLord's v17 rooting toolkit for the .423, it is basically a one click, straight-forward operation. However, for the .67, things get a tiny bit more complicated (it will seem very simple once you get familiar with flashing firmwares with Flashtools, trust me).
Anyway, I do advise you to flash .67 since it is a far more mature firmware than .423 (and by mature, I mean less bugs and a more optimized and stable OS, just as is expected of a newer firmware). You need to keep a close eye to your ZL model (C6502, C6503 or C6506). I don't know which one Bell/Rogers sells, but it is easy to find out (Settings -> About the phone -> Model Number). Flashing a firmware created for a device different than yours might be troublesome and, though I've read from time to time about people using different firmwares on different models without any problems (e.g. flashing a C6503 firmware on a C6502 ZL), I definitely advise against it.
Either way, the one true rule here is to take your time to read the info/guide/tutorial threads around in the forum.
Click to expand...
Click to collapse
it is a 6506 so I think I should be fine with the directions you provided.
cwoodffr said:
it is a 6506 so I think I should be fine with the directions you provided.
Click to expand...
Click to collapse
In that case, since there is no Generic Canadian firmware for the C6506, I would suggest the Generic US one found in this thread: http://forum.xda-developers.com/showthread.php?t=2459497
It should be absolutely fine to flash the US Generic firmware (since it is supposed to be operator/bloatware free and fully functional for any C6506 as the German/Baltic/Middle-Eastern-and-Asian/Brazilian generic firmwares are for the C6503)
For info on stock firmwares available, check this thread: http://forum.xda-developers.com/showthread.php?t=2333187
You should be able to find the small .ftf files for the "old" (.423) kernel and the "new" (.67) kernel alone. If you don't find the kernel-only files, you'll also need to download any C6506 .423 full firmware .ftf file and follow the "Using complete ftf packages" mentioned on the OP (opening post) of sanjulgupta's rooting thread (http://forum.xda-developers.com/showthread.php?t=2458268 ).
Best regards and good luck.
Done! Moved to .67, then Rooted using the small files. No issues except that I lost the native browser?
Safe STOCK Oreo by Fastboot FULL flash:
download file from my gdrive: https://drive.google.com/open?id=1XWoaudSHAhQMWi3Au4wmtf2QaCrhugoD
Now to what matters...
Important!!! Only for RETAIL versions AMERICAS with working band base ending in ¨R¨, also for people who DID NOT mess up with persist and EFS...otherwise it is likely to loose IMEI...also....working for previous BRICKED devices that need to use Moto Z bootloader, but only RETAIL AMERICAS versions.
Anything else, please read and follow this post here: https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
download and unzip file.
extract ROM folder and copy within very same folder the adb fastboot oreo g5+ folder and content extracted in same folder all together.
before going on, make sure you have motorola latest drivers installed, found in ADDONS, adbz folder, motorola device manager.
restart phone in bootloader, connect to laptop.
run file with name OREO G5 PLUS DE CERO.bat (spanish whatever), once done, unplug and restart phone.
should delay a few moments and go into setup.
additionally, you may want to install latest TWRP 3231 found in RECOVERIEZ folder.
additionally, you may want to flash motorola boot logo found in BOOT LOGOZ folder, to prevent the unlocked phone boring screen.
additionally, you may want to flash Magisk 17.1 in ROOTZ folder, only Magisk file, nothing else.
additionally, you may want to flash Kernels like Extended or EX found in KERNELZ folder.
some apps in APPZ folder that I use.
in REVIVALZ you may find files to bring bricked phone to life, but that is another history you may need to find out by reading posts.
in ADBz you can find extra folders for CMD commands.
This tuto is for knowledgeable people.
I have my device working fine in official stock again, however........BOOTLOADER STAYS FOR MOTOZ, meaning, you cannot take OTAS, reason for which locking Bootloader is unnecesary, recommended that once TWRP3231 is flashed, you may backup averything, all partitions, remember this is the last backup for official STOCK we will have from Motonovo.
For further updated official releases, just flash as regular in adb-cmd.
Ciao Babies!!!
Iam uploading my special Bricked moto Z Loader Stock Oreo TWRP Moto G5+ for those who may need it, ciao!!!
Thank you very much, I just followed your method, very fast and clean, thank you I got Oreo on my phone!
SowilM said:
Thank you very much, I just followed your method, very fast and clean, thank you I got Oreo on my phone!
Click to expand...
Click to collapse
Happy to help brother!
So this will work for european users who did not break their persist?
Fabiuz99 said:
So this will work for european users who did not break their persist?
Click to expand...
Click to collapse
As far as i Know only for retail americas but you can try on your own and let us know
Battery performance is for fully happy and satisfied OVERWHELMING
will it work for indian version
will it work for indian version
---------- Post added at 06:48 PM ---------- Previous post was at 06:00 PM ----------
prnv1312 said:
will it work for indian version
Click to expand...
Click to collapse
thnks alot man
can i update my moto g5 plus build number NPNS25.137-93-14 rooted with this?
LLegion said:
Safe STOCK Oreo by Fastboot FULL flash:
download file from my gdrive: https://drive.google.com/open?id=1XWoaudSHAhQMWi3Au4wmtf2QaCrhugoD
Now to what matters...
Important!!! Only for RETAIL versions AMERICAS with working band base ending in ¨R¨, also for people who DID NOT mess up with persist and EFS...otherwise it is likely to loose IMEI...also....working for previous BRICKED devices that need to use Moto Z bootloader, but only RETAIL AMERICAS versions.
Anything else, please read and follow this post here: https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
download and unzip file.
extract ROM folder and copy within very same folder the adb fastboot oreo g5+ folder and content extracted in same folder all together.
before going on, make sure you have motorola latest drivers installed, found in ADDONS, adbz folder, motorola device manager.
restart phone in bootloader, connect to laptop.
run file with name OREO G5 PLUS DE CERO.bat (spanish whatever), once done, unplug and restart phone.
should delay a few moments and go into setup.
additionally, you may want to install latest TWRP 3231 found in RECOVERIEZ folder.
additionally, you may want to flash motorola boot logo found in BOOT LOGOZ folder, to prevent the unlocked phone boring screen.
additionally, you may want to flash Magisk 17.1 in ROOTZ folder, only Magisk file, nothing else.
additionally, you may want to flash Kernels like Extended or EX found in KERNELZ folder.
some apps in APPZ folder that I use.
in REVIVALZ you may find files to bring bricked phone to life, but that is another history you may need to find out by reading posts.
in ADBz you can find extra folders for CMD commands.
This tuto is for knowledgeable people.
I have my device working fine in official stock again, however........BOOTLOADER STAYS FOR MOTOZ, meaning, you cannot take OTAS, reason for which locking Bootloader is unnecesary, recommended that once TWRP3231 is flashed, you may backup averything, all partitions, remember this is the last backup for official STOCK we will have from Motonovo.
For further updated official releases, just flash as regular in adb-cmd.
Ciao Babies!!!
Click to expand...
Click to collapse
can i update my moto g5 plus build number NPNS25.137-93-14 rooted with this? june security update
LLegion said:
Safe STOCK Oreo by Fastboot FULL flash:
download file from my gdrive: https://drive.google.com/open?id=1XWoaudSHAhQMWi3Au4wmtf2QaCrhugoD
Now to what matters...
Important!!! Only for RETAIL versions AMERICAS with working band base ending in ¨R¨, also for people who DID NOT mess up with persist and EFS...otherwise it is likely to loose IMEI...also....working for previous BRICKED devices that need to use Moto Z bootloader, but only RETAIL AMERICAS versions.
Anything else, please read and follow this post here: https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
download and unzip file.
extract ROM folder and copy within very same folder the adb fastboot oreo g5+ folder and content extracted in same folder all together.
before going on, make sure you have motorola latest drivers installed, found in ADDONS, adbz folder, motorola device manager.
restart phone in bootloader, connect to laptop.
run file with name OREO G5 PLUS DE CERO.bat (spanish whatever), once done, unplug and restart phone.
should delay a few moments and go into setup.
additionally, you may want to install latest TWRP 3231 found in RECOVERIEZ folder.
additionally, you may want to flash motorola boot logo found in BOOT LOGOZ folder, to prevent the unlocked phone boring screen.
additionally, you may want to flash Magisk 17.1 in ROOTZ folder, only Magisk file, nothing else.
additionally, you may want to flash Kernels like Extended or EX found in KERNELZ folder.
some apps in APPZ folder that I use.
in REVIVALZ you may find files to bring bricked phone to life, but that is another history you may need to find out by reading posts.
in ADBz you can find extra folders for CMD commands.
This tuto is for knowledgeable people.
I have my device working fine in official stock again, however........BOOTLOADER STAYS FOR MOTOZ, meaning, you cannot take OTAS, reason for which locking Bootloader is unnecesary, recommended that once TWRP3231 is flashed, you may backup averything, all partitions, remember this is the last backup for official STOCK we will have from Motonovo.
For further updated official releases, just flash as regular in adb-cmd.
Ciao Babies!!!
Click to expand...
Click to collapse
will it work on a latin american one? xt1680 currently on npn25.137-92 november patch unlocked bootloader. This is not my daily driver. If the flash of this oreo rom doesnt work, can i just reflash my npn25.137-92 firmware back? or will that not work?
carloandreaguilar said:
will it work on a latin american one? xt1680 currently on npn25.137-92 november patch unlocked bootloader. This is not my daily driver. If the flash of this oreo rom doesnt work, can i just reflash my npn25.137-92 firmware back? or will that not work?
Click to expand...
Click to collapse
I am friom mexico and my phone is working perfect...is your question anserred alwearu...can not go back to nouhat
will it work for indian version XT1686
LLegion said:
Safe STOCK Oreo by Fastboot FULL flash:
I have my device working fine in official stock again, however........BOOTLOADER STAYS FOR MOTOZ, meaning, you cannot take OTAS, reason for which locking Bootloader is unnecesary, recommended that once TWRP3231 is flashed, you may backup averything, all partitions, remember this is the last backup for official STOCK we will have from Motonovo.
Click to expand...
Click to collapse
Can you please clarify the above info. I have a U.S. x1687 that is still stock nougat that I'd like to upgrade to Oreo (since Motonovo screwed everyone with the August security update and lots of us are experiencing major battery drain issues!) . I'd like to remain completely stock if at all possible. Any way to update with the Moto G5+ bootloader?
carloandreaguilar said:
will it work on a latin american one? xt1680 currently on npn25.137-92 november patch unlocked bootloader. This is not my daily driver. If the flash of this oreo rom doesnt work, can i just reflash my npn25.137-92 firmware back? or will that not work?
Click to expand...
Click to collapse
nvrpayretail said:
Can you please clarify the above info. I have a U.S. x1687 that is still stock nougat that I'd like to upgrade to Oreo (since Motonovo screwed everyone with the August security update and lots of us are experiencing major battery drain issues!) . I'd like to remain completely stock if at all possible. Any way to update with the Moto G5+ bootloader?
Click to expand...
Click to collapse
You need bootloader open and yess you can flash safely it ks stock and battery is workimg awesome
LLegion said:
You need bootloader open and yess you can flash safely it ks stock and battery is workimg awesome
Click to expand...
Click to collapse
Sorry, I still a bit confused. The text I quoted says "bootloader stays MotoZ". If I install this update, as is, will my bootloader be MotoZ or remain Moto G5+?
Thanks...
I have the US version (retus), bootloader unlocked, nougat 7.0 with August patch (NPNS25. 137-93-18). Can I use this method safely? Thanks
I do not know what else to say...just flash as edpalined if phone breaks then unbrick it reading other tutos sorry pals but seems you are not reading enough
No risk no Win buddies
Hi, great write up! I like how your zip is a one stop shop. I used the included Moto G5+ toolkit to flash the stock Oreo zip which worked perfectly. I down graded to stock 7.1 from custom 9.0 however I'm noticing while on official Oreo whenever I reboot the device it will TWRP loop back into recovery and the only way to get back in the system is to go to bootloader and boot to system. Anyone else had this happen and fix it?
XT1867
OC.92 bootloader (unlocked)
TWRP 3.2.3.1
JohnSmith8786 said:
Hi, great write up! I like how your zip is a one stop shop. I used the included Moto G5+ toolkit to flash the stock Oreo zip which worked perfectly. I down graded to stock 7.1 from custom 9.0 however I'm noticing while on official Oreo whenever I reboot the device it will TWRP loop back into recovery and the only way to get back in the system is to go to bootloader and boot to system. Anyone else had this happen and fix it?
XT1867
OC.92 bootloader (unlocked)
TWRP 3.2.3.1
Click to expand...
Click to collapse
Do no flash from twrp but from runnimg the batch file oreo desde cero and it will flash the recobery as well to the oreo stock and thats it.buddie
Hello guys!
I have a sim unlocked Galaxy S20 (SM-G980F) from Orange Romania and I want the new update (Android 12 and OneUI 4) and to get rid of the pre-installed apps from Orange. Apparently it is a known fact that some mobile network operators tend to postpone the new firmware updates (which I think it's stupid) because they have to 'test' it and load it with a bunch of useless apps that nobody needs. It wouldn't have been such a problem if this would happen in a timeframe of a few days, but usually it takes months. I contacted Orange and they said the upcoming update is being 'tested' and it will probably be released sometime in March (which again, it's just stupid).
I am looking for a way to change the Software Service Provider from ORO to ROM (or something else, to get the update directly from Samsung and not Orange); Samsung and Vodafone already rolled the update.
So, I have a few questions:
1. Can I change the Service Provider? (SM-G980F on Android 11)
1.1. If yes, how can I do it? Can you guys kindly guide me towards a tutorial?
1.2. Can I do it for free?
2. Should I just install a custom ROM? (I have seen many on this forum, but most of them seem to have problems if the high refresh rate is enabled etc... any reccomendations?)
Thank you guys! Any advice is much appreciated!
PS: I am kind of unfamiliar with these things, i used to flash custom ROMs on my old phones back when Cyanogenmod was a thing and I've used Android since 1.5. I don't know what changed and what's new so any help is welcome! Thank you!
First off, why do you even want Android 12 so badly? Early adopters catch all the bugs. And moreover, if you want to mod your phone, you'll quickly notice that a lot of popular mods aren't yet available for Android 12. As of today:
There still is not an official Magisk release for Android 12 (only Canary/pre-release builds).
Xposed module GravityBox for Android 12 has not been released.
Xposed module Firefds Kit for Android 12 has not been released.
And if you start modding, you're likely to find more things that just don't exist for A12 yet.
1. Can I change the Service Provider? (SM-G980F on Android 11)
Click to expand...
Click to collapse
Yes.
1.1. If yes, how can I do it? Can you guys kindly guide me towards a tutorial?
Click to expand...
Click to collapse
It used to be fairly easy. You could open the Preconfig dialog with a dialer code and change your CSC code. Loss of this functionality in recent software is lamented loss of this functionality in recent software is lamented here. There are many discussions about changing CSC code that make mention of the commercial software and service Samkey such as this and this; I have no personal experience with their offering so I can't recommend them. Interestingly it seems from the discussions that there is typically some lag between an Android release and support for that release from Samkey, so the trend I just referenced above is hardly an isolated phenomenon.
It's worth mentioning that the changing of CSC codes has been discussed extensively throughout the forum. One of the downsides of XDA though is that discussion is heavily segregated by device, so you can easily miss what you're looking for if you search only in a sub-forum for your device.
1.2. Can I do it for free?
Click to expand...
Click to collapse
With root, certainly. Otherwise, it is not so clear based on the above.
You can launch the Preconfig dialog from a root shell:
am start -n com.samsung.android.cidmanager/.preconfig.PreconfigActivity
I've noticed that in some configurations (notably when CSC code is VZW), the Preconfig dialog seems to be somehow disabled. However, with root access you can also simply edit /efs/imei/omcnw_code.dat.
2. Should I just install a custom ROM? (I have seen many on this forum, but most of them seem to have problems if the high refresh rate is enabled etc... any reccomendations?)
Click to expand...
Click to collapse
That's your choice. Browse the ROM section and see if there is anything available for your device that you like. Custom ROMs vary greatly in user experience as a consequence both the ROM's objectives and the developer's skill.
They all have a few things in common though: they will irrevocably trip the warranty void bit and cause a loss of Knox-related functionality (notably including Samsung Pay). They also will prevent you from receiving official OTA updates.
Another option is that you can simply root your device and start modding away yourself. Basically, that workflow is something like this:
OEM Unlock.
Boot into download mode with vol up + vol down + insert USB cable connected to PC.
Volume up to confirm unlock.
Flash TWRP from ODIN.
Flash Multi-disabler from TWRP.
Wipe /data from TWRP.
Install Magisk from TWRP.
Once you have root, you can not only change your CSC code as desired, but edit the read-only filesystems on your device, notably including the filesystems containing the CSC. It's even possible to blow away the CSC content completely and integrate the CSC content from the ROM of another region.
Of course, it goes without saying that you need to back up anything important on your phone before you start any experiments. Of particular importance, be sure to back up efs and sec_efs with TWRP and make sure the backups are stored somewhere safe (e.g., on a PC) before you start attempting any changes to efs partitions. A damaged efs partition is one of the easiest ways to render your phone useless. Note also that custom ROM installation almost always involves wiping /data somewhere along the way.
So, the bloatware you talk about is located in /product , /hidden or /odm depending on how your phone is configured. I can help you out contact me on telegram @cha0scl0wn. Regards.
Thank you guys so much for your replies!
I managed to launch the Preconfig dialog (dialing *#272*62826# in the stock phone app - other codes did not work, also tried the google phone app - nothing) but the only options to change the CSC are those in the picture (AMO - Orange Spain, FTM - Orange France etc). Basically I can select another Orange CSC which does not help. I want to change it to unbranded, to get the firmware updates directly from Samsung.
Now, if I root the phone, will I be able to change ORO to unbranded? But I'm a bit confused because rooting cancels OTAs, right? So I need to root, change CSC to unbranded (if possible) and then install the update myself? But then I will have to manually install every update?
If I root, change CSC to unbranded, install the update, unroot will I get the OTAs?
Rooting also kills Knox and Samsung Pay?
Thanks again guys for responding! I appreciate it! Cheers!
I managed to launch the Preconfig dialog (dialing *#272*62826# in the stock phone app - other codes did not work, also tried the google phone app - nothing) but the only options to change the CSC are those in the picture (AMO - Orange Spain, FTM - Orange France etc). Basically I can select another Orange CSC which does not help. I want to change it to unbranded, to get the firmware updates directly from Samsung.
Click to expand...
Click to collapse
Wow--you got lucky: I wasn't expecting the dialer code to work based both on my own experience and reports here on the forum. The Preconfig dialog is really just a testing tool: it allows you to select other CSC codes that already exist within the firmware and see the effects of those setting changes. I don't know if there is an effective unbranded configuration included on the OXM package (i.e., similar to XAA in the OYN package).
I don't have a lot of experience with the OTA updates (all my devices are unlocked).
Now, if I root the phone, will I be able to change ORO to unbranded? But I'm a bit confused because rooting cancels OTAs, right? So I need to root, change CSC to unbranded (if possible) and then install the update myself? But then I will have to manually install every update?
Click to expand...
Click to collapse
You'll still be able to select any CSC. I suppose in theory you could create your own CSC configuration for an imaginary carrier, but the route that I took was different. I stripped out all the unwanted junk out of the optics and prism images (along with de-bloating I did in a lot of other places in the ROM). I also edited all the XML configuration files that ship with the CSC to my liking (think: call recording on, shutter sound menu on, etc). After installing the resulting ROM, there was pretty much no carrier-specific software running on the device; splash screens, sounds, and other markings were also gone. I actually ended up adding a handful of carrier-specific content back to my ROM to get Wi-Fi calling working since it appears that the carrier I use (VZW) has a slightly nonstandard implementation of the feature.
But yes, once you head down this path, you'll be updating your phone by yourself, and it likely won't be the most enjoyable activity. I also don't feel the need for every single update, and I especially have no interest of moving to A12 in the foreseeable future.
Keep in mind that you should be able to pm disable bloatware packages that are really bothering you even without rooting/unlocking your bootloader.
Hi, a have recently purchased the XZ2 Compact single Sim model, it should arrive later this week. While waiting, I would appreciate everyone's opinion on which stock firmware version is best in terms of performance and battery life:
• Android 8 Oreo
• Android 9 Pie
• Android 10
Or if you guys haven't found a any difference, between firmware versions at all, then please comment below !
Thanks in advance.
David-538 said:
Hi, a have recently purchased the XZ2 Compact single Sim model, it should arrive later this week. While waiting, I would appreciate everyone's opinion on which stock firmware version is best in terms of performance and battery life:
• Android 8 Oreo
• Android 9 Pie
• Android 10
Or if you guys haven't found a any difference, between firmware versions at all, then please comment below !
Thanks in advance.
Click to expand...
Click to collapse
Latest 10 with eXistenZ patch - https://forum.xda-developers.com/t/rom-stock-xz2-xz2c-xz2p-existenz-quindim-v1-0-0-06-05-20.4095403/
levone1 said:
Latest 10 with eXistenZ patch - https://forum.xda-developers.com/t/rom-stock-xz2-xz2c-xz2p-existenz-quindim-v1-0-0-06-05-20.4095403/
Click to expand...
Click to collapse
Thanks for your suggestion, I just meant stock, without rooting, or installing any mods. Like has Sony made it worse with a9/a10 official update, or is there no major performance loss when upgrading ?
David-538 said:
Thanks for your suggestion, I just meant stock, without rooting, or installing any mods. Like has Sony made it worse with a9/a10 official update, or is there no major performance loss when upgrading ?
Click to expand...
Click to collapse
I have never used stock as-is, because of Sony bloatware, restrictions, etc, but I typically prefer stock UI over most custom ROM UIs, so if I can get eXistenZ, I will always go with it. @niaboc79 has been the master of Sony roms going back to at least 4.4. Between UI customization and under the hood type stuff, there's no better option I have found. With root and eXistenZ, the whole firmware is at your control...
If you're only interested in straight-stock vs. custom ROM, then custom ROM is by far better, but not sure why you would limit yourself to straight stock if that's the case, because you have to unlock bootloader and root to use custom ROM. The only advantage of straight stock is official support/security, which is arguably n/a in this case, since the last official update was 2 years ago...
levone1 said:
I have never used stock as-is, because of Sony bloatware, restrictions, etc, but I typically prefer stock UI over most custom ROM UIs, so if I can get eXistenZ, I will always go with it. @niaboc79 has been the master of Sony roms going back to at least 4.4. Between UI customization and under the hood type stuff, there's no better option I have found. With root and eXistenZ, the whole firmware is at your control...
If you're only interested in straight-stock vs. custom ROM, then custom ROM is by far better, but not sure why you would limit yourself to straight stock if that's the case, because you have to unlock bootloader and root to use custom ROM. The only advantage of straight stock is official support/security, which is arguably n/a in this case, since the last official update was 2 years ago...
Click to expand...
Click to collapse
Hi, ah yes, I also prefer rooting and custom roms, but there's chance the device won't be in unlocked, because I ordered it from Aliexpress, and it's the Japanese Docomo version. Anyway I also heard that some features and good photo quality, get lost when unlocking ? Is there a work around if the DRM keys get lost ?
David-538 said:
Hi, ah yes, I also prefer rooting and custom roms, but there's chance the device won't be in unlocked, because I ordered it from Aliexpress, and it's the Japanese Docomo version. Anyway I also heard that some features and good photo quality, get lost when unlocking ? Is there a work around if the DRM keys get lost ?
Click to expand...
Click to collapse
I don't think there's any such thing for this phone. Some have found a way to dump ta, but not to restore it, so not much use...
I upgraded to 10 to start with, then unlocked bl, etc. I think that's the best way. There's much discussion in the forums about camera function and drm in regards to 8 and 9, (ask @MartinX3 or @Pandemic), and seems like there may be different things you can do...
I'm not so hung up on the finer aspects of camera functionality. I think the difference is pretty subtle. Camera is good for me, (probably better on stock with unlocked bl than on custom/AOSP).
levone1 said:
I don't think there's any such thing for this phone. Some have found a way to dump ta, but not to restore it, so not much use...
I upgraded to 10 to start with, then unlocked bl, etc. I think that's the best way. There's much discussion in the forums about camera function and drm in regards to 8 and 9, (ask @MartinX3 or @Pandemic), and seems like there may be different things you can do...
I'm not so hung up on the finer aspects of camera functionality. I think the difference is pretty subtle. Camera is good for me, (probably better on stock with unlocked bl than on custom/AOSP).
Click to expand...
Click to collapse
Okay, thanks for the info. I'm new to Sony devices lol. Well I always wanted to try out a sony device. Anyway is 960fps video recording still there ? After unlocking your bootloader ?
levone1 said:
I have never used stock as-is, because of Sony bloatware, restrictions, etc, but I typically prefer stock UI over most custom ROM UIs, so if I can get eXistenZ, I will always go with it. @niaboc79 has been the master of Sony roms going back to at least 4.4. Between UI customization and under the hood type stuff, there's no better option I have found. With root and eXistenZ, the whole firmware is at your control...
If you're only interested in straight-stock vs. custom ROM, then custom ROM is by far better, but not sure why you would limit yourself to straight stock if that's the case, because you have to unlock bootloader and root to use custom ROM. The only advantage of straight stock is official support/security, which is arguably n/a in this case, since the last official update was 2 years ago...
Click to expand...
Click to collapse
Just flashed eXistenZ after seeing your opinion. But help me out... How do i know the flash is properly done if there is no kernel brand on device stats... Weird
Purplearyes said:
Just flashed eXistenZ after seeing your opinion. But help me out... How do i know the flash is properly done if there is no kernel brand on device stats... Weird
Click to expand...
Click to collapse
...
Purplearyes said:
Just flashed eXistenZ after seeing your opinion. But help me out... How do i know the flash is properly done if there is no kernel brand on device stats... Weird
Click to expand...
Click to collapse
Not sure what you mean by kernel brand, but you know if flashed properly because the ui and options will be drastically different with eXistenZ compared to stock. If everything's the same, then it's not flashed.
levone1 said:
Not sure what you mean by kernel brand, but you know if flashed properly because the ui and options will be drastically different with eXistenZ compared to stock. If everything's the same, then it's not flashed.
Click to expand...
Click to collapse
Yes i just realized the flash didn't went through. im experiencing many issues. Firstly twrp is not flashing anything always some error of storage access or something. then i try to flash on los recovery, and it works for lineage perfect flash, but for existenz stock zip it flashes everything no errors but doesn't change anything on the stock rom (.618 clean install) i can't seem to figure it out...
levone1 said:
Not sure what you mean by kernel brand, but you know if flashed properly because the ui and options will be drastically different with eXistenZ compared to stock. If everything's the same, then it's not flashedalso
levone1 said:
I have never used stock as-is, because of Sony bloatware, restrictions, etc, but I typically prefer stock UI over most custom ROM UIs, so if I can get eXistenZ, I will always go with it. @niaboc79 has been the master of Sony roms going back to at least 4.4. Between UI customization and under the hood type stuff, there's no better option I have found. With root and eXistenZ, the whole firmware is at your control...
If you're only interested in straight-stock vs. custom ROM, then custom ROM is by far better, but not sure why you would limit yourself to straight stock if that's the case, because you have to unlock bootloader and root to use custom ROM. The only advantage of straight stock is official support/security, which is arguably n/a in this case, since the last official update was 2 years ago...
Click to expand...
Click to collapse
I did some research and from what is logged on existenz page it includes nothing more than UI customizations? Am i missing something. How can this stock patch be the best for you if it only does UI changes..?
Click to expand...
Click to collapse
Purplearyes said:
Yes i just realized the flash didn't went through. im experiencing many issues. Firstly twrp is not flashing anything always some error of storage access or something. then i try to flash on los recovery, and it works for lineage perfect flash, but for existenz stock zip it flashes everything no errors but doesn't change anything on the stock rom (.618 clean install) i can't seem to figure it out..
Click to expand...
Click to collapse
- Which version of TWRP? Make sure you are using the right one. Should be this one - https://forum.xda-developers.com/xperia-xz2/development/recovery-twrp-3-3-1-0-t4074305
- Did you follow this, (from eXistenZ thread):
Flash latest android 10 firmware with Newflasher and boot it once.
Reboot in bootloader mode with adb (adb reboot boolloader) and boot TWRP (see TWRP thread for instructions).
Inside TWRP, go in settings and uncheck unmount system before flashing.
Mount system partition and Flash eXistenZ Quidim cleaner.
Boot once, it shouldn't reach pin code screen, reboot in bootloader mode with adb.
Boot TWRP, mount system partition and flash the rom.
Flash Magisk.
(e.g. - make sure to boot once before flashing, use adb for bootloader mode, check system in TWRP, etc...)
levone1 said:
- Which version of TWRP? Make sure you are using the right one. Should be this one - https://forum.xda-developers.com/xperia-xz2/development/recovery-twrp-3-3-1-0-t4074305
- Did you follow this, (from eXistenZ thread):
Flash latest android 10 firmware with Newflasher and boot it once.
Reboot in bootloader mode with adb (adb reboot boolloader) and boot TWRP (see TWRP thread for instructions).
Inside TWRP, go in settings and uncheck unmount system before flashing.
Mount system partition and Flash eXistenZ Quidim cleaner.
Boot once, it shouldn't reach pin code screen, reboot in bootloader mode with adb.
Boot TWRP, mount system partition and flash the rom.
Flash Magisk.
(e.g. - make sure to boot once before flashing, use adb for bootloader mode, check system in TWRP, etc...)
Click to expand...
Click to collapse
I used 3.4.00 twrp, maybe should try 3.3.10. Also i flashed .618 which is 10 though not the latest but it should be the same thing.
The rom seems to flash, because i get the existenz custom settings on phone settings, idk if that is all it does.