yashsingh1/xdaforums huggingface dataset:
[Android Software Development] _that:
The logo is a hidden back button. And some advanced commands are hidden if they are not supported on the current device.

The UI is customizable by editing the theme XML.
[Android Software Development] Ibuprophen:
I hope you don't think of this as a stupid question. I have done allot of different android projects but, I haven't touched anything regarding TWRP (besides updating any new version releases).

I know that i can search the thread but, instead of getting bits and pieces, has there ever been a more thorough "how to" guiding someone through the TWRP's theme xml for customization?

Sent from my Communicator (SCH-I535) on the Bridge of the U.S.S. Enterprise (N.C.C. 1701).
[Android Software Development] G.M.L:
Deleted
[Android Software Development] TimSchumi:
I'll think about it...

Anyways, I first want to see if I can submit this anyway.
[Android Software Development] _that:
Yes, but it has not been updated since ages and it's no longer on the web site. Most should be self-explaining though if you read the XML. Here's the very old documentation:

http://web.archive.org/web/20150317050654/http://www.teamw.in/twrp2-theme-guide

http://web.archive.org/web/20150315022410/http://www.teamw.in/twrp2-reference-guide

Note that <object type="button"...> has been changed to <button...>. With this in mind, most of the theming guide should still make sense.

This is "How to compile TWRP", not a theme announcement thread.
[Android Software Development] NepoRood:
Tim, I see you all over, offering very good advice to people that don't know as much as you (kudos, for that, I like to help too!) When building TWRP, prebuilt kernel usually works better than compiling a kernel for it, in my limited experience anyway.

Give it a shot, you may save yourself some time and effort.

My 2 Cents,

Nepo
[Android Software Development] TimSchumi:
Thanks for the commendation! (Also kudos to you for helping others way more often than I do).

I now decided to switch to a prebuilt kernel for submitting my twrp to teamwin, but I'll definitely keep the patches and the kernel source handy if I need to build a new kernel (I'll definitely have to build a new one for fixing SELinux and this wiping error is driving me crazy, too :eek: )
[Android Software Development] NepoRood:
Call it what you want, "Official" really comes down to the dev team being able to build your device without any kind of "patches" or errors. Meaning, sync your repos and then build.

According to them, it should just "work", and I don't put any blame towards the developers (it should just work, lol), but sometimes patches are needed. The bad thing is, sometimes patches are hard to incorporate into the source, what works for you may not work for a similar device (and WTF is up with that? lol)

Anyway, I'm just rambling on like Led Zeppelin,

Regards,

Nepo
[Android Software Development] TimSchumi:
I now managed to cross out all patches. The patch I mentioned in my last post is the patch which enables the TARGET_KERNEL_CUSTOM_TOOLCHAIN Flag, which was missing since Android 5. It is not needed for building TWRP (prebuilt kernel :D), but I will need it if I will build a new kernel. I don't want to add 3 lines I do not understand to my BoardConfig, just to change the toolchain :p
[Android Software Development] mauronofrio:
How can i send a change to https://gerrit.omnirom.org for twrp?

How can i add a markdown to my source?
[Android Software Development] Captain_Throwback:
https://github.com/omnirom/android/blob/android-7.1/README.md

For markdown, that's gerrit.twrp.me
[Android Software Development] mauronofrio:
I dont understand what is markdown, is site, a repository or what else?
[Android Software Development] Captain_Throwback:
https://github.com/TeamWin/twrpme/tree/master/_devices
[Android Software Development] mauronofrio:
when i try to push the change i got this problem

mauronofrio@PORTATILE-MAURO ~/twrp/android_bootable_recovery $ git push ssh://mauronofrio@gerrit.omnirom.org:29418/android_bootable_recovery HEAD:refs/for/android-7.1Counting objects: 48, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (41/41), done.
Writing objects: 100% (48/48), 302.73 KiB | 0 bytes/s, done.
Total 48 (delta 14), reused 0 (delta 0)
remote: Resolving deltas: 100% (14/14)
remote: Processing changes: refs: 1, done
To ssh://mauronofrio@gerrit.omnirom.org:29418/android_bootable_recovery
! [remote rejected] HEAD -> refs/for/android-7.1 (no common ancestry)
error: failed to push some refs to 'ssh://mauronofrio@gerrit.omnirom.org:29418/android_bootable_recovery'
[Android Software Development] Captain_Throwback:
Did you make your change on top of the HEAD of the omnirom/android_bootable_recovery android-7.1 branch? Or are you using a different upstream as your origin?
[Android Software Development] mauronofrio:
When i try to clone twrp source i got this error and so i change some github files and i'm trying to send them

