yashsingh1/xdaforums huggingface dataset:
[Android Software Development] MicroMod777:
Did a kdz restore, formated sd card from tablet and now it flashes fine. Throws same mtp error in log but no twrp reboot on flashing. As long as I can flash, im good! Thanks again.
[Android Software Development] mhannigan:
I LOVE TWRP, but one thing has always bothered me - it has the absolute most hideous splash screen. In fact, when I've told a couple of friends they should be using it, each of them, when they saw that ugly blue TeamWin screen, asked me if I was serious because it looks like [fill in ugly thing here].

This is nothing against your dev efforts. If you didn't make the best and most usable recovery I the planet, I wouldn't be writing this message - and I'd like to stand up before my legs get numb as I sit here on the toilet, so I will cut to the chase.

Would compiling my own recovery be the best/only way of replacing that with something cool and shiny (that says TeamWin of course) or might there be an easier way? Thanks.

Mike
[Android Software Development] yuweng:
TWRP has allow to use customize themes for quite awhile now, refer to this thread & if you only wanna change the splash screen then refer to post#2, z31s1g has done a great job on it & constantly updating it too . . . :good:
[Android Software Development] mohamed786:
hai i have compiled twrp recovery for my device i cant able to install/flash recovery.img while in odin it gives fails as output

Then i have flashed boot.img but i have seen that the Twrp recovery sucessfully booted...

Issues:

Rebooting only in recovery alone (while i click reboot system it show no os installed do you want to reboot)

System

Sd card

Data

Cache partitions not mounted

plz help me...
[Android Software Development] ibub:
A friend compiled a build that has the same symptoms as this. No partitions are listed as available in mount menu. I think the error message is because twrp does not see /system (not mounted). Recovery.fstab and twrp.fstab seems correct. Recovery.rc has:

on fs

# mount All The Things

mount_all ./fstab.lgl34c

setprop ro.crypto.fuse_sdcard true

so I don't understand why partitions are unavailable.
[Android Software Development] yuweng:
Guys, as one of my Master Shifu once said . . .

So pls post your github device tree, if you don't have one then use pastebin, post as much info as possible such as recovery log then only fellow XDA members/ Developers will be able to help you & always use the hide button to hide your extra long compile log . . .
[Android Software Development] aniket.lamba:
How to modify the files in the source in order to compile TWRP along with the ROM? My device also has TWRP recovery.

Here's the TWRP source for my device - https://github.com/armani-dev/twrp_device_xiaomi_armani
[Android Software Development] vampirefo:
What is the main difference between 2.8.6.0 and 2.8.5.0? I ask caused I compiled both on the same exact source CM12, both compiled and seem to work fine, except when selecting reboot to system.

Only 2.8.5.0 reboots to system 2.8.6.0 reboots to twrp splash screen then back into twrp recovery, 2.8.6.0 doesn't allow me to leave twrp recovery, yet 2.8.5.0 reboots to system just fine.
[Android Software Development] _that:
You need to merge the TWRP-specific settings into the ROM device tree's BoardConfig.mk.

I guess this is related: https://github.com/omnirom/android_bootable_recovery/commit/bc2bc6bb674991e7f758d2f72e960e7638be281d
[Android Software Development] vampirefo:
Thanks, that was the problem, I rolled those files back, now 2.8.6.0 reboots to system just like 2.8.5.0, I am glad it was an easy fix, I am a die hard CWM recovery fan, just started working with TWRP, due to CWM recovery not supporting lollipop and TWRP does.

My builds of TWRP seem to work just fine, I am going over some of the BoardConfig.mk options for TWRP to get the best out of the recovery for my device.

By the way really impressed on how fast TWRP recovery is being compiled.

Made recovery image: /media/vampirefo/05f64de9-2a44-478e-a67a-8c2261d9e88b/CM12/out/target/product/yellowtail/recovery.img

#### make completed successfully (07:20 (mm:ss)) ####

vampirefo@vampirefo-GA-MA78GM-US2H:/media/vampirefo/05f64de9-2a44-478e-a67a-8c2261d9e88b/CM12$

