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.
I have read basically all the posts here on xda related to this matter. But, being a noob in "rom,kernel, recovery" world, I need to get spoon-fed in some area. Can any kindhearted fellow answer the following questions?
1. I will always use latest official MIUI global beta rom. I need to have the MOST stable custom recovery installed all the time (preferably TWRP official if possible). I want to receive OTA and flash them via custom recovery. Can it be done? if so, what are the MOST hassle-free steps? (want to have root for sum lucky pather action)
2. What are these "encryption", "force disable encryption treble" stand for and what it means for a user like me who wants to run latest Magisk all the time with custom recovery?
3. I can manage to flash OTA and then flash magisk again if needed to maintain root status, is that all I need to do before booting into the new updated and rooted system?
If someone can explain and provide insights, that will be a great help.
1. The most hassle free to do OTA updates is to revert back to stock recovery when the update.zip package is ready to be flashed because
2. Every OTA update in MIUI will encrypt /data partition. (This is Xiaomi's standard data protection). I didn't tried to do OTA updates with Official Twrp but you can try. That is why everyone when trying to flash custom rom, flashing DFE.zip (Disable Force Encryption) will of course disables the system to encrypt data during boot.
3. Magisk has OTA survival script so when there is OTA updates, Magisk will automatically install after OTA update is finished.
hi
i just update my mi a3 from June to October update (first updated to September and then notify me immediately for October update). now every time i turn WiFi or hotspot on it turn back off.
something that maybe cause the problem:
i use magisk tutorial for updating and then i realize it was bad decision and twrp is gone. installed twrp (via fastboot then twrp.zip) and magisk(via twrp) again and then face the problem. i don't check that it was there before reinstalling twrp or not.
how can i fix it?
update: it seems like twrp not working with October ota. i install alogcat and searched error. it lead me to this threat where twrp made this problem with same errors.
i reboot to twrp and now i stock in it. rebooting to system take me back to twrp. decryption isn't working anymore(no prompet for pattern).
i just can reboot to fastboot!!!
i managed to download 10.3.8.0 pfqmixm and extract images from it. flash all of them in slot a and b via fastboot. then flash twrp and it decrypt my data. phone boot to system now but wifi and hotspot problem exist. if i flash stock boot.img phone show a page that it coudn't load system and maybe my data was corrupted. it give me to option: 1. try again (reboot) 2. factory data reset.
any suggestion?
ghasemi.hussein said:
hi
i just update my mi a3 from June to October update (first updated to September and then notify me immediately for October update). now every time i turn WiFi or hotspot on it turn back off.
something that maybe cause the problem:
i use magisk tutorial for updating and then i realize it was bad decision and twrp is gone. installed twrp (via fastboot then twrp.zip) and magisk(via twrp) again and then face the problem. i don't check that it was there before reinstalling twrp or not.
how can i fix it?
update: it seems like twrp not working with October ota. i install alogcat and searched error. it lead me to this threat where twrp made this problem with same errors.
i reboot to twrp and now i stock in it. rebooting to system take me back to twrp. decryption isn't working anymore(no prompet for pattern).
i just can reboot to fastboot!!!
Click to expand...
Click to collapse
But it's working for me
At end i clean install v10.3.8.0. all data lost. it socks really.
again after installin twrp wifi and hotspot breaked.
Hi Guys
I've rooted and installed TWRP On my A20(A205F) successfully.
Yesterday I decided to check for updates and I found that the A20 now has an October Security Update.
[I'd also like to state that I haven't been able to patch my boot.img in Magisk, It failed to download the Magisk v20 Zip all the time, so I got it from somewhere else and tried to get it to work. Eventually it worked and managed to download the zip and patch my boot.img for october update but once I tried it again it keeps failing to download the installer zip.]
So I downloaded the whole firmware and did a full on backup of all my stuff then I proceeded to flash via odin the updated firmware. I've managed to get Root via Magisk working 100% but then I went on to flash TWRP and came out with a bootloop, actually I've tried multiple ways to install TWRP and Magisk without a successful outcome I've now come back to the June Update so I got Magisk and TWRP back.
Some links on the Github page of Magisk isn't working??? Whats up with that? I couldn't download anything from there.
So is there anyway someone could help with getting the update and having TWRP and Magisk working again?
It's a tale as old as time. I have a functioning A3 with TWRP and magisk installed. OTA Jan security update failed. "Installation problem" was all it said. I expected this. I think all my magisk mods are systemless but I did flash a custom kernel in TWRP to get kcal.
Ok I'd gone through this for the December update. I downloaded fastboot ROM and extracted the boot.img. I made sure it was correct. Laurel sprout V10.3.13.0.PFQEUXM. But flashing it with either TWRP or fastboot I got the dreaded error screen on reboot where your options are try again or factory reset. Yes I flashed into the active slot. Even when I chose to factory reset and started fresh, I still got the same error when I tried to update.
I also tried to flash boot+system but also got same corrupted error. I tried using flash_all_except_data_storage but got an antirollback error. I've gone back to a nandroid backup for now but obviously I need to get this sorted out before the Android 10 update.
Any ideas? Thanks
Mi A3 doesn't have anti rollback mechanism as far as I know. If you installed TWRP, you also most probably enabled "allow system modifications" (there is a one time prompt on the first start of TWRP, pretty much everyone just dismisses it without reading). TWRP remembers this setting and for each subsequent boot into TWRP it automatically mounts system as R/W, breaking OTA even if you don't flash anything.
You need to reflash stock fastboot images for boot and system with the same version as you're currently running. If you are getting data corruption error, it usually happens when you flash system image from incorrect region or versions differ too much (you're flashing too old image).
Don't install TWRP (or make sure that you delete its settings first and then do NOT allow system modifications).
As you already performed a factory reset, I'd start from fresh state again - switch to active slot A and reflash whole ROM from fastboot, including data wipe (flash_all.bat if I'm not mistaken, but I don't have it in front of me, so double-check its content that it doesn't lock your bootloader).