yashsingh1/xdaforums huggingface dataset:
[Android Software Development] vampirefo:
OK, thanks, I build from CM13, and cm12.1. I am going to leave both for now though, my guess only the correct one is active per source.
[Android Software Development] magdeoz:
An expert who can help me with this:

Export includes file: system/core/adb/Android.mk -- /home/magdeoz/omni/out/target/product/condor/obj/EXECUTABLES/adbd_intermediates/export_includes
Notice file: system/core/adb/NOTICE -- /home/magdeoz/omni/out/target/product/condor/obj/NOTICE_FILES/src//root/sbin/adbd.txt
make: *** No rule to make target `/home/magdeoz/omni/out/target/product/condor/obj/STATIC_LIBRARIES/libbatteryservice_intermediates/export_includes', needed by `/home/mag
deoz/omni/out/target/product/condor/obj/EXECUTABLES/healthd_intermediates/import_includes'. Stop.
make: *** Waiting for unfinished jobs....
Notice file: system/core/adb/NOTICE -- /home/magdeoz/omni/out/target/product/condor/obj/NOTICE_FILES/src//system/lib/libadbd.a.txt

#### make failed to build some targets (32 seconds) ####
[Android Software Development] bigsupersquid:
I managed to build twrp 2.8.7.0 in omni 6.0 repo for my htc a5 (desire 816) hoping it would fix the MTP issue with the last official twrp for a5.

So it works nice except that in spite of MTP working and good data transfer over USB cable, I have zero adb function. Device not found and all that jazz. Shows up in lsusb as HTC device.

//edit: duh, my bad. in system.prop,

persist.sys.usb.config=mtp should've been persist.sys.usb.config=mtp,adb
[Android Software Development] cezer kiran:
have anyone developed omnirom for snapdragon 615?? i have devolped successfully twrp for it but while compiling rom im facing somany errors. i referenced oppo r5 device tree it has some caf repos, is it necessary to use caf repos for sd 615 ???
[Android Software Development] AlxMAX:
Hi,

I have tried to build the TWRP recovery for the Nexus 6 (shamu) device. The installed firmware on my phone was CyanogenMod.. First, I have used the omnirom tree. The build went well, but the recovery was not able to mount the user data partition because of the its encryption. Then, I have tried to use the cyanogenmod tree. The build went well, but the recovery was not able to mount any of the phone partitions. Since then, I was able to learn there was a default encryption password used to encrypt the user data. Somehow, there seems to be an error with the password. I have even tried it with no luck. So I have tried to look for differences between files in the CyanogenMod sources and in the OmniROM sources with not so much luck. So I've learnt that TWRP duplicates a cryptfs.c file used for the password setting (there is a copy in omnirom_tree/system/vold and there's another one in omnirom_tree/bootable/recovery/crypto/lollipop). Anyway, I would like to know what files should I modify in order to make the OmniROM based TWRP work with a phone with CyanogenMod.
[Android Software Development] wowanbelousov:
good afternoon!

I want to collect himself manually TWRP tell how to do

I do not know much English

smartphone J500H

Our off-Working http://xdaforums.com/android/development/recovery-twrp-2-8-7-0-samsung-galaxy-j5-t3219901
[Android Software Development] Slimegod:
I'm getting this recovery image error building TWRP https://pastebin.com/DTjRwjmc
[Android Software Development] vampirefo:
It's saying your recovery.img is to big, so either up your recovery size on your boardconfig or reduce size by removing stuff from twrp via flags.
[Android Software Development] sub77:
have a look on this device tree: https://github.com/Tasssadar/android_device_moto_shamu?files=1
[Android Software Development] DJBhardwaj:
Have set up OmniROM tree and trying to build for angler.

Have already added TW_THEME := portrait_hdpi to boardconfig.mk

Please help.
[Android Software Development] lj50036:
You have to lunch for your device .....

Thx Josh
[Android Software Development] DJBhardwaj:
As in, "lunch angler" ?
[Android Software Development] AlxMAX:
Actually you can use the command breakfast angler then you can use mka recoveryimage.

Edit: you can find here a description of the commands defined by envsetup.sh: https://wiki.cyanogenmod.org/w/Envsetup_help
[Android Software Development] DJBhardwaj:
I will try and report ASAP. thank you both for the help.
[Android Software Development] Slimegod:
Getting this flashing error.
[Android Software Development] vampirefo:
That's a rom problem, not a twrp problem.
[Android Software Development] Slimegod:
What is it exactly then just a bad build?
[Android Software Development] T-Macgnolia:
You need to edit your updater-script to only show klte as the message says your recovery is for klte.

