yashsingh1/xdaforums huggingface dataset:
[Android Software Development] zainifame:
can u upload your recovery.img, boot.img aslo build.prop and vold.fstab from your original rom, i will try to build it for you but if my build can boot :p
[Android Software Development] YuutaW:
That's a good thread!:good: Thanks
[Android Software Development] Zoggn:
my vold.fstab didn't have nothing interesting)) but i attach him)
[Android Software Development] zainifame:
check my pull request on your repos, and can u give me partition list on your phone?

by running :

su
cat /proc/partitions
or
cat /proc/mtd
[Android Software Development] Zoggn:
partitions https://gist.github.com/zoggn/b399715825d13b492a9ec7615b76deee
[Android Software Development] Amd4life:
can someone help me create a TWRP img for the new V20...I am stumped.

what files would I need to supply for those more talented than a noob like myself?
[Android Software Development] aj20010319:
I am trying to compile TWRP for lenovo vibe x3 but the screen goes black on boot and cant be used until the timeout reaches ends.

Here's my device tree, https://github.com/aj20010319/android_device_lenovo_x3

Anyone knows how can I fix it?
[Android Software Development] LiQuiD0101:
Having an issue compiling my recovery for my vk810

I can successfully build and use it.. kind of...

My issue is I cant install img files in my new recovery

Keeps telling me /external_sd/recovery.img/ is not a directory

I can install zips just fine.

Prebuilt kernel

Any ideas? Im stumped

Thanks
[Android Software Development] shoey63:
It's a bug in the 7-0 branch. There is a fix on omnirom gerrit that hasn't been merged yet. Cherry-pick it and rebuild. It should work after that.
[Android Software Development] LiQuiD0101:
Thank you!!!!!! I needed for 6.0 which they also had the fix for.

Applied and everything working!!

Thanks again
[Android Software Development] DodoGTA:
That's a general TWRP bug
[Android Software Development] ka_putt:
Hello everybody,

I'm trying at moment to compile TWRP for Huawei T2 Pro. The hardware is not much different from Honor 5 (kiwi), but when I compiling it, isn't working, even I using normaly kiwi sources from twrp. Compiled TWRP image for kiwi from twrp site is working without issues.

I've tryed to compile on OMNI 6 and CM13, still the same.

I hope someone can halp me :)

sorry for my bad englisch...^^
[Android Software Development] Startrek852:
The files you are using will NOT work on Marshmallow. Try using Omni 5.1.
[Android Software Development] czarsuperstar@gmail.com:
Quick question? How do you go about contacting The team to add a recovery on the list
[Android Software Development] MSF Jarvis:
#twrp channel on freenode IRC
[Android Software Development] czarsuperstar@gmail.com:
Thank you so much but I have sent pms and emails I received an email to properly name the source code which I also did. I am not complaining but before this phone I never compiled a recovery and I believe that it's solid. From looking at similar phones and such. I don't have the phone anymore but I don't want to leave them hanging. I just compiled 2 new images both K7's but one is the Metro and the other is as330. I just want to make sure that all is good. For the as330 I split up the boot image with mkboot tool and switch between the two kernels. I setup 2 omni folders. As330 in omni and ms330 in omni5.1 so it would not conflict.

https://github.com/czarsuperstar/android_device_lge_m1

Is the source code which I built using omni5.1 with 6.0 bootable recovery. Any assistance would be greatly appreciated.
[Android Software Development] ashyx:
Which is a rather contrived way of doing things. [emoji52]

As a suggestion, I'm sure it would benefit all round to actually create a proper submission form on the twrp server.

I'm guessing there are reasons why this isn't so?
[Android Software Development] czarsuperstar@gmail.com:
I followed the instructions for submitting the recovery from the twrp site so I did that. I mean it's not that important to have the team take over as I always tested the images before releasing it but I just wanted to talk to someone else just to make sure that all is good. Thanks.
[Android Software Development] MSF Jarvis:
The thing is that the TWRP team needs to make sure they can reproduce builds similar to yours before they add official support. Your recovery images are irrelevant if your device tree is unable to generate a good one on the TeamWin servers. It's just a matter of making sure stuff gets tested well enough.
[Android Software Development] ashyx:
I'm aware of that and that's precisely my point.

All that is required is:

Name and email of submitter

Link to source (github etc)

Name and email of willing tester

Much easier than the back and forth of IRC plus let's TW process the submissions at their leisure.

I've got countless builds out there, verified and working just fine.

It would be so much easier for me to submit via a form rather than chasing the team on IRC each time.
[Android Software Development] czarsuperstar@gmail.com:
I know that it's solid. Others have used my source tree to make a recovery and no problem. I have built from bootable recovery 5.1,6.0,and 7.0 so I know that it's solid. It is the same as the LG Leon LTE except that it is a msm8909 kernel. It's just that without the phone I can't implement certain features like the on5 has. K7 is using tuxera.sh which supports NTFS,EXFAT and other things but I have been having problems downloading omni 6.0 which would help me out a lot. I have tried to build the on5 recovery and it's missing something so it would not compile. So I was just wondering. Thanks for the help. Czarsuperstar

---------- Post added at 05:20 PM ---------- Previous post was at 05:07 PM ----------

http://androidforums.com/threads/twrp-for-lg-k7-m1-from-source.1056107/

http://xdaforums.com/android/development/twrp-m1-lg-k7-t3462130

Testers of the last image created for stable use

That was just the last image all together 4,000 downloads.
[Android Software Development] czarsuperstar@gmail.com:
And that is only after 4 weeks from last Stable release.

More photos of downloads of previous versions. Hope this provides an insight into the development of this phone. Thanks.
[Android Software Development] MSF Jarvis:
[MENTION=2892269]czarsuperstar@gmail.com[/MENTION] I fail to see what the motive is to show off 4k downloads of your TWRP builds here. If you need it to be made official, you HAVE to follow the process everyone else is following, any gripes you have with the current system are better off reported directly to the team
[Android Software Development] czarsuperstar@gmail.com:
The point is this: I have followed procedures. So to make sure this is getting seen by a member of the team. Check some pages back. Biggbiff sent me an email to correct the sources naming (TWRP K7 aka M1 to android device lge m1) . I see phones releasing after this phone and have received official support. So I put it in Team Win Recovery Project's Thread. Hope this provides a relivent answer.

---------- Post added at 11:42 AM ---------- Previous post was at 11:32 AM ----------

I've been a member of XDA for 6 years and have contributed to many devices. I was the first to put flash player lite on the Moto Cliq on eclair 2.1 so I am not new to the scene. I just want what everyone else is receiving: support. I have the on5 and tried to complie for it but it doesn't build on 5.1 so how can a recovery that doesn't build on Omni 5.1 can received official support but not the K7? I have videos on YouTube making the recovery not a repackaged kernel and recovery ramdisk like the first betas to be released.

Edit: as of this morning I compiled same device tree on Omni Rom 6.0 and it builds so my device is compilable on OR 5.1 and 6.0 so I know that my device tree is solid.
[Android Software Development] czarsuperstar@gmail.com:
I was able to complie for the on5 using Omni Rom 6.0. 1 question is why is it a yellowish orange color? The png is blue when I look at the contents of twres but yellowish orange when flashed.

---------- Post added at 01:35 PM ---------- Previous post was at 01:30 PM ----------

This is the email:
[Android Software Development] ashyx:
Because you're using the wrong pixel format.
[Android Software Development] czarsuperstar@gmail.com:
I used the TWRP device tree straight from TWRP so I can find the pixel format from a recovery logs? On it now. Thanks

---------- Post added at 04:39 PM ---------- Previous post was at 04:12 PM ----------

http://pastebin.com/mwKK0fgg

Is the recovery log. All I did was add the device tree from Team Win Recovery Project so I guess this would be a issue to resolve(not a major one but affects the theming).
[Android Software Development] ashyx:
Try commenting out the pixel format, on some devices TWRP can grab the correct pixel format.

If not and its a recent device try:

TARGET_RECOVERY_PIXEL_FORMAT := ABGR_8888
[Android Software Development] czarsuperstar@gmail.com:
It's not added in I am building it now in matter of fact it's finished after flashing I will let you know what I added in.?

Edit: I am going to add what you told me so I can fix the color.

---------- Post added at 05:25 PM ---------- Previous post was at 05:05 PM ----------

You are the truth. Adding that to the BoardConfig.mk worked TWRP is blue and themes are accurate.???. Thanks so much for your help on this matter. I will let the maintainer know.
[Android Software Development] czarsuperstar@gmail.com:
Another Question. I added the ABGR_8888 and when I boot into recovery it's blue, but taking screenshots of the recovery it's still the yellowish orange hue how can that be. I have never seen that before or is it just me.?
[Android Software Development] izi501:
Hello everybody,

First I'd like to thank the dev for his amazing work :) This recovery is very useful and has a lot more features than CWM for my phone.

