@karsten One thing that would help me is an explanation why the bootloader refuses to boot my custom boot.img with FAILED (remote: 'dtb not found'). I know there’s a dtbo partition but I don’t know inhowfar that’s used by the bootloader. I’ve built the kernel using the msm8953-perf_defconfig, and …

good links. some scary things there regarding the qcom bootloader. we’re going to have to be careful to not brick our phones :wink: what I meant is: with a regular boot sequence from slot A, the bootloader loads the boot image from boot partition A extracts the kernel, ramdisk, and dtb from that…

[image] corvuscorax: we’re going to have to be careful to not brick our phones Too late :grin: (waiting for stock rom or a rooted phone) If the bootloader read the dtbo partition, it is on the active slot (pretty sure, from the test I did, which bricked my phone…). You can know which one is …

I didn’t manage to compile overlay dtbo 's It’s possible to start compilation by setting CONFIG_BUILD_ARM64_DT_OVERLAY=y and export EXT_DTC=$( which dtc ) (assuming you have a system wide dtc installed which supports the -@ directive. apt-get device-tree-compiler does the trick however the…

[image] pigpig: You can know which one is active with “getvar all”, or change it with “–set-active=b” Interesting find: Slot A was active. I set it to slot B and tried to boot. I still cannot boot anything I give it with fastboot boot boot.img Same as before (dtb not found) But the phon…

Actually, you can change its state : ~ % sudo fastboot getvar all [...] (bootloader) current-slot:a (bootloader) slot-retry-count:b:0 (bootloader) slot-success:b:No (bootloader) slot-active:b:No (bootloader) slot-unbootable:b:Yes (bootloader) slot-retry-count:a:1 (bootloader) slot-success:a:No (boo…

[image] corvuscorax: It can boot into recovery and after trying to boot into android and failing for 3 times, it enters into a minimal recovery menu instead. (only options are “try again” and “Factory data reset”) I don’t want to quote the whole post, but do I smell possible solution vectors …

I found some more info on the hardware: The closest dts seems to be sdm632-mtp-s3.dts because a bugreport (adb bugreport something.zip) contains a full dmesg from boot: <5>[ 0.000000] Linux version 4.9.112-perf+ (build@15e77c5c4e08) (gcc version 4.9.x 20150123 (prerelease) (GCC) ) #2 SMP PREEMP…

Actually, that kinda makes sense, from https://source.android.com/devices/bootloader/flashing-updating The way an A/B update works is – assume working system is booted from slot A: (according to how I understand https://source.android.com/devices/tech/ota/ab/#post-installation ) data of the OTA …

There’s some more info which fields are used for what: FairphoneMirrors/android_kernel_fairphone_sdm632/blob/master/Documentation/devicetree/bindings/arm/msm/board-id.txt * BOARD-ID The qcom,board-id entry specifies the MSM platform and subtype revision. It can optionally be an arr…

Also relevant, bugreport dmesg contains the kernel command line. Only issue is a buffer overrun, its truncated after 4 lines, but still includes valuable info Kernel command line: kpti=0 console=ttyMSM0,115200,n8 androidboot.console=ttyMSM0 androidboot.hardware=qcom msm_rtb.filter=0x237 ehci-hcd.pa…

FP3 custom rom development based on released source code

Participate Development

AnotherElk January 6, 2020, 10:56pm 37

I don’t want to quote the whole post, but do I smell possible solution vectors here for the following? …