yashsingh1/xdaforums huggingface dataset:
[Android Software Development] andy_zhang:
TARGET_BOARD_PLATFORM := msm8953

TARGET_BOARD_PLATFORM_GPU := qcom-Adreno506

Can you find it for me, Thanx

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

I get error

cat: external/busybox/busybox-full.links: 没有那个文件或目录

bootable/recovery/gui/Android.mk:127: ****************************************************************************

bootable/recovery/gui/Android.mk:128: * TW_THEME is not valid: ''

bootable/recovery/gui/Android.mk:129: * Please choose an appropriate TW_THEME or create a new one for your device.

bootable/recovery/gui/Android.mk:130: * Available themes:

bootable/recovery/gui/Android.mk:131: * landscape_hdpi landscape_mdpi portrait_hdpi portrait_mdpi watch_mdpi

bootable/recovery/gui/Android.mk:132: ****************************************************************************

bootable/recovery/gui/Android.mk:133: *** stopping。 停
[Android Software Development] ashyx:
But what device is it?
[Android Software Development] andy_zhang:
Chinese 360n4s
[Android Software Development] ashyx:
Which device tree are you using?
[Android Software Development] andy_zhang:
Lg g3 d855
[Android Software Development] ashyx:
This would be a more appropriate device tree to use as a base:

https://github.com/markw-dev/android_device_xiaomi_markw-twrp

Go through each make file and modify as required, set flags change partition sizes, kernel and dtb, paths.

.
[Android Software Development] andy_zhang:
Thanx, i will try.
[Android Software Development] DarkFrenzy:
How to disable ntfs and foreign language and encryption features
[Android Software Development] pvineeth97:
I added TWRP_EVENT_LOGGING := true in BoardConfig.mk.

This is the recovery log file.

https://drive.google.com/file/d/0B9ZHDklJCY7DUkdHTW1GMGFyUU0/view?usp=drivesdk

Output of "grep . /sys/class/input/event*/device/name" in Android:

https://image.ibb.co/jK5nwF/Whats_App_Image_2017_03_13_at_11_46_55.jpg

In recovery.log it is mentioned:

/dev/input/event6
Event object: touch_dev
EV: ST minX: 0 maxX: 0 minY: 0 maxY: 0
EV: MT minX: 0 maxX: 720 minY: 0 maxY: 1280
[Android Software Development] andy_zhang:
I have some trouble.

bootable/recovery/gui/Android.mk:129: * TW_THEME is not valid: ''

bootable/recovery/gui/Android.mk:130: * Please choose an appropriate TW_THEME or create a new one for your device.

bootable/recovery/gui/Android.mk:131: * Available themes:

bootable/recovery/gui/Android.mk:132: * landscape_hdpi landscape_mdpi portrait_hdpi portrait_mdpi watch_mdpi

bootable/recovery/gui/Android.mk:133: ****************************************************************************

bootable/recovery/gui/Android.mk:134: *** stopping。 停止。

zfz@zfz-virtual-machine:~/Omni60$ ^C

zfz@zfz-virtual-machine:~/Omni60$ ^C

zfz@zfz-virtual-machine:~/Omni60$

I don't know how to solve it.
[Android Software Development] pvineeth97:
You did'nt mention "TW_THEME" in BoardConfig.mk.
[Android Software Development] andy_zhang:
I have meantioned, i have added it
[Android Software Development] Matt07211:
Adding Target screen/width height had fix the errors I was getting with TW_THEME.

Reference: https://github.com/Matt07211/androi...mmit/465e8cb590f92dfdfb2cd5918be74aa0a4fae5b6

That being said I haven't got my TWRP to boot yet so....
[Android Software Development] andy_zhang:
1505/obj/RECOVERY_EXECUTABLES/pigz_intermediates/export_includes

make: *** 没有规则可以创建“out/target/product/QK1505/obj_arm/SHARED_LIBRARIES/libbmlutils_intermediates/teamwin”需要的目标“out/target/product/QK1505/system/xbin/busybox”。 停止。

make: *** 正在等待未完成的任务....

Notice file: external/zlib/NOTICE -- out/target/product/QK1505/obj/NOTICE_FILES/src//system/lib64/libz.so.txt
[Android Software Development] ashyx:
You need to make sure each make file reflects the name of your device, for example change:

omni_full_markw.mk

to

omni_360n4s.mk

then modify its contents like so:

$(call inherit-product, vendor/omni/config/gsm.mk)

# Inherit from the common Open Source product configuration

