Database Info

ClockworkMod Recovery 4.0.0.9 for the T-Mobile myTouch 4G Slide (MoDaCo edition)

Cool! I got a myTouch 4G Slide!
Not cool! No ClockworkMod recovery!
Solution! Make my own.
You must have a 'S-OFF' device to install this recovery image!
Here is my unofficial MoDaCo build of ClockworkMod for the T-Mobile myTouch 4G Slide / aka HTC Doubleshot. In order to flash this recovery, you need to have temproot or permanent root via Fr3evo (grab from here, push to /data/local, run via ADB then reconnect after it drops your connection for root access). If you need ADB, you can grab it here.
You use this image at your own risk! Proceed with caution!
To install, simply...
Download the ClockworkMod image file from here
Copy the file to /data/local ('adb push doubleshot.clockworkmod.4.0.0.9.modaco.img /data/local')
Write the image to the recovery partition ('dd if=/data/local/doubleshot.clockworkmod.4.0.0.9.modaco.img of=/dev/block/mmcblk0p21')
Do a recovery reboot to test ('adb reboot recovery').
That's it!
P

paulobrien said:
Cool! I got a myTouch 4G Slide!
Not cool! No ClockworkMod recovery!
Solution! Make my own.
You must have a 'S-OFF' device to install this recovery image!
Here is my unofficial MoDaCo build of ClockworkMod for the T-Mobile myTouch 4G Slide / aka HTC Doubleshot. In order to flash this recovery, you need to have temproot or permanent root via Fr3evo (grab from here, push to /data/local, run via ADB then reconnect after it drops your connection for root access). If you need ADB, you can grab it here.
You use this image at your own risk! Proceed with caution!
To install, simply...
Download the ClockworkMod image file from here
Copy the file to /data/local ('adb push doubleshot.clockworkmod.4.0.0.9.modaco.img /data/local')
Write the image to the recovery partition ('dd if=/data/local/doubleshot.clockworkmod.4.0.0.9.modaco.img of=/dev/block/mmcblk0p21')
Do a recovery reboot to test ('adb reboot recovery').
That's it!
P
Click to expand...
Click to collapse
Thanks for this! Man I wish I had mine in my hands already! I'm gonna give this a shot as soon as it arrives
Sent from my demonSPEED Glacier

Mine is S-ON :O
raycaster3 said:
Thanks for this! Man I wish I had mine in my hands already! I'm gonna give this a shot as soon as it arrives
Sent from my demonSPEED Glacier
Click to expand...
Click to collapse

Revolution said:
Mine is S-ON :O
Click to expand...
Click to collapse
Boo! Damn
Sent from my HTC Glacier

So what does hboot do to /dev/block/mmcblk0p21 after the phone is turned back on if you temp root and dd it?

thank you!

paulobrien said:
Cool! I got a myTouch 4G Slide!
Not cool! No ClockworkMod recovery!
Solution! Make my own.
You must have a 'S-OFF' device to install this recovery image!
Here is my unofficial MoDaCo build of ClockworkMod for the T-Mobile myTouch 4G Slide / aka HTC Doubleshot. In order to flash this recovery, you need to have temproot or permanent root via Fr3evo (grab from here, push to /data/local, run via ADB then reconnect after it drops your connection for root access). If you need ADB, you can grab it here.
You use this image at your own risk! Proceed with caution!
To install, simply...
Download the ClockworkMod image file from here
Copy the file to /data/local ('adb push doubleshot.clockworkmod.4.0.0.9.modaco.img /data/local')
Write the image to the recovery partition ('dd if=/data/local/doubleshot.clockworkmod.4.0.0.9.modaco.img of=/dev/block/mmcblk0p21')
Do a recovery reboot to test ('adb reboot recovery').
That's it!
P
Click to expand...
Click to collapse
what does this means 'dd if=/data/local/doubleshot.clockworkmod.4.0.0.9.modaco.img of=/dev/block/mmcblk0p21'

That line of code just copies the recovery image from a directory on the phone to the special place where a recovey image is supposed to be.
Sent from my myTouch_4G_Slide using XDA App

