Database Info

[Q] Nexus S no network service! What do I do?

Hi guys I have a 2 month old Nexus S and for no apparent reason all of a sudden today I noticed I am not getting any network service (australia vodafone).
I've tried removing and trying other sim cards which are known to work. My sim card works in other phones so it's nothing wrong with the sim card. Wifi still works perfectly. I've tried going in and out of airplane mode to restart the antenna and I've tried to turn it off and on again. I've also done a factory reset and erased all data through the android menu as well as the bootloader separately to no avail.
However what I also noticed is even though I did factory resets it doesn't seem to completely reset it as the android version still shows 2.3.3 which I applied using a manual update. The phone had 2.3.1 when I bought it. How do I do a full reset to send it back to 2.3.1?
The phone is still under warranty however if it is a software issue I would rather fix it myself then send it away.

I'm having the same issue. I've posted in the cyanogen forums but I'll share the issue here as well.
I'm pretty scare the radio is damaged or something...
I've rebooted my Nexus S with Cyanogen RC4 to show a friend of mine the boot animation. From that point on, I'd get messages that the application "com.android.phone" force crashed all the time.
I noticed at that point that I had no signal/radio/service.
Wifi worked properly and still works fine.
I've tried updating Cyanogen to the stable release, still no service but I stopped getting the phone crashing errors.
Tried flashing a new radio (KB3) through clockwork recovery, didn't fix the problem.
Tried flashing stock back (2.3.3 Deodexed unrooted) didn't work.
Made sure data and cache was wiped, didn't fix the issue.
I've also tried relocking and re-unlocking the device (oem lock, oem unlock), to no avail.
As a last resort, attempted to enable and disable airplane mode but no go either.
I'm pretty scared that the radio might be damaged (how would it have been damaged by a simple reboot ?) How can I tell and what further steps can I take to diagnose this ?
Right now, I'm trying to reflash cyanogen so that I try and get a dmesg on the device.
Thanks,

Additionnal bit of info.
Someone on Cyanogen forums asked me to try to flash the radio through fastboot instead of clockwork recovery..
If I do that, it is able to send the file but it seems unable to write. It gets stuck here:
fastboot flash radio XXKB1-GRI40-radio-nexuss-unsigned.zip
sending 'radio' (4126 KB)... OKAY
writing 'radio'...
(I've tried flashing both KB1 and KB3 through flashboot, same results)

Hello everyone,
I have the same issue. I turned my phone on this morning and it said "no service, emergency call only".
I used wifi to apply the OTA 2.3.4 with hope that it'd fix the issue as I read from my google searches. But it does not.
I tried flashing back to KB3 to run with 2.3.4 as well but that doesn't help.
If the phone can still do emergency call, it means the hardware is OK, right?
any suggestion? Thank you very much.
Opteron.

Did anyone ever find a solution?

you could try dialing *#*#4636#*#*, going to phone information, and looking at your preferred network type (might be the wrong one). you could also go to phone information, push menu, go to select radio band, and try a few different ones. hopefully that solves it, or you might have to flash a different radio/rom
edit: make sure you write down the original preferred network type before you change it. it could screw with what kind of service you get if you set it to the wrong one

Hi,
I am having the similar problem with my Nexus S
Tried the *#*#4636#*#* settings to EURO and GSM only but with no success.
Did anyone ever find a solution?

hi, im just wondering what type of root did you use for the AU nexus s. im not sure what root method to use for the SCLCD :S
thanks

fooraide said:
I'm having the same issue. I've posted in the cyanogen forums but I'll share the issue here as well.
I'm pretty scare the radio is damaged or something...
I've rebooted my Nexus S with Cyanogen RC4 to show a friend of mine the boot animation. From that point on, I'd get messages that the application "com.android.phone" force crashed all the time.
I noticed at that point that I had no signal/radio/service.
Wifi worked properly and still works fine.
I've tried updating Cyanogen to the stable release, still no service but I stopped getting the phone crashing errors.
Tried flashing a new radio (KB3) through clockwork recovery, didn't fix the problem.
Tried flashing stock back (2.3.3 Deodexed unrooted) didn't work.
Made sure data and cache was wiped, didn't fix the issue.
I've also tried relocking and re-unlocking the device (oem lock, oem unlock), to no avail.
As a last resort, attempted to enable and disable airplane mode but no go either.
I'm pretty scared that the radio might be damaged (how would it have been damaged by a simple reboot ?) How can I tell and what further steps can I take to diagnose this ?
Right now, I'm trying to reflash cyanogen so that I try and get a dmesg on the device.
Thanks,
Click to expand...
Click to collapse
Hello! did you find any solution or you repaired your nexus s? Im having the same problem. when i try to back to stock from Cyanogen..Any suggestion? Regards

found a solution
hi guys ! I recently had the same trouble that no signals were being received after updating to 4.1.2 but then i dialed *#*#4636#*#* and turned off the radio and turned it on again and now its all fine

[Q] Rebooting issues?

I have occasional reboots while the phone is sleeping (you have to re-enter your pin after it happened).
Reboot were occuring ~2 times a week.
I had root installed and I am thinking of sending it to warranty, so I re-flashed the original firmware and made a factory reset. I am not thinking that root or Ad-Block is causing this, but I don't want to have root installed when I send it.
I also read in a german forum that I am not alone with this. My firmware is I9103XWLA4_I9103DRELA1_I9103NELA1 (android 2.3.6 with Drei branding). (original Drei branded phone in Austria)
http://www.android-hilfe.de/samsung-galaxy-r-forum/208721-hilfe-galaxy-r-schaltet-sich-aus-ein.html
Does anybody else have any reboot issues? Pls also name firmware and if root is installed.
Thanks!

Yes some of our users (mostly indian as far as I remember) experienced random reboots. It usually ended up in service with motherboard's or device's replacement. That has nothing to do with root. Root is just an application located in system/app that gives you permission to perform operations in system partition....etc. Of course it's possible to induce such behavior if you use some let us call them "dangerous" applications that requires superuser's permission, but su-application doesn't do anything by itself.
I also use this rom XWLA4 with my regional CSC. My device is rooted and have never experienced such issues (I own it since october 2011).

Thanks for the info, so I think more and more that this could be a hardware issue.
I am kind of preparing of giving it back to samsung to exchange it, this is the real reason I removed root and root apps.
I am just not really sure if this is a software or hardware issue, so this is why i posted.

I completely understand. To unroot, restore stock fw and send it to service is the best u can do in such situation.

I've done it now, but it did not happen, since I unrooted it and did a factory reset.
Lets see if it will happen again (then I will send it in) and how long I can survive without root.

alx07999 said:
I've done it now, but it did not happen, since I unrooted it and did a factory reset.
Lets see if it will happen again (then I will send it in) and how long I can survive without root.
Click to expand...
Click to collapse
i was also facing similar kind of issue, I've done factory reset and cleared the cache. now i am not facing that problem..

IMO sending it to the service center should be a last ditch effort.. Coz those guys take so much time plus they always go after the motherboard... I have a feeling its the cache issue or battery calibration issue. Coz even i faced the prob and like mj.vikram suggested - I did a wipe cache and calibrated battery and it seems to have worked.
Cheers.

Factory Reset and Cache Clear did not work, so i've given it to the service center. They've exchange a part of the motherboard, I did not have any reboots since.
If I get reboots again I will write here.

alx07999 said:
Factory Reset and Cache Clear did not work, so i've given it to the service center. They've exchange a part of the motherboard, I did not have any reboots since.
If I get reboots again I will write here.
Click to expand...
Click to collapse
My bad - I shud have updated the post. Even I faced the issue again and have given it to the service center.
Glad to hear ur issue is resolved. Enjoy the machine!

[Q] Galaxy Nexus radio/modem failure, baseband version : unknown

Hi,
I'm new to this forum.
I got a new Samsung Galaxy Nexus (unlocked GSM-i9250) mobile thruoug Google Store and got it to India.
I did an OTA upgrade from ICE Stock 4.0.4 to stock JB 4.1.1. My next upgrade to 4.1.2 failed, though detected by system failed.
So I used the phone for about 2 days and one day after charging, there was no radio service. WIFI works. Tried another SIM
and operator but in vain.
As all my efforts of factory reset, reboot etc failed, I thought of reflashing the latest images.
So I downloaded the latest images from Google site, unlocked the bootloader, followed different threads
and tried updating to 4.1.2. System now boots to 4.1.2 and WIFI works, but no GSM service still.
In the phone settings
Basebad version : unknown
Network : Unknown
IEMI : unknown
Service state : Out of service/Radio off (keeps toggling every 4-5 sec)
So I tried going back to 4.0.4 and system boots back to 4.0.4, but no GSM service
No idea what is happening. Two of us bought at the same time and got the same to India. For my friend, the OTA updates
to 4.1.1 and 4.1.2 went through fine.
I saw similar issues reported but not able to figure out how finally they solved it.
Any suggestions/help is appreciated.
Thanks in advance
Sanu

sanu.mathews said:
Hi,
I'm new to this forum.
I got a new Samsung Galaxy Nexus (unlocked GSM-i9250) mobile thruoug Google Store and got it to India.
I did an OTA upgrade from ICE Stock 4.0.4 to stock JB 4.1.1. My next upgrade to 4.1.2 failed, though detected by system failed.
So I used the phone for about 2 days and one day after charging, there was no radio service. WIFI works. Tried another SIM
and operator but in vain.
As all my efforts of factory reset, reboot etc failed, I thought of reflashing the latest images.
So I downloaded the latest images from Google site, unlocked the bootloader, followed different threads
and tried updating to 4.1.2. System now boots to 4.1.2 and WIFI works, but no GSM service still.
In the phone settings
Basebad version : unknown
Network : Unknown
IEMI : unknown
Service state : Out of service/Radio off (keeps toggling every 4-5 sec)
So I tried going back to 4.0.4 and system boots back to 4.0.4, but no GSM service
No idea what is happening. Two of us bought at the same time and got the same to India. For my friend, the OTA updates
to 4.1.1 and 4.1.2 went through fine.
I saw similar issues reported but not able to figure out how finally they solved it.
Any suggestions/help is appreciated.
Thanks in advance
Sanu
Click to expand...
Click to collapse
I had a similar experience with my previous Nexus S device. The phone would start up perfectly fine but it wouldn't catch reception. I think I flashed the wrong radio.img file (there are a lot of Nexus S variants).
I would try the following steps:
- Flash CWM recovery
- Flash a custom ROM (you can use "Mounts and Storage" in CWM recovery to gain temporary access to your internal storage - you will need to do this to copy your ROM file there)
- If you like it, just stick to the custom ROM.
If you insist on going back to the stock ROM, there are threads here that guide you to go back to stock completely. Even if you go back to a previous ICS ROM (specific to your phone), you should start receiving OTA updates normally.
Best of luck!

Thanks for the reply.
I'm almost sure the radio image is fine. I downloaded the images from
Google Nexus developers site for "takju" for Galaxy Nexus "maguro" matching with my phone.
I flashed matching ROM and radio images from Google site. Tried both ICS 4.0.4 & JB 4.1.2
I'll try custom ROMs if nothing works out. I'm going to try this first time, so need to chk the threads first. This is my first Andriod phone and already ran into trouble after just 2 days of use, that too without any manual flashing. Only OTA happened before the issue.
Could the h/w have gone bad ?
In fastboot mode, the radio version is displayed correctly, but not after phone is up and running.
If the h/w has become faulty, I still expect the "Baseband version" in "About Phone" to be correct.
Is this assumption correct ? If it is s/w issue, I'm relived and I can try some custom image. So I'm hoping its only a s/w glitch.
Thanks a lot

you flashed the wrong rom on your phone and corrupted its efs partition. If you have a backup (why should you if you didn't even know that it was that to fail your phone's radio..) you could proceed and restore it. If you don't it's a big mess and you might have to go to a repair service.
Anyway you could still try and flash the original ROM for your phone and see if it fixes the problem. If not there are tools on the web (search the forums) that could try and restore your partition even if you don't have a backup.
If you succeed in restoring your phone don't EVER forget to backup you /efs partition

Thanks.
I tried flashing as the phone radio just stopped working after I charged the phone one day morning.
Let me follow your suggestions. I didn't know about efs partition. may be its messed up
What is puzzling me is, how can the factory images from google be wrong.
clait said:
you flashed the wrong rom on your phone and corrupted its efs partition. If you have a backup (why should you if you didn't even know that it was that to fail your phone's radio..) you could proceed and restore it. If you don't it's a big mess and you might have to go to a repair service.
Anyway you could still try and flash the original ROM for your phone and see if it fixes the problem. If not there are tools on the web (search the forums) that could try and restore your partition even if you don't have a backup.
If you succeed in restoring your phone don't EVER forget to backup you /efs partition
Click to expand...
Click to collapse

sanu.mathews said:
Thanks.
I tried flashing as the phone radio just stopped working after I charged the phone one day morning.
Let me follow your suggestions. I didn't know about efs partition. may be its messed up
What is puzzling me is, how can the factory images from google be wrong.
Click to expand...
Click to collapse
It's not the factory images to be wrong but the fact that if the /efs partition is really corrupted the stock images don't contain the info necessary to flash that partition as well.
In fact it may become corrupted after a wrong flashing but a new, correct, flash won't restore it. The only way back is the /efs backup.
What if you type *#06#? Does it show you an IMEI number or what?

*#06# shows "OK"
clait said:
It's not the factory images to be wrong but the fact that if the /efs partition is really corrupted the stock images don't contain the info necessary to flash that partition as well.
In fact it may become corrupted after a wrong flashing but a new, correct, flash won't restore it. The only way back is the /efs backup.
What if you type *#06#? Does it show you an IMEI number or what?
Click to expand...
Click to collapse

sanu.mathews said:
*#06# shows "OK"
Click to expand...
Click to collapse
Between the blue line and the OK it should show the sixteen digit long IMEI number. the fact that it isn't shown simplifies the diagnosis. I'm 100% sure you've got your /efs partition corrupted.
Please do a forum search on how to restore it.
Sent from my GT-I9300 using Tapatalk 2

Thanks a lot.
This eliminates so much un-wanted time waste/means no need to try various steps.
Can I get efs dump from another Galaxy nexus and flash it on mine after rooting ?
I'm under the impression that IEMI number etc should be in OTP and that can't get corrupted but efs may have some meta data regarding the same
clait said:
Between the blue line and the OK it should show the sixteen digit long IMEI number. the fact that it isn't shown simplifies the diagnosis. I'm 100% sure you've got your /efs partition corrupted.
Please do a forum search on how to restore it.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse

sanu.mathews said:
Can I get efs dump from another Galaxy nexus and flash it on mine after rooting ?
Click to expand...
Click to collapse
No can do, the IMEI is a per device unique number.
Check this thread and do some forum search: http://forum.xda-developers.com/showthread.php?t=1689525
You're not the only one that lost the IMEI so chances are likely to you to resolve your issue!

If I copy the IMEI number from the box or my working phone, will it work ?
What I want to know is, is it only coming from EFS or if IMEI is changed will be there be some signature that will fail etc
I have used fastboot but not sure about rooting, so need to read that before trying Rooting
In India, Samsung won't repair my phone as I got it from US.
Another worry is, let IMEI number be wrong and let there be no network, but atleast "Baseband version : Unknown" shdn't come in the phone, correct ? Coud there be any issue with radio image partition itself ?
clait said:
No can do, the IMEI is a per device unique number.
Check this thread and do some forum search: http://forum.xda-developers.com/showthread.php?t=1689525
You're not the only one that lost the IMEI so chances are likely to you to resolve your issue!
Click to expand...
Click to collapse

sanu.mathews said:
If I copy the IMEI number from the box or my working phone, will it work ?
What I want to know is, is it only coming from EFS or if IMEI is changed will be there be some signature that will fail etc
I have used fastboot but not sure about rooting, so need to read that before trying Rooting
In India, Samsung won't repair my phone as I got it from US.
Another worry is, let IMEI number be wrong and let there be no network, but atleast "Baseband version : Unknown" shdn't come in the phone, correct ? Coud there be any issue with radio image partition itself ?
Click to expand...
Click to collapse
Mate - I too am from India, and I too got the exact same problem, and I too tried all you did - all this about a month back. I have reconciled myself to the fact that its a hardware issue. Since samsung centers in India won't do any repairs, I'm afraid we're both stuck with really expensive music players.
My sympathies.

Fixed by sending in for warranty
Just an update...I was having all of these symptoms...unknown IMEI, Baseband, etc...basically gave me an expensive media player for a few months while waiting for a fix on XDA. After no update I decided to call up Samsung and after talking to 3 different technicians, I was able to send it in. Just a note for anyone about to do the same, they will try very hard to blame it on the carrier/SIM card, so save yourself some trouble and just say you already went to the physical store of your carrier (calling isn't enough)and they couldn't get it working. Once you get past that, they will email you a printable 2-day UPS shipping label so you can ship it to them for free. It took 2 weeks from the time I called to having a working phone back in my hands.
This was their fix:
Problem found:
NO PCS SERVICE
Solution:
REPLACED PBA
After a quick search I found that the PBA is the motherboard, so it's definitely a hardware issue. Hope you guys are still under warranty because I've heard this is ~$200 to fix otherwise.
Good luck.

[Q] Is my Galaxy Tap2 Bricked? Keep rebooting.....

Hi bro, i need some help here, suddenly my GT2 (GSM) will auto reboot after every 15-60 minute. It was running fine for the past 10 month since have install cyanogenmod cm-10.1.3.
The weird part is, not only it reboot, it will do a rollback to a fix setting every time it reboot.
- Let say, as a normal you have many application install, many photo or file in your phone
How it happen, as a normal user, I went to uninstall any application via application manager or Delete some photo from my gallery. It show success deleted..... but soon after few minute my phone rebooted by itself. After this reboot i notice what i just delete/remove come back again. Seems like there is a restore being done.
I also try to reset to setting using phone manager, and it fail
I try to boot in to recover mode, such as
clear data/factory reset
clear cache
go to advanced>wipr dalvic
Install cyanogenmod cm-10.1.3, cyanogenmod cm-10.1.2 or even cyanogenmod cm-10.1.1
I have try clear data/factory reset, clear cache, go to advanced>wipr dalvic
or any other combine setting i can think of.... it fail too
once i reboot my phone, it still went back to this Fix Setting, every thing just come back.....
even i select install new OS
Any ideas what happen?
Thanks

Look here for similar issue. Maybe move conversation there and see if together a solution is found.
http://forum.xda-developers.com/showthread.php?t=2859471
Sent from my Nexus 4 using XDA Premium HD app

Yes, it look simular to my issue, can you help PM me the step, so that will give it a try. Now i just been force to bought a new smart phone as my current not working.

Read about these issues from various thread, this is happened due to broken emmc. The only step will have to replace it.
If someone can developed a kernel to prevent this issue which is happen to omap4 device
Unfortunately most kernel, maybe all current kernel, did not apply this.

jak978 said:
Read about these issues from various thread, this is happened due to broken emmc. The only step will have to replace it.
If someone can developed a kernel to prevent this issue which is happen to omap4 device
Unfortunately most kernel, maybe all current kernel, did not apply this.
Click to expand...
Click to collapse
So this is due to broken emmc, and i need to ask someone to replace it at some cost
is there a way to check the issue is emmc or just some software/firmware/rom issue
Till now, my phone still stay the same, it will reboot after sometime. I even try to flash it with other ROMS and even update my phone with the latest CWM or PhilZ, i even get the message of update success/status ok. But after a reboot, my phone still went back/revert to that same "OLD" setting with every thing still there. Restore to factory still fail, look like my phone is as good as a brick phone...
Anyone know of a way to resolve it?

OTA update Fail, Save my data

Hi ~
- Be kind with me, it's my first post! -
I'm facing a very bad problem with my Galaxy S6. A week ago I received an OTA from Samsung and I installed it. My phone rebooted and showed the bugdroid, meaning that the update was progressing. After that, the device keep rebooting over and over just after I entered my encryption password. I said to myself that I can try to wipe the cache because maybe an application was causing this problem. But now, the device is only showing the Samsung logo then just shut himself off.
Now I need your help to get my data. The hard part is that my device is encrypted. After many hour of search I see two solutions:
Flash the rom via ODIN
Install TWRP which can read encrypted volumes
The first solution seems easy and I keep the warranty. The problem is that I'm not 100% sure that flashing the rom again will not touch the /data and /sdext partitions (and the header/footer where master key are to decrypt the volume).
The second solution seems safer and should not touch any other partitions. But knox counter will be incremented and I will loose my warranty.
So, does anyone could test if flashing the rom via ODIN do not absolutely touch encrypted volumes and certificate that I will be able to get my data again?
Thank you a lot

Have a leap of faith. Go ahead and flash. Otherwise bring it to Samsung for warranty repair. They may be able to recover your data for you.

roydok said:
Have a leap of faith. Go ahead and flash. Otherwise bring it to Samsung for warranty repair. They may be able to recover your data for you.
Click to expand...
Click to collapse
I want to be sure and I don't want to loose any photos if possible, so no
I already tried to go in a Samsung repair store (Allo PSM), but they just don't care about my data, their job is just to make the phone working again.

So Anyone is able to confirm to me that flashing stock Galaxy S6 ROM (AP Via Odin) doesn't touch the /data and /sdext partition that are encrypted?

After many hours of search, I was able to make my phone working again!
For anyone concerned by the problem in the future, here's some informations:
You can flash a stock rom, your encrypted /data will not be erased and you will be prompt to enter your password on the next boot
In my case flashing a newer rom didn't solve my problem (bootloop after entering the password of the encrypted partition). I had to flash the rom that was in the phone before the OTA.
Now everything seems to working again. No data were lost, all my configuration was saved. Android showed a message that a problem occurred during the upgrade process and I sent logs to Samsung, hoping that it will help them!