HTC One M9 support addition #88
Comments
|
They do seem to be encrypted, in a way that a lot of the images, including the likes of system.img, are hidden. |
|
The images can all be extracted using 7zip 9.3x versions with the alternative "open with" command - inside these zips are 7 sub-zips which contain all images and can just be pulled out. The header of the zip is either wrong, does not follow standards or something. For this reason, a new htc_fastboot.exe is required to flash these too. The 2014 htc_fastboot is not able to parse the full zip. Some versions even crash. |
|
@Sneakyghost Indeed. I've fixed a bug in ruuveal preventing the use of the dump option in this scenario in 8eb471c, so now this works:- $ ./ruuveal -D 0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.8_Radio_01.01_U11440261_56.02.50306G_2_F_release_425571_signed.zip out.zip ruuvealLarge zip format detected containing 7 zipfile(s) |
|
Thank you, Sir. |
The HTC One M9 now uses appsboot instead of hboot (aboot) and it looks like the key is not stored in aboot anymore - i attempted a key extraction with bruutveal and got some fail message which i don't recall right now. However, talks around the xda-forum have been that the key might now live somewhere else, possibly in recovery.
If you could kindly look into this please?
A RUU can be found here: http://forum.xda-developers.com/showpost.php?p=59557045&postcount=1
The aboot.img for 1.32.401.8 RUU is here: https://drive.google.com/file/d/0BzqWaJywIe10TnBWVUJNR0NjajA/view?usp=sharing
Notice: it appears the RUU's on that post are signed but not encrypted - I do expect HTC to go back to encryption though. These RUU's are initial release versions and might still be different.
Thanks.
The text was updated successfully, but these errors were encountered: