DO NOT FLASH CWM - If you have FW v1.02
If FW is v1.01, 1.00, 0.94, Check for any of the following files on your Scroll: - (they may not be there - but check 1st)
1. /system/etc/install-recovery.sh
2. /system/recovery-from-boot.p
RENAME - Them 1st (or delete them, but renaming them, means you still have a local copy if they are ever needed in the future.) Otherwise problems will occur when flashing CWM - (More so with scrolls that have FW v1.02) - You will need to have your Scroll rooted to do this and use a program like root explorer.
NOTE - This might not be the main cause of problems with flashing CWM on to scrolls with FM v1.02 - But it is best not to have them there, named as they are at present on you scroll when flashing CWM - Or even after you have flashed CWM, regardless of your firmware version)
INFO - Below is just some background information on what those files do.
### Start of info ###
In the init.rc file there is this service call line:
- Code: Select all
service flash_recovery /system/etc/install-recovery.sh
oneshot
Each time the OS boots it therefore runs /system/etc/install-recovery.sh
- Code: Select all
#!/system/bin/sh
if ! applypatch -c MTD:recovery:2048:039c557a915d0952eba272ceddb5824efff621ad; then
log -t recovery "Installing new recovery image"
applypatch MTD:boot:5165056:2da0a439bb088865736290b16e8277d47cfd5d6d MTD:recovery 1975102594023372b9758eb4e3dcd288564e6971 5423104 2da0a439bb088865736290b16e8277d47cfd5d6d:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
What this does is look at the first 2K block of the recovery partition image and take a SHA1 has of it. If the hash isn't the one shown then it calls "applypatch". Applypatch uses the first 2,875,392 bytes of the boot partition image (headers, kernel, and ramdisk) and the contents of /system/recovery-from-boot.p (a "diff" file) to mathematically reconstruct an image of the recovery partition.
### End of info ###
I hope this post helps