I'm trying to build twrp 2.7 but I get an error : the recovery partition is too large. I enabled every build option I could find to reduce the size of the recovery, but I still have a file too big. Do you have an advice about how I could reduce again the size ? The file should finally be around 4 MB.

Thanks in advance, sorry if this question has already been replied, my seearch didn't give any good result.

What is the URL of the topic in which you asked this question ? I'm curious to know how to use a better compression option for kernel :)
[Android Software Development] HowardZ:
My bad - it was not a forum, it was a twrp chat room.

The advise was to change from gzip to using or XZ compressioni for the kernel.

However, I think the offical CM10.2 for deb is using no kernel compression whatsoever.

Kernels come with config files which are created via "make menuconfig" (of which I am not familiar).

So, I edited the config file for the kernel I was using and it now looks like this:]

CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_HAVE_KERNEL_XZ=y
CONFIG_HAVE_KERNEL_LZO=y
# CONFIG_KERNEL_GZIP=y # ************ this line commented out by HZ
# CONFIG_KERNEL_LZMA is not set
# ******************** following line restored by HZ
CONFIG_KERNEL_XZ=y

First of all CM10.2 for deb device was using a totally different config file which was shorter and did NOT look like it was generated by "make menuconfig" and did not have any of these kernel compression options in it. I used a different config file which looked modifyable and had deb in its filename.

A purist, like the person in the TWRP chat room, never edits the config file, but instead runs make menuconfig.

In my case it was a small easy edit.

Using XZ compression solved the kernel being too large. I think the error was with the kernel having no compression whatsoever, as I saw no such options in the kernel config file being used by the official CM10.2 build for deb.

Anyways, I hope this helps you.

Remember I am a real beginner in all of this.

Regards,

Howard
[Android Software Development] Android-Andi:
Hey together! Hey [MENTION=912474]Dees_Troy[/MENTION] !

Can someone tell me if i need to do all the setup for P5100 and P5110? CM10.2 is synced to my PC. Both haveing official TWRP 2.6.3.0 but i need the latest version to flash KitKat Roms...

Can someone guide me on how to set it up for P3100 and P3110? I have unofficial TWRP 2.6.3.0 for both. Based on P5100 and P5110 TWRP :D

Is there an easy way? can i copy and paste init.rc, recovery.fstab, drivers.so and build.prop from this? i allready have an extra recovery-kernel to use with unofficial TWRP.

Kind regards

Andi

---------- Post added at 05:09 PM ---------- Previous post was at 05:05 PM ----------