I made a few more BoardConfig.mk adjustments, reboot computer then did a rebuild, this time just over 5 minutes to compile recovery..

#### make completed successfully (05:08 (mm:ss)) ####
[Android Software Development] _that:
And it can be made even faster - when I preserve the kernel objects ($OUT/obj/KERNEL_OBJ), a full "mka recoveryimage" takes only about 1 minute.
[Android Software Development] ItsAnilSingh:
Help me pls.

I am using cm-10.1 source with omnirom bootable recovery branch android-5.0 for porting TWRP and getting the following error with and without otatools while compiling. I already built CWM recovery with the same cm-10.1 sources.

I also used android-4.4 and android-5.1 branch of omnirom bootable recovery instead but having same error.
[Android Software Development] vampirefo:
After using twrp for a few days, I like the recovery and have noticed two things one terminal command doesn't work and sometimes I get a phantom click.

My screen sometimes clicks itself or something selects an option I didn't check.

Over all recovery is very nice.
[Android Software Development] _that:
Saying "doesn't work" is useless - do you get any error messages? Anything related in recovery.log? What device do you have and what device tree did you use to build?
[Android Software Development] vampirefo:
No problem terminal command fixed now, phantom click seems to be due to wind or even breathing, need to find a way to lower sensitivity.

I have a dell Venue 8 3830, just need to find a way to adjust touch so wind doesn't cause phantom clicks.

I am using my device tree for Venue 8 3830, I don't see an option to lower touch sensitivity.

---------- Post added at 01:51 PM ---------- Previous post was at 01:09 PM ----------
[Android Software Development] vampirefo:
Little more tweaking seems to have fixed the phantom clicking. Now to test backup and restore.

Update

Backup and restore works just fine on my device.
[Android Software Development] _that:
If you don't share with us *how* you solved those problems, your posts don't help anyone.
[Android Software Development] vampirefo:
Ok, no problem I had 3 problems I will list all 3 and the solution I used to fix them.

1. Problem twrp 2.8.6.0 would not allow me to boot into system.

1. Solution replace twrp-functions.cpp and twrp.cpp from 2.8.5.0

2. Problem terminal command didn't work

2. Solution to BoardConfig.mk I added below two lines.

BOARD_USE_CUSTOM_RECOVERY_FONT := "roboto_10x18.h"

RECOVERY_GRAPHICS_USE_LINELENGTH := true

3. Problem phantom clicks, twrp would make own selections sometime.

3 Solution to BoardConfig.mk I added below four lines, I believe it was TW_NO_USB_STORAGE, but I added them all at the same time, so I list them all as the solution.

BOARD_HAS_NO_REAL_SDCARD := true

TW_NO_REBOOT_BOOTLOADER := true

TW_NO_REBOOT_RECOVERY := true

TW_NO_USB_STORAGE := true
[Android Software Development] mohamed786:
[/COLOR]

Hai! Twrp 2.8.5 is branch 5.0 correct... :)
[Android Software Development] vampirefo:
Yes.
[Android Software Development] mohamed786:
Did u tell me how did u resolve u r backup problem
[Android Software Development] vampirefo:
What backup problem? I never had one, backup and restore was just fine for me.
[Android Software Development] katinatez:
Is that in the kernel.mk? Can I see an example on github? Thanks
[Android Software Development] _that:
No, it's just selective cleaning of the output directory.
[Android Software Development] Yogesh1969:
How to start Compiling?

Hi . I saw your thread regarding touch recovery, but it stops after a few posts . I didn't know whether to continue there or start here. ( Please suggest). With my limited knowledge, I could collect boarconfig.mk and recovery.fstab . Can you tell me what is actually to be done ?

