yashsingh1/xdaforums huggingface dataset:
[Android Software Development] vuvkar:
hey guys, after succesful compiling and installing, the phone keeps restarting, and can't enter recovery, Is there any way to get logs?

here's the last lines of compiling

cp: cannot stat ‘/home/vuvkar/android/system/out/target/product/vivo/root/init.recovery.*.rc’: No such file or directory

----- Making uncompressed recovery ramdisk ------

----- Making compressed recovery ramdisk ------

----- Making recovery image ------

Made recovery image: /home/vuvkar/android/system/out/target/product/vivo/recovery.img

#### make completed successfully (20:37 (mm:ss)) ####
[Android Software Development] Android-Andi:
It only says you don't have a init.recovery.*.rc inside your device trees root dir, not every device need one.

If you have a init.recovery.*.rc inside a common tree you need to place it inside device/MANUFACTURE/COMMONDEVICE/recovery/root and define your common tree using TARGET_RECOVERY_DEVICE_DIRS flag.

(it defaults to

TARGET_RECOVERY_DEVICE_DIRS := $(TARGET_DEVICE_DIR)/recovery/root

If TARGET_RECOVERY_DEVICE_DIRS is not defined).

For reference: https://github.com/omnirom/android_...mmit/159b3f36170ae2ed7cfaf30b0cb96674aace149e

You have adb access?

If yes:

Try adb shell dmesg to check if it's an kernel issue.

Try adb pull /tmp/recovery.log

Gesendet von meinem LG-H815 mit Tapatalk

Edit:

Make sure your kernel is compatible with M if you compile inside omni 6 source. On my first twrp on 6.0 i forgot some selinux commits needed for M on my kernel which prevent twrp from booting.
[Android Software Development] _that:
You can try rebooting to Android and read /proc/last_kmsg (or /sys/fs/pstore/console-ramoops on newer kernels) - it should contain the previous kernel log (if the kernel did start at all).

Generally, if you can't even boot the kernel and don't get adb access, that's a device-specific problem with your kernel, dtb, boot image format, or init configuration - all those early boot issues are not really related to TWRP. Debugging tactics include reading the kernel log (see above), unpacking the boot image and comparing it with known working ones, and mixing different parts of your boot image with the known working one and manually repacking for testing.
[Android Software Development] vuvkar:
Ok, thank guys
[Android Software Development] Slimegod:
Anyone can help me out with this :what::what:
[Android Software Development] Android-Andi:
error might happen before the output you posted

Gesendet von meinem LG-H815 mit Tapatalk
[Android Software Development] Slimegod:
I'll do another build and see thanks:thumbup:

Edit : is this a recovery issue https://pastebin.com/xM095vVQ. I think it is but I'm not sure on how to fix it.

Edit 2: problem got fixed.
[Android Software Development] boa19861105:
This is how the problem?

Which would you like? [aosp_arm-eng] 17

WARNING: Trying to fetch a device that's already there

Traceback (most recent call last):

File "build/tools/roomservice.py", line 312, in <module>

fetch_dependencies(device)

File "build/tools/roomservice.py", line 268, in fetch_dependencies

fetch_device(device)

File "build/tools/roomservice.py", line 280, in fetch_device

git_data = search_gerrit_for_device(device)

File "build/tools/roomservice.py", line 78, in search_gerrit_for_device

device_data = check_repo_exists(git_data, device)

File "build/tools/roomservice.py", line 58, in check_repo_exists

"exiting roomservice".format(device=device))

Exception: hima not found,exiting roomservice
[Android Software Development] russel5:
Thanks for your answer, i'm find the solutions.

All problem was in /external/sepolicy/init.te file
[Android Software Development] beroid:
how solve this error?

