yashsingh1/xdaforums huggingface dataset:
[Android Software Development] rohitsinha12:
Error while compiling orangefox recovery for Lenovo A6000

https://del.dog/sutuxowado.cs
[Android Software Development] surendrajat:
https://twrp.me/faq/OfficialMaintainer.html

---------- Post added at 03:27 PM ---------- Previous post was at 03:18 PM ----------

Clone latest busybox repo from omnirom.
[Android Software Development] surendrajat:
Check this out...

And if you really want to build yourself then check this wiki...
[Android Software Development] surendrajat:
To understand A-Z you need to read a few posts and articles, now don't ask where are those... just search. That wiki, however, is very straightforward and if you follow correctly, you'll get a TWRP.

Now, TWRP built with 5.1 sources will boot on your device but it'll have issues with encryption and because kernel source for your device(I dare to assume SM-J415X) hasn't been released yet so you'll have to wait a while to get fully working TWRP.
[Android Software Development] Odin Erbe:
Hi I'm looking for a TWRP RECOVERY for my Gigaset GS100 ... I can not find anywhere on the net one. Please help me .. love greetings

MTK 6793 WA
[Android Software Development] surendrajat:
No. It's related to the /data partition. Also root protection etc. need to be removed from the kernel to be used in twrp therefore source is needed.
[Android Software Development] leonardommello:
Has anyone had any problem on touch display not working in twrp? Samsung Exynos device.
[Android Software Development] MartinX3:
Yes.

So I implemented the touch.ko files into my twpr ramdisk. :silly:
[Android Software Development] ashyx:
The touch drivers are part of the kernel. If touch is disabled in recovery then you need to patch the boot mode flag in the drivers that disables touch while in recovery.
[Android Software Development] MartinX3:
In the driver blob?
[Android Software Development] ashyx:
See this example, grep the touchscreen driver for 'bootmode' and remove the offending code if it exists as you can see in the synaptic driver.

https://github.com/CaptainThrowback...mmit/3e364f07a7e939f0ad35e04b6d05f6419aaf5f64
[Android Software Development] leonardommello:
I saw on code and recompiled the kernel. Thank very much :victory:

About dtb (dt.img):

how do you compile it? I did a kernel recompile, but didn't find anything about dt. My device is with samsung exynos 7870.
[Android Software Development] ashyx:
It's not necessary to compile the dtb. You can use the prebuilt dtb from the boot.img.
[Android Software Development] leonardommello:
I recompiled the kernel but after compiling Twrp and uploading to the device and that it started to reboot and didn't open the twrp(recovery). With the first kernel I used it did not work the touchscreen but open normally. Do you have any tutorials or postings that I can base for the recovery make?
[Android Software Development] Rortiz2:
Hi [MENTION=5602116]surendrajat[/MENTION], I tried contact with TeamWin to add official support to the BQ M8 tablet but when I give it to submit I get the error:

502 Bad Gateway

nginx / 1.10.3 (Ubuntu)

What can I do?
[Android Software Development] Ibuprophen:
There's a Contact issue (via website and email) from the twrp.me website is not working...

I had reported this on TWRP's Google Plus to the attention of [MENTION=912474]Dees_Troy[/MENTION] and, about a month or so later, I had received a confirmation from Dees_Troy on reading the information reported.

Just a little heads up regarding this...

~~~~~~~~~~~~~~~

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Tandy TRS-80.
[Android Software Development] CalebQ42:
HELP. please (Razer Phone 2)

The factory images and kernel source recently were released for my device (Razer Phone 2) so I decided to try my hand at compiling TWRP. I've never done anything like this before so it's been quite interesting so far.

I can get a recovery.img or boot.img to compile just fine, but when I flash it then the device refuses to boot (it is stuck on the splash screen just before the boot animation)

My setup:

I'm using Omni Android 9.0 source, I set up a repo for my device at https://github.com/CalebQ42/android_device_razer_aura (I'm not too sure about a lot of it. I've largely based it off of https://github.com/TeamWin/android_device_razer_cheryl which is for the first razer phone cross referenced with some similarly spec-ed devices).

I also have been using https://github.com/LineageOS/android_vendor_qcom_opensource_cryptfs_hw for cryptfs, though even with it I still have to set ALLOW_MISSING_DEPENDENCIES because of missing "generated_kernel_headers"

