Related
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.
Hi,
I recently got my phone in a major problem while installing recovery using LGMDP. Right after that 'no sim card inserted' is flashing constantly flashing on my screen and I am not able to use my 'phone'. i had a backup of my phone's NV file. I tried to restore it using this and this but couldn't for dunno what reason. In frustration I later deleted all my files saved to fix this problem including my backed up NV file. Now before going to LG service centre to fix my phone, I want to make a final try to fix it myself.
Please help I need a NV file and definite method to restore it in my phone.
Thank You.
My phone will not recognize Verizon as its carrier or connect to a cellular network in any way. Settings > About Phone > Status > IMEI reads "0." I have, in some capacity, "lost" my IMEI.
I understand their are a lot of threads on this topic, however, I (unfortunately and ignorantly) have done a number of things after the actual losing of my IMEI and I am not sure the current state of my device or if a backup of my IMEI exists anywhere.
First my story. I successfully managed to get one of the early nightly builds of CM10.2 running on my phone and all was well. After updating to a more recent nightly via the CM updater, I noticed I had lost cell service in all capacity. Confused, I decided to not take any chances and revert to a CWM full backup I had made while still running CM10.1 stable. Still nothing. At this point, I thought that something was wrong with my firmware, and so I flashed a zip containing the latest Verizon firmware successfully (same that was installed previously). Nothing.
Not really understanding that one could lose their IMEI or the potentially signs of such loss, I decided to go all the way to stock via odin. The image did unlock the boot loader and grant SU, but did not wipe user data. Thinking it would help, I wiped data/factory reset within the stock recovery and then reflashed the image. Of course, still nothing. This is my current situation.
So my question is this: do I have any hope of recovering or "injecting" my IMEI? From my understanding, the Samsung mechanism designed to backup the IMEI in these such instances is broken. In fact, it probably "restored" it to a bogus null value. I think this means that I now have no IMEI information on my device. If so, does this mean I can manually inject it somehow? I have tried methods that purport to build the files on a pc and then move them to the device but I cannot access any of the Qualcom menu's that necessarily put the phone in a certain USB mode via the phone dialer. I get "no mobile network available."
Also: I still have my CM10.1 full CWM backup from before I lost my IMEI. If this backup contains the information needed to restore my IMEI, is their any way I can retrieve it? I think this is my best shot, but I'm not sure.
I would like to know if my new phone is a paperweight, since I am still within the 14 day return period. If I have indeed bricked my phone, there is a slim change that I can reset everything back to stock and play dumb with Verizon to get an exchange.
I apologize for the ambiguous vocabulary and/or description. I have a good working knowledge of most of the stuff on xda, but a lot of the language used in forums regarding IMEI restoration is foreign to me.
Thanks in advance for any help!
You have to Odin a stock ics image, or restore a backup if you have it, and dial *2767*3855#.
This should fix your imei and eri status by reprovisioning your phone.
Also as soon as you reroot and get up and running again, make an imei backup so you won't have to go back to stock if you have this issue again.
You could manually inject it, but a moderator has to grant you permission to use the thread. However, manually injecting it with qpst will leave your phone in roaming (not actually roaming, but the status icon won't go away) because it won't fix your eri number.
Use this option first, if it doesn't work you can try injecting it.
Sent from my SCH-I535 using Tapatalk 2
I used qpst to restore my imei and then used this method to get back without using odin, if you haven't already done so. I also think you can get your imei and eri back without using qpst with this method. I had already restored my imei and eri wasn't saying 5 like it should.
http://forum.xda-developers.com/showpost.php?p=44871571&postcount=3
Edit : I forgot, once you have your imei and eri restored and backed up. Don't forget to flash your modem back up to the version you want.
hey,one day my phone was going crazyand laggy.no sensors were working.So i decided to restore from Cwm backup i made earlier.After that my phone shows unknown baseband and imei and same sensor problem and also getting random reboots.
i have tried flashing factory images,deleting persist/sensors/sns file,but still facing the problems.
also in fastboot it shows me the baseband version but it is only in about phone where it says baseband unknown.
Any help would be greatly appreciated.
ak****gupta95 said:
hey,one day my phone was going crazyand laggy.no sensors were working.So i decided to restore from Cwm backup i made earlier.After that my phone shows unknown baseband and imei and same sensor problem and also getting random reboots.
i have tried flashing factory images,deleting persist/sensors/sns file,but still facing the problems.
also in fastboot it shows me the baseband version but it is only in about phone where it says baseband unknown.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
You flashed the full Google factory image (flash-all.batt) in fastboot and your issue still not solved? Do you see a Imei number when you type in dialpad *#06# and a Macadress in about the phone? Have you backed-up your EFS folder? Start with flashing the cache.img in fastboot (fastboot flash cache cache.img), that helps sometimes.
already done
gee2012 said:
You flashed the full Google factory image (flash-all.batt) in fastboot and your issue still not solved? Do you see a Imei number when you type in dialpad *#06# and a Macadress in about the phone? Have you backed-up your EFS folder? Start with flashing the cache.img in fastboot (fastboot flash cache cache.img), that helps sometimes.
Click to expand...
Click to collapse
yes i flashed full factory image several times.
no idon't see imei in dialpad.
yes i see a wifi mac adress.
No i have not backed up efs. but i dont think efs is the problem as it says unknown baseband.
yes i have also flashed cashe.img in fastboot.
ak****gupta95 said:
yes i flashed full factory image several times.
no idon't see imei in dialpad.
yes i see a wifi mac adress.
No i have not backed up efs. but i dont think efs is the problem as it says unknown baseband.
yes i have also flashed cashe.img in fastboot.
Click to expand...
Click to collapse
Can you still make calls?
gee2012 said:
Can you still make calls?
Click to expand...
Click to collapse
no i am unable to make calls.
ak****gupta95 said:
no i am unable to make calls.
Click to expand...
Click to collapse
Well, imo the EFS file is corrupted, you will need a new motherboard to fix the issue i`am afraid. Sorry mate, hope i`am wrong and maybe someone else has a different opinion that can help you
these are the exact symptoms of a corrupt EFS, and because you don't have a backup your phone is screwed and you will need a new motherboard. always backup EFS the moment you get your phone... That's what everybody says.
If I were you in this situation I'd salvage as many sellable parts of the phone (screen, battery etc), and use the money to buy a completely new phone. Otherwise I will just send it in for replacement
Sent from my Nexus 5 using Tapatalk
don't think efs messed up
I don't think that the efs is messed up.I only did a restore from backup.moreover I had never flashed any custom ROM on the device.I was running stock ROM with xposed and restored stock ROM.Also,the day this thing happened,I flashed factory image several times and was unable to fix the problem.However,the next day it became fine automatically and was showing baseband and imei.Then I just power off the phone.When I turned it on,I was again not able to see imei.Since then I have been unable to get imei back.
so here's my story:
I bought a used j7 prime. it had android 6.0.1 and it was working fine. even though it didn't seem rooted, the device status was custom and i couldn't get updates. so i downloaded android 7 firmware and i flashed it with Odin. the phone worked fine but i was getting the famous "not registered on network" error. I tried different solution that only made the phone worse. the last thing i tried was flashing an EFS folder ( i think ) that i downloaded through odin and the got messed up. so i flashed android 7 again but then my IMEI was unknown, so i rooted the phone and tried to restore the EFS folder that i had already backed up using EFS Professional, but i get an error message saying "unable to extract archive".
i have no idea what to do and i really need help.
thank you in advance.
nasralli said:
so here's my story:
I bought a used j7 prime. it had android 6.0.1 and it was working fine. even though it didn't seem rooted, the device status was custom and i couldn't get updates. so i downloaded android 7 firmware and i flashed it with Odin. the phone worked fine but i was getting the famous "not registered on network" error. I tried different solution that only made the phone worse. the last thing i tried was flashing an EFS folder ( i think ) that i downloaded through odin and the got messed up. so i flashed android 7 again but then my IMEI was unknown, so i rooted the phone and tried to restore the EFS folder that i had already backed up using EFS Professional, but i get an error message saying "unable to extract archive".
i have no idea what to do and i really need help.
thank you in advance.
Click to expand...
Click to collapse
Did you flash all Firmware (AP, BL,CSC,CP)?
AP, BL, CSC, CP is the new model for installing Firmware
hi
please flash this file with odin.https://drive.google.com/file/d/1TUXAQT4qJPZg9Qrt0ColKZQCxwW1mOG1/view?usp=drivesdk
for fix this problem use this way:
1. download and install partition backup program
https://drive.google.com/file/d/1XQf_jAZR164MI5kDbFPXLGBNKz56GgPY/view?usp=drivesdk
2. download efs image file(attention this file for j7 prime model only)
https://drive.google.com/file/d/1CxVhAxdmlpElo2gvKKNJ_cDrs2PTxByI/view?usp=drivesdk
3. download and exteract this help file for restor efs.img file with partition backup program on your phone.
https://drive.google.com/file/d/1V6UXQqxKMQ1bBXavUGoc8SkGjKDSXtHU/view?usp=drivesdk
I have the same problem on my SM-610F that I bought thinking that flashing would fix the prob.
It also says that the Device Status is custom and IMEI is unknown.
I didn't do any modification after buying it.
Just flashed TWRP by Odin and now it's it says Unable to mount /data.
Been searching for further fixes so far. ??
this happend to a lot, well just install any roms here you will get imei back.
Sent from my SM-G610F using XDA Labs
AmirRouichi said:
well just install any roms here you will get imei back.
Click to expand...
Click to collapse
Any rom means any Custom ROM? I've tried flashing the stock rom, but in vain.
Service Centre told me to send it back to Oman where it was brought from. ??
A S Ovin said:
Any rom means any Custom ROM? I've tried flashing the stock rom, but in vain.
Service Centre told me to send it back to Oman where it was brought from. ??
Click to expand...
Click to collapse
There are 2 ways to bring back the imei
1. you need to flash custom rom or stock rom ( Custom rom link: https://forum.xda-developers.com/t/therealrom-pure-edition-g610x-9.4009347/
Note: Before installation remove the sim. One installation done and reboot the system and once home screen comes insert the sim)
2. one more method is there try once it may helpful for you. First remove the sim from the device. Do network setting reset in the Settings->About-> Reset option-> Select only Network and wifi reset. Note this will erase your saved network passwords. Then install google dialer from playstore. Run the below code *#*#27262826#*#* in google dialer. A screen will come to install CSC features. In the first drop down select the country you want (for india select INS) and submit. Reboot the system. After completion insert the sim and enjoy ur mobile network. It will work for VOLTE. If above code doesn't pop up that option then u need to install rom again.
do it this only in
A S Ovin said:
I have the same problem on my SM-610F that I bought thinking that flashing would fix the prob.
It also says that the Device Status is custom and IMEI is unknown.
I didn't do any modification after buying it.
Just flashed TWRP by Odin and now it's it says Unable to mount /data.
Been searching for further fixes so far. ??
Click to expand...
Click to collapse
About the /data thing. Go to TWRP, select wipe, advanced wipe, click on data, select Repair or Change File System, Change File System, Choose EXT3, let it do. Then go to home screen, and do the same but choose EXT4. You can now access your data until you reboot to Stock ROM or any OneUI/TouchWiz based ROM.
This happens as Samsung encrypts(?) the /data partition. About the IMEI, the factory effed up. You need to send it back to where you bought it and seek replacement.