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
Related
Hi all.
Was wondering why I get an error "unfortunately dialer has stopped" on about half the calls I make or receive. It starts to dial but then I get the error and it kills the call. Any idea what it may be and how I can fix it ? I am on benzo rom and latest gapps with included vindicator kernel.
I'm thinking it's a radio and /or baseband issue but don't know.
When I was on stock 5.1 on Rogers wireless it worked fine and I never had the issue. But on Rogers it said LYM47D and this ROM says LYM47I. Not sure if that makes any difference.
I entered the keypad code and verified that LTE is enabled and lte/GSM is selected.
I tried flashing the LYM47D radio in TWRP but that didn't help.
Any help would be much appreciated
Thanks a lot
Searched around everywhere and the issue seems to be relatively widespread. During the Gear VR installation process, the install button becomes greyed out, stating "Network error occurred. Try again later."
Im using a Galaxy S7 Edge (G935F) stock ROM rooted +xposed.
I've tried editing the CSC file at /system/csc/sales_code.dat but this hasn't done anything!
I'd prefer not to wipe my phone and go through the hassle but if it that works (I've heard it doesn't) then I'll give it a shot.
Any help would be greatly appreciated, thanks!
I got the same problem after xposed installed on my G935T, when it was rooted and installed all work fine, but when i returned to stock rom (because the lag and big hot introduced by rooting it) GearVR never work again always with the wizard error "network problem" but i noticed that when i enter to the recovery and leave it, i get a red message "data mount problem invalid argument" i check xposed installer install.sh script and i notice that they mount /data storage in some lines maybe they change the way /data need to be mount so.. gearvr detect that data is wrong mounted and it avoid to be installed.. so.. im stuck on that weird problem.. and cant install gear vr now.
Serge Winters said:
I got the same problem after xposed installed on my G935T, when it was rooted and installed all work fine, but when i returned to stock rom (because the lag and big hot introduced by rooting it) GearVR never work again always with the wizard error "network problem" but i noticed that when i enter to the recovery and leave it, i get a red message "data mount problem invalid argument" i check xposed installer install.sh script and i notice that they mount /data storage in some lines maybe they change the way /data need to be mount so.. gearvr detect that data is wrong mounted and it avoid to be installed.. so.. im stuck on that weird problem.. and cant install gear vr now.
Click to expand...
Click to collapse
I figured it out! It's a problem with your phone's CSC version (Consumer Service Code)!
Flash your original CSC version (that should be compatible with Gear VR) using this tool - http://forum.xda-developers.com/s7-edge/development/utility-flashable-csc-selection-30-t3392957
If your variant is not available contact the Dev and he will add it upon request! Let me know how you go
Thanks you benno4678 for that solution!, it seems like is more than one solution for this problem hehe, well i fixed it.. i just take out the sim card and start the phone without it.. then i connect to an U.S vpn and everything works fine this time.. is like Oculus hate Cuba nahh.. seriously i think this is because I'm using t-mobile phone with TMB CSC in a different carrier like you said... but without sim card the phone din't show the carrier info so oculus installs works. Btw my operator don't have any CSC defined so.. my solution is the only one that work for me
SOLVED
Take the SIM card out and reboot. Install the software with the SIM card OUT. It worked for me.
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
My sister who has the Mi A2, like I do, got an error after downloading and wanting to install the latest OTA.
After the phone restarts to install the update, she gets stuck in the recovery where she can choose between retrying the update (Which doesn't work and brings her back to the same error screen, or factory resetting the phone. When she factory resets her phone, she can boot back into android, but whenever she restarts her phone, she gets the error message and needs to do a factory reset to continue using her phone.
I previously had a Mi A1, and today, the guy that I have sold it to called me because he has the exact same problem.
I find it really strange and would like to hear if anyone else experienced similar issues.
Update:
Seems this has something to do with a bug in the latest OTA on devices that have the language set to Dutch. Taking the SIM-card out, restarting the device (It doesn't give the error anymore), changing the language to anything else but Dutch and inserting the SIM-card again fixes the issue. It can also be fixed by changing the SIM to an older device that can remove the SIM-pin. In this case the user can still use the Dutch language. I guess residents from Belgium and The Netherlands will have to wait until Xiaomi patches the OTA until they can use the Dutch language again.
My wife also had the same issue.. shame