Can't install Mar update, gets "Installation Problem". Tried using the Mi A1 Tool to flash rom and lock bootloader (it was locked anyway), but to no avail. Have Gcam installed. Is Gcam blocking this update? If so, how can I circumvent this issue without losing Gcam? Thanks in advance.
I directly flashed the last OTA with mi flash tool without wiping data.
Me too , there is anyone who can solve this problem ?
Related
Dear, a system update has appeared today. However, after downloading, it fails. I think it's because of root. Has anyone experienced something like this or is there any solution to install this update (75MB)
Only option is to use mi flash tool for clean installation and take ota update.I tried all possible options to take ota ;but nothing worked for me.Mi flash tool also not working for me.I used 29 fastboot commands to restore my phone.
Hello, did anyone find an option to make an OTA System Update with unlocked Bootloader, TWRP installed, Magisk root installed and Android One 9 running?
Systemupdate always abort after download
My bootloader is locked and I applied feb update (after getting stuck in bootloop and flashing the flash_all_except_storage.bat), now how do I root (possibly systemlessly) my mi a1 without losing any data?
https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
Patched feb boot file, I used this and no problem.
https://forum.xda-developers.com/showpost.php?p=75749481&postcount=765
The way he represents his work is really not search friendly. Thanks. Solved
Hello Guys,
i have april version of the Os + Magisk...
of course flashing the may ota doesn't work
i have tried uninstalling masgisk with magisk uninstall+twrp but received an error 1...
is there any method i can use to flash that OTA ? does it exists in TWRP version that i could use or something ?
Do you locked bootloader? With unlocked bootloader you cant update via OTA
Firmware Finder shows there's a new update available for my BTV-W09. It's B355 dated 06/05/18. It's a small OTA, only 190mb. Has anybody installed it? Does anybody know what's in it?
Firmware Finder provides the changelog. It has the June security patches.
No netflix hd update? ****!
How install? I don't remember. [emoji28]. Thanks in advance.
Enviat des del meu ONEPLUS A6003 usant Tapatalk
Anyone have any luck applying this update with TWRP recovery? Looks like it is going to require a flash back to stock to apply?
I was only able to install it with stock. Even then, it had to be the full install, not the OTA update. That install locks the bootloader and unroots; so I then had to re-unlock, which of course wipes the entire device, and then restore from a Google and Titanium backup. Not sure updating is worth the pain. really.
My rooted tab is now threatening to install this update when I reboot. Does anybody remember how to stop a firmware update when it wants to update on reboot?
I don't think there's much to worry about as if you're rooted with TWRP, it'll just reboot into TWRP and wait for you to manually apply it, if you can find it on the file system.
I'm currently trying to apply B356 which was recently released. This minor update contains the July 2018 Google security patches. The last time I did this from B351, this is what I did:
Via TWRP, Installed the 2 full OTA zip files for B352 downloaded with firmwarefinder. This replaced TWRP with the stock recovery but did not wipe my data.
Rebooted, and applied B353 via the normal OTA through settings. This installed the B353 full package (2.52GB).
Reinstalled TWRP with fastboot (twrp_BTV-W09_5_greatslon.img)
Booted to TWRP & installed Magisk
Re-enabled the 5GHz wifi radio
However, this doesn't seem to be working with B356 thus far. Installing the Firmwarefinder zip files failed (at least update.zip did, I didn't try the other two) so I installed the FF B352 images mentioned above. However, applying the stock OTA through settings wants to install 3 patches (B353, June 18, July 18) of size 786MB. They downloaded successfully but then it fails to apply during the reboot.
Anyone else have any luck? What did you wind up doing?
Thanks!
Every time I've applied an update, I ended up locking the bootloader and then having the phone wiped when I unlock the bootloader. I'd love to find a way to update without locking the bootloader. If you find a way to that with this update, please let post how you did it!
So I'm about 1 month trying to update my Mi A1 with this security patch, I can download the update but when I'm tapping to install I get this error: " Installation will resume automatically when device is idle"
I tried to hit "resume" and I got a "installation problem" error.
I tried to reboot after the "idle" message, nothing happens.
I searched a lot on Google, Xda,Reedit and I think no one in the world reported this problem.
Anyone can help me?
Anyone know a solution to this problem ?
Sent from my Xiaomi Mi A1 using XDA Labs
Anyone to help me?
Sent from my Xiaomi Mi A1 using XDA Labs
???
Sent from my Xiaomi Mi A1 using XDA Labs
Looks like you're alone with this problem... or maybe there's an obvious solution if you do a basic search and so people are ignoring your request (didn't check myself)...
Is Your phone 100% untouched and stock (no root, magisk, ...)?
If so You could try to reset Your phone and do all updates before installing anything until updates are finished.
I am also got this problem , after that I have flashed stock recovery and system images and booted with magisk patched.img, then updated with ota and re-rooted with magisk manager ota method. (I have unlocked bootloader with magisk rooted)
BalaN83 said:
I am also got this problem , after that I have flashed stock recovery and system images and booted with magisk patched.img, then updated with ota and re-rooted with magisk manager ota method. (I have unlocked bootloader with magisk rooted)
Click to expand...
Click to collapse
Let me try that, thank you!
Sent from my Xiaomi Mi A1 using XDA Labs
I had the same issue. For me it was because I flashed the stock ROM via TWRP and didn't use the Fastboot Recovery. After I flashed the latest Fastboot ROM, it worked just fine!