I have compiled COT touch recovery for some 4 devices. But this is just going over my head.
[Android Software Development] largusek:
Can you add support samsung galaxy A3?
[Android Software Development] :
This thread is about building it yourself for your device. :good:
[Android Software Development] _that:
Try removing this line:
[Android Software Development] arvinquilao:
Gah! How could I overlooked that flag. Thanks! It's showing up now. :)
[Android Software Development] Matthew_333:
Haii.. Im trying to build TWRP for e975, but i always get an error.. This is my output: http://pastebin.com/nDun9CeE This is my boardconfig.mk: http://pastebin.com/QVVzpcEz Do any of you have an idea how to solve this and build? Thank you for any help :)
[Android Software Development] _that:
Reading the error message helps. Really.

bootable/recovery/gui/Android.mk:137: * TW_THEME () is not valid.
bootable/recovery/gui/Android.mk:138: * Please choose an appropriate TW_THEME or create a new one for your device.
bootable/recovery/gui/Android.mk:139: * Valid options are portrait_mdpi portrait_hdpi watch_mdpi
bootable/recovery/gui/Android.mk:140: * landscape_mdpi landscape_hdpi

You have:

TW_THEME := hdpi_portrait
[Android Software Development] Android-Andi:
Maybe [MENTION=912474]Dees_Troy[/MENTION] can update the OP:

TW_THEME := watch_mdpi

TW_THEME := portrait_mdpi

TW_THEME := portrait_hdpi

TW_THEME := landscape_mdpi

TW_THEME := landscape_hdpi

Supported resolutions:

portrait_mdpi = 320x480 480x800 480x854 540x960

portrait_hdpi = 720x1280 800x1280 1080x1920 1200x1920 1440x2560 1600x2560

watch_mdpi = 240x240 280x280 320x320

landscape_mdpi = 800x480 1024x600 1024x768

landscape_hdpi = 1280x800 1920x1200 2560x1600
[Android Software Development] Matthew_333:
Alredy changed this, and i found a fault.. But i have a question more.. I dont want to build in 720x1280, but in 768x1280 (which is obviously not supported.. Is there a way to do this?
[Android Software Development] _that:
TWRP will scale the theme to fit the screen, stretching the layout slightly.
[Android Software Development] Matthew_333:
I alredy have version in 720x1280, and on right side of screen it lefts a black ribbon...
[Android Software Development] _that:
A current version of TWRP should really fill the screen. If you can't explain what's wrong, adb pull /tmp/recovery.log and attach it.
[Android Software Development] fix-this!:
Im going to attempt to port twrp tonight for the lg g stylo for tmobile. I have xubuntu x64 installed. Can anybody tell me if there is a good guide to setting up the build enviorment for android 5.0? Ive searched and found guides but it may be outdated. Just wanna be sure.

Thanks.

Is this guide pretty current and relavent? : http://xdaforums.com/showthread.php?t=2639611
[Android Software Development] ne0zone75:
sepolicy build errors for serrano....

Good evening,

I am trying to update my builds for GT-I9190+2+5 from v2.8.5.0 (successfully compiled along with Omni 5.0) to v2.8.6.0 which i am trying to build against Omni 5.1 and i am getting these sepolicy related compilation errors :

device/samsung/msm8930-common/sepolicy/common/vold.te:10:ERROR 'unknown type proc_dirty_ratio' at token ';' on line 17414:
allow vold cache_file:file { write create open };
allow vold proc_dirty_ratio:file { { getattr open read ioctl lock } { open append write } };
checkpolicy: error(s) encountered while parsing configuration

... i've already tried to sync sepolicy to upstream CM sources but it does not make a change :(

Thank you for helping me out on this one ! :good:

PS : i've synced and omnified cm-12.1 sources for serrano3gxx...
[Android Software Development] Android-Andi:
Check your vold.te file Inside the device tree.

proc_dirty_ratio seems not to be defined. CM might have added it to vendor/cm or external/sepolicy but omni don't.

Do you have a working cm-12.1 tree? If yes you can build from CM 12.1 Source too.

Clone twrp inside bootable/recovery-twrp

Inside your BoardConfig.mk add:

RECOVERY_VARIANT := twrp

Add your twrp flags and good to go :)
[Android Software Development] ne0zone75:
Good morning and thank you for your answer,

I did not get what you suggested above, meanwhile i cherry picked this CM commit and got rid of the previously mentioned build error BUT i am encountering some other ones... :

