Custom ROMs

bitswitch

Member
Jul 24, 2010
8
5
0
Looks like the Devour has a locked bootloader too.
I found this while digging around the file system.

install-recovery.sh
Code:
#!/system/bin/sh
if ! applypatch -c MTD:recovery:2048:d054cb346a1277afe19a03ccce64a6d2c0403146; then
  log -t recovery "Installing new recovery image"
  applypatch MTD:boot:2406400:46fc9b47694c4a33a0b4371729c684ddaa4c7ee8 MTD:recovery df64964e779ef8273c78acde064cf0a9aecfb6f8 2664448 46fc9b47694c4a33a0b4371729c684ddaa4c7ee8:/system/recovery-from-boot.p
else
  log -t recovery "Recovery image already installed"
fi

This looks similar to the files found on the Droid X.
It does some SHA1 checking and looks like it replaces the recovery image if the check fails.
 
What does this mean for our future rom development? Is there enough similarities between the droid x and devour for us to use a rom made for the droid x?
 

Trending Posts

Forum statistics

Threads
962,061
Messages
6,988,907
Members
3,164,766
Latest member
nafizahp3