Database Info

moving dalvik-cache to /cache ???

saw this over here...
http://andblogs.net/2009/05/quick-hack-save-tons-of-space/#more-1660
Quick Hack: Save Tons of Space
Posted on May 8th, 2009 in Android Hacking by Disconnect Tagged cupcake, customize, G1 & ADP1, hacking, howto, kernel, space
So I was looking at my phone, and under 1.5 my dalvik cache was 31 megs (!!!). Rather than move apps to SD (I use my sd card for other stuff, and my apps are only 15 megs anyway) I began thinking.. what else could I move? Aha!
Here are the directions for moving dalvik-cache to /cache, which is unused on these images anyway (it is only for OTA updates.)
There is no fancy installer or much support, and there may be bugs (I only just did this today.)
Its pretty easy. And, so far, works well for me This walkthrough isn’t going to be particularly handholding, but if you need more help try the comments.
Just boot up a capable recovery image (such as JF’s) and mount up /cache and /data.
view sourceprint?
1.# cd /cache
2.# mkdir dalvik-cache
3.# chown 1000 dalvik-cache
4.# chgrp 1000 dalvik-cache
5.# chmod 771 dalvik-cache
6.# cd /data
7.# mv dalvik-cache dalvik-cache-orig
8.# ln -s /cache/dalvik-cache dalvik-cache
The other thing you need is a new boot.img. This one is tuned for JF’s 1.5 adp1 image, and it may or may not work with anything else. Boot Image Cache to Cache JF1.5-ADP1 (71)
(All it does is create the /cache/dalvik-cache dir if it is missing and make sure the perms on /cache are 771 instead of 770.)
Tadah! If everything works, you can remove dalvik-cache-orig. If not, just flash the backup (you did take a backup, right?)
Enjoy!
(Big thanks to JF for helping with the boot image since I have no dev tools right now, and for testing it out for me too.)
any one try it yet? be nice to free up 70meg more on the phone...

Has anyone tried this?
I tried to follow it, but I dont know what to do with the boot.img.gz file.
I did everything else but I got an unbootable phone afterwards and was forced to do a wipe.
I'm running JF 1.5 ADP1 image.
Any help is welcome.
THanks

this is potentially dangerous. /cache may be cleared under many occasions, so if a modified init.rc is not used, you may have a loop on boot.
even if you have such init.rc file, it would be painful to boot after /cache is cleared.
the ultimate solution is to use haykuro's new spl.

M0E-lnx said:
Has anyone tried this?
I tried to follow it, but I dont know what to do with the boot.img.gz file.
I did everything else but I got an unbootable phone afterwards and was forced to do a wipe.
I'm running JF 1.5 ADP1 image.
Any help is welcome.
THanks
Click to expand...
Click to collapse
if you do not flash the modified boot.img file then you CANNOT move the stuff to /cache .. each time you boot it is mounted non-executable .. the modified boot.img makes it executable each time you boot .. if dalvik-cache cannot execute then your phone doesn't load

LucidREM said:
if you do not flash the modified boot.img file then you CANNOT move the stuff to /cache .. each time you boot it is mounted non-executable .. the modified boot.img makes it executable each time you boot .. if dalvik-cache cannot execute then your phone doesn't load
Click to expand...
Click to collapse
Is this the boot.img.gz linked in that howto up top?
If so, how do I go about flashing it?
I really need a solution. I do a lot of online radio streaming and my memory runs out quick. I'd really like to keep my jf 1.5 setup as I have become quite confortablle with it

M0E-lnx said:
Is this the boot.img.gz linked in that howto up top?
If so, how do I go about flashing it?
I really need a solution. I do a lot of online radio streaming and my memory runs out quick. I'd really like to keep my jf 1.5 setup as I have become quite confortablle with it
Click to expand...
Click to collapse
that boot.img.gz file is an archive .. extract the boot.img file out of it to the SD card and then it's something like:
flash_image boot /sdcard/boot.img
or something like that in Terminal .. and then just reboot

And is this done in just terminal or do I need to boot the recovery console?

M0E-lnx said:
And is this done in just terminal or do I need to boot the recovery console?
Click to expand...
Click to collapse
i can't even justify that line of questioning

LucidREM said:
i can't even justify that line of questioning
Click to expand...
Click to collapse
That is the most eloquent response of that nature I've ever seen. I wish I could +1 rep you for that

I gave it a shot, keep getting an error " cannont rename 'dalvik-cache': No such file or directory!
Using RA 1.2.3

ROM
prophetz said:
I gave it a shot, keep getting an error " cannont rename 'dalvik-cache': No such file or directory!
Using RA 1.2.3
Click to expand...
Click to collapse
what ROM are you using? if you already have some form of apps2SD running your dalvik-cache may already be moved .. or you may have mistyped something

BootScreen Help

So i made a bootscreen with the boot1.gif in the system/media/bootscreen folder but some would rather have the cool nexus boot. When I made the flashable zip for them they got
Had the following problem flashing the nexus-bootscreen...
E:Can't symlink /system/bin/dumpcrash
E:Failure at line 9: symlink dumpstate SYSTEM:bin/dumpcrash
Phone would not boot afterwards. Had to do a nandroid restore.
Click to expand...
Click to collapse
I'm sure it has to do with the flashable zip being the bootanimation.zip in the /system/media/ folder. Anybody know a way to fix or make flashable for them so they can override mine without having to redo the nexus one into one gif image?

Read the update script, doesn't look like it is correct.

riggsandroid said:
Read the update script, doesn't look like it is correct.
Click to expand...
Click to collapse
i will fix
hold on

regaw_leinad said:
i will fix
hold on
Click to expand...
Click to collapse
Thanks .
(XDA is kinda like USA Network, characters are wanted)

for you sir

regaw_leinad said:
for you sir
Click to expand...
Click to collapse
wooh, i was correct! lol, just learning update scripts and how this all works. pretty straight forward, but the semantics get me...thanks regaw.

riggsandroid said:
wooh, i was correct! lol, just learning update scripts and how this all works. pretty straight forward, but the semantics get me...thanks regaw.
Click to expand...
Click to collapse
no problem
for all you themers... just take that update script and save it... use it in all of your theme zips. basically it says, whatever's in the folder system, to copy it to the phone.

regaw_leinad said:
no problem
for all you themers... just take that update script and save it... use it in all of your theme zips. basically it says, whatever's in the folder system, to copy it to the phone.
Click to expand...
Click to collapse
thanks man

un/repack .rfs files?

Is it possible to repack a .rfs file? It's easy to extract, but how do you repack?

You can't really repack them...
You can flash them to your, change them and redump them..
Or mount in linux and change... but becareful of permissions this way
Sent from my SPH-D700 using XDA App

chris41g said:
You can't really repack them...
You can flash them to your, change them and redump them..
Or mount in linux and change... but becareful of permissions this way
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
What do you mean by redump? Ill most likely try to change it by mounting in linux like you said...how could the permissions be messed up?

ugothakd said:
What do you mean by redump?
Click to expand...
Click to collapse
Code:
mount -ro remount /dev/block/stl9 /system
sync
cat /dev/block/stl9 > /sdcard/system_redump.img
ugothakd said:
Ill most likely try to change it by mounting in linux like you said...how could the permissions be messed up?
Click to expand...
Click to collapse
The problem is that rfs is proprietary. The file system can only be properly mounted on the phone.
However, since rfs is a backwards-compatible extension of vfat, you can still mount an rfs image with the vfat driver on any Linux machine. This works well enough to grab some files off it. The problem is that regular vfat doesn't support POSIX permissions (owner, group, mode bits, etc.), those are implemented as a proprietary extension. So if you modify an rfs image under vfat, the permissions may end up being not what you expect them to be when mounted on the phone.
The annoying part about modifying rfs images is that, at least under Eclair, an rfs file system couldn't be loopback mounted. I don't know if they can be mounted on an mmcblkp? device or only over an stl one, or even if this limitation is still there.