I'm using a prebuilt kernel because I had trouble compiling the kernel and the boot.img at the same time (basically it's removing some files from the out directory and rm says it isn't deleting a folder because -r wasn't specified and it stops, though the kernel seems to already be compiled. I'll edit with the specifics later)

Any help would be greatly appreciated!

Edit: Error from build the kernel:

make[1]: Leaving directory '/home/belac/Omni/out/target/product/aura/obj/KERNEL_OBJ'
make: Leaving directory '/home/belac/Omni/kernel/razer/sdm845'
depmod: WARNING: could not open /home/belac/Omni/out/target/product/aura/obj/PACKAGING/depmod_system_intermediates/lib/modules/0.0/modules.order: No such file or directory
depmod: WARNING: could not open /home/belac/Omni/out/target/product/aura/obj/PACKAGING/depmod_system_intermediates/lib/modules/0.0/modules.builtin: No such file or directory
[ 97% 39/40] Prebuilt: (/home/belac/Omni/out/target/product/aura/kernel)
FAILED: /home/belac/Omni/out/target/product/aura/kernel
/bin/bash -c "(rm -f /home/belac/Omni/out/target/product/aura/kernel ) && (cp \"/home/belac/Omni/out/target/product/aura/obj/KERNEL_OBJ/arch/arm64/boot/\" \"/home/belac/Omni/out/target/product/aura/kernel\" )"
cp: -r not specified; omitting directory '/home/belac/Omni/out/target/product/aura/obj/KERNEL_OBJ/arch/arm64/boot/'
ninja: build stopped: subcommand failed.
06:55:59 ninja failed with: exit status 1
[Android Software Development] Heze85:
i manage to compile a twrp for my mt6797, but i cant get the touch working.... at least on recovery-partition, on the boot partition twrp works flawless .... any help or advice??? pleeaaase
[Android Software Development] ashyx:
Grep the touch driver for 'bootmode' with reference to recovery and comment out the offending lines.
[Android Software Development] Heze85:
but how? i have no linux system running... and honestly no idea how
[Android Software Development] ashyx:
Then how have you compiled twrp? :confused:
[Android Software Development] Heze85:
with help of the tutorial and the help of god (i think), but i dont find anything about my problem, the kernel is just a file with lot of symbols in it, all other files open just fine in hex-editor
[Android Software Development] ashyx:
How can you have possibly compiled twrp from source if you don't have a running Linux System?

You need the kernel source not a hex editor.
[Android Software Development] Heze85:
https://drive.google.com/file/d/1mSzXMx0ykLwROs1IOyIxfj7Oy1M6MYB2/view?usp=sharing

ported , i dont know ... there is the file , i hope someone can help me with this mess
[Android Software Development] MartinX3:
Hey [MENTION=4899305]ashyx[/MENTION]

Could you help me with the PIE encryption. (Bootloop because data partition, stock rom)

Snapdragon 845, keymaster 4.0.

The keymaster gives error -38 (invalid argument)

https://xdaforums.com/showpost.php?p=78400544&postcount=2314

I just used the changes from the mentioned OnePlus 6t commit to upgrade to keymaster 4.0
[Android Software Development] jahidinbedod:
can someone help me

how to fix this problem

E: String resource 'ZIP_Compatible_err' not found. Using default value.

Zip Treble Compatibility Error !

Invalid Zip file format !

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

can someone help me

how to fix this problem

E: String resource 'ZIP_Compatible_err' not found. Using default value.

Zip Treble Compatibility Error !

Invalid Zip file format !
[Android Software Development] _that:
Looks like you built TWRP with a too old Android tree or you're trying to install a too new package.
[Android Software Development] PWn3R:
Hi - trying my hand at building this. I am new to TWRP builds, but maintained Nexus 6 builds of Beanstalk for a long time.

I can't get the source to download. When I run this:

pwn3r@PWn3R-Home:~/android/perseus/twrp$ repo init -u https://github.com/omnirom/android_bootable_recovery.git -b android-9.0
gpg: keybox '/home/pwn3r/.repoconfig/gnupg/pubring.kbx' created
gpg: /home/pwn3r/.repoconfig/gnupg/trustdb.gpg: trustdb created
gpg: key 16530D5E920F5C65: public key "Repo Maintainer <repo@android.kernel.org>" imported
gpg: key 67B7E448692B382C: public key "Conley Owens <cco3@android.com>" imported
gpg: Total number processed: 2
gpg: imported: 2