$(call inherit-product, $(SRC_TARGET_DIR)/product/aosp_base_telephony.mk)

# Inherit from our custom product configuration

$(call inherit-product, vendor/omni/config/common.mk)

PRODUCT_NAME := omni_360n4s

PRODUCT_DEVICE := 360n4s

PRODUCT_BRAND := some_chinese_make

PRODUCT_MODEL := 360n4s

PRODUCT_MANUFACTURER := some_chinese_manufacturer

Each make file must be changed from

markw

to

360n4s

Where '360n4s' is the device name of your product.

Then to build you would use:

lunch omni_360n4s-eng
[Android Software Development] Matt07211:
~DELETED~

My content I post got cut off before the qoutr finished ?

I can't remember what I typed.
[Android Software Development] Matt07211:
Oh, seems like my text got cut out. ****. I was quoting the person above.
[Android Software Development] ashyx:
Yeh did it to me twice, bloomin xda labs!
[Android Software Development] Matt07211:
Yea, I was wondering why you kept having dots I'm your reply. XDA labs needs to be able to handle unicode characters better
[Android Software Development] _that:
And people who post build logs should build with LC_ALL=C so that everybody can read the messages.
[Android Software Development] pvineeth97:
Recovery logs are here: https://xdaforums.com/showpost.php?p=71405215&postcount=2894

I actually copied the kernel file from "recovery.img-kernel". I got it by extracting recovery.img from Carliv Image Kitchen. I never found zImage file from which I can rename it to kernel and use it.
[Android Software Development] andy_zhang:
Thanx again.

I have the erro:no common.mk.so I delete this line.
[Android Software Development] _that:
I was talking about people who post build logs and that they should build with LC_ALL=C in the environment.

Your recovery logs are incomplete, you didn't tell us if you touched the screen or if you got any output from the hexdump command.

And the kernel extracted from a boot image is actually a zImage.
[Android Software Development] Matt07211:
I'm fairly new to building TWRP, how is this done.

I'm currently at the stage of debugging why TWRP won't boot, got any tips on how to get better debug logs.

Another question, in my attached log I'm getting 2 specific types of errors.

The first one is about tzdata, looks like it's as simple as adding the below into BoardConfig.mk

# Time Zone data
PRODUCT_COPY_FILES += \
bionic/libc/zoneinfo/tzdata:recovery/root/system/usr/share/zoneinfo/tzdata

The second error(s) are:

I:Loading package: splash (/twres/splash.xml)
I:Load XML directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/splash.xml' directly
E:Package splash failed to load.
E:Failed to load splash screen XML.

I:Loading package: TWRP (/data/media/0/TWRP/theme/ui.zip)
I:Loading zip theme
I:Loading package: TWRP (/twres/ui.xml)
I:Load XML directly
E:LoadLanguageListDir '/twres/languages/' path not found
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/en.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/ui.xml' directly
E:Package TWRP failed to load. Failed to load base packages.
E:An internal error has occurred: unable to load theme.

Hopefully adding [URL"https://github.com/TEAM-Gummy/andro...e5f753bf88a3b500b2cd"]TW_SCREEN_BLANK_ON_BOOT[/URL] may be able to fix my problem.
[Android Software Development] pvineeth97:
Yes I have touched the screen. I provided you the recovery log as it is.

LOG: https://drive.google.com/file/d/0B9ZHDklJCY7DUkdHTW1GMGFyUU0/view

Do I need to include the kernel from the stock recovery or just extract it from boot.img and include it in my device tree?

Output of "grep . /sys/class/input/event*/device/name" in Android:

https://image.ibb.co/jK5nwF/Whats_App_Image_2017_03_13_at_11_46_55.jpg

In recovery.log it is mentioned:

/dev/input/event6
Event object: touch_dev
EV: ST minX: 0 maxX: 0 minY: 0 maxY: 0
EV: MT minX: 0 maxX: 720 minY: 0 maxY: 1280

Output from hexdump (From Android):

hexdump doesn't work inside TWRP.
[Android Software Development] _that:
This is only useful if your operating system uses some non-English locale. It should cause the build tools to emit English messages:

LC_ALL=C mka recoveryimage

Looks like twres from the theme isn't copied to your ramdisk image. What Android tree are you building in?
[Android Software Development] _that:
That depends on the device. Usually either should work.

Define "doesn't work". It's part of busybox so it should work.
[Android Software Development] pvineeth97:
Will try again.

---------- Post added at 01:15 AM ---------- Previous post was at 01:10 AM ----------

hexdump -C /dev/input/event6

