Database Info

Universal No GSM Problem

Hi All,
It had been a long time that i have been trying to solve the 'No GSM' problem.
My device is O2 xda Exec, but strangely it started to show no sim card and then showing No GSM on the boot screen.
I had tried various ROMS by our friends, but no one is able to sort out this problem. Now i am really tired of it.
If anyone can help, knows any method to sort this out, any clues, i will be very happy.

i have the same problem.....
i had flash several rom's, but i cant flash radio rom as i show in this topic
http://forum.xda-developers.com/showthread.php?t=457873

Try flashing back to the original factory ROM pack, it comes with everything in one upgrade package, so it will flash your ROM, Radio and Extended ROM at once. Trying cooked ROMs will not solve it, simply because they don't come with Radio as a general rule, so if you are missing a Radio, flashing a developed ROM will not add one.
Alternatively, of course, it may indicate problems with your main board that simply no longer reads your SIM.

i don't know the original rom version of it.
i had tried 2 original Imate WWE roms and it stucks at 0% at flashing radio rom. i instead it, i flash the rom and extrom separately several times, with severak versions, and the only problem is flashing the radio rom.
the device works properly, except GSM. the wifi and BT turns on and off. (no other devices to have comunicate)
i tried also sim "unlock" (it is already unlocked from factory) and i have the "success" message, then tried to flash radio rom, but unsuccessful.
then i did a rom backup from other device (Orange SPVM500 brand) to sd card and then restore to Jasjam, but shows "error ID"
then, i tried to backup the entire rom from itself to SD and restore it again, but the commands seems to not work.
then a did a upgrade bootloader (because it stucked at bootloader) even using UNI_bootloader EXIT.exe
i have no more ideas, then have it a large hammer!

hi_siddhu said:
.... but strangely it started to show no sim card and then showing No GSM on the boot screen....
Click to expand...
Click to collapse
mine started like that.... and the other one (i have 2), today showed me the same message...

jesuis said:
mine started like that.... and the other one (i have 2), today showed me the same message...
Click to expand...
Click to collapse
SIM is due for replacement?

i tried 2 sim card's from 2 different operators.
actually it is without sim card, but shows the "NO GSM" at start up.
on past Saturday, my other pda (old HTC BLUEANGEL) had a freeze on receiving a call (i must reset it 4 times) then i made a call and nothing happened after that.
very strange.
i tried also backup a rom from the device to sd card and shows me an error (error = FF) on mtty1[1].42
i do the operation successfully on my other htc.

i read that sometimes take out and plug in the batery several times, works...
mine dont.

Try this it worked for me.....
Most of the ROM you update only have the nk.nbf (OS ROM) but don't have ms_.nbf (Extended ROM), radio_.nbf (Radio ROM). so you should upgraded the radio_.nbf manually.. and the problem should me solved..... so simply download any new Radio version in my case 1.17.XX and copy the file radio_.nbf (Radio ROM) in to the ROM update folder . Enter boot screen and update... the problem should be solved.... have a look at following link as welll... might be helpful...
http://wiki.xda-developers.com/index...name=UNI_Radio

I too have the "NO GSM" issue, and have noticed that most cases are associated with the o2 Exec; as is mine. I'm also missing my IMEI in 'device information'. I think the issue may have something to do with the CID lock originally found in the o2 Exec. I too have tried almost anything and have heard the original ROM is the only way back (which I don't have). However, I believe that an SD upload/download of a radio ROM may be a possible solution. The trick is getting the 'header' of the "to be downloaded" radio ROM to match up with the device. This is where I'd left off on trying to fix my device...I don't know how to edit the ROM's header and save, so that I may download via SD card...any help would be much appreciated...

Its a HW problem...

what do you mean by sd upload/download of rom ????
EXEC/JASJAR said:
I too have the "NO GSM" issue, and have noticed that most cases are associated with the o2 Exec; as is mine. I'm also missing my IMEI in 'device information'. I think the issue may have something to do with the CID lock originally found in the o2 Exec. I too have tried almost anything and have heard the original ROM is the only way back (which I don't have). However, I believe that an SD upload/download of a radio ROM may be a possible solution. The trick is getting the 'header' of the "to be downloaded" radio ROM to match up with the device. This is where I'd left off on trying to fix my device...I don't know how to edit the ROM's header and save, so that I may download via SD card...any help would be much appreciated...
Click to expand...
Click to collapse
what do you mean by sd upload and download of rom ??????
can you be explain in more detail.....
Cheers
rajiv

You can find more information in the forum adout downloading by SD card. Tomal has an SD ROM tool; or you could try the service manual...Either way, I cannot seem to get an SD download to work because of a fixed CID lock; this was confirmed through MTTY. However, I believe if I clone the header (acceptable to the device) into the "new" radio ROM; my device should be able to update. If it doesn't, I feel I could then confidently believe that the issue is in the hardware...'til then...
Can anyone out there help me with this, PLEASE!!!

So try unlockind your device to make it SuperCID
EXEC/JASJAR said:
You can find more information in the forum adout downloading by SD card. Tomal has an SD ROM tool; or you could try the service manual...Either way, I cannot seem to get an SD download to work because of a fixed CID lock; this was confirmed through MTTY. However, I believe if I clone the header (acceptable to the device) into the "new" radio ROM; my device should be able to update. If it doesn't, I feel I could then confidently believe that the issue is in the hardware...'til then...
Can anyone out there help me with this, PLEASE!!!
Click to expand...
Click to collapse
try to unlock ue device then.follow the link below..
http://wiki.xda-developers.com/index.php?pagename=Uni_Simlock_by_Buzz_and_team
Cheers
Rajiv

How can the ROM version suddenly change?

Hi All,
Just a quick question.
I noticed today that my ROM and Manila version under Settings have reverted back to 1.66 despite the fact that ROM version under on the o2 boot screen is still 1.72.
How can this happen? Is it something to do with restoring a backup?
Any ideas?
Thanks in advance.
EDIT: Sorry Mods, I thought I was back in the HD2 General thread. Please move it.

what did you use to restore a backup it could have saved some registry bits and changed them in the phone,

Im sure you restored a full backup after changing the ROM Dont do this !!! Seriously you get many problems with that. Just restore your contacts, messages etc. and install everything clean again...

possibly, my bad....
elburna said:
Im sure you restored a full backup after changing the ROM Dont do this !!! Seriously you get many problems with that. Just restore your contacts, messages etc. and install everything clean again...
Click to expand...
Click to collapse
I changed my ROM ages ago and checked the version under Settings straight afterwards and it was fine Im sure ( I think LOL). I need do a restore today after the HTC Messaging Client 2015 update didnt work and just happened to notice the inconsistency.
Anyway I reckon the ROM version displayed in settings is simply reading from a registry setting (I found the wrong manila version number in the registry also) , as the boot screen displays the correct version.
PS. I use SPBbackup in ROM upgrade mode when moving to a new ROM and and this is the first time I have experienced this. Bearing in mind that I have gone from 1.43 O2 to 1.66 stock to 1.72 O2 and this is the first time I noticing this, 2 months after last upgrade.
Strange...I havent noticed any issues, so I will probably just fix at the point of the next upgrade (assuming there will be one).
Thanks for input so far.

[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] Nexus S 4G 4.0.4 issues with radio

So I've been trying to upgrade my phones from a custom ROM to the official 4.0.4 releases on Nexus S 4G. So I flashed the IMM76D signed zip (flashable one) and got it working. A bit after this, I noticed that I wasn't getting SMS messages. I'm not going to bore you guys with a backstory, so I'm just going to say what I did.
I used "SMSC Updates" found on the Cyanogenmod Wiki to update my SMSC settings (tried all of the following numbers: 07918188561627F7, 07917140140000F0) after seeing it as a suggestion somewhere else about SMS issues. I re-flashed the radio (the new one that released with 4.0.4), and I still cannot get it to work.
I've tried several ROMs, too. Un-rooted, re-rooted, had problems with recovery (solved those, though), and re-rooted again. Also, attempting to use 4G settings crashes the phone.
Does anyone have any suggestions for what I should do? As far as I know, I'm able to send SMS, but not receive. Could this be a Sprint issue?
Thanks.

xation said:
So I've been trying to upgrade my phones from a custom ROM to the official 4.0.4 releases on Nexus S 4G. So I flashed the IMM76D signed zip (flashable one) and got it working. A bit after this, I noticed that I wasn't getting SMS messages. I'm not going to bore you guys with a backstory, so I'm just going to say what I did.
I used "SMSC Updates" found on the Cyanogenmod Wiki to update my SMSC settings (tried all of the following numbers: 07918188561627F7, 07917140140000F0) after seeing it as a suggestion somewhere else about SMS issues. I re-flashed the radio (the new one that released with 4.0.4), and I still cannot get it to work.
I've tried several ROMs, too. Un-rooted, re-rooted, had problems with recovery (solved those, though), and re-rooted again. Also, attempting to use 4G settings crashes the phone.
Does anyone have any suggestions for what I should do? As far as I know, I'm able to send SMS, but not receive. Could this be a Sprint issue?
Thanks.
Click to expand...
Click to collapse
When you say new radio, do you mean LC1? I have had that radio for a week and all is good. If I were you I'd take a screenshot of my current setup and post it on here. I would try to, if you haven't already updating Prl and Profile and call Sprint and get them to reprovision your phone.
Hope you get it fixed soon. Sorry I couldn't be of more help..

xation:
Have you resolved your SMS issue?
My wife's S4G is doing the same thing after OTA: can't send, only receive SMS. MMS, on the other hand, are fine.
I've also tried the mentioned CM SMSC update, did not work; tried (*#*#72786#*#*) re-provision, but no luck.
Running out of ideas...

Just a follow up:
I installed Go_SMS, un-installed Handcent, and SMS started working!

[q] ruu 3.16.401.9?

Hello,
I have a question about the latest RUUs. While wondering how I could put an end to the helicoptering issue without sending it back for the 2nd time (1st time, they just replaced the screen... and I don't know what else they did because it didn't happen for 2 months) as I currently have no acceptable replacement device to use while it's in repair, I checked if I had the latest radio and firmware installed because some users told me the latest versions made the helicoptering disappear for them.
I can see on AndroidRUU that the latest available JB RUU for Europe is 3.16.401.8, but I have a 3.16.401.9 firmware on my One S. Any idea where it comes from? Does everyone actually have this one now? 'cause I havent seen a RUU for that. Wouldn't it be weird that a supposedly newer firmware didn't solve an issue that the previous one solved?
Anyway, would it be safe to install the 3.16.401.8 RUU currently available to see if that really solves the helicoptering like it supposedly did for some? I still have a 100% stock device and don't want/have the time to do all the tasks to try Maximus and its newest radio for example (I'm also a bit afraid of not being able to revert it back to stock if that doesn't work either and I finally decide to send it back for repair after that).
PS: as for the radio, I have the same as everyone I guess (1.15.50.05.29_10.30.50.08L)