1. bitswitch's Avatar
    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.
    07-25-2010 06:46 PM
  2. hoganistrash's Avatar
    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?
    07-26-2010 01:52 AM
  3. snowboarderxd1's Avatar
    FRF91 Froyo Running on Motorola Milestone - Droid Life: A Droid Community Blog
    well the milestone has a encrypted bootloader and now has a custom Rom does that mean theres still hope for the Devour? Also, since the droid X community is so big and the droidX is similar to the Devour when a custom rom is found for the droid X will the same way be used to load it onto the devour?
    07-27-2010 10:18 AM
LINK TO POST COPIED TO CLIPBOARD