gives empty output in recovery.
[Android Software Development] Matt07211:
Using the minimal omni manifest, lollipop 5.1.1.

Will adding something like product copy files into device.mk help with this or what?

I sadly didn't get to try my patch's I mentioned above last night cause the machine ibise wasn't online.
[Android Software Development] _that:
Then your kernel isn't sending any events and you need to look at the kernel source for the "touch_dev" device why. And please edit your post and remove the multiple quotes.
[Android Software Development] pvineeth97:
kernel source? Should I decompile the kernel I extracted from recovery or take the kernel source from opensource.lge.com?
[Android Software Development] GreyLeshy:
Hello everyone!

I have a working TWRP 3.1.0 and from it I deleted the folder kitakami-common\rootdir\system\sbin folder so that the files that were in this folder were taken from the system when loading the recovery.

But I can't mount the system partition in the file init.recovery.kitakami.rc. This file is processed exactly, I installed and tested. In the terminal, the teams are working.

on init
symlink /dev/block/platform/soc.0/f9824900.sdhci /dev/block/bootdevice

on fs
mount -t ext4 -o ro /dev/block/bootdevice/by-name/system /system

on boot
write /sys/class/android_usb/android0/idVendor 0FCE
# write /sys/class/android_usb/android0/idProduct 6${ro.usb.pid_suffix}
write /sys/class/android_usb/android0/idProduct 51D9

# Copy proprietary kernel modules
cp /system/lib/modules/core_ctl.ko /sbin/core_ctl.ko
cp /system/lib/modules/ecryptfs.ko /sbin/ecryptfs.ko
cp /system/lib/modules/kscl.ko /sbin/kscl.ko
cp /system/lib/modules/texfat.ko /sbin/texfat.ko
cp /system/lib/modules/mhl_sii8620_8061_drv.ko /sbin/mhl_sii8620_8061_drv.ko

# Load proprietary kernel modules
insmod /sbin/core_ctl.ko
insmod /sbin/ecryptfs.ko
insmod /sbin/kscl.ko
insmod /sbin/texfat.ko
insmod /sbin/mhl_sii8620_8061_drv.ko

Please help with this problem.
[Android Software Development] Captain_Throwback:
Why aren't you mounting system via recovery.fstab? You shouldn't need to mount anything in an init script.
[Android Software Development] GreyLeshy:
If to do through mount_all ./fstab.kitakami , mounted, but umount will not happen. And no files are copied from the script.
[Android Software Development] Captain_Throwback:
That's not the fstab I'm talking about. TWRP uses twrp.fstab or recovery.fstab for mounting partitions. Did you read the first post of this thread?
[Android Software Development] Matt07211:
I'm still suffering from these errors

I:Loading package: splash (/twres/splash.xml)
I:Load XML directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/splash.xml' directly
E:Package splash failed to load.
E:Failed to load splash screen XML.

I:Loading package: TWRP (/data/media/0/TWRP/theme/ui.zip)
I:Loading zip theme
I:Loading package: TWRP (/twres/ui.xml)
I:Load XML directly
E:LoadLanguageListDir '/twres/languages/' path not found
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/en.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/ui.xml' directly
E:Package TWRP failed to load. Failed to load base packages.
E:An internal error has occurred: unable to load theme.

https://github.com/Matt07211/android_device_samsung_xcover3lte

Googling doesn't bring up anything and my lack of experience is off no help, anyone able to shed some light on this problem or how to fix it would be great
[Android Software Development] Captain_Throwback:
Where are your device files?
[Android Software Development] Matt07211:
Oh im stupid, I thought I linked.

https://github.com/Matt07211/android_device_samsung_xcover3lte
[Android Software Development] Captain_Throwback:
Do you have splash.xml in your ramdisk?

EDIT: You're copying over a lot of files, rather than just putting them under recovery/root and letting them copy over to the ramdisk automatically. I also see that you're including your own init.rc, but it's missing this: https://github.com/omnirom/android_bootable_recovery/blob/android-7.1/etc/init.rc#L27

Any reason you can't just use the stock one, and add your device specific stuff to init.recovery.{ro.hardware}.rc?
[Android Software Development] Matt07211:
I haven't unpacked recovery.img to check yet, but I have checked the $OUT folder, where the ramdisk folder is (before it gets packed into the final product) and can verify its at least there in the final stages of building.

The error looks like it can find the splash.xml but has trouble doing anything else with it.

