Related
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.
I have a new Moto G5 here and i'm wondering if I should install a custom 8.1 ROM.
I'm not new to TWRP, ROM installation and other things related, but I want to know:
- are the most recent ROMs stable enough for daily use (if so, which one should I choose? battery life should be at least solid)?
- are there any major problems/incompatibilites when using those ROMs ("camera in video mode not recording" and other things?)?
- which way is safe to prevent those common IMEI-loss/IMEI-0 problems? Or is it still a jeopardy? Is there a good guide somewhere?
Thank you in advance!
you should install atomic os
Camera doesn't work very well without using a third-party application such as Footej. USB tethering doesn't work and it doesn't seem to be a priority.
An advice: don't attempt to go back to stock after installing an 8.1 ROM (at least for now). Don't perform the "fastboot erase modemst1" or "fastboot erase modemst2" commands when flashing something manually. And, finally, don't even try to downgrade using a fastboot ROM (or RSD Lite); you will effectively kill your device with no other (current) solution than replacing the whole motherboard.
They're more stable and faster than stock 7.0, except for the camera bugs. While Motorola does not release the official blobs, it will not have how to fix the bugs.
If you want to go back to stock rom, install a debloated ROM.
Read this article that I wrote of how not to lose the IMEI or hardbrick the device.
There are so many dangers to installing oreo that whenever I begin to consider it, I always end up deciding not to
Will Motorola ever release the blobs? Or is it unknown?
Exanneon said:
There are so many dangers to installing oreo that whenever I begin to consider it, I always end up deciding not to
Will Motorola ever release the blobs? Or is it unknown?
Click to expand...
Click to collapse
I hope it releases before the christmas xD
Same, the sooner the better, I really want a stable oreo experience.
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
Hi all,
so my current smartphone died for good and instead of getting a new one, I thought I'd revive my old Sony Xperia Z1 Compact. It's been a while since I switched it on so the battery is dead but I'm planning to buy a new battery and replace it. Then I plan to install LineageOS (which is based on Android 10 I believe?)
However I've never done rooting or anything more than basic end user stuff so I've searched the internet and thought I needed to root my phone and then flash the LineageOS. I've read some beginner guides on this forum and other places. However, I've ran into some conflicting/confusing(?) info and need some clarification before starting out. Hope someone can help with my admittedly-very-noobie questions:
1) Can I install LineageOS WITHOUT rooting my phone?
I believe that the bootloader needs to be unlocked first but is rooting necessary? The reason being is that I just want to get rid of the current stock ROM (I think it was Lollipop - can't know for sure because the new battery hasn't arrived yet) and install LineageOS. I don't want a rooted phone because it might conflict with banking apps and such (I know there are workarounds i.e. masking/reflashing/unrooting but as I am not that familiar with the development systems I will just be exposing myself to unknown vulnerabilities) so is it possible to just have the custom ROM and not completely root the phone?
2) Unlocking the bootloader
So I read I have to do a backup first before unlocking the bootloader. Is an SD card necessary or only for rooting? Since unlocking the bootloader will format the SD card anyway? Where should the backup be stored then?
I'd really appreciate some guidance. Thanks!!
Cheers,
traegr
LineageOS or most other roms aren't rooted by default. You will have to install solutions like magisk.
If you install twrp https://forum.xda-developers.com/sony-xperia-z1-compact/development/recovery-twrp-3-3-1-t3960699 make sure you are on latest stock firmware as you need the latest bootloader which allows booting into recovery. Flash firmware with Xperia Flashtool which has inbuilt firmware downloader. http://www.flashtool.net/index.php
If you can't boot into TWRP, you can try flashing attached file with xperia flashtool.
Instead of unofficial lineage I recommend AICP forum.xda-developers.com/sony-xperia-z1-compact/orig-development/rom-aicp-15-0-q10-0-amami-t4005457 . It's got good battery life and nice inbuilt tweaks and customization options..
Hope this helps
Also you need to flash Gapps if you want to use certain apps. Important point for AICP is that you can use microg instead. https://microg.org/
drater2 said:
LineageOS or most other roms aren't rooted by default. You will have to install solutions like magisk.
If you install twrp https://forum.xda-developers.com/sony-xperia-z1-compact/development/recovery-twrp-3-3-1-t3960699 make sure you are on latest stock firmware as you need the latest bootloader which allows booting into recovery. Flash firmware with Xperia Flashtool which has inbuilt firmware downloader. http://www.flashtool.net/index.php
If you can't boot into TWRP, you can try flashing attached file with xperia flashtool.
Instead of unofficial lineage I recommend AICP forum.xda-developers.com/sony-xperia-z1-compact/orig-development/rom-aicp-15-0-q10-0-amami-t4005457 . It's got good battery life and nice inbuilt tweaks and customization options..
Hope this helps
Click to expand...
Click to collapse
Hi, thanks for replying.
What's the difference between the lineage and AICP?
traegr said:
Hi, thanks for replying.
What's the difference between the lineage and AICP?
Click to expand...
Click to collapse
AICP provides more customizations while lineage is a "cleaner" approach. In the end AICP builds on top of lineage sources and adds several features. It totally depends on your personal taste. I consider it to be a bit overloaded. But that's my opinion. Which may be a bit influenced as I build the lineage version. Hehe
But once you have a recovery set up you can easily flash one, test it, and try the other one afterwards.
Hardware functionality should be same as AICP (SpiritCroc) and lineage (mse and me) share the same device tree sources. If one of us repairs something the other one will also get the fixes.
Both AICP and lineage have OTA update support. If you need microg you can either go with AICP 15 (Android 10) or Lineage 16 (Android 9).
Also you can easily backup your entire system with twrp if something goes wrong when flashing or whatever.
And when "hopping" roms you can make backups with Titatnium (root needed)
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.