Why in the world would you buy an android and then want to install wm7? Get a Nokia.

Did you download KJ2 stock from 1st post? Extract it from there.

Weird and strange stuff just happened. I tried to do the removal of the triangle and it takes such a long time to flash to the stock kernel. So disconnect the phone and it gave me the phone-to-pc screen (soft brick or something).
And there is no way that I can get into download mode again.

Then I just connect the phone again in the brick-mode to pc, fire up odin and load up the stock rom and it flash the rom successfully and reboot the phone.

Now, here is the weird thing, I was SuperRom 1.1 before I flashed the stock. After flashed and reboot, the phone still retain all settings and apps of the previous rom. NONE of the stock rom system apps were found after reboot, only the kernel were retained. Now I longer has root to the kernel.

Going back to 1st post to root, lol.

First try on the rooting with doomlord, failed.
A lot of errors when it tried to write the su apps. Will submit a screen capture if 2nd round fail again. On v3 first try.

Now on v2 and see, 10 minutes and still stuck at

[+] Found a GingerBread ! 0x0002e118
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] Sleeping a bit (~40s)...
[*] Waking !

This the 2nd try.
Still a lot of error. this is the runme.bat after edit.

@echo --- STARTING ----
@echo --- WAITING FOR DEVICE
@files\adb wait-for-device
@echo --- cleaning
@files\adb shell "cd /data/local/tmp/; rm *"
@echo --- pushing zergRush"
@files\adb push files\zergRush /data/local/tmp/.
@echo --- correcting permissions
@files\adb shell "chmod 777 /data/local/tmp/zergRush"
@echo --- executing zergRush
@files\adb shell "./data/local/tmp/zergRush"
@echo --- WAITING FOR DEVICE TO RECONNECT
@echo if it gets stuck over here for a long time then try:
@echo disconnect usb cable and reconnect it
@echo toggle "USB DEBUGGING" (first disable it then enable it)
@echo --- DEVICE FOUND
@echo pause
@echo --- pushing busybox

And this is the result after pushing the ram more than 500MB.
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- cleaning
--- pushing zergRush"
1324 KB/s (23056 bytes in 0.017s)
--- correcting permissions
--- executing zergRush

[**] Zerg rush - Android 2.2/2.3 local root
[**] © 2011 Revolutionary. All rights reserved.

[**] Parts of code from Gingerbreak, © 2010-2011 The Android Exploid Crew.

[+] Found a GingerBread ! 0x0002e118
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[+] Zerglings found a way to enter ! 0x18
[+] Overseer found a path ! 0x000305e0
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[+] Overseer found a path ! 0x000305e0
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[-] Zerglings did not leave interesting stuff
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
pause
--- pushing busybox
1955 KB/s (1075144 bytes in 0.537s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting

----------------------

It didn't reboot

Oops, silly mistake on the code. Instead of @echo to @pause, its @echo pause.
Shouldn't be doing this noob mistake. Trying again with the correct code.

Doesn't work. maybe my sgs already messed big time.
Time to odin flash root kernel.

This post has been edited by rainbow6: Dec 14 2011, 07:39 PM

I think its up and online now.

Depends what were you using the phone for 2.5 hours.
Charge to full and then do battery calibrate either thru CWM or download from market Battery Calibrate.
I don't know about others, but my battery is about 2-2.5% per hour on normal usage so if you can get about that or better, then your battery life is ok.
Else, check runaway processes that is draining battery such as wifi sharing etc.. Oh lastly, if you are using dlink wifi router, watch out, that could be the main battery killer literally.

My DIR655 can wipe out all my androids(SGS1, SGS2, MINI, and IPAD2) battery in 8 hours.