Get https://gerrit.googlesource.com/git-repo/clone.bundle
Get https://gerrit.googlesource.com/git-repo
remote: Counting objects: 1, done
remote: Finding sources: 100% (10/10)
remote: Total 10 (delta 1), reused 10 (delta 1)
Unpacking objects: 100% (10/10), done.
From https://gerrit.googlesource.com/git-repo
d26146d..d4b13c2 master -> origin/master
* [new tag] v1.13.0 -> v1.13.0
Get https://github.com/omnirom/android_bootable_recovery.git
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (22) The requested URL returned error: 404 Not Found
Server does not provide clone.bundle; ignoring.
remote: Enumerating objects: 32020, done.
remote: Total 32020 (delta 0), reused 0 (delta 0), pack-reused 32020
Receiving objects: 100% (32020/32020), 91.22 MiB | 34.46 MiB/s, done.
Resolving deltas: 100% (16977/16977), done.
From https://github.com/omnirom/android_bootable_recovery
* [new branch] android-4.3 -> origin/android-4.3
* [new branch] android-4.4 -> origin/android-4.4
* [new branch] android-5.0 -> origin/android-5.0
* [new branch] android-5.1 -> origin/android-5.1
* [new branch] android-6.0 -> origin/android-6.0
* [new branch] android-7.0 -> origin/android-7.0
* [new branch] android-7.1 -> origin/android-7.1
* [new branch] android-8.0 -> origin/android-8.0
* [new branch] android-8.1 -> origin/android-8.1
* [new branch] android-9.0 -> origin/android-9.0
Checking out files: 100% (1552/1552), done.
fatal: manifest 'default.xml' not available
fatal: manifest default.xml not found

I can't seem to find an XML in any of the directories. I was going to try one of the older versions of the minimal code, but this device shipped with PIE and encryption changes and other items between the old versions concern me. I am aware that I am going to need to piece together device support files for this device, and I may need some assistance there as well.
[Android Software Development] ashyx:
Looks like your trying to initialize just the recovery sources.

You need the omni sources first, recovery will be automatically included.

To clone just the latest recovery sources you just need to use:

git clone https://github.com/omnirom/android_bootable_recovery.git

To build TWRP you're gonna need the OMNI sources:

repo init -u git://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni.git -b twrp-8.1

Then do:

repo sync
[Android Software Development] David B.:
Would anyone care to dumb this explanation down? I have experience with Linux, and yet I find this extremely difficult to follow. I want to built TWRP for the Nexus 6 (codename shamu), but I would like to use a different version of the device tree from what is maintained by the official TWRP team. Instead, I want to use the Nexus 6 device tree maintained by the LineageOS team. To be clear, I want to build using the tree for Android Oreo 8.1 and not Android Pie 9.0.
[Android Software Development] ashyx:
Tree as in lineage 8.1 branch sources?

Why would you want to use Lineage sources? You will encounter issues you will have to fix.

If your sole intention is to build TWRP then you're better sticking with Omni sources and using the 8.1 branch, which I think is the default branch at the moment anyway.
[Android Software Development] MartinX3:
The author just stopped development of the minimal branch and said us to use the entire Omni 9.0 source.
[Android Software Development] ashyx:
You can build twrp with practically any branch from android 5 upwards.

Personally I build everything using android 6 branch.

You would be fine using 8.1 branch.

If you're stlll determined to use the full omni sources, which will be massive then just do:

repo init -u git://github.com/omnirom/android.git -b android-9.0

Make sure you've got plenty of hard drive space and a fast connection!
[Android Software Development] MartinX3:
Yes, I did it. 250GB space after compiling, because it also downloads every branch. :)

But sadly since compiling with 8.1 (and 9.0 recovery) for PIE I can't decrypt userdata anymore.
[Android Software Development] PWn3R:
I downloaded the 9.0 branch as you suggested, but there were several 404 messages, and I don't see the recovery source included, like it didn't download it. I'm starting to work on the device tree (for perseus, Xiaomi Mi Mix 3). Do I need to drop the 9.0 recovery source that I git cloned into a folder in the Omni source? Sorry I'm not terrible adept at git and I've probably forgotten half or more of what I had learned in the 2 years since I stopped building for the Nexus 6.
[Android Software Development] ashyx:
If it's the full source then recovery will be included.

If you're getting 404 messages you might have to modify the manifest to point to the correct location of what its looking for or if it continues to download you may just be able to ignore it as it may not be needed anyway.

Best just to suck it and see.
[Android Software Development] Teeemoo:
Hi,

Im trying to compile TWRP for the Nubia X NX616J using:

https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni (TWRP 8.1)

and

https://github.com/TwrpBuilder/twrpbuilder_tree_generator/wiki

I also tried CM and older Versions of TWRP (still the same result).

Compiling results in a recovery.img which seems to be fine (no errors whatsoever) but after unlocking and flashing, the recovery partition seems to be corrupted.

In the screen there is a warning with "your device is corrupt and will not boot" - so Im forced to reflash the original recovery image.

Im assuming the screen is not the result of wrong compiling but more because the device refuses to allow the recovery?

Like the Nubia's have an relocking bootloader - so you can basically just flash and after reboot its locked again.

What is weird too: If flashing on recovery1 and then booting to emerg recovery [recovery2] (which should be just fine?) its also corrupted.

Bootloader and System on the other hand work just fine.

Does anyone know why this happens? (Or better: what to do in this case?)
[Android Software Development] ashyx:
Is you device oem unlocked?
[Android Software Development] Teeemoo:
Yes, in the options ofc

But it keeps relocking after reboot (at least the OEM unlock from fastboot)

But that should not be a problem because the BL is unlocked and allows flashing :?
[Android Software Development] ashyx:
You still need OEM_UNLOCK enabled regardless of whether the manufacturer has unlocked the bootloader or not.
[Android Software Development] Teeemoo:
Hi,

The bootloader can be unlocked by typing "fastboot oem nubia_unlock <pass>" after that I can flash whatever I want - but after rebooting / booting to recovery the

bootloader is locked again (without doing anything).

I tried to use "fastboot boot twrp.img" but unfortunately the device does not know the command "boot".

Also "fastboot oem unlock" is unknown too - dang!

But OEM-Unlock in Dev options is enabled.

The device is Rooted too (flashed boot.img with magisk).

Any tips?
[Android Software Development] ashyx:
I'm not really that familiar with your particular device. Isn't there are forum for a similar device where you can pose your issues?

Have you tried simply repacking the stock recovery with no changes to see if that gets rejected also?
[Android Software Development] Teeemoo:
Well thanks for the answer!

Im the only one developing for the Nubia X right now ...

And actually the repacked original recovery image is also corrupt when flashing - is there a way of signing the TWRP?

Found some tutorials online but they require flashing some zips or using self-signed certs..
[Android Software Development] The_Walking_Playground:
Hi,

You can try the signing method from here: https://github.com/youyim123/androi...6112#diff-66b3695afd4573cd55d338a523917aa5R40

Adding that section to your makefile should work for your device, I think. It seems to work for another Nubia device.

TWP
[Android Software Development] MartinX3:
Maybe this needs fixes for other devices (I can't test many different devices)

But I upgraded the minimal build environment to 9.0.

https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni/tree/twrp-9.0
[Android Software Development] ashyx:
Thanks for that I noticed you'd got that merged just recently.
[Android Software Development] Teeemoo:
Still not working at all,

the device, again, replies with "Device Corrupt, will not boot" only when booting to recovery. The rest works fine.

Do I need to get hands on the Nubia X Verity Key's?

Im not really into signing and stuff so this question might sound stupid.

Any other ideas :/?

Its so annoying that "oem nubia_unlock <pass>" is only a temp unlock, like whats the purpose of a temporary unlock. Nubia pls.
[Android Software Development] pix106:
I build TWRP for LP devices using twp-5.1 branch.

A few weeks ago, system/core android-5.1 branch was removed from omnirom's github.

Do you know any replacement ?
[Android Software Development] Jleeblanch:
If you downloaded the FULL omni source, then the twrp recovery source is NOT included despite the numerous replies stating otherwise. You would need to create a local manifest which removes aosp's recovery and includes omni's bootable recovery source (which contains TWRP).

<remove-project name="platform/bootable/recovery" />
<project path="bootable/recovery" name="android_bootable_recovery" revision="android-9.0" remote="omnirom" />

You'll most likely also need some other repos as well.
[Android Software Development] Teeemoo:
No ideas?
[Android Software Development] ashyx:
Have you actually tried disabling dm-verity first by patching the boot image then flashing it?

You can do this with a Magisk patched boot image.
[Android Software Development] David B.:
By "tree" I was referring to the device tree for my specific phone (Nexus 6). The reason I want to do this is because TWRP decryption is not working on the Nexus 6 when it has been encrypted with an installation of LineageOS 15.1. I posted an issue on the TWRP GitHub repo about it and I was told that the issue could be traced to the device tree for my phone, so I opened an issue on the Nexus 6 TWRP device tree, but the maintainer has ignored it so I decided I could try to fix things by building TWRP using the device tree from LineageOS. I am not sure if it would work or if it is even possible, but giving it a try seemed like a sensible idea.

Would building from a newer version of Omni? I am still trying to figure out how all of this fits together.
[Android Software Development] ashyx:
Where is your tree? You need to include the crypto flags for decryption to work. Even then it may not work without adding the required libs.

There is now a minimal android 9.0 branch of omni.

However unless your kernel supports that version twrp won't boot.
[Android Software Development] MartinX3:
https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni/tree/twrp-9.0 :)

