yashsingh1/xdaforums huggingface dataset:
[Android Software Development] jahidinbedod:
issue didnt mount data
[Android Software Development] vicky karthi:
can any one in this XDA developer are ready to teach or put a correct twrp compile process pls make it fast:confused::confused::confused::confused::confused::confused::confused::confused::confused::confused::confused:
[Android Software Development] TimSchumi:
The process on how to compile is in the first post of this thread...
[Android Software Development] kaiz16:
Thank you so much

I compiled twrp successfully ???
[Android Software Development] vicky karthi:
hey bro i want to create a custom recovery i can't understand from the post can you teach me how to do?,what are thing is required?,how to fix the bugs?,and make it very simple to understand better maner(:(:(poor english.and make a video and post in this xda developer

---------- Post added at 05:14 AM ---------- Previous post was at 05:12 AM ----------

hey bro i want to create a custom recovery i can't understand from the post can you teach me how to do?,what are thing is required?,how to fix the bugs?,and make it very simple to understand better maner(poor english.and make a video and post in this xda developer
[Android Software Development] ashyx:
If you don't have the knowledge to understand what is posted in the OP then you don't have the skills to build a custom recovery.

How do you expect to fix issues or bugs if you haven't a clue about the basics?

There is no point in trying to do something if you don't understand what it is you are doing.

I suggest you educate yourself and research, research, research then come back.
[Android Software Development] mightysween:
I am building TWRP for the Moto X4 and it seems that like many recent devices, we will need to temporarily boot TWRP and install it from a flashable ZIP that replaces the boot.img ramdisk.

The problem is that I can not seem to build any image that will boot to recovery using the "fastboot boot" command. Is there a trick to this??

I am currently building 3.2.1 from omni-6.0 sources, but have had this issue since 3.1.1. I am hoping someone has a solution for this as it is really the only thing holding back TWRP release for the X4.
[Android Software Development] qiurigao:
target thumb C++: healthd <= system/core/healthd/BatteryMonitor.cpp

system/core/healthd/BatteryMonitor.cpp: In member function 'bool android::BatteryMonitor::update()':

system/core/healthd/BatteryMonitor.cpp:189:11: error: 'struct android::BatteryProperties' has no member named 'maxChargingCurrent'

props.maxChargingCurrent = 0;

^

system/core/healthd/BatteryMonitor.cpp:277:43: error: 'struct android::BatteryProperties' has no member named 'maxChargingCurrent'

if (props.maxChargingCurrent < maxChargingCurrent) {

^

system/core/healthd/BatteryMonitor.cpp:278:43: error: 'struct android::BatteryProperties' has no member named 'maxChargingCurrent'

props.maxChargingCurrent = maxChargingCurrent;

^

system/core/healthd/BatteryMonitor.cpp: In member function 'void android::BatteryMonitor::dumpState(int)':

system/core/healthd/BatteryMonitor.cpp:416:49: error: 'struct android::BatteryProperties' has no member named 'maxChargingCurrent'

props.chargerWirelessOnline, props.maxChargingCurrent);

^

build/core/binary.mk:706: recipe for target '/home/lenovo/twrp6/out/target/product/karate/obj/EXECUTABLES/healthd_intermediates/BatteryMonitor.o' failed

make: *** [/home/lenovo/twrp6/out/target/product/karate/obj/EXECUTABLES/healthd_intermediates/BatteryMonitor.o] Error 1

#### make failed to build some targets (06:12 (mm:ss)) ####
[Android Software Development] ananjaser1211:
Handle multiple variants with 1 image

Hey fellas. First thanks a ton for this Guide its pretty well made and covered alot of ground. I have built recoveries for my device + 4 other variants, the issue we face is each variant has different dt image needed , so it wont work on another variant, So instead ive built a twrp for each variant. so im wondering, would it work if i combine DTB of similar variants (for example the G/GM Versions) so it is unified. or should i stick to my method and just ./build_all.sh

Thanks in advance, This is my current Tree (excuse the mess)

