Database Develop

[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] Which firmware is safe for my Bell I9000M

* 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

[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] what is going on with my captivate?

so i have a captivate that ive had for a little while now. and of course ive flashed a few different gingerbread roms like usual.
anyways i wanted to try a froyo from so i used the odin 1 click stock tool to flash back to jf6,
that worked, but for some reason it wont allow me to master clear.
also my phone keeps switching between showing service, and a blue circle with a cross out sign....
(no internet access)
if i flash a rom over it, it starts acting like normal again
any idea whats wrong or whati can do?
thanks!

USB Debugging is need to do master clear. Did you turn on debugging?

speedy_11 said:
USB Debugging is need to do master clear. Did you turn on debugging?
Click to expand...
Click to collapse
yeah it was enabled.

The_Zodiac said:
so i have a captivate that ive had for a little while now. and of course ive flashed a few different gingerbread roms like usual.
anyways i wanted to try a froyo from so i used the odin 1 click stock tool to flash back to jf6,
that worked, but for some reason it wont allow me to master clear.
also my phone keeps switching between showing service, and a blue circle with a cross out sign....
(no internet access)
if i flash a rom over it, it starts acting like normal again
any idea whats wrong or whati can do?
thanks!
Click to expand...
Click to collapse
This happened on one of my old cappies that i got replaced. It was a 1008 build. It's an error in the efs folder. Did you make a backup of your efs folder before you started flashing?
If you didn't here's a method that worked for me that might get you back to normal. What i did was use Kies mini to upgrade to stock 2.2 then make sure the botton combos were working (vol up+dwn/plug usb to get to download mode, and vol up+vol dwn + power to get to recovery.) If those are working, now flash back to stock using Odin 1 click.
This wokred for me. hope it helps.
If you have your original efs folder, use Root Explorer to place the original folder ni place of the current one while on stock 2.1, then reboot to see if it worked.

What Gingerbread Roms did you "play" around with, I'm guessing you used the I9000 bootloaders also?

jack man said:
This happened on one of my old cappies that i got replaced. It was a 1008 build. It's an error in the efs folder. Did you make a backup of your efs folder before you started flashing?
If you didn't here's a method that worked for me that might get you back to normal. What i did was use Kies mini to upgrade to stock 2.2 then make sure the botton combos were working (vol up+dwn/plug usb to get to download mode, and vol up+vol dwn + power to get to recovery.) If those are working, now flash back to stock using Odin 1 click.
This wokred for me. hope it helps.
If you have your original efs folder, use Root Explorer to place the original folder ni place of the current one while on stock 2.1, then reboot to see if it worked.
Click to expand...
Click to collapse
im not sure what build because its a replacement from att and they didnt put the build number on the sticker.
i did backup the efs folder so i can try that.
melbourne408 said:
What Gingerbread Roms did you "play" around with, I'm guessing you used the I9000 bootloaders also?
Click to expand...
Click to collapse
a few apex, dvlevs, obsession. and yes i loaded gb bootloaders.
does jf6 flash you back to eclair bootloaders?

The_Zodiac said:
im not sure what build because its a replacement from att and they didnt put the build number on the sticker.
i did backup the efs folder so i can try that.
a few apex, dvlevs, obsession. and yes i loaded gb bootloaders.
does jf6 flash you back to eclair bootloaders?
Click to expand...
Click to collapse
Your going to want to flash back to eclair (imho) or froyo if you'd rather, but it will have to be done through odin without a 1 click method. If you know what I'm talking about all good. If not lemme know and I'll help ya to the links, cleaning the kitchen atm but its all good
Sent From My Swaggin 1.6 Son Of A Glitch

^^^^Wtf are you talking about? Odin one click to jf6 (eclair) includes both bootloaders... Thus replacing the I9k ones...
Op if everything works after you rom it and you have no plans to go to stock does it matter?
It could just be how the phone acts with the jf6 modem as its a signal problem...
And what exactly are you doing when trying to master clear and what happens?

studacris said:
^^^^Wtf are you talking about? Odin one click to jf6 (eclair) includes both bootloaders... Thus replacing the I9k ones...
Op if everything works after you rom it and you have no plans to go to stock does it matter?
It could just be how the phone acts with the jf6 modem as its a signal problem...
And what exactly are you doing when trying to master clear and what happens?
Click to expand...
Click to collapse
my concern if my phone stops working for whatever reason and i sen it in under warranty it will have to be stock att froyo.
(i get to that by flashing stock eclair then by using mini kies)

The_Zodiac said:
my concern if my phone stops working for whatever reason and i sen it in under warranty it will have to be stock att froyo.
(i get to that by flashing stock eclair then by using mini kies)
Click to expand...
Click to collapse
Couple things for the Master Clear
1. Make sure to shut down Odin then restart it without the phone connected
2. If that doesn't work restart your PC
3. If all else fails, root, install ROM Manager, get into CWM and do a factory reset
Like Studacris said, Odin to JF6 flashes the proper bootloaders, so you dont need to worry there. I've done it TONS of times
Edit** Are you using this Odin?
http://www.mediafire.com/?0w2y31maz8mdom4 If not, I would HIGHLY recommend using it

studacris said:
^^^^Wtf are you talking about? Odin one click to jf6 (eclair) includes both bootloaders... Thus replacing the I9k ones...
Op if everything works after you rom it and you have no plans to go to stock does it matter?
It could just be how the phone acts with the jf6 modem as its a signal problem...
And what exactly are you doing when trying to master clear and what happens?
Click to expand...
Click to collapse
Dam, bad correlation on my part. Didn't want anything going wrong with bootloaders, my self learned fault on being incoherent and half asleep, just didn't want any brick brick brickety brick bricks-as my dad laughs to me all the time. Thanks for the correction.
Sent From My Swaggin 1.6 Son Of A Glitch

I'll try to follow up on what Studa was going for.
The_Zodiac said:
my concern if my phone stops working for whatever reason and i sen it in under warranty it will have to be stock att froyo.
(i get to that by flashing stock eclair then by using mini kies)
Click to expand...
Click to collapse
Ok, but that would be a good thing, you can just use the signal problem as an added reason for sending it in. If you can flash stock and it boots, all is well. Anything else just goes in your favor of why you deserve a new one.
Plus, if the phone stops working to the point it does not boot they will have no real way of telling what was running before, nor will they waste the time to find out. It will get tossed into the re-write pile, and go thru the paces for becoming a referb.

You do realize that the phone has to be regularly on to do a master clear and not be in download mode right?

dsilvan55 said:
You do realize that the phone has to be regularly on to do a master clear and not be in download mode right?
Click to expand...
Click to collapse
yes i do...

Reflash the stock jf6 with no sim card
Sent from my GT-I9000 using XDA App

Problem with my Bell i9000M (Needs serious help)

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.