yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Ryrzy:
hi...

first... thanks for you grat job !! twrp reovery is realy good !!!

now, my problem :)

i got working (at last... ufff) recovery for my rk3066 rockchip tablet, and i have compile twrp for it... but there is a problem... when i make backup, everything is ok... but when i restore some of mtd parytions it restores and restores and restores.... and it cant stop restore :) sometimes it makes nothing, sometimes it bricks my tab and i must flash it with stock full ROM... ;/ when i restore partitions like system and data there is no problems..

my recovery.fstb looks like this:

# mount point	fstype	device	[device2]
/boot	mtd	boot
/recovery	mtd	recovery
/kernel	mtd	kernel
/misc	mtd	misc
/cache	ext4	/dev/block/mtdblock6
/data	ext4	/dev/block/mtdblock7
/system	ext4	/dev/block/mtdblock9
/sdcard vfat /dev/block/mtdblock10
/external_sd	vfat	/dev/block/mmcblk0p1	/dev/block/mmcblk0

maybe i do something wrong ? please help ;/
[Android Software Development] Ryrzy:
i have changed my recovery fstab and now in cwm everything works nice, restoring boot is ok and tablet is working, but in twrp still not working... now twrp is restoring it seems ok but tab is death after restore :) i dont have any idea whats wrong... but it seems that something in twrp...

fstab:

# mount point fstype device [device2]
/misc emmc /dev/block/mtdblock1
/kernel emmc /dev/block/mtdblock2
/boot emmc /dev/block/mtdblock3
/recovery emmc /dev/block/mtdblock4
/cache ext4 /dev/block/mtdblock6
/data ext4 /dev/block/mtdblock7
/system ext4 /dev/block/mtdblock9
/sdcard vfat /dev/block/mtdblock10
/external_sd vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0

twrp log:

[RESTORE STARTED]

Restore folder: '/external_sd/TWRP/BACKUPS/0000000000000000/2013-10-07--12-58-51 PMP5870C_20130921_v4.0_by_Ryrzy'
Skipping MD5 check based on user setting.
Restoring 4 partitions...
I:Restore filename is: misc.emmc.win
I:Restore file system is: 'emmc'.
Restoring misc...
I:Restore command: 'dd bs=4096 if='/external_sd/TWRP/BACKUPS/0000000000000000/2013-10-07--12-58-51 PMP5870C_20130921_v4.0_by_Ryrzy/misc.emmc.win' of=/dev/block/mtdblock1'
1024+0 records in
1024+0 records out
4194304 bytes (4.0MB) copied, 0.293238 seconds, 13.6MB/s
I:dd bs=4096 if='/external_sd/TWRP/BACKUPS/0000000000000000/2013-10-07--12-58-51 PMP5870C_20130921_v4.0_by_Ryrzy/misc.emmc.win' of=/dev/block/mtdblock1 process ended with RC=0
[misc done (1 seconds)]

I:Restore filename is: kernel.emmc.win
I:Restore file system is: 'emmc'.
Restoring kernel...
I:Restore command: 'dd bs=4096 if='/external_sd/TWRP/BACKUPS/0000000000000000/2013-10-07--12-58-51 PMP5870C_20130921_v4.0_by_Ryrzy/kernel.emmc.win' of=/dev/block/mtdblock2'
2048+0 records in
2048+0 records out
8388608 bytes (8.0MB) copied, 1.084525 seconds, 7.4MB/s
I:dd bs=4096 if='/external_sd/TWRP/BACKUPS/0000000000000000/2013-10-07--12-58-51 PMP5870C_20130921_v4.0_by_Ryrzy/kernel.emmc.win' of=/dev/block/mtdblock2 process ended with RC=0
[kernel done (1 seconds)]

I:Restore filename is: boot.emmc.win
I:Restore file system is: 'emmc'.
Restoring boot...
I:Restore command: 'dd bs=4096 if='/external_sd/TWRP/BACKUPS/0000000000000000/2013-10-07--12-58-51 PMP5870C_20130921_v4.0_by_Ryrzy/boot.emmc.win' of=/dev/block/mtdblock3'
4096+0 records in
4096+0 records out
16777216 bytes (16.0MB) copied, 2.328311 seconds, 6.9MB/s
I:dd bs=4096 if='/external_sd/TWRP/BACKUPS/0000000000000000/2013-10-07--12-58-51 PMP5870C_20130921_v4.0_by_Ryrzy/boot.emmc.win' of=/dev/block/mtdblock3 process ended with RC=0
[boot done (2 seconds)]

I:Restore filename is: recovery.emmc.win
I:Restore file system is: 'emmc'.
Restoring recovery...
I:Restore command: 'dd bs=4096 if='/external_sd/TWRP/BACKUPS/0000000000000000/2013-10-07--12-58-51 PMP5870C_20130921_v4.0_by_Ryrzy/recovery.emmc.win' of=/dev/block/mtdblock4'
4096+0 records in
4096+0 records out
16777216 bytes (16.0MB) copied, 2.096117 seconds, 7.6MB/s
I:dd bs=4096 if='/external_sd/TWRP/BACKUPS/0000000000000000/2013-10-07--12-58-51 PMP5870C_20130921_v4.0_by_Ryrzy/recovery.emmc.win' of=/dev/block/mtdblock4 process ended with RC=0
[recovery done (2 seconds)]
[Android Software Development] feiplane:
hi guys,

1st of all, Thx Team Win for creating this great recovery:good:

I've successfully compiled for my HTC Desire 600 but with 1 issue.

I've set flags for the external sd, but in TWRP, all the flags became unhandled starting from settingsstorage

/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=removable;storage;settingsstorage;backup=1;display="MicroSD";storagename="MicroSD";backupname="MicroSD"

I can't see any error inside the script, anyone can help me with it?
[Android Software Development] Ryuinferno:
/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="MicroSD";storagename="MicroSD";backupname="MicroSD"removable;storage;settingsstorage;backup=1

Try this instead...
[Android Software Development] feiplane:
Thx for reply, trying it now

so the order of the flags matters?

and about the settingsstorage, is it double s or single s?

btw, this might be off topic a bit to ask but I just can't find the answer,

why every recoverys(including CWM, Philz and TWRP) I compiled with CM10.1 source, all of them have a same behavior that is,

everytime going into the recovery, after certain time frame, it will just reboot automatically by itself, either idle or work in progress, manual reboot(system, recovery, bootloader) will takes long time to perform too.

At 1st, I thought my phone is hang but later found out that it is not, it just needs time to do it, but reboot with adb command, no such problem at all, really strange.

With CM10.2 source, all recoverys refused to work at all, there is just black screen with flashes in certain interval and no adb access......:eek:

is it something to do with my device's android version?
[Android Software Development] feiplane:
well, still no cure

storagename="MicroSD"

backupname="MicroSD"

settingsstorage

backup=1

these 4 are those unhandled
[Android Software Development] feiplane:
alright, it is nothing to do with the scripts but the source I use, 2.4 is too low for those 4 flags to work properly......
[Android Software Development] Xperia_Modder:
hello guys

I've built TWRP 2.7 for my xperia u (cm10.2) but touch isn't working, how to solve it?

i'm using these boardconfig flags:

#TWRP

HAVE_SELINUX := true
DEVICE_RESOLUTION := 480x854
RECOVERY_GRAPHICS_USE_LINELENGTH := true
BOARD_HAS_NO_REAL_SDCARD := true
TW_NO_REBOOT_BOOTLOADER := true

ps: i don't have a prebuilt init.rc, maybe this is why touch doesn't work
[Android Software Development] DualJoe:
- Check dmesg log. You're probably missing firmware or kernel object (*.ko).

