Database Info

Unlocked/Developer Stock RUU 2.18.617.1 - HTC One A9

The link to RUU2.18.617.1 is now available.
Stock RUU 2.18.617.1
due to the change of encryption key, firmware_2.18.617.1 need to flash.
you can find the firmware.zip in OTA files.
link to OTA2.18.617.1

goodman_east said:
The link to RUU2.18.617.1 is now available.
Stock RUU 2.18.617.1
Click to expand...
Click to collapse
Oh thank god. I softbricked my phone earlier from the update.

Rebelb0y11 said:
Oh thank god. I softbricked my phone earlier from the update.
Click to expand...
Click to collapse
Have you try the ruu ? i have a 153 error. the other ruu all works fine

I can confirm the ruu works.
I am s-off and bootloader unlocked with sprint a9.

This is ROM don't update my One A9 s-off. After run ruu update and start install shield wizzard Nothing happens. PC with Windows 10

AlexeiFV said:
This is ROM don't update my One A9 s-off. After run ruu update and start install shield wizzard Nothing happens. PC with Windows 10
Click to expand...
Click to collapse
Install the latest HTC Sync Manager, It has some libs for the update program to run.

shafez said:
Install the latest HTC Sync Manager, It has some libs for the update program to run.
Click to expand...
Click to collapse
I am install. Before start update error - 132. Please Help me

AlexeiFV said:
I am install. Before start update error - 132. Please Help me
Click to expand...
Click to collapse
Same here mate
Can anyone already flash the ruu give me the "fastboot getvar all" result ? I need ti see what is wrong on my device

salvy' said:
Same here mate
Can anyone already flash the ruu give me the "fastboot getvar all" result ? I need ti see what is wrong on my device
Click to expand...
Click to collapse
My results
C:\Fastboot>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_hiaeul
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 1.57.617.60
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PQ912000
(bootloader) cid: BS_US001
RUU dos'nt update. Error - 132

I was having some problems to install the update, I had a custom ROM on it and that seems to be the problem, What I did first is to install RUU 1.57.617.60 and after that install the Nougat update, now is running fine.

RUU does indeed update with s-off and an unlocked bootloader,have to run it from download mode...doesnt matter what ROM you have [email protected] that point... Ive flashed with my rom loaded on device back to stock RUU many many times...

Has anyone tried flashing the latest supersu onto the at&t HTC one a9 running nougat yet? Yes I'm running mine s off and bootloader unlocked

I think the issues that some people are having are related to the encryption of the RUU itself. I don't think it is going to install on firmware bases other than 1.57.617.60 due to that.
The encryption is different than previous RUUs.
@Captain_Throwback @nkk71 The HTC RUU Decryption Tool 3.1.0 will not decipher this RUU. I guess the time has come for 2PQ9_keyfile_2.bin.
+++ Welcome to the HTC RUU Decryption Tool 3.1.0 +++
by nkk71 and Captain_Throwback
Mac OS X support by topjohnwu
RUU identified as Executable file
Extracting rom.zip from RUU_HIA_AERO_UL_N70_SENSE80GP_ATT_MR_NA_Gen_Unlock_2.18.617.1.exe
Extracting temporary files...
Extracting rom zip files...
Extracting rom.zip...done.
Extracting android-info.txt...done.
Cleaning up...
Done!
Information extracted from RUU.EXE:
INFO: RUU modelid: 2PQ912000
INFO: RUU mainver: 2.18.617.1
Extracting ZIP files
Normal Zip format detected, using unzip
Archive: /nougat/OUT/romzip/rom.zip
extracting: info.bin
extracting: zip_0.zip
extracting: zip_1.zip
extracting: zip_2.zip
extracting: zip_3.zip
extracting: zip_4.zip
extracting: zip_5.zip
extracting: zip_6.zip
extracting: zip_7.zip
extracting: zip_8.zip
extracting: zip_9.zip
extracting: zip_10.zip
extracting: zip_11.zip
extracting: zip_12.zip
extracting: zip_13.zip
extracting: zip_14.zip
extracting: zip_15.zip
extracting: zip_16.zip
extracting: zip_17.zip
extracting: zip_18.zip
extracting: zip_19.zip
extracting: zip_20.zip
extracting: zip_21.zip
extracting: zip_22.zip
Finished: Successfully extracted zip files to 'dumped_zips'
Attempting to find suitable keyfile
Find First Encrypted ZIP
Encrypted zip to be used for testing: 'zip_0.zip'
No proper keyfile, trying known keys instead...
Testing keyfile '0P3P_keyfile_4.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile '0P6B_keyfile_1.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile '0P6B_keyfile_6.20.654.3.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile '0P6B_keyfile_6.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile '0PAJ_keyfile_1.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile '0PCV_keyfile_1.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile '0PFH_keyfile_2.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile '0PGZ_keyfile_1.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile '0PJA_keyfile_2.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile '0PKV_keyfile_1.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile '0PM9_keyfile_1.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile '0PN7_keyfile_1.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile '0PN7_keyfile_4.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile '0PN7_keyfile_5.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile '2PQ9_keyfile_1.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile '2PRG_keyfile_2.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile '2PS6_keyfile_1.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile '2PST_keyfile_1.08.401.2.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile 'PJ75_keyfile_4.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile 'PO58_keyfile_4.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Processing ZIP... 32768/131716851
Still no proper keyfile, trying all ruuveal built-in keys...
Testing ruuveal device 'cp2dcg'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'cp2dtg'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'cp2dug'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'cp3dcg'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'cp3dtg'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'cp3dug'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'cp3edtg'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'cp5dtu'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'cp5dug'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'cp5dwg'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'csndug'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'deluxe_j'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'deluxe_u'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'deluxe_ub1'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'dlpdtu'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'dlpdug'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'dlpdwg'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'dlxp_u'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'dlxp_ul'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'endeavor_td'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'endeavor_u'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'enrc2_u'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'enrc2b_u'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'evita'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'evitare_ul'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'fireball'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'jel_dd'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'jewel'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'k2_plc_cl'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'k2_u'...1
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'k2_ul'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'm4_u'...1
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'm4_ul'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'm7_u'...1
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'm7_ul'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'm7_wlj'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'm7_wls'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'm7_wlv'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'm7cdtu'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'm7cdug'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'm7cdwg'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'magnids'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'monarudo'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'mystul'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'proto'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'protodcg'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'protodug'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'prototd'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 't6dug'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 't6dwg'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 't6tl'...1
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 't6u'...51
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 't6ul'...1
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 't6ula'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 't6whl'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 't6wl'...1
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'tc2'...51
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'ville'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'villec2'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'z4td'...1
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'zara_cl'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'zara_wl'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Processing ZIP... 32768/131716851
Trying force extraction of hboot/hosd...
Archive: zip_0.zip
warning [zip_0.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
inflating: tmp/hosd_signed.img
error: invalid compressed data to inflate
caution: filename not matched: hboot*
Archive: zip_1.zip
warning [zip_1.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_2.zip
warning [zip_2.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_3.zip
warning [zip_3.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_4.zip
warning [zip_4.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_5.zip
warning [zip_5.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_6.zip
warning [zip_6.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_7.zip
warning [zip_7.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_8.zip
warning [zip_8.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_9.zip
warning [zip_9.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_10.zip
warning [zip_10.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_11.zip
warning [zip_11.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_12.zip
warning [zip_12.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_13.zip
warning [zip_13.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_14.zip
warning [zip_14.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_15.zip
warning [zip_15.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_16.zip
warning [zip_16.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_17.zip
warning [zip_17.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_18.zip
warning [zip_18.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_19.zip
warning [zip_19.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_20.zip
warning [zip_20.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_21.zip
warning [zip_21.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_22.zip
warning [zip_22.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
... assuming hosd, going to unpack it...
Android Image Kitchen - UnpackImg Script
by osm0sis @ xda-developers
Supplied image: hosd_signed.img
Setting up work folders...
Splitting image to "split_img/"...
BOARD_KERNEL_CMDLINE console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 earlyprintk androidboot.hardware=htc_hiae androidkey.dummy=1 androidboot.selinux=permissive
BOARD_KERNEL_BASE 80000000
BOARD_NAME hosd:0
BOARD_PAGE_SIZE 2048
BOARD_KERNEL_OFFSET 00008000
BOARD_RAMDISK_OFFSET 01000000
BOARD_TAGS_OFFSET 00000100
Unpacking ramdisk to "ramdisk/"...
Compression used: data
Error!
ERROR: Unable to unpack hosd (res=1)
Working directory cleaned.
ERROR: Could not find suitable decryption key!
Please provide a suitable keyfile, hboot or hosd (depending on device).
Removing unneeded work folders
INFO: RUU modelid: 2PQ912000
INFO: RUU mainver: 2.18.617.1
Finished: Tool has finished but there was an error, please
check the console output and your OUT folder
'/nougat/OUT_2PQ9_2.18.617.1'

CSnowRules said:
I think the issues that some people are having are related to the encryption of the RUU itself. I don't think it is going to install on firmware bases other than 1.57.617.60 due to that.
The encryption is different than previous RUUs.
@Captain_Throwback @nkk71 The HTC RUU Decryption Tool 3.1.0 will not decipher this RUU. I guess the time has come for 2PQ9_keyfile_2.bin.
+++ Welcome to the HTC RUU Decryption Tool 3.1.0 +++
by nkk71 and Captain_Throwback
Mac OS X support by topjohnwu
RUU identified as Executable file
Extracting rom.zip from RUU_HIA_AERO_UL_N70_SENSE80GP_ATT_MR_NA_Gen_Unlock_2.18.617.1.exe
Extracting temporary files...
Extracting rom zip files...
Extracting rom.zip...done.
Extracting android-info.txt...done.
Cleaning up...
Done!
Information extracted from RUU.EXE:
INFO: RUU modelid: 2PQ912000
INFO: RUU mainver: 2.18.617.1
Extracting ZIP files
Normal Zip format detected, using unzip
Archive: /nougat/OUT/romzip/rom.zip
extracting: info.bin
extracting: zip_0.zip
extracting: zip_1.zip
extracting: zip_2.zip
extracting: zip_3.zip
extracting: zip_4.zip
extracting: zip_5.zip
extracting: zip_6.zip
extracting: zip_7.zip
extracting: zip_8.zip
extracting: zip_9.zip
extracting: zip_10.zip
extracting: zip_11.zip
extracting: zip_12.zip
extracting: zip_13.zip
extracting: zip_14.zip
extracting: zip_15.zip
extracting: zip_16.zip
extracting: zip_17.zip
extracting: zip_18.zip
extracting: zip_19.zip
extracting: zip_20.zip
extracting: zip_21.zip
extracting: zip_22.zip
Finished: Successfully extracted zip files to 'dumped_zips'
Attempting to find suitable keyfile
Find First Encrypted ZIP
Encrypted zip to be used for testing: 'zip_0.zip'
No proper keyfile, trying known keys instead...
Testing keyfile '0P3P_keyfile_4.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile '0P6B_keyfile_1.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile '0P6B_keyfile_6.20.654.3.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile '0P6B_keyfile_6.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile '0PAJ_keyfile_1.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile '0PCV_keyfile_1.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile '0PFH_keyfile_2.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile '0PGZ_keyfile_1.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile '0PJA_keyfile_2.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile '0PKV_keyfile_1.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile '0PM9_keyfile_1.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile '0PN7_keyfile_1.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile '0PN7_keyfile_4.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile '0PN7_keyfile_5.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile '2PQ9_keyfile_1.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile '2PRG_keyfile_2.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile '2PS6_keyfile_1.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile '2PST_keyfile_1.08.401.2.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile 'PJ75_keyfile_4.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing keyfile 'PO58_keyfile_4.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Processing ZIP... 32768/131716851
Still no proper keyfile, trying all ruuveal built-in keys...
Testing ruuveal device 'cp2dcg'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'cp2dtg'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'cp2dug'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'cp3dcg'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'cp3dtg'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'cp3dug'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'cp3edtg'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'cp5dtu'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'cp5dug'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'cp5dwg'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'csndug'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'deluxe_j'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'deluxe_u'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'deluxe_ub1'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'dlpdtu'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'dlpdug'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'dlpdwg'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'dlxp_u'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'dlxp_ul'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'endeavor_td'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'endeavor_u'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'enrc2_u'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'enrc2b_u'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'evita'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'evitare_ul'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'fireball'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'jel_dd'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'jewel'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'k2_plc_cl'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'k2_u'...1
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'k2_ul'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'm4_u'...1
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'm4_ul'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'm7_u'...1
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'm7_ul'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'm7_wlj'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'm7_wls'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'm7_wlv'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'm7cdtu'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'm7cdug'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'm7cdwg'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'magnids'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'monarudo'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'mystul'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'proto'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'protodcg'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'protodug'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'prototd'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 't6dug'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 't6dwg'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 't6tl'...1
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 't6u'...51
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 't6ul'...1
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 't6ula'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 't6whl'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 't6wl'...1
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'tc2'...51
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'ville'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'villec2'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'z4td'...1
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'zara_cl'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Testing ruuveal device 'zara_wl'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Processing ZIP... 32768/131716851
Trying force extraction of hboot/hosd...
Archive: zip_0.zip
warning [zip_0.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
inflating: tmp/hosd_signed.img
error: invalid compressed data to inflate
caution: filename not matched: hboot*
Archive: zip_1.zip
warning [zip_1.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_2.zip
warning [zip_2.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_3.zip
warning [zip_3.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_4.zip
warning [zip_4.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_5.zip
warning [zip_5.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_6.zip
warning [zip_6.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_7.zip
warning [zip_7.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_8.zip
warning [zip_8.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_9.zip
warning [zip_9.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_10.zip
warning [zip_10.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_11.zip
warning [zip_11.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_12.zip
warning [zip_12.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_13.zip
warning [zip_13.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_14.zip
warning [zip_14.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_15.zip
warning [zip_15.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_16.zip
warning [zip_16.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_17.zip
warning [zip_17.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_18.zip
warning [zip_18.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_19.zip
warning [zip_19.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_20.zip
warning [zip_20.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_21.zip
warning [zip_21.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
Archive: zip_22.zip
warning [zip_22.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
caution: filename not matched: hboot*
caution: filename not matched: hosd*
... assuming hosd, going to unpack it...
Android Image Kitchen - UnpackImg Script
by osm0sis @ xda-developers
Supplied image: hosd_signed.img
Setting up work folders...
Splitting image to "split_img/"...
BOARD_KERNEL_CMDLINE console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 earlyprintk androidboot.hardware=htc_hiae androidkey.dummy=1 androidboot.selinux=permissive
BOARD_KERNEL_BASE 80000000
BOARD_NAME hosd:0
BOARD_PAGE_SIZE 2048
BOARD_KERNEL_OFFSET 00008000
BOARD_RAMDISK_OFFSET 01000000
BOARD_TAGS_OFFSET 00000100
Unpacking ramdisk to "ramdisk/"...
Compression used: data
Error!
ERROR: Unable to unpack hosd (res=1)
Working directory cleaned.
ERROR: Could not find suitable decryption key!
Please provide a suitable keyfile, hboot or hosd (depending on device).
Removing unneeded work folders
INFO: RUU modelid: 2PQ912000
INFO: RUU mainver: 2.18.617.1
Finished: Tool has finished but there was an error, please
check the console output and your OUT folder
'/nougat/OUT_2PQ9_2.18.617.1'
Click to expand...
Click to collapse
Did you generate a new keyfile?

Captain_Throwback said:
Did you generate a new keyfile?
Click to expand...
Click to collapse
New keyfile has been uploaded in the RUU decryption tool thread here.

Captain_Throwback said:
Did you generate a new keyfile?
Click to expand...
Click to collapse
htc changed the key

The same situation for downgrade, because of the change of encrytion key, I cannot flash ruu1.57.617.60, it gave the error: ERR check AES encrypted magic string failed.
So I flash firmware_1.57.617.60 first, then can flash ruu1.57.617.60 sucessfully.

goodman_east said:
The link to RUU2.18.617.1 is now available.
Stock RUU 2.18.617.1
due to the change of encryption key, firmware_2.18.617.1 need to flash.
you can find the firmware.zip in OTA files.
link to OTA2.18.617.1
Click to expand...
Click to collapse
I flash firmware from OTA and after the ruu will work ? I have a signature error now

Thanks Mate work, Update to 7.0

My A9 is Hong Kong version on stock, Can I flash it?

Related

I want to ask my friends forum about some activity that occurs in fastboot.
when i use fastboot update update.zip option, that appear is:
Code:
archive do not Contain 'android-info.txt'
archive do not Contain 'android-product.txt'
error: update package has no android-info.txt or android-info.txt
then in one after another with requests other files: system.sig, boot.sig, recovery.sig
where I can get the 5 files above?
Code:
- Android-info.txt
- Android-product.txt
- system.sig
- boot.sig
- recovery.sig
Is there some friends who can help me in making techniques with ropes?

Ok, so from what I gathered is that all HTC's new RUU's for JellyBean has a new zip protection. This thread is for some ideas to try to find a way to get around and/or fix this problem.
From the EVTARE 1.15.502.9 RUU, I get this output trying to unzip:
Code:
unzip 'rom.zip'
Archive: rom.zip
warning [rom.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
file #1: bad zipfile offset (local header sig): 384
(attempting to re-compensate)
file #1: bad zipfile offset (local header sig): 384
file #2: bad zipfile offset (local header sig): 939275
(attempting to re-compensate)
file #2: bad zipfile offset (local header sig): 939275
file #3: bad zipfile offset (local header sig): 939844
file #4: bad zipfile offset (local header sig): 940066
inflating: recovery_signed.img
error: invalid compressed data to inflate
inflating: system.img
error: invalid compressed data to inflate
inflating: userdata_16g.img bad CRC 04e7f027 (should be de5e140e)
inflating: userdata_32g.img
error: invalid compressed data to inflate
inflating: splash1.nb0
inflating: tp.img
inflating: ramdisk.img
inflating: wlan.img
inflating: rawpt_16g.img
inflating: rawpt_32g.img
inflating: pg3fs_spcustom.img
inflating: mdm9k.img
error: invalid compressed data to inflate
inflating: u64g.hdr
inflating: u32g.hdr
inflating: u16g.hdr
inflating: u32gr.hdr
inflating: bct.img
inflating: userdata_64g.img
inflating: userdata_32g_resv.img
inflating: rawpt_64g.img
Here's from the VILLEPLUS 1.14.709.16 RUU:
Code:
unzip 'rom.zip'
Archive: rom.zip
warning [rom.zip]: 384 extra bytes at beginning or within zipfile
(attempting to process anyway)
file #1: bad zipfile offset (local header sig): 384
(attempting to re-compensate)
file #1: bad zipfile offset (local header sig): 384
file #2: bad zipfile offset (local header sig): 408146
(attempting to re-compensate)
file #2: bad zipfile offset (local header sig): 408146
file #3: bad zipfile offset (local header sig): 408689
inflating: rcdata.img
inflating: boot_signed.img
inflating: recovery_signed.img
inflating: system.img bad CRC 35922281 (should be 9a30ea6e)
inflating: splash1.nb0
inflating: dzdata_16g.img
error: invalid compressed data to inflate
inflating: dzdata_16g.hdr
inflating: sbl2.img
inflating: sbl3.img
inflating: tz.img
inflating: rpm.img
inflating: adsp.img
inflating: pg2fs_spcustom.img
inflating: wcnss.img
error: invalid compressed data to inflate
file #18: bad zipfile offset (local header sig): 651011233
inflating: sbl1-1.img
inflating: sbl1-2.img
inflating: sbl1-3.img
inflating: dzdata_64g.hdr
inflating: cs_cypress_smart.img
inflating: dzdata_64g.img
error: invalid compressed data to inflate
So at a glance it seems they're using an offset or something that makes the zip corrupt.
Hopefully you guys can help and we can get this problem fixed. I won't even start on how this tactic is stupid on HTC's part.

so far i have tried using DD to strip bad bits / bytes out of the file and it still is corrupted
you can strip the first ammount of bytes
Code:
Today I had to remove the first 1131 bytes from an 800MB mixed text / binary file, a filtered subversion dump I'm hacking for a new repository. What's the best way to do this?
To start with I tried
dd bs=1 skip=1131 if=filtered.dump of=trimmed.dump
but after the skip this copies the remainder of the file a byte at a time, i.e. very slowly. In the end I worked out I needed 405 bytes to round this up to three blocks of 512 which I could skip
dd if=/dev/zero of=405zeros bs=1 count=405
cat 405zeros filtered.dump | dd bs=512 skip=3 of=trimmed.dump
which completed fairly quickly but there must have been a simpler / better way? Is there another tool I've forgotten about? Thanks!
got past alot of the bad header files
but i think there is an algorithm inside the .exe that will tell us what we want
also when trying to flash these RUU's it looks on your device for a sigcheck
if you are able to successfully run the RUU
does the system cache the system.img somewhere?? or does it extract it to the unit

same with CYGWIN
same with CYGWIN
with ext2explore only system files folder/ apps extracted
467 MB (490,099,471 bytes
516 Files, 2 Folders
second folder bin is empty

carl1961 said:
same with CYGWIN
with ext2explore only system files folder/ apps extracted
467 MB (490,099,471 bytes
516 Files, 2 Folders
second folder bin is empty
Click to expand...
Click to collapse
its looking right now as if we need to figure out how to repack the CRC and remove those 384 misc byte?

Beyond Compare Failed too

Yeah. It looks like they're purposely corrupting the zips. The only thing I find common is 384 offset.
Sent from my HTC One XL using Tapatalk 2

i think its a set of data to be stripped from the actual file
if we find the data to strip i feel it will resolve the other unzipping problems
now
where to find this data to strip

Maybe extract the exe and the cab to find out
Sent from my HTC One XL using Tapatalk 2

I uploaded what cygwin un ziped if you can use it
http://d-h.st/QQS
romcygwin.zip
I copyed rom.zip to phone and tryed with term console and busybox complained

are these still with corrupted System.img?

Zarboz said:
are these still with corrupted System.img?
Click to expand...
Click to collapse
yes thats what was unziped

carl1961 said:
yes thats what was unziped
Click to expand...
Click to collapse
jw did any one else have success with dd if=
and removing the first 384 bytes in the file?

I don't really think that "corrupted" is good name for that. They are not corrupted, because device can read and extract it properly. I think this is a mechanism of faked checksums inside or maybe HTC wrote some small app for Linux and a password or special keyfile might be required.

mike1986. said:
I don't really think that "corrupted" is good name for that. They are not corrupted, because device can read and extract it properly. I think this is a mechanism of faked checksums inside or maybe HTC wrote some small app for Linux and a password or special keyfile might be required.
Click to expand...
Click to collapse
Yeah. It would make sense
Sent from my HTC One XL using Tapatalk 2

Did have a quick look, HTC have messed with it, they've done their own thing to it. If it was a normal corrupt zip afaik it would still start with Pk showing its a zip file
but this doesnt start with pk
Also you have this [email protected] & RUU version number 1.14.709.16 within the zip
They clearly messed with the file.
Think diamondback/flemmard/chainfires needed for this one
I could get most of it extracted, 4 failed due to data error and the only 1 failed due to CRC error was the main system.img

Shaky156 said:
Did have a quick look, HTC have messed with it, they've done their own thing to it. If it was a normal corrupt zip afaik it would still start with Pk showing its a zip file
but this doesnt start with pk
Also you have this [email protected] & RUU version number 1.14.709.16 within the zip
They clearly messed with the file.
Think diamondback/flemmard/chainfires needed for this one
I could get most of it extracted, 4 failed due to data error and the only 1 failed due to CRC error was the main system.img
Click to expand...
Click to collapse
Yeah. The offset of 384 is constant throughout all the zips. But yes, we'll need some real help.
Sent from my HTC One XL using Tapatalk 2

mike1986. said:
I don't really think that "corrupted" is good name for that. They are not corrupted, because device can read and extract it properly. I think this is a mechanism of faked checksums inside or maybe HTC wrote some small app for Linux and a password or special keyfile might be required.
Click to expand...
Click to collapse
i agree
i feel as tho it does a sig check on the device and decrypts the .zip with the coresponding "pub" / "priv" key on the device

Tried extracting it yesterday and the only solid thing I got was /system/app/ through cygwin. None of the other /bin/ or /framework/ files or anything for that matter other than app succeeded.
Why would they even do it in the first place is beyond me.

usaff22 said:
Tried extracting it yesterday and the only solid thing I got was /system/app/ through cygwin. None of the other /bin/ or /framework/ files or anything for that matter other than app succeeded.
Why would they even do it in the first place is beyond me.
Click to expand...
Click to collapse
to stop custom roms of JB, also to increase people upgrading there phone $$$

I was able to extract the app folder but the the rest of the folders in the system.img gave me errors and I couldn't look in the build.prop it froze up the application that I was using. I think the answer to our problem is in the build.prop. Just throwing out and idea.
Does anyone know how to extract the exe with out running it?

So im trying to flash XZDual Recovery to my phone and this is what i keep getting in the command shell, please someone help.
Last login: Sat Nov 21 12:18:16 on ttys001
Yazans-MacBook:~ YazanAbz$ /Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh
chmod: files/adb.linux: No such file or directory
chmod: files/adb.mac: No such file or directory
==============================================
= =
= XZDualRecovery =
= Maintained by [NUT] =
= =
= For many Sony Xperia devices! =
= =
==============================================
Run the installer with sudo if it fails to connect to your device!
Choose an installation option:
1/ Installation on device rooted with SuperSU
2/ Installation on device rooted with SuperUser
3/ Installation on an unrooted (Lollipop 5.0) ROM using rootkitXperia
Q/ Exit
Enter option:
3
Using rootkitXperia to attempt an installation.
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 142: cd: files: No such file or directory
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 143: ./adb.mac: No such file or directory
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 144: ./adb.mac: No such file or directory
=============================================
Step1 : Waiting for Device.
=============================================
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 150: ./adb.mac: No such file or directory
Succes
=============================================
Device and firmware information:
=============================================
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 156: ./adb.mac: No such file or directory
Device model is
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 158: ./adb.mac: No such file or directory
Firmware is
=============================================
Step2 : Sending the recovery files.
=============================================
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 165: ./adb.mac: No such file or directory
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 166: ./adb.mac: No such file or directory
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 167: ./adb.mac: No such file or directory
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 168: ./adb.mac: No such file or directory
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 169: ./adb.mac: No such file or directory
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 170: ./adb.mac: No such file or directory
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 171: ./adb.mac: No such file or directory
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 172: ./adb.mac: No such file or directory
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 173: ./adb.mac: No such file or directory
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 174: ./adb.mac: No such file or directory
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 175: ./adb.mac: No such file or directory
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 176: ./adb.mac: No such file or directory
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 177: ./adb.mac: No such file or directory
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 178: ./adb.mac: No such file or directory
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 180: ./adb.mac: No such file or directory
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 184: ./adb.mac: No such file or directory
=============================================
Step3 : Setup of dual recovery.
=============================================
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 190: ./adb.mac: No such file or directory
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 191: ./adb.mac: No such file or directory
=============================================
Attempting to get root access for installation using rootkitXperia now.
NOTE: this only works on certain ROM/Kernel versions!
If it fails, please check the development thread (Post #2) on XDA for more details.
******** REMEMBER THIS: ********
XZDualRecovery does NOT install any superuser app!!
You can use one of the recoveries to root your device.
=============================================
To continue, press enter...
=============================================
Sending files
=============================================
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 101: ./adb.mac: No such file or directory
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 102: ./adb.mac: No such file or directory
=============================================
Installing using rootkitXperia by cubeundcube
Big thanks to anyone involved in the development:
Keen Team, cubeundcube, AndroPlus and zxz0O0
=============================================
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 115: ./adb.mac: No such file or directory
=============================================
If your device now boots to recovery, reboot
it to system to continue and allow this script
to check and clean up. The script will continue
once your device allows adb connections again.
=============================================
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 128: ./adb.mac: No such file or directory
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 129: ./adb.mac: No such file or directory
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 130: ./adb.mac: No such file or directory
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 132: ./adb.mac: No such file or directory
If your device booted to recovery and you see this menu, please reboot your device to system and press C.
You should have been told it is installing the recovery package, including a version.
If the unrooted installation failed, please press R once the device finished rebooting to retry!
R/ Retry installation on an unrooted ROM using rootkitXperia
C/ Continue installation
Q/ Exit
Enter option:
r
Retrying the rootkitXperia installation.
=============================================
Installing using rootkitXperia by cubeundcube
Big thanks to anyone involved in the development:
Keen Team, cubeundcube, AndroPlus and zxz0O0
=============================================
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 115: ./adb.mac: No such file or directory
=============================================
If your device now boots to recovery, reboot
it to system to continue and allow this script
to check and clean up. The script will continue
once your device allows adb connections again.
=============================================
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 128: ./adb.mac: No such file or directory
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 129: ./adb.mac: No such file or directory
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 130: ./adb.mac: No such file or directory
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 132: ./adb.mac: No such file or directory
If your device booted to recovery and you see this menu, please reboot your device to system and press C.
You should have been told it is installing the recovery package, including a version.
If the unrooted installation failed, please press R once the device finished rebooting to retry!
R/ Retry installation on an unrooted ROM using rootkitXperia
C/ Continue installation
Q/ Exit
Enter option:
r
Retrying the rootkitXperia installation.
=============================================
Installing using rootkitXperia by cubeundcube
Big thanks to anyone involved in the development:
Keen Team, cubeundcube, AndroPlus and zxz0O0
=============================================
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 115: ./adb.mac: No such file or directory
=============================================
If your device now boots to recovery, reboot
it to system to continue and allow this script
to check and clean up. The script will continue
once your device allows adb connections again.
=============================================
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 128: ./adb.mac: No such file or directory
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 129: ./adb.mac: No such file or directory
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 130: ./adb.mac: No such file or directory
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 132: ./adb.mac: No such file or directory
If your device booted to recovery and you see this menu, please reboot your device to system and press C.
You should have been told it is installing the recovery package, including a version.
If the unrooted installation failed, please press R once the device finished rebooting to retry!
R/ Retry installation on an unrooted ROM using rootkitXperia
C/ Continue installation
Q/ Exit
Enter option:
c
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 210: ./adb.mac: No such file or directory
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 211: ./adb.mac: No such file or directory
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 212: ./adb.mac: No such file or directory
=============================================
Installation FAILED!
Please copy and paste the contents of
this window/screen to the DevDB thread.
=============================================
/Users/YazanAbz/Desktop/T2U-lockeddualrecovery2.8.23-RELEASE.combined/install.sh: line 229: ./adb.mac: No such file or directory
Yazans-MacBook:~ YazanAbz$

UPDATE: This version of the tool is now deprecated. Please use the updated version!
(and thank @nkk71 while you're at it!!)
[TOOL][LINUX|WINDOWS][64bit][20-MAY-2016]Universal HTC RUU/ROM Decryption Tool 3.0.0​
----------------------------------------------------
Original Post:
First of all, I want to state that I deserve credit for none of this - all I did was aggregate some of the great work done by the fantastic devs here on XDA.
BIG Thanks @nkk71, for his idea to make this work universally on all encrypted HTC RUUs and all his hard work to make it happen! All I really did was post the thread.
Prerequisites:
- A system running a 64-bit Linux distro (tested on Ubuntu 15.10 & 16.04 LTS)
- At least 5GB of available disk space (ROMs are big)
readme.txt:
Code:
*** Captain_Throwback & nkk71's RUU decryption scripts for HTC Devices ***
INSTALLATION STEPS:
Extract files into folder of your choice, being sure to preserve the folder structure. The decrypt-htc binary and this readme file should be the only files in the root folder.
Download the encrypted RUU or encrypted rom zip of your choice from HTC (or wherever).
Place RUU.exe in the "place_ruu_here" folder or the ROM.zip in the "place_rom_zip_here" folder.
Run ./decrypt-htc and wait for script to complete (you may be prompted for input if there are issues).
The script will output 3 files (to the "out" folder): boot.img, system.img & the encrypted rom zip you started with (or was extracted from the RUU), named for SD card flashing on your device (if your device has an SD card). There will also be a folder with the extracted firmware for your device that can be used however you see fit :).
NOTE: For the A9, for example, the rom.zip will be named 2PQ9IMG.zip. Each device has a specific filename which will be reflected.
Below is a script of the expected output of the script when processing a RUU.exe.
Code:
Welcome to the RUU extraction and decryption script!
Extracting temporary files...
Extracting rom zip files...
Extracting rom.zip...done.
Extracting android-info.txt...done.
Cleaning up...
Done!
Extracting ZIP files
LargeZip format detected, using ruuveal
ruuveal
-------
Large zip format detected containing 7 zipfile(s)
Dumped (copied) zip file to: 01_dmp.zip
Dumped (copied) zip file to: 02_dmp.zip
Dumped (copied) zip file to: 03_dmp.zip
Dumped (copied) zip file to: 04_dmp.zip
Dumped (copied) zip file to: 05_dmp.zip
Dumped (copied) zip file to: 06_dmp.zip
Dumped (copied) zip file to: 07_dmp.zip
Finished: Successfully extracted zip files to '/home/throwback/android/decrypt/tool/working/extract'
Model ID found by extracting android-info.txt from RUU. Model ID identified as: 0PJA
Looking for keyfile: 0PJA_keyfile_2.bin
Found matching keyfile! Using keyfile: 0PJA_keyfile_2.bin
Decrypting ZIP files
Decrypting 01_dmp.zip
Encrypted zip detected, running ruuveal...
ruuveal
-------
Decrypted RUU (zip) written to: /home/throwback/android/decrypt/tool/working/decrypt/decrypted_zips/dec_01_dmp.zip
Decrypting 02_dmp.zip
Encrypted zip detected, running ruuveal...
ruuveal
-------
Decrypted RUU (zip) written to: /home/throwback/android/decrypt/tool/working/decrypt/decrypted_zips/dec_02_dmp.zip
Decrypting 03_dmp.zip
Encrypted zip detected, running ruuveal...
ruuveal
-------
Decrypted RUU (zip) written to: /home/throwback/android/decrypt/tool/working/decrypt/decrypted_zips/dec_03_dmp.zip
Decrypting 04_dmp.zip
Encrypted zip detected, running ruuveal...
ruuveal
-------
Decrypted RUU (zip) written to: /home/throwback/android/decrypt/tool/working/decrypt/decrypted_zips/dec_04_dmp.zip
Decrypting 05_dmp.zip
Encrypted zip detected, running ruuveal...
ruuveal
-------
Decrypted RUU (zip) written to: /home/throwback/android/decrypt/tool/working/decrypt/decrypted_zips/dec_05_dmp.zip
Decrypting 06_dmp.zip
Encrypted zip detected, running ruuveal...
ruuveal
-------
Decrypted RUU (zip) written to: /home/throwback/android/decrypt/tool/working/decrypt/decrypted_zips/dec_06_dmp.zip
Decrypting 07_dmp.zip
Encrypted zip detected, running ruuveal...
ruuveal
-------
Decrypted RUU (zip) written to: /home/throwback/android/decrypt/tool/working/decrypt/decrypted_zips/dec_07_dmp.zip
Unzipping decrypted zips
Archive: decrypted_zips/dec_01_dmp.zip
inflating: decrypted_all/android-info.txt
inflating: decrypted_all/aboot_signed.img
inflating: decrypted_all/radio.img
inflating: decrypted_all/splash1.nb0
inflating: decrypted_all/adsp.img
inflating: decrypted_all/rfg_1.img
inflating: decrypted_all/rfg_2.img
inflating: decrypted_all/ramdisk.img
inflating: decrypted_all/android-info2.txt
inflating: decrypted_all/sensor_hub.img
inflating: decrypted_all/emmc_appsboot.mbn
inflating: decrypted_all/persist.img
inflating: decrypted_all/dt.img
inflating: decrypted_all/bootloader
inflating: decrypted_all/gpt_main_32g.img
inflating: decrypted_all/pg2fs_ship_signkey.img
inflating: decrypted_all/apppreload.img
inflating: decrypted_all/cota.img
inflating: decrypted_all/gpt_main_64g.img
inflating: decrypted_all/sbl1-8994-1.img
inflating: decrypted_all/sdi.img
inflating: decrypted_all/hosd_signed.img
inflating: decrypted_all/rpm-8994-1.img
inflating: decrypted_all/pmic-8994-1.img
inflating: decrypted_all/boot_signed.img
inflating: decrypted_all/recovery_signed.img
inflating: decrypted_all/cpe.img
inflating: decrypted_all/tz-8994-1.img
inflating: decrypted_all/hyp-8994-1.img
inflating: decrypted_all/tp_SYN3351.img
inflating: decrypted_all/tp_MXM11876.img
inflating: decrypted_all/cir.img
inflating: decrypted_all/backup_android-info.txt
Archive: decrypted_zips/dec_04_dmp.zip
inflating: decrypted_all/system.img_02
Archive: decrypted_zips/dec_03_dmp.zip
inflating: decrypted_all/system.img_01
Archive: decrypted_zips/dec_07_dmp.zip
inflating: decrypted_all/dzdata_16g.img
inflating: decrypted_all/dzdata_32g.img
inflating: decrypted_all/dzdata_16g.hdr
inflating: decrypted_all/dzdata_32g.hdr
inflating: decrypted_all/dzdata_64g.hdr
inflating: decrypted_all/dzdata_64g.img
Archive: decrypted_zips/dec_06_dmp.zip
inflating: decrypted_all/system.img_04
Archive: decrypted_zips/dec_02_dmp.zip
inflating: decrypted_all/system.img_00
Archive: decrypted_zips/dec_05_dmp.zip
inflating: decrypted_all/system.img_03
7 archives were successfully processed.
Move system img files to system folder
‘decrypted_all/system.img_00’ -> ‘decrypted_system/system.img_00’
‘decrypted_all/system.img_01’ -> ‘decrypted_system/system.img_01’
‘decrypted_all/system.img_02’ -> ‘decrypted_system/system.img_02’
‘decrypted_all/system.img_03’ -> ‘decrypted_system/system.img_03’
‘decrypted_all/system.img_04’ -> ‘decrypted_system/system.img_04’
Finished: Successfully decrypted RUU to '/home/throwback/android/decrypt/tool/working/decrypt'
/home/throwback/android/decrypt/tool/working/decrypt/decrypted_system
/home/throwback/android/decrypt/tool/out
Attempting to create system.img
Multi-part system images
Sparse Image detected, using simg2img
Please be patient, this can take several minutes...finished.
Testing system.img...
e2fsck 1.42.12 (29-Aug-2014)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/home/throwback/android/decrypt/tool/out/system.img: 4685/286720 files (0.0% non-contiguous), 1041188/1146880 blocks
Finished: Successfully created system.img in '/home/throwback/android/decrypt/tool/out'
Renaming and moving files...
Rom.zip has been renamed for your device.
Boot image extracted from firmware.zip. boot.img & system.img can be used as base for building a new ROM.
Script complete! Files can be found in the 'out' folder. Enjoy your decrypted system!
(above output is from M9 RUU)
Important Notes:
If decrypting a rom.zip that is "combined" (meaning the first zip isn't encrypted), you will see the following error message at the top of the ruuveal section:
Code:
invalid htc aes encrypted zip file!
This just indicates that the first zip file isn't encrypted. The script will continue and complete with no issues, so this isn't a concern.
You may also see these messages:
Code:
caution: filename not matched: system.img*
Code:
1 archive had fatal errors.
These errors indicate that the first zip doesn't contain a system image to be extracted, which is fine (that's the zip that contains the firmware). This isn't a concern either.
The last issue you might notice is this:
Code:
warning [../out/firmware.zip]: 256 extra bytes at beginning or within zipfile
(attempting to process anyway)
The extra 256 bytes is HTC's signature on the unencrypted firmware zip. This also is nothing to worry about.
As long as you have all of the output files at the end of the script, everything should be fine.
Thanks:
twogood for unshield
@kmdm for unruu & ruuveal
@Flemmard for bruutveal
@osm0sis for Android Image Kitchen
@A.S._id for ANDROID_IMG_REPACK_TOOLS

Additional Info
Change Log:
January 11, 2016 - v2.0.0
Complete overhaul of existing script and process
Now works on any encrypted RUU/ROM for any HTC device with a known decryption key
For devices with unknown keyfile, user can provide hboot or hosd image (based on same software version is preferable) and a new keyfile will be created. You can share the new keyfile so that it can be added to our database.
Improved script output and error handling
January 1, 2016 - v1.5.3
Fixed the binary problem - should now work on PCs other than mine
January 1, 2016 - v1.5.2
Back to bash script (for now) to ensure compatibility with other PCs
January 1, 2016 - v1.5.1
Some script and binary cleanup (back end stuffs)
December 31, 2015 - v1.5
Compile script into binary format (back end stuffs)
December 31, 2015 - v1.4.1
Back-end cleanup to use "working" folder for zip processing
December 31, 2015 - v1.4
Added code to handle "combined" zips where first zip file is already decrypted
December 31, 2015 - v1.3
Can now handle encrypted rom zips!
Kill script if no files found
Script renamed from decrypt.sh to decrypt-htc.sh
Renames rom.zip from ruu (or provided rom.zip) to 2PQ9IMG.zip (or whatever corresponds to that for other applicable devices) automatically and puts in "out" folder
December 31, 2015 - v1.2
Added unshield and libunshield to zip so manual compilation is no longer necessary (thanks @nkk71)
December 30, 2015 - v1.1
Added version number
Modified script to allow for usage on multiple HTC devices
December 30, 2015
Initial version

Mine [emoji6]
Sent from my HTC One M9 using Tapatalk

Updated this (just now) to allow for handling of other devices which use the same type of encrypted RUU (like the Desire 626s, for example).

v1.2 is up! No more compilation of libunshield is necessary, thanks to @nkk71's help! Seriously, give that guy some love!

v1.3 is up!
Now there are provisions for handling encrypted ROMs that are zipped, and not just those from an RUU.
Can someone please try this thing out and provide feedback!!!!

v1.4 added.
Now "combined" zips can be extracted/decrypted as well.

Hello. Have tried it. I get the three files. But in Terminal i get the Message
"21 archives were successfully processed"
"2 archives had fatal errors"
Can i ignore the 2 archives fatal errors?

comibined zip first not encrypt

AntikerTa said:
Hello. Have tried it. I get the three files. But in Terminal i get the Message
"21 archives were successfully processed"
"2 archives had fatal errors"
Can i ignore the 2 archives fatal errors?
Click to expand...
Click to collapse
Yes you can, the error is not really an error, it just doesn't find a system.img_xx in 2 zip files, that's all
Sent from my HTC One M9 using Tapatalk

AntikerTa said:
Hello. Have tried it. I get the three files. But in Terminal i get the Message
"21 archives were successfully processed"
"2 archives had fatal errors"
Can i ignore the 2 archives fatal errors?
Click to expand...
Click to collapse
If you look in the "expected script output" in the OP, you'll see the same message (which is why I posted it there).
Though with the latest version, there will only be one archive with a "fatal" error.
If you have good files in the "out" folder, then assume everything went fine.

bl4ckluna said:
comibined zip first not encrypt
Click to expand...
Click to collapse
Was there a point to this post?

Followed instructions...
~/ruudecrypt$ ./decrypt-htc
./decrypt-htc: }u2n��ɢ
No worky, that is the output. Took the HTC RUU from their site. renamed ruu_a9.exe put it in the folder. Nothing else in root. Run decrypt script and that is what it does above.
Also, extracted the rom.zip out of the RUU, placed it in the folder ruu_a9.zip same error.

techlogik said:
Followed instructions...
~/ruudecrypt$ ./decrypt-htc
./decrypt-htc: }u2n��ɢ
No worky, that is the output. Took the HTC RUU from their site. renamed ruu_a9.exe put it in the folder. Nothing else in root. Run decrypt script and that is what it does above.
Also, extracted the rom.zip out of the RUU, placed it in the folder ruu_a9.zip same error.
Click to expand...
Click to collapse
What are you running this on? Where are the details to help troubleshoot? "No worky"? Really?

Is anyone else having issues with the latest version? I can go back to the previous format, but as long as the Linux distro can handle a bash script, it shouldn't matter whether the script is used or the binary is.

Followed your instructions, not much more to explain. For kicks, installed VMWorkstation Pro 12, installed a fresh Ubuntu 15.10, updates etc. Java/ADB and the usual basic stuff. Nothing special going on here, plain vanilla Ubuntu.
Again, downloaded your script in a folder. Copied ruu over to the working folder, renamed it to ruu_a9.exe
Ran the ./decrypt-htc script
Now, it gives this message, but similar:
./decrypt-htc: 8��������y����Y'��w������W�+Ɣ?�has expired!
Please contact your provider [email protected]
What more do you want for diagnosis?

techlogik said:
Followed your instructions, not much more to explain. For kicks, installed VMWorkstation Pro 12, installed a fresh Ubuntu 15.10, updates etc. Java/ADB and the usual basic stuff. Nothing special going on here, plain vanilla Ubuntu.
Again, downloaded your script in a folder. Copied ruu over to the working folder, renamed it to ruu_a9.exe
Ran the ./decrypt-htc script
Now, it gives this message, but similar:
./decrypt-htc: 8��������y����Y'��w������W�+Ɣ?�has expired!
Please contact your provider [email protected]
What more do you want for diagnosis?
Click to expand...
Click to collapse
Try the version I just uploaded and see if that works any better.

Tried that one, more of the same:
[email protected]:~/decrypt$ ls
bin decrypt-htc keyfile lib place_rom_zip_here place_ruu_here readme.txt
[email protected]:~/decrypt$ ./decrypt-htc

�N��<Z"��@i�?|�w��
�U>I�t��k�*��TN�8'B��8�m?�"w$�[email protected]�['��
bF��
#��
[email protected]:~/decrypt$

techlogik said:
Tried that one, more of the same:
[email protected]:~/decrypt$ ls
bin decrypt-htc keyfile lib place_rom_zip_here place_ruu_here readme.txt
[email protected]:~/decrypt$ ./decrypt-htc

�N��<Z"��@i�?|�w��
�U>I�t��k�*��TN�8'B��8�m?�"w$�[email protected]�['��
bF��
#��
[email protected]:~/decrypt$
Click to expand...
Click to collapse
Alright, 1.5.2 should take care of it. I'll have to figure out why only I can run the binary. But until then, might as well have a usable version available .

Captain_Throwback said:
Alright, 1.5.2 should take care of it. I'll have to figure out why only I can run the binary. But until then, might as well have a usable version available .
Click to expand...
Click to collapse
That worked. Thanks.

i am using a REDMI 5 and when i flash Magisk this error occurs
Plz help
Updating partision details...
...done
Installing ZIP file '/sdcard1/Magisk-17.1.zip
Checking for Digest file...
Skipping Digest Check: no Digest file found
*****************************
*Magisk v17.1 Installer
*****************************
-Mounting /System, /Vendor
-Target image: /dev/block/mcblk0p21
-Device platform: arm64
-Constructing environment
-Unpacking boot image
-Checking ramdisk status
-Patching ramdisk
-Repacking boot image
!Unable to repack boot image!
-Unmounting partitions
Updater process ended with ERROR:1
Error installing zip file '/sdcard1/Magisk-v17.1.zip'
Updating partition details...
...done