(i build my first CWM today, i am really new with all that stuff :p )
[Android Software Development] Android-Andi:
i got it working 1 time... but i can´t build it again :(

i got 2.6.3.0 .... but can´t flash KitKat :(

anybody knows how to get 2.6.3.3 or newer ? i used this https://github.com/TeamWin/Team-Win-Recovery-Project/tree/twrp2.7 to replace android/system//bootable/recovery
[Android Software Development] gr8nole:
Colors partially inverted

[MENTION=912474]Dees_Troy[/MENTION] or anyone else

I have compiled a working version of 2.6.3.0 (using CM10.2 and source from link in OP) but have one issue I can't figure out. The red and blue colors seem to be switched. All of the colors that should be blue look light orange instead.

I have tried both of these flags with no change (one at a time):

TARGET_RECOVERY_PIXEL_FORMAT := "BGRA_8888"

TARGET_RECOVERY_PIXEL_FORMAT := "RGBX_8888"

I have also tried with neither flag. When neither flag is present it starts in 565 mode. The colors look correct in the CWM recovery I built.

From my last_log I see:

Starting the UI...Pixel format: 1024x600 @ 32bpp

Pixel format: BGRA_8888

I have no more ideas how to fix this.

Samsung Galaxy Tab 3 (7 in Wifi only SM-T210R).

Thanks for your time.
[Android Software Development] Silesh.Nair:
Can anyone point me to a full list of twrp flags that I can use on 2.7 or earlier.
[Android Software Development] Android-Andi:
Can someone tell me howto compile Android 4.4 compatible TWRP?
[Android Software Development] Silesh.Nair:
build using twrp2.7 branch.

I just compiled mine without issues.
[Android Software Development] Android-Andi:
i tried it some days ago but i got error while flashing CM11... i got something like "set_metadata_recursive: some changes failed" ... using CWM 6.0.4.5 worked.
[Android Software Development] ferhung:
About recovery.fstab for CM-10.2/11.0 & android 4.3/4.4

“Note that TWRP does not currently support the "fstab 2" version of fstab files seen in AOSP 4.3 / CM10.2. You will still need to use the "old" format of fstab for TWRP. To maximize TWRP's compatibility with your build tree, you can create a twrp.fstab and use PRODUCT_COPY_FILES to place the file in /etc/twrp.fstab When TWRP boots, if it finds a twrp.fstab in the ramdisk it will rename /etc/recovery.fstab to /etc/recovery.fstab.bak and then rename /etc/twrp.fstab to /etc/recovery.fstab. Effectively this will "replace" the fstab 2 file that your device files are providing with the TWRP fstab allowing you to maintain compatibility within your device files and with other recoveries.”

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

About recovery.fstab for CM-10.2/11.0 & android 4.3/4.4, can you get more information? I build it for cm-11.0, but the twrp didn't work~~~
[Android Software Development] Android-Andi:
i tryed again to compile for P3110 (Galaxy Tab 2 7.0)... i can only build TWRP 2.6.3.0 ... using CM 11 tree as base ... and CM10.2 as base... can flash KitKat Roms... am i doing something wrong? how to get latest KitKat-Compatible TWRP 2.6.3.3 (or whatever) ?

Is there a new build-flag to get KitKat-Support?

Any idea [MENTION=912474]Dees_Troy[/MENTION] ? If not maybe you can update P5100 and P5110 (official supported by TWRP) ? I can patch this builds to make them work on P3100 and P3110 :p :D
[Android Software Development] Dees_Troy:
I added this to the guide today:

Notes about 4.4 Kit Kat ROMs and SELinux

There's absolutely no SELinux support in ICS trees or older. libselinux is not included in these trees and some dependencies for libselinux don't exist elsewhere in these older trees so there's no way to get SELinux support unless you move to a newer tree. I recommend using a 4.3 based tree or higher.

SELinux support is included in all builds of TWRP so long as you build in a tree that has libselinux present. However, for SELinux support to work, your kernel must support it as well. If you're using an older kernel, your TWRP won't support SELinux and you will get errors when installing 4.4 Kit Kat ROMs due to set_metadata not being able to set SELinux contexts. You'll see an error in the recovery log stating something along the lines of "Operation not supported on transport endpoint." This means you need to add SELinux support to the kernel you are using in recovery. (Yes, at least in most cases, recovery has its own kernel.)
[Android Software Development] Android-Andi:
i used CM10.2 (official tree) and CM11 (unofficial device tree) as base... it´s working... but only TWRP 2.6.3.0 without kitkat support... how to get a newer version of TWRP? I have seen 2.6.3.3 and higher for other devices.
[Android Software Development] Dees_Troy:
The fourth/last digit of our version number is reserved for device specific updates that usually don't involve code updates to TWRP. For example, a device specific update might include changing the kernel in the recovery image to one that supports SELinux. The problems with installing Kit Kat ROMs were related to the kernel in the recovery image not supporting the ability to read & write SELinux contexts on ext4 file systems.
[Android Software Development] Android-Andi:
Ok i´ll try again with "stock" cm recovery kernel... maybe the "old" kernel is the reason for not working... i replaced the kernel... i hope i get the touch working without changeing the kernel :/

Do you know how i can set the kernel config to build the touchscreen driver as a module? Can you guide me?

(I would if i can but:

)
[Android Software Development] gr8nole:
Did you try the flags in the OP that flip the touches?

Sent from my DROID RAZR MAXX HD
[Android Software Development] Android-Andi:
where do i have to place twrp.fstab on my pc (source at /Home/user/android/system)

And how to link in buildflag (PRODUCT_COPY_FILES := ???) ?

only thing thats missing ;)

---------- Post added at 06:11 AM ---------- Previous post was at 06:10 AM ----------

you Saved my day :)
[Android Software Development] gr8nole:
Look in your device.mk and see if there are any "PRODUCT_COPY_FILES" that you can reference.

Basically, it looks like you just separate the source and destination by using a colon. It shouldn't matter where the file is located as long as you point to it correctly in the COPY.
[Android Software Development] FateNozomi:
When my twrp boots up, it doesn't mount anything, can't even wipe data/factory reset. As for the recovery.fstab, I have no idea how to do it as i can't find PRODUCT_COPY_FILES in my device.mk file. Any ideas how to fix it? >.< Sorry for this noob question, thanks in advanced.
[Android Software Development] ashyx:
It maybe worth trying BGRA_8888
[Android Software Development] czarsuperstar@gmail.com:
I am going to try that but I don't get it. Would that be a camera problem? Just wondering for developing purposes.
[Android Software Development] ashyx:
Camera? No its nothing to do with the camera.