Error loading context file from /mnt/IHDD/DEV/Android/TWRP/5.1/sources/OmniROM/out/target/product/serrano3gxx/obj/ETC/property_contexts_intermediates/property_contexts
make: *** [/mnt/IHDD/DEV/Android/TWRP/5.1/sources/OmniROM/out/target/product/serrano3gxx/obj/ETC/property_contexts_intermediates/property_contexts] Error 4
make: *** Deleting file `/mnt/IHDD/DEV/Android/TWRP/5.1/sources/OmniROM/out/target/product/serrano3gxx/obj/ETC/property_contexts_intermediates/property_contexts'
make: *** Waiting for unfinished jobs....

... with some

... out/target/product/serrano3gxx/obj/ETC/property_contexts_intermediates/property_contexts: Multiple same specifications for...

errors

AND

Error loading context file from /mnt/IHDD/DEV/Android/TWRP/5.1/sources/OmniROM/out/target/product/serrano3gxx/obj/ETC/file_contexts_intermediates/file_contexts
make: *** [/mnt/IHDD/DEV/Android/TWRP/5.1/sources/OmniROM/out/target/product/serrano3gxx/obj/ETC/file_contexts_intermediates/file_contexts] Error 4
make: *** Deleting file `/mnt/IHDD/DEV/Android/TWRP/5.1/sources/OmniROM/out/target/product/serrano3gxx/obj/ETC/file_contexts_intermediates/file_contexts'

... with a bunch of

... out/target/product/serrano3gxx/obj/ETC/file_contexts_intermediates/file_contexts: Multiple same specifications for...

errors

... any ideas ?

Also, could you please explain your previous solution a little bit more... :good:

Thanks,

Regards
[Android Software Development] Android-Andi:
[MENTION=5280400]ne0zone75[/MENTION] whole output?

About the other solution:

Serrano3gxx has official cm 12.1 builds?

If yes, sync cm 12.1 source.

Inside your cm12.1 source git clone twrp inside bootable/recovery-twrp

Now add mentioned flag, it will build twrp instead cm-recovery now.
[Android Software Development] Vanily:
Trying to build TWRP for Xperia Ray (urushi) using CM12.1 sources, but building stops with the following error:

target Prebuilt: twrp (/home/media/android/source/out/target/product/urushi/obj/RECOVERY_EXECUTABLES/twrp_intermediates/twrp)
bootable/recovery/updater/install.c:1473: error: undefined reference to 'wipe_block_device'
collect2: error: ld returned 1 exit status
build/core/executable_internal.mk:66: recipe for target '/home/media/android/source/out/target/product/urushi/obj/EXECUTABLES/updater_intermediates/LINKED/updater' failed
make: *** [/home/media/android/source/out/target/product/urushi/obj/EXECUTABLES/updater_intermediates/LINKED/updater] Error 1
make: *** Waiting for unfinished jobs....

make clean didn't help.

Can anybody help me?
[Android Software Development] neckbonest:
looking for a dev to compile TWRP for the LG G pad X8.3. i have rooted my X8.3 using the LG 1-click root v1.3. i am no dev but will help with anything i can

we do not have our own section yet so i am asking here.
[Android Software Development] CelticWebSolutions:
Hi All,

I built TWRP for a device of mien and it works perfectly, the only thing that done't work is ADB, if I try and connect to the device via ADB I get a not online / not authorized response. How can I rebuild it so that it is authorized please? What am I doing wrong / missing out?

Thanks in advance.

Regards

Celtic
[Android Software Development] Lrs121:
I can look into it if you'd like. is it the same as LG G pad 8.3 codename V500

is it linux you are having issues with adb?
[Android Software Development] neckbonest:
that would be great. its the newer version of the 8.3. the v500(wifi only) vk810 is the cellular version. X8.3 is VK815 ot sure if there is a wifi only model
[Android Software Development] CelticWebSolutions:
Thanks, I worked it out in the end. It was set as secure in the build.prop so I removed that and now I get access as you'd expect in recovery without having to be previously authorised via android.

