What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Custom Recovery Image

mine is completely fixed, and all typos fixed. make sure this is done thru terminal emulator, i put adb shell initially, but this is wrong. go to my sig for the whole thing
 
Quick question, one we copy these files onto our sd card and complete the flash do these files need to stay on the sd card or can they be deleted?
 
Guys,

I posted up a collected/corrected version of all the instructions on my OP. See there for help.

EDIT: @Blackandgrey remove the space between xbin/flash_image and you'll stop getting the permission denied.


PS: Tdawg, you have a bunch of little mistakes in your instructions. (Mount command is wrong and there's no space between xbin/flash_image) Just refer people to the OP, I gave you props, dont worry! :p
 
(i use short versions of the mount command because we have the mtab and fstab to remember our types and block devices)
su
mount -o rw,remount /system
mv /system/recovery-from-boot.old /system/recovery-from-boot.p
sync
mount -o ro,remount /system

Just curious, since people are contradicting command syntax.

When can you use the short mount commands (exclude filesystem and blocks) ? Are mtab and fstab implemented with adb only ? I am not really clear on why sometimes they are omitted and sometimes I see them not.

Thanks!
 
I've never been able to get the short mount commands to work, either in ADB or in terminal emulator, so I always use the long versions.
 
How would I do this if my phone was already bricked...mine is. Its stuck at the moto screen. I have a spare but would really like to get my bricked phone working.
 
As I don't have a bricked phone to test on, my guess would be to start with ADB. See if you can get a shell session through ADB and if so, then follow the instructions. If not, you're probably SOL for now, but I havent been able to test any theories out on my droid.
 
How would I do this if my phone was already bricked...mine is. Its stuck at the moto screen. I have a spare but would really like to get my bricked phone working.

yeah, in my experience it's a brick if you can't get into the recovery by holding x

i had found on a droid in such a state, i could get to the bootloader (hold dpad up on power on) but recovery (x), test (t), and safe (dpad center) just left me with the phone hung at the moto logo. maybe there's some way to reflash the whole phone with some bootloader commands, but how to do such a thing is anyone's guess.
 
For those wonder about adb, the way I found was to download the SDK kit and install on your pc. It contains adb, but I gotta warn you that SDK is not the most straightforward down load process to get working. Gotta download it, then additionally download tools and your phone type files. Then you still need to be able to understand run/cmd function on your PC, as well as pathing and dos commands to some extent. If you have always and only been a GUI user, be warned.

And, I could understand where you might have some usb issues. I had already downloaded and installed Moto media Link, so between that and SDK on my XP machine I have not seen any usb issues.

So unless you really need to run this stuff on your pc, or just want to get through all of the above to have pc control, I would suggest terminal on the phone. Unless someone here has a better suggestion to getting adb function other than using SDK.

Craig
 
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?
 
Everytime I try step one I get Permission Denied.

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/.
 
Back
Top