Hello, I am also facing the same issue on the Google Pixel 5 with redbull kernel.
If I use the default prebuilt kernel from the AOSP tree, I am able to flash and boot successfully. I was also having success with the factory image. However, when building a custom kernel using the android-msm-redbull-4.19-android11-qpr2 repo branch provided by this guide <https://source.android.com/setup/build/building-kernels>, I am stuck at the Google logo screen with the "waiting for any device" message: Here is my log: $ fastboot flashall -w -------------------------------------------- Bootloader Version...: r3-0.3-7051238 Baseband Version.....: g7250-00069-210128-B-7108850 Serial Number........: 11141FDD4001LG -------------------------------------------- Checking 'product' OKAY [ 0.070s] Setting current slot to 'a' OKAY [ 0.290s] Sending 'boot_a' (9324 KB) OKAY [ 0.412s] Writing 'boot_a' OKAY [ 0.324s] Sending 'dtbo_a' (16384 KB) OKAY [ 0.650s] Writing 'dtbo_a' OKAY [ 0.180s] Sending 'vbmeta_a' (8 KB) OKAY [ 0.140s] Writing 'vbmeta_a' OKAY [ 0.078s] Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.140s] Writing 'vbmeta_system_a' OKAY [ 0.077s] Sending 'vendor_boot_a' (18844 KB) OKAY [ 0.670s] Writing 'vendor_boot_a' OKAY [ 0.120s] Rebooting into fastboot OKAY [ 0.070s] *< waiting for any device >* No changes have been made to the kernel. Would appreciate any advice. Thanks! ~Joshua On Tuesday, 15 December 2020 at 00:03:16 UTC+8 xiling.gong wrote: > > Hello Henry, > > Thanks a lot for your reply. > > I've got the same issue on Pixel4 and fixed it using your method. > > But Pixel5 looks like a bit different and unable to be fixed with the same > solution. > All the .ko built on Pixel5 is unable to be insmod into kernel. > Don't know where is the root cause... > > 在2020年12月3日星期四 UTC+8 上午2:36:48<henryda...@gmail.com> 写道： > >> Hello, >> >> I had a similar problem on a Pixel 4 and fixed it by pushing all the .ko >> files from the kernel dist directory to /vendor/lib/modules. >> >> On Sun, 29 Nov 2020 at 19:11, xiling.gong <xilin...@gmail.com> wrote: >> >>> Hello, I'm working on a Pixel5 with AOSP and custom build kernel. >>> The issue is that I can't flash/boot the Pixel5 with custom build kernel. >>> Anyone please help to check this issue? >>> Thanks a lot. >>> >>> *kernel source:* >>> >>> * repo init -u https://android.googlesource.com/kernel/manifest >>> <https://android.googlesource.com/kernel/manifest> >>> -b android-msm-redfin-4.19-android11-d1 * >>> *AOSP source:* >>> * repo init -u https://android.googlesource.com/platform/manifest >>> <https://android.googlesource.com/platform/manifest> -b android-11.0.0_r15* >>> >>> Build the kernel >>> ./build/build.sh >>> Then put >>> MSM_KERNEL/out/android-msm-pixel-4.19/dist/Image.gz-dtb >>> to >>> AOSP_SOURCE/device/google/redfin-kernel/ >>> then build the aosp >>> source build/environment >>> lunch aosp_redfin-userdebug >>> make -j8 >>> fastboot flashall >>> When do flash, the flash process will hang at >>> < waiting for any device > >>> -------------------------------------------- >>> Bootloader Version...: r3-0.3-6776358 >>> Baseband Version.....: g7250-00016-200911-B-6826885 >>> Serial Number........: 09261FDD4003XC >>> -------------------------------------------- >>> Checking 'product' OKAY [ 0.068s] >>> Setting current slot to 'b' OKAY [ 0.411s] >>> Sending 'boot_b' (98304 KB) OKAY [ 12.051s] >>> Writing 'boot_b' OKAY [ 1.977s] >>> Sending 'dtbo_b' (16384 KB) OKAY [ 2.150s] >>> Writing 'dtbo_b' OKAY [ 0.386s] >>> Sending 'vbmeta_b' (8 KB) OKAY [ 0.139s] >>> Writing 'vbmeta_b' OKAY [ 0.078s] >>> Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.140s] >>> Writing 'vbmeta_system_b' OKAY [ 0.078s] >>> Sending 'vendor_boot_b' (98304 KB) OKAY [ 12.632s] >>> Writing 'vendor_boot_b' OKAY [ 2.020s] >>> Rebooting into fastboot OKAY [ 0.066s] >>> < waiting for any device > >>> And the phone keeps rebooting. >>> >>> I've also tried to replace a single .ko (e.g., cam_flash.ko) in >>> MSM_KERNEL/android-msm-pixel-4.19/dist/ >>> into >>> AOSP_SOURCE/device/google/redfin-kernel/ >>> Then build the aosp and flashall, it will also failed to finish the >>> flash and the system hang. >>> >>> If I push MSM_KERNEL/android-msm-pixel-4.19/dist/cam_flash.ko to >>> /data/local/tmp/, >>> and then insmod >>> insmod cam_flash.ko >>> it will fail with message >>> insmod : failed to load cam_flash.ko: Exec format error >>> >>> Thanks a lot. >>> >>> -- >>> -- >>> You received this message because you are subscribed to the "Android >>> Building" mailing list. >>> To post to this group, send email to android-...@googlegroups.com >>> To unsubscribe from this group, send email to >>> android-buildi...@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-buildi...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/android-building/f6f8fcc5-e617-4ef7-93ec-6b65a573b43fn%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/android-building/f6f8fcc5-e617-4ef7-93ec-6b65a573b43fn%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/cbeb01b6-5d1e-484e-8b8a-b40aaa2efa68n%40googlegroups.com.
