• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Finally Custom Recovery for 2.2.1 stock phones !!!!!!

Just curious, is ext backup and .android_secure important? i tryed to run the option with all and i got Error :run 'nandroid-mobile.sh' via adb.

just doing Nand backup alone worked perfectly.

if the others arnt important i wont bother with it

Its not from lack of space on Sdcard since i have 14Gb free
Seems what that means is you do not have the sd card formated to ext
So no its not important.
You do not need it formated to ext however some are working on a way to format part of the card to linx style ext2 and ext3 filesystem to allow the phone to use part of the card for internal memory. And virtual memory.
 
  • Like
Reactions: hav0kk and Prime85
Upvote 0
Just curious, is ext backup and .android_secure important? i tryed to run the option with all and i got Error :run 'nandroid-mobile.sh' via adb.

just doing Nand backup alone worked perfectly.

if the others arnt important i wont bother with it

Its not from lack of space on Sdcard since i have 14Gb free


good question and one i'm also interested in. the more information the better
 
Upvote 0
Hey guys,
I just rooted fine following the directions provided but I can not seem to have the ability to finalize the custom backup..... it errors out stating mtd: not writing bad block at 0x00220000, error closing recovery: no space left on device.....??? i have 54mb's free? Please see pic, I have shut down devices on numerous attempts and pulled battery as well... what am I doing wrong, please assist. The files are extracted at the root of my sd card with 854mb avail.
 

Attachments

  • 0x00220000 error.jpg
    0x00220000 error.jpg
    229.8 KB · Views: 89
Upvote 0
Ok folks. I removed the original custom recovery and image. Redownloaded and finally see the joneidy build.
and on a side note i'm glad you changed the background. helps confirm we have the right recovery running.

hav0kk, I'm kinda in the same boat.
I rooted my stock v2.2.1 prior to seeing this thread so I flashed thunder recovery.
I'd like to flash joneidy's custom recovery and wondered if you'd share how you removed thunder recovery.

Thanks
 
Upvote 0
hav0kk, I'm kinda in the same boat.
I rooted my stock v2.2.1 prior to seeing this thread so I flashed thunder recovery.
I'd like to flash joneidy's custom recovery and wondered if you'd share how you removed thunder recovery.

Thanks

You can just flash my recovery on top of the other. It would work with no errors :)
 
  • Like
Reactions: jabbawest
Upvote 0
I went through the entire rooting process of a second phone without a hitch until I tried to flash the custom recovery img
I keep getting this error:

flash_image recovery /sdcard/recovery-2.2.1-joneidy.img
flash_image: permission denied

First make sure you get # then make sure that you pushed flash_image. Heres the command
Code:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system

# cat /sdcard/flash_image > /system/bin/flash_image

# chmod 755 /system/bin/flash_image

# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak

# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system

# flash_image recovery /sdcard/recovery-2.2.1-joneidy.img

And reboot after it just to make sure.

Hope it helps
 
Upvote 0
jabbawest - you need to go back one step to "toggle signature verify"; hit enter and at the bottom it will say "verification disabled". then try flashing again and all should run smoothly.
# toggle signature verify
toggle signature verify
toggle: not found

Is is safe to start this over?
Frankly, I'm considering the thunder recovery just to get data back and then proceed with trying to flashing joneidy's recovery.
 
Upvote 0
I'm having an issue. No matter how many times I edit the "environmental variables" to the C:/android-sdk-windows/platform-tools
I always get "error: device not found"

My phone is plugged in. I've tried it with the usb storage activated and deactivated.

I am using admin privileges on CMD prompt.
I'll even manually change the location to look for "adb shell" into the C:/android-sdk...etc location and it still gets the same error.

What am I doing wrong? My phone is flashed. But my service is goneeee. I'm pretty upset. I just thought I could get rid of bloatware and be on my merry way. But apparently you need to be a comp whiz to do everything without effing up. :/

Anyway.
I have recovery and flash 2.2.1 file in the root directory for the phone. Maybe it's stuck only in the sd root? Idk. I can only open the drive when it's in storage mode. Otherwise it comes up transparent.

I don't get the
$ su
#

and everyone who gets the answer never seems to fully explain how they did it... It's pretty frustrating.
 
Upvote 0
I'm having an issue. No matter how many times I edit the "environmental variables" to the C:/android-sdk-windows/platform-tools
I always get "error: device not found"

My phone is plugged in. I've tried it with the usb storage activated and deactivated.

I am using admin privileges on CMD prompt.
I'll even manually change the location to look for "adb shell" into the C:/android-sdk...etc location and it still gets the same error.

What am I doing wrong? My phone is flashed. But my service is goneeee. I'm pretty upset. I just thought I could get rid of bloatware and be on my merry way. But apparently you need to be a comp whiz to do everything without effing up. :/

Anyway.
I have recovery and flash 2.2.1 file in the root directory for the phone. Maybe it's stuck only in the sd root? Idk. I can only open the drive when it's in storage mode. Otherwise it comes up transparent.

I don't get the
$ su
#

and everyone who gets the answer never seems to fully explain how they did it... It's pretty frustrating.

OK check you Personal Messages.
 
  • Like
Reactions: acerl
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones