building for Nexus 7 deb

doniks

Ah, no, I guess it should be

add_lunch_combo cm_deb-userdebug
lunch cm_deb-userdebug
make

that is progressing now, let's see where it goes.

doniks

ok that ran through until

#### make completed successfully (01:04:37 (hhss)) ####

and I see

cd out/target/product/deb/
ls *.img
boot.img cache.img ramdisk-android.img ramdisk-recovery.img ramdisk-ubuntu.img recovery.img system.img userdata.img

however when I put my device into bootloader mode and then try

fastboot boot recovery.img

it boots and reboots and ends up in the TWRP recovery which is what is installed currently

fastboot boot boot.img

simply keeps on rebooting forever and ever. same happens when I do either of

fastboot flash boot boot.img
fastboot flash recovery recovery.img

and then reboot into either system or recovery.

so, what now?

flohack

@doniks Maybe you need to unlock smth? some devices protect everything from being overwritten? NOt sure about that

doniks

Mhm, no I don't think that's it. I did that oem unlock thingy a long time ago and had since had multiple android versions, multiple different recoveries, also UT for a lengthy period. So I don't think a lock is keeping me.

flohack

@doniks There is no logical reason why fastboot flash recovery recovery.img should not work, sorry then...

doniks

I tried the following:

fastboot flash recovery twrp.img
fastboot boot recovery.img

observe that it boots the ubuntu recovery and then reboots into twrp recovery

adb shell cat /proc/last_kmsg > last_kmsg

When reading that logfile I spot the following towards the end:

SELinux: Could not open sepolicy: No such file or directory
init: SELinux: Failed to load policy; rebooting into recovery mode

Sounds like I have a problem with SELinux!? But what to do?

flohack

@doniks SELinux is a kernel extension for security and policies. can you check the output of the kernel settings script for Ubuntu: https://github.com/janimo/phablet-porting-scripts/tree/master/kernel => it will tell you what needs to be changed in the kernel config file, and it can also apply those changes. Then a rebuild of the kernel should get you going.

BR

doniks

Ah thanks! I'll check that.

But it makes me wonder ... I have a recovery that has trouble booting. But, stupid question: Is it a "cyanogenmod recovery" or is it an "ubports recovery"? I guess, I'm somewhere in between, right? The "repo init" brought the ubports side and the "local_manifest" brought in the cm side. If it were straight "cm only", then the resulting recovery would probably just boot. But then, I don't want cm, so, I'm venturing into ubp territory and those config options you linked are probably the next step deeper into ubp land.

I'm rambling ... I'm just trying to understand what I'm actually doing, while copy pasting instructions.

I see in the script there is a CONFIGS_OFF : CONFIG_DEFAULT_SECURITY_SELINUX

that does indeed sound like it might resolve the problem. Let's see.

doniks

Alrighty! Welcome to the Ubports Recovery

I applied most of what sounded like "turn off SELinux". I didn't apply all the check-config changes yet, because I was concerned about changing too many things at once and breaking more than fixing. (diff below)

Recovery seems to be working fine now: Shows menu, I can navigate it with volup/voldown/power and with touch gestures, all actions I tried seemed to work. On to image building

git diff

arrrghhh .... forum software! why can I copy/paste a diff as plain text, which of course screws up the layouting of the post because it's misinterpreted as markdown, but I am NOT allowed to copy/paste into a

code block

because "Error

Post content was flagged as spam by Akismet.com"

Whatever, I adjusted the following:
CONFIG_SECURITY_SELINUX_BOOTPARAM=y
CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=0
CONFIG_SECURITY_SELINUX_DISABLE=y
CONFIG_DEFAULT_SECURITY_SELINUX=n

flohack

@doniks You can safely apply all changes of this script - in fact they are all necessary, so dont bother with trying one by one

doniks

@Flohack said in building for Nexus 7 deb:

@doniks You can safely apply all changes of this script - in fact they are all necessary, so dont bother with trying one by one

Ok, let me try. I saw some apparmor stuff and thought .... uh, probably I need to hunt for kernel patches to make this work, let me postpone THAT headache ....

doniks

@doniks said in building for Nexus 7 deb:

@Flohack said in building for Nexus 7 deb:

@doniks You can safely apply all changes of this script - in fact they are all necessary, so dont bother with trying one by one

Ok, let me try.

Yup, that was easy enough. Applied all changes. Rebuilt. Flashed recovery. Rebooted. Works just as well until here!

flohack

