Custom Recovery Image

[blackngray70]

well then good sir i pose to you that you do not have root access which is required

I do have root I've installed the transparent task bar and I've installed the recovery image and root apps work I'm most definitely rooted but running su from adb shell does not work for me on my PC or my laptop.

Sounds like possibly "su" isn't in your path while setting in the adb shell as a regular user. Do you know exactly where "su" is in your directory tree? Mines in /system/bin/.

No I don't know where it is in the directory tree. I used the super user zip to root. How can I find out where it is? I'm learning as I go

 

[toka]

Short mount commands work only if you use busybox mount instead of the built-in mount command.
1). Install BusyBox binary
2). Create symlinks (either run busybox --install -s or manually create links)
3). Make sure busybox + links are found in your path before the built-in commands

Does anyone have any recommendation on which image to use? I see that the DroidDev page lists versions 0.09 and 0.10 as Do Not Restore - but does that mean do not use at all, or just don't use the "Restore" function of the image?

That was likely the case, this is what I get for writing up instructions after the fact =)

You could also type busybox sh leaving just busybox in your /system/xbin (last dir in path) - you wouldn't need symlinks or have to worry about pathing in that case, as it should default to the builtin applet. Can't confirm this - as I'm staying factory on my 2nd phone, but it would make sense to me from a linux perspective =)

 

[phone]

I do have root I've installed the transparent task bar and I've installed the recovery image and root apps work I'm most definitely rooted but running su from adb shell does not work for me on my PC or my laptop.

Sounds like possibly "su" isn't in your path while setting in the adb shell as a regular user. Do you know exactly where "su" is in your directory tree? Mines in /system/bin/.

No I don't know where it is in the directory tree. I used the super user zip to root. How can I find out where it is? I'm learning as I go

If you have busybox installed you could use "find."

$ busybox find / -name su

You could check if it's in /system/bin

$ ls -l /system/bin/su

Or grab a file manager like Astro and do a search for "su."

Let us know what you find.

 

[p0rk burn]

Help the noob!

I did the trial run of installing the custom recovery image before setting it to block the stock image and it worked fine. Then, I repeated those steps and added "mv /system/recovery-from-boot.p /system/recovery-from-boot.old" to block it. When I got to "flash_image recovery /sdcard/recovery-0.10.0.img" it responded with "can't find recover partition."

That line makes me a little squeamish. Whats the proper course of action here?

Thanks.

 

[p0rk burn]

Ah, lmgtfy! I was copying a typo from a post earlier in the thread. "recovery" not "recover"! Thanks anyways!

 

[tdawg5480]

Ah, lmgtfy! I was copying a typo from a post earlier in the thread. "recovery" not "recover"! Thanks anyways!

think they should fix that post or delete it lol it messed me up for hours then i experimented and it worked then thought i fixed something for everyone an was happy i accomplished something....turns out a typo lol:icon_ banana:

 

[blackngray70]

Sounds like possibly "su" isn't in your path while setting in the adb shell as a regular user. Do you know exactly where "su" is in your directory tree? Mines in /system/bin/.

No I don't know where it is in the directory tree. I used the super user zip to root. How can I find out where it is? I'm learning as I go

If you have busybox installed you could use "find."

$ busybox find / -name su

You could check if it's in /system/bin

$ ls -l /system/bin/su

Or grab a file manager like Astro and do a search for "su."

Let us know what you find.

OK I did a search and I have two results...

data/local/su 74.45kb

system/bin/su 26.0kb

And when I tried the busybox search I got a super long list of results all ending in Permission Denied.

 

[dustin4863]

could someone post a link to the recovery image the link in op does not work anymore thanks

 

[boostdscoob]

Go here :
AllDroid.org - View topic - App to install busybox,flash_image v5 (updated 12/20)

 

[boostdscoob]

Go here :
AllDroid.org - View topic - App to install busybox,flash_image v5 (updated 12/20)

 

[fichdak]

asdfasdfasdf

I'm so confused. I'm a noob at this type of stuff. I'll tell you what I did so far and can someone please tell me WHY nothing's happening?

Alright, well my first problem is probably that I'm using terminal o mac os x 10.6.

1. i put the files on the sd card
2. I cd'd Desktop which is where I had the adb, so I typed ./adb shell su in terminal and hit enter. a thing popped up on my phone saying allow root? and i hit allow. then terminal went to the next line and a # sign appeared (meaning su, correct?). then i typed the next thing "mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system" and hit enter and nothing happened. i keep trying different things but idk what I'm doing.

I'm sure whatever I'm doing wrong is stupid and n00bish, but if someone could help me out, I'd appreciate it. I need the recovery image on my Droid so I get get wifi tethering.

Thanks

 

[tdawg5480]

Not to be rude but what you typed should of not yielded much on screen
besides this mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
and we are supposed to use mtdblock4 nowadays from what I gather DO NOT play with anything until you knw what your doing. IMHO you need only root, busybox, and flash_image recovery thats it until you know how to use things a nandroid backup is a good idea but from experience yesterday and nandroid backup cant fix everything be careful and read this, and welcome to the forum.....and Happy Holidays http://www.droidforums.net/forum/dr...covery-framework-res-apk-custom-boot-ani.html

asdfasdfasdf

I'm so confused. I'm a noob at this type of stuff. I'll tell you what I did so far and can someone please tell me WHY nothing's happening?

Alright, well my first problem is probably that I'm using terminal o mac os x 10.6.

1. i put the files on the sd card
2. I cd'd Desktop which is where I had the adb, so I typed ./adb shell su in terminal and hit enter. a thing popped up on my phone saying allow root? and i hit allow. then terminal went to the next line and a # sign appeared (meaning su, correct?). then i typed the next thing "mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system" and hit enter and nothing happened. i keep trying different things but idk what I'm doing.

I'm sure whatever I'm doing wrong is stupid and n00bish, but if someone could help me out, I'd appreciate it. I need the recovery image on my Droid so I get get wifi tethering.

Thanks

 

[ucpro]

i can't get past step 5, it says 'no such file or directory'

5 - cat /sdcard/flash_image > /system/xbin/flash_image

 

[tktouch12]

I'm sorry, but could someone please explain what this flash_image is?

 

[Bear in NM]

The flash_image is the command (in binary I think) that actually flashes the image. Most of us got it early on in the sp recovery game, around 0.0.10. If you do not have it you will need it. The following link is to the sholes website. If it does not work, when you go to sholes, scroll down the main page to get to page 2. On page 2 there is a discussion of sp recovery, with a "read more" tab at the bottom of the intro paragraph. When you click read more, at the bottom of the text explaination you will see an early version of the recovery image along with the flash image binary file. It used to work as a link that would download to your computer. Now when you right click mouse you can "save as", and this might work to get it to your computer. On mine, when I download it adds a .txt extension to the file. That .txt extension needs to be removed so that it is simply flash image with no extension.

SP Recovery Image with nandroid! | Sholes

The file may be hosted somewhere else for download, I am just not sure where. Might be safer if someone who has it can send it to you, or perhaps scan your phone to see whether you have a version already.

Craig