yashsingh1/xdaforums huggingface dataset:
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] nkk71:
^^ Number 3 --> BAD, incorrect process.

^^ Number 7 --> expected, after 30 failed attempts your device is supposed to wipe itself (google security).

Let's try again, if you can, please follow the exact procedure mentioned:

Normally booting ROM

Set a PIN

on boot

Reboot normally and make sure PIN works properly

Reboot to TWRP

It will ask for a password -> CANCEL the prompt! do not let it decrypt

Reboot and tell me if the ROM accepts your PIN

After that stop,

do NOT bother trying to decrypt in TWRP again

, if the above process works for the booted ROM, then vold_decrypt is changing something you don't want.

If the ROM still does not accept your PIN, then it's the something unrelated to decryption in TWRP.

And do you know if you're running with verity enabled or not? (eg if you have Magisk flashed then it should be disabled), you can do an

adb shell mount

in booted ROM and it should give some info.
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] lyfkevin:
Oh Sorry, I forgot to mention that I cannot go into twrp directly by

,fastboot boot twrp.img, It gave blackscreen

So I flashed into recovery first.

Does the version I using affect?

My u11+ is 1.05.400.13 hk version which same as below

and I OTA updated to .10.400.23

How to grab log in blackscreen, fastboot works, adb failed.

">fastboot continue"

resuming boot...

FAILED (remote: Failed to load image from partition: 00000050)

finished. total time: 0.159s
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] goodman_east:
Kernel sources of U11 plus have been released here: https://www.htcdev.com/devcenter/downloads
[MENTION=2605798]nkk71[/MENTION] [MENTION=1162986]Captain_Throwback[/MENTION]
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] devsk:
I haven't seen an official RUU for U11+. Has anybody?
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] nkk71:
fastboot boot <img> doesn't work on all devices, so never mind, just flash it as usual.

But can you please try the instructions from my previous post https://xdaforums.com/showpost.php?p=74836915&postcount=80
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] devsk:
In case , someone is looking for the stock boot/recovery from HTC for Magisk or even for recovering from a bad twrp flash, find it at https://xdaforums.com/htc-u11/development/stock-recovery-taiwan-version-1-10-709-t3719599
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] digio1996:
Well, there is a RUU_OCEAN_WHL_O80_SENSE90GP_MR_NA_Gen_Unlock_2.31.617.2 online but i don't know if it is actually an original one. I would really like to try to install this recovery and root my device (i need root for many reasons) but first i would like to find a RUU for my U11+. Am i the only one with CID HTC_622?
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] goodman_east:
It is a RUU of HTC U11, not for U11 plus.

Maybe U will need this: https://androidfilehost.com/?w=search&s=ocean_M
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] goodman_east:
The ROM doesn't accept my PIN after I do exactly what you asked the first time I input my PIN, BUT the second time the PIN is accepted.

I'll test again to confirm this.

Edit: Maybe I typed a wrong PIN first time. The ROM can boot to system if NOT let TWRP decrypt.

Edit2: I removed PIN and set another one, rebooted to TWRP and canceled request of PIN, and then rebooted to system, input my new PIN, and can boot to system.
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] nkk71:
Thanks for the feedback, a couple more tests please (you'll need to be connected to the PC for the second test):

Boot ROM, make sure PIN works

Reboot to TWRP

Enter a

wrong

PIN and let decryption fail

Reboot ROM, check if PIN still works

If it still works

Reboot to TWRP

While TWRP is waiting at the decryption screen, open an adb shell:

adb shell
~ # [B][COLOR="Blue"]date[/COLOR][/B]
Fri Jun 26 03:42:46 GMT 1970

As you can see the date time is wrong, let's fix it before decryption

~ # [B][COLOR="blue"]date 121613212017[/COLOR][/B]
Sat Dec 16 13:21:00 GMT 2017

The format for the datetime is MMDDhhmmYYYY (so month, day, hour, minutes, year)

~ # [B][COLOR="blue"]date[/COLOR][/B]
Sat Dec 16 13:28:10 GMT 2017

^^ okay date and time are now correct

.

Enter correct PIN, and let TWRP decrypt

Reboot, and check if PIN is still working in ROM

You may want to cross your fingers while doing it, cause I'm out of ideas if this doesn't work :o
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] goodman_east:
I'll test right now.

Edit1: After enter a wrong PIN in TWRP, It said that Password failed, please try again. But I chose to press cancel and reboot to system. And then enter my PIN, but cannot be accepted.
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] nkk71:
Can you try the second method (setting the date and time correctly, before trying any decryption).
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] goodman_east:
Okay, I need format data to enter system first. wait a sec please.