T-Macgnolia on Tapatalk
[Android Software Development] vampirefo:
Most likely the update script has stupid childish checks, you would need to remove all these stupid checks.
[Android Software Development] T-Macgnolia:
It is not the updater-script that does the checks. The checks are built into the recovery. The updater-script just prevides the info for the recovery to check against what device info was built into it.

T-Macgnolia on Tapatalk
[Android Software Development] Slimegod:
Correct. My build is a unified build. I've flashed a similar rom that was unified also, same updater.script as mine and flashed with no error.
[Android Software Development] T-Macgnolia:
Yeah I saw it was a unified build frome the screen shot. And I say the last device listed was klte. Your recovery doesn't like something in your META-IF folder. I would compare all the files in that folder with the ones from a ROM that flashed successfully.

T-Macgnolia on Tapatalk
[Android Software Development] vampirefo:
Removing the checks from update script prevents checks period.
[Android Software Development] T-Macgnolia:
LMAO I swear some people crack me up.

T-Macgnolia on Tapatalk
[Android Software Development] vampirefo:
Yep, you that person, it's cool most people like you have no clue what they are talking about.
[Android Software Development] T-Macgnolia:
No you are that person. I havebeen doing ROM development for over 4 years now. I know exactly what I am talking about. Yes the updater script has. A check in the begining but it is to check against the device that the recovery was built for. Or in other words the ro.product.device that was listed in the defualt.prop when it was compiled. Also yes you can remove the asserts check from the updater-script but that only keeps it from checking against what is in the recovery. Also itisstupid to do that cause the checks are there for a reason. And that reason is to try and keep you from screwing up your device. Bit if you want tobe stupid and screw up your device by circumventing the protection in recovery go ahead I mean it is only money right.

T-Macgnolia on Tapatalk
[Android Software Development] vampirefo:
So this boring post is just to say I am right, I knew that already, thanks I guess, now once he removes the checks the rom will then install.
[Android Software Development] Slimegod:
Guys chill out. You all are both right in different ways. More then likely it's a build issue. Did the assert removal and it failed without a message as to why. I removed the checks and it still failed. So it's something within my build. I've done this build before and flashed fine so I'll have to figure it out, thanks :thumbup:
[Android Software Development] T-Macgnolia:
Amazing how your suggestion did not work like I already new it wouldn't. Also amazing how someone trys to help spread knowledge and then someone gets all butt hurt cause the feel like someone was teying to be little them when they were actually trying to help educate them. People like you have made XDA forums a forum that is no longer fun to be on. Grow the heck up and stoptaking stuff personal.

T-Macgnolia on Tapatalk
[Android Software Development] Slimegod:
I tried using the updater-script as you suggested then ran into the initial error. I know i tweaked my BoardConig.mk and added the "Assert" line only to be compatible with my CDMA device, it was set to GSM previously but flashed fine. So it's kinda confusing. That may be it.
[Android Software Development] T-Macgnolia:
That may be it but I am not sure. But just for further knowledge the gsm.mk has been unified to work for CDMA and GSM devices. The cdma.mk is obsolete now that is why all devices call the gsm.mk files in their configuration.

T-Macgnolia on Tapatalk
[Android Software Development] Slimegod:
Interesting. So even if the asserts are GSM devices will it still work for CDMA as well? This is the device tree I'm using https://github.com/elelinux/android_device_samsung_klte_bringup?files=1 configs were tweaked to build for OMNI though.
[Android Software Development] T-Macgnolia:
No the files I was talking about are for APN's. What file are you talking about and where did you make your change.

T-Macgnolia on Tapatalk
[Android Software Development] Slimegod:
I just edited the BoardConfig.mk so it's unified with CDMA. But i think i may have found the issue. The Muppet Repo for my devices Android.mk only targets klte. I may be wrong but I'm just observing all things.
[Android Software Development] T-Macgnolia:
Sorry but I still don't understand what you mean by, "I edited the BoardConfig.mk so it's unified with CDMA." Are you talking about the TARGET_OTA_ASSERT_DEVICE line in your BoardConfig.mk? I myself have never liked the idea of a unified device tree as it tends to create problems. Also where did your device repo originally come from? I don't know what version of Android you are building but CM has more updated device tree for that device I think as CM has 12.1 and 13.0 branches

T-Macgnolia on Tapatalk
[Android Software Development] Slimegod:
Correct "TARGET_OTA_ASSERT_DEVICE". My bad i know i needed clarification. Yeah that link i posted is the device tree I used, cm11. Yeah I've heard unified builds cause problems. I've never built for my device. But the s3 I've build roms for, this one in particular.
[Android Software Development] pug1:
Hi was wondering if anyone can help. I get a successful build but no boot in to recovery. Here is my log as the build finishes.http://hastebin.com/hubafivute.vhdl