- Check original *.rc's for loaded modules (insmod).
[Android Software Development] Xperia_Modder:
Thanks i'll try

Inviato dal mio Xperia U con Tapatalk
[Android Software Development] creeve4:
I'm all setup to build AOKP, can I build TWRP using AOKP source?
[Android Software Development] HowardZ:
I already build unofficial CM10.2 successfully for the Nexus 7 LTE.

When I follow the directions to build TWRP, and I "fastboot boot recovery.img" I find that it is ClockworksMod recovery.

What simple thing am I doing wrong?
[Android Software Development] ktempleton:
That is obviously you not replacing the source recovery folder
[Android Software Development] HowardZ:
OK, I figured out that rather than one line in roomservice.xml, I needed to add two lines:

<remove-project name="CyanogenMod/android_bootable_recovery" />
<project name="TeamWin/Team-Win-Recovery-Project" path="bootable/recovery" remote="github" revision="twrp2.7" />

I needed to do the "remove-project"

However, when the build is done, there is no recovery.img created

I get the following error:

----- Making recovery image ------
/media/UBUNTU/out/system/target/product/deb/recovery.img maxsize=10543104 blocksize=135168 total=10604544 reserve=270336
error: /media/UBUNTU/out/system/target/product/deb/recovery.img too large (10604544 > [10813440 - 270336])
make: *** [/media/UBUNTU/out/system/target/product/deb/recovery.img] Error 1
make: *** Deleting file `/media/UBUNTU/out/system/target/product/deb/recovery.img'
make: *** Waiting for unfinished jobs....
cp: cannot stat `/media/UBUNTU/out/system/target/product/deb/cm-*': No such file or directory
cp: cannot stat `/media/UBUNTU/out/system/target/product/deb/recovery.img': No such file or directory
Reading local directories
Synchronizing folders
Reading remote server file list
Detecting changes from last sync
Synchronizing files
Finished!
[Android Software Development] HowardZ:
OK, I got help in the twrp forum and needed to use a better compression option for the kernel.
[Android Software Development] TimSchumi:
The cm.mk was generated with this name by mkvendor.sh. Does not renaming it make any difference?

EDIT: Is cm.mk being renamed to cm_cs02ve.mk or device.mk to device_cs02ve.mk?
[Android Software Development] ashyx:
Cm.mk
[Android Software Development] ashyx:
Heres what gets it building under 5.1 branch: https://github.com/ashyx/android_device_samsung_cs02ve

Compiled recovery image is in cs02ve folder.

Pull request sent. Its up to you if you want to merge.
[Android Software Development] TimSchumi:
Thanks :thumbsup:

Did you compile with CM 11 sources?
[Android Software Development] ashyx:
No omni, but it should compile under cm too if you have everything right.
[Android Software Development] MSF Jarvis:
Not necessarily Sir, many devices build well under OmniROM but don't boot into TWRP built in a CM tree. No idea why
[Android Software Development] ashyx:
I said compile not boot, but true much better to compile twrp with Omni.
[Android Software Development] MSF Jarvis:
Oh yeah sorry, my bad.
[Android Software Development] TimSchumi:
Thank you so much! It worked!
[Android Software Development] heliusjing:
how to compile twrp recovery for lenovo vibe x3,because I have no device tree
[Android Software Development] MSF Jarvis:
Check out this thread http://xdaforums.com/android/software/twrp-flags-boardconfig-mk-t3333970

The first post has a link to a tool that'll try to create a device tree from scratch, just make sure to leave all support requests in that thread only.
[Android Software Development] heliusjing:
okay ，thank u very much ,BTW which brunch should I use
[Android Software Development] MSF Jarvis:
The script will see to it all, clone it from github.com/MSF-Jarvis/AIO-TWRP-Compiler
[Android Software Development] heliusjing:
hey ,mate,I have compiled a twrp recovery for lenovo vibe x3, but there is a bug that no response to touch screen within five minutes when into twrp recovery,but a few mins later ,everything goes well.I don't know how to figout out it after try it again and again. I think I need ur help,here is my device tree:https://github.com/arpitnnd/android_device_lenovo_x3_row-1/tree/twrp-3,thanks in advance
[Android Software Development] ferhung:
Try this: https://github.com/ferhung-mtk/andr...mmit/62847246ed9d0553c7ec0befaa02cdbbe5085c5f

This fixes some platforms as: mtk6592/6582/6752 and some samsung devices.

PS: Using TW_SCREEN_BLANK_ON_BOOT is not a good idea for twrp. Maybe twrp should make a argument for it.
[Android Software Development] heliusjing:
not black srceen ,just no response when tap screen ,but about 5 mins later ,it works,
[Android Software Development] ferhung:
Make a logcat to post here.
[Android Software Development] heliusjing:
hey ,mate,I have compiled a twrp recovery for lenovo vibe x3, but there is a bug that no response to touch screen within five minutes when into twrp recovery,but a few mins later ,everything goes well.I don't know how to figout out it after try it again and again. I think I need ur help,here is my device tree: https://github.com/arpitnnd/android_device_lenovo_x3_row-1/tree/twrp-3 ,here is the recovery log : https://paste.omnirom.org/view/3b24eba9 。thanks in advance！！！
[Android Software Development] :
How do I decompile a TWRP image which only contains a ramdisk image and no kernel because every tool I try to use to decompile recovery.img it fails,I just need to add stock device kernel to that generic recovery.img
[Android Software Development] NepoRood:
I use the Carliv Image Kitchen to unpack/repack recovery and boot images
[Android Software Development] :
Isn't that only for MTK though? I need to decompile for a Rockchip device
[Android Software Development] NepoRood:
No, it'll most likely work. He has a Windows and Linux version, and I've unpacked for several different devices.
[Android Software Development] :
Oh ok will give it a shot
[Android Software Development] bgcngm:
[MENTION=4878287]_that[/MENTION], is there any way to circumvent this bug on a device that's using a prebuilt kernel (due to unreleased kernel sources)? I'm facing the same issue on Xiaomi Mi5, with some users reporting non-working touch after TWRP initialises.

For the record, I already tried the following TWRP additional build flags without success:

RECOVERY_GRAPHICS_FORCE_SINGLE_BUFFER := true

TW_SCREEN_BLANK_ON_BOOT := true
[Android Software Development] _that:
The workaround for that race condition in graphics_fbdev has been committed for a while. Are you using overlay graphics?

fb0 is for output only, not for input.
[Android Software Development] bgcngm:
It still seems to happen:

Starting TWRP 3.0.2-0 on Mon Aug 22 22:34:07 2016
(pid 423)
BOARD_HAS_NO_REAL_SDCARD := true
RECOVERY_SDCARD_ON_DATA := true
I:Lun file '/sys/module/g_android/parameters/file'
TW_INCLUDE_CRYPTO := true
I:TW_BRIGHTNESS_PATH := /sys/class/leds/lcd-backlight/brightness
I:Found brightness file at '/sys/class/leds/lcd-backlight/brightness'
I:Got max brightness 255 from '/sys/class/leds/lcd-backlight/max_brightness'
I:TWFunc::Set_Brightness: Setting brightness control to 80
I:LANG: en
Starting the UI...open_overlay cannot open fb0: No such file or directory
setting DRM_FORMAT_RGBX8888 and GGL_PIXEL_FORMAT_RGBX_8888
cannot find/open a drm device: No such file or directory
cannot open fb0 (retrying): No such file or directory
cannot open fb0 (retrying): No such file or directory
fb0 reports (possibly inaccurate):
vi.bits_per_pixel = 32
vi.red.offset = 0 .length = 8
vi.green.offset = 8 .length = 8
vi.blue.offset = 16 .length = 8
setting GGL_PIXEL_FORMAT_RGBA_8888
double buffered
framebuffer: 0 (1080 x 1920)
Using fbdev graphics.
TW_SCREEN_BLANK_ON_BOOT := true
I:TWFunc::Set_Brightness: Setting brightness control to 80
I:Loading package: splash (/twres/splash.xml)
I:Load XML directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/splash.xml' directly
I:Checking resolution...
I:Loading resources...
I:Loading variables...
I:Loading mouse cursor...
I:Loading pages...
I:Loading page splash
I:Switching packages (splash)
blacklisting hbtp_vm input device
=> Linking mtab
=> Processing recovery.fstab
...

Sure, I know that. But it seems that some devices have input issues until sleep once and wake up with a key press, judging by this commit.
[Android Software Development] _that:
You can try to port the retry-open loop from graphics_fbdev.cpp to open_overlay() in graphics_overlay.cpp and see if it improves things.
[Android Software Development] bgcngm:
Just tried that. It finds the overlay graphics:

Starting the UI...
open_overlay cannot open fb0 (retrying): No such file or directory
open_overlay cannot open fb0 (retrying): No such file or directory
Overlay graphics may work (mdssfb_90000), but not enabled. Use TW_TARGET_USES_QCOM_BSP := true to enable.
setting DRM_FORMAT_RGBX8888 and GGL_PIXEL_FORMAT_RGBX_8888
cannot find/open a drm device: No such file or directory
fb0 reports (possibly inaccurate):
vi.bits_per_pixel = 32
vi.red.offset = 0 .length = 8
vi.green.offset = 8 .length = 8
vi.blue.offset = 16 .length = 8
setting GGL_PIXEL_FORMAT_RGBA_8888
double buffered
framebuffer: 0 (1080 x 1920)
Using fbdev graphics.

But I can't compile with TW_TARGET_USES_QCOM_BSP.
[Android Software Development] _that:
OK, then this is completely unrelated to the touch issues and the workaround in overlay graphics isn't needed for your device.
[Android Software Development] bgcngm:
Yeah, the workaround is not needed, but I'm not convinced about the touch issue being unrelated. I had a confirmation from two users that touch works right after TWRP boots only if built with TW_SCREEN_BLANK_ON_BOOT set (see related commit). The fact is that initial code pointed out that it fixed screen/touch driver. However, for strange that it may seem, I still have to wait a few seconds for touch to work or eventually let screen go off to turn it back on.

Any ideas how to debug input device?
[Android Software Development] _that:
I've read that on some devices, touch only starts to work after screen blank/unblank, but not that it prevents booting.

You can enable input event logging in TWRP (TWRP_EVENT_LOGGING := true in gui/Android.mk), but I guess this won't help you if already know that events only start after a screen blank/unblank. It seems to be a kernel-side issue. Maybe you can read the kernel code to find out how the touch driver is linked to the screen blank/unblank ioctl.
[Android Software Development] bgcngm:
It doesn't prevent booting, TWRP boots just fine. It just seems that the screen blank/unblank trick only works for certain hardware variants, but not for others (my case). For me, setting TW_SCREEN_BLANK_ON_BOOT or not is the same, as I always have to wait a few seconds after TWRP boots or wait for screen off/on instead.

Right... I could check the kernel sources if Xiaomi had released the code. :p
[Android Software Development] Heemzy:
recovery iasue

Pls help me...my issue is dat d touchscreen is not working on my device. UMI HAMMER S Mtk6735m. Any help...
[Android Software Development] bigsupersquid:
Sure wish there was legal recourse against manufacturers who don't recognize that they're violating the GPL by using the Linux kernel in any product that they don't provide source changes for.

Maybe if we were rich and could afford mega lawyers to match the bought and paid for corporate shills we could force them to release it or shut down their companies (that's right Xiaomi, Polaroid, you and other lame-o companies should pay for all the money you've made off of open source software that you won't share the changes from)

Which, back to slightly on topic, is one of the great things about twrp. Shared public source code, developers willing to help with questions... That's what software should be.

Sorry, personal rant because closed source Linux kernels really irritate me.
[Android Software Development] Hacker432:
Holy words

Inviato dal mio Y550-L01 utilizzando Tapatalk
[Android Software Development] bgcngm:
With TWRP event logging enabled:

Reloading input devices
Event object: synaptics_dsx_stylus
EV: ST minX: 0 maxX: 1079 minY: 0 maxY: 1919
EV: MT minX: 0 maxX: 0 minY: 0 maxY: 0
Event object: synaptics_dsx
EV: ST minX: 0 maxX: 1079 minY: 0 maxY: 1919
EV: MT minX: 0 maxX: 1079 minY: 0 maxY: 1919
Event object: hbtp_vm
blacklisting hbtp_vm input device
EV: ST minX: 0 maxX: 0 minY: 0 maxY: 0
EV: MT minX: 0 maxX: 0 minY: 0 maxY: 0
Event object: qbt1000_key_input
EV: ST minX: 0 maxX: 1000 minY: 0 maxY: 1000
EV: MT minX: 0 maxX: 0 minY: 0 maxY: 0
Event object: qpnp_pon
EV: ST minX: 0 maxX: 0 minY: 0 maxY: 0
EV: MT minX: 0 maxX: 0 minY: 0 maxY: 0
Event object: pwm-ir
EV: ST minX: 0 maxX: 1079 minY: 0 maxY: 1919
EV: MT minX: 0 maxX: 0 minY: 0 maxY: 0
Event object: gpio-keys
EV: ST minX: 0 maxX: 1079 minY: 0 maxY: 1919
EV: MT minX: 0 maxX: 1079 minY: 0 maxY: 1919
EV: synaptics_dsx => type: 3 code: 39 value: 0
EV: synaptics_dsx => EV_ABS ABS_MT_TRACKING_ID 0
EV: synaptics_dsx => type: 1 code: 14a value: 1
E:TOUCH_KEY: 330
E:HardwareKeyboard::KeyDown 330
E:Unmapped keycode: 330
EV: synaptics_dsx => type: 1 code: 145 value: 1
E:TOUCH_KEY: 325
E:HardwareKeyboard::KeyDown 325
E:Unmapped keycode: 325
EV: synaptics_dsx => type: 3 code: 35 value: 542
EV: synaptics_dsx => EV_ABS ABS_MT_POSITION_X 542
EV: synaptics_dsx => type: 3 code: 36 value: 1837
EV: synaptics_dsx => EV_ABS ABS_MT_POSITION_Y 1837
EV: synaptics_dsx => type: 3 code: 30 value: 5
EV: synaptics_dsx => EV_ABS ABS_MT_TOUCH_MAJOR 5
EV: synaptics_dsx => type: 3 code: 31 value: 3
EV: synaptics_dsx => EV_ABS ABS_MT_TOUCH_MINOR 3
EV: synaptics_dsx => type: 0 code: 0 value: 0
EV: synaptics_dsx => EV_SYN SYN_REPORT
EV: p->x=542 x-range=0,1079 fb-width=1080
EV: x: 542 y: 1837
E:TOUCH_START: 542,1837
EV: synaptics_dsx => type: 3 code: 31 value: 4
EV: synaptics_dsx => EV_ABS ABS_MT_TOUCH_MINOR 4
EV: synaptics_dsx => type: 0 code: 0 value: 0
EV: synaptics_dsx => EV_SYN SYN_REPORT
EV: synaptics_dsx => type: 3 code: 31 value: 3
EV: synaptics_dsx => EV_ABS ABS_MT_TOUCH_MINOR 3
EV: synaptics_dsx => type: 0 code: 0 value: 0
EV: synaptics_dsx => EV_SYN SYN_REPORT
EV: synaptics_dsx => type: 3 code: 39 value: -1
using ABS_MT_TRACKING_ID value -1 to indicate touch releases
EV: synaptics_dsx => EV_ABS ABS_MT_TRACKING_ID -1
EV: synaptics_dsx => type: 1 code: 14a value: 0
E:TOUCH_KEY: 330
E:HardwareKeyboard::KeyUp 330
EV: synaptics_dsx => type: 1 code: 145 value: 0
E:TOUCH_KEY: 325
E:HardwareKeyboard::KeyUp 325
EV: synaptics_dsx => type: 0 code: 0 value: 0
EV: synaptics_dsx => EV_SYN SYN_REPORT
E:TOUCH_RELEASE: 542,1837
[Android Software Development] Rotkaeqpchen:
I got the Moto G4 Play (XT1602) and already tried to build TWRP but I'm not experienced enough to successfully do it. So I'd like to ask you if someone of you could please do it. I will donate of course if it works.

I've attached the boot.img, recovery.img and info.txt of my device.

Thanks in advance!
[Android Software Development] DevUt:
Hey guys im k getting an error

source and target don't have same number of chunks!
source chunks:
chunk 0: type 0 start 0 len 3907594
chunk 1: type 2 start 3907594 len 1528832
chunk 2: type 0 start 4742085 len 1083
target chunks:
chunk 0: type 0 start 0 len 6967296
make: *** [build/core/Makefile:1056: /var/lib/jenkins/android/build/cm-13.0/out/target/product/endeavoru/obj/PACKAGING/recovery_patch_intermediates/recovery_from_boot.p] Error 1
make: *** Waiting for unfinished jobs....

Here is my recovery.mk

LZMA_BIN := /usr/bin/lzma

$(INSTALLED_RECOVERYIMAGE_TARGET): $(MKBOOTIMG) \
$(recover_ramdisk) \
$(recovery_kernel)
@echo ----- Compressing recovery ramdisk with lzma ------
rm -f $(recovery_uncompressed_ramdisk).lzma
$(LZMA_BIN) $(recovery_uncompressed_ramdisk)
$(hide) cp $(recovery_uncompressed_ramdisk).lzma $(recover_ramdisk)
@echo ----- Making recovery image ------
$(MKBOOTIMG) $(INTERNAL_RECOVERYIMAGE_ARGS) --output $@
@echo ----- Made recovery image -------- $@
$(hide) $(call assert-max-image-size,$@,$(BOARD_RECOVERYIMAGE_PARTITION_SIZE),raw)

$(INSTALLED_BOOTIMAGE_TARGET): $(MKBOOTIMG) $(INTERNAL_BOOTIMAGE_FILES)
$(call pretty,"Target boot image: $@")
$(hide) $(MKBOOTIMG) $(INTERNAL_BOOTIMAGE_ARGS) --output $@
$(hide) $(call assert-max-image-size,$@,$(BOARD_BOOTIMAGE_PARTITION_SIZE),raw)

and this is the device tree https://github.com/DevUt/android_device_htc_endeavoru/tree/twrp3/

And the problem is only when building rom
[Android Software Development] bigsupersquid:
It's a kernel error.

the error readout offers a solution.

Sometimes using a lower kernel toolchain version avoids errors like that, but it's cooler to fix the errors and keep using the newer toolchain.

However, you're wanting a binary out of the recovery, and it's statically linked to twrp. So if you extract the binary and try to run it in a ROM it probably will crash anyway being unable to link dependent libraries. You can look in the project Android.mk file and see what it's dependent on, maybe move those libs too if they don't conflict with the ROM (weak maybe,) or try to set up a static compilation in that makefile.
[Android Software Development] DevUt:
Just follow this commit https://github.com/DevUt/android_ke...mmit/b55caaf98d8800d68bd9f90f712772be6c2356b2