Continuation of
https://xdaforums.com/showpost.php?p=78317447&postcount=2084
You need to know the several partitions. For that you issue a command from a rooted adb access or a rooted shell on the unit, and do like:
Code:
ls -l /dev/block/platform/ff0f0000.dwmmc/by-name/
Among a lot of other partitions it will mention:
Code:
recovery -> /dev/block/mmcblk2p7
When making a backup of the stock PX5 recovery image you need rooted adb access or a rooted shell on the unit, and do like:
Code:
dd if=/dev/block/mmcblk2p7 of=/sdcard/stock-px5-recovery.img
Then verify it:
Code:
sha1sum /sdcard/stock-px5-recovery.img
This should give you some sha1sum. Then do the dd and verify again and see if you get the same sha1sum.
When writing a recovery image, you first verify its sha1sum like:
Code:
sha1sum /sdcard/my_custom_recovery.img
And to write the recovery to its recovery partition you do something like:
Code:
dd if=/sdcard/my_custom_recovery.img of=/dev/block/mmcblk2p7
Followed by a verify:
Code:
dd if=/dev/block/mmcblk2p7 of=/sdcard/check-my_custom_recovery.img
sha1sum /sdcard/check-my_custom_recovery.img
And of course both sha1sums should be equal. Then you can remove the /sdcard/check-my_custom_recovery.img
Then the proof of the pudding: try to reboot to the TWRP recovery.
etc. etc. And that is only to find the correct recovery image. Then the start for the "quest" of the custom ROM starts with multiple flashes, errors, probably soft-bricks. etc.
BE VERY CAREFUL!! And check my commands for yourself. I looked very carefuly at it, but everyone can make mistakes.
I will not do this myself.
