yashsingh1/xdaforums huggingface dataset:
[Android Software Development] _that:
TWRP from the android-6.0 branch is compatible with Omni 4.4 and 5.1. Here is my local manifest:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remove-project name="android_bootable_recovery"/>
<project name="android_bootable_recovery" path="bootable/recovery" remote="omnirom" revision="android-6.0" />
</manifest>
[Android Software Development] cezer kiran:
Im using twrp 5.1 branch and on stock rom based on 5.1

Just now i compiled recovery.img and flashed in boot partition and when i swithched on the phone boots into recovery i cant boot into system also the touch and the buttons arent working
[Android Software Development] someone755:
If you flash a recovery onto the boot partition the kernel will obviously only boot the recovery.

Use a recovery partition, or if that's not an option, integrate your recovery into the ramdisk.
[Android Software Development] cezer kiran:
Have found that due to extract ramdisk elf i can bake the recovery image and flash it in FOTAkernel partition now i have it correctly but the touch screen and buttons are not working plz help .other than that no problems inside the rom
[Android Software Development] cezer kiran:
Also inside recovery my pc showing my mobile as t2 ultra instead of xperia c3
[Android Software Development] tra_dax:
I m using this branch:

https://github.com/omnirom/android_bootable_recovery/tree/android-4.4

??

tra_dax
[Android Software Development] cezer kiran:
Touchscreen working but only after the first screen time out any help?
[Android Software Development] Android-Andi:
Could you try android-5.1 or 6.0 branch?

You should get a dmesg and check why the Touchscreen driver don't come up again.

Gesendet von meinem LG-H815 mit Tapatalk
[Android Software Development] cezer kiran:
sorry i dint get you could you xplain bit detail , my issue is the touch screen is working ony after the screen time out in twrp
[Android Software Development] Android-Andi:
adb shell dmesg > dmesg.txt

Check if there is a error :)

Gesendet von meinem LG-H815 mit Tapatalk
[Android Software Development] cezer kiran:
thanks mate will check
[Android Software Development] Android-Andi:
Np, for now you could set

TW_NO_SCREEN_TIMEOUT := true

As workaround until you fixed the issue.

Gesendet von meinem LG-H815 mit Tapatalk
[Android Software Development] cezer kiran:
i said only after screen time out the touch works ,if i set to no time out then touch wont work
[Android Software Development] Android-Andi:
TW_SCREEN_BLANK_ON_BOOT := true

Gesendet von meinem LG-H815 mit Tapatalk
[Android Software Development] cezer kiran:
have you seen the attachment
[Android Software Development] Android-Andi:
No time to look into it atm

Gesendet von meinem LG-H815 mit Tapatalk
[Android Software Development] Android-Andi:
https://github.com/omnirom/android_bootable_recovery/commit/cd56f8cb29821430c72ae5f753bf88a3b500b2cd

For reference, try using that flag, might fix your issue and doesn't need anything else.

Gesendet von meinem LG-H815 mit Tapatalk
[Android Software Development] cezer kiran:
Thanks mate issue solved:D
[Android Software Development] Slimegod:
I'm getting this kernel error building OMNIROM. Here's the full console Android-Andi https://pastebin.com/25QiaBk6
[Android Software Development] Android-Andi:
*

The present kernel configuration has modules disabled.

Type 'make config' and enable loadable module support.

Then build a kernel with module support enabled.

/home/slimegod/android/omni/kernel/samsung/klte/Makefile:1149: recipe for target 'modules' failed

Not sure about this, never run into that issue. Maybe try what get suggested: Type 'make config' and enable loadable module support.

Gesendet von meinem LG-H815 mit Tapatalk
[Android Software Development] Slimegod:
What line is that in the pastebin that you see the error you pointed out? Yeah I enabled CONFIG_MODULE to "y". It wasn't set on previous builds I did so maybe me setting it triggered the error. Perviously it was building fine before I set it so that could be it.
[Android Software Development] Android-Andi:
It is still ahead of that.

Post whole console via pastebin.com and i show you the line.

Gesendet von meinem LG-H815 mit Tapatalk
[Android Software Development] cezer kiran:
I hope i solved that but got another

host Java: guavalib (/home/kiran/omni5.1/out/host/common/obj/JAVA_LIBRARIES/guavalib_intermediates/classes)

warning: [options] bootstrap class path not set in conjunction with -source 1.7

external/guava/guava/src/com/google/common/base/Splitter.java:375: error: method spliterator in interface Iterable<T> cannot be applied to given types;

return spliterator(sequence);

^

required: no arguments

found: CharSequence

reason: actual and formal argument lists differ in length

