yashsingh1/xdaforums huggingface dataset:
[Android Software Development] mukulsoni:
Plesae help

Someone please help, getting this error while compiling

Export includes file: bionic/libc/Android.mk -- /home/mukul/Android/TWRP/out/target/product/j7elte/obj/STATIC_LIBRARIES/libc_stack_protector_intermediates/export_includes
Export includes file: bionic/libc/Android.mk -- /home/mukul/Android/TWRP/out/target/product/j7elte/obj/STATIC_LIBRARIES/libc_syscalls_intermediates/export_includes
make: *** No rule to make target '/home/mukul/Android/TWRP/out/target/product/j7elte/obj/STATIC_LIBRARIES/libjemalloc_intermediates/export_includes', needed by '/home/mukul/Android/TWRP/out/target/product/j7elte/obj/STATIC_LIBRARIES/libc_common_intermediates/import_includes'. Stop.
make: *** Waiting for unfinished jobs....
[Android Software Development] boa19861105:
I try to compile the core but my compiler does not know is not correct

/home/boa/android/kernel/toolchains/aarch64-linux-android-4.9/bin/../libexec/gcc/aarch64-linux-android/4.9.x-sabermod/cc1: error while loading shared libraries: libisl.so.15: cannot open shared object file: No such file or directory

make[2]: *** [scripts/mod/empty.o] Error 1

make[1]: *** [scripts/mod] Error 2

make[1]: *** Waiting for unfinished jobs....

make: *** [scripts] Error 2

make: *** Waiting for unfinished jobs....

/home/boa/android/kernel/toolchains/aarch64-linux-android-4.9/bin/../libexec/gcc/aarch64-linux-android/4.9.x-sabermod/cc1: error while loading shared libraries: libisl.so.15: cannot open shared object file: No such file or directory

/home/boa/android/kernel/toolchains/aarch64-linux-android-4.9/bin/../libexec/gcc/aarch64-linux-android/4.9.x-sabermod/cc1: error while loading shared libraries: libisl.so.15: cannot open shared object file: No such file or directory

/home/boa/android/kernel/toolchains/aarch64-linux-android-4.9/bin/../libexec/gcc/aarch64-linux-android/4.9.x-sabermod/cc1: error while loading shared libraries: libisl.so.15: cannot open shared object file: No such file or directory

/home/boa/android/kernel/toolchains/aarch64-linux-android-4.9/bin/../libexec/gcc/aarch64-linux-android/4.9.x-sabermod/cc1: error while loading shared libraries: libisl.so.15: cannot open shared object file: No such file or directory
[Android Software Development] _that:
Check your toolchain installation - this is not related to TWRP.
[Android Software Development] shouhu1993:
can someone help?

i am trying to compile twrp for nubia z9mini. now i compileed successfully. but after i flash recovery.img it can't reboot to twrp. when i select reboot to recovery mod it always reboot to fastboot mod.

this is my device that extract from boot.img in stock rom.

this is my device https://github.com/shouhu1993/nx511j_device
[Android Software Development] 西村大一:
Why don't you send 'adb reboot recovery' via adb or open terminal emulator and type 'reboot recovery' after typing 'su' to grant superuser permission to terminal emulator?
[Android Software Development] shouhu1993:
i tried it,but the same result. In bootloader it saied that "no kernel (boot partition is bad)". and the android system boot normally.
[Android Software Development] 西村大一:
Maybe you didn't compile it properly, or other issues. I personally don't know how to work with ZTE devices, so unfortunately you're out of luck. Or probably the recovery needs to be integrated in the kernel. Dunno but the message seems to suggest so.
[Android Software Development] shouhu1993:
sorry, the messege is "no kernel(boot partiton is bad)". i think there must be some files wrong. i would try another way to solve it. thank you for your reply.
[Android Software Development] Lussardi:
I need TWRP to HTC 626s how to compile?
[Android Software Development] :
. build/envsetup.sh

lunch

*choose your device*

mka recoveryimage
[Android Software Development] rexdrive:
So, I need to compile TWRP for a completely unsupported device. Previously I compiled TWRP for my Xperia M whose device tree was available, but this device doesn't have any. So, please could someone tell me as to how to start building a tree. I have already created the .mk files but I don't know what to do after that, i.e., I see in other device trees that there are folders such as bluetooth, overlay, etc. How do I make one for mine? Thank you.
[Android Software Development] chrisrotolo:
just trying to help, I had similar errors recently on ubuntu 12.10, I had to install openjdk and make it default -java, as well as link it in -java -alternatives
[Android Software Development] Dees_Troy:
What make command are you using? The cryptsettings binary isn't normally compiled as part of TWRP.
[Android Software Development] hell_lock:
I was using 'brunch device'. Anyways, I have given up on the project. This is not compatible with cm7. There were more incompatibility issues in the source.
[Android Software Development] #define:
Were you compiling full rom just for recovery??

Sent from my Nexus 7
[Android Software Development] hell_lock:
yep.. cuz make recovery doesnt work for my phone
[Android Software Development] #define:
You have to use make bootimage for yours..

Samsung galaxy y right??

Sent from my Nexus 7

---------- Post added at 08:02 PM ---------- Previous post was at 08:01 PM ----------

And i'm assuming you followed the cm7 instructions instead of the regular ones....

Sent from my Nexus 7
[Android Software Development] Dees_Troy:
That's funny because I built 20 builds of TWRP last night in CM7 as part of the 2.4.2.0 update we're rolling out today and every one of them built just fine. Do like the others said and make bootimage (this is documented in the guide). TWRP itself will build fine in CM7 but the updater binary code may not because the updater code is intended for Android 4.1 instead of 2.3.
[Android Software Development] lambstone:
@Troy, How do you reckon will I be able to build a working TWRP for my unsupported device if the sources aren't available for my device. I would not have the MKBoard files and such available on the cm9/10 repo

Also, do you know how to set custom "button combination for entering recovery"
[Android Software Development] Dees_Troy:
Then you have to make some device files. It's usually easiest to base your files off of files that you find for a similar device. E.g. if your device is a tegra 3 find another device that has TWRP that is a Tegra 3 from our github then modify by updating the recovery.fstab, kernel, and device names, etc.
[Android Software Development] apascual89:
Hi Dees, first of all great work! Is the Sony Xperia z on the radar for you guys? If not I might try to get it working next week when I get mine.
[Android Software Development] Dees_Troy:
Yes, I'm sure we'll be trying to get TWRP onto the Xperia Z once people start getting their hands on models that can be unlocked.
[Android Software Development] #define:
@Dees_Troy...

Hey.. You didnt reply to my PM about official support for HTC Explorer... (After the test image)

Please do so at your earliest convenience..

We're really excited to have our device up there...:D

Sent from my Nexus 7
[Android Software Development] apascual89:
Is there anything I can do to help when I get it?
[Android Software Development] Dees_Troy:
I haven't meant to ignore. I've been very busy with releasing the last 2 versions. Sorry. It might work better if you can stop by the IRC channel so that we can troubleshoot the build together in a more real-time environment.

Feel free to stop by the IRC channel when you get your hands on it. We'll see what we can do.
[Android Software Development] #define:
Sure.... Tell me the time and i'll be there...

Sent from my Nexus 7
[Android Software Development] Dees_Troy:
I'll be in IRC for roughly another hour. After that I have no idea when or how long I'd be around until Monday at around 7:30AM Central time.
[Android Software Development] chinajjb:
I have followed the instrument to add some necessary parameters in boardconfig.mk,

TW_INTERNAL_STORAGE_PATH := "/data/media"

TW_INTERNAL_STORAGE_MOUNT_POINT := "data"

TW_EXTERNAL_STORAGE_PATH := "/storage/sdcard1"

TW_EXTERNAL_STORAGE_MOUNT_POINT := "sdcard"

TWRP_EVENT_LOGGING := true

BOARD_HAS_FLIPPED_SCREEN := true

but I got stunk on entering recovery mode,only got a black screen,but I can sure that the twrp booted,because when I used "adb devices",it prompted "0123456789ABCDEF" alike message,I couldn't get the recovery.log under /tmp.I tested it more than ten times to solve this problem,but got the same black screen!

so I used another way to let twrp work ,after modified nexus 7 twrp recovery,now I can enter twrp recovery on my tablet,but my device is similar with nexus7 ,not same ,so my screen is upside down,and I can not touch the menu correctly.and there's a funny thing that there are two same ui on the screen ,one is top ,and another is bottom(when press the power button and short press it again ,there are two unlock bars on the screen ,one is in the middle ,another one is on the bottom)

is there any way to solve it?(simply replace some files to solve this problem),or compiling is the only way to fix this upside down problem,if it is ,what compiled files is related with upside down feature?

any reply and suggestion will be appreciated!!

best regards!!!

by the way ,how to compile the touch cwm recovery with using " BOARD_HAS_FLIPPED_SCREEN := true",I only can compile key version cwm recovery on my computer,is there any guide to do it?

thanks a lot!
[Android Software Development] Ganesh A:
Can you add a guide for PORTING TWRP from similar devices..[device partitions]
[Android Software Development] adri_360:
Hi,