Thanks for the offer of help :)

Regards

Celtic
[Android Software Development] vampirefo:
Any special config for compiling TWRP for MTK6572? I just got this Walmart phone last night need to make recovery for it.

I have already compiled TWRP for x86 tablets.

http://xdaforums.com/android/development/root-nextbook-ares-8-twrp-recovery-t3133165

And build tethered TWRP for other devices.

http://xdaforums.com/android/development/linux-version-twrp-2-8-6-0-tethered-t3123075

So I am wondering if any special setting or patch is needed to compile for mtk devices, ext4 system

I know with Carliv recovery I had to add BOARD_HAS_MTK := true in the past with mtk devices, for it to work on MTK devices, no patches needed as he added the mtk stuff to recovery, it was activated via BoardConfig.
[Android Software Development] vampirefo:
Well I compiled twrp for my BLU Studio 5.0 C, I didn't seen any options for MTK devices, so I just straight compiled twrp, seems to work just fine on my MTK phone.
[Android Software Development] nerdyblonde:
Hey, I am working on building TWRP for my LG E980.. I am using CM12.1 source, since Omni doesn't build for the E980. I am using the Omni-5.1 recovery branch.

I keep getting this error: http://hastebin.com/afonuhiday.mel

I, of course, have the target kernel config in BoardConfig.mk, along with all the other TWRP configs needed for my device. Could you tell me how to go about preserving the kernel objects you mentioned? Hoping maybe that will let me pass up the error I'm getting.

Thanks in advance for any help.. =)
[Android Software Development] vampirefo:
OUT/obj/KERNEL_OBJ

Doesn't exist on any of my builds, my guess only few people have this, most likely due to building kernel, I use prebuilt kernels. Wouldn't speed up anything for me, except building kernel so useless for me.

Just use prebuilt kernel, much simpler, and faster, unpack your stock recovery.img and use the kernel inside it.
[Android Software Development] nubikom:
device configuration file

I wish I can install TWRP for my tablet

Hisense WM8 Wondermedia 8"

But when I open my "Device configuration file" is empty ?

Are you sure just send this empty folder to you ?

Or there is another configuration file besides /config ?

I use Root Explorer and have root

And I try search in Play Store but goomanager is not there
[Android Software Development] _that:
The error message disagrees. :)

Preserving the object files works only after you have compiled it successfully at least once (by not deleting obj/KERNEL_OBJ from $OUT).

---------- Post added at 10:34 PM ---------- Previous post was at 10:29 PM ----------

This thread is about compiling TWRP for your device yourself, it's not a request thread. You need to read and understand all pages of the chapter starting here -> http://source.android.com/source/building.html to do that successfully.
[Android Software Development] corphish:
Hi,

I am trying to build TWRP for an old device based on Jellybean 4.1.2.

So I am using android_bootable_recovery from Omni tree, branch 4.3.

I replaced the CM 10.0's bootable recovery with this one.

As per OP, made necessary changes in the board config.

Only thing is, I set to resolution to 320x480, but my device resolution is 240x320 (320x480 is the minimum, so..)

I built it, compilation was success. However, resultant binaries like teamwin and twrp are only 1 or 0 bytes.

So as expected, if I try flashing the img, and then try booting in recovery, I see the old recovery.

Can anybody help me?

TIA
[Android Software Development] k2wl:
Symlink: /home/k2wlxda/cm-source/cm12/out/target/product/nx511j/recovery/root/sbin/mkfs.exfat -> mount.exfat
make: *** No rule to make target `/home/k2wlxda/cm-source/cm12/out/target/product/nx511j/obj_arm/EXECUTABLES/updater_intermediates/updater', needed by `/home/k2wlxda/cm-source/cm12/out/target/product/nx511j/obj/PACKAGING/target_files_intermediates/cm_nx511j-target_files-1caae9e774.zip'. Stop.
make: *** Waiting for unfinished jobs....

