yashsingh1/xdaforums huggingface dataset:
[Android Software Development] vampirefo:
Could be several things, for mist of my recoveries twrp packed them using standard packing, which only works on one of my devices, all others require special packing.

Unpack your stock recovery, then unpack your twrp recovery, are they packed exactly the same?
[Android Software Development] sdeft:
I couldn't tell as the kernel was prebuilt in the TWRP device tree for my phone.

I am stuck now...Have to wait for the repo sync to finish as made an error and whole repo was deleted as I tried to initiate the twrp-5.1 branch.

So now I am syncing the below repo branch (will be ready in the morning I guess:))

repo init -u git://github.com/lj50036/platform_manifest_twrp_omni.git -b twrp-5.1

---------- Post added at 01:04 AM ---------- Previous post was at 01:01 AM ----------

Haven't touched the original recovery. I compared with the official TWRP one for my device and yes they seem to be packed the same.
[Android Software Development] NepoRood:
[MENTION=1364858]sdeft[/MENTION]

TWRP doesn't require kernel source, using prebuilt is fine. Personally, I use CM11, it works best for me, build it, flash it, boot it. Since going to that branch, I haven't had any problems with "proper packing" of a recovery image.

PS, in the future, if you want to "change things up", just remove your manifest (folder and default.xml shortcut, local manifest/roomservice.xml are keepers), then do a repo init :good:
[Android Software Development] Aadi:
To my luck fastboot opened up without bricking and so I did flash it by fastboot but still it redirects to my old recovery :(
[Android Software Development] Aadi:
Try to get another theme from themers and copy it to the gui folder i did like that mine has a resolution of 240x320 :D

---------- Post added at 10:53 AM ---------- Previous post was at 10:52 AM ----------

Never mind i got it to work.
[Android Software Development] vishnu:
I've been trying to port the TWRP Recovery for Xperia U (kumquat), and I'm getting the following error during compilation :

make: *** No rule to make target `bootable/recovery/res/images/icon_firmware_error.png', needed by `/home/vishnu/android/system/out/target/product/kumquat/root/res/images/icon_firmware_error.png'. Stop.

And from what I can see, the bootable/recovery/res/ folder of TWRP just has a single file : dummyfileforgit.

Now on copy-pasting the contents of the /res/images folder from CWM Recovery into the TWRP Recovery folder, the error is resolved. But why exactly is TWRP requesting for these files?
[Android Software Development] Ryuinferno:
You did not declare the res type in your BoardConfig.mk...refer to the first post for more details...
[Android Software Development] vishnu:
Are you talking about the screen resolution? I did add :

DEVICE_RESOLUTION := 480X854

to my BoardConfig.mk.
[Android Software Development] Ryuinferno:
You have to check whether is there a res for that size...afaik there is none...
[Android Software Development] vishnu:
It is there inside '/bootable/recovery/gui/devices/480x854'.
[Android Software Development] Ryuinferno:
Something is really wrong then...that file is only requested by the Android.mk of CWM...if you replaced the whole recovery folder with the one by twrp, it should not request anymore...you error happens because twrp does not use that .png at all...
[Android Software Development] vel_tins:
Well, so far so good.

After a few hickups, I am at least, able to build TWRP.

But one question:

Where (in which location) do I put the .ko files (touch, nand, keyboard), so that they are included in the recovery.img after compiling?
[Android Software Development] paradiselost28:
Nice work ! Can anyone compile this recovery for the Samsung Galaxy S (I9000) ? It would be great...
[Android Software Development] #define:
Hey [MENTION=912474]Dees_Troy[/MENTION]!

I compiled from the twrp2.6 branch, using CM10, and the recovery version still shows 2.5.0.0 on top.. Thought I would let you know..

BTW, you guys are supporting the HTC Pico officially.. Can you please update your fork of the device tree?? A new kernel has been pushed.. Here's the link:

https://github.com/bhargz/cm10_htc_pico
[Android Software Development] Ryuinferno:
Use the 2.5 branch instead... That's updated to 2.6...for some unknown reason, the 2.6 branch has not been updated...
[Android Software Development] :
Hi!

I'm new to building from source, so forgive me for sounding like a noob. :)

I want to build TWRP from source, so I can change the curtain image and integrate the fix for backups not copying over to the PC, on the Nexus 4.

Now if I want to compile just TWRP, why would I need to sync CyanogenMod or ClockworkMod sources? I'm confused.

Please help me out?

Thanks!
[Android Software Development] #define:
A recovery is an integral part of the system.. When you compile a rom, a recovery also gets compiled.. So basically, a rom can be compiled without a recovery but not the other way..
[Android Software Development] :
Oh, I thought Recovery was separate from the ROM installed; since, TWRP, once installed, works with any ROM I flash ( AOSP, AOKP, PA, CM...)

What sort of source would TWRP need from CyanogenMod?

Thanks for answering! :)
[Android Software Development] #define:
Everything except bootable/recovery.. For that you use TWRP.. The rest of the instructions you can find in the 1st few posts..
[Android Software Development] :
Well, I guess I won't be compiling then. I can't possibly download all the CyanogenMod source (>10GB).... :(

I was hoping just the 1 GB of TWRP source would be enough...

Any ways to bypass this?
[Android Software Development] globula_neagra:
It would not be possible for you Dees, to implement the same system of the CWM builder and have an online solution ?
[Android Software Development] Johnsondr80:
Nice guide. Thanks for doing it
[Android Software Development] iurnait:
hey there, so i am trying to build TWRP for the galaxy player 5, and ive run across a few errors:

The first one that i ran into was this:

build/core/base_rules.mk:130: *** external/fuse/lib: MODULE.TARGET.STATIC_LIBRARIES.libfuse already defined by bootable/recovery/fuse. Stop.

So i deleted external/fuse, which caused this error:

external/exfat/fuse/main.c:25:18: fatal error: fuse.h: No such file or directory
compilation terminated.
make: *** [/home/tianrui/android/cm/out/target/product/venturi/obj/STATIC_LIBRARIES/libexfat_mount_intermediates/main.o] Error 1
make: *** Waiting for unfinished jobs....

So i deleted external/exfat because it was already included in bootable/recovery.

Now, im getting this:

target Executable: busybox (/home/tianrui/android/cm/out/target/product/venturi/obj/EXECUTABLES/busybox_intermediates/LINKED/busybox)
/home/tianrui/android/cm/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.7/bin/../lib/gcc/arm-linux-androideabi/4.7/../../../../arm-linux-androideabi/bin/ld: warning: shared library text segment is not shareable
/home/tianrui/android/cm/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.7/bin/../lib/gcc/arm-linux-androideabi/4.7/../../../../arm-linux-androideabi/bin/ld: error: treating warnings as errors
collect2: error: ld returned 1 exit status
make: *** [/home/tianrui/android/cm/out/target/product/venturi/obj/SHARED_LIBRARIES/libminuitwrp_intermediates/LINKED/libminuitwrp.so] Error 1
make: *** Waiting for unfinished jobs....
external/busybox/debianutils/mktemp.c:96: warning: warning: mktemp() possibly used unsafely; consider using mkstemp()
[Android Software Development] pcwizzy37:
My main PC (the c2d) is an Asus X83Vm (also called Asus N80Vm.). (laptop)

I also have a Toshiba Portege 3500. (my homeschool computer). (laptop)

And my Intel Pentium ii 333MHz 256MB RAM desktop. (with Debian.)

Take win10 off that thing! Iinstall Linux (best would be Lubuntu 14.04).

I sort of dislike AMD.
[Android Software Development] yuweng:
i first learn to built TWRP on an Athlon XP, first built with CCACHE tooks 1 1/2 hours ! 2nd build with CCACHE took half an hour ! To build a ROM, it tooks 7 hours ! :laugh: 14 minutes for building CyanogenMod 13.0, i wonder for TWRP, i'll say it'll only take 2 or 3 minutes... :cowboy:

shoxxy has shared with me that he built TWRP/ ROM on his old laptop & control his built at work via teamviewer & MSF Jarvis use a build server, no need to build it locally, there is a guide here for google cloud, you can build TWRP on it too... :good:
[Android Software Development] pcwizzy37:
Athlon XP? are you sure? before i knew a thing about linux, i had a pc with an AMD Athlon XP 2000+, and it ran win xp(my favorite version of mickeysoft windows) quite slowly.
[Android Software Development] MSF Jarvis:
Both of my servers(one's only got 50 gigs storage, I use to work with TWRP only on it) are currently free, and I'd be glad to share if someone's in need. PM me if you wanna build TWRP or CM13 or anything and I'll give you restricted access(what'd you think, root access? Hah! Gotcha!!)
[Android Software Development] bigsupersquid:
I've read an xda tutorial/review/something informational that showed cpu speeds don't matter much compared to storage media speed and configuration.

I originally built on a /old/ Dell single core with 512Mb ram. took twelve hours overnight to build gingerbread without ccache :P

my 8core 3GHz 16Gb ram that i overheated and killed still took three hours to build kitkat before populating ccache. thirty minutes after ccache.

it was using one regular seven year old HDD with separate partitions for ccache and output, and an external usb3 drive for source.

i get the same build time for marshmallow from my current 2core 2.4GHz AMD ($8 shipped ?!) with only one 64 Gb SSD for output and separate source / ccache spinning hard drives.

the supposed optimal configuration according to the article was six SSD drives in a striped RAID format. made builds go ridiculously fast on not the fastest cpu not the most ram machines.

the quote was mostly to say thanks for the link to the cloud server build guide. I'd considered that here and there while my hardware was down but didn't want to figure out how to do it.
[Android Software Development] DarkFrenzy:
should i change mms136 to zinitix_bt_532 to get sysfs working

this is my touch screen driver

https://github.com/CyanogenMod/andr....0/drivers/input/touchscreen/zinitix_bt_532.c
[Android Software Development] Android-Andi:
You might need to implement a sysfs to your driver, mms136 code was an example.

~ All my work, news etc. on http://andi34.github.io ~
[Android Software Development] vampirefo:
Finally got time to built twrp 3.0.2 on my new pc, Ubuntu 16.04 Mate.

Built in 5 minutes flat. So I am happy with that time.

About 2 minutes faster than my 2007, AMD pc.

---------- Post added at 07:06 PM ---------- Previous post was at 07:03 PM ----------

Did you get it built?
[Android Software Development] Ophidian_DarkCore:
i still have your 4.4.4 rom on my optimus v(really an optimus u). that sdcard f2fs stuff you came up with was epic to say the least

---------- Post added at 10:46 PM ---------- Previous post was at 10:43 PM ----------

the processes sit hella waiting for the disk to catch up!

this happens on my setup. dual x5470 xeon, 32gb ram, two seagate 80g hdds. the bottleneck is obvious

changing the output directory to a different disk is a lifesaver

---------- Post added at 11:01 PM ---------- Previous post was at 10:46 PM ----------

I got a dell t5400 for 120$, the ram upgrade was 50$!!!, the cpus were 80$ plus a heatsink for 20. budget dev boxes ftw
[Android Software Development] :
Hi All, TWRP for the Moto G4 Plus is now available. The tree can be found at https://github.com/motog4plus/android_device_motorola_athene and the XDA thread at http://xdaforums.com/moto-g4-plus/development/wip-twrp-3-0-2-2-recovery-moto-g4-plus-t3386586. I have also attached the build.prop below.
[Android Software Development] daniel4501:
How you did this?

I'm trying to do this and I can not .

Could you direct me a tutorial or tell me step by step to install TWRP on the emulator .
[Android Software Development] pcwizzy37:
Cool, don't want to waste a whole gig of RAM though.
[Android Software Development] MSF Jarvis:
Please Google on how to use AVD. And don't quote the OP if you simply don't know what you are dealing with.
[Android Software Development] DevUt:
Im running into these errors

make[1]: Leaving directory `/home/devut/a/android/system/kernel/htc/endeavoru'
make -C kernel/htc/endeavoru O=/home/devut/a/android/system/out/target/product/endeavoru/obj/KERNEL_OBJ INSTALL_MOD_PATH=../../system ARCH=arm CROSS_COMPILE=" arm-eabi-" modules_install
make[1]: Entering directory `/home/devut/a/android/system/kernel/htc/endeavoru'
INSTALL arch/arm/mach-tegra/baseband-xmm-power2.ko
INSTALL drivers/bluetooth/btwilink.ko
INSTALL drivers/bluetooth/hci_uart.ko
INSTALL drivers/hid/hid-elecom.ko
INSTALL drivers/hid/hid-magicmouse.ko
INSTALL drivers/hid/hid-wacom.ko
INSTALL drivers/hid/hid-wiimote.ko
INSTALL drivers/misc/ti-st/gps_drv.ko
INSTALL drivers/hid/uhid.ko
INSTALL drivers/misc/ti-st/hci_if_drv.ko
INSTALL drivers/misc/ti-st/st_drv.ko
INSTALL drivers/net/kineto_gan.ko
INSTALL drivers/scsi/scsi_wait_scan.ko
INSTALL drivers/net/usb/raw_ip_net.ko
INSTALL drivers/staging/ti-st/fm_drv.ko
INSTALL drivers/usb/class/cdc-acm.ko
INSTALL drivers/usb/serial/baseband_usb_chr.ko
INSTALL net/bluetooth/bluetooth.ko
INSTALL net/bluetooth/bnep/bnep.ko
INSTALL net/bluetooth/hidp/hidp.ko
INSTALL net/wireless/cfg80211.ko
INSTALL net/bluetooth/rfcomm/rfcomm.ko
INSTALL net/wireless/lib80211.ko
DEPMOD 3.1.10-cyanogenmod+
Warning: you may need to install module-init-tools
See http://www.codemonkey.org.uk/docs/post-halloween-2.6.txt
make[1]: Leaving directory `/home/devut/a/android/system/kernel/htc/endeavoru'
mdpath=`find /home/devut/a/android/system/out/target/product/endeavoru/system/lib/modules -type f -name modules.order`; if [ "$mdpath" != "" ];then mpath=`dirname $mdpath`; ko=`find $mpath/kernel -type f -name *.ko`; for i in $ko; do arm-eabi-strip --strip-unneeded $i; mv $i /home/devut/a/android/system/out/target/product/endeavoru/system/lib/modules/; done; fi
mdpath=`find /home/devut/a/android/system/out/target/product/endeavoru/system/lib/modules -type f -name modules.order`; if [ "$mdpath" != "" ];then mpath=`dirname $mdpath`; rm -rf $mpath; fi

#### make failed to build some targets (30:39 (mm:ss)) ####

Im using the omni's bootable recovery with CM13
[Android Software Development] MSF Jarvis:
[MENTION=7401277]DevUt[/MENTION],

...
Warning: you may need to install module-init-tools
...

Try apt install -y module-init-tools
[Android Software Development] DevUt:
i used that command but without -y flag

and ran that command again with this result

devut@devut-HP-2000-Notebook-PC:~$ sudo apt install -y module-init-tools
[sudo] password for devut:
Reading package lists... Done
Building dependency tree
Reading state information... Done
module-init-tools is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 202 not upgraded.
devut@devut-HP-2000-Notebook-PC:~$
[Android Software Development] Startrek852:
OK, That means it's installed, try building now.
[Android Software Development] daniel4501:
I'm trying to do this and I can not .

Could you direct me a tutorial or tell me step by step to install TWRP on the emulator .
[Android Software Development] Startrek852:
Dude, you already posted this AND got an answer. You're just spamming now.
[Android Software Development] vampirefo:
Why? By the time you get this setup, you could have already built 10 of 15 real recoveries.
[Android Software Development] Startrek852:
I think you mean 10 to 15.
[Android Software Development] DevUt:
Did but still failling

when is type service module-init-tools

It tells service unrecognized

But when i type kmod it gives me a answer

as kmod replaced module-init-tools
[Android Software Development] yuweng:
Some times its best to compile the latest kernel with recovery, most of the time TARGET_PREBUILT_KERNEL := will do and you'll get over the kernel build error... :cowboy:
[Android Software Development] DevUt:
What all changes should i do ?
[Android Software Development] MSF Jarvis:
Comment out the TARGET_KERNEL_SOURCE and TARGET_KERNEL_CONFIG lines, unpack your stock boot.IMG, take the zImage, and place it in your device tree with name as kernel(easy to remember that way). Then add TARGET_PREBUILT_KERNEL := <path-to-kernel-file-extracted-earlier> to your BoardConfig.mk
[Android Software Development] DevUt:
A ZImage is also made during this process can i use that one? Because there are some changes in the source of the kernel

And also should the path be like :- device/htc/endeavoru/kernel/zImage :confused:i
[Android Software Development] MSF Jarvis:
The path looks good, my suggestion would be compile the kernel separately, outside the Android build yree using any number of guides available and then use that zImage by adding the flag and placing the zImage at the location you say :)
[Android Software Development] DevUt:
But can that zImage be used?
[Android Software Development] MSF Jarvis:
Yeah definitely
[Android Software Development] DarkFrenzy:
i have started making twrp using u r minimal twrp tree but i m getting this error at the starat of the process

Checking build tools versions...
bootable/recovery/gui/Android.mk:127: ****************************************************************************
bootable/recovery/gui/Android.mk:128: * TW_THEME is not valid: ''
bootable/recovery/gui/Android.mk:129: * Please choose an appropriate TW_THEME or create a new one for your device.
bootable/recovery/gui/Android.mk:130: * Available themes:
bootable/recovery/gui/Android.mk:131: * landscape_hdpi landscape_mdpi landscape_mdpixx portrait_hdpi portrait_mdpi watch_mdpi
bootable/recovery/gui/Android.mk:132: ****************************************************************************
bootable/recovery/gui/Android.mk:133: *** stopping. Stop.
[Android Software Development] MSF Jarvis:
Make sure you have this flag in your BoardConfig.mk

TW_THEME := portrait_hdpi

You may want to change its value to one of the other values the error message shows in case the UI looks weird.
[Android Software Development] DarkFrenzy:
no thats was not the problem

i didnt ran this . build/envsetup.sh and lunch i just directly ran make -j3 recoveryimage
[Android Software Development] MSF Jarvis:
It had started building TWRP with the goldfish device tree which is full-AOSP and hasn't been TWRP-ified yet. Good that it's working now, wishing you luck :good:
[Android Software Development] DarkFrenzy:
it was really great, twrp build completed in 10 minutes (used built in kernel).

thanks a lot for the twrp minimal cm13 tree,

how to get screen timeout in setting ? screen light is not turning off
[Android Software Development] MSF Jarvis:
The option isn't there? In settings, one of the tabs does have a screen timeout setting. Please check back and report.
[Android Software Development] DarkFrenzy:
Yes its not there. But in the official twrp that option is there . I will compare with it.

Official twrp has mtp bug and has no USB storage and no f2fs support.

My twrp has no mtp bug and has USB storage and f2fs support.

How to contact the deestroy
[Android Software Development] MSF Jarvis:
"the deestroy" totally confused me, but anyways, Dees_Troy can be found at #twrp on webchat.freenode.net/ but a safer way is to mail him the link to your device tree at dees_troy@teamw.in asking him to make you maintainer. If you want a solution of this issue, IRC is the right way out.
[Android Software Development] DevUt:
My boardConfig

TARGET_PREBUILT_KERNEL := device/htc/endeavoru/kernel/zImage

and new error :

rc
Copy: /home/devut/a/android/system/out/target/product/endeavoru/root/ueventd.rc
target Prebuilt: (/home/devut/a/android/system/out/target/product/endeavoru/kernel)
acp: missing destination file
make: *** [/home/devut/a/android/system/out/target/product/endeavoru/kernel] Error 2
make: *** Waiting for unfinished jobs....
[Android Software Development] Startrek852:
try renaming the zImage to kernel.
[Android Software Development] NepoRood:
Try removing this from your endeavoru.mk file:

# Prebuilt kernel
ifeq ($(TARGET_PREBUILT_KERNEL),)
LOCAL_KERNEL := device/htc/endeavoru/kernel
else
LOCAL_KERNEL := $(TARGET_PREBUILT_KERNEL)
endif

PRODUCT_COPY_FILES := \
$(LOCAL_KERNEL):device/htc/endeavoru/kernel

In my limited experience, above is not needed with "TARGET_PREBUILT_KERNEL :=" in the BoardConfig.mk

EDIT:

Just to make sure, unpack your recovery.img or boot.img file with AIK, use the zImage, located in: split_img folder (look for something similar to: recovery.img-zImage) and use that for your "prebuilt kernel"
[Android Software Development] pix106:
I had to add my prebuilt kernel to PRODUCT_COPY_FILES to avoid getting an error on build.

I never tried using LOCAL_KERNEL syntax.

Maybe this is your line that is wrong, i would try replacing

PRODUCT_COPY_FILES := \
$(LOCAL_KERNEL):device/htc/endeavoru/kernel

with

PRODUCT_COPY_FILES := \
$(LOCAL_KERNEL):kernel

My working TWRP minimal devicetree for Lenovo TAb2A7-10F : https://github.com/pix106/android_device_lenovo_Tab2A710F
[Android Software Development] MSF Jarvis:
Next time, keep the commit messages in English rather than French ;)
[Android Software Development] NepoRood:
I've only built TWRP for a few devices, that's why I said limited experience ;)

I have noticed other devices using what you suggested though :good:
[Android Software Development] pix106:
You know french enough to identify it :)
[Android Software Development] MSF Jarvis:
A teacher tried for three years to teach my class French when I was in sixth grade. Apparently she didn't do a bad job at it ;)
[Android Software Development] pix106:
this is my first device :)

These commit messages are automatic, it's actualy worse : i did not input any commit message :)
[Android Software Development] NepoRood:
We all start somewhere, I've built for: Allwinner, MTK and Qcom devices (one of each, lol)
[Android Software Development] MSF Jarvis:
I officially maintain one Qcom and one MTK lol ;)
[Android Software Development] NepoRood:
The Droid Turbo has an official maintainer already, maybe I'll get my other devices added someday...
[Android Software Development] MSF Jarvis:
Don't lose hope ;) Try with the AllWinner one
[Android Software Development] NepoRood:
Episode IV: A New Hope

lol, I gotta get TWRP to build on CM13 first. I'm getting a lot of errors right now...
[Android Software Development] MSF Jarvis:
I'll give you my server over SSH if you want, that way, I can see what's exactly going on, plus we can work together on the same goddamn terminal! You type this into the shell : "#MSF build broken! Fix pl0x!" And I go berserk, type like crazy, and the issue's fixed :) Now how cool is that ;)
[Android Software Development] NepoRood:
Sounds good to me, my friend. Unfortunately, I'm 120 miles away from my terminal right now. As soon as I get back home tho, imma pm the **** out of you :D
[Android Software Development] DevUt:
Can I also join the bandwagon ? And also what it takes to become a twrp official maintainer I want to become of HTC one x :laugh:
[Android Software Development] MSF Jarvis:
Not much, a working device tree and some luck to find the lead devs on #twrp on IRC. They'll run you a test build, confirm its working, then they'll release an official build and update the device page to show you as maintainer. Nice and easy :)

About the server bandwagon, not sure. My friend who provided my main build server is currently in another country, and the server took the opportunity and messed itself up. I'm hoping that by the time [MENTION=7237874]NepoRood[/MENTION] covers the 120 miles to home, my server would be back up :D
[Android Software Development] DevUt:
what does this means to me?

http://xdaforums.com/showpost.php?p=54175266&postcount=4881
[Android Software Development] MSF Jarvis:
That you shouldn't use a prebuilt kernel if you have also cloned the kernel source :)