yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Fyramiz:
Can you please help me,ive compiled twrp(struggling as i don't have kernel source so used stock kernel which is big so i used TW_EXCLUDE tags) and the device is A/B unisoc powered device with super partition and i can't use fastboot boot as its a unisoc(tryed it in fastboot and fastbootd) and i tryed to just flash it to inactive slot but stuck at factory bootloader logo i restored device using SPD flash tool but recovery doesn't work, if any know solution plz tell me
[Android Software Development] GivFNZ:
Oh nice, I was having this issue too, but that fixed my issue, thank you!
[Android Software Development] Anghirrim:
Hello,

With ArchVisions, we recently managed to build TWRP for the Galaxy Tab S9 FE (here).

However, I have a questions regarding the patched vbmeta.img. Is it supposed to be device specific or generic?

I tried to compare some by unpacking them using the following tool: https://github.com/cfig/Android_boot_image_editor

The content of the output vbmeta.avb.json is different from one one vbmeta to another. One is almost completely empty (except from the structure), another one is a copy/paste of the stock vbmeta.img extract, and I couldn't understand how it can be called "patched".

Shall we always generate a patched vbmeta.img (knowing that on Samsung devices we have no fastboot), or can we just use an empty one (except from the structure)?

Thanks for your help.
[Android Software Development] tham.400:
What's wrong here? I'm trying to compile TWRP for oriole (Pixel 6) and it keeps throwing this error when building the vendor_boot

FAILED: Target vendor_boot image: out/target/product/oriole/vendor_boot.img
Outputs: out/target/product/oriole/vendor_boot.img
Error: exited with code: 1
Command: /bin/bash -c "(out/host/linux-x86/bin/mkbootimg --dtb out/target/product/oriole/dtb.img --vendor_cmdline \"buildvariant=userdebug\" --base --pagesize --ramdisk_offset --tags_offset --kernel_offset --header_version 4 --dtb_offset --vendor_cmdline --vendor_ramdisk out/target/product/oriole/obj/PACKAGING/vendor_boot_intermediates/vendor_ramdisk.cpio.gz --ramdisk_type RECOVERY --ramdisk_name recovery --vendor_ramdisk_fragment out/target/product/oriole/obj/PACKAGING/vendor_ramdisk_fragments_intermediates/recovery.cpio.gz --vendor_boot out/target/product/oriole/vendor_boot.img ) && (size=\$(for i in out/target/product/oriole/vendor_boot.img; do stat -c \"%s\" \"\$i\" | tr -d '\\n'; echo +; done; echo 0); total=\$(( \$( echo \"\$size\" ) )); printname=\$(echo -n \"out/target/product/oriole/vendor_boot.img\" | tr \" \" +); maxsize=\$((67108864)); if [ \"\$total\" -gt \"\$maxsize\" ]; then echo \"error: \$printname too large (\$total > \$maxsize)\"; false; elif [ \"\$total\" -gt \$((maxsize - 32768)) ]; then echo \"WARNING: \$printname approaching size limit (\$total now; limit \$maxsize)\"; fi ) && (out/host/linux-x86/bin/avbtool add_hash_footer --image out/target/product/oriole/vendor_boot.img --partition_size 67108864 --partition_name vendor_boot --prop com.android.build.vendor_boot.fingerprint:\$(cat out/target/product/oriole/build_fingerprint.txt) )"
Output:
usage: mkbootimg [-h] [--kernel KERNEL] [--ramdisk RAMDISK] [--second SECOND]
[--dtb DTB]
[--recovery_dtbo RECOVERY_DTBO | --recovery_acpio RECOVERY_ACPIO]
[--cmdline CMDLINE] [--vendor_cmdline VENDOR_CMDLINE]
[--base BASE] [--kernel_offset KERNEL_OFFSET]
[--ramdisk_offset RAMDISK_OFFSET]
[--second_offset SECOND_OFFSET] [--dtb_offset DTB_OFFSET]
[--os_version OS_VERSION] [--os_patch_level OS_PATCH_LEVEL]
[--tags_offset TAGS_OFFSET] [--board BOARD]
[--pagesize {2048,4096,8192,16384}] [--id]
[--header_version HEADER_VERSION] [-o OUTPUT]
[--gki_signing_algorithm GKI_SIGNING_ALGORITHM]
[--gki_signing_key GKI_SIGNING_KEY]
[--gki_signing_signature_args GKI_SIGNING_SIGNATURE_ARGS]
[--gki_signing_avbtool_path GKI_SIGNING_AVBTOOL_PATH]
[--vendor_boot VENDOR_BOOT] [--vendor_ramdisk VENDOR_RAMDISK]
[--vendor_bootconfig VENDOR_BOOTCONFIG]
mkbootimg: error: argument --base: expected one argument
[Android Software Development] desalesouche:
+1
[Android Software Development] spanorg:
I am trying to copy some files to recovery/root/sbin or recovery/root with PRODUCT_COPY_FILES += \ but all are ignored. Do you know why ???

Thanks in advance.
[Android Software Development] f5bud:
screen is scrambled

hello,

I use CM12 sources https://github.com/omnirom/android_bootable_recovery

to build recovery for moto G LTE (XT1039)

The resolution config is good for this device: DEVICE_RESOLUTION := 720x1280 but at recovery boot the screen is scrambled

have you ever experienced that?
[Android Software Development] :
hi,

maybe this/these in boardconfig

RECOVERY_GRAPHICS_USE_LINELENGTH := true <---if already present/set, maybe comment out ?

TARGET_RECOVERY_PIXEL_FORMAT := "RGBA_8888" <---may be RGBX , i know i pulled a black screen with the wrong setting so maybe

m
[Android Software Development] andreya108:
iSerialno

Hi, all!

I've noticed that in my twrp build adb is showing 0123456789ABCDEF serial number to pc.

I tried to set correct ro.serialno in properties but after that adb not visible from pc any more.

So, again,

no ro.serialno defined -> adb visible with serial 0123456789ABCDEF

ro.serialno defined -> could not connect to adb

Please help, what is the matter?

ps: mass_storage and MTP are not working either when ro.serialno defined, so all usb stuff going down. No errors in log.
[Android Software Development] :
A,

hi,

sounds weird or maybe not,

if adb is putting out a bogus serial but, you can connect mtp,adb,mass_storage

then it doesn't seem like forcing the correct serial is helpful or useful.

also maybe it's a problem with your kernel source or you may be using a flag in your boardconfig that

isn't needed or isn't correct for your build/device. also check your kernel command line / boot args.

you may have a conflict. lastly check your pc's distro, you may need a downgrade/upgrade of android-tools-adb

and/or android-tools-fastboot.

m

---------- Post added at 07:59 PM ---------- Previous post was at 07:54 PM ----------

S,

monitor your build output for warnings concerning files which don't exist.

also check your product copy entries for format and go over your .mk's to be sure you're

calling/pointing to other sources correctly.

m
[Android Software Development] lj50036:
That is what everyone gets in twrp for a adb device output ?

0-9 a-f is hexadecimal, which is just how it works...... :D

Thx Josh
[Android Software Development] andreya108:
Thanks to all for answering!

Sounds reasonable, but why this restriction is needed?

When the system is loaded the actual non hex id is used in adb and it is ok.

---------- Post added at 10:46 AM ---------- Previous post was at 10:36 AM ----------

But who cares? That is just a "unique" id.

I cannot touch kernel, I use prebuilt one. The platform is MTK and we have no full kernel and drivers sources here for most of devices. kernel command line is empty. just upgraded android sdk and platform tools to the latest 21 version. nothing changed.

I'm adding the actual serialno in patched init.c (it can be found in /sys/sys_info/serial_number). The only thing my patch does is reading /sys/sys_info/serial_number and setting the result to ro.boot.serialno property. Then, in recovery I see it in ro.serialno (set in init.c further) and in usb/iSerial (set in init.rc).
[Android Software Development] katinatez:
Hello hope someone can help me figure this one out. I built twrp on android-5.0 and every function works but I get random reboots on occasions when in recovery. To duplicate this error I enter recovery and reboot into recovery and about the 3-5 time doing this, recovery reboots back into system.

Any ideas anyone?
[Android Software Development] f5bud:
For peregrine (XT1039)

Add in

msm8226-common/BoardConfigCommon.mk

TARGET_RECOVERY_PIXEL_FORMAT := "RGBX_8888"

Add in peregrine/BoardConfig.mk

TW_EXCLUDE_MTP := true

DEVICE_RESOLUTION := 720x1280

TW_IGNORE_MAJOR_AXIS_0 := true

RECOVERY_GRAPHICS_USE_LINELENGTH := true

Add in peregrine/device.mk

PRODUCT_COPY_FILES += \

$(LOCAL_PATH)/rootdir/etc/twrp.fstab:recovery/root/etc/twrp.fstab

peregrine/rootdir/etc/twrp.fstab

# mount point fstype device

/data f2fs /dev/block/platform/msm_sdcc.1/by-name/userdata flags=fsflags="inline_xattr"

/cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache

/system ext4 /dev/block/platform/msm_sdcc.1/by-name/system

/boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot

/recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery

/misc emmc /dev/block/platform/msm_sdcc.1/by-name/misc

/external_sd auto /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="microSD card";storage;removable

/usb-otg auto /dev/block/sda1 /dev/block/sda flags=display="USB OTG";storage;removable
[Android Software Development] ne0zone75:
You maybe should try to reverse this commit if you are building TWRP against CyanogenMod sources : here ;)