https://github.com/ananjaser1211/android_device_samsung_j5y17lte
[Android Software Development] ashyx:
This is not the case in my experience and I've compiled many recoveries fir Samsung devices

. As long as the device specs are the same for that model, the kernel and dtb usually works for all variants.
[Android Software Development] ananjaser1211:
Thanks, i think ive thought that they all have different DTS Because i was using prebuilts, I have checked each variant DTS, and all 5 end up using either 1 of the 2 DTS, eur open / openm

So 2 recovery variants / 2 kernel variants for those 5 would do just fine :good: thanks again.
[Android Software Development] Blackball:
I tried to build twrp for huawei oreo with 8.0 and got 3.2.1.0 but it doesn't load. I saw only the (Splash? ) Startscreen. I don't know how it called [emoji1]

Can I build twrp for oreo with 7.1 for 3.1.1.?

Gesendet von meinem VKY-L29 mit Tapatalk
[Android Software Development] Blackball:
Now i have compiled with 7.1 and TWRP was booting.

But there are few problems. I cant backup system, cust etc (Screenshot), i cant flash for example boot images and

it didnt see my system is installed.

Can somebody give me some hints ?

Or tell me how i can compile 3.1.1. Maybe thats the problem.

My device is Huawei P10plus with Oreo.

Greets
[Android Software Development] _that:
Where is your device tree (check your fstab!)? Where is your recovery.log (adb pull /tmp/recovery.log)?
[Android Software Development] Blackball:
I will upload my recovery log when im at home.

my fstab should be ok.

/boot	emmc	/dev/block/bootdevice/by-name/ramdisk	flags=display="boot";backup=1;flashimg

/cache	ext4	/dev/block/bootdevice/by-name/cache

/cust	ext4	/dev/block/bootdevice/by-name/cust	flags=display="cust";backup=1;wipeingui;flashimg

/data	f2fs	/dev/block/bootdevice/by-name/userdata	flags=display="data";backup=1;wipeingui

/external_sd	vfat	/dev/block/mmcblk1p1	/dev/block/mmcblk1	flags=display="MicroSD Card";storage;wipeingui;removable

/misc	emmc	/dev/block/bootdevice/by-name/misc

/modem_secure	ext4	/dev/block/bootdevice/by-name/modem_secure

/oeminfo emmc	/dev/block/bootdevice/by-name/oeminfo	flags=display="oeminfo";backup=1;flashimg

/product	ext4	/dev/block/bootdevice/by-name/product	flags=display="product";backup=1;wipeingui;flashimg

/recovery emmc	/dev/block/bootdevice/by-name/recovery_ramdisk	flags=display="recovery";backup=1;flashimg

/recovery2 emmc	/dev/block/bootdevice/by-name/erecovery_ramdisk	flags=display="recovery2";backup=1;flashimg

/splash2	ext4	/dev/block/bootdevice/by-name/splash2

/system	ext4	/dev/block/bootdevice/by-name/system	flags=display="system";backup=1;flashimg;wipeingui

/usb-otg	auto	/dev/block/sde1 /dev/block/sde	flags=display="USB OTG";storage;removable;backup=0

/vendor	ext4	/dev/block/bootdevice/by-name/vendor	flags=display="vendor";backup=1;wipeingui;flashimg

/version	ext4	/dev/block/bootdevice/by-name/version	flags=display="version";backup=1;wipeingui;flashimg

Its possible that 3.2.1 is not compatible with my phone (P10plus) ?

---------- Post added at 12:51 PM ---------- Previous post was at 12:29 PM ----------

Here my log. Tapatalk don't allow my to upload txt or log file:/

I hope spoiler work

Spoiler content hidden.

Gesendet von meinem VKY-L29 mit Tapatalk

---------- Post added at 01:30 PM ---------- Previous post was at 12:51 PM ----------

Twrp can't find my partitions so I try the direkt way like /dev/block/sdd55 and not bootdevice

Gesendet von meinem VKY-L29 mit Tapatalk
[Android Software Development] ashyx:
Post the output of

ls -laR /dev/block
[Android Software Development] desalesouche:
[MENTION=477335]Blackball[/MENTION] it seems your fstab have some typo/space uneeded.?

see what you posted about fstab:

/product ext4 /dev/block/bootdevice/by-name/product flags=display="product";backup=1;wipeingui;flashim g

and

/version ext4 /dev/block/bootdevice/by-name/version flags=display="version";backup=1;wipeingui;flashim g
[Android Software Development] Blackball:
Problem solved. Thank you guys.

I changed the fstab like this

/dev/block/platform/ff3b0000.ufs/by-name/system_a

[emoji3]
[Android Software Development] junaid1211:
please compile one for lyf wind 7
[Android Software Development] ashyx:
Change your pixel format, its wrong.
[Android Software Development] swpointer:
This thread is for compiling it yourself. Just follow the instructions, and you'll have one.
[Android Software Development] jacoghi:
Hi everybody from teamwin. I'm facing a strange issue when compiling twrp-8.1, which is: Compilation goes fines till 99%, kernel compiles (caf 6.6 r1) and all seems good, however it halts complaining about ADBD, can't remember the exact message right now, but it's like:

"Can't stat adbd cause it's not included in (device path)system/bin/" or something in that sense. I'm using the minimal tree BTW. twrp-7.1 compiles just fine, haven't tried 8.0 yet.

Thanks as always. Using omni sources.

EDIT: Exact line:

Copying baseline ramdisk...

cp: cannot stat '(...)/system/bin/adbd': No such file or directory

EDIT: 8.0 compiles just fine as well. Problem is only with 8.1
[Android Software Development] PaWill:
I tried.

TARGET_RECOVERY_PIXEL_FORMAT := "BGRA_8888" and "RGBX_8888" - boot yellow

TARGET_RECOVERY_PIXEL_FORMAT := "RGB_565" and "ABGR_8888" - black screen

Here are the data of AIDA64 mali-t860
[Android Software Development] ashyx:
Looks like it should be "BGRA_8888"

Ensure you are cleaning your source before recompiling.

You could also try without setting a pixel format.
[Android Software Development] PaWill:
what does it mean?

my run.sh

cd /home/user/TWRP7_3.2

. build/envsetup.sh

lunch omni_rk3399-userdebug

make clean && make -j5 recoveryimage

black screen :(
[Android Software Development] NepoRood:
Do an "eng" build, not "userdebug"

add_lunch_combo omni_rk3399-eng
[Android Software Development] PaWill:
not changed

boot yellow or black screen
[Android Software Development] NepoRood:
Does "yellow" function properly? If so, try to apply a theme to change the color...
[Android Software Development] PaWill:
Starting the UI...

setting DRM_FORMAT_RGBX8888 and GGL_PIXEL_FORMAT_RGBX_8888

setting DRM_FORMAT_XBGR8888 and GGL_PIXEL_FORMAT_BGRA_8888, GGL_PIXEL_FORMAT may not match!

setting DRM_FORMAT_XBGR8888 and GGL_PIXEL_FORMAT_BGRA_8888, GGL_PIXEL_FORMAT may not match!

Using drm graphics.

Very slow mouse. It is difficult to work.

I don't know how to do themes.
[Android Software Development] pix106:
Correct me if I'm wrong, but yellow TWRP is not just a color, it means something is wrong in graphics.

Theming would only hide the problem but not solve it :)
[Android Software Development] PaWill:
I agree.

This may be due to "curve" the kernel 7.1.2 for rk3399?
[Android Software Development] NepoRood:
You are correct Sir, but a theme will make it "Not Yellow", lol. IF it functions, deal with yellow, IMO

My DragonTouch X10 always has the "backlight" on, so I deal with it :good:

I'm not sure what this means...
[Android Software Development] PaWill:
bugs kernel for rk3399 android 7.1.2
[Android Software Development] pix106:
I have an issue close to this one with this Cube Talk 9X MT8392 build, color is fine but swipe gesture is a bit slow, yet usable.

i dealt with this slow swipe issue ;)
[Android Software Development] _that:
You both (you and [MENTION=1844098]PaWill[/MENTION]) could try a different graphics backend and see if it makes a difference (you may need to comment out parts of minuitwrp/Android.mk, for example the drm stuff).
[Android Software Development] junaid1211:
i tried but it shows android for a sec then it fades.only black screen.then i have to restart.please help
[Android Software Development] Qiangong2:
When I try to build twrp with the minimal manifest here: https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni/tree/twrp-6.0

It always fails at:

including ./frameworks/native-caf/services/sensorservice/Android.mk ...
including ./frameworks/native-caf/services/surfaceflinger/Android.mk ...
including ./frameworks/native/Android.mk ...
build/core/base_rules.mk:157: *** frameworks/native/cmds/dumpstate: MODULE.TARGET.STATIC_LIBRARIES.libdumpstate.default already defined by frameworks/native-caf/cmds/dumpstate. Stop.

I can't seem to find this error elsewhere, how do I fix it?
[Android Software Development] TimSchumi:
Remove either frameworks/native or frameworks/native-caf from the manifest
[Android Software Development] Temanyan:
Hi all, can anyone help with decryption, I don't understand what is wrong. As alternative system vold working fine, but this is not right decrypt. All logs and three of device Huawei Nova Can-L11 dual SIM, snapdragon 625.
[Android Software Development] Qiangong2:
How do you troubleshoot what may be wrong when TWRP doesn't load? It just hangs on the manufacturer logo for me.
[Android Software Development] Ijal_kelink:
Twrp for asus zenfone go
[Android Software Development] Ibuprophen:
I don't have this device but, the following TWRP threads may be what you are looking for.

https://xdaforums.com/showthread.php?t=3282861

https://xdaforums.com/showthread.php?t=3288482

https://xdaforums.com/showthread.php?t=3603019

Good Luck!

~~~~~~~~~~~~~~~

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Android Software Development] DiamondJohn:
/proc/last_kmsg
[Android Software Development] Qiangong2:
I did that, but unless I am doing something wrong, it isn't coming up with errors. It just says:

ram console header, hw_status: 0, fiq step 0.

There is no other lines in /proc/last_kmsg. It just will not boot to the recovery.
[Android Software Development] ashyx:
It's best to do:

cat proc/last_kmsg > sdcard/last_kmsg.txt

Then examine the output using something like Notepad++

You also need to post way more details. It doesn't boot isn't sufficient.

Device, firmware build, kernel stock or custom, built in which branch, device tree?
[Android Software Development] Qiangong2:
Here is my thread on it: https://xdaforums.com/android/development/root-blu-studio-g-d790q-megathread-t3555466

It is the BLU Studio G D790Q which runs 6.0, I have most of the stock kernel that I have been supplementing with other MT6580 based phones. Right now I am trying to build with the stock kernel I have.

My device tree: https://github.com/Qiangong2/android_device_blu_d790q

My kernel tree: https://github.com/Qiangong2/android_kernel_blu_d790q

Even after sending it to the sdcard, the last_kmsg still only gives that one line.
[Android Software Development] ashyx:
Sometimes last_kmsg needs to be enabled in the kernel config.

It also may have moved to:

cat /sys/fs/pstore/console-ramoops > sdcard/last_kmsg.txt

The other consideration is Selinux causing issues if your kernel isn't booting as permissive.

Does your custom kernel boot the stock recovery?
[Android Software Development] Qiangong2:
According to the config, pstore is enabled, but there is no console-ramoops file. I don't know how you would check if the custom kernel boots the stock recovery. Isn't the kernel integrated into the recovery?
[Android Software Development] ashyx:
You can split the ramdisk from the kernel and then repack your kernel with the stock recovery ramdisk.
[Android Software Development] Qiangong2:
I did that and it doesn't boot, so it looks like it's probably a kernel problem.

