[Q] Which firmware is safe for my Bell I9000M - Galaxy S I9000 Q&A, Help & Troubleshooting

* Edit post
* Delete post
* Report this post
* Reply with quote
GT-I9000M Question on firmware.
Postby icehunter » Sun Dec 19, 2010 8:45 am
Hi,
I bought my phone from bell canada and it came with JH2. I then flashed straight to JK4 with kies. My phone itself seemed to have no issues other than occasional black screen where I couldn't see anything.
I used oenclickroot to try and get clockwork mod on to backup phone, but it failed to unroot the phone after. So I forced another flash from kies. It seems the unroot is gone.
So i really have 2 questions.
1) Is the phone still rooted? SU is not present
2) Is it safe to use the froyo firmwares or are they bricking the phones?
I ask number 2 because I found JK3 on samfirmware.com
I9000UGJK3 ## 512.PIT Version 2.2 2010 November DOWNLOAD 1 file select NO .PIT
This seems to match my phone?
What should i do
Thanks very much

The only safe firmware is jh2, the one that came with the phone. That is, with no lagfix or root. Why? Because that's stock. If your looking for safe, don't bother hacking.
On the other hand, if you want to experiment, try different roms. I've used jk3 and 4 (which was pulled) with success and now I'm running docs rom with no lagfix just fine. Most problems people report aren't issues with the phone but mistakes made by not reading the instructions.
Sent from my GT-I9000 using XDA App

Since I used kies to put the JH2 on there, are the previous roots I've done completely gone? I want to make sure I don't have a trace of them on there ^^ And thank you for your reply

windraker said:
Since I used kies to put the JH2 on there, are the previous roots I've done completely gone? I want to make sure I don't have a trace of them on there ^^ And thank you for your reply
Click to expand...
Click to collapse
Probably. I've never used Kies (well, I installed it, ran it, flashed jk4 over JH2 that I flashed with Odin and uninstalled it), but I'm assuming it would have wiped out the root. I wouldn't worry too much about having your phone rooted, it doesn't really affect anything unless you manage to mess something up with busybox.
If you aren't comfortable farting around with the phone, I'd just wait for Bell to officially release JK4. Who knows, maybe they'll skip right to 2.2.1. If you are, give Docs or Darkys firmware a shot, just make sure you follow all the instructions including backing up /efi, and making sure your 3 button recovery works. If you got those, you're all set, the worse that can happen is that your internal SD dies, which despite all the naysayers, isn't very common given the number of phones out there.
EDIT: I forgot to mention, if you flash JK3, just flash the tarball you downloaded under "PDA" in Odin, and uncheck re-partition (no pit, you're already at 512). JK3 worked much better for me than JK4 (buggy stuff), but YMMV. Again, search the forums and make sure you backup efi just in case.

shadoslayer said:
Probably. I've never used Kies (well, I installed it, ran it, flashed jk4 over JH2 that I flashed with Odin and uninstalled it), but I'm assuming it would have wiped out the root. I wouldn't worry too much about having your phone rooted, it doesn't really affect anything unless you manage to mess something up with busybox.
If you aren't comfortable farting around with the phone, I'd just wait for Bell to officially release JK4. Who knows, maybe they'll skip right to 2.2.1. If you are, give Docs or Darkys firmware a shot, just make sure you follow all the instructions including backing up /efi, and making sure your 3 button recovery works. If you got those, you're all set, the worse that can happen is that your internal SD dies, which despite all the naysayers, isn't very common given the number of phones out there.
EDIT: I forgot to mention, if you flash JK3, just flash the tarball you downloaded under "PDA" in Odin, and uncheck re-partition (no pit, you're already at 512). JK3 worked much better for me than JK4 (buggy stuff), but YMMV. Again, search the forums and make sure you backup efi just in case.
Click to expand...
Click to collapse
hmm, i never thought I installed busybox, i teried z4root, which failed to unroot, error 7 or something and I did the superoneclick which always froze at end, I never actually downloaded busybox as far as i know
I'm gonna try odin tonight, unless I can somehow make kies install JK3 or JK4 again ^^, btw, I looked up EFI, do you mean backup my rom???

My bad, its /efs not /efi...i need to lay off the eggnog.
There is a great sticky in this forum that had the instructions. Basically flash jh2, use one click root and follow the instructions. Its always a good idea to back this up in case something nukes your IEMI
Sent from my GT-I9000 using XDA App

Related

[Q] Should I downgrade my Bell JK4 2.2 to 2.1 before it bricks?

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

[Q] Can't root Bell i9000M

Hey,
First of all, I tried to find the answer tot he problem in the forums before posting but I was unsuccessful.
I am having some trouble rooting my Bell i9000M. It came with Froyo when I recieved it. I tried androot, z4root, and SuperOneClick but they all failed. In my forum research I came across some comment that said z4root does notwork with the UGJK4 version.
I am restricted to 2 computers, a Mac and a laptop running Ubuntu Linux, so it'd be difficult for me to use Kies for anything.
What is my next step in rooting the phone?
I also tried to flash a kernel, which I read I can do without root access usining heimdall but this error occured: unknown required load command 0x80000022.
My phone is able to do into 3-button recovery and download modes.
Thanks in advance for your help.
Alex.
edit: spelling
Upgrade to Jl2 use superoneclick it works.
Sent from my GT-I9000 using XDA App
have done a lot of reading over the last week trying to work out how to root my SGS i9000M, checking both these forums as well as android & phandroid, as well as googling the issue and trying the Market. I've also checked out many youtube videos on this topic but they seem out of date now. I note the most recent thread on here by liv4air (march 2011) but it doesn't really help with my query.
I am a total noob with regard to this - only heard about rooting a couple of weeks ago but I definitely like the idea. My 1st handset had to be replaced due to a sound issue (it had 2.2 Froyo) - was replaced with a handset sourced for Canadian market (linked to Bell - has lots of stock apps from them that are useless to me). I'd like to get rid of them to start with, but this handset is running Eclair 2.1 - didn't realise this for awhile after it was replaced and didn't actually understand the differences between the builds and firmware.
So now i've got GT-i9000M, Eclair.UGJH2
kernel [email protected] #2, firmware version 2.1-update1 (updated via Kies).
I have tried the one click root download which put the 'update.zip' file on my SD but when I tried to install this in the recovery mode (have discovered that I have the download and recovery mode buttons - also totally new to me!) there was a red error message:
E:Error in /sdcard/update.zip
(status 7)
Installation aborted.
Have seen the Ryan ZA OCLF in Market too, but understand that the 'rooting' ability has been removed from that app.
Have downloaded the Odin3 program to maybe try to root it via this method but am confused about how to get kernels/which ones to get...or even if that's what I have to do! can find various kernels etc at SamFirmware but not really sure how to use them.
Am I even close to working out how to root this phone!?
Please help!
Flash EZbase : http://forum.xda-developers.com/showthread.php?t=991792 with odin. All the instructions you need are over there.
It's a complete, stock rom except for a few modifications (such as root and cwm recovery), you can choose to download froyo or gingerbread depending on what you want to flash next, if you do.
(Froyo is the 2.2 android OS that has more stable custom roms/kernels while Gingerbread is the new 2.3.3)
Also since you're on a i9000m, you may want to flash a "i9000m" modem (with the 850mhz band) found here: http://forum.xda-developers.com/showthread.php?t=876391 after flashing, but it's not necessary.
Thanks for that link - it looks promising so i'll read through it properly and give it a go soon. I can't query to that forum as it's a development thread but a couple more queries...just want to make sure i don't do anything stupid!
The instructions state: Download all the EZOdin, EZbase CSC, PDA, PHONE and PIT if you do not have Samsung Kies installed, The Samsung USB Drivers will be required to.
Do you know if this means to download ALL those things if I don't have Kies installed, or just PIT if I don't have Kies installed? I do have Kies installed so not sure which of the above I require.
And on the Kies topic, it also states: If Samsung Kies is used please make sure you kill all Samsung Kies related services that are running (kies, tray agent, etc.)
sorry if i'm making you smack your head in disbelief at my ignorance, but does this mean I can use Kies to flash a kernel to my phone (and hence not need the above)...or that when using EZOdin to flash my phone, I need to make sure I have Kies completely shut down during the process?
And I assume by having Kies on my PC, I do not need to download the samsung USB drivers.
Thanks!
What the first sentence means is that you will need the usb drivers if Kies is not installed. There's a period missing I guess.
For the second one, it means you need to close Kies completely before flashing.
Thanks!
Got EZOdin, and the PDA/PHONE/CSC files, but when I click on the EZBase pit file this is all that's written on the page it opens:
v˜4
Edit: don't know why the rest of my post wouldn't complete above, but no luck in downloading the EZOdin.pit file, either at home (or now here at work).
Any thoughts? Reiterating my noob knowledge (or lack thereof) - I assume the .pit file is crucial to the process? Is there anywhere else I get this file, or another .pit file that will suffice?
Maybe i'll do some reading on PIT....
Rooted successfully!
been a bit of a task over the last fortnight trying to work out the ins & outs of rooting, the ways to go about it and to find a method that worked, which i've finally done.
this is really just a post in case anyone in a similar position and feeling as lost as i was along the road to discovery might benefit from how i managed it.
(and this assumes you've already read the many disclaimers out there about bricking your phone, & making sure you do a lot of reading of the threads on this topic)
i ended up using shortfuse superoneclick. got the program from shortfuse.org - v1.9. i downloaded it and ran it with my anitvirus turned off. It worked fine as per the instructions on the website (shortfuse.org) or in the thread here.
Bell Galaxy Vibrant i9000M
recently upgraded from 2.1 to 2.2 via Kies
UGKC1
kernel 2.6.32.9 [email protected] #4
...now to do some proper exploring and fun!
Well done, take your time and,welcome to the world of fast galaxy s!!
Sent from gt i9000 insanity 8.5/fugumod
see these instructions: http://touristinparadise.blogspot.com/2010/11/samsung-galaxy-s-how-to-install.html
good kernel, root, cwm and excellent, clear instructions
lgsshedden said:
see these instructions: http://touristinparadise.blogspot.com/2010/11/samsung-galaxy-s-how-to-install.html
good kernel, root, cwm and excellent, clear instructions
Click to expand...
Click to collapse
Now rooted and have gone and obtained TiB, Terminal Emulator, Wireless Tether and Root Explorer.
Had the speedmod kernel downloaded and was going to try to flash it to my phone via Odin as per the link you provided but wasn't sure if the kernel itself would root my phone and didn't get replies for my query about that.
So...now that i'm rooted you would still recommend flashing the speedmod kernel? I would assume mainly for the benefits of the kernel itself? Any likelihood of problems arising, having already rooted with SuperOneClick?
Thanks for your advice - the speedmod does sound good and have heard many happy reports from users.
yes it would have rooted you hence my suggestions for using it: sorry to have not been more clear
yes the speedmod kernel would be an upgrade over the stock one but my signature indicates what I use now: very fast and outstanding, not available on xda
I was never able to get oneclick to work as it was blocked on my pc, so my solution stemmed from having to find an alternate answer to a problem like yours
its fun once you get started: lots of help, even more opinion!

[Q] I9000M 2.2 UGKC1 to 2.2.1 XXJPY questions

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.

[Q] Does repartitioning delete 'update.zip' file

I tried ODIN for the first time the other day to install JVQ then JVR.
When I did that, I selected repartition with the 512 pit. Everything went somewhat fine, but because of issues I was experiencing, I went back to Stock 2.2 KC1 (i9000m).
When I did so, I noticed all the Bell Bloatware was still missing (the install of KC1 was done through KIES after spoofing the firmware to think it was JL2.)
So the phone still appeared ot to be completely stock.
I went into recovery mode and tried everything. I noticed it would fail when trying to apply update.zip. Something about a signature or whatever.
Now that I applied the new KG3 (Gingerbread) from Kies, the Bell Bloatware is still not there, and I notice I don't have the normal shutdown sound that was there with the original KC1.
My question is, did repartitioning cause a complete delete of everything on the phone, including the update.zip?
If so, how do I get this thing back to complete stock? I mean out of the box stock.
Its not like I want the bloatware, but I just want to make this thing original again, to ensure no corruption in what the new Gingerbread is trying to do.
Thanks
Ok confirmed via another user in another thread that the Shutdown sound is no longer a part of KG3.
Now if I can just confirm the rest in my initial post.
Any help guys?

[Q] Giving Up On Kies Upgrade Attempt, How Can I Try 2.3 without JF6?

Hey folks. I basically just want Gingerbread on my phone, but I'm having issues doing it through Kies as it won't recognize the current firmware when I connect.
I'm not able to flash to JF6 in Odin OneClick without getting an ATT boot screen and nothing more.
Apparently I need to have JF6 in order to get Kies to recognize the phone. I'd like to get this done today (Been two weeks without full function), and I'm thinking I just want to flash to a good rom that runs 2.3.
Is there anything I can do to flash to something other than I896UXJL1-stock or I896UXJI2 TORONTO? These flash well, but are not what I was looking for. Again, I'm going to need something that doesn't require JF6, or another method to get JF6 on without getting stuck at the ATT screen.
Any flash with Odin does not require you to be on a prerequisite firmware, it will flash over whatever you're running.
Go to the Dev section, find a gingerbread firmware with bootloaders included, put phone in download mode and flash.
Full List of Necessary Files for Successful Flash
Okay, I've been browsing around, trying to find something suitable, but now it would seem that I'm not able to flash anything except for the OneClick method which gives me that ATT screen.
I read somewhere that later editions of the Captivate may not work out well with certain Odin flashes. I think my phone is 1038?
I'm hoping that someone might be good enough to show me how to get this thing to flash to what Samsung sent to Rogers from the factory, or at least to a point that I can successfully flash to 2.3. Right now I'm stuck.
Thanks in advance for any help.
Okay, I'm back to UXJL1, using Odin 1.81, and I also found a OneClick that reportedly switches out the bootloaders for GB bootloaders. I tried it, and it did give me an ATT screen, followed by a normal boot and I was back to having apps like Titanium crashing on boot, which is beyond annoying to figure out.
My biggest issue is that I think I have a decent grasp of what's involved in this process, but I don't know which file is compliant with which. I seem to always use 512 for the partition, but I see some variations in that. I also don't know what to do about the bootloader situation except the one tool I mentioned above.
Basically I could either use what I have, go back to Firefly, or keep trying this GB upgrade. I'd rather keep trying but I also need a phone.
I have a ton of different firmware files at my disposal and can download whatever else I need if mentioned, I also have a few different versions of Odin, and OneClick. I downloaded Odin OneClick 2.xx for rooting purposes and it seemed to work with a flash I did today.
Again, thanks for any help.
As for bootloaders. If the 1 click doesn't work, or you don't know if your phone likes 1 clicks I've attached a pda.tar and a odin in a rar that contains just GB bootloaders. This isn't my work I downloaded from somewhere in xda, I just can't remember where so I can't link. All credit to whoever created it. I can't speak specifics for I896 but random FC's usually means a bad flash. Try downloading again or another odin rom. Sorry I can't be any more help.

Categories

Resources