---------- Post added at 01:57 PM ---------- Previous post was at 01:54 PM ----------

The minimal manifest files are only redirections to the github.

You can traverse the forks of this repo.

As example there is a 5.1 branch

https://github.com/mauronofrio/android_system_core/tree/android-5.1
[Android Software Development] David B.:
Thanks! Doesn't the issue I was describing with encryption still remain an issue when doing it this way though?
[Android Software Development] MartinX3:
The nexus 6 was my previous device. :D

I would recommend building it with logcat support and use logcat, dmesg and the /tmp/recovery.log to locate the problem. :)

(adb shell)

BTW.

Do you mean this?

https://xdaforums.com/nexus-6/orig-...geos-15-1-nexus-6-shamu-t3773143/post78485177
[Android Software Development] David B.:
I actually grabbed a copy of the TWRP log from my device using the official TWRP build for the Nexus 6 and posted it on the GitHub issue I opened. I tried to figure out what was wrong myself but I was unable to decipher it. Regarding the link you posted, that is not the issue I am describing.

The issue I am describing is different. The post you linked to refers to an issue with decryption not working with LOS itself. The issue that I am describing is TWRP-related. When I upgraded my phone from LineageOS 14.1 to LineageOS 15.1, I tried doing a dirty flash using the instructions that the LineageOS team provided for how to do so, but I ran in to some problems and decided to do a clean install. Before doing that, I took a backup of the dirty LOS 15.1 upgrade using TWRP without any issues. I then did a full wipe of my phone and installed a fresh clean image of LOS 15.1. As part of this process, the encryption from 14.1 was lost and I had to re-encrypt using the fresh LOS 15.1 installation that I had made. I then tried to make a TWRP backup of the fresh install, but TWRP was failing to decrypt. Apparently something about how decryption is handled in LinageOS 15.1 (I believe this change was not LineageOS-specific and impacted Android as a whole) does not play nice with TWRP.
[Android Software Development] MartinX3:
So logcat and dmesg may help.

And I recommend titanium Backup. :)

https://xdaforums.com/nexus-6/orig-...geos-15-1-nexus-6-shamu-t3773143/post78512198

I see :)

Maybe you need to use the official lineageos device tree for twrp.

If you can compile a working lineageOS, you can exchange the recovery with the twrp, like I did in the minimal TWRP 9.0 manifest file.
[Android Software Development] David B.:
I actually do use Titanium Backup and I love it, but the problem is that in some cases, it is preferable to have a full system backup image instead of just backups of apps. As for logcat and dmesg, are they not included in the TWRP log I mentioned?

As for the LineageOS tree for TWRP, I looked at doing that, but there are two problems with that. The first is that I still do not understand how to use it to build TWRP, and the second is that the minimal manifest repo, which I believe is what you are talking about, was never moved to LOS 15.1. It is still on LOS 14.1 and unsurprisingly, I do not know what I have to do in order to update it.
[Android Software Development] MartinX3:
Logcat and dmesg are giving you different, but usefull output.

To activate logcat, too, look here.

https://github.com/TeamWin/Team-Win-Recovery-Project/issues/352

You only need to look at the twrp-extras.xml in the minimal TWRP manifest files.

You can grab and copy it into the local_manifests folder in the .repo folder.

Just use the full lineageos sources with the 15.1 device tree. :)
[Android Software Development] Ssssss8622:
Can anyone compile twrp for vivo y83. Please let me Know how much to pay.
[Android Software Development] ashyx:
https://twrpbuilder.github.io