yashsingh1/xdaforums huggingface dataset:
[Android Software Development] DeckerSU:
Seems i have discovered a serious bug in TWRP 3.0.2-0 with backup subpartitions. Trying to explain:

In recovery.fstab i have following:

/efs1 emmc /dev/block/bootdevice/by-name/modemst1 flags=display="EFS";backup=1
/efs2 emmc /dev/block/bootdevice/by-name/modemst2 flags=backup=1;subpartitionof=/efs1

modemst2 there is declared of subpartition of /efs1. So in recovery.log i see correct information:

/efs1 | /dev/block/mmcblk0p14 | Size: 1MB
Flags: Can_Be_Backed_Up Has_SubPartition IsPresent
Primary_Block_Device: /dev/block/mmcblk0p14
Display_Name: EFS
Storage_Name: EFS
Backup_Path: /efs1
Backup_Name: efs1
Backup_Display_Name: EFS
Storage_Path: /efs1
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd

/efs2 | /dev/block/mmcblk0p15 | Size: 1MB
Flags: Can_Be_Backed_Up Is_SubPartition IsPresent
SubPartition_Of: /efs1
Primary_Block_Device: /dev/block/mmcblk0p15
Display_Name: efs2
Storage_Name: efs2
Backup_Path: /efs2
Backup_Name: efs2
Backup_Display_Name: efs2
Storage_Path: /efs2
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd

But during backup i see that modemst2 partition backup rewrites modemst1 data:

Backing up EFS...
I:Reading '/dev/block/mmcblk0p14', writing '/external_sd/media/0/TWRP/BACKUPS/e5b5e059/2016-09-17--22-48-10_MMB29M_release-keys/efs1.emmc.win'
Backing up efs2...
I:Reading '/dev/block/mmcblk0p15', writing '/external_sd/media/0/TWRP/BACKUPS/e5b5e059/2016-09-17--22-48-10_MMB29M_release-keys/efs1.emmc.win'
* Generating md5...
I:MD5 for /external_sd/media/0/TWRP/BACKUPS/e5b5e059/2016-09-17--22-48-10_MMB29M_release-keys/efs1.emmc.win: c7934df6e1f5c4dab3fb3cba53424ca3 efs1.emmc.win

* MD5 Created.
I:Partition Backup time: 0
* Generating md5...
I:MD5 for /external_sd/media/0/TWRP/BACKUPS/e5b5e059/2016-09-17--22-48-10_MMB29M_release-keys/efs1.emmc.win: c7934df6e1f5c4dab3fb3cba53424ca3 efs1.emmc.win

* MD5 Created.

As you are see when try to backup /dev/block/mmcblk0p14 TWRP used filepath efs1.emmc.win and when try to backup second efs partition /dev/block/mmcblk0p15 TWRP still use same path. As a result in efs1.emmc.win we get only second EFS2 parition:

00000000: 11 00 00 00-03 00 00 00-D8 01 00 00-00 02 90 E1 Ш ђб
00000010: 00 FE 15 00-00 FE 15 00-00 00 A6 E1-00 00 00 00 ю ю ¦б
00000020: 00 00 A6 E1-00 00 00 00-49 4D 47 45-46 53 32 17 ¦б IMGEFS2
00000030: 00 00 00 5A-EA 32 37 57-01 00 00 00-02 01 00 00 Zк27W

And all contents of EFS1 is missing in backup. Size of efs1.emmc.win = sizeof(modemst2) (!!!) Backup is not include modemst1 partition.

As an result - restoring of this backup (restoring modemst2 without modemst1) "bricks" the phone.

Can somebody try to reproduce the situation on TWRP builded from latest sources? Try to declare one partition as a subpartition of another and try to see the result. How many partitions (really) you will get in backup?
[Android Software Development] Startrek852:
You need to compile with the android-7.0 branch of TWRP, because it has this commit: https://github.com/omnirom/android_bootable_recovery/commit/724c5148a5bf341479bf943b0c64ce8d40814148 which will fix your problem.
[Android Software Development] DeckerSU:
Thx for fast reply. I have an another dummy question. Can i use android-6.0 branch of Omni without full clone of android-7.0 branch? I mean can i clone only "android_bootable_recovery" in exising android-6.0 local repo? How can i do this correctly?

It's enough to clear android_bootable_recovery in local copy of android-6.0 branch and use:

git clone https://github.com/omnirom/android_bootable_recovery/tree/android-7.0

Or this way is incorrect?
[Android Software Development] Startrek852:
Yes, you can use the android-7.0 branch in a 6.0 tree. Just add this to .repo/local_manifests/twrp.xml:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remove-project name="android_bootable_recovery" />
<project path="bootable/recovery" name="android_bootable_recovery" remote="omnirom" revision="android-7.0" groups="pdk-cw-fs" />
</manifest>

Then run repo sync --force-sync.
[Android Software Development] DeckerSU:
Big thx, i was succefully build my TWRP on android-7.0 branch and bug was fixed.
[Android Software Development] Startrek852:
You're welcome.
[Android Software Development] czarsuperstar@gmail.com:
https://github.com/czarsuperstar/android_device_lge_m1

I used mkboot tools to unpack boot.img to get the kernel and dt. Img. Also I used Omni 5.1 downloaded from androidhost since I blew through my 8 GB of hotspot with android bootable recovery 6.0. I have also used 7.0 bootable recovery so the bootable recovery version doesn't matter just get all the proper info about your board (msm8916 or in my case msm8909) you should be on your way. That's if you can't build the kernel itself. I used a build.sh to compile changing paths accordingly and the kernels defconfig. Many kernel devs use a script to build. Won't be hard to find.
[Android Software Development] shoey63:
Have any of you guys synced up to https://github.com/omnirom/android_bootable_recovery/tree/android-7.0, compiled a recovery and tried to flash an image?

Well I have, and there is an issue Which I have reported

It's being ignored in Github, so I'm posting here. [MENTION=912474]Dees_Troy[/MENTION], [MENTION=4878287]_that[/MENTION], can you take a look at it?

Edit: Building on Omni 5.1 branch for Leo and Yuga. Same error on both builds.
[Android Software Development] MSF Jarvis:
The best place would be the #twrp channel on irc.freenode.net . You are more likely to get attention from the relevant people there, plus more people who can actually fix this issue.
[Android Software Development] czarsuperstar@gmail.com:
I had a problem with 7.0 also so I used 6.0.
[Android Software Development] Sykul:
Hi,

I could not install TWRP on my device :(

I have android KitKat 4.4.2. I tried both 2.8.1.0 an 2.7.1.0 versions. On both version everything seems to go right, but after reboot to recovery there is only black screen. No matter if i try with custom recovery or CWM. Each time the same.

I have chinese mobile ALPS A9+ build on MTK6582. Could someone help me to install TWRP on it?
[Android Software Development] Startrek852:
Where the heck are you getting this TWRP that you're flashing??
[Android Software Development] Sykul:
I have not found the TWRP dedicated to my device, so try do make it via PC aps form here:

http://www.gizbeat.com/5786/how-to-make-create-twrp-mt6592-mt6582-mt6572-mt6589-mt6595/

or here:

http://www.mtkroms.com/2015/10/twrp-recovery-for-all-mtk-devices.html
[Android Software Development] shoey63:
[MENTION=5660972]DeckerSU[/MENTION] Cherry-pick this https://gerrit.omnirom.org/#/c/19248/

or wait for it to be merged
[Android Software Development] DeckerSU:
Thx, after i apply this commit:

git fetch https://gerrit.omnirom.org/android_bootable_recovery refs/changes/48/19248/1 && git cherry-pick FETCH_HEAD

It works perfect.
[Android Software Development] almamun512:
I need a help

What is the java version needed for building twrp from omini 6.0 sources

Plz Anyone tell me

i'm trying to build recovery for j2 3g verient

Plz anyone help
[Android Software Development] MSF Jarvis:
1.7
[Android Software Development] almamun512:
https://drive.google.com/open?id=0B0rTXdhaTd2MWGR2c205SklvTDQ

getting this error at the first time of building

and also my device isnt in TARGET_BUILD_VARIANT=eng
[Android Software Development] ashyx:
It's telling you what the error is. You need to add an appropriate theme flag to the BoardConfig.
[Android Software Development] Sykul:
Seriously nobody is able to help me? :(
[Android Software Development] TimSchumi:
How do I create a clean TWRP or Omni Device Tree (preferably with the minimal TWRP sources)? Just like the build/tools/device/mkvendor.sh script in CyanogenMod. I tried creating the Tree with the CyanogenMod script and change everything from cm to omni, but it didn't work
[Android Software Development] ashyx:
Find a device using a similar platform and modify its device tree to suit your device.
[Android Software Development] lj50036:
You can always use this base source... Its only a starting point, but it can be quite useful... :)

https://github.com/lj50036/android_device_vendor_codename/tree/android-6.0

Thx Josh
[Android Software Development] TimSchumi:
[emoji106] Thank you very much
[Android Software Development] TimSchumi:
How can I decrease the size of the Recovery when building TWRP in android-6.0 branch? I need ot to fit in a 8MB partition, but it is about 10MB in size.

EDIT:

Exact Values:

maxsize=8564160

total=9678848
[Android Software Development] MSF Jarvis:
https://github.com/TeamWin/android_device_htc_pico/commit/611e674bb398bf4e212671c7d523f9837be36efc
[Android Software Development] czarsuperstar@gmail.com:
I have a question? I have compiled Twrp for the LG K7 and the Motorola surnia using a prebuilt kernel, but I notice for surnia it has soc.0 in the BoardConfig and I'm able to flash all the custom roms available for surnia but if I don't add soc.0 in the fstab for the LG K7 I get errors in recovery about the path not being a directory (LG K7) . What am I doing wrong? For surnia in command line it says android.hardware.boot=soc.0 , so I tried that to no avail. Im stuck can someone please point me in the right direction? The boot is using Tuxera: https://www.tuxera.com

So I don't know if that has anything to do with it. I have looked everywhere concerning the file system that is being used on the phone. Also Tuxera has a partnership with Microsoft so I don't know where to go or even start. Thanks for any and all assistance provided.

Also there is this: http://www.tuxera.com/products/tuxera-exfat-embedded/
[Android Software Development] Hacker432:
Hi guys

Nougat is here and previews of unofficial ROMs too

My device, Y550, got an unofficial build.

It is still buggy but we're working on it

Anyway, is a new TWRP required for CM14?

A user flashed it with this error:

E: Unknown command [log]

E: Unknown command [log]

Any idea?

P.S: he flashed it with my official TWRP 3.0.2.0 for the device

Inviato dal mio Y550-L01 utilizzando Tapatalk
[Android Software Development] TimSchumi:
I get a "missing seperator" error in line 29 if using this customrecoveryimg.mk or in line 28 if I use this customrecoveryimg.mk file

EDIT: Dump that, there was a Tab missing when copying it from GitHub in the last line
[Android Software Development] czarsuperstar@gmail.com:
For the Surnia the Nougat Rom does the same but boots up.
[Android Software Development] MSF Jarvis:
Yes the error is ignorable, who really gives a f*** for anything but TWRP logs ;)
[Android Software Development] _that:
AOSP recovery got a new command in the updater API to write text to an installation log (/tmp/last_install, which is copied to /cache/recovery/last_install when recovery ends). TWRP currently doesn't support that, but it's uncritical.
[Android Software Development] Hacker432:
Thank you guys

Impeccable as usual :)

Inviato dal mio Y550-L01 utilizzando Tapatalk
[Android Software Development] czarsuperstar@gmail.com:
Any help?
[Android Software Development] Brenza:
I think mine is a very dumb question but I'm new to these things...

I got a new "Digiland DL5003QL", this phone is not supported by any custom recovery I heard of so I'm quite interested in this guide..

Can I build TWRP for my phone, it runs the official firmware and it's not supperted by Omnia or CM... Also I do not have the source code of my rom..

Again, I know it's probably a dumb question :P
[Android Software Development] kenymccornick:
Do you guys have any idea why I keep getting this error every time I flash any custom ROM: "flashing SuperSU... mount:failed to mount /dev/block/bootdevice/by-name/system at /system: device or resource busy"? Then of course umount fails too but the script succeeds and everything ends well. SuperSU works without issues but I don't know if maybe other bugs on my ROM might be related to this. System partition is not mounted when I start flashing. What's going on? Thanks
[Android Software Development] ne0zone75:
Crypto. for OnePlus 3 !?

Hi,

I am trying to build TWRP for OP3 using CM-13.0 device tree and build is successful BUT crypto. is not working properly. You will find my TWRP build flags below :

...
# Crypto
TARGET_HW_DISK_ENCRYPTION := true
#TARGET_CRYPTFS_HW_PATH := $(PLATFORM_PATH)/cryptfs_hw
...
# Recovery
TARGET_RECOVERY_FSTAB := $(PLATFORM_PATH)/rootdir/etc/fstab.qcom
TARGET_RECOVERY_UI_LIB := librecovery_ui_msm
TARGET_RECOVERY_UPDATER_LIBS := librecovery_updater_msm
TARGET_RELEASETOOLS_EXTENSIONS := device/qcom/common
BOARD_HAS_LARGE_FILESYSTEM := true
TARGET_USERIMAGES_USE_EXT4 := true
#TARGET_USERIMAGES_USE_F2FS := true

# TWRP
RECOVERY_VARIANT := twrp
#TARGET_RECOVERY_FSTAB := $(BOARD_PATH)/configs/fstab.qcom
TW_THEME := portrait_hdpi
BOARD_HAS_NO_REAL_SDCARD := true
TARGET_RECOVERY_QCOM_RTC_FIX := true
TW_BRIGHTNESS_PATH := /sys/class/leds/lcd-backlight/brightness
TW_DEFAULT_LANGUAGE := en-US
#TW_EXTRA_LANGUAGES := true
TW_INCLUDE_CRYPTO := true
...

...meanwhile i will try with Omni-6.0 device tree ;)

Thanks
[Android Software Development] lj50036:
Have you had a look at the TWRP device tree ?

https://github.com/TeamWin/android_device_oneplus_oneplus3

Maybe that will help ?

Thx Josh
[Android Software Development] ne0zone75:
Hey [MENTION=5123642]lj50036[/MENTION],it's good to read words from you ?,

I have solved my issue by adding 'TheMuppets' vendor tree for my target device... yes i forgot to add it earlier so there was no proprietary sources at all ?.

I believe that my TWRP build flags are mostly OK, i grabbed them from Omni-6.0 OP3 device tree...

I will check TW Github later...

Thanks and i wish you all the best

Tapatalked from my OnePlus 3
[Android Software Development] ne0zone75:
FYI and to be accurate, i did not manage to get a fully working recovery image with CyanogenMod 13 sources but i did with OmniROM 6 ones.

Regards

Tapatalked from my OnePlus 3
[Android Software Development] DodoGTA:
Where can I submit requests for official support if I have all of the requirements?
[Android Software Development] bigsupersquid:
you could try here

https://twrp.me/contactus/

Somebody mentioned IRC earlier too but I forget the channel.
[Android Software Development] MSF Jarvis:
#twrp is the best place for getting your device supported. You get quick access to the devs, and help as well if needed.
[Android Software Development] czarsuperstar@gmail.com:
Please can someone Aid Me in fixing issues with the LG K7? I have asked for assistance. I think I know what the problem is but I can't create the emulator for testing and debugging.

https://github.com/czarsuperstar/android_device_lge_m1

It's not up to date but I think the paths are not set-up right

---------- Post added at 12:11 PM ---------- Previous post was at 12:07 PM ----------

And I don't have the Phone anymore but I compiled it and will still maintain it if need be. [MENTION=912474]Dees_Troy[/MENTION] I know that you are very busy and I don't mean any offenses but I followed the directions for your analysis. Please let me know if you are really to take over. Thanks
[Android Software Development] ashyx:
You'd be better off actually stating what the issue is.
[Android Software Development] czarsuperstar@gmail.com:
The issue is in Fstab( thinking of the Phone as soc.0). I made the paths as /dev/block/platform/soc.0/by- name/system but I think the paths are supposed to be /dev/block/platform/7824900.sdhci/by- name/system. So I have followed procedure by message to Dees Troy. I am awaiting a response.
[Android Software Development] ashyx:
You're not stating the actual issue. I take the issue is you can't mount any partitions?

Take the paths from the fstab in the stock recovery.
[Android Software Development] czarsuperstar@gmail.com:
It's mounts but when flashing specifically targeted paths: error pops up

I don't have the Phone anymore so I need feedback. I tried to compiled the emulator for testing and debugging but that was unsuccessful. I have a test image uploaded but I have yet to receive feedback. I have a different Phone now so I could leave it as be but than what kind of developer would I be? I always stick with my projects to very end. I can compile any image with no problems. Was just asking for the people who still have the Phone. Thank you for your response.
[Android Software Development] ashyx:
Use the paths in the stock fstab and try adding the following to the BoardConfig:

TARGET_PLATFORM_DEVICE_BASE := /devices/soc.0/

If that doesn't work then maybe you'd be better using the block device path.
[Android Software Development] czarsuperstar@gmail.com:
That's also a problem. Fstab.m1 has it as /dev/block/bootdevice/by- name/system

But the command line has android.boot= 7824900.sdhci

