OTA update (temp folder location) - Xperia Z5 Q&A, Help & Troubleshooting

I have an Xperia Z5 with a custom bootloader and a TWRP recovery (obviously rooted and has the Xposed binaries installed). I've tried installing the OTA update for Android 6.0.1 but it keeps failing to install (re-downloaded it over 7 times).
I was wondering if anyone knew where the temporary folder is where the OTA update is stored before installation?
That way, I could download the OTA update again, move it to another folder and install it via the TWRP recovery.

Related

[Q] Question on updating through ota.

Hey. I was wondering if you could help me update my phone to the latest ota update. I'm rooted and have xposed installed, and anytime I try to update the zip fails to install. I've also tried removing xposed, but it still didn't work.
Any suggestions?
Marco_Mena said:
Hey. I was wondering if you could help me update my phone to the latest ota update. I'm rooted and have xposed installed, and anytime I try to update the zip fails to install. I've also tried removing xposed, but it still didn't work.
Any suggestions?
Click to expand...
Click to collapse
Use search, you can't use OTA on a rooted phone as rooting alters system files that the OTA expects to NOT be altered.
scott_doyland said:
Use search, you can't use OTA on a rooted phone as rooting alters system files that the OTA expects to NOT be altered.
Click to expand...
Click to collapse
In another thread they told me that I can update if my phone is rooted and with stock recovery.
What you can do is flash a custom recovery and then after copy the outs file from /cache to your PC. On your PC modify the updater-script and repack the zip file and flash it on your phone through custom recovery.
You can even unpack the contents of OTA. zip and manually copy it in your /system and fix the permissions.

how to update Android via OTA when Multirom and TWRP are installed

Hi,
today I received a security update in my Nexus 5. I accepted it and when rebooted it got stuck in the multirom menu and it didnt update anything. Last time I have to lock the device and flash the rooted image in order to proceed with the update. this time I would like to do it diferently if possible.
Is there any other way to flash the update without removing multirom and locking back the device?
where is the update.zip stored when the system automatically downloads the update? maybe I could manually flash it using the TWRP.
thanks!
Jose

Update a rooted Stock Nougat to Oreo?

Hi,
I've got a MHA-L29 C432 B198.
Currently the bootloader is unlocked, TWRP flashed into 1st recovery partition and phh's Superuser installed.
Now I got a message that Orea is available and even downloaded... but I cannot find any dload folder or anything else with >2GB on the sdcard.
Anyhow, I would like to know if I could simply start the update when I flash stock recovery again. Or will it trouble with root?
My phone is setup like yours but I'm L29 C567 B190 and xposed installed, I just tried to take the OTA update by flashing back the stock recovery and it still fails.
Can someone point me to the correct path to either take the OTA update, or to a TWRP flashable version of the update? I'm still new to the Huawei ecosystem (or lack thereof) and cannot determine how to do this properly and desperately want to avoid wiping my phone in the process.

Update Troubles

Hi everybody, i am currently running OxygenOS 5.1.0 and i am trying to update to latest version.
1. I tried with local update inside settings but nothing the message is: unable to install system update
2. I tried unlocking bootloader, installing TWRP and trying to install update via TWRP but i get stuck in Error7, seems like the package is not recognized for my phone.
I rad a lot about removing assert rows inside update scripts in the .zip package. Unfortunately in my package there is no update-script and i don't know any possible way to force my installation. Do you have any suggestion?
I'd recommend to go back to full stock (lock bootloader) and then try to do all the OTA updates. It's not working for you this way?

Custom ROM

Hello, will it be possible to return from custom firmware to the original one and continue to receive OTA update ?
Uxlewl said:
Hello, will it be possible to return from custom firmware to the original one and continue to receive OTA update ?
Click to expand...
Click to collapse
Yes, if you used TWRP to create a backup of your stock ROM before you flashed a custom ROM, you just use TWRP to restore the backup of stock ROM.
Or, if you didn't use TWRP to backup your stock ROM, you can flash your device's stock firmware using the flashtool designed to be used with devices made by your device's manufacturer.
But to install TWRP you need Root, and if you get it, then OTA updates stop coming or am I wrong?
Uxlewl said:
But to install TWRP you need Root, and if you get it, then OTA updates stop coming or am I wrong?
Click to expand...
Click to collapse
No, installing TWRP does not require root. Yes, TWRP and root prevent the installation of OTA updates.
That is, to make a backup copy of the original firmware, you need TWRP, but if you install it, you lose the ability to receive OTA updates, and if you restore the original after the custom firmware, there will be no updates? Or can TWRP be removed and OTA updates will come again? I'm sorry I do not understand.
Uxlewl said:
That is, to make a backup copy of the original firmware, you need TWRP, but if you install it, you lose the ability to receive OTA updates, and if you restore the original after the custom firmware, there will be no updates? Or can TWRP be removed and OTA updates will come again? I'm sorry I do not understand.
Click to expand...
Click to collapse
To be more specific, installing TWRP does not necessarily prevent a device from actually receiving/downloading OTA updates, it prevents the actual installation of OTA updates because part of the OTA update includes automatically booting into stock recovery to apply the update. If you have TWRP installed, the OTA update can possibly be downloaded to the device but when the device automatically tries to reboot into recovery, it is trying to boot into stock recovery but if you have TWRP installed, it can't boot into stock recovery to apply the update and when it tries to boot into TWRP, it will try to apply the update but it will fail, resulting in a bricked device and the device will have to be restored.
When it comes to OTA updates, all that is required is an unmodified stock system partition(meaning, no root or any other kind of modifications to the system partition), stock recovery(meaning, no TWRP) and the update has to be offered by your carrier if they offer the update for your specific device.
If a device is rooted, has other system modifications and/or has TWRP installed and you want to apply a stock OTA update, you have to remove root and any other system modifications and you must replace TWRP with the original stock recovery before you can apply the update. If you have TWRP and or root and you remove them to apply an OTA update, you can root the device again and install TWRP again after the update, provided that the OTA does not come with a locked bootloader that can not be unlocked, in this case, you will not be able to reinstall TWRP or root because the bootloader will be locked, which prevents you from installing TWRP again. Sometimes, users remove root and TWRP to apply OTA updates with the intention of rooting and/or installing TWRP again after the update but then get stuck in a position where they can no longer root the device or install TWRP because the bootloader gets locked during the update and there is no way to unlock the newly updated bootloader, from then on, they are stuck with stock with no way to get root, TWRP and custom ROMs reapplied to the device because they were not aware that the update came with a locked bootloader that can not be unlocked by any means.

Categories

Resources