Dear fellow developers and technicians,
I have a serious reason for that i do contact you. It is about a uncommercial forensic investigation
attempt on important evidence data and photographies on a broken mobile. The mobile is a
HTC Wildfire S, display is readable, touch interface is broken, hboot locked and data integrity is
untouched. So called experts deny the recoverability of the device while i disagree to that.
When i power on the device by pressing [volume down + power] the following information
about the device shows up:
------------------------------------------------------------------------------------------------------------------
*** LOCKED ***
MARVEL PVT SHIP S-ON RL
HBOOT-1.09.0099
MICROP-0451
RADIO-7.57.39.10M
Feb 8 2012, 18:29:31
FASTBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
BOOTLOADER
REBOOT
REBOOT Downloader
POWER DOWN
------------------------------------------------------------------------------------------------------------------
I successfully dumped the token via the commandline and fastboot and obtained the unlock
key (unlock_key.bin) for the device from HTCDev.com. The problem is that i am able to unlock
the bootloader (hboot) to gain remote access or data recovery while accepting the loss of
data caused by the data privacy security measurements. Unlocking the bootloader (hboot)
forces to accept factory reset with no chance to circumvent at user input/output level. I've
already tried to kickstart a custom recovery image what logically fails with a improperly
certificate signed recovery image due to the locked bootloader.
As i did a lot of forensic works in information technologies in the past i know that it is possible
to "clone" the signing of the recovery image so that it goes through as if it was a regular update.
In the past i was using SigTool (Google banned?, not MathLab SigTool or whatever SignTool,
SignTool.jar, SIS SignTool, or else). Also i did lost my own utility for signature processing due to
loss of data on my workstation. I do not have access to a information repository with needed
information about signing and also time is short.
Solution Approach is as following:
+ download custom recovery system image that is compatible with a unlocked bootloader (hboot)
+ download tool to dump/clone/apply certification process
+ download regular HTC bootloader (hboot) update
+ dump certificate from signed update
+ apply signature to custom recovery system image that is compatible with a unlocked bootloader (hboot)
+ flash clone signed custom recovery system image
Any clear answer or complete solution approaches ?
Please help!
I have a serious reason for that i do contact you. It is about a uncommercial forensic investigation
attempt on important evidence data and photographies on a broken mobile. The mobile is a
HTC Wildfire S, display is readable, touch interface is broken, hboot locked and data integrity is
untouched. So called experts deny the recoverability of the device while i disagree to that.
When i power on the device by pressing [volume down + power] the following information
about the device shows up:
------------------------------------------------------------------------------------------------------------------
*** LOCKED ***
MARVEL PVT SHIP S-ON RL
HBOOT-1.09.0099
MICROP-0451
RADIO-7.57.39.10M
Feb 8 2012, 18:29:31
FASTBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
BOOTLOADER
REBOOT
REBOOT Downloader
POWER DOWN
------------------------------------------------------------------------------------------------------------------
I successfully dumped the token via the commandline and fastboot and obtained the unlock
key (unlock_key.bin) for the device from HTCDev.com. The problem is that i am able to unlock
the bootloader (hboot) to gain remote access or data recovery while accepting the loss of
data caused by the data privacy security measurements. Unlocking the bootloader (hboot)
forces to accept factory reset with no chance to circumvent at user input/output level. I've
already tried to kickstart a custom recovery image what logically fails with a improperly
certificate signed recovery image due to the locked bootloader.
As i did a lot of forensic works in information technologies in the past i know that it is possible
to "clone" the signing of the recovery image so that it goes through as if it was a regular update.
In the past i was using SigTool (Google banned?, not MathLab SigTool or whatever SignTool,
SignTool.jar, SIS SignTool, or else). Also i did lost my own utility for signature processing due to
loss of data on my workstation. I do not have access to a information repository with needed
information about signing and also time is short.
Solution Approach is as following:
+ download custom recovery system image that is compatible with a unlocked bootloader (hboot)
+ download tool to dump/clone/apply certification process
+ download regular HTC bootloader (hboot) update
+ dump certificate from signed update
+ apply signature to custom recovery system image that is compatible with a unlocked bootloader (hboot)
+ flash clone signed custom recovery system image
Any clear answer or complete solution approaches ?
Please help!
xda-developers
One of five volunteers on placebo with these qualities was detected with
RépondreSupprimerdiabetes.
In the case of the Lipitor claim, several of the original grievances were submitted in the Area of South
RépondreSupprimerCarolina, which is where the brand-new Lipitor MDL lies.
That is actually a resting ailment in which a person finds
RépondreSupprimerthis challenging up to rest or even to remain sleeping during the course
of nighttime.