So I can't test it because of not having the phone. Could you tell me how to build the emulator for testing and debugging? Thank you so much.
[Android Software Development] MSF Jarvis:
You cannot flash just anything on an emulator. you need to run a custom emulator build to use TWRP on an emulator. Debugging needs to happen on a physical device
[Android Software Development] czarsuperstar@gmail.com:
Thank you.
[Android Software Development] ashyx:
The command line is simply telling the kernel the boot device is called 7824900.sdhci.

So you could use either in your path and both would work.

I don't use emulators I just get willing testers.
[Android Software Development] czarsuperstar@gmail.com:
Can I use it and put:

TARGET_PLATFORM_DEVICE_BASE := /devices/7824900.sdhci/?
[Android Software Development] czarsuperstar@gmail.com:
Thank you. 7824900.sdhci would probably work. When I put /device/by- name it says not a path in red only soc.0 has proven to be effective. I see that the recovery fstab for the on5 has a path stating specifically: 13540000.dwmmc0. So the question is if the fstab has simply just /dev/block/bootdevice/by- name/system

Would putting the same line work in the BoardConfig.mk with the fstab as :- /dev/block/bootdevice/by- name/system work?

Thank you again.
[Android Software Development] ashyx:
Yes that will work if that is indeed the correct path to the partition.

What is this particular device?
[Android Software Development] czarsuperstar@gmail.com:
LG K7 Metro/LG tribute 5

https://github.com/czarsuperstar/android_device_lge_m1

Thank youagain I will try it.
[Android Software Development] :
Hello everybody, I want to compile a TWRP recovery for my Medion Lifetab S9512 with the shortened omni manifest. But even though it compiles without problems it stucks at the Boot Logo and starts to boot the system when trying to enter the recovery. The CM-Recovery I compiled with the same BoardConfig.mk is booting, but not the TWRP-recovery. Additionally, I cannot create any logs when boating because adb is not working before the system is running. Could anybody give me an advice for which flags I have to look, to solve this situation? Here is my device tree

Thanks in advance!
[Android Software Development] bigsupersquid:
are you building -eng variant? that'll give you access to adb as soon as it starts up the service.
[Android Software Development] :
Even with -eng instead of -userdebug variant logcat starts to work when the system is booting and not when the recovery fails. Here is the log that gets created.
[Android Software Development] zainifame:
[MENTION=912474]Dees_Troy[/MENTION] where can i get branch for twrp 3.0.2-1/2/3 sir?
[Android Software Development] bigsupersquid:
ah, recovery doesn't logcat by default, you have to set something i forget for that. i was thinking of the rom itself.

you could try

cat /proc/last_kmsg

to see if the kernel registered any issues before rebooting
[Android Software Development] ashyx:
It doesn't exist. They are all 3.0.2-0 builds with modified build numbers.
[Android Software Development] :
Thank you for that! Even though it says "No errors detected" I can search it for hints :) Here it is.
[Android Software Development] zainifame:
I think that's have branch :) thanks, and di u know how to register twrp to official?, my build is not official so i planned to register an official build
[Android Software Development] ashyx:
Contact Dees_Troy on IRC
[Android Software Development] bigsupersquid:
it crashes here

[ ?* ?*4.634246] Warning: unable to open an initial console.

[ ?* ?*4.634765] Root-NFS: no NFS server address

[ ?* ?*4.634979] VFS: Unable to mount root fs via NFS, trying floppy.

[ ?* ?*4.636077] VFS: Cannot open root device "(null)" or unknown-block(2,0)

[ ?* ?*4.636444] Please append a correct "root=" boot option; here are the available partitions:

[ ?* ?*4.636749] b300 ?* ?* ?* ?*15532032 mmcblk0 ?*driver: mmcblk

[ ?* ?*4.637298] ?* b301 ?* ?* ?* ?* ?* ?* 128 mmcblk0p1 f9f21f00-a8d4-5f0e-9746-594869aec34emmcblk0p1

[ ?* ?*4.637878] ?* b302 ?* ?* ?* ?* ?* ?* 256 mmcblk0p2 f9f21f01-a8d4-5f0e-9746-594869aec34emmcblk0p2

[ ?* ?*4.638275] ?* b303 ?* ?* ?* ?* ?* ?* ?*64 mmcblk0p3 f9f21f02-a8d4-5f0e-9746-594869aec34emmcblk0p3

[ ?* ?*4.638824] ?* b304 ?* ?* ?* ?* ?* ?*1024 mmcblk0p4 f9f21f03-a8d4-5f0e-9746-594869aec34emmcblk0p4