target asm: libpng <= external/libpng/arm/filter_neon.S
clang: error: unknown argument: '-fpredictive-commoning'
clang: error: unknown argument: '-ftree-loop-vectorize'
clang: error: unknown argument: '-ftree-partial-pre'
clang: error: unknown argument: '-fipa-cp-clone'
make: *** [/home/alex/Workspace/Android/out/target/product/v500/obj/SHARED_LIBRARIES/libpng_intermediates/arm/filter_neon.o] Error 1
[Android Software Development] #Vangreen:
Where I can find source to compile twrp 3.0 ? I try with omni source but its compile old 2.8.7.0 :/
[Android Software Development] _that:
Yes it's normal on some devices, but it's a bug (a race condition between init and the recovery). We should wait for a reasonable time until init creates the device node.

For that effect I blame the kernel until someone comes up with a better explanation. :) You could try reading the values that we are displaying directly from the kernel's sysfs to verify (files in /sys/class/power_supply/battery/)
[Android Software Development] _that:
Use the android-6.0 branch of bootable/recovery - it's compatible with Omni 4.4 to 6.0.
[Android Software Development] #Vangreen:
thx but how change brunch only on this folder ?

EDIT

Never mind :D thx
[Android Software Development] cognitive:
https://github.com/TeamWin/Team-Win-Recovery-Project
[Android Software Development] MSF Jarvis:
Processor ?? Chipset?? Device Tree link?? Some good dev as maintainer??

Fulfill these requirements and we have a deal
[Android Software Development] Android-Andi:
I think you read the OP and Thread title?

Gesendet von meinem LG-H815 mit Tapatalk
[Android Software Development] rockalber:
Am sorry but no one helping us
[Android Software Development] rockalber:
Am attaching some screen shots
[Android Software Development] MSF Jarvis:
Device tree?? Developer ??
[Android Software Development] #Vangreen:
When i change it, repo synk and compile this is still the same old recovery :/

TT || LG F70

Never mind, my bad. Tuż for awsome work, recovery works :D
[Android Software Development] rockalber:
Our device didn't have developer
[Android Software Development] MSF Jarvis:
So sad. No recovery for you then. Unless you send the device to [MENTION=912474]Dees_Troy[/MENTION] or [MENTION=2638973]bigbiff[/MENTION] or [MENTION=4878287]_that[/MENTION] . Even then there's no guarantees that they'll build TWRP for your device.
[Android Software Development] rockalber:
Ok thanks for your time
[Android Software Development] Mr,bluwe:
Why we can't have unless we send the device? I can be a tester if they want..

Sent from my GALAXY Core Prime VE (G361H)..
[Android Software Development] kodein:
xz3c

Pls compile twrp 3.0 for xperia z3c. thnk
[Android Software Development] MSF Jarvis:
Well, [MENTION=912474]Dees_Troy[/MENTION] hates remote testers, and for good reason. Most are n00bs (No offence intented), and make debugging a hard job. Even more cant use IRC or even basic adb shell commands to report stuff and grab logs respectively. So no, I am almost sure this device is not getting official TWRP anytime soon.

---------- Post added at 02:48 PM ---------- Previous post was at 02:45 PM ----------

This is a "Compile **** yourself" thread, not a "I'm so n00b, make me a recovery please" thread. Everyone stop whining.

P.S. [MENTION=912474]Dees_Troy[/MENTION], I think you should start reporting in these posts now. Too many of these guys are popping up here.
[Android Software Development] MSF Jarvis:
I'm switching over to my laptop right now. Let it Rip!!!!!
[Android Software Development] Slimegod:
Is there a way to fix this? I'm not familiar with it and Google isn't helping http://pastebin.com/Y33VCMkP
[Android Software Development] vuvkar:
Can, you just little explain what commits in Selinux, As my kernel doesn't start at all :/
[Android Software Development] MSF Jarvis:
Why doesn't this seem like a mka recoveryimage output log?? Are you sure you were building *only* the recovery??
[Android Software Development] Slimegod:
I'm building my recovery within my build. Kernel and recovery included. I think this error was before the kernel build.
[Android Software Development] MSF Jarvis:
Then this is not the right place to ask these questions. This thread only provides help about building TWRP recovery, and audio or decidedly non-TWRP stuff.
[Android Software Development] SlimShady's:
Does anyone know how to fix this?

http://hastebin.com/ilejahexol.hs