where T is a type-variable:

T extends Object declared in interface Iterable

Note: Some input files use or override a deprecated API.

Note: Recompile with -Xlint:deprecation for details.

Note: Some input files use unchecked or unsafe operations.

Note: Recompile with -Xlint:unchecked for details.

1 error

1 warning

make: *** [/home/kiran/omni5.1/out/host/common/obj/JAVA_LIBRARIES/guavalib_intermediates/javalib.jar] Error 41

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

Any ideas ?
[Android Software Development] androidlover5842:
hey i am compiling twrp using slimkat 4.4 sources but i am getting this error

----- Making recovery image ------
/bin/bash: (((10712064 / 100) - 1) / img_blocksize + 1) * img_blocksize: division by 0 (error token is "img_blocksize + 1) * img_blocksize")
make: *** [/home/sumit/slimkat4.4/out/target/product/kylevess/recovery.img] Error 1
make: *** Deleting file `/home/sumit/slimkat4.4/out/target/product/kylevess/recovery.img'

can anyone help me please thanks in advance!
[Android Software Development] vampirefo:
I never see any errors, using cm12, cm11, cm12.1 my guess your ramdisk is too big.
[Android Software Development] Jaocagomez:
Hi!

i want to build twrp for x force based on x play which is the one actually working for both devices

im actually running ubuntu 14.04 x64

installed android sdk

made a git clone from https://github.com/omnirom/android_bootable_recovery/

and also made a git clone from https://github.com/TeamWin/android_device_moto_clark

i might sound noob as hell but i really want to do this, can someone really point me in the right direction, i think if it boots on x force most of the hardwork its done i just need to adjust the details.

but first i need to compile the one from x play.

so after i downloaded everything what commands or what do i need to do?

other guides talk about building android but i think i dont need the same things.

any links that can help? i can read.
[Android Software Development] vampirefo:
Start by actually reading the first post.
[Android Software Development] Jaocagomez:
you're totally right, downloading omni source now...
[Android Software Development] Slimegod:
Ran into this build error https://pastebin.com/YSs1xjGt
[Android Software Development] xWolf13:
Create an empty document named "export_includes" in the directory ../klte/obj/STATIC_LIBRARIES/libinit_msm_intermediates/
[Android Software Development] fgl27:
that init is on device/qcom/common

have you clone that?

if yes and it doesn't work, go to the android.mk in that folder and remove the if part leave only

include $(all-subdir-makefiles)

but that is only need to build kernel from source

in this twrp tree they are using pre-building

https://github.com/TeamWin/android_device_samsung_klte

with is way faster, but need to build a kernel first to have the files.
[Android Software Development] Slimegod:
Thanks for the clarification. I'm actually building OMNI for the s5, KitKat. I used OMNI qcom device tree which I should've used cm-11. You have a point though when things are cloned certain things happen compared to actually being downloaded and prebuilt like kernels. I ran into this though a few days ago maybe you and anyone else who what's to chime in can tell me what this is http://pastebin.com/6TS3Xc8j. Google isn't breaking this down as to what this error is.
[Android Software Development] aniket.lamba:
Have you pointed the kernel in the right directory? Check your Boardconfig for the kernel path.
[Android Software Development] Slimegod:
Yes the TARGET_KERNEL is set.

Edit: the dtb tool I was using was for lollipop and the kernel I'm building is KitKat so that could've been the issue.
[Android Software Development] sub77:
its not the dtbtool, looks like there is a wrong path in your custom mkbootimg.mk, the dts files should be located in arch/arm/boot/dts/
[Android Software Development] Slimegod:
That's where it's located https://github.com/Gigoo25/android_device_samsung_klte/blob/master/mkbootimg.mk

Edit: my dts file is located in arch/arm/boot/dts, just checked my kernel. I'm using cm-11.0 kernel. So it's targeted correctly.
[Android Software Development] AMDFusion:
Guys i've weird issues.Compiling everything is ok but when i flashed the recovery,after the Samsung logo,it boots to TWRP but then it sort of stuck at TWRP logo.( screen shows TWRP logo,flickers,shows TWRP logo flickers and so on) but will not proceed with the normal recovery.

I still could boot normally to the systems though after restarting with buttons.

What could possibly go wrong?
[Android Software Development] _that:
That usually means that TWRP is crashing before entering the main menu. Pull /tmp/recovery.log to find out where it is crashing.
[Android Software Development] AMDFusion:
Theres no log when i tried to pull.When i checked manually on file explorer it does not exist.

How?
[Android Software Development] _that:
adb pull /tmp/recovery.log while TWRP is crash looping.
[Android Software Development] AMDFusion:
Yes i did that and adb could not find any device,

It said : error device not found.
[Android Software Development] _that:
Does it show up in the output of lsusb?

You need to get adb working first before you continue with TWRP.
[Android Software Development] AMDFusion:
It does not show up on the output of lsusb during recovery but works fine(detected) when phone boots to android which means adb works fine.
[Android Software Development] Slimegod:
My qcom-common Android.mk has that line but it's already without the "if" part your referring too. I'm still running into that error even when using TWRP klte device tree.
[Android Software Development] fgl27:
that device tree uses pre build kernel, when not building the kernel is not need qcom/common you must have change the tree or the erro would not appear or you didn't make clean before make recovery.

TWRP doesn't need to build the boot.img, just need a kernel and dtb image, if you have a pre build one just use it, unpack any boot.img for the OS you wanna to build of that device and don't change the tree just update kernel and dtb for the unpacked one it must build.
[Android Software Development] Slimegod:
So when using TWRP the qcom-common device tree isn't necessary?
[Android Software Development] fgl27:
No I write...
[Android Software Development] Slimegod:
Ok I see. I was using a prebuilt kernel before but I deleted it when I used the TWRP device tree. I ran the "make clean" command. Will try it again and see.

Edit: was able to get past that error. I had to get a init file and add it to my device folder. I'm running into this framework/av error You ever ran into this framework/av error http://pastebin.com/SqhzCkkh. More then likely I'll have to revert a ExtendedCodec.cpp commit.
[Android Software Development] tra_dax:
I have built the multiboot for my phone. But there's one problem with it. My device's recovery partition size is 8mb and the multuboot's size is 16mb. I want to resize/expand the partition. Can anyone tell me how to do that??

Thanks in advance???

tra_dax
[Android Software Development] _that:
Just delete adjacent partitions until there is enough space for the recovery partition, then recreate the recovery partition. If these partitions happened to be important (like firmware for modem, or the Android boot image) you'll have to learn to live without a working phone or without the ability to boot Android. But you'll have enough space for TWRP. ;)

Seriously, repartitioning is dangerous if you don't know *exactly* what you're doing. By using XZ compression for the kernel and the ramdisk, and if that's not enough, by recompiling the kernel with a minimal config (you don't need networking drivers in recovery for example), you can usually save enough space to fit the recovery boot image into your partition.
[Android Software Development] androidlover5842:
i tried to repartition my recovery but when i flashed that recovery i was getting purple screen with four displays how can i resize my recovery partition ? I have tried xz compression

Thanks in advance
[Android Software Development] _that:
This thread is about how to compile TWRP. For repartitioning your device, please ask in your device forum.
[Android Software Development] AlxMAX:
Hi. I have attempted to rebuild the TWRP recovery using the Omni ROM source tree (downloaded from the android-6.0 branch) and it went OK. I've got the recovery.img and I have flashed it to my phone. The problem was the recovery was not able to decrypt the data storage. My phone is a Nexus 6 and the main firmware is CyanogenMod 13, nightly 20160105. I have input more times the PIN for the decryption but each time it failed. I was pretty sure I have input the PIN correctly more than once. ;) I remember Dees_Troy has modified the sources and he has released the 2.8.7.1 version which solved the decryption problem. I don't know if my decryption problem is the same as the one he has solved. Nevertheless, I am interested about the modifications.

Edit: I have also attempted to rebuild TWRP recovery using the CyanogenMod source tree. I've got the recovery.img, the recovery was not able to find any partition.
[Android Software Development] T-Macgnolia:
Your problem is uou do not have a AndroidProducts.mk file in your divce folder. You need to create one, just look in the Omnirom github at how they have it. It is a very simple file with only one line.

Also do not worry about the no omni.dependencies file. That is just a file that roomservice lookes for to write a roomservice.xml to pull in your device repos that you need if you have then in the omni.dependencies file.

T-Macgnolia on Tapatalk
[Android Software Development] Desmanto:
Thank you for the quick reply. For the androidproducts.mk, do you mean the one in the /omni/device/ZTE/P839F30/ or the one in the /omni/bootable/recovery/gui/device/ ? I see a lot of similiar folder structure in the whole repo, make me confused for the similiarity. If it is the first, I remember it has the androidproducts.mk file already, as in the github, the file is also there. But i need to recheck it later when i arrived home.

I will ignore the omni dependencies error then. I will try to recompile it later.
[Android Software Development] _that:
Looks like you're trying to compile C++ code with a C compiler.
[Android Software Development] cezer kiran:
so how to change that ?

it seems that gcc is used instead of g++ so how to change that?
[Android Software Development] Desmanto:
I have checked it, there is Androidproducts.mk in the /omni/device/ZTE/P839F30/. The content just this.

PRODUCT_MAKEFILES := \

$(LOCAL_DIR)/omni_P839F30.mk

But still no luck of compiling, got the same TW_THEME () is not valid.:(

All other file should be intact, I try to resync, it was completed already.
[Android Software Development] _that:
omni_P839F30.mk contains this line:

$(call inherit-product, device/zte/P839F30/full_P839F30.mk)

So try renaming "ZTE" to "zte".
[Android Software Development] SlimShady's:
Hi guys :) I'm building OmniROM 6.0.1 for LG L90 (w7).

I got into an error: http://hastebin.com/dujufeyelu.pas

Now the point is: I've Omnified all my device tree, tried everything but nothing...still got this error.

I'm building on Ubuntu 14.04. I chatted into the IRC of Omni but no one replied me..And I thought here someone would give me an hand..

This is my local_manifest in case you wanna see device/vendor/kernel trees: http://hastebin.com/siyivamudu.xml

Thank you very much in advance. :)
[Android Software Development] Slimegod:
After i flash a rom and reboot using TWRP it goes into download mode with a "Could not do normal boot" error. My device is GS 5
[Android Software Development] _that:
I guess it's as easy as changing the file name from .c to .cpp.
[Android Software Development] _that:
If you didn't compile TWRP yourself, this is off topic here. If you did, post info about your ROM tree in which you built TWRP, your kernel and device tree and the differences to the official build, the ROM you tried to flash, recovery.log from installing the ROM, etc.
[Android Software Development] MSF Jarvis:
My suggestion would be to build the kernel separately then rename the zImage to kernel and place at the commented location. Then remove the inline kernel building parameters and compile again
[Android Software Development] Hacker432:
Hi

I'm a noobie in Android development but I'm trying to learn

I have the source of a working twrp for my smartphone (Huawei Y550)

How can I add the f2fs tool in the twrp?

Inviato dal mio HUAWEI Y550-L03 utilizzando Tapatalk
[Android Software Development] MSF Jarvis:
https://github.com/MSF-Jarvis/android_device_htc_pico/blob/android-4.4/BoardConfig.mk#L44

Adding that line to BoardConfig.mk does the trick.
[Android Software Development] Hacker432:
And the f2fs external tool?
[Android Software Development] MSF Jarvis:
Which external tool?? This will let you wipe partitions into F2FS easily. Wasn't that what you wanted??
[Android Software Development] Hacker432:
OK, thank you, now I understand ^^

Inviato dal mio HUAWEI Y550-L03 utilizzando Tapatalk
[Android Software Development] MSF Jarvis:
Press the button[emoji4]
[Android Software Development] Hacker432:
Oh, sorry xD

Inviato dal mio HUAWEI Y550-L03 utilizzando Tapatalk
[Android Software Development] desalesouche:
kernel need to support f2fs also.
[Android Software Development] Hacker432:
Yes, I know

Inviato dal mio HUAWEI Y550-L03 utilizzando Tapatalk
[Android Software Development] cezer kiran:
make: *** No rule to make target `/home/kiran/omni/out/target/product/ferrari/obj/STATIC_LIBRARIES/libbatteryservice_intermediates/export_includes', needed by `/home/kiran/omni/out/target/product/ferrari/obj/EXECUTABLES/healthd_intermediates/import_includes'. Stop. any help seniors ???
[Android Software Development] Slimegod:
How do i fix this error https://pastebin.com/UEF95QmS
[Android Software Development] Ganesh A:
Should I do these things in Android SDK or Linux only??
[Android Software Development] chinajjb:
Linux only
[Android Software Development] Ganesh A:
Can.i do it in Vm...Do i need 32 or 64 bit...
[Android Software Development] chinajjb:
vm is ok ,and 64bit is recommended!
[Android Software Development] Deadly:
You can do it in VM.. 32/64 doesn't matter.. read op post.. you need to be able to compile cm first..

____________________________________

“If you wait to do everything until you’re sure it’s right, you’ll probably never do much of anything.” –Win Borden
[Android Software Development] chinajjb:
hi,Deadly!

would you mind having a check of my post here?at the tenth page of this thread,thanks!
[Android Software Development] apascual89:
For new sony devices like the z, does the samsung process apply or the one for typical devices? The Z will be my first Sony device.
[Android Software Development] chinajjb:
I got another problem ,I think I can use sdcard now ,because I can switch to use "external sdcard",but the problem is ,when I click the install icon ,the screen is freezing!but adb can be used well ,it also mean that the tablet is not hanged ,right?

oh ,dear me!! the sdcard has mount correctly when I used "adb shell" and enter the sdcard directory,and the contents is the external sdcard exactly,but the screen is still freezing now! how to fix it ?please please please please please help me,guys!

twrp will be perfect on my tablet right now if I can get you guys help,please!

and the twrp is 2.4.3.0 compiled version!
[Android Software Development] lambstone:
What if I am working for a completely device? I'm thinking of compiling TWRP for a generic chinese tablet running on an A31 chip.
[Android Software Development] ktempleton:
@dees_troy i have a question i build roms for the d710 and want to include twrp in my roms i was looking at your github and the device tree you have is ics yet i know someone has built twrp for jb4.2.2 on this device because i use it every day was wondering if you knew what flags had to be added to build this recovery because it rocks and is far superior to any that are available thanks in advance kt
[Android Software Development] Dees_Troy:
Try to select "use external sdcard" then adb pull /tmp/recovery.log and post the log.

The Allwinner A31 is a Cortex A7 design which is just a power efficient Cortex A15 but otherwise functionally equivalent and includes NEON. The Nexus 10 is a Cortex A15 so you could base your architecture flags off of the Nexus 10 aka Samsung Manta.

Build flags are here:

https://github.com/TeamWin/device_samsung_d710/blob/ics/BoardConfig.mk#L181
[Android Software Development] chasmodo:
Hi everyone.

I'd like to try and replace CWM recovery with TWRP in GT-N7000 CM10.1 (4.2.2). Full phone specs are here. Its recovery.fstab looks like this:

# mount point	fstype	device

/boot	emmc	/dev/block/mmcblk0p5
/recovery	emmc	/dev/block/mmcblk0p6

/efs	ext4	/dev/block/mmcblk0p1
/cache	ext4	/dev/block/mmcblk0p7
/system	ext4	/dev/block/mmcblk0p9
/data	ext4	/dev/block/mmcblk0p10
/preload	ext4	/dev/block/mmcblk0p12

/emmc	vfat	/dev/block/mmcblk0p11
/sdcard	vfat	/dev/block/mmcblk1p1

I removed android_bootable_recovery project and replaced it with TWRP in roomservice.xml. TWRP source got downloaded from Github

with no problems at all.

After snooping around TWRP repo, I picked t0lte as somewhat similar device and copied some of its build flags in BoardConfig.mk, and it now

