Multiple Questions about System Update (Solved) - Xperia Z5 Premium Q&A, Help & Troubleshooting

Hey xda-Community!
I've got a Z5P on Android Version: 6.0, Build: 32.1.A.1.185, Kernel Version: 3.10.84-perf-g19d6d92, SuperSU: v2.78 and TWRP Version on 3.0.2-0.
I've recovered my DRM Keys and unlock-rooted with this guide.
I've experienced some annoying problems with the OS (Fingerprint, Youtube not working, random forced process kills) and would like to update it. Sadly I forgot how to update and i'm not totally sure about the correct way. Now my questions are:
1. Do I normally update with Flashtool?
2. What do I need to do while updating? Reflash SU Binary, DRM Key restore
3. What should I backup over TWRP? (Would be great if I could keep OS and App settings...)
I've read somewhere about problems with a TWRP backup, which could (soft)-brick the phone...
Thanks for your help
http://forum.xda-developers.com/z5-...ting-xperia-z5-z5p-variants-drm-keys-t3437902
http://forum.xda-developers.com/z5-premium/general/32-1-1-185-stock-modified-kernel-t3355369

Nevermind, found out how to update, I need modified kernel for this.
I'll just reflash everything I had before (SuperSU, DRM Restore, XPosed,...)

Related

[Q] Newb M8 questions

Hi all,
Long time reader, first time poster.
Please don't kill me if my questions are somehow dumb. I promise I searched the web and xda thouroughly before posting.
1) I rooted my phone with HTCDev.com for the sole purpose of installing titanium backup. I tried to unintall some unwanted bloatware (scribble, tv, twitter, zoe, fitbit and more...) but they keep returning after boot. Why is that? Is it related to S-on? Is there a simple way to fix this?
2) My current software version is 1.54.707.7, I can update OTA to 2.22.707.3. Should I? From my experience with my previous samsung device, I'm afraid that updating blindly can cause more harm than good at some cases.
3) Can I update OTA even when I'm rooted? Will I need to replace the recovery and root again?
Thanks in advance,
Tal
talla1 said:
Hi all,
Long time reader, first time poster.
Please don't kill me if my questions are somehow dumb. I promise I searched the web and xda thouroughly before posting.
1) I rooted my phone with HTCDev.com for the sole purpose of installing titanium backup. I tried to unintall some unwanted bloatware (scribble, tv, twitter, zoe, fitbit and more...) but they keep returning after boot. Why is that? Is it related to S-on? Is there a simple way to fix this?
2) My current software version is 1.54.707.7, I can update OTA to 2.22.707.3. Should I? From my experience with my previous samsung device, I'm afraid that updating blindly can cause more harm than good at some cases.
3) Can I update OTA even when I'm rooted? Will I need to replace the recovery and root again?
Thanks in advance,
Tal
Click to expand...
Click to collapse
Hi Tal,
ok let's see if I can help you a little bit.
Regarding (1) I got a question: where and which files of the named apps did you delete?
Regarding (2) Sure you could update vis OTA as long as all system apps and stock recovery ist installed. Did you reinstall stock recovery, or are you unsing some custom recovery? As with custom recovery you can download but not install the OTA. This can then be done even if you are rooted. If you use supersu having the pro version installed you could try activating OTA survival mode and maybe root acces will still be there after performing the OTA. If not you could simply reinstall a custom recovery and using this root.
Hope this helps!?
If you could give me some answers regarding (1) I'll try to help ypu with this as well.
HTCNerdYoda said:
Hi Tal,
ok let's see if I can help you a little bit.
Regarding (1) I got a question: where and which files of the named apps did you delete?
Regarding (2) Sure you could update vis OTA as long as all system apps and stock recovery ist installed. Did you reinstall stock recovery, or are you unsing some custom recovery? As with custom recovery you can download but not install the OTA. This can then be done even if you are rooted. If you use supersu having the pro version installed you could try activating OTA survival mode and maybe root acces will still be there after performing the OTA. If not you could simply reinstall a custom recovery and using this root.
Hope this helps!?
If you could give me some answers regarding (1) I'll try to help ypu with this as well.
Click to expand...
Click to collapse
Thanks for the detailed and fast response, Yoda!
Regarding (1), I'm not sure I understand what you mean "where and which files". I backed up the mentioned apps in titanium backup, and then uninstalled them, again, with titanium backup. This method worked for me on my previous device (Samsung i9300).
Regarding (2), that's valuable information that I did not get anywhere from reading the sticky posts. I didn't know that the original recovery is needed in order to update OTA. I installed TWRP in order to install SuperSU. Is there a specific version of stock recovery that goes with the device? Or is there just one stock recovery for m8?
I had another question hidden in there, I'll make it number 3:
(3) Can someone tell me if the 2.22.707.3 version is any good? Stable enough? Or should I stick with 1.54.707.7 in the meanwhile?
Thanks allot!
Tal
talla1 said:
Thanks for the detailed and fast response, Yoda!
Regarding (1), I'm not sure I understand what you mean "where and which files". I backed up the mentioned apps in titanium backup, and then uninstalled them, again, with titanium backup. This method worked for me on my previous device (Samsung i9300).
Regarding (2), that's valuable information that I did not get anywhere from reading the sticky posts. I didn't know that the original recovery is needed in order to update OTA. I installed TWRP in order to install SuperSU. Is there a specific version of stock recovery that goes with the device? Or is there just one stock recovery for m8?
I had another question hidden in there, I'll make it number 3:
(3) Can someone tell me if the 2.22.707.3 version is any good? Stable enough? Or should I stick with 1.54.707.7 in the meanwhile?
Click to expand...
Click to collapse
(1) there are two folder /system/app and /system/priv-app. And overall there is the rw settings of the new kernel used. To be abled to unistall unwanted system apps maybe take a look at this post: http://forum.xda-developers.com/showthread.php?t=2723463, as maybe you need another kernel to accomplish it.
(2) you have to use a corresponding recovery, meaning you would have to download the 1.54.707.7 recovery (just google for it and you should find it in any forum) to work.
(3) I'm sorry that I can't be of any help here, as I performed an S-OFF debranding my phone and changin the CID to HTC__102 right from the start, setting it up to be on the WWE 2.22.401.4 since then.
3) the newest update (2.22 one) is very stable for me, no problems at all.
Sent from my One M8 using XDA Free mobile app
Thanks for this information!
Sent from my HTC One_M8 using XDA Free mobile app
HTCNerdYoda said:
Thanks for this information!
Click to expand...
Click to collapse
1) HTCDev unlocks the boot loader, it doesn't root. This can delete some default system apps, preventing an OTA. In order to have changes to system stick after reboot you need a kernel module: http://forum.xda-developers.com/showthread.php?p=51543139
2) Don't worry, HTC are much better with updates than Samsung. They work, you can trust them.
3) Once you have unlocked boot loader, you may struggle to update OTA due to the missing apps, but there are threads here explaining what to do. As mentioned, you'll need stock recovery and yes, you may need to root again, after installing your custom recovery after the update.
BenPope said:
1) HTCDev unlocks the boot loader, it doesn't root. This can delete some default system apps, preventing an OTA. In order to have changes to system stick after reboot you need a kernel module: http://forum.xda-developers.com/showthread.php?p=51543139
2) Don't worry, HTC are much better with updates than Samsung. They work, you can trust them.
3) Once you have unlocked boot loader, you may struggle to update OTA due to the missing apps, but there are threads here explaining what to do. As mentioned, you'll need stock recovery and yes, you may need to root again, after installing your custom recovery after the update.
Click to expand...
Click to collapse
Thanks for all the valuable info!!
I tried searching for the recovery, but as always, it's not that simple.. Too many sources of information and I don't know who's genuine. I haven't found a link on XDA yet (to the full stock ROM yes, not for the recovery only).
You say that OTA is a hassle when the recovery is replaced. I'm not stressed on upgrading OTA. How WOULD YOU SUGGEST to upgrade? Downloading the newest stock from XDA and using fastboot?
I created nandroid backups before but never restored one, so JUST TO BE SURE: this backup will be the full snapshot? Meaning: my old version (if the new one sucks) + apps + data? I don't need to backup ANYTHING except doing a nandroid backup?
Thanks again.
Tal
UPDATE: dug around some more and found the stock recoveries here after following the link from this post.
But before I flash anything, I just want to make sure that:
1) The nandroid I'll do in TWRP is the only backup I need to do.
2) There is no simpler option than returning to stock recovery, updating OTA, returning to TWRP recovery, rooting.
Tal

Systemless OTA upgrade

I know there are several threads covering similar things, however I still can't find the relevant info for my specific question.
I am on 6.0 Build L
I rooted using systemless root - I have changed nothing in my system partition as far as I know as I wanted root for AdBlock and TitaniumBU.
I am using the stock kernel too.
TWRP 2.8.7.2
I now have a 6.0.1 OTA - but I'm 100pc confused as to exactly how to go about installing this.
Some people seem to say OTA on this setup will work fine on similar setups.
Others say I need to flash 101 things to get it working.
Literally no idea.
How I Did it...
From a site with this in the title:
can_i_manually_flash_601_also_does_ota_work_with
Systemless root doesn't break ota, non-stock recovery breaks OTA.
Unlock bootloader, flash 6.0.1, flash TWRP, flash systemless root...
I did this:
Went back to stock recovery, by flashing via ADB, rebooted downloaded and attempted to install OTA on phone. Process started, rebooted, proceeded and then failed with error . Rebooted, got Factory image.
Extracted and ran flash-all.bat ONLY AFTER Removing the -w from this line:
fastboot -w update image-bullhead-mmb29k.zip
Got latest SuperSU v2.61 zip with auto boot patcher:
See androiding.how/android-6-0-1-root
Copied this to Memory on phone.
Flashed/Installed TWRP Recovery using ADB.
Booted into TWRP Recovery and installed SuperSU.
So now I'm running systemless rooted 6.01 on a Nexus 5X with mmb29k and every thing is working.
I think even though I rooted systemless 6.0, the modified Boot Image was still not letting OTA work.
We shall have to wait and see on the next OTA. Maybe just going back to stock recovery will be all that's needed.
There are some ADB commands that allow you to temporarily select a recovery image, but I'm not sure how that works.
Good Luck!
teapea said:
I know there are several threads covering similar things, however I still can't find the relevant info for my specific question.
I am on 6.0 Build L
I rooted using systemless root - I have changed nothing in my system partition as far as I know as I wanted root for AdBlock and TitaniumBU.
I am using the stock kernel too.
TWRP 2.8.7.2
I now have a 6.0.1 OTA - but I'm 100pc confused as to exactly how to go about installing this.
Some people seem to say OTA on this setup will work fine on similar setups.
Others say I need to flash 101 things to get it working.
Literally no idea.
Click to expand...
Click to collapse

Help updating from Marshmallow to Nougat

Hello all,
For the last 4-5 firmware updates I've had no issue using fastboot to flash the firmware images, then flashing SuperSU, ElementalX kernel, Viper4Android and AdAway host lists through recovery to update to the latest build but keep my root mods.
I would like to now to the same with DP5 (or, at the very least, the first official Nougat build when it drops soon) and make sure I do it safely without any bricking.
Here's the current status -
Bootloader: Unlocked
Build: Android 6.0.1 MTC19Z, July Security Patch
Root Status: Rooted
Root Mods: ElementalX Kernel, Viper4Android, AdAway
Essentially, I want the same set up/root mods as above, only on 7.0. My questions are as follows:
1. Does the process differ at all for both installation of the firmware (through fastboot) or root method (flash TWRP, flash SuperSU)?
2. Is a full data wipe required? Recommended?
3. Anything else I should know?
Thanks in advance for the help. I'd love to make this as painless as the monthly firmware updates without any hiccups.
- Moonboots
The process does not differ much for the installation of the firmware; all you need to do is flash the factory images and TWRP through fastboot, and flash SuperSU/root through TWRP.
However, for a working TWRP and root, you'll need to decrypt your phone again, which will of course wipe your phone's data and internal storage.
I suggest looking at this helpful thread over on the Nexus 6P forums saying how to switch to 7.0 here:
http://forum.xda-developers.com/nexus-6p/general/how-to-switch-to-android-n-preview-t3409538
Even though it's for the 6P, I have used it myself and the procedure is the same. Once you've done all that, you're good to flash the latest SuperSU through TWRP.
As for V4A, I'm not sure whether it is compatible with Android N yet. You can install the ElementalX kernel normally after installing 7.0, but I don't think it's been updated to DP5.
If you do decide to update to Nougat, the modified boot.img for NPD90G can be found here:
http://forum.xda-developers.com/nexus-5x/general/4-17-16-t3360574
Thank you! I actually kept my phone encrypted all this time. Have you seen significant performance increases by decrypting?
EDIT: I see it's actually necessary for working TWRP in 7.0, thus far. Interesting. I'll have to work on getting my data backups set tonight.

Official Android Nougat, phh Superuser, Magisk Mod

