yashsingh1/xdaforums huggingface dataset:
[Android Software Development] gee one:
Try rerunning just the make command. I think some things get built out of order, so try make recoveryimage again to see if you get past the error.
[Android Software Development] narueon:
Just mean just make insted or mka recoveryimage
[Android Software Development] gee one:
Whatever your just command was. Just repeat it again. There are parts that are building simultaneously, so they might finish a little out of order.
[Android Software Development] narueon:
Thankyou. I did make clean. Now again started the process. I will do make recoveryimage if the process stops again
[Android Software Development] narueon:
I have compiled twrp 3.1.1 successfully. But after flashing recovery it doesn't boot up.

I used prebuilt kernel extracted from boot.img of my device( Asus Zenfone 5 T00F)

Please someone halp me.
[Android Software Development] Ibuprophen:
The statement of "after flashing recovery it doesn't boot up" is really a form of "Generic Statement".

What i mean by a Generic Statement is that more specific information is really needed to get a better/more precise view of what's happened/happening.

For example... I've seen members state that a device is Bootlooping but, it actually is stuck in the boot up process/screen.

I hope i had explained this okay via text... :)

______________

PLEASE NOTE: I welcome any member to help with further valuable information/clarification for any of my posts.

×MY DEVELOPMENTS×

[APP][TOOL][4.2+]The SELinux Toggler

[ZIP][TOOL][AIO]BusyBox Stericson Binary Installer v1.26.2 {BB/TB Auto-Symlink}

×IN DEVELOPMENT×

[APP][TOOL][4.2+][OFFICIAL]The SELinux Switch

Will Supersede "The SELinux Toggler"

×IDEAS FOR DEVELOPMENT×

[APP][UNOFFICIAL][4.2+]XDA Forum {Classic}

[APP][UNOFFICIAL][4.2+]XDA Reader {Classic}
[Android Software Development] narueon:
Yeah I understood what you meant. But there isn't any other way I can tell it. When I try to boot into recovery only my device (Asus) logo is shown and it reboot after few minute. Again tries to boot up but I'm 3rd time goes back to bootloader.

I tried taking log but it just says

<waiting for device>

I have already configured device to get recognised. (Udev rules)
[Android Software Development] messi2050:
This probably a kernel error (panic) if you are sure that your tree is correct..
[Android Software Development] narueon:
Yeah I have posted my kernel device and vendor tree. Can u check it once.?
[Android Software Development] messi2050:
Vendor is not necessary when you are building only a recovery, it will be better if you can create more simple tree for compiling twrp.
[Android Software Development] narueon:
Can you suggest me a guide to do it?
[Android Software Development] NepoRood:
There's a great guide, Here
[Android Software Development] rajit:
trining to build RR for samsung a5 2016

stuck here. any luck
[Android Software Development] NepoRood:
This is a thread for building TWRP, not a ROM (you also posted the same in another thread, see my answer in said thread...)
[Android Software Development] messi2050:
I'm building twrp 3.1.1 using latest branch 7.1 and inside lineage 13 source, I'm using stock prebuilt 6.0 kernel, everything is working great except while installing lineage 14.1 it can't deal with the new [file_contexts.bin] format and i always get this line:

[I:Update binary zip

I:Zip does not contain SELinux file_contexts file in its root.]

And that causes the rom to not boot.. any tips ?
[Android Software Development] narueon:
I have successfully compiled twrp 3.1.1 for my device ( ASUS Zenfone 5 T00J) but even the Recovery boots up I have ghost touch issue ( Random touches automatically). How can I fix this.??
[Android Software Development] messi2050:
Can you post your tree
[Android Software Development] narueon:
TWRP - random touch, scroll bar moving

device name: Asus Zenfone 5 (T00F)

device : https://goo.gl/p62FGk

kernel : https://goo.gl/csLTFi

vendor : https://goo.gl/cLHRw2
[Android Software Development] messi2050:
If you are building using the twrp branch

https://github.com/zenfone-legacy/android_device_asus_T00F/blob/twrp-7.1/BoardConfig.mk#L181

then you will have to check the kernel or use prebuilt one.
[Android Software Development] narueon:
How to Check Kernel

what do you mean by check the kernel? can u guide me through this.

Inline kernel building is already there if that is what you mean

https://github.com/zenfone-legacy/android_device_asus_T00F/blob/twrp-7.1/BoardConfig.mk#L47
[Android Software Development] narueon:
TWRP - random touch, scroll bar moving (SOLVED)

There was issue with my input sensor. Its fixed now and now TWRP works perfectly.
[Android Software Development] NepoRood:
What did you do to fix it? Sharing "fixes" helps everyone :good:
[Android Software Development] Rijugarai99:
Make a twrp recovery for Lava Pixel V2
[Android Software Development] narueon:
Solving Touch Issue (Dancing Touch/Ghost Touch)

Issue :

1. Buttons are pressed automatically without touching them.

2. Automatically Scrolling through option as you move your phone (pages like setting time zone, browsing files to install etc)

Cause: It is caused due to multiple input sources ( touch,accelerometer,etc). This acts as touch input and automatically presses buttons.

Solution:

You should find the device other than "touch input" that is acting as touch input.

1. Build TWRP using the following flag.

TWRP_EVENT_LOGGING := true

2. Take log and then open the recovery.log

3. Find the input device causing issue by looking at events.(there will be multiple events from same device.)

EV: blah blah blah.....

Mine was accelerometer with the following name :

x0akxtj9_accel

4. Add the following TWRP Flag to your device's BoradConfig.mk to Blacklist the device.

TW_INPUT_BLACKLIST := accelerometer

TW_INPUT_BLACKLIST := "accelerometer\device_causing_issue"

mine : TW_INPUT_BLACKLIST := "accelerometer\x0akxtj9_accel"

Reference : This Commit -> https://goo.gl/Etkun4

And finally recompile and flash the recovery.img.

I hope its not too detailed :D

I will add my logs and a gif later.

I was able to identify the problem and solve it using this thread : https://goo.gl/tY12xH

If there are any more doubts just PM me.
[Android Software Development] narueon:
Hello guys,

There isn't any backup "system image" option under Backup. How can I fix it ?

TWRP logo and name is not shown when TWRP boots up. Only a grey screen. My device is a 720p one. How to fix it ?
[Android Software Development] Mr Beardsly:
Well, This is on my list of compiling now.
[Android Software Development] ashyx:
Add it to your fstab.
[Android Software Development] edinzulic:
Does anyone know how to compile a recovery for Acer Z6 Plus, I do not know how to do it all.

My Acer Z6 Plus

Chipset Mediatek MT6753

CPU: Octa core 1,3 GHZ Cortex - A53

ROM: 32GB, RAM: 3 GB

Android version: Marshmallow 6.0 (no update, fabric state)

His original state ROM

Build Number: Acer_AV0M0_T11_1.00.0_EMEA_BHT

Kernel Vesion: 3.18.19+

queen@scmbuild #1

Wed Jun 7 17:10.58 CST 2017
[Android Software Development] Salcykhan:
Spreadtrum

SC9830A

Twrp img for this chipset (tested)

http://www.mrhhacking.com/2017/04/cu...ame-7.html?m=1
[Android Software Development] kaew158:
Need help to create TWRP v3.x for Lenovo A1000 SC8830 Android 5.0 . I flash many files but still stuck on boot logo screen.

Boot & Recovery
[Android Software Development] desalesouche:
https://teamw.in/twrpfaq is not secured :SSL_ERROR_BAD_CERT_DOMAIN
[Android Software Development] nkk71:
https://twrp.me/FAQ/
[Android Software Development] pvineeth97:
Any idea about this error?

https://hastebin.com/unacuyocar.pas

Compiling TWRP on Omni-5.1

Device tree: https://github.com/PVineeth/android_device_lge_mlv5_recovery
[Android Software Development] danerrickcuba@gmail.com:
Can someone plz make a video compiling TWRP? I'm hopelessly lost, being trying this and failing completely.