any one know , fix for this error i am compiling cm12.1 with twrp recovery 5.1 branch
[Android Software Development] SdtBarbarossa:
[MENTION=912474]Dees_Troy[/MENTION]

Xperia L (Taoshan) twrp is using old repo.... it doesnt work properly

may you can use this repo?

https://github.com/SdtBarbarossa/android_device_sony_taoshan

changes by varun included to make f2fs working for us....

changed system.prop to make the recovery flash zips that check the prop (varun missed that one...)

Edit:

http://gerrit.twrp.me/#/c/914/

that would be enought....
[Android Software Development] user_for_android:
Hello,

On 4pda.ru forum someone has compile TWRP for Nokia X2 (Android smartphone).

http://4pda.ru/forum/index.php?showtopic=651024&view=findpost&p=41082834

Please, add this TWRP in yours repository and review code on github!

repo https://github.com/cm-nokia-x2

compiled TWRP file https://yadi.sk/d/so1LALyUhUrSc

mirror on Google Disk https://drive.google.com/folderview...p1NkRTcDc0OEtwZkhTMEN0cm5XSVljNnc&usp=sharing

features:

backup EFS (IMEI code)

backup persist (bt and wifi mac address).

P.S. But I am not developer.

Developers are

https://github.com/vm03

and

https://github.com/zombah

P.P.S. Sorry for my bad English.
[Android Software Development] SdtBarbarossa:
what jdk are you using?

try resync with ( repo sync -j 4 -c )

if you face those problems after.... try compile with omni source ...thats recommended
[Android Software Development] Epirex:
F2FS

anyone have problems with f2fs? I applied wipe to /data and /cache with f2fs and doesn't work :(

Added: My kernel have support for f2fs :p
[Android Software Development] Lrs121:
Some roms default to ext4 only and will reformat the partitions to do so. It is possible that is what is happening
[Android Software Development] Epirex:
But, my ROM if supported f2fs format (Check this commits: add f2fs tool, add f2fs support for recovery)

It's strange, if I change ext4 for f2fs in recovery.fstab I have softbrick :eek:
[Android Software Development] Lrs121:
The device is meant to have ext4 partitions so when you change the fstab it breaks things, if you can format the partitions as f2fs in the recovery then the recovery propperly supports f2fs. as for why it doesnt work im not sure. there is probably an error that is not seen.
[Android Software Development] SdtBarbarossa:
i dont know how it works for samsung... but for sony you have to set mountpoints in qcom.fstab ...have you any related file that declares mountpoints in samsung?

and second thing is your twrp.fstab ... dont supply lenght if you want to use f2fs in twrp....

if you want to get an idea look at sony taoshan device tree commits
[Android Software Development] Epirex:
Thanks for reply, I added mountpoints in my fstab for f2fs but I have softbrick :eek: and adb logcat is not working for know the problem :(
[Android Software Development] vampirefo:
LOL, you have to add the mount points to your boot.img, switching mount points in recovery is just for recovery, if you plan on booting into another file system you have to make sure your boot.img supports it.
[Android Software Development] Epirex:
Sorry for my noob question xD how to change mount point in boot.img? my kernel support f2fs (Check this commits: fs: add F2FS support, Enable F2FS)
[Android Software Development] vampirefo:
You have to unpack boot.img change ext4 to f2fs for all partitions you want to mount as f2fs repack then flash boot.img
[Android Software Development] SdtBarbarossa:
best will ve to compile whole rom+kernel with new mountpoints... mostly you will need to declare mountpoints double (one f2fs and one ext4) for system only one will work (the first one)

also keep in mind that you cant just blind change ext4 to f2fs ...you have to declare correct flags (they differ between ext4 and f2fs)
[Android Software Development] Epirex:
Okay, big thanks guys!
[Android Software Development] hawkeyexp:
Hi @ all,

tried to compile twrp for sony z1 (honami) and get it compile and booting but gui is buggy - has anybody an idea what goes wrong ? Res is set in boardconfig...
[Android Software Development] _that:
Try this:

RECOVERY_GRAPHICS_USE_LINELENGTH := true -- fixes slanty looking graphics on some devices