I cant get any MMI codes to work on my Samsung S22 Ultra, get the Connection problem error. I have tried all the suggested fixes in IE. Anyone have a real fix?
The tools that are accessible are specific to the ROM that is on the device, some generic ones should usually always work. The numbers may have also changed between models/android versions.
It is also possible that the both of you bought a fake device that generally lacks those tools.
Related
I received a new phone today that I got on eBay, a Cobalt SP300. The hardware itself is pretty decent, except for the camera, but I've run into some issues with Android. I think it might be my APN settings, even though I've tried many different variation, but I can't get outbound texting to work. It just says sending for a while and then fails. Inbound texting however works fine.
Another issue is that I am stuck on the Edge network. I took a game since the eBay description said Edge only, but I was hoping it might have been in error since this chipset inherently has 3G built into it. But I think for some reason this company disabled it. Also kind of odd since it says it allows HSDPA right on the box... Anyway,when I go into the info screen (*#*#4636#*#*) I see it says GSM only, but it won't let me change it. I remember seeing on a russian site some sort of debugging screen where you could see all bands the phone allows. Anyone know how to get to that?
Would anyone be able to help with this?
Would knowing the baseband or kernel version help?
Thanks
I have also tried getting into an engineering mode as well using *#*#3646633#*#* and *#*#197328640#*#* to view band modes but neither of those codes work, it just brings me back to the dialer screen.
As far as the no incoming texts go, I figured that out by putting the proper SMSC code for AT&T in the messaging app setting. Hopefully this bit might help anyone else with the same problem.
I don't know if anyone may be able to answer this now but with so many of these selling on eBay someone else is bound to searching for the same fix as I am for the 3G. I made the EDGE bearable by using Opera Mini however.
Also, I found the original Chinese version of this phone, the Morningside A206.
And it turns out I'm not alone in the search for 3G, I found something in Chinese with someone inquiring why their A206 won't connect to 3G.
I would post these links but I don't have enough posts.
3G is looking less likely to be activated.
I found an app called Mobileuncle MTK Tools that gets you into engineer mode. I go down to Band Modes (Screenshot attached) and the GSM modes are all selectable but all of the UMTS modes are grayed out. It just seems so weird I know this is a MT6575 chipset which supports it. Is there anything else that can be done?
I also happened to find out how to root the phone if anyone comes across this and needs to know.
Follow these instructions: http://forum.xda-developers.com/showthread.php?t=2046161
I also had to find the drivers elsewhere, so just google this .rar file: usb_driver_MT65xx_Android_ZTE_v821.rar
The first google result from rghost . net worked fine
I've recently left my i9100 for an i9305 and decided to start by flashing the equivalent to my favourite ROM from my S2, namely SlimSaber (SlimKat unoffical build with Saber Mod) from here (build 8.0).
Anyway, regrettably i never tested out the phone much with the stock software because i wanted to go strait back to the KitKat experience I'm used to. I did however unlock the phone using USSD code *#19732864# as outlined in method 3 here. I believe I followed it exactly and it worked without a hitch
With it unlocked i put in my GiffGaff SIM and the first thing I noticed was that after every text, instead of getting the regular message saying "woohoo that text was free" or relevant credit update, i just get a similar box with a load of Chinese text.
Then I realised that the proximity sensor doesn't work. I don't mean to go specifically into that problem in this thread but while researching a fix I came across some USSD codes that might help. Now I can get a few to work: *#06# to show my IMEI , *#31# (Checks outgoing caller ID settings) and *#*#4636#*#* (User statistics and Phone Info), but all others I've tried just give me "Running USSD Code" and then "Connection problem or invalid MMI Code". This includes the one I unlocked my phone with in the first place and all the ones that are supposed to help my problem. A couple of the codes (*#526# and *#528#, both for WLAN Engineering Mode) yielding more Chinese text in place of the second message. I've tried putting a coma or semi-colon after the codes to no avail.
I presume that the network messages run on the same system as USSD/MMI and that the problems are connected. Not sure if the proximity sensor issue is connected.
The fact that a code worked before, but then stopped working seems to imply that it was something to do with flashing the ROM. Can anyone confirm that custom ROMs can mess with your USSD codes? Or could the unlock process have changed something? I've tried different kernels but the problem persists. Does anyone know at what firmware level native USSD codes are defined?
Many thanks for any input.
Hi,
The best place to find help would be in your device section, here...
> Samsung Galaxy S III I9300, I9305 > Galaxy S III Q&A, Help & Troubleshooting
Good luck!
Moved
Ok, great thanks. Seeing as you said nothing about getting it moved I just made a duplicate thread there. You can find it here:
http://forum.xda-developers.com/galaxy-s3/help/network-messages-coming-chinese-invid-t2913800
Mods feel free to delete this one.
Hello, Recently I have bought an Unlocked At&T LG G3 The seller told me that the phone has a bad IMEI But it's unlocked to be used interntionally. When I received it, It's working fine, except the data network speed trough EDGE is too slow. As yo can see on the screenshot below I couldn't find the option to change the network type. and I'm stuck at "E" which mean EDGE.
http://s14.postimg.org/8r7vs0x27/Quick_Memo_2015_09_09_11_41_43_1.png
The phone's model is LG-D850 and it's running android 4.4.2 KitKat. it has no IMEI when I dial *#06# it shows IMEI: 0-05 on Settings/about phone/Status... it says IMEI: 0
Anyone here to help?
First, here are the possible reasons why you don't have an IMEI:
The phone was reported lost or stolen in the past.
The phone is still active on the owner's wireless carrier account.
There is money owed on the wireless carrier account to which the ESN/MEID/IMEI is connected.
For the reasons above, this community does not support such devices and you will probably not get any help.
But, this can also happen during a bad flash, so to fix the issue, you have 3 options:
Reset, unroot, then root and flash again
Try the suggested steps in this video
Find a company that can fix the problem by sending the phone to them
youngunix said:
First, here are the possible reasons why you don't have an IMEI:
The phone was reported lost or stolen in the past.
The phone is still active on the owner's wireless carrier account.
There is money owed on the wireless carrier account to which the ESN/MEID/IMEI is connected.
For the reasons above, this community does not support such devices and you will probably not get any help.
But, this can also happen during a bad flash, so to fix the issue, you have 3 options:
Reset, unroot, then root and flash again
Try the suggested steps in this video
Find a company that can fix the problem by sending the phone to them
Click to expand...
Click to collapse
Thanks for your reply, I'm not seeking to restore the IMEI. I just want to have the option to switch mobile network type. Should I root the phone and install a custom ROM?
AminhoVic said:
Thanks for your reply, I'm not seeking to restore the IMEI. I just want to have the option to switch mobile network type. Should I root the phone and install a custom ROM?
Click to expand...
Click to collapse
My bad, thought you wanted the IMEI back. In that case, the E (edge) is showing up could be due to Maroc Telecom throttling your connection or their towers could be far way (happens when you travel cross country too). Anyway, if you want to fiddle with network settings and try to get it to work BEFORE attempting to flash any ROM, try the following [3845#*855# 3845#*850#] USSD code from your stock dialer. You will get a hidden menu containing a juicy list of options and settings, so what you are probably looking for is the "LTE-Only" option (I am not sure though, but you can look through the settings).
And as always, attempt the suggestions AT YOUR OWN RISK.
youngunix said:
My bad, thought you wanted the IMEI back. In that case, the E (edge) is showing up could be due to Maroc Telecom throttling your connection or their towers could be far way (happens when you travel cross country too). Anyway, if you want to fiddle with network settings and try to get it to work BEFORE attempting to flash any ROM, try the following [3845#*855# 3845#*850#] USSD code from your stock dialer. You will get a hidden menu containing a juicy list of options and settings, so what you are probably looking for is the "LTE-Only" option (I am not sure though, but you can look through the settings).
And as always, attempt the suggestions AT YOUR OWN RISK.
Click to expand...
Click to collapse
I'm living at a major city, here the 4G works great. So yeah I have to change the mobile network type since it is on EDGE by defaut I guess.
I attemted the USSD code however it says "connection problem or invalid mmi code" after I hit dial. I have also tried a bunch of codes before but no luck.
I think I will falsh the phone that's the option left. I just have rooted the phone, then I will install TWRP and I will try to flash a ROM in it. What do youu suggest me to use from those ROMs posted here ?
AminhoVic said:
I'm living at a major city, here the 4G works great. So yeah I have to change the mobile network type since it is on EDGE by defaut I guess.
I attemted the USSD code however it says "connection problem or invalid mmi code" after I hit dial. I have also tried a bunch of codes before but no luck.
Click to expand...
Click to collapse
I get the same error if I use a third party dialer app (i.e., Dialer) until I tried the stock phone app.
I think I will falsh the phone that's the option left. I just have rooted the phone, then I will install TWRP and I will try to flash a ROM in it. What do youu suggest me to use from those ROMs posted here ?
Click to expand...
Click to collapse
I haven't flashed any custom ROMs on my LG, but from experience, each device somehow reacts differently to custom ROMs. For instance, I've flashed my S.G. Note (i717) over 30 times and some ROMs were stable at first then started having issues with them.
The best advice I can give you, is to pick a ROM from the list you posted and check the comments to see if it is stable or too many users have issues with it.
AminhoVic said:
I'm living at a major city, here the 4G works great. So yeah I have to change the mobile network type since it is on EDGE by defaut I guess.
I attemted the USSD code however it says "connection problem or invalid mmi code" after I hit dial. I have also tried a bunch of codes before but no luck.
I think I will falsh the phone that's the option left. I just have rooted the phone, then I will install TWRP and I will try to flash a ROM in it. What do youu suggest me to use from those ROMs posted here ?
Click to expand...
Click to collapse
Ever think that it does not have the correct bands for your carrier?
Hi,
following problem to my LG P930:
I got it as a present because my old phone was crashed. First I wanted to do with the P930 is to get root access and flash CM to it. This was difficult enough, but now I have a problem where I coundn´t find any information.
With original firmware (I think it was 2.2.6 or 2.3.6) LTE was working. Now, with the last CM 11 and with CM 10.2 LTE dowesn´t work. I can ping any homepage with the terminal, but the speed for downloading is just at 40k/s, really really slowly.
I found, that maybe LTE must be unlocked by an unlock-code. Therefore I have to open a menu under the number 2945#*930#, but when I call this, just the msg appears, "Connection problem or invalid MMI code". Most of all #* calls do not work at all!
I tried to fix it, but all methods I found are for MTK devices, but the P930 has a snapdragon cip.
The *#06# call works, my IMEI is valid, I can make calls and send sms, the Internet works, but much too slow for daily use. My Sim Card gets access to o2 network in Germany.
I tried 3 CM ROMS and different settings in APN and mobile networks, but nothing works.
I tried to get network access with a Telekom SIM, but there I couldn´t get any access, so I wasn´t able to make calls, neither sms nor Internet.
does anyone have an Idee how to solve this issue?
PS: only thing I found is in this thread, is to rename modemfs folder.
But I don´t understand what eduds mean in post 8, and his problem was an other, because his mobile data doesn´t work at nothing.
http://forum.xda-developers.com/showthread.php?t=2567399
Thanks for response, regards from Germany
Hi,
Thanks for using XDA assist.
Please create a XDA account and post here:
Nitro HD General
Good Luck! - gsstudios
Update 25-11-21: My friend told me that there are already some hardware-based physical tools that implement JTAG (IEEE 1149.1). I couldn't be able to say more about this because know nothing about electronics. (Those are very scarse to get where I live).
I'm recently entering this world of mobile phones and I was struggling with a phone which was unable to get the carrier signal. And a friend of mine which has been in this world for like 6 years now said: "It has to be a problem with the modem (hardware integrated component to communicate with the carrier)". By the way, he reached this conclussion after several practical testing without any successfully result. Coincidently he had a complete board for that cellphone model and after a replacement, the phone was able to have reception (also call and receive). But this was a radical solution, like formatting a PC because of one of the installed programs is just misbehaving.
So my doubt: Is there any hardware testing or diagnostic tool capable of interact with each (or several) components on the board and performance several actions and get their status?
For instance, let's say, before replacing the entire board from the example before, we were aiming to check the integrated modem status and if possible send instructions to send and receive instructions from the carrier. Can this be done? Be it this testing and diagnostic tool software or hardware based? Something resembling the POST (Power-On Self-Test) performed when a computer boots up, but be it done for testing and information gathering arbitrarily.
Full disclosure, before replacing the entire board we hard reset and also flashed the phone, without any successfull outcome. We spent like 4 days banging our heads against the wall. With such a hypothetic tool we could have saved ourselves a lot of time and effort. Maybe such a tool already exists and here I am posting out of ignorance. In both cases, any help is appreciated.
PS: I used the term modem in this post but I don't truly know if this is the proper term to refer, my apologies in advance.
PS1: I stumbled upon this tool named PC-Doctor but the Android version has to be installed in the phone's Android OS. But almost all phones we receive are close to dead (logo stuck, boot loop, FRP bypassing required), so installing an APK probably would not be an optimal solution here.
Thanks in advance!
ppdmartell said:
I'm recently entering this world of mobile phones and I was struggling with a phone which was unable to get the carrier signal. And a friend of mine which has been in this world for like 6 years now said: "It has to be a problem with the modem (hardware integrated component to communicate with the carrier)". By the way, he reached this conclussion after several practical testing without any successfully result. Coincidently he had a complete board for that cellphone model and after a replacement, the phone was able to have reception (also call and receive). But this was a radical solution, like formatting a PC because of one of the installed programs is just misbehaving.
So my doubt: Is there any hardware testing or diagnostic tool capable of interact with each (or several) components on the board and performance several actions and get their status?
For instance, let's say, before replacing the entire board from the example before, we were aiming to check the integrated modem status and if possible send instructions to send and receive instructions from the carrier. Can this be done? Be it this testing and diagnostic tool software or hardware based?
Full disclosure, before replacing the entire board we hard reset and also flashed the phone, without any successfull outcome. We spent like 4 days banging our heads against the wall. With such a hypothetic tool we could have saved ourselves a lot of time and effort. Maybe such a tool already exists and here I am posting out of ignorance. In both cases, any help is appreciated.
PS: I used the term modem in this post but I don't truly know if this is the proper term to refer, my apologies in advance.
PS1: I stumbled upon this tool named PC-Doctor but the Android version has to be installed in the phone's Android OS. But almost all phones we receive are close to dead (logo stuck, boot loop, FRP bypassing required), so installing an APK probably would not be an optimal solution here.
Thanks in advance!
Click to expand...
Click to collapse
When you say modem, that could be taken to mean two things.
1) it could refer to the radio, the actual radio hardware component.
2) it could refer to the modem software that is part of your stock firmware and controls the RIL(Radio Interface Layer).
Typically, when we in this community say "modem", we are referring to the modem software. When we are referring to the hardware, we say "radio".
In the case of your device, it could be that you had the proper radio hardware and that it was "able" to function but possibly your modem software was not correct. Or it could have been that you did have the correct modem software installed but your radio hardware component was actually damaged or not able to function.
If it was an issue with improper modem software, you could have potentially downloaded and flashed the correct modem software to solve the issue.
If it was an actual fault in the radio hardware, switching the motherboard or at least unsoldering the radio component and replacing it with a new radio component is the correct solution.
If the device was from a different country/region or if the device was from a different carrier than the carrier that you were trying to activate it with, it was probably just a case of needing to flash a compatible modem software to work in your country/region or on your carrier network.
Yes, there are tools to diagnose the hardware but they are generally software based and are useless to diagnose the device if it doesn't at least power on and function in some manner. I know there are android apps available that can be used to test/diagnose the internal hardware components but they all probably require rooting the device.
It stands to reason that there should be various PC software based android hardware component testing/diagnostic tools that are used via connecting the device to PC but I've never looked into that or ever had a need for them.
As for hardware based tools to test or diagnose Android based hardware components, I'm not versed in what they could be, but I'm fairly certain that they exist and are used, it would not make any sense if they did not exist.
A Google search for:
"Android hardware testing and diagnostic tools"
Should find lots of tools to start researching.
Droidriven said:
When you say modem, that could be taken to mean two things.
1) it could refer to the radio, the actual radio hardware component.
2) it could refer to the modem software that is part of your stock firmware and controls the RIL(Radio Interface Layer).
Typically, when we in this community say "modem", we are referring to the modem software. When we are referring to the hardware, we say "radio".
In the case of your device, it could be that you had the proper radio hardware and that it was "able" to function but possibly your modem software was not correct. Or it could have been that you did have the correct modem software installed but your radio hardware component was actually damaged or not able to function.
If it was an issue with improper modem software, you could have potentially downloaded and flashed the correct modem software to solve the issue.
If it was an actual fault in the radio hardware, switching the motherboard or at least unsoldering the radio component and replacing it with a new radio component is the correct solution.
If the device was from a different country/region or if the device was from a different carrier than the carrier that you were trying to activate it with, it was probably just a case of needing to flash a compatible modem software to work in your country/region or on your carrier network.
Yes, there are tools to diagnose the hardware but they are generally software based and are useless to diagnose the device if it doesn't at least power on and function in some manner. I know there are android apps available that can be used to test/diagnose the internal hardware components but they all probably require rooting the device.
It stands to reason that there should be various PC software based android hardware component testing/diagnostic tools that are used via connecting the device to PC but I've never looked into that or ever had a need for them.
As for hardware based tools to test or diagnose Android based hardware components, I'm not versed in what they could be, but I'm fairly certain that they exist and are used, it would not make any sense if they did not exist.
A Google search for:
"Android hardware testing and diagnostic tools"
Should find lots of tools to start researching.
Click to expand...
Click to collapse
Honestly I didn't know radio was the proper term to refer that hardware component. Now I do and thanks to you.
However, in this case I just used a practical problem to communicate my idea. I should have expressed myself in a better way. The underlying issue was the diagnostic tool itself, and not the radio problem I used, maybe like some sort of low-level query-based tool to test and diagnose the components.
And I also should have done some research in google before posting here too. Maybe I got lucky. Just in case I could find any solution to my issue, I will gladly post it here.
Thanks for the reply.