Assistant
REPLY |
Building TWRP recovery from source |
Message#1 17.01.15, 23:38 | |
Starting a new life. [offline] Topics Curator Group: Curators Messages 2561 Check in: 03.04.12 Xiaomi Redmi Note 4X Snapdragon 3/32 Reputation: 699 | ������ TWRP recovery �� ���������� downloadOrder table recovery | How to build cwm � | CWM Recovery Compilation � | Creating recovery for MTK �
What do we need: AIDA64 and DiskInfo on smartphone Ubuntu 12.04 x64 Unlimited Internet, as it will be downloaded about 12 gig source. 38.5 GB of free space, this is only on the source code and on the assembly + 10 gigs on the system itself. I got to Ubuntu 16.04.2 x64 and Android 6.0. The sources Omni 6.0.1 I weigh 75 gigs + will be unpacked and for a total of about 200 gigs to build. Build on Ubuntu 17.10 If you do not have your own sources, then look for the config (device) of a similar device on the same processor onGithub. Here to you for example my configTWRP_D10A_HighScreen And so let's get started Under the utility spoiler there is a video instruction for assembling TWRP Install Ubuntu 12.04 x64 or 16.04.2 x64 (as you are looking for yourself, I will not paint) For Ubuntu 12.04 x64 and Android 4.4.4 Install the necessary packages sudo apt-get install bison build-essential curl flex g ++ - multilib gcc-multilib git-core gnupg gperf lib32ncurses5-dev libxml2-utils lzop pngcrush schedtool squashfs-tools xsltproc zip zlib1g-dev Next, we put Java Oracle 6 sudo add-apt-repository ppa: webupd8team / java sudo apt-get update sudo apt-get install oracle-java6-installer Login on github (quotes are not needed) git config --global user.name "your nickname" git config --global user.email "your mail" Next, create folders mkdir ~ / bin mkdir ~ / omni Install repo curl http://commondatastorage.googleapis.com/git-repo-downloads/repo>~ / bin / repo chmod a + x ~ / bin / repo Add a variable echo "export PATH = ~ / bin: $ PATH">>~ / .bashrc And download the source, android omni 4.4.4. cd ~ / omni repo init -u https://github.com/omnirom/android.git -b android-4.4 repo sync Now we wait while about 12 gig sources are downloaded. For Ubuntu 16.04.2 x64 and Android 6.0 Install the necessary packages sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev gcc-multilib g ++ liblii-dev-i386 libc6-dev-i386 dev libxml2-utils xsltproc unzip maven schedtool For Android 5.0 - 6.0 you need openjdk 7 sudo add-apt-repository ppa: openjdk-r / ppa sudo apt-get update sudo apt-get install openjdk-7-jdk Login on github'e git config --global user.name "your nickname" git config --global user.email "your mail" Further, according to the familiar scheme mkdir ~ / bin PATH = ~ / bin: $ PATH echo 'PATH = ~ / bin: $ PATH'>>~ / .bashrc echo 'export USE_CCACHE = 1'>>~ / .bashrc curl https://storage.googleapis.com/git-repo-downloads/repo>~ / bin / repo chmod a + x ~ / bin / repo Create a folder for omnirom sources and enter it. mkdir omni cd omni Downloading source repo init -u https://github.com/omnirom/android.git -b android-6.0 repo sync Well, let's start writing a config for our device Finalization spoiler And now the fun begins First, create the device folder for your device. cd ~ / omni / device mkdir -p vendor_name / device_name mkdir -p HighScreen / D10A_HighScreen Create an Android.mk file with the contents: LOCAL_PATH: = $ (call my-dir) ifeq ($ (TARGET_DEVICE), device_name) include $ (call all-makefiles-under, $ (LOCAL_PATH)) endif LOCAL_PATH: = $ (call my-dir) ifeq ($ (TARGET_DEVICE), D10A_HighScreen) include $ (call all-makefiles-under, $ (LOCAL_PATH)) endif PRODUCT_MAKEFILES: = \ $ (LOCAL_DIR) /device_name.mk \ $ (LOCAL_DIR) /omni_device_name.mk I look like PRODUCT_MAKEFILES: = \ $ (LOCAL_DIR) /D10A_HighScreen.mk \ $ (LOCAL_DIR) /omni_D10A_HighScreen.mk The contents of the device_name.mk file should look like this: LOCAL_PATH: = device / vendor_name / device_name $ (shell mkdir -p $ (OUT) / obj / KERNEL_OBJ / usr) ifeq ($ (TARGET_PREBUILT_KERNEL),) LOCAL_KERNEL: = $ (LOCAL_PATH) / kernel else LOCAL_KERNEL: = $ (TARGET_PREBUILT_KERNEL) endif PRODUCT_COPY_FILES + = \ $ (LOCAL_PATH) / kernel: kernel \ $ (LOCAL_PATH) /dt.img:dt.img \ $ (LOCAL_PATH) /recovery.fstab:root/recovery.fstab $ (call inherit-product, build / target / product / full.mk) PRODUCT_NAME: = device_name Attention if in your kernel and recovery there is no dt.img file, then you should not have a line: $ (LOCAL_PATH) /dt.img:dt.img \ It looks like this to me: LOCAL_PATH: = device / HighScreen / D10A_HighScreen $ (shell mkdir -p $ (OUT) / obj / KERNEL_OBJ / usr) ifeq ($ (TARGET_PREBUILT_KERNEL),) LOCAL_KERNEL: = $ (LOCAL_PATH) / kernel else LOCAL_KERNEL: = $ (TARGET_PREBUILT_KERNEL) endif PRODUCT_COPY_FILES + = \ $ (LOCAL_PATH) / kernel: kernel \ $ (LOCAL_PATH) /dt.img:dt.img \ $ (LOCAL_PATH) /recovery.fstab:root/recovery.fstab $ (call inherit-product, build / target / product / full.mk) PRODUCT_NAME: = D10A_HighScreen # Inherit device configuration $ (call inherit-product, device / vendor_name / device_name / device_name.mk) # Device identifier. This must come after all inclusions PRODUCT_DEVICE: = device_name PRODUCT_NAME: = omni_device_name PRODUCT_BRAND: = vendor_name PRODUCT_MODEL: = # device model PRODUCT_MANUFACTURER: = vendor_name All these values ​​are in your system / build.prop stock firmware, rely primarily on them. I have so # Inherit device configuration $ (call inherit-product, device / HighScreen / D10A_HighScreen / D10A_HighScreen.mk) # Device identifier. This must come after all inclusions PRODUCT_DEVICE: = D10A_HighScreen PRODUCT_NAME: = omni_D10A_HighScreen PRODUCT_BRAND: = HighScreen PRODUCT_MODEL: = Boost 2se PRODUCT_MANUFACTURER: = HighScreen In the split_img folder, take the file recovery.img-zImage, rename it to kernel. In the same folder, take the file recovery.img-dtb and rename it to dt.img, if this file is not there, we disassemble the kernel and look for there only the name will be boot.img-dtb, if there is not, then it is not needed. Both files (or one) are left in the device / vendor_name / device_name path Next, go to the ramdisk / etc folder, take the file recovery.fstab, put it there as the previous 2 files and edit it to make it look like this, but the paths should be yours! / system ext4 /dev/block/platform/msm_sdcc.1/by-name/system / data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata / cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache / boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot / recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery / external_sd vfat / dev / block / mmcblk1p1 flags = display = "External_sd"; storage; wipeingui; removable / internal_sd vfat /dev/block/platform/msm_sdcc.1/by-name/usbmsc flags = display = "Internal_sd"; storage; wipeingui; removable / usb-otg vfat / dev / block / sda1 / dev / block / sda flags = display = "USB OTG"; storage; wipeingui; removable We create the BoardConfig.mk file here the most difficult and some values ​​will have to be pulled from the device on the same process. Well, let's go, we write there: # Platform TARGET_BOARD_PLATFORM: = Open AIDA64, point CPU, first line. I have so # Platform TARGET_BOARD_PLATFORM: = msm8226 Further # Architecture TARGET_ARCH: = # AIDA64 second line, TARGET_ARCH_VARIANT: = TARGET_CPU_ABI: = TARGET_CPU_ABI2: = TARGET_CPU_SMP: = TARGET_CPU_VARIANT: = These values ​​also write off, I have it so # Architecture TARGET_ARCH: = arm TARGET_ARCH_VARIANT: = armv7-a-neon TARGET_CPU_ABI: = armeabi-v7a TARGET_CPU_ABI2: = armeabi TARGET_CPU_SMP: = true TARGET_CPU_VARIANT: = krait Further # Bootloader TARGET_NO_BOOTLOADER: = true TARGET_BOOTLOADER_BOARD_NAME: = The first line does not change, and in the second the name of the chip is mine # Bootloader TARGET_NO_BOOTLOADER: = true TARGET_BOOTLOADER_BOARD_NAME: = MSM8226 Here we will stop on more in detail: # Kernel TARGET_PREBUILT_KERNEL: = # here we specify the path to the device / vendor_name / device_name / kernel kernel BOARD_KERNEL_CMDLINE: = BOARD_KERNEL_BASE: = BOARD_KERNEL_PAGESIZE: = BOARD_KERNEL_SEPARATED_DT: = true BOARD_MKBOOTIMG_ARGS: = With the first line, the line BOARD_KERNEL_CMDLINE, go to the folder of the parsed recovery and look for the file recovery.img-cmdline and enter its contents in this line. The string BOARD_KERNEL_BASE in the same folder as the recovery.img-base file, its contents is entered in this string. Line BOARD_KERNEL_PAGESIZE in the same file recovery.img-pagesize its contents we enter in this line. This BOARD_KERNEL_SEPARATED_DT: = true line does not change. Here BOARD_MKBOOTIMG_ARGS first specify the path to dt.img - dt device / vendor_name / device_name / dt.img Next - kernel_offset write the contents of the file recovery.img-kerneloff Attention if in your kernel and recovery there is no dt.img file, then you should not have a line: BOARD_KERNEL_SEPARATED_DT: = true And in the line: BOARD_MKBOOTIMG_ARGS: = --dt device / vendorname / devicename / dt.img --kernel_offset 0x ******** --ramdisk_offset 0x ******** - tags_offset 0x ******* * There should be no path to this file.--dt device / vendorname / devicename / dt.img, just write like this: BOARD_MKBOOTIMG_ARGS: = --kernel_offset 0x ******** --ramdisk_offset 0x ******** --tags_offset 0x ******** Next --ramdisk_offset here is the contents of the file recovery.img-ramdiskoff And finally - tags_offset is the contents of the file recovery.img-tagsoff, you also need to add before each value 0x (your characters) for clarity, see below. It looks like this to me # Kernel TARGET_PREBUILT_KERNEL: = device / HighScreen / D10A_HighScreen / kernel BOARD_KERNEL_CMDLINE: = console = null androidboot.hardware = qcom user_debug = 31 msm_rtb.filter = 0x37 lpj = 192000 BOARD_KERNEL_BASE: = 0x00000000 BOARD_KERNEL_PAGESIZE: = 2048 BOARD_KERNEL_SEPARATED_DT: = true BOARD_MKBOOTIMG_ARGS: = --dt device / HighScreen / D10A_HighScreen / dt.img --kernel_offset 0x00008000 --ramdisk_offset 0x02000000 - tags_offset 0x01e00000 The next thing we need is the size of the partitions in bytes. Download from Google Play "terminal emulator" and write cat / proc / partitions Open DiskInfo, 3 points, settings, set daws Partition name, Expert mode and Unmounted partitions. We look for the necessary section, we take number from the terminal and we multiply by 1024, we fill # Partitions BOARD_BOOTIMAGE_PARTITION_SIZE: = BOARD_RECOVERYIMAGE_PARTITION_SIZE: = BOARD_SYSTEMIMAGE_PARTITION_SIZE: = BOARD_CACHEIMAGE_PARTITION_SIZE: = BOARD_USERDATAIMAGE_PARTITION_SIZE: = BOARD_FLASH_BLOCK_SIZE: = 131072 The string BOARD_FLASH_BLOCK_SIZE is pulled from a similar device, but I have not seen another value for now. # Recovery TARGET_RECOVERY_PIXEL_FORMAT: = "RGBX_8888" # Open AIDA64, Display and at the bottom of the line GL_EXT_texture_format TARGET_USERIMAGES_USE_EXT4: = true BOARD_HAS_LARGE_FILESYSTEM: = true BOARD_USE_CUSTOM_RECOVERY_FONT: = \ "roboto_15x24.h \" BOARD_SUPPRESS_EMMC_WIPE: = true And last # TWRP HAVE_SELINUX: = true DEVICE_RESOLUTION: = # here we write the screen resolution TW_IGNORE_MAJOR_AXIS_0: = # we look at it like a similar device RECOVERY_GRAPHICS_USE_LINELENGTH: = # we are looking like a similar device BOARD_HAS_NO_REAL_SDCARD: = # # this is if you have a separate partition for internal memory, and not in the / data section (/ data / media) TW_DEFAULT_EXTERNAL_STORAGE: = # we are looking like a similar device TW_INTERNAL_STORAGE_PATH: = # here we write for example "/ internal_sd" - you have these values ​​in recovery.fstab TW_INTERNAL_STORAGE_MOUNT_POINT: = # then "internal_sd" TW_EXTERNAL_STORAGE_PATH: = # here we write "/ external_sd" TW_EXTERNAL_STORAGE_MOUNT_POINT: = # then "external_sd" # USB Mounting TARGET_USE_CUSTOM_LUN_FILE_PATH: = / sys / devices / platform / msm_hsusb / gadget / lun% d / file # This is the line you are looking for yourself using the root explorer to go through this path, you may have another. And create the last vendorsetup.sh file with the contents add_lunch_combo omni_device_name-userdebug I have it so add_lunch_combo omni_D10A_HighScreen-userdebug Everything, now we will start assembly We collect I want to draw your attention, collect recovery on the commands below, if you collect with the command mka or some other, then look for answers in another topic, you can not write here. [/ B] It's pretty simple cd ~ / omni . build / envsetup.sh lunch omni_device_name-userdebug make -j5 recoveryimage # here we write the number of cores of your CPU +1 Well, now we wait, in the omni / out / folder I don’t remember the exact path, then I’ll write, and you’ll find it, there will be a freshly baked recovery.img. Examples Utility What would twrp teach to understand the vendor section for project treble We unlock the lock on MTK processors. Solving the TWRP 3.2.3 build problem on Omni 7.1 source Another version of the TWRP assembly TWRP assembly instruction video Flags for BoardConfig.mk More flags for BoardConfig.mk Build TWRP on Lineage OS 14.1 Solving the problem of time synchronization Solving the problem of landscape / portrait orientation on the tablet Addition to the main instruction, assembly TWRP 3.0. * From wladimir_tm Build TWRP with a minimum set of sources Tips to reduce the size of the recovery from wladimir_tm Installing openjdk7 on Ubuntu 17.04 Russian translation TWRP 2.8.7.0 Useful post for phones with intel processes Solution for system / sepolicy / domain.te error: 446: ERROR 'unknown type camera' at token Sources In qms with requests to help me, do not write, I gave you all the necessary information. Only editable suggestions are accepted. Good luck in the assembly of the recovery. Post has been editedderak1129 - 16.05.19, 22:02 Reason for editing: what would twrp teach to understand the vendor section for project treble |
Message#2202 05.03.19, 00:45 | |
Experienced [offline] Group: Friendssavagemessiahzine.com Messages 400 Check in: 04.03.16 Runbo Q5 4G Reputation: 42 | Is the previous versions of OmniROM TWRP available in the repository? When I try to synchronize version 6.0, I get 9.0, the -b key android-6.0 is ignored. github.com/omnirom/android.git repo init -uhttps://github.com/omnirom/android.git -b android-6.0 Fromhttps://github.com/omnirom/android e78d181..f7d4332 android-9.0 ->origin / android-9.0 .repo / manifests /: discarding 165 commits This repository did not find the required one. github.com/minimal-manifest-twrp AOSP repo init -u git: //github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp.git -b twrp-7.1 fatal: Couldn't find remote ref refs / heads / twrp-7.1 fatal: Couldn't find remote ref refs / heads / twrp-7.1 fatal: can not be obtained manifest git: //github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp.git It turns out that there is only this repository, the minimum? github.com/minimal-manifest-twrp OMNI repo init -u git: //github.com/minimal-manifest-twrp/platform_manifest_twrp_omni.git -b twrp-7.1 remote: Enumerating objects: 116, done. remote: Counting objects: 100% (116/116), done. remote: Total 557 (delta 116), reused 116 (delta 116), pack-reused 441 Receiving objects: 100% (557/557), 236.74 KiB | 904.00 KiB / s, done. Resolving deltas: 100% (254/254), completed with 41 local objects. From git: //github.com/minimal-manifest-twrp/platform_manifest_twrp_omni * [new branch] master ->origin / master * [new branch] twrp-4.4 ->origin / twrp-4.4 * [new branch] twrp-5.1 ->origin / twrp-5.1 * [new branch] twrp-6.0 ->origin / twrp-6.0 * [new branch] twrp-7.1 ->origin / twrp-7.1 * [new branch] twrp-8.0 ->origin / twrp-8.0 * [new branch] twrp-8.1 ->origin / twrp-8.1 * [new branch] twrp-8.1-macOS ->origin / twrp-8.1-macOS * [new branch] twrp-9.0 ->origin / twrp-9.0 * [new tag] android-6.0.1_r46 ->android-6.0.1_r46 .repo / manifests /: discarding 4 commits |
Message#2203 10.03.19, 09:52 | |
Starting a new life. [offline] Topics Curator Group: Curators Messages 2561 Check in: 03.04.12 Xiaomi Redmi Note 4X Snapdragon 3/32 Reputation: 699 | K Dear friends, since cases of flooding and offtopic have become frequent, I ask you to follow the rules of the forum and not deviate from the topic of discussion. And also if you want to help me with the removal of unwanted posts, minus the post. And I ask you not to ply offtop, you do not need to encourage him. -------------------- Xiaomi Redmi Note 4X If there are people who learn German and live in St. Petersburg, write in a personal, we will communicate in German. |
Message#2204 11.03.19, 08:39 | |
Veteran [offline] Group: Friendssavagemessiahzine.com Messages 1335 Check in: 25.09.12 Jiayu S3 Advanced Reputation: 182 | Tell me, I compiled TWRP, at first glance everything works, but I would like to be able to remove the encryption of the data section (RM Forceencrypt button on the screenshot from another recovery). Options TW_INCLUDE_CRYPTO: = true TARGET_HW_DISK_ENCRYPTION: = true BoardConfig.mk included. How to add this button? Phone Lenovo Z5, the source here:https://github.com/ixm...d_device_lenovo_jd2018 Post has been editedgfofanov - 11.03.19, 08:39 |
Message#2205 11.03.19, 21:33 | |
Guru [offline] Group: Friendssavagemessiahzine.com Messages 2476 Check in: 26.07.11 Reputation: 794 | maybe someone knows or tells you where to dig I try to turn on logcat, then to see why the keymaster crashes, but I get 14,2488,323589254, -; init: starting service 'logd' ... 14,2489,323589994, -; init: starting service 'keymaster-3-0' ... 14,2490,323590681, -; init: Created socket '/ dev / socket / logd', mode 666, user 1036, group 1036 14,2491,323590847, -; init: Created socket '/ dev / socket / logdr', mode 666, user 1036, group 1036 14,2492,323590973, -; init: Created socket '/ dev / socket / logdw', mode 222, user 1036, group 1036 31,2493,323596989, -; logd: failed to set AID_LOGD uid 14,2494,323597551, -; init: Service 'logd' (pid 939) exited with status 255 14,2495,323597585, -; init: Sending signal 9 to service 'logd' (pid 939) process group ... 14,2496,323597685, -; libprocessgroup: Successfully killed process cgroup uid 0 pid 939 in 0ms 14,2497,323615070, -; init: Service 'keymaster-3-0' (pid 940) received signal 6 14,2498,323615099, -; init: Sending signal 9 to service 'keymaster-3-0' (pid 940) process group ... 14,2499,323615199, -; libprocessgroup: Successfully killed process cgroup uid 0 pid 940 in 0ms |
Message#2206 12.03.19, 15:57 | |
Experienced [offline] Group: Friendssavagemessiahzine.com Messages 400 Check in: 04.03.16 Runbo Q5 4G Reputation: 42 | If you have the last message in the logs: # make: Nothing to be done for 'recoveryimage'. #### make completed successfully (20 seconds) #### You want to compile the recovery.img file for TWRP and specify the parameter in the BoardConfig.mk file TARGET_NO_BOOTLOADER: = true then the file recovery.img is not formed. Although the TARGET_NO_BOOTLOADER: = true parameter means that you do not need to compile the bootloader but it also affects recovery.img. At the same time, there are no errors in the logs, as make considers that everything is good and correct, and everything goes according to the plan. |
Message#2207 12.03.19, 19:31 | |
Trpc [offline] Group: Friendssavagemessiahzine.com Messages 2003 Check in: 09.04.16 Apple iPhone SE Reputation: 203 | Good day. The brightness does not change in recovery. TW_BRIGHTNESS_PATH: = "/ sys / class / leds / lcd-backlight / brightness" is registered during the build (as in the ramdisk), from TWRP itself I tried to send 255 or 0 manually to all found brightness files through the terminal, nothing changes at all (except for indicator brightness). And the recovery crashes when installing archives from a memory card (I / O ERRORS), but everything works with internal memory. Android 6, TWRP 3.2.3-0, Z00ED, treehttps://github.com/Xsa...TWRP_device_asus_azure, almost useless loghttps: //paste.fedorapr...MzRRgRObaCFWztr2alUJ2Q Post has been editedEl'Xsanori Leo - 12.03.19, 20:18 -------------------- Therel0adedProject C.by Xsanori L. AMD K16.3 IMC // Intel GL960 | AMD A8-7410 / / Intel Core 2 Duo T7500 | AMD Radeon R5 + AMD Radeon R5 M430 // Intel GMA X3100 |
Message#2208 12.03.19, 20:52 | |
The local [online] Group: Friendssavagemessiahzine.com Messages 3350 Check in: 03.01.14 Xiaomi Redmi 5 3/32 Reputation: 1513 | Here isthisI would comment it out for now, butthiswould do this: TW_MAX_BRIGHTNESS: = 4095 Well, why? On LOST.DIR swears. Card format did not try? -------------------- My humble works on 4 A man cannot know everything and possess the full truth, but he can strive for it ... |
Message#2209 12.03.19, 23:00 | |
Trpc [offline] Group: Friendssavagemessiahzine.com Messages 2003 Check in: 09.04.16 Apple iPhone SE Reputation: 203 | Bodya-Kolibass As for the flash drive, you were right, as it turned out, she ordered to live a long time - the memory split, read / write errors even under the line, etc., went. Well, in short, go under the acronym. But the brightness for some reason did not start, the level of the slider does not change. I haven’t yet tried to send signals manually. It seems that this is something asus namudrili themselves, well, I will try to chemize, probably ... -------------------- Therel0adedProject C.by Xsanori L. AMD K16.3 IMC // Intel GL960 | AMD A8-7410 / / Intel Core 2 Duo T7500 | AMD Radeon R5 + AMD Radeon R5 M430 // Intel GMA X3100 |
Message#2210 17.03.19, 00:20 | |
Experienced [offline] Group: Friendssavagemessiahzine.com Messages 400 Check in: 04.03.16 Runbo Q5 4G Reputation: 42 | if make yields a single error #### make failed to build some targets (32 seconds) #### and nothing else, for example GEN printutils / Config.in HOSTCC scripts / basic / fixdep HOSTCC scripts / basic / split-include /home/mtumanov/omni/external/busybox/scripts/basic/split-include.c: In function 'main': /home/mtumanov/omni/external/busybox/scripts/basic/split-include.c:134:6: warning: ignoring return value of gets gets declared declared fgets (old_line, buffer_size, fp_target); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ HOSTCC scripts / basic / docproc GEN / home / mtumanov / omni / out / target / product / F1m / obj / busybox / full / Makefile HOSTCC scripts / kconfig / conf.o /home/mtumanov/omni/external/busybox/scripts/kconfig/conf.c: In function 'conf_askvalue': /home/mtumanov/omni/external/busybox/scripts/kconfig/conf.c:106: warning: ignoring return value of gets warn declared fgets (line, 128, stdin); ^~~~~~~~~~~~~~~~~~~~~~~ /home/mtumanov/omni/external/busybox/scripts/kconfig/conf.c: In function 'conf_choice': /home/mtumanov/omni/external/busybox/scripts/kconfig/conf.c.0454:4: warning: ignoring return value of with gets declared declared declared declared declared declared [-Wunused-result] fgets (line, 128, stdin); ^~~~~~~~~~~~~~~~~~~~~~~ HOSTCC scripts / kconfig / kxgettext.o HOSTCC scripts / kconfig / mconf.o /home/mtumanov/omni/external/busybox/scripts/kconfig/mconf.c: In function 'show_textbox': /home/mtumanov/omni/external/busybox/scripts/kconfig/mconf.c:847:2: warning: ignoring return value of write write ’, with attribute warn_unused_result [-Wunused-result] write (fd, text, strlen (text)); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /home/mtumanov/omni/external/busybox/scripts/kconfig/mconf.c: In function 'exec_conf': /home/mtumanov/omni/external/busybox/scripts/kconfig/mconf.c:481:2.73: warning: ignoring return value, added with warn_unused_result [-Wunused-result] pipe (pipefd); ^~~~~~~~~~~~ SHIPPED scripts / kconfig / zconf.tab.c SHIPPED scripts / kconfig / lex.zconf.c SHIPPED scripts / kconfig / zconf.hash.c HOSTCC scripts / kconfig / zconf.tab.o In file included from scripts / kconfig / zconf.tab.c: 152: 0: scripts / kconfig / zconf.hash.c: 155: 43: warning: 'kconf_id_strings_contents' is static but used in inline function 'kconf_id_lookup' which is not static #define kconf_id_strings ((const char *) & kconf_id_strings_contents) ^ scripts / kconfig / zconf.hash.c: 222: 44: note: in expansion of macro 'kconf_id_strings' register const char * s = o + kconf_id_strings; ^~~~~~~~~~~~~~~~ scripts / kconfig / zconf.hash.c: 215: 26: warning: 'kconf_id_hash' is static but used in inline function 'kconf_id_lookup' which is not static register int key = kconf_id_hash (str, len); ^~~~~~~~~~~~~ scripts / kconfig / zconf.hash.c: 171: 26: warning: 'wordlist' is static but it is not in static static struct kconf_id wordlist [] = ^~~~~~~~ HOSTLD scripts / kconfig / conf scripts / kconfig / conf -s Config.in # # using defaults found in .config # SPLIT include / autoconf.h ->include / config / * GEN include / bbconfigopts.h HOSTCC applets / usage /home/mtumanov/omni/external/busybox/applets/usage.c: In function 'main': /home/mtumanov/omni/external/busybox/applets/usage.c:52:50: warning: ignoring return value of the warning_united_result [-Wunused-result] write (STDOUT_FILENO, usage_array [i] .usage, strlen (usage_array [i] .usage) + 1); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ GEN include / usage_compressed.h HOSTCC applets / applet_tables /home/mtumanov/omni/external/busybox/applets/applet_tables.c: In function 'main': /home/mtumanov/omni/external/busybox/applets/applet_tables.c:144:4: warning: ignoring return value of gets gets declared declared fgets (line_old, sizeof (line_old), fp); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ GEN include / applet_tables.h CC applets / applets.o LD applets / built-in.o HOSTCC applets / usage_pod make [1]: Leaving directory '/ home / mtumanov / omni / external / busybox' #### make failed to build some targets (32 seconds) #### I was helped to add a description of the second processor architecture to the BoardConfig.mk file TARGET_2ND_ARCH: = arm TARGET_2ND_ARCH_VARIANT: = armv7-a-neon TARGET_2ND_CPU_VARIANT: = cortex-a53 TARGET_2ND_CPU_ABI: = armeabi-v7a TARGET_2ND_CPU_ABI2: = armeabi after that the make error went away. The first processor architecture is TARGET_ARCH: = arm64 TARGET_ARCH_VARIANT: = armv8-a TARGET_CPU_VARIANT: = cortex-a53 TARGET_CPU_ABI: = arm64-v8a |
Message#2211 18.03.19, 07:50 | |
Man with straight arms [online] Group: Curators Messages 2729 Check in: 26.12.13 Asus MeMO Pad 7 ME176CX Reputation: 761 | gfofanovApparently you have a modified assembly, because there is no such pribluda in the official repo, drip in the direction of the already existing TWRP Posted on 03/18/2019 07:52: depesh1977if it doesn't start, there is a cant in the tree, no more options Posted on 03/18/2019 07:55: No differenceBy the way, if you need to download the sources of the TvRP itself with handles, if there is no need to build version 2.8.7.0 or lower, if the kernel is 3.18. * then the version of the android does not matter here -------------------- |
Message#2212 18.03.19, 08:27 | |
Guru [online] Group: Friendssavagemessiahzine.com Messages 3094 Check in: 11.08.13 Lenovo Vibe B A2016 Reputation: 151 | And dt.img can mow. It does not seem to be in boot and recovery, but in the source code of the kernel there is. When compiling in the log, it skips lines. And I collected the tree myself and took it from a similar donor. By the way, I collected in two stages. At the first error, the core was asked to out, and the assembly went further. Well, it was going accordingly then. I downloaded and 6 and 7 minimum package tvrp, also going, but did not start. -------------------- |
Message#2213 18.03.19, 08:29 | |
Man with straight arms [online] Group: Curators Messages 2729 Check in: 26.12.13 Asus MeMO Pad 7 ME176CX Reputation: 761 | |
Message#2214 18.03.19, 08:30 | |
Guru [online] Group: Friendssavagemessiahzine.com Messages 3094 Check in: 11.08.13 Lenovo Vibe B A2016 Reputation: 151 | |
Message#2215 18.03.19, 08:42 | |
Man with straight arms [online] Group: Curators Messages 2729 Check in: 26.12.13 Asus MeMO Pad 7 ME176CX Reputation: 761 | depesh1977nothing supernatural, MT6735 porridge.zip(6.06 MB) Post has been editedSkyrimus - 18.03.19, 08:44 -------------------- |
Message#2216 18.03.19, 09:03 | |
Man with straight arms [online] Group: Curators Messages 2729 Check in: 26.12.13 Asus MeMO Pad 7 ME176CX Reputation: 761 | |
Message#2217 18.03.19, 09:41 | |
Guru [online] Group: Friendssavagemessiahzine.com Messages 3094 Check in: 11.08.13 Lenovo Vibe B A2016 Reputation: 151 | well, most likely you made the tree in the old way, so there are a lot of nuances By the way, by the old. The one in the hat. And what is another option? -------------------- |
Message#2218 18.03.19, 10:00 | |
Starting a new life. [offline] Topics Curator Group: Curators Messages 2561 Check in: 03.04.12 Xiaomi Redmi Note 4X Snapdragon 3/32 Reputation: 699 | depesh1977, There are no fundamental differences, some flags have stopped working, without which it will not gather. But I do not think that there are many. Maybe I'll do it the other day. -------------------- Xiaomi Redmi Note 4X If there are people who learn German and live in St. Petersburg, write in a personal, we will communicate in German. |
Message#2219 18.03.19, 10:16 | |
Guru [online] Group: Friendssavagemessiahzine.com Messages 3094 Check in: 11.08.13 Lenovo Vibe B A2016 Reputation: 151 | [email protected], 10:00 There are no fundamental differences, some flags have stopped working, without which it will not gather. But I do not think that there are many. Maybe I'll do it the other day. I'll definitely wait. But while I'm in Moscow. Ostankino, work, home and so on until April. -------------------- |
Message#2220 18.03.19, 14:17 | |
Veteran [offline] Group: Friendssavagemessiahzine.com Messages 1335 Check in: 25.09.12 Jiayu S3 Advanced Reputation: 182 | Apparently you have a modified assembly, because in the official repo there is no such pribluda Thank. I was told that decoding is still not working in that recovery. Okay, I'm happy with the format data. Tell me, is there a cutout support in TWRP? Now, as I understand it, in the place of the notch I have a watch. Not critical, of course. In principle, I would be satisfied with reducing the screen resolution (move the status bar down). How to do it? |
Message#2221 18.03.19, 18:18 | |
Man with straight arms [online] Group: Curators Messages 2729 Check in: 26.12.13 Asus MeMO Pad 7 ME176CX Reputation: 761 | |
mobile version | Now: 20.05.19, 07:52 |