I don't understand very well this tutorial. When i download the cm10 source for my Optimus don't have any booteable folder. And don't have this line un BoardConfig.mk

Enviado desde TheDarkRoom
[Android Software Development] chinajjb:
The bootable directory lies on the directory you spicifed running "repo init ..............",you should be able to find it if you synced source completely! if not ,"repo sync" again!

"And don't have this line un BoardConfig.mk",what dose it mean?
[Android Software Development] Android-Andi:
Maybe you need a custom recovery-graphics.c.

Here's how we solved the black screen on Samsung Golden (S3 mini). Made changes are ifdefed for reference and didn't removed unused code parts. Maybe you need something similar.

https://github.com/andi34/android_d...mmit/531ac38b54f135a2503a403bc17324351a0865ce
[Android Software Development] vel_tins:
They are not needed for TWRP.

Also look for a device with an identical/similar SoC
[Android Software Development] rexdrive:
Oh k!
[Android Software Development] shouhu1993:
hi man,did you fix this error? i face it too.
[Android Software Development] hackvcs:
I am having this issue with my build for the HTC Desire 626s with touch not working on the recovery partition it works on the boot partition. HTC hasn't published the Kernel source for this phone yet is there anyway around this.
[Android Software Development] _that:
Ask them to stop violating the GPL and publish the kernel source.
[Android Software Development] hackvcs:
Will do lol
[Android Software Development] boa19861105:
How the kernel source code disables digital converter turn it on

My Butterfly 3 devices HTC has released the kernel source code

I helped Butterfly 3 compiled TWRP, but he could not operate under TWRP touch
[Android Software Development] juancollado2003:
Hello people, I want to make a TWRP for the galaxy J1LTE which has the same cpu of xcover3ltexx, but Im noob in compiling, any book or guide for start will be helpfull, anyone please?
[Android Software Development] ashyx:
Your posting in a thread about how to compile TWRP, but asking how to compile TWRP?:what:
[Android Software Development] :
True but this guide is relatively bland in details. Gives very little info with regards to compiling such as it doesn't explain the placement for device trees, kernel source, vendor blobs (if applicable) and so on. Doesn't even explain the environment setup needed to get the jobs done. This guide is mostly based on the presumption that the reader already has these basic skills and knowledge and can piece together the rest.
[Android Software Development] _that:
There are other guides how to set up an Android build environment. CM has a good one in their Wiki, Omni has another one.
[Android Software Development] :
Yea, I know about them already. I believe Omni is slightly outdated right now if I recall. Could be wrong on that so don't quote me on it lol.
[Android Software Development] juancollado2003:
I said I'm noob and this thread is for advance, but I already get my answer, let's check omni
[Android Software Development] :
http://docs.omnirom.org/Setting_Up_A_Compile_Environment
[Android Software Development] ashyx:
Well I agree with that as it does seem like you've started reading a book half way through if you're a noob.

But noobs should be learning other stuff before diving in.

So I guess it forces them to do a bit of research first, which is a good thing.

Tbh I wish they would update it because there's loads of things like flags missing and what they do.
[Android Software Development] :
Couldn't agree more but I would suspect that to be a hassle. Maybe if other team members had access to the thread it would genuinely ease up on the maintenance? Either way, I typically go to the source and review it there for more detailed understanding on these flags so I know what's needed for my device and what isn't as well as knowing the purpose behind any given flag I may consider using.
[Android Software Development] vampirefo:
This would help, I have compiled several twrp's for several different device, the flags weren't too important until I compiled twrp for my latest device BLU ENERGY X PLUS E030U, then the flags paid an extremely important part.

I was getting errors I haven't had seen before, I compiled twrp the same way as I have for other mtk devices, yet twrp was throwing weird errors. the flags fixed everything.

took time to look up the flags and such, but recovery for BLU ENERGY X PLUS E030U is working great.
[Android Software Development] Dukenukemx:
Got a phone called MHORSE with root and trying to install recovery but when the installer is done the phone just reboots back into KitKat. It has the MTK6582 chip in it. With "adb reboot recovery" I hear the phone disconnect from the PC a few times and then it boots normal.
[Android Software Development] :
Wrong thread. Need to ask in your device forum about this problem.
[Android Software Development] cognitive:
I want to build TWRP with android 5.0.2 bootloader. I build from CM12.1 source code. But I dont know which branch I should git and repo from github.com: android-6.0 (twrp 2.8.7.0), android-5.0 (twrp 2.8.5.0)?
[Android Software Development] _that:
Use android-6.0 for TWRP. If that causes build problems (we're still not fully done with restoring compatibility with all Android trees), try android-5.1.
[Android Software Development] cognitive:
Thanks sir
[Android Software Development] blastagator:
Trying to update device repos to Android-M. Getting a build error about healthd and /minui/minui.h being missing. I am assuming this is because you guys aren't done with the M update, but thought I'd check. Want to mess with my build setup more if it is supposed to be working.

I'm using cm-13.0, removing /bootable/recovery and syncing twrp into /bootable/recovery-twrp

Thanks :)

edit: Exact error:

target thumb C++: healthd <= system/core/healthd/healthd.cpp
target thumb C++: healthd <= system/core/healthd/healthd_mode_android.cpp
target thumb C++: healthd <= system/core/healthd/healthd_mode_charger.cpp
target thumb C++: healthd <= system/core/healthd/BatteryMonitor.cpp
system/core/healthd/healthd_mode_charger.cpp:47:25: fatal error: minui/minui.h: No such file or directory
#include "minui/minui.h"
^
compilation terminated.
build/core/binary.mk:706: recipe for target '/home/greg/android/twrp/cm130/out/target/product/d800/obj/EXECUTABLES/healthd_intermediates/healthd_mode_charger.o' failed
make: *** [/home/greg/android/twrp/cm130/out/target/product/d800/obj/EXECUTABLES/healthd_intermediates/healthd_mode_charger.o] Error 1
make: *** Waiting for unfinished jobs....
target thumb C++: healthd <= system/core/healthd/BatteryPropertiesRegistrar.cpp
target StaticLib: libbatteryservice (/home/greg/android/twrp/cm130/out/target/product/d800/obj/STATIC_LIBRARIES/libbatteryservice_intermediates/libbatteryservice.a)

#### make failed to build some targets (03:44 (mm:ss)) ####
[Android Software Development] sub77:
if your target provides a own healthd you have to convert it to c++

Gesendet von meinem falcon mit Tapatalk
[Android Software Development] blastagator:
Added exact error to my post - looks like it is trying to build the standard one.

Although, I edited my build script previously to include

LANG=C

to get past a different build error. Tinkering some more now.

edit: I changed to LANG=CPP, but still got the same healthd error.
[Android Software Development] _that:
You shouldn't remove bootable/recovery, or modify system/core/healthd/Android.mk to use recovery-twrp as include path instead:

LOCAL_C_INCLUDES := bootable/recovery
[Android Software Development] blastagator:
That was originally my though, however, that causes this to happen:

Checking build tools versions...
build/core/base_rules.mk:157: *** bootable/recovery: MODULE.TARGET.EXECUTABLES.recovery already defined by bootable/recovery-twrp. Stop.

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

Which is why I removed that folder in the first place.

edit: Nevermind. Thanks for tip about adding the include line :)

edit2: Double nevermind, hit the same error. Ergh?! Will tinker a little more.

Fixed:

https://github.com/blastagator/cm_d...mmit/21e1466c8d601ed6e7d97b0d960d9cf5f6f1fd7c

https://github.com/blastagator/android_bootable_recovery-dummy

Probably not ideal, but it works.
[Android Software Development] desalesouche:
Hi, after applying your fix, i have following error:

bootable/recovery-twrp/minuitwrp/../../../device/huawei/cherry/twrp/graphics.c:39:24: fatal error: font_10x18.h: No such file or directory

#include "font_10x18.h"

any clue sir? thanks.:)
[Android Software Development] blastagator:
Looks like your phone may have a custom graphics.c I believe this is mentioned somewhere in this thread for how to handle that.
[Android Software Development] ashyx:
Could anyone sensibly answer this question, is it possible to build cwm recovery using omni sources and cwm recovery sources?

Also one for teamwin, it seems omni still doesn't fully support cortex-a53, when I use this cpu flag to build twrp it always fails with an error. It seems there is a missing shared library libc.so that isn't created during the build.
[Android Software Development] xathras:
I'm in the earliest stage in the (mis)adventure of compiling a TWRP recovery for my phone, which is an Allview X2 Xtreme (in Europe), a rebranded Gionee Elife E8. The phone is also available in the US as the Blu Pure XL 2015. It's a Mediatek X10 Helio (mt6795) device.