mauronofrio@PORTATILE-MAURO ~/twrp $ git clone ssh://mauronofrio@gerrit.omnirom.org:29418/android_bootable_recovery
Cloning into 'android_bootable_recovery'...
remote: Counting objects: 3427, done
remote: Finding sources: 100% (317/317)
remote: Total 20500 (delta 128), reused 20432 (delta 128)
Ricezione degli oggetti: 100% (20500/20500), 50.34 MiB | 1.08 MiB/s, done.
Risoluzione dei delta: 100% (10055/10055), done.
Checking connectivity... fatto.
warning: l'HEAD remoto si riferisce ad un ref inesistente, impossibile eseguire il checkout.
[Android Software Development] JW09I4:
This has likely been asked before, and if one could simply point me in the right direction of where to look or what search term to use in thread search, I'd be extremely appreciative =]​

I know how to build AOSP, however I'm a bit lost on a few things from the OP.

Do I sync TWRP's source files into it's own folder within my AOSP buildroot, or do I simply sync TWRP to it's own directory outside of the buildroot and only copy over certain make files from AOSP?
[Android Software Development] Rapacious:
I'm not really seeing the BoardConfig.mk in this repository

omnirom/android_bootable_recovery @ github

Am I missing something?

Any help would be greatly appreciated.

Thank You.
[Android Software Development] NepoRood:
The BoardConfig.mk file is located inside the device tree, not the recovery folder. Example: device/motorola/quark/BoardConfig.mk
[Android Software Development] celoxocis:
I have succesfully build an TWRP with decryptable /data mount point.

At some point in time i had a problem with mounting /data which i was able to fix.

Now that i fixed all problems im good to go to install SuperSu.

But im running into this problem:

*****************
SuperSU installer
*****************
- Mounting /system, /data and rootfs
mount: mounting /dev/block/mmcblk0p54 on /system failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p54 on /system failed: Device or resource busy
mount: mounting /dev/block/dm-0 on /data failed: Device or resource busy

/dev/block/mmcblk0p54 => is /system

/dev/block/dm-0 => is decrypted userdata mmcblk

full recovery log here:

https://drive.google.com/file/d/0B3LG0HRNQ0LqVDVFeEtIY2VqeGc/view

im thankful for any pointers or a way to debug why the resource is actually busy.

here is dmesg: https://drive.google.com/file/d/0B3LG0HRNQ0LqVzVwX0FrWkpUdVU/view
[Android Software Development] morfikov:
I'm trying to build TWRP recovery image for my phone (Neffos Y5), but unfortunately I have some difficulties with this task. I asked some questions in this thread., but unfortunately there's was no answers, so I decided to link that post here. So if you can guide me or point me in the right direction, I would be glad because I really want to build that image, though I don't really know how. :D
[Android Software Development] swpointer:
I'm going to try building this for the S7 active this weekend. Wish me luck, and thanks for the guide.
[Android Software Development] yhguo:
This is a useful thread! :D I'm wondering how TWRP is compiled for Android Wear watches, e.g. LG Watch Urbane (bass) which is already supported? I'm interested in porting TWRP for Android Wear 2.0 Preview on LG Watch Urbane 2nd (LTE) as the current TWRP seems not to work well with latest squashfs.
[Android Software Development] hyperterminal:
[MENTION=5169699]yhguo[/MENTION] wtf, twrp for a smart watch how, it does not even have volume buttons
[Android Software Development] yhguo:
[MENTION=7496856]sharath3589[/MENTION] it is indeed supported, see this: https://twrp.me/devices/lgwatchurbane.html. Many people have used it to install SuperSU and root the LG Urbane watch. Touch screen of the watch is enough to use TWRP.
[Android Software Development] hyperterminal:
How much does the watch cost, even I want to buy then, does it support all the apps supported by a smartphone
[Android Software Development] yhguo:
The LG Watch Urbane costs around $200. Apps on its current OS, Android Wear 1.x, rely much on the smartphone to complete network transmission, data processing, etc. In the recent future, Android Wear 2.0 will be released to this watch to allow independent apps to run on the watch. The number of watch apps now is small though, compared to phone apps.
[Android Software Development] Rapacious:
How do I find things like BOARD_KERNEL_BASE or BOARD_RECOVERYIMAGE_PARTITION_SIZE?

I've tried using cat on /proc/mtd but no such file exists.

it's for a samsung galaxy on5 (SM-S550TL.)

I am looking at the device tree for the SM-G550T.
[Android Software Development] Joeisgood99:
What does this flag do?

