yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Pavlex4:
Now I have this problem:

lunch cm_s3ve3g-userdebug

build/core/config.mk:374: *** Error: could not find jdk tools.jar, please install JDK6, which you can download from java.sun.com. Stop.

Device s3ve3g not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).

Found repository: android_device_samsung_s3ve3g

Default revision: cm-11.0

Checking branch info

Default revision cm-11.0 not found in android_device_samsung_s3ve3g. Bailing.

Branches found:

cm-12.0

Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.

build/core/config.mk:374: *** Error: could not find jdk tools.jar, please install JDK6, which you can download from java.sun.com. Stop.

** Don't have a product spec for: 'cm_s3ve3g'

** Do you have the right repo manifest?
[Android Software Development] MSF Jarvis:
Look, I don't want to hate you, but next time you paste the logs in your post rather than an external paste service, I swear I'm reporting you. Your error looks like a problematic build environment setup, which is hardly surprising in your case. Use these commands to fix it :

sudo add-apt-repository ppa:openjdk-r

sudo apt install openjdk-6-jre openjdk-6-jdk -y
[Android Software Development] Pavlex4:
What means this: https://postimg.org/image/pzyorqv1d/
[Android Software Development] MSF Jarvis:
:eek:

It means everything is working. Type mka recoveryimage now
[Android Software Development] Pavlex4:
After I run mka bacon I get error: https://postimg.org/image/qycalhh7r/

I fixed problem with java but now I have this error: https://postimg.org/image/rpcddk04h/
[Android Software Development] Muhammad Ashraf:
touch to wake also not working
[Android Software Development] MSF Jarvis:
There's no touch to wake functionality in TWRP

---------- Post added at 03:55 PM ---------- Previous post was at 03:49 PM ----------

Are you using the full cm-11.0 source or some minimal manifest for TWRP only?
[Android Software Development] Pavlex4:
I am using manifest for twrp only: https://github.com/iBullRay/manifest_s3ve3g
[Android Software Development] MSF Jarvis:
This is for your device source. Okay, do this :

cd .repo/manifests/

git remote -v

And send me the screenshot
[Android Software Development] Pavlex4:
https://postimg.org/image/7kq7herg7/
[Android Software Development] MSF Jarvis:
Try doing this in your source dir :

repo sync -l

And try again
[Android Software Development] Pavlex4:
Still have same error!!!!

What to do?????????
[Android Software Development] NepoRood:
You can use this

Works on Windows and Linux, a very useful/nice tool

---------- Post added at 11:17 AM ---------- Previous post was at 11:06 AM ----------

Your manifest contains no CyanogenMod source code, it's only device sources. If you don't want to sync full source code, you have a few options:

Minimal Manifests

CM12.1 <-- Recommended

CM13

Omni5.1

Omni6
[Android Software Development] MSF Jarvis:
Umm no, Nepo, he has the source code. Scroll a bit, you'd see my post where I confirm that he has indeed synced up full cm11 sources
[Android Software Development] Pavlex4:
I don't have cm13 and 12.1.1 have only cm11 and cm12.0.
[Android Software Development] MSF Jarvis:
Try the make otatools command. First do the usual lunch, then make otatools
[Android Software Development] Pavlex4:
What version of cm to use?
[Android Software Development] MSF Jarvis:
Whatever latest is available.
[Android Software Development] NepoRood:
Hence: New Signature

[MENTION=6552280]MSF Jarvis[/MENTION] :p

I'd swore I clicked every link, lol
[Android Software Development] MSF Jarvis:
*swear
[Android Software Development] Android-Andi:
Might be a commit missing in system/core or in build repo.

Is it really complaining about mkbootimage or it's because bootable/recovery/res-720 doesn't exist?

Sure having twrp synced? Setup as recovery variant? Or replaced cm recovery?

