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.
[Unofficial] HTC U11+ TWRP Recovery
- Thread starter sabpprook
- Start date
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.
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.
@sabpprook 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
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.
----------
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:
Code:
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!
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......
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......
same here, it just reboot into a black screen
If we want root it seems that we have to install a custom recovery
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.
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!!!
Last edited:
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...
No offence guys, I'm just a casual visitor here, but
Shouldn't these questions go to Q&A and guides to General
That way people actually following development of
- 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
That way people actually following development of
[Unofficial] HTC U11+ TWRP Recovery
can stay focused on it.
Last edited:
No offence taken @nkk71. Apologies for derailing the thread.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
That way people actually following development of
[Unofficial] HTC U11+ TWRP Recoverycan stay focused on it.
No apologies, you are only very kind. May be he is right, may be not...even if I'm not a developer, testing the abilities of unofficial twrp at my own risk may help developers I think...anyway elsewhere in the unofficial twrp threads (see pixel 2 xl) there are a lot of question regarding magic flash. So if I may put this question...are you sure that flashing with twrp magisk_14_5.zip doesn't work and the only possibility is to patch the bot ing?
I'm not saying you shouldn't post here when you have relevant information regarding the current TWRP version, and feel free to post all over the place if you wish, but may I invite you to read:
Device Forum Rules (Please Read before posting)
I think the different forums are clearly explained in there.
As to why I asked to get back on topic is rather simple: You probably have noticed that the current TWRP build breaks your decryption key for the booted ROM.
Obviously this is a major problem, and something that is not easy to debug. So this thread is an ongoing work in progress, and as such should stay on topic.
Furthermore, I do not have this device, and doing *blind builds* is not something I nor the many of the other developers would usually do, but I am trying to help a bit, and I appreciate all the logs and relevant information people are posting.
However, I also have limited time, just like every other person, and having to read 3 or 4 pages of what I consider irrelevant information to the problem at hand, is a waste of time for me.
Understood, and I thank you a lot for your effort. I'll try by myself about magisk installation without bothering this thread with non-developer's questions. Let's hope in the future to see here the main (and more open minded) HTC developers
Seriously?
I really don't understand your problem, what's so difficult of looking in the General or Q&A forum on "How to root your device", and if there is no such thread you can create one.
You can even get people's attention by using mentions.
I never said anything about doing it by yourself
And thanks to your "compliment", I won't bother you folks anymore (so feel free to continue here), I have better things to do than waste my time with this.
Seriously?
I really don't understand your problem, what's so difficult of looking in the General or Q&A forum on "How to root your device", and if there is no such thread you can create one.
You can even get people's attention by using mentions.
I never said anything about doing it by yourself
And thanks to your "compliment", I won't bother you folks anymore (so feel free to continue here), I have better things to do than waste my time with this.
Me too...I am a 55 years old university professor and marketing consultant with the hobby of technology. Really I would like to close this discussion too and I really thank you for your effort. But please give me only the possibility to say that I'm almost sure that you're right but also that in other twrp threads the developers behaviour and friendliness is different. Dot and sorry again.
EDIT: anyway in the Q&A section of a so young device the probability to find somebody to exchange experiences and suggestions is asymptotic to 0.
Last edited:
@nkk71: forgive the newbie....Seriously?
I really don't understand your problem, what's so difficult of looking in the General or Q&A forum on "How to root your device", and if there is no such thread you can create one.
You can even get people's attention by using mentions.
I never said anything about doing it by yourself
And thanks to your "compliment", I won't bother you folks anymore (so feel free to continue here), I have better things to do than waste my time with this.
He does not know your contributions to XDA. Please don't let a single person's post determine your path. You are bigger than that man!
Top Liked Posts
-
There are no posts matching your filters.
-
25
It have been about 2 years, I finally get a U11 plus to make TWRP device tree with working decrypt function.
Source: https://github.com/sabpprook/android_device_htc_ocm
Please download latest TWRP build in following link.
[Android 8.0]
twrp-3.3.1-0-ocm_171001.img
twrp-3.3.1-0-ocm_171201.img
twrp-3.3.1-0-ocm_180601.img
twrp-3.3.1-0-ocm_180901.img
twrp-3.3.1-0-ocm_181001.img
twrp-3.3.1-0-ocm_181101.img
[Android 9.0]
PS. watch out the last 6 digits at the filename, it must equal to your system's android patch level. e.g. 2017-12-01 (Dec, 2017) = 171201, otherwise TWRP will not decrypt data partition.
PS2. U11+ already get Android Pie update, but this update will break data decrypt function in TWRP recovery.
@nkk71, thanks all the works you've done for us.9@kuchivas
It states in the op that this version of TWRP cannot decrypt /data
OP, as this is a trebble device, have you added support for backing up /vendor?
In order to modify system, fstab in /vendor would need to be modified to remove DM verity, the same applies to removing forced encryption8
@nkk71: forgive the newbie....Seriously?
I really don't understand your problem, what's so difficult of looking in the General or Q&A forum on "How to root your device", and if there is no such thread you can create one.
You can even get people's attention by using mentions.
I never said anything about doing it by yourself
And thanks to your "compliment", I won't bother you folks anymore (so feel free to continue here), I have better things to do than waste my time with this. He does not know your contributions to XDA. Please don't let a single person's post determine your path. You are bigger than that man!7
Seriously?
I really don't understand your problem, what's so difficult of looking in the General or Q&A forum on "How to root your device", and if there is no such thread you can create one.
You can even get people's attention by using mentions.
I never said anything about doing it by yourself
And thanks to your "compliment", I won't bother you folks anymore (so feel free to continue here), I have better things to do than waste my time with this.
New posts
-
-
[App][Beta] Stinger News - News and RSS feeds your way. [FREE] [NO ADS]
- Latest: Stephen.k.spear