@doniks In general if you got a working CM kernel no real kernel patches are needed except apparmor3 => But you can try stealing that as a whole subdir from a kernel that has these patches applied. Should be more like copy/paste.

BR

doniks

one step further. next road block. I've cloned the rootstock-ng thingy, downloaded the vivid....tar.gz, ran the rootstock thingy. It did it's thing, the tablet rebooted but is stuck at the Google logo screen. adb is not working. nothing seems to be happening. Not sure how to proceed, don't have any ideas

doniks

I realize that there is a deb image in the rc channel

ubuntu-device-flash --verbose --server=https://system-image.ubports.com/ touch --device=deb --channel=ubuntu-touch/rc-proposed

that installs and starts just fine. Poking around in that image, it seems to me as if the initrd is basically the same as my self built one, but the kernel config and the android system.img look quite different. Though, I still don't know what exactly to do ...

Andreas Pokorny

@doniks You might want to try the google_msm kernel in ubports. It already contains the apparmor and other backports:
https://github.com/ubports/android_kernel_google_msm/tree/ubp-5.1

but it does not contain a reasonable kernel config for flo.

You could also verify that the user space binaries and firmware files are being picked up get copied into the out/target/product/...../system directory.

If none of that gets you any further - use adb while in recovery and go to /data/system-data and examine the var/log files for clues..

Andreas Pokorny

I meant deb .. not flo

flohack

@Andreas-Pokorny You can edit posts here xD

doniks

@Andreas-Pokorny said in building for Nexus 7 deb:

Thanks for your tips.

You could also verify that the user space binaries and firmware files are being picked up get copied into the out/target/product/...../system directory.

I think I'm good here:

cd vendor/qcom/deb/proprietary
for b in * ; do find ../../../../out/target/product/deb/system/ -name $b ; done
../../../../out/target/product/deb/system/vendor/firmware/a300_pfp.fw
../../../../out/target/product/deb/system/vendor/firmware/a300_pm4.fw
../../../../out/target/product/deb/system/bin/ATFWD-daemon
../../../../out/target/product/deb/system/bin/bridgemgrd
../../../../out/target/product/deb/system/bin/btnvtool
../../../../out/target/product/deb/system/bin/diag_klog
../../../../out/target/product/deb/system/bin/diag_mdlog
../../../../out/target/product/deb/system/bin/ds_fmc_appd
../../../../out/target/product/deb/system/vendor/lib/egl/eglsubAndroid.so
[...]

doniks

@Andreas-Pokorny said in building for Nexus 7 deb:

At first I thought about looking into this:

If none of that gets you any further - use adb while in recovery and go to /data/system-data and examine the var/log files for clues..
But really, I think the problem with that build was that the root partition never got mounted, I'm not even sure whether much of anything of the initrd got mounted/executed

However, I think i must have messed up something earlier, maybe I did still end up using the old kernel config, I don't know, at some point (without having knowingly done something different) the screen came up (and adb as well). But then the display was all garbled up. I can recognize that it's trying to display the welcome screen, but the colors are all distorted, looking pink and green and it seems as if the characters shown are all way too big and don't really fit on the screen.

At that point, I thought, ok, lets switch to that other kernel,

@doniks You might want to try the google_msm kernel in ubports. It already contains the apparmor and other backports:
https://github.com/ubports/android_kernel_google_msm/tree/ubp-5.1

but it does not contain a reasonable kernel config for flo.

so I change the manifest to

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
  <remote       name="cm"       fetch="http://github.com/CyanogenMod"       revision="refs/heads/cm-12.1" />
  <project       path="device/asus/deb"       name="android_device_asus_deb"       remote="cm"       revision="cm-12.1" />  
  <project       path="device/asus/flo"       name="android_device_asus_flo"       remote="cm"       revision="cm-12.1" />

  <!--
  <project       path="kernel/google/msm"       name="android_kernel_google_msm"       remote="cm"       revision="cm-12.1" />
  <remote       name="ubp"      fetch="http://github.com/ubports"      review="http://review.ubports.com"      revision="refs/heads/ubp-5.1" />
  -->

   <project       path="kernel/google/msm"       name="ubports/android_kernel_google_msm"       remote="ubp"        revision="ubp-5.1" />  
</manifest>

and copied the cyanogen_flo_defconfig file back. Ie, the one from cm deb repo with all the check-config adjustments. Rebuilt and

fastboot boot boot.img

but that produces the same result actually, adb comes up, screen comes up, display is all garbled up. Not sure, what's next.