so like a kid in a candy store i got ahold of ROM manager and ODIN and started flashing cool looking roms..next thing i know, the t-mobile logo is popping up and i am a not-so-proud owner of a modded T-Mobile Captivate, no longer an ATT Galaxy S!
of course the t-mobile network uses different frequencies and the like, so the phone part of my phone stopped working...bummer! i grumbled as i flashed back to a ROM that worked with the ATT network (FUSION it is called) but apparently that ROM does not mess with the internal network settings thats why it worked so well initially it didnt change the stock cell internals...
so now i have a hybrid phone, half-tomobile half-att half Fusion, and it only picks us signals from the Edge network!!! i barely get any reception so it pretty useless...
so i need some help...i can i get this beast back into a condition where is will work as an ATT galaxy?? also, for whatever reason i cannot mount or download market apps to the phone tho it does pickup wifi connections...
any help/ideas appreciated...advTHANKSance!
- mark
Flash back to stock with odin 1 click. Or try just flashing a new modem with cwm.
Sent from Serenpitidy x.x
ok...i finally fixed the mess i made by using this process...
manually set the modem/APK using this guide...may or may not have been needed in the end...
http://www.wireless.att.com/answer-center/solutionDisplay.jsp?solutionId=KB110934
reset the phone to factory using this thread...
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
note..i used the old I897UCJH2 Firmware but the plan is to upgrade to JH6 tonight...
did a factory reset on the phone and BINGO...full working baseline phone. thanks for the help guys what a great site u run
Hello,
Please help if you can! I updated my Nexus S to 2.3.4 the other day, and everything was working fine. Today, the phone at some point lost the ability to connect to my network (Bell Mobility). I was out and about and was turning data off, and might have hit the 2g/3g toggle by accident, and seem to remember reading about that causing problems - though I have no idea if I did for sure (the sun was bright) and am honestly not sure what's wrong EDIT: when I go into wireless & networks\mobile networks\network operators, the phone will only recognize Roger's Wireless (and it was bought at a Telus store!) The UI still works fine, and I can still connect via wifi - just no way to get it to recognize Bell's network
As stated above, everything was working fine this morning - voice, data and sms all good. Here is all the info from my phone:
Android version 2.3.4
Baseband version NO DGSXXKD1
Kernel Version 2.6.35.7-ge383d80 [email protected] #1
Build number GRJ22
The bootloader is unlocked, and I had been running CM7 before flashing the manual 2.3.4. I'm not sure what to do. Tried re-flashing the manual 2.3.4 update.zip, and nothing. I know a very little bit about rooting/flashing (just enough to follow guides), and am wondering whether I need to re-flash a different kernel/radio/rom or something. I did search, and couldn't find anything that outlined my problem exactly (I do apologize if something is out there and I just didn't look hard enough).
Again, the phone was bought new at a Telus store, and found the Bell Mobility network out of the box no problem. Am hoping someone can help!
Thanks so much for reading, and if you are able to help.
Check your APN's to make sure the data info is in there I had to manually enter mine (bought phone from Telus to use on Bell/Sasktel's network) for Sasktel and bob was my uncle
Every upgrade i need to put them back in. No automatic for me, so i would start there
Menu - Settings - Wireless & Network - Mobile Networks - Access Point Names.
If nothing is in there, you need your APN settings. Talk to bell support for the info, and they should be able to help you over the phone (they support android even if they dont sell a Nexus S)
Cheers!
Thanks so much for your response, though I don't think that the APN's are the issue at all; they're still in there and fine. I think that it's the actual radio (or baseband), as the phone will not recognize the bell network, only the Rogers network (and it was bought new at a Telus store!)
I think that I need to re-flash the radio, and maybe the kernel. I searched to try and find the radio image for my phone, but haven't found anything clear enough for me to be comfortable to try - I've read time and again that flashing radios is one of the riskier things to do. I don't think that my phone is bricked (can still boot it up, and all of the ui works and can connect via wifi). Don't want to risk doing more damage.
Thanks again for your response though!
i think i'm having the same problem. i've manually upgraded to 2.3.3 then to 2.3.4. and then i put a sim card in - not used it as a phone before this.
i can get 3-4 white bars lit up but can't connect to any network. the bars turn green when wifi is active, but still can't connect ("can't connect at this time. please try again later" toast appears). not sure if the phone is borked, or if the upgrade wasn't that successful.
I actually have this same issue but using it on at&t in the USA...Really hope it isn't broken cause I have no way to fix it since i'm not in canada
Maybe check if the 2g box is checked in mobile networks. Check your apn settings and if that doesn't help try and flash another radio.
Sent from my Nexus S using Tapatalk
djnoicatse said:
Maybe check if the 2g box is checked in mobile networks. Check your apn settings and if that doesn't help try and flash another radio.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
i'm unrooted, and don't intend to root. apn is fine as suggested above, and regardless of 2g checked or unchecked, still no connect
Rogers is the only 2G gsm provider, your phone may be stuck on 2G. If you have the choice, I would go back to 2.3.3 full stock and see if everything then works.
Sent from my Nexus S
Matridom said:
Rogers is the only 2G gsm provider, your phone may be stuck on 2G. If you have the choice, I would go back to 2.3.3 full stock and see if everything then works.
Sent from my Nexus S
Click to expand...
Click to collapse
but you have to root to flash 2.3.3 right?
MarkusPO said:
but you have to root to flash 2.3.3 right?
Click to expand...
Click to collapse
No. you are best to use cwm and restore a stock image for your phone
Sent from my Nexus S
Your best option is to flash back to 2.3.3. Download rom manager from the market and flash clockwork recovery. Once in recovery flash the 2.3.3 .zip file. I saw it somewhere here but i forgot where I saw it. Hope that helps.
Sent from my Nexus S using Tapatalk
Try this http://devsforandroid.com/index.php?board=18.0
I'm NOT SURE if it'll work, but it's worth the try. Make sure to to wipe everything before you flash. I'm not responsible for any damage this may cause. But I hope this helps you out.
If anyone wants to chime in and correct me please do so.
Sent from my Nexus S using Tapatalk
Or if you're not comfortable flashing the stock 2.3.3 rom maybe just try and flash back the xxkb2 radio which I believe was the stock baseband for Rogers, telus, Fido and bell. I have the .zip file for you to try and flash through CWM if you need it. Otherwise you can find it somewhere here aswell.
Sent from my Nexus S using Tapatalk
i'm not looking to root nor use any 'hacks'. i don't trust them.
under the battery, the phone is just a i9020. no letter afterwards.
Flashing a ROM doesn't require root, it requires unlocking the bootloader, which Google officially allows you to do that. You can unlock the bootloader, flash 2.3.3 ROM, then lock it as if it had never been unlocked. Just keep in mind that unlocking resets to factory default and wipes your SD card clean, backup before you do it.
Ahhh yes, I had same thing except with Telus I fixed it once, but the second time I could not get it to work, do this, flash this radio
http://forum.xda-developers.com/showthread.php?t=1044261
it is the stock radio your phone came with, then call up bell and get them to "repush" your sim card... hopefully you will see your network again.
Si_NZ said:
Flashing a ROM doesn't require root, it requires unlocking the bootloader, which Google officially allows you to do that. You can unlock the bootloader, flash 2.3.3 ROM, then lock it as if it had never been unlocked. Just keep in mind that unlocking resets to factory default and wipes your SD card clean, backup before you do it.
Click to expand...
Click to collapse
if i unlock to then flash, don't i need a radio package? how do i know which one to use?
also, would i be able to do a full compile of android and flash that?
MarkusPO said:
if i unlock to then flash, don't i need a radio package? how do i know which one to use?
also, would i be able to do a full compile of android and flash that?
Click to expand...
Click to collapse
It depends on which ROM you flash. I flashed the official 2.3.3 ROM, it contains the radio image, it'll flash it as you apply the update.
Do you remember which baseband version it came with out of box? That should give us hint as to which radio applies to your phone. I think there are really only two types of radios used except NS 4G, 850/1900/2100 (i9020A radio) and 900/1700/2100 (i9020T radio). You can ask your service provider or check out their website which band you are running on.
Back to flashing ROM, I just realised you don't even need to unlock the bootloader if you are flashing Google signed files. You should most likely be able to flash a 2.3.3 full ROM, then flash the 2.3.4 update file. But if you find the 2.3.4 full ROM, that's even more convenient. I saw a full ROM on the forum, but I that was for i9023 or i9020. Not too sure, maybe others know.
For the Canadian carriers, as stated before, Rogers is the only 2g (edge) carrier all others (Bell, Telus, Sasktel) are 3g (HSPA). go Settings>Wireless & network settings>mobile networks and ensure "Use only 2g networks" is not selected.
If this does not work flash the KB2 modem, the other modems may lose 850mHz spectrum which could be causing your grief.
Solution!!! (At least this worked for me!) - Didn't have to flash anything
Hey all,
I apologize for not posting this sooner, but found a solution that worked for me, hope it might work for others experiencing the same problem.
**PLEASE keep in mind that though this worked for me, I don't know if it will work for you (maybe it might make things worse for some people). Especially keeping in mind that I DON'T KNOW FOR CERTAIN what originally caused the issue for me, nor what specific factors (rom build, phone model, radio image, etc) might have contributed. As well, I am on the Bell Network. USE ANY OF WHAT'S STATED BELOW AT YOUR OWN RISK. Disclaimer stated, read on...**
In the dialer, I punched in *#*#4636#*#* and then from the menu that popped up, selected Phone Information.
From there, in the Set preferred network type: drop down menu (scroll down a little, you'll see it) I selected GSM/CDMA auto (PRL). **Again, remember that I'm on the Bell Network in Canada. Should you be trying this, these settings might not be for you. Again, AT YOUR OWN RISK**
Then, still from the Phone Information screen, I pressed menu button (the hard menu button on the phone), and then chose the Select Radio Band option. From there, I believe I selected Auto, though I may have selected USA (It's been a couple of days, and I can't remember, I apologize).
After that, went back to the Phone Information menu, and pressed Run Ping Test. It seemed to show all of the necessary (and appropriate for my network) settings as ok, and... everything worked!!! Full network connection as before!
Hope this might help someone else! Keep in mind that I'm not sure what caused the original problem; I do believe I remember pressing the 2g/3g toggle, and also remember reading somewhere that this can cause problems. Specifically, that it stopped peoples phones from going back from 2g to 3g - in my case (Bell Mobility) there is no 2g network to drop down to, so if it got stuck on EDGE mode, it probable looked for the only local carrier with a GM EDGE network, (Rogers) and got stuck there. Not sure, but maybe this is what happened. Any wise folks out there that might be able to confirm/offer insight?
Anyhow, thanks so much for all the responses and offers of help!
Ok, major screw up on my part. Accidentally odined the ATT Captivate stock files to my Showcase. Needless to say, i had a brick for a while. I have managed to get the phone back into download mode and loaded the Mesmerize software. The phone can at least make calls now, but no data yet. Does ANYONE have ANY odin files for CS? Or any advice would be good too.
Check your PM.
Ok, got stock CS software running on the phone again, but I still have no 3g or 2g data connection. Any thoughts?
Nevermind. Just forgot to do *228. Long day today.
Any chance I could get a copy of Odin for Showcase? I have to go back to stock for warranty purposes? Thanks!
I know this is an old post, but I cant seem to find the Ntelos odin files for the showcase. anyone got them?
I have the same problem. I have an NTELOS Showcase and I accidently flashed Cellular South Odin on it. Phone can still make calls but its crippled. No 3G and its just crap! Not sure what to do. I just want it back to Stock NTELOS again
tecknogod said:
I have the same problem. I have an NTELOS Showcase and I accidently flashed Cellular South Odin on it. Phone can still make calls but its crippled. No 3G and its just crap! Not sure what to do. I just want it back to Stock NTELOS again
Click to expand...
Click to collapse
Having the same issue. I accidentally flashed US Cellular stock files on mine and now I have no 3G. There's no development support for Ntelos and no one seems to either know what to do or care to help.
This is for the generic showcase http://rootzwiki.com/topic/19968-odingeneric-showcase-ntelos-fa10ei20eh09/
CSPIRE Showcase
I am having trouble getting my sch-i500 back up and running. I had updated to ics aokp_fascinatemtd_build 28, but ran into the problem of it showing that i was on verizon towers. I downloaded and tried to odin a cspire modem but no help. also tried *228 before and after the modem file. I can get cwm4 fixed for cm7 to come up and also the download for odin screen, but none of the files i have downloaded will work. it gets to factoryfs and hangs up. I have downloaded almost all files from rootzwiki labeled for use with cspire. any help will be appreciated.
ok so i got my phone up and running, aokp ics. but it was showing verizon as my carrier. I downloaded the cspire ei20 modem file from rootzwiki, used odin with atlas2.2.2.pit, put the modem file under phone section as instructions on rootzwiki said, checked repartition and clear phone efs, now the phone will not turn on. I can still get to download and intend to redo the aokp when i get home this evening. but how do i get the modem for cspire to work?
I updated my skyrocket to ics from gingerbread through keis. After doing so i noticed that i lost my wifi capabilities, att and samsung coundnt help at this point all it would do is say wifi turning on but it never would and i think i remember seeing my mac address in the phone status. Then i walked into the att store and my att wifi hotspot started working so i held signal for a min until i left i came home it wouldnt work so i flashed back to gingerbread using odin now it says wifi mac adress unavalable. When i try to turn on wifi in seting it acts like its going to but dont then says error under ive done resets recoverys all that crap and i cant figure this out i realy need some help. Any advice
Im just going to put this out there im not stupid im just not as tech savy as all of yall yet so please be very informational
Paydayexpress said:
I updated my skyrocket to ics from gingerbread through keis. After doing so i noticed that i lost my wifi capabilities, att and samsung coundnt help at this point all it would do is say wifi turning on but it never would and i think i remember seeing my mac address in the phone status. Then i walked into the att store and my att wifi hotspot started working so i held signal for a min until i left i came home it wouldnt work so i flashed back to gingerbread using odin now it says wifi mac adress unavalable. When i try to turn on wifi in seting it acts like its going to but dont then says error under ive done resets recoverys all that crap and i cant figure this out i realy need some help. Any advice
Im just going to put this out there im not stupid im just not as tech savy as all of yall yet so please be very informational
Click to expand...
Click to collapse
I had that same issue when I updated my girl's skyrocket to ICS via kies. It seems to fine now after a couple reboots and a few days of use. I would root the phone and do a complete wipe and flash stock ICS but thats just me.
jamrockbwoy said:
I had that same issue when I updated my girl's skyrocket to ICS via kies. It seems to fine now after a couple reboots and a few days of use. I would root the phone and do a complete wipe and flash stock ICS but thats just me.
Click to expand...
Click to collapse
i guess ill try that and se if it helps i havent tryed rooting yet . did you use odin for your flash and what flash did you use.and did you root before or after you flashed. just kinda wanting to get a heads up on the prosses
Paydayexpress said:
i guess ill try that and se if it helps i havent tryed rooting yet . did you use odin for your flash and what flash did you use.and did you root before or after you flashed. just kinda wanting to get a heads up on the prosses
Click to expand...
Click to collapse
I used ODIN to root and recovery to flash the prefered ROM
check this link here..........
http://forum.xda-developers.com/showthread.php?t=1652398
Use odin and return to stock. Then re-try the update.
I have two questions 1) is my only way to fix this to go back to stock ICS using ODIN? 2) Once i get back to that, what do i do in order to get to a working version of JB? is it as simple as trying another ROM? Is it ok to skip ICS and just flash another version of JB?
Background if you want it....
Followed vincon guide : http://forum.xda-developers.com/show....php?t=1773659
Started with Stock ATT 4.0.4
CWM via odin
baseb: UCLI3
I flashed JB [ROM] [4.1.2] [UCLL3] Stock Debloat to my i727 last night. Everything went seemingly smooth, everything worked with a strange exception being my exchange account wouldn't authenticate.Today my service is off about 95% of the time, then it will come on and ill get a text or two, then it goes off. voice calls dont work at all. LTE data is hit or miss.WiFi works
In phone status under network type its toggling: UTMS:3 to HSPA:11 to HSPAP15 to no service...then it drops everything and service state will say out of service and disconnected.
My IMEI is correct, I confirmed that.
It tried dialing the *#*#XXXX#*#* thing, that just said no connection and ended.
I started to go down the path of looking to flash a new radio, but that just doesn't seem like the answer to me... obviously the risk of me being wrong is high. i did check the MD5 numbers on other radios though and they came back as mismatched, so i did nothing there.
Also i wiped cache 3 times, as well as dalvek
Is there a simple solution that Ive missed or do i need to go to stock via ODIN? What, if anything, did i do wrong>
If you didn't flash corresponding UCLL3 baseband - AFAIK intermittent service is expected.
If you need to flash baseband - flash the latest UXUMA7 baseband.
Well i've actually had the exact same problem, in several variations and on several androids and here's my conclusions:
1 Magnetic storms and grid issues with the carrier. There's not much to do about these, except maybe for a making a tin hat for your phone. But, on a second thought this would also kill the signal
2 If the issue persists for more than a couple of days then the other thing for me was = radios that just didn't work with my carrier or rom. Changing these showed instant results.
I actually had this exact problem but for me it was on the carrier end. I tried every ROM and radio out there to no avail. After about a month and my parents also experiencing the issue, we called the carrier and they had it fixed in about two weeks.
Sent from my SGH-I727 using xda app-developers app
thanks for the help -
gonna try latest baseband and see how it goes
bgcole said:
thanks for the help -
gonna try latest baseband and see how it goes
Click to expand...
Click to collapse
It worked. Thanks again to all.
That's good to hear