Related
Hey all you fellow sad bunch of Bell Galaxy owners,
I did the bell upgrade via kies, did factory reset, cache wipe, format sd card and so far my phone is running just dandy on the new froyo.
I did it because it was all official and now I see that they pulled the update! And looking at all these threads it looks like this will brick my phone in a matter of days simply because of bad software, not hardware.
Should I try to downgrade before I'm doomed? And where do I find the old bell files to do this odin thing?
Any advice/curious musings would be greatly appreciated.
Yes.
I had mine on jk4 for a day and then changed firmwares. No issues so far.
I'm running jpu now.
Thanks! Hey it's not clear to me as to what is the best route to do the downgrade for the i9000m, and which roms are compatible with this bell version, can I install any rom and be fine?
I have the idea that the i9000m is quite different from the other galaxy s variants.
Rom manager doesn't work on this phone so I guess my only option is odin?
From what I understand, failure is mainly caused by a data corruption on the SDCard when changing firmware. So I'd stay away from frecquent firmware change for now...the more you do it, the higher the risk is.
JK4 is still official, so if you get issue with it, you're pretty much covered by the waranty.
I did mine and its been fine no problems
Sent from my GT-I9000M using XDA App
Dusante said:
Thanks! Hey it's not clear to me as to what is the best route to do the downgrade for the i9000m, and which roms are compatible with this bell version, can I install any rom and be fine?
I have the idea that the i9000m is quite different from the other galaxy s variants.
Rom manager doesn't work on this phone so I guess my only option is odin?
Click to expand...
Click to collapse
Rom Manager won't work on JK4 stock because it installed 3e recovery which checks that update.zip files are signed before running them. If you choose to stick with JK4 and want to pursue Rom Manager, your best bet is probably using a kernel which has Rom Manager built in. For example, I flashed SpeedMod Kernel k10j on one of my phones (check the i9000 dev forums).
If you choose to "downgrade", use Odin. JK3 (2.2) and JH2 (2.1) are Bell specific firmwares. Alternatively, using the reg hack solution might work (I've never used it myself so can't offer help). Let us know if you need help with Odin or flashing an earlier firmware.
How do I downgrade my Bell Vibrant? I have 2 Bell Vibrants.. 1 already got the SDcard error 3 days after updating to 2.2.. My second one is still working (2.2) and I want to save it! Please show me how to safely downgrade back to 2.1
Bricks were happening before Froyo 2.2 (JK4) came out of the official channel (Kies).
Nobody can say for certain that it has something to do with JK4 or with an internal hardware issue that is a ticking time bomb. If your phone is working fine on 2.2 (like mine), enjoy it, otherwise send it back to Bell for repair when it dies.
bimmerboii said:
How do I downgrade my Bell Vibrant? I have 2 Bell Vibrants.. 1 already got the SDcard error 3 days after updating to 2.2.. My second one is still working (2.2) and I want to save it! Please show me how to safely downgrade back to 2.1
Click to expand...
Click to collapse
1) Verify you have Recovery and Download mode still working (3 button combo).
2) Remove any lag fixes if you have applied them and download the UGJH2 PDA from Samsung firmware website.
3) Start Odin and put the JH2 firmware (tar file) in the PDA section.
4) Put the 512 pit file that came with Odin install in the PIT section.
5) Click Re-partition.
6) Stop Kies if running and connect phone to USB cable.
7) Ensure that Odin recognizes the phone in the ID:COM section.
8) Click Re-Partition and hit Start.
9) Pray that it works, wait for it to reboot and wait for it to startup, it may take longer than normal for the first boot.
I'm not responsible if it does not work out for you.... Personally, if you have it working on JK4, I would leave it well enough alone.
Thanks for giving the step by step guide.. I am experiencing some FC's on JK4.. I think it's on it's way to getting bricked.. I wana put back JH2 as soon as possible
I went back to JK3 as I've had no problems with it and it's given me the best battery life. Its currently sitting at 84% remaining battery after 12 hours use.
xedd said:
1) Verify you have Recovery and Download mode still working (3 button combo).
2) Remove any lag fixes if you have applied them and download the UGJH2 PDA from Samsung firmware website.
3) Start Odin and put the JH2 firmware (tar file) in the PDA section.
4) Put the 512 pit file that came with Odin install in the PIT section.
5) Click Re-partition.
6) Stop Kies if running and connect phone to USB cable.
7) Ensure that Odin recognizes the phone in the ID:COM section.
8) Click Re-Partition and hit Start.
9) Pray that it works, wait for it to reboot and wait for it to startup, it may take longer than normal for the first boot.
I'm not responsible if it does not work out for you.... Personally, if you have it working on JK4, I would leave it well enough alone.
Click to expand...
Click to collapse
is this likely the best way to get an i9000m that has been upgraded to 2.2 to have e2 recovery? Also where would i download the JH2 rom file?
AdamArchibald said:
is this likely the best way to get an i9000m that has been upgraded to 2.2 to have e2 recovery? Also where would i download the JH2 rom file?
Click to expand...
Click to collapse
its all here http://forum.xda-developers.com/showpost.php?p=9776920&postcount=26
successfully downgraded to 2.1 will now upgrade to 2.2 JL2
I've been running JK4 since it got realeased and so far so good. Never had any probleme related to firmware. My phose is a new one got after my first one died using JPC so I don't think it's related to firmware but realy hardware.
Sent from my GT-I9000M using XDA App
Hello,
I've a Galaxy-S (was from T-Mobile Uk, but I unlocked it, debranded it and so on), it used to be 2.1, so back in november I updated to 2.2 using the Kies trick (changing the area code and so on). Now I'm finding myself *not-so-happy* about many bugs that are around (sometimes apps just crash... etc..). I'd like to go to 2.2.1 if this would help. But Kies doesn't even show an available update, so I was thinking of flashing one with Odin. Which one do you recommend?
My firmware is XXJPP. I don't remeber how to get other info/codes, so tell me how if you need them.
Also, I'm ready to wipe everything, but I'd avoid it. So tell me how.
Thanks.
JPY or WJS8 in UK with CPW csc .
Build your own in the rom kitchen .
http://romkitchen.org/sgs/?s=home
http://forum.xda-developers.com/showthread.php?t=817703
jje
dariodariodario said:
Hello,
I've a Galaxy-S (was from T-Mobile Uk, but I unlocked it, debranded it and so on), it used to be 2.1, so back in november I updated to 2.2 using the Kies trick (changing the area code and so on). Now I'm finding myself *not-so-happy* about many bugs that are around (sometimes apps just crash... etc..). I'd like to go to 2.2.1 if this would help. But Kies doesn't even show an available update, so I was thinking of flashing one with Odin. Which one do you recommend?
My firmware is XXJPP. I don't remeber how to get other info/codes, so tell me how if you need them.
Also, I'm ready to wipe everything, but I'd avoid it. So tell me how.
Thanks.
Click to expand...
Click to collapse
I suggest you the JS8 ROM. Is the last froyo 2.2.1 european firmware. You can use the JS8 rome in the romkitchen to customize your fw as you want
Odin for flashing Kies for orugnal upgrade
Is JS8 an official upgrade from JPY(2.2.1)? For the UK aswell????
Or is it just a general European(including UK) update?
I'm on JPY right now. Upgraded officially from JPO(2.2) in the UK.
Do you think it is better to flash JS8 firmware?
(I have tried 2.3.3 JVK but I would rather wait for the official gingerbread update)
JPY is still the most current firmware for UK. I'm in Australia and have been using it since release. Docs version of course.
JS8 is Nordic I think.
Sent from my GT-I9000 using XDA App
dariodariodario said:
Hello,
I've a Galaxy-S (was from T-Mobile Uk, but I unlocked it, debranded it and so on), it used to be 2.1, so back in november I updated to 2.2 using the Kies trick (changing the area code and so on). Now I'm finding myself *not-so-happy* about many bugs that are around (sometimes apps just crash... etc..). I'd like to go to 2.2.1 if this would help. But Kies doesn't even show an available update, so I was thinking of flashing one with Odin. Which one do you recommend?
My firmware is XXJPP. I don't remeber how to get other info/codes, so tell me how if you need them.
Also, I'm ready to wipe everything, but I'd avoid it. So tell me how.
Thanks.
Click to expand...
Click to collapse
For stock go to samfirware.com, sign up, download Odin and jpy 2.2.1 (for UK). Install with Odin without repartition ticked and you should still have your apps/data.
Site has all the files and instructions you need. Just make sure you have download mode.
2.2.1 is miles better than 2.2. You'll wonder why you waited so long.
Sent from my GT-I9000 using XDA App
The networks do not upgrade all the incremental updates JPY last one in general use and none have bothered to push out the later upgrades preferring to wait for the official release of 2.3 .
Either JPY or WJS8 will work well on UK phones .
jje
I tried both the kitchen and the: stock Rome. Even if the kitchen seems so clever and you don't need Odin in order to upgrade, I ended up with a 2.2.1 Tom that didn't have the market app, and other basic ones. Plus the media scanner was crashing every 10 seconds. Another one started up in Chinese and kept crashing various system apps. That's to say that it is not the best choice for stability. Instead I went to samfirmware got 2.3.2 and it is stable, clean and fast. Using Odin is easy in the end so I recommend this if you want a fully functional phone. And gingerbread is so faaaast
That's to say that it is not the best choice for stability.
You are doing something wrong then as its the safest and most problem free method .
jje
I have 3uk sgs and immediately went for odin for all my flash updates.
First thing is to check u have three button combo working. Just pull the battery to get out of that mode.
I'd go straight to gingerbread JPK. And with the few, clockworkmod zips you can add battery percentage and a few other nice things that aren't included.
I haven't looked back as jpk is such a great rom - memory management is sorted so no need for autokillet or taskmanagers.
Sent from my GT-I9000 using XDA App
OK, so I've been reading guides, FAQs, how-tos, and various forum posts, and thought I had a pretty good handle on how to flash FW to this machine. So, last night I backed up everything important, and downloaded from here ( http://forum.xda-developers.com/showthread.php?t=1102881 ) the following:
2.2 UGKC1/UGKC1/BMCKC1/Sbl. This is the stock FW as currently installed on my I9000M from upgrading through Kies.
2.2.1 XWJS8/XXJPY/OXXJS5 (MultiCSC) (no sbl)
So just as a sanity test I first tried flashing the UGKC1 PDA file over to my I9000M using Odin. This worked as expected, since it's the same kernel.
Next, I tried to flash over just the XXJPY PDA file over to my I9000, using Odin. No re-partition, no PIT, no modem or CSC. No go - it just repeatedly displays the GT-I9000M screen and never boots the kernel. Couldn't get into recovery mode from this state, but was able to access 3-button download mode.
So, tried flashing over the 2.2.1 XXJPY PDA, Phone and CSC files. Same as before - no actual boot.
I flashed it back to the 2.2 UGKC1 PDA, phone and CSC files, and did a factory data reset and cache clear, and everything was fine running 2.2 again.
From reading here it appears that others have successfully installed 2.2.1 or even 2.3.x kernels on Bell Canada GT-I9000M phones. So, what important step did I miss?
Do I need to re-partitiion? Do I need to use a 2.2.1 FW that includes the boot loader?
For now I'm OK running 2.2, but would eventually really like to be on 2.3.x and don't want to wait for Samsung to make 2.3.x (what happened to 2.2.1) available to GT-I9000M phones. I'll leave it alone for now as I'm going on vacation in a couple of weeks and don't want a hosed phone.
What happens if you flash just a kernel like CF root or speedmod? My only other thought is to redownload jpy and try again as maybe the download was corrupted.
Also with another kernel like speedmod you could download and install a custom rom on cwm (clockwork mod) via recovery that is 2.2.1
I've had some problems with 2.3.4 (never tried 2.3.3) so I am back on Froyo for a bit until things get sorted out a bit more.
G
I don't know if there is a suitable version of CF Root for the UGKC1 firmware - they mostly seem to be oriented to the more international versions. As usual, in Canada we get something a little weird. Don't know about speedmod.
I don't think there should have been any problem with the downloads, as the files themselves are in md5 format, which means they are getting verified by Odin 1.8 when it goes to use them, as I understand it. If they were corrupted Odin should complain about it.
With the announcement ( http://forum.xda-developers.com/showthread.php?t=1158492 ) that Gingerbread is supposed to get an official release to Bell phones soon (which mine originally was), I might just let this lie, for now.
There is a gentleman on youtube by the name of AndroidGalaxyS (original, I know) that has some excellent and detailed walkthroughs and reviews of various ROMs for the I9000M.
youtube.com/user/AndroidGalaxyS
Specifically in your case, you'll want to watch this one that shows how to install 2.3.4 JVP:
youtube.com/watch?v=cLXQn0gOBuA&feature=feedu
Good luck.
I agree that the source maybe lacking. I just found out that the JL2 firmware from samfirmware.com is missing db_data file so I would always get an error after flashing that. KC1 would also not always boot for me so it might be missing something too.
That said what are you trying to accomplish? If you are just trying to go to another stock rom I'd just leave it and put a custom kernel on to give you root and CWM recovery.
Most any other Froyo rom is flashable from CWM in recovery and you do not need to worry about odin except to recover from bad things and it looks like you can do that. Gingerbread is different because they changed the bootloaders and that means Odin.
Of course its getting harder to dig back and find those Froyo roms since the rest of the i9000 world has been on GB for a while.
G
Thanks for the replies, so far. Mostly I was just experimenting, and trying out XXJPY was just a first step in my experimentation before moving on to GB. Part of the reason for this is that it seems like a lot of the modified kernels and so on are meant to be flashed over certain versions of the firmware, and those versions don't include the Bell/Virgin-specific ones. Or maybe I've misunderstood how this stuff works.
Yes, while my attempts to install XXJPY have been a complete failure, even when re-partitioning with a PIT file, when I re-flashed back to the stock UGKC1 FW everything was fine.
At this point I'm just trying to get a better understanding of where this went wrong. I've never specifically updated the SBL - the JPY package I installed didn't include it, and I didn't check off the "Update boot loader" box when re-installing KC1.
I've seen a number of posts here from people who updated I9000Ms to other FW, but unfortunately they don't seem to have detailed exactly where they started from, or exactly what they installed, or how.
Hey everybody,
Im kinda new to droid development, and have played around with it a little (flashing roms, kernels, rooting etc) however, im curious why there are roms based on pretty much every other firmware other than GKG3. I might sound like a n00b for asking about this but its mainly for my knowledge. I figured KG3 would be fairly common as it is one of the North American firmwares, but I must be incorrect? Anyways any insight on this would be great. Also a quick question, seeing as I am a Bell I9000m SGS owner does it matter if I put firmware from say Europe on my phone? I have noticed that my signal decreases when I put a rom on that is JVR based? Curious if this causes my phone, seeing as the modem is being changed to JVR, to think that I am out of country and will inflict long distance charges. This probably sounds like a dumb question, and I dont really believe LD charges will apply, but some confirmation would be nice as google didnt really help me out on this one.
Thanks!
KG3 is 2.3.3 and although it was just issued to Bell and other N.American customers, the rest of the Anfroid world has been using 2.3.4 for 6 months and some have moved to 2.3.5. The roms you see here are cutting edge and most use the latest firmware. The last official and stable release was JVR a 2.3.4 firmware and there are many good roms for JVR. It is easy to keep your KG3 modem in place and the KG3 CSC file and just upgrade your system to a custom JVR kernel and JVR rom.
I tried flashing galaxian's jvr kernel and it just bootlooped so maybe I'm doing this wrong? I kept my stock modem and CSC, flashed kernel using oden, factory reset was done as well as a cache clear prior to the flash and all I'm getting is a bootloop so I'm not entirely sure what I'm doing wrong any advice would be appreciated! And again thanx for the info in the previous post!
Sent from my GT-I9000M using XDA App
yes you flashed just the kernel, you must first flash the stock rom and then any custom kernel for the same firmware -- you need the stock rom to install the correct bootloaders prior to flashing the custom kernel
so in odin, flash JVR stock in pda, KG3 in phone and CSC
tick auto re-boot
then flash the custom kernel of choice in odin under pda
Awesome thanks for the tips! Will give this a try
Hi guys - you guys might be able to help with a wee problem.
upgraded FW today via kies to 2.3.3 KG3 from froyo 2.2 with speedmod kernel.
in the process though i lost root but worse is i now don't have 3BR, when i used to. I still have 3 button download mode though.
I want to root again and flash a different kernel (for root but also for performance/tweaks) but worried to without 3BR ie. how will I access tweaks/enable root etc without it!?
Any ideas/advice please? Thanks
first flash a complete 2.3. firmware, either 2.3.4 JVR or 2.3.5 JVT. This should re-install basic 3BR functionality. I think you have not got the necessary bootloaders in the jump from froyo to GB and a complete stock install should correct this. Do tick re-partition and use 512 pit, do check auto-boot: let the phone boot and right itself. Check for 3BR and do a system reset.
Then flash KG3 modem and CSC. Your phone should then be functional.
Then flash a kernel with root inbuilt to it.
If you use the GTO Tornado kernel you can also clean your system completely as this stage instread. If you use another kernel, do the factory reset, davlik cache clean etc. prior to flashing the kernel as suggested above.
Do the clean prior to re-installing your apps.
lgsshedden said:
first flash a complete 2.3. firmware, either 2.3.4 JVR or 2.3.5 JVT.
Click to expand...
Click to collapse
Thanks! will give this a go but have only ever really flashed a kernel before with odin so want to be doubly sure about these steps if that's ok? apologies for my noobish ignorance
- only found a 2.3.4 JVR at samfirmware - getting this and the 512pit file. This should be fine?
- then flash a KG3 modem and CSC - any idea where I get those files from? - the ones i've got now i only got through kies (and when i do get em, when i do this in odin do i only use the phone/csc boxes and leave pit empty/uncheck re-partition?
thanks again mate.
Edit: forgot to say my reason for questioning the JVR is because the one i have is listed as European...where as I have a bell mobility but in australia - does this matter? latest FW for aus/america is JVN 2.3.3
no problem: always better to ask for help first then assitance fixing a problem when it all goes pear shaped.
There is a thread on the KG3 firmware with lots of these questions answered: http://forum.xda-developers.com/showthread.php?t=1211939 and also the basic resource for firmware posted by Ramad here: http://forum.xda-developers.com/showthread.php?t=1102881 -- scroll down and you will find KG3 under N.American, he also has a nice set of illustrations for using odin.
You can also source a cwm zip for the KG3 modem from perka's stash here and on the market (free app) -- useful to havce the modem in cwm zip form as then you can just install a new stock firmawre such as JVR or JVT and add the modem in recovery.
lgsshedden said:
no problem: always better to ask for help first then assitance fixing a problem when it all goes pear shaped.
Click to expand...
Click to collapse
Thanks so much again - that looks like a hefty bit of reading to be done there via your links so before I do that, just one more Q please - and apologies if the answer for this is somewhere in the links you've provided.
i was just trying to read up about why the samfirm file extracts only to a single .tar file called JVR_JVR_JVR and how to use that in Odin and came across this thread:http://forum.xda-developers.com/showthread.php?t=1075278
my Q is - in this thread he makes a strong point of stating not to tick repartition and not to put the .pit file...but you say to do so.
am i missing something obvious?
well different people different perspectives on re-partition and pit.
Tick re-partition and flash the pit file. Leave it un-ticked and do not flash pit file. That's the only key: do one or the other.
As I understand it, the reason to re-partition is that it re-sets the base file system upon which you are now flashing the stock firmware -- seems a basic step whenever you move firmware versions e.g. 2.2 to 2.3, 2.3.3 to 2.3.4 to 2.3.5 -- not so much if you are installing a rom or kernel within that family of firmware.
Since I always then convert the file system to ext2 to speed up the system and I use damain's kernel to clean the system, I do use the pit file whenever I flash a new stock firmware to clear the basic file system and further aid removal of legacy files that could complicate the install.
---------- Post added at 09:28 PM ---------- Previous post was at 09:24 PM ----------
BTW the samfirmware files do extract using 7zip into the component parts for use in odin: pda (rom) phone (modem) and CSC. You then flash a custom kernel in the pda section if you use one for performance and root.
thanks lgssheddon, for the info here and in the PM.
Will crack on now with reading all the links you provided.
I just have to say a big fat D'oh! - why oh why could I not find the answer to what was bothering me most ie. apparent loss of recovery mode. The very first post in the first thread you linked gave me the answer - that it is now a 2BR (and tried it on my phone et voila, by magic I can get into recovery again!). Don't know how I could not find this thread even when I searched "KG3"!!
Thanks again for your help. i'l llet you know how i get on once i digest all this info
doktorV said:
Hi guys - you guys might be able to help with a wee problem.
upgraded FW today via kies to 2.3.3 KG3 from froyo 2.2 with speedmod kernel.
in the process though i lost root but worse is i now don't have 3BR, when i used to. I still have 3 button download mode though.
I want to root again and flash a different kernel (for root but also for performance/tweaks) but worried to without 3BR ie. how will I access tweaks/enable root etc without it!?
Any ideas/advice please? Thanks
Click to expand...
Click to collapse
The 3 button recovery has changed for KG3. I believe it used to be upvol home and power. I do believe now it is volup, voldown, and power. This should work for you to get you into recovery to flash whatever you like. Also the samfirmware for JVR is branded with Swisscom and doesnt work very well for using it with a KG3 modem and CSC, with my experience anyway. I would recommend to go to a JVQ PDA and use KG3 for your Phone and CSC. Also after you have installed this make sure to check what your country code is and install it. Hope this helped
lgsshedden said:
[/COLOR]BTW the samfirmware files do extract using 7zip into the component parts for use in odin: pda (rom) phone (modem) and CSC. You then flash a custom kernel in the pda section if you use one for performance and root.
Click to expand...
Click to collapse
The firmware that he is referring to doesn't. It is only one file meant for the PDA section of ODIN. Not entirely sure why they did this but i was running into problems with it as well. If you know how to play around with the core files you could in theory extract it to its root and put multiple files into .tar files (ex. select factoryfs.rfs, param.lfs etc. and place it under one .tar) but thats a lot of playing around and potentially dangerous if not done correctly.
not sure which download you are referring to but there was a branded version of JVR and a generic one on samfirmware: I have the one that does not have the swisscom logo and it certainly was extracted by 7zip into its component files (pda/phone/CSC) as they are still on my pc in that format.
You can also source stock firmware from Ramad's thread.
And I stand by my comment that for anyone using KG3 as a modem, JVR is the most stable official release available, much better than JVQ. JVT has a lot of promise and will be a better firmware than JVR but it is not yet had all the bugs sorted and while there are Gold Rom version for JVR any JVT rom is still at a beta stage and should not be used yet by someone just starting to flash custom firmware (IMO).
Hi again,
Q for lgssshedden really but if anyone can help i'd appreciate it!
have had 2 crashes now with Tornado Aureus RC1 - few little bugs/glitches eg with ringtone changing etc then on a reboot it won't go past the Tornado start screen with the big flame.
First time I just reflashed stock KG3 then reflashed the Tornado kernel, no problem. This time when I try to flash the Tornado kernel (either Aureus RC1 or Gold) it just bootloops at startup even though the flashing seems to go ok.
So now i'm back to (yawn) stock KG3 2.3.3. Really just want to root it again but with Tornado not seeming an option i'm finding it hard where to turn to root.
Thanks in advance!
Hi XDA developers,
I'm a newbie. I've been searching posts on xda and still couldn't remedied the problem. I currently have the i9000m from Bell Canada. I upgraded my i9000m to 2.3.3 Gingerbread earlier in Kies. Recently, I've been trying to unlock my phone and without rooting, the best solution seems to be going back to Eclair, so I followed the youtube tutorial by djeddieone and tried to go back to Eclair using Odie. It basically flashes a rom (I suspect that's a T-mobile rom that shouldn't be flashed onto my phone) in Odin. My phone no longer boots and cannot get into recovery mode. (When I try to start the phone, there are random colour dots showing on the screen.) The only mode that works seems to be downloading mode. I think I need to flash a stock rom from bell, but the link on sammobile (i9000ugjk3) seems to be expired and cannot be downloaded. So i'm trying to find alternative ways to see how to remedy this problem.
Thanks in advance.
I highly doubt that Bell will release a new update for the i9000m. You are better finding a newer rom (JVT or newer) and flashing that via Odin. Im using CM9 nightlies (but I feel it has too many bugs for daily use). If you can find a newer rom that is tweaked, you should notice better battery, faster, etc.
Just my $0.02
Hey I had similar issue - tried flashing new firmware w/odin & stuck with download only... I finally went to a Bell store to send it in, but they were able to use new firmware recovery software to re-flash stock gb2.3.3! I just said Kies messed-up the phone... Anyway, it will get you back to stock functionality. Good luck!
Sent from my GT-I9000M
vassosman said:
I highly doubt that Bell will release a new update for the i9000m. You are better finding a newer rom (JVT or newer) and flashing that via Odin. Im using CM9 nightlies (but I feel it has too many bugs for daily use). If you can find a newer rom that is tweaked, you should notice better battery, faster, etc.
Just my $0.02
Click to expand...
Click to collapse
I have not found any bugs since I update to the latest update-cm-9-20120425-NIGHTLY-galaxysmtd-signed.zip
bioniceric said:
The only mode that works seems to be downloading mode. I think I need to flash a stock rom from bell, but the link on sammobile (i9000ugjk3) seems to be expired and cannot be downloaded. So i'm trying to find alternative ways to see how to remedy this problem.
Click to expand...
Click to collapse
Since you can still get into download mode, you're OK.
You can download the UGKG3 ROM files from this thread:
http://forum.xda-developers.com/showthread.php?t=1102881
Search for UGKG3.
The file is in 7Zip format. If you don't have something to unpack it, get IZArc.
Flash the 3 files and you should be up and running.
bioniceric said:
Hi XDA developers,
I'm a newbie. I've been searching posts on xda and still couldn't remedied the problem. I currently have the i9000m from Bell Canada. I upgraded my i9000m to 2.3.3 Gingerbread earlier in Kies. Recently, I've been trying to unlock my phone and without rooting, the best solution seems to be going back to Eclair, so I followed the youtube tutorial by djeddieone and tried to go back to Eclair using Odie. It basically flashes a rom (I suspect that's a T-mobile rom that shouldn't be flashed onto my phone) in Odin. My phone no longer boots and cannot get into recovery mode. (When I try to start the phone, there are random colour dots showing on the screen.) The only mode that works seems to be downloading mode. I think I need to flash a stock rom from bell, but the link on sammobile (i9000ugjk3) seems to be expired and cannot be downloaded. So i'm trying to find alternative ways to see how to remedy this problem.
Thanks in advance.
Click to expand...
Click to collapse
After you restore your phone to KG3 via Odin/Download mode per Black Rose's link earlier in this thread, you should be back where you started on KG3.
Then from KG3 ( 2.3.3),
I suggest:
1) Use SuperOneClick to root your phone (SuperOneClick can also UNroot your phone later if you want).
2) Use Galaxy_S Unlock by Helroz available on the G-store.
This worked well for me with no problems.
And just for reassurance, NEVER flash a ROM that is not explicitly for the i9000/i9000M to this device.