yashsingh1/xdaforums huggingface dataset:
[Android] MrGreg1:
OK I get it. Please understand that I am new to this stuff. I am an IT guy for over 30 years but have never taken the time to learn about modding Android devices. I am only a little over a week into this effort. So thanks for being patient with me. This is why I am working on an older phone. If I hard brick it, then I do not have allot to loose.

The reason for this effort is that I am trying to achieve s-off on this phone. I have tried firewater, rumrunner, and even sunshine tells me my device is not currently supported.

I made a mistake early on. I updated to 2.15.502.1 via the RUU. This was before I even learned what s-off was and the power it comes with. The update process updated hboot from 1.40 to 1.73. I suspect that s-off may be achievable with hboot 1.40 but I am not sure of this. I been trying to downgrade ever since to no avail. As you know, and I learned the hard way, downgrading is only achievable with s-off.

I had the idea to try and work around this problem. I thought why not use the android-info.txt file from 2.15.502.1 with the 1.19.502.1 firmware. Then repackage and flash. However, you have just taught me that this would not work. The zip file would not be digitally signed with HTC's private key. Sigh....

So it looks like the only way I will ever get s-off is with this device. I am not even sure if this will work either. I have a question into the support team asking them. Here is the link...

http://www.micro-box.com/catalog/products/htc-pro-cable-2-edition-2016.html

I almost forgot. I notice that for 2.15.502.1 the romzip zip folder contains the 1.73 hboot image file. Just wondering if it was your intention to leave that there or it was missed in the cleanup process.

Thanks again for your hard work and support.
[Android] Captain_Throwback:
What you're asking about is off-topic for this thread. Go ask this on Q&A in your device forum. As for downgrading hboot, you might want to try this, if you're brave enough.

P.S. I can attest to the fact that the tool I linked can successfully downgrade the hboot on the EVO LTE - that's the only relevant device I had to use it on.
[Android] nkk71:
I believe the above post answers your S-OFF question.

In addition, just to add: if it was easy to sign firmwares / RUUs / and achieve s-off, then it would already have been posted and shared long before I ever started tinkering with phones ;)

It contains both the hboot as well as the *minor* / *preupdate* zip, and they were left there on purpose. After all the purpose of the tool is to provide as many files and information that is extracted from the RUU.

What you then decide to do with the files and information is entirely up to you :)
[Android] beaups:
Why go to all of the work of buying some random box. Just use sunshine?

--beaups
[Android] nkk71:
Didn't know sunshine works on the One X / One X+ especially since that's still running 4.1
[Android] mariosaraylian:
Final Firmware Output After Extraction

Captain_Throwback:

We chatted on IRC about this vaguely in the #TWRP channel the other day. You had mentioned to me that "To prevent wiping data, you need to remove all dzdata* files (and maybe something else)".

I removed the dzdata* files. What were the other files to remove in the extraction of the Firmware? If I compare this to the last FUU for the M8, and compare the files that are removed, do you think I'll be in good shape to try and flash it on this Desire 530?

There's about 10 other files that aren't in the M8 FUU, and I noticed there isn't a sensor_hub.img file etc...Does any of this matter or apply?

I wanted to run this by you before I flash it and risk bricking it....

Attached is my Decrypt Log.

Thanks for your help!

M
[Android] Captain_Throwback:
You didn't have that conversation with me...and I don't see how it's relevant to the tool. Every device uses different firmware, so the RUU would only contain what is relevant to the device it's for. I wouldn't worry about "missing" images that are there for one device and not another. They're probably based on different SoCs and came out at different times, so that's expected.

EDIT: [MENTION=2256702]Zanzibar[/MENTION]
[Android] mariosaraylian:
Captain_Throwback:

I apologize! That was Zanzibar I was having that chat with about the RUU Extractor. You and I were briefly chatting about the M10 and PayPal Credit LOL!
[Android] nkk71:
Hmm -_-
[Android] mariosaraylian:
[MENTION=2605798]nkk71[/MENTION]: Shou sar??
[Android] nkk71:
Nothing actually, I was looking at your log on my phone, and saw a bug... Turns out it wasn't your log at all but some old log I had on my phone.

So all good
[Android] metropical:
help - what I do wrong? Running HTC_RUU_Decrypt_Tool_3.0.8-MACOSX

