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.
Related
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.
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.
In about phone, my base band is S700.0.5S.DK17
Why?
I have installed 2 DK28 ROMs without issue as well...
Well now im getting reboots on texts.
any ideas?
bdf said:
In about phone, my base band is S700.0.5S.DK17
Why?
I have installed 2 DK28 ROMs without issue as well...
Well now im getting reboots on texts.
any ideas?
Click to expand...
Click to collapse
Because the modem flash failed, even though it said it didn't. Flash the DK28 modem using Odin again.
I have 3 times now, what am I doing wrong?
bdf said:
I have 3 times now, what am I doing wrong?
Click to expand...
Click to collapse
Redownload the modem. From different sources.
Sent from my Venomous Viper of an Epic in the Mile High City
I tried that, as well as the other options if it failed (which it never does).
Still DK17.
WTF
Try using going to DI18 with Odin, then using Firon's flashable dk28 to update. This is the original thread.
Try posting in the right section. Thanks
Sorry, I assumed this would be a dev issue.
In any case, nothing seems to work. I tried the above, when I took it back to stock configuration it still said DK17, and still does.
Everything seems to work OK, GPS, 4g, 3g phone data, everything.
What would this be affecting and are there any other things I can to to solve this?
Thanks,
BD
This happened with me as well. And this isn't my first time flashing a modem so i know I did it right. I've ran several dk28 roms already and everything works perfectly including gps. Im leaving it as it is.
Sent from my SPH-D700 using XDA App
Well I have tried everything I can think of, nothing changes it up or down.
I guess since everything works, Ill leave it alone.
BD
Iam having the same problem has anyone figured out why our baseband won't change I have flashed over and over and my baseband is stuck on dk17. Thanks
Sorry if this isn't the right place to post this but I figured I'd post this experience I had trying to upgrade the firmware on my Sprint Galaxy tab so that other might benefit.
Here goes; I got a brand new galaxy tab with the dj30 firmware on it. I rooted it and did the wifi supplicants trip to get adhoc networks going. Nothing too strange. Then the system tried to auto updated itself to ea24 which I let it. But after I checked it it seems that the upgrade couldn't get through. This process would repeat itself on a regular basis.
I didn't think much about it until I heard that netflix could be played on certain android devices and I of course wanted to play it on my tab. I side loaded it, changed the system props and saw that it still couldn't play. My first attempt to load a custom rom(the ginger for gsm failed, yes I know they're incompatible)which bricked the phone. What then followed was an orgy of flashing anything vaguely related to the tab to get it to at least power on. The only thing that would work was the dj30 base image.
Now I'm back to square one except that my navigation system no longer works so I flash modem.bin from ea24 which fixed the gps. My tab tried to auto update itself to ea24 like it usually tries to do but this time SUCCESS!. Then two more ota updates came after that and worked just as well.
I think flashing the modem might have been what got the upgrade process going.
Sorry if this is a little long I just figured it might be useful to anyone in the same situation.
Can you Pls point me in the direction to get thus modem? I too am having this problem. [email protected]. Pls email it to me if you have. THANKS
Sent from my PC36100 using XDA App
trapstarr56 said:
Can you Pls point me in the direction to get thus modem? I too am having this problem. [email protected]. Pls email it to me if you have. THANKS
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Search
Sent from my ADR6300 using Tapatalk
Hey Cruton. Seems you and I are in the same position. I'm also stuck on DJ30. Managed to upgrade to rooted gingerbread, but market and browser fc no matter what I try. Your suggestion is something I haven't tried yet. Could you elaborate a bit more? I tried flashing modem.bin (from the EA24 updater) but it freezes up. Do I load it under "phone" in odin? Also, which version were you using?
Cruton. Thank you so much for going through the effort of posting your experience. You have saved my tab. I didn't know what to do anymore. Your trick worked, received all updates OTA and then I received gingerbread OTA. Everything stable and running after two weeks of trying absolutely everything (as I was in EXACTLY the same position as you, so you know how frustrating it is). I wish I could buy you a beer man. Thanks again.
Viparo said:
Cruton. Thank you so much for going through the effort of posting your experience. You have saved my tab. I didn't know what to do anymore. Your trick worked, received all updates OTA and then I received gingerbread OTA. Everything stable and running after two weeks of trying absolutely everything (as I was in EXACTLY the same position as you, so you know how frustrating it is). I wish I could buy you a beer man. Thanks again.
Click to expand...
Click to collapse
I'm just glad to return a little to this community
Viparo said:
Hey Cruton. Seems you and I are in the same position. I'm also stuck on DJ30. Managed to upgrade to rooted gingerbread, but market and browser fc no matter what I try. Your suggestion is something I haven't tried yet. Could you elaborate a bit more? I tried flashing modem.bin (from the EA24 updater) but it freezes up. Do I load it under "phone" in odin? Also, which version were you using?
Click to expand...
Click to collapse
I haven't had trouble with the market or the browser. I believe it was version 1.7 of Odin and I put modem.bin into the Phone section. Interestingly I had to repeat this entire process when the gingerbread update was out. I had to try 3 times with flashing modem.bin because it kept freezing up but it went through eventually. Good luck.
I have a Samsung Fascinate from Verizon Wireless.
Up until two days ago, it used to work perfectly on Android Froyo Superclean 2.8.
I had that ROM for about a year and a half and never thought of updating my OS up until two days ago.
At first, I discovered that I could get Gingerbread for my phone (not a stock version though).
I looked on the internet and I ended up flashing C-Spire Wireless Gingerbread 2.3.6 by accident.
When I finally finished all of the updating on that, I tried to go on the internet but it was not functioning the way it used to.
Most of the time, my phone could not connect to the 3G network, and when it did, it was very slow and disconnected every minute or so.
So, I then flashed the stock version of Gingerbread 2.3.5 for Verizon, but when I finished doing that, I still found that my internet was extremely buggy.
I also tried to install some radios on my phone to see if that helped, but it did not.
Shortly after, I stalled Superclean3 milestone 2 but the internet issue was not solved.
After that, I installed TSM Resurrection 2.2. The internet problems were still there.
Then, I went and installed ICS. Internet was still buggy.
I then got Jelly Bean from Cyanomod. The internet was still the same.
Then I went back to the stock Gingerbread 2.3.5. My internet is still really annoyingly horrible and I don't know what to do.
Any solutions please?
yoyohan77 said:
I have a Samsung Fascinate from Verizon Wireless.
Up until two days ago, it used to work perfectly on Android Froyo Superclean 2.8.
I had that ROM for about a year and a half and never thought of updating my OS up until two days ago.
At first, I discovered that I could get Gingerbread for my phone (not a stock version though).
I looked on the internet and I ended up flashing C-Spire Wireless Gingerbread 2.3.6 by accident.
When I finally finished all of the updating on that, I tried to go on the internet but it was not functioning the way it used to.
Most of the time, my phone could not connect to the 3G network, and when it did, it was very slow and disconnected every minute or so.
So, I then flashed the stock version of Gingerbread 2.3.5 for Verizon, but when I finished doing that, I still found that my internet was extremely buggy.
I also tried to install some radios on my phone to see if that helped, but it did not.
Shortly after, I stalled Superclean3 milestone 2 but the internet issue was not solved.
After that, I installed TSM Resurrection 2.2. The internet problems were still there.
Then, I went and installed ICS. Internet was still buggy.
I then got Jelly Bean from Cyanomod. The internet was still the same.
Then I went back to the stock Gingerbread 2.3.5. My internet is still really annoyingly horrible and I don't know what to do.
Any solutions please?
Click to expand...
Click to collapse
Only thing I can think of is follow droid styles guide in the forums
http://forum.xda-developers.com/showthread.php?t=1238070
Sent from my SCH-I500 using xda premium
To go back to stock you need to flash the the pit file to repatriation and put everything back in order. Found the forum in fascinate android development about going back to stock Verizon rom. I had a 3g issue when I first flashed AOKP b40. Going back to stock worked perfect to fix data. Then back to ics on AOKP. And if your gonna flash an ics rom make sure you flash THS build 2 first to lay the ground work for the next ics rom of your choice.
Sent from my Fascinate Unicorn Glitched up M6-style.
Maybe your radio got corrupted somehow? Try flashing a bunch of different ones to see if it helps... all that info is found in droidstyle's guide
edit: Oops sorry, somehow I skimmed over that part saying you already tried different radios. I agree with the above though, go back to stock via droidstyle's guide and see what happens...
I just stumbled across something that may help you... read this and try it out... some people have reported data issues being resolved after doing that update. I've never done it myself, but I think I'm going to start making it a habit