Related
Im having an issue after flashing my phone to GB 2.3.3 my service cant be recognized under the about phone gives me the correct os and build but the baseband and IMEI are unknown. I followed these steps correctly and i cant figure out my problem. Link below is what i used.
http://androidadvices.com/how-to-update-samsung-galaxy-s-4g-to-gingerbread-2-3-3-firmware/
did you back up your efs folder?
this problem more than likely pertains to the fact that your efs folder got wiped somehow during the flash the only way to fix it is with the backup
Yeah i fixed it! thanks
I just had this happen to me but I don't have my efs folder backed up. Will a nandroid backup fix it if not how can I unroot it so I can send it into tmobile?
Edit: Didn't work I'm going to have to unroot this I have KB5 on now since it was the only froyo non deodexed rom I could find but I can't seem to get superoneclick to unroot it.
Edit2: All I need is a rom suitable for turning the phone into tmobile to get an exchange done.
Is there anyway to get the the unknown IMEI and baseband back to normal and if not can someone please help me unroot the phone because superoneclick isn't working?
Compxpert said:
Is there anyway to get the the unknown IMEI and baseband back to normal and if not can someone please help me unroot the phone because superoneclick isn't working?
Click to expand...
Click to collapse
ive had the same thing happen to me. odin back to a froyo rom then do the gingergread ext4 starter pack found in the dev section. i used kd1 as my froyo hope this helps.
mongo41 said:
ive had the same thing happen to me. odin back to a froyo rom then do the gingergread ext4 starter pack found in the dev section. i used kd1 as my froyo hope this helps.
Click to expand...
Click to collapse
This didn't resolve my issue still no signal, baseband unknown, and IMEI unknown. I also used kd1 as my froyo.
Flashed on stock nondeodexed KB5 and unrooted it with superoneclick so its ready for handset exchange.
i just bought this phone on craigslist and its having the same baseband unkwon problem has anyone figured out a fix for this yet?
krise11385 said:
i just bought this phone on craigslist and its having the same baseband unkwon problem has anyone figured out a fix for this yet?
Click to expand...
Click to collapse
Is it just the baseband or do you also have a missing/unknown/bad IMEI?
Battery pull for 10 min or more? Other threads on the same topic suggest it.
Sent from my SGH-T959V using XDA App
Guys, you may want to try this before going forward with anything hard...
So, this same thing happened to me. I had Valhalla Black flashed on my phone, it started to glitch (reloading the home screen every 3 seconds or so and not loading any apps), so I did a CWM restore and it went into a boot loop (the splash screen would freeze and never load the ROM).
So, I used Heimdall One-Click to flash the stock Gingerbread ROM, and my IMEI/etc were all unknown. I saw all these options to use hex editors and stuff to redo the nv_data.bin file and was just about to do them...but...
I decided to check and see if it was the SIM card that went haywire. I put the SIM into another phone and the phone ended up getting service, so I thought, "Oh, sh**, I'm screwed...I'm going to have to do all this IMEI repair stuff..."
In the end, I put the SIM back into my t959v after taking it out of the old phone I was checking it with...AND BAM, IT WORKED! IMEI and everything are back and I'm getting service.
Point of the story: check your SIM card in another phone and see if you get service, then put it back in your other phone and see if you get service again.
FU** YEAH!!! No tough stuff afterall! Reflashing Valhalla Black and restoring apps, settings, etc. from Titanium...
Loaded cm10 20120927 last night and all ran good. no data drops or anything. i ram cyanogenmod backup this morning and on reboot no imei or anything. good that i backup it up to my sdcard and to dropbox.
if one of the MODS would like to move this to the development forum thats ok. i know that if wouldn't matter because cm10 probably didnt cause the imei loss.
Edit: I took a chance and rebooted again hoping that it was just something sbout the reboot and imei, phone number etc etc is back. Good for me, but not sure I have read of this happening. Anyway, all is good now.
ef-civic said:
Loaded cm10 20120927 last night and all ran good. no data drops or anything. i ram cyanogenmod backup this morning and on reboot no imei or anything. good that i backup it up to my sdcard and to dropbox.
if one of the MODS would like to move this to the development forum thats ok. i know that if wouldn't matter because cm10 probably didnt cause the imei loss.
Edit: I took a chance and rebooted again hoping that it was just something sbout the reboot and imei, phone number etc etc is back. Good for me, but not sure I have read of this happening. Anyway, all is good now.
Click to expand...
Click to collapse
Did you not back up your IMEI via ADB?
stargate125645 said:
Did you not back up your IMEI via ADB?
Click to expand...
Click to collapse
yes I did
I'm not sure why you made this thread though if you had your imei backed up and it came back after a reboot. I lost mine 3-4 times and it came back each time after a reboot, I never had to recover from my backup yet though.
Installed JB ROM on S3 Verizon - not connecting to network
Any suggestion on how to fix this this issue.
I install a JB rom last night, but it seemed like it deleted the IMEI number off the phone. Through the forums, I was able to restore ( I didn't not back Up IMEI - i know) the IMEI number back on the cell phone.
However, the phone is unable to register to the Verizon network. I have an inside Verizon guy, who helped associate, on his end, my IMEI number to my account/ sim card. still not connecting. has any one else got this problem, and able to resolve?
I should be getting a new Sim Card tonight, hoping that might resolve the issue, if not, I will call Verizon Warranty to get a new phone.
PS. on verizonwireless, it shows that Samsung S3 is associated with my SIM/ telephone number.
thanks for any suggestion or help in advance.
jaimanny said:
Any suggestion on how to fix this this issue.
I install a JB rom last night, but it seemed like it deleted the IMEI number off the phone. Through the forums, I was able to restore ( I didn't not back Up IMEI - i know) the IMEI number back on the cell phone.
However, the phone is unable to register to the Verizon network. I have an inside Verizon guy, who helped associate, on his end, my IMEI number to my account/ sim card. still not connecting. has any one else got this problem, and able to resolve?
I should be getting a new Sim Card tonight, hoping that might resolve the issue, if not, I will call Verizon Warranty to get a new phone.
PS. on verizonwireless, it shows that Samsung S3 is associated with my SIM/ telephone number.
thanks for any suggestion or help in advance.
Click to expand...
Click to collapse
There's a link in my signature for "IMEI Repair" click that and you can fix the problem
jaimanny said:
Any suggestion on how to fix this this issue.
I install a JB rom last night, but it seemed like it deleted the IMEI number off the phone. Through the forums, I was able to restore ( I didn't not back Up IMEI - i know) the IMEI number back on the cell phone.
However, the phone is unable to register to the Verizon network. I have an inside Verizon guy, who helped associate, on his end, my IMEI number to my account/ sim card. still not connecting. has any one else got this problem, and able to resolve?
I should be getting a new Sim Card tonight, hoping that might resolve the issue, if not, I will call Verizon Warranty to get a new phone.
PS. on verizonwireless, it shows that Samsung S3 is associated with my SIM/ telephone number.
thanks for any suggestion or help in advance.
Click to expand...
Click to collapse
Reprovision on the stock rom.
con247 said:
Reprovision on the stock rom.
Click to expand...
Click to collapse
This! Dialer code *2767*3855#
droidstyle said:
This! Dialer code *2767*3855#
Click to expand...
Click to collapse
yup, that worked. I thought I did that earlier with my verizon guy. Maybe it took time to sync up..
anyway thank you for your help.
thanks con247, and droidstyle.
So I recently flashed the CM10 M2 rom on my verizon GS3 and it worked good for a week. Now I can't get any service on the phone.(calls, internet, etc).
I flashed it back to bone stock using Odin and still didn't do the trick. I thought it might be the SIM card but I tested it with my old Droid Razr and it worked fine. Any solutions? I really want this phone functioning again. thank you
Kinda new to Samsung and Verizon but from what I read, u may have list your imei, you can look up tutorials on you tube on how to restore it if u backed it up, or how to install default ones. Happened to me and I had to do a factory reset and re root
Sent from my PC36100 using xda premium
chupafaros said:
Kinda new to Samsung and Verizon but from what I read, u may have list your imei, you can look up tutorials on you tube on how to restore it if u backed it up, or how to install default ones. Happened to me and I had to do a factory reset and re root
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
wasn't sure on how to restore default imei. I did an unroot and re-root and still didnt work. still need help
still in need of help I noticed my IMEI was at 0 so went through a long process to restore it. Now I do have a number under "IMEI" but mobile network still isn't working. I'm currently running stock everything. please and thank you
Well if your like me, you now believe you have a $700 brick. Well I had t he same issue, and I'm rolling done the highway typing this post on my phone. Just fixed it today in fact. This is what I did to fix it. I have a vzw sgs3. Flash it to stock. Flash stock modem fw. Search the forum for restore imei guide tool. Follo those instructions and you'll download a file with a panda icon. after that, when it turns on you will still have no service. This is ok. Search the forums for SIM reprovision. One of the posts tells you to back up everthing including your internal sd. Do that if you want your stuff. Then it will tell you to dial *2767*8858#. (I know these are the wrong numbers but they are in the *xxxx*xxxx# format and it starts with *27.) This should do it.when it reboots it's like a factory reset. But it fixes it. Oh and I also had Verizon give me a new SIM. To 're cap... search Guide imei restore tool and SIM provision.hope this helps.
mrfishjosh said:
Well if your like me, you now believe you have a $700 brick. Well I had t he same issue, and I'm rolling done the highway typing this post on my phone. Just fixed it today in fact. This is what I did to fix it. I have a vzw sgs3. Flash it to stock. Flash stock modem fw. Search the forum for restore imei guide tool. Follo those instructions and you'll download a file with a panda icon. after that, when it turns on you will still have no service. This is ok. Search the forums for SIM reprovision. One of the posts tells you to back up everthing including your internal sd. Do that if you want your stuff. Then it will tell you to dial *2767*8858#. (I know these are the wrong numbers but they are in the *xxxx*xxxx# format and it starts with *27.) This should do it.when it reboots it's like a factory reset. But it fixes it. Oh and I also had Verizon give me a new SIM. To 're cap... search Guide imei restore tool and SIM provision.hope this helps.
Click to expand...
Click to collapse
I would like to first thank you for your input. Although i had that panda icon program i used a different program to restore my imei as well as my eri. After doing that i thought i finally fixed it then realized im still missing some of the numbers under phone status such as MIN. PRL version and ICCID. does the sim reprovision fix this.
Thank you all who have gave me advice to fix this problem. I finally got it fixed and i can't be happier. After going through circles restoring my IMEI and PRL it still wasn't working. What did the trick was dialing *2767*3855# which did a factory reset. My mobile is working again!!!!!!!!!!!!!:highfive:
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.
Hello,
I started with Galaxy Note 2- i317M (rogers, canada), rooted with DN3 V4 beta installed. But I wanted to try DN4, so I created a back-up using TWRP and tried installing DN4. However, I later realized that it is not for the LTE versions yet and phone did not recognize SIM anymore. So I wiped the data and tried installing dn3 v5.5, but the phone still did not connect.
Losing all hope I installed DNv4 again, but it still did not work. So i finally just tried restoring from the back-up I made using TWRP. Everything in the phone is same except no network.
Finally I tried restoring from back-up after doing a complete wipe of internal storage and everything except the external card. But still the error does not go away. I researched more about the error and the fact that my imei shows up as null/null. I used the instructions of using EFS professional, but it did not work. The model number in my phone now shows up as SM-G900F and baseband shows as unknown, and it shows DN3V5 Rom despite the clean-up and restoring from DN3V4.
Any guidance available on this please...I need specific steps because after 12 hour search and try-outs I am lost now.....
UPDATE:
Solved it! Here is the solution for anyone in this problem
http://forum.xda-developers.com/showpost.php?p=46231268&postcount=4
worked like a charm.. No reason to throw this and get a new phone
I have had this problem. It didn't happen whilst flashing though. My imei number is now a generic one and I had no efs backup. After 5 days of trying everything I can find I'm giving up. My note 2 is dead as far as I'm concerned. As far as I'm aware to get my imei back I'll have to send it for repair so I'll buy another phone and not a Samsung
I don`t think your phones are dead. I didn`t try it personally, but I`m sure you can restore your EFS back. Just you need to do some research, maybe you could start here:
https://www.google.ro/?gws_rd=ssl#safe=off&q=how+to+recover+efs+folder
Do not give up, read on end you will eventually do it! And, by the way, next time maybe you don`t forget to back up before doing anything to your phone!
nmugurel2003 said:
I don`t think your phones are dead. I didn`t try it personally, but I`m sure you can restore your EFS back. Just you need to do some research, maybe you could start here:
https://www.google.ro/?gws_rd=ssl#safe=off&q=how+to+recover+efs+folder
Do not give up, read on end you will eventually do it! And, by the way, next time maybe you don`t forget to back up before doing anything to your phone!
Click to expand...
Click to collapse
I did back up. with both titanium backup and twrp but it is not working. And I dont think I will give up. I will format is all together and start over if i have to.
Do you think it will work if I format it entirely and start over?
dexterousyash said:
I did back up. with both titanium backup and twrp but it is not working. And I dont think I will give up. I will format is all together and start over if i have to.
Do you think it will work if I format it entirely and start over?
Click to expand...
Click to collapse
Glad to see you solved it!