[ ?* ?*4.639373] ?* b305 ?* ?* ?* ?* ?* ?*8192 mmcblk0p5 f9f21f04-a8d4-5f0e-9746-594869aec34emmcblk0p5

[ ?* ?*4.639770] ?* b306 ?* ?* ?* ?* ?* 65536 mmcblk0p6 f9f21f05-a8d4-5f0e-9746-594869aec34emmcblk0p6

[ ?* ?*4.640319] ?* b307 ?* ?* ?* ?* ?* 65536 mmcblk0p7 f9f21f06-a8d4-5f0e-9746-594869aec34emmcblk0p7

[ ?* ?*4.640930] sr_class1p5_calib_work: iva: Calibration complete: Voltage Nominal=1114000Calib=1101460 margin=50000

[ ?* ?*4.641510]

[ ?* ?*4.641723] ?* 103:00000 ?* ?* ?* ?*512 mmcblk0p8 f9f21f07-a8d4-5f0e-9746-594869aec34emmcblk0p8

[ ?* ?*4.642272] ?* 103:00001 ?* ?* ?* 6144 mmcblk0p9 f9f21f08-a8d4-5f0e-9746-594869aec34emmcblk0p9

[ ?* ?*4.642669] ?* 103:00002 ?* ?* ?*32768 mmcblk0p10 f9f21f09-a8d4-5f0e-9746-594869aec34emmcblk0p10

[ ?* ?*4.643249] ?* 103:00003 ?* ?* ?* 8192 mmcblk0p11 f9f21f0a-a8d4-5f0e-9746-594869aec34emmcblk0p11

[ ?* ?*4.643798] ?* 103:00004 ?* ?* ?* 8192 mmcblk0p12 f9f21f0b-a8d4-5f0e-9746-594869aec34emmcblk0p12

[ ?* ?*4.644348] ?* 103:00005 ?* ?* 524288 mmcblk0p13 f9f21f0c-a8d4-5f0e-9746-594869aec34emmcblk0p13

[ ?* ?*4.644744] ?* 103:00006 ?* ?* 262144 mmcblk0p14 f9f21f0d-a8d4-5f0e-9746-594869aec34emmcblk0p14

[ ?* ?*4.645294] ?* 103:00007 ?* ?* 131072 mmcblk0p15 f9f21f0e-a8d4-5f0e-9746-594869aec34emmcblk0p15

[ ?* ?*4.645843] ?* 103:00008 ?* 14417408 mmcblk0p16 f9f21f0f-a8d4-5f0e-9746-594869aec34emmcblk0p16

[ ?* ?*4.646423] b310 ?* ?* ?* ?* ?* ?*4096 mmcblk0boot1 ?*(driver?)

[ ?* ?*4.646789] b308 ?* ?* ?* ?* ?* ?*4096 mmcblk0boot0 ?*(driver?)

[ ?* ?*4.647338] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)

kernel panics are often right at the end of last_kmsg

my guess is that it's not loading initramfs/initrd properly
[Android Software Development] :
Thank you, I will check that
[Android Software Development] ashyx:
Are you sure this is correct?
[Android Software Development] :
For Cm-recovery this was working, but maybe twrp can't work correctly without. I take a look at this too.
[Android Software Development] kantjer:
I made my first TWRP build for Angler using the Omni android-7.0 branch.

The build finished OK but when booting into recovery TWRP is presenting me with an encryption password. AFAK this was fixed in the 3.0.2-1 and newer builds.

Any tips how to fix this, my device is encrypted but with the stock password.
[Android Software Development] DodoGTA:
Then enter "default_password" as your password (if you haven't set your own password)
[Android Software Development] kantjer:
Thanks but that's not the solution I'm looking for.

I make scheduled nandroids so I need to avoid the password input all together like on the the 3.0.2-1 and -2 builds.
[Android Software Development] Sharashchandra:
Hi

Please help me how to compile TWRP for stock lollipop ROM (android 5.0), mtk6582
[Android Software Development] Zoggn:
Hello! I try to build TWRP recovery for Alcatel Idol 2 Mini(qualcom 200 msm8610). When I flash recovery and reboot i see only black screen. I pull recovery log(https://gist.github.com/zoggn/7f5d91b710edae4622ee630c8d7919c6 ). My TWRP Tree here-> https://github.com/zoggn/android_device_tcl_miata . (excuse me for my bad English:o)