[HowTo] Rooting Philips HMP8100 Player by ShaunMT's modded uImage_recovery

[fleet_tw]

# Thanks to ShaunMT for the great work #

[Disclaimer]
Do this on your own risks.

[Preparation]
Clean SD Card ... x1


[Rooting]

1. Download the V72 Card flash ROM from Philips website:
http://download.p4c.philips.com/file...93_fus_aen.zip

2. Unzip it to root directory of the SD Card *Without* update.zip and uImage_recovery

3. Download the Root Package from here(Thanks to ShaunMT):
http://www.freak-tab.de/ShaunMT/Kyser_Root-signed.zip
and download the modded uImage_recovery from here(Thanks to ShaunMT):
http://www.freak-tab.de/ShaunMT/HMP8100/HMP8100_SMT_Mod_Recovery.7z

4. Rename the Root Package to update.zip then extract the modded uImage_recovery and copy the two files to root directory of the SD Card.

5. Unplug your HMP8100, insert the SD Card then plug the power cord back. SD Flashing shoud be in progress shortly. watch the progress bar, when finished, the screen will go blank and right now you need to pull out the SD card otherwise the SD Flashing will loop.

6. Now you get Root access.

7. (*Optional*) Pick up a root access management tool like SuperSU, Superuser etc.

8. (*Optional*) Put "qemu.hw.mainkeys=1" in the bottom of system/build.prop to remove the virtual button bar.

[shaunmt]

# Thanks to ShaunMT for the great work #

[Disclaimer]
Do this on your own risks.

[Preparation]
Clean SD Card ... x1


[Rooting]

1. Download the V72 Card flash ROM from Philips website:
http://download.p4c.philips.com/file...93_fus_aen.zip

2. Unzip it to root directory of the SD Card *Without* update.zip and uImage_recovery

3. Download the Root Package from here(Thanks to ShaunMT):
http://www.freak-tab.de/ShaunMT/Kyser_Root-signed.zip
and download the modded uImage_recovery from here(Thanks to ShaunMT):
http://www.freak-tab.de/ShaunMT/HMP8100/HMP8100_SMT_Mod_Recovery.7z

4. Rename the Root Package to update.zip then extract the modded uImage_recovery and copy the two files to root directory of the SD Card.

5. Unplug your HMP8100, insert the SD Card then plug the power cord back. SD Flashing shoud be in progress shortly. watch the progress bar, when finished, the screen will go blank and right now you need to pull out the SD card otherwise the SD Flashing will loop.

6. Now you get Root access.

7. (*Optional*) Pick up a root access management tool like SuperSU, Superuser etc.

8. (*Optional*) Put "qemu.hw.mainkeys=1" in the bottom of system/build.prop to remove the virtual button bar.

You might want to do some additional testing.

If you remove the factory_update_param.aml file, then the modified recovery should boot normally and allow you to manually choose any .zip file to attempt flashing.

Using this method, all you need on the SD card are the uImage_recovery and the kyzer_root.zip.

Also, if anything goes wrong, you can flash the update.zip from the official firmware to return to stock.

ShaunMT

[fleet_tw]

You might want to do some additional testing.

If you remove the factory_update_param.aml file, then the modified recovery should boot normally and allow you to manually choose any .zip file to attempt flashing.

Using this method, all you need on the SD card are the uImage_recovery and the kyzer_root.zip.

Also, if anything goes wrong, you can flash the update.zip from the official firmware to return to stock.

ShaunMT

I've tried to remove factory_update_param.aml on SD to enter recovery, but it not works. it reboots normally when without the .aml file.

[shaunmt]

I've tried to remove factory_update_param.aml on SD to enter recovery, but it not works. it reboots normally when without the .aml file.

That's interesting... the recovery must hang when it tries to load the user interface... can't think of any reason why it should though, considering it is the stock recovery, with no mods, aside from the signature key.

ShaunMT

[Phatohoh]

# Thanks to ShaunMT for the great work #

[Disclaimer]
Do this on your own risks.

[Preparation]
Clean SD Card ... x1


[Rooting]

1. Download the V72 Card flash ROM from Philips website:
http://download.p4c.philips.com/file...93_fus_aen.zip

2. Unzip it to root directory of the SD Card *Without* update.zip and uImage_recovery

3. Download the Root Package from here(Thanks to ShaunMT):
http://www.freak-tab.de/ShaunMT/Kyser_Root-signed.zip
and download the modded uImage_recovery from here(Thanks to ShaunMT):
http://www.freak-tab.de/ShaunMT/HMP8100/HMP8100_SMT_Mod_Recovery.7z

4. Rename the Root Package to update.zip then extract the modded uImage_recovery and copy the two files to root directory of the SD Card.

5. Unplug your HMP8100, insert the SD Card then plug the power cord back. SD Flashing shoud be in progress shortly. watch the progress bar, when finished, the screen will go blank and right now you need to pull out the SD card otherwise the SD Flashing will loop.

6. Now you get Root access.

7. (*Optional*) Pick up a root access management tool like SuperSU, Superuser etc.

8. (*Optional*) Put "qemu.hw.mainkeys=1" in the bottom of system/build.prop to remove the virtual button bar.