TARGET_NO_BOOTLOADER := true

I thought the answer obvious but,

for instance it's in android_sony_common sony phones have a bootloader....
[Android Software Development] TimSchumi:
Then you may need to combine the output of

ls -al /dev/block/[something]/by-name

cat /proc/partitions

df -h

The first command tells you for example, that the system partition is mmcblk0p16

The second command tells you the size for the partition in bytes (or kilobytes) and the third command tells you the number of blocks (or vice versa)

About BOARD_KERNEL_BASE:

At least in the CM/Lineage Repositories there is a tool which creates an empty device tree. If you add a boot.img as argument (and the tool is able to unpack it) It will read the kernel offset from there. Then, copy this value to your device tree.

As far as I know, TARGET_NO_BOOTLOADER tells TWRP, that the phone doesn't have a fastboot mode. This is the case on Samsung devices. If you set this flag to true, TWRP will hide the "Reboot to Bootloader/Fastboot" Button
[Android Software Development] Rapacious:
Thanks for the help.

I found out my system partition is /dev/block/mmcblk0p19, and my recovery is /dev/block/mmcblk0p1.

Using cat on /proc/partitions told me that mmcblk0p19 has 2990080 blocks.

and df told me that the block size is 4.0K

so I take the block size and multiply it by the # of blocks and convert the product into hex right?
[Android Software Development] TimSchumi:
Block size in df does not seem to be correct. Somewhere is the size of the partitions shown in bytes. If you need the blocksize, take the size in bytesand divide it through the # of blocks.

If you can't find anything, I would multiply the number of blocks with 1024 and see if it's a size that could be correct
[Android Software Development] _that:
No, your output of the partition symlinks is truncated on the right side. Userdata seems to be p21 (it's usually the largest partition on the whole device).
[Android Software Development] Rapacious:
Thank you, that made a difference.

---------- Post added at 09:03 PM ---------- Previous post was at 09:01 PM ----------

I guess my last question is

Do I really need to set TARGET_PREBUILT_KERNEL ?

I don't have a rooted phone so I can't extract a boot.img to split.
[Android Software Development] NepoRood:
You'll need some kind of kernel, lol, TWRP won't run without a kernel. Any OTAs or firmware floating around for your device? You should find a boot image in those...
[Android Software Development] Rapacious:
There's some Firmware from India that I can find.

I have the kernel from the device tree for the T-mobile version of the phone.

Would that work?

I was told it wouldn't. That's why I'm looking elsewhere.
[Android Software Development] NepoRood:
Which device are you trying to build for? There's three versions of my phone, and the same TWRP works on all three...
[Android Software Development] Rapacious:
https://twrp.me/devices/samsunggalaxyon5tmobile.html

I'm trying to build for the SM-S550TL. It's the Simple Mobile version of the Samsung Galaxy on5.

I've already tried flashing the one for the T-Mobile onto my phone, and I just get a security check error.

This has something to do with the Secure Download being enabled but I haven't been able to find a way to disable it.
[Android Software Development] NepoRood:
Did you try the Odin install method?
[Android Software Development] Rapacious:
Yes I did. It said FAIL on the computer, and the phone said secure download fail: recovery.

I've doing some googling and read that turning off the reactivation lock in settings will fix this, but I've also read about the reactivation lock being something entirely different from the secure download.
[Android Software Development] ashyx:
This has nothing to do with secure download.

Security check error means either OEM unlock isn't enabled or the bootloader is locked and the recovery requires to be signed.

If that's the case you're flogging a dead horse.
[Android Software Development] Rapacious:
OEM unlock just disables the FRP lock for me.

---------- Post added at 09:56 PM ---------- Previous post was at 09:55 PM ----------

in Download mode anyway
[Android Software Development] ashyx:
Do you have the stock recovery from the s550tl firmware?
[Android Software Development] Rapacious:
I do not.

---------- Post added at 10:29 PM ---------- Previous post was at 10:10 PM ----------

When I try to use lunch, I'm getting some errors.

WARNING: Trying to fetch a device that's already there

Traceback (most recent call last):

File "build/tools/roomservice.py", line 354, in <module>

fetch_dependencies(device)

File "build/tools/roomservice.py", line 309, in fetch_dependencies

fetch_device(device)

File "build/tools/roomservice.py", line 321, in fetch_device

git_data = search_gerrit_for_device(device)

File "build/tools/roomservice.py", line 81, in search_gerrit_for_device

device_data = check_repo_exists(git_data, device)

File "build/tools/roomservice.py", line 58, in check_repo_exists

"exiting roomservice".format(device=device))

Exception: on5ltetfntmo not found,exiting roomservice

Is this normal?
[Android Software Development] NepoRood:
If you can't flash a TWRP that's already in existence, how you going to flash one that you build? :confused:
[Android Software Development] Rapacious:
that error is from the one I'm trying to build.

---------- Post added at 11:48 PM ---------- Previous post was at 11:46 PM ----------

but I do hear your point.
[Android Software Development] bigsupersquid:
Per your earlier post

lrwxrwxrwx root root 2017-01-09 23:04 RECOVERY -> /dev/block/mmcblk0p1

You can attempt to get your stock recovery.img with dd or cat in adb... Good odds it'll fail but worth a shot.

dd if=/dev/block/mmcblk0p1 of=/sdcard/recovery.img

Or

cat /dev/block/mmcblk0p1 > /sdcard/recovery.img

[EDIT]

if either of those gets you an extractable .img there a tiny chance that reversing the command will allow you to flash the new recovery. But without su i doubt it'll read or write one.

[/EDIT]
[Android Software Development] Gaboros:
I have ported TWRP for my device but it can't flash zips to the system partition. I tried to backup and restore system partition and it worked. But when I try to flash the zip file:

mount: failed to mount /dev/block/platform/mtk-msdc.0/by-name/system at /system: No such file or directory
ApplyParsedPerms: removexattr of /system/bin/bakcuptool.sh to 0 failed: Operation not supported on transport endpoit.

Recovery log: http://pastebin.com/FXxN26xN

Can someone help?
[Android Software Development] Captain_Throwback:
That's an updater-script problem. Don't try to change attributes on the script file and it should install fine.

EDIT: In the log, there's also this error -

error: make_ext4fs_directory: open: No such file or directory

These all point to script errors, not recovery issues.
[Android Software Development] Gaboros:
No it's not it's problem. Tried two different update script. Neither can mount the system partition. And I have older TWRP recovery for my phone which is not my built and it has no problem with this scripts.
[Android Software Development] Captain_Throwback:
Well /system is mounted in your recovery. So I guess you need to look at the device files of the working TWRP build and see what needs to be changed. Maybe you need to manually symlink for working by-name partition handling?
[Android Software Development] Gaboros:
By looking the device files you mean the source? Unfortunately it's not available for the working one. Of course I could compare it if I had it.

