Related
Hi, I was just wanting to clarify what firmwares are safe to use on the Bell i9000.
I previously screwed up my phone because I flashed JPC and it corrupted my internal memory.
I was hopping to clear up what can be flashed on the Bell version of the i9000 and what can't me.
So far this is what I know.
Good:
JP2
JP3
BOJI
HVJHI
GJH2
JM2
JM4
XWJM5
JM7
JM8
UGJH2
1.20Ghz Kernel
Bad:
JPC
JPH
(possibly caused by One click lagfix)
To keep 850mhz radio
Modem: http://www.mediafire.com/?qic38waf8px13mz
CSC: http://www.mediafire.com/?7ow6p25nhzle5jo
JPC worked fine on my Bell Vibrant. Any of the international firmwares will work without any issues short of the issues inherent in the firmware already.
That was my understanding as well, but many people and all of the seem to have Bell Vibrants are getting corrupt sd cards from JPC, which basically bricks the phone.
My Bell Vibrant was Bricked no idea why ? because i didn't root or use a custom ROM so Bell [email protected]#$%# me over. Dammit 500 $ paper weight.
Now i gotta wait 3 to 6 weeks unless someone knows how to unbrick one without the 3 button recovery mode ?
Anyone ideas ? lol
Fuzz21 said:
My Bell Vibrant was Bricked no idea why ? because i didn't root or use a custom ROM so Bell [email protected]#$%# me over. Dammit 500 $ paper weight.
Now i gotta wait 3 to 6 weeks unless someone knows how to unbrick one without the 3 button recovery mode ?
Anyone ideas ? lol
Click to expand...
Click to collapse
No exactly what this thread is about sorry.
I also have a brick sent back to Bell/Samsung for repairs due to JPC.
I'm pretty sure any other firmware is fine. I had the HK JP2 installed without issue. Other than that I just stuck with the UGJH2 as it's nearly as new as any of the international firmwares and runs smooth, even without a lagfix.
mafiaboy01 said:
Hi, I was just wanting to clarify what firmwares are safe to use on the Bell i9000.
I previously screwed up my phone because I flashed JPC and it corrupted my internal memory.
I was hopping to clear up what can be flashed on the Bell version of the i9000 and what can't me.
So far this is what I know.
Good:
HK JP2
JP3
UGJH2
Bad:
JPC
JPH
Click to expand...
Click to collapse
I've had no problem with JPC. I've flashed it a couple of times over the past few weeks. It ran extremely well. JPH on the other hand has hooped my phone.
jentech said:
I've had no problem with JPC. I've flashed it a couple of times over the past few weeks. It ran extremely well. JPH on the other hand has hooped my phone.
Click to expand...
Click to collapse
For me and some others JPC did it :S
jentech said:
I've had no problem with JPC. I've flashed it a couple of times over the past few weeks. It ran extremely well. JPH on the other hand has hooped my phone.
Click to expand...
Click to collapse
JPC ran like garbage on mine but no major issues aside from the lag, JPH though has been a champ for me thus far.
Sent from my GT-I9000 using XDA App
we need to pin down as to what caused these SDCARD errors so we can all avoid that.
I'm thinking maybe repartitioning with the wrong pit file might cause something like this ?
I'm using JPC on my I9000m now, working nicely (some lag here and there, but nothing AutoKiller can't take care of), and since I saw the post about the SDCARD error on one of the i9000m, am a bit hesitant to flash JPH.
Problem is, if it does get bricked, its basically paper weight because am in the US and doubt Bell or Samsung US/Canada would be willing to help.
I also would like to find out what is causing the problems, it has to be an issue with only some of the Bell ones because there are people running these frimwares with no issues.
mafiaboy01 said:
I also would like to find out what is causing the problems, it has to be an issue with only some of the Bell ones because there are people running these frimwares with no issues.
Click to expand...
Click to collapse
am just throwing out ideas here, but it could be one of the lag fixes causing corruption in the internal memory if not correctly uninstalled before flashing new firmwares ?
jentech, did you use any of the lag fixes prior to flashing JPH ?
madmack said:
am just throwing out ideas here, but it could be one of the lag fixes causing corruption in the internal memory if not correctly uninstalled before flashing new firmwares ?
jentech, did you use any of the lag fixes prior to flashing JPH ?
Click to expand...
Click to collapse
JPC messed mine with no lagfix installed. This has been ruled out in several threads on xda.
Sent from my I7500 using XDA App
it is also highly likely that us bell users are flashing with bell modem so that we can keep 850 out of the box and is root of the sdcard corruption.
for some reason i remember having nexus one that every firmware and mod always strongly warned that froyo modem is required as well as flushing dalwik cache right after upgrading from éclair.
and here most of us are doing just that using jh2 with froyo.
well as for me i know i wont be upgrading to froyo as long as this thing with sdcard keeps happening as my 30 days was up on sept 9 so no more DOA and even if under warranty still not willing to be without the phone for more than a month.
madmack said:
am just throwing out ideas here, but it could be one of the lag fixes causing corruption in the internal memory if not correctly uninstalled before flashing new firmwares ?
jentech, did you use any of the lag fixes prior to flashing JPH ?
Click to expand...
Click to collapse
I lag fixed mine but as others have said it doesn't seem to be the cause.
Though I did seem to find a progressive decay in the phone until it finally shut off and never started. It wasn't all of a sudden.
mafiaboy01 said:
I lag fixed mine but as others have said it doesn't seem to be the cause.
Though I did seem to find a progressive decay in the phone until it finally shut off and never started. It wasn't all of a sudden.
Click to expand...
Click to collapse
Which lag fix ? if you used OCLF, did you allocate the entire internal memory to it ?
madmack said:
Which lag fix ? if you used OCLF, did you allocate the entire internal memory to it ?
Click to expand...
Click to collapse
Yes I did use OCLF, I only allocated the default so something like 800mb.
Sent from my GT-I9000M using XDA App
All the ones bricked, were you also having issues with the 3 button recovery? Trying to see if there is any connection there.
I'm reading around regarding this error, and it seems some guys with other phones and the same error got things running back by using Parted. You basically boot into recovery, push Parted to the bin folder, and then repartition/format that failed block: mmcblk0p1
I'm not sure what the file system currently is on that block, but the guys I got this info from were formatting it to ext2. I think if we modify it to match the filesystem that our ROMs require, then we're good. It's a long shot though, and if anybody has a bricked phone with them now, they could give it a go before sending it back for repair.
I used kies yesterday and upgraded to UGJH2, don't remember what it was before, whatever was factory loaded but now I am having all sorts of problems that I did not before.
GPS is way out of wack. Phone freezes. Signal disappears. Right now it's running smoothly but all day it was going retarded.
I give it a bit, if it doesn't sort itself out by the time froyo rolls I'll be flashing this sucka.
Thanks for the heads on good roms.
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.
Hi everybody, with the release of JL2 that supposedly "fixes" the SD card corruption, I have some questions.
Last week when I finally got my phone back (with JH2), I flashed JK4 using Odin (no repartition or PIT), and it worked flawlessly. I have not been having any issues with GPS or any crashing/freezing. I have two questions:
1. If I flash JL2 over JK4, do I need to wipe my data / cache afterwards, or can I leave it to keep all my settings and programs? They're both Froyo roms, so I'm not sure what is safe to do in this situation.
2. What is the difference between JL2 and JK4? I've compared the individual files inside the tar files, and they all seem to have the exact same size, but different dates. See the attached image for reference. Is it possible for the files to actually contain different code that fix the problem, even though the files are the same size? Has anyone noticed a true difference between the two ROMs?
Basically, I'm trying to decide if it's worth the risk to flash a new rom and/or have to go through the trouble of reconfiguring everything, if I may not need to.
Thanks, Mike.
have same question got my phone from repair and they installed JK4 on it... should I update it to JL2?
1. You're probably safe to flash without any wiping. If you do happen to run into any issues though a factory reset would likely take care of it.
2. I can't say for sure what's different, but GPS for me is much better - it locks on much faster and seems to be able to maintain the locks it has. I've also noticed no issues with WiFi so far - I did have an issue with WiFi on JK4 where it would not turn on and throw the occasional error, but I've played on WiFi on and off a few times on JL2 and it's been fine.
I'd say flash it - I was on JK4 but fell back to JH2 due to the bricking problem - even if I had no issues on JK4 and kept with it I'd flash JL2 anyway.
What risks are you talking about that your not already taking with JK4? An update is an update so you should update. I like how you say everything is working flawlessly so I do not want to change it and risk "something happening" 90% of users who have had there phones fail from custom roms and JK4 there phones were working flawlessly. Mine worked flawless for 2 weeks then boom Sd corruption some phones last even longer.
got_milk said:
1. You're probably safe to flash without any wiping. If you do happen to run into any issues though a factory reset would likely take care of it.
2. I can't say for sure what's different, but GPS for me is much better - it locks on much faster and seems to be able to maintain the locks it has. I've also noticed no issues with WiFi so far - I did have an issue with WiFi on JK4 where it would not turn on and throw the occasional error, but I've played on WiFi on and off a few times on JL2 and it's been fine.
I'd say flash it - I was on JK4 but fell back to JH2 due to the bricking problem - even if I had no issues on JK4 and kept with it I'd flash JL2 anyway.
Click to expand...
Click to collapse
I must say, your sig is classic. Hahahah.
The file that supposedly fixes the corrupt internal SD card is the sbl.bin
It's some type of secondary bootloader, and it may be that it needs to be a specific size and reside in a specific location for the hardware to process it during boot.
If that is the case, the fact that the sizes match does not mean the files are identical, and you should definitely update to the newest sbl.bin by flashing jl2.
Also, I love that quote about the '10 types of people' because anyone who understands binary should actually correct it to '1 types of people' In binary 0 is a valid first type of people; and '10' means there would be 3 types.
I guess that makes you the 3rd type...
Sent from my GT-I9000M using XDA App
Hey all. So after 1 month without my phone, I finally got it back from Bell. It's good to have it back!! Before my internal memory died, I was running Docs Rom, and I was actually quite happy with it. Now that the phone is back, it has the stock firmware on it. Im debating if I want to put on Hardcore, or update to the new 2.2 bell and call it a day.
Are we seeing a good reason to use Hardcore's Kernel vs the Stock JL2 Rom?
For those I9000m users who had their phone die, did you mod again, or stay stock?!?
I got mine back with JK4 on it, so I updated it to JL2 right away via Kies. I'm running Hardcore's SpeedMod K12L kernel with the /data lagfix enabled for the last few days without any issue.
Thats exactly what I was planning.
Hope it works out! Thanks for the feedback, makes me feel not so crazy for hopping back into modding after losing my phone for a month!
Whats the worst thing thats gonna happen you get a new phone and $100 credit to your account ? Happy Flashing ;p.
Upgrade to JL2. Apparently fixes the SD card issue, and it's quite fast.
Been running a custom JL2 ROM for a few days and it's great; I'm quite impressed. I was running a custom JPY ROM on a previous phone before it died.
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...