Data Crashes.
Please contact your service center
How can i do
Wizard Service Tool--SIM unlock
Decrypted stored sum: 192BE1B323532C8D
Decrypted calcd sum: 1EE6F72A2868E34B
Checksums did NOT match!!
Could not determine a key index to decrypt it.
Your CID block must be corrupted or file isn't
from a valid CID dump!!
Aborting operation.
michael73 said:
Data Crashes.
Please contact your service center
How can i do
Wizard Service Tool--SIM unlock
Decrypted stored sum: 192BE1B323532C8D
Decrypted calcd sum: 1EE6F72A2868E34B
Checksums did NOT match!!
Could not determine a key index to decrypt it.
Your CID block must be corrupted or file isn't
from a valid CID dump!!
Aborting operation.
Click to expand...
Click to collapse
I've given you a clue.
P800W
How can i get cid dump for my machine
THX
When read cid block it post
CURRENT_CID has no value
In the REXX script named:
At line number:1092
it seemed i need cid dumps with index is 1092
who can send me ,thanks
mailto:[email protected]
Have you already found solution for this problem?
I have one in same situation.
BR
AC
Same problem here. Any solutions sofar?
I made a foolish attempt of converting my HTC 10 au kddi (japan) to US Unlocked for to get the Nougat update. I tried to use a RUU exe file but it came back with a error ( not a major error, it seems as it wouldn't even flash the file and state wrong model something). Of course, I have 2 back up on the ready. One for the stock of stock and the other after receiving the first and only OTA. However, both seems to failed after around 80% and after that the system partition become unmounted and it shown an error saying Failed to mount /system (Invalid Argument). I still have access to the download, RUU, bootloader and recovery mode but cannot seems to get the back up working. Any idea of why is appreciate.
nerodarknight said:
I made a foolish attempt of converting my HTC 10 au kddi (japan) to US Unlocked for to get the Nougat update. I tried to use a RUU exe file but it came back with a error ( not a major error, it seems as it wouldn't even flash the file and state wrong model something). Of course, I have 2 back up on the ready. One for the stock of stock and the other after receiving the first and only OTA. However, both seems to failed after around 80% and after that the system partition become unmounted and it shown an error saying Failed to mount /system (Invalid Argument). I still have access to the download, RUU, bootloader and recovery mode but cannot seems to get the back up working. Any idea of why is appreciate.
Click to expand...
Click to collapse
You soft-bricked your unit.
Find an RUU for the firmware version your phone originally had, make sure your CID and MID match the ones for the RUU was created for.
NEVER flash RUU for different firmware without being S-OFF. Always confirm that CID and MID of the RUU match your CID and MID. ALWAYS!
Kyuubi10 said:
You soft-bricked your unit.
Find an RUU for the firmware version your phone originally had, make sure your CID and MID match the ones for the RUU was created for.
NEVER flash RUU for different firmware without being S-OFF. Always confirm that CID and MID of the RUU match your CID and MID. ALWAYS!
Click to expand...
Click to collapse
I managed to get around that by flashing a custom ROM, happily running Viper MM ROM. FYI, I changed the CID and MID because I'm S-OFF but it does not seems to work. I'm rocking the Viper MM ROM until I can get my hand on a RUU for my variant and hopefully by that time I will be rocking Nougat, Japan carriers tend to take a long time with their update.
nerodarknight said:
I managed to get around that by flashing a custom ROM, happily running Viper MM ROM. FYI, I changed the CID and MID because I'm S-OFF but it does not seems to work. I'm rocking the Viper MM ROM until I can get my hand on a RUU for my variant and hopefully by that time I will be rocking Nougat, Japan carriers tend to take a long time with their update.
Click to expand...
Click to collapse
Cool, sounds like you are sorted.
Well, regarding your firmware and cid/mid...it seems to me then that regardless what you set your cid/mid to your device has some significant hardware differences that make it impossible to boot the firmware of another variant.
Shame really, not much you can do in that case.
Kyuubi10 said:
Cool, sounds like you are sorted.
Well, regarding your firmware and cid/mid...it seems to me then that regardless what you set your cid/mid to your device has some significant hardware differences that make it impossible to boot the firmware of another variant.
Shame really, not much you can do in that case.
Click to expand...
Click to collapse
[RESTORE STARTED]
Restore folder: '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup'
Skipping MD5 check based on user setting.
Calculating restore details...
I:InfoManager file '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/boot.info' not found.
I:Restore file system is: 'emmc'.
I:InfoManager file '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/system_image.info' not found.
I:Restore file system is: 'emmc'.
Restoring 2 partitions...
Total restore size is 4784MB
I:Restore filename is: boot.emmc.win
I:Restore file system is: 'emmc'.
Restoring Boot...
I:Reading '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/boot.emmc.win', writing '/dev/block/mmcblk0p59'
[Boot done (2 seconds)]
I:Restore filename is: system_image.emmc.win
I:Restore file system is: 'emmc'.
Restoring System Image...
I:Reading '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/system_image.emmc.win', writing '/dev/block/mmcblk0p62'
Truncating string cache entries.
Truncating string cache entries.
I:Error writing destination fd (No space left on device)
This is the error I got after the backup restore failed. If possible can you explain what does it mean?
nerodarknight said:
[RESTORE STARTED]
Restore folder: '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup'
Skipping MD5 check based on user setting.
Calculating restore details...
I:InfoManager file '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/boot.info' not found.
I:Restore file system is: 'emmc'.
I:InfoManager file '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/system_image.info' not found.
I:Restore file system is: 'emmc'.
Restoring 2 partitions...
Total restore size is 4784MB
I:Restore filename is: boot.emmc.win
I:Restore file system is: 'emmc'.
Restoring Boot...
I:Reading '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/boot.emmc.win', writing '/dev/block/mmcblk0p59'
[Boot done (2 seconds)]
I:Restore filename is: system_image.emmc.win
I:Restore file system is: 'emmc'.
Restoring System Image...
I:Reading '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/system_image.emmc.win', writing '/dev/block/mmcblk0p62'
Truncating string cache entries.
Truncating string cache entries.
I:Error writing destination fd (No space left on device)
This is the error I got after the backup restore failed. If possible can you explain what does it mean?
Click to expand...
Click to collapse
Ok, so either you run out of space on system partition, or you have corrupted filesystem.
If you don't mind starting from scratch, you could try formatting system partition.
Not sure what file system Android uses, i believe EXT3 or 4. (if anyone else knows, feel free to help).
But you could try that, then run the restore again
Kyuubi10 said:
Ok, so either you run out of space on system partition, or you have corrupted filesystem.
If you don't mind starting from scratch, you could try formatting system partition.
Not sure what file system Android uses, i believe EXT3 or 4. (if anyone else knows, feel free to help).
But you could try that, then run the restore again
Click to expand...
Click to collapse
Doesn't not seems to work, formatted the system partition but it still failed
If this is any help, I successfully converted it to WWE but since I got a bug with the service : LTE (data) is good but no call or text whatsoever so that's why I'm trying to convert back, flashed the firmware zip and then restore back up. The firmware zip worked out fine but the restore always failed. To add to that, when I'm on WWE firmware I can restore the WWE firmware backup just fine.
I found out that some how I shrank the system partition so that's why it is not able to fit the back up, is there anyway to reverse this at all?
nerodarknight said:
I found out that some how I shrank the system partition so that's why it is not able to fit the back up, is there anyway to reverse this at all?
Click to expand...
Click to collapse
I believe TWRP should be capable...
Google for a guide.
nerodarknight said:
I made a foolish attempt of converting my HTC 10 au kddi (japan) to US Unlocked for to get the Nougat update. I tried to use a RUU exe file but it came back with a error ( not a major error, it seems as it wouldn't even flash the file and state wrong model something). Of course, I have 2 back up on the ready. One for the stock of stock and the other after receiving the first and only OTA. However, both seems to failed after around 80% and after that the system partition become unmounted and it shown an error saying Failed to mount /system (Invalid Argument). I still have access to the download, RUU, bootloader and recovery mode but cannot seems to get the back up working. Any idea of why is appreciate.
Click to expand...
Click to collapse
I have the same problem this happened after I formatted the date to blink rom
How can I solve this problem after I tried to install the rom maximos hd and I did not succeed I returned my bachup from the stock more now this giving error in the horade do the same I am with bild 2.41.401.3 cid HTC__M27 mid 2PS62000
Can someone help me please ???
hi guys,i think that i have bricked my phone.
1) i'm not able to run/flash any recovery
2) i can't flash any RUU because i know that in S-on mode the bootloader must is relocked and i can't relock this :
C:\Users\jeremy\Desktop\android>fastboot oem lock
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.097s]
finished. total time: 0.101s
3)i can't enable oem unlock and developer option because the system is deleted,the recovery fail to boot
What can I do? Please help me
There is a way to execute Sunshine S-OFF through fastboot?(obviously paying)
What you wrote only applies to devices that are older than the M9. You don't need to relock for flashing a RUU.
However, it's impossible to get S-OFF via Sunshine without a working system. You might be able to get S-OFF via a java card or an xtc clip, though. (Both are much more expensive!) The good news is that you don't need S-OFF due to what I wrote in the first sentence (assuming that a suitable RUU is available for your phone).
Flippy498 said:
What you wrote only applies to devices that are older than the M9. You don't need to relock for flashing a RUU.
However, it's impossible to get S-OFF via Sunshine without a working system. You might be able to get S-OFF via a java card or an xtc clip, though. (Both are much more expensive!) The good news is that you don't need S-OFF due to what I wrote in the first sentence (assuming that a suitable RUU is available for your phone).
Click to expand...
Click to collapse
Oh my god yes! My phone not does seem to go in the oemRUU mode
(and he always has problems to reboot in the selected mode using the buttons,so i go to bootloader and next i go to download/selected mode)
and flashing exe RUU with the metod : "file replacement rom.zip" the RUU say "rebooting M9 in bootloader mode"
(in practice it is not the bootloader mode but a white screen with the HTC logo and red writing)
And say "waiting for bootloader" for long time,next say "error 171"
That error is mentioned in the ReadMe thread. I'd suggest you to try flashing the RUU via htc_fastboot or an SD card. (I personally prefer the latter method.) Instructions can be found in the ReadMe thread, as well.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
That error is mentioned in the ReadMe thread. I'd suggest you to try flashing the RUU via htc_fastboot or an SD card. (I personally prefer the latter method.) Instructions can be found in the ReadMe thread, as well.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
this is what happens https://youtu.be/EHxBPgTzqZU
this time there have been errors,
but even when it seems that the various parts of the ruu are starting flashing(0%) the phone will reboot and the result is the same
flashing with fastboot:
C:\Users\jeremy\Desktop\android>htc_fastboot flash zip 0PJAIMG_HIMA_UHL_M60_SENSE70_MR_H3G_UK_3.35.771.12_Radio_01.01_U11440792_93.00.51117G_F_release_464296_signed.zip
htc_fastboot v3.0.9.2 (2015-05-29)
target rom version: 3.35.771.12
found large-zip header, file count: 8
processing file 1/8...
sending 'zip' (170579 KB)...
OKAY [ 12.380s]
writing 'zip'...
(bootloader) HOSD CL#670679
FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 13.672s
-----------------------------------------------------------------------------------------------------
Fastboot getvar all :
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: ###########
(bootloader) version-main: 3.35.771.12
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_93.00.51117G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: H3G__402
I have the latest RUU for h3g devices downloaded from your Google Sheet,my firmware is 3.35.771.12
There is a way to individually flash a particular part of the RUU for having
at least working "oemRUU mode"?
Please check whether the file is corrupted by comparing its MD5 checksum with the desired value from the download site.
If it matches then there's something wrong with the phone that I haven't seen before. (Maybe a new variant of the dying nand?) If it doesn't match you need to re-download the RUU till it matches.
You can extract the single parts of the RUU's firmware with the help of the decryption tool that is linked in the ReadMe thread. The flashing commands got linked in Q8 of the FAQ as solution for the blue screen error.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Please check whether the file is corrupted by comparing its MD5 checksum with the desired value from the download site.
If it matches then there's something wrong with the phone that I haven't seen before. (Maybe a new variant of the dying nand?) If it doesn't match you need to re-download the RUU till it matches.
You can extract the single parts of the RUU's firmware with the help of the decryption tool that is linked in the ReadMe thread. The flashing commands got linked in Q8 of the FAQ as solution for the blue screen error.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
md5 match
the blue bootloader is a problem I had with another m9 and i fixed.
i try with the decryption tool
Help with RUU_Decrypt_Tool
i have put the "rom.zip" in the directory of decrypter
the command I used is this :
RUU_Decrypt_Tool -s ROM.zip -o
log :
C:\Users\Matteo\Desktop\recupero>RUU_Decrypt_Tool -s ROM.zip -o
+++ Welcome to the HTC RUU Decryption Tool 3.6.5 +++
RUU identified as HTC LargeZip file
Moving 'ROM.zip' temporarily to working folder
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 'dumped_zips'
ExtractZIPs took 12.418 seconds.
Attempting to find suitable keyfile
Find First Encrypted ZIP
Finished: No encrypted zip(s) found, keyfile not needed
KeyFinder took 2.318 seconds.
Decrypting ZIP files
Decrypting (1/7) '01_dmp.zip'
Encryption not found, checking headers...
normal zip, testing...
No errors detected in compressed data of 01_dmp.zip.
unzip test OK, copying file...
... immediate cleanup specified, deleting '01_dmp.zip'
Decrypting (2/7) '02_dmp.zip'
Encryption not found, checking headers...
normal zip, testing...
No errors detected in compressed data of 02_dmp.zip.
unzip test OK, copying file...
... immediate cleanup specified, deleting '02_dmp.zip'
Decrypting (3/7) '03_dmp.zip'
Encryption not found, checking headers...
normal zip, testing...
No errors detected in compressed data of 03_dmp.zip.
unzip test OK, copying file...
... immediate cleanup specified, deleting '03_dmp.zip'
Decrypting (4/7) '04_dmp.zip'
Encryption not found, checking headers...
normal zip, testing...
No errors detected in compressed data of 04_dmp.zip.
unzip test OK, copying file...
... immediate cleanup specified, deleting '04_dmp.zip'
Decrypting (5/7) '05_dmp.zip'
Encryption not found, checking headers...
normal zip, testing...
No errors detected in compressed data of 05_dmp.zip.
unzip test OK, copying file...
... immediate cleanup specified, deleting '05_dmp.zip'
Decrypting (6/7) '06_dmp.zip'
Encryption not found, checking headers...
normal zip, testing...
No errors detected in compressed data of 06_dmp.zip.
unzip test OK, copying file...
... immediate cleanup specified, deleting '06_dmp.zip'
Decrypting (7/7) '07_dmp.zip'
Encryption not found, checking headers...
normal zip, testing...
No errors detected in compressed data of 07_dmp.zip.
unzip test OK, copying file...
... immediate cleanup specified, deleting '07_dmp.zip'
Finished: Successfully decrypted zips to 'decrypted_zips'
DecryptZIPs took 49.846 seconds.
Unzipping decrypted ZIP files
Unzipping decrypted zip: (1/7) 'dec_01_dmp.zip'
Archive: dec_01_dmp.zip
inflating: C:/Users/Matteo/Desktop/recupero/OUT/firmware/android-info.txt
inflating: C:/Users/Matteo/Desktop/recupero/OUT/firmware/android-info2.txt
inflating: C:/Users/Matteo/Desktop/recupero/OUT/firmware/backup_android-info.t
xt
caution: filename not matched: system*.img*
caution: filename not matched: boot.img
caution: filename not matched: boot_*.img
... immediate cleanup specified, deleting 'dec_01_dmp.zip'
Unzipping decrypted zip: (2/7) 'dec_02_dmp.zip'
Archive: dec_02_dmp.zip
inflating: C:/Users/Matteo/Desktop/recupero/OUT/firmware/system.img_00
caution: filename not matched: boot.img
caution: filename not matched: boot_*.img
... immediate cleanup specified, deleting 'dec_02_dmp.zip'
Unzipping decrypted zip: (3/7) 'dec_03_dmp.zip'
Archive: dec_03_dmp.zip
inflating: C:/Users/Matteo/Desktop/recupero/OUT/firmware/system.img_01
caution: filename not matched: boot.img
caution: filename not matched: boot_*.img
... immediate cleanup specified, deleting 'dec_03_dmp.zip'
Unzipping decrypted zip: (4/7) 'dec_04_dmp.zip'
Archive: dec_04_dmp.zip
inflating: C:/Users/Matteo/Desktop/recupero/OUT/firmware/system.img_02
caution: filename not matched: boot.img
caution: filename not matched: boot_*.img
... immediate cleanup specified, deleting 'dec_04_dmp.zip'
Unzipping decrypted zip: (5/7) 'dec_05_dmp.zip'
Archive: dec_05_dmp.zip
inflating: C:/Users/Matteo/Desktop/recupero/OUT/firmware/system.img_03
caution: filename not matched: boot.img
caution: filename not matched: boot_*.img
... immediate cleanup specified, deleting 'dec_05_dmp.zip'
Unzipping decrypted zip: (6/7) 'dec_06_dmp.zip'
Archive: dec_06_dmp.zip
inflating: C:/Users/Matteo/Desktop/recupero/OUT/firmware/system.img_04
caution: filename not matched: boot.img
caution: filename not matched: boot_*.img
... immediate cleanup specified, deleting 'dec_06_dmp.zip'
Unzipping decrypted zip: (7/7) 'dec_07_dmp.zip'
Archive: dec_07_dmp.zip
inflating: C:/Users/Matteo/Desktop/recupero/OUT/firmware/boot_signed.img
caution: filename not matched: system*.img*
caution: filename not matched: boot.img
... immediate cleanup specified, deleting 'dec_07_dmp.zip'
Finished: Successfully unzipped files to 'firmware'
UnzipDecryptedZIPs took 1 minute 6.438 seconds.
Moving system img files
(1/5) moving system.img_00 to system
(2/5) moving system.img_01 to system
(3/5) moving system.img_02 to system
(4/5) moving system.img_03 to system
(5/5) moving system.img_04 to system
Finished: Successfully moved system img files
Attempting to create 'system/system.img'
Multi-part system images (5 parts)
Sparse Image detected, using simg2img
Please be patient, this can take several minutes...
Processing file 'system.img_00'...
Processing file 'system.img_01'...
Processing file 'system.img_02'...
Processing file 'system.img_03'...
Processing file 'system.img_04'...
finished.
Finished: Successfully created 'system/system.img'
Create system.img took 26.569 seconds.
Testing 'system/system.img'...
e2fsck 1.43.5-WIP (17-Feb-2017)
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
system/system.img: 4778/286720 files (0.0% non-contiguous), 967159/1146880 block
s
Finished: 'system/system.img' successfully passed filesystem check
Adding boot.img to the system folder
Moving firmware/boot_signed.img to system/boot.img
Checking android-info.txt
Information extracted from firmware/android-info.txt:
INFO: RUU modelid: 0PJA10000
INFO: RUU mainver: 1.32.401.17
Checking keyfile state
Unencrypted RUU, no keyfile was needed.
Restoring 'ROM.zip' to normal folder
Removing unneeded work folders
INFO: RUU modelid: 0PJA10000
INFO: RUU mainver: 1.32.401.17
Overall process completion time: 2 minutes 51.801 seconds.
Finished: Successfully extracted zip files to
'C:/Users/Matteo/Desktop/recupero/OUT_0PJA_1.32.401.17'
what files should I flash? i have some texts in firmware folder ,boot.img and system.img in system folder
I can not find the instructions to flash but i think fastboot flash boot boot.img and fastboot flash system system.img
????
Locked bootloader? Hey you just need to flash via ruu(same bootloader number) its work for me all the time, plug in to pc before boot to bootloader and flash it and automaticly boot to download mode
maliken333 said:
Locked bootloader? Hey you just need to flash via ruu(same bootloader number) its work for me all the time, plug in to pc before boot to bootloader and flash it and automaticly boot to download mode
Click to expand...
Click to collapse
maliken333 you did not understand what the problem is
for Flippy498:
flashing boot.img log: (but doesn't work in practice,same situation as before)
fastboot flash boot boot.img
target reported max download size of 800000000 bytes
sending 'boot' (30836 KB)...
OKAY [ 2.793s]
writing 'boot'...
(bootloader) HOSD CL#670679
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.292s]
finished. total time: 5.088s
flashing system.img log :
fastboot flash system system.img
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
erasing 'system'...
OKAY [ 0.265s]
sending sparse 'system' 1/5 (698282 KB)...
OKAY [ 50.435s]
writing 'system' 1/5...
(bootloader) HOSD CL#670679
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 27.855s]
sending sparse 'system' 2/5 (771158 KB)...
OKAY [ 59.966s]
writing 'system' 2/5...
(bootloader) HOSD CL#670679
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 30.999s]
sending sparse 'system' 3/5 (770028 KB)...
OKAY [ 58.387s]
writing 'system' 3/5...
(bootloader) HOSD CL#670679
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 31.357s]
sending sparse 'system' 4/5 (772185 KB)...
OKAY [ 59.710s]
writing 'system' 4/5...
(bootloader) HOSD CL#670679
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 30.749s]
sending sparse 'system' 5/5 (695586 KB)...
OKAY [ 57.187s]
writing 'system' 5/5...
(bootloader) HOSD CL#670679
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 27.786s]
finished. total time: 434.723s
same situation as before
If your phone has unlocked bootloader and you atleast still can boot to fastboot your phone is still breathing, i recommend you to flash via sdcard here all your files needed
https://www.google.com/amp/s/forum....nd-backup-ota-update-collection-t3132698/amp/
Thanks for who collected these files. Ciao
maliken333 flash with sd not work for me,please read the previous messages and watch the video.
Why did you decrypt the RUU for firmware 1.32.401.17 and not the one for your current firmware?
Sent from my HTC One M9 using XDA Labs
i'm sure thath the RUU put in decrypter is 3.35.771.12 tried and tried again-->the number in the log is 1.32.401.17(h3g "fake" update?)
I flashed the img files of the RUU( come out of the decrypter) but it did not change anything. Even when i flash the recovery gives a positive result but in practice nothing happens.
Flippy498 strange situation is true?
oemRUU mode not work for me after flashing the images of the the decrypter
there is a button combination to reboot in oemRUU?
trought fastboot every reboots give a white screen with logo and red writes
I'll take a closer look at the RUU. Unfortunately, my download speed seems to be insanely slow, today. I probably won't be able to reply until tomorrow.
Edit: I can't replicate the issue with the wrong version number using this RUU and this version of the decryption tool.
Code:
+++ Welcome to the HTC RUU Decryption Tool 3.6.5 +++
RUU identified as HTC LargeZip 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]: n
* 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]: n
Downloading keyfiles...
Connecting...
Found 45 keyfiles
8 2PYR_keyfile_1.07.401.1.bin 96B ...DOWNLOADED
2 PM66_keyfile_2.22.720.10.bin 96B ...DOWNLOADED
Downloaded 2 new keyfiles.
Download_Keyfiles took 4.242 seconds.
Moving 'D:\Flippy\Downloads\HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64\0PJAIMG_HIMA_UHL_M60_SENSE70_MR_H3G_UK_3.35.771.12_Radio_01.01
Extracting ZIP files
LargeZip format detected, using ruuveal
ruuveal
-------
Large zip format detected containing 8 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
Dumped (copied) zip file to: 08_dmp.zip
Finished: Successfully extracted zip files to 'dumped_zips'
ExtractZIPs took 13.285 seconds.
Attempting to find suitable keyfile
Find First Encrypted ZIP
Encrypted zip to be used for testing: '01_dmp.zip'
No proper keyfile, trying known keys instead...
Testing keyfile '0P3P_keyfile_4.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Processing ZIP... 32768/174673476
Testing keyfile '0P4E_keyfile_2.14.631.15.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Processing ZIP... 32768/174673476
Testing keyfile '0P6B_keyfile_1.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Processing ZIP... 32768/174673476
Testing keyfile '0P6B_keyfile_6.20.654.3.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Processing ZIP... 32768/174673476
Testing keyfile '0P6B_keyfile_6.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Processing ZIP... 32768/174673476
Testing keyfile '0P8B_keyfile_2.18.401.3.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Processing ZIP... 32768/174673476
Testing keyfile '0P9C_keyfile_1.59.1402.11.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Processing ZIP... 32768/174673476
Testing keyfile '0P9C_keyfile_3.12.709.5.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Processing ZIP... 32768/174673476
Testing keyfile '0PAJ_keyfile_1.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Processing ZIP... 32768/174673476
Testing keyfile '0PCV_keyfile_1.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Processing ZIP... 32768/174673476
Testing keyfile '0PE6_keyfile_1.51.401.5.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Processing ZIP... 32768/174673476
Testing keyfile '0PFH_keyfile_2.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Processing ZIP... 32768/174673476
Testing keyfile '0PFH_keyfile_4.11.401.1.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Processing ZIP... 32768/174673476
Testing keyfile '0PFJ_keyfile_2.10.401.2.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Processing ZIP... 32768/174673476
Testing keyfile '0PGZ_keyfile_1.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Processing ZIP... 32768/174673476
Testing keyfile '0PHC_keyfile_1.18.401.4.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Processing ZIP... 32768/174673476
Testing keyfile '0PHC_keyfile_2.10.425.3.bin'...
ruuveal
-------
Invalid zip file - aborting!
failed to decrypt zip file!
Processing ZIP... 32768/174673476
Testing keyfile '0PJA_keyfile_2.bin'...
ruuveal
-------
Processing ZIP... 32768/174673476Decrypted RUU (zip) written to: tmpzip.zip
Archive: tmpzip.zip
testing: android-info.txt OK
testing: apppreload.img OK
testing: aboot_signed.img OK
testing: cota.img OK
testing: gpt_main_32g.img OK
testing: gpt_main_64g.img OK
testing: android-info2.txt OK
testing: sbl1-8994-1.img OK
testing: sdi.img OK
testing: hosd_signed.img OK
testing: rpm-8994-1.img OK
testing: pmic-8994-1.img OK
testing: boot_signed.img OK
testing: recovery_signed.img OK
testing: adsp.img OK
testing: cpe.img OK
testing: radio.img OK
testing: rcdata.img OK
testing: modem_st1.img OK
testing: modem_st2.img OK
testing: tz-8994-1.img OK
testing: hyp-8994-1.img OK
testing: pg2fs_ship_signkey.img OK
testing: sensor_hub.img OK
testing: tp_SYN3351.img OK
testing: tp_MXM11876.img OK
testing: cir.img OK
testing: splash1.nb0 OK
testing: backup_android-info.txt OK
No errors detected in compressed data of tmpzip.zip.
INFO: keyfile passed all tests
Finished: Successfully found decryption key, copied to 'tmp/use_keyfile.bin'
KeyFinder took 14.284 seconds.
Decrypting ZIP files
Decrypting (1/8) '01_dmp.zip'
Encrypted zip detected, running ruuveal...
ruuveal
-------
Processing ZIP... 32768/174673476Decrypted RUU (zip) written to: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/decrypted_zips/dec_01_dmp.zip
... immediate cleanup specified, deleting '01_dmp.zip'
Decrypting (2/8) '02_dmp.zip'
Encrypted zip detected, running ruuveal...
ruuveal
-------
Processing ZIP... 32768/375697238Decrypted RUU (zip) written to: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/decrypted_zips/dec_02_dmp.zip
... immediate cleanup specified, deleting '02_dmp.zip'
Decrypting (3/8) '03_dmp.zip'
Encrypted zip detected, running ruuveal...
ruuveal
-------
Processing ZIP... 32768/506686320Decrypted RUU (zip) written to: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/decrypted_zips/dec_03_dmp.zip
... immediate cleanup specified, deleting '03_dmp.zip'
Decrypting (4/8) '04_dmp.zip'
Encrypted zip detected, running ruuveal...
ruuveal
-------
Processing ZIP... 32768/483441437Decrypted RUU (zip) written to: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/decrypted_zips/dec_04_dmp.zip
... immediate cleanup specified, deleting '04_dmp.zip'
Decrypting (5/8) '05_dmp.zip'
Encrypted zip detected, running ruuveal...
ruuveal
-------
Processing ZIP... 32768/391545061Decrypted RUU (zip) written to: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/decrypted_zips/dec_05_dmp.zip
... immediate cleanup specified, deleting '05_dmp.zip'
Decrypting (6/8) '06_dmp.zip'
Encrypted zip detected, running ruuveal...
ruuveal
-------
Processing ZIP... 32768/375197833Decrypted RUU (zip) written to: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/decrypted_zips/dec_06_dmp.zip
... immediate cleanup specified, deleting '06_dmp.zip'
Decrypting (7/8) '07_dmp.zip'
Encrypted zip detected, running ruuveal...
ruuveal
-------
Processing ZIP... 32768/70183328Decrypted RUU (zip) written to: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/decrypted_zips/dec_07_dmp.zip
... immediate cleanup specified, deleting '07_dmp.zip'
Decrypting (8/8) '08_dmp.zip'
Encrypted zip detected, running ruuveal...
ruuveal
-------
Processing ZIP... 32768/13449969Decrypted RUU (zip) written to: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/decrypted_zips/dec_08_dmp.zip
... immediate cleanup specified, deleting '08_dmp.zip'
Finished: Successfully decrypted zips to 'decrypted_zips'
DecryptZIPs took 25.497 seconds.
Unzipping decrypted ZIP files
Unzipping decrypted zip: (1/8) 'dec_01_dmp.zip'
Archive: dec_01_dmp.zip
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/android-info.txt
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/apppreload.img
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/aboot_signed.img
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/cota.img
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/gpt_main_32g.img
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/gpt_main_64g.img
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/android-info2.txt
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/sbl1-8994-1.img
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/sdi.img
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/hosd_signed.img
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/rpm-8994-1.img
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/pmic-8994-1.img
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/boot_signed.img
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/recovery_signed.img
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/adsp.img
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/cpe.img
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/radio.img
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/rcdata.img
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/modem_st1.img
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/modem_st2.img
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/tz-8994-1.img
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/hyp-8994-1.img
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/pg2fs_ship_signkey.img
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/sensor_hub.img
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/tp_SYN3351.img
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/tp_MXM11876.img
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/cir.img
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/splash1.nb0
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/backup_android-info.txt
... immediate cleanup specified, deleting 'dec_01_dmp.zip'
Unzipping decrypted zip: (2/8) 'dec_02_dmp.zip'
Archive: dec_02_dmp.zip
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/system.img_00
... immediate cleanup specified, deleting 'dec_02_dmp.zip'
Unzipping decrypted zip: (3/8) 'dec_03_dmp.zip'
Archive: dec_03_dmp.zip
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/system.img_01
... immediate cleanup specified, deleting 'dec_03_dmp.zip'
Unzipping decrypted zip: (4/8) 'dec_04_dmp.zip'
Archive: dec_04_dmp.zip
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/system.img_02
... immediate cleanup specified, deleting 'dec_04_dmp.zip'
Unzipping decrypted zip: (5/8) 'dec_05_dmp.zip'
Archive: dec_05_dmp.zip
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/system.img_03
... immediate cleanup specified, deleting 'dec_05_dmp.zip'
Unzipping decrypted zip: (6/8) 'dec_06_dmp.zip'
Archive: dec_06_dmp.zip
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/system.img_04
... immediate cleanup specified, deleting 'dec_06_dmp.zip'
Unzipping decrypted zip: (7/8) 'dec_07_dmp.zip'
Archive: dec_07_dmp.zip
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/system.img_05
... immediate cleanup specified, deleting 'dec_07_dmp.zip'
Unzipping decrypted zip: (8/8) 'dec_08_dmp.zip'
Archive: dec_08_dmp.zip
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/dzdata_16g.hdr
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/dzdata_16g.img
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/dzdata_32g.hdr
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/dzdata_32g.img
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/dzdata_64g.hdr
inflating: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT/firmware/dzdata_64g.img
... immediate cleanup specified, deleting 'dec_08_dmp.zip'
Finished: Successfully unzipped files to 'firmware'
UnzipDecryptedZIPs took 1 minute 52.573 seconds.
Moving system img files
(1/6) moving system.img_00 to system
(2/6) moving system.img_01 to system
(3/6) moving system.img_02 to system
(4/6) moving system.img_03 to system
(5/6) moving system.img_04 to system
(6/6) moving system.img_05 to system
Finished: Successfully moved system img files
Attempting to create 'system/system.img'
Multi-part system images (6 parts)
Sparse Image detected, using simg2img
Please be patient, this can take several minutes...
Processing file 'system.img_00'...
Processing file 'system.img_01'...
Processing file 'system.img_02'...
Processing file 'system.img_03'...
Processing file 'system.img_04'...
Processing file 'system.img_05'...
finished.
Finished: Successfully created 'system/system.img'
Create system.img took 35.782 seconds.
Testing 'system/system.img'...
e2fsck 1.43.5-WIP (17-Feb-2017)
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
system/system.img: 4936/286720 files (0.0% non-contiguous), 1067079/1146880 blocks
Finished: 'system/system.img' successfully passed filesystem check
Adding boot.img to the system folder
Copying firmware/boot_signed.img to system/boot.img
Checking android-info.txt
Information extracted from firmware/android-info.txt:
INFO: RUU modelid: 0PJA10000
INFO: RUU mainver: 3.35.771.12
Checking keyfile state
Keyfile used already matches one in the keyfiles folder.
Restoring 'D:\Flippy\Downloads\HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64\0PJAIMG_HIMA_UHL_M60_SENSE70_MR_H3G_UK_3.35.771.12_Radio_01
Removing unneeded work folders
INFO: RUU modelid: 0PJA10000
[COLOR="Red"][B]INFO: RUU mainver: 3.35.771.12[/B][/COLOR]
Overall process completion time: 3 minutes 33.099 seconds.
Finished: Successfully extracted zip files to
'D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT_0PJA_3
Writing logfile to: D:/Flippy/Downloads/HTC_RUU_Decrypt_Tool_3.6.5-WINDOWS64/OUT_0PJA_3.35.771.12/RUU_Decrypt_LOG-0PJA10000_3.35.771.12_2017-10-15_110044.txt