Database Develop

[SOLVED] install-recovery.sh - The undeletable script from the dark side...

Greeting all,
First of, I would like to thanks all of you for the amount of info I have found in this forum.
This is trully amazing and, so far, allowed me to sucessfully:
- Unlock my phone
- Root my phone
- Install a custom recovery image
I know that I am creating a new post on a very known and discussed subject BUT after 2 days of google seach nothing I have tried has permitted me to sucessfuly delete this £$%^&*() of script.
As you all know, it needs to be deleted to launch the custome recovery image (at the moment, I am stucked with the exclamation mark with the little Droid when I try).
IMPORTANT: I currently run the Froyo android 2.2 official ROM.
To delete this scipt, I have tried 2 approaches:
- Console mode from windows using ADB
- directly form the phone using a File explorer
#1: From the console:
As mentionned in many previous posts, I have tried the following commands once connected to the nexus
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
I beleive this command is either incorrect OR no longer working with Froyo 2.2 as I get the following message which looks fishy (I am not a Linux specialist...):
Usage: mount [-r] [-w] [-o options] [-t type] device directory
When I try to delete the scripe with the commande below, I am kindly informed that it failed as it is still a read only file system
rm /system/etc/install-recovery.sh
#2: From the phone
I read that SUFBS, a very nice file explorer was available on the market allowing to mount both system AND data in RW would allow me to do it.
I have had several try at it enabling RW at different moment (System then etc then directly when I am in the folder and see the script I want to delete) and whatever I do, each time I select the command delete, it looks like it works (little pacman eating) but the script from the dark side is sill there like nothing happened...
As I am close to give it the microwave treatment to see if it works better ;-) I thought I give it a try on the forum to see if any Android/Linux god would spend 5 minutes to explain to me what I am doing wrong...
Thanks a lot in advance!
BooToo

Try this:
mount -o rw,remount /system
I can't guarantee that works with Froyo but it's all I've ever used and I don't remember it giving me any problem when I used Froyo.

Umm I think it should be mount -o remount,rw then type the rest
You can also try this mount -o remount,rw /dev/block/mtdblock3 /system
Sent from my Nexus One using XDA App

adb is supposed to have it's own remount command for doing this, but I've only used adb once when I rooted so I'm no help there.
Other than that, try doing: ls -l /system/xbin/mount to see if mount is a link to busybox. If it is, the last part of the output will look like this: /system/xbin/mount -> busybox
If it is, type busybox | head -n1 to see what version of busybox you have.
ilostchild said:
Umm I think it should be mount -o remount,rw then type the rest
Click to expand...
Click to collapse
Heh, I never realized I had those backwards compared to how people usually do it, but the order doesn't actually matter. It's not necessary to specify the device as the remount option doesn't change the mount point or device.
# mount | grep system
/dev/block/mtdblock3 on /system type yaffs2 (ro,relatime)
# mount -o rw,remount /system
# mount | grep system
/dev/block/mtdblock3 on /system type yaffs2 (rw,relatime)

Well...
I am an ass...
I did not have enabled the "USB debugging" on the phone...
Problem soved with the exact command lines I put at the beginning...

After rooting, flashing clockworkmod through ROM manager it was still going into stock recovery mode. Then I deleted /system/etc/install-recovery.sh and got my phone(HTC magic - 32A) bricked. Now it starts, shows rogers logo for 5-6 seconds and restarts and repeats untill i take out battery. I tried all combinations(power+back , power+home, Power+volume, Menu+home+power, menu+call+power) for quickboot and recovery mode but no success. Anyone has any idea about this issue?

If you have an HTC Magic, you're in the wrong forum...
Sent from my Nexus One using XDA App

just rename the script and you're done!

1) Bump 6 month old thread
2) Post in the completely wrong forum
3) Posts: 1 Join Date: Feb 2011
UGH.

error while loading new compiled Linux kernel image into the android emulator(1.5)
I am sorry, that i am asking my question in "reply" but i am not able to make a new post.
I have successfully compiled Linux kernel for android:
[email protected]:~/common# ARCH=arm CROSS_COMPILE=~/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi- make
CHK include/linux/version.h
make[1]: `include/asm-arm/mach-types.h' is up to date.
CHK include/linux/utsrelease.h
.
.
.
SYMLINK include/asm -> include/asm-arm
CALL scripts/checksyscalls.sh
<stdin>:1097:2: warning: #warning syscall fadvise64 not implemented
<stdin>:1265:2: warning: #warning syscall migrate_pages not implemented
<stdin>:1321:2: warning: #warning syscall pselect6 not implemented
<stdin>:1325:2: warning: #warning syscall ppoll not implemented
<stdin>:1365:2: warning: #warning syscall epoll_pwait not implemented
CHK include/linux/compile.h
Kernel: arch/arm/boot/Image is ready
Kernel: arch/arm/boot/zImage is ready
Building modules, stage 2.
MODPOST 157 modules
[email protected]:~/common#
but i get the following error while loading this images in the emulator:
[email protected]:~/android-sdk-linux_x86/tools# ./emulator -avd avd1.5 -kernel ~/common/arch/arm/boot/zImage -show-kernel -verbose
emulator: found SDK root at /home/preetam/android-sdk-linux_x86
emulator: root virtual device file at /home/preetam/.android/avd/avd1.5.ini
.
.
.
yaffs_read_super: isCheckpointed 0
sh: can't access tty; job control turned off
# init: cannot find '/system/bin/playmp3', disabling 'bootsound'
init: cannot find '/system/bin/dbus-daemon', disabling 'dbus'
eth0: link up
init: untracked pid 578 exited
init: untracked pid 579 exited
warning: `rild' uses 32-bit capabilities (legacy support in use)
init: untracked pid 601 exited
init: untracked pid 592 exited
init: untracked pid 605 exited
init: untracked pid 602 exited
init: untracked pid 609 exited
init: untracked pid 606 exited
init: critical process 'servicemanager' exited 4 times in 4 minutes; rebooting into recovery mode
save exit: isCheckpointed 1
save exit: isCheckpointed 1
Restarting system with command 'recovery'.
Reboot failed -- System halted
and the emulator didn't start with the new kernel image(emulator didn't reboot). what is the problem here..?? and how can i replace my emulator's image with newly compiled Linux permanently??
please help. thank you!

I did everything as the guy who initiated this post under windows vista, and I have the same problem. However, I don't know how to go about deleting or renaming that scrip. Can you, give me a step by step procedure? Thank you

Flash this through recovery to delete the script...
http://db.tt/ooDaCnU

Hi,
I am sort of new to this. how do I flash using the above script?

adb not working with N1 rooted?

hi,
two days ago i rooted my Nexus One FRF91-Vodafone with these two methods ( forum.xda-developers.com/showthread.php?p=7548842 and forum.xda-developers.com/showthread.php?t=736271). Still some commands of adb don't work and i can't find a solution.
Code:
C:\>cd android/tools
C:\android\tools>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT05EP800252 device
C:\android\tools>adb shell
$ su
su
# id
id
uid=0(root) gid=0(root)
# exit
exit
$ exit
exit
C:\android\tools>adb remount
remount failed: Operation not permitted
C:\android\tools>adb root
adbd cannot run as root in production builds
C:\android\tools>
as you can see the device is connected in debug mode and i am rooted but the commands "adb remount" and "adb root" don't work (and maybe some other commands? i don't know). does it happen because the bootloader is still locked? if so, is there a way to have those commands working without unlocking it? if not, what could it be?
sorry for my english
thanks a lot

I'd have to guess because "remount" and "root" are not the way to do it.. Where are you seeing this is the way to do what you need to do?

how shoul it be used? i found a lot place where is written just like that. besides i read that the default.prop should be like this:
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
for adb to work properly
but mine is like this
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0
and i don't understand why, i cant change it because it's a read-only file

What about:
Code:
mount -o remount,rw /system
?

i have this same problem, im guessing you went the way without unlocking your bootloader?
if so i dont think you can do adb remount
but what you can do is this method
adb shell
su
#mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
this will remount your phone system to read-write and you should be good to push/pull/cp/rm/clear/ and what your trying to do

Thanks for the info. I was having the same issue with my N1. The full mount path worked
Kage_

If you're really slick, I imagine you could add an alias "remount" to your shell profile script (.csh or something similar) to execute that full command for you when you needed it

[Q] Restoring stock Recovery Image on Sprint

Hey all,
I had the sense to use the Rotobackup method on my new Sprint Tab after rooting it with the Z4root package. I then proceeded with the ( now outdated ) CWM Flash process adapted from the Epic 4g. Now, I can get into CWM and the process appears to be functional, but I can't get the "Wipe Data/Factory Reset" to work. It all goes well, but when I boot back into android, all the junk is still there.
Now, I know this wouldn't normally be a big deal... However.. In set'n up for my Rotobackup, I punched in a spare Gmail account in case someone wanted a copy of the backup for dissection,etc... Now, since I can't get the factory wipe to work ( neither from the Privacy menu, nor CWM ), I can't get that acct off my Tab so I can get to all my purchased apps on my main account.
Since I have the Rotobackup, I'm thinking that I can just restore one of those packages and get the stock recovery image back in place. I just want to verify which one I should restore before I move forward.
My expectation is that I need to restore the 'boot.bin' file. Can someone confirm this?
For the record, these are the files I have saved:
Code:
-rw-r--r--. 1 root root 262144 Dec 22 19:00 boot.bin
-rw-r--r--. 1 root root 32768000 Dec 22 19:00 cache.rfs
-rw-r--r--. 1 root root 25620093 Dec 22 19:23 data.tgz
-rw-r--r--. 1 root root 86507520 Dec 22 19:00 dbdata.rfs
-rw-r--r--. 1 root root 6553600 Dec 22 19:00 efs.rfs
-rw-r--r--. 1 root root 336068608 Dec 22 19:00 factoryfs.rfs
-rw-r--r--. 1 root root 16777216 Dec 22 19:00 modem.bin
-rw-r--r--. 1 root root 1310720 Dec 22 18:58 param.lfs
-rw-r--r--. 1 root root 262144 Dec 22 19:00 pit.pit
-rw-r--r--. 1 root root 1310720 Dec 22 19:00 Sbl.bin
-rw-r--r--. 1 root root 7864320 Dec 22 18:59 zImage
Thanks in advance,
LK

Or, can I simply do an rm -rf /data/* to get the effect of a factory wipe?
Thanks,
LK

Ok, I figured it out..
So, the thought of flashing the recovery image came from my root experiences on Evo. I decided while waiting for a response to do more digging through the CWM installation routine and noticed that it made a backup of the original recovery file ( since on Epic and Tab, it's a redirector method instead of an image on the Evo ). AND.. it had a 'Remove root/CWM' option!
I modified the run.sh script to NOT remove root on that option and only put the original CWM in place, ran it.. and VIOLA!
Hope this may help someone else.
LK

are you saying you have a working CWM running on your Sprint-flavored tab?

Hello Zoinks,
Nope... the CWM wasn't working properly on my Samsung Tab. I reverted to the stock recovery on my Tab to regain the ability to wipe it.
Thanks,
LK

and you were so close to being my new best friend
which modem are you using? we have not been able to properly export the factory modem

I'm afraid neither of us are that lucky.
I'm still using the original modem. Nothing has actually been flashed to the device aside from what it took to root it.
Nothing to see here...
LK

ok, so I also just rooted my new sprint tab. using the z4root method. I also have learned about rooting through my evo. I have not however got as far as you have as in getting a recovery image. If i understand what I have tried to absorb on this from the board, is that A) I should have gone with tmobile for the tab!!!! lol and B) this aint no EVO!!!!!
So could you point me in the right direction/advice with what I should do now, because I am lost!!!!
thanks in advance

I'd install bash with the 'Bash Installer' app from the market, and then any other goodies you like for rooted devices ( Adfree Android is a personal fav ).
Aside from that, hang tight and watch for more advancements in alternative ROMS and Recovery managers. Don't install any recovery manager at this time as they are too buggy for normal use and don't really have much in the way of usable features yet.
Clockwork Mod is the closest, but still doesn't support nandroid backup and the like.
Oh, also.. you should check into creating a 'Rotobackup' of your device per the instructions found in another thread of this sub-form.
Enjoy!
LK

linuxkidd said:
Ok, I figured it out..
So, the thought of flashing the recovery image came from my root experiences on Evo. I decided while waiting for a response to do more digging through the CWM installation routine and noticed that it made a backup of the original recovery file ( since on Epic and Tab, it's a redirector method instead of an image on the Evo ). AND.. it had a 'Remove root/CWM' option!
I modified the run.sh script to NOT remove root on that option and only put the original CWM in place, ran it.. and VIOLA!
Hope this may help someone else.
LK
Click to expand...
Click to collapse
I'm having the same problem, can you tell me how to do that? Where's the run.sh file?
Thanks.

Hello zephyrd,
The problem I had was because I used the CWM process outlined in this thread. The 'run.sh' script is the one included with the downloads in that thread.
I edited the run.sh file as follows:
* FInd the section that starts with 'function remove {'
* Inside that section, find the following two sub-sections:
- echo Running root file cleaner on device
- echo Removing remount binary
* Comment out the lines under those sections with # so that the final 'function remove {' section looks like this:
Code:
function remove {
clear
echo +++++++++++++++++++++++++++++++++++++++++++++++++++++
echo "Simple Root and ClockworkMod Uninstaller 2.01";
echo +++++++++++++++++++++++++++++++++++++++++++++++++++++
echo Bash Scripts by DRockstar and Firon
echo exploit by joeykrim, original uninstaller by noobnl
echo
echo REMOVES ALL ROOTS AND CLOCKWORKMOD REDIRECTOR
echo MODIFIED FOR USE WITH GALAXY TAB
chooser
startserver
checkroot
echo Mount device RW
$adb shell mount -t rfs -o remount,rw /dev/block/stl9 /system
#echo Running root file cleaner on device
#$adb push rclean /system/xbin/rclean
#$adb shell chmod 755 /system/xbin/rclean
#$adb shell /system/xbin/rclean
#$adb shell rm /system/xbin/rclean
#echo Removing remount binary
#$adb shell rm /system/bin/remount > /dev/null 2>&1
#$adb shell rm /system/xbin/remount > /dev/null 2>&1
echo Removing ClockworkMod redirector
$adb shell rm /system/bin/recoveryfiles/*
$adb shell rmdir /system/bin/recoveryfiles
$adb shell rm /system/bin/recoveryres/images/*
$adb shell rmdir /system/bin/recoveryres/images
$adb shell rm /system/bin/recoveryres/*
$adb shell rmdir /system/bin/recoveryres
$adb shell rm /system/bin/recovery
echo Restoring original recovery file
$adb push recovery /system/bin/recovery
$adb shell chmod 755 /system/bin/recovery
echo Rebooting phone
$adb reboot
checkboot
echo
echo SIMPLE ROOT UNINSTALLER COMPLETED.
end
}
When you run the 'run.sh' command, pick the 'Simple Root and ClockworkMod Uninstaller' option. This will restore your recovery manager back to the stock one, while leaving your Tab rooted.
NOTE: This same logic can be applied to the 'run.bat' file. The sections that need to be commented out are the same. Instead of using a # to comment the lines, place the word 'REM ' in front of them.
The run.bat 'remove' function will look as follows when done:
Code:
:remove
cls
echo +++++++++++++++++++++++++++++++++++++++++++++++++++++
echo Simple Root and ClockworkMod Uninstaller 2.01
echo +++++++++++++++++++++++++++++++++++++++++++++++++++++
echo Batch Scripts by DRockstar and Firon
echo exploit by joeykrim, original uninstaller by noobnl
echo.
echo REMOVES ALL ROOTS AND CLOCKWORKMOD REDIRECTOR
echo MODIFIED FOR USE WITH GALAXY TAB
call :chooser
if "%a%"=="m" goto :menu
call :startserver
call :checkroot
echo Mount device RW
adb shell mount -t rfs -o remount,rw /dev/block/stl9 /system
rem echo Running root file cleaner on device
rem adb push rclean /system/xbin/rclean
rem adb shell chmod 755 /system/xbin/rclean
rem adb shell /system/xbin/rclean
rem adb shell rm /system/xbin/rclean
rem rem echo Removing remount binary
rem adb shell rm /system/bin/remount > nul
rem adb shell rm /system/xbin/remount > nul
echo Removing ClockworkMod redirector
adb shell rm /system/bin/recoveryfiles/*
adb shell rmdir /system/bin/recoveryfiles
adb shell rm /system/bin/recoveryres/images/*
adb shell rmdir /system/bin/recoveryres/images
adb shell rm /system/bin/recoveryres/*
adb shell rmdir /system/bin/recoveryres
adb shell rm /system/bin/recovery
echo Restoring original recovery file
adb push recovery /system/bin/recovery
adb shell chmod 755 /system/bin/recovery
echo Rebooting phone
adb reboot
call :checkboot
echo.
echo SIMPLE ROOT UNINSTALLER COMPLETED.
goto :end
If you have any questions, please let me know. It's better to ask now than screw up your tab.
Hope this helps!
LK

linuxkidd said:
Hello zephyrd,
The problem I had was because I used the CWM process outlined in this thread. The 'run.sh' script is the one included with the downloads in that thread.
I edited the run.sh file as follows:
* FInd the section that starts with 'function remove {'
* Inside that section, find the following two sub-sections:
- echo Running root file cleaner on device
- echo Removing remount binary
* Comment out the lines under those sections with # so that the final 'function remove {' section looks like this:
When you run the 'run.sh' command, pick the 'Simple Root and ClockworkMod Uninstaller' option. This will restore your recovery manager back to the stock one, while leaving your Tab rooted.
NOTE: This same logic can be applied to the 'run.bat' file. The sections that need to be commented out are the same. Instead of using a # to comment the lines, place the word 'REM ' in front of them.
The run.bat 'remove' function will look as follows when done:
If you have any questions, please let me know. It's better to ask now than screw up your tab.
Hope this helps!
LK
Click to expand...
Click to collapse
Thanks so much for the help! However, this doesn't solve my problem, which is outlined in this thread.
I think my factory setting is modified somehow and can not be removed.
I don't expect any solutions any time soon but if you think you can help I can provide more info on the problem.
Thanks again!

Copy of stock recovery
Think you could post of a copy of the stock recovery file?

wolfson292 said:
Think you could post of a copy of the stock recovery file?
Click to expand...
Click to collapse
yea i could really use that right now too

Recovery process
Can you give me a guide to follow to
A. Return to stock: titanium back up on sd card. Unfortunately no way to get titanium bac on tab as market has disapeared. Unless I can down load .apk and then install from card.
B. Replace voodoo kernal with different one that restores screen rotation, market etc.
Will make generous donation to coffee/beer funds.
Any help for a noob in trouble?
[email protected] for mail, gtalk and pm's

can any one tell me how to make a copy of the original recovery image or send me a link to where i could find that information i searched the net but couldnt find an answer
plz help or email me at [email protected]

[Q] CWR Error: Can't mount /cache

I get this error in CWR (3.2.0.1), I have a nook with a blue sticker:
Code:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/command
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/command
Nothing, and I mean Nothing I have found in this forum solved this error, including the repartition-boot-stock+factory rest.
Any help guys? I am desperate!

adb is working but shell is not
This is what I got, anyone has an idea how to recover from this?
Code:
C:\Users\Barak>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -

reifba said:
This is what I got, anyone has an idea how to recover from this?
Code:
C:\Users\Barak>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Click to expand...
Click to collapse
Nothing, and I mean Nothing I have found in this forum solved this error, including the repartition-boot-stock+factory rest.
Click to expand...
Click to collapse
If you repartitioned, that may be the reason the adb command is not working....

patruns said:
If you repartitioned, that may be the reason the adb command is not working....
Click to expand...
Click to collapse
So I have 2 two problems in which the solution to one causes the other...
In the mean time I manged to run both the Froyo and HoneyComb from the sd card, but not the CM7 (which is the one I am trying to install on the internal memory)

using ADB to restore
I tried to use the methods described in:
:http://forum.xda-developers.com/showthread.php?t=919353
However it is not clear where should the factory.zip go?
for some reason it also says that the /dev partition is only 244MB so I cannot flash the system.img, it is probably the partition in the SD card and not the memory, so not much advancement here either. I also think that because it gives me 11223344556677 as the S/N and not the real one.
The quest to restore the nook continues...

Is there a way to manually repartition through ADB?
or anything? cause nothing solves the first error posted in this thread

reifba said:
I tried to use the methods described in:
:http://forum.xda-developers.com/showthread.php?t=919353
However it is not clear where should the factory.zip go?
for some reason it also says that the /dev partition is only 244MB so I cannot flash the system.img, it is probably the partition in the SD card and not the memory, so not much advancement here either. I also think that because it gives me 11223344556677 as the S/N and not the real one.
The quest to restore the nook continues...
Click to expand...
Click to collapse
factory.zip and rombackup.zip should be located on /dev/block/mmcblk0p3
system should be written to /dev/block/mmcblk0p5
1123344556677 is normal for the device listing when adb'ing in when running CWM on the uSD
to write the img files you need to use:
dd if=(IMG FILE ON SD) of=(PARTITION ON /dev... i.e. /dev/block/mmcblk0p1)
to help you out...here's a list of what goes where:
mmcblk0p1-boot.img
mmcblk0p2-rom.img
mmcblk0p3-factory.img
mmcblk0p4-logical.img
mmcblk0p5-system.img
mmcblk0p6-data.img
mmcblk0p7-cache.img
mmcblk0p8-media.img

problem:
thanks for the reply, I am studying more about andriod and adb now than during all my bachelor's.
just
adb push factory.zip /dev/block/mmcblk0p3 ??
and
adb shell dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
(in some places I saw they didn't write "/block")
and where is rombackup.zip from?
the problem is that for some reason /dev/ is only 244MB so I can't dd system.img, only the boot.img.
I wish that somewhere in the world would exist something that solves it from CWR, just some zip I would install to fix boot+factory+system in one stroke...

reifba said:
thanks for the reply, I am studying more about andriod and adb now than during all my bachelor's.
just
adb push factory.zip /dev/block/mmcblk0p3 ??
and
adb shell dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
(in some places I saw they didn't write "/block")
and where is rombackup.zip from?
the problem is that for some reason /dev/ is only 244MB so I can't dd system.img, only the boot.img.
I wish that somewhere in the world would exist something that solves it from CWR, just some zip I would install to fix boot+factory+system in one stroke...
Click to expand...
Click to collapse
to get factory and rombackup zip files on mmcblk0p3...
adb shell mkdir /sdcard/tmp3
adb shell mount /dev/block/mmcblk0p3 /sdcard/tmp3
adb push factory.zip /sdcard/tmp3
adb push rombackup.zip /sdcard/tmp3

more problems (desperation is looming)
DizzyDen said:
adb shell mount /dev/block/mmcblk0p3 /sdcard/tmp3
Click to expand...
Click to collapse
when I type the above I get
Code:
[email protected]:/ # mount /dev/block/mmcblk0p3 /sdcard/tmp3
Usage: mount [-r] [-w] [-o options] [-t type] device directory
I had to do it in the shell in order to su.

reifba said:
when I type the above I get
Code:
[email protected]:/ # mount /dev/block/mmcblk0p3 /sdcard/tmp3
Usage: mount [-r] [-w] [-o options] [-t type] device directory
I had to do it in the shell in order to su.
Click to expand...
Click to collapse
then I would use
mount rw /dev/block/mmcblk0p3 /sdcard/tmp3
If that doesn't work:
mount rw -o remout /dev/bloc/mmcblk0p3 /sdcard/tmp3
but it would appear something else is amiss... since it even shows the command should have worked... since everything other than the command (mount) the device (/dev/block/mmcblk0p3) and directory (/sdcard/tmp3) are optional parameters

[Q] Problems with Clockwork Mod Recovery on Gingerbread XWJVZ

Hi guys
i have a prety strange problem with clockwork mod recovery on a phone i was trieng to flash for a freind. INstalling zips on the recovery always fails. I tried diffrent versions of Cyanogenmod, none worked. Also the gapps packet fails.
I do get the following error message:
script aborted: assert failed: run_program("/tmp/updater.sh") == 0
assert failed: run_program("/tmp/updater.sh") == 0
E:Error in /sdcard/cm-9.1.0-galaxysmtd.zip
(Status 7)
Installation aborted.
What is the actualy strange thing about that problem is that i seam to have two diffrent recoverys. Starting the recovery over the buttos fails and if i start it through rom manager i sometimes end up on clockworkmod recovery and sometimes end up in samsungs galaxy s recovery
Let me tell you how I got to were I am now. I folowed the instruktion on Cyanogenmod but after flashig the root kernel over heimdall the phone was stuck in a bootloop. The recovery was gone but download mode was still working. So no real brick. After a while strugeling with odin, I was able to get back to stock rom with a Heimdall image. Thanks for those images aorth
After flashing a diffrent root kernel i did get root and was able to install ROM Manager and Clockwork Mod Recovery. But the recovery doesent realy work. I did uninstalled and reinstalled clockwork mod recovery and reied diffrent version of it, but nothing did help...
Anybody has an idea what went wrong and what i could do to fix it?

Hilmy said:
After flashing a diffrent root kernel i did get root and was able to install ROM Manager and Clockwork Mod Recovery. But the recovery doesent realy work. I did uninstalled and reinstalled clockwork mod recovery and reied diffrent version of it, but nothing did help...
Anybody has an idea what went wrong and what i could do to fix it?
Click to expand...
Click to collapse
flash a semaphore kernel for root and CWM from here http://forum.xda-developers.com/showthread.php?t=1112908

xsenman said:
flash a semaphore kernel for root and CWM from here http://forum.xda-developers.com/showthread.php?t=1112908
Click to expand...
Click to collapse
I did flash that kernel now, Flashing with Odin worked well, but after the reboot i was stuck in a bootloop again.
Is this Kernel maybe only compatible with a specific version of the original Samsung ROM? Or ist the a specific setting in Odin i have to use?

Hilmy said:
I did flash that kernel now, Flashing with Odin worked well, but after the reboot i was stuck in a bootloop again.
Is this Kernel maybe only compatible with a specific version of the original Samsung ROM? Or ist the a specific setting in Odin i have to use?
Click to expand...
Click to collapse
Semaphore and CF Root kernels have a specific ROM kernel, use solutions in My Android Solutions link below to resolve boot loop problems

xsenman said:
Semaphore and CF Root kernels have a specific ROM kernel, use solutions in My Android Solutions link below to resolve boot loop problems
Click to expand...
Click to collapse
Fixing the Bootloop problem isent realy a problem. Did that allot in the last days while tryeing difrent kernels
I did find a matching CF Root kernel now. No more boot loop but still two recoverys. The clockwork mod recovery, which can be enterd over the kernels CWM App, and the Android system recovery which apears when i boot to recovery over Rom Manager.....
I still cant install any ROMs over any of those recoverys. When i try over clockwork mod recovery I get an error and the process gets aborted. The error message looks like that again:
assert failed: run_program("/tmp/updater.sh") == 0
E:Error in /sdcard/cm-9.1.0-galaxysmtd.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Does anybody know what that means and what i could do to fix it?
The full recovery log from clockwork mod recovery looks like that:
Starting recovery on Fri Sep 14 17:52:35 2012
framebuffer: fd 4 (480 x 800)
ClockworkMod Recovery v3.0.0.5
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /sdcard vfat /dev/block/mmcblk0p1 (null)
2 /system rfs /dev/block/stl9 (null)
3 /cache rfs /dev/block/stl11 (null)
4 /data rfs /dev/block/mmcblk0p2 (null)
5 /datadata rfs /dev/block/stl10 (null)
6 /boot bml boot (null)
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Checking for ext4 partitions...
Checking /system...
Checking /data...
Checking /datadata...
Checking /cache...
Done!
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "recovery"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=herring
ro.revision=48
ro.build.id=GINGERBREAD
ro.build.display.id=GINGERBREAD.XWJVZ
ro.build.version.incremental=XWJVZ
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.6
ro.build.date=Fri Nov 25 16:47:47 KST 2011
ro.build.date.utc=1322207267
ro.build.type=user
ro.build.user=root
ro.build.host=DELL145
ro.build.tags=release-keys
ro.product.model=GT-I9000
ro.product.brand=samsung
ro.product.name=GT-I9000
ro.product.device=GT-I9000
ro.product.board=GT-I9000
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=s5pc110
ro.build.product=GT-I9000
ro.build.description=GT-I9000-user 2.3.6 GINGERBREAD XWJVZ release-keys
ro.build.fingerprint=samsung/GT-I9000/GT-I9000:2.3.6/GINGERBREAD/XWJVZ:user/release-keys
ro.build.PDA=I9000XWJVZ
ro.build.hidden_ver=I9000XWJVZ
ro.build.changelist=762604
ro.flash.resolution=720
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
dalvik.vm.heapsize=64m
ro.opengles.version=131072
persist.service.usb.setting=0
ro.config.ringtone=01_Minimal_tone.ogg
ro.config.notification_sound=01_Sherbet.ogg
ro.config.alarm_alert=Good_Morning.ogg
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.locationfeatures=1
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=2.3_r8
wifi.interface=eth0
wifi.supplicant_scan_interval=15
ro.secdevenc=true
ro.error.receiver.default=com.samsung.receiver.error
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.ril.hsxpa=1
ro.ril.gprsclass=10
media.stagefright.enable-player=false
media.stagefright.enable-meta=false
media.stagefright.enable-scan=false
media.stagefright.enable-http=true
media.stagefright.enable-rtsp=false
dev.sfbootcomplete=0
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.com.google.clientidbase=android-samsung
init.svc.console=running
init.svc.recovery=running
init.svc.adbd=running
init.svc.setup_fs=stopped
init.svc.tvout=stopped
ro.radio.noril=yes
ro.bt.bdaddr_path=/efs/bluetooth/bt_addr
status.battery.state=Slow
status.battery.level=5
status.battery.level_raw=50
status.battery.level_scale=9
ro.telephony.call_ring.multiple=0
ro.nfc.port=I2C
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
-- Installing: /sdcard/cm-9.1.0-galaxysmtd.zip
Finding update package...
I:Update location: /sdcard/cm-9.1.0-galaxysmtd.zip
Opening update package...
Installing update...
package_extract_file: no updater.sh in package
set_perm: chown of /tmp/updater.sh to 0 0 failed: No such file or directory
set_perm: chmod of /tmp/updater.sh to 777 failed: No such file or directory
about to run program [/tmp/updater.sh] with 1 args
run_program: execv failed: No such file or directory
run_program: child exited with status 1
script aborted: assert failed: run_program("/tmp/updater.sh") == 0
assert failed: run_program("/tmp/updater.sh") == 0
E:Error in /sdcard/cm-9.1.0-galaxysmtd.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Does anybody understand anythong in that log?

Hilmy said:
Does anybody understand anythong in that log?
Click to expand...
Click to collapse
Status 7 means you may have improper radio/spl requirements for CM 9, try to Flash JVU ROM + Root ( from My Androids Collection link below )
Do the wipes before flash, suggest you re download the CM 9 zip file, could be reason for update.sh getting 0

Thank for your help xsenman. Your collection of Galaxy S files is amazing :good:
xsenman said:
Status 7 means you may have improper radio/spl requirements for CM 9, try to Flash JVU ROM + Root ( from My Androids Collection link below )
Click to expand...
Click to collapse
I tried the JVU radio from your collection. But still the same error...
When i was googleing my problem i found something else that could be the problem. It was a post about an other phone, but it had the same error like i have. Im useing CWM 3.0.0.5 which isent realy the newest one. They said the problem could be fixed by installing a newer version of CWM. But since the recovery in my case is baked in to the Kernel, i dont seam to be able to update it. When i open the newer update.zip in the old version i can open it, but it doesent realy install. I still get the Status 7 error and not eaven wipes are working. When I do the diffrent wipes it says finished after a second, but when i rebot the system I still get in the non wiped system. And when i reebot to recovery im in CWM 3.0.0.5 again...
I googled, but i dident find a way to update a CWM recovery that was installed by flashing a root kernel. Do you maybe know how that could work?
Or doesent that make any sense at all?
xsenman said:
Do the wipes before flash, suggest you re download the CM 9 zip file, could be reason for update.sh getting 0
Click to expand...
Click to collapse
I did allot of factory resets, cache wipes and dalvik cashe wipes already. Felt like 100 times already
Does anyboday have any good ideas? Would realy like to return my friends phone back to him running a nice custom ROM, after all those months i was pushing him to give it a try :silly:

Hilmy said:
I googled, but i dident find a way to update a CWM recovery that was installed by flashing a root kernel. Do you maybe know how that could work?
Or doesent that make any sense at all?
Click to expand...
Click to collapse
That is the problem your recovery (CWM) needs to be changed (not the modem) , the JVU CF root kernel should have done the job (if you had flashed it) , since it did not, flash the semaphore kernel from here http://forum.xda-developers.com/showthread.php?t=1112908

The problem is soleved It was something i dident eaven know its possible...
Since it wasent my phone, i never tried running it with a simcard. Today i was about to give up and give the phone back to my freind with stockrom. But stockrom dident get a network connection. So i rememberd seeing something about a deleted IMEI Number in xsenmens Android Solutions. I cheked the IMEI and found out the phone doesent have one anymore. That was the problem couseing the Status 7 error in the recovery
Xenmen your Android Solutions are amazing. If you have any problems with your I9000 have a look here: http://forum.xda-developers.com/showthread.php?t=1841250
Thanks for your suport Xenmen and thanks for your Android Solutions :good:

I agree, I've not had to use any of them yet, but I did have a little browse and xsenman's guides look very well written and laid out. A lot of effort gone to there, well appreciated by many.
GT-I9000 / SEMA / SLIMBEAN2.3

Update hellybean
Hi Guys,
I try to update my firmware to jellybean 4.1.2 and i tryed also to update te hellybean
This is what i get on my screen.
assert failed: run_program("/tmp/updater.sh") == 0 assert failed: run_program("/tmp/updater.sh") == 0
E:Error in /sdcard/jellybean 4.1.2/cm-10.1-20121222-NIGHTLY-galaxysmtd.zip (Status 7)
Who can help me please for to update me samsung galaxy GT I9000 to hellybean