yashsingh1/xdaforums huggingface dataset:
[Android Software Development] pvineeth97:
Ok Thanks :)

---------- Post added at 04:58 PM ---------- Previous post was at 04:52 PM ----------

I am building it on CM 14.0. Wouldn't that be a problem? :)
[Android Software Development] batoussai:
Finally got around looking at the logs on my phone. Seems something is wrong in the kernel, to be fair it's pretty much greek to me what is in the last_kmsg, if anyone could help this is a copy of it: http://pastebin.com/fyrkCg5b

If I had to guess these seem to be the interesting lines in the file:

[ 0.659251]<7> (7)[1:swapper/0][DISP][disp_lcm_probe #198]ERROR:FATAL ERROR!!!LCM Driver defined in kernel is different with LK
[ 0.659264]<7> (7)[1:swapper/0][DISPCHECK]disp_lcm_probe returns null
[ 0.659277]<7> (7)[1:swapper/0][DISPCHECK]primary_display_init end
[ 0.659293]<7> (7)[1:swapper/0][DISP][primary_display_get_width #7222]ERROR:lcm handle is null

and

[ 0.664418]<7>-(7)[1:swapper/0]init eMMC Failed ,line:1523
[ 0.664454]<7>-(7)[1:swapper/0]not find in scatter file error!
[Android Software Development] ashyx:
Shouldn't be. But I prefer to build with Omni. Builds in a fraction of the time.
[Android Software Development] pvineeth97:
I get this error while building TWRP.

libminadbd_intermediates/LINKED/libminadbd.so

system/core/adb/adb_auth_client.cpp:94: error: undefined reference to 'android_pubkey_decode'

I am building it on CM 14.
[Android Software Development] CaHbKaUp:
bootable/recovery/minadbd/Android.mk

locate LOCAL_WHOLE_STATIC_LIBRARIES and add libcrypto_utils_static at the end

probably next error you will get with updater:

bootable/recovery/updater/Android.mk

add line: LOCAL_STATIC_LIBRARIES += libcrypto_utils_static
[Android Software Development] pvineeth97:
I am using CM 13's BusyBox to build TWRP. CM 14's BusyBox is not released.

---------- Post added at 09:30 PM ---------- Previous post was at 09:27 PM ----------

I renamed TWRP recovery folder as "recovery-twrp" and not "recovery". Should I rename it as "recovery"?
[Android Software Development] CaHbKaUp:
yes, i suggest that root recovery directory is bootable/recovery, so if you change it, correct this path respectively
[Android Software Development] pvineeth97:
I get this error if I change the folder name from "recovery-twrp" to "recovery".
[Android Software Development] kenymccornick:
Hey man! I finally got some free time and wanted to compile twrp with the material theme you recommended. I tried following your instructions, I created a twrp-theme folder in my device tree and a material-tesla folder inside that contains the extracted zip. However, I'm getting this error when i try to compile, not sure what's telling me:

Notice file: system/core/toolbox/NOTICE -- /home/kenymccornick/CM-13.0-TWRP/out/target/product/wt88047/obj/NOTICE_FILES/src//fake_packages/toolbox_symlinks-timestamp.txt
HOSTLD scripts/kconfig/conf
cp -fr bootable/recovery-twrp/gui/devices/common/res/* /home/kenymccornick/CM-13.0-TWRP/out/target/product/wt88047/recovery/root/twres/
Symlink: /home/kenymccornick/CM-13.0-TWRP/out/target/product/wt88047/recovery/root/sbin/[ -> busybox
scripts/kconfig/conf -s Config.in
cp -fr twrp-theme/material-tesla/* /home/kenymccornick/CM-13.0-TWRP/out/target/product/wt88047/recovery/root/twres/
#
# using defaults found in .config
#
Symlink: /home/kenymccornick/CM-13.0-TWRP/out/target/product/wt88047/recovery/root/sbin/[[ -> busybox
cp: cannot stat ‘twrp-theme/material-tesla/*’: No such file or directory
bootable/recovery-twrp/gui/Android.mk:171: recipe for target '/home/kenymccornick/CM-13.0-TWRP/out/target/product/wt88047/obj/STATIC_LIBRARIES/libguitwrp_intermediates/twrp' failed
make: *** [/home/kenymccornick/CM-13.0-TWRP/out/target/product/wt88047/obj/STATIC_LIBRARIES/libguitwrp_intermediates/twrp] Error 1
make: *** Waiting for unfinished jobs....
SPLIT include/autoconf.h -> include/config/*
HOSTCC applets/usage
HOSTCC applets/applet_tables
GEN include/bbconfigopts.h
GEN include/usage_compressed.h
GEN include/applet_tables.h
HOSTCC applets/usage_pod
CC applets/applets.o
LD applets/built-in.o
make[1]: Leaving directory '/home/kenymccornick/CM-13.0-TWRP/external/busybox'

#### make failed to build some targets (04:55 (mm:ss)) ####

Here is the device tree I'm using: https://github.com/kenymccornick/android_device_wingtech_wt88047/tree/cm-13.0-twrp

Any help would be highly appreciated, thanks in advance.

Nestor
[Android Software Development] ashyx:
Looks like your path is wrong.

I suggest you put the the theme in the device folder and use:

TW_CUSTOM_THEME := $(DEVICE_PATH)/twrp-theme/material-tesla
[Android Software Development] carlosuema:
Hello everyone!

I was able to compile the TWRP to my device and it seems to work properly.

However, I can not use the interface because of a strange behavior that does not explain in words. So I share this video so someone can clarify why.

https://drive.google.com/file/d/0B1aPW-rnHeM-S1lDNDZZcnhyYTA/view?usp=sharing

My device is a Quantum MUV and uses the mt6735m processor and I am also using the stock kernel

I tested it with CM-Recovery and it worked!

However, what I really want is the TWRP
[Android Software Development] kenymccornick:
Thanks a lot, worked like a charm!
[Android Software Development] ashyx:
Open the .twrps file in sdcard/twrp with a text editor change the value of:

tw_mount_system_ro2 to 1

then add this line:

tw_never_show_system_ro_page0

This should get you past the read only page.

What happens then, laggy, unresponsive?
[Android Software Development] carlosuema:
Thanks for the answer !

It seems to be both lag and unresponsive. When I press a button, for example install button, the button is pressed and does not return.

I tested using a mouse and everything works fine.
[Android Software Development] _that:
Seems like your kernel produces unusual touch events. In minuitwrp/events.cpp there's a #define _EVENT_LOGGING that is commented out - uncomment this and rebuild, then touch the screen a bit and read recovery.log to see what's going on.
[Android Software Development] ashyx:
Are the sources for your kernel available anywhere?
[Android Software Development] carlosuema:
Here is the recovery.log. I read it, however, I can not see something that leaps out of my eyes. I'm new to it. Could you look at it and see some probable problem?

Thank you in advance!
[Android Software Development] carlosuema:
The company that makes my device has not yet made available the source of this kernel. However, as the processor of this device is the mt6735m of mediatek, I presume that this one here, https://github.com/CyanogenMod/android_kernel_cyanogen_mt6735, could work. I've tried to compile it but I have not yet achieved success.
[Android Software Development] ashyx:
Which defconfig did you use? The closest I can see is aeon6735_35u_m0_defconfig but not sure how compatible this is?
[Android Software Development] _that:
try setting this in your BoardConfig:

TW_USE_KEY_CODE_TOUCH_SYNC := 330
[Android Software Development] carlosuema:
It worked! But I think I need to work on it!

When I play an option, it's necessary to play twice!

The sliding function does not work!

When I use the virtual keyboard, touching another letter is selected!

Even so, it's a breakthrough! Thank you very much!

NOTE: If you want to give any more tips, feel free! Rsrsr

---------- Post added at 01:53 PM ---------- Previous post was at 01:50 PM ----------

That's exactly what I've used in my tests! Always gives error in the part of keys and encryption!

There's a little bit of leverage on my part, but I'd like to compile a minimal version, just to see if it boot!
[Android Software Development] prabaecepct:
Help porting

Hai I am sucesfully compiled twrp for my vivo v3 after flashing reboot to the recovery when entering reboot and directly go main boot to the system after system boot when entering recovery mode old stock recovery how to fix this help me developers sorry for bad English

My device tree
[Android Software Development] carlosuema:
Flash again you twrp, then when in twrp recovery, mout /sytem with rw permissions and delete recovery-from-boot.p file in /system.
[Android Software Development] ashyx:
Are there any stock sources available for a model similar to yours?
[Android Software Development] carlosuema:
Yes, the Wiley Spark, wich one i based my tree device!

Enviado de meu Quantum MUV usando Tapatalk
[Android Software Development] manuelmagix:
I tried two Aroma packages on my bq X5 Plus "gohan" with TWRP 3.0.2.0, and the interface was upside down, and it didn't install what it was supposed to install.

[IMG="aroma"]https://img.xda-cdn.com/unR9IPik96MzByNUO32Nnh7il9I=/http%3A%2F%2Fuploads.tapatalk-cdn.com%2F20161107%2F3a093dcf61887779fa328e067bffea01.jpg[/IMG]

https://img.xda-cdn.com/unR9IPik96M...20161107/3a093dcf61887779fa328e067bffea01.jpg
[Android Software Development] sub77:
UNBELIEFABLE, usually they are the kings of opensource;)
[Android Software Development] cw-network:
great guide
[Android Software Development] DevUt:
Do you know there is thank button to avoid such useless posts?

Click thanks if you know :P

(Person with low humor stay away)
[Android Software Development] shoey63:
? just another newcomer trying to bump up his post count to 10+
[Android Software Development] HereticOS:
I know i get likely stones thrown in my direction but i risk it and ask :D

Have here one of this 'China Tablets' with Allwinner A23 Chip.

There exist a SDK with a device tree for this device here:

dl.linux-sunxi.org/SDK/A23-v1.0/unpacked/A23/android/device/softwinner/polaris-p1/

Should this in theory be enough to port TWRP?

To make that clear, i started today to learn about this stuff. So this all looks still very like the Matrix Code to me. I don't want someone doing the job for me. Just need some starting points :)
[Android Software Development] bigsupersquid:
It sure looks like it. More than you'll need for building recovery, it's got lots of goodies.

Except the kernel source and defconfig. You can extract and use the stock kernel if it's recent enough for selinux.

What was that thing running, ice cream sandwich? I haven't seen a vold.fstab in a while. Well, maybe not, other files look more up to date.
[Android Software Development] HereticOS:
Nope, it's kitkat. 4.4.4 to be precise. What you mean with goodies?

Only 'goodies' i found so far a a mass of adware junk like dragonfire and softwinner services.

One of the many reasons i want to get rid of the stock rom.

and thanks for the fast answer! i will try it.
[Android Software Development] bigsupersquid:
I meant goodies like bootloader code, which you shouldn't need, but exposes more of the innards of the device than manufacturers often hand out.

I'm guessing the adware and stuff are installed in the device's rom, doubt they're built from source with that sdk.

You can build kitkat with that then, and twrp should be relatively cooperative, but building a newer android version than 4.4 will require trickier modifications than for twrp.

Looks like mostly vanilla aosp so omni might cooperate better than cm when you build.
[Android Software Development] HereticOS:
Well, the adware stuff is in the SDK /polaris-common/prebuild/preinstallapk/ and /prebuild/framework_aw/

So should be no problem to get rid of it.

The included lichee build.sh works fine as far i can tell.

Only complaint is

Have to look into that.

At the end i get

Guess that means 'all okay'.

but make in /android/ fails with

which is strange. this is definitive a 64-bit linux.

but i'm sure i figure out what is wrong. (don't want to spam this thread)
[Android Software Development] bigsupersquid:
You can post build-specific questions over in this thread:

http://xdaforums.com/showthread.php?t=2060017
[Android Software Development] prabaecepct:
I am compiled twrp from omni 5.1 suroce after flash recovery img Now my phone tries to boot into recovery, but the screen stays black and after about 15 seconds the phone starts normally

How to fix this

I am using vivo v3 sd616 chip set
[Android Software Development] kep2008:
When compiling get an error...

Can you tell me how to fix... :(

[ 3% 10/267] build /home/kep2008/omni...bj/ETC/sepolicy_intermediates/sepolicy
FAILED: /bin/bash -c "(/home/kep2008/omni/out/host/linux-x86/bin/checkpolicy -M -c 30 -o /home/kep2008/omni/out/target/product/eva/obj/ETC/sepolicy_intermediates/sepolicy.tmp /home/kep2008/omni/out/target/product/eva/obj/ETC/sepolicy_intermediates/policy.conf ) && (/home/kep2008/omni/out/host/linux-x86/bin/checkpolicy -M -c 30 -o /home/kep2008/omni/out/target/product/eva/obj/ETC/sepolicy_intermediates//sepolicy.dontaudit /home/kep2008/omni/out/target/product/eva/obj/ETC/sepolicy_intermediates/policy.conf.dontaudit ) && (/home/kep2008/omni/out/host/linux-x86/bin/sepolicy-analyze /home/kep2008/omni/out/target/product/eva/obj/ETC/sepolicy_intermediates/sepolicy.tmp permissive > /home/kep2008/omni/out/target/product/eva/obj/ETC/sepolicy_intermediates/sepolicy.permissivedomains ) && (if [ \"userdebug\" = \"user\" -a -s /home/kep2008/omni/out/target/product/eva/obj/ETC/sepolicy_intermediates/sepolicy.permissivedomains ]; then	echo \"==========\" 1>&2;	echo \"ERROR: permissive domains not allowed in user builds\" 1>&2;	echo \"List of invalid domains:\" 1>&2;	cat /home/kep2008/omni/out/target/product/eva/obj/ETC/sepolicy_intermediates/sepolicy.permissivedomains 1>&2;	exit 1;	fi ) && (mv /home/kep2008/omni/out/target/product/eva/obj/ETC/sepolicy_intermediates/sepolicy.tmp /home/kep2008/omni/out/target/product/eva/obj/ETC/sepolicy_intermediates/sepolicy )"
system/sepolicy/domain.te:446:ERROR 'unknown type camera' at token ';' on line 9086:
neverallow { domain -appdomain -camera -cameraserver} file_type:file execmod;
#camera_server neverallow needed for Android N
checkpolicy: error(s) encountered while parsing configuration
/home/kep2008/omni/out/host/linux-x86/bin/checkpolicy: loading policy configuration from /home/kep2008/omni/out/target/product/eva/obj/ETC/sepolicy_intermediates/policy.conf
[ 3% 10/267] build /home/kep2008/omni...RIES/libbmlutils_intermediates/teamwin
ninja: build stopped: subcommand failed.
make: *** [ninja_wrapper] Ошибка 1
[Android Software Development] sub77:
minimize your devicetree, look at those on github.com/teamwin
[Android Software Development] ashyx:
A bit pointless just posting the error message.

It looks like you've missed a step.

Post your steps and commands you used to begin the build or screen shots.
[Android Software Development] TimSchumi:
There is an SE Policy error in there:

system/sepolicy/domain.te:446:ERROR 'unknown type camera' at token ';' in line 9086:

neverallow { domain -appdomain -camera -cameraserver } file_type:file execmod;

#camera_server neverallow needed for Android N

Looks like you need to define a sepolicy domain called "camera"
[Android Software Development] kep2008:
Source omni 7.0.

This device tree (only changed system.prop).

ro.build.id=NRD90M
ro.build.display.id=NRD90M test-keys
ro.build.version.incremental=eng.jenkin.20161031.052247
ro.build.version.sdk=24
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=7.0
ro.build.version.security_patch=2016-08-05
ro.build.version.base_os=
ro.build.date=Mon Oct 31 05:22:47 CST 2016
ro.build.date.utc=1477862567
ro.build.type=user
ro.build.user=jenkins
ro.build.host=wuhjk0116cna
ro.build.tags=test-keys
ro.build.flavor=generic_a15-user
ro.product.model=generic_a15
ro.product.brand=Huawei
ro.product.name=generic_a15
ro.product.device=generic_a15
ro.product.board=
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.manufacturer=unknown
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=generic_a15
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=generic_a15-user 7.0 NRD90M eng.jenkin.20161031.052247 test-keys
ro.build.fingerprint=Huawei/generic_a15/generic_a15:7.0/NRD90M/jenkin10310522:user/test-keys
ro.build.characteristics=default
# end build properties

. build/envsetup.sh
lunch omni_eva-userdebug
make -j3 recoveryimage
[Android Software Development] ashyx:
You should do:

source build/envsetup.sh

I would also remove:

TWHAVE_SELINUX := true
[Android Software Development] TimSchumi:
. build/envsetup.sh shoud is the same as source build/envsetup.sh

---------- Post added at 11:42 AM ---------- Previous post was at 11:30 AM ----------

The system.prop should only contain values that do not EXIST/ARE NOT SET by default. Already existing values should be changed through ADDITIONAL_DEFAULT_PROPERTIES in the device.mk file
[Android Software Development] pix106:
Same problem with a mt6592 device, did you find anything ?

I'm still trying things... :)

Edit : using omni 5.1 + twrp from 6.0, prebuilt 3.4.67 kernel
[Android Software Development] ashyx:
Is it not possible to request the kernel source code from your manufacturer? They are obligated to provide this.
[Android Software Development] pix106:
I don't know if there's a published source for chinese FNF ifive mini 3GS i just got... I highly doubt about it :) I'll have a look.

In some other project with a lenovo Tab2 A7-10F, kernel source is indeed published, but it's partial and i can't build a kernel that boots with GUI (=it boots my rom, but with no gui).

So even if manufacturer publishes a kernel source, it can be "legal and opensource compliant" but incomplete.

But for TWRP, a prebuilt kernel should be enough, i have already done so for 2 devices.
[Android Software Development] kep2008:
Thanks for the info.

I get the same error...

If omni/system/sepolicy/domain.te comment out the line

[COLOR="Red"]#[/COLOR]neverallow { domain -appdomain userdebug_or_eng(`-camera -cameraserver')} file_type:file execmod;

compile successfully...

Only twrp not boot... :(
[Android Software Development] ashyx:
Not necessarily, I often have to build custom kernels to work with my twrp builds.
[Android Software Development] pix106:
Ok, thanks for info.

If i can't get touch screen to work properly (=no need to double tap), i'll search this way.

Thanks !
[Android Software Development] ashyx:
You need to look for a triple buffering flag in the defconfig. If it's there comment it out or disable it via menuconfig.
[Android Software Development] pix106:
ok, if i get a kernel source i'll try.

This made me want to try building with NUM_FRAMEBUFFER_SURFACE_BUFFERS := 2 and NUM_FRAMEBUFFER_SURFACE_BUFFERS := 3, not working better.

I also tried using the kernel from a working TWRP 2.5. image, in which touchscreen works fine (but resolution is wrong), and the same double tap problem happens too.

So it can be TWRP build related only don't you think so ?

I have the double tap problem without this line in my BoardConfig.mk

If i add it, touchscreen stops working, screen vibrates but doesn't click.

How can i find which values i could try ?
[Android Software Development] _that:
From the recovery.log after enabling event logging (read the posts before the one that you quoted for details).
[Android Software Development] pix106:
thanks.

I had tried it earlier, but couldn't see anything in /cache/recovery/log or last_log...

Now, in /tmp/recovery.log i get

E:TOUCH_RELEASE: -1,65535
EV: mtk-tpd => type: 1 code: 14a value: 0
E:TOUCH_KEY: 330
E:HardwareKeyboard::KeyUp 330
EV: mtk-tpd => type: 0 code: 2 value: 0
EV: mtk-tpd => EV_SYN SYN_MT_REPORT
EV: mtk-tpd => type: 0 code: 0 value: 0
EV: mtk-tpd => EV_SYN SYN_REPORT
EV: x: 1466 y: 1793
E:TOUCH_START: 1466,1793
E:TOUCH_HOLD: 1466,1793
E:TOUCH_REPEAT: 1466,1793
[Android Software Development] ashyx:
Tried this myself with no success.

In my case the kernel was forcing triple buffering, but twrp wants to use double buffering. This was causing what seemed like an extra page in memory being created, hence what seems like an unresponsive and laggy touch response until it is tapped twice to update the display.

Removing the triple buffering flag in the kernel fixed the issue.
[Android Software Development] _that:
Double buffering in TWRP (and in any other software I'm aware of) works like this:

- tell the display subsystem (kernel, whatever) to display page 0 of the framebuffer

- draw something on page 1

- tell the display subsystem (kernel, whatever) to display page 1 of the framebuffer

- draw something on page 0

- repeat

How can the kernel "force" triple buffering, other than by not properly implementing the FBIOPUT_VSCREENINFO (or FBIOPAN_DISPLAY) ioctl? It's always the userspace program, in this case TWRP, that explicitly requests the kernel to display a specific portion of the framebuffer.
[Android Software Development] carlosuema:
I could not make the touch work properly yet. But I'm trying. In the meantime I have used a mouse like work arround!
[Android Software Development] ashyx:
So basically your saying I'm talking rubbish and I just made it up?
[Android Software Development] Westboy82:
Old user want learn

Hi guys,

it's a long time im using your recovery, but now i cant find for my HOMTOM HT10 helio X20.

There is no actual root metod for my device.

So i decided to learn to do my own.

Can you point me a complete guide?

Or is there someone already challenged it?

Tnx
[Android Software Development] MSF Jarvis:
I believe he's saying that you're slightly confused
[Android Software Development] amirhtc:
TWRP for Datamini TWG10(needed)

Hi [MENTION=912474]Dees_Troy[/MENTION] , I need your help , I have Datamini TWG10 based on Android 5.1.1 powered by Intel Atom Z3735F with 2 GB RAM and Screen Size	25.65cm (10.1)

Resolution	1280 x 800 Pixels

Screen Type	IPS Touchscreen

actually I have tried your post so many times but due to I am a non-experimented person to be unsuccessful .

Please kindly put a proper TWRP for this device in the TWRP device list page , I need urgently to root this device using TWRP.

Or guide me , can I use a TWRP from another devices , if yes , which one(s) , if No , what should i do ? where can i find a proper TWRP for my tablet ( ITS NOT IN TWRP IMG Devices list

THANK YOU SO MUCH .

FULL INFO OF THE DATAMINI TWG10 ->

http://xdaforums.com/windows-10/general/overview-datamini-twg10-2-1-tablet-t3290027
[Android Software Development] _that:
I explained how TWRP uses double buffering and I asked for an explanation how your fix works.
[Android Software Development] ashyx:
I'm not slightly confused about anything. The simple fact is disabling triple buffering in the kernel fixed the issue where nothing else would. This has been the case on 3 separate devices I've compiled for.

That's fine.
[Android Software Development] kep2008:
In addition to this post.

Replaced kernel, took from recovery for 7.0. TWRP is started, but can not mount the data... :crying:
[Android Software Development] ashyx:
You would need a kernel that supports f2fs or format back to ext4.

---------- Post added at 10:30 AM ---------- Previous post was at 10:24 AM ----------

Nope, it has to be the actual source code used to build the actual kernel that is released with the firmware. Even though many manufacturers regularly fail to do so, Samsung being one of the worst offenders.
[Android Software Development] kep2008:
It twrp worked on stock 6.0, i want to do for 7.0-beta.

I tried to do

/data	ext4	/dev/block/platform/hi_mci.0/by-name/userdata

but nothing changes...
[Android Software Development] ashyx:
Do it using the advanced wipe options in twrp. Select ext4 as the partition type.
[Android Software Development] pix106:
I did build a kernel using lenovo's source and config file, it builds, it boots fine, using adb i can see the rom is fully booting, but i have no display at all.

So, it "has to"... => Lenovo did not or failed :)