Hi fleet_tw,

I cannot root HMP8100 by using the method provided (like attachment)
Would you please advise what's going wrong?
Many thanks!!!

[summervin]

HMP8100/98

# Thanks to ShaunMT for the great work #

[Disclaimer]
Do this on your own risks.

[Preparation]
Clean SD Card ... x1


[Rooting]

1. Download the V72 Card flash ROM from Philips website:
http://download.p4c.philips.com/file...93_fus_aen.zip

2. Unzip it to root directory of the SD Card *Without* update.zip and uImage_recovery

3. Download the Root Package from here(Thanks to ShaunMT):
http://www.freak-tab.de/ShaunMT/Kyser_Root-signed.zip
and download the modded uImage_recovery from here(Thanks to ShaunMT):
http://www.freak-tab.de/ShaunMT/HMP8100/HMP8100_SMT_Mod_Recovery.7z

4. Rename the Root Package to update.zip then extract the modded uImage_recovery and copy the two files to root directory of the SD Card.

5. Unplug your HMP8100, insert the SD Card then plug the power cord back. SD Flashing shoud be in progress shortly. watch the progress bar, when finished, the screen will go blank and right now you need to pull out the SD card otherwise the SD Flashing will loop.

6. Now you get Root access.

7. (*Optional*) Pick up a root access management tool like SuperSU, Superuser etc.

8. (*Optional*) Put "qemu.hw.mainkeys=1" in the bottom of system/build.prop to remove the virtual button bar.

Hi,

May I know is it possible to install android 4.4 Kitkat onto this media box? Thanks.

[MiCmAsTa]

# Thanks to ShaunMT for the great work #

[Disclaimer]
Do this on your own risks.

[Preparation]
Clean SD Card ... x1


[Rooting]

1. Download the V72 Card flash ROM from Philips website:
http://download.p4c.philips.com/file...93_fus_aen.zip

2. Unzip it to root directory of the SD Card *Without* update.zip and uImage_recovery

3. Download the Root Package from here(Thanks to ShaunMT):
http://www.freak-tab.de/ShaunMT/Kyser_Root-signed.zip
and download the modded uImage_recovery from here(Thanks to ShaunMT):
http://www.freak-tab.de/ShaunMT/HMP8100/HMP8100_SMT_Mod_Recovery.7z

4. Rename the Root Package to update.zip then extract the modded uImage_recovery and copy the two files to root directory of the SD Card.

5. Unplug your HMP8100, insert the SD Card then plug the power cord back. SD Flashing shoud be in progress shortly. watch the progress bar, when finished, the screen will go blank and right now you need to pull out the SD card otherwise the SD Flashing will loop.

6. Now you get Root access.

7. (*Optional*) Pick up a root access management tool like SuperSU, Superuser etc.

8. (*Optional*) Put "qemu.hw.mainkeys=1" in the bottom of system/build.prop to remove the virtual button bar.

Unable to root using this method. Having the same problem as Phatohoh

[shaunmt]

Sorry guys... I made this modified recovery for the developer who posted the OP. I don't know if he is still supporting it. I am unable to offer much support, because I don't have this device.

I might be able to make some suggestions if you can advise what ROM and android version you are currently running and describe the problem in more detail.

ShaunMT

[MiCmAsTa]

Sorry guys... I made this modified recovery for the developer who posted the OP. I don't know if he is still supporting it. I am unable to offer much support, because I don't have this device.

I might be able to make some suggestions if you can advise what ROM and android version you are currently running and describe the problem in more detail.

ShaunMT

It's currently running on 4.1.1 Jelly Bean Kernel Version 3.0.8.

Thanks in advance shaunmt

[shaunmt]

It's currently running on 4.1.1 Jelly Bean Kernel Version 3.0.8.

Thanks in advance shaunmt

I just had another look at Phatohoh's post... and his photo...

If verification is failing, it means the security key in the update signature doesn't match the security key in the recovery signature.

This is either because you are using the stock recovery, which was signed with secret propriety keys by the manufacturer and can only be used to install official updates from the manufacturer... or, if you are using the modified recovery, the recovery is looking for the standard google test keys and your update file was signed with some other key.

Verify you followed the instructions correctly. There is no way to visually tell the difference between the stock recovery and the modified recovery. They look exactly the same, but check for different keys when you attempt to install an update.

Assuming you followed the instructions correctly, the update you are trying to install won't work with the modified recovery.

[MiCmAsTa]

I just had another look at Phatohoh's post... and his photo...

If verification is failing, it means the security key in the update signature doesn't match the security key in the recovery signature.

This is either because you are using the stock recovery, which was signed with secret propriety keys by the manufacturer and can only be used to install official updates from the manufacturer... or, if you are using the modified recovery, the recovery is looking for the standard google test keys and your update file was signed with some other key.

Verify you followed the instructions correctly. There is no way to visually tell the difference between the stock recovery and the modified recovery. They look exactly the same, but check for different keys when you attempt to install an update.

Assuming you followed the instructions correctly, the update you are trying to install won't work with the modified recovery.

Then I guess its GAME OVER for this! Thanks shaunmt