| || |
Re: Stopping OTA Update via file modification?
Just wanted to provide an update:
I've only used mfastboot/fastboot a couple of times and wanted a step by step guide to follow, so I found this one and followed it to the letter:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
Of course, I still found it weird that the Moto G was able to be restored just fine to 4.3 but would no longer work for updates, while trying 4.4.2 would not boot at all.
Turns out, my guide only included instructions to flash system.img_sparsechunk 1-3, and I didn't realize immediately that the stock 4.4.2 firmware has an extra system.img_sparsechunk #4, so I was only flashing about 90% of the system.
Now everything is fixed, and I feel more confident over using mfastboot in the future.
With that said, I can assure everyone that a rooted phone and unlocked bootloader will not prevent being prompted for OTA updates to download and install.
Of course, I made the inadvertent mistake of giving it permission to install.
I don't want to get in the same position with my Moto X, especially if I don't have access to fastboot and stock firmware when it happens. If anyone knows how to permanently freeze OTA updates on the Moto X, I welcome your help.
I like updates, but I just don't want them to happen automatically when I am unable to fix things if bricks the phone or causes a bootloop.
If I can prevent the OTA from downloading automatically and prompting me to update, there is much less chance to accidentally install it.
I am really looking forward to playing with the Moto X this weekend.