It's what twrp is grabbing from the framebuffer.
[Android Software Development] czarsuperstar@gmail.com:
It didn't work. The change to B made it yellowish orange hue but it turns blue just before it shuts off. So I changed it back to A. I am satisfied with the results. Thanks for your help.
[Android Software Development] batoussai:
So what if after compiling without errors I get a recovery Image that doesn't boot nor gives me a working console for debugging?
[Android Software Development] Startrek852:
First off, make sure you always compile TWRP as eng, not userdebug. And if it doesn't boot, plug it into a computer and use that for debugging.
[Android Software Development] ashyx:
You need to specify what 'doesn't boot' means.

It may just be a blank screen.

Look in cache/recovery/last_log to see if the recovery log was created.
[Android Software Development] batoussai:
Well, guess I started wrong then. Pretty sure I compiled it as userdebug.

Thanks.

It leaves me hanging on the manufacturer logo for some minutes and then automatically reboots to android.

Will take a look if there's a log in there.

Thanks.
[Android Software Development] ka_putt:
hello everybody,

I have an issue, my compiled TWRP can not found any partitions and I don't know what went wrong. I made few pics,

maybe someone have a solution for me.
[Android Software Development] zainifame:
where's your source?
[Android Software Development] ka_putt:
still on my pc... at moment I am just trying to compile and get it working, also no sources...
[Android Software Development] zainifame:
i mean device tree?, if u didn't have so i cant help
[Android Software Development] ashyx:
You're trying to use the stock recovery.fstab in twrp?
[Android Software Development] ka_putt:
yes I understood what are you meaning. I can upload device.mk and boadconfig.mk or comeplete folger as zip

no I don't used it. I took from kiwi(honor) because recovery from kiwi worked good, but it is not original one for my device Mediapad T2
[Android Software Development] ashyx:
Well it looks to me like a stock recovery.fstab because the format is incorrect.

Post it up.
[Android Software Development] ka_putt:
it's strange, i can not upload my device tree as zip or tar...

Edit

link to file

https://drive.google.com/open?id=0B0MqC_6mOlloTzBMOHpTN1MxVjA
[Android Software Development] zainifame:
like [MENTION=4899305]ashyx[/MENTION] said seems like u'r using fstab.qcom(recovery not using this fstab format), i saw on your boardconfig.mk try to replace with this and build again or just unpack .img and replace fstab

TARGET_RECOVERY_FSTAB := $(DEVICE_PATH)/recovery/etc/twrp.fstab
[Android Software Development] ka_putt:
thank you! It worked :)
[Android Software Development] zainifame:
u'r wellcome, is your twrp build still showing error?
[Android Software Development] ka_putt:
also at moment looks good, rest of functions i gonna test tomorrow
[Android Software Development] ashyx:
He has recovery.fstab >> stock fstab

and

twrp.fstab >> correct fstab

both in recovery/etc

Using the path made twrp use the correct one.
[Android Software Development] SdtBarbarossa:
maybe a kernel panic... may a look to lastkernel_msg is worth
[Android Software Development] TimSchumi:
I have a problem with TWRP from branch android-6.0 in omnirom sources (Should be 3.0.2). Nearly everything works fine, but if I wipe any partition (even if I wipe just one), every partition will fail to mount due to "Invalid Argument". It is only fixed by flashing back old TWRP (also unofficial but stable) through Download Mode and then flashing the ROM again through the old TWRP. This can be bypassed by selecting "Do rm -rf instead of wiping" in Settings, but it would be good if I get it fixed.

Short: Everything works, even Mounting. But after I wiped any partition, ALL partitions fail to mount due to "Invalid Argument"

Device tree: http://www.github.com/SiniTurk/android_device_samsung_cs02/tree/twrp-6.0
[Android Software Development] pvineeth97:
Where do I need to put this line?

PRODUCT_COPY_FILES += device/lge/hammerhead/twrp.fstab:recovery/root/etc/twrp.fstab

What should I add in twrp.fstab?
[Android Software Development] ashyx:
You don't really need that line. If you're just building for twrp just put the fstab in the device folder or create root/etc in the device folder and put the fstab in etc folder.

Any thing in the root folder will be automatically included.

TWRP.fstab needs your device partition mount paths.