Related
Hi All
I have a nexus 9 with an unlocked bootloader, root (from CF auto-root), and TWRP installed, currently on 5.0.1 LRX22C. I have read this means that I will not be able to complete an OTA due to lack of stock recovery and changes within the system files that the OTA will check.
So my question is how much of stock do I have to return to be able to do the OTA to 5.0.2 and 5.1 later today. I am hoping that I won't have to do a factory reset and wipe all the files and apps, but if so nevermind.
Do I have to relock the bootloader?
Do I have to flash back to stock completely or can I just flash a stock recovery?
If I wait will a flashable zip be created by someone, that would allow me to keep unlocked and rooted?
If this has been asked before, I am sorry, I have searched but couldn't find any clear answers that were related to lollypop.
I am used to samsung phones and the nexus ADB sideloading ect. is taking me a while to get used to, so any link to a guide would be very appreciated.
Thanks for any help,
OTA appears to checksum the entire partitions, so even remount RW could have an effect (with no intentional accesses, depending how the filesystem works). However, this doesn't make a lot of sense since any update is going to struggle to replicate the same raw filesystem data reliable - maybe this is why we are seeing 5.0.2 OTAs fail on 'stock' devices.
fallen2004 said:
Hi All
I have a nexus 9 with an unlocked bootloader, root (from CF auto-root), and TWRP installed, currently on 5.0.1 LRX22C. I have read this means that I will not be able to complete an OTA due to lack of stock recovery and changes within the system files that the OTA will check.
So my question is how much of stock do I have to return to be able to do the OTA to 5.0.2 and 5.1 later today. I am hoping that I won't have to do a factory reset and wipe all the files and apps, but if so nevermind.
Do I have to relock the bootloader?
Do I have to flash back to stock completely or can I just flash a stock recovery?
If I wait will a flashable zip be created by someone, that would allow me to keep unlocked and rooted?
If this has been asked before, I am sorry, I have searched but couldn't find any clear answers that were related to lollypop.
I am used to samsung phones and the nexus ADB sideloading ect. is taking me a while to get used to, so any link to a guide would be very appreciated.
Thanks for any help,
Click to expand...
Click to collapse
Do not relock your bootloader. It is not necessary.
Since you are rooted with a custom recovery, if you want to take the OTA, you will have to fastboot flash the stock 5.0.1 system.img, recovery.img, boot.img, and vendor.img.
IMHO, it's just as easy to fastboot flash the 5.0.2 factory images and forget about the OTA.
cam30era said:
Do not relock your bootloader. It is not necessary.
Since you are rooted with a custom recovery, if you want to take the OTA, you will have to fastboot flash the stock 5.0.1 system.img, recovery.img, boot.img, and vendor.img.
IMHO, it's just as easy to fastboot flash the 5.0.2 factory images and forget about the OTA.
Click to expand...
Click to collapse
Okay well I think I will wait until the 5.1 factory image is released, backup my phone, then fastboot flash it.
I guess I will then have to reroot and add TWRP again?
fallen2004 said:
Okay well I think I will wait until the 5.1 factory image is released, backup my phone, then fastboot flash it.
I guess I will then have to reroot and add TWRP again?
Click to expand...
Click to collapse
Do it in the other order. Fastboot flash TWRP, then flash SuperSU from inside TWRP. Very easy.
I got the update for the January Security Update today. I grabbed the .zip's location and the link on Google's servers is:
https://android.googleapis.com/pack...51c56752.signed-angler-MMB29P-from-MMB29M.zip
Hope it helps others!
PSA: this is not flashable over custom ROMs, and cannot be used to install the factory OS from nothing. That's what the factory images are for . This .zip is solely to incrementally update from the December security update to the January one.
Is there an easy way to flash this update.zip without the need of a computer?
tinker_tf said:
Is there an easy way to flash this update.zip without the need of a computer?
Click to expand...
Click to collapse
Unless you have a custom recovery, no. Sorry about that
Updated. Thanks for the link!
I have a rooted, stock ROM and TWRP and with several Xposed Modules, can I flash this?
Also, I don't have the December update, where do I find that?
And lastly, I'm on MDB08L Build, will that work?
For those wanting to use this update and have completely stock system based on MMB29M. Boot into recovery and do an ADB sideload update.zip (rename zip first). Mine updated with no issues.
CipherSec said:
I have a rooted, stock ROM and TWRP and with several Xposed Modules, can I flash this?
Click to expand...
Click to collapse
If you've got all that set up, why not just update using the full factory image (without the wipe)
LeoRex said:
If you've got all that set up, why not just update using the full factory image (without the wipe)
Click to expand...
Click to collapse
I assumed I'll lose all my system modifications (i.e. Xposed Modules and their settings) as well as losing root and TWRP and having to reroot again.
pmedwards25 said:
Unless you have a custom recovery, no. Sorry about that
Click to expand...
Click to collapse
This is exactly the file you need if you don't have custom recovery, don't have root, and have not unlocked bootloader. It is the same file that would eventually come to you OTA. You do however need access to adb and a computer. I don't think this is flashable with a custom recovery.
Thanks..
Thanks for this file bro. dont need to wait.
Alright, feeling like a complete noob, here. I'm on systemless root 2.61 with TWRP. I fastboot flashed the stock boot.img and stock recovery, then tried to sideload the OTA zip. I got a "system contains unexpected contents" error, then installation aborted. Now, with systemless root, I had the understanding that flashing the stock system.img would not be necessary. I was not using systemless root before when I flashed the previous OTA zip. Can anyone spot where I might have gone wrong?
Casyis said:
Alright, feeling like a complete noob, here. I'm on systemless root 2.61 with TWRP. I fastboot flashed the stock boot.img and stock recovery, then tried to sideload the OTA zip. I got a "system contains unexpected contents" error, then installation aborted. Now, with systemless root, I had the understanding that flashing the stock system.img would not be necessary. I was not using systemless root before when I flashed the previous OTA zip. Can anyone spot where I might have gone wrong?
Click to expand...
Click to collapse
Try flash stock system image
Does this update fix the LTE issue?
HRodMusic said:
Does this update fix the LTE issue?
Click to expand...
Click to collapse
No it does not
I got it:
For systemless root, fastboot flash: 1) boot.img; 2) recovery.img; 3) vendor.img; 4) system.img
Boot to recovery and enter sideloade mode. adb sideload [update].zip
Reboot to bootloader. Re-flash TWRP, then in TWRP re-flash kernel (if custom) & superSU.
I used a toolkit to root my 6P. I'm using rooted stock rom. I got an OTA update but it seems I can't update it that way as per all others. So how do I go about installing this on my mobile? Do I need to unroot, flash stock recovery & then flash the new image? Then again I have to root?
fyi: i'm rooted with systemless root and twrp
I tried to take this update per usual as i would if i were unrooted, of course that didn't work totally. i assumed i would just find the update.zip file (i did: /data/data/com.google.android.gms/app.download/update.zip, icywtk) but when i tried to flash that it said the zip was corrupted. i deleted the zip and now it still says my december build is up to date. can't we just flash the update.zip with twrp? i did allow for the system to be modified this time when i booted twrp.
asj0422 said:
fyi: i'm rooted with systemless root and twrp
I tried to take this update per usual as i would if i were unrooted, of course that didn't work totally. i assumed i would just find the update.zip file (i did: /data/data/com.google.android.gms/app.download/update.zip, icywtk) but when i tried to flash that it said the zip was corrupted. i deleted the zip and now it still says my december build is up to date. can't we just flash the update.zip with twrp? i did allow for the system to be modified this time when i booted twrp.
Click to expand...
Click to collapse
I am rooted with twrp. Same deal, twrp reports and error 7 when trying to flash the Jan security update.
kmp14 said:
I am rooted with twrp. Same deal, twrp reports and error 7 when trying to flash the Jan security update.
Click to expand...
Click to collapse
i just tried this again with the same results. it says that the installer is expecting a different build (the one that my settings app shows i'm on) but that i have a build called huawei/mmasomething/ dee_stroyer somethingsomething. (i would post exactly what it says but i've already rebooted into system). I do remember something with "dee_stroyer" when i was rooting but it's not the system...
anyone else have any ideas? i'd like to just update normally and keep my data... and the stock android with root.
EDIT: also, the update won't update my recovery will it? i don't want to have to reflash that. i should be able to update even when i'm away from a computer haha.
Rooted with TWRP. I just tried an ADB sideload and get the same error.
As the tiltle says I want to install ota update on my phone. It's bootloader is officially unlocked, rooted amd xposed is also installed. I'm right now on cofface twrp.
Unless you made a backup of unmodified stock boot and system before rooting etc.
The ota will probably fail.
If you have made a backup of them? Then restore the backup and apply the OTA.
Make backups again if the OTA gets applied. Then root and install xposed again.
If you can follow this thread you see the steps involved in applying an ota.
corkiejp said:
Unless you made a backup of unmodified stock boot and system before rooting etc.
The ota will probably fail.
If you have made a backup of them? Then restore the backup and apply the OTA.
Make backups again if the OTA gets applied. Then root and install xposed again.
If you can follow this thread you see the steps involved in applying an ota.
Click to expand...
Click to collapse
I didnt made the back up of those files but today i unrooted, uninstalled xposed, flashed stock recovery but still ota fails.
i even followed the guide and replaced emmc file and modified updater script but twrp was not able to flash the update and can i install recovery rom using twrp even when im rooted and xposed is install adn do i lose data by flashing it?
Once you have modified your system and boot images. you can not unmodified them by removing the changes. Because the images will still be modified!
I don't know if you can flash the latest rom, without losing your data. What rom are you using?
I flashed xiaomi.eu rom, to avoid having to worry about getting and applying OTA updates. As detail in my previous post.
With xiaomi.eu rom, I can flash the updated roms without losing data.
You could try, making a TWRP backup of your data partition.
Flash the latest version of your rom.
Then if data gets wiped, restore the TWRP backup of data partition.
My phone was officially unlocked, used alka twrp. I can still have ota update of cause failed on incremental update, alter rebooted the phone, I received the second ota update full rom and flashed it , flashed superSU and exposed v86 with success.
Sent from my Redmi Note 3 using Tapatalk
farhantahir said:
As the tiltle says I want to install ota update on my phone. It's bootloader is officially unlocked, rooted amd xposed is also installed. I'm right now on cofface twrp.
Click to expand...
Click to collapse
To flash recovery MIUI rom through twrp, delete the emmc_appsboot.mbn file from the firmware_update folder inside the rom zip file, and then flash rom through ALKA TWRP .
To update rom, download OTA through updater app or MIUI site and then open the OTA zip file and delete emmc_appsboot.mbn file inside the firmware-update folder and then flash through ALKA TWRP .
manishbhakuni14 said:
To flash recovery MIUI rom through twrp, delete the emmc_appsboot.mbn file from the firmware_update folder inside the rom zip file, and then flash rom through ALKA TWRP .
To update rom, download OTA through updater app or MIUI site and then open the OTA zip file and delete emmc_appsboot.mbn file inside the firmware-update folder and then flash through ALKA TWRP .
Click to expand...
Click to collapse
Officially unlocked the bootloader, I always successfully ota full rom flashed by alka twrp. No needed to do additional steps.
Sent from my Redmi Note 3 using Tapatalk
timberwolf60 said:
Officially unlocked the bootloader, I always successfully ota full rom flashed by alka twrp. No needed to do additional steps.
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
is this working for ota for you plz tell
android_smater said:
is this working for ota for you plz tell
Click to expand...
Click to collapse
On my rmn3 pro, failed on first incremental ota update. Upon reboot, I will received another ota, this time will be full rom. Flashed with alka twrp with success.
Sent from my Redmi Note 2 using Tapatalk
OTA not worked on twrp..only work full rom on twrp recovery so u flash full rom zip file ..u hv stock recovery then works ota updates
Zentalk forums claims that stock firmware WW_15.0405.1803.99 is released but I can't find it on the Asus support page. Anyone knows where it is?
I spent awhile looking for it as well couldn't find it
Is this update only for OTA devices and those with unlocked boot-loaders excluded from this update?
It's up now
Asus web site is always later then phone OTA, today (11-4-2018) the web site can download the upgrade file.
Now is there an easy way to install this with TWRP?
I use the same TWRP version as the last few updates
How do you do that? Anytime I try and install the stock ROM zip with TWRP, I get some error 7 message and refuses to install.
U can't flash the stock ASUS Rom with twrp. U need to reflash the stock boot.img and the stock recovery. Then update. Then reflash twrp.
How do you get the stock recovery? The one online is outdated and won't update to the latest rom.
someaguy said:
How do you get the stock recovery? The one online is outdated and won't update to the latest rom.
Click to expand...
Click to collapse
Flash these in fastboot mode. Open the archive and copy them to your fastboot directory.
https://drive.google.com/file/d/1NK66Zlaish2sqEsb6ci2ABb9XPN-HDIU/view?usp=sharing
EEa(EU) rom 10.3.3.0 update
Received it too yesterday and all is ok.
Does anyone know how to flash that update using TWRP? I have rooted my Stock ROM with TWRP, and the Update is downloaded OTA and then reboots to recovery, but TWRP obviously is unable to install it: First it doesn't ask for the password to decrypt the data partition and shows the crypted content of the partition, making it impossible to see or select the downloaded update. A reboot into recovery decrypts the data partition and shows the downloaded Update (as a ZIP) in the folder /downloaded_rom. I tried to install that ZIP from TWRP manually, but to no avail - all you get is an error message.
Edit: Forget the question. Seems the phone healed itself. The first OTA download was an update 10.3.1 to 10.3.3 with a size of around 500 MB, and that couldn't be installed. When the System Updater saw this didn't succeed, it downloaded the complete 10.3.3 Package (2,2 GB) OTA, and installed that via TWRP with no problems whatsoever. I lost Magisk, which i needed to reinstall, but other than that, everything's fine.
Edit 2: The complete package obviously also overwrites TWRP, which i had to reinstall, too.
cgdams said:
Does anyone know how to flash that update using TWRP? I have rooted my Stock ROM with TWRP, and the Update is downloaded OTA and then reboots to recovery, but TWRP obviously is unable to install it: First it doesn't ask for the password to decrypt the data partition and shows the crypted content of the partition, making it impossible to see or select the downloaded update. A reboot into recovery decrypts the data partition and shows the downloaded Update (as a ZIP) in the folder /downloaded_rom. I tried to install that ZIP from TWRP manually, but to no avail - all you get is an error message.
Edit: Forget the question. Seems the phone healed itself. The first OTA download was an update 10.3.1 to 10.3.3 with a size of around 500 MB, and that couldn't be installed. When the System Updater saw this didn't succeed, it downloaded the complete 10.3.3 Package (2,2 GB) OTA, and installed that via TWRP with no problems whatsoever. I lost Magisk, which i needed to reinstall, but other than that, everything's fine.
Edit 2: The complete package obviously also overwrites TWRP, which i had to reinstall, too.
Click to expand...
Click to collapse
reagarding edit 2: which twrp did you use? I have real problems after the update, as the phone has no wifi now and the recovery is not working anymore
I also want to know if there's a place to get flash able zips through twrp for the latest eu roms.
lvnatic said:
I also want to know if there's a place to get flash able zips through twrp for the latest eu roms.
Click to expand...
Click to collapse
Here you can get all the official ROMs, fastboot and recovery
https://xiaomifirmwareupdater.com/archive/miui/raphael/
magdap said:
reagarding edit 2: which twrp did you use? I have real problems after the update, as the phone has no wifi now and the recovery is not working anymore
Click to expand...
Click to collapse
sorry i'm late with an answer, but i always use the newest version of mauronofrios TWRP (https://forum.xda-developers.com/k20-pro/development/recovery-unofficial-twrp-xiaomi-redmi-t3944363).
Robbo.5000 said:
Here you can get all the official ROMs, fastboot and recovery
https://xiaomifirmwareupdater.com/archive/miui/raphael/
Click to expand...
Click to collapse
Thanks, can I flash the file using twrp and keep the recovery?
lvnatic said:
Thanks, can I flash the file using twrp and keep the recovery?
Click to expand...
Click to collapse
You will need to flash Magisk immediately after the ROM to stop MIUI restoring stock recovery.