Nokia 1 Plus doesn't boot on v216+

[ghost]

• system-quack-arm32_binder64-ab-vanilla.img
• Stock recovery
• Shows the usual Android Go boot screen, doesn't get to the actual AOSP boot screen
• Not booting far enough for adb to be available
• Runs slightly warm
• Had to remove battery as it didn't react to long power button press

It booted fine in v215 and v214

[ghost]

I can try getting a ramoops if that's helpful - can take a while though since there's no TWRP for the Nokia 1 Plus yet so it'll be a bit of fiddling around

[ghost]

flash boot.img and vendor.img from stock rom this should fix this problem..

[ghost]

Everything except system is already stock from March 2020, which I think was the last Android 9 OTA for the 1 Plus, Nokia started rolling out the 10 OTA a few days ago, but I haven't been able to get stock's update manager to notice that yet.

I completely re-flashed the device with stock ROM from October 2019 and went through the available OTAs up until March, and only then went and tried the Treble builds.

[ghost]

strange, I will do some tests with the boot, any news post the result here

[ghost]

Thank you, I appreciate the support - I'm still relatively new to Android and it's a bit overwhelming at times.

> cat /vendor/build.prop | grep build                                                                                                                                                                                                   
ro.vendor.build.date=Thu Mar 5 16:03:30 CST 2020
ro.vendor.build.date.utc=1583395410
ro.vendor.build.fingerprint=Nokia/Antman_00WW/ANT:9/PPR1.180610.011/00WW_0_98E:user/release-keys
ro.vendor.build.security_patch=2019-01-05

And my boot.img is really strange:

> adb shell 'cat /dev/block/by-name/boot > /mnt/boot.img' && adb pull /mnt/boot.img
/mnt/boot.img: 1 file pulled. 14.7 MB/s (16777216 bytes in 1.087s)
> abootimg -i boot.img
boot.img: ramdisk size is null
boot.img: not a valid Android Boot Image.

I can upload it somewhere if you want.

[ghost]

Oh well I guess if I can't work with the boot.img, I can't fiddle my way to a ramoops either.

> file boot.img
boot.img: Android bootimg, kernel (0x40008000), page size: 2048, cmdline (bootopt=64S3,32S1,32S1 buildvariant=user veritykeyid=id:6eca8159f395095f595e8c78044c79b1bfeb357)

> ./mtkimg/build/mtkimg info boot.img
MTKIMG V0.44(linux64) by rom1nux

Image header :

 Signature                      : ANDROID!

 Kernel size                    : 8132922 bytes
 Kernel load address            : 0x40008000

 Ramdisk size                   : 0 bytes
 Ramdisk load address           : 0x45000000

 Second stage size              : 0 bytes
 Second stage load address      : 0x40F00000

 Tags address                   : 0x44000000
 Page size                      : 2048 bytes
 Product name                   : ''
 Command line                   : 'bootopt=64S3,32S1,32S1 buildvariant=user veritykeyid=id:6eca8159f395095f595e8c78044c79b1bfeb357e'
 ID                             : DA9D09AC2EB4FE21EDB01FA4131BBCBBF1F3F018

Image layout :

 Bloc           Offset      Pages    Size (bytes)
 ------------------------------------------------
 Header     0x00000000          1            2048
 Kernel     0x00000800       3972         8134656
 Ramdisk    0x007C2800          0               0
 Free       0x007C2800       4219         8640512
 ------------------------------------------------
 Total                       8192        16777216
 ------------------------------------------------

[ghost]

Update: more recent releases (v217, v219) don't boot either.

I also regularly try out @AndyCGYan's LineageOS 17.x GSIs but these stopped booting with the May release too. With the Lineage images, I at least get to the Lineage boot screen though and my computer notices an MTP device, but unfortunately no ADB.

Regarding Nokia Android 10 update, I had to roll that back, they did something about dm-verity which prevents anything non-standard from booting.

I'm also still looking into ramoops.