[Unofficial] HTC U11+ TWRP Recovery

[Tumpster]

I can't seem to even seem to get my Linux Mint box to see my HTC U11+ when in bootloader mode. No issues seeing it normally but bootloader/fastboot seems to go blind. Any one else run into this issue?

 

[Exelios]

Encryption is not a problem for Magisk

You just have to wipe data in TWRP, this removes encryption until next boot, so do not reboot! Flash magisk from MicroSD now before rebooting, as data is not encrypted at this moment.

Stupid simple way we got around rooting many phones.
Works in most cases, if it fails then there is also something else holding magisk back.

Never patch a boot.img manually again.

 

[b_rajesh13]

Hi all.

I attempted to flash twrp. See below for the command and results. It seems successful.
I proceeded to execute the 'fastboot reboot-bootloader' command after flashing. Then, On the phone I selected 'Reboot to Recovery'. But after initial boot the phone comes back to the fastboot screen without starting the TWRP. I can't seem to fire up TWRP for some reason.
I tried erasing the cache as recommended by some other forums but not helping.
Any help will be appreciated! Thank you!

PS C:\Users\rajesh.balakrishnan1\Desktop\platform-tools> .\fastboot flash recovery twrp-3.2.1-0_TEST1212_2_ocm.img
target reported max download size of 2399200000 bytes
sending 'recovery' (44264 KB)...
OKAY [ 3.185s]
writing 'recovery'...
(bootloader) HOSD CL#1010171
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 4.716s]
finished. total time: 7.914s

 

[b_rajesh13]

No decrypt, no write to partitions, so no.

I stuffed up my phone with a treble enabled rom and after several attempts flashing the stock RUU zip file, I resort to recovering thr phone through a nandroid backup using TWRP.

So does that mean my recovery attempt will fail too? Any way to make it work?

 

[Cryptycat7]

I stuffed up my phone with a treble enabled rom and after several attempts flashing the stock RUU zip file, I resort to recovering thr phone through a nandroid backup using TWRP.

So does that mean my recovery attempt will fail too? Any way to make it work?

Unless you got rid of force encryption somehow, that won't work. TWRP can't read the internal storage, so creating and restoring a nandroid can't work. Which method did you try? This video is for the HTC 10, but the procedure didn't change and the method works flawless on the U11+ as well. Good luck.

 

[Siminica]

hi all

currently rooted with magisk (twrp installed) - got an update notification for 1.24.401.7 and I have some questions:
will it be enough to flash stoc recovery and take the update?
after the update magisk will still be in place and functional?

thank you

 

[DanteGR]

hi all

currently rooted with magisk (twrp installed) - got an update notification for 1.24.401.7 and I have some questions:
will it be enough to flash stoc recovery and take the update?
after the update magisk will still be in place and functional?

thank you

You also need the stock boot.img along with the stock recovery.

 

[Siminica]

You also need the stock boot.img along with the stock recovery.

will this https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md not be enough to do from magisk? (point 2 from prerequisites)

 

[DanteGR]

will this https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md not be enough to do from magisk? (point 2 from prerequisites)

This should be enough yes. What it does essentially is the same I stated above i.e. restore the stock boot.img.
Would you happen to know which of the methods stated after that (Devices with A/B partitions OR devices with Flashfire support) we have to use after that?

 

[Siminica]

This should be enough yes. What it does essentially is the same I stated above i.e. restore the stock boot.img.
Would you happen to know which of the methods stated after that (Devices with A/B partitions OR devices with Flashfire support) we have to use after that?

Haven't got that far yet
I remember I read somewhere that U11+ even if it got treble doesn't have A/B but only A partition - or maybe I didn't get it right
As for Flashfire - never tried it and don't know if even it's compatible
But what bothers me right now are posts #155 - #158 from this thread - seems even with stock recovery and stock boot.img OTA is not possible, but only with prior RUU flash

 

[DanteGR]

Haven't got that far yet
I remember I read somewhere that U11+ even if it got treble doesn't have A/B but only A partition - or maybe I didn't get it right
As for Flashfire - never tried it and don't know if even it's compatible
But what bothers me right now are posts #155 - #158 from this thread - seems even with stock recovery and stock boot.img OTA is not possible, but only with prior RUU flash

Yeah well if I finally decide to mess with root i'm not touching the recovery partition. I will use the patched boot.img method instead. It's such a shame that this wonderful device doesn't have proper developer support (and most probably will not have in the future either).

 

[Siminica]

Yeah well if I finally decide to mess with root i'm not touching the recovery partition. I will use the patched boot.img method instead. It's such a shame that this wonderful device doesn't have proper developer support (and most probably will not have in the future either).

I just read the FlashFire description in playstore - won't work for magisk patched boot images, only if magisk installed through twrp
So I guess I will first try to flash stock recovery and after that to recover boot in magisk and see if I get any luck with ota (A/B partition method)
If not, I will flash the RUU for current version and try to take ota even if after that I will not have a boot img to patch until someone publish the zip for ota
but this will take place later on in the evening when I get back from work

 

[TeHashX]

I want to boot into recovery or flash it only to backup boot.img, I will get data encrypted message when reboot to system? Firmware v1.24.401.7
Thanks

 

[Siminica]

Yeah well if I finally decide to mess with root i'm not touching the recovery partition. I will use the patched boot.img method instead. It's such a shame that this wonderful device doesn't have proper developer support (and most probably will not have in the future either).

Unfortunately I can confirm that flashing stock recovery and boot (latest through magisk uninstall option) did not allow me to take ota.

---------- Post added at 01:50 PM ---------- Previous post was at 01:45 PM ----------

I want to boot into recovery or flash it only to backup boot.img, I will get data encrypted message when reboot to system? Firmware v1.24.401.7
Thanks

there is a procedure in this thread or the cleanslate for u11+ thread describing how to set a pin before flash twrp in order to be sure the automatic decription is not possible - because the pin will be required and you will choose cancel
successfully used that on 1.24.400.2 flash twrp and then boot into twrp to flash cleanslate kernel

 

[Toxicology]

Unfortunately I can confirm that flashing stock recovery and boot (latest through magisk uninstall option) did not allow me to take ota.

---------- Post added at 01:50 PM ---------- Previous post was at 01:45 PM ----------


there is a procedure in this thread or the cleanslate for u11+ thread describing how to set a pin before flash twrp in order to be sure the automatic decription is not possible - because the pin will be required and you will choose cancel
successfully used that on 1.24.400.2 flash twrp and then boot into twrp to flash cleanslate kernel

So to be clear... I never flashed custom recovery and still have stock recovery from the beginning. I only flashed patched boot.img an rooted the device. Will I be able to take the OTA? Or do I have to use RUU and start from 0?

 

[Siminica]

So to be clear... I never flashed custom recovery and still have stock recovery from the beginning. I only flashed patched boot.img an rooted the device. Will I be able to take the OTA? Or do I have to use RUU and start from 0?

I am afraid the RUU is the answer but it's only my own experience with the process which makes me say that:
I had twrp installed but it could not interact with data as it was encrypted (and preserved like this), system was kept read only in twrp - I only flashed CleanSlate through twrp.
When I tried to revert I first flashed stock recovery, so my situation was: root with magisk by patched boot img, and CleanSlate kernel installed. From this point I tried to restore boot.img through magisk (uninstall magisk option - it said successfully restored) and after that to take ota. But the process stoped at 24% like described in posts #155 - #158 from this thread and after a while booted back to old state, with ota update available notification (at least no bootloop or other troubles)
And in this point I flashed the old RUU, took OTA and started all over in order to get boot.img to patch in magisk

 

[Toxicology]

I am afraid the RUU is the answer but it's only my own experience with the process which makes me say that:
I had twrp installed but it could not interact with data as it was encrypted (and preserved like this), system was kept read only in twrp - I only flashed CleanSlate through twrp.
When I tried to revert I first flashed stock recovery, so my situation was: root with magisk by patched boot img, and CleanSlate kernel installed. From this point I tried to restore boot.img through magisk (uninstall magisk option - it said successfully restored) and after that to take ota. But the process stoped at 24% like described in posts #155 - #158 from this thread and after a while booted back to old state, with ota update available notification (at least no bootloop or other troubles)
And in this point I flashed the old RUU, took OTA and started all over in order to get boot.img to patch in magisk

Do you think it's because you have custom kernel instead of stock? Guess restoring stock boot with magisk should give you stock kernel too... Or this is the problem. In another thread someone also had the 24 % Problem... While in the same thread someone else was able to take the Ota without RUU and without troubles.

 

[Siminica]

Do you think it's because you have custom kernel instead of stock? Guess restoring stock boot with magisk should give you stock kernel too... Or this is the problem. In another thread someone also had the 24 % Problem... While in the same thread someone else was able to take the Ota without RUU and without troubles.

I am not sure if stock boot means also stock kernel as I patched boot and running fine with stock kernel and also in CleanSlate it's stated you can flash kernel without root (so no need for magisk and patched boot).
But in the threads everybody talk about having stock recovery and stock boot prior to ota (some mention also RUU) and I never thought to try to flash stock kernel taken from RUU

 

[Toxicology]

I am not sure if stock boot means also stock kernel as I patched boot and running fine with stock kernel and also in CleanSlate it's stated you can flash kernel without root (so no need for magisk and patched boot).
But in the threads everybody talk about having stock recovery and stock boot prior to ota (some mention also RUU) and I never thought to try to flash stock kernel taken from RUU

Well, it was just an idea, for its maybe the only difference and maybe Ota also checks stock Kernel during flash.

Ok I'll give it a try... First restore stock boot via Magisk, then download Ota, save zip, install Ota, after reboot patching boot.img via Magisk should be the right order? Well, of course my device won't stop at 24 also!

 

[newyesor]

Fixing strategies OTA:
1.) To restore OTA function fast and easy: run a RUU.
2.) If there is no RUU for your specific model, you could convert to another model which has a RUU.
3.) Then there is a third, theoretical way I have not yet tested: obtain an untouched system image that fits your FullStock (same version), flash that in fastboot (it can be a raw dump or a TWRP systemimage backup of the correct system) and then flash the corresponding FullStock again. That should, like a RUU, restore OTA functionality too.
4.) Also very simple: grab the HTC OTA file which you find in /data/data/com.htc.updater somewhere if you can download. If not, find it on XDA from someone else who got it. Then put it on your sdcard, have stock recovery flash it from SDCard (no detailed guide here but its the same since years, there are tons of guides on how to manually flash a HTC OTA out there. Use Google).
5.) Remove boot.img from my FullStock zip before you flash. Your custom ROM of choice will put a hacked kernel into your phone again anyway...

However, at time of writing this, I know @nkk71 is investigating other, simpler methods to restore the correct state.