yashsingh1/xdaforums huggingface dataset:
[Android Software Development] igigiberia:
I am software engineer myself, I work on various stuff and learning is not something that frightens me, but this post describes it's accuracy in the beginning when the author says that it's not step by step guide, and using Omni (which I have never used before) as it seems leads to reading documentation, and I don't see any point of such big description if you can not simply put step-by-step instruction for rookies (which is mostly the case on XDA, people come to read topics as they consider themselves to rookies, and yes, we are all rookies on XDA until sufficient experience for not using the forum but only our knowledge).

I appreciate all those detailed expressions of procedure what is made, don't think that I don't, but this still doesn't give me a clue what the process really is itself. I confirm it's professional website for those who desire to learn, but then you should agree also, that this post is not for those who is equipped with only desire, but also with base knowledge, that is required from very (and I would say it as it reads - VEEEEEEEEEEEEEEEERY!) specific fields :)

So either the author should put detailed instructions (step-by-step), or you all should expect that people wouldn't start doing alchemy on their phones without asking for help from experienced fellas.

Though I already did start doing alchemy, and ended up with unlocked bootloader, and unable to build this myself to use Bank apps, as they have this security checks...
[Android Software Development] palmbeach05:
Crash course, others can add on and clean up as needed

Boot into linux os

Sudo apt-get install all libs required to build android

Install latest open jdk

Install repo

Setup username and email for builds

Repo sync omni tree

Repo sync device tree(s), including vendor and kernel trees

Build
[Android Software Development] _that:
As a software engineer you know that if you can write a detailed step-by-step guide for something, you can insted just write a script to automate it. It's not that easy, especially when porting TWRP to a new device, which is basically a subset of porting Android. So start your journey here: https://source.android.com/setup/build/requirements
[Android Software Development] igigiberia:
Thank you for step by step instruction.

It is even better than building TWRP.

I will try that, and will come back if I have any issues.
[Android Software Development] 99degree:
sorry a little bit ot

i tried to run P9000 twrp ramdisk from below url1 with my own kernel on m3 note successed and found out that init binary does do 3 phase init like android

10 does (first stage, selinux and second stage). And also the top cmd confirm and shows "init --second_stage". It does open up the window to chainload the whole android system sit on /system or /data by the mean of recovery ramdisk. This is another route to boot android discribed in latest platform/system/core/init/readme.md, so I would like to try this out on my old m3note (really not working with bind mount and without dmesg). I am not skill up to compile the twrp myself so, is there anybody tried in porting android in this way or offer me some insight to which version (android 9r? or latest) of source code does twrp P9000 3.3.0.1 recovery image used, so i can make the chainloading in progress based on the official twrp ramdisk?

url1

twrp.me/elephone/elephonep9000.html
[Android Software Development] Surge1223:
The problem isn't that a lot of the folks who work and know about this don't want to help, but if you actually dig into how much would have to be posted for a step by step guide then you'd do.

Tbh I think most ignore the questions people ask when it's clear they're not so much as struggling or passionate about building but more so for less virtuous things.

I mean when you have a cmon, when someone asks you to make crap for them, for no reason, with absolutely nothing to gain from doing so, unless you're like 14 and want to get your 5 mins of fame by building twrp for the note 10 or something, you're obviously goimg to get grief for it. Lol

I think honestly the author should have posted less.

just saying
[Android Software Development] Surge1223:
Building as root user
[Android Software Development] igigiberia:
Couldn't agree with that, may be it gives some arrogance when u know so much about building TWRP that you are not willing to share it for beginners but only for those who struggle enough to gain this info depending on their fails experience... But world doesn't move that direction in development anymore, may be it was very generous for those who shared information precisely by then, where developers where so rare, but by now, with this open source world and huge community, it's common. Of course, if it's not such a professional network where each of us have to have base knowledge to understand it further, so those who write topics, spend minimal time to point the obvious hints to solve a problem. In that case writing such a guideline is welcome, as everyone should understand as everyone is at least experienced enough to go into details and analyze a problem. But in this case, XDA posts, as I am follower of HTC since M7, where always precise in their descriptions and till now, I never posted anything as information provided was always enough to proceed with my problems and solve them, and it was first time I asked for a final result without following steps, because there where none. But no worries, instructions are already provided by our fellow user "palmbeach05", so I know where to start at least now.
[Android Software Development] Eamo5:
[MENTION=912474]Dees_Troy[/MENTION] Hi, I'm trying to compile TWRP for taimen using your provided wahoo trees. I was curious if there was a device tree available specifically for taimen, as I've manually made my own Omni device trees for taimen and have successfully compiled TWRP but I can't seem to get past the TWRP splash screen. I cant help but wonder if I'm missing something specifically for taimen from the (seemingly private) taimen trees used for official builds. Official builds have had broken decryption since August, hence I wanted to experiment with updating the provided sources from Google to see if I could get it working. I can only imagine you're very busy, but if you wouldn't mind taking the time to help out, it'd be greatly appreciated. My trees for wahoo and taimen are attached below. Thanks

https://github.com/Eamo5/android_device_google_wahoo/commits/android-9.0

https://github.com/Eamo5/android_device_google_taimen/commits/android-9.0
[Android Software Development] r3muxd:
I'm pretty sure that wahoo covers both walleye/taimen IIRC.
[Android Software Development] Eamo5:
You'd think so, but there's no omni_taimen.mk or omni_wahoo.mk or omni_walleye.mk for me to build with for any wahoo based devices.
[Android Software Development] r3muxd:
You need to create one, along with an androidproducts.mk and removing the "msm8998" "remove-project" line from your .repo manifest.

PRODUCT_MAKEFILES := \

$(LOCAL_DIR)/omni_wahoo.mk

for androidproducts.mk and I can't find my old omni_wahoo file.
[Android Software Development] Eamo5:
Oh I see. So to ensure I understand correctly, I *only* need to create an omni_wahoo.mk and this *does not* rely on me creating an omni_taimen.mk? I assumed I'd need to make omni makefiles specifically for taimen and that the provided TWRP trees for wahoo were fine without any extensive modifiations.
[Android Software Development] smtsng13:
i own redmi note 4. i was making TWRP device tree for other mobile so i looked in RN4(mido) DT for reference and i found this.

Cache size

Stock = 0x0010000000 = 268435456 = 256MB

TWRP DT = 0x0018000000 = 402653184 = 384MB

402653184 - 268435456 = 134217728 = 128MB <==

Userdata size

Stock = 57033595904

Stock(-16384) = 57033579520

TWRP DT = 58846081024

TWRP DT(-16384) = 58846064640

58846081024 - 57033595904 = 58846064640 - 57033579520 = 1812485120‬ <==

where do this extended size came from?

And one more question, do i need fstab.qcom when i use recovery.fstab?
[Android Software Development] 7Raatoo:
Por favor disponibilizem no aplicativo para o Multilaser MS60z é urgente
[Android Software Development] Clark Joseph Kent:
4. Use the English language.

We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation.
[Android Software Development] Laikar_:
I am getting "Unknown ARM architecture version: armv8-a." when trying to lunch, what am i missing/ doing wrong?
[Android Software Development] matteo0026:
Hi guys, I updated with success TWRP to Oreo kernel for nappa and yamcha from TeamWin official sources. https://github.com/matteo0026/android_device_bq_nappa https://github.com/matteo0026/android_device_bq_yamcha Now, I have an ask. How can the recovery work well with Nougat 7.1 libs?
[Android Software Development] palmbeach05:
It just does work, but i'd update yout twrp to 3.3.1, which i think is available starting on 8.0/8.1 build manifests
[Android Software Development] The_Walking_Playground:
Hi,

The latest TWRP builds in all trees going back to 5.1.

TWP
[Android Software Development] matteo0026:
I used minimal twrp sources based on Android 8.1. And... Are you an official maintainer? I just have to make a pull request on the official TeamWin GitHub page for pushing? I can do it
[Android Software Development] palmbeach05:
Ok, well give it a shot with something above 8.0 (recommend 8.1). If you read into omnirom's bootable recovery tree, you'll see what i mean about older versions not being up to par at 3.3.1. Remember, minimal manifest is your friend. Use that in combination with your device, kernel, and vendor trees on 8.1 as well

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

Me? I am
[Android Software Development] ashyx:
Sometimes you have no choice but to build using an older branch if your kernel doesn't support newer branches.

