yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 General] JaY_III:
I actually miss that app. Any way we can get it back?
[Galaxy S I9000 General] DT3CH:
Ya I dont know why anyone would even wanna be on KG3 except for a couple of reasons, you wanna keep the phone completely stock, or you have something wrong with the phone and wanna return it to stock for a warranty repair

Anytime an offical ROM is released, you pretty much usually just want the modem and to a lesser extent the CSC (provided that its not the most recent release/leak i.e. the Swiss JVR), Ive been waiting all this time to get an official GB modem for Bell but thats it...

Why stick around on 2.3.3 when you can have 2.3.4 or 2.3.5?
[Galaxy S I9000 General] gfacer:
We'll this thread is about the stock rom so I am sure we have our reasons.
[Galaxy S I9000 General] zorxd:
The Swype keyboard on Bell's releases is the only one to support French Canada (French with a QWERTY keyboard). It can be transferred to other ROMs but some people might not want to do this. And most (all?) custom ROMs in the development section do not include it either.

So it's not only about the modem. And yes, if your phone break you might not want them to see the i9000 boot screen (bell's phones are supposed to show i9000M)

Some people just don't mess with unofficial things anyway and will always wait for the kies update.
[Galaxy S I9000 General] joelhon:
So the steps you took were i assume:

1)flash stock KG3 via kies/odin

2)flash JVR pda via odin

3)flash tornado kernel w/o auto boot checked

4)reboot into recovery and root/setup kernel

5) flash GTO JVR in CWM.

Please confirm or correct this.

Also did you originally use stock JVR or deodexed?
[Galaxy S I9000 General] tkdb:
When I do this...under the messages in Odin, it says failed. Any suggestions???
[Galaxy S I9000 General] tkdb:
I could not get this to work. Under messages it says failed. Suggestions?
[Galaxy S I9000 General] RyYYZ:
Yes, disconnect, put it back in download mode, and try again. The first time I tried flashing the rooted kernel, it also said failed, but a second try worked. Several other people have reported similar behaviour, sometimes requiring multiple (2 or more) attempts to flash the kernel. Don't know why, but they all seem to have gotten it eventually.
[Galaxy S I9000 General] darrenweiner:
I also had to flash the kernel twice. The phone is now rooted perfectly.
[Galaxy S I9000 General] lgsshedden:
stock jvr, do not use deodexed if going Tornado which is an odexed rom: the steps are as you detail yes -- should be problem free.

One proviso: those steps are ok if you are coming from stock and never flashed any custom rom or kernel i.e. you are updating to kg3 on kies then wanting to customize.

If you have done prior flashing, then the clean your phone (see guide) and installing stock jvr with kg3 modem and csc would be a preferable route as the clean phone has proven to be the difference between problem free install and "issues" left from residual and legacy stuff.
[Galaxy S I9000 General] lgsshedden:
the kernel is for people already on gingerbread 2.3.3

should be if you are on kg3 through kies all should be ok but phone by phone sometimes the bootloaders aren 't behaving

quick answer is to try flashing again, always untick autooboot and pull the battery and go into recovery after first flashing the kernel, clear cache, davlik cache and set up the system

if this does not happen for you, flash stock jvr using either the samfirmware or stock ramad versions, with jvr as pda, kg3 as modem and kg3 csc -- you will then load the jvr 2.3.4 stock rom and more importantly the correct bootloaders which are bundled with the rom

then flash the kernel and proceed to set up and install the tornado rom in recovery also

the next version of the kernel will have a built in clean phone function and will circumvent these issues but for now we have to work around these issues manually, but it is easily done

p.s. the phone is very resilient and most anything you can do flashing in odin can be fixed except for flashing bootloaders within odin which is not so simple and is inherently more risky, hence all my comments suggest fixing any issues related to bootloaders by flashing the correct stock rom or at least a functioning stock rom e.g JVR instead of KG3, rather than trying to "fix" the bootloaders within kg3

nothing more disconcerting than flashing and seeing the odin screen go red and "fail" pop up -- check you haven't put something where it shouldn't be, go back into download, start again -- most times its user error and simple to fix.
[Galaxy S I9000 General] Spudsicles:
Battery charging bug...

Anyone else have this where I unlocked the phone, it said it was at 100% charged, and not charging... but my battery app said it was 85%. Then my battery app turned to 100%... so I unplugged it and it went to 85%. GRRR!!!

So this new update tells me that it randomly picks a number between 85% and 100% battery life, and stops charging the phone. Lame!

My two cents, other than that... I like the update to Gingerbread from Froyo.
[Galaxy S I9000 General] DT3CH:
It is indeed about the stock ROM, but people in here also want root, which means they want to change things up, so for those people why would you want to stick with an outdated ROM, especially one that is buggy?

Agreed..... like I said above, my post was more for those that want to change things up
[Galaxy S I9000 General] tkdb:
HELP!

i did have the stock gingerbread 2.3.3 from kies, did everything i was supposed to , and got a big FAIL. now i dont know what happened to my phone, i can get it into download mode, but that's it! the only other response i get from it is a symbol showing to attach it to my computer.

i dont know what to do from here. did i brick it? am i screwed?? :'(
[Galaxy S I9000 General] joelhon:
If you can get it into dl mode then try and re-flash all should be O.K. Make sure that everything is in the right places.
[Galaxy S I9000 General] tkdb:
i did exactly that! all is good, and my phone is rooted. :) Phew....
[Galaxy S I9000 General] omishi:
Hmm i tried to root my phone using the root kernel with odin following the instruction posted a couple pages back. But When i check to see if my phone is rooted it still said no. Even thought odin said i passed and with no fail message. Anyone know what i did wrong? Then i check to see if i can root with superoneclick. However superoneclick said the phone is rooted. I'm lost
[Galaxy S I9000 General] lgsshedden:
Yeah well soc is not the best. Use the kernel from hardcore or damian best options.
[Galaxy S I9000 General] xxbeanxx:
adb shell then ls -l /system/xbin/su

See what that gives you. Paste the output here.
[Galaxy S I9000 General] DeHann:
Download and install Superuser and Busybox from the market and you should be good...
[Galaxy S I9000 General] omishi:
ahh cool thanks. Superuser fixed that for me. Weird that it didn't detect root in the first place. So i had to uninstall and reinstall superuser.
[Galaxy S I9000 General] DeHann:
I am no expert but I think it is because the file is a zimage and not a kernel; although, someone else may be able to clarify. Either way, all's well that ends well.
[Galaxy S I9000 General] DeHann:
I have since flashed JVR with TW Launcher 4.5 from Fr4gg0r, a battery/CRT/extended power menu mod from Sphinx02, and CF-Root. Not to mention the KG3 modem. Quite happy with this setup now. The touchwiz mod from SGS2 makes everything so much better... :)
[Galaxy S I9000 General] mackendw:
Hi:

I'm trying to get the Google Talk app to work on my Samsung Galaxy S I9000. Just upgraded to 2.3.3 using Kies. Went well.

Just finished installing the rooted kernel from haloimage. Installed superuser and busybox following this.

I have the GTalk-......zip image on the phone in the root directory and can see it no problemo. When I boot up the phone in recovery mode and attempt to install the GTalk app, it says the file has incorrect checksum or some such mismatch. Used bluetooth to xfer it from my mac to the phone. md5 sum is good on phone vs what the mac reports.

Is there something I'm missing here as to how the root kit is supposed to work? ie: how is the root authority passed into the recovery sequence for the user doing the install of the GTalk app?

Experts feel free to chime in here :)

thx.

mackendw.
[Galaxy S I9000 General] joelhon:
I'm confused :s does google talk not come pre-installed on the phone?

Swyped from a galaxy far far away.
[Galaxy S I9000 General] xxbeanxx:
zImage is a kernel. (THE kernel actually)
[Galaxy S I9000 General] srkoza:
Lol im using miui based on 2.3.5 gb dont waste your time people root ur phone and flash miui way better rom
[Galaxy S I9000 General] mackendw:
Right, the voice version does. But I believe the newer version that supports 2 way voice/video is only usable on 2.3.3+ with the latest GTalk app. Hence the need to upgrade it and the root schmozzle.

Maybe I'm wrong...
[Galaxy S I9000 General] masterslacker:
I have flashed the ROM from here, as well as the rooted kernel. The kernel works, and has rooted, after installing superuser and busybox.

Now, I'm trying to install a ClockworkMod Recovery, but it doesn't work from RomManager. Has anyone been able to flash either a custom kernel that has this built in, or has gotten Rom Manager to work for flashing CWM?
[Galaxy S I9000 General] xxbeanxx:
CWM won't work from rom manager if you have recovery 3e.
[Galaxy S I9000 General] masterslacker:
Any ideas how I can change that?
[Galaxy S I9000 General] mackendw:
So, question here becomes, when you have "rooted" your phone, is doing this just exposing a root level user access to run commands and manipulate files/directories on the phone with no restrictions?

and, by part 2 of the same question, if you have a tarball, zip, etc. and run adb shell, does that also imply that you can just explode the tar ball / zip file to install apps using the root user access privileges? or is there some other special things that you have to do?
[Galaxy S I9000 General] DeHann:
Heya! Thanks for the clarification.

So, do custom kernels with extras (CWM, Voodoo Sound, BLN, etc.) just contain code since the zImage is only one file?

Sorry, I am more Windows-based and not much into programming.
[Galaxy S I9000 General] DeHann:
You could ask a developer to create a custom kernel based on the I9000UGKG3 firmware; or, create your own even...lol

I have sent a PM to Chainfire requesting a custom CF-Root for KG3 and am waiting his reply (I think he is still on vacation though) as I personally would just rather use the stock firmware.

I have also heard that the Tornado kernel is working on KG3 too. Just search this thread for more information.

Finally, you could always flash JVR and use the KG3 modem. JVR is version 2.3.4 and KG3 is only 2.3.3; so, this is really the recommended option. Especially since there are many custom kernels/roms/mods/etc. which are based on JVR.
[Galaxy S I9000 General] xxbeanxx:
Yes rooting your phone installs a setuid/gid command that allows you to gain superuser privileges.

Not quite sure what you're asking here but... You don't need root access to untar or unzip archives on your phone. As long as the command is available and you can read the archive and write to the destination you can do it.
[Galaxy S I9000 General] xxbeanxx:
The zImage file is just an executable that gets ran by the bootloader. It's generally a standard elf binary and contains everything needed to bootstrap the OS. Generally it contains the initrd, which is a filesystem that gets loaded into a ramdisk and that contains various things like commands to mount partitions or whatever else may be needed.

You can tear apart a kernel, isolating the initrd, which can then be unpacked, edited, repacked, and re-embedded into a new zImage.

Custom kernels generally add things to the initrd and then modify the init.rc script inside to make it do new things. So in the case of rooting, you would add a su command to the initrd, then modify the init.rc to copy this command somewhere and setuid it. You can also add different recovery images or kernel drivers.

Not sure if this makes sense, I don't have time to reread it..
[Galaxy S I9000 General] xxbeanxx:
Or use CM7...it's 2.3.5.

Sorry a little off topic. :)
[Galaxy S I9000 General] DeHann:
Thanks for the explanation. It is excellent information. I had to read it slowly to understand it though. Lol.

Did you have to sign up with the Cyanogen Mod forums to download it?
[Galaxy S I9000 General] joelhon:
I used it before when I was on 2.3.3 and could use video chat, so the capability is already there it just needs the proper firmware.

Swyped from a galaxy far far away.
[Galaxy S I9000 General] gfacer:
Zimage is the kernel. Not sure why its named that though...
[Galaxy S I9000 General] xxbeanxx:
http://en.wikipedia.org/wiki/Vmlinux:
[Galaxy S I9000 General] jpaik:
I have tried to update the firmware on my Galaxy S, without success. I have tried it using 3 different PCs (each running WIN XP).

The entire process proceeds and ends the same way, regardless of the PC. I launch Kies - - the latest version - -, I connect the device, the device is discovered and connected. After a period when nothing seems to be happening, I then get the usual messages: continue, or back up + continue; don't disconnect the cable, etc. etc.

(In one of my first tries, I backed up the appropriate files through Kies without doing the firmware update.)

The firmware files are downloaded. But at this point I notice that the upper-left portion of the screen shows the device is now disconnected. Kies eventually reports that the device is disconnected and I need to reboot it.

I have gone through this frustrating procedure countless times. Re-booted the Galaxy S; shut down the Galaxy S + remove battery + SIM then add back the battery + SIM and start up. Nothing seems to work. The update fails.

I have stock everything on this device. I have disabled any constantly running software like Juice Defender and Lookout.

Has anyone else seen this? Is the latest version of Kies the problem?

I am grateful for any ideas! Thanks.
[Galaxy S I9000 General] xxbeanxx:
This happened to me; it was a driver issue. I installed the drivers that came with superoneclick to fix it, but you will have to force them over your current ones or else it will say that there are no newer drivers.

I'm not sure what drivers are bundled with superoneclick, maybe the sdk drivers?
[Galaxy S I9000 General] lgsshedden:
you have now discovered why so many give up on kies and speak disparagingly about it -- odin allows much more user control plus you can customize the firmware, stock or modded. Options.
[Galaxy S I9000 General] mk_ln:
I've noticed that I've had a few dropped calls recently; I'm going back to KC1 modem
[Galaxy S I9000 General] jpaik:
I finally got the upgrade. I wish I had documented this as I went along, as I'm not 100% sure why it worked!

I uninstalled the Samsung drivers on the PC, and did a registry cleanup. Rebooted the PC. Through Kies I re-installed the drivers. I also shut down and restarted the Galaxy S while cabled into the PC.

What a painful process. Kies is a disgrace.
[Galaxy S I9000 General] pure_energy1:
Root did not work for me. I get a FC when I try to load Superuser.
[Galaxy S I9000 General] haloimplant:
Try it again. Same thing happened to me but it worked the 2nd time.
[Galaxy S I9000 General] urself25:
It happened to me too. I uninstalled SuperUser and reinstalled it from the Market and everything went fine after that.
[Galaxy S I9000 General] pure_energy1:
It worked after I un/re-installed Superuser from the market as stated above.

Thanks...

Speaking of the market... I hate the new market.
[Galaxy S I9000 General] quadracer111:
Now running official gingerbread thanks to this thread.

Any custom rom suggestions?
[Galaxy S I9000 General] xxbeanxx:
CM7

10chars
[Galaxy S I9000 General] I9000m:
How do i install this to my phone using ODIN?????
[Galaxy S I9000 General] xxbeanxx:
¿

10charrrr
[Galaxy S I9000 General] urself25:
Look for the thread "how to install cyanogenmod and live through it"
[Galaxy S I9000 General] midirt:
Has anybody flashed just the KG3 modem on DarkyRom 10.2 through its "zip from sdcard" option? What file do I use for the zip? Does it work?

Unmodified DarkyROM works in the city, but outside of GTA I get "emergency calls only" while my wife's SGS with factory rom is fine. I guess I need KG3 modem? Please help with instructions on how to do it. Thanks.
[Galaxy S I9000 General] grokon:
Yes you can use KG3 modem with Darky... I've done it

For instruction, use the search fonction..

For the signal outside GTA, it's a matter of 850 band... you may flash KG3 modem or enable the 850 band using that procédure

Good luck!
[Galaxy S I9000 General] romandesign:
I've done the service mode sequence but it didn't help for some reason.I've searched this forum for hours but could not find a link or instructions for KG3 modem file on darkyrom. Please help and point me to the link! Thanks.
[Galaxy S I9000 General] upichie:
You don't need a KG3 modem specific to Darky's ROM, I don't believe, so just search for a KG3 modem. I'd offer a link, but I use CM7, which doesn't use rom-specific modems.
[Galaxy S I9000 General] grokon:
yep, you just need a CWM flashable modem to do it via "install zip from sdcard"

If i remember, i got that kg3 modem file from this thread. anyway here is it again and thanks to the original uploader...

(but not sure anymore if i flashed from CWM or Odin...)
[Galaxy S I9000 General] midirt:
Thanks a lot!
[Galaxy S I9000 General] jeff260z:
I finally figured out what was causing my upgrade issues.

I was continually getting the "this device's version cannot be updated" no matter what I did. I finally read about the devices product code causing issues so I checked my product code and it was GT-I9000HKAXEE Sweden. Being from Canada I thought this could be a problem. :)

I searched for how to change the product code back to GT-I9000HKABMC I9000M	Canada Bell.

I found the answer on another site here.

Once I changed my product code to BMC I connected to Kies and it said Update available!

I started the update and after a bit I noticed that Kies was showing no device connected but I left it for a few minutes and it turns out it was still working. It continued still showing no device connected for the remainder of the update.

I am now at 2.3.3. :)
[Galaxy S I9000 General] Beulvar:
anyone else getting an issue where Kies wants the device rebooted constantly but will never actually do the firmware update? I have rebooted the phone and my pc multiple times, as well i have removed Kies a few times too.

Edit..got it to work finally, had to boot to recovery on it and do a factory default first.
[Galaxy S I9000 General] strikerx120:
can someone help me idid this and the root failed and now my phones bricked....i mangaed t o get my p[hone into download mode but yeah

<ID:0/004> Added!!

<ID:0/004> Removed!!

<ID:0/004> Added!!

<ID:0/004> Odin v.3 engine (ID:4)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Get PIT for mapping..

<ID:0/004> Firmware update start..

<ID:0/004> zImage

<ID:0/004> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

<ID:0/004> Removed!!

i did exactly as u said and i had 2.3.3 running on my vibrant from bell

can someone give me exact step by step deatails on how ot recover my phopne or get to a fresh install of android because i f'ed up
[Galaxy S I9000 General] ysr84:
Thanks man worked for me....
[Galaxy S I9000 General] JJNutty:
You should probably go here now and scroll down until the section "North America (I9000M)" - http://xdaforums.com/showthread.php?t=1102881

The instructions for flashing the files are also found above the download links.

Hope this helps + good luck!
[Galaxy S I9000 General] steve5190:
I'm trying to update my stock Bell Vibrant SGS to KG3 from JH2 (Eclair), but all Kies is offering me is KC1 (Froyo). Do I have to update incrementally or has KG3 been removed?

Also, would updating the firmware re-enable the SIM lock? I'm on Fido.

Thanks
[Galaxy S I9000 General] greeced:
You have to update to kc1 first, then it will update to kg3

And it will remain unlocked if it was unlocked already
[Galaxy S I9000 General] kpucci:
are you able to re-root on 2.3.3 yet? I have the same setup as you do.
[Galaxy S I9000 General] are609:
http://beta.swype.com/
[Galaxy S I9000 General] lgsshedden:
root is not a problem: after the install of KG3 just flash any of the kernels with root such as ChainFire, Hardcore or Tornado. Chainfire's kernel is closest to stock but adds root, Hardcore's more customized and with added features, and the Tornado kernel is fully customized. You can add a custom rom or stay with stock, use the KG3 modem and CSC and move up to 2.3.4 and by next week the latest 2.3.5, both of which over improved functionality over 2.3.3.

I understand that people sometimes want to stay on stock for fear of violating warranty. I think it is a false concern: the only time my own phone was bricked was using Kies and Bell's faulty firmware release -- we all know how well Bell did and did not react to that fiasco. Any custom flashing is always recoverable by using odin and re-installing stock. Lastly, if you do damage the phone, presently neither Samsung nor Bell have any real interest in repairing it as they both want to sell you a new Galaxy S2 and your warranty is not near as inclusive as the sales person implied (my daughter recently dropped her phone -- there are people who repair them privately for about 40% of what Bell wanted to charge, a sum suspiciously close to a new phone cost, while Samsung refused to take the phone for repair referring us to Bell).

So, if you want to try KG3, you may wish to follow any of the excellent guides available, and try a custom kernel for root and a JVR rom.
[Galaxy S I9000 General] biscuit26:
is there any way to unlock the phone with this firmware ?? none of the unlocking apps are working and i still can't manage to get my phone rooted

thanks
[Galaxy S I9000 General] lgsshedden:
have you tried this thread?: http://xdaforums.com/showthread.php?t=761045
[Galaxy S I9000 General] rocked_out:
I had stock UGKG3 on my never rooted i9000m. It was the best experience for me, lagging and FC wise.

Then i wanted the percentage display of my battery on my status bar and somehow rooted my phone by flashing using odin with i think it was CF-somthing(still have the file somewhere) then downloaded an app called "battery icon mod" (which later i found out it's not for i9000m) and stuck on boot loop.

Then i been looking around the internet and tried a few roms without much knowledge. Failed many times. Pissed off and didn't have my phone for a whole day.

Finally found a stock froyo rom with bootloader. Finally able to get into android. Then applied Darky rom 10.2. I did like the appearance and the touchwiz launcher 4.5 (later found out twlauncher was the main cause of the freeze issues) and GPS was dead on for me, never been more accurate. Started having freeze issue. Applied froyo rom that i found, applied it then applied stock UGKG3 with Sbl thru odin then applied rooted stock UGKG3.

And now i was wondering if i could go back to stock froyo and then update UGKG3 thru kies?

(i've never been happier with UGKG3. For me, froyo was the most frustrating state, had firmware issue. Bought it second hand and using it with rogers. Luckily my gf has exact same model as mine with bell. She took it in as hers and they fixed it for free. Even after that so much lag and many FCs. Also i smashed my screen at that state)

and now i think i understand what kernel is. If I'm able to root it after UGKG3 with kies, then i could just find a rom that only contains kernel with battery mod?

Or any other suggestions?

Oh and i need to have allshare. Darky rom didnt have that.

I know 3 things.

1. As long as i could go into 3 button download mode, i could revive my phone by flashing thru odin.

2. most likely that only way i could not get into download mode and completely brick is to inturupt the flashing process.

3. each version of android (ie. 2.1, 2.2, 2.3) has different bootloader