UBports Robot Logo UBports Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Device Bootloops After Flashing Images [boot.img , system.img , dtbo.img , vendor_boot.img] [Motorola Moto G52] [Halium 13]

    Scheduled Pinned Locked Moved Porting
    1 Posts 1 Posters 14 Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • systemmaniac2010S Offline
      systemmaniac2010
      last edited by

      Device Boot Loop Issue While Porting to Ubuntu Touch (Halium 13)

      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:

      Boot Loop Sequence

      1. The device shows the Motorola start-up logo for one second.
      2. The device shows the unlocked bootloader warning screen for 6 seconds.
      3. It shows the Motorola logo again for 6 to 10 seconds, but now with a horizontal pixelated line on the screen.
      4. It then shows a blank screen for 5 to 10 seconds.
      5. The cycle repeats, but the line gradually moves down on each reboot.

      Troubleshooting Performed

      At this stage, I entered the fastboot bootloader and tried:

      fastboot boot twrp.img
      

      However, the device immediately started boot looping.

      I then replaced dtbo.img with the one from the latest LineageOS 20 build available for my device.

      After this change, the horizontal line disappeared.

      I was able to successfully boot TWRP using:

      fastboot boot twrp.img
      

      Logging Investigation

      I attempted to read the pstore logs but couldn't find any useful output.

      I suspected the kernel might not have been built with the required logging options enabled.

      To address this, I:

      • Created a separate logging.config file with the right kernel flags.
      • Added it to deviceinfo.
      • Verified that the options were correctly applied to the generated .config file located at:
      workdir/downloads/KERNELOBJ
      
      • Added the appropriate kernel command-line parameters to the vendor cmdline in the deviceinfo file.

      Current Status

      Despite these changes:

      • The device still does not boot properly.
      • USB does not become available.
      • The pstore directory remains empty even after enabling all relevant logging flags and kernel parameters.

      Source Tree

      For debugging and error analysis, the device source tree is available at:

      • https://gitlab.com/systemmaniac2010/motorola-rhode

      Please help me out with this.

      1 Reply Last reply Reply Quote 0

      Hello! It looks like you're interested in this conversation, but you don't have an account yet.

      Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

      With your input, this post could be even better 💗

      Register Login
      • First post
        Last post