As I maintain a number of devices I use all the way from lollipop to pie and have no issues with either.

Can you expand on which issues you are referring to?
[Android Software Development] matteo0026:
Oh ok, so... Wait before pushing everything, my testers still have to test decrypt and some other functions.
[Android Software Development] palmbeach05:
Yes. Make sure everything is good to go in an unofficial release/test build first before requesting maintainership or before pushing commits to twrp's repos
[Android Software Development] tongqabiz:
Cannot boot recovery partition failed

Hi everyone,

I have an issue,

Yesterday I tried to install LineageOS 16 and GappsPico

Since my Manta Nexus 10 only have space for 700M, I couldnt install any type of Gapps.

So I do a partition changed.

After deleting and recreating partition, I mistakenly reboot the linux kernel. So it means my Nexus doesnt have any TWRP or anything

Right now, if I pressed power + volume up - hoping to get the recovery option - which I dont get, I only got start.

Is theres a way to fix this? or its just doom for me?

really appreciate it
[Android Software Development] palmbeach05:
This thread is for how to build twrp. Not to request someone to build it.
[Android Software Development] yuri-2016:
TWRP recovery works weird on Motorola One Zoom

Hi!

I compiled TWRP recovery for Motorola One Zoom. But "fastboot boot twrp.img" doesn`t work (boots into stock recovery). And "fastboot flash" boots TWRP only to the start page - touchscreen doesn`t work, adb too, no logs can be found in regular log-addresses (like /cache/recovery, tmp or so). What can be the problem? If you need I can show the BoardConfig.mk and the entire device_tree. Thanks in advance.
[Android Software Development] ilia3367:
So there's no one to help with that? :confused:

Or did the XDA run out of real masters?

I'm ready to provide my phone for remote work and experiments.

I'm ready to pay someone who does this work!
[Android Software Development] ashyx:
Is it an Mtk device?
[Android Software Development] ilia3367:
No, Snap 675
[Android Software Development] ashyx:
Try flashing it to the boot partition. If touch works it's disabled in recovery.
[Android Software Development] yuri-2016:
It`s not MTK, no "recovery" partition is present on Moto One Zoom - only boot-partition." fastboot boot" is not working at all.
[Android Software Development] palmbeach05:
Android 10?
[Android Software Development] ilia3367:
https://www.gsmarena.com/motorola_one_zoom-9745.php
[Android Software Development] Shtiff1:
Please do not ask us to add TWRP support for your device. We simply do not have access to all of the devices or the developer resource to port your device for you. You can port your own device here:

http://xdaforums.com/showthread.php?t=1943625
[Android Software Development] De_Haos:
Well you are supported to.
[Android Software Development] Shtiff1:
My device is currently not supported.
[Android Software Development] Phoenix591:
bak partitions don't count, there needs to be two of the important partitions mentioned in that article, particularly boot and system, and NOT have a recovery partition, but none of those are in your screenshots, however ...

A/B was added in Nougat (and few devices, even launching with Nougat supported it, it became a little more common with oreo, but its still not super common).

to check for 100% sure see here
[Android Software Development] MKUltraBlack:
I have tried the tutorial and can't build twrp. I can however theme twrp and decompile with android image Kitchen. Is there something I can do with the decompiled image (s7 edge) to change the screenshot colour invert (blue=orange etc) Does it have to be done when building a new image or will the premade image decompiled be editable
[Android Software Development] The_Walking_Playground:
Hi,

You have to build from source to fix that issue. Did you post the errors you're facing to see if someone could help you resolve them?

TWP
[Android Software Development] MKUltraBlack:
I already have twrp for s7 edge, I tried building it before but can't even figure out where to start from the tutorial. It's good, but missing so much information for beginners it's not worth bothering with for me. Like where the device tree goes, how and where to add it, get it, steps missing etc. I also only use windows, I have tried, but as I say NOT beginner friendly. I will just continue using the stock images until someone can make a full comprehensive tutorial (probably never as this partial one is here).

Thank you for the information btw, thought there might have been something in the decompiled image to save time of scouring the net trying to find the missing steps to build.

I only theme twrp, but is there a chance in the future someone from the xda group could make this a full tutorial. It's a vital piece of information for people without stock recovery and it may be useful to some with previous experience but for the sake of an hours typing it is overly sparse. I know it takes time to type tutorials etc and I and many others are grateful but it seems to me like the sort of thing that used to get rejected from xda for not providing sources, not enough info etc

When you try Google (we hide everything) just about every link takes you back to this incomplete tutorial and I end up in a (boot)loop

There are also a few video tutorials that are so low definition I can't make out what the folders, text etc says on it, and instead of adding a voiceover to describe what they are doing it's usually a dubstep track hammering away in the background lol

Anyway not having a go, as I say it's a good tutorial, could just do with being complete ?
[Android Software Development] The_Walking_Playground:
Hi,

Well, the tutorial you can start with is the "Building Android" one from Google: https://source.android.com/setup/build/requirements

And if LineageOS is available for your device, you can try building that: https://wiki.lineageos.org/devices/hero2lte/build

Once you can get through those, you'll have the basic knowledge necessary to understand this guide.

TWP
[Android Software Development] boowho:
Patching the ROM

I've read that TWRP may be able to patch the system image so that TWRP is not automatically replaced with the stock recovery at next system boot.

This has never worked for me. I have a Samsung Gear Live watch, but no joy. I have tried both V2.x.x and V3.3.3.

I've tried rebooting back into recovery IMMEDIATELY after flashing TWRP and it's all there working. Next time a system boot is done, recovery back to stock.

What might I being doing wrong??

Thanks

Boowho??
[Android Software Development] ashyx:
You need to allow modifications to system in twrp.
[Android Software Development] boowho:
You mean like R/W permissions on the system partition?? I think I've tried that, but will try again.

Thanks
[Android Software Development] DualJoe:
recovery loop

If i reboot (at least once) with 'recovery' button the device cannot boot into 'system' anymore. It always boots into recovery. All other modes (poweroff, download, recovery) still work but 'system' boots to recovery always. I can fix this by flashing recovery again with heimdall/odin. Then everything's fine again until i press 'recovery' again.

Is there a fix for this or do i have to disable the recovery reboot (TW_NO_REBOOT_RECOVERY) as a last resort? Is this a known bug? Looks like a running wild ota flash mode or something. I also cannot set the bytes manually via shell in PARAM partition (mtd0 write protection error in dmesg) even though writing does work properly in TWRP.

TWRP 3.3.1

MSM8916

Galaxy A300FU (a3ulte)
[Android Software Development] Abhinav2005:
Same here
[Android Software Development] DualJoe:
On which device and twrp version?
[Android Software Development] Abhinav2005:
Twrp 3.3.1 on Samsung tab a 10.5
[Android Software Development] blackbuga:
You use stock kernel ? Or have modified
[Android Software Development] DualJoe:
Modified kernel.

https://github.com/Galaxy-MSM8916/android_kernel_samsung_msm8916
[Android Software Development] palmbeach05:
That kernel should be good. I just used it over on the j5 2015 and 2016 for their official twrp builds. Could you post link to the device repo(s) that you're using?
[Android Software Development] Abhinav2005:
But I am using stock kernel
[Android Software Development] palmbeach05:
Using stock from samsung to make twrp?
[Android Software Development] Sands207:
Yes, thats exactly what he said. Doesn't it need to be modified to build TWRP?
[Android Software Development] palmbeach05:
It does. I was just reading that on tg that a modified kernel needs to be used.
[Android Software Development] DualJoe:
Device tree is on the same Github account (a3ulte). I've used this custom flags in BoardConfig.mk (the others are in device tree):

When i try to write 0x030000 manually to PARAM partition (.../by-name/param) i get a write protection error for mtd0 in dmesg (shell exit code is 0 though). That's kinda weird as TWRP definitely can write properly. I haven't check yet if the symlink actually is ok though. It was predefined in device/samsung/qcom-common/recovery/root/sbin/postrecoveryboot.sh. But if Abhinav2005 has the same effect that's quite a coincidence that rather sounds like a TWRP bug. Just a wild guess but maybe TWRP sets a wrong A/B mode or something that goes into a "locked" mode that it cannot leave by simple rewrite to PARAM. Heimdall/Odin can re-set the mode from 'download mode' (by reflashing recovery) so you can escape that stage by this. That's also the only way i know so far to workaround the bug.

Currently i have removed the 'reboot/recovery' button so no harm can be done. LOS16 works properly as well with the kernel.
[Android Software Development] DualJoe:
TWRP 3.0.2-Ashyx reboots properly to recovery though. He seems to use omni source. But it could be TWRP 3.0.2<>3.3.1 as well so we don't know for sure. It would be great if some more people could confirm the issue.
[Android Software Development] MKUltraBlack:
Forgot to say thank you for these links ?? very useful, turns out I just had to put device tree folder in device/samsung/hero2lte, I can now get it to start building but it fails with a ninja.mk:125 or something.

When building is there a place I can find an error log to send or just put the CMD text in a text file enough ?

Many thanks again on the links ?
[Android Software Development] ballerd:
Hi I recently started trying to build twrp for my device its already been build for mine unofficially but I don't how hes done it

I downloaded twrp minimal I placed device tree what I used from previous configurations on his github but I keep getting errors I don't understand how hes built it and what do about vendor files I cant find them anywhere and do I need to put kernel source in this build also included screenshot of read.me from original dev
[Android Software Development] ballerd:
Getting this error now
[Android Software Development] ballerd:
I also get this error target arch variant is arm v8 but my device is arm-7 don't understand why am getting g this error could it be a make file error anybody have a idea
[Android Software Development] Golv:
Hello!

Please help me solve my problem.

I used https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni/commits/twrp-9.0

Device tree based on 8.1 worked flawlessly.

I updated the kernel 9.0 based on new Pie ​​sources.

Used Deconfig from previous version 8.0 - https://github.com/Golv/android_kernel_htc_ocn/commits/master

Replaced kernel (Image.lz4-dtb) in device tree and made small changes to the tree itself. (Device Tree)

TWRP compiled and started.

All the main things work, but I can’t access via ADB.

Serial number is displayed, but the command:

adb shell

gives an answer

device offline

What have I done wrong? How to get ADB working? :confused:

Logs from TWRP - attached.

Thanks!
[Android Software Development] The_Walking_Playground:
Hi,

Have you tried working with [MENTION=1162986]Captain_Throwback[/MENTION] on this? I know he had hit a roadblock with Pie decryption on U11 so if you have made progress on it that would be fantastic. I'm sure he can probably help with your adb problem. You should be able to join his TWRP Slack from the U11 TWRP OP to get in touch with him.

TWP
[Android Software Development] soorajsp:
Script released?

Sir, the script released?
[Android Software Development] NZedPred:
There's no error there that I can see? But I do see it's not outputting anything. Perhaps your setup isn't quite right?

I managed to get a build going for sailfish (Original Pixel), refer to my thread here:

https://xdaforums.com/pixel/how-to/how-to-building-twrp-source-goodies-t4029449

You can follow the instructions in it except for the bit about patching for sailfish, and just replace sailfish with marlin. E.g. you'll use lunch omni_marlin-eng.
[Android Software Development] palmbeach05:
Yeah, you can. The thread is called, how to compile twrp. So stop begging and get to building
[Android Software Development] sdembiske:
If anyone has run into the following error, I would appreciate any direction you can provide to help overcome it:

--------------------------

[1063/1063] including vendor/qcom/opensource/dataservices/Android.mk ...

[ 99% 4514/4515] glob vendor/qcom/open...rce/interfaces/wifi/supplicant/2.0/src

ninja: error: '/home/s/Desktop/LOS_16.0_MotoG_LTE/out/target/product/peregrine/system/xbin/strace', needed by '/home/s/Desktop/LOS_16.0_MotoG_LTE/out/target/product/peregrine/obj/SHARED_LIBRARIES/libbmlutils_intermediates/teamwin', missing and no known rule to make it

09:26:56 ninja failed with: exit status 1

#### failed to build some targets (56 seconds) ####

--------------------------

I am compiling with full omnirom source for LineageOS 16.0 unofficial and no amount of searching has provided clear direction on working through it.

Thank you,

s
[Android Software Development] The_Walking_Playground:
Hi,

It looks like you're including strace somewhere but it's either not included in your downloaded source, or the path to it is incorrect.

TWP