Database Develop

[Q] Bell i9000m - Froyo

Hi,
Has anyone been using froyo (JPK, JPM) on the i9000m (Bell version only) for more than 20 days without issues.
If so what is the batch number on the sticker under your IMEI. 08/10, 09/10 etc...
The reason I ask is coz bell swapped my phone due to SD issue and I donot want to rebrick it.
Thanks

Same here, sd problem with JPK but cant tell S/N since phone got swapped.
Also looking foward for a froyo that do not mess with internal sd

Your problem is not Froyo. Internal SD issues are unrelated to firmware.
Any Froyo + Bell modem works just fine. There are other modems with 850 support that work just fine too.

rdenis said:
Your problem is not Froyo. Internal SD issues are unrelated to firmware.
Any Froyo + Bell modem works just fine. There are other modems with 850 support that work just fine too.
Click to expand...
Click to collapse
My SD dissapears once in a while - i just reboot it and it comes back
is this happening to everyone ?

I had an issue where I restarted my phone and everything was erased. The SD card was still recognized. I had to reflash my phone with Odin to get it to work again though. Even the factory reset in the boot menu wasn't doing anything. I think it had something to do with the OCLF.
I've been using it for about 15 days or so now without OCLF and everything works fine.

Just wondering if there's a video on how to install Froyo on the i9000m. All these posts about corrupted internal SD is making wonder if it's worth upgrading to Froyo since it looks like it's pretty risky. Worse is I'm a noob and I've got a bad feeling about doing it myself without any help from a video.
Thanks

juinny said:
Just wondering if there's a video on how to install Froyo on the i9000m. All these posts about corrupted internal SD is making wonder if it's worth upgrading to Froyo since it looks like it's pretty risky. Worse is I'm a noob and I've got a bad feeling about doing it myself without any help from a video.
Thanks
Click to expand...
Click to collapse
If it makes you feel any better, my i9000m corrupted itself, despite not having been rooted, not running any lag-fix and running the same ROM out of the box...I managed to save it by combining a bunch of tips I found for people recovering from a bad flash.

mattomatic said:
If it makes you feel any better, my i9000m corrupted itself, despite not having been rooted, not running any lag-fix and running the same ROM out of the box...I managed to save it by combining a bunch of tips I found for people recovering from a bad flash.
Click to expand...
Click to collapse
Okay. So you're saying the phone itself is just badly manufactured? I was really hoping that froyo will fix all this awful things. I'm also having trouble connecting to Kies. Is Froyo for the i9000m out on Kies yet?

Hey,
Ive been running froyo stable on an i9000m for a month now using the kies reg. hack that was available a couple of weeks ago. Have had 0 problems.

This I9000M SD thing is a hardware issue. If you have a phone from a bad batch, you'll eventually succumb to the SD card issue regardless of what firmware you decide to use. People have even experienced this without ever flashing/modding anything. If you have a good phone, froyo or any other firmware for that matter will be fine.

The question is how long till you know you are out of the woods?
I bought my bell galaxy s on launch day and have had no issues with the sd card. Does this mean I am worry free? So that was back in August.
Also shouldn't there be a recall if this is happening to so many people?
Sent from my GT-I9000M

MaestroSeven said:
The question is how long till you know you are out of the woods?
I bought my bell galaxy s on launch day and have had no issues with the sd card. Does this mean I am worry free? So that was back in August.
Click to expand...
Click to collapse
i too bought mine on launch day, and i just sent it in for repair last week, so don't count it "safe" just yet.

MaestroSeven said:
The question is how long till you know you are out of the woods?
I bought my bell galaxy s on launch day and have had no issues with the sd card. Does this mean I am worry free? So that was back in August.
Also shouldn't there be a recall if this is happening to so many people?
Sent from my GT-I9000M
Click to expand...
Click to collapse
I bought mine in early August on launch weekend, and my SD card died this past weekend, even though I had never flashed any new roms.
I had to send it in for repairs.

kmkarim said:
Hey,
Ive been running froyo stable on an i9000m for a month now using the kies reg. hack that was available a couple of weeks ago. Have had 0 problems.
Click to expand...
Click to collapse
What registry hack ?
do you NEED to do a registry hack to get the official 2.2 froyo on your bell i9000m ?
if so, why ?
shouldn't we be able to upgrade officially without having to resort to hacks ?
or are you using this hack in the case that the official upgrade isn't out yet ?

15 days with doc's rom with lagfix ext4 no rfs

Funkadelick said:
What registry hack ?
do you NEED to do a registry hack to get the official 2.2 froyo on your bell i9000m ?
if so, why ?
shouldn't we be able to upgrade officially without having to resort to hacks ?
or are you using this hack in the case that the official upgrade isn't out yet ?
Click to expand...
Click to collapse
Currently there's pre release (dev roms) available via test mode on kies. It is in no way final but still pretty stable

rumy said:
The reason I ask is coz bell swapped my phone due to SD issue and I donot want to rebrick it.
Thanks
Click to expand...
Click to collapse
Just play and re-brick it. If it's going to fail it will fail and there is nothing IMO that you can do about it. If it needs to go in 5 times then so be it. I bought mine on a visa doubling the warranty. My guess is it will be going in at least 5 times unless they "actually" fix the issue which I doubt.

[Q] i9000M status (SD card and JL2)

Hi
I bought a used i9000m. It is running JL2 just fine. However I fear the SD card issue.
If I flash a custom ROM and/or a ext4 lagfix, is there more chances that I get the SD card problem?
And if I get this problem, can I flash back to JL2 to make it look stock before I send it for replacement?
Also I think the GPS is now pretty good with JL2. Slower to fix, but accurate.

it doesn't really matter what you do
if it's defective it will die eventually
better to die sonner than later, meanwhile there is still warranty

Yeah but if it dies and I am stuck with a custom recovery and/or a i9000 boot screen (instead of i9000m), they might not honor my warranty isn't it?

Also what is the easiest, least intrusive way to have an ext4 lag fix + root? I have seen many roms and kernels changing a lot of stuff. I really only need lag fix + root.
edit: I installed voodoo 5.1.

[Q] Any Bell users with the faulty SD card issue ever try custom ROMS ? Does it work?

Any Bell i9000m users out there ? Do you (did you) have the faulty SD card issue ? Are you able to successfully flash ROMS ?
I have the SD issue (I think) -- when I upgraded to 2.2 it Froze on the reboot and was stuck there - I had to do a recovery / wipe / clear cache and then it rebooted and is fine - but I think and suspect the SD card is faulty since it's not the first time I've had to do a reset.
Anyways, I'm thinking about trying out a ROM because my phone is ridiculously slow. I should also add I don't know how to root it (z4mod doesn't work neither does superoneclick)
But I am worried if I flash custom ROMS and Kernals etc. that I will lose everything -- anyone come across this concern ?

Hey,
I had a galaxy s with an internal sd card failure. i had to send it to samsung and they fixed it for me while putting the new 2.2 firmware on it.
if you want to try out a custom firmware, try seeARM's custom firmware. unlike other custom roms, this one uses a JL2 modem, which (assuming you're using this in north america) will let you also use the 850Mhz for 3G data.
the JL2 modem is suppose to be good for the bell phones because it doesn't increase the chance of internal sd failures (so i've heard, but I can't be sure about this). so if you want a custom rom, you can try to read up on that.

[Q] Bell I9000M and rooting & gingerbread upgrading how-to

Hello, I would like to get help on my attempt to root my phone and upgrading to unofficial gingerbread rom like Darky's; I have lost all my credibility to Samsung customer support.
Anyway, first of all, I am sorry for this thread which may be on the forum. However, I have been searching a lot but couldn't get clear updated how to for upgrading gingerbread from KC1.
Here is my phone spec
Model number I9000M
Firmware Version: 2.2
Baseband Version: UGKC1
Kernel Viosion: 2.6.32.9 [email protected] #4
Build number: Froyo.UGKC1
I would like to know two things.
A guide from KC1 to gingerbread not past firmware (was not sure whether it would be same)
How are we recovering 850MHZ band? They say put JL1 modem back but I didn't really get it.
Thanks in advance~

