[Unofficial] HTC U11+ TWRP Recovery

[Tumpster]

Anyone able to build a guide on how to unlock/root/TWRP this phone? Seems a bit tricky with all the information passed across multiple threads. Thanks all!

 

[Siminica]

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.

Hi,

2 - could be achieved without s-off? as no s-off is available for this device to my knowledge
3 - it seems to me twrp cannot work with internal because of encryption, so no backup / restore in twrp
4 - if ota is not installing from phone (with stock recovery) do you expect it to flash by booting in recovery? isn't what the phone will anyway do when installing from updates?

and the last remark - maybe you should check the profile of the person you mentioned

Best regards

---------- Post added at 04:31 PM ---------- Previous post was at 04:16 PM ----------

Anyone able to build a guide on how to unlock/root/TWRP this phone? Seems a bit tricky with all the information passed across multiple threads. Thanks all!

Hi,

1. Unlock - htcdev - you'll not find the exact device in list but U11 will do, the rest of the procedure is as described on site
2. Root - Magisk by patching boot img (procedure described in Magisk thread, also needed files are there to download) or by flashing in TWRP (with prior wiping and no reboot in between - because of force encryption - check in this thread)
3. TWRP - it doesn't really matter at this point because cannot decrypt - you flash it just to extract boot img for magisk or for flashing Magisk and to flash CleanSlate kernel if you'd want to (you can flash CleanSlate without root as it's not needed)

Best regards

 

[newyesor]

@Siminica
Hi,
This method above from xda HTC U11
2.s-off only,If you want make supercid.(s-off is not support on HTC U11+)
3.Now,twrp is can not back up data but you can restore backup stock rom from twrp.(obtain an untouched system image that fits your FullStock (same version)
4. OTAs, you HAVE to make sure you haven't modified /system (and /vendor if available) in anyway and it's stock recovery.

 

[The_Walking_Playground]

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.

Hi,

nkk71 passed away some months ago. There was an article on the portal.

TWP

 

[newyesor]

Hi,

nkk71 passed away some months ago. There was an article on the portal.

TWP

Yes,This method is come from on board xda htc u11.

 

[veeny101]

Do I need to backup anything before I do this?

 

[force70]

Do I need to backup anything before I do this?

You would be wise to back up before flashing anything, this included.

sent from my Pixel 2 XL or Note FE

 

[veeny101]

You would be wise to back up before flashing anything, this included.

sent from my Pixel 2 XL or Note FE

What do I need to backup if I want to return to stock for ota?

 

[rexx0520]

Is there any working workaround for decrypting data...?
Can't understand what "need to wipe userdata before reboot" means, if so isn't the decryption useless?
Thanks.

 

[force70]

What do I need to backup if I want to return to stock for ota?

Lol... whatever you dont want to lose of course.

sent from my Pixel 2 XL or Note FE

 

[newyesor]

What do I need to backup if I want to return to stock for ota?

You can flash Ruu for restore stock rom and receive ota.
Twrp is 'not backup your data.

 

[Cryptycat7]

Anyone able to build a guide on how to unlock/root/TWRP this phone? Seems a bit tricky with all the information passed across multiple threads. Thanks all!

Flashing magisk requires a decrypted partition. Kernel forces encryption, so we wipe data to get a decrypted partition for the short period of time to flash magisk. Once we reboot the storage is encrypted, but the phone is rooted. but also rooted. Hope this answers your question.

 

[The_Walking_Playground]

Flashing magisk requires a decrypted partition. Kernel forces encryption, so we wipe data to get a decrypted partition for the short period of time to flash magisk. Once we reboot the storage is encrypted, but the phone is rooted. but also rooted. Hope this answers your question.

Hi,

Flashing Magisk does not require a decrypted partition. Magisk will patch the kernel so that forced encryption is disabled, but only if the device is either already unencrypted, or that option is included at flash time.

TWP

 

[Cryptycat7]

Hi,

Flashing Magisk does not require a decrypted partition. Magisk will patch the kernel so that forced encryption is disabled, but only if the device is either already unencrypted, or that option is included at flash time.

TWP

Yes. You are right. I wasn't precise, but who would disable force encryption unless you want to tinker with multi ROM and stuff.

 

[The_Walking_Playground]

Yes. You are right. I wasn't precise, but who would disable force encryption unless you want to tinker with multi ROM and stuff.

Hi,

Well, since TWRP can't safely decrypt this device, running unencrypted would allow a user to freely root and flash a custom kernel without the need of setting a PIN on boot and cancelling the prompt in TWRP, etc. In other words, it would be a simpler user experience for anyone that wants to try out anything custom, including the Treble ROMs. I don't believe MultiROM is an option on this device, is it?

TWP

 

[Cryptycat7]

Hi,

Well, since TWRP can't safely decrypt this device, running unencrypted would allow a user to freely root and flash a custom kernel without the need of setting a PIN on boot and cancelling the prompt in TWRP, etc. In other words, it would be a simpler user experience for anyone that wants to try out anything custom, including the Treble ROMs. I don't believe MultiROM is an option on this device, is it?

TWP

With disabled force encryption it would be something that could be done.
no-kexec hard boot patch is the masterpiece developed by XDA Recognized Developer @nkk71, he is leaving a big gap. R.I.P.

 

[The_Walking_Playground]

With disabled force encryption it would be something that could be done.
no-kexec hard boot patch is the masterpiece developed by XDA Recognized Developer @nkk71, he is leaving a big gap. R.I.P.

Hi,

Forced encryption doesn't prevent MultiROM from working - it works on both the HTC 10 and the U11, and both force encryption. So that was never an obstacle to it being developed. But yes, he will be greatly missed .

TWP

 

[Cryptycat7]

Hi,

Forced encryption doesn't prevent MultiROM from working - it works on both the HTC 10 and the U11, and both force encryption. So that was never an obstacle to it being developed. But yes, he will be greatly missed .

TWP

Good morning from MEZ
Forced encryption doesn't prevent MultiROM from working, but it requires a decrypted data partition to work. So if the force encrypt flag is set to 1, storage will be encrypted on reboot; resulting in a bricked phone (worse case). You can use Magisk to prevent force encryption, but I wouldn't rely on it, since it isn't developed with multiboot in mind. Every patch you add to this frigale boot process must be longtime tested, before I'd recommend anyone trying it.

 

[The_Walking_Playground]

Good morning from MEZ
Forced encryption doesn't prevent MultiROM from working, but it requires a decrypted data partition to work. So if the force encrypt flag is set to 1, storage will be encrypted on reboot; resulting in a bricked phone (worse case). You can use Magisk to prevent force encryption, but I wouldn't rely on it, since it isn't developed with multiboot in mind. Every patch you add to this frigale boot process must be longtime tested, before I'd recommend anyone trying it.

Hi,

You're right; even though TWRP and MultiROM can decrypt the device, Android stills needs to be able to for the primary ROM to boot, which on this device, is problematic. It wouldn't be a problem to run secondary ROMs while encrypted, though. You'd just never be able to boot back into the primary ROM without formatting data, which would effectively wipe out MultiROM. So the only safe way to run is just to go unencrypted, as I mentioned before.

TWP

 

[digio1996]

I have a question about Magisk, i know that is a little bit OT but maybe someone can help me very quick: I can't find the OTA file of the latest HK update (1.24.400.3) but i would like to root it. Does the boot.img change for every update or can i try to use the previous boot.img to patch it through Magisk? Any other solution? If not, i will install and root through TWRP :/