I'm on cm12.1 source and have downloaded a tree from github for my device lenovo yoga tab 2. Also replaced bootable/recovery with the said files on #1 post.

Can any one help

Cheers
[Android Software Development] cezer kiran:
make: *** No rule to make target `/home/kiran/source/out/target/product/ferrari/obj_arm/SHARED_LIBRARIES/libcamera_client_intermediates/export_includes', needed by `/home/kiran/source/out/target/product/ferrari/obj_arm/SHARED_LIBRARIES/libandroid_runtime_intermediates/import_includes'. Stop.

guys please help
[Android Software Development] T-Macgnolia:
Sounds like a vendor issue to me.

T-Macgnolia on Tapatalk
[Android Software Development] cezer kiran:
how to resolve that?
[Android Software Development] T-Macgnolia:
Look in your devices vendor folder and see if you have libcamera_client.so. if not add it to you vendor and to the vendor-blobs.mk and your Android.mk in your vendor.

T-Macgnolia on Tapatalk
[Android Software Development] cezer kiran:
well try out
[Android Software Development] cezer kiran:
futher i am facing these errors

target SharedLib: libandroid_runtime_32 (/home/kiran/source/out/target/product/ferrari/obj_arm/SHARED_LIBRARIES/libandroid_runtime_intermediates/LINKED/libandroid_runtime.so)
frameworks/base/core/jni/android_media_AudioRecord.cpp:243: error: undefined reference to 'android::AudioRecord::set(audio_source_t, unsigned int, audio_format_t, unsigned int, unsigned int, void (*)(int, void*, void*), void*, unsigned int, bool, int, android::AudioRecord::transfer_type, audio_input_flags_t, audio_attributes_t const*)'
frameworks/base/core/jni/android_media_AudioSystem.cpp:1468: error: undefined reference to 'android::AudioSystem::registerPolicyMixes(android::Vector<android::AudioMix>, bool)'
frameworks/base/core/jni/android_media_AudioTrack.cpp:371: error: undefined reference to 'android::AudioTrack::streamType() const'
collect2: error: ld returned 1 exit status
make: *** [/home/kiran/source/out/target/product/ferrari/obj_arm/SHARED_LIBRARIES/libandroid_runtime_intermediates/LINKED/libandroid_runtime.so] Error 1
[Android Software Development] ferhung:
This is TWRP. Stop talking about the building errors of the dirty device & vendor trees here. Clean the posts, plz.
[Android Software Development] T-Macgnolia:
I hope they don't clean the posts. I mean have you ever tried googling for fixes to build errors? The more answers that are out there the better.

T-Macgnolia on Tapatalk
[Android Software Development] ferhung:
I known what's that mean. But not here, plz.
[Android Software Development] tonicairoli:
cube t6

Hi guys, i'm new here. I'm italian so sorry for my english. I don't know if it's the right threads where i have to write. If not i wonder you to excuse me.

I have got a cube t6 tablet. I can't able in noway to root it. I just tried all methods founded on the web but noone working. I'm looking for a custom recovery twrp for my tablet. I think it's the only way to root but i can't compile and on web i can't find a working twrp for my t6. There's someone here that can help me? If yes what device info do you need for compiling recovery? Thanks
[Android Software Development] Slimegod:
Getting this build error https://pastebin.com/ys2td0y9
[Android Software Development] yuweng:
Totally agree with ferhung, been using mkvendor.sh on cm source all these while, never had any problem at all, most questions regarding build error here is bcos they are using device tree for building ROMs... :cowboy:

i've once ask Master Shifu Dees_Troy why don't he make some script like mkvendor.sh for omni then i'll be easier for newbies, he replied saying that there are just too many devices out there & a generic mkvendor.sh won't work so i started my device tree manually & guess what is on my device tree, only 5 files, AndroidProducts.mk, BoardConfig.mk, kernel, omni_device_name.mk, recovery.fstab & it did built a fully working TWRP.... :cool:
[Android Software Development] T-Macgnolia:
I understand what you are saying. But all of us with knowledge of building Android, and building recovery is part of that, should be willing to help out where and when we can. That is what a community is about. And do we not all concider ourselfs part of the Android community. Plus that is also the spirit of the open source community as well which Android is part of.

Also just a side note on mkvendor.sh in CM. I don't know about you but everytime I have used mkvendor.sh I have to manually move the otatools to my bin folder in my home/user directory for the command ./build/tools/device/mkvendor.sh to work. And that peuce of information is not in the CM WiKi. Also even though that script may actually get you far enough or atleast close to being able to build a custom recovery. It is far from having you ready to build a working ROM.

