<?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>i.MX ProcessorsのトピックRe: Can't boot to Android Pie System after Kernel loading?</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Can-t-boot-to-Android-Pie-System-after-Kernel-loading/m-p/1163196#M162947</link>
    <description>&lt;P&gt;How did you solve this issue . I am facing similar problem&lt;/P&gt;</description>
    <pubDate>Tue, 06 Oct 2020 03:36:48 GMT</pubDate>
    <dc:creator>Ketki</dc:creator>
    <dc:date>2020-10-06T03:36:48Z</dc:date>
    <item>
      <title>Can't boot to Android Pie System after Kernel loading?</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Can-t-boot-to-Android-Pie-System-after-Kernel-loading/m-p/1084954#M159111</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey Guys,&lt;/P&gt;&lt;P&gt;I am porting android 9 for our custom board based on imx6q sabresd board. I've config. the device tree and ubooot and build the android images. After flashing the images to sd-card and&amp;nbsp;powering the board, the Kernel is loading (for both normal boot and recovery) but after it starts init process it isn't&amp;nbsp;loading the android system or recovery system. It doesn't even mount the sd card partitions for boot according to bootlog.&lt;/P&gt;&lt;P&gt;I've verified the fstab.freescale file in the /vendor partition which contains filesystem to be mounted for every partition.&lt;/P&gt;&lt;P&gt;The following is the section of boot log&amp;nbsp;for normal boot and recovery boot where I think the problem is and I've bolded the problems, but I don't know why is it happening and how to solve?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;=================&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;Normal Boot&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;==================&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Freeing unused kernel memory: 1024K&lt;BR /&gt;init: init first stage started!&lt;BR /&gt;init: Using Android DT directory /proc/device-tree/firmware/android/&lt;BR /&gt;&lt;STRONG&gt;init: [libfs_mgr]fs_mgr_read_fstab_default(): failed to find device default fstab&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;init: bool android::init::FirstStageMount::InitRequiredDevices(): partition(s) not found in /sys, waiting for their uevent(s): boot, system, vbmeta, vendor&lt;/STRONG&gt;&lt;BR /&gt;mmc1: Timeout waiting for hardware cmd interrupt.&lt;BR /&gt;mmc1: sdhci: ============ SDHCI REGISTER DUMP ===========&lt;BR /&gt;mmc1: sdhci: Sys addr: 0x00000000 | Version: 0x00000002&lt;BR /&gt;mmc1: sdhci: Blk size: 0x00000000 | Blk cnt: 0x00000001&lt;BR /&gt;mmc1: sdhci: Argument: 0x00000c00 | Trn mode: 0x00000000&lt;BR /&gt;mmc1: sdhci: Present: 0x01f88009 | Host ctl: 0x00000001&lt;BR /&gt;mmc1: sdhci: Power: 0x00000000 | Blk gap: 0x00000080&lt;BR /&gt;mmc1: sdhci: Wake-up: 0x00000008 | Clock: 0x000010ff&lt;BR /&gt;mmc1: sdhci: Timeout: 0x0000008e | Int stat: 0x00000000&lt;BR /&gt;mmc1: sdhci: Int enab: 0x007f1003 | Sig enab: 0x007f1003&lt;BR /&gt;mmc1: sdhci: AC12 err: 0x00000000 | Slot int: 0x00000003&lt;BR /&gt;mmc1: sdhci: Caps: 0x07eb0000 | Caps_1: 0x0000a000&lt;BR /&gt;mmc1: sdhci: Cmd: 0x0000341a | Max curr: 0x00ffffff&lt;BR /&gt;mmc1: sdhci: Resp[0]: 0x00000000 | Resp[1]: 0x00000000&lt;BR /&gt;mmc1: sdhci: Resp[2]: 0x00000000 | Resp[3]: 0x00000000&lt;BR /&gt;mmc1: sdhci: Host ctl2: 0x00000000&lt;BR /&gt;mmc1: sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x00000000&lt;BR /&gt;mmc1: sdhci: ============================================&lt;BR /&gt;init: Wait for partitions returned after 10010ms&lt;BR /&gt;&lt;STRONG&gt;init: bool android::init::FirstStageMount::InitRequiredDevices(): partition(s) not found after polling timeout: boot, system, vbmeta, vendor&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;init: Failed to mount required partitions early ...&lt;/STRONG&gt;&lt;BR /&gt;init: Reboot start, reason: reboot, rebootTarget: bootloader&lt;BR /&gt;init: Reboot ending, jumping to kernel&lt;BR /&gt;imx-sdma 20ec000.sdma: external firmware not found, using ROM firmware&lt;BR /&gt;ci_hdrc ci_hdrc.1: remove, state 4&lt;BR /&gt;usb usb2: USB disconnect, device number 1&lt;BR /&gt;ci_hdrc ci_hdrc.1: USB bus 2 deregistered&lt;BR /&gt;ci_hdrc ci_hdrc.0: remove, state 4&lt;BR /&gt;usb usb1: USB disconnect, device number 1&lt;BR /&gt;ci_hdrc ci_hdrc.0: USB bus 1 deregistered&lt;BR /&gt;reboot: Restarting system with command 'bootloader'&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;=================&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;Recovery&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;==================&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Freeing unused kernel memory: 1024K&lt;BR /&gt;init: init first stage started!&lt;BR /&gt;init: First stage mount skipped (recovery mode)&lt;BR /&gt;init: Using Android DT directory /proc/device-tree/firmware/android/&lt;BR /&gt;&lt;STRONG&gt;init: bool android::init::FirstStageMount::InitRequiredDevices(): partition(s) not found in /sys, waiting for their uevent(s): boot, system, vbmeta, vendor&lt;/STRONG&gt;&lt;BR /&gt;mmc1: Timeout waiting for hardware cmd interrupt.&lt;BR /&gt;mmc1: sdhci: ============ SDHCI REGISTER DUMP ===========&lt;BR /&gt;mmc1: sdhci: Sys addr: 0x00000000 | Version: 0x00000002&lt;BR /&gt;mmc1: sdhci: Blk size: 0x00000000 | Blk cnt: 0x00000001&lt;BR /&gt;mmc1: sdhci: Argument: 0x00000c00 | Trn mode: 0x00000000&lt;BR /&gt;mmc1: sdhci: Present: 0x01f88009 | Host ctl: 0x00000001&lt;BR /&gt;mmc1: sdhci: Power: 0x00000000 | Blk gap: 0x00000080&lt;BR /&gt;mmc1: sdhci: Wake-up: 0x00000008 | Clock: 0x000010ff&lt;BR /&gt;mmc1: sdhci: Timeout: 0x0000008e | Int stat: 0x00000000&lt;BR /&gt;mmc1: sdhci: Int enab: 0x007f1003 | Sig enab: 0x007f1003&lt;BR /&gt;mmc1: sdhci: AC12 err: 0x00000000 | Slot int: 0x00000003&lt;BR /&gt;mmc1: sdhci: Caps: 0x07eb0000 | Caps_1: 0x0000a000&lt;BR /&gt;mmc1: sdhci: Cmd: 0x0000341a | Max curr: 0x00ffffff&lt;BR /&gt;mmc1: sdhci: Resp[0]: 0x00000000 | Resp[1]: 0x00000000&lt;BR /&gt;mmc1: sdhci: Resp[2]: 0x00000000 | Resp[3]: 0x00000000&lt;BR /&gt;mmc1: sdhci: Host ctl2: 0x00000000&lt;BR /&gt;mmc1: sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x00000000&lt;BR /&gt;mmc1: sdhci: ============================================&lt;BR /&gt;init: Wait for partitions returned after 10009ms&lt;BR /&gt;&lt;STRONG&gt;init: bool android::init::FirstStageMount::InitRequiredDevices(): partition(s) not found after polling timeout: boot, system, vbmeta, vendor&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;init: Failed to init devices for INIT_AVB_VERSION&lt;/STRONG&gt;&lt;BR /&gt;init: Loading SELinux policy&lt;BR /&gt;SELinux: Class process2 not defined in policy.&lt;BR /&gt;SELinux: Class infiniband_pkey not defined in policy.&lt;BR /&gt;SELinux: Class infiniband_endport not defined in policy.&lt;BR /&gt;SELinux: the above unknown classes and permissions will be denied&lt;BR /&gt;SELinux: policy capability network_peer_controls=1&lt;BR /&gt;SELinux: policy capability open_perms=1&lt;BR /&gt;SELinux: policy capability extended_socket_class=1&lt;BR /&gt;SELinux: policy capability always_check_network=0&lt;BR /&gt;SELinux: policy capability cgroup_seclabel=0&lt;BR /&gt;SELinux: policy capability nnp_nosuid_transition=0&lt;BR /&gt;audit: type=1403 audit(43.980:2): policy loaded auid=4294967295 ses=4294967295&lt;BR /&gt;selinux: SELinux: Loaded policy from /sepolicy&lt;/P&gt;&lt;P&gt;selinux: SELinux: Loaded file_contexts&lt;/P&gt;&lt;P&gt;init: init second stage started!&lt;BR /&gt;init: Using Android DT directory /proc/device-tree/firmware/android/&lt;BR /&gt;selinux: SELinux: Loaded file_contexts&lt;/P&gt;&lt;P&gt;init: Running restorecon...&lt;BR /&gt;selinux: SELinux: Could not stat /dev/block: No such file or directory.&lt;/P&gt;&lt;P&gt;init: waitid failed: No child processes&lt;BR /&gt;init: Couldn't load property file '/system/etc/prop.default': open() failed: No such file or directory: No such file or directory&lt;BR /&gt;init: Unable to set property 'ro.product.first_api_level' to '26' in property file '/prop.default': Read-only property was already set&lt;BR /&gt;init: Couldn't load property file '/product/build.prop': open() failed: No such file or directory: No such file or directory&lt;BR /&gt;init: Couldn't load property file '/odm/default.prop': open() failed: No such file or directory: No such file or directory&lt;BR /&gt;audit: type=1400 audit(44.140:3): avc: denied { dac_read_search } for pid=1 comm="init" capability=2 scontext=u:r:init:s0 tcontext=u:r:init:s0 tclass=capability permissive=1&lt;BR /&gt;ueventd: ueventd started!&lt;BR /&gt;audit: type=1400 audit(44.140:4): avc: denied { create } for pid=1 comm="init" name="cgroup.procs" scontext=u:r:init:s0 tcontext=u:object_r:rootfs:s0 tclass=file permissive=1&lt;BR /&gt;selinux: SELinux: Loaded file_contexts&lt;/P&gt;&lt;P&gt;audit: type=1400 audit(44.140:5): avc: denied { write } for pid=1 comm="init" path="/acct/uid_0/pid_145/cgroup.procs" dev="rootfs" ino=12430 scontext=u:r:init:s0 tcontext=u:object_r:rootfs:s0 tclass=file permissive=1&lt;BR /&gt;ueventd: Parsing file /ueventd.rc...&lt;BR /&gt;ueventd: Parsing file /vendor/ueventd.rc...&lt;BR /&gt;ueventd: Unable to read config file '/vendor/ueventd.rc': open() failed: No such file or directory&lt;BR /&gt;ueventd: Parsing file /odm/ueventd.rc...&lt;BR /&gt;ueventd: Unable to read config file '/odm/ueventd.rc': open() failed: No such file or directory&lt;BR /&gt;ueventd: Parsing file /ueventd.freescale.rc...&lt;BR /&gt;ueventd: Unable to read config file '/ueventd.freescale.rc': open() failed: No such file or directory&lt;BR /&gt;ueventd: firmware: loading 'imx/sdma/sdma-imx6q.bin' for '/devices/soc0/soc/2000000.aips-bus/20ec000.sdma/firmware/imx!sdma!sdma-imx6q.bin'&lt;BR /&gt;audit: type=1400 audit(44.420:6): avc: denied { write } for pid=1 comm="init" name="cursor_blink" dev="sysfs" ino=8543 scontext=u:r:init:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=1&lt;BR /&gt;audit: type=1400 audit(44.420:7): avc: denied { open } for pid=1 comm="init" path="/sys/devices/virtual/graphics/fbcon/cursor_blink" dev="sysfs" ino=8543 scontext=u:r:init:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=1&lt;BR /&gt;file system registered&lt;BR /&gt;audit: type=1400 audit(44.480:8): avc: denied { wake_alarm } for pid=151 comm="charger" capability=35 scontext=u:r:charger:s0 tcontext=u:r:charger:s0 tclass=capability2 permissive=1&lt;BR /&gt;healthd: battery l=85 v=3 t=35.0 h=2 st=2 c=400 fc=4000000 cc=32 chg=a&lt;BR /&gt;read descriptors&lt;BR /&gt;read strings&lt;BR /&gt;imx-sdma 20ec000.sdma: external firmware not found, using ROM firmware&lt;BR /&gt;mmc1: Timeout waiting for hardware cmd interrupt.&lt;BR /&gt;mmc1: sdhci: ============ SDHCI REGISTER DUMP ===========&lt;BR /&gt;mmc1: sdhci: Sys addr: 0x00000000 | Version: 0x00000002&lt;BR /&gt;mmc1: sdhci: Blk size: 0x00000000 | Blk cnt: 0x00000001&lt;BR /&gt;mmc1: sdhci: Argument: 0x80000c08 | Trn mode: 0x00000000&lt;BR /&gt;mmc1: sdhci: Present: 0x01f88009 | Host ctl: 0x00000001&lt;BR /&gt;mmc1: sdhci: Power: 0x00000000 | Blk gap: 0x00000080&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've used fsl_sdcard_partition.sh script on&amp;nbsp;Ubuntu 18.04 to flash the images to sd-card.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 10 Apr 2020 10:22:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Can-t-boot-to-Android-Pie-System-after-Kernel-loading/m-p/1084954#M159111</guid>
      <dc:creator>krishnandu_bisw</dc:creator>
      <dc:date>2020-04-10T10:22:43Z</dc:date>
    </item>
    <item>
      <title>Re: Can't boot to Android Pie System after Kernel loading?</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Can-t-boot-to-Android-Pie-System-after-Kernel-loading/m-p/1084955#M159112</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Biswas,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The partition table depends on the size of the storage that you are going to use. If your current storage does not fit with your partition table. You will get errors at the time you are mounting the partitions.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How are you copying and partitioning the eMMC memory? I think you may use UUU.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 10 Apr 2020 15:18:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Can-t-boot-to-Android-Pie-System-after-Kernel-loading/m-p/1084955#M159112</guid>
      <dc:creator>Bio_TICFSL</dc:creator>
      <dc:date>2020-04-10T15:18:51Z</dc:date>
    </item>
    <item>
      <title>Re: Can't boot to Android Pie System after Kernel loading?</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Can-t-boot-to-Android-Pie-System-after-Kernel-loading/m-p/1084956#M159113</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for your fast reply,&lt;/P&gt;&lt;P&gt;But have read my problem description (not just log), because I've mentioned every possible details.&lt;/P&gt;&lt;P&gt;I'm using an SD-card of 8GB(actually 7.38GB) and not emmc and also I'm using fsl_sdcard_partition script for partitioning and flashing.&lt;/P&gt;&lt;P&gt;All the partition are being created properly because I have configured the partition table according to the size of raw images. So the images are flashed properly and not overlapping on other partitions.&lt;/P&gt;&lt;P&gt;When I use UUU with flash script this output appears and remains stuck.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Screenshot from 2020-04-11 14-53-00.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/106013i24B9D99D5872473F/image-size/large?v=v2&amp;amp;px=999" role="button" title="Screenshot from 2020-04-11 14-53-00.png" alt="Screenshot from 2020-04-11 14-53-00.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Is it because the libuuu version is 1.3.134 and uuu version&amp;nbsp;required is 1.2.135?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 11 Apr 2020 04:19:18 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Can-t-boot-to-Android-Pie-System-after-Kernel-loading/m-p/1084956#M159113</guid>
      <dc:creator>krishnandu_bisw</dc:creator>
      <dc:date>2020-04-11T04:19:18Z</dc:date>
    </item>
    <item>
      <title>Re: Can't boot to Android Pie System after Kernel loading?</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Can-t-boot-to-Android-Pie-System-after-Kernel-loading/m-p/1084957#M159114</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I also tried with uuu 1.2.135....&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="uuu-flash.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/106029i5C81B77EAF7CA339/image-size/large?v=v2&amp;amp;px=999" role="button" title="uuu-flash.png" alt="uuu-flash.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 11 Apr 2020 08:50:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Can-t-boot-to-Android-Pie-System-after-Kernel-loading/m-p/1084957#M159114</guid>
      <dc:creator>krishnandu_bisw</dc:creator>
      <dc:date>2020-04-11T08:50:54Z</dc:date>
    </item>
    <item>
      <title>Re: Can't boot to Android Pie System after Kernel loading?</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Can-t-boot-to-Android-Pie-System-after-Kernel-loading/m-p/1084958#M159115</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey guys,&lt;/P&gt;&lt;P&gt;I was able to solve this uuu flashing problem. But still the problem is same,,,.After flashing with uuu tool when I reboot the board, it gives the same debug output.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With Regards.&lt;/P&gt;&lt;P&gt;Krishnandu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Apr 2020 12:21:18 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Can-t-boot-to-Android-Pie-System-after-Kernel-loading/m-p/1084958#M159115</guid>
      <dc:creator>krishnandu_bisw</dc:creator>
      <dc:date>2020-04-15T12:21:18Z</dc:date>
    </item>
    <item>
      <title>Re: Can't boot to Android Pie System after Kernel loading?</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Can-t-boot-to-Android-Pie-System-after-Kernel-loading/m-p/1084959#M159116</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;can anybody help,&amp;nbsp;i am&amp;nbsp;still stuck with this problem.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Problem Update:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;/dev/block directory for block devices (including sd card) isn't being created before init's execution. That is why its not mounting any partition of sd-card.&lt;/P&gt;&lt;P&gt;But I don't know where to add commands to create it and make kernel to load devices into it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Apr 2020 12:50:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Can-t-boot-to-Android-Pie-System-after-Kernel-loading/m-p/1084959#M159116</guid>
      <dc:creator>krishnandu_bisw</dc:creator>
      <dc:date>2020-04-21T12:50:22Z</dc:date>
    </item>
    <item>
      <title>Re: Can't boot to Android Pie System after Kernel loading?</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Can-t-boot-to-Android-Pie-System-after-Kernel-loading/m-p/1163196#M162947</link>
      <description>&lt;P&gt;How did you solve this issue . I am facing similar problem&lt;/P&gt;</description>
      <pubDate>Tue, 06 Oct 2020 03:36:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Can-t-boot-to-Android-Pie-System-after-Kernel-loading/m-p/1163196#M162947</guid>
      <dc:creator>Ketki</dc:creator>
      <dc:date>2020-10-06T03:36:48Z</dc:date>
    </item>
  </channel>
</rss>