And as always, last_kmsg only shows:

ram console header, hw_status: 5, fiq step 0.
[Android Software Development] NepoRood:
Why not use the prebuilt kernel from your stock recovery or boot image?
[Android Software Development] ashyx:
Agreed that would be my suggestion also.
[Android Software Development] Qiangong2:
Because whenever I have built with a prebuilt kernel, touch does not work. I have CTR recovery already built, but I would like TWRP instead if possible.
[Android Software Development] dorianpb:
This might be stupid, but how to i find/ create the BoardConfig.mk?
[Android Software Development] ashyx:
Find a device tree with similar/same specs and modify it as required.
[Android Software Development] Ibuprophen:
I've never dealt with the BoardConfig.mk myself and though this thread is appropriate for this question, here's some other threads may also be helpful too.

https://xdaforums.com/showthread.php?t=3333970

https://xdaforums.com/showthread.php?t=1630849

https://xdaforums.com/showthread.php?t=3698419

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

Good Luck!

~~~~~~~~~~~~~~~

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Android Software Development] NepoRood:
MTK, right? You could give a shot at flashing it to boot, instead of recovery...

(Hold keys to boot)
[Android Software Development] yuweng:
Fyi. an obituary, though a bit late, just found out today, i guess many doesn't know that there are quite a few of TWRP contributors & he was one of them, pls don't leave your condolences/ comments at this thread, reply here if you have something so say, R.I.P RD nkk71
[Android Software Development] kherio:
TWRP for LG V30?

thx
[Android Software Development] jusma:
Hello does anyone have a tutorial on how to build a device tree for my device. I cannot find device tree files, but have kernel source from the manufacturer website. It is a Huawei Nova 2 device and the current recovery image created by cofface on xda does not decrypt the data partition.
[Android Software Development] ashyx:
Just search on Github. TWRP device trees are more or less the same no matter what the device. You just need to modify the mk files to suit your device.
[Android Software Development] jusma:
I have repo synced minimal omni rom. Can I just download any available device tree file and change the mk file? Or do the other files in a set of device tree differ across phones?
[Android Software Development] ashyx:
It's best to just search for a device with a similar spec to yours, but yes the mk files are pretty much the same for every device and just need to be modified to suit.

Maybe this will help.

https://github.com/skinzor/android_device_huawei_hwcan/tree/android-7.1

https://github.com/Xelfmade/android_device_huawei_hwcan?files=1
[Android Software Development] _that:
Ask them for the device tree. TWRP is GPL-licensed, so if there is a TWRP image on xda, you should be able to get the sources.
[Android Software Development] jusma:
Thanks for your inputs. cofface had not replied earlier to my message, but will try again.
[Android Software Development] kirito9:
Hey, does anyone know what's needed for minimal cm-11.0 to build twrp? [MENTION=7237874]NepoRood[/MENTION] made a cm-12.1 minimal source before so I was wondering if the same can be done for cm-11.0.
[Android Software Development] jusma:
Has anyone tried to compile TWRP in CYGWIN? I was following the tutorial here: https://developerswork.github.io/works/GUIDES/AndrodDeviceTree/

And I am stuck on the following two commands...

. build/envsetup.sh
make -j4 otatools

When I run the second, it shows the following message and throws an error...

============================================

PLATFORM_VERSION_CODENAME=REL

PLATFORM_VERSION=7.1.2

TARGET_PRODUCT=aosp_arm

TARGET_BUILD_VARIANT=eng

TARGET_BUILD_TYPE=release

TARGET_BUILD_APPS=

TARGET_ARCH=arm

TARGET_ARCH_VARIANT=armv7-a

TARGET_CPU_VARIANT=generic

TARGET_2ND_ARCH=

TARGET_2ND_ARCH_VARIANT=

TARGET_2ND_CPU_VARIANT=

HOST_ARCH=x86_64

HOST_2ND_ARCH=x86

HOST_OS=cygwin