As the first post recommended Omnirom source I found this link (http://docs.omnirom.org/Setting_Up_A_Compile_Environment). It's a liitle out of date, in particular in recommending Java 6. Eventually I had to scrub everything and start again.

My next stop was this page (https://source.android.com/source/initializing.html). I did a clean install of Ubuntu 14.04 on an old laptop and installed Java 8. Later on I got a message saying that I had attempted a Java 7 action but that I had Java 8 installed. Back to the drawing board again.

On my third attempt I looked for a way of minimising the size of the source download and found this useful page (https://github.com/marduk191/recovery_manifest/tree/android-5.1). I now appear to have a working build environment - I can now lunch without it falling over.

So my advice (for what it's worth) is to read these 3 pages together and make some sensible decisions.

I installed Ubuntu 14.04, together with these libraries:-

sudo apt-get install bison g++-multilib git gperf libxml2-utils make python-networkx zlib1g-dev:i386 zip

Then I installed Java 7 like this:-

sudo apt-get install python-software-properties

sudo add-apt-repository ppa:webupd8team/java

sudo apt-get update

sudo apt-get install oracle-java7-installer

And added the repository like this:-

repo init -u https://github.com/marduk191/recovery_manifest.git -b android-5.1

If there are any other beginners like me out there, I hope this help you.
[Android Software Development] :
[MENTION=4899305]ashyx[/MENTION], I am under the impression that cwm is closed source, correct?
[Android Software Development] _that:
This is the "How to compile TWRP" thread. Nobody here cares about CWM. :)
[Android Software Development] :
Haha, valid point :cool:
[Android Software Development] xathras:
My MediaTek X10 Helio (mt6795) SoC is also cortex-a53 based. I found this page (https://drive.google.com/file/d/0B9O9_6wNQG3DbnZtT0p4d0FMQ2M/view) while looking for recovery info for my phone. The Xiaomi Redmi Note 2 and the HTC M9+ are also X10 Helio based. The HTC BoardConfig.mk entries for the platform look like this:-

TARGET_ARCH := arm64

TARGET_NO_BOOTLOADER := true

TARGET_BOARD_PLATFORM := mt6795

TARGET_CPU_ABI := arm64-v8a

TARGET_CPU_ABI2 := armeabi-v7a

TARGET_ARCH_VARIANT := armv8-a

TARGET_CPU_VARIANT := generic

TARGET_2ND_ARCH := arm

TARGET_2ND_ARCH_VARIANT := armv7-a-neon

TARGET_2ND_CPU_ABI := armeabi-v7a

TARGET_2ND_CPU_ABI2 := armeabi

TARGET_2ND_CPU_VARIANT := cortex-a53

TARGET_CPU_SMP := true

ARCH_ARM_HAVE_TLS_REGISTER := true
[Android Software Development] ashyx:
Neither do I, but seeing as twrp uses omni sources and I don't want to download a crap load of cyanoGenmod source code just to build cwm because twrp has a non responsive touch screen in the particular device I compiled it for.

---------- Post added at 10:25 PM ---------- Previous post was at 10:24 PM ----------

I was talking about the bootable recovery sources.

---------- Post added at 10:27 PM ---------- Previous post was at 10:25 PM ----------

Thats basically how I handled it. It compiles and boots fine, but it niggles me that it's just a work around.
[Android Software Development] blastagator:
I have looked, and looked - what does the flag TW_OEM_BUILD do??? I have found reference to it in the code and online but can't figure out what the heck it is for. How would TWRP be OEM? :confused:

I looked through some of the code - my guess is to replace stock recovery where the only function is what stock reco would do? e.g. factory reset, or obeying commands when an app restarts the phone directing recovery to do something.
[Android Software Development] _that:
As you already found out, that flag builds a limited version of TWRP that could be used by some OEM as a stock recovery.
[Android Software Development] desalesouche:
replace libc folder in omni with the one from cm?
[Android Software Development] _that:
Since I wrote that post I've learned how to use the gdbserver that's included in the prebuilt binaries (and gdb on the PC) to debug TWRP. However my latest attempt in debugging resulted in the host side gdb to segfault, and I have no static gdb binary for x86.

I'll try this again in the next few days and will keep you informed when I find out more.
[Android Software Development] magdeoz:
hello I need help, a friend trying to compile TWRP but the size is a little bigger than the device supports some form of compressing a little more recovery image?

size generated recovery is 10.5 mb

and supporting the device is maximum 9.8MB

any help
[Android Software Development] _that:
Use LZMA or XZ compression on the kernel and/or the ramdisk.
[Android Software Development] xathras:
Does anyone know if there is a comprehensive list of TWRP flags anywhere? If there is I can't find it.
[Android Software Development] _that:
Read the Android.mk in bootable/recovery (and subdirectories). It doesn't get more comprehensive than that. :)
[Android Software Development] xathras:
So if I asked you for a list of all known English words, your advice would be to read everything ever written in the English language. My question was: "Is there an English dictionary".