Hello all,
Yesterday I did what many did and upgraded to Nougat as soon as it dropped, using the "sign up for Android beta" method. I came from a bootloader unlocked, rooted Nexus 5x running the latest version of 6.0.1 with a few basic mods - AdAway, Viper4Android, ElementalX Kernel w/ profile manager, Cf.Lumen and Greenify.
In upgrading to Android 7.0, I first flashed the system, vendor, boot and recovery image from the most recent version of 6.0.1 to revert completely to unrooted stock before taking the OTA.
After reading about this new method of systemless root that also seems to allow Android Pay to work, I'm trying to wrap my head around it before trying, and wanted some of the wise minds of XDA to confirm my procedure.
Current Status-
Device: Nexus 5x
Build: Android 7.0 NRD90M
Unlock Status: Bootloader Unlocked
Root Status: Unrooted
Boot.img and Recovery.img: Stock
Procedure:
1. Download latest TWRP, boot device into fastboot mode, and "fastboot flash recovery [TWRP file]"
2. Navigate to TWRP Recovery, locate phh root .zip (already downloaded to device), Magisk mod and ElementalX kernel, flash these.
3. Once booted, follow directions in the Magisk thread to mount the desired mods (AdAway, Viper4Android, etc.) while still passing SafetyNet check, and Android Pay will continue to work.
Also, if I understand correctly, future system updates will be possible using FlashFire and the OTA .zip while maintaining root status and the modifications, since \system is not modified using this method.
Any confirmation/feedback is welcome!
Thanks,
Moonboots
Moonboots said:
Hello all,
Yesterday I did what many did and upgraded to Nougat as soon as it dropped, using the "sign up for Android beta" method. I came from a bootloader unlocked, rooted Nexus 5x running the latest version of 6.0.1 with a few basic mods - AdAway, Viper4Android, ElementalX Kernel w/ profile manager, Cf.Lumen and Greenify.
In upgrading to Android 7.0, I first flashed the system, vendor, boot and recovery image from the most recent version of 6.0.1 to revert completely to unrooted stock before taking the OTA.
After reading about this new method of systemless root that also seems to allow Android Pay to work, I'm trying to wrap my head around it before trying, and wanted some of the wise minds of XDA to confirm my procedure.
Current Status-
Device: Nexus 5x
Build: Android 7.0 NRD90M
Unlock Status: Bootloader Unlocked
Root Status: Unrooted
Boot.img and Recovery.img: Stock
Procedure:
1. Download latest TWRP, boot device into fastboot mode, and "fastboot flash recovery [TWRP file]"
2. Navigate to TWRP Recovery, locate phh root .zip (already downloaded to device), Magisk mod and ElementalX kernel, flash these.
3. Once booted, follow directions in the Magisk thread to mount the desired mods (AdAway, Viper4Android, etc.) while still passing SafetyNet check, and Android Pay will continue to work.
Also, if I understand correctly, future system updates will be possible using FlashFire and the OTA .zip while maintaining root status and the modifications, since \system is not modified using this method.
Any confirmation/feedback is welcome!
Thanks,
Moonboots
Click to expand...
Click to collapse
Howdy sir! I'm still learning myself so I can't give you a great answer, but it's been a few weeks so I thought maybe you already gave this a shot? I'm looking to follow about the same process soon. I'm currently bootloader unlocked with TWRP loaded on Nougat (NRD90S on 5X).
How'd this go for ya?
Thanks!

How to operate with Stock ROM

Hi,
I have question. All my devices (present and also all previous) I have rooted, unlock bootloader, have custom recovery and so on.... and I flash always some custom ROM. And now I have idea, that I want to used as daily driver customized Stock ROM. I know it's nothing new, but I want to keep:
- custom recovery
- unlock bootloader
- root
- busybox
I know, that it is very easy. But - and now my question (it is what I don't know) - when comes some monthly update, how can I do update to latest Stock ROM (downloaded from Google Factory Image) without lost of unlock bootloader, root without losing data and so on.....
How can I update Stock ROOTed ROM with keep all data and settings?
I can imagine, that I flash only system.img which I root after that or something like this. Maybe is this beginners question, but I want to try it and I'm not sure how to....
Can somebody describe this procedure step by step (first flash and each update).
Thank you in advance
Just extract the zip you download from Google Factory Images and flash system, vendor and boot via fastboot.
https://elementalx.org/how-to-install-android-monthly-security-updates/
....EDIT....
Everything seem to be fine. My previous problem was that I tried to flash wrong version of SuperSU....

Categories

Resources