[android-building] Error building msm kernel android-msm-crosshatch-4.9-pie-qpr2
I'm getting theese errors after a few minutes when I run the *build/build.sh
*command
home/Chiang/msm/private/msm-google/scripts/link-vmlinux.sh: line 93: 31794
Killed ${LD} ${LDFLAGS} -r -o ${1} $(modversions)
${objects}
make[2]: *** [/home/Chiang/msm/private/msm-google/Makefile:1099: vmlinux]
Error 137
make[1]: *** [Makefile:152: sub-make] Error 2
make: *** [Makefile:24: __sub-make] Error 2
*repo init -u https://android.googlesource.com/kernel/manifest -b
android-msm-crosshatch-4.9-pie-qpr2*
*repo sync*
*sudo su*
*build/build.sh*
Without being su I run into some permission denied errors as follows:
rm: cannot remove '.tmp_versions/snd-soc-wcd934x.mod': Permission denied
rm: cannot remove '.tmp_versions/ftm5.mod': Permission denied
rm: cannot remove '.tmp_versions/snd-soc-wcd-spi.mod': Permission denied
rm: cannot remove '.tmp_versions/pinctrl-wcd.mod': Permission denied
rm: cannot remove '.tmp_versions/sec_touch.mod': Permission denied
rm: cannot remove '.tmp_versions/snd-soc-wcd9xxx.mod': Permission denied
rm: cannot remove '.tmp_versions/snd-soc-cs35l36.mod': Permission denied
rm: cannot remove '.tmp_versions/snd-soc-sdm845-max98927.mod': Permission
denied
rm: cannot remove '.tmp_versions/wcd-core.mod': Permission denied
rm: cannot remove '.tmp_versions/wcd-dsp-glink.mod': Permission denied
rm: cannot remove '.tmp_versions/snd-soc-sdm845.mod': Permission denied
I have run
*sudo apt-get update*
--
--
You received this message because you are subscribed to the "Android Building"
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en
---
You received this message because you are subscribed to the Google Groups
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to android-building+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[android-building] Locking bootloader after flashing custom ROM/kernel
Hi, Im wondering if there is some way after building clean-ish aosp to re-lock the bootloader? I end up in bootloader loop if I lock it. Any in-depth tutorial would be appreciated. Any tutorials for this? Regarding the Google Pixel devices. Thank you -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to android-building@googlegroups.com To unsubscribe from this group, send email to android-building+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-building+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [android-building] Touchscreen not working after building and flashing clean msm kernel for the Google Pixel blueline
Thanks! Hmm, So it is not possible to flash custom ROM/kernels on the Google Pixel Device ending up with enabled dm-verity? Or is that for all Android Devices? Is it possible to flash custom rom/kernels without disabling dm-verity? On Tuesday, 2 April 2019 23:23:04 UTC+2, Alessio Balsini wrote: > > > Thank you! > > This seemed to work :) > > Had to run the adb disable-verity command before remounting. > > That's strange, `adb remount` with -R should also disable verity. > Anyway, cool that it worked. > > > I tried enabling dm-verity after pushing the .ko modules > > > > It has resulted in "Your device is corrupt. It can't be trusted and may > not work properly. > > Visit this link on another device: g.co/ABH" > > > > Pressing the power button to continue takes me into the bootloader for a > few seconds, I see the Google logo for about 1sec. And Im back into the > Fastboot Mode. I guess I can flash Pixel factory image. But how do I get > pass the dm-verity check? > > That is an expected behavior, enforced for security reasons. > Unfortunately, being able to pass the verity checks would require to > update vendor.img, as well as the keys for all the verity checks, that > is not possible... > > Regards, > Alessio > -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to android-building@googlegroups.com To unsubscribe from this group, send email to android-building+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-building+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [android-building] Touchscreen not working after building and flashing clean msm kernel for the Google Pixel blueline
I built the kernel using this guide https://source.android.com/setup/build/building-kernels with the build/build.sh command Do you have a tutorial for using the make bootimage command? Or should I just run the make bootimage command instead of the shell? And flash it in the same way Thanks! fredag 29. mars 2019 15.45.37 UTC+1 skrev Alessio Balsini følgende: > > Hi, > > > The phone reboots. But then I am not able to use the touch screen at > all. I cant unlock the phones sim card. If I hold down the power button for > a while and reboot it. The touch screen works. Not sure what causes that, > but maybe the kernel has been removed and switched out with the old one? > > How did you build the kernel? > I suspect your device is missing the touch screen drivers (maybe the > drivers you have in your device are not compatible with your kernel). > > `fastboot boot` just loads your boot image into ram, it does not flash > the boot partition. That's why the device switches back to the old > kernel after reboot. > > > Another similar question is. If Id like to put the Image.lz4-dtb file > inside the AOSP ROM. Where should I put it, and is that possible? If that > would make me able to flash both kernel and ROM at the same time? > > You should update the files in device/google/crosshatch-kernel and > then run `make bootimage`. > > Cheers, > Alessio > -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to android-building@googlegroups.com To unsubscribe from this group, send email to android-building+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-building+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[android-building] Touchscreen not working after building and flashing clean msm kernel for the Google Pixel blueline
Hi I have built and flashed clean AOSP. fastboot flashall -w Which worked like a charm. Thn I build msm and flashed it with fastboot boot Image.lz4-dtb The phone reboots. But then I am not able to use the touch screen at all. I cant unlock the phones sim card. If I hold down the power button for a while and reboot it. The touch screen works. Not sure what causes that, but maybe the kernel has been removed and switched out with the old one? Another similar question is. If Id like to put the Image.lz4-dtb file inside the AOSP ROM. Where should I put it, and is that possible? If that would make me able to flash both kernel and ROM at the same time? -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to android-building@googlegroups.com To unsubscribe from this group, send email to android-building+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-building+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[android-building] No ram.img file after successfully building AOSP
build completed successfully (05:33:52 (hh:mm:ss))
im running the emulator command in my AOSP folder. Not sure why the ram.img
isnt built. For the Google Pixel 3 - blueline.
emulator
emulator: WARNING: Couldn't find crash service executable
AOSP/prebuilts/android-emulator/linux-x86_64/emulator64-crash-service
emulator: WARNING: system partition size adjusted to match image file (1018
MB > 800 MB)
statvfs('AOSP/out/target/product/blueline/snapshots/default_boot/ram.img')
failed: No such file or directory
emulator: WARNING: encryption is off
--
--
You received this message because you are subscribed to the "Android Building"
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en
---
You received this message because you are subscribed to the Google Groups
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to android-building+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
