[Galaxy S I9000 Q&A, Help & Troubleshooting] SkySwimmer:
My interesting journey with my Galaxy S1 i9000

Hey everyone, I could do with your help . .and im not too proud to say - i need it badly http://xdaforums.com/images/smilies/eek.gif

Below is what happened & my question is how to i get back to where i was flashing roms successfully from CWM?

I bought my first Galaxy i9000 3 weeks ago, a move up from a Galaxy 3 i5801 & I was delighted with it, yeh I know its quite behind the Galaxy s3 & now the S4 but still it has a lot to offer I believe. SO on with my adventure to get custom roms onto it, I thought hmmm wouldn’t it be nice to have Jelly Bean on it & bring some new life into this old workhorse of a smartphone. I was a total noob 3 weeks ago but figured out quite a few things & did the following

1.	With odin I Installed Stock gingerbread firmware JW4 inplace of the froyo that was on it

2.	I rooted the phone with superoneclick & it worked first time like a charm

3.	I then flashed Clockworkmod recovery through odin & then discovered my S1 is one of those that wont boot into recovery or download mode with the 3 button combo (spent hours fiddling with the buttons)]

4.	Didn’t give up there & I discovered I can install custom kernels with CWM preinstalled in which I had an option in the phones main menu to reboot into recovery mode, I thought Bingo im a zip flash away from a nice new Jelly in your belly rom, but something got messed up & I softbricked it, or so I hoped it was just softbricked, but either way I couldn’t get into download mode coz my phone doesn’t have the 3 button combo!

5.	Not giving up there I found out you can get a usb jig to boot into download mode, a week later it came & I couldn’t wait to stick that little fella in the usb slot & see if he’s boot my ole S1 into that famous save your backside download mode, low & behold it did, whippeee

6.	I then re did steps above 1 to 3 & this time I got into recovery mode, but still only from the phones power off menu that came with the custom kernel, my usb jig only gets me into download mode I’ll have you know

7.	So into recovery I went & bam I successfully installed Slim bean 4.1 (as I heard 4.1 roms have most compatability right now) Hooraaay I have a sweet slick Jelly bean rom on my S1 happy days im gonna enjoy this

8.	But as faith would have it, my fun in JellyBean world wasn’t to last too long, I tried installing HD games & non HD games but they wouldn’t play – just a frozen black screen & no sound. I presumed not all games are compatable with all android phone even thought were supposed to be a universal platform (ehem) but I thought I’d try another custom rom for the hell of it, plus I wanted to try others out & maybe as a bonus some games would work.

9.	Into recovery mode I went & I attempted to install AOKP M technology 6.1 & even thought I cleared caches & factory wiped the rom progress bar gets about 3 percent progress then the phone resets & im left sitting their looking at a sephamore logo, now as lovely as that logo is (thanks sephamore kernel guys, I think it’s a kernel!) I don’t wanna look at it all day!

10.	So back to my life saving Usb jig & I have to do steps 1 – 3 just to get into recovery mode, I basically need a stock rom with a custom kernel that gives me an option to reboot into recovery coz of my pesky 3 button combo problem, i.e. I have to do a lot just to get into recovery each time.

11.	Now everytime I try to install a custom rom from recovery even the slimbean that was the first one that worked, they all get about 10 seconds into the flash & reboot & hang at the logo. All I can do now is flash a stock gingerbread rom but now I cant even root the stock gingerbread with superoneclick, this suggests I messed up something on a very deep level in the phones system partition where superoneclick goes to do its thing. For example in the log in S1click it seems to not be able to find an important directory on the system partition "/data/local/tmp/output

/system/bin/su: No such file or directory" Did i damage this?

I think if I can find out why superoneclick cant root my phone then I can flash zips from recovery again, i.e. jelly bean roms in particular. It seems every since I tried to install another jelly bean rom after the first one its messed up things, most likely the person writing this, but I always read all the rom instructions carefully & its usually just do a cache wipe etc.

12. The only way I can root is by flashing stock gingerbread then Chainfire’s stock kernel with CWM in it, this get me rooted & an option to reboot into recovery from gingerbread desktop but I still cant flash roms from recovery.

Any advice to get me some jelly again would be much appreciated – here's the last part of a log from superoneclick from your information. Ive trolled the forums for a couple of days now & I cant find a solution, I need expert help!

ls -l /system/xbin/su > /data/local/tmp/output 2>&1

export TEMPRANDOM=19900

export PS1=END:$TEMPRANDOM;cat /data/local/tmp/output

/system/xbin/su: No such file or directory

END:19900export PS1=""

ls -l /system/bin/su > /data/local/tmp/output 2>&1

export TEMPRANDOM=82318

export PS1=END:$TEMPRANDOM;cat /data/local/tmp/output

/system/bin/su: No such file or directory

END:82318export PS1=""

[+] Found a GingerBread ! 0x00000118 [+] Found a Samsung, running Samsung mode [*] Scooting ... [*] Sleeping a bit (~40s)... [*] Waking ! [*] Sending 149 zerglings ... [*] Sleeping a bit (~40s)... [*] Waking ! [*] Sending 189 zerglings ... [-] Hellions with BLUE flames !

END:24611export PS1=""

export PS1=""

/dev/block/stl10 on /dbdata type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8)

/dev/block/stl11 on /cache type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8)

/dev/block/stl6 on /mnt/.lfs type j4fs (rw,relatime)

/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)

/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)

END:74469export PS1=""

mount -o rw,remount /dev/block/stl9 /system > /data/local/tmp/output 2>&1 export TEMPRANDOM=83883 export PS1=END:$TEMPRANDOM;cat /data/local/tmp/output mount: Operation not permitted END:83883

Thanks a mill for reading this everyone