Android Enterprise FOTA Update using script
- 23 November 2020
- MobiControl - Android Scripting
3 Answers- 0 Upvote
- 2 Followers
3 Answers
Hi Yoan,
Thank you for posting on SOTI Central.
That script essentially does the same thing as the "System Update Policy" Profile configuration which is available on MobiControl v15: System Update Policy (soti.net)
A couple of suggestions which you can try:
- Slightly different script:
- writeprivateprofstring SystemUpdatePolicy SystemUpdatePolicy 1
apply SystemUpdatePolicy
- writeprivateprofstring SystemUpdatePolicy SystemUpdatePolicy 1
- If you have the .ZIP of the firmware, send it to the device via a File Sync Rule and use the "install_system_update" script to install it: Script Commands for Android Enterprise: Managed Devices (soti.net). You may need to request the .ZIP from the OEM.
Kind regards,
Technical Support | SOTI Inc. | 1.905.624.9828 | support@soti.net | www.soti.net |
Hello,
Thank you for your answer.
The following script does not work :
- writeprivateprofstring SystemUpdatePolicy SystemUpdatePolicy 1
apply SystemUpdatePolicy
Regarding the second point, I am currently waiting for the zip file from the OEM.
But it appears that the "install_system_update" command cannot be used on encrypted devices (AE DO).
Do you have any idea of the corresponding script using the "sendintent" command instead?
The update is directly triggered by the system and not by a third application.
I don't know how to compose the "sendintent" command (type of intent, the intent URL, etc.)
Thank you.
Best regards,
Hi Yoan,
Here are two examples for different manufacturers to have this working, one for Motorola and the other for iSafe Mobile:
- sendintent -b "intent:#Intent;action=com.motorolasolutions.intent.action.UPDATE_PACKAGE;S.file=/sdcard/update.zip;end"
- sendintent -s "intent://#Intent;action=com.isafemobile.auxota.INSTALL_OTA;S.file=/sdcard/update.zip;end"
More information on the script itself can be found here: The sendintent Command (soti.net)
As you can see above you will require the installer activity bundle ID for Coppernic. The best way to get this is to ask Coppernic for the bundle ID required to install the OS update.
Alternatively, you can try enabling ADB on a test device, run ADB logging script, download and install a test APK, and finding the bundle ID used to install the APK.
Failing this, I would recommend opening a case with SOTI Support (support@soti.net) so we can carry out further investigation how to get this working for your devices.
Kind regards,
Technical Support | SOTI Inc. | 1.905.624.9828 | support@soti.net | www.soti.net |