RUU identified as Executable file

Extracting rom.zip from RUU_M7_7.18.531.35.exe

ERROR: something went wrong with exec() (errno=2 'No such file or directory')!

offending execvp: 'unruu' 'unruu' '/Volumes/OWC MiniStack/HTC M7/HTC_RUU_Decrypt_Tool_3.0.8-MACOSX/RUU_M7_7.18.531.35.exe'

ERROR: UnRUU failed

Removing unneeded work folders

Finished: Tool has finished but there was an error, please

check the console output and your OUT folder

'/Volumes/OWC MiniStack/HTC M7/HTC_RUU_Decrypt_Tool_3.0.8-MACOSX/OUT'

ERROR: UnRUU failed

Removing unneeded work folders

Finished: Tool has finished but there was an error, please

check the console output and your OUT folder

'/Volumes/OWC MiniStack/HTC M7/HTC_RUU_Decrypt_Tool_3.0.8-MACOSX/OUT'

Another attempt

RUU identified as Executable file

Extracting rom.zip from RUU_M7_7.18.531.35.exe

ERROR: something went wrong with exec() (errno=2 'No such file or directory')! see bottom of message

offending execvp: 'unruu' 'unruu' '/Volumes/OWC_MiniStack/HTC_M7/HTC_RUU_Decrypt_Tool_3.0.8-MACOSX/RUU_M7_7.18.531.35.exe'

ERROR: UnRUU failed

Removing unneeded work folders

Finished: Tool has finished but there was an error, please

check the console output and your OUT folder

'/Volumes/OWC_MiniStack/HTC_M7/HTC_RUU_Decrypt_Tool_3.0.8-MACOSX/OUT'

ERROR: UnRUU failed

Removing unneeded work folders

Finished: Tool has finished but there was an error, please

check the console output and your OUT folder

'/Volumes/OWC_MiniStack/HTC_M7/HTC_RUU_Decrypt_Tool_3.0.8-MACOSX/OUT'

/Volumes/OWC_MiniStack/HTC_M7/HTC_RUU_Decrypt_Tool_3.0.8-MACOSX

-bash: /Volumes/OWC_MiniStack/HTC_M7/HTC_RUU_Decrypt_Tool_3.0.8-MACOSX: is a directory
[Android] nkk71:
You want to get rid of the ones striked out ones: (and the italic ones are mentioned later)

inflating: E:/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/android-info.txt
[STRIKE] inflating: E:/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/apppreload.img[/STRIKE]
inflating: E:/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/aboot_signed.img
inflating: E:/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/cota.img
inflating: E:/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/gpt_main_8g.img
inflating: E:/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/gpt_main_16g.img
inflating: E:/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/partition_info
[STRIKE] inflating: E:/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/android-info2.txt [/STRIKE]
inflating: E:/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/sbl1-8909-1.img
inflating: E:/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/hosd_signed.img
inflating: E:/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/rpm-8909-1.img
[B][I] inflating: E:/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/boot_signed.img
inflating: E:/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/recovery_signed.img
[/I][/B] inflating: E:/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/wcnss.img
inflating: E:/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/radio.img
inflating: E:/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/rcdata.img
inflating: E:/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/rfg_3.img
inflating: E:/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/modem_st1.img
inflating: E:/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/modem_st2.img
inflating: E:/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/tz-8909-1.img
inflating: E:/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/cmnlib32.img
inflating: E:/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/keymaster.img
inflating: E:/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/pg2fs_ship_signkey.img
inflating: E:/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/tp_HMX852XE.img
[I] inflating: E:/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/splash1.nb0 [/I]
[STRIKE] inflating: E:/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/backup_android-info.txt [/STRIKE]

[STRIKE] inflating: E:/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/dzdata_8g.hdr
inflating: E:/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/dzdata_8g.img
inflating: E:/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/dzdata_16g.hdr
inflating: E:/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/dzdata_16g.img
[/STRIKE]

You may also want to get rid of stock boot.img and stock recovery:

[STRIKE] inflating: E:/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/boot_signed.img
inflating: E:/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/recovery_signed.img
[/STRIKE]

Duno if you care about bootsplash:

inflating: E:/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/splash1.nb0

