Navigation

    UBports Robot Logo

    UBports Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    Need help for porting to xiaomi 4 cancro

    Porting
    5
    27
    4935
    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.
    • T
      Tonoxis last edited by Tonoxis

      I see you have syspart on the kernel's cmdline, but not datapart (if that's still used in ubports-boot), if this is still used then that may be the reason why it's not creating your data directories. However system-data should be created by the rootfs (it contains overrides for certain items in directories on the system image like /etc/init/*.override, /var, etc.)

      MultiROM doesn't create these folders specifically, that's done by system-image-upgrader during installation of the Ubuntu Touch rootfs. So ensure that you have a valid Ubuntu Touch rootfs on your device, system.img should be in /data and I think ubuntu.img as well (not sure, I mainly use MultiROM with my Nexus 7). Other than that, It looks like your ramdisk is booting and running properly, at least to me. You may wish to remove the breakpoint from the kernel cmdline and get the last_kmsg from recovery instead to get a more full, detailed log including what happens after the ramdisk's execution (which isn't shown in your log as the ramdisk pauses it's init execution for the breakpoint).

      I would suggest letting the system sit for about 1 minute before rebooting over to recovery to do this, do note that to see the Ubuntu logs, you MUST start into recovery right after rebooting the system, it MUST NOT attempt to start anything but recovery or you'll find yourself with a different log file (for instance, the recovery image will rewrite the last_kmsg with it's own if it was the last thing to start up before a reboot). So if you can do an adb reboot recovery, or a reboot recovery from your ramdisk to boot into recovery, that will help a ton!

      To get the last_kmsg from recovery:

      • Ensure you boot straight into recovery after rebooting the system from it's boot animation.
      1. Once the device is in recovery and plugged into the machine, simply type adb pull /proc/last_kmsg.

      There you go. This should help since any of us attempting to assist can see the messages from past the ramdisk (your current log only shows the end of the ramdisk startup, but not Ubuntu's startup which is what we want.)

      Though those Kernel oops in the log (you can find these with the --- cut here --- style lines) could have something to do with things, but it looks like the only issues are with a crypto driver for the platform not being able to create a sysfs entry (not sure if qcrypto.0 is essential to your platform or not), though I don't have this device myself, so I can't give you an answer there.

      EDIT: I also noticed this interesting line in the logs, I'm not sure what it is though [system] Activated service 'com.canonical.SystemImage' failed: Launcher could not run (out of memory)

      This may be why your system isn't starting.

      kuailexs 2 Replies Last reply Reply Quote 0
      • kuailexs
        kuailexs @Tonoxis last edited by

        @Tonoxis
        No breakpoint, no way to get any log. Can not restart.black screen. More than five drive letters on the computer. Can only be forced to shut down. Can not get last_kmsg
        0_1512445460349_ff1b97df-2335-454e-98df-ce5294708b7b-图片.png

        1 Reply Last reply Reply Quote 1
        • kuailexs
          kuailexs @doniks last edited by kuailexs

          @doniks Good news. Now it can boot up. thank you for your help

          1 Reply Last reply Reply Quote 0
          • kuailexs
            kuailexs @Tonoxis last edited by

            @Tonoxis Good news. Now it can boot up. thank you for your help

            1 Reply Last reply Reply Quote 0
            • kuailexs
              kuailexs last edited by

              0_1512518646384_1ca35734-46a4-4576-98be-9c10014f69be-图片.png /media/feifei/linux/68606daaac13f3f4.jpg

              Flohack 1 Reply Last reply Reply Quote 1
              • T
                Tonoxis last edited by

                Great news! What did you change to have it boot up (for future reference)? Was it the datapart kernel cmdline variable? As for the 5 volumes appearing in Nautilus, you may have entered QCOM_DL. If you're entering QCOM_DL while attempting to get into recovery, that means your recovery image is bad and needs re-flashed.

                kuailexs 1 Reply Last reply Reply Quote 0
                • kuailexs
                  kuailexs @Tonoxis last edited by

                  @Tonoxis The reason is that there is no 'ro.product.device=cancro' in build.prop, not loading 70-cancro.rules

                  T 1 Reply Last reply Reply Quote 0
                  • T
                    Tonoxis @kuailexs last edited by

                    @kuailexs Ah wonderful! Glad it was something minor instead of something huge!

                    1 Reply Last reply Reply Quote 0
                    • Flohack
                      Flohack @kuailexs last edited by

                      @kuailexs Excellent Xie-Xie!

                      Can you tell us what works:

                      Boot - OK
                      Bluetooth
                      Camera
                      Cellular Radio
                      GPS
                      Graphics
                      Resume
                      Rotation
                      Sound
                      Touch
                      Wifi

                      These are the main features we need to call it a good port. Good Luck!

                      BR

                      My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                      kuailexs 1 Reply Last reply Reply Quote 0
                      • kuailexs
                        kuailexs @Flohack last edited by

                        @Flohack Most do not work

                        Boot - OK
                        Bluetooth
                        Camera
                        Cellular Radio
                        GPS
                        Graphics - OK
                        Resume
                        Rotation
                        Sound - OK
                        Touch - OK
                        Wifi

                        1 Reply Last reply Reply Quote 1
                        • Flohack
                          Flohack last edited by

                          Yeah this is expected but its a good progress already πŸ˜‰

                          BR Florian

                          My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                          kuailexs 1 Reply Last reply Reply Quote 0
                          • kuailexs
                            kuailexs @Flohack last edited by

                            @Flohack Please help me to see the log
                            https://github.com/kuailexs/porting-log

                            1 Reply Last reply Reply Quote 0
                            • Flohack
                              Flohack last edited by

                              Hello,

                              I am sorry I cannot help you much. You probably should join the Halium telegram group and talk with the guys there, they are the experts πŸ˜‰

                              BR

                              My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                              1 Reply Last reply Reply Quote 0
                              • Y
                                Yxles last edited by

                                holy crap sorry for reviving this but are you the same guy here
                                https://forum.xda-developers.com/t/rom-alpha-ubports-ubuntu-touch-16-04-by-kuailexs-v0-1-4-cancro.3973615/

                                Flohack kuailexs 2 Replies Last reply Reply Quote 0
                                • Flohack
                                  Flohack @Yxles last edited by

                                  @yxles No πŸ˜‰

                                  My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                                  1 Reply Last reply Reply Quote 0
                                  • kuailexs
                                    kuailexs @Yxles last edited by

                                    @yxles Yes.

                                    1 Reply Last reply Reply Quote 0
                                    • First post
                                      Last post