HOST_OS_EXTRA=CYGWIN_NT-6.1-2.9.0-0.318-5-3-x86_64-64bit

HOST_CROSS_OS=

HOST_CROSS_ARCH=

HOST_CROSS_2ND_ARCH=

HOST_BUILD_TYPE=release

BUILD_ID=NJH47F

OUT_DIR=/cygdrive/d/twrp/v7.1/out

============================================

Using '/usr/bin/ninja' binary on 'cygwin'

build/core/combo/select.mk:49: build/core/combo/HOST_cygwin-x86.mk: No such file or directory

make: *** No rule to make target 'build/core/combo/HOST_cygwin-x86.mk'. Stop.

#### make failed to build some targets (2 seconds) ####

I had actually set the HOST_OS environment variable to 'cygwin' in Windows 7. In my build/core/combo folder, I don't have a HOST_cygwin-x86.mk ofcourse, and duplicating the linux file to HOST_cygwin-x86.mk or setting my HOST_OS to windows or linux doesn't help either.
[Android Software Development] DodoGTA:
You're not really supposed to build it on Cygwin
[Android Software Development] NepoRood:
IIRC, the script by [MENTION=4478781]yuweng[/MENTION] uses cm11, and will download the source for you, link

Or, look at projects in cm12 and compare to what is/isn't there in cm11...
[Android Software Development] kirito9:
Yeah I compared some projects from minimal omni 4.4 and started making the changes. I'll check the script from yuweng.
[Android Software Development] zakraoui.ahmed:
hello guys i am from Tunisia. i have huawei gr5 2017 model: bll-l21 a middle Africa version. this phone is like honor 6x. the twrp for honor 6x is supported only for model: bll-l22 and not bll-l21. i need a twrp recovery to root my phone but it's not found and i am accountant, i have no idea to compile a twrp with LINUX?, so, please if you can help me and thanks.
[Android Software Development] jusma:
Hi folks, I repo synced Minimal TWRP omnirom manifest and configured the device tree for my phone. However, when I run the following commands...

$ . build/envsetup.sh
$ lunch omni_hwpic-eng

I get the following error...

build/core/product_config.mk:234: *** Can not locate config makefile for product "omni_hwpic". Stop.

I am not sure what config am I missing. Please help.
[Android Software Development] jusma:
I had also added "TW_THEME := portrait_hdpi" to the BoardConfig.mk file in my device tree, but get the following error...

****************************************************************************

Could not find ui.xml for TW_THEME:

Set TARGET_SCREEN_WIDTH and TARGET_SCREEN_HEIGHT to automatically select

an appropriate theme, or set TW_THEME to one of the following:

landscape_hdpi landscape_mdpi portrait_hdpi portrait_mdpi watch_mdpi

****************************************************************************

Seems it is not reading the TW_THEME value properly due to some reason.
[Android Software Development] ashyx:
Do a make clean and try again.
[Android Software Development] jusma:
I did do make clean and make clobber, still have the problem. I can always temporarily hard code that, but can you suggest something for the error I posted one comment earlier...

build/core/product_config.mk:234: *** Can not locate config makefile for product "omni_hwpic". Stop.

This is my current show stopper
[Android Software Development] ashyx:
Not without seeing your device tree.
[Android Software Development] Goayandi:
Hey guys!

I have not found a solution to my problem so far. I hope you can help me. For weeks i'm working on TWRP for my device, a Xiaomi Mi Pad3 (based on Mediatek MT8176). I have fixed all errors - but one is left. TWRP has a yellow / orange interface for me. Sometimes it flickers a bit and i can see the blue default theme. On screenshots there is also the blue default. I think it is related to the RGB settings or something.

When i tried to add "TARGET_RECOVERY_PIXEL_FORMAT := RBG_565" to BoardConfig.mk - nothing changed.

My Repo:

https://github.com/Goayandi/android_twrp_xiaomi_cappu/

Thanks in advance
[Android Software Development] jusma:
I managed to fix this.