Database Develop

[I9020T][ROM][STOCK]Nexus S Android 2.3.1, Build GRH78 Factory Firmware

Please read this post in its entirety before downloading and flashing.
THIS IS FOR I9020T ONLY! IF YOU DECIDE TO GET BRAVE AND TRY THIS ON AN I9020A, I9023 OR D720, MAY THE FORCE BE WITH YOU. I AM NOT RESPONSIBLE FOR ANY DAMAGE CAUSED TO ANY PHONE BY USING THIS ROM.
YOU MUST FLASH THIS ROM USING CLOCKWORKMOD RECOVERY. THIS WILL NOT FLASH USING THE STOCK ANDROID 3E RECOVERY AS THE ZIP FILE IS NOT SIGNED. I HAVE NOT TESTED IT ON OTHER RECOVERIES.
This is probably more for posterity now than anything else, however I have created a CWM-flashable full on ROM for the Nexus S Gingerbread firmware, version 2.3.1, build GRH78. This is built exactly the same way that the full OTA ROM packages for 2.3.3 and 2.3.4 were built.
Some notes:
1. Flashing this ZIP will remove ClockworkMod Recovery on first boot. Android 2.3.1 introduced a script that automatically overwrites alternate recoveries with the stock Android 3e recovery each time you reboot your phone. The script is located in /system/etc/install-recovery.sh. If you root the ROM, you can rename this file to avoid flashing the stock recovery on each reboot.
2. Flashing this ZIP will overwrite your bootloader and radio, restoring them to I9020XXJK1 and I9020XXJK8 respectively. These are the versions that came stock with GRH78.
3. GRH78 is receiving OTA updates. As of this writing, the latest version of Android is 2.3.4, and Google is pushing an OTA update for 2.3.1 to 2.3.4.
4. This ZIP will NOT clear your user data or cache. For users running a stock ROM, I would highly suggest clearing your data and cache manually as sometimes downgrading without clearing data and cache can cause problems. If you are coming from a non-stock ROM, you are required to clear your data and cache or the ROM will not boot.
5. Since writing NFC tags wasn't introduced until GRI40/2.3.3, the Tags app is read-only.
6. There is no video chatting through Google Talk. This feature was not introduced until GRJ22/2.3.4.
Instructions:
1. Download the Stock GRH78 ROM package here.
2. Copy it to the root of your USB storage.
3. Reboot into ClockworkMod Recovery (or flash it).
4. Select "Install ZIP From SD Card"
5. Select "Choose ZIP"
6. Find the ZIP file and select it.
7. Wait for it to finish.
8. Wipe data and cache (optional but HIGHLY recommended for stock ROM users and REQUIRED for non-stock ROM users)
9. Reboot and have fun.

Reserved...just in case.

Hello,
I tried your ROM with my Nexus S (I didn't know the version exactly) and I have now a black screen and the phone won't boot or show me anything =(

OyoKooN said:
Hello,
I tried your ROM with my Nexus S (I didn't know the version exactly) and I have now a black screen and the phone won't boot or show me anything =(
Click to expand...
Click to collapse
Aw come on man.......you gotta read! Can you get into recovery?
Sent from my Nexus S using XDA Premium App

Yes I know, I'm a dumb ass.
I have only access to fastboot (via Terminal only).

Try flashing Clockwork Mod Recovery with fastboot.
fastboot flash recovery.img

I did but I even don't know if I can boot into the recovery because the screen stay off.

Can you get to the bootloader? If you don't even see the bootloader screen, you may have bricked it.

I managed to fix it using ODIN.
Thanks.

Congrats Glad you got it working.

plz plz help begging u !
OyoKooN said:
I managed to fix it using ODIN.
Thanks.
Click to expand...
Click to collapse
i made the same mistake plz plz help me ....
i m stuckkkkk !

Lol I can't help but say what a bunch of retards haha. Make sure you gave the correct version before flashing. Might give it a try one of following days
Sent from my Nexus S

[Recovery] Unofficial TWRP 2.6.3.0 for XT901 / XT907

UNLOCKED BOOTLOADER REQUIRED
Here it is: TWRP 2.6.3.0
I've tested backing up / restore, wiping, and installing an old backup (from ver. 2.6.0.0) and all seem to work. I also included the flag "HAVE_SELINUX := true" so it should be compatible with the newer 4.3 based ROMs (needs tested).
To install:
Download and unzip file ("img" was a few bytes over the 8mb forum limit)
Code:
fastboot flash recovery XT901-XT907-TWRP-2.6.3.0-recovery.img
BUGS: I have had the screen start very dim. Sometimes restarting the recovery would fix it, otherwise go to settings / screen, and set the timeout short so it goes out. Press power to turn on and it is at full brightness.
Enjoy!!
Thanks to:
TeamWin for TWRP.
Hashcode and Dhacker for STS-Dev Team source.
Djrbliss for unlocking the bootloader & providing root in the first place.
and mattlgroff

Thank you! Just tested it briefly and it works great. Glad the recovery is finally fixed to be able to use ADB. Was unable to use any TWRPs from 2.5.0.0+ as ADB was broken in the recovery.

CM 10.2 Build removed due to errors.

jbaumert said:
OP updated with link for TWRP compiled with CM10.2 sources
Click to expand...
Click to collapse
The recovery built with the 10.2 sources seems to have an issue with mounting the internal storage and sdcard, but the 1st one built is running perfect. I made a flashable zip of the 2.6.3.0 recovery for anyone who wants to simply flash it in recovery.

@mic213, Thanks for the sanity check. Any chance you have tried backup / restore of a 4.3 build?
Sent from my XT901 using Tapatalk 4

I was able to backup with it. Still hangs at reboot.
Sent from my XT907 using Tapatalk 4

netizenmt said:
Still hangs at reboot.
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
Do you mean when you reboot from TWRP? I noticed that on other builds, but didn't think much of it.

Recovery Tools is a free app on Google Play. Simply download the Recovery IMG. file from this post, and then open the Recovery Tools app. Grant it root, and now you can simply flash the img. file from the app without having to go into fastboot or compress the file into a flash able zip. Once recovery is flashed phone will reboot into whichever recovery is the most recently flashed. About as basic and straight forward as can be.
---------- Post added at 09:34 PM ---------- Previous post was at 09:22 PM ----------
The recovery file works great, only bug after about 4 days of use would be the dim menu screen in recovery. Still very readable even when bug pops up. Thanks for the great upload

Thanks. I could never get 4.3 to reboot past the initial boot after install, and now it finally does.

scottocs said:
Thanks. I could never get 4.3 to reboot past the initial boot after install, and now it finally does.
Edit....ehh maybe. Still working on it.
Click to expand...
Click to collapse
just make sure everything is wiped and that you are using 4.3 Gapps, also look up the SuperSU 1.65 update, some people have had trouble keeping root when rebooting into 4.3. Flash 4.3 ROM then GAPPS followed by SuperSU update, I would suggest running 4.3 on TWRP 2.5 or 2,6 first. Once your able to run 4.3 on one of those, then good ahead and try flashing 2.6.3. If anything on your phone is 4.2 and trying to load onto 4.3 it will never make it far past the boot screen.

Edited because I started rambling and couldn't delete.
Long story short, I have been having issues wiping, installing, and recovering.
I was flashing from a 4.3 ROM to another 4.3 ROM and decided it would be a good idea to wipe internal. Messed me up good.
I went back to 4.2 finally fixed booting issue on getting stuck at boot image. (Wasn't even making it to the boot animation.) I'll wipe everything except internal like I did before and go from 4.2 to 4.3. Last time I did this I didn't have issues.

motoroid7 said:
I'm not sure what I did, but some ROMs suggest that you wipe internal memory. I did this but now I have the issue after installing a ROM and booting it up... playing with it, if I then go to reboot the phone at all I just get stuck on my boot image (not the animation.) This happens on regardless of what ROM I've installed.
I also now can't go back to my backups. They fail on restoring. [Most recent backup was made on 2.5.0.0, previous to that 2.3.2.3]
How do I fix my phone? I'm wondering if I need to fxz back to a rooted stock ROM to fix what's going on?
Click to expand...
Click to collapse
This happened to me on TWRP too. When I went to restore, it say that it failed. However, I decided to boot into system anyway. TWRP gave me a warning that no OS was installed but I went ahead and rebooted. It booted into my backed up ROM just fine but it needed to be set up, like I just had flashed it. Basically, the restore process restored everything but my data. I did a barebones set up then booted back into recovery and went to restore the same exact ROM. This time, I got my complete ROM, just as I had saved it. This is kind of a long process, but it's better than having to FXZ or using a utility to go back to stock.

RikRong said:
This happened to me on TWRP too. When I went to restore, it say that it failed. However, I decided to boot into system anyway. TWRP gave me a warning that no OS was installed but I went ahead and rebooted. It booted into my backed up ROM just fine but it needed to be set up, like I just had flashed it. Basically, the restore process restored everything but my data. I did a barebones set up then booted back into recovery and went to restore the same exact ROM. This time, I got my complete ROM, just as I had saved it. This is kind of a long process, but it's better than having to FXZ or using a utility to go back to stock.
Click to expand...
Click to collapse
It's too bad I can't seem to locate the delete button on these posts, I'll go ahead and edit it. I was finally able to flash LiquidSmooth v2.9 (Android 4.2). It finally booted up, I just went back in and flashed gapps. It restarted fine. The real test is going to see if I go to hit a regular reboot and it boots up normally again. If that's the case I'm fixed. I would like to flash back to SlimROM that I had, but it seems that's going to probably be difficult without it messing up again. Not sure what to do if it does again. I won't be wiping internal memory anymore. I didn't have issues going from 4.2 to 4.3 when I didn't do it.
Any idea why I get a funky e:error: unknown media 'datamedia' error all the time in TWRP? I've had that error since like v2.3.x.x

motoroid7 said:
It's too bad I can't seem to locate the delete button on these posts, I'll go ahead and edit it. I was finally able to flash LiquidSmooth v2.9 (Android 4.2). It finally booted up, I just went back in and flashed gapps. It restarted fine. The real test is going to see if I go to hit a regular reboot and it boots up normally again. If that's the case I'm fixed. I would like to flash back to SlimROM that I had, but it seems that's going to probably be difficult without it messing up again. Not sure what to do if it does again. I won't be wiping internal memory anymore. I didn't have issues going from 4.2 to 4.3 when I didn't do it.
Any idea why I get a funky e:error: unknown media 'datamedia' error all the time in TWRP? I've had that error since like v2.3.x.x
Click to expand...
Click to collapse
Not 100% sure, but i believe that when you wiped your internal memory on 4.3 you deleted the ROOT. SuperSU seems to be having issues with
carrying over root on 4.3 to some peoples devices, Ive had to flash SuperSU update 1.65 from recovery otherwise when ROM boots up I get stuck in a cycle of SU Binary update/reboot. Also make sure that in Developer Options in your custom ROM, that Root Access is set to APPS and ADB and the same in SuperSU - APPS/ADB. Now to clarify I may be merging two unrelated issues together. If so, my bad lol.. But from my experience running PaCMan 4.3 since August, and now running TWRPS 2.6.3 since OP , 4.3 ROOT will not revert back to 4.2 unless Recovery is included in the backup. One final suggestion, try flashing the boot.img from 4.2 before flashing your 4.2 restore. I was able to revert back to 4.1 restores when I upgraded to 4.2 but while running 4.2 I deleted the Root Data from Internal Storage, I strongly suggest looking up arrrghhhs Sept. 15th Kernal for XT 926 which runs the same for XT 907. It damn near all the way current with CM 10.2 merges, should make running which ever 4.3 ROM you want much easier. If you want to run a 4.2 Rom , look up arrrghhhs 10.1 kernal version.
Arrrghhhs xt926/907 kernal

Kyles1329 said:
Not 100% sure, but i believe that when you wiped your internal memory on 4.3 you deleted the ROOT. SuperSU seems to be having issues with
carrying over root on 4.3 to some peoples devices, Ive had to flash SuperSU update 1.65 from recovery otherwise when ROM boots up I get stuck in a cycle of SU Binary update/reboot. Also make sure that in Developer Options in your custom ROM, that Root Access is set to APPS and ADB and the same in SuperSU - APPS/ADB. Now to clarify I may be merging two unrelated issues together. If so, my bad lol.. But from my experience running PaCMan 4.3 since August, and now running TWRPS 2.6.3 since OP , 4.3 ROOT will not revert back to 4.2 unless Recovery is included in the backup. One final suggestion, try flashing the boot.img from 4.2 before flashing your 4.2 restore. I was able to revert back to 4.1 restores when I upgraded to 4.2 but while running 4.2 I deleted the Root Data from Internal Storage, I strongly suggest looking up arrrghhhs Sept. 15th Kernal for XT 926 which runs the same for XT 907. It damn near all the way current with CM 10.2 merges, should make running which ever 4.3 ROM you want much easier. If you want to run a 4.2 Rom , look up arrrghhhs 10.1 kernal version.
Arrrghhhs xt926/907 kernal
Click to expand...
Click to collapse
To piggy back on general advice: I found I was having all sorts of problems going from 4.2 to 4.3. What finally did the trick was I wiped Dalvik, System, Cache AND I formatted data. The formatting was what did the trick.

When you wipe in twrp 2.5+ the recovery does not delete data/cache from internal (system) unless user mounts system prior to wipe. Wiping system cache, data, and dalvik cache is a full system wipe. Recommended if switching ROM rather than flashing nightly. This way no files from a AOKP ROM stick around and try to associate with your new CM based ROM.
Sent from my XT907 using Tapatalk 2

Thanks for the advice guys.
I was finally able to successfully getting my phone to work again last night (very early in the AM). It's very strange. I actually had 0 issues going from LiquidSmooth v2.9 to LiquidSmooth v3.0 (4.2 to 4.3). Though it was from the same dev could be part of it. It wasn't until I tried flashing from SlimROM/4.3 to CM10.2 nightly (where I wiped internal memory requiring me to type "yes".) Another thing is strange is even though it was saying I lost root in TWRP, I'm not sure that I ever did, unless TWRP just re-installed it when I reboot recovery automatically... because I finally told it no when asked if I wanted to re-install root? Then I was finally able to get LiquidSmooth v2.9 bootable and stable.
Again, thanks for all the help guys. I just wish I had a little bit understanding what I all did to finally get it to boot up. It was pretty early in the morning... going on 5/6AM. So I was pretty tired doing all of this. I just knew I couldn't let my phone not be up and running by morning.

I did a backup last night, flashed a 4.3 ROM which had reboot issues, and then restored with this version. I had zero issues, unlike when I was trying to restore with the previous version. Thank-you for your work.

It works with the xt902 too. Thanks!

What's the difference between the link in the first post and the one in the fourth? One of the is broken? Which one has been built with the CM10.2 sources?
I'm using a CM10.2 ROM... Which one should I peek?
Thanks!

[Q] will i lose root while upgrading to 12.1.A.1.201 from 12.1.A.0.266?

Hi,
I'm currently running stock 4.3 (12.1.A.0.266). My phone is ROOTED, but have LOCKED BOOTLOADER. I have
My question is simple: will I lose root? Or any apps/data/sms/etc for that matter?
I just don't want to do all the stuff all over again. 12.1.A.0.266 is buggy but still is tolerable. >.>

wakoko79 said:
Hi,
I'm currently running stock 4.3 (12.1.A.0.266). My phone is ROOTED, but have LOCKED BOOTLOADER. I have
My question is simple: will I lose root? Or any apps/data/sms/etc for that matter?
I just don't want to do all the stuff all over again. 12.1.A.0.266 is buggy but still is tolerable. >.>
Click to expand...
Click to collapse
Yes, you'll lose root if you update via OTA or flashing stock.
However, I think OTA does not wipe data, so you'll probably have your data. Do back them up just in case (can't remember since it's been a while since I last update via OTA ).
If you want rooted .201, install either of these roms:
http://forum.xda-developers.com/showthread.php?t=2704312
(v1.1 looks and works like 201)
http://forum.xda-developers.com/showthread.php?t=2658043
(v2 is a much "improved" version of the above)
I have installed the first one and loved it.
A few days ago I installed the second one and loved it even more.
Whatever you do, do a nandroid backup of your .266 (and preferably, add titanium backup of your apps and data/sms/contacts)

my mobile vibrating only after reboot!!!!!
My mobile was a rooted onewith .266 verson and i was trying to put the new rom and screwup!! ias you told i installe i downloaded the new rom v2 and super user,and dual recovery files... i ectracted from sd card all as you tol one by one ...while reboot...i saw sony logo and vibrating freequently only...not opening....!!!!!!!!!!! i tried to reset..same thing.....screwed up?!!!!!
headache59 said:
Yes, you'll lose root if you update via OTA or flashing stock.
However, I think OTA does not wipe data, so you'll probably have your data. Do back them up just in case (can't remember since it's been a while since I last update via OTA ).
If you want rooted .201, install either of these roms:
http://forum.xda-developers.com/showthread.php?t=2704312
(v1.1 looks and works like 201)
http://forum.xda-developers.com/showthread.php?t=2658043
(v2 is a much "improved" version of the above)
I have installed the first one and loved it.
A few days ago I installed the second one and loved it even more.
Whatever you do, do a nandroid backup of your .266 (and preferably, add titanium backup of your apps and data/sms/contacts)
Click to expand...
Click to collapse

Yup - screwed up somewhere in the process but no worries.
The process is almost the same way you got your .266 root.
To get new root and recoveries:
a. Flashtool - choose .257, then follow prompt to hook in your usb cable while pressing the Vol-down button
b. Once complete, close flashtool, unplug your device and reboot device
c. Once loaded and past the minor set up, turn on usb debugging and check "unknown sources" (all under settings)
d. Assuming you have all adb drivers installed (through flashtool installation), hook up your device to the PC and install Doomlord's exploit V18 and recoveries
Install new root 201
Boot into recoveries and flash the said .201 rom+SU+recovery (all zip files) using TWRP. Make sure you wipe cache/dalvik cache/data first. After flashing the zip files, select reboot from TWRP, and let the phone run a bit as it sets itself up (android and sony) during the booting process.
Note:
Ultimate purexsp V2.1 zip is simply an update file (not the full rom) - don't flash this one yet.
Somewhere within the thread you'll find the V2 full rom <663MB in size (as seen in my ext SD card). Flash this one and ignore the other versions
Edit:
Here it is:http://forum.xda-developers.com/showpost.php?p=51733368&postcount=423

stucked on SONY cant open...!!!
Again >> i tried to flash with XperiaSP_C530X_12.0.A.1.257_KernelOnly.ftf file but same thing..after flashing when iam switching on..its stuck on the SONY.... not moving foeward.!!!!!!! give me solution...if its open i can do somthing...
one more can i flash directly with your v2?V2 full rom <663MB or i will flash first with v1 then v2? plz clerify..
headache59 said:
Yup - screwed up somewhere in the process but no worries.
The process is almost the same way you got your .266 root.
To get new root and recoveries:
a. Flashtool - choose .257, then follow prompt to hook in your usb cable while pressing the Vol-down button
b. Once complete, close flashtool, unplug your device and reboot device
c. Once loaded and past the minor set up, turn on usb debugging and check "unknown sources" (all under settings)
d. Assuming you have all adb drivers installed (through flashtool installation), hook up your device to the PC and install Doomlord's exploit V18 and recoveries
Install new root 201
Boot into recoveries and flash the said .201 rom+SU+recovery (all zip files) using TWRP. Make sure you wipe cache/dalvik cache/data first. After flashing the zip files, select reboot from TWRP, and let the phone run a bit as it sets itself up (android and sony) during the booting process.
Note:
Ultimate purexsp V2.1 zip is simply an update file (not the full rom) - don't flash this one yet.
Somewhere within the thread you'll find the V2 full rom <663MB in size (as seen in my ext SD card). Flash this one and ignore the other versions
Edit:
Here it is:http://forum.xda-developers.com/showpost.php?p=51733368&postcount=423
Click to expand...
Click to collapse

Thanks!!! done
Finally its done..!!!!!! i dont know wht i did..finally everythings allright..!!!:victory::victory::victory::victory::victory::victory::highfive::highfive::highfive:
babugd said:
Again >> i tried to flash with XperiaSP_C530X_12.0.A.1.257_KernelOnly.ftf file but same thing..after flashing when iam switching on..its stuck on the SONY.... not moving foeward.!!!!!!! give me solution...if its open i can do somthing...
one more can i flash directly with your v2?V2 full rom <663MB or i will flash first with v1 then v2? plz clerify..
Click to expand...
Click to collapse

Congratz and enjoy the new fantastic rooted rom!

[Q] P880 does not boot after installing Vanir 4.4

So I have done the following steps:
Rooted my phone using Kingo root
Did a backup using Droidexplorer
Unlocked bootloader (check by entering secret menu)
Flashed CWM Touch recovery from their site for the LG Optimus 4x HD
Made a backup using CWM
Did a factory reset
Flashed Vanir 4.4 rom, I used the bottom one from here: http://www.emccann.net/nuclearmistake/VanirAOSPNightlies/p880/
Rebooted, did not get past LG logo after leaving for 15 minutes, removed and reinserted Battery
Rebooted into recovery wiped the cache and dalvik cache
Rebooted again and did not get past LG logo again after leaving for 15 minutes
I have no idea which Vanir 4.4 release is stable as the first post isn't updated here: http://forum.xda-developers.com/showthread.php?t=2609285
I also cannot find a Vanir 4.3 release as the download points to the same page as the 4.4 version which only shows a limited amount of releases.
What is my next step?

WitchHunterNL said:
So I have done the following steps:
Rooted my phone using Kingo root
Did a backup using Droidexplorer
Unlocked bootloader (check by entering secret menu)
Flashed CWM Touch recovery from their site for the LG Optimus 4x HD
Made a backup using CWM
Did a factory reset
Flashed Vanir 4.4 rom, I used the bottom one from here: http://www.emccann.net/nuclearmistake/VanirAOSPNightlies/p880/
Rebooted, did not get past LG logo after leaving for 15 minutes, removed and reinserted Battery
Rebooted into recovery wiped the cache and dalvik cache
Rebooted again and did not get past LG logo again after leaving for 15 minutes
I have no idea which Vanir 4.4 release is stable as the first post isn't updated here: http://forum.xda-developers.com/showthread.php?t=2609285
I also cannot find a Vanir 4.3 release as the download points to the same page as the 4.4 version which only shows a limited amount of releases.
What is my next step?
Click to expand...
Click to collapse
I suggest using TWRP Recovery instead from Adams Omni thread, flash that like a zip in recovery and then re-reboot to recovery and load TWRP.
go to wipe>Advanced Wipe
And select cache, Dalvik Cache, System, and Data, and swipe to wipe them at the bottom.
Then go back to install, and find the Rom Zip and flash the Rom and then reboot, if it still isnt working, re-download the file, or choose a different rom and see if that one boots for you.

I don't think the recovery can be the problem here, so I would start with checking the download, and perhaps trying another ROM.
© Nexus 7 (2013)

Its probably an outdated recovery version you're using I know that only twrp 2.6.3.0 and up support flashing KitKat Roms
don't forget to hit thanks!

abhi08638 said:
Its probably an outdated recovery version you're using I know that only twrp 2.6.3.0 and up support flashing KitKat Roms
don't forget to hit thanks!
Click to expand...
Click to collapse
If he was using an outdated recovery, in the case of CWM anything below 6.0.4.4, he wouldn't even be able to pass the installation as he would get a status 7 error. Since he got to the point where he was ready to boot, again I don't think it's the recovery's fault. But to clear things up, would the OP mind sharing his recovery version?
If you do want to stick with Vanir, another thing you could try is to flash a custom kernel on top of the ROM and see if it boots then. Good luck!
© Nexus 7 (2013)

[Q] Phone fails to start installing ROM

Okay so, I'm not exactly sure if this is the right place but I'll ask here anyway.
I took my old i9000 out of the closet and started playing around with it as I want to use it on my upcoming travel. To make long story short, I used to have a custom ROM on the phone all those years ago, but I am by no means an expert on the subject.
So what I have done so far today:
1. Returned the phone to stock ROM with Odin (XWJW1 or something, most recent anyway)
2. Rooted with Semaphore 2.7.4.
3. Installed Rom Manager and Superuser to check for CWM updates (which caused some sort of a verification error when I tried to boot to CWM through the app).
4. Downloaded the appopriate Slimkat and gapps and moved them into the internal storage.
But after the last step (and after wipe cache, format system etc) when I try to install the ROM, the bar on the screen progresses only slightly and after "Installing update..." it crashes (just goes black without any error messages) and gets stuck with just "Semaphore" on the screen.
I wish to update the phone to Slimkat 4.4.2. But what causes this problem, any ideas? Am I doing something wrong? If anyone can give any help that would be much appreciated!
PS. If I wanted to install for example Philz recovery, how am I supposed to do it when the file is .img?

Anyone?

I guess no one is using this phone anymore?

Yes, you are doing many things bit wrong.... (and many people use this phone still). I hope following will help you:
*recovery and kernel are sharing the same partition on the i9000 what means that you can't flash recovery separately
*make sure to backup your IMEI if still there
*flash first CM10.2 to get updated recovery for KitKat roms and to resize the system and data partitions to those used by all KitKat roms and reboot once into the system. You will need to flash trice to make it work (1. only warning of resizing to come and data lost- and status 7 abort, 2. only recovery update, 3. successful flashing)
*flash SlimKat and latest SlimGapps (addons) for 4.4.4
*PhilZ touch screen isn't yet working well on the i9000 but if you flash Mackay KK kernel, you can get beautiful TWRP touch recovery
tetakpatalked from Nexus 7 flo