Or you think I could unpack the img file the working one and get the information from there?
[Android Software Development] Gaboros:
Added symlinks to the init.recovery.mt6735.rc. Still not works. I think this error comes from the format command but I don't know why. It's works with the other TWRP. :(
[Android Software Development] vampirefo:
You didn't check the box the mount system ro did you? Some people do that, checking that box prevents flashing ROMs, or making any other changes to system.

Boot into twrp, select mount, if the box is checked "Mount system partition read-only" uncheck it.

Sent from my Lineage OS R1HD by tapatalk
[Android Software Development] Gaboros:
No it's not checked. And as far as I know it's only for the backups. Even if it's checked the zips can modify it. Or at least that's how it works in the other recovery which is work and the warning also state this.
[Android Software Development] vampirefo:
No it prevents zips from install, doesn't prevent backups.

Sent from my Lineage OS R1HD by tapatalk
[Android Software Development] Gaboros:
Strange it's work totally reversed on the working TWRP. But anyway it's not checked in my port and fails. :(
[Android Software Development] vampirefo:
If it's opposite on your recovery, then check the box and see what happens.

Sent from my Lineage OS R1HD by tapatalk
[Android Software Development] Gaboros:
Sure I have tried but nothing. Still fails (probably) on the format command.
[Android Software Development] Hacker432:
Hi

I'm facing this error http://pastebin.com/PfKw2e9V while compiling TWRP-3.0.3.

F2FS-tools are in external folder so this is not the problem

I think the problem is in twrp sources

Did anyone have the same error?
[Android Software Development] NepoRood:
Just curious, have you tried older source code?

(ie, CM 12/13 or Omni 5/6)
[Android Software Development] Hacker432:
Solved

https://github.com/Hacker432/androi...mmit/8046fe7a80050b91f5f196d858f32a3bc0b8d2a5
[Android Software Development] Fillint:
Hi ,I extracted boot.img and recovery.img from my device. I dont have any kernel source or CM device tree for this device Is there anything I can do for compiling TWRP?

Mediatek 6592 - Android lollipop 5.1
[Android Software Development] NepoRood:
TWRP don't need source, prebuilt is fine. Did you check github for any kind of 6592 device?
[Android Software Development] Fillint:
Actually checked one of them saying cm.11.0 build(didnt test on my device ). Do you suggest them over prebuilt one ?

Anyway, can you put me in the right direction for using the prebuilt images?
[Android Software Development] NepoRood:
Prebuilt will make it just a "tad bit" easier, lol. Just be sure to add it to your "device".mk

Example:

LOCAL_PATH := device/Alco/RCT6303W87DK
ifeq ($(TARGET_PREBUILT_KERNEL),)
LOCAL_KERNEL := $(LOCAL_PATH)/kernel
else
LOCAL_KERNEL := $(TARGET_PREBUILT_KERNEL)
endif
[Android Software Development] anjelz2012:
please support for Xperia Z5 Premium E6853
[Android Software Development] Android-Andi:
Please read the OP. Maybe you'll fine out what this thread was made for.
[Android Software Development] Sudarshankakoty:
When I try compiling with CM13 sources, I get random missing/makefile error.
[Android Software Development] Groteski:
I've installed the app on my phone when I rebooted into system from TWRP. It asks if you want to install it upon reboot. I would like to delete it but I can't see how.

Thanks!
[Android Software Development] WhiteWolf:
i am building TWRP for Samsung J7 Prime..but when booting in recovery i cant mount both storages (internal and external).....

someone knows the issue ?
[Android Software Development] ashyx:
Check your mount points in the fstab.

If it's mm you won't be able to mount internal storage until its unencrypted.
[Android Software Development] WhiteWolf:
http://pastebin.com/enffu8L8

here is my fstab ....

I cant understand the problem...
[Android Software Development] ashyx:
Are you sure the external sdcard mount point is

/dev/block/sdb1?

Try this:

/external_sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="Micro SDcard";storage;wipeingui;removable
[Android Software Development] WhiteWolf:
no sir it didnt work...
[Android Software Development] ashyx:
Did you copy and paste that all on one line?

It should work.

Please post your recovery.log file or the output on pastebin.com

Edit: you can try this fstab.

http://pastebin.com/raw/H3nAHzsA
[Android Software Development] WhiteWolf:
here is the log...

SDCard Still doesn't mount

http://pastebin.com/sJt09iH6
[Android Software Development] MSF Jarvis:
I don't see external_sd in the initial mounting block in the logs. Is it normal [MENTION=4899305]ashyx[/MENTION] ?
[Android Software Development] ashyx:
It creates the mount point but is unable to mount the partition. Seems he's using Adopted storage and the encryption is causing the issue.

[MENTION=5060472]Varun hellboy[/MENTION] needs to post his device tree to see if he's using the correct crypto flags.
[Android Software Development] oF2pks:
adb unauthorized with cm13/14 repo

To use format/f2fs-tools_version>=1.6, is there an easy way to avoid unauthorized adb within latest twrp3.0.3 , on

cm13/14 repo/compilation

.

Thx for help
[Android Software Development] _that:
lunch an -eng build, not userdebug.
[Android Software Development] Dr4In:
Where do i request official TWRP for Mi Note Pro? Its a flagship from Xiaomi
[Android Software Development] vampirefo:
In a MI Note Pro thread.

https://xdaforums.com/mi-note-pro/development/recovery-twrp-3-0-note-pro-t3317453
[Android Software Development] WhiteWolf:
https://github.com/varunjamwal/android_device_on7xelte .......... here ...sir please take a look
[Android Software Development] ashyx:
Are you using adoptable storage?
[Android Software Development] WhiteWolf:
No
[Android Software Development] DevUt:
Varun you have a typo in the fstab

It is

/external_sd	vfat	/dev/block/mmcblk1p1 /dev/block/mmcblk1

You are missing 1 after blk
[Android Software Development] WhiteWolf:
yeah i corrected it earlier...but no result again
[Android Software Development] Captain_Throwback:
Where's the new log, then?
[Android Software Development] WhiteWolf:
Here it is...

http://pastebin.com/LiP2xZEJ
[Android Software Development] Captain_Throwback:
According to that log, the filesystem for external_sd is "auto", not vfat (and auto does not work). Can you link the fstab you're using? It can't be the one we were looking at before, based on that log.

EDIT: Maybe I should also confirm - are you sure that there's an external SD card currently in your device?
[Android Software Development] WhiteWolf:
The result was same for vfat...i was trying with auto....

I updated the git repo...

And yeah sdcard is there ....

This issue is killing me....
[Android Software Development] ashyx:
You've changed things since posting the first and second log.

You've changed pixel format, the brightness file path, the first log referenced adoptable storage and data wasn't mountable.

I think at this point it's worth trying another sdcard which has been formatted to FAT32/exFat.