I'm having it while compiling TWRP :(
[Android Software Development] Android-Andi:
I can only tell for 3.0 kernel:

https://github.com/SlimRoms/kernel_samsung_espresso10/commits/mm6.0/security

I merged them on 30.01., but check if you miss some older too.

If you have a different kernel version you should check different kernel source.

Gesendet von meinem LG-H815 mit Tapatalk
[Android Software Development] jerdog:
Boys, boys - you're both pretty. Keep it on topic, which is specifically about "how to compile TWRP touch recovery" or else you'll find yourselves with some free time on your hands outside of XDA, mmk?
[Android Software Development] yuweng:
And i was wondering why still some of the OT like this one was not removed except for my Master Shifu's _that, i guess the MOD cannot see you're a RD/ RC thru pm & your contributions towards TWRP, the OP is already less active here on XDA...

Don't leave us, we still need your expertise/ advice here... May be should highlight the OT post is this & this & this then the MOD wouldn't make a mistake next time... :cowboy:
[Android Software Development] MSF Jarvis:
Please tell me which tree are you compiling in. If its Omni 6.0, try using Omni 4.4 and twrp's android-6.0 branch.

You need the XDA account as well buddy. [MENTION=487859]jerdog[/MENTION] is super pissed off at us, I already got a warning for sympathising with [MENTION=4878287]_that[/MENTION].
[Android Software Development] SlimShady's:
Yes. I use Omni 6.0 branch.

Inviato dal mio LG-D405n utilizzando Tapatalk
[Android Software Development] MSF Jarvis:
Most devices are being built by TWRP in the setup I described earlier, so I would recommend swithching to that.
[Android Software Development] vuvkar:
TWRP

Hey guys I could finaly compile and run recovery, Now it starts and I have smth like that, pink and very small :/
[Android Software Development] MSF Jarvis:
Seems like an issue with the colorspace. There is a list on the first post, try switching between them. One of them will definitely work
[Android Software Development] vuvkar:
Already tried, but the problem is still there :/
[Android Software Development] MSF Jarvis:
Tried the linelength flag??
[Android Software Development] vuvkar:
No will try and report
[Android Software Development] DarkFrenzy:
this is not working: ro.sf.hwrotation=270

where to add that line ?

in my rom build.prop if a remove that line, screen will be in landscape and the touch will be weird.

and in twrp recovery this is same screen is in landscape and if i touch install , wipe is touched. how to fix this

which files in ramdisk/sbin/ is responsible for touch
[Android Software Development] Android-Andi:
[MENTION=5706443]DarkFrenzy[/MENTION] you need to put the touchscreen driver in landscape mode by default or use sysfs in init.recovery.rc

Example from tab2: https://github.com/omnirom/android_...d-5.1/recovery/root/init.recovery.espresso.rc

https://github.com/omnirom/android_...mmit/8b6bac9e34645aaac5adae780eed7d3a09c7f9df

Gesendet von meinem LG-H815 mit Tapatalk
[Android Software Development] DarkFrenzy:
thanks. but thats while building. i m trying to solve in ramdisk. unpacking the recovery.img.

is these to enough to build twrp

https://github.com/TeamWin/android_device_samsung_lt02ltetmo

https://github.com/TeamWin/kernel_samsung_lt02ltetmo

my diskspace is very low at the movement so i hope no need of a huge source to build. i m having 20gb free.

---------- Post added at 10:38 AM ---------- Previous post was at 10:28 AM ----------

is this possible through ramdisk folder. i have these files init.rc, init.recovery.qcom , init.recovery.usb.rc ueventd.qcom.rc, ueventd.rc

or

can i build twrp using only these two

https://github.com/TeamWin/android_device_samsung_lt02ltetmo

https://github.com/TeamWin/kernel_samsung_lt02ltetmo
[Android Software Development] Android-Andi:
You have a sysfs to control touch orienration? If not you need to add it. Or maybe you have a config option for it in touch driver?

If you have a sysfs It's an 2 line change in ramdisk, else you have at least to compile a new zImage after making needed changes.