looks like this:

# Recovery: set depending on recovery being built for. (CWM or TWRP)
# both init scripts can be found in the recovery folder
TARGET_RECOVERY_INITRC := bootable/recovery/etc/init.rc

# TWRP specific build flags

BOARD_USE_CUSTOM_RECOVERY_FONT:= \"roboto_15x24.h\"
DEVICE_RESOLUTION := 800x1280
TW_INTERNAL_STORAGE_PATH := "/data/media"
TW_INTERNAL_STORAGE_MOUNT_POINT := "data"
TW_EXTERNAL_STORAGE_PATH := "/sdcard"
TW_EXTERNAL_STORAGE_MOUNT_POINT := "sdcard"
RECOVERY_SDCARD_ON_DATA := true
BOARD_HAS_NO_REAL_SDCARD := true
PRODUCT_BUILD_PROP_OVERRIDES += BUILD_UTC_DATE=0
TW_NO_USB_STORAGE := true
TWRP_EVENT_LOGGING := false
SP1_NAME := "efs"
SP1_BACKUP_METHOD := files
SP1_MOUNTABLE := 1
TW_INCLUDE_INJECTTWRP := true
TW_DEFAULT_EXTERNAL_STORAGE := true
TW_BRIGHTNESS_PATH := "/sys/devices/platform/s5p-dsim.0/s6e8aa0/backlight/panel/brightness"
TW_MAX_BRIGHTNESS := 255
TARGET_USERIMAGES_USE_EXT4 := true

I'd appreciate any advice on adding, removing or editing stuff from BoardConfig before I start the Rom build.
[Android Software Development] AAccount:
Just wondering if I can request a few twrp flags. On the Galaxy Tab 10.1, the new TWRP 2.4.3.0 produces an image that is too big to fit on the the measly 5mb recovery partition. Even after disabling exfat using the appropriate flag, it is still too big. I managed to get it to fit by removing the twrp boot curtain jpg and the relevant lines from gui.cpp and action.cpp and the su injection related files. Is it possible to add in a few flags like TWRP_No_Curtain or TWRP_No_SU for older devices? I suppose it's possible to keep doing a manual removal job but maybe for people with older devices, this might be helpful.