Here is my situation (this started a couple weeks ago and I am a little fuzzy with some exact details).
My phone was running a little slow, so I restarted it. After the phone rebooted, it no longer worked. I can't remember for certain if the error message "sim not allowed: mm#3" was showing at that time, but I do remember that not only was the phone not working, but the phone's imei had been replaced with a meid. I found this out when going into settings, then about device, and then into status. I don't remember when exactly the meid dissappeared and the phone started showing its imei again, but yes the imei has returned. Even though that issue cleared up, the phone still isn't right.
What's going on now.. Sometimes I get the error message "sim not allowed: mm#3" and sometimes I don't. When the message does show, maybe 50% of the time with a simple restart of the phone the message will go away and the phone will partially work (making calls/text but no data.. wifi works). The other 50% of the time I can typically get it to accept the sim by entering the code "*#*#4636#*#* and then changing the preferred network type (the same network type does not always work). When the phone will work (again, that's only partially working) it will now only use the edge:2 network type.
It goes without saying that everything I have done attempting to fix this issue has failed. I have us.d odin to reflash the firmware packs and even the modem file. The list of files I flashed are G900A_Downgrade_to_NCE.tar.md5, AP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5, CP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5
CSC_ATT_G900AATT1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5,
and these files did all flash successfully. I attempted to flash G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.md5 but the process failed. Unfortunately I don't remember the error message when it failed, but I will be happy to reflash it so I can get the error code for you.
I even went as far as flashing the ported tmobile rom and then flashing back to at&t, and yet again the problem was not fixed.
Just before starting this post I followed the steps listed in http://forum.xda-developers.com/galaxy-note-3/help/sim-allow-mm3-solution-t2921741 hoping this may work, and it doesn't appear to have made any difference.
fix for sim not allowed mm#3
rooted the phone, preformed a nv item rebuild and the issue seems to be fixed.... phone is running 4g currently. no repeat of the error code yet
Related
. I flashed the KZ file with lg update software as explained in the XDA thread but I could not get the process to work right. My phone kept disconnecting at 28% and it would not turn on no matter what I did. It would only make a short vibrate as if it was turning on, and the computer would notice it but only for a short time. And never once did a light on the screen, or LG logo, or anything at all ever appear.
I figured I had really screwed it up, but when I plugged it into the wall it booted up perfectly. All my data was in tact and the rom i had flashed through cwm was still there, not the kdz file that I flashed with the lg software.. I noticed that my sim card did not come up as being in the phone at all. I looked in system setting status and noticed that all info related to my imei said unknown. I opened up the mfg app (277634#*# from the phone app).. Under "version info" then "factory version" my phone now says xmm6260.. It always used to say p925..etc... Even after flashing the zip to debrand from at&t this never changed from p925 even when every other aspect of my phone has.. I was hoping maybe once I put in an activated sim card everything would be fine and my phone would be unlocked which is why i flashed through lg software.. But seeing as how other people are having this similar issue and their phones not seeing the sim card, well im looking for some advice.. Should I try and re flash kdz file through lg software again? if i do, im going to do it on my XP computer this time, not Windows 7..
Just wanted to add that I did try wiping data and cache from cm and no dice.. Root and CMW work fine but no matter what I do, if my phone is turned off, i cannot boot up or boot to cwm or boot at all unless i plug the phone into a wall carger and then once its on it stays on and i can unlug.. SORRY ABOUT THE LONG POST, THANKS IN ADVANCE FOR ANY HELP..
I would reflash CWR first and foremost, then try to flash back to stock.
No IMEI/GSM Radio
Hi, were you able to fix your problem? If so, could you please give me a hand, I have same problem.
Im attaching a couple of screen shots, one where you can see that IMEI is not shown and other is where you see the phone number thats on the SIM but has a sign like if no SIM were inserted.
Using the KDZ detects the IMEI, but after flashing it doesnt show up on phone.
Thanks
Took my phone to a cellphone shop and they fixed it. Everything is back to stock and working normal.
Hi ive got the same problem, did you fix it?
Yes, my phone is working perfect at stock. Im going to wait for GB ir ICS with a working 850MHz baseband.
I have an SCH-i800 that I have CM9 (p1c 9.1.0) installed on. I have been using it for several weeks with no problem. Since I am planning on going on a trip, I decided to active pre-paid Verizon service for the tablet. At first, I attempted to activate the device. It went through the phone call but after a minute, it just sat at activating. That is when I noticed that the radio state in the status bar had an X on it. I rebooted the tablet to try again and got "com.android.phone has topped unexpectedly". I re-flashed CM9 (at the time I was using 9.0.0) and it worked again. Activation was not necessary. After a day, the error came up again and radio state went to off with an X. I tried 9.1.0, same problem after a day. I even tried a nightly CM10, same problem. Reboots, cache wipes, permission fixes do not make it work. The error persists until a re-flash of CM. I see on the Support Downloads for the Verizon Tablet, there are two modem files. My baseband version is currently S:I800.0.3V.EI04. I have attempted to "flash" these both via Odin (which failed after a couple minutes) and ZIP (which looked like it worked) to the EC02 on the site, but my baseband doesn't seem to change.
So my first question is, is there a how-to on flashing as I have searched high and low on one for the Verizon Tab specifically, and have yet to find one. Is there a ZIP file that is specifically meant for the i800? I am almost certain this is my problem and that a downgrade (this tablet when stock was updated to the latest Verizon image).
My second question is, has anyone else experienced this? Is there someone that is using a CM9 Verizon tab with EI04 baseband and not have this problem?
Is there a way I can track down what crashed the program? I have tried logcat, but it doesn't appear to give me much detail other than to tell me that it stopped.
And if you ask, no I did not use the Verizon service with this tablet before putting CM9 on it, so I wouldn't know if it worked before.
Any input that someone could provide would be useful. Thanks!
So I finally took the plunge today and rooted. I flashed the most recent Sprint version of ViperROM, and everything was going just fine and dandy, I was all giddy setting up my MoDaCo UI mods, etc, until I tried to send a text. Tried to send for 5 minutes, got the fail message. Well, that's weird. What about 3G data? Nope, nothing. Maybe the ROM is bad? I flashed the stock ROM by viperboy, also didn't work. Same problems. So now I'm stuck with no cellular connection and I need it soon. How do I fix it? (Note that I followed my tutorials step by step and everything works except cellular connection. Also note that it says I have service and that data is going in/out, but it's not actually sending/receiving anything. It seems that I need something called an RUU, but I have no idea what that is or where to get a correct one and how to flash it.
Please give me a step by step (I'm using TWRP if that matters), as this is my first time rooting or doing anything more advanced with my phone past advanced themes in Nova Launcher. I'll need links if you have them, or at least where to look. Please help me, because don't want to go back to stock after getting all my awesome tweaks already!
And yes, I have updated my PLR and Profile in the system updates menu, same results.
EDIT: I fixed it, yay! I tried clicking UICC unlock in the software update menu. It said no profile update available, and then it started working (it's actually faster than normal! ) It may have been the profile update that did it and it took a second to update, but it works now! Yay! I even rebooted to make sure it was going to stay after a shutdown, etc, and it did! I guess I should check all option before posting a thread next time... (If you can't tell I'm extremely happy it works!)
EDIT 2: It stopped working again :'(. Now I'm constantly losing the 3G connection that I "had" and messages and data only work about 10% of the time they say they're connected. Wifi still works. When I try updating the profile, it says it could not be updated and to try again later (this is after several tries and a reboot). I try to update the PLR and I get error code 1233. Apprently this is an HTC specific error with no know fix? I try to do the UICC unlock, and it gives me the same error as the profile message.
EDIT 3: It seems Sprint is having issues in my area, I will update again if they resolve it or reply to my tweet.
EDIT 4: They told me to go restart the booster thingy I have in my house, and now my connection is working for now...
Hello all,
Every ROM I have tried to flash has come with some type of problem or another.
I have a SIM locked T-Mobile HTC One with a PTel SIM inside. I unlocked the bootloader, rooted the phone, and installed TWRP. Then, I downloaded several ROMs and tried to flash them (after doing wipe data and cache). Here are the specific problems I have run into with each ROM.
OneDroid: The screen keeps popping up "Unfortunately, Android Keyboard has stopped". After second boot, in addition to the other error message, the screen keeps popping up systemUI has stopped. The whole thing is just unusable.
Android Revolution HD: I am unable to obtain any phone signal.
ViperOne: Same issue, no signal.
InsertCoin: I can't get a proper HSPA+ connection due to incorrect APN settings. I have followed the directions on PTel's own website, but was unable to obtain data. It's a shame because I like this ROM the most of all.
MaximusHD: The only ROM to have worked properly.
I am sure I have done something wrong somewhere. I guess I'll just live with MaximusHD.
MaximusHD is completely stock with very minor changes. For other ROMs you have to select (or flash additional stuff) that you have T-Mobile device I think. But it is better to have their threads searched for "T-mobile".
HELP - "dm-verity verification failed..." recovery message and no cell service
Background Info:
Was rooted on OE2 via pingpongroot and supersu and froze some bloatware with Titanium Backup, nothing else done to the phone. Flashfire was on there but never used. Phone has worked fine this way for about 7 months.
This past Friday I suddenly lost all network connectivity and was very sporadic in connecting to the LTE network. Also lost ability to send text messages.
These are the steps I did:
1. Went to the ATT store, verified IMEI was ok, and got a new SIM card - nothing
2. Tried *#*#4636#*#* dialer code to see the network settings - nothing
3. *#0011# diagnostics dialer code - nothing
4. Tried different APN settings as well as APN reset - nothing
5. Factory reset - nothing (could not factory reset from UI, had to do it from recovery - "dm-verity verification failed..." message seen in recovery)
6. Removed pingpongroot app and uninstalled root via supersu, verified with rootchecker - nothing
7. Did another factory reset without root - nothing (could not factory reset from UI, had to do it from recovery - "dm-verity verification failed..." message seen in recovery)
8. Somehow the texting message center digit code was changed, so I did some googling and changed it back to +13123149810 from 313133127 - FIXED TEXT MESSAGING
9. Spent an hour with tech support verifying there were no network restrictions or limitations with my device - nothing
10. Attempted an OTA update on the phone - update failed (dm-verity verification failed.... message in recovery)
I didnt find too much on the dm-verity verification failed... message in recovery. It seems it has something to do with system files being modified, or something with the EFS. I cannot figure out what is going on with no network service, so an option is to either replace the phone under warranty from a service center, or to try and flash stock firmware via ODIN. Phone doesnt have knox tripped and says official under status, so I dont think I would have a problem replacing with them.
Questions:
1. Will "dm-verity verification failed..." cause issues with Odin and going back to stock recovery? Last thing I want is a brick when I could return it.
2. Can anyone think of anything else I could try in terms of trying to get my cell signal back? It connects to LTE in high populated places, but in places where it used to have fine reception (work, home) it gets nothings. This combined with the fact that my message center code was changed makes me think something deep in the network settings was also changed, but I have no idea where to look.
Thanks.
Do you still have frozen bloatware? You might want to try un freezing everything, and seeing if that helps. Perhaps you locked something up that's in need of an update / conflicting now.
AoN
anneoneamouse said:
Do you still have frozen bloatware? You might want to try un freezing everything, and seeing if that helps. Perhaps you locked something up that's in need of an update / conflicting now.
AoN
Click to expand...
Click to collapse
Everything should be unfrozen after I did the factory reset, as I saw all of the ATT bloatware pop up again.
I am receiving reception again!
1. Odin back to stock. In this case it was OE2
2. Factory reset - this removed the "dm-verity verification failed..." message in recovery
3. Took the OTA update to OI2 ROM version
4. Factory Reset
5. Took the OTA update to OJ7 ROM version
6. Now have reception again in areas where it suddenly dropped off.
I do notice that my IMEISV number changed between OTA updates, and there are some extra network options in the secret dialer code menu. Not sure if that had anything to do with it, or the fact that I did not take any OTA updates since receiving the phone 7 months ago.
Anyway, hope this helps some people who may have suddenly lost reception in places they used to have it.
orlandoxpolice said:
I am receiving reception again!
1. Odin back to stock. In this case it was OE2
2. Factory reset - this removed the "dm-verity verification failed..." message in recovery
3. Took the OTA update to OI2 ROM version
4. Factory Reset
5. Took the OTA update to OJ7 ROM version
6. Now have reception again in areas where it suddenly dropped off.
I do notice that my IMEISV number changed between OTA updates, and there are some extra network options in the secret dialer code menu. Not sure if that had anything to do with it, or the fact that I did not take any OTA updates since receiving the phone 7 months ago.
Anyway, hope this helps some people who may have suddenly lost reception in places they used to have it.
Click to expand...
Click to collapse
Sorry bro, as you installed the old program?
I believe it's because you are on Of4 firmware, but restored the oe2 files? To get back you need the flash the files in Odin from the muniz of4 update thread.
Nevermind, I see you updated already.