yashsingh1/xdaforums huggingface dataset:
[Android Software Development] ashyx:
But your device isn't a Lenovo, it's some generic Chinese model. It may use the same source code, but the config will be different. There are many different ways to build a kernel from the same source code and the config makes all the difference. Kernel code contains drivers that need to loaded at boot time.

The config is what decides which drivers are used for your specific device.

If your device allows it (highly unlikely) you can pull the config from the device itself.

The fact that you say it boots but no display means something is wrong with the config.

You may be able to figure this out if you do some research on the specs of your device and see if you can find a device which is using the same specs and have a look at the config of it.

Have a look at the display parameters.
[Android Software Development] pix106:
I was replying to your remark about manufacturer released source.

For kernel building, i'm talking about Lenovo Tab2 A7-10F, for which Lenovo released sources, with included config file for the device.

I think Lenovo released an incomplete source and/or config, i did not manage to build a kernel with gui for now. It should build fine and fully working if it was complete, imho.

For the chinese model, FNF ifive mini 3GS, as i told before i have no kernel source.

For what i understand from my tests, the touchscreen problem may not be that related to kernel, as it happens too using the kernel from a working TWRP 2.5 image.

I have the same "have to touch twice" problem using TWRP 2.8.7 from omnirom 5.1 and 3.0.2 from omnirom 6.0.
[Android Software Development] zainifame:
i have problem with my twrp 3.0.2-0 the splash didn't show up and just blank grey and white color but it's boot the problem is on the splash, on my twrp 2.8.7.0 splash (curtain) is fine, can u guys help me? my device running x86 intel clovertrail z2850 chipset, and this some error code i take at boot to twrp 3.0.2-0

--------- beginning of main
I/X86Assembler( 113): generated scanline__00000077:03010101_00008001_00000000 [611 ipp ins size] (753 ins size) at [0xb4f001f0:0xb4f004e1] in 8902575 ns
I/X86Assembler( 113): generated scanline__00000077:03545405_00000A01_00000000 [345 ipp ins size] (489 ins size) at [0xb4f004f0:0xb4f006d9] in 7353052 ns
E/pixelflinger( 113): error generating or caching assembly. Reverting to NOP. cache_err: 1
I/X86Assembler( 113): generated scanline__00000077:03545405_00000A08_00000000 [343 ipp ins size] (493 ins size) at [0xb4f006e0:0xb4f008cd] in 7034408 ns
E/pixelflinger( 113): error generating or caching assembly. Reverting to NOP. cache_err: 2
I/X86Assembler( 113): generated scanline__00000077:03545405_00000000_00000000 [328 ipp ins size] (430 ins size) at [0xb4f008e0:0xb4f00a8e] in 6784125 ns
E/pixelflinger( 113): error generating or caching assembly. Reverting to NOP. cache_err: 1
[Android Software Development] divis1969:
TWRP build on CM 14.1

I'm wondering is it possible to build twrp (branch android-7.1 maybe) on CM 14.1 source tree?

I've encountered the following error:

ninja: error: '/home/test/devel/cm_m2_14/out/target/product/meilan2/obj/STATIC_LIBRARIES/libbootloader_message_intermediates/export_includes', needed by '/home/test/devel/cm_m2_14/out/target/product/meilan2/obj/EXECUTABLES/init_intermediates/import_includes', missing and no known rule to make it
[Android Software Development] _that:
Not yet. You can try this *unofficial* tree with merged 7.1 updates:

https://github.com/Dees-Troy/Team-Win-Recovery-Project
[Android Software Development] divis1969:
Well, it also fails.

Initially it fails claiming for busybox.

Once I've added

TW_USE_TOOLBOX := true

it fails with

ninja: error: 'system/core/toolbox/df.c', needed by '/home/dsmirnov/devel/cm_m2_13/out/target/product/meilan2/obj/EXECUTABLES/toolbox_recovery_intermediates/df.o', missing and no known rule to make it
[Android Software Development] _that:
You can add busybox via a local manifest (e.g. from Omni or CM, from a branch where busybox was still included). IMHO the best solution.
[Android Software Development] TheOddTaco:
Need Help! For some reason the TWRP/CM recoveries i compile on CM13 don't boot up (even in cm14.1) . I already switched the defconfig, updated the dt.img and zImage and still nothing. Yesterday, i did another attempt and different configuration and booted up to DemiGod's Crash Handler.

Heres the device tree i used:

https://github.com/TheOddTaco/android_device_lge_ms330
[Android Software Development] czarsuperstar@gmail.com:
You might get an answer or not. I have requested help for the device and still no luck.
[Android Software Development] kirito9:
Question: I compiled TWRP for my device using CM11, latest twrp source and everything works great except vibration. I'm using a custom KK ROM and vibration works there, well vibration works in all ROMs. I think I read somewhere that having the kernel source for your device would allow you to make vibration work? Is there some flag to add to the BoardConfig.mk to make it work? :confused:

Like if I increased the vibration strength would that help somehow? I felt a very faint vibration after the wiping process completed (screen goes dark and it vibrates to let you know it's finished). I increased the strength in the menu but nothing. Just that very very faint vibration for like a second. Could it be hardware related as well?
[Android Software Development] czarsuperstar@gmail.com:
What can be added to the BoardConfig.mk to make the recovery accept the cmdline from the boot image?
[Android Software Development] kirito9:
Nice thread here for flags http://xdaforums.com/android/software/twrp-flags-boardconfig-mk-t3333970.
[Android Software Development] czarsuperstar@gmail.com:
The problem is that the recovery works good but using the paths from boot won't allow flashing system partitions.

https://github.com/czarsuperstar/android_device_lge_m1

Is my device tree but the boot has a different path but when added to the recovery fstab it gives errors.
[Android Software Development] czarsuperstar@gmail.com:
It seems that the K7 isn't the only phone with/ dev/block/platform/soc.0/by-name in the fstab but has /dev/block/bootdevice/by-name as the system partition. The Leon c50 has the same problem. A custom twrp image from unjustified Dev is allowing proper handling of the fstab of the c50 but the official image from the Team Win Development members doesn't. I am wondering if this issue has been looked at because there lies the keys to rectify the problem. I have contacted Unjustified Dev and I'm waiting for a response. But if anyone can be of some assistance on this problem it would be greatly appreciated.

Reference post

http://xdaforums.com/leon/development/rom-unofficial-cyanogenmod-12-1-lg-leon-t3166642

Thank you
[Android Software Development] muralivijay:
How to fix fb swap active fail Invaild arguments

i have compiled twrp for my device xolo era 4g spreadtrum chipset based .. compiled using marshmallow source . compiled twrp can,t booting stuck at xolo logo .. " fb swap active fail: invaild arguments" i got log here ... how to fix it ? help please !

here log

pastebin.com/PWfUG1UG
[Android Software Development] kirito9:
Can you please delete this log and upload it to a service like pastebin.com?? For future logs, use pastebin.
[Android Software Development] muralivijay:
twrp not boot fb swap active fail invaild arguments

i have compiled twrp for my device xolo era 4g spreadtrum chipset based .. compiled using marshmallow source . compiled twrp can,t booting stuck at xolo logo .. " fb swap active fail: invaild arguments" i got log here ... how to fix it ? help please !

here log

[MENTION=4101821]pastebin[/MENTION].com/PWfUG1UG remove "@"
[Android Software Development] ashyx:
http://pastebin.com/PWfUG1UG

Do you have the kernel source?
[Android Software Development] muralivijay:
No used prebuilt kernel
[Android Software Development] divis1969:
New OTA mechanism in CM14/AOSP7

Hi,

I've tried to build the TWRP 7.1 because I've supposed that it should already have the appropriate changes to adopt the new procedure to apply the OTA.

I've encountered this issue with CM14.1 based build.

Unfortunately, TWRP seems did not have it.

I do not exactly know when this procedure appeared.

It looks like the OTA updater in android writes some data into /misc and it is used by the bootloader to enter into recovery.

Recovery is expected to read it too and apply the OTA.

When finished, it should clear the misc.

TWRP is not yet able to apply the OTA this way.

It is not clearing /misc as well, so bootloader is starting recovery again and again.

Is this a known issue?

Or did I misunderstand it?
[Android Software Development] _that:
Since you're not providing any details, I guess that your fstab doesn't include a correct entry for /misc.
[Android Software Development] kirito9:
Hi, is the IRC channel still up? I try to get it but it says

#twrp Cannot join channel (+r) - you need to be identified with services

I try to authenticate before joining but I get "kirito9 is not a registered nickname."
[Android Software Development] _that:
Unfortunately we had to limit access to the channel to identified nicknames because of repeated abuse by a certain person. However everybody can register a nickname on freenode: https://freenode.net/kb/answer/registration
[Android Software Development] kirito9:
Thanks :), will be registering now.
[Android Software Development] czarsuperstar@gmail.com:
Is there an email where the team can be reached?
[Android Software Development] kirito9:
IRC is quicker, I'm sure you'll get your problem solved there.
[Android Software Development] czarsuperstar@gmail.com:
I solved the problem. I also compiled c50 TWRP and posted it so people can flash a custom rom.
[Android Software Development] kirito9:
Excellent :). Yet to figure out mine but will keep trying.
[Android Software Development] czarsuperstar@gmail.com:
What's wrong? Look in the root folder of your devices system.
[Android Software Development] kirito9:
I found the flag for vibration in TWRP and I tried both paths. sys/class/timed_output..... and sys/devices/virtual/...... but nothing. I even increased the VIBRATOR_TIME_MS but nothing still. I probably have to check my kernel and try to increase the vibration somehow.
[Android Software Development] czarsuperstar@gmail.com:
Have you tried using Omni Rom? I can't build on CM.
[Android Software Development] kirito9:
Tried Omni ROM but I didn't try with the flag. I'll give it a go. Omni is recommended to build TWRP as stated in the first post.
[Android Software Development] muralivijay:
How to fix fb swap active fail : invaild argument .... Twrp not booting stuck at logo
[Android Software Development] Sudarshankakoty:
No rule to make target ERROR

I am getting this compiling error.. How to fix it ?
[Android Software Development] divis1969:
Yes, right, I did not notice the appropriate partition is mapped to another place.

I've fixed it, and now recovery can recognize the parameters and attempts to apply the OTA, but fails.

For some reason, it is trying to find the /system in /dev/block/platform/mtk-msdc.0/by-name/system

Here is the quote:

I:operation_start: 'OpenRecoveryScript'
Running Recovery Commands
I:command is: 'install'
I:value is: '@/cache/recovery/block.map'
I:Unable to mount '/external_sd'
I:Actual block device: '', current file system: 'auto'
I:Unable to mount '/usbotg'
I:Actual block device: '', current file system: 'auto'
I:Installing mapped zip file '/cache/recovery/block.map'
Installing zip file '@/cache/recovery/block.map'
Installing zip file '@/cache/recovery/block.map'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
sysutil: mmapped 75 ranges
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
sysutil: mmapped 75 ranges
Target: Meizu/cm_meilan2/meilan2:7.1/NDE63X/548c0bf593:userdebug/test-keys
Target: Meizu/cm_meilan2/meilan2:7.1/NDE63X/548c0bf593:userdebug/test-keys
could not detect filesystem for /dev/block/platform/mtk-msdc.0/by-name/system, assuming ext4
could not detect filesystem for /dev/block/platform/mtk-msdc.0/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/mtk-msdc.0/by-name/system at /system: No such file or directory
mount: failed to mount /dev/block/platform/mtk-msdc.0/by-name/system at /system: No such file or directory
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
run_program: child exited with status 127
unmount of /system failed; no such volume
unmount of /system failed; no such volume
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
Patching system image unconditionally...
performing update
Patching system image unconditionally...
open "/dev/block/platform/mtk-msdc.0/by-name/system" failed: No such file or directory
script aborted: E1001: Failed to update system image.
E1001: Failed to update system image.
error: 1001
Updater process ended with ERROR: 7

This path is incorrect, the /system is correctly described by fstab:

/system	ext4	/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/system	flags=display="System";backup=1

and was recognized by TWRP:

/system | /dev/block/mmcblk0p21 | Size: 1487MB Used: 1108MB Free: 379MB Backup Size: 1108MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_Available_in_GUI IsPresent
Primary_Block_Device: /dev/block/mmcblk0p21
Display_Name: System
Storage_Name: System
Backup_Path: /system
Backup_Name: system
Backup_Display_Name: System
Storage_Path: /system
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files

I did not yet found where the incorrect path come from. Any suggestions?
[Android Software Development] _that:
You can add more debug output to graphics_fbdev.cpp to check the values in the struct fb_var_screeninfo vi and read your kernel source to see why it doesn't like the values.
[Android Software Development] kirito9:
Logs? Copy and paste the output in a service like pastebin.com :).
[Android Software Development] muralivijay:
My device not have kernel source .. using prebuilt kernel
[Android Software Development] _that:
This is not only for you but for everyone who posts in this thread with build errors:

First, everyone please stop posting screenshots of your terminals. It's unsearchable, it's less readable than normal text, often the relevant portion of the output is not even on the screen, and it's a waste of bandwidth. Copy the text into a collapsed section of your post or use a paste site instead.

Second, I can't see how your post is related to the part of the OP that you quoted.

Third, if you expect help with build errors, you need to include the following information:

* the ROM tree and exact version (branch/tag of the manifest) that you're using

* the branch of TWRP (omnirom/bootable/recovery) that you're using

* the device you're building for (code name and marketing name), ideally with your device tree in a public repository

* the make target that you used for starting the build
[Android Software Development] _that:
The kernel is GPL licensed, so you must be able to get the kernel source from the manufacturer. If not, you're using an illegal copy of Linux and I can't help you.
[Android Software Development] _that:
Maybe from the non-TWRP fstab in your ramdisk? Or maybe it's hardcoded in the updater?
[Android Software Development] Sudarshankakoty:
---------- Post added at 11:59 AM ---------- Previous post was at 11:58 AM ----------

[/COLOR]

1. ROM Tree : My Device tree, vendor, kernel sources is not in github or anywhere, my manufacturer constantly refusing to release kernel sources till now, so using a prebuilt kernel. So I have extracted device tree from my device using mkvendor.sh script. Tree Can be found here.. : https://drive.google.com/open?id=0B377TLFOgWdsRjlMMzFPbFdzV2s ( I don't know how to upload this on github as I dont dont know how to create a local manifest for my device.

2. Brunch of TWRP : Cloned using git clone https://github.com/omnirom/android_bootable_recovery.git (for Android 5.1).

3. Device Name : Micromax (vendor) Q370 (codename).

4. Using CM13 Sources to build.

Errors I am getting now :

5 warnings generated.
make: *** wait: No child processes. Stop.

A fix to whole compiling process will be very helpfull and will be greatly appreciated.
[Android Software Development] divis1969:
yes, I'm suspecting the fstab of the CWM recovery which I did not yet updated with new paths.

This path is used in the updater-script which I suppose it generated by the build before I've tried to use TWRP.

I've tried to regenerate the OTA zip with the modified CWM fstab, but was unable to do this because make fails with the error:

ninja: error: '<workspace>/out/target/product/meilan2/obj_arm/EXECUTABLES/updater_intermediates/updater', needed by '<workspace>/out/target/product/meilan2/obj/PACKAGING/target_files_intermediates/cm_meilan2-target_files-ccf9bbcad9.zip', missing and no known rule to make it

I suppose this 'updater' should be provided by TWRP (bootable/recovery-twrp/Android.mk), but did not yet find the way to fix

Any suggestions?
[Android Software Development] divis1969:
I've found few diffs between CWM and TWRP bootable/recovery<-twrp>/updater/Android.mk related to ARM64.

I've merged those manually and the build continues.

I suppose TWRP team need to merge it too.
[Android Software Development] sudeep22:
please any one make twrp for my device coolpad note 5

stock recover link->https://drive.google.com/open?id=0B-KtX0447urSejBka05HYUNKLUk

kernal sources-https://drive.google.com/file/d/0B3wvScQytk0dek4xb2p5TjdYeFU/view?usp=drivesdk

please no devlopers working please
[Android Software Development] czarsuperstar@gmail.com:
Xda
[Android Software Development] muralivijay:
my device manufacturer is xolo from india. they not released any opensource and kernel source for my device.. so i can possible use other manufacturer kernel source with sam soc chipset based ?
[Android Software Development] muralivijay:
How to add more debug in graphics _fbdev.cpp ? Help please
[Android Software Development] muralivijay:
[MENTION=933916]that[/MENTION] now i have kernel source of my device .. how to check graphics _fbdev.cpp ? Help please
[Android Software Development] lj50036:
Its always a good idea to tag the correct user :)

[MENTION=4878287]_that[/MENTION] is the correct username..

If your attention to detail cannot even get the username right, maybe looking at kernel source is not for you :D

Thx Josh
[Android Software Development] muralivijay:
Hmm twrp compile ! Without kernel source not possible right ?
[Android Software Development] Matt07211:
Entirety possible. Refer to my screenshot. As long as you have a already compiled kernel, then you don't need to compile it.
[Android Software Development] Guizão BR:
Guys, i've compiled the TWRP but the touch not work, someone can help me?

https://github.com/GuizaoBR/AICP-Q5

I fixed, hahaha, sorry
[Android Software Development] muralivijay:
But why he [MENTION=4878287]_that[/MENTION] asking kernel source for fix fb swap active : fail " iam only have prebuilt kernel
[Android Software Development] Matt07211:
I'm sorry I really can't make sense of this sentence. I know English isn't probably a language you know well but I jsut can't make sense of this sentence
[Android Software Development] ashyx:
Because issues like that are sometimes related to the kernel and can be fixed by modifying the kernel source.
[Android Software Development] czarsuperstar@gmail.com:
Alot of people are compiling TWRP with only a prebuilt kernel and DT.img compiling kernels when you are just beginning to learn about root is complex for some people. I learned the hard way.
[Android Software Development] skulldreamz:
What app is that? Looks like it's put together really well, thanks
[Android Software Development] vampirefo:
I guess no one read the problem you had with prebuilt kernel, had they, perhaps they wouldn't keep telling you can build with prebuilt kernel.

Perhaps [MENTION=4878287]_that[/MENTION] can answer your question, no one else appears to have a clue.
[Android Software Development] AlxMAX:
TWRP for Nougat

Is the guide in OP still working for the Android 7 sources? I am attempting to build the TWRP recovery using the CyanogenMod source tree because they already have a device source tree for Nexus 6. It's easier than creating a device source tree for Omnirom and trying the Omnirom tree.

Edit: I have managed to integrate the recovery source tree, but the compilation fails because the ext4crypt_tar.h file could not be found. Where is this file located?

Edit 2: It seems like the Android.mk for libtar is not taking into account the different directory name for the recovery which in my case is bootable/recovery-twrp (it doesn't use $(commands_recovery_local_path) )
[Android Software Development] czarsuperstar@gmail.com:
If he uses a root explorer he can find out from the device itself. I did it with the K7. He has to look for fb or framebuffer references on his device. The Fstab has information, The init.recovery.rc has information, and so forth. I just kept Googling and I found answers. Everytime I found new information I added it to device tree and the next revision is born. He has to find a similar device like his if he can't obtain the kernel source.
[Android Software Development] _that:
I already did, but this is not the thread to teach someone the basics of C programming.
[Android Software Development] Matt07211:
Quick edit, can be found on Google play.

When I had hoped into this thread, I didn't read the back log of posts. This question just looked like a simple question,,and I had not realized that it was in relation to a previous question, as their was no indexation there was.

And _that has already given his answer above to the guys question now anyway.
[Android Software Development] vampirefo:
Good, I saw he was asking for your help directly, glad you helped him.

---------- Post added at 07:10 PM ---------- Previous post was at 06:39 PM ----------

ext4crypt_tar.h should be in bootable/recovery/crypto/ext4crypt

It might just be easier to use omnirom rather than cm, I do use both though. omnirom source just makes it easier to drop new twrp source in it and compile.
[Android Software Development] Sudarshankakoty:
With CM sources, you may get missing files error. Specially in the out/obj folder.
[Android Software Development] vampirefo:
I just built Twrp branch android-7.1 on cm13 source without any error, I also build same on omni 5.1 source.
[Android Software Development] svendsvin:
Official TWRP App from Google Play

I just installed the official TWRP app from Play store (https://play.google.com/store/apps/details?id=me.twrp.twrpapp). I found an update and tried to install it. Now I'm stuck at fast boot screen and no matter what I push nothing happens. It's very stucked. I'm getting the errors "invalid boot image size" and "failed to validate boot image". Also it says "fastboot reason: fall-through from normal boot mode". Any suggestions what to do now, please?

PS. Tried using "fastboot reboot" through adb, but it just returns to the fast boot screen.
[Android Software Development] JMak00:
Yeah, I'm wondering how I use this ad I already TWRP installed on my lg g3 and have already flashed a recovery image.
[Android Software Development] bigsupersquid:
Find your device on twrp.me, download it's current twrp,

fastboot flash recovery twrpblabla.img

fastboot reboot recovery

If that works, reboot into bootloader

Then extract the boot.img from your current rom.zip and

fastboot flash boot boot.img

fastboot reboot

You might also try powering off the device and using the normal key combo to get into fastboot rather than letting it fall through, sometimes fastboot malfunctions on my htc's unless it's directly booted there from power off
[Android Software Development] Sudarshankakoty:
You must have device, kernel tree in github. That's why you got it easy. I challenge you with my device. :laugh:
[Android Software Development] vampirefo:
I build my own device trees, none of my devices are supported via twrp.

My devices

http://www.bestbuy.com/site/insignia-8-tablet-16gb/5157800.p?skuId=5157800

http://www.gsmarena.com/blu_r1_hd-8171.php

http://www.gsmarena.com/blu_energy_x_plus-7449.php