Edit1:

1 change system language to English and set a PIN of 1122.

2 reboot normally and PIN 1122 accepted, boot to system.

3 reboot to TWRP without touch anything,

D:\adb>adb shell
~ # [6ndate
date
Thu Feb 5 12:12:25 GMT 1970

4 change date and time

hu Feb 5 12:12:25 GMT 1970
~ # [6ndate 121720232017
date 121720232017
Sun Dec 17 20:23:00 GMT 2017
~ # [6ndate
date
Sun Dec 17 20:23:04 GMT 2017

5 enter 1122 to decrypt, and data decrypted successfully.

6 reboot, PIN of 1122 is incorrect, cannot boot to system.

Edit2: It seems I type a wrong date(present time is 2017/12/16, not 2017/12/17), I'll test one more time.
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] nkk71:
Unfortunately I'm out of ideas for the moment :(

I'll let you know if anything comes to mind, but all this is very weird.
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] goodman_east:
Test one more time and still my PIN was not accepted.

D:\adb>adb shell
~ # [6ndate
date
Thu Feb 5 12:28:33 GMT 1970
~ # [6ndate 121620382017
date 121620382017
Sat Dec 16 20:38:00 GMT 2017
~ # [6ndate
date
Sat Dec 16 20:38:04 GMT 2017
~ # [6n
D:\adb>adb pull tmp
pull: building file list...
pull: tmp/recovery.log -> ./recovery.log
1 file pulled. 0 files skipped.
979 KB/s (25088 bytes in 0.025s)

upload the log View attachment log.zip.

Thank U very much for helping us to build TWRPs.
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] nkk71:
We could try something, not sure how much difference it will make.

1- Set PIN, make sure it's properly working in ROM

2- Enter TWRP, at the decrypt prompt let's make a backup before decrypting:

adb shell

dd if=/dev/block/bootdevice/by-name/extra of=/tmp/extra_0.img
dd if=/dev/block/bootdevice/by-name/misc of=/tmp/misc_0.img

3- decrypt in TWRP, then pull the same ones

adb shell

dd if=/dev/block/bootdevice/by-name/extra of=/tmp/extra_1.img
dd if=/dev/block/bootdevice/by-name/misc of=/tmp/misc_1.img

please be careful with the above commands, dd can be dangerous (if is inputFile, of is outputFile)

zip them up and send them to me please.

If you don't want to wait for me to take a look at them, before rebooting out of TWRP, restore the initial ones

dd if=/tmp/extra_0.img of=/dev/block/bootdevice/by-name/extra
dd if=/tmp/misc_0.img of=/dev/block/bootdevice/by-name/misc

But this is really a longshot
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] sabpprook:
[MENTION=5064339]goodman_east[/MENTION]

I patched the kernel, dtb to remove dm-verity and forceencrypt, then replaced the [MENTION=2605798]nkk71[/MENTION] build.

Can you try this one? Let it decrypt data and then reboot to system.

https://drive.google.com/open?id=1d1tbGSeEMmuGqy45_Ocppo_6bBgedk9m
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] goodman_east:
Give me a download link please.

But I'll test [MENTION=2605798]nkk71[/MENTION] 's instructures first.
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] goodman_east:
misc_0 and misc_1 are the same.

extra changed after data decryption

View attachment dd.zip

Edit1: restore extra_0 to extra partition.

~ # [6ndd if=/tmp/extra_0.img of=/dev/block/bootdevice/by-name/extra
dd if=/tmp/extra_0.img of=/dev/block/bootdevice/by-name/extra
128+0 records in
128+0 records out
65536 bytes (64.0KB) copied, 0.010105 seconds, 6.2MB/s
~ # [6nreboot
reboot

My PIN cannot be accepted

Boot to TWRP without decryption, dd extra

D:\adb>adb shell
~ # [6ndd if=/dev/block/bootdevice/by-name/extra of=/tmp/extra_2.img
dd if=/dev/block/bootdevice/by-name/extra of=/tmp/extra_2.img
128+0 records in
128+0 records out
65536 bytes (64.0KB) copied, 0.008220 seconds, 7.6MB/s
~ # [6nexit
exit

D:\adb>adb pull /tmp
pull: building file list...
pull: /tmp/recovery.log -> ./recovery.log
pull: /tmp/extra_2.img -> ./extra_2.img
2 files pulled. 0 files skipped.
269 KB/s (84267 bytes in 0.305s)

extra_2.img is not the same as either extra_0.img or extra_1.img.

View attachment extra_2.zip
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] nkk71:
well try restoring extra to it's original _0 one and see if it works.
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] goodman_east:
I test something as following:

1 Boot to TWRP with decryption, restore extra_0, and reboot to bootloader

D:\adb>adb push extra_0.img /tmp
7481 KB/s (65536 bytes in 0.008s)

D:\adb>adb shell
~ # [6nls /tmp
ls /tmp
extra_0.img extra_2.img recovery.log
~ # [6ndd if=/tmp/extra_0.img of=/dev/block/bootdevice/by-name/extra
dd if=/tmp/extra_0.img of=/dev/block/bootdevice/by-name/extra
128+0 records in
128+0 records out
65536 bytes (64.0KB) copied, 0.010268 seconds, 6.1MB/s
~ # [6n

2 boot to TWRP from bootloader, dd extra partition as extra_3.img without decryption

D:\adb>adb shell
~ # [6ndd if=/dev/block/bootdevice/by-name/extra of=/tmp/extra_3.img
dd if=/dev/block/bootdevice/by-name/extra of=/tmp/extra_3.img
128+0 records in
128+0 records out
65536 bytes (64.0KB) copied, 0.007947 seconds, 7.9MB/s
~ # [6nexit
exit

D:\adb>adb pull /tmp
pull: building file list...
pull: /tmp/recovery.log -> ./recovery.log
pull: /tmp/extra_3.img -> ./extra_3.img
2 files pulled. 0 files skipped.
261 KB/s (84267 bytes in 0.314s)

And extra_3 is the same as extra_0.

seems exra was modified when rebooting from TWRP to system.

Edit1: After doing all of those above, boot to system, PIN cannot be accepted

Edit2: boot to TWRP again to dd extra as extra_4

D:\adb>adb shell
~ # [6ndd if=/dev/block/bootdevice/by-name/extra of=/tmp/extra_4.img
dd if=/dev/block/bootdevice/by-name/extra of=/tmp/extra_4.img
128+0 records in
128+0 records out
65536 bytes (64.0KB) copied, 0.008036 seconds, 7.8MB/s
~ # [6nexit
exit

D:\adb>adb pull /tmp
pull: building file list...
pull: /tmp/recovery.log -> ./recovery.log
pull: /tmp/extra_4.img -> ./extra_4.img
2 files pulled. 0 files skipped.
2252 KB/s (84267 bytes in 0.036s)

extra_4 is the same as extra_2

Edit3: format data, boot to system, set a PIN ,boot normally, boot to TWRP, dd extra as extra_5

extra_5 is different from anyone of extra_0 to extra_4

View attachment extra345.zip
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] goodman_east:
cannot touch in TWRP, but data successfully decrypted with default password.

And cannot boot to system due to a prompt of password incorrect.

View attachment recovery.zip
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] sabpprook:
[MENTION=2605798]nkk71[/MENTION]

Will it be "androidboot.selinux=permissive" cause this problem?
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] sabpprook:
How about this one? I remove androidboot.selinux=permissive from cmdline

https://drive.google.com/open?id=12DKLsNGihq7BqbS_4p8xc3pMbUfZvE_2
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] nkk71:
Doubt it, all this is very strange however. The normal U11 is using the same method (same files and services) except it lacks a vendor partition, and the only other device I've seen that is using vold_decrypt + FDE Keymaster 3 and also has a vendor partition is some mediatek device that I don't know (can't remember the name), but everything working properly.

I have no idea what could be causing this *change*. I'll try to ask someone more skilled, if they have any ideas.
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] nkk71:
[MENTION=5064339]goodman_east[/MENTION]

Just want to reconfirm one thing:

When ROM fails to accept PIN or default password, when you reboot to TWRP it is still able to decrypt properly right?
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] goodman_east:
YES

Edit: double checked
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] nkk71:
can you do a

getprop

actually 3:

1- during booted ROM

2- on twrp decryption prompt

3- after decryption
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] goodman_east:
a moment please

Edit

1- during booted ROM 1

2- on twrp decryption prompt 2

3- after decryption 3
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] nkk71:
Thanks, can you please also send me a backup of your boot.img (the exact one from your device, just make a backup in twrp of boot only, and send it over)
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] goodman_east:
[QRCODE][/QRCODE]

Thank U.

View attachment boot.emmc.zip
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] milesd:
black screen

hi there, at least one user wrote about no success with booting twrp ending up in a black screen. all others had luck? booting twrp without flashing it?

I tried every version by coming out, same result. fastboot boot twrpxxx.img. first to come is the new 'letter' from htc about unlocked bootloader followed by blscr.

Software of that phone is still so poor, I want to gather upcoming otas (full of hope) and keep or at least save my stock recovery as I haven't found any

for my version 1.10.400.23 in the net, so I dont wanna flash twrp for now.

A nice evening everywhere!!
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] digio1996:
I have got your same problem and same version (1.10.400.23). I just need root but i am worried about going back then. If anyone find stock recovery for this version please let us know :D
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] nenebear:
Here is the ota zip link

1.05.709.12 -- 1.04.709.1

http://fotadl-az.htc.com/secure/OTA...1.04.709.1_release_515101wb3yz82664g0pd2z.zip

1.10.709.23 -- 1.05.709.12

http://fotadl-az.htc.com/secure/OTA....05.709.12_release_517077z7dxrjhjj6rk2y9h.zip

1.10.400.23 -- 1.05.400.13

http://fotadl-az.htc.com/secure/OTA....05.400.13_release_517158ov5r8lbbi6tc9m38.zip
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] goodman_east:
Try the following instruction to root your U11 plus system.

1 make sure oem unlock open and bootloader unlocked

2 flash latest TWRP [MENTION=2605798]nkk71[/MENTION] https://www.androidfilehost.com/?fid=673791459329066862

3 boot to TWRP, choose wipe-format data, input yes and enter

4 boot to bootloader or download, and then boot to recovery again.

DO NOT

reboot to system.

5 flash latest supersu [MENTION=631273]Chainfire[/MENTION] https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip

6 reboot to system
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] devsk:
Instead of that using the closed source SuperSU, use open source Magisk to root, and without touching the recovery partition. Follow this procedure:

1. Download http://fotadl-az.htc.com/secure/OTA....05.400.13_release_517158ov5r8lbbi6tc9m38.zip

2. Extract firmware.zip.

3. Extract boot.img from firmware.zip from step 2 and transfer to the /sdcard.

4. Install Magisk Manager and select Beta channel

5. Click install and choose to use "patch the stock boot image" method. It will browse you to /sdcard. Choose the boot.img from step 3. After its done, it will give you path of patched boot image.

6. Transfer the patched boot image from step 5 to PC using 'adb pull'

7. Boot the phone into download mode and flash the patched boot image.

8. Reboot and enjoy!!
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] sabpprook:
[MENTION=2605798]nkk71[/MENTION]

found "qseecomd_static" under /vendor/bin/ and it will be called in download mode

service qseecomd_static /sbin/qseecomd_static
class core
seclabel u:r:htc_dlmode:s0
user root
group root
disabled

on property:ro.bootmode=download
start qseecomd_static
start htc_dlmode
setprop sys.usb.config fastboot

on property:ro.bootmode=RUU
start qseecomd_static
start htc_dlmode
setprop sys.usb.config fastboot

Build a TWRP using "qseecomd_static" instead "qseecomd"

https://drive.google.com/open?id=1oJZbz0Xh96AqKWQmT9A1AWe0lACAh35n
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] goodman_east:
other files moved to vendor too.
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] digio1996:
Thank you so much! I'm gonna try this tomorrow! I have just a question.. for point number 7, i will do "fastboot erase cache" and then "fastboot flash boot boot.img" .. is it correct?

If something goes wrong in the flash of boot.img how do i go back? Thank you!
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] goodman_east:
Does supersu closed source or open source affect to gain root?

Supersu is enough for me.
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] milesd:
Take out original boot.img from ota posted above, in case of accident flash that one back again. fastboot flash boot bootfilename.img
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] DanteGR:
Thank you for this.

Being away for too long from HTC and all so just one question if I may.

If you need to receive an OTA what's the procedure?

Unroot, relock bootloader and receive the OTA?

Thank you in advance.
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] nkk71:
Doubt it would matter whether it's static or dynamically linked. In hosd they're probably using a static build because the linker (/system/bin/linker[64]) isn't available.

Also qseecomd & co aren't really the problem, TWRP is able to decrypt properly, both the first time and subsequent times. As I mentioned the ROM is however no longer able/willing to accept the decryption key, possibly related to a "key upgrade" occurring during TWRP decrypt, thereby invalidating the key(s) for decryption in ROM.

It's a rather complicated matter, and I'm neither an expert nor even a *decryption amateur* to be able to figure this out easily. Considering I do not have a device with this particular issue, I can only rely on whatever source code and articles are available to the general public, and try to make some [wild] guesses.

But this also takes time and is not one of my favorite subjects, so it's not the highest priority for me. I'm not saying I will not pursue it further, but until I go through the sources, etc. and *think* I found something, I'm not going to send you more blind builds, which I doubt would make any difference.

[MENTION=4375068]sabpprook[/MENTION] btw, my device tree is here https://github.com/nkk71/android_device_htc_ocm/tree/android-8.0

if you want to build using it, I'm using omni's minimal 8.0 manifest https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni/tree/twrp-8.0
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] devsk:
With magisk, when you want to take OTA, you follow this guide: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips

---------- Post added at 09:10 AM ---------- Previous post was at 09:07 AM ----------

Yes, that flash command is correct but I did only the boot, and did not need to erase cache.

If something goes wrong, you can flash the stock boot image that you got in Step 3. using fastboot just like above. It will just undo whatever magisk did.
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] nicechan:
----------

thanks for your guide, and for developers‘ hard work.

I rooted my U11+ by this method, here I have one question.

can I reboot to recovery again?

cause I flashed recovery,then flash SU without wipe data, then I need password to boot to system, but I didn't set a password.

so I used fastboot -w, wiped all data as a new phone, I just want to know if I reboot to recovery and flash something, will I have to wipe data again?

by the way, I'm form beijing, but I don't know too much about code or development, can you leave me a contact?

like wechat or QQ or something, thanks again!

---------- Post added at 03:18 AM ---------- Previous post was at 03:11 AM ----------

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

Hi, I followed your guide and searched magisk's guide as this:

Via Magisk Manager (Only support v14.0+):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the latest Magisk Manager
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/MagiskManager/patched_boot.img[.tar]
Copy the patched boot image to your PC. If you can't find it via MTP, you can pull the file with ADB: adb pull /sdcard/MagiskManager/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. If using fastboot: fastboot flash boot /path/to/patched_boot.img, or use the ODIN software.
Voilà!

I succeed to gain the patched boot image, but when I flashed this by fastboot flash boot patched_boot.img, I reboot into a black screen.

so I had to flash the stock boot.img extracted from your OTA zip, then I can reboot to system again, but didn't get root.

where did I do wrong? or can I have some other way to try?

thanks for your kind!
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] goodman_east:
Check your pm please.
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] milesd:
my u11+ rollercoaster day

Never read a success root message here.

My first try: KingRoot. stuck at 1%-no root

2nd TWRP 3.1.1.2 cant read encrypted partition, anyway, install SuperSU 2.82 from sdcard- no root

3rd TWRP 3.2.0.0 handles encryption, install SuperSU 2.82- no root, after new reboot encrypted system

4th TWRP 3.2.0.1 handles encryption but encrypted system after reboot

5th Magisk (try it, why not) very confusing first time, patched_boot.img bringing a bootloop-no root

So I'm back to stock now and learn to be more patient!

I had OneX, M7, M9+, I was really happy while unboxing U11+, 'cause I didn't know......
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] digio1996:
same here, it just reboot into a black screen :mad:

If we want root it seems that we have to install a custom recovery :(
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] devsk:
did you guys select Beta channel and install 14.5 of Magisk? It was a breeze for me, it worked the first time without any fuss.
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] digio1996:
Ops.. i didn't :silly:. Where do you find the beta channel?

Edit: found it in app settings, i will let you know if that works

Edit 2: IT WORKED, thank you so much!!!
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] lukemo:
but is it necessary in your opinion to patch the boot img? Is it not possible to flash magisk.zip (14.5) with twrp as we do with the pixel 2 xl? Thanks...
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] nkk71:
No offence guys, I'm just a casual visitor here, but

Isn't this supposed to be a development thread

About TWRP in particular

So I fail to see the point of all the random questions in here, like

where do I get stock recovery X

how do I root this device

where can I find OTA

how do I patch boot.img

Shouldn't these questions go to Q&A and guides to General :confused:

That way people actually following

development

of

[Unofficial] HTC U11+ TWRP Recovery​

can stay focused on it.
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] milesd:
OK, you're right! working perfect! But explanation was a bit sloppy.

Thank you!!
[HTC U11+ ROMs, Kernels, Recoveries, & Other Develo] devsk:
No offence taken [MENTION=2605798]nkk71[/MENTION]. Apologies for derailing the thread.