Intro
The info on how to do this is scattered around, thought it might be good to have a post for this, was really annoying for me to get this fixed
Problem
After upgrading to the latest Cyanogenmod 10.1 (cm-10.1-20121224-NIGHTLY-d2vzw.zip), the phone will not connect to the cell network. Some symptoms of this:
- Cannot send/receive text messages
- Cannot make calls, all calls give error "Your account is not authorized to make calls to this phone number"
- On boot, activation starts ("Waiting for network...") but cannot complete
- In Settings -> About Phone -> Status, you see the following info:
-- Roaming: Roaming
-- Mobile Network State: Disconnected
-- My phone number : 000-000-0311 (or similar)
Solution
I tried a number of solutions, but the only way I've seen to fix this is to revert to stock ICS using Odin, then perform a full factory reset. Please note that you will lose ALL data, including anything on the internal storage. The SD card should not be touched. You will also lose your unlocked bootloader, although that is easily restored.
1. BACK UP any data you might need, including clockwork/titanium backups, get them off your phone
2. Follow instructions here to flash the rooted ICS image (stock.vzw_root66.tar) using Odin. The torrent is much faster to download the image.
3. If your phone goes into a boot loop (stuck on the LTE boot logo), boot into stock recovery (Vol Up + Home + Power) and clear data / factory reset
4. Boot up the phone, go into the dialer, type: *2767*3855#
5. Your phone will immediately factory reset itself
You should now have cell connectivity again, and should also have root. You can then unlock your bootloader (get v1.2 here) and finally use Clockwork to re-install another ROM.
Note that after doing the above to restore my cell connectivity, I tried to do a clean install of CM 10.1, with full data wipe and such, and I once again lost cell connectivity and had to factory reset again. It seems to me like something is very broken with CM 10.1 for the VZ S3, and until it's figured out I recommend staying with CM 10.0 (cm-10-20121216-NIGHTLY-d2vzw.zip), which does not appear to have this problem.
funkymonk101 said:
Intro
The info on how to do this is scattered around, thought it might be good to have a post for this, was really annoying for me to get this fixed
Problem
After upgrading to the latest Cyanogenmod 10.1 (cm-10.1-20121224-NIGHTLY-d2vzw.zip), the phone will not connect to the cell network. Some symptoms of this:
- Cannot send/receive text messages
- Cannot make calls, all calls give error "Your account is not authorized to make calls to this phone number"
- On boot, activation starts ("Waiting for network...") but cannot complete
- In Settings -> About Phone -> Status, you see the following info:
-- Roaming: Roaming
-- Mobile Network State: Disconnected
-- My phone number : 000-000-0311 (or similar)
Solution
I tried a number of solutions, but the only way I've seen to fix this is to revert to stock ICS using Odin, then perform a full factory reset. Please note that you will lose ALL data, including anything on the internal storage. The SD card should not be touched. You will also lose your unlocked bootloader, although that is easily restored.
1. BACK UP any data you might need, including clockwork/titanium backups, get them off your phone
2. Follow instructions here to flash the rooted ICS image (stock.vzw_root66.tar) using Odin. The torrent is much faster to download the image.
3. If your phone goes into a boot loop (stuck on the LTE boot logo), boot into stock recovery (Vol Up + Home + Power) and clear data / factory reset
4. Boot up the phone, go into the dialer, type: *2767*3855#
5. Your phone will immediately factory reset itself
You should now have cell connectivity again, and should also have root. You can then unlock your bootloader (get v1.2 here) and finally use Clockwork to re-install another ROM.
Note that after doing the above to restore my cell connectivity, I tried to do a clean install of CM 10.1, with full data wipe and such, and I once again lost cell connectivity and had to factory reset again. It seems to me like something is very broken with CM 10.1 for the VZ S3, and until it's figured out I recommend staying with CM 10.0 (cm-10-20121216-NIGHTLY-d2vzw.zip), which does not appear to have this problem.
Click to expand...
Click to collapse
easier way is If you remove ur sim card and boot up and connect via wifi, u can then register and set up the phone. then shut down put sim card back in and boot up. go to system settings -> More... under wireless and networks -> mobile networks -> CDMA subscription and choose RUIM/SIM (NOT NV)
This should now let the ur phone have access to the network and get rid of the roaming issue.
Same problem
Having this exact problem. My problem is I do not have access to a windows computer and thus cannot use Odin. I have already performed a Factory reset so I may try the way that involves removing the sim card. I dont know how more people haven't posted on this yet...
---------- Post added at 05:48 PM ---------- Previous post was at 05:34 PM ----------
rossida said:
easier way is If you remove ur sim card and boot up and connect via wifi, u can then register and set up the phone. then shut down put sim card back in and boot up. go to system settings -> More... under wireless and networks -> mobile networks -> CDMA subscription and choose RUIM/SIM (NOT NV)
This should now let the ur phone have access to the network and get rid of the roaming issue.
Click to expand...
Click to collapse
as far as I can tell this does not work. You must have a sim card to get past the second screen in boot up. There is no other option besides to turn of your phone.
Thank you for the help! My phone as been out of commission for the past 2 days and the OP directions fixed it. However the second post did nothing to help out. Worth a shot though
Does anyone know if this can be done from a Mac?? I am a little desperate here. Ive spent most of Christmas day messing with this.
You'll have to find a Windows computer, or install a windows virtual machine using vmware fusion or parallels desktop.
will this work for us cellular??
rossida said:
easier way is If you remove ur sim card and boot up and connect via wifi, u can then register and set up the phone. then shut down put sim card back in and boot up. go to system settings -> More... under wireless and networks -> mobile networks -> CDMA subscription and choose RUIM/SIM (NOT NV)
This should now let the ur phone have access to the network and get rid of the roaming issue.
Click to expand...
Click to collapse
This has happened to me twice. The second time I used this method and it worked for me. It was only successful when I switched to the executioner 2.5 rom which was on my sd card. Thanks!
Nvm fixed it
*wrong thread*
killerkiyoshi said:
Nvm fixed it
Click to expand...
Click to collapse
How???
Okay, finally have my service back in stock touchwiz. This is what I did for anyone that cares to know: In CM10 during "activation" I pulled my sim card out, let it finish activating, powered down put sim card back in. Then I booted it back up and went to system settings -> More... under wireless and networks -> mobile networks -> CDMA subscription and choose RUIM/SIM (NOT NV). THEN I did a factory reset in CM10 making it look as if I had just flashed it again. Then I booted into recovery and went back to stock TouchWiz where my 4g LTE came back magically and I could call and place texts. Not really any rhyme or reason but my service is back and I am beyond pleased. I am very nervous to flash any roms as of now I might wait til tomorrow luckily I have all my stuff backed up Hopefully it stays this way. Message me with any questions and I will help as much as I can. Merry Christmas
pupsinmytub said:
Okay, finally have my service back in stock touchwiz. This is what I did for anyone that cares to know: In CM10 during "activation" I pulled my sim card out, let it finish activating, powered down put sim card back in. Then I booted it back up and went to system settings -> More... under wireless and networks -> mobile networks -> CDMA subscription and choose RUIM/SIM (NOT NV). THEN I did a factory reset in CM10 making it look as if I had just flashed it again. Then I booted into recovery and went back to stock TouchWiz where my 4g LTE came back magically and I could call and place texts. Not really any rhyme or reason but my service is back and I am beyond pleased. I am very nervous to flash any roms as of now I might wait til tomorrow luckily I have all my stuff backed up Hopefully it stays this way. Message me with any questions and I will help as much as I can. Merry Christmas
Click to expand...
Click to collapse
Yall all need to chill out. Just fix your mobile network settings, toggle airplane mode, and you'll be fine.
You have no reason to fear flashing any roms.... With common sense.
Sent from my SCH-I535 using xda app-developers app
Flash cm10.1 go to settings/networks/cdma subscriptions and change it back to RUIM/SIM. U haz data now. :thumbup:
Sent from my SCH-I535 using xda app-developers app
None of this has worked for me. I have followed the post directions and still have roaming. I am not seeing this option some of you are talking about though " wireless and networks -> mobile networks -> CDMA subscription and choose RUIM/SIM (NOT NV)"... is this option supposed to be in the stock ics rom?
Update: the line had been suspended for some very odd reason
Got it working on VZW SG3 for now
This worked for me:
Reboot to recovery and fix permissions (not sure if this step helped just following some other posts) --> change mobile networks to the sim option ---> and most importantly enable National Data Roaming (this is the step that kicked over my signal)
After doing this it has started to let me call out and receive sms. My only concern is what consequences will i have with the national data roaming enabled and secondly when I am in other networks if I will get better signal; i live in a small town and get 1x so I have no idea what will happen till i get into the city but this seems to be a good fix for now. Hope this helps.
Tried all posted solutions and then some, still can't get CM 10.1 working on d2vzw
All,
I have a stock-rooted SCH-I535, and am also unable to get CM 10.1 working without losing the voice connection. It appears that my problem is corrupted NVRAM. Although my IMEI remains correct after flashing 10.1, my phone number and other info (ERI) gets corrupted. After a day of anxious attempts to fix the phone, the only fix I've found is flashing root66 (after which the phone still doesn't boot to the OS), factory reset (allows phone to boot), and then dialing factory-reset code *2767*3855#. For some reason the dialer-initiated reset seems to fix the NVRAM issue while the recovery-initiated reset does not.
After figuring out how to fix the problem, I've tried a handful of ways to get CM 10.1 working properly.
Original try: flash 10.1 over rooted-VRBLK1 using TWRP 2.3.1. After fixing by flashing root66, recovery factory-reset, and dialer factory-reset, I was nervous and made a couple backups.
used the su ; reboot nvbackup commands in this RootzWiki post.
Made a QPST backup with the instructions in this XDA post.
2nd try: factory reset, wipe data/system partitions, re-flash 10.1 with TWRP. This attempt had the same roaming/corrupted phone info result, but this time I was confident because I was armed with the two backup methods above.
I tried using the Samsung MEID RepairV3.5 in this XDA thread, but it wouldn't connect to the phone running CM10.1. I've gotten that tool to connect to the root66 image, so I know I'm following the procedure correctly. However, the developer specifically states that the tool is intended for stock images, so I wasn't surprised that it failed to work on CM 10.1.
with su privilages, I used terminal command "reboot nvrestore". I expected this to work, but it resulted in an unbootable OS. I had to flash root66 and repeat the fix process described at top.
Third try: flashed 10.1 again with TWRP 2.3.1. I tried using the QPST recovery I had created earlier. I got the phone into diagnostic mode (RMNET+DM+MODEM) using terminal commands for AOSP ROMs. For some reason I couldn't get the scripts to work, even with full permissions in the "root" directory -- the script resulted in the phone disconnecting from my computer in MTP mode, but it didn't connect in diagnostic mode. Terminal commands did the trick though -- I may be making some n00b mistake with the scripts. After typing the commands in manually and connecting to QPST, when I told QPST to "restore" the backup, it gave me an error message with incompatible phone, and if I checked the "allow phone/file ESN mismatch" box, the restore failed because the phone didn't respond to the QPST commands. I'm sure the phone was in diagnostic mode because it came up under Device Manager "ports" as depicted in the QPST instructions, so it seems like the corrupted NVRAM was causing problems with making a QPST connection.
Fourth try: TWRP update to 2.3.3.0. Same results as 2.3.1.0.
Fifth try: switch to clockworkmod touch recovery 6.0.2.3. Same result as both TWRP versions.
So, I'm pretty frustrated. I have the phone back up and running rooted-stock VRBLK3. I'd really like to get JB4.2 though, so if anyone can ID the problem, please post! I hope it's a simple fix from a n00b mistake, but after all the fruitless effort above, I expect that it's a more significant issue.
One last thought: I always rebooted into recovery to install the 10.1 image, and I never tried using the ClockworkMod ROM Manager or TWRP-compatible GooManager apps. My wife is tired of me spending the holiday weekend hunkered over my phone, so if anyone wants to try that route please let me know if it works.
The only other idea I have is to install 10.1, then try flashing the VRBLK3 baseband by itself. Again, I don't have the time to pursue this idea (or expertise to know if it's a good one), so any good insight would be appreciated. One last thought: personally, I'm not willing to wander around in voice or data "roaming" even if everything else is working fine. I rely on this phone for daily use, and am not comfortable without the radios working normally.
Happy new year!
thank you. can confrim this method to work for a verity of roms. ha.
vabeachfc3s said:
Flash cm10.1 go to settings/networks/cdma subscriptions and change it back to RUIM/SIM. U haz data now. :thumbup:
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
This worked, just reboot the phone after you make this change and you'll have your activated phone back with voice/data. :good:
No Service
I flashed CM10.1-m a few days ago (using this method to root and unlock bootloader http://forum.xda-developers.com/show....php?t=2046439 then flashing CM10.1-m through Odin), and my phone worked flawlessly for 2 days. It started to lag a bit during swipe-style text entry (no tracing line or predictive words appeared), so I rebooted hoping to fix the problem.
After reboot I lost all verizon service. The phone said "No Signal" or "Emergency Calls Only." The phone would not identify a mobile network, and no option for CDMA/LTE was available under mobile network settings, although verizon APN's were still identified. I think I lost my IMEI/EFS but don't know enough to be sure.
First I flashed stock VRALG1 android 4.0.4 without success. However after I flashed stock VRBLK3 android 4.1.1 my verizon service was restored.
I would really like to figure out how to keep CM10.1... touchwhiz is awful. Can someone confirm this problem can be fixed through one of the following methods? http://forum.xda-developers.com/showpost.php?p=35600769&postcount=2&nocache=1
Also don't want to trip my flash counter... any idea at what point this would happen?
Hello ladies and gents,
I purchased my girl an s3 and she has been running stock rooted for a while and wanted to try something different so I flashed cm10.1. I factory reset, cleared system, and caches. Then flashed the rom via trwrp 2.3.3 flashed gaps. Everything went successful but she lost all data. I read that it was fixed but I had to Odin root66 and dial that code to do another reset.
What can I do differently that won't lose data next time? The Verizon s3 seems more temperamental than my T-Mobile s3.
Sent from my SGH-T999 using Tapatalk 2
First thing to always do is read the OP for bugs I'm pretty sure he explained the loss of data and how to fix it.
Second would be to research the ROM you are flashing by reading comments from other flashers.
Last would be waiting for a stable version of the ROM to be uploaded.
Have fun and flash with the speed of light
But the things is I did all of those things. I am no stranger to rooting and crack flashing. I'm saying they said the data bug was fixed as of 12/24, I flashed 1/19 and it still broke data. But I guess I'll just lurk the thread... my bad for asking a question in the q/a forum...
Sent from my SGH-T999 using Tapatalk 2
Here's all the info I: have saved in case I come across this problem (again)
Fixing Data
If you flashed a CM10.1 nightly and are stuck at roaming/activating or don't have data, try any of the following (in order of simplicity):
(1) Go into Mobile Settings - Mobile Networks. Change CDMA mode to RUIM, go into airplane mode, come out, it should login to 4g in a minute. You can wait for activating to time out then skip or not install gapps until after setting the correct mobile network setting.
(2) Power down. Take out the sim card and reboot. In mobile network settings set roaming to auto and the subscription to RUIM/SIM, turn off the phone, pop the sim card back in, boot up.
If none of those work this will work for sure:
Originally Posted by Deevious88
Hallelujah! My phone has voice AND data back! (thanks to the posters above)
How to get voice AND data back:
1.) Odin the root66.tar file from http://forum.xda-developers.com/show....php?t=1762204 (the torrent version downloads MUCH faster)
2.) Open the dialer and enter *2767*3855#
3.) DONE! Voice and data should be fixed (it fixed it for me at least, and I had tried EVERYTHING else)
From there just Odin back to Jellybean following http://forum.xda-developers.com/show....php?t=1974114 and you're golden...
That's how to get back to working condition without fail... Might want to post similar instructions in the OP as dirty flashing did nothing for quite a few of us.
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Fixing GPS
Originally Posted by invisiblek
GPS - it HAS been working for 98% of builds, however if you cannot get GPS to connect, possibly due to dirty flashing, the following has worked every build for me: Settings - Apps - downloaded - GPS Status - clear cache, clear data, force stop. Then open gps status back up, let it sit with gps on for a moment and see if it starts searching for signal again....if this still doesn't work (sometimes) - settings - apps - all - google services framework - clear data. This has worked 100% of the time but I try to avoid it because if you do this, you need to go open back up the play store and see if it still connects. If not, recovery - clear cache, clear dalvik usually takes care of that.
Clean install of builds has given me 100% functional gps every time.
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Unofficial CM10.1
(I know several people have posted these, I looked quickly and only found mastamoon's which is also what I am running, I'll happily post more here if I find them).
mastamoon http://d-h.st/users/mastamoon
invisiblek http://rootzwiki.com/topic/35602-rom...0#entry1058210
aerovan http://rootzwiki.com/topic/37216-uno...zw-2012-12-18/
First do this: change your CDMA Subscription to RUIM/SIM then your Roaming Mode to Automatic and then reboot.
If doesn't work, try: restoring IMEI and then Odin back to stock.
The RUIM method mentioned prior has always been what fixed my problem when experiencing the same issue as you. Also, definitely back up your IMEI if you have not yet.
I'm kind of worried at this point. After looking through some threads I found with a search for a similar problem I'm going to make my own.
Problem: No data at all. About section of phone says:
Network: Unknown
Mobile network type: Unknown
Service state: Out of service
Mobile network state: disconnected
I do still have an IMEI.
It happened in the middle of normal operation, browsing the web with stock browser with CM10.1 (4.2) with the 1/20 nightly.
What I've tried: Already reset SIM card, toggled Mobile Data and everything data related I can find in the Settings menu. I've data wiped and flashed the same nightly through recovery along with the same gapps .zip that was all working halfway through the day. I got home from work and tried using Odin to flash back to a pre-rooted full wipe 4.1.1 ROM found using this thread: http://forum.xda-developers.com/showthread.php?t=1984436
The first time it booted up to the stock startup screen and just hung. Cleared data through recovery, booted into Odin and tried again and it booted up, but still no data. That's where I am now. I just don't know what else to try. I see some stock radio flash instructions but I'm really not sure what that accomplishes if I'm already flashing stock ROMs. The trouble is I know just enough about this to break stuff.
Does anyone have any recommendations or ideas?
hextlol said:
I'm kind of worried at this point. After looking through some threads I found with a search for a similar problem I'm going to make my own.
Problem: No data at all. About section of phone says:
Network: Unknown
Mobile network type: Unknown
Service state: Out of service
Mobile network state: disconnected
I do still have an IMEI.
It happened in the middle of normal operation, browsing the web with stock browser with CM10.1 (4.2) with the 1/20 nightly.
What I've tried: Already reset SIM card, toggled Mobile Data and everything data related I can find in the Settings menu. I've data wiped and flashed the same nightly through recovery along with the same gapps .zip that was all working halfway through the day. I got home from work and tried using Odin to flash back to a pre-rooted full wipe 4.1.1 ROM found using this thread: http://forum.xda-developers.com/showthread.php?t=1984436
The first time it booted up to the stock startup screen and just hung. Cleared data through recovery, booted into Odin and tried again and it booted up, but still no data. That's where I am now. I just don't know what else to try. I see some stock radio flash instructions but I'm really not sure what that accomplishes if I'm already flashing stock ROMs. The trouble is I know just enough about this to break stuff.
Does anyone have any recommendations or ideas?
Click to expand...
Click to collapse
SOLUTION: Settings > Mobile Network > Network Mode - was set to GSM/UMTS in 4.1.1 pre-rooted ROM. changed to LTE/CDMA and resolved. Can't believe I overlooked that.
Thanks.
Been trying to figure out this problem but can't. Was running Carbonrom 4.3. Was updating to TWRP 2.6.3.0 using terminal emulator (using instructions from the twrp site). rebooted phone after update. That's when the problem arise -- could not make any phone calls.
What I've done:
1 - restored my prior backups (synergy, beanstock, cleanrom) -- did not resolve problem. Has data access, but cannot make or receive phone calls.
2 - re-installed roms from scratch (after full wipes, including format of internal storage/data) -- same result.
3 - checked my IMEI - it's valid, and matches the back of phone.
4 - checked my mobile network setting: cdma/lte/evdo
5 - again, Data works fine: I can surf the web, access Google Playstore & install programs, receive text messages.
...but I cannot make any outgoing calls. And when I make a call to my cell phone, it does straight to voicemail
Any suggestions? Did the SIM card go bad?
finally fixed the problem. Had to Odin back to stock >> took OTA updates >> factory reset, and bingo.
...weird that phone boinked but data worked?!?
epagib said:
finally fixed the problem. Had to Odin back to stock >> took OTA updates >> factory reset, and bingo.
...weird that phone boinked but data worked?!?
Click to expand...
Click to collapse
I've had this happen several times in different circumstances. The fix I've found is to manually set the radio band using the "phone info" app. Under "Phone Information" I click on the menu which brings up an option to select the radio band. For some reason I need to do this while traveling to Canada too, I need to select the PCS band, then go back to Cellular once I reenter the US and want to get back on Verizon. I tried Odin'ing back to stock, and it didn't work for me, but I might have had the wrong stock at the time (I was out of town).
epagib said:
finally fixed the problem. Had to Odin back to stock >> took OTA updates >> factory reset, and bingo.
...weird that phone boinked but data worked?!?
Click to expand...
Click to collapse
Did you have your imei backed up using the synergy method? I had the same problem and with the same exact ROM, Carbon 4.3. When I switched Roms I couldn't make or receive calls but I could use my data and even send SMS. Luckily I had a backup of my imei in the form of a zip file that I flashed in recovery. It fixed it.
Sent from my SCH-I535 using Tapatalk 4
ok so here's the deal folks. I've been trying to fix this problem on my ATT Skyrocke since the 21st. I had flashed a copy of the Liquid Smooth ROM with all data working. Bear in mind, this S2 is net unlocked and APN settings are changeable with my sim card in, and everything is set to Straight Talk APN settings. When LS ROM was installed, everything worked fine, til this fateful day of the 21st where everything just stopped... No network, no data, no nothing. Every once in a while my network shows up and allows me to make short phone calls ranging from 45 seconds to 10 minutes, and sms/mms are even more widely spread on being able to receive. After going through my EFS folder, it seems that the phone is missing a critical file named nv_data. I have everything else in the EFS folder that should be there, at least from my experience, but my data still will not come back up. SOMEONE PLEASE TELL ME THIS IS FIXABLE!!!!!!!!!!!!! I'm losing my mind, considering this is my only work phone for my business, and as of yet, i don't have enough income from this business to buy a new phone.
EDIT*****
Before I forget, which I already did once, I have tried the following steps to fix this:
1: Bought a new sim card tray through ebay - no change
2: Flashed back to stock ROM - (multiple times) no change
3: Flashed multiple older roms - no change
4: Ran the EFSFix off of this: http://forum.xda-developers.com/showthread.php?t=1611796
Currently looking at performing a dark side wipe to install a new custom rom, but not sure if this will work yet or not.
420tuprophit13 said:
ok so here's the deal folks. I've been trying to fix this problem on my ATT Skyrocke since the 21st. I had flashed a copy of the Liquid Smooth ROM with all data working. Bear in mind, this S2 is net unlocked and APN settings are changeable with my sim card in, and everything is set to Straight Talk APN settings. When LS ROM was installed, everything worked fine, til this fateful day of the 21st where everything just stopped... No network, no data, no nothing. Every once in a while my network shows up and allows me to make short phone calls ranging from 45 seconds to 10 minutes, and sms/mms are even more widely spread on being able to receive. After going through my EFS folder, it seems that the phone is missing a critical file named nv_data. I have everything else in the EFS folder that should be there, at least from my experience, but my data still will not come back up. SOMEONE PLEASE TELL ME THIS IS FIXABLE!!!!!!!!!!!!! I'm losing my mind, considering this is my only work phone for my business, and as of yet, i don't have enough income from this business to buy a new phone.
EDIT*****
Before I forget, which I already did once, I have tried the following steps to fix this:
1: Bought a new sim card tray through ebay - no change
2: Flashed back to stock ROM - (multiple times) no change
3: Flashed multiple older roms - no change
4: Ran the EFSFix off of this: http://forum.xda-developers.com/showthread.php?t=1611796
Currently looking at performing a dark side wipe to install a new custom rom, but not sure if this will work yet or not.
Click to expand...
Click to collapse
goto READ THIS B4 POSTING | THE MOST Common Questions Answered HERE read/do q)25.d and borrow someones active att sim card, if after that phone still doesnt work right then its some kind of hw failure
hey vin. actually i had tried that thread and instructions for such already. although i went ahead and did it again in hopes that maybe i just did it wrong, but no change.
Here's a little update:
The baseband is known, running on I727UCMC1 baseband, but the IMEI number shows up as 0/00. I spent the entire night searching the forums here and over at androidforums.com and ran through google. There's no listing of the baseband being known, but the imei number being corrupt. Maybe I'm just using the wrong keywords... IDK but I do know this is really strange. I've never ran into this issue before.
So anyone know why the Baseband would be known, but the IMEI corrupt?
420tuprophit13 said:
hey vin. actually i had tried that thread and instructions for such already. although i went ahead and did it again in hopes that maybe i just did it wrong, but no change.
Here's a little update:
The baseband is known, running on I727UCMC1 baseband, but the IMEI number shows up as 0/00. I spent the entire night searching the forums here and over at androidforums.com and ran through google. There's no listing of the baseband being known, but the imei number being corrupt. Maybe I'm just using the wrong keywords... IDK but I do know this is really strange. I've never ran into this issue before.
So anyone know why the Baseband would be known, but the IMEI corrupt?
Click to expand...
Click to collapse
baseband aka radio has nothing todo w/the imei.
as to why imei got corrupted, idk why it happened and i dont know if theres a fix for that
edit: a bad radio might corrupt the efs folder though not sure if thats what happened to u
it seems you might have a corrupted efs folder
search for corrupted imei
try this http://forum.xda-developers.com/showthread.php?t=1611796