1.I'm on samsung touch wiz 5.1.1 , no existing cyanogen or lineage kernel, only twrp I have it's 2.8, Dev retired, no custom roms, no modded stock roms, nothing at all.

How should I proceed compiling this? My tab is galaxy tab active.
[Android Software Development] kaew158:
Need help to unpack boot & recovery image. I will try to create my twrp.

Boot & Recovery
[Android Software Development] kessaras:
So why here ?

Use image kitchen
[Android Software Development] desalesouche:
twrp for huawei y550 (msm8916)

hi all, may i request some help about how to fix my touchscreen problem?

touch is not working during about 10 seconds after reboot to twrp recovery. i used that flag : TW_SCREEN_BLANK_ON_BOOT := true but no success.

here is my recovery log: https://hastebin.com/uqufekanac.sql

edit: does twrp node is dead?
[Android Software Development] kaew158:
I am not success to unpack my recovery image.

AIK , APKtools , Carliv Image Kitchen ,and AIK apk

Unsupport image format!

Can you unpack my recovery image and upload?
[Android Software Development] qiurigao:
including ./frameworks/native-caf/services/powermanager/Android.mk ...

including ./frameworks/native-caf/services/sensorservice/Android.mk ...

including ./frameworks/native-caf/services/surfaceflinger/Android.mk ...

including ./frameworks/native/Android.mk ...

build/core/base_rules.mk:157: *** frameworks/native/cmds/dumpstate: MODULE.TARGET.STATIC_LIBRARIES.libdumpstate.default already defined by frameworks/native-caf/cmds/dumpstate. Stop.

#### make failed to build some targets (12 seconds) ####

root@vultr:~/twrp#

help me
[Android Software Development] kirito9:
Start here https://xdaforums.com/android/software/guide-how-to-compile-twrp-source-step-t3404024.
[Android Software Development] desalesouche:
hi, you have twice the same folder. it is said. it means you have to delete native or native-caf folder.
[Android Software Development] katinatez:
https://github.com/xiaolu/mkbootimg_tools
[Android Software Development] pvineeth97:
I am doing the same way you are doing to compile for cortex-a53 using OMNI sources.

Can you look at it thanks? I dont know where is the problem.

I am getting the same error:

Install: /home/vineeth_pen/android/omni_twrp-5.1/out/target/product/mlv5/system/lib64/libstdc++.so
target Strip: libm (/home/vineeth_pen/android/omni_twrp-5.1/out/target/product/mlv5/obj/lib/libm.so)
target SharedLib: libext2_blkid (/home/vineeth_pen/android/omni_twrp-5.1/out/target/product/mlv5/obj/SHARED_LIBRARIES/libext2_blkid_intermediates/LINKED/libext2_blkid.so)
target SharedLib: libext2_profile (/home/vineeth_pen/android/omni_twrp-5.1/out/target/product/mlv5/obj/SHARED_LIBRARIES/libext2_profile_intermediates/LINKED/luct/mlv5/obj/STATIC_LIBRARIES/libc_intermediates/libc.a)
target StaticLib: libc_nomalloc (/home/vineeth_pen/android/omni_twrp-5.1/out/target/product/mlv5/obj/STATIC_LIBRARIES/libc_nomalloc_intermediates/libc_nomalloc.a)
target StaticLib: libc_nomalloc_32 (/home/vineeth_pen/android/omni_twrp-5.1/out/target/product/mlv5/obj_arm/STATIC_LIBRARIES/libc_nomalloc_intermediates/libc_nomalloc.a)
[Android Software Development] ashyx:
What error/issue are you having for which device?
[Android Software Development] desalesouche:
up.
[Android Software Development] pvineeth97:
I solved it. See my commits on the github repo.
[Android Software Development] desalesouche:
solved:touchscreen freeze

following explanation on that post:https://xdaforums.com/showpost.php?p=73410114&postcount=3356

and with some guidance from [MENTION=912474]Dees_Troy[/MENTION] (thanks man!)

i could determinate that in kernel defconfig 2 differents touchscreen were enabled with same reference compat.

i disabled the unneeded one and now twrp deosn't freeze any more at boot.

https://github.com/HUAWEI-Y550-Y635...mmit/a05cc65e5c30051c473f9d3b9bd51d104ae19779
[Android Software Development] Mandeep Hundal:
Greetings,

Its my first post here.

My question is that did someone compile recovery for Micromax Bolt Q326, if not could someone compile it

Tell me please if its possible
[Android Software Development] Captain_Throwback:
This thread is for assistance with compiling TWRP from source, not for requests.

P.S. Almost anything is possible, if you're willing to do the work.
[Android Software Development] kairi_zeroblade:
edit:

got it compiling the only issue is after compilation its spurs me with this errors..of course unless they are normal ones..

__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!

are these issues normal??
[Android Software Development] SuperHanss:
[MENTION=912474]Dees_Troy[/MENTION] how would I go about improving the touch responsiveness in TWRP 2.7 for my device (Xperia Z)?
[Android Software Development] tsynik:
TWRP

Hi, guys. I'm trying to make TWRP 2.7 for my device (UBIFS + flipped screen). Strange thing is: I've successfully build TWRP 2.4.1.0 (with ubifs addons) from source and it works fine on my device (except it won't format UBI volumes). 2.4.1.0 was setup in CM10.1 tree. Now I'm trying to make 2.7 with UBUFS too. Changed repo config to 2.7 (with UBI) and done clean build. Nothing changed in my device files, TWRP 2.7 built fine (no errors), but it won't boot. I'm stuck on logo (no adb). Is there something I miss for move from 2.4.1.0 to 2.7?

Here is my device files. Works fine with TWRP 2.4.1.0 (+UBI). Won't boot on 2.7.
[Android Software Development] desalesouche:
F2FS

[MENTION=912474]Dees_Troy[/MENTION]

hi sir i manage to compile twrp 2.7.0.0 for my device.

and it is working fine.

but i would like to add F2Fs option , for the moment it only show ext3 and ext4.

how can i do?

thank you.
[Android Software Development] surdu_petru:
TWRP on a new device !

Hello !

I managed to bring TWRP 2.7.0.0 for a new device : Huawei Ascend P6 !

My build is almost fully functionally, apart two issues : No LED activity while connected to USB/Power Charger & Internal Storage cannot be mount !

Because I want to make it officialy , I want to know : where should I send these requests to verification, or what should I do , in order to be available also official !

Thank you very much for your advice !

Edit:

Working well on custom rom's based AOSP and also on custom rom's based stock Huawei Firmware !

regards,

Surdu Petru
[Android Software Development] gimmeitorilltell:
You will get more help by going to the twrp chat listed in the op. Dees_Troy has several threads and its hard for anyone to keep up with so many. I went there for help and got it. You might have to message someone there and leave the page open for a response.
[Android Software Development] MasterAwesome:
I tried compiling twrp 2.7 for my device Moto G(falcon) after it compiled the dt.img it gave me an error

system/core/charger/charger.c:1309: error: undefined reference to 'res_create_display_surface'
system/core/charger/charger.c:1318: error: undefined reference to 'res_create_display_surface'
collect2: error: ld returned 1 exit status
make: *** [/home/naz/cm11/out/target/product/falcon/obj/EXECUTABLES/charger_intermediates/LINKED/charger] Error 1
make: *** Waiting for unfinished jobs....

other recoveries build properly except for this one. What might be the mistake im doing?
[Android Software Development] Polloos:
I have the same error. I have been told that reverses this commit:

https://github.com/CyanogenMod/android_system_core/commit/89b9236061f98eb33d58345a691d3db6e032aaca
[Android Software Development] vetzki:
hello,

i get this strange error (builds for grouper and mako are without problem):

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.4.2
TARGET_PRODUCT=full
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a
TARGET_CPU_VARIANT=generic
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.13.10-1-MANJARO-x86_64-with-glibc2.2.5
HOST_BUILD_TYPE=release
BUILD_ID=KVT49L
OUT_DIR=out
============================================
including ./abi/cpp/Android.mk ...
including ./art/Android.mk ...
including ./bionic/Android.mk ...
including ./bootable/diskinstaller/Android.mk ...
including ./bootable/recovery/Android.mk ...
bootable/recovery/gui/Android.mk:68: ********************************************************************************
bootable/recovery/gui/Android.mk:69: * DEVICE_RESOLUTION is NOT SET in BoardConfig.mk
bootable/recovery/gui/Android.mk:70: * Please see http://tinyw.in/nP7d for details
bootable/recovery/gui/Android.mk:71: ********************************************************************************
bootable/recovery/gui/Android.mk:72: *** stopping. Schluss.
(venv)[mv@mv-Aspire-5755G ~/Dokumente/Projekt/AOSP-4.4/Projekt]$ cat device/asus/tilapia/BoardConfig.mk |grep DEVICE_RESO
DEVICE_RESOLUTION := 720x1280

I hope someone has a helpful hint for me, because I set a device_resolution in boardconfig.mk.
[Android Software Development] MasterAwesome:
you have to lunch your device... just typing make recoveryimage will try to build a generic source recovery which will fetch its device source code from GitHub. First, at the root of source directort once you replaced bootable/recovery with one of twrp

source build/envsetup.sh
lunch
#Select your device here usually its like cm_$devicename-eng
#if youre building the whole rom cm_$devicename-userdebug
make -j# recoveryimage

#= no of processors+1

if it still gives similar errors add this to BoardConfig.mk

TARGET_SCREEN_HEIGHT := 1280
DEVICE_RESOLUTION := 720x1280
TARGET_SCREEN_WIDTH := 720

Good luck:cool:
[Android Software Development] vetzki:
Thanks, I already "lunched" the device, but I'll try with target_screen_height & widht (current I set only the device_resolution). Strangely, recovery works for mako and grouper but not for tilapia.

sorry for my bad english
[Android Software Development] MasterAwesome:
Thanks, it works :)

Sent from Moto G using CyanogenMod 11
[Android Software Development] Alonso1398:
Hello, I'm really happy that I managed to build TWRP, because my device and similar don't have support of anything (mine is galaxy music) I haven't been able to test all features but it boots perfectly and the touch is working perfectly too. Looking into a log, my recovery didn't have SElinux support and I really didn't understood how to have SElinux support. Where is the recovery's kernel and how do I edit it to have SELinux support? Also, I'm using CM11 source.

This is my boardconfig.mk . Also, does the "TWHAVE_SELINUX := true" really works? Beside that, I'm really really happy:laugh: thanks for this guide.

USE_CAMERA_STUB := true

# inherit from the proprietary version
-include vendor/samsung/ivoryss/BoardConfigVendor.mk

TARGET_ARCH := arm
TARGET_NO_BOOTLOADER := true
TARGET_BOARD_PLATFORM := bcm21654
TARGET_CPU_ABI := armeabi-v7a
TARGET_CPU_ABI2 := armeabi
TARGET_ARCH_VARIANT := armv7-a
TARGET_CPU_VARIANT := cortex-a9
ARCH_ARM_HAVE_TLS_REGISTER := true

TARGET_BOOTLOADER_BOARD_NAME := ivoryss

BOARD_KERNEL_CMDLINE :=
BOARD_KERNEL_BASE := 0x82000000
BOARD_KERNEL_PAGESIZE := 4096

# fix this up by examining /proc/mtd on a running device
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x00800000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00800000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x38000000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x8547BC00
BOARD_FLASH_BLOCK_SIZE := 131072

TARGET_PREBUILT_KERNEL := device/samsung/ivoryss/kernel

BOARD_HAS_NO_SELECT_BUTTON := true
TARGET_RECOVERY_INITRC := device/samsung/ivoryss/recovery/init.rc
TARGET_RECOVERY_PIXEL_FORMAT := "BGRA_8888"

#twrp
DEVICE_RESOLUTION := 240x240
RECOVERY_SDCARD_ON_DATA := true
BOARD_HAS_NO_REAL_SDCARD := true
TWHAVE_SELINUX := true

TW_INTERNAL_STORAGE_PATH := "/data/media"
TW_INTERNAL_STORAGE_MOUNT_POINT := "data"
TW_EXTERNAL_STORAGE_PATH := "/sdcard"
TW_EXTERNAL_STORAGE_MOUNT_POINT := "sdcard"

TW_CUSTOM_POWER_BUTTON := 107
TW_INCLUDE_INJECTTWRP := true
TWRP_EVENT_LOGGING := true

PRODUCT_COPY_FILES += device/samsung/ivoryss/twrp.fstab:recovery/root/etc/twrp.fstab
[Android Software Development] justlovejoy:
Sorry to waste a post mods.

Awesome That's awesome advice and just from reading incredibly useful knowledge for who it was intended for. Great job!
[Android Software Development] gimmeitorilltell:
The kernel you use to compile is what needs to support selinux.
[Android Software Development] gimmeitorilltell:
I'm not the smartest at this so don't quote me but if you're using the Samsung kernel, it very well may be for a sense Rom. Therefore it will not work for what you are trying to accomplish. You need an aosp kernel with selinux support. I may be wrong but that's where I would start if I were you.
[Android Software Development] MasterAwesome:
Why, Thank you!
[Android Software Development] Alonso1398:
Sorry for that, already solved my problem, the source worked, and for fixing the error just had to make a small change to a file. Man I'm so happy the recovery now says that it has Full SELinux support:laugh:
[Android Software Development] vetzki:
thx, worked (without screen_height & screen_width). As you already mentioned I lunched no device (it seems i was very confused that day. I had bet that I lunched tilapia but after looking again in the output above I saw that theres no product :silly: ).

Again, thx for the hint.

sorry for bad english
[Android Software Development] Mandeep Hundal:
Then please suggest me any site that gives info from very basic to advance.

Because I'm new to these kind of things

Therefore assistance is needed to move forward.

That would be great help.
[Android Software Development] NepoRood:
Go checkout this great Guide
[Android Software Development] Mandeep Hundal:
Although it's useful but it doesn't clear what hardware requirement needed also what processor and how much internal memory as well as how much ram is needed to make process faster without any lag.

Moreover, The files have to download how much internet data I need. So I could do these small things before beginning.

That would be great help.
[Android Software Development] gee one:
Just do it, you'll figure it out as you go. ;)

The full tree for lineage is about 25gb-30gb of drive space for one device. The minimal builds for TWRP should be significantly smaller, but they could still be double digit gbs.

The recovery takes 10-15 mins to compile, but I am using ccache on an i7-2600k with plenty of ram. The full build for a rom takes about 45-50 mins. Your mileage will vary depending on computer specs. Again, just start it. The first sync is the longest.
[Android Software Development] ZawZaw:
Hi...Sirs,

I want to know this:

How many filesize of Omni full Source?

I means that https://github.com/omnirom/android

Thank You.

•••
[Android Software Development] Mandeep Hundal:
Can these resources be downloaded through mobile or only through Cmd in computer.

As I've explored site with resources but there's no download option. Only it does open the files.

As I want to compile recovery for Micromax Q326 ver 5.1.

So do I have to download branch tree of 5.1.

But there's confusion about omni and lineage.

Also, give me suggestion what computer or laptop will be better.
[Android Software Development] TheMeddlingMonk:
You will need to use a computer, not a mobile phone, to download them. As it says in the guide, a Linux OS is required. The repositories are in github, so you will use git to checkout a copy of the branch(es) you need.

The OmniROM version (in this case 5.1) is referring to the OS version (Android 5.1). It has no relationship to the version number of your device.

A desktop will usually be better than a laptop, simply because they typically have more processor power and RAM. That said, you can successfully run this on an older PC. Celerons or Intel Atoms will be much slower, but they should be able to compile it for you. I get away with it (albeit slowly) on an old machine with 2GB of RAM; realistically, more would be better, but it is possible. What are your machine specs? They will likely be more than adequate.