Edit: In reply to your edit, this is the first time ever doing a Device/ROM port and building a ROM/TWRP, so I don't know the best practices or how to go about doing​ things correctly.
[Android Software Development] Captain_Throwback:
Most device trees are pretty lean. Here's one of my TWRP-only trees: https://github.com/TeamWin/android_device_htc_oce/tree/android-7.1

And notice this folder: https://github.com/TeamWin/android_device_htc_oce/tree/android-7.1/recovery/root

That's where you put files that need to be added to the recovery ramdisk. The only makefiles I have are for setting up the device name, and the BoardConfig for setting up the relevant flags.

EDIT: If you're also trying to build AOSP/Lineage in addition to TWRP, then your tree will be much more extensive, but that goes outside the purview of this thread.
[Android Software Development] Matt07211:
I'm the second option, I'm trying to build ROM in addition to TWRP, but don't worry I won't ask rom building errors here ;)

I've got a few questions:

1) If I use TWRPs Init.rc would that affect loading splash.xml, meaning it may work or loading it? Geuss the easiest way to find out is to compile and test. (Machine I build on isn't online, so the results of this have got to Wait.)

2) So if I change it to "recovery/root/" I can remove the copy lines from my file, as it's done automatically, correct?

3) slightly off topic, but said ^ thing will also apply to boot ramdisk?, that is, I put the contents into "boot/root/". I doubt the other stuff like LineageOS Automatically copies files though.

Any thanks for your help, and I'll report back if changing the ramdisk layout and removing my init.rc has any affect.
[Android Software Development] Captain_Throwback:
1) Yes, if you use the TWRP init.rc, it will likely load the splash properly, as you're missing the LD_LIBRARY_PATH variable in the one you're currently copying over.

2) Yes, if you put your ramdisk files under recovery/root in your device folder, they will get placed in the recovery ramdisk automatically.

3) I don't know, but I doubt it. I think this is a recovery-specific feature.
[Android Software Development] Matt07211:
1) cool

2) Great

3) I geuss I'll have to find out.

If the error still persists, then I'll be back here later tonight.
[Android Software Development] GreyLeshy:
I read the first post and even if I refer to twrp.fstab or recovery.fstab, the system partition is also mounted, but it can not be unmounted afterwards. A partition firmware is also mounted, which is no longer mounted after unmounting. Files are not copied.
[Android Software Development] Captain_Throwback:
Sometime the system partition gets "locked up" if you build with debugging flags enabled. That's not an fstab problem, though. All your mounts should be in the twrp.fstab.
[Android Software Development] Matt07211:
Still didn't work, same errors still persist, any other ways I can debug it and/or fix it?

Edit:

Describing the current boor: When I try to boot to TWRP I get the initial phone logo (phone name and the word Android)it then seems to turn off, then light the screen back up (still black), then the screen get even brighter again, then the phone reboots to the OS
[Android Software Development] GreyLeshy:
In General I have made in the initialization script reference to the file in which prescribed already mounting and unmounting system, and loading proprietary kernel modules.

service proprietarymodules /sbin/proprietarymodules.sh

oneshot

disabled

user root

group root

seclabel u:r:recovery:s0

on fs

start proprietarymodules
[Android Software Development] AlxMAX:
I have a question, but first let me quote one of my messages in the dedicated TWRP thread in the Nexus 6 part.

Since that post, TWRP 3.1 was released and by decompiling it I have noticed 2 things:

those keymaster files and the QSEEComAPI module already included in the recovery.

the official recovery is based on Android 5.

The android-5.1, android-6.0 and adroid-7.0 branches of the proprietary_vendor_motorola repository of DonkeyCoyote have a file, device-partial.mk, with indications for the build system to copy the right files to the recovery ramdisk. Then android-7.1 branch has a file, device-vendor.mk, which doesn't have those entries. If I add those entries manually in my build tree, the recovery works. My question would be if another decryption mechanism is planned for the Nexus 6 recovery (vold?) or that's the right thing to do (add those entries to device-vendor.mk for good).
[Android Software Development] bjeastin:
IMO I would change it to your devices Board_Kernel_CMDLINE there isnt any harm in doing so if its bootlooping and not working anyways
[Android Software Development] Zauq:
I am using unofficial version of TWRP for my device "Qiku Terra". TWRP works perfectly except the external sdcard, OTG works just fine though. It's not shown in the TWRP. Upon checking I found that mmcblk1p1 isn't present while in recovery, I used "df" in terminal to check the same.

I have tried all the basis fixes such as add "external_sd......." in the twrp.fstab and others but to no avail.