I don't know about mounting the rfs image directly on the phone.. but I do it on debian.. and the rest of what he said is correct.. as soon as you start changing things.. the links, and permissions may start getting messed up because vfat doesn't support links or posix permissions.. so you will have to be careful with those sorts of things.. but for small carefully made changes it will work

I get it...so redumping makes a .img file that can be (possibly) restored by cwm? So itd be a yaffs2 file system? Or would it still be an rfs file just renamed to .img.
Related to the permissions...if I wanted to say add a program like su or nano to a stock factoryfs.rfs, I would need to chmod the file in terminal emulator after making and odin'ing a tar file for it to work?

no.. rfs is an img regardless and its an rfs img.. he just put an img file extension, you would put an rfs extension and it would flash in odin.. i actually use a different method using dd, there is a tutorial in general i made called making an odin tar.. check it out..
you cant change the permissions when mounted because vfat doesnt support permissions.. you would need to flash it to the phone to change permissions, or.. add an initscript or something that does it..
i suggest leaving those types of things to the kernel though..

chris41g said:
no.. rfs is an img regardless and its an rfs img.. he just put an img file extension, you would put an rfs extension and it would flash in odin.. i actually use a different method using dd, there is a tutorial in general i made called making an odin tar.. check it out..
you cant change the permissions when mounted because vfat doesnt support permissions.. you would need to flash it to the phone to change permissions, or.. add an initscript or something that does it..
i suggest leaving those types of things to the kernel though..
Click to expand...
Click to collapse
I actually have...lol. I think I even thanked you for it. I'm thinking about ways that would help the et4g...they can't pull a stock kernel without root, and they're current method of rooting flashes a different kernel. If rooting can be done by odin'ing a slightly modified factoryfs.rfs, then they can get the kernel, then they hit the holy grail.

If I recall, the SGSII no longer uses rfs.

ugothakd said:
I actually have...lol. I think I even thanked you for it. I'm thinking about ways that would help the et4g...they can't pull a stock kernel without root, and they're current method of rooting flashes a different kernel. If rooting can be done by odin'ing a slightly modified factoryfs.rfs, then they can get the kernel, then they hit the holy grail.
Click to expand...
Click to collapse
So it seems someone needs to install a rooted kernel, install some stuff to the /system partition (su, busybox, bash, nano, recovery(?), whatever), and then dump the /system partition to an image.
Unless maybe I'm missing something...
It shouldn't matter what kernel you have installed while dumping /system.
Kind of off-topic, but still slightly relevant...
Does the Epic 4G Touch get fastboot like the Nexus S 4G did?
[EDIT]
mkasick said:
If I recall, the SGSII no longer uses rfs.
Click to expand...
Click to collapse
Good point, from what I've been told it uses EXT4, so you should be able to mount and edit as much as you like without worry.
[/EDIT]
=]

Son of a gun. I wrote up this nice guide, and it doesn't use rfs??? Thanks for telling me though. I'm still gonna post it. Check the et4g android development section to see it
---------- Post added at 06:26 PM ---------- Previous post was at 06:22 PM ----------
nubecoder said:
So it seems someone needs to install a rooted kernel, install some stuff to the /system partition (su, busybox, bash, nano, recovery(?), whatever), and then dump the /system partition to an image.
Unless maybe I'm missing something...
It shouldn't matter what kernel you have installed while dumping /system.
Kind of off-topic, but still slightly relevant...
Does the Epic 4G Touch get fastboot like the Nexus S 4G did?
[EDIT]
Good point, from what I've been told it uses EXT4, so you should be able to mount and edit as much as you like without worry.
[/EDIT]
=]
Click to expand...
Click to collapse
Nope, good ol' odin like us. And they don't have a rooted kernel. The samsung source doesn't build right

ugothakd said:
Son of a gun. I wrote up this nice guide, and it doesn't use rfs??? Thanks for telling me though. I'm still gonna post it. Check the et4g android development section to see it
Click to expand...
Click to collapse
Could probably just add in some chmod / chown permission commands in there after the cp commands (where you copy su and superuser into the mounted image) and it should work as expected.
Also, I am required to use sudo whenever I mount a factoryfs.rfs file in my Ubuntu install here.
[edit]
ugothakd said:
Nope, good ol' odin like us. And they don't have a rooted kernel. The samsung source doesn't build right
Click to expand...
Click to collapse
Well the NS4G had both Odin and fastboot, I was hoping they would continue on with that. =[
[/edit]
=]

nubecoder said:
Could probably just add in some chmod / chown permission commands in there after the cp commands (where you copy su and superuser into the mounted image) and it should work as expected.
Also, I am required to use sudo whenever I mount a factoryfs.rfs file in my Ubuntu install here.
[edit]
Well the NS4G had both Odin and fastboot, I was hoping they would continue on with that. =[
[/edit]
=]
Click to expand...
Click to collapse
Thanks, I forgot the mount command required root...edited accordingly
Also, you'd have to boot up and chmod because it'l be mounted as a vfat image, which doesn't support permissions.
I also realized you'd need 2 epic touch's for this to work exactly right...

i can confirm the et4g uses ext4.. so you can mount and edit at will.. might need to edit as su on your linux box..

[GUIDE] another way to increase data partition size (non-dualboot)

having a 750mb for data partition like in my previous post seems interesting for everyone. however, make a 2nd rom isn't easy for everyone. there are some people who can't download a rom, which makes dualboot mod useless for them. well...I want to share the joy of having a bigger data partition, so I modify a kernel to enable 2nd ext3 sdcard partition as data partition. for now on lets call this mod **data-2sd**. the steps is quite easy.
preparation step:
1. download a modified kernel from here
2. rename the file to 'boot.img'.
3. repartition your sdcard. all partition is primary. 1st partition fat32. 2nd partition ext3. adjust the partition size to any size you want.
Click to expand...
Click to collapse
the steps:
1. install the kernel
2. make a blank file named 'bootsdcard' in your root sdcard
3. reboot your device.
notes:
1. this kernel is made based on irfanbagus's kernel. (credits for him)
2. if you already have 2nd partition in your sdcard, please reformat it.
3. don't use link2sd or a2sd.
4. clean you init.d folder (optional)
5. you'll need a fast sdcard for best result. our default sdcard is too slow.
Click to expand...
Click to collapse
well...thanks for irfanbagus who has make a dualboot kernel for us. as I have said, I modify the kernel based on his work. the modified script is not an efficient one. I have to admit that. feel free to edit the kernel if you don't satisfy with my work.
btw, I realize that not everyone want to use sdcard's 2nd partition, especially when their sdcard is slow and they have to wait till they have enough money to buy a faster one. well...you don't have to uninstall this kernel since I've made an option to turn off data-2sd feature simply by delete 'bootsdcard' from your sdcard. now, it will act as stock DXLC stock kernel with init.d support. when you already have a fast sdcard you can turn on data-2sd feature again by make 'bootsdcard' file in your sdcard.
you could find the modified files here
www.mediafire.com/download.php?cc1kg8s7cx27onb
www.mediafire.com/download.php?0xydu66254ic6yz
DISCLAIMER:
do it with your own risk. no need to thanks or press it. I'm just a noob. give that to the original dev instead.
KNOWN ROM INCOMPATIBILITY ISSUE
============================
please read this before install this kernel. these roms are reported to incompatible with this kernel. some user said it work, but some other said it doesn't work in these rom. to minimilize the risk, I'll list all reported incompatibility issue with my kernel.[/b]
Incompatibility list
1. chobits digital v1.8 and v2
2. m.u.r (merruk ultimate rom) v1
please inform me if you got another incompatibility issue with other custom rom[/quote]
ADDITIONAL STUFF
==============
if your rom incompatible with this kernel you may try this guide to increase your /data partition as well. you'll need a kernel with init.d support to use this method. please read carefully before modify your system.
1. go to system/etc/init.d
2. delete all a2sd and link2sd related stuff
3. create a new file named 01data2sd. put this script inside it
Code:
#!/system/bin/sh
unmount /data
mount -t ext3 -o nosuid,nodev /dev/block/mmcblk0p2 /data
4. set the permission to 777 (rwxrwxrwx)
5. open your terminal manager. type these command.
Code:
su
mkdir /data/sd-ext
mount -t ext3 -o nosuid,nodev /dev/block/mmcblk0p2 /data/sd-ext
note: its blk-zero-p-two, not blk-O-p2
6. via root explorer go to /data.
7. copy all stuff in /data into /data/sdext.
8. open terminal manager. type these command.
Code:
umount /data/sd-ext
9. restart your device.
if you got bootloop, via adb, type these command
Code:
adb shell
su
mount -o remount rw /system
chmod 222 /system/etc/init.d/*
exit
exit
adb reboot
KNOWN ISSUE: gps not working.
NOTE: the bug is a lil bit annoying for several person. if you want a BETTER-FASTER-BUGLESS-BATTERY FRIENDLY method to save your internal memory, you can use my akuro tweak.
TERM OF USE AND SHARING:
this thread intent is for sharing. feel free to use, edit, distribute all material inside this thread which came from me. if there any parts of this mod which comes not from me please refer to the original dev I've mentioned in this thread. if want to share it to another forum or modify it you don't have to ask my permission. no need to credits, put links or whatsoever. you'll only need to remember that you should held all the responsibility by using this mod, modify it or distribute it. DO IT WITH YOUR OWN RISK
Click to expand...
Click to collapse

what is the advantage?

sgy's original data partition size is only 190mb. you can get 1gb or bigger data partition for your device by using this mod.

I see. I will try this, does it work on creeds 2.0?

it will work on all rom but will make your a2sd didn't work. please remove all a2sd script in init.d before use this mod.

So this will be my steps?
1. FLash your ROM/CUSTOM ROM
2. Delete the scripts in data/system/init.d via Root Explorer.
3. Make a file name "bootsdcard" in root directory of your sdcard.
Question : What file? .txt? .exe?
4. Flash the Kernel via Odin or other methods.
5. Reboot your device.
So now all my apps are on my SD? or all futured apps are on it?

just a plain file without any extension.
for the second question...this mod will change your data partition to 2nd sdcard ext3 partition. its completely different with a2sd or link2sd since it won't move any installed app in your device. your previous app will remain in your original data partition. when you activate the feature and reboot your phone, it would be like when you turn on the device for the first time.

so it will show 750mb not 190mb?

I will try this tomorrow
bla bla bla

devion14 said:
so it will show 750mb not 190mb?
Click to expand...
Click to collapse
it depends on your partition size. you can make it 750mb, 1gb, or any size you want.

does it support init d tweaksthe kernel is based on what??
---------- Post added at 06:23 PM ---------- Previous post was at 06:22 PM ----------
and what stock rom should i used? what roms have no sd card issues? im using dxlc1..

Sir. I dont have to modified the custom rom with modified updater-script? I just have to flash the kernel and then custom rom with the formated 1st. Fat32 and 2nd. Ext3. ?
Sent from my GT-S5360 using Tapatalk 2

kurotsugi said:
sgy's original data partition size is only 190mb. you can get 1gb or bigger data partition for your device by using this mod.
Click to expand...
Click to collapse
Now I am using DDLC2 official firmware and my 2nd partition (ext3) size is 1.06 GB,
but I am not using any kernal and other thing, I am using pure official ROM and
rooted my mobile thats all. From lot of months I am using this second partition
with Link2sd app.
See this attachment

devion14 said:
does it support init d tweaksthe kernel is based on what??
---------- Post added at 06:23 PM ---------- Previous post was at 06:22 PM ----------
and what stock rom should i used? what roms have no sd card issues? im using dxlc1..
Click to expand...
Click to collapse
it supports init.d script. however, there are some script in init.d which will mount your 2nd partition in different place. its better to remove them before you activate this feature.
it works for both custom and stock rom.
krishna_nirvana said:
Now I am using DDLC2 official firmware and my 2nd partition (ext3) size is 1.06 GB,
but I am not using any kernal and other thing, I am using pure official ROM and
rooted my mobile thats all. From lot of months I am using this second partition
with Link2sd app.
See this attachment
Click to expand...
Click to collapse
thats your choice. however this mod doesn't require any app and you don't have to link your app to to ext partition. when you uninstal link 2sd you'll lose all your app in ext partition.
tandob said:
Sir. I dont have to modified the custom rom with modified updater-script? I just have to flash the kernel and then custom rom with the formated 1st. Fat32 and 2nd. Ext3. ?
Sent from my GT-S5360 using Tapatalk 2
Click to expand...
Click to collapse
nope. you don't need to install any rom. but make sure that you have a clean 2nd ext partition.

What is the Base Firmware of This Modified Kernel?
I Hope its DXLC1? Or ?

tandob said:
Click to expand...
Click to collapse
is it for real?
kurotsugi said:
it supports init.d script. however, there are some script in init.d which will mount your 2nd partition in different place. its better to remove them before you activate this feature.
it works for both custom and stock rom.
thats your choice. however this mod doesn't require any app and you don't have to link your app to to ext partition. when you uninstal link 2sd you'll lose all your app in ext partition.
nope. you don't need to install any rom. but make sure that you have a clean 2nd ext partition.
Click to expand...
Click to collapse
ok...ill try...i will use
v6 supercharger only

yup...its based on DXLC kernel. we do only a minor modification in init.rc and /sbin folder.

ok, downloading now..will give this a shot
BTW does increasing internal memory with this increase speed a little bit? coz the more internal memory the faster right?

internal memory space doesn't related to device speed. in fact, it will a little bit slower since ext3 partition is slower than rfs. nevertheless, the differences is not significant. and could only seen in benchmarking test.

[RECOVERY] Fixed CWM v3.0.2.8

I remember downloading this and saving it when I still had the SK4G. It works great, just replace the update.zip on the / of your sdcard to use. Click the THANKS button if you D/L'ed/Used/Referred To/So on...
Just because of the nature of this mod, I cannot and will not be held responsible for any mishaps to your devices and or any of its accessories (SDCards) that in this weird world of ours may just happen. This should not discourage you to use it, just saying.. You break it, You fix/replace it.
LINK: CLICK MEEEEEE
I'll still help you with your device (tech help mostly), if you need anything PM me. (probably only/fastest response)

dude your a life saver im on att and a flashaholic unfourtunatly while me and some pantech flex users are hard at work getting recovery after we successfully rooted our device about 5 days ago i havent been able to flash anything because the new cwm for the sk4g had been taken down everywhere and the koush one is so buggy and wont let me backup or flash i been looking everywhere for this

this doesnt work for me. Invalid signature. How do you install CWM when you have none after stock odin?

rpmccormick said:
this doesnt work for me. Invalid signature. How do you install CWM when you have none after stock odin?
Click to expand...
Click to collapse
I have the same problem. My sidekick is just rooted. I wanted to instal your cwm, but it writes Invalid signature. How can I install it?

dudanko said:
I have the same problem. My sidekick is just rooted. I wanted to instal your cwm, but it writes Invalid signature. How can I install it?
Click to expand...
Click to collapse
I may be wrong, but I think its due to not replacing the stock binary file with the modded binary file. I'm trying to find it online but krylon's site no longer hosts the file...

dudanko said:
I have the same problem. My sidekick is just rooted. I wanted to instal your cwm, but it writes Invalid signature. How can I install it?
Click to expand...
Click to collapse
Make sure you guys are extracting the the zip and putting the extracted recovery into the system/bin, not the whole zip.

You can also use the search and find where I reposted sduvicks fakeflash utility. It will install CWM for you.

In V2 eXDialer have force closes

shadowscott said:
I may be wrong, but I think its due to not replacing the stock binary file with the modded binary file. I'm trying to find it online but krylon's site no longer hosts the file...
Click to expand...
Click to collapse
His page on Android Spin? I used to download it from there .. don't know if its stopped working now :/
I tried sduvick's script but it wasn't working for me so I had to push the files myself.

rpmccormick said:
this doesnt work for me. Invalid signature. How do you install CWM when you have none after stock odin?
Click to expand...
Click to collapse
dudanko said:
I have the same problem. My sidekick is just rooted. I wanted to instal your cwm, but it writes Invalid signature. How can I install it?
Click to expand...
Click to collapse
replace the update.zip on the /root of the SD. No Odin required. Rename to update.zip, and place it straight on your SD.

That did not work until after I rooted it using RageAgainstTheCage
Re-upped by me here:
http://www.mediafire.com/?hn5ikyt6xpn8d9x
After doing that, then it allows the update.zip to work without failing signature check.
EDIT: Then I also used SuperOneClick to shell-root.

-__-
Ok guys the actual problem here is that there is a file missing that you need to push through to your "/system/bin" folder in your SK's root directory.
The missing file is the custom "recovery" binary file that krylon360 created. After doing so, either by ADB pushing the file or copy pasting it with a root file manager, you may boot into recovery then run the 'reinstall packages' command in the stock recovery. This in turn loads the new recovery.....
ALWAYS CHECK YOUR MOUNTS IN CUSTOM RECOVERY. It will save you an accidental pain in the ass. Trust me.
Mounts should look as follows:
----------------------------------------------------------------------------------------------------
-unmount /cache
-mount /data
-mount /sdcard (this sometimes says it is mounted-- not important)
-unmount /system (MOST IMPORTANT. IF IT DOES NOT READ AS THIS SAYS- THEN FIX THAT AND MOUNT IT BEFORE ANY BACKUPS OR WIPES. YOU WILL GET STUCK IN THE SCRIPT)
----------------------------------------------------------------------------------------------------
I will see if I can host the file in my Dropbox. As for the help, it is available in many older posts already. But a hitting that thanks button couldn't hurt ;D

Zydrate_blue said:
Ok guys the actual problem here is that there is a file missing that you need to push through to your "/system/bin" folder in your SK's root directory.
The missing file is the custom "recovery" binary file that krylon360 created. After doing so, either by ADB pushing the file or copy pasting it with a root file manager, you may boot into recovery then run the 'reinstall packages' command in the stock recovery. This in turn loads the new recovery.....
ALWAYS CHECK YOUR MOUNTS IN CUSTOM RECOVERY. It will save you an accidental pain in the ass. Trust me.
Mounts should look as follows:
----------------------------------------------------------------------------------------------------
-unmount /cache
-mount /data
-mount /sdcard (this sometimes says it is mounted-- not important)
-unmount /system (MOST IMPORTANT. IF IT DOES NOT READ AS THIS SAYS- THEN FIX THAT AND MOUNT IT BEFORE ANY BACKUPS OR WIPES. YOU WILL GET STUCK IN THE SCRIPT)
----------------------------------------------------------------------------------------------------
I will see if I can host the file in my Dropbox. As for the help, it is available in many older posts already. But a hitting that thanks button couldn't hurt ;D
Click to expand...
Click to collapse
IIRC, I believe this is the file that everyone wants..
http://www.4shared.com/file/BqnNCX3K/recovery.html

Thank you
I would like to say thanks to you all helping out with this. My lack of signing in here has to do with me not even having an Android-powered device anymore. I sold my SideKick and MyTouch together for about $250. I still come back here and look around every now and then, but see that a lot of you guys have it under control. So, once again thank you.:good: