• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

Modded recovery and boot images

Search This thread

Autarkis

Senior Member
Dec 12, 2008
97
0
Basel
It's awesome, I've got root despite having had RC30, having sucessfully applied DREAIMG.img to my phone. :) THANKS GUYS! I want to bear all your children! (Unfortunately I'm male, so there's going to be problems, and maybe JesusFreke would be pissed as well ;) - just kidding, related stuff into my PM box please ;))

Nowww... I'm going for JesusFreke's Mod. For that I've got to install recovery_testkeys.img.

I've got a file /system/recovery.img , I've done all the instructions correctly (I hope). The file is persistent, meaning it remains there even though I reboot the phone.

But, even though I repeated the copying and flashing instructions multiple times and rebooted from flash_image recovery recovery.img directly into the recovery screen (that's POWER + hold CAMERA, right?) as well as into the normal boot process, the image doesn't appear to get flashed by init.rc. :confused: Meaning, it won't say "test-keys" or even boot up the Skateboarding Android (which I some way or another assume it should).

I'm probably either missing a step, missing the information that this won't work, or booting into the wrong kind of screen with the wrong combination of keys. I'm 100% certain that the /system/recovery.img is correct, because I pulled it back via adb and compared md5sums.

Any help would be appreciated, but again, thanks for bringing me this far!
 

jashsu

Senior Member
Nov 15, 2008
1,860
20
Thanks! I'm totally embarassed now. :eek: Now it's showing a triangle with a big exclamation mark. That doesn't seem too well... can you point me to a thread where recovery mode basics are explained? I don't want to clutter this thread... thanks.
That is what the recovery looks like

ALT+L to show text
ALT+S to flash update.zip
ALT+W to wipe /cache and /data

On modified recovery v1.3 and up:
ALT+B to backup nand for nandroid usage
 

JesusFreke

Inactive Recognized Developer
Oct 23, 2008
736
54
Dallas
Thanks! I'm totally embarassed now. :eek: Now it's showing a triangle with a big exclamation mark. That doesn't seem too well... can you point me to a thread where recovery mode basics are explained? I don't want to clutter this thread... thanks.

Press alt+l to turn on text (not needed on JFv1.3, but needed on anything prior), and then alt+s to apply an update (must be named update.zip on your sdcard)
 

andyandrwew

Senior Member
Jun 23, 2008
147
5
Lawrenceville, GA
Code:
D:\Android\AndroidMod>adb push boot_nosecure.img /data/local/boot.img
939 KB/s (0 bytes in 1533952.001s)

D:\Android\AndroidMod>adb shell
$ su
su
# flash_image boot /data/local/boot.img
flash_image boot /data/local/boot.img
# rm /data/local/boot.img
rm /data/local/boot.img
#

Now reboot the phone and let it boot normally. If the boot image was corrupted, it will boot into recovery mode instead. You can use the included update zip file to reload the original RC29 boot image.

Otherwise, if it boots up normally, open a command prompt however you like (telnet, adb, terminal emulator app, etc.) and type "getprop ro.secure". If it says 0, then you're running the modified boot image. Otherwise, if it says 1, you're still running the original boot image.

if you are going to install RC30 v1.3 then the boot image is automatically installed -WOW thanx JF- and oh yeh i got it running thanx to every1 that helped me


Jesus Freke- Are you developing for Android because you seem to see a lot of holes in the OS?
 

JesusFreke

Inactive Recognized Developer
Oct 23, 2008
736
54
Dallas
if you are going to install RC30 v1.3 then the boot image is automatically installed -WOW thanx JF- and oh yeh i got it running thanx to every1 that helped me


Jesus Freke- Are you developing for Android because you seem to see a lot of holes in the OS?

I do it because I enjoy it
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Here is a zip file containing a modified recovery and boot image, as well as a few other things:
    http://rapidshare.com/files/166164961/AndroidMod.zip
    http://jf.nyquil.org/AndroidMod.zip
    http://android-dls.com/forum/index.php?f=24&t=191&rb_v=viewtopic (see post for actual link to file)


    NOTE: if you need a complete RC30 to v1.3 guide, see this page.


    The recovery image (recovery_testkeys.img) uses the test keys that are distributed with the android platform source. This means that an OTA update or an update.zip update must be signed with the test key in order for it to install. In other words, it will no longer install OTA updates from t-mobile. You don't want them stealing back root access from you now do you? :).

    I've also included the test keys and the SignApk.jar tool, so you can sign your own update scripts (for use only with the modified recovery image). You can resign any image, even if it has been signed before. So for example, if you needed to install an "official" t-mobile update, you must re-sign it with the test keys first.

    Another bonus in this recovery image is that ADB is enabled while in recovery mode. You can't adb into a shell (no sh binary), but you can at least use it to push and pull files from the device. For example, you could push an update.zip file to the sdcard.


    The boot image (boot_nosecure.img) has been modified so that adb has root access by default. So when you do an adb shell, you automatically get a root shell. You can remount the system image using adb, and then push files directly to the system partition.


    Finally, the "update - Restore Original RC29 Boot Image.zip" file is an update.zip file signed with the test keys, which will restore your boot partition back to the stock RC29 image. Useful if you accidentally hose your boot partition..



    To install the recovery image onto your phone:

    Code:
    D:\Android\AndroidMod>adb push recovery_testkeys.img /data/local/recovery.img
    912 KB/s (0 bytes in 1767424.001s)
    
    D:\Android\AndroidMod>adb shell
    $ su
    su
    # mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
    mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
    # cd /system
    cd /system
    # cat /data/local/recovery.img > recovery.img
    cat /data/local/recovery.img > recovery.img
    # flash_image recovery recovery.img
    flash_image recovery recovery.img
    #


    Note: You must place the recovery image at /system/recovery.img. the init.rc boot script automatically flashes the recovery partition with that file every time you boot up the phone.

    At this point, it's probably a good idea to reboot the phone into recovery mode, and make sure it loads OK. If the recovery image is corrupt somehow, it will throw you back into SPL mode (the multi-color bootloader screen). If that happens, just boot the phone normally, and reflash recovery image.

    Once it boots into recovery mode, press alt+L, and the next to top line of text should say something like "using test keys.". If it doesn't, then you're still using the original recovery image.



    Note: If you are planning on installing the modified RC30 update, you can ignore the following - there is no need to install the boot image. The update already has a newer, modified boot image.


    Now that you know you have the modified recovery image loaded, you can install the boot image:

    Code:
    D:\Android\AndroidMod>adb push boot_nosecure.img /data/local/boot.img
    939 KB/s (0 bytes in 1533952.001s)
    
    D:\Android\AndroidMod>adb shell
    $ su
    su
    # flash_image boot /data/local/boot.img
    flash_image boot /data/local/boot.img
    # rm /data/local/boot.img
    rm /data/local/boot.img
    #

    Now reboot the phone and let it boot normally. If the boot image was corrupted, it will boot into recovery mode instead. You can use the included update zip file to reload the original RC29 boot image.

    Otherwise, if it boots up normally, open a command prompt however you like (telnet, adb, terminal emulator app, etc.) and type "getprop ro.secure". If it says 0, then you're running the modified boot image. Otherwise, if it says 1, you're still running the original boot image.
    1
    Look at the original post. I added a link for the zip file..

    thank you. Sorry