Database Info

PLEASE HELP! 2.3.4 and suddenly can't connect to my network (Bell Mobility)

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!

[Q] No cell after 2.3.6 (and many attempts to fix it)

ok here goes, first off, i apologize if this is in any way redundant to someone's else question. with the amount of people whose phone got wrecked with the 2.3.6 update im sure somebody has had the problem im having.
like many people i just clicked "install" when google pushed the 2.3.6 ota. my phone was running 2.3.4. rooted. when it rebooted, i was greeted with the android exclamation mark.
i happened to have a clockwork backup so i tried restoring my backup. and restore it did, but not the radio. after the google update my radio was something like NO GSXXK1 or so. i tried the radio fix here:
http://forum.xda-developers.com/showthread.php?p=14564429&mode=linear#post14564429
i tried reflashing the stock 2.3.3 rom from google, wiping the bootloader and all. ive in fact tried many many things that ive read on xda and google forums.
now, ive managed somehow to have a running 2.3.4 with cell signal. using the efs file copy method in he link above. that restored my 3g and ability to place phone calls but sms arent working. i did the *#*#4636#*#* thing and notice that smsc is 00, i tried to set to the right value of +17057969300 for Rogers canada but all i get is an update error followed by a crash.
and now, funny, my search button is acting weird, like an eye that keeps twitching.
im not very knowledgeable in this stuff, just enough to get by and install custom roms but clearly im in over my head now.
why did copying my 3 efs file in the root of the sd card restore signal? i dont think these files really belong there, so just what the heck happened?
is there a way i can restore my nexus S to google stock rom when they shipped the phone? i mean, a complete wipe, sd, boot, radio...everything.
if i can start back with the stock phone, i can re-root again and start fresh.
any ideas please??
im physically tired of reading everything, misleading information and constantly flashing back and forth hoping its gonna work. oh and mandatory angry comment: thank you google for effing up my phone!
edit:
the only stock rom i tried i the 2.3.3 stock update available in clockwork. made no results.
current specs:
my phone is a i9020a
current baseband : NO DGSXXKD1
current build: GRJ22
android ver: 2.3.4
core: 2.6.35.7-ge382d80 [email protected] #1

Follow my last thread posted
Sent from my Nexus S using xda premium

Thanks dude, i had actually done that and did manage to get a signal back. its SMS that just wont work and when do the INFO thing to set the right value, i either get update error or a crash.
i installed stock rom 2.3.4 and install radio uckd1. that made my signal work even without having to move the efs files on the root of the sdcard. but still no sms.
is anybody else getting sms problems? this was working before the 2.3.6 fiasco.
im with rogers canada, in ottawa.

ok, just to loop the loop on this one and hoping it will be of use to somebody else.
my sms issue wasnt related to my phone at all, once i had a signal back, that's as far as the phone was concerned.
i placed a call to rogers to let them know i couldnt sms anymore.
long story short, they tried many things but ultimately, its doing the "hard" reset on the network for my phone that did it. im sure there a better name for it but basically they erased my phone from their network, i had to wait about an hour for the change to propagate. when i powered the phone back, it resynced everything and sms was back online without a single thing to do.

[Q] Desire S loosing signal

Hi all,
A week ago I bought a brand new Desire S and installed latest CM 7.1 stable following the guide on cyanogemod Desire S Wiki using revolutionary 0.4pre4. Everything was smooth and nice, I flashed ROM and GAPPS and my phone is working absolutely perfectly... but there is one little problem...
I am using Desire to fetch my mails from 2 mailservers using IMAP every 30 mins. But when the phone is switching between network modes i.e. HSDPA -> EDGE or EDGE -> GSM or any other way, I am disconnected from operator network for about 10 seconds until the network mode changes and everything is fine after that, until there is another network mode switch.
This happens for me about 10 times a day, so my phone sometimes appears that It is turned off for people who want to call me. Immediately after connecting to network I get a missed call SMS from my operator.
Interesting thing is, that when I disable email fetching, disable background data transfer and disable network data, the phone works fine without "blackouts".
Can someone help me with this problem? Maybe a radio issue?
Some more info:
ROM: Cyanogenmod 7.1.0 Desire S
Recovery: Revolutionary CWM v4.0.1.4
HBOOT: 6.98.1002
Kernel: 2.6.35.14-cyanogenmod+ [email protected] #1
Radio: 20.28I.30.085AU_3805.06.02.03_M

There is a newer radio-file online.
Maybe it's solving your problem.
I'm using MIUI and never had such problems, but i'm interested in flashing CM, so please report if the problem is gone by flashing newer radio!

Which radio version are you using?
Today I am testing 2G only switch so I am on EDGE data only.

Flashing radios is safe......, but a bad radio flash will instantly brick your phone.
You are using 1.47.401.4 radio, try updating to the 2.10.401.5 one.

Thanks for reply.
Shoud I flash something else with the radio?
I have 20.4801.30.0822U_3822.10.08.04 downloaded from cmw.22aaf3.com
Another I have is ftom OTA update zip file OTA_Saga_S_HTC_Europe_2.10.401.8-1.47.401.4_release_225210fmxlt12djw1sr7y5.zip where is one radio.img in formware.zip file too - version unknown
So Which one to flash?
and if so, which method should I use to flash radio? The Android SDK one or the ZIP + Bootloader one?

MyroLM said:
Shoud I flash something else with the radio?
Click to expand...
Click to collapse
no need
MyroLM said:
I have 20.4801.30.0822U_3822.10.08.04 downloaded from cmw.22aaf3.com
Click to expand...
Click to collapse
this file is what ur looking for! check md5-checksum before flashing!
MyroLM said:
and if so, which method should I use to flash radio? The Android SDK one or the ZIP + Bootloader one?
Click to expand...
Click to collapse
Both will work, i'm using method by using bootloader normaly

Strangely I had the same issues as you on Endymion.
Then I updated radio to the latest.
It worked well.
Then I went to CM7. It was fine for a while, but now I'm losing signal with no 3G bars and its not switching automatically to 2G like it should when It has no 3G signal!
EDIT:
After really reading your post, I realise my issue is no way like yours! Yours seems really bad. Update your radio.
-------------------------------
Sent from my HTC Desire S

So, here we go with the results
I flashed 20.4801.30.0822U_3822.10.08.04, md5sum checked OK, update sucess, but phone with no signal...
I flashed 20.48.30.0822U_3822.09.08.20, md5sum checked OK, update sucess, but phone with no signal again...
I flashed 20.28I.30.085AU_3805.06.02.03 back, md5sum checked OK, update sucess, but phone with no signal again...
... what now ... ?

After each flash wiped cache and Dalvik...

in your telephone-info there is shown the new radio after every flash?
do you have removed the batterycover, because there is integrated the antenna of your device!

mouzzza said:
in your telephone-info there is shown the new radio after every flash?
Click to expand...
Click to collapse
Yes, correct number every time.
mouzzza said:
do you have removed the batterycover, because there is integrated the antenna of your device!
Click to expand...
Click to collapse
No, the cover is at its place where it should be. Somehow I did the trick and I am back online with 20.28I.30.085AU_3805.06.02.03 on 2G only for now.
I read somwhere in the forum that ENG HBOOT is required for new radios... Are you sure I dont need to flash eng hboot it before new radio ??

MyroLM said:
Somehow I did the trick and I am back online with 20.28I.30.085AU_3805.06.02.03 on 2G only for now
Click to expand...
Click to collapse
in your area 3g is actually available?
may it helps to go outside, to find your net for the first time!
did you set an accesspoint for 3g?
may you have to set automatic settings, rather than 3g/2g-only?!
MyroLM said:
I read somwhere in the forum that ENG HBOOT is required for new radios... Are you sure I dont need to flash eng hboot it before new radio ??
Click to expand...
Click to collapse
using same hboot as you, never had problems on flashing radio-files!

yes, in my area there is 3g, when I turn off 2g only switch there is a problem described in my first post, so i am on 2g for now just to keep phone connected to network.
main problem is when i am driving and the phone is switching network modes.
so I give 20.4801.30.0822U_3822.10.08.04 today another chance, try to flash if again.
but i am woried about stucking on HTC logo after flash :-( and brick it.

MyroLM said:
but i am woried about stucking on HTC logo after flash :-( and brick it.
Click to expand...
Click to collapse
i already had the problem for several times, and i also pulled out the battery (you shouldn't do that)!
only had to boot into bootloader, start recovery, wipe all partitions, flash rom and was having fun again with my device
this thread could help you, if really stuck on HTC logo
For your real problem on loosing the signal, did you ever tried out using actual stock rom, or another custom one like MIUI?
i used MIUI from 2010-08 till yesterday, now trying out CM7.1 for some days

I have the same or a very similar problem. I have the stock rom.
I already had 3 different desire s motherboard's and 2 different display's.
The first Desire S i had, with android 2.3.3, had a excellent signal. Due some problems i had, the phone bricked and had to go to HTC to repair.
HTC replaced the motherboard and update the version of the android to 2.3.5 and ever since the signal caption, the signal switch was working very bad.
The phone went to a second repair because of this, new phone, and again with android 2.3.5. The problems persisted.
I also tested with different SIM cards, from different mobile operators.
So, my conclusion is either android 2.3.5 or this new versions of Desire S have problems with signal caption and signal switch.
So as you, i need some help with this issue!

mouzzza said:
i already had the problem for several times, and i also pulled out the battery (you shouldn't do that)!
only had to boot into bootloader, start recovery, wipe all partitions, flash rom and was having fun again with my device
this thread could help you, if really stuck on HTC logo
For your real problem on loosing the signal, did you ever tried out using actual stock rom, or another custom one like MIUI?
i used MIUI from 2010-08 till yesterday, now trying out CM7.1 for some days
Click to expand...
Click to collapse
But when I reboot to recovery it will flash the radio again I think.
i hate stock roms, and dont like MIUI design That is why I am using Cyanogen
Anyway if I use 2G only switch, the phone is stable as rock both calls and data transfer.
EDIT: OK, flashed 20.4801.30.0822U_3822.10.08.04 sucessfully, signal OK, I will see what happens whet metwork mode switches

@Green Hawk:
give us more information about your device please, which radio you're using? Did they flash actual radion also?
@MyroLM:
report if the problem is still there or it's gone with flashing the rom

I am still testing new radio, but looks good Give me some days let you know...

Hi All,
I have a similar problem with the latest CM7.1 nightly builds (Reaper, jorgen2009). I never saw this with older CM7.1 versions, e.g. Nexx version, ICS, MIUI oder Endymion.
I have WLAN on and leave my house. Phone switches to 2G/3G..., so far so good. When I return home, The WLan sign in the status bar appears again, everything seems to be fine, but I have no connection. I get no data via WLan until I swicth WLan off and on again.
Radio is the latest from 2.10.401.5.
Best Regards
Wrapp

Had similar problems, upgrading to the latest radio helped. I got stuck on the HTC screen and I went through flashing RUU's and unlocking bootloaders back and forth... when the only thing that needs to be done is to wipe the cache.
Learned a lot about bootloaders though. But my warranty got void because i did the htcdev unlock... (Sorry for OT)

[Q] No WiFi

I have a Samsung Rugby Smart ( AT&T ).
I used the last two files on this page:
http://forum.xda-developers.com/showpost.php?p=30347369&postcount=5
Stock recovery and system: odin_gingerbread.ucla4_recovery_stock_system_stock _no_root.tar.md5
ClockworkRecovery 6.0.1.1 and No-Bloatware and Root: odin_gingerbread.ucla4_recovery_cwr_6011_system_no _bloat.tar.md5.gz
and my WiFi is not working. When I go to Wireless and Networks - Wi Fi Settings -
Says: Error next to the check mark to turn wifi on or off. :crying:
Everything else seems to work including sound.
Baseband: I847UCLH4
Gingerbread 2.3.6
Build Number: GINGERBREAD.UCLH4
Kernel version: 2.6.35.7
WiFi MAC address: Unavailable
Bluetooth address: works!!
Does anyone have any idea what could be the problem?
thanks you

Is this issue solved?
Is this issue solved?
VoiceArtistUSA said:
I have a Samsung Rugby Smart ( AT&T ).
I used the last two files on this page:
http://forum.xda-developers.com/showpost.php?p=30347369&postcount=5
Stock recovery and system: odin_gingerbread.ucla4_recovery_stock_system_stock _no_root.tar.md5
ClockworkRecovery 6.0.1.1 and No-Bloatware and Root: odin_gingerbread.ucla4_recovery_cwr_6011_system_no _bloat.tar.md5.gz
and my WiFi is not working. When I go to Wireless and Networks - Wi Fi Settings -
Says: Error next to the check mark to turn wifi on or off. :crying:
Everything else seems to work including sound.
Baseband: I847UCLH4
Gingerbread 2.3.6
Build Number: GINGERBREAD.UCLH4
Kernel version: 2.6.35.7
WiFi MAC address: Unavailable
Bluetooth address: works!!
Does anyone have any idea what could be the problem?
thanks you
Click to expand...
Click to collapse

You could flash back to stock firmware and try again. If the error persists then the files are probably not right for your phone.

broadways said:
You could flash back to stock firmware and try again. If the error persists then the files are probably not right for your phone.
Click to expand...
Click to collapse
The files the OP pulled are for his phone based on the baseband shown. It looks like it may be related to the OTA update that came through recently.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
---------- Post added at 08:40 AM ---------- Previous post was at 08:37 AM ----------
VoiceArtistUSA said:
I have a Samsung Rugby Smart ( AT&T ).
I used the last two files [edit] [and] my WiFi is not working
Baseband: I847UCLH4
Does anyone have any idea what could be the problem?
Click to expand...
Click to collapse
Did you install the OTA update that AT&T pushed recently before flashing the ODIN images?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

kemonine96 said:
Did you successfully apply the ota update that came through for the rugby?
Click to expand...
Click to collapse
VoiceArtistUSA said:
Yes, before any root or flash of course.
Click to expand...
Click to collapse
That explains it, the OTA update includes a slightly changed kernel (based on what I saw in the diffs) that is likely causing your WiFi issue. Can you try applying motorhead's kernel from here and see if WiFi starts working? I know it is not a full fix, but it should get your wifi back to working while motorhead and I coordinate on getting a stock kernel that can be flashed from CWR put together.

YEEEEE HAAAAWWWWW
I got some WIFI !!!!
Camera, BT and sound, seems like everything works.
Can't imagine why not a "Full fix".
Thank You !!!!
Says there is an OTA update, after it downloads, I get tossed into CWM bootloader 6.1.1 and the update doesn't get applied.
All I do is choose 'reboot system'.
Also I'm getting ...
"[ AT&T Address Book] Checking Subscriber Information"
when I touch contacts.
I am not an AT&T customer, I use STLK the BYOP program.
We really need a custom ROM for this great device, no bloat, no AT&T updates, no AT&T bloatwares, No CIQ, No City ID.
I would be HAPPY to PAY for a custom ROM and have it delivered two weeks from last Thursday. Jellybean?
Someone like me who chooses a rugged phone may not be into all the bells and whistles, so a basic stripped down
ROM would be great.
and yes, I am getting lag coming out of deep sleep. may have to hit power button twice to unlock.
Can't wait to try Motorheads soon to be released power kernel...
kemonine96 said:
That explains it, the OTA update includes a slightly changed kernel (based on what I saw in the diffs) that is likely causing your WiFi issue. Can you try applying motorhead's kernel from here and see if WiFi starts working? I know it is not a full fix, but it should get your wifi back to working while motorhead and I coordinate on getting a stock kernel that can be flashed from CWR put together.
Click to expand...
Click to collapse

VoiceArtistUSA said:
I got some WIFI !!!!
Camera, BT and sound, seems like everything works.
Click to expand...
Click to collapse
I'm glad to hear it's working again for you.
VoiceArtistUSA said:
Can't imagine why not a "Full fix".
Click to expand...
Click to collapse
Because I assumed you wanted to roll back all the way to stock . If I knew you were good with non-stock kernel I'd have said full fix .
VoiceArtistUSA said:
Says there is an OTA update, after it downloads, I get tossed into CWM bootloader 6.1.1 and the update doesn't get applied.
All I do is choose 'reboot system'.
Click to expand...
Click to collapse
There is an updater app you can freeze to prevent this from running. Nicedream06 and motorhead1991 have it disabled w/o ill effects.
VoiceArtistUSA said:
"[ AT&T Address Book] Checking Subscriber Information"
when I touch contacts.
I am not an AT&T customer, I use STLK the BYOP program.
Click to expand...
Click to collapse
No ideas on this one. I'm an ATT subscriber and I don't remember that firing off, but I bought the phone the month it was released...
VoiceArtistUSA said:
We really need a custom ROM for this great device, no bloat, no AT&T updates, no AT&T bloatwares, No CIQ, No City ID.
I would be HAPPY to PAY for a custom ROM and have it delivered two weeks from last Thursday. Jellybean?
Click to expand...
Click to collapse
Working on it with a few others "right now". We have stable boot in ICS (CM9 and AOSP builds) but the modem is dead. No cell service at all. There are other problems but we are focused on getting the antenna up and going.
VoiceArtistUSA said:
Someone like me who chooses a rugged phone may not be into all the bells and whistles, so a basic stripped down
ROM would be great.
Click to expand...
Click to collapse
Check the super thread. I have an ODIN image that is pretty stripped down and it includes the 6.x version of CWR. I left a few things in "just in case" but they can easily be stripped out using any of the various root tools for removing system apps.
VoiceArtistUSA said:
and yes, I am getting lag coming out of deep sleep. may have to hit power button twice to unlock.
Can't wait to try Motorheads soon to be released power kernel...
Click to expand...
Click to collapse
If you can post over in motorhead's thread that you are experiencing the problem it will help out to know that it is common. He mentioned he was looking into it. I'm sure something will be ready soonish.

kemonine96 said:
I'm glad to hear it's working again for you.
Because I assumed you wanted to roll back all the way to stock . If I knew you were good with non-stock kernel I'd have said full fix .
There is an updater app you can freeze to prevent this from running. Nicedream06 and motorhead1991 have it disabled w/o ill effects.
No ideas on this one. I'm an ATT subscriber and I don't remember that firing off, but I bought the phone the month it was released...
Working on it with a few others "right now". We have stable boot in ICS (CM9 and AOSP builds) but the modem is dead. No cell service at all. There are other problems but we are focused on getting the antenna up and going.
Check the super thread. I have an ODIN image that is pretty stripped down and it includes the 6.x version of CWR. I left a few things in "just in case" but they can easily be stripped out using any of the various root tools for removing system apps.
If you can post over in motorhead's thread that you are experiencing the problem it will help out to know that it is common. He mentioned he was looking into it. I'm sure something will be ready soonish.
Click to expand...
Click to collapse
The lag is a noted issue, along with the WiFi shutting off randomly and intermittently. I'm researching these issues as much as I can to find a fix, but I can only do so much so fast .

I was going to start a new thread but then I found this. I too had the issue with I the wifi turning off and the screen lag. After reflashing the no bloat Odin image and the 1.1 kernel my wifi turns on, but does not find any networks. It just searches then shuts off? Any ideas? I wonder if the stock kernel being worked on would fix this or if there is something else wrong. Any help would be greatly appreciated.
Sent from my SAMSUNG-SGH-I847 using xda premium

I sent the rugby smart to SAM to have it completely reloaded. when it comes back, i will try to make a back up much like i make an image of a hard drive...if that's possible.
For my PC, I have an image of this existing hard drive. If i pull it out and put in a BLANK hard drive, I can write the image to the new disk with all my apps installed...I use that feature often with my pc's and others...for mine, I frequently make a new updated image and delete the oldest one.
Once I change the bootloader, is it possible to get it back if I backed up with with Kies?

You guys are in luck. Kernel1.2 should be out shortly with the lag and wifi fixed . I'm waiting to hear back from another tester, but so far ut's proven stable. I've only had one error pop up, and that was after running pretty hard.

Motorhead1991, Is this for the Samsung Rugby Smart?
How much of, if any, overclocking??
Can you also tweak a non-overclocked version without "City ID" app, "Carrier IQ" app and possibly no AT&T bloatware??
You rock for everything thus far

No overclocking just yet, but I'm giving it hell. On the bright side, Kemonine and myself are currently treading in uncharted territory for this device (see if anyone gets my reference)
And to answer your question, yes it'll be for the Rugby.

iam not sure
thats a good question

Motorhead1991 said:
And to answer your question, yes it'll be for
the Rugby.
Click to expand...
Click to collapse
After a day of use, it seems very stable and even more efficient.

That is great news! Can't wait to test
Sent from my SAMSUNG-SGH-I847 using xda premium

alan2424m said:
thats a good question
Click to expand...
Click to collapse
Yeah, it actually did hurt to ask that one.

So after flashing the following new odin images
•Stock boot / kernel:
•Stock Boot + Stock Recovery + Stock System:
•Stock Boot + CWR 6.0.1.2 + No Bloat System:
My WiFi still turns on, searches for a while, finds nothing and turns back off! I have no idea what to do next. Any ideas?

ESPFreak said:
So after flashing the following new odin images
•Stock boot / kernel:
•Stock Boot + Stock Recovery + Stock System:
•Stock Boot + CWR 6.0.1.2 + No Bloat System:
My WiFi still turns on, searches for a while, finds nothing and turns back off! I have no idea what to do next. Any ideas?
Click to expand...
Click to collapse
When you flashed via ODIN did it show it was flashing the boot area? In the status window it should tell you which images are being flashed to the device. Can you re-try the stock boot/kernel ODIN image and confirm it did flash the boot image?

That is the only thing that booted. As soon as I selected the image I got a "MD5 checksum failed" prompt. The "start" button changed to the same message but it let me click it and it loads the boot.img. Does that help at all?
Sent from my SAMSUNG-SGH-I847 using xda premium

[Q] No cellular wireless signal after Cyanogenmod 9 - ICS on i897

Not getting a cell phone signal at all on my Captivate. very rarely I get it and it stays on until I reboot for some reason, or sometimes goes off on its own. No problem with wi-fi or anything else.
Have had Gingerbread 2.3.5 - KK4 (official) for a long time, and did not have this problem. Here is what I did:
Installed Cyanogenmod 9.0 (ICS 4.0.4) on my Captivate that had the stock Gingerbread KK4. Also installed the gapps-ics package from 29 April 2012
I did this after rooting, and installing clockworkmod.
Even updated it to Cyanogenmod 9.1, but have the same issues.
More detail on it:
- The cellular radio shows no signal, but Wifi is on fine.
- When I press the power button, I see the power off and reboot options, including one that says "Airplane Mode is ON", although it clearly isn't since Wifi is working
- A couple of times, I rebooted into recovery, and did a "repair permissions" and rebooted, and it got a signal, but does not happen always
- Once the signal is on, it stays on for the whole day, but goes off again after a reboot
- Turning Airplane mode on and off does not help
Is this a modem issue, that seems to be a popular problem. It's almost as if there is a software bug that fools the phone into switching off wireless radio
Please help me fix it, or share successful fixes

I had same problem when I went to helly bean then back to remics-jb I flashed back to stock then back up to what I wanted it fixed the problem so I think its the modem.
Sent from my SGH-I897 using xda app-developers app

You need to flash to stock and back.
Sent from my SGH-I777 using xda premium

How do you flash your rom?
Im a little bit afraid to bricked again my cappy.
Sent from my SAMSUNG-SGH-I897 using xda premium

KOROCK is right
So were you able to fix? I had a similar problem as well; I made the mistake of putting cm9.1 on and it bricked because I followed the instructions that popped up when I thought I had flashed it correctly. I tried everything; this is my daily driver so I had no choice but to find a fix, and find it fast as my clients were unable to get a hold of me for a few hours.... Anyways, got a little off track; but did you fix?

up_on1 said:
So were you able to fix? I had a similar problem as well; I made the mistake of putting cm9.1 on and it bricked because I followed the instructions that popped up when I thought I had flashed it correctly. I tried everything; this is my daily driver so I had no choice but to find a fix, and find it fast as my clients were unable to get a hold of me for a few hours.... Anyways, got a little off track; but did you fix?
Click to expand...
Click to collapse
Not fixed yet. Wheredo I get the stock rom.?

rdugar said:
Not fixed yet. Wheredo I get the stock rom.?
Click to expand...
Click to collapse
A little search/reading goes a long way.. http://forum.xda-developers.com/showthread.php?t=1300843
KK4 is what you'll want to go back to stock but I highly suggest you read this before you do anything http://forum.xda-developers.com/showthread.php?t=1350266
Also, before returning to stock, you could try flashing a different modem.

Check to see if your baseband is still there. If it said "Unknown", you need to restore it. CM9 is supposed to have the modem.bin file included though. Check to see if the /radio folder have modem.bin in it, if it does, and the baseband still say Uknown, then manually delete the modem.bin, do a wipe and reflash a CM rom that have modem.bin included.
If Baseband is still there and still no signal, then check to see if IMEI is corrupted or lost (if its null or doesn't match the back of the phone). You can either copy over the efs backup folder if you have one and "fix permission" in CWM. If not, then you need to ODIN the phone to stock to fix it.