Anyone has any idea???
[Android Software Development] andy_zhang:
Can you give me your coad?
[Android Software Development] Zauq:
Please respond in English as I don't know Chinese. I've translated your response on google but still didn't get what you're trying to say. Thanks
[Android Software Development] andy_zhang:
Your mobile phone should be the product of China. My mobile phone is also qiku 360n4s. I want to make him twrp, But always fail.

---------- Post added at 07:42 AM ---------- Previous post was at 07:39 AM ----------

I want to make one twrp for my mobile phone. But he always fails, always making mistakes.

I have no device.i modify from other. Can u help me?
[Android Software Development] Zauq:
How you're trying to port twrp for you device?? What are the specs of your device?? My Qiku Terra is from China and I am Chinese 360 OS.
[Android Software Development] andy_zhang:
My device is 360os 360n4s. I wann Learn to make your own. But I don't know how to do it.
[Android Software Development] Zauq:
Is your bootloader unlocked?? Is your device MediaTek or Snapdragon??
[Android Software Development] andy_zhang:
Not be unlock, but can via 9008 flash it, my device is snap
[Android Software Development] andy_zhang:
make: *** [/home/zfz/Omni60/out/host/linux-x86/obj/EXECUTABLES/checkpolicy_intermediates/policy_parse.cpp] 错误 126
[Android Software Development] dom133:
I have this error when i try compile recovery
[Android Software Development] pvineeth97:
hahaha... I created a new device tree for 6.0.1. Fork that again.

Anyways... I have the same error. I solved it once long back but don't remember it.

Edit: Solved.
[Android Software Development] pvineeth97:
We want to make our TWRP build for our device OFFICIAL.

Whom to contact? :D
[Android Software Development] Ibuprophen:
Go to the twrp.me website and there's information in there outlining that type of submission.

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...

***PLZ THANK ME WITH A THUMBS UP***
[Android Software Development] GreyLeshy:
Help, my recovery does not accept the password for decryption of DATA.

Firmware Nougat Stock, TWRP 3.1.0, config: init.recovery.kitakami.rc, pulldecryptfiles.sh.

Please tell me how can I decrypt the data in recovery?
[Android Software Development] pvineeth97:
Exact link please. I couldn't find it :D
[Android Software Development] Matt07211:
I searched the word "twrp" clicked the first link and clicked "Contact Us".

https://twrp.me/contactus/
[Android Software Development] CrashOverride93:
You have a contact form available on the official teamwin website.

www.twrp.me
[Android Software Development] Captain_Throwback:
Recovery log?
[Android Software Development] GreyLeshy:
Log
[Android Software Development] Matt07211:
Sorry to bump my old post, but I'm still having trouble with this error. My original post )the one I'm quoting) has the log and device repo link. I've manually gone through my recovery ramdisk by hand and everything seems to be as it should but the error persists.
[Android Software Development] Pruikki:
Question! on behaf of Snapdragon 800 Galaxy S 4 (i9506) users

Can TRWP replace Odin? on my Rooted phone.

can i just install the app on my SG S4 S800 edition and in there select the correct recovery and it does the rest?

is it possible it can be that easy?

thanks
[Android Software Development] Captain_Throwback:
Link to device files?
[Android Software Development] GreyLeshy:
Log recovery from one device
[Android Software Development] Captain_Throwback:
:confused:

Where are your device files? The issue is likely in there somewhere. Without seeing them I can't tell you what the issue might be.
[Android Software Development] GreyLeshy:
Files for the device, here it should be fine. General configuration: kitakami, common.
[Android Software Development] Captain_Throwback:
Why don't you try just putting the necessary blobs in the recovery ramdisk? Or is there a size issue if you do that? You could also try vold decrypt, if you can't get standard TWRP decrypt working, but I suspect your issue is just some missing blobs. Where is your recovery/root folder?
[Android Software Development] GreyLeshy:
Libs placed in recovery but still a recovery key does not accept.

Probably some modules missing, but has not yet figured out what.
[Android Software Development] Mohtasham jaffery:
boardconfig.mk

what is boardconfig.mk. where it located in android 5.1
[Android Software Development] NepoRood:
BoardConfig.mk, is the device configuration make file, it is used during the Android build process and is not located inside a ROM. If you go to Github you can see one of mine :good:
[Android Software Development] _that:
Type exactly these words into Google and it gives you this link: https://source.android.com/source/add-device.html

If you don't understand something on that page, use Google before asking here. If you're still stuck after 30-60 minutes of research, you'll know enough to ask a smart question as described here: http://www.catb.org/esr/faqs/smart-questions.html