Android boot.hardware is cmdline that is used to detect init.{hardware}.rc file which in my case is init.Dior.rc not init.qcom.rc. 2. First udev rules are read from rules.d dir which is inside ramdisk itself. Then afterwards when init mounts data partition then it read rules files inside system partition and overrides the earlier loaded ones. 3. My processor is definitely msm-8926 since in dts directory I have h3lte device tree which is only for 8926 and not 8928. If my device was 8928 and not 8926 the device tree wudnt have loaded in first place.

i dnt think that matters anyway. if /data is nt mounted there wont be no logs in it, right?

yeah i did. The file pushes fine. I still dont know y aint it able to read device name. God this is so frustrating.

Hello. After updating my sources again and updating my device repo, now i am able to get last_kmsg and dmesg logs. Unfortunately the device doesnt boot yet. But it doesnt die on boot, it keeps restarting. From what i read in last_kmsg (attached below), i think the issue is in 70-$device.rules file. One of errors in the log is that, udev is unable to get device name, which may in turn cause device.rules udev file fail to load. Please help.

TIA.

last_kmsg: http://pastebin.com/Hd8YD82a

@ChrisLuck Dont worry about lsusb. Even i am not getting that right now. Give me your github sources link. Let me look at that. I am getting recovery logs now. Thankfully. But unfortunately there's not much support out there so progress is very slow.

can u send me link to last_kmsg? I am getting them now. When your device bootloops reboot back to bootloader directly and then boot (not flash) recovery.img from ubuntu build. Then get the last_kmsg and dmesg with following command:

adb shell cat /proc/last_kmsg > last_kmsg

And then pastebin it and send me link. I'll see if i can help.

No you You have to use your phone's current udev rules file to port udev rules to Ubuntu readble format. More specifically all /dev rules in your Android udev files need to be copied to Ubuntu udev. You can check Mako's udev to get the ideas how to copy Android udev rules to Ubuntu readable one.

Dont use ubuntu's recovery. It sucks way too much. Use TWRP. Ubuntu's recovery is very unstable. Use it only to check if your kernel build is fine. If your data is empty then ubuntu's system.img is not getting created. Also you need 70-device.rules file where you specify all the udev rules for ubuntu's init to mount dev folder properly. And also adbd.conf to configure adbd on preboot so you get logcats. Check here how they have done.

https://github.com/ubuntu-touchCAF/project_rootstock/tree/ubuntu-touch

Hahaha.....seems like you are on same error as mine. Even i have recovery working properly but when booting normally it gets stuck at vendor logo. Check which initrd version are u using and then see if ubuntu rootfs version is same as initrd version. I think the issue is somewhere in initrd as stressed by ubuntu porting guide. Also get last_kmsg. That will help alot us in figuring out the problem.

Yes setting selinux to permissive will disable selinux check on boot. But first make sure your kernel config is right. Try to boot recovery first. SELinux is least of your worries right now. Android's boot.img and ubuntu's boot.img are earths apart from each other. Make sure your dtb's are in place.

Instead of deleting all *.se policy files, just set selinux=permissive in kernel cmdline. And thats not it. You will have to port AppArmor also if your kernel is not backported right now. For that set apparmor=0 too in cmdline. Goodluck!

Ok sorry. I read how to go into recovery without damaging last_kmsg. So when i am in bootloop and i press recovery mode key combination the screen goes off and on again. Should i keep pressing the combination until i get to recovery or leave the buttons as soon as screen goes black?

I can give u the recovery last_kmsg but that wont help because recovery works fine. I already added console=tty0 and in kernel config CONFIG_VT_CONSOLE and HW_CONSOLE. Nothing. I dont know how to extract when booting normally as its not detected in lsusb. And when i boot recovery everything gets overwritten. I asked alexforsale also. The thing is kernel is made up of two things zImage and ramdisk. When booting in recovery it (kernel) loads fine and android ramdisk loads properly so i get to recovery. This indicates my kernel is fine right? Because in recovery the device is loaded properly (H3 LTE). Now when i boot normally all is see is boot loop. Does this indicate something wrong with ubuntu ramdisk? Now if there was some error in my kernel then even recovery shudnt have booted right? if i am not wrong

Hello. I am trying to port ubuntu-touch to redmi note 4G. So far i have only been able to get recovery running fine (does it mean kernel is building fine?). But when i boot in normal mode, the device is stuck at bootloader. It doesnt even get listed in lsusb command. Thats a big setback. Any help would be greatly appreciated. I am using configs from original_defconfig with changes from port script.

TIA.