michaelmab88 said:
That line of code just copies the recovery image from a directory on the phone to the special place where a recovey image is supposed to be.
Sent from my myTouch_4G_Slide using XDA App
Click to expand...
Click to collapse
My device is ship s-off can't use this methods.so i used sdcard flash succeeded. Thanks!

Crossing my fingers that someone finds a way to get S-off on these. I'm too spoiled with CM7, I forgot what it's like to have a "stock" phone that you can't delete unwanted apps, overclock, tweak, etc.
I think I might just box up the MTS4G and continue to use my G2 until true root is available.

Can we get an hboot dump from someone with S-off? Just curious if it's possible to flash that to hboot with temp root?

masker2011 said:
what does this means 'dd if=/data/local/doubleshot.clockworkmod.4.0.0.9.modaco.img of=/dev/block/mmcblk0p21'
Click to expand...
Click to collapse
Specifically this command is a raw linux command that would work on almost any machine. It's telling the dd utility to copy the img file to the /dev/ mount in the specific block mmcblk0p21.
Every partition is grouped into blocks. Usually 512kbytes but it could be something else.

Akujin said:
Can we get an hboot dump from someone with S-off? Just curious if it's possible to flash that to hboot with temp root?
Click to expand...
Click to collapse
Nope. See the 'Bounties!' thread.