I personally never had to build a recovery for a device until my last two devices and it has taught me a good bit I did not already know avout building and about how recovery actually works. So I am glad that I was forced to have to do it in the long run.

But back to what I was saying. I just feel we should be a community. Not shun others because they are trying to learn. I mean we all were complete noobs at one time ourselves.

T-Macgnolia on Tapatalk
[Android Software Development] DJBhardwaj:
Hey guys, I was trying to compile TWRP for angler (Nexus 6P) and faced an error, could someone please help?

target C++: healthd <= system/core/healthd/healthd_mode_charger.cpp
system/core/healthd/healthd_mode_charger.cpp:91:5: error: 'GRSurface' does not name a type
GRSurface* surface;
^
system/core/healthd/healthd_mode_charger.cpp:118:5: error: 'GRSurface' does not name a type
GRSurface* surf_unknown;
^
system/core/healthd/healthd_mode_charger.cpp:159:1: error: 'frame' has no non-static data member named 'surface'
};
^
system/core/healthd/healthd_mode_charger.cpp:413:63: error: 'GRSurface' has not been declared
static int draw_surface_centered(struct charger* /*charger*/, GRSurface* surface)
^
system/core/healthd/healthd_mode_charger.cpp: In function 'void draw_unknown(charger*)':
system/core/healthd/healthd_mode_charger.cpp:433:18: error: 'struct charger' has no member named 'surf_unknown'
if (charger->surf_unknown) {
^
system/core/healthd/healthd_mode_charger.cpp:434:49: error: 'struct charger' has no member named 'surf_unknown'
draw_surface_centered(charger, charger->surf_unknown);
^
system/core/healthd/healthd_mode_charger.cpp: In function 'void draw_battery(charger*)':
system/core/healthd/healthd_mode_charger.cpp:448:47: error: 'struct frame' has no member named 'surface'
draw_surface_centered(charger, frame->surface);
^
system/core/healthd/healthd_mode_charger.cpp: In function 'void draw_capacity(charger*)':
system/core/healthd/healthd_mode_charger.cpp:467:44: error: 'struct frame' has no member named 'surface'
batt_height = gr_get_height(frame->surface);
^
system/core/healthd/healthd_mode_charger.cpp: In function 'void healthd_mode_charger_init(healthd_config*)':
system/core/healthd/healthd_mode_charger.cpp:888:72: error: 'struct charger' has no member named 'surf_unknown'
ret = res_create_display_surface("charger/battery_fail", &charger->surf_unknown);
^
system/core/healthd/healthd_mode_charger.cpp:891:18: error: 'struct charger' has no member named 'surf_unknown'
charger->surf_unknown = NULL;
^
system/core/healthd/healthd_mode_charger.cpp:896:5: error: 'GRSurface' was not declared in this scope
GRSurface** scale_frames;
^
system/core/healthd/healthd_mode_charger.cpp:896:17: error: 'scale_frames' was not declared in this scope
GRSurface** scale_frames;
^
system/core/healthd/healthd_mode_charger.cpp:910:43: error: 'struct frame' has no member named 'surface'
charger->batt_anim->frames[i].surface = scale_frames[i];
^
make: *** [/home/dhananjay/omnirom/out/target/product/angler/obj/EXECUTABLES/healthd_intermediates/healthd_mode_charger.o] Error 1

#### make failed to build some targets (05:32 (mm:ss)) ####

dhananjay@dhananjay-linux:~/omnirom$
[Android Software Development] _that:
This is a mismatch between your ROM version and the minui header - what branch of Omni and TWRP are you using? You should always use the android-6.0 branch of bootable/recovery.
[Android Software Development] DJBhardwaj:
I was using Tasssadar's repo for TWRP (multirom): https://github.com/Tasssadar/Team-Win-Recovery-Project

How can I fix this?
[Android Software Development] _that:
Use non-MultiROM TWRP or help Tassadar merge all the recent changes from upstream into his fork.
[Android Software Development] DJBhardwaj:
Well, that would take some time. For now, I think, I should just merge this commit: https://github.com/TeamWin/Team-Win-Recovery-Project/commit/c798c9cd2486e0ff83776002c74f113677b10a84, with my local repo ? I could see some major changes for miniui.h
[Android Software Development] _that:
Might be enough - try it. :)
[Android Software Development] Slimegod:
Can someone help me out with this, it's a recovery issue. Never faced it before :what:
[Android Software Development] _that:
Use TWRP from the android-6.0 branch.
[Android Software Development] Slimegod:
I'm building 4.4.4 though, will it build?
[Android Software Development] nkk71:
[MENTION=3998397]DJBhardwaj[/MENTION]

since you left, i'll just leave this here for you:

[19:11:23 - 04 Feb] <nkk71> you pm'd me earlier?

[19:15:43 - 04 Feb] <dhananjay151293_> yes

it's best to discuss these things in public, feel free to mention me (@ nkk71, without the space) if you feel like I can help

PMs are usually low priority for me

[19:16:12 - 04 Feb] <dhananjay151293_> tasssadar doesn't have the latest twrp marshmallow merge

[19:16:24 - 04 Feb] <dhananjay151293_> this commit

[19:16:25 - 04 Feb] <dhananjay151293_> https://github.com/TeamWin/Team-Win-Recovery-Project/commit/c798c9cd2486e0ff83776002c74f113677b10a84

[19:16:48 - 04 Feb] <dhananjay151293_> so i can't even compile multirom twrp

[19:16:55 - 04 Feb] <dhananjay151293_> how do i proceed now?

that's up to you

[19:16:57 - 04 Feb] <nkk71> i'm working on a different approach, but it's not finished yet, and the current branch will be deleted soon

[19:22:16 - 04 Feb] <dhananjay151293_> Oh, good to know. Where can i follow you on github?

https://github.com/nkk71/android_bootable_recovery/tree/android-6.0-mrom

just deleted the old one, and created a new one... and I may (or not) repeat that until I'm happy with it.

if you prefer a squashed commit, you can look here for the time being: https://github.com/multirom-htc/Team-Win-Recovery-Project/tree/android-6.0

[19:23:57 - 04 Feb] <dhananjay151293_> When would you be able to complete the project?

whenever time permits

[19:34:03 - 04 Feb] <dhananjay151293_> I see, i think you are going on by merging every single commit

think again, i am not
[Android Software Development] vampirefo:
I just compiled TWRP 3 for E030U, all went well, currently using TWRP 3 to make a backup.

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

#### make completed successfully (05:41 (mm:ss)) ####

Thanks for the great recovery.
[Android Software Development] DJBhardwaj:
OKay, I went through it. Took me a day, roughly.

But then, this is the new error:

[MENTION=2605798]nkk71[/MENTION]

Now, I am stuck here:
[Android Software Development] DJBhardwaj:
The above was solved, mistake at my side.

Now, this:
[Android Software Development] androidlover5842:
i have compile twrp 3.0 for my device but want to share my twrp here and here his that thread where i share twrp . How can i share it in https://twrp.me/ ?
[Android Software Development] _that:
Contact Dees_Troy with the link to your device tree. Ideally join us on IRC (freenode #twrp), wait for him to show up (his timezone is UTC-6) and be available for testing pre-release builds.
[Android Software Development] workdowg:
_that

BTW... Thanks for you contribution! A real terminal will be such a help, at least for me. On my S2 we couldn't get ADB working in TWRP so using the built-in terminal is so tedious trying to test commands I gave up and used a flashable zip to test each one (this was not really any less tedious...) ...
[Android Software Development] androidlover5842:
thanks
[Android Software Development] DJBhardwaj:
[MENTION=4878287]_that[/MENTION]

Please help :rolleyes:
[Android Software Development] _that:
I already told you what your problem is. This is not a "fix my build for me" thread, and it is not about the MultiROM fork of TWRP. Find out why your healthd is incompatible with the minui in your fork of TWRP, find the commits you need to merge, and fix it yourself.
[Android Software Development] DJBhardwaj:
Thank you :good:
[Android Software Development] _that:
The onscreen keyboard is still a pain, but with a USB keyboard it is pretty usable. The terminal emulation is still very minimal - I stopped adding features when I got busybox less and vi to work. So everybody now needs to learn the basics of vi because nano is too big to fit into the recovery partition of some devices. :)
[Android Software Development] regalstreak:
* TW_BOARD_CUSTOM_GRAPHICS support has been deprecated in TWRP. *

For this issue, remove that line from the boardconfig.mk.

It has been deprecated as of 3.0.0
[Android Software Development] Slimegod:
I'm getting this build error https://pastebin.com/G4JQCeLd it just stops. Never had this happen. Doesn't even say a error.
[Android Software Development] carnby24:
Anyone can do twrp for zenfone selfie?
[Android Software Development] _that:
Sorry I can't help you with your locked bootloader, but from your logs I notice that we have a race condition - we are trying to open the framebuffer before init has created the device node for it.
[Android Software Development] pug1:
Sorry to ask this again but my question went unanswered.

Can anyone help plz