~ All my work, news etc. on http://andi34.github.io ~
[Android Software Development] NepoRood:
#redneck
[Android Software Development] Pavlex4:
I synced cm13 but when I run lunch cm_s3ve3g-eng I get error: https://postimg.org/image/n85rqby93/

I tried this commands but still have same error:

2) type this : 'mkdir -p .repo/local_manifests/ && cd .repo/local_manifests/'

3) and then this : 'git clone https://github.com/iBullRay/manifest_s3ve3g'

4) and finally 'cd ../../ && repo sync --no-tags -c --no-repo-verify --force-sync -f'
[Android Software Development] Muhammad Ashraf:
I mean when the screen is turned off when I touch the screen one time then it shows lockscreen of twrp
[Android Software Development] Android-Andi:
You haven't added it here https://github.com/iBullRay/android_device_samsung_s3ve3g/blob/cm-11.0/vendorsetup.sh

Are you sure you have twrp synced?

Location? bootable/recovery-twrp? In this case make sure defining

RECOVERY_VARIANT := twrp

in your boardconfig

Asm you can see in the previous output the compiler complains about a resource path in bootable/recovery which doesn't exist (wrong recovery source? Or Set an invalid theme flag?)

~ All my work, news etc. on http://andi34.github.io ~
[Android Software Development] Pavlex4:
It was added inside vendorsetup.sh.

I have synced twrp.

I have added: RECOVERY_VARIANT := twrp inside boardconfig.

I still have same error!!!!!!!!!!!!!!!
[Android Software Development] Hacker432:
Guide to compile TWRP recovery step by step from zero

http://xdaforums.com/showthread.php?t=3404024
[Android Software Development] Muhammad Ashraf:
please which flag should I add to enable touch to wake in twrp??

i mean when the screen times out and then touch the screen the screen will be on again in the lock screen

thanks
[Android Software Development] MSF Jarvis:
It's a kernel level modification and even then it will be *double tap* to wake. I imagine the power button isn't too far away for someone to not want to reach out to press it
[Android Software Development] Muhammad Ashraf:
ok, but It was like that in a pre-built image but for z3 not z3dual it was working but any z3dual cyanogenmod rom couldn't be installed because it is detecting from recovery that it is for z3

now I have built TWRP from source for z3dual but that feature is not working

also in my note 2 it was like that (tap to wake was present)
[Android Software Development] Pavlex4:
I have problem:

1. I created empty folder and named it twrp

2. I run this command: repo init -u git://github.com/lj50036/platform_manifest_twrp_cm.git -b twrp-13.0

3. I did repo sync -j3

4. I created folder /kernel/samsung/s3ve3g and put kernel source inside it.

5. I create folder /device/samsung/s3ve3g and put device tree inside it.

6. I create folder /device/samsung/s3ve3g and put vendor files inside it.

7. I run this command: . build/envsetup.sh

8.When I run this command I get error: https://postimg.org/image/6f8f5oypt/

I fixed problem by adding this sources to /device/samsung folder:

https://github.com/CyanogenMod/andro...ce_qcom_common

https://github.com/CyanogenMod/andro...ng_qcom-common

https://github.com/MSM8226-Samsung/a...msm8226-common
[Android Software Development] Pavlex4:
I have problem, recovery.img too large: https://postimg.org/image/u1432e1qp/
[Android Software Development] sub77:
if not solved so far, disable tw logcat flag.
[Android Software Development] followmsi:
Thanks ...actually the logcat flag was the problem. ;)

All fine now !
[Android Software Development] celoxocis:
i was about to build a TWRP with a prebuilt kernel and dt.img.

i have done it successfully in the past. as base i extracted a marshmallow boot.img from stock rom.

