[Unofficial] HTC U11+ TWRP Recovery

[goodman_east]

@goodman_east

I patched the kernel, dtb to remove dm-verity and forceencrypt, then replaced the @nkk71 build.
Can you try this one? Let it decrypt data and then reboot to system.

https://drive.google.com/open?id=1d1tbGSeEMmuGqy45_Ocppo_6bBgedk9m

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

 

[sabpprook]

@nkk71
Will it be "androidboot.selinux=permissive" cause this problem?

 

[sabpprook]

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 4362219

How about this one? I remove androidboot.selinux=permissive from cmdline

https://drive.google.com/open?id=12DKLsNGihq7BqbS_4p8xc3pMbUfZvE_2

 

[nkk71]

@nkk71
Will it be "androidboot.selinux=permissive" cause this problem.

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.

 

[nkk71]

@goodman_east

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?

 

[goodman_east]

@goodman_east

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?

YES

Edit: double checked

 

[nkk71]

YES

Edit: double checked

can you do a

getprop

actually 3:
1- during booted ROM
2- on twrp decryption prompt
3- after decryption

 

[goodman_east]

can you do a

getprop

actually 3:
1- during booted ROM
2- on twrp decryption prompt
3- after decryption

a moment please

Edit
1- during booted ROM 1
2- on twrp decryption prompt 2
3- after decryption 3

 

[nkk71]

a moment please

Edit
1- during booted ROM 1
2- on twrp decryption prompt 2
3- after decryption 3

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)

 

[goodman_east]

[QRCODE][/QRCODE]

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)

Thank U.

View attachment boot.emmc.zip

 

[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!!

 

[digio1996]

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!!

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

 

[nenebear]

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

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

 

[goodman_east]

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!!

Try the following instruction to root your U11 plus system.
1 make sure oem unlock open and bootloader unlocked
2 flash latest TWRP @nkk71 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 @Chainfire https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip
6 reboot to system

 

[devsk]

Try the following instruction to root your U11 plus system.
1 make sure oem unlock open and bootloader unlocked
2 flash latest TWRP @nkk71 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 @Chainfire https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip
6 reboot to system

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!!

 

[sabpprook]

@nkk71
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

 

[goodman_east]

@nkk71
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

other files moved to vendor too.

 

[digio1996]

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!!

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!

 

[goodman_east]

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!!

Does supersu closed source or open source affect to gain root?
Supersu is enough for me.

 

[milesd]

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!

Take out original boot.img from ota posted above, in case of accident flash that one back again. fastboot flash boot bootfilename.img