And finally, you'll have to check the android-info.txt, especially if you're encrypted, it may have certain wipe you don't want (eg extra partition)
[Android] nkk71:
Looks like your folder structure may not be correct.

[MENTION=4470081]topjohnwu[/MENTION]
[Android] metropical:
here's my folder structure. would you please tell me what needs to be done?

There was nothing in the Console that I could ascertain and the OUT folder was empty.
[Android] nkk71:
The only Mac at my disposal is my wife's and I'm not messing with that one, so use 3.6.5 on Windows or Linux :)
[Android] metropical:
oh you quitter! nudge, nudge, wink, wink.

I'll try on BootCamp.

I can barely figure usage of the Tool in OSX, windows, worse. Can't figure how to even launch the Tool.
[Android] nkk71:
I would rather you check your attitude at the door, if you don't mind.

Then perhaps this isn't meant for you, the OP is quite clear about *usage*, as is the tool. (Perhaps not foolproof,

it was never meant to be

, but it does get the job done).
[Android] metropical:
"I would rather you check your attitude at the door, if you don't mind."

No, I don't mind. nudge, nudge, wink, wink is a well known joke. Sorry if it doesn't translate .

"Then perhaps this isn't meant for you, the OP is quite clear about *usage*, as is the tool. "

mmmmm, perhaps for someone well experienced with the concepts.

But a support community is supposed to be just that.

as you have been in the past.

But experience is not foolproof either.

sorry to have bugged you.
[Android] nkk71:
I don't mind the question, and i have no issues with you *winking* or *hinting*. Though I do consider them inappropriate in here.

Yes, even with my very bad memory, I do remember you from the M7 days... yeah long time ago. good times too.

I've already mentioned [MENTION=4470081]topjohnwu[/MENTION] to fix his MacOS port, so you'll need to wait for Mr.Magisk to see if has time for you :p , I never supported macOS anyway.
[Android] metropical:
yes, wish I never got hoodwinked into my current G4. Though it works well (after a factory "refurbish"), it's nowhere near the build of the M7 or the stability.

Very tempted to get a U11, just concerned if HTC will survive the current thinning of the herd.

And the difficulty in try to see and touch a U11.

Hopefully topjohnwu will have time. Like to have my back-up phone as current as possible.

It is annoying that I can't seem to get the conventional old school RUU method to work either.

Perhaps I'll search my notes and see what I did to get to 7.18.531.2.

I think I stepped back some and then took OTAs.
[Android] JochenP:
my platform: win7 64

Decrypt Tool 3.6.5

RUU: _OCEAN_DUGL_N71_SENSE90GP_HTC_Europe_1.27.401.5

thanks for your genious work,

i have problem by using argument -z: DecryptTool error is: invalid zipfile and is skipping extracting system files and firmware (firmware folder contents only txt-info-files).

With argument -s or/and -f all is running perfect and i get system- and firmwarefiles.

Please have a look - thanks
[Android] nkk71:
Next time please attach the log.

But if you mean running the tool only with the -z option then yes, no system nor firmware files will be extracted. The flags are *cumulative*, for example:

-sfz -> system.img + firmware files + sdcard ZIP
-sf -> system.img + firmware files
-s -> system.img
-sz -> system.img + sdcard ZIP
-z -> sdcard ZIP
-zf -> sdcard ZIP + firmware files
[Android] metropical:
finally figured out the W7 method. It failed, but here's the log.

I checked debugging boxes, but if you need to see them to help, please send me the path.

Thanks.

+++ Welcome to the HTC RUU Decryption Tool 3.6.5 +++

RUU identified as Executable file

Please enter your choices

* Create a logfile [Y/n]: y

* Extract system.img and boot.img [Y/n]: y

* Extract the firmware files [Y/n]: y

* Create an sd-card flashable zip [y/N]: y

* Do you wish to check for new keyfiles [Y/n]: y

* If a new keyfile is generated, do you wish to upload it [Y/n]: y

* Enable debugging options [y/N]: y

* Print Debug Info [y/N]: y

* Do a 'slow cleanup' [y/N]: n

* Keep all intermediary files [y/N]: n

DBG full_path_to_maindir='C:/Users/buzz/Downloads'

DBG full_path_to_keys='C:/Users/buzz/Downloads/keyfiles'

DBG full_path_to_bins'/Downloads/bin'

DBG full_path_to_wrk'C:/Users/buzz/Downloads/OUT'

DBG full_path_to_ruu_file='C:/Users/buzz/Downloads/RUU.exe'

DBG full_path_to_hb_file=''

DBG PATH='/cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbem:/cygdrive/c/Windows/System32/Windo

Downloading keyfiles...

DBG about to execvp (run system program): 'keyfile_updater'

DBG 'keyfile_updater'

DBG '--download-new'

[0;31mERROR: something went wrong with exec() (errno=9 'Bad file descriptor')![0m

offending execvp: 'keyfile_updater'

'keyfile_updater'

Download_Keyfiles took 0.024 seconds.

Disabling keyfile upload due to failed download.

Extracting rom.zip from RUU.exe

DBG about to execvp (run system program): 'unruu'

DBG 'unruu'

DBG 'C:/Users/buzz/Downloads/RUU.exe'

[0;31mERROR: something went wrong with exec() (errno=9 'Bad file descriptor')![0m

offending execvp: 'unruu'

'unruu'

ERROR: UnRUU failed

ERROR: UnRUU failed to produce either rom.zip or rom_01.zip+rom_02.zip aborting!

UnRUU took 0.018 seconds.

Removing unneeded work folders

Overall process completion time: 0.077 seconds.

Finished: Tool has finished but there was an error, please

check the console output and your OUT folder

Writing logfile to: C:/Users/buzz/Downloads/OUT/RUU_Decrypt_LOG-__2017-09-18_113543.txt
[Android] nkk71:
No idea what you're doing wrong, but anyway 72mins download time, 3 mins decryption time, tell me what you need:

C:\Users\BLARP\Downloads\--(IDM_Downloads)--\Programs\OUT_PN07_7.18.531.35>dir /s /n
Volume in drive C is Windows
Volume Serial Number is 68F9-92CE

Directory of C:\Users\BLARP\Downloads\--(IDM_Downloads)--\Programs\OUT_PN07_7.18.531.35

18/09/2017 20:27 <DIR> .
18/09/2017 20:27 <DIR> ..
18/09/2017 20:27 <DIR> firmware
18/09/2017 20:25 1,615,572,958 PN07IMG.zip
18/09/2017 20:27 <DIR> romzip
18/09/2017 20:30 29,331 RUU_Decrypt_LOG-PN0713000_7.18.531.35_2017-09-18_202744.txt
18/09/2017 20:27 <DIR> system
2 File(s) 1,615,602,289 bytes

Directory of C:\Users\BLARP\Downloads\--(IDM_Downloads)--\Programs\OUT_PN07_7.18.531.35\firmware

18/09/2017 20:27 <DIR> .
18/09/2017 20:27 <DIR> ..
18/08/2015 22:53 6,972,416 adsp.img
18/08/2015 23:09 160 android-info-1.txt
18/08/2015 23:10 160 android-info-2.txt
18/08/2015 23:10 160 android-info-3.txt
18/08/2015 22:47 104 android-info.txt
18/08/2015 23:06 7,194,880 boot_signed.img
18/08/2015 22:53 9,475 cir.img
18/08/2015 22:57 14,704 dzdata_16g.hdr
18/08/2015 22:57 167,481,200 dzdata_16g.img
18/08/2015 22:57 21,360 dzdata_32g.hdr
18/08/2015 22:57 167,744,368 dzdata_32g.img
18/08/2015 22:58 25,152 dzdata_64g.hdr
18/08/2015 22:58 167,981,632 dzdata_64g.img
18/08/2015 23:06 2,096,384 hboot_signedbyaa.img
18/08/2015 22:53 4,188,160 pg2fs_spcustom.img
18/08/2015 22:45 72,522,240 radio.img
18/08/2015 22:58 1,125,583 ramdisk.img
04/08/2015 10:52 149 rcdata.img
18/08/2015 23:06 13,172,992 recovery_signed.img
18/08/2015 22:53 144,296 rpm.img
18/08/2015 22:53 108,158 sbl1-1.img
18/08/2015 22:53 108,158 sbl1-2.img
18/08/2015 22:53 108,158 sbl1-3.img
18/08/2015 22:53 108,158 sbl1-4.img
18/08/2015 22:53 108,158 sbl1-5.img
18/08/2015 22:53 127,746 sbl2.img
18/08/2015 22:53 321,382 sbl3.img
02/02/2015 13:27 4,194,304 splash1.nb0
18/08/2015 22:53 32,782 tp_HMX852XD.img
18/08/2015 22:53 47,388 tp_SYN3202.img
18/08/2015 22:53 543,122 tz.img
31 File(s) 616,503,089 bytes

Directory of C:\Users\BLARP\Downloads\--(IDM_Downloads)--\Programs\OUT_PN07_7.18.531.35\romzip

18/09/2017 20:27 <DIR> .
18/09/2017 20:27 <DIR> ..
18/09/2017 20:25 104 android-info.txt
1 File(s) 104 bytes

Directory of C:\Users\BLARP\Downloads\--(IDM_Downloads)--\Programs\OUT_PN07_7.18.531.35\system

18/09/2017 20:27 <DIR> .
18/09/2017 20:27 <DIR> ..
18/09/2017 20:27 7,194,880 boot.img
18/09/2017 20:27 1,879,048,192 system.img
2 File(s) 1,886,243,072 bytes

Total Files Listed:
36 File(s) 4,118,348,554 bytes
11 Dir(s) 23,373,524,992 bytes free

Note that my upload speed is even worse than my download speed, so it will take time.
[Android] metropical:
very generous, but that'd be 3-4 hours of your time.

Let's try this or perhaps someone else will volunteer that will take less of their time.

Below are snaps from my W7 on Bootcamp side.

Perhaps they provide some clues?
[Android] nkk71:
I really have no idea what's going on there, I can assure you I've tested linux64 (live-usb and full), as well as windows32/64 (again one in a box another one not), and the last run was on my active laptop (Win10x64 using the 32bit decrypt version), so I really don't know what's going.

I can leave whatever file you want on dropbox, and let it sync overnight, better than nothing I guess
[Android] Black-FR:
You have a link, for the RUU, which you need to be decrypt?

Then I do it on my PC and upload it for you.

Might be slightly faster. ;)
[Android] Captain_Throwback:
Those aren't errors - that's keyfinder doing its job...:rolleyes: Nowhere does it say "error" does it?

P.S. Please just attach the log next time. Hide tags don't work in XDA Labs and I have to scroll through all of that...
[Android] nkk71:
You're looking at this the wrong way, look at the end of keyfinder output:

Testing keyfile '2PZC_keyfile_1.03.651.7.bin'...
ruuveal
-------

Processing ZIP... 32768/112601640Decrypted RUU (zip) written to: tmpzip.zip
Archive: tmpzip.zip
....
testing: android-info.txt OK
....
[B]No errors detected in compressed data of tmpzip.zip.[/B]
[B]INFO: keyfile passed all tests[/B]
[B]Finished: Successfully found decryption key, copied to 'tmp/use_keyfile.bin'[/B]
KeyFinder took 13.446 seconds.

It's looking for a proper key, so yeah, you'll got a few failures finding it, it's the end result that matters.
[Android] metropical:
thanks. http://www.htc.com/us/support/htc-one-t-mobile/news/ at the bottom of the page.

7.18.531.35 for T-Mo US.

I'm sure it's well tested, but perhaps my lack of PC awareness is the issue ....... or bootcamp.

appreciate the help from both of you. Dropbox is fine if that works.

I'm thinking just the RUU.zip and running this:

zip in fastboot folder in computer

Command fastboot oem rebootRUU

fastboot flash zip xxxxx.zip

fastboot flash zip xxxxx.zip

fastboot reboot oem

unless there is a reason I need the other bits ..........?

and, BTW, how do you like the U11. I was thinking of it and retiring my aggravation with the G4.

The M7 is my old phone that I use for back up. It was a very reliable beast.
[Android] nkk71:
It will be here https://www.dropbox.com/s/5nrmkneyrwyzlku/PN07IMG.zip?dl=0

ONCE IT ACTUALLY UPLOADS!! (dropbox says 4 hours, I personally would not hold my breath)

sha1sum: d0d4a81712b7f4870d0ed1add43d6e7951bb3a26 PN07IMG.zip

once it's uploaded, i'll keep it there for a couple of days, then delete it, so once it's up, please mirror it.
[Android] metropical:
Thanks Very.

I'll look later or tmrw. Not to be a total idiot, I assume you mean mirror from my Drop? Or ............?
[Android] mariosaraylian:
nkk71:

THANK YOU for the detailed reply!!!!!!!!!!!!!!!!!

I will try it and post how it works out!

Merci Kteer........!
[Android] metropical:
seems to still be on the upload. maybe it's stuck? I think it's been about 12 hours.
[Android] nkk71:
don't know when it finished, but looks uploaded to me.
[Android] metropical:
Yea, looks good now. Get it when I'm home from work. Thanks very nkk71.
[Android] Petarg:
Can somebody please link me RUU.exe file for HTC U11 Europe 1.27.401.5?
[Android] Captain_Throwback:
Wrong thread. This isn't an RUU request thread. Go look/post in your device forum.
[Android] mariosaraylian:
nkk71:

Pardon this stupid question: You had mentioned in your previous detailed post to me (Thank You AGAIN!):

"And finally, you'll have to check the android-info.txt, especially if you're encrypted, it may have certain wipe you don't want (eg extra partition)"

In my "android-info.txt" file there are several entries which are contain "eraseonflash <target>". Do I want to delete these entries entirely from the .txt file (only because they say "erase on flash, erase on partition, erase on soff.....etc.....?)

modelid: 2PST20000

cidnum: T-MOB010

mainver: 1.36.531.14

btype:1

aareport:1

hbootpreupdate:1

nohardreset: 1

resparseoption: -S150M

eraseonflash: system

eraseonflash: userdata

eraseonflash: aboot

eraseonflash: boot

eraseonflash: hosd

eraseonflash: radio

eraseonflash: recovery

eraseonflash: rpm

eraseonflash: sbl1

eraseonflash: tz

eraseonflash: sp1

eraseonflash: cmnlib32

eraseonflash: keymaster

eraseonflash: cota

eraseonsoff: frp

erasepartition: cache

erasepartition: extra

erasepartition: ssd

eraseonsoff: carrier

rompack: v2

ASN1DERencoding: on
[Android] xunholyx:
Download a no wipe firmware from someone else, and diff the android-info text with yours. Use Beyond Compare or something like that. Then you'll know what entries should be deleted.
[Android] metropical:
got it done. Took some trial and error in BC/W7 as I'm not that swift with it.

But updated and wrote a guide for others .

Android File host RUU.zip posted.
[Android] xchang168:
OK,thanks
[Android] santod040:
HTC U11+

[MENTION=2605798]nkk71[/MENTION]

Just wanted to confirm that the Tool is still working great moving forward to HTC U11+ (Ocean Master).

I have successfully decrypted an RUU from two HTC U11+ models from different regions, using each aboot for retrieving the keyfile.

So in short, I just want to say thanks once again for all the dedication and effort you've put into this priceless utility. :good:
[Android] nkk71:
Thanks, glad to hear it :)

Hope you're letting the tool upload the new keyfiles :D
[Android] santod040:
Of course! :good:
[Android] nkk71:
Thanks :)

Last time I checked (22nd July) we had 40 keyfiles, as of today we're at 45 :good:
[Android] michielc:
Thank you for the tool ! Is it possible to repack the extracted files after making modifications in the firmware folder ?
[Android] nkk71:
Not currently, but even if it were (or will be), then it would only be useful for S-OFF devices.
[Android] ziand:
I had a failure with uploading keyfile 2Q4D_keyfile_1.01.709.3.bin : View attachment 2Q4D_keyfile_1.01.709.3.zip

d:\Program Files\HTC_RUU_Decrypt_Tool>RUU_Decrypt_Tool.exe --sync-keyfiles

+++ Welcome to the HTC RUU Decryption Tool 3.6.5 +++

Synchronizing keyfiles...

1) Downloading keyfiles...

Connecting...

Found 46 keyfiles

Your keyfiles are up to date.

2) Uploading keyfiles...

Connecting...

................

................

..........

Uploading '2Q4D_keyfile_1.01.709.3.bin'...upload error 19 (FTP: couldn't retrieve (RETR failed) the specified file)!

....

Transfer error!

d:\Program Files\HTC_RUU_Decrypt_Tool>

It works properly with RUU_1.01.709.3.zip and RUU_1.05.709.12.zip for htc_ocmdugl HTC U11+