cberbes said:
Crossing my fingers that someone finds a way to get S-off on these. I'm too spoiled with CM7, I forgot what it's like to have a "stock" phone that you can't delete unwanted apps, overclock, tweak, etc.
I think I might just box up the MTS4G and continue to use my G2 until true root is available.
Click to expand...
Click to collapse
Are you forgetting the fact that the MT4GS is also a Sense phone? While I like Sense, the option to use regular old Android should always be there (I'm looking at YOU, Motorola).

In the bounty thread it had been noted that that there is no on board charging circuit on the phone and that if certain factors do not exist in recovery then the phone can not charge.
I was wondering if this has affected you, out you have already compensated for this. If you have that issue resolved it may be of help to nbetcher and others looking to give us s-off.
Sent from my myTouch_4G_Slide using XDA Premium App

I can't use the command dd if=/data/local/doubleshot.clockworkmod.4.0.0.9.modaco.img of=/dev/block/mmcblk0p21
Whats the fix for that?

electro_chef said:
I can't use the command dd if=/data/local/doubleshot.clockworkmod.4.0.0.9.modaco.img of=/dev/block/mmcblk0p21
Whats the fix for that?
Click to expand...
Click to collapse
Did you elevate yourself to root first?
If you're not sure. At the android prompt type su [enter]
Now you're root and can run anything.

masker2011 said:
what does this means 'dd if=/data/local/doubleshot.clockworkmod.4.0.0.9.modaco.img of=/dev/block/mmcblk0p21'
Click to expand...
Click to collapse
This line isn't working.
Is there a missing "ADB" or "ADB SHELL" that's supposed to go in front of the dd?
Or is this command supposed to be executed on the device itself?

jdmarko said:
This line isn't working.
Is there a missing "ADB" or "ADB SHELL" that's supposed to go in front of the dd?
Or is this command supposed to be executed on the device itself?
Click to expand...
Click to collapse
I believe its suppose to be executed on the device, however if the device doesn't have root, than its useless.
You can use fastboot to flash it.

I'm getting the same charging issue as everyone else.
If the phone is off, and you plug the charger in, the LED will light up. But the phone will not charge, it will freeze, and you must do a battery pull to get it to boot from that point.
Any idea for the fix?

NS4G Recovery Question

So I just rooted via Pete's instructions, I'm on CWM 3.1.0.1 or something but I see some people are on 4.x.x.x what should I be on? Rom manager only lists the 3.1.0.1 thanks in advance.

DigitalDementia said:
So I just rooted via Pete's instructions, I'm on CWM 3.1.0.1 or something but I see some people are on 4.x.x.x what should I be on? Rom manager only lists the 3.1.0.1 thanks in advance.
Click to expand...
Click to collapse
you should upgrade to the latest, 4.x.x.x.

Im not really finding a link to that CWM version, if I flash one of the kernels will it give me the newest recovery? I know that's how people did it on the fascinate.

Going into the nexus s developement thread and look for cwm 4.x.x.x section posted by j_r0dd. The latest should be 4.0.1.4. Grab that .img file and put it into your C:\AndroidSDK\tools folder or wherever you have it located.
1. Open cmd,
cd C:\whateveryounamedit\tools
2. Boot into bootloader
3. Plug in usb and type: fastboot devices, your devices # should pop up, sometimes if its blank its still connected.
4. Type: fastboot flash recovery nameofrecovery.img
I would give a link, but im on the app.
Sorry.
EDIT: oh and be sure you grab the one for ns4g devices.

Wow thanks for being so helpful! I'll do that ASAP.

Your welcome.

kijp15 said:
Going into the nexus s developement thread and look for cwm 4.x.x.x section posted by j_r0dd. The latest should be 4.0.1.4. Grab that .img file and put it into your C:\AndroidSDK\tools folder or wherever you have it located.
1. Open cmd,
cd C:\whateveryounamedit\tools
2. Boot into bootloader
3. Plug in usb and type: fastboot devices, your devices # should pop up, sometimes if its blank its still connected.
4. Type: fastboot flash recovery nameofrecovery.img
I would give a link, but im on the app.
Sorry.
EDIT: oh and be sure you grab the one for ns4g devices.
Click to expand...
Click to collapse
adb doesn't seem to recognize fastboot as a command? I'm in the bootloader though.

Anyone have a zip of the cwm 4.x.x.x recovery?

Did you install android sdk on your computer? If not, you should do that before you proceed.
EDIT: or did you put adb to your path on your computer

I'm on W7 so I just went to platform-tools and typed cmd in the address bar. However fastboot isn't in platform-tools?
So I went to tools but got another error trying to flash.
Sorry for all the questions I've never had to use fastboot.

Or just put the .img file on the root of your sdcard.
Open terminal
type flash_image recovery /sdcard/nameofrecovery.img

Download android terminal
su
flash_image recovery /sdcard/nameofrecovery.img
Hit enter, it should now read the .img file
After that type reboot recovery to check it. Hope this helps.

kijp15 said:
Download android terminal
su
flash_image recovery /sdcard/nameofrecovery.img
Click to expand...
Click to collapse
If it says no image found?

DigitalDementia said:
If it says no image found?
Click to expand...
Click to collapse
Are you doing correctly?
I've done it a tons of time and it never gave me that msg.

When downloaded it, did it say .txt at the end, if it did change it from
.txt to .img.
And try again.

Positive. I renamed it cwm4.img for ease of use and I type:
su
flash_image recovery /sdcard/cwm4.img
Then it says flash_image: not found

kijp15 said:
When downloaded it, did it say .txt at the end, if it did change it from
.txt to .img.
And try again.
Click to expand...
Click to collapse
Still an image file.

Is your img file in any folders?
If it is your doing something wrong that I don't know about. Ha. If it is take out and out it on the root of your sdcard.
I've just flashed a img wit this same exact process and it went threw.

kijp15 said:
Is your img file in any folders?
If it is your doing something wrong that I don't know about. Ha. If it is take out and out it on the root of your sdcard.
I've just flashed a img wit this same exact process and it went threw.
Click to expand...
Click to collapse
Ugh... frustrating! It's not in a folder, it's right on the root mocking me. Okay just so I know I'm doing it right I do it like this:
su
flash_image recovery /sdcard/cwm4.img
Right? With the spaces between recovery and /sdcard/ ?

Hmmm... that is right.. is your terminal a black or blue background?
If its black your have the wrong terminal.

[KERNEL] Modified Stock Kernel [init.d/bootanimation]

Hey Guys,
here is the stock kernel from XXKQ7 including init.d and custom bootanimation support.
Root and Busybox needed
HOW-TO
1. Download one of the following zips
2. Put the zip on your internal SDCard
3. Shut down your phone
4. Go into Recovery-Mode: First power off your Phone, then hold Power + VolumeUp. Release the two buttons 3 seconds after the samsung logo is shown.
5. "install zip from sdcard" -> "choose zip from internal sdcard" -> "stockkernel_init.d_bootanimation_KQ7"
6. Reboot your phone
Downloads
KQE Kernel
KQB Kernel
KQ7 Kernel
Further Instructions
1. Create /system/etc/init.d place some script in it or flash any other init.d script package
2. To change the bootanimation place your favorited sanim.zip in /system/media/
After that you can flash Thunderbolt or AdrenalineShot and use their advantages.
Please give some Feedback it is working correctly because im really new to this stuff. I have a GT-I9001 and at the moment everything seems to run as it should. I had no bootloops as it sometimes was the case with FeaMod or N00b.

what’s this kernel‘s CPU frequency ，OC?

Why you are concerned?
Sent from my GT-I9001 using XDA App

crybert said:
Why you are concerned?
Sent from my GT-I9001 using XDA App
Click to expand...
Click to collapse
sorry, some mistakes in front of my words

Nice, been looking all over for stock kernel..How its prforming? Im currently on latest feacore, with batt drain all the time. Can u post ur batt stats pic?Would love to have usable phone than some short lived super fast phone..

Nice man......thansk is ok on my phone.

can i use it on another phone???

safwanjin said:
can i use it on another phone???
Click to expand...
Click to collapse
u can't be serious , right ?

safwanjin said:
can i use it on another phone???
Click to expand...
Click to collapse
I'm soooo tempted to say yes... but dude, the answer really is NO WAY MAN (unless you want a device which can only be used for throwing in your neighbors windows)
For the ones that want to automate uploading boot.img, here's a batchfile (untested). Just use attached, drag your boot.img ontop of it and ready it is...
Code:
for %%i in (%1) do set onlyfilename=%%~nxi
adb push %1 /sdcard/%onlyfilename%
adb -d remount
adb -d shell dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
adb -d remount
echo all ok?
echo rebooting...press a key to continue...
pause >nul
adb -d reboot
pause

crybert said:
Hey Guys,
I cooked this Kernel with dsixda's Android Kitchen because I wanted a stock kernel with init.d. So here it is.
Root and Busybox needed.
How-To with TerminalEmulator
1. Download boot.img here
2. Place boot.img on your SD-Card
3. Download TerminalEmulator from Market: https://market.android.com/details?id=jackpal.androidterm
4. Run TerminalEmulator and type:
Code:
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
reboot
How-To with adb
1. Download boot.img here
2. Place boot.img on your SD-Card
3. Connect your Phone to your PC with the USB-cable (USB-Debugging has to be enabled)
4. Download adb-tools on your PC and extract the files to C:/adb
5. Run cmd on your PC and type
Code:
cd c:/adb
adb shell
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
reboot
After that you can flash Thunderbolt or AdrenalineShot and use their advantages.
Please give some Feedback it is working correctly because im really new to this stuff. I have a GT-I9001 and at the moment everything seems to run as it should. I had no bootloops as it sometimes was the case with FeaMod or N00b.
Click to expand...
Click to collapse
hmm I can install this over your ROM ?

chasemyass said:
hmm I can install this over your ROM ?
Click to expand...
Click to collapse
You should be able to install it over any rom. Although as you are asking this, I wonder why you'd need it

nikagl said:
You should be able to install it over any rom. Although as you are asking this, I wonder why you'd need it
Click to expand...
Click to collapse
well because I think it could be same kernel version or maybe better than mine if it`s not same

chasemyass said:
well because I think it could be same kernel version or maybe better than mine if it`s not same
Click to expand...
Click to collapse
it's only if you want to tinker with init.d stuff ... and trust me: you don't

nikagl said:
it's only if you want to tinker with init.d stuff ... and trust me: you don't
Click to expand...
Click to collapse
maybe...maybe not i will see

@Crybert:Y dont u integrate CF-ROOT ramdisk with ur kernel,it makes things a hell lot easier

Can be fixed in kernel skype issue with upside-down video from front camera?

prescott66 said:
Can be fixed in kernel skype issue with upside-down video from front camera?
Click to expand...
Click to collapse
just turn the phone around

nope!

what is 'vbus_wake_lock', 'msm_otg' and 'usb_bus_active'?
this 3 kernal are the huge cause of my wakelock.

annoymous1234 said:
what is 'vbus_wake_lock', 'msm_otg' and 'usb_bus_active'?
this 3 kernal are the huge cause of my wakelock.
Click to expand...
Click to collapse
whoa,these are not kernels!

[Q] ClockworkModRecovery (Only wants to wipe data) [SOLVED - Read / Scroll Down]

Ok, so i have a fresh new stock of 21e flashed onto my phone. Rooted with no errors, and I have Clockwork ROM Manager installed.
If I use the app to boot into recovery my phone just automatically Wipes all data then loads back up as if a fresh install was done, so I thought I would check the problem out myself (Power and vol.down), and the only options I have in the Clockwork Boot Menu are as follows:
Android system recovery <3e>
Confirm wipe of all user data?
THIS CAN NOT BE UNDONE.
No
No
No
No
No
No
No
Yes -- delete all user data
No
No
No
Click to expand...
Click to collapse
If I go back one page the only options I have are as follows:
Android system recovery <3e>
Android system recovery utility
reboot system now
wipe data/factory reset
wipe cache partition
wipe cache partition and package recovery
wipe nv dynamic partition
Click to expand...
Click to collapse
I can not go back any further, they are my only options in boot recovery of which I find extremely odd. (Until this is sorted I can not install a new ROM/Kernel and fix my network)
Any help would be much appreciated.
Kind Regards.

Loopy Frog said:
Ok, so i have a fresh new stock of 21e flashed onto my phone. Rooted with no errors, and I have Clockwork ROM Manager installed.
If I use the app to boot into recovery my phone just automatically Wipes all data then loads back up as if a fresh install was done, so I thought I would check the problem out myself, and the only options I have in the Clockwork Boot Menu are as follows:
If I go back one page the only options I have are as follows:
I can not go back any further, they are my only options in boot recovery of which I find extremely odd. (Until this is sorted I can not install a new ROM/Kernel and fix my network)
Any help would be much appreciated.
Kind Regards.
Click to expand...
Click to collapse
That's not ClockworkMod.
That's the stock Android recovery.

ah lol (embarrassing)
Thanks though... ok so it seems that my problem is that the copious amount of things that I try to install clockwork boot, it just wont happen. Any ideas?
Regards

Loopy Frog said:
ah lol (embarrassing)
Thanks though... ok so it seems that my problem is that the copious amount of things that I try to install clockwork boot, it just wont happen. Any ideas?
I am just about to see if I can do something with the LGDP2 V36 UMTS.
Regards
Click to expand...
Click to collapse
You can flash ClockworkMod Recovery with this.
[GUIDES/TOOLS]Making Developing/Flashing/Returning to Stock Easier
The Dark Lestat said:
1. Recovery Manager
This is a flashing tool that will let you install:
Stock Recovery
ClockworkMod Recovery
Touch ClockworkMod Recovery
Requirement:
You'll need to have the LG Thrill / Optimus 3D
You'll need to be rooted.
Superuser and SU have to be updated to the latest app and binary
Update Superuser in the market
Open Superuser app and go to the options
Scroll to the bottom and click "Su binary"
DOWNLOAD LINK: Recovery Manager - 18 MB
How To Use:
Extract the files with WinRar or 7zip
Launch "Recovery Manager.bat"
Make sure your phone is in "USB Debugging Mode" and is plugged in
Choose your option
Wait for the screen to refresh
Boot into recovery to verify it was flashed successfully
Click to expand...
Click to collapse

No Luck :-(
Did your guide word for word, all went successfully.
However.... I can use root applications on the device etc...
Though it appears I can no longer get the clockwork boot anymore?

Loopy Frog said:
No Luck :-(
Did your guide word for word, all went successfully.
However.... I can use root applications on the device etc...
Though it appears I can no longer get the clockwork boot anymore?
Click to expand...
Click to collapse
Try: 3d+volume down+power button
hold til 3 sec after seeing the logo.

Loopy Frog said:
No Luck :-(
Did your guide word for word, all went successfully.
However.... I can use root applications on the device etc...
Though it appears I can no longer get the clockwork boot anymore?
Click to expand...
Click to collapse
You can also use the ROM Manager app to boot into recovery.

p-vlad said:
Try: 3d+volume down+power button
hold til 3 sec after seeing the logo.
Click to expand...
Click to collapse
Nope doesn't work. >_<
The Dark Lestat said:
You can also use the ROM Manager app to boot into recovery.
Click to expand...
Click to collapse
Yeah that's what I was using when it used to work, however now when I do it, It just "deletes all user data". Obviously because it is not having any response from the Clockwork recovery boot, and goes straight into:
Android system recovery <3e>
Confirm wipe of all user data?
THIS CAN NOT BE UNDONE.
No
No
No
No
No
No
No
Yes -- delete all user data
No
No
No
Click to expand...
Click to collapse
I just don't understand why My boot wont change from android to the clockwork boot. >_<

Is it being flashed properly?
Try doing the flashing manually. Download the recovery image from www.clockworkmod.com/rommanager (choose touch for P920, nothing else), then open adb in cmd and type the following commands with phone plugged in:
adb push <image name>.img /data/local/tmp
adb shell su -c "dd if=/data/local/tmp/<image name>.img of=/dev/block/mmcblk0p6 bs=4096"
adb shell "rm /data/local/tmp/<image name>.img"
Replace <image name> with the filename of the img. If everything checks out, you should be able to boot into CWM. If you get errors, post them here
(I took the commands from The Dark Lestat's batch file, props go to him. I was too lazy to search for it Don't judge me, it's 12.30am here)

pandaball said:
Try doing the flashing manually. Download the recovery image from www.clockworkmod.com/rommanager (choose touch for P920, nothing else), then open adb in cmd and type the following commands with phone plugged in:
adb push <image name>.img /data/local/tmp
adb shell su -c "dd if=/data/local/tmp/<image name>.img of=/dev/block/mmcblk0p6 bs=4096"
adb shell "rm /data/local/tmp/<image name>.img"
Replace <image name> with the filename of the img. If everything checks out, you should be able to boot into CWM. If you get errors, post them here
Click to expand...
Click to collapse
Thanks Panda, I'll give it ago later when I have time, and let ya know how I go.

Loopy Frog said:
Thanks Panda, I'll give it ago later when I have time, and let ya know how I go.
Click to expand...
Click to collapse
Also, I'll update the scripts with a newer version, so that it's simplified.

Holy Sh*t .. .
dont use Rom Manager to boot into recovery.. there where so many bad reports about that app.. if you want to boot into recovery.. do this.. .
install Terminal Emulator..
type in ..
su (enter)
reboot recovery (enter)
your phone will boot into what recovery you have .. .
hope that helps!

JastaPein said:
Holy Sh*t .. .
dont use Rom Manager to boot into recovery.. there where so many bad reports about that app.. if you want to boot into recovery.. do this.. .
install Terminal Emulator..
type in ..
su (enter)
reboot recovery (enter)
your phone will boot into what recovery you have .. .
hope that helps!
Click to expand...
Click to collapse
It's not using ROM Manager to BOOT into recovery.
It's using ROM Manager to install ClockworkMod that was the issue.

Very weird indeed. I also have flashed yhe 21E rom from LG. Next I rooted the phone and installed CWM touch. I have no problems with it.

JastaPein said:
Holy Sh*t .. .
dont use Rom Manager to boot into recovery.. there where so many bad reports about that app.. if you want to boot into recovery.. do this.. .
install Terminal Emulator..
type in ..
su (enter)
reboot recovery (enter)
your phone will boot into what recovery you have .. .
hope that helps!
Click to expand...
Click to collapse
Thanks, either/or this doesn't matter at this stage, I need to able to boot into recover for this or even clockwork to do it anyway. I'll keep this in mind nonetheless.
pandaball said:
Is it being flashed properly?
Try doing the flashing manually. Download the recovery image from www.clockworkmod.com/rommanager (choose touch for P920, nothing else), then open adb in cmd and type the following commands with phone plugged in:
adb push <image name>.img /data/local/tmp
adb shell su -c "dd if=/data/local/tmp/<image name>.img of=/dev/block/mmcblk0p6 bs=4096"
adb shell "rm /data/local/tmp/<image name>.img"
Replace <image name> with the filename of the img. If everything checks out, you should be able to boot into CWM. If you get errors, post them here
(I took the commands from The Dark Lestat's batch file, props go to him. I was too lazy to search for it Don't judge me, it's 12.30am here)
Click to expand...
Click to collapse
All went well, expect for the last string, see below;
I renamed "recovery-clockwork-touch-5.8.1.5-p920" - "x"
C:\Users\Astro\ADB>adb push x.img /data/local/tmp
3204 KB/s (5995063 bytes in 1.827s)
C:\Users\Astro\ADB>adb shell su -c "dd if=/data/local/tmp/x.img of=/dev/block/mmcblk0p6 bs=4096"
1463+1 records in
1463+1 records out
5995063 bytes transferred in 0.992 secs (6043410 bytes/sec)
C:\Users\Astro\ADB>adb shell "rm/data/local/tmp/x.img"
rm failed for /data/local/tmp/x.img, No such file or directory
Click to expand...
Click to collapse

Loopy Frog said:
All went well, expect for the last string, see below;
I renamed "recovery-clockwork-touch-5.8.1.5-p920" - "x"
Click to expand...
Click to collapse
I'm about to upload a newer version of it. Let me know if it works.

Alright.
Here's the new Recovery Manager with updated scripts. It should be a lot cleaner now.
Recovery Manager

The Dark Lestat said:
Alright.
Here's the new Recovery Manager with updated scripts. It should be a lot cleaner now.
Recovery Manager
Click to expand...
Click to collapse
You my friend, are truly amazing!! what ever your alterations were; it worked!
Thank you.

Loopy Frog said:
You my friend, are truly amazing!! what ever your alterations were; it worked!
Thank you.
Click to expand...
Click to collapse
I think it's because my scripts were thrown together in the previous one.
Anyways, it's cleaned up.
Glad it worked!

confusion after flashing recovery via terminal emulator (lg P500)

I AM NOOB SO PLEASE DONT BE HARSH
NOW FIRST I DOWNLOADED 2 FILES
"FLASH_IMAGE" AND "AMONRA RECOVERY 3.0.6.img"(renamed it to recovery.img) and PASTED THE FLASH_IMAGE IN /system/bin and recovery.img in root of sdcard
AFTER THAT I OPENED TERMINAL EMULATOR
I TYPED THE FOLLOWING
su
# flash_image recovery /sdcard/recovery.img
then after pressing enter it only showed me
#
NOW IM IN CONFUSION WHETHER THE RECOVERY FLASHED SUCCESFULLY OR NOT ( I DONT WANT REBOOT INTO RECOVERY WITHOUT ANY satisfaction)
so please help me
and thanks in advance

No need for flash_image to be thr.
Do 'su' then 'flash_image recovery /sdcard/recovery.img'
Sent from my LG-P500 using xda premium

allenwalker1998 said:
No need for flash_image to be thr.
Do 'su' then 'flash_image recovery /sdcard/recovery.img'
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
but
without the flash_image it says flash_image: not found

androidisfuture said:
but
without the flash_image it says flash_image: not found
Click to expand...
Click to collapse
Okay then u place it whr it was supposed to be
Sent from my LG-P500 using xda premium

allenwalker1998 said:
Okay then u place it whr it was supposed to be
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
sir you jave any other idea?????/

Thank you alien walker for your time
i risked and rebooted into recovery
and it pefectely worked
so i should close this thread