Gesendet von meinem LG-H815 mit Tapatalk

Edit:

Not sure if those are present in latest twrp source https://github.com/TeamWin/android_device_samsung_lt02ltetmo/blob/android-4.4/BoardConfig.mk#L49+l50

Might be the source of your issue. Totally forgot about this flags[emoji14]maybe it need to be recompiled completely...
[Android Software Development] DarkFrenzy:
I was trying to port the latest twrp 3 from s4 mini to tab 3 7.0 sprint, both device resolution is different thats why the touch issues are there.

I know building kernels,but dont know to build recovery.

Is those two enough for building twrp
[Android Software Development] ktempleton:
Well that would be cool but I'm trying to include this in my ROM I'm building for the d710 using the repo from Team-Hydra on github thanks for your help

Also ATM I'm trying to plug this into my AOKP build
[Android Software Development] ktempleton:
You need the device d710 the galaxys2common also need the vendor files hardware samsung those i believe are the needed repos
[Android Software Development] chinajjb:
well ,what's the line of code ?
[Android Software Development] ktempleton:
I would go to the d710 folder and find the full d710 mk find where it calls that file and remove the reference

---------- Post added at 09:57 PM ---------- Previous post was at 09:39 PM ----------

Or you can use the frameworks base from team hydra

Scratch that i would just remove it from the mk file
[Android Software Development] chinajjb:
here is what I am getting now:

target Export Resources: framework-res (/home/jjb/android/cm/out/target/common/obj/APPS/framework-res_intermediates/package-export.apk)

host StaticLib: libLLVMCore (/home/jjb/android/cm/out/host/linux-x86/obj/STATIC_LIBRARIES/libLLVMCore_intermediates/libLLVMCore.a)

libpng warning: Ignoring attempt to set cHRM RGB triangle with zero area

libpng warning: Ignoring attempt to set cHRM RGB triangle with zero area

Copying: /home/jjb/android/cm/out/target/common/obj/JAVA_LIBRARIES/core_intermediates/noproguard.classes.dex

target Jar: core (/home/jjb/android/cm/out/target/common/obj/JAVA_LIBRARIES/core_intermediates/javalib.jar)

'/home/jjb/android/cm/out/target/common/obj/JAVA_LIBRARIES/core_intermediates/classes.dex' as 'classes.dex'...

target Java: core-junit (/home/jjb/android/cm/out/target/common/obj/JAVA_LIBRARIES/core-junit_intermediates/classes)

target Java: ext (/home/jjb/android/cm/out/target/common/obj/JAVA_LIBRARIES/ext_intermediates/classes)

target Java: bouncycastle (/home/jjb/android/cm/out/target/common/obj/JAVA_LIBRARIES/bouncycastle_intermediates/classes)

Copying: /home/jjb/android/cm/out/target/common/obj/JAVA_LIBRARIES/core-junit_intermediates/classes-jarjar.jar

Copying: /home/jjb/android/cm/out/target/common/obj/JAVA_LIBRARIES/core-junit_intermediates/emma_out/lib/classes-jarjar.jar

Copying: /home/jjb/android/cm/out/target/common/obj/JAVA_LIBRARIES/core-junit_intermediates/classes.jar

Copying: /home/jjb/android/cm/out/target/common/obj/JAVA_LIBRARIES/core-junit_intermediates/noproguard.classes.jar

target Dex: core-junit

Copying: /home/jjb/android/cm/out/target/common/obj/JAVA_LIBRARIES/core-junit_intermediates/noproguard.classes.dex

target Jar: core-junit (/home/jjb/android/cm/out/target/common/obj/JAVA_LIBRARIES/core-junit_intermediates/javalib.jar)

'/home/jjb/android/cm/out/target/common/obj/JAVA_LIBRARIES/core-junit_intermediates/classes.dex' as 'classes.dex'...

device/samsung/d710/overlay/frameworks/base/core/res/res/values/config.xml:52: error: Resource at config_networkLocationProvider appears in overlay but not in the base package; use <add-resource> to add.

device/samsung/d710/overlay/frameworks/base/core/res/res/values/config.xml:55: error: Resource at config_geocodeProvider appears in overlay but not in the base package; use <add-resource> to add.

device/samsung/d710/overlay/frameworks/base/core/res/res/values/config.xml:98: error: Resource at config_autoBrightnessButtonKeyboard appears in overlay but not in the base package; use <add-resource> to add.

make: *** [/home/jjb/android/cm/out/target/common/obj/APPS/framework-res_intermediates/package-export.apk] 错误 1

make: *** 正在删除文件“/home/jjb/android/cm/out/target/common/obj/APPS/framework-res_intermediates/package-export.apk”

make: *** 正在等待未完成的任务....

注意：某些输入文件使用或覆盖了已过时的 API。

注意：要了解详细信息，请使用 -Xlint:deprecation 重新编译。

注意：某些输入文件使用了未经检查或不安全的操作。

注意：要了解详细信息，请使用 -Xlint:unchecked 重新编译。

注意：某些输入文件使用或覆盖了已过时的 API。

注意：要了解详细信息，请使用 -Xlint:deprecation 重新编译。

注意：某些输入文件使用了未经检查或不安全的操作。

注意：要了解详细信息，请使用 -Xlint:unchecked 重新编译。

build error!

I am so sorry that nothing else can help you further!!
[Android Software Development] ktempleton:
since your not building for the rom you can just delete the overlay folder from the d710 device folder
[Android Software Development] chinajjb:
yeah,you are right!!:good:

I got the recovery,img just now ,let me upload it!

hope it can help you,but be aware that my cm source is 10.1 .not cm9.0 !

because there's "For building TWRP for d710 in CM9 -- use ramdisk only and install using injecttwrp " at https://github.com/TeamWin/device_samsung_d710
[Android Software Development] ktempleton:
sweet

link?

thanks my man im runing 4.2 did you use the device tree from team win? i just added the flags to team hydras device tree im not sure cm 9 tree would even build on 10.1 source...
[Android Software Development] chinajjb:
done!

I am so sorry that I know nothing about device tree ,I just downloaded the needed file from https://github.com/TeamWin/device_samsung_d710 ,and remove that "frameworks/base/build/phone-hdpi-512-dalvik-heap.mk" and another line(forgot what it is) in d710.mk!that's all
[Android Software Development] ktempleton:
ok now the one you uploaded is 7 mb but the one in the twrp zip i have is 2.2thats quite a difference also in the zip i have its named ramdisk-recovery.img i think im missing something am i?thanks again
[Android Software Development] chinajjb:
here is all what I got by compiling ,you can check it out,I am actually a noob on android system and compiling,so I can not explain how it comes!:o

http://www.kuaipan.cn/file/id_30708260252157863.htm
[Android Software Development] ktempleton:
This is funny I can't read that site and can't figure out how to download lol what I need is the one that says ramdisk-recovery.img should be a little but bigger than 2mb
[Android Software Development] chinajjb:
here it is!
[Android Software Development] ktempleton:
OK that's what I needed thanks my man I don't know why it won't build in my ROM but at least this way I can put it up on my thread for the people to use I hit your thanks button a few times
[Android Software Development] chinajjb:
hey ,ktempleton

here is the file you want ,2.4.4.0 !good luck!
[Android Software Development] ktempleton:
You are the man thanks alot:D
[Android Software Development] rnovino:
Video Tutorial

Hi guys can any one link a tutorial on how to compile a twrp from scratch/source , coz I have search a tons of tutorials here in xda and even on other sites but the tutorials are not in detail form :( hopefully someone can link a good detailed tutorial it can be in any form of video or article thanks in advance
[Android Software Development] Ozadroid:
Here you go..

http://xdaforums.com/showthread.php?t=1943625

:banghead:
[Android Software Development] Dees_Troy:
Please don't take this the wrong way, but if you need step-by-step directions or you're asking for a video tutorial then you're simply not ready for this.

From a high-level, you'll need a Linux environment to compile in (virtual machine works too) and all of the things needed to compile CM from source. There are already other guides out there for these things and I made no attempt to rewrite or document those things here short of a link to a guide in the CM wiki. Once you get past those steps then you can come back to this guide.
[Android Software Development] Android-Andi:
It's simple if you have an official twrp or omni device and kernel tree.

You can sync omni source, look at the device tree which version is supported.

Gesendet von meinem LG-H815 mit Tapatalk
[Android Software Development] bigsupersquid:
regarding the htc desire 816 (a5,) which is on the supported list...

when I install twrp 3 from the official links I have no mtp function, while adb works fine.

when I build it the mtp works... the primary difference is the init.recovery.usb.rc being updated to Marshmallow.

should I fork the device tree and push changes to gerrit so it can be fixed upstream? the device still seems pretty popular, especially compared to my old ones.
[Android Software Development] Android-Andi:
Push through gerrit if there is an official twrp or omni device tree

Gesendet von meinem LG-H815 mit Tapatalk
[Android Software Development] NShut:
omnirom 5.1 twrp compile

hello. sorry by my english

i have two bugs (or not?)

1.

if i compile officical repository omnirom 5.1 with make -j3 (j4), rom not compiled with diffrent errors:

one error says

another error

if i make -j1, all compile normaly. maybe i wrote not this theme, but i cant find where write

2

i have sp8830 soc sc7731 platfom, and in twrp source codes:
[Android Software Development] vuvkar:
Using the linelenth didn't help :/ Still help pink 2x TWRP :/
[Android Software Development] MSF Jarvis:
Darn it! Link me the device tree and I'll try and find the issue
[Android Software Development] pug1:
Hi all

Have managed to compile a build that boots. Looks like it was the kernel I was using.

It sits at the twrp splash screen for about 10 seconds then goes to the menu. Is that normal?

As I press reboot system it says 'no os is installed', but there is. I reboot and it boots in to the ROM. Has anyone experienced this?

Thanks
[Android Software Development] Slimegod:
My build fails when flashing using TWRP 2.8.7.0, here's my log http://pastebin.com/sNaKJAfg. According to my log its not recognizing my system partitions and I'm not sure why. My build is OmniROM 4.4.4 and TWRP is built within the source. I thought about using this commit https://gerrit.omnirom.org/#/c/11057/. I'm not sure what that'll do or if it'll fix it.
[Android Software Development] gee one:
I had that issue with the previous version- I just flashed and ignored it. Worse case if there is no OS is that you would end up back in recovery.
[Android Software Development] SergioTeddy:
Need some help building twrp 3.0.0-0 for Wileyfox Storm

I’ve successfully build a twrp 2.8.7.0 and everything works .

But twrp 3.0.0-0, i tried to boot it via fastboot and it booted up perfectly. Now, the problem I’m facing is this: The touch is not working, meaning if I try to click on something, for example "Install" or anything, it just vibrates, nothing else happens, it just does not take me where I want to navigate.
[Android Software Development] NShut:
document twrp options

in document first post

is not work, because source code contain usermrf. edit post please. one symbol, but one build is so long...
[Android Software Development] Startrek852:
Hello, I'm trying to compile TWRP for the Nextbook Ares 8, but I'm getting this error:

collect2: error: ld returned 1 exit status
build/core/executable_internal.mk:79: recipe for target '/home/andrew/android/system/out/target/product/NXA8QC116/obj/EXECUTABLES/toolbox_recovery_intermediates/LINKED/toolbox' failed
make: *** [/home/andrew/android/system/out/target/product/NXA8QC116/obj/EXECUTABLES/toolbox_recovery_intermediates/LINKED/toolbox] Error 1

Any help?
[Android Software Development] bigsupersquid:
Might have to

make clean

ccache -C

and rebuild
[Android Software Development] Startrek852:
I don't use ccache.
[Android Software Development] bigsupersquid:
is a precaution for those who do, like me.

the make clean, will remove all the old linker debris, unless you just started from a clean build anyway. if so, I've got no info based on that log excerpt.