[Galaxy S I9000 Android Development] madsci44:
trying to fill in the blanks to return to stock kernel

Hello

I have a brand new i9000M (bell version in Canada) It was stock with i9000UGJH2. I applied voodoo beta 4 lagfix via update.zip method approx 1 week after I received the phone.

Before the lagfix, standby (very light, if any usage) was draining about 4% per day.

After applying the lagfix, standby drain jumped to about 6% per hour, and disabling lagfix makes no difference (enabled or disabled) to the battery drain.

I was able to verify with quadrant that I was enabling and disabling correctly. (1680 or so when enabled). Besides the quadrant score, I didnt notice any dramatic difference in the phone operation. It seemed good both with and without the lagfix. (maybe samsung has improved this in more recent stock builds?) The color improvements were noticeable in bright modes.

Other than the lagfix, the phone had not been rooted, flashed, or unlocked or modified from stock in any way. Since I do not currently use them, I always have wifi, gps, and bluetooth completely turned off. The only widget running is the app monitor and - as with all other settings - were the same both for the period before and after I installed the lagfix. - - Incase any of that is helpful info.

From the reading I have done, I am guessing that different firmwares must have some variations in kernel config to do with the rest of the setup that would account for the differences in results others are having but I have no idea.

In any case, I have decided I would like to restore my original stock kernel. The most convenient method would have been redbend_ua - I am a long time linux user, but I am new to android and smartphones. I rooted and got adb working, I found my bml7 backup image, but could not execute the redbend_ua which I extracted from voodoo's update.zip. I tried chmod 755 on the file to set the execute bit for owner but I guess android wont allow executable on SD? I had done su of course. /sbin was mounted read-only, I was going to try remounting rw to move the file over there with a different name so as not to overwrite the original, but decided I dont know enough to judge if that was a good idea or if it would even work. I'm not familliar enough with android's particular setup.

After further reading the redbend method would still be the most convenient, but it looks like I will have to boot into windows and try odin. I renamed the bml7-zImage-kernel-backup.img to bzImage and did the tar -cf, and am ready to try odin as a last resort. I have some questions first;

1) Has anyone actually tried restoring their kernel from this voodoo-created backup image via odin successfully?

2) I think understand about flashing PDA only, (no CSC no Phone) - Is it necessary to use a .pit file in this case as with a stock firmware?

3) I presume in this case since its a partial firmware (is it?) then "repartition" should *not* be checked?

4) If I am able to restore my stock kernel, will there be any other remnants of the voodoo lagfix on the system other than the installation files on the SD card? - will the partition arrangement still be the same as stock?

5) Also my phone is sim-locked, I presume now I'll have to unlock to do via odin??

I really wish I could use the redbend method - frankly in my opinion its all dangerous if one isnt careful or is ill informed. - In my case I am more comfortable with shell.

Its unfortunate there isn't a clean reversal version of update.zip - or some generic method of swapping out kernels via that route - it would be so easy to test back and forth.

Thanks in advance for any clarification.