I have researched this but will not be doing it. The early models (build date prior to 1210) of the i9000M have internal SD card issues and the secondary boot loader you run now does something to prevent such corruption. To upgrade to gingerbread you will have to replace the boot loader. I suspect you will lose the secondary boot loader doing this and thus at risk of internal SD card corruption.
My fears may be groundless but that is why I am still running Darky's v9.5

jim5055 said:
I have researched this but will not be doing it. The early models (build date prior to 1210) of the i9000M have internal SD card issues and the secondary boot loader you run now does something to prevent such corruption. To upgrade to gingerbread you will have to replace the boot loader. I suspect you will lose the secondary boot loader doing this and thus at risk of internal SD card corruption.
My fears may be groundless but that is why I am still running Darky's v9.5
Click to expand...
Click to collapse
Mine is one of the early models (10.07), listed on the phone itself. I did have internal sd card issues and lost a bunch of stuff 2nd week of december when i upgraded to froyo (spoof fw in fact)...
Once i got it back 5 weeks later, i started researching different ROMs. I went to darky's 9.5 when it was released...
However, i went on a trip in late april, and sat next to a guy on the airplane who was running one of Darky's GB Release candidates, and he had NO issues with it.
Once i returned home, and darky's rom became more stable, i upgraded...
I was running 10.1, but now on F1 MOD V9 right now (still dark core 2.73).
So if you aren't sure about upgrading, understand that i haven't had any issues... however, everyone's experience will be different...

How can a Captivate phone SGH-i897 show different model in specs screen?

I'm hoping someone here can help in explaining this because this is something I've NEVER seen or heard of before and in theory, shouldnt be possible but i'm seeing it with my own eyes!
I'm (about to) purchase a slightly used Samsung Galaxy S CAPTIVATE model (SGH-i897) at least that is what the "boot up screen" shows.. I KNOW this is the Captivate.. i've seen the physical differences between it and the Vibrant.. they are basically the same phones hardware wise but do have a different physical appearance on the outside.. the Vibrant's model is GT-i9000..
now when I go to the "About screen"...the model shows the GT-i9000! How is this possible? I'm baffled because I know that i'm actually looking at a CAPTIVATE and the boot up screen shows the correct model number..but the android os (which shows the gingerbread 2.3.5 model in the about screen) is showing the model number as the VIBRANT.. gt-i9000, on the same phone!
I want this phone and was about to buy it but i'm thinking this could seriously cause problems when i go to root and mod it as the conflicting model numbers could create problems with the proper files and processes i'll need to follow when doing the root/mods...
Has anyone heard of this or can explain this because I am STUMPED!
THanks

ok, it appears like a custom Kernel was used cause this conflict. Make sense?
I looked at the About screen again and the KERNEL VERSION looks like something that is NOT the stock kernel. It states:
2.6.35.7-I9000XXJVT-CL617736
[email protected] #DarkCore_4.1_JVT_C
this has to be a custom Kernel right?
This phone must have been rooted and mod'd at some point (the seller didn't know and thought his cousin only unlocked the phone).
I assume a custom kernel that likely is typically for the Vibrant GT-i9000 was flahed with or without a custom rom to this phone and that is why there is the conflicting model numbers... this make sense?
Normally that wouldn't be good idea to use another kernel or rom for a slightly different model of phone but i guess it worked..
I would now like to confirm that this is the case and if so, that it is obviously ok..cuz the phone is working fine.
Should I now wipe the phone back to stock rom/kernel? Can I? if I want to do more mod'ing on the phone anyways.. different kernels and likely update os to ICS 4.0
Thanks for any help on this and hopefully this all makes sense now and explains what i'm seeing

Many of the custom builds for the Captivate are based on I-9000 framework. DarkCore is one of the custom kernels. This phone has been flashed. If you prefer a stock Captivate firmware, there are ODIN One-Click programs in the Development section that will put you back to an "Out-of-the-Box" state. Then do some reading if you plan on shopping around for different roms, as there are several different sets of bootloaders among them and a bootloader mishap is a surefire way to brick this phone.
Happy Flashing and good luck! Welcome to the Captivate!

The vibrant model number is T-959 or some ****..I9000 is the international galaxy s. The original.
It is really easy to switch what is displayed in about phone...it's all in the builds.prop located in /system
You can open that up with a plain text editor and change any instance of Gt-I9000 to sgh-I897 and Viola...
But as mentioned above, flashing to stock with Odin/heimdall will get you back to stock.
Btw what does "build number" say in about phone? Cause that is the name of the ROM that was flashed to it.

Build number says: Mosaic 8
So that is the custom rom that was flashed to the phone I take it?
Ultimately I dont want to go back to the stock rom/kernel but want to definitely flash to OTHER custom roms/kernels. With that being said will I have to go back to stock on either rom or kernel FIRST before doing another change?
I'd like a kernel that will allow me to play with some overclocking and the rom(s) can be one of many.. preferrably I want to put ICS 4.0 on this
Can anyone give me the links to the best info/tutorials to flash the kernel/rom's to do so on this phone?
As said, the actual phone is an unlocked and rooted AT&T Samsung Galaxy S Captivate SGH-i897 but has been already flashed with custom rom kernel as follows:
Model Number
GT-i9000
Firmware Version
2.3.5
Baseband Version
I9000UGJK4
Kernel Version
2.6.35.7-I9000XXJVT-CL617736
[email protected] #DarkCore_4.1_JVT_C
Build Number
Mosaic 8
Thanks

M8 is a great custom rom. You shouldn't need to flash to stock before flashing a new rom. Just follow the steps in the first post of each rom you want to flash. A good ROM to try next would be Mosaic 9

yeah...i hear great things about mosaic!

Thanks..i figured it was a good rom..i play around with it for a while.. it also came with the custom kernel from DarkCore..
I'm fairly new mod'ing rooted phones and all that so I'm curious if I can install a different custom kernel on this Mosaic 8 Rom and if so, what's best way? I want to use one of the many on this site that allow for oc'ing...is it ok to replace the Darkcore Kernel that came with this rom to any other or not?
THanks

hey buddy, i happen to be the lead developer for mosaic.
you are more than welcome to change the kernel, the best way to do that would be in cwm recovery...which can be accessed by holding down on the power button and choosing recovery. or by powering off and holding vol up and power til you see the first splash (that should actually say I9000) then let go that will boot into recovery.
if you see an at&t screen at all the its vol up AND down AND power.
as said above i have updated mosaic, and the latest version includes a kernel that is overclockable already, this one to be exact the .tars in post 1 are for use with odin. post 2 are zips to be flashed in recovery. ater the kernel is flashed it will install an app called semaphore, in there are a bunch of options including oc up to 1300Mhz
that being said...FIRST I would play around with it some more and get used to it WHILE DOING SOME RESEARCH AND READING...i mean you just got the phone...get to know it take her out on the town before you get her all nekkid and vulnerable

THANK YOU SO MUCH for this reply! I was just trying to get into recovery mode and I noticed this phone was allowing me.. this is due to the rom/kernel on it..but you're post with the info WORKED! I was about to start doing a bunch of stuff to try and fix.. THANKS
This whole double splash screen is very new to me with it showing the phone as TWO different models..
I see you have the new Mosaic 9 out..and that's the one you're takling about i take it? and it comes with another new custom kernel that will allow for oc'ing too? sounds good..and 1300 is more then enought.. I'm happy with 1.2 if I can.. dont need to get crazy and try for 1.6 like some..
Just follow the steps on the main page for that rom and all should be good? What will be the easiest way for me to flash to your new rom/kernel? Can I do it from a rom manager or use sd card or internal mem? Any help on this is greatly appreciated! Thanks again for posting a response to my concerns!

btw can i just update this Mosaic 8 rom to that new custom kernel you're talking about or do i have to update to the new Mosaic 9 rom first?

You can flash that on 8.
Don't ever use ROM manager, it doesn't work right on the galaxy line.
And whenever sdcard is mentioned, that is the internal sd, cwm does not flash from an external sdcard.
To flash mosaic 9 over 8 just put ROM on sdcard, boot into recovery, wipe data/factory reset, then go to install zip from sdcard, choose zip, and find the ROM you just downloaded.
Flash the kernel the same way, just don't do the wipe first.
The ROM flash will wipe all your apps, the kernel will not, use titanium backup to backup your apps, then restore them after the flash. Again only needed if you're flashing the ROM and you can flash the kernel on the ROM you have now,
but a backup is a good idea before any flash if something were to go arwy.
As for the 2 boot screens (and the different button combos for recovery, btw download mode is vol down and power), is because the phone has I9000 bootloaders, which is the first splash you see, the second splash is the kernel, both darkcore and semaphore use the same splash the one that says sgh-I897. some kernels use a custom image there instead.
But again, i urge you STRONGLY, PLEASE read, and understand completely what it is that you want to do, and more importantly how to fix a situation that doesn't go as planned, BEFORE you start flashing stuff. Please.

Thanks again bud this is all so helpful. I already downloaded your mosaic 9 zip. Quick question..do i have to format my sd card a certain way first for the update to work? on past.flashes on different phone certain.partioning had to be done on the sd card in order for the update to work.successfully.
Thanks n looking forward to this mosaic 9.
Sent from my GT-I9000 using XDA App

Nope, you're good. Anything that was needed, which was flashing gingerbread bootloaders, has already been done by the previous owner.

Thanks again bud. That last question was pointless cuz i read back again and u mentioned that the sd card stated is always internal and not external..so obviously i wouldnt need to format n partition etc. Thats a bit newer for me well on this new phone anyways. Used to using ext card in past.
As of now ive only updated the kernel to the new one and not the whole new rom...yet. Will play around with it for a bit. The oc was very easy and working just fine.
Btw any plans to do this mosaic rom on ICS 4.0 at all? Or maybe there is one u could recommend? i really want to check it out as so many are "raving" about the new ics os and that it the best by far, etc. Whats your take?
One other question about the flashing from the internal sd now, hope this aint silly but if the zip rom file is saved to the internal mem and im doing the usual data wipe/factory reset wont everything get cleared.including the rom file itself and then not find it when i go to do the update?
and again thanks for all the info, still a bit of noob when it comes to the phones side of things but fyi im definitely a techie when it comes to the pc hardware, software and networking side. Take care
Sent from my GT-I9000 using XDA App

Data wipe/factory reset only wipes the /data partition. Leaving all others including /sdcard intact.

Data factory reset clears (/data, /dbdata or /datadata depends on the ROM you are on, /cache, and /mnt/sd_card/android.secure

Definitely gonna wait a while before flashing any ICS4 roms as still too early and lots of bugs to workout. Im hoping u guys eventually come out with an ics rom cuz this mosaic 8 n 9 are damn good and high quality and read a lot of good things too.
Sent from my GT-I9000 using XDA App

So the bootloaders, when are they input or changed? Is it a seperate update or do they typically come with a rom or kernel? So the ones i have now with the dual splash screens (gt-i9000 then sgh-i897), will i keep those if i wipe and flash a different rom or will a new set of different bootloaders come with most other custom roms? I still dont fully understand that yet and would prefer to mess with them as little as possible cuz i know how important they are and thats an easy way to mess up a phone.
Another quick question i have is about the Captivate phone itself...i know all the specific hardware specs and its states it has 512 ram outside of the 16gb storage/2gb internal rom but why can i only find spec screens that show my phone having 323mb of ram and of that most of it is used up all the time even after a fresh wipe and flash of the mosaic 8 rom ane nothing new installed? Does this have something to do with the rom itself or am i missing something? a little puzzled by this. Part reason i upgraded to this phone was to get better hardware and have more memory cuz i like to eventually install a ton of apps but im thinking i could quickly run into issues with the numbers im seeing. Any thoughts on this? Thanks
Sent from my GT-I9000 using XDA App

Bootloaders ate only flashed with a pc flashing program such as Odin or heimdall.
The second image may change, that within the kernel itself, the first image will not.
As far as storage space goes, you have 16gb on the entire phone. 2gb of that is for user apps. About a Gb for the system, and about 13Gb on the sdcard.
you do have 512mb of ram, but some of that is always used by the system leaving the user with 323. And THAT being mostly used up is just they way Android handles memory. It keeps recently opened applications loaded in memory so that if you wanna access it again it will open much faster than having to reload it. It will also kill off apps as the memory load grows. Put simply: free ram is wasted ram.