<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Device Bootloops After Flashing Images [boot.img , system.img , dtbo.img , vendor_boot.img] [Motorola Moto G52] [Halium 13]]]></title><description><![CDATA[<h2>Device Boot Loop Issue While Porting to Ubuntu Touch (Halium 13)</h2>
<p dir="auto">I am trying to port my device to Ubuntu Touch, using Halium 13. I have flashed the images to the right partitions, but I encountered a boot loop with the following behavior:</p>
<h3>Boot Loop Sequence</h3>
<ol>
<li>The device shows the Motorola start-up logo for one second.</li>
<li>The device shows the unlocked bootloader warning screen for 6 seconds.</li>
<li>It shows the Motorola logo again for 6 to 10 seconds, but now with a horizontal pixelated line on the screen.</li>
<li>It then shows a blank screen for 5 to 10 seconds.</li>
<li>The cycle repeats, but the line gradually moves down on each reboot.</li>
</ol>
<h3>Troubleshooting Performed</h3>
<p dir="auto">At this stage, I entered the fastboot bootloader and tried:</p>
<pre><code class="language-bash">fastboot boot twrp.img
</code></pre>
<p dir="auto">However, the device immediately started boot looping.</p>
<p dir="auto">I then replaced <code>dtbo.img</code> with the one from the latest LineageOS 20 build available for my device.</p>
<p dir="auto">After this change, the horizontal line disappeared.</p>
<p dir="auto">I was able to successfully boot TWRP using:</p>
<pre><code class="language-bash">fastboot boot twrp.img
</code></pre>
<h3>Logging Investigation</h3>
<p dir="auto">I attempted to read the pstore logs but couldn't find any useful output.</p>
<p dir="auto">I suspected the kernel might not have been built with the required logging options enabled.</p>
<p dir="auto">To address this, I:</p>
<ul>
<li>Created a separate <code>logging.config</code> file with the right kernel flags.</li>
<li>Added it to <code>deviceinfo</code>.</li>
<li>Verified that the options were correctly applied to the generated <code>.config</code> file located at:</li>
</ul>
<pre><code class="language-text">workdir/downloads/KERNELOBJ
</code></pre>
<ul>
<li>Added the appropriate kernel command-line parameters to the vendor cmdline in the <code>deviceinfo</code> file.</li>
</ul>
<h3>Current Status</h3>
<p dir="auto">Despite these changes:</p>
<ul>
<li>The device still does not boot properly.</li>
<li>USB does not become available.</li>
<li>The <code>pstore</code> directory remains empty even after enabling all relevant logging flags and kernel parameters.</li>
</ul>
<h3>Source Tree</h3>
<p dir="auto">For debugging and error analysis, the device source tree is available at:</p>
<ul>
<li><a href="https://gitlab.com/systemmaniac2010/motorola-rhode" target="_blank" rel="noopener noreferrer nofollow ugc">https://gitlab.com/systemmaniac2010/motorola-rhode</a></li>
</ul>
<p dir="auto">Please help me out with this.</p>
]]></description><link>https://forums.ubports.com/topic/12328/device-bootloops-after-flashing-images-boot.img-system.img-dtbo.img-vendor_boot.img-motorola-moto-g52-halium-13</link><generator>RSS for Node</generator><lastBuildDate>Tue, 02 Jun 2026 15:44:07 GMT</lastBuildDate><atom:link href="https://forums.ubports.com/topic/12328.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 02 Jun 2026 13:31:29 GMT</pubDate><ttl>60</ttl></channel></rss>