<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: How to update bootloader when using A/B update in Android 9 update_engine in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/How-to-update-bootloader-when-using-A-B-update-in-Android-9/m-p/1027778#M151838</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/girodassoc@neuralrasa.com"&gt;girodassoc@neuralrasa.com&lt;/A&gt;,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As per my understanding u-boot won't be a part of OTA process. As it is the boot-loader which is dealing with changing the boot partitions after the OTA, if we change the boot-loader and it gets corrupted then there won't be any way to recover back. You can also verify the same in the android source for i.MX8M Mini at "&lt;STRONG&gt;./build/make/tools/releasetools/ota_from_target_files.py". &lt;/STRONG&gt;Here, you can see there is an option kept with the name &lt;STRONG&gt;"--full_bootloader"&lt;/STRONG&gt;, however there is nothing implemented for this option.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, your u-boot changes are not seen after an OTA. I would recommend not to do an OTA of boot-loader, as failure in this won't be able to recover back to working boot-loader.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Feel free to let us know if you have any further queries in this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Kunal&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 24 Mar 2020 18:41:11 GMT</pubDate>
    <dc:creator>kunalkotecha1</dc:creator>
    <dc:date>2020-03-24T18:41:11Z</dc:date>
    <item>
      <title>How to update bootloader when using A/B update in Android 9 update_engine</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/How-to-update-bootloader-when-using-A-B-update-in-Android-9/m-p/1027777#M151837</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;How do I update the bootloader for the evk_8mm when using A/B update in the Android 9 Pie update_engine?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I installed the Android P9.0.0_2.3.0 demo image on the evk_8mm, then built an OTA package that included updates to the u-boot and linux kernel device trees, published my payload.bin on my OTA server and then applied it using the command line "update_engine_client".&amp;nbsp; On reboot, my linux kernel modifications were observed, but my u-boot modifications were not.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I apply the same build to the evk_8mm using uuu, my u-boot modifications are observed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What am I missing?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Mar 2020 21:36:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/How-to-update-bootloader-when-using-A-B-update-in-Android-9/m-p/1027777#M151837</guid>
      <dc:creator>girodassoc</dc:creator>
      <dc:date>2020-03-13T21:36:19Z</dc:date>
    </item>
    <item>
      <title>Re: How to update bootloader when using A/B update in Android 9 update_engine</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/How-to-update-bootloader-when-using-A-B-update-in-Android-9/m-p/1027778#M151838</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/girodassoc@neuralrasa.com"&gt;girodassoc@neuralrasa.com&lt;/A&gt;,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As per my understanding u-boot won't be a part of OTA process. As it is the boot-loader which is dealing with changing the boot partitions after the OTA, if we change the boot-loader and it gets corrupted then there won't be any way to recover back. You can also verify the same in the android source for i.MX8M Mini at "&lt;STRONG&gt;./build/make/tools/releasetools/ota_from_target_files.py". &lt;/STRONG&gt;Here, you can see there is an option kept with the name &lt;STRONG&gt;"--full_bootloader"&lt;/STRONG&gt;, however there is nothing implemented for this option.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, your u-boot changes are not seen after an OTA. I would recommend not to do an OTA of boot-loader, as failure in this won't be able to recover back to working boot-loader.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Feel free to let us know if you have any further queries in this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Kunal&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Mar 2020 18:41:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/How-to-update-bootloader-when-using-A-B-update-in-Android-9/m-p/1027778#M151838</guid>
      <dc:creator>kunalkotecha1</dc:creator>
      <dc:date>2020-03-24T18:41:11Z</dc:date>
    </item>
  </channel>
</rss>

