no permission to read the phones status code
Getting this error message after a fresh wipe and install of EU rom. Anyone else seen it. It appears randomly.
Related
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.
I just got my Mi5, nice device but the sw is not that good, getting some fc's in settings etc.
Anyway, i want to install the dev rom to be able to unlock my device.
Was shipped with Miui version 7.2.13.0
When i use the updater application i getting an error "Unfortunately, updater has stopped"
Bug report says"java lang null point exemption, java etc"
Can the dev rom be installed in some other way?
Ok, found an way:
http://forum.xda-developers.com/showpost.php?p=66856879&postcount=4
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
"there was a problem connecting to fonts.gstatic.com" error during initial startup
new max 2, white, from banggood, first boot, google asks me things... i enter the passw for my wifi, then i encounter this error "there was a problem connecting to fonts.gstatic.com" and there is no way to go out... to go into os, i am STUCK at this error!
i bypassed the problem i don't know why, but also if at the moment i am in the OS, i still have problems with google cccount. i can't add a google account i read always the same problem!
i also updated the rom because i found an OTA but nothing changed. i would not root and change the rom of the phone BECAUSE it is not for me but for a friend and i would keep it STOCK 100%
any solution please
So yeah, my note 8 secret codes are not working after I flashed the stock ROM due to system corruption (And knox bit 1), the *#0# code and the other codes just don't work, it shows an error message, sometimes an MMI error and sometimes unknown application, any idea why this is happening?
Sorry for the broken english, im not a native speaker
its *#0*#
I tried again, and the same error, I think is a ROM error, so I am changing the ROM to see if that is what is causing the error