Now i would like to have some advice about building TWRP against CyanogenMod sources for S4 mini because since 2.8.0.0 i am not able to get a reliable build for it : the device is not always booting successfully to recovery :(

-> i am using android-4.4 omni sources for TWRP and building along with CM-11.0 sources tree

-> here are my TWRP build flags :

# TWRP
TW_HAS_DOWNLOAD_MODE := true
TW_NO_REBOOT_BOOTLOADER := true

DEVICE_RESOLUTION := 540x960
RECOVERY_GRAPHICS_USE_LINELENGTH := true
TARGET_LCD_BLANK_PATH := \"/sys/class/lcd/panel/backlight\"
TW_BRIGHTNESS_PATH := "/sys/devices/platform/mipi_samsung_oled.1281/lcd/panel/backlight"
TW_MAX_BRIGHTNESS := 255

RECOVERY_SDCARD_ON_DATA := true
TW_NO_USB_STORAGE := true

TW_INTERNAL_STORAGE_PATH := "/data/media/0"
TW_INTERNAL_STORAGE_MOUNT_POINT := "data"
TW_EXTERNAL_STORAGE_PATH := "/external_sd"
TW_EXTERNAL_STORAGE_MOUNT_POINT := "external_sd"

TW_INCLUDE_CRYPTO := true
TW_INCLUDE_CRYPTO_SAMSUNG := true
TW_CRYPTO_FS_TYPE := "ext4"
TW_CRYPTO_REAL_BLKDEV := "/dev/block/platform/msm_sdcc.1/by-name/userdata"
TW_CRYPTO_MNT_POINT := "/data"
TW_CRYPTO_FS_OPTIONS := "nosuid,nodev,noatime,noauto_da_alloc,journal_async_commit,errors=panic"
TW_CRYPTO_FS_FLAGS := "0x00000406"
TW_CRYPTO_KEY_LOC := "footer"

Since MTP is the major feature of 2.8.0.0 and issue appeared for it, i also tried to build TWRP with 'TW_EXCLUDE_MTP := true' build flag but it did not help...

Thank you for giving me some leads about solving this issue,

Regards

PS : [MENTION=3261191]F4k[/MENTION] => Did you manage to deal with the 'recovery not always booting' bug with 2.8.1.0 (android-4.4) or 2.8.2.0 (android-5.0) for S4 mini ?! Thanks !
[Android Software Development] katinatez:
I have the same bug, rebooting in recovery. Using all android-5.0 source and device tree. Compiled v2.8.2.0 & v2.8.3.0 and same bug. Do you know a fix?
[Android Software Development] F4k:
I've tried a fix by user [MENTION=5739341]thomson.aa[/MENTION] works for compiling TWRP android-4.4 branch, you have to add a line on twrp-functions.cpp

Search for this:

int TWFunc::Set_Brightness(std::string brightness_value)
{

std::string brightness_file = DataManager::GetStrValue("tw_brightness_file");;

And change for this:

int TWFunc::Set_Brightness(std::string brightness_value)
{
return 0;
std::string brightness_file = DataManager::GetStrValue("tw_brightness_file");;

android-5.0 doesn't seems to work so far for S4 Mini
[Android Software Development] ne0zone75:
Thank you for the fix :) and for clarifying the situation about TWRP android-5.0 branch for S4 mini !

Kind regards
[Android Software Development] whodisname:
Wrong thread.
[Android Software Development] linhbs:
It's nice for me. Thank you very much.
[Android Software Development] m0d:
I am trying to compile recovery for sony z3 compact.

I am using omnirom source, but the device and kernel trees from CM12 since omni does not have repos for z3c,

I get the following error,

libsepol.check_assertion_helper: neverallow on line 297 of external/sepolicy/domain.te (or line 5288 of policy.conf) violated by allow vold vfat:filesystem { relabelto };
Error while expanding policy

make: *** [/home/ne/zZz/omni/out/target/product/z3c/obj/ETC/sepolicy_intermediates/sepolicy] Error 1

How can or should I fix this error?

Thank you for your time
[Android Software Development] :
hi,

in boardconfig or device.mk of your device tree, as well as device/kernel common, you can try commenting out the complete

sepolicy/selinux union entries, clobber and re-run.

you may also need to remove the sepolicy directories in those devicecommon trees.

i just zip/archive them in place and then delete the directories. that way if you need to

restore them , just right click, extract here.

m
[Android Software Development] m0d:
Thank you.

I found this in msm8974-common/BoardConfigCommon.mk

# SELinux
include device/qcom/sepolicy/sepolicy.mk

BOARD_SEPOLICY_DIRS += \
device/sony/msm8974-common/sepolicy
# The list below is order dependent
BOARD_SEPOLICY_UNION += \
bluetooth.te \
device.te \
domain.te \
file.te \
location.te \
mac-update.te \
mpdecision.te \
radio.te \
rild.te \
sct.te \
sensors.te \
suntrold.te \
system_server.te \
tad.te \
ta_qmi.te \
tee.te \
thermanager.te \
time_daemon.te \
wpa.te \
file_contexts \
genfs_contexts

Do I comment all three: qcom/sepolicy and BOARD_SEPOLICY_DIRS and all the BOARD_SEPOLICY_UNION?

And in shinano-common/BoardConfigCommon.mk

# SELinux
BOARD_SEPOLICY_DIRS += \
device/sony/shinano-common/sepolicy
# The list below is order dependent
BOARD_SEPOLICY_UNION += \
file_contexts

And again here both BOARD_SEPOLICY_DIRS and the BOARD_SEPOLICY_UNION?

As for the line: export LD_LIBRARY_PATH .:/sbin

In which init do I add it to?

I have in z3c/rootdir the file init.sony.usb.rc (also init.device.rc)

and in shinano-common/rootdir I have init.recovery.qcom.rc (init.qcom.rc , fstab.qcom)

I am thinking either z3c/rootdir the file init.sony.usb.rc or shinano-common/rootdir I have init.recovery.qcom.rc but I am not sure which.

In shinano-common/shinano.mk

there is

# Init
PRODUCT_COPY_FILES += \
$(COMMON_PATH)/rootdir/fstab.qcom:root/fstab.qcom \
$(COMMON_PATH)/rootdir/init.qcom.rc:root/init.qcom.rc \
$(COMMON_PATH)/rootdir/init.recovery.qcom.rc:root/init.recovery.qcom.rc \
$(COMMON_PATH)/rootdir/ueventd.qcom.rc:root/ueventd.qcom.rc
[Android Software Development] :
hi,

comment out;

## SELinux

#include device/qcom/sepolicy/sepolicy.mk

#

#BOARD_SEPOLICY_DIRS += \

# device/sony/msm8974-common/sepolicy

## The list below is order dependent

#BOARD_SEPOLICY_UNION += \

# bluetooth.te \

# device.te \

# domain.te \

# file.te \

# location.te \

# mac-update.te \

# mpdecision.te \

# radio.te \

# rild.te \

# sct.te \

# sensors.te \

# suntrold.te \

# system_server.te \

# tad.te \

# ta_qmi.te \

# tee.te \

# thermanager.te \

# time_daemon.te \

# wpa.te \

# file_contexts \

# genfs_contexts

or you can back up boardconfig file as whatever.mk_bak

and then delete the commented example from above from the "original" and run your build/test

the build system defines it own policy in external/sepolicy , i've never found the specific ones in the device tree

to be useful/necessary

And for shinano-common/BoardConfigCommon.mk

do the same.

As for the line: export LD_LIBRARY_PATH .:/sbin

should be defined in init.environ.rc - after you run make/mka recoveryimage, look in out/../../../recovery/root and/or out/../../../root

# set up the global environment
on init
export PATH /sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
export LD_LIBRARY_PATH /vendor/lib:/system/lib
export ANDROID_BOOTLOGO 1
export ANDROID_ROOT /system
export ANDROID_ASSETS /system/app
export ANDROID_DATA /data
export ANDROID_STORAGE /storage
export ASEC_MOUNTPOINT /mnt/asec
export LOOP_MOUNTPOINT /mnt/obb
export BOOTCLASSPATH /system/framework/core.jar:/system/framework/conscrypt.jar:/system/framework/okhttp.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/framework2.jar:/system/framework/telephony-common.jar:/system/framework/voip-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/webviewchromium.jar:/system/framework/telephony-msim.jar:/system/framework/qcmediaplayer.jar

You will find that sometimes you need to perform interesting "tricks" to get a build through, don't lose track of your changes.

m
[Android Software Development] m0d:
I commented out everything but when I tried again I get a new error now:

target Prebuilt: (/home/ne/zZz/omni/out/target/product/z3c/kernel)
Target boot image: /home/ne/zZz/omni/out/target/product/z3c/boot.img
cp: cannot stat ‘/home/ne/zZz/omni/out/target/product/z3c/ramdisk-recovery.cpio’: No such file or directory
make: *** [/home/ne/zZz/omni/out/target/product/z3c/boot.img] Error 1
[Android Software Development] :
hmm, is the kernel source available for the device ?

you have to learn to understand you build's error/warning messages, in this case cp:cannot stat 'blah': No such blah

means;

dude, the instruction in your boardconfig says the file named 'blah' is located 'here' but i can't find it, :eek:

correct the entry which points to it's location, then clobber and start again.

m
[Android Software Development] m0d:
Thank you once again.

Yes the source is available, and I include the source in the manifest.

It might be a naming issue.

msm8974-common/BoardConfigCommon.mk points to the file:

BOARD_CUSTOM_BOOTIMG_MK := device/sony/msm8974-common/boot/custombootimg.mk

And,

In the file custombootimg.mk of msm8974-common/boot I have

uncompressed_ramdisk := $(PRODUCT_OUT)/ramdisk.cpio

I have ramdisk.cpio in the out directory, but I guess it is looking for ramdisk-recovery.cpio, or are they two separate files?

UPDATE:

I think I found it,

Something to do with dbtool:

DTBTOOL := $(HOST_OUT_EXECUTABLES)/dtbToolCM$(HOST_EXECUTABLE_SUFFIX)
$(INSTALLED_DTIMAGE_TARGET): $(DTBTOOL) $(TARGET_OUT_INTERMEDIATES)/KERNEL_OBJ/usr $(INSTALLED_KERNEL_TARGET)
$(call pretty,"Target DT image: $@")
$(hide) $(DTBTOOL) $(TARGET_DTB_EXTRA_FLAGS) -o $(INSTALLED_DTIMAGE_TARGET) -s $(BOARD_KERNEL_PAGESIZE) -p $(KERNEL_OUT)/scripts/dtc/ $(KERNEL_OUT)/arch/arm/boot/
@echo -e ${CL_CYN}"Made DT image: $@"${CL_RST}

$(INSTALLED_BOOTIMAGE_TARGET): $(PRODUCT_OUT)/kernel $(uncompressed_ramdisk) $(recovery_uncompressed_ramdisk) $(INSTALLED_RAMDISK_TARGET) $(INITSH) $(PRODUCT_OUT)/utilities/busybox $(PRODUCT_OUT)/utilities/extract_elf_ramdisk $(MKBOOTIMG) $(MINIGZIP) $(INTERNAL_BOOTIMAGE_FILES) $(INSTALLED_DTIMAGE_TARGET)
[Android Software Development] :
hi,

I am fairly certain that, ramdisk.cpio = ramdisk-recovery.cpio

make the change/rename in your boardconfig or msm8974-common/boot/custombootimg.mk

don't change anything in device/qcom/common/dtbtool/

m
[Android Software Development] m0d:
I tried that. It did not work.

I believe I needed to include: android_device_qcom_common

But, it is not adding dtbToolCM to out/host/linux-x86/bin during compilation.

This causes ramdisk-recovery.cpio not to be generated as dbtoolcm is needed to generate the file,

$(INSTALLED_BOOTIMAGE_TARGET): $(PRODUCT_OUT)/kernel $(uncompressed_ramdisk)[COLOR="Red"] $(recovery_uncompressed_ramdisk)[/COLOR] $(INSTALLED_RAMDISK_TARGET) $(INITSH) $(PRODUCT_OUT)/utilities/busybox $(PRODUCT_OUT)/utilities/extract_elf_ramdisk $(MKBOOTIMG) $(MINIGZIP) $(INTERNAL_BOOTIMAGE_FILES) $(INSTALLED_DTIMAGE_TARGET)

which in turn generates the error.

Somehow this is not being triggered, [device/qcom/common/Android.mk]:

ifneq (,$(filter $(QCOM_BOARD_PLATFORMS),$(TARGET_BOARD_PLATFORM)))

include $(all-subdir-makefiles)

endif
[Android Software Development] :
hi

:eek: :eek: :eek: :p :laugh:

okay, i was operating under the impression that you had the required source present and accounted for.

yes you need device/qcom/common/dtbtool

git clone https://github.com/CyanogenMod/android_device_qcom_common.git

rename directory appropriately

for build using the prebuilt method make sure you have a similar entry for dt.img/dtb as you do for kernel

for inline build you need the following accounted for in boardconfig.mk of your actual device tree, not common

BOARD_KERNEL_CMDLINE := [your kernel command line and add the following outside brack to the end] --dt dt.img

BOARD_KERNEL_SEPARATED_DT := true

isn't this fun ? :silly:

m
[Android Software Development] m0d:
Hey,

What do you mean by the above I do not quite follow?

I added the following to device/sony/z3c/BoardConfig.mk

BOARD_KERNEL_CMDLINE := [androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3 dwc3.maximum_speed=high dwc3_msm.prop_chg_detect=Y] --dt dt.img
BOARD_KERNEL_SEPARATED_DT := true

But still got:

target Prebuilt: (/home/ne/zZz/omni/out/target/product/z3c/kernel)
[COLOR="Red"]Target boot image[/COLOR]: /home/ne/zZz/omni/out/target/product/z3c/[COLOR="Red"]boot.img[/COLOR]
cp: cannot stat ‘/home/ne/zZz/omni/out/target/product/z3c/ramdisk-recovery.cpio’: No such file or directory
make: *** [/home/ne/zZz/omni/out/target/product/z3c/boot.img] Error 1

EDIT: Another thing I noticed - boot.img is not in out directory.

It is not created or pulled from kernel.

In the out directory only kernel, ramdisk.img, and ramdisk.cpio are on the top directory.

It is still not generating dbToolCM which in turn does not make the .cpio file.

Boo

I found the following in device/sony/shinano-common/BoardConfigCommon.mk which I used above for BOARD_KERNEL_CMDLINE

# Kernel information
BOARD_KERNEL_BASE := 0x00000000
BOARD_KERNEL_PAGESIZE := 2048
[COLOR="DeepSkyBlue"]BOARD_KERNEL_CMDLINE[/COLOR] := androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3 dwc3.maximum_speed=high dwc3_msm.prop_chg_detect=Y
BOARD_MKBOOTIMG_ARGS := --ramdisk_offset 0x02000000 --tags_offset 0x01E00000
BOARD_KERNEL_SEPARATED_DT := true
TARGET_DTB_EXTRA_FLAGS := --force-v2

Yes.

So much fun.

But I need to sleep now.

Hope tomorrow brings the rainbow with a pot of TWRP.
[Android Software Development] :
hi,

the kernel command line does not go in bracket/braces that was just used to display an

[example] <example> example. :eek:

compress and upload your device tree to mega, google drive, or dev-host,

include your prebuilt kernel and dt.img

our combined psychic might is not enough to solve this problem ! :silly:

m
[Android Software Development] katinatez:
I'm trying to read your conversation and believe you want to compile with prebuilt kernel & dt.img; if so here is a perfect example of that here

https://github.com/katinatez/android_device_oneplus_bacon-kernel

Hope it helps