i just now noticed. there is no "boot.img-dtb" in the extracted folder (using superR's kitchen)

did something change in marshmallow based boot.img's? how can a TWRP using prebuilt kernel/dt.img be build without a dt.img?
[Android Software Development] arvinquilao:
Some newer kernels ship with appended dtb. If you have the kernel source, you can confirm it by checking if the defconfig has this line:

CONFIG_ARM_APPENDED_DTB=y
[Android Software Development] cmonty14:
Hi!

Where can I download the build for D6603?

Can you please share it?

THX
[Android Software Development] DevUt:
Goto /out dir and search for recovery.img (including sub folders)

As I don't reme2 the path
[Android Software Development] cmonty14:
I'm sorry, but I don't fully understand.

Could you please specify what I'm supposed to do?

Which file should I download? Where do I find it?
[Android Software Development] DevUt:
Are you building twrp?
[Android Software Development] cmonty14:
I didn't compile TWRP for D6603, yet because other users have created it already.
[Android Software Development] NepoRood:
Upper right corner of your screen, there's a search box, "Search All Forums".

Give it a shot :good:
[Android Software Development] Pavlex4:
How to fix this error: https://postimg.org/image/4kqv4d8s7/
[Android Software Development] Startrek852:
You need to run make mrproper in the kernel directory.
[Android Software Development] Pavlex4:
I run it before make recoveryimage but still have error!

I run this commands: http://pastebin.com/kzhQXL3S
[Android Software Development] Startrek852:
Try deleting and resyncing the kernel directory.
[Android Software Development] DevUt:
You don't need to use export ARCH=arm

Make cyanogen_defconfif

And make menuconfig

Just goto kernel dir make clean && make mrproper

Then

croot

mka -j5 recoveryimage
[Android Software Development] Pavlex4:
I am using menuconfig because I want to use lzma compression.

---------- Post added at 05:52 PM ---------- Previous post was at 05:48 PM ----------

This is part of my defconfig what should I change to enable lzma: http://pastebin.com/kypKWfyM

---------- Post added at 05:55 PM ---------- Previous post was at 05:52 PM ----------

This is part of my defconfig what should I change to enable lzma: http://pastebin.com/kypKWfyM
[Android Software Development] Startrek852:
Just uncomment CONFIG_KERNEL_LZMA.
[Android Software Development] Pavlex4:
Do you mean to remove hashtag?
[Android Software Development] Startrek852:
Yes, and the space after it.
[Android Software Development] Pavlex4:
It is successfully compiled!!!

---------- Post added at 06:35 PM ---------- Previous post was at 06:31 PM ----------

Now I have error with command make multirom: https://postimg.org/image/hhjcyer8n/
[Android Software Development] Pavlex4:
I fixed make multirom error.Now I have this error: https://postimg.org/image/otg2vubmv/
[Android Software Development] Pavlex4:
How to fix this: http://pastebin.com/CnAkT2hY
[Android Software Development] goldchang:
[MENTION=6049290]Pavlex4[/MENTION]

I remember that someone have the same issue with you
[Android Software Development] Pavlex4:
Who?
[Android Software Development] goldchang:
I did see it somewhere on github

You'll need to find it though

I'll post if I found it
[Android Software Development] Pavlex4:
Did you find it?
[Android Software Development] DevUt:
Init is failing to set ro.hardware

You will see that init.recovery. endeavoru.rc is loaded because I modded init.rc in recovery

http://pastebin.com/eHTkLjfd
[Android Software Development] DevUt:
How to go permissive without using kernel cmdline
[Android Software Development] MSF Jarvis:
setenforce 0 in *.rc
[Android Software Development] DevUt:
Shouws invalid command
[Android Software Development] heliusjing:
how to port twrp recovery
[Android Software Development] Android-Andi:
Read first post on first page

~ All my work, news etc. on http://andi34.github.io ~
[Android Software Development] Startrek852:
Seriously? Read the first post of this thread and you'll find out.
[Android Software Development] DevUt:
When should I give that command on early-init or on init or on boot
[Android Software Development] MSF Jarvis:
I think on boot is perfect
[Android Software Development] rw041504:
nothing

try it
[Android Software Development] Android-Andi:
https://github.com/omnirom/android_bootable_recovery/blob/android-6.0/etc/init.rc#L16

https://github.com/omnirom/android_bootable_recovery/blob/android-6.0/prebuilt/permissive.sh

It is permissive by default

~ All my work, news etc. on http://andi34.github.io ~
[Android Software Development] DevUt:
I was also looking for my rom :silly:
[Android Software Development] bigsupersquid:
add androidboot.selinux=permissive to kernel command line for rom or recovery permissive without build flags
[Android Software Development] DevUt:
I already ruled out that option because an s-on HOX does not get kernel cmdline from Rom it is provided by the bootloader in short we cannot change it and also s-off is my available for 1.72 hboot for Hox
[Android Software Development] bigsupersquid:
have you tried sending the kernel and ramdisk separately with a command line through fastboot?

not good for a user experience but good for testing if it works. my hrc evo 3d from 2011 and my comparatively new htc desire 816 are both s-on but will accept kernel command line through fastboot. the evo won't flash it while s-on except to recovery after htc unlocked (still s-on but less limited.)

if yours is anything like the mostly locked evo (s-off is a pain and I've not done it to this one yet) you might be able to boot your ROM from the recovery partition instead of the boot partition.

kexec in kernel like multirom uses (but in recovery partition instead of boot) is another maybe

sorry, getting pretty OT for TWRP
[Android Software Development] redfeast:
i got this error while building twrp

i got this error while building how to resolve

Symlink: /home/prudhvi/dev/pac/out/target/product/fortuna3g/recovery/root/sbin/yes -> busybox
Symlink: /home/prudhvi/dev/pac/out/target/product/fortuna3g/recovery/root/sbin/zcat -> busybox
Notice file: bootable/recovery-twrp/NOTICE -- /home/prudhvi/dev/pac/out/target/product/fortuna3g/obj/NOTICE_FILES/src//fake_packages/busybox_symlinks-timestamp.txt
Export includes file: bootable/recovery-twrp/fb2png/Android.mk -- /home/prudhvi/dev/pac/out/target/product/fortuna3g/obj/STATIC_LIBRARIES/libfb2png_intermediates/export_includes
Import includes file: /home/prudhvi/dev/pac/out/target/product/fortuna3g/obj/STATIC_LIBRARIES/libfb2png_intermediates/import_includes
make: *** No rule to make target 'true', needed by '/home/prudhvi/dev/pac/out/target/product/fortuna3g/obj/EXECUTABLES/recovery_intermediates/twrp.o'. Stop.
make: *** Waiting for unfinished jobs....
Export includes file: bootable/recovery-twrp/fb2png/Android.mk -- /home/prudhvi/dev/pac/out/target/product/fortuna3g/obj/RECOVERY_EXECUTABLES/fb2png_intermediates/export_includes

[MENTION=6552280]MSF Jarvis[/MENTION]

[MENTION=5829679]DeeStROy_[/MENTION]
[Android Software Development] MSF Jarvis:
Make clean, sync and build again
[Android Software Development] redfeast:
can we compile twrp 3.0 for cm-12.1 source [MENTION=6552280]MSF Jarvis[/MENTION]
[Android Software Development] NepoRood:
Yes
[Android Software Development] redfeast:
it's not resolved by doing this
[Android Software Development] MSF Jarvis:
Then post full build logs please, last 5 lines don't reveal anything. And for ****'s sake use hastebin.com or Github gists if you have a Github account for posting logs
[Android Software Development] Android-Andi:
There's something wrong in the BoardConfig i think: "No rule to make target "true", needed by ...."

~ All my work, news etc. on http://andi34.github.io ~
[Android Software Development] redfeast:
here is full log -------> https://gist.github.com/redfeast/8cc19945158d2b3fa55be1bcde4b0593

here is device tree -------> https://github.com/redfeast/android_device_samsung_fortuna3g/tree/cm-12.1
[Android Software Development] Android-Andi:
[MENTION=6431585]redfeast[/MENTION]

TARGET_RECOVERY_DEVICE_MODULES :=

Don't set that to "true", needs the module name, e.g. chargeled (or what ever is needed by your device)

Also you should change

TW_BRIGHTNESS_PATH := /sys/devices/platform/s3c24xx-pwm.0/pwm-backlight.0/backlight/pwm-backlight.0/backlight

To

TW_BRIGHTNESS_PATH := "/sys/devices/platform/s3c24xx-pwm.0/pwm-backlight.0/backlight/pwm-backlight.0/backlight"

Maybe some more flags can be removed, e.g. the default language because it is en by default anyway

~ All my work, news etc. on http://andi34.github.io ~
[Android Software Development] redfeast:
Thank you very much, but I'm a noob in building , could you help me to find what modules are necessary in recovery mode, and my device don't have a led
[Android Software Development] Android-Andi:
Lol... No, can't help you on that. Maybe you don't need recovery modules, my devices don't need it.

Add the important flags only, if something is not working, start looking at what's wrong. Copy and past from other devices without knowing or blind adding stuff isn't a good way.

~ All my work, news etc. on http://andi34.github.io ~
[Android Software Development] redfeast:
True that's what i did, but not from other device but from this guide directly

---------- Post added at 19:13 ---------- Previous post was at 18:38 ----------

thank you very much ,i got few more errors but this time it's not target error ,

please check gist for log

https://gist.github.com/redfeast/8cc19945158d2b3fa55be1bcde4b0593
[Android Software Development] NepoRood:
If you're building TWRP only (and not a rom) you don't need to build a kernel, prebuilt is fine for TWRP.

Try commenting out kernel path and defconfig, see if that helps with the error. Also, your offset flags are not needed, since you're using the mkbootimg args flag.
[Android Software Development] redfeast:
Yes i did as you said, but now a different error appear, regarding no rule to make usr, but too early than before, checkout the log please i revised it

As of now I'm building twrp, when it's successful i will build pac-5.1
[Android Software Development] MSF Jarvis:
mkdir -p $OUT/obj/KERNEL_OBJ/usr

touch $OUT/obj/KERNEL_OBJ/usr/export_includes

This is a common pitfall of using a prebuilt kernel, I face this daily :crying:
[Android Software Development] NepoRood:
OK, if you plan to build a rom in the future, best to get rid of kernel errors now, I would think. Unfortunately, I can't help with that, I've never built a kernel (or a rom for that matter) Seems like error before had to do with KConfig, double check everything, and undo what I told you earlier :p

Sorry I can't be of more help,

Nepo

EDIT: or do as Jarvis suggested, he'll be more help than I
[Android Software Development] redfeast:
K i will undo, so i should not use a prebuilt kernel to build rom

So now anyone help fix the above quoted errs with kconfig
[Android Software Development] 101AjA101:
Hello Experts & Dev of Xda iam totally noob & don't have much knowledge to build rom or recovery, iam posting here coz i post in help section about my this matter before & Art Vanderlay advice me from this topic to post here so here is my problem,

I have a MT6580 Phablet running Lollipop 5.1 , I ported TWRP successfully, i used google nexus 7 2012 tablet TWRP 3.0.2.0 to port , now everything working fine but the screen is flipped, I mean the TWRP screen showing menu & buttons etc on portrait but the touches input act like the TWRP screen is landscape which is a headache! so can you please help me what need to do to fix this issue.
[Android Software Development] NepoRood:
You'll have to build your own if the touch points are off. There's plenty of info on this, I've provided some links:

Step-by-Step Compiling Guide, here

Auto Compiler, here

Flag Reference, here
[Android Software Development] 101AjA101:
thanks for the reply but as i already told in my post that iam totally noobi & don't have knowledge to build my own, thats why i ask dev's to help.
[Android Software Development] NepoRood:
I understand that, links provided are "newbie friendly" :D

If your touch points are landscape but view is portrait, then TWRP needs to be compiled using the swap XY flag, and possibly some others. This can't be done to a ported recovery because it's already been compiled.

I can probably build one for you, but I'd need a stock recovery image, and I have no way of testing it, so you run a chance of getting a brick. Best to take the plunge and learn how to make your own, it's not really that hard, but the info can be overwhelming, lol
[Android Software Development] 101AjA101:
Thanks for the advice NepoRood, if the above link is newbie friendly then i guess iam lower then newbie lol, or lowest, anyways i attached my stock recovery & the one which i port twrp recovery,

Q: why i attached both recoveries?

A: my stock recovery given odd or wrong mounting points so i manual get all mounting points of my device & add them on ported twrp recovery so may be if you use stock recovery mounting points it not work correct, i understand about brick risk as i one time did hard brick & then after one month search i found my device stock Rom & make my device alive again :P

Thankd for the help, i appreciate it.

Kind Regards.
[Android Software Development] NepoRood:
lol, if you know how to port a "working" recovery, change mount points and come back from a brick, you're not that low of a newbie :good:

If you can do all that, you can build TWRP
[Android Software Development] MSF Jarvis:
I changed that behavior 3 months ago in this commit : https://github.com/MSF-Jarvis/AIO-TWRP-Compiler/commit/d1ef21affaebd7fd4e5f1495a389c80f41e7a9ab

So now it will work on all distros provided your BE setup is perfect
[Android Software Development] 101AjA101:
well my friend if i can then i never ask for help, anyways if you can't help then no problem, you still awesome bro, thanks for all help, hope some else one here help me.

Kind Regards
[Android Software Development] MSF Jarvis:
If you feel you are a noob then use the thread for step by step compilation of TWRP linked earlier by [MENTION=7237874]NepoRood[/MENTION]. I've had to face a lot of **** because of my behavior towards n00bs in this thread and so I will advise you to stick to that thread and that thread only
[Android Software Development] 101AjA101:
problem fixed & it can't be done without NepoRood help so all credit goes to NepoRood bro, i highly appreciated your help bro, you are my rockstar, Love you Xda experts & devs like NepoRood,

Thanks & Peace.

Kind Regards

AjA
[Android Software Development] redfeast:
Anyone tell me how to prepare a device tree for new device, basically is it needed to be prepared by us or OEM provide device tree
[Android Software Development] NepoRood:
You have to do it yourself, if there's not one already. You can search Github, use a sample, and/or refer to this guide.
[Android Software Development] redfeast:
What is the difference between building

32 bit and 64 bit roms, as my processor (cortex-a53)support both, but officially Samsung shipped it with a 32 one, now what are major changes to be made (i mean to which partitions) to get a 64 one, only system and boo.img, recovery are enough?
[Android Software Development] Gauravkarki:
Recovery mode issue in honor 4x

Since I unlock my bootloader in my honor 4x and

Flash the TWRP.img properly , but my phone can't get into

RECOVERY MODE . When I hit VOL+ and power button it

opens FASTBOOT MODE instead of RECOVERY MODE.

Plzzzzzz Help me to resolve this problem.

..

.
[Android Software Development] NepoRood:
1) Try Vol- and Pwr

2) Use adb:

adb reboot recovery
[Android Software Development] Gauravkarki:
Thansk for your advice but I tried both of them nothibg works

VOL- + PWR (NOTHING HAPPENS) , and ADB REBOOT RECOVERY ( IT OPENS FASTBOOT MODE).

plzzz suggest smthng else....thkyou
[Android Software Development] bigsupersquid:
when my boot.img or recovery.img is missing dtb then it'll fastboot boot but not boot after being flashed. it then kicks into fastboot (well, hboot on my htc devices anyway. fastboot on my older lg Optimus v.)

is your build including dtb for kernel (if it's new enough for that of course)