[Unofficial] HTC U11+ TWRP Recovery

lyfkevin

lyfkevin

Senior Member
Sep 27, 2010
381
352
0
Dec 14, 2017 at 2:59 AM
nkk71 said:
.
Click to expand...
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
 

Attachments

  • Like
Reactions: goodman_east
nkk71

nkk71

Inactive Recognized Developer / Inactive Recognize
May 26, 2010
8,743
7,570
0
49
Beirut
Dec 14, 2017 at 10:49 AM
lyfkevin said:
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
Click to expand...
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://forum.xda-developers.com/showpost.php?p=74836915&postcount=80
 
  • Like
Reactions: goodman_east
D

digio1996

Member
Sep 9, 2016
14
3
0
Dec 15, 2017 at 10:30 PM
devsk said:
I haven't seen an official RUU for U11+. Has anybody?
Click to expand...
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?
 
goodman_east

goodman_east

Senior Member
Jan 13, 2013
258
94
0
Amoy
Dec 15, 2017 at 11:30 PM
digio1996 said:
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?
Click to expand...
It is a RUU of HTC U11, not for U11 plus.
Maybe U will need this: https://androidfilehost.com/?w=search&s=ocean_M
 
goodman_east

goodman_east

Senior Member
Jan 13, 2013
258
94
0
Amoy
Dec 16, 2017 at 6:47 AM
nkk71 said:
^^ 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:
  1. Normally booting ROM
  2. Set a PIN on boot
  3. Reboot normally and make sure PIN works properly
  4. Reboot to TWRP
  5. It will ask for a password -> CANCEL the prompt! do not let it decrypt
  6. 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
Code: 
adb shell mount
in booted ROM and it should give some info.
Click to expand...
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.
 
Last edited:
  • Like
Reactions: nkk71
nkk71

nkk71

Inactive Recognized Developer / Inactive Recognize
May 26, 2010
8,743
7,570
0
49
Beirut
Dec 16, 2017 at 11:40 AM
goodman_east said:
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 mu new PIN, and can boot to system.
Click to expand...
Thanks for the feedback, a couple more tests please (you'll need to be connected to the PC for the second test):

  1. Boot ROM, make sure PIN works
  2. Reboot to TWRP
  3. Enter a wrong PIN and let decryption fail
  4. Reboot ROM, check if PIN still works

If it still works
  1. Reboot to TWRP
  2. While TWRP is waiting at the decryption screen, open an adb shell:
    Code: 
    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

    Code: 
    ~ # [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)
    Code: 
    ~ # [B][COLOR="blue"]date[/COLOR][/B]
Sat Dec 16 13:28:10 GMT 2017
    ^^ okay date and time are now correct
    .
  3. Enter correct PIN, and let TWRP decrypt
  4. 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 :eek:
 
  • Like
Reactions: goodman_east
goodman_east

goodman_east

Senior Member
Jan 13, 2013
258
94
0
Amoy
Dec 16, 2017 at 11:42 AM
nkk71 said:
Thanks for the feedback, a couple more tests please (you'll need to be connected to the PC for the second test):

  1. Boot ROM, make sure PIN works
  2. Reboot to TWRP
  3. Enter a wrong PIN and let decryption fail
  4. Reboot ROM, check if PIN still works

If it still works
  1. Reboot to TWRP
  2. While TWRP is waiting at the decryption screen, open an adb shell:
    Code: 
    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

    Code: 
    ~ # [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)
    Code: 
    ~ # [B][COLOR="blue"]date[/COLOR][/B]
Sat Dec 16 13:28:10 GMT 2017
    ^^ okay date and time are now correct
    .
  3. Enter correct PIN, and let TWRP decrypt
  4. 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 :eek:
Click to expand...
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.
 

Attachments

Last edited:
nkk71

nkk71

Inactive Recognized Developer / Inactive Recognize
May 26, 2010
8,743
7,570
0
49
Beirut
Dec 16, 2017 at 12:06 PM
goodman_east said:
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.
Click to expand...
Can you try the second method (setting the date and time correctly, before trying any decryption).
 
  • Like
Reactions: goodman_east
goodman_east

goodman_east

Senior Member
Jan 13, 2013
258
94
0
Amoy
Dec 16, 2017 at 12:09 PM
nkk71 said:
Can you try the second method (setting the date and time correctly, before trying any decryption).
Click to expand...
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,
Code: 
D:\adb>adb shell
~ # [6ndate
date
Thu Feb  5 12:12:25 GMT 1970
4 change date and time
Code: 
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.
 
Last edited:
  • Like
Reactions: nkk71
goodman_east

goodman_east

Senior Member
Jan 13, 2013
258
94
0
Amoy
Dec 16, 2017 at 12:44 PM
nkk71 said:
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.
Click to expand...
Test one more time and still my PIN was not accepted.

Code: 
D:\adb>adb shell
~ # date
date
Thu Feb  5 12:28:33 GMT 1970
~ # date 121620382017
date 121620382017
Sat Dec 16 20:38:00 GMT 2017
~ # date
date
Sat Dec 16 20:38:04 GMT 2017
~ # 
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.
 
nkk71

nkk71

Inactive Recognized Developer / Inactive Recognize
May 26, 2010
8,743
7,570
0
49
Beirut
Dec 16, 2017 at 12:56 PM
goodman_east said:
Test one more time and still my PIN was not accepted.

Thank U very much for helping us to build TWRPs.
Click to expand...
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
Code: 
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
Code: 
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
Code: 
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
 
  • Like
Reactions: goodman_east
goodman_east

goodman_east

Senior Member
Jan 13, 2013
258
94
0
Amoy
Dec 16, 2017 at 1:25 PM
nkk71 said:
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
Code: 
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
Code: 
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
Code: 
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
Click to expand...
misc_0 and misc_1 are the same.
extra changed after data decryption
View attachment dd.zip

Edit1: restore extra_0 to extra partition.
Code: 
~ # dd 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
~ # reboot
reboot
My PIN cannot be accepted

Boot to TWRP without decryption, dd extra
Code: 
D:\adb>adb shell
~ # dd 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
~ # exit
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
 
Last edited:
goodman_east

goodman_east

Senior Member
Jan 13, 2013
258
94
0
Amoy
Dec 16, 2017 at 1:47 PM
nkk71 said:
well try restoring extra to it's original _0 one and see if it works.
Click to expand...
I test something as following:
1 Boot to TWRP with decryption, restore extra_0, and reboot to bootloader

Code: 
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

Code: 
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
Code: 
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
 
Last edited:
You must log in or register to reply here.

New posts

Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone