{C}Canada bell galaxy!!WARNING!! FLASING!FAIL REBOOTING!!VOODOO!!STUCK AT S LOGO..ETC - Galaxy S I9000 General

This issue only applies on Canada Bell Galaxy S Vibrant I9000m (not international i9000)
My experience:
installed Voodoo.. one day, my phone wouln't boot up..
Upgrade a lite version of firmware through odin and update.zip
cell phone stuck at S logo forever
I went to the bell store and got a replace one
I didn't learn my leason...
upgrade 2.2 version to my new device
works fine for 3 days and then fail to reboot
bell store sent my device for repair(i waited 10 days)
they said one of the components on the motherboard got replaced.....
SO please aware!!!!!!
First, DO NOT use odin to retore or upgrade your galaxy. This will cuze flashing(when rebooting), rebooting fail, and stuck at S log.
Reason: Since your model is i9000m not i9000, 99%of the firmwares will not support this model(basically you are using a wrong firmware)
Second: do not install OCLF or Voodoo!! if you feel your homesceen lagg!! you can install laungh pro or ADW(i prefer ADW, fast and easy)
Reason:For people who are using the international i9000, it is fine becasue they can restore the device via odin. Since bell i9000m has no compatible firmware!! DO NOT take the risk!!!!! wait untill 2.2 version which is coming at the end of Nov

I agree with you. Bottom line is dont mess around with the Bell Galaxy Vibrant. Just wait until Bell releases 2.2 for it. It's not the same as the regular i9000 where you can flash roms all you want.

This Thread is pointless.. just because you have issues does not mean that all i9000m phones will have the same issue.. I for one have been running 2.2 for a long time now.. and so have many others.. I have flashed my phone over 20 times now.... and the i9000m has the same hardware as the i9000 the only thing that is different is the stock firmware and the radio.. they are made on the same line.

TriC_101 said:
This Thread is pointless.. just because you have issues does not mean that all i9000m phones will have the same issue.. I for one have been running 2.2 for a long time now.. and so have many others.. I have flashed my phone over 20 times now.... and the i9000m has the same hardware as the i9000 the only thing that is different is the stock firmware and the radio.. they are made on the same line.
Click to expand...
Click to collapse
If you read around, you're actually one of the lucky ones. I'm on my 5th Bell SGS and of the failed ones:
A) Zero changed ROMs
B) Two I tried to lagfix
C) Three I tried root
My most recent one has survived a little over a month now... rooted, but I've never touched another rom/lagfix.
If you read the Bell SD issue thread, the worldwide 2.2 is a huge contributor to Bell SGS failures.

I agree i was researching about lag fix. When i look for bricking incidence by voodoo or ryanza, it's usually i9000m for some reason.....
But i say we are lucky ones because we dont face too much lag problem. Phone lags at times which i understand. It's been performing way better than my netbook.
Sent from my GT-I9000M using XDA App

ca7846 said:
I agree i was researching about lag fix. When i look for bricking incidence by voodoo or ryanza, it's usually i9000m for some reason.....
But i say we are lucky ones because we dont face too much lag problem. Phone lags at times which i understand. It's been performing way better than my netbook.
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
The lag problem was not an issue for me running JH2 for about a month. Then the slow attacked, and it was lagging lagging lagging..
So it looks like about once a month I'll have to revert to a Nandroid backup to undo the lag mania.

TriC_101 said:
This Thread is pointless.. just because you have issues does not mean that all i9000m phones will have the same issue.. I for one have been running 2.2 for a long time now.. and so have many others.. I have flashed my phone over 20 times now.... and the i9000m has the same hardware as the i9000 the only thing that is different is the stock firmware and the radio.. they are made on the same line.
Click to expand...
Click to collapse
i know that there are some people, such as yourself, that aren't experiencing any issues, but other people, such as myself, have flashed froyo correctly, and have their phone die within a couple of days as a result. there has to be something else that is different, if the hardware is the same.
if you look at the two threads about sdcard failure, it's 12% for the i9000's and 30.97% for the i9000m's. clearly more than double the failure rate. i think there is definately something that is different between the two. i just wish someone could figure it out so i could safely flash international roms.

wang1chung said:
i know that there are some people, such as yourself, that aren't experiencing any issues, but other people, such as myself, have flashed froyo correctly, and have their phone die within a couple of days as a result. there has to be something else that is different, if the hardware is the same.
if you look at the two threads about sdcard failure, it's 12% for the i9000's and 30.97% for the i9000m's. clearly more than double the failure rate. i think there is definately something that is different between the two. i just wish someone could figure it out so i could safely flash international roms.
Click to expand...
Click to collapse
Spot on. Most threads here with the Bell i9000M are mostly seeking help to fix their bricked phones. And if you read them, the problem usually comes after applying lag fix or flashing a rom, etc. It wont come immediately, but the phone will start to "die" out. It may or may not happen to you, but the probability is quite likely.

I think the difference is.most of the euro 9 000 r 8gb.versions... the 9000m r 16gb versions... diff memory chip.
Sent from my GT-I9000M using Tapatalk

TriC_101 said:
This Thread is pointless.. just because you have issues does not mean that all i9000m phones will have the same issue.. I for one have been running 2.2 for a long time now.. and so have many others.. I have flashed my phone over 20 times now.... and the i9000m has the same hardware as the i9000 the only thing that is different is the stock firmware and the radio.. they are made on the same line.
Click to expand...
Click to collapse
I agree with you. We all know there were some 9000m with internal memory issues that caused some failures and flashing has its risks, no matter what phone you use.
I've flashed my i9000m now about umpteen times, I've run voodoo, oclf, among other things and haven't had any problems. So now I'm using JPK without any lagfix, and its running perfectly now.

wlz1028 said:
This issue only applies on Canada Bell Galaxy S Vibrant I9000m (not international i9000)
My experience:
installed Voodoo.. one day, my phone wouln't boot up..
Upgrade a lite version of firmware through odin and update.zip
cell phone stuck at S logo forever
I went to the bell store and got a replace one
I didn't learn my leason...
upgrade 2.2 version to my new device
works fine for 3 days and then fail to reboot
bell store sent my device for repair(i waited 10 days)
they said one of the components on the motherboard got replaced.....
SO please aware!!!!!!
First, DO NOT use odin to retore or upgrade your galaxy. This will cuze flashing(when rebooting), rebooting fail, and stuck at S log.
Reason: Since your model is i9000m not i9000, 99%of the firmwares will not support this model(basically you are using a wrong firmware)
Second: do not install OCLF or Voodoo!! if you feel your homesceen lagg!! you can install laungh pro or ADW(i prefer ADW, fast and easy)
Reason:For people who are using the international i9000, it is fine becasue they can restore the device via odin. Since bell i9000m has no compatible firmware!! DO NOT take the risk!!!!! wait untill 2.2 version which is coming at the end of Nov
Click to expand...
Click to collapse
Very good morning,
First I want to congratulate you for the support given from this site, second I would like to explain my problem
I have a Galaxy S GT19000 8 gb I have it with my operator Movistar, the problem is that for some reason I upgraded the firmware by mistake and now I get the logo type AT & T and I finally fails PANIC KERNEL, I tried to restore it but Unfortunately in any PC that connects Sea XP, VISTA, WIN7 recognizes me, I wonder if there is any solution to this problem and now I have to admit that only serve to throw.
Greetings and again good work that they are doing.

I don't have any issues with my i9000M.
I've rooted it, flashed 3 times with official firmware from Kies (no registry change) and also applied OCLF. My phone is still up and running! (*knock on wood*)

MaelstromXC said:
I don't have any issues with my i9000M.
I've rooted it, flashed 3 times with official firmware from Kies (no registry change) and also applied OCLF. My phone is still up and running! (*knock on wood*)
Click to expand...
Click to collapse
go flash jpm, and report back after 3 days and a few reboots.
the issue isn't with official bell roms, it's with international ones. if you flash jpm, you have a high chance of your phone bricking (unless you're one of the few lucky ones).

shadoslayer said:
I agree with you. We all know there were some 9000m with internal memory issues that caused some failures and flashing has its risks, no matter what phone you use.
I've flashed my i9000m now about umpteen times, I've run voodoo, oclf, among other things and haven't had any problems. So now I'm using JPK without any lagfix, and its running perfectly now.
Click to expand...
Click to collapse
well, if we are so sure the hardware is the same, the only thing left is the bml's, correct? if that is where the wear leveling is, why don't we extract and compare? i sent mine in, but i do have a backup of bml3 and bml6.

I had Darky's 2.2 ROM on my i9000m for two days before flashing back go JH2+Voodoo. I didnt specifically have any problems with the phone, but the ROM took away my 850MHz band so I reverted.

Hi,
I'm new here and I bought a Bell Galaxy last week. Yesterday, I installed OCLF on it and have no problem yet. Should I uninstall it to make sure?This thread put a doubt about my OCLF installation.
Any advice? If my phone bug, there will be a "factory reset" option for me?
Regards,
Snooze

I have the Bell Vibrant i9000m and have flashed about 5 times. Unlocked and running on Rogers. I've only had one problem and that was the phone restarting during a flash, went into download mode and restored to stock 2.1 via Odin3 1.3.

I have the GT-I9000M and never encountered a problem of flashing different firmwares, until I tried flashing voodoo. I believe the problem lies in the original F/W Kernal's not recognizing the partition of the internal SD since the Partition are in a different format. Creating a SD Card Failure when putting an original F/W without disabling voodoo first. Since it cannot mount the partition it cannot copy over files over to install a different F/W. I just wish there was a small Flash Kernal that would simple wipe the SDCard, partition and format to the original format for convenience sake of all these troubled i9000 users. I've just encountered this and is the only time I've ever encountered a problem with SDcard failures. I've flash numerous F/W without any problems. I've gone 2.1 to 2.2 back to 2.1 (UG8/JH2/JM8&Voodoo/JPA/JPK/JPM). From losing my 850 band just to get it back with the right procedure. All I can say RFS may not be the best file system but its the one I'll probably stick with when I get my phone back. Besides 2.2 was never that bad without a lag fix anyways just wanted to try something new. Also just in reference it has also shown in polls that it didn't matter whether you were on 2.1 with or without lagfix or 2.2 with/without lagfix either that the Sd Card could also fail. For now I'm just sharing my experience

Woolios said:
I have the GT-I9000M and never encountered a problem of flashing different firmwares, until I tried flashing voodoo. I believe the problem lies in the original F/W Kernal's not recognizing the partition of the internal SD since the Partition are in a different format. Creating a SD Card Failure when putting an original F/W without disabling voodoo first. Since it cannot mount the partition it cannot copy over files over to install a different F/W. I just wish there was a small Flash Kernal that would simple wipe the SDCard, partition and format to the original format for convenience sake of all these troubled i9000 users. I've just encountered this and is the only time I've ever encountered a problem with SDcard failures. I've flash numerous F/W without any problems. I've gone 2.1 to 2.2 back to 2.1 (UG8/JH2/JM8&Voodoo/JPA/JPK/JPM). From losing my 850 band just to get it back with the right procedure. All I can say RFS may not be the best file system but its the one I'll probably stick with when I get my phone back. Besides 2.2 was never that bad without a lag fix anyways just wanted to try something new. Also just in reference it has also shown in polls that it didn't matter whether you were on 2.1 with or without lagfix or 2.2 with/without lagfix either that the Sd Card could also fail. For now I'm just sharing my experience
Click to expand...
Click to collapse
totally agree...http://forum.xda-developers.com/showthread.php?t=793404...look at the number it doesnt matter if it is 2.1 2.2 or no lagfix....the amount of sd card failures are the same...it isnt the rom its just ur phone...numbers dont lie

TriC_101 said:
This Thread is pointless.. just because you have issues does not mean that all i9000m phones will have the same issue.. I for one have been running 2.2 for a long time now.. and so have many others.. I have flashed my phone over 20 times now.... and the i9000m has the same hardware as the i9000 the only thing that is different is the stock firmware and the radio.. they are made on the same line.
Click to expand...
Click to collapse
Exactly what I was thinking.

Related

Here it is again folks! Htc hd official upgrade

I am not sure what is up them but here is the official release again.
Get it while it is hot!
http://forums.t-mobile.com/t5/HTC-H...ate-Now-Available-on-T-Mobile-com/td-p/380116
Did you try this? better than the original one they put out? I'm wondering why it's the same version number. Seems like a good way to confuse people.
Supposedly there were issues with downloading the originial release, so they had to correct that. But, the version they put up is the same one as before.
I've got all 3 "versions" of the new ROM now (leaked, first official issue, and this new one now too) and they're all the same.
Confusing? Yes. Big deal? Not really
so basically this isn't going to fix any issues? you downloaded it and it's the same everything? Why would they bother?
crisisinthecity said:
so basically this isn't going to fix any issues? you downloaded it and it's the same everything? Why would they bother?
Click to expand...
Click to collapse
Well yes it's the same as the first release of the 2.13 ROM if that's what you mean. I think they just put it back up because there's people who didn't get it before they had to pull it temporarily for the downloading issues. I assume it'll stay available there from now on.
crisisinthecity said:
Did you try this? better than the original one they put out? I'm wondering why it's the same version number. Seems like a good way to confuse people.
Click to expand...
Click to collapse
I used the First release and still have it on my computer at home. I downloaded the leaked version and it was a godsend. I hear when they made it official on the 18th it caused people a lot of problem even bricking. according to the link they where having server issues and that is why they had to pull the official release but I guessed they fixed the issues now. It is the same ROM version as the one I have so your guess is as good as mine. I think sirphunkee has them all downloaded but has not implemented them and is still running 2.10xxx
toreone said:
I used the First release and still have it on my computer at home. I downloaded the leaked version and it was a godsend. I hear when they made it official on the 18th it caused people a lot of problem even bricking. according to the link they where having server issues and that is why they had to pull the official release but I guessed they fixed the issues now. It is the same ROM version as the one I have so your guess is as good as mine. I think sirphunkee has them all downloaded but has not implemented them and is still running 2.10xxx
Click to expand...
Click to collapse
Correct, and I should have made that clear...still on 2.10, haven't flashed any of the upgrade downloads.
Somewhere in one of the threads in this section about the upgrade, the leaked version and the first "official" releases were compared and found to match bit-for-bit. Also, T-Mobile forums had confirmation that the recent re-release is identical to the one they put up before the download issues. So, by the commutative property of Windows Mobile Mathematics (WMM), they're all the same
However, that's not to say that the end experience from those who have flashed any of the three doesn't vary greatly. Some report a near-magical cleansing of demons, others are suddenly needing an exorcism...and this is across all three "releases" of this ROM.
sirphunkee said:
Correct, and I should have made that clear...still on 2.10, haven't flashed any of the upgrade downloads.
Somewhere in one of the threads in this section about the upgrade, the leaked version and the first "official" releases were compared and found to match bit-for-bit. Also, T-Mobile forums had confirmation that the recent re-release is identical to the one they put up before the download issues. So, by the commutative property of Windows Mobile Mathematics (WMM), they're all the same
However, that's not to say that the end experience from those who have flashed any of the three doesn't vary greatly. Some report a near-magical cleansing of demons, others are suddenly needing an exorcism...and this is across all three "releases" of this ROM.
Click to expand...
Click to collapse
I forget where I read...but a lot of people where having issue when the flashed to a custom rom then flashed to the upgraded tmobile rom with out returning their phones back to stock. I guess that was a major issue. Or people had to factory reset then run the upgrade I didn't do either of those things when I flashed and it worked great. I mean I didnt have CHT or Editor on but I did have a bunch of apps.
I bought my HD2 last week and the rom it came with from the factory is 2.13.531.1. I have had the phone freeze on me 2 or 3 times in the week I have owned it. Even though the rom that was just released is the same version would it still be a good idea to flash it? I am coming from a G1 and on occasion have flashed a rom and the phone ran like crap. Then upon re flashing the same exact rom the phone ran like normal.
I upgraded last evening, despite my initial trepidation.
Everything seems smooth now--a lot of the hiccups when texting seem to be gone (out of order texts, highlighting of last text sent and lag when trying to write a text that is part of a longer thread).
Swype is working a 100x better.
So far, so good.
ReganH22 said:
I bought my HD2 last week and the rom it came with from the factory is 2.13.531.1. I have had the phone freeze on me 2 or 3 times in the week I have owned it. Even though the rom that was just released is the same version would it still be a good idea to flash it? I am coming from a G1 and on occasion have flashed a rom and the phone ran like crap. Then upon re flashing the same exact rom the phone ran like normal.
Click to expand...
Click to collapse
That happens with winmo as well as android....after flashing a ROM, sometimes either a re-flash, or an immediate hard-reset is needed to get it to "stick". In fact, most chefs recommend doing a hard-reset right after a new flash, just to be safe, and I've seen numberous times where a buggy install is fixed perfectly just by doing that. So, if you're fine with the effort involved, I would certainly suggest it...it certainly can't hurt
Cool. Thanks for the info sirphunkee.
Software Upgrade or ROM
I downloaded the update from T-Mobile and have it running on my HD2. Was this an update to my ROM, so a hard reset will reload this update? I talked with a T-Mobile rep on the phone who said a hard reset would remove the update and I would have to re-install it.
jwperez1 said:
I downloaded the update from T-Mobile and have it running on my HD2. Was this an update to my ROM, so a hard reset will reload this update? I talked with a T-Mobile rep on the phone who said a hard reset would remove the update and I would have to re-install it.
Click to expand...
Click to collapse
Good thing you asked here to be sure
No, a hard-reset will only "reload" whatever the currently flashed ROM is...whether it's an official update or a custom ROM.

Optus Australia & Samsung Galaxy S

Hi peeps, I just wanted to tell you about my experience with this phone and with Optus.
I purchased a Samsung Galaxy S from them earlier in September. The 3 button recovery method never worked on the phone Eventually I did brick it, when a lag fix failed to complete un-installing when moving files (RyanZAEXT2LagFix BETA 2-3).
The phone wouldn't boot, it kept re-booting repeatedly on the first Samsung Galaxy S screen. Anyway I took it in 1 day before the 2 week swap over period expired, lucky me no waiting for repairs!
Anyway the 3 button recovery method works on the new phone The manufacturing date on the battery on the new phone is 8/10 on the non functioning one it was 7/10. I'd recommend anyone purchasing this phone to check that the 3 button rec mode is working before walking out of the store. I have a feeling it just isn't Optus, but is probably a bad batch? :| Interested to know of others experiences.
I dont think anyone really knows why 3BR doesn't work on some handsets. Anyways, I got mine on Aug 6 through Virgin (delivered by Optius). 3BR mode is working, and no GPS issues
I got mine from optus just when it has been released and I have no issue witht he recovery ... so nothing to do with optus phone
G'day,
I got mine from Optus about a month ago. No 3BR mode at all. I have since ventured into flashing on Android (having owned a Touch HD for nearly two years and flashing Energy's ROM's once a week) and doing the regedit to flash the JH2 ROM, then Odin to get back to JG4.
Since doing this, 3BR has worked without a problem. I don't care how it has been fixed, because I just wanted to make sure I could flash to Froyo when it is released.
Hopefully Optus will come up with the goods soon!!!
I bought mine outright from Allphones, but it's Optus branded. 3 button recovery works perfectly.
This is definitely not limited to Optus phones. There are plenty of international members who have the same issue. Have a look around on this forum and you'll see.
When i got mine 3br was working then i briked and flash using oding for optus firmware 3br wasnt working then I reflash using kies now 3BR started working again.
Sent from my GT-I9000 using XDA App
I bought mine the day of release with Optus. Battery Date 2010.06.12. It's always worked fine with 3 button recovery. It came with JF1 Optus firmware and I've flashed it with JF3, JF4 (Optus), JG5, JM2, JP3, JM6, JPC, JPH (current). JM6 and JPH have been great for the GPS and Compass. The others were all a bit average for the GPS and outright shocking for the compass.
I got my sgs on july and 3 button always work
got mine
I got my phone on the 2/8/2010 through telechoice on virgin but it had optus firmware on it and the 3 button recovery worked.
Got mine in mid August from Allphones on an Optus plan.
No 3 button recovery.
Rooted using TA Gunnman 1 click root (PC USB way) and lag fixed with RyanZA OCLF.
Do scared to try anything else without 3 button working
Edit: Is it safe to use Richthofen's 3 button ZIP/update fix on my Optus SGS? http://forum.xda-developers.com/showthread.php?t=785201
Edit: Nevermind,Ive read up on it,tested and confirmed by other Optus users as working so I tried it and it worked.
Now Ive also got 3 button recovery..What a load off...
=Oberon= said:
Edit: Nevermind,Ive read up on it,tested and confirmed by other Optus users as working so I tried it and it worked.
Now Ive also got 3 button recovery..What a load off...
Click to expand...
Click to collapse
I have also seen it worked for Virgin users too - however, this link seems to have disappeared - what's the latest method to fix the 3 button recovery/download modes?
Cheers,
Xav.
My optus phone has the date 23/07/2010 and when I got it, it was on 2.1 and it didn't have 3br but after I flashed new bootloaders it has worked since. Now on gingerbread with JVP modem and I couldn't imagine being back on 2.1 or 2.2
I've had mine for about 12 months now, and it had 3 button from start (which has come in handy) Was on 2.1 when I got it, hung out for 2.2... and getting itchy feet for 2.3... though I may just end up jumping ship and ROMing it...
Had so many problems with it when it was running on RFS - constant FC's and shut downs and all sorts of problems like that (I was even missing calls because it was taking so long to think about bringing up the answer buttons). Rooted, lagfixed and I'm actually happy with the device... though still want 2.3.4... Come on Optus/Samsung... how long does it take to "test"... the only thing they are testing is our patience!! *RANT ENDED*
Digi79 said:
I've had mine for about 12 months now, and it had 3 button from start (which has come in handy) Was on 2.1 when I got it, hung out for 2.2... and getting itchy feet for 2.3... though I may just end up jumping ship and ROMing it...
Had so many problems with it when it was running on RFS - constant FC's and shut downs and all sorts of problems like that (I was even missing calls because it was taking so long to think about bringing up the answer buttons). Rooted, lagfixed and I'm actually happy with the device... though still want 2.3.4... Come on Optus/Samsung... how long does it take to "test"... the only thing they are testing is our patience!! *RANT ENDED*
Click to expand...
Click to collapse
You're still on 2.2? At least flash 2.2.1 you won't be disappointed.
MrIwik said:
My optus phone has the date 23/07/2010 and when I got it, it was on 2.1 and it didn't have 3br but after I flashed new bootloaders it has worked since. Now on gingerbread with JVP modem and I couldn't imagine being back on 2.1 or 2.2
Click to expand...
Click to collapse
I got 2.1 when I first got the phone, then updated to 2.2 via Kies. Which ROM gave you the fixed bootloaders? Which method did you use?
Xav.
xavieda said:
I got 2.1 when I first got the phone, then updated to 2.2 via Kies. Which ROM gave you the fixed bootloaders? Which method did you use?
Xav.
Click to expand...
Click to collapse
I think it was 2.2.1 (JPU?) was already on 2.2 via kies, I'm pretty sure this was the method I used- http://forum.xda-developers.com/showthread.php?t=821698
MrIwik said:
I think it was 2.2.1 (JPU?) was already on 2.2 via kies, I'm pretty sure this was the method I used- http://forum.xda-developers.com/showthread.php?t=821698
Click to expand...
Click to collapse
Right, thanks. I have read through that thread a bit before. Thing is, you need to get root first to confirm whether or not the phone can actually be successfully flashed using that method - I know there's SuperOneClickRoot or something but I also read that can stuff the phone too.
Or did you just take a deep breath and load up a 2.2.1 ROM?
Regards,
Xav.

Bell galaxy s data fix

hey guys i recently flashed my phone to froyo 2.2 and lost data connection, however my problem was not that i didnt have the reqquired band but my apn settings were reset. so if u flashed ur phone and lost data check ur apn settings first ... it should look like this
APN: pda.bell.ca
Proxy server: web.wireless.bell.ca
Port: 80
after i entered the info my data started working again
hope this helps...
did flash to official jpm via hacked kies? how's everything so far?
That may work but it's not the default settings. APN should be inet.bell.ca, not sure about the rest.
get ready for it to get bricked in the next couple of days
ya i flashed via kies, everything works well, feels alot snappier without lagfix..also the samsung task manager seems to work better as it kills programs that arnt running alot faster.
bimmerboii said:
get ready for it to get bricked in the next couple of days
Click to expand...
Click to collapse
i'm going to have to agree with this guy......a few days, and a few reboots, and you'll be bricked.
The apn settings should be like this:
name: Bell
APN: inet.bell.ca
rest , leave them empty and save and use. tried and tested.
Ya. I am alo on be and confirm its inet.bell
I retured a phone i updated to 2.2 cuz was verry unstable and keeps fc on multitasking.
Also when i flashed back to the stoxk bell jh2 i could not get the bell branding csc file to restore all the programs correctly. So i just gave up and doa the phone with new one
Good luck. And btw now that you have updated you will not get the update id any that bell givea the rest of us.
Sent from my GT-I9000M using XDA App
wang1chung said:
i'm going to have to agree with this guy......a few days, and a few reboots, and you'll be bricked.
Click to expand...
Click to collapse
Why would it be bricked? I just updated mine yesterday to froyo on bell.
i too am on bell, and have tried updating to jpk and jpm. it never turns out well, and if you start getting FC's and "can't mount" errors in recovery, i suggest you flash back to jh2 before your sdcard gets corrupted to the point where you can't flash it.
i'm just saying a lot of people were having this issue with the bell i9000m when flashing to froyo.
bassboy_pete said:
Why would it be bricked? I just updated mine yesterday to froyo on bell.
Click to expand...
Click to collapse
prepare yours to be bricked as well lol
wang1chung said:
i too am on bell, and have tried updating to jpk and jpm. it never turns out well, and if you start getting FC's and "can't mount" errors in recovery, i suggest you flash back to jh2 before your sdcard gets corrupted to the point where you can't flash it.
i'm just saying a lot of people were having this issue with the bell i9000m when flashing to froyo.
Click to expand...
Click to collapse
Spot on.. (based on observation and some other threads) most Bell i9000M get corrupted a few days after flashing i9000 roms. Once it gets corrupted you will have to send the phone for repairs.
Just wait for Bell's official 2.2...it wont be long
Out of the 3 SGS's I have , only one had a problem with the SD Card. All 3 were on JPK and are now on JPM. The only one that had this problem had a lagfix installed. The other 2 don't and are still alive since JPK was put on them on the day of it's release. JPM was put on all 3 of them last night. I only have the 850Mhz problem with the 3 of them. The SDCard problem is not related to Froyo as others have had it happen with 2.1 . The phone I had fixed got a brand new system board installed in it but the rest of the phone was my old one since I had marked both with a marker.
I noticed people were commenting on which APN is correct (inet.bell.ca or pda.bell.ca).
As shipped, the phones came set with inet.bell.ca as the APN. This is actually their APN for tethered connections. While it works fine for data, people on older plans without a tethering option were getting charged fees for tethering because of this.
pda.bell.ca is what all other phones use for on-device data, which is why most people suggest using that one. Both will work on the SGS.
ya i just noticed my phone getting alot of force closes, then when i rebooted it got stuck on the galaxy s screen. went into download mode and flashed back to jh2 with odin, phone works fine now...and as for not being able to update through kies, im not too worried about that as odin makes it easy to flash new firmwares...and i have a feeling bell is gonna slack on rolling out 2.2 anyways. and most of us that root out phones do not have much interest goin with stock roms anyways
bimmerboii said:
Spot on.. (based on observation and some other threads) most Bell i9000M get corrupted a few days after flashing i9000 roms.
Click to expand...
Click to collapse
labellee25 said:
The SDCard problem is not related to Froyo as others have had it happen with 2.1
Click to expand...
Click to collapse
Doesnt have to be 2.2... Happens as long as it's the i9000 rom
Weird, I have a bell i9000M (got it in august). Ive flashed to froyo using the kies registry hack and its been running flawlessly, havent experienced any force closes or lag
bimmerboii said:
get ready for it to get bricked in the next couple of days
Click to expand...
Click to collapse
This is not true have you looked at the SD thread?? look at the votes. http://forum.xda-developers.com/showthread.php?t=793404&page=32 its about 50% failed with 2.1 and 50% with 2.2
TriC_101 said:
This is not true have you looked at the SD thread?? look at the votes. http://forum.xda-developers.com/showthread.php?t=793404&page=32 its about 50% failed with 2.1 and 50% with 2.2
Click to expand...
Click to collapse
Did you even read this thread? OP already said his phone was starting to act up already and flashed it back.
And if you read my previous posts, i didnt limit the failure to 2.2 alone.

Samsung Galaxy S gets Froyo update in India.

Samsung Galaxy S gets Froyo update in India.
http://www.indian-tech-news.com/samsung-galaxy-s-gets-froyo-update-in-india/4211/
Just updated my phone to Froyo.
After updating, phone running slow as compare to previous version.Have you experience this, please let me know.
napster_doom said:
Samsung Galaxy S gets Froyo update in India.
http://www.indian-tech-news.com/samsung-galaxy-s-gets-froyo-update-in-india/4211/
Just updated my phone to Froyo.
After updating, phone running slow as compare to previous version.Have you experience this, please let me know.
Click to expand...
Click to collapse
Do you use lagfix before updated to Froyo?
Yes, untouched froyo feels more laggy than eclair, but the custom froyo ROMs is really fast like the Doc's ROM or Tayutama ROM or Cognition ROM (Captivate) or ...etc
I recommend to update the kernel to the one with lagfix (ext4 or jfs), but I don't know which one is the best since I'm using the Samsung Captivate (AT&T version of Galaxy S, and the kernels are not excangeable between Captivate and i9000 Galaxy S)
Or, you also can use the custom froyo ROMs like I mentioned above..
No I did not use any Lag fix or such kind of software.
Also I am experiencing a bug in Samsung Kies, When I update my phone to latest software and again if I connect phone to Kies, it again gives me a notification of phone update to the latest firmware again and again.
Anyways, thanks for your suggestion.
I have laso updated it yesterday, it is quiet laggy than 2.1, I laso applied lagfix, but it is not as responsive as 2.1, seems like it is related to JIT compiler which is not optimized for hummingbird. Waiting for cyanogenmod
Hey guys....what's the rom version number?
Long update process
Did it take long for you people after the froyo upgrade for phone to reboot. Its already been 10 mins and I see blank screen, though button lights are on and phone vibrates after few minutes.
thanks
Hey guys.. Updated my sgs to froyo yest.. As u guys mentioned the phone is quite laggy compared to eclair.. But after restarting it for like 10 times nd after using it for sometime, there was a considerable decrease in the lag.. But even so it's not as responsive as eclair.. Hope samsung fixes this soon in the next update..
charlie_55555 said:
Did it take long for you people after the froyo upgrade for phone to reboot. Its already been 10 mins and I see blank screen, though button lights are on and phone vibrates after few minutes.
thanks
Click to expand...
Click to collapse
were you on a custom ROM with lagfix before? that may be a problem. if so, reflash to DDJG4 using odin and then retry kies update.
i Have upgrade my galaxy s to Uk Froyo with Registry edit in kies befor
now the official Froyo in india has been released
How to upgrade now to orignal indian rom
Kies says....This device's verson cannot be upgraded
pls help
Solution to lag for Froyo
1) Do Factory Reset before and after upgrade.
2) Wipe Cache Partition.
This will boost Froyo Experience for sure...
deepforest said:
i Have upgrade my galaxy s to Uk Froyo with Registry edit in kies befor
now the official Froyo in india has been released
How to upgrade now to orignal indian rom
Kies says....This device's verson cannot be upgraded
pls help
Click to expand...
Click to collapse
Use, Kies Registry Patcher to fool Kies.... Look for Galaxy S India Thread in here ...
Or Search for Kies Registry Patcher ...you will find it...
from there, you can hack Kies to detect your org. firmware.... ;-)
Help
Virtualsk said:
1) Do Factory Reset before and after upgrade.
2) Wipe Cache Partition.
This will boost Froyo Experience for sure...
Click to expand...
Click to collapse
Hi
@ Virtualsk
Can you tell me how to do:
1) Factory Reset
2) Wipe Cache Partition
And if i do this will i also data from my internal SD card the 8GB or 16GB?
-Sunil
sunilgogo said:
Hi
@ Virtualsk
Can you tell me how to do:
1) Factory Reset
2) Wipe Cache Partition
And if i do this will i also data from my internal SD card the 8GB or 16GB?
-Sunil
Click to expand...
Click to collapse
Go into Recovery mode...i.e., Press Volum Up + Home Button + power button to gather....
There you will find both options...
No, it will not remove data of your SD Card...However, you can back up that data using Kies...since, It will remove Contacts for sure.
Help
Virtualsk said:
Go into Recovery mode...i.e., Press Volum Up + Home Button + power button to gather....
There you will find both options...
No, it will not remove data of your SD Card...However, you can back up that data using Kies...since, It will remove Contacts for sure.
Click to expand...
Click to collapse
Thanks Virtualsk
I did take a backup of all things important for me.
Have you updated to official Froyo for your Samsung Galaxy S Gt i9000 and what are you views on a personal level? (This is assuming you have Samsung Galaxy S Gt i9000 )
Here is the video for somebody like me, who does not know the 101 of RestoreMode Good Video by TechSaviSolution on You Tube.
sunilgogo said:
Thanks Virtualsk
I did take a backup of all things important for me.
Have you updated to official Froyo for your Samsung Galaxy S Gt i9000 and what are you views on a personal level? (This is assuming you have Samsung Galaxy S Gt i9000 )
Here is the video for somebody like me, who does not know the 101 of RestoreMode Good Video by TechSaviSolution on You Tube.
Click to expand...
Click to collapse
I installed Europe JP6 first ....
Later on I installed Asian JPD
and Now i am on Indian JP6.
Personally, there is a lot of performance improvement done in Froyo. I dont see lag that much....However, i always prefer Factory Reset before and After Update.
Frankly, You should get the speed after following the steps.
Help
Virtualsk said:
I installed Europe JP6 first ....
Later on I installed Asian JPD
and Now i am on Indian JP6.
Personally, there is a lot of performance improvement done in Froyo. I dont see lag that much....However, i always prefer Factory Reset before and After Update.
Frankly, You should get the speed after following the steps.
Click to expand...
Click to collapse
Thanks for your response, i will try and update my phone, and will post my results.
Hi,
Me too using the asian JPD version but have an impression that its great after upgrade and reset but after use for some time it becomes less responsive and laggy.. Anyways since you switched from JPD to JP6, how is the performance for JP6? Better/same/crappy? as even I am thinking of the same.
Mr.Hunk said:
Hi,
Me too using the asian JPD version but have an impression that its great after upgrade and reset but after use for some time it becomes less responsive and laggy.. Anyways since you switched from JPD to JP6, how is the performance for JP6? Better/same/crappy? as even I am thinking of the same.
Click to expand...
Click to collapse
Well, from my point of view, its similar to JPD. However, you will notice some lag in some apps only. thats due to FAT32 filesystem being used by Samsung instead of EXT2.
Virtualsk said:
... thats due to FAT32 filesystem being used by Samsung instead of EXT2.
Click to expand...
Click to collapse
Samsung uses RFS filesystem.
kiriapurv said:
Samsung uses RFS filesystem.
Click to expand...
Click to collapse
Yes, Which is build as Lagacy FAT ... ;-)

[australia] android-v2.3.3 (optus)

anyone with an australian handset had much luck installing android v2.3.3 on their device without the help of a 3rd party rom like darkys or ultibread?
ive managed to install (original-xxjvk) functioning on samsung galaxy s with only a custom kernel if anyone is interested in a howto. ive only had my galaxy for a few weeks and have only managed to get it running myself without forced closes etc.
i dunno if anyone is having the same amount of trouble as i am trying to hook into android v2.3.3 but i think ive mastered it for aussies lookin to use the latest android on australian networks no hassles. i just didn't want to post a howto for something everyone has already worked out lookin like a fool. heh.
any replies appreciated.
I've been running stock JVK for about a month now, and Stock JVB since Saturday, Virginmobile (phone from Optus). No issues here.
Stock jvk with fugu mod, rooted and voodoo 7 sound with camera mods. I turned Hspda off today and since 7am till now 5pm still have 78%(and I use it fairly heavy). Runs well only thing I want next is android lockscreen and I'm happy.
On Virgin.
Sent from my GT-I9000 using Tapatalk
It took me a good 7 hours, haha all night trying to get GB on mah phone... had all sorts of problems as well.
Eventually, I installed I9000XWJVH, and it seems to be going good.
^^^
Just in time to flash 2.3.4 this evening
Downloading it right now.
Just worried about me having a non-stock kernel... using CWM (I think) with CWM Recovery... (CF-Root-XW_NEE_JVH-v3.2-CWM3RFS)
Are you flashing with Odin?
It wouldn't be a bad idea to flash the stock firmware first to get the updated bootloaders.
Yeah, I am using Odin.
flash stock jvh again?
Nope...
If you have your filesystem converted to ext4, just convert back to rfs.
If you really want to be sure of a clean flash, flash a 3 file firmware with a 512 pit and re-partition.
ok, well, I have no idea if I have ext4 or not... I don't remember ever seeing or doing anything with that, so, I am assuming I am still on rfs.
I have 3 files and a pit for the JVP. Do I just use those and flash with odin + repartition and that's it?
Don't need to do anything before?
I had stock JVK running for quite a while with no problems but with all the tasty looking ROMs out there I gave up and went for Simply Honey. First was using Darkys which was nice but SH wins me over with its lush blue-look =)
Now running JVO with no issues. Can get 6-8hrs heavy usage out of my phone =)
I know this sounds really blonde, but...
I'm trying to find a way to upgrade my Android OS to 2.3 (from 2.1) - however my phone is locked to Telstra and I'm finding it difficult (with my limited knowledge of Android) to upgrade.
Can someone please help me out? I'd be so grateful!
I found the best Guide to be: [GUIDE] Flash/Install/Update to Gingerbread 2.3.4 to I9000: Detailed guide for n00bs
It isn't too difficult but do read, re-read & go through the steps a few times before committing any changes.
Be prepared though... This flashing thing can get quite addictive as there seems like there is always another ROM that does just a little more than your current ROM & often just a little faster.
Good luck.
Oh - To keep all the grumpy forum members happy, do a quick search before asking a question such as this. You are not the first to ask this and there are many threads that have covered possible answers.
Just Updated to 2.3.3 Unbranded from Darky's Rom.
Had to Downgrade to 2.2 then to 2.3.3 as Odin just kept Failing.

Categories

Resources