Database Users

HTC Universal SIM Card is missing

My HTC Universal says the SIM Card cannot be found or is missing, which of course is not true. I have tried with several SIM-Cards, but none of them work better. The error message appears as follows: Sometimes the phone connects to the network, but then suddenly the connection is cut off.
I bought a second-hand device, but before I jump to any conclusions I would like to rule out whether:
-it could be related to a radio upgrade
-it could be related to the SIM-Lock removal
-it could be related to a ROM-Upgrade
I am using Radio 1.18 and maxstegi's ROM 4.7.
Besides, I would like to know where to fix the device. It was originally a T-Mobile MDA Pro, but now that their software isn't any longer installed, they would probably refuse.
Thanks in advance
Michael

I had the same problem with mine. I eventually solved it by playing a hot-air rework blower over the radio chips, It's a bit of a drastic job, but it worked for me.
Here is the background:
http://forum.xda-developers.com/showthread.php?p=1757576
John

i had the same problem .. and i tried another solution .. i got a dry magnetic head spray cleaner and i sprayed the whole mother board connectors .. it worked as a start with me and i am waiting if it will remain good or will happen again ..

3 days now and my xda didn't give the sim card message - my problem solved

Great idea. I'll try today!

Sorry..but..for "dry", what do you mean? Is it the isopropyl alcohol based liquid?

i mean dry that it does not leave any traces on sprayed place after a while .. some other magnetic cleaner sprays leaves an oil layer over the sprayed area ..
ask in your location for a magnetic head spray cleaner and i am sure you can found one easily
it is now about 1 week and i had no problems
thanks

hey aymn_louis
I also suffered with sim card problem and got the solutions please check your PMs, sent you the web address to download it, have used it myself, works good.
Currently i m usin' this one
http://forum.xda-developers.com/showthread.php?t=332071
good luck

aymn_louis said:
i mean dry that it does not leave any traces on sprayed place after a while .. some other magnetic cleaner sprays leaves an oil layer over the sprayed area ..
ask in your location for a magnetic head spray cleaner and i am sure you can found one easily
it is now about 1 week and i had no problems
thanks
Click to expand...
Click to collapse
Hi aym_louis "big mind"!
Yesterday I immediately went to buy the spray "deoxide for contacts" instead of "magnetic heads cleaner". It was not the kind that also protect the contacts, so it doesn't leave the oil layer on them.
Well...I opened the mda pro, sprayed all over the motherboard and waited for 20 mins. I inserted the sim and didn't work....at first!
I tried after some more time, and it worked, and kept working 'till now...thing that never happened before! Maybe it needed more time to deoxidate the mysterious contacts.
Really good idea! You solved a big problem, in a easier and more secure way, compared to the hot hair flow!
Weeel done!

thanks dear .. any time

ajay8008 said:
hey aymn_louis
I also suffered with sim card problem and got the solutions please check your PMs, sent you the web address to download it, have used it myself, works good.
Currently i m usin' this one
http://forum.xda-developers.com/showthread.php?t=332071
good luck
Click to expand...
Click to collapse
sorry .. didn't notice your PM . anyhow you've got your problem solved

Yes problem solved

Hey Guys,
I also have this problem for a long time and I'm using another device now..
to summarize:
1. I need a magnetic head cleaner? not contact cleaner?
2. Which chip should I spray? on which side of the MB?
3. Should I go the "hot air blower" route at all?
It's a really annoying problem!
Thanks,
Ariel

aymn_louis said:
i had the same problem .. and i tried another solution .. i got a dry magnetic head spray cleaner and i sprayed the whole mother board connectors .. it worked as a start with me and i am waiting if it will remain good or will happen again ..
Click to expand...
Click to collapse
I've got the same problem, and I've tried yuor solution but it doesn't work for me.
I've used a dry magnetic head spray cleaner on the motherbord (front and back) but the problem is the same ..Sometimes SIM Card is missing..
I noticed that if the settings of the phone (Band) I force GSM (not Auto) error occurs less frequently..
any Idea?

It worked great!!!
Just tried the dry magnetic head cleaner spray and all I can say is it WORKED GREAT on my Uni, which was displaying that «Invalid or missing SIM card» annoying message!!!
I disassembled the unit completely (this included removing all the inner metallic "shields" fitted to both sides of the mainboard), sprayed the mainboard on both sides repeatedly and quite abundantly and allowed it to dry for an hour.
On the first reboots it kept getting stuck on the 1st splash screen, so I waited for another hour, for it do dry completely.
I then performed a hard reset on the Uni(t).
It simply worked. My SIM card is now recognized again.
I'm on my 4th reboot since I've reassembled it and the OS loads completely, I've reinstalled the software applications I lost after the hard reset and my SIM card keeps being recognized by the Uni and allowing me to make / receive phone calls & text messages.
Thanks a lot for the hint.

pitermaikal said:
Just tried the dry magnetic head cleaner spray and all I can say is it WORKED GREAT on my Uni, which was displaying that «Invalid or missing SIM card» annoying message!!!
I disassembled the unit completely (this included removing all the inner metallic "shields" fitted to both sides of the mainboard), sprayed the mainboard on both sides repeatedly and quite abundantly and allowed it to dry for an hour.
On the first reboots it kept getting stuck on the 1st splash screen, so I waited for another hour, for it do dry completely.
I then performed a hard reset on the Uni(t).
It simply worked. My SIM card is now recognized again.
I'm on my 4th reboot since I've reassembled it and the OS loads completely, I've reinstalled the software applications I lost after the hard reset and my SIM card keeps being recognized by the Uni and allowing me to make / receive phone calls & text messages.
Thanks a lot for the hint.
Click to expand...
Click to collapse
congratulation on your WORKING mobile

Hi Guys,
For what it's worth i have exactly the same problem on my G3 device. I used Servisol Video 40 from www.maplin.co.uk which is a tape head/disc drive cleaner, and it says on the can that it "removes tape oxides and dirt". I removed the shields around all the qualcomm chips and covered the MB, let it dry in sunlight (took 10 mins), reassembled and the problem is still exactly the same, i.e. this method DID NOT work.
For those of you who DID get this to work it would be very useful to know EXACTLY what cleaner you used.
It would also be helpful to know how 'permanent' the fix was, and if anyone else has tried what I have and succeeded or failed?
Many thanks for the helpful posts, if I can get this solution to work it would be awesome. If not then it's onto the rework station and who knows what then.
Cheers,
Appy

I am suffering from the exact same problem; can those of you who fixed this horrendous issue by spraying your motherboards, could you please confirm that your devices are still free of that "missing sim card" error. And what brand of spray did you guys use? If at all it makes a difference.
Thank you.

I cannot find anything in stores remotely similar to "dry magnetic heads cleaner spray" if you guys know the brand name of this product or an alternative, please post your replies.
Your help is greatly appreciated!

found contact/head cleaner at the source; sprayed once then tested, it didn't work. Sprayed second time then tested, it didn't work either but managed to keep the phone alive without loosing the sim for a few hours. I guess will be spraying the third time in a few days...
If anyone has any suggestions please feel free to share.

Touch screen going wild when charging

Hello guys, my touchscreen going crazy whenever I'm charging the phone.
Doesn't receive input half of the time. No matter which charger / rom / kernel I try with, problem still there.
The weird thing is, it doesn't happens whenever I'm in TWRP.
Anybody knows the problem? making me charge the phone only at night...

gal_b said:
Hello guys, my touchscreen going crazy whenever I'm charging the phone.
Doesn't receive input half of the time. No matter which charger / rom / kernel I try with, problem still there.
The weird thing is, it doesn't happens whenever I'm in TWRP.
Anybody knows the problem? making me charge the phone only at night...
Click to expand...
Click to collapse
I'm betting that your digitizer is going bad - mine did similar things, then parts of the touch screen stopped responding - had to reset the touch screen several times (cat /sys/devices/virtual/input/lge_touch/f54 seemed to work for some duration of time). I eventually (as of yesterday) replaced the LCD/digitizer and it now works correctly (apart from the fact that I screwed up the new screen, that is).

I would try to open back cover and attach digitizer connector cable properly (next to Jack connector). This worked for me, when I had same problem
Sent from my LG-D802 using XDA Free mobile app

robotzki said:
I would try to open back cover and attach digitizer connector cable properly (next to Jack connector). This worked for me, when I had same problem
Sent from my LG-D802 using XDA Free mobile app
Click to expand...
Click to collapse
Do you have a tutorial? how does it looks? (the digitzer connector). If not, can you shoot one for me? it would be great, because i'm not an expert

gal_b said:
Do you have a tutorial? how does it looks? (the digitzer connector). If not, can you shoot one for me? it would be great, because i'm not an expert
Click to expand...
Click to collapse
Ive attached the image. on the black shield, i added extra tape to hold digitizer connector in place. Firstly make sure that connector is pressed in place properly.
I also glued down the left end of mainboard, so it couldnt wiggle anymore. Hope this helps... Id did for me!

well..... tried it... didn't help :/ but... here's one thing that looks weird to me: when i'm on jb - no problems. when i'm up to kitkat - the problem is back
WTF is GOING ON?!? also knock-on is gone now... brb throwing my phone on the wall

bump

[Q] Replaced battery - now touch screen doesn't work right

No amount of recalibration would correct my bad battery so I replaced the battery in my Nexus 10 (running lollypop). It was a complete pain to get the thing apart but it wasn't all that complex. I wanted to test it with the back off but the new battery was dead and I figured, “what could I possibly have done wrong anyhow” so I put it all together and charged it. I found out what I could do wrong. Now that I have it back together and fully charged the touch screen doesn't respond hardly at all. Everything else seems fine. I can boot to Android, boot to recovery etc... Like I mentioned above, taking it apart is a PITA and I'd like to only do it one more time and forever be done. I am guessing one of the 3 ribbon cables over the battery is for the touch screen. I'd like to only fiddle with the right cable only. Does anyone know which one specifically affects the screen?

Jerryp7
Did you find out what the problem was with you tablet. I have the same problem. I'm sure its the ribbon cables but I don't see anything out the ordinary. Thanks.
John R.

I had to open it back up (which is what I wanted to avoid because it was such a birch). Everything looked OK but I unplugged and replugged everything and it's been fine ever since. It had to have been one of the ribbon cables.

Replaced battery - now touch screen doesn't work right
Jerryp7
Thanks for the quick reply. I reopened the table and found the locking bar on one of the ribbon cables is broken. Any idea if they can be replaced?
Thanks again.
Regards,
John R.

Success!
Jerryp7
The clamp for the ribbon cable wasn't broken! The movable part had become detached. After many tries I figured how it went back together. I then found that it helps to hold the cable into the connector as you close the clamp.
Murphy's law rules again.
John R.

Glad you solved it. My only suggestion was to form a little plastic hold-down and super glue. If you ever had to do it again you could snip it off.

Jerry
The new battery still didn't correct the problem with the battery quitting at about 25% left. Do you know if there is any else I should try. I was in contact with Google before I replaced the battery and followed several procedures they suggested. Needless to say none of them worked. When I try to wipe the system cache partition I never get the screen that allows me to select the Recover mode. I get a screen with an arrow on the left that says "Start" and a droid in the center with the words "Downloading" under it. I let that run for over an hour but it didn't appear to do anything. If you have any suggestions I would appreciate them. Thanks.
John R.

Not sure. I'm not having any problems. Have you tried recalibrating the battery? I did that before replacing it which naturally didn't help a bad battery. Is you device rooted? I think it has to be to recalibrate. I use skipsoft unified android toolkit and have been for years. Last thing I did was upgraded to the OTA Build LMY49G which breaks root but the toolkit rooted it even thought Mark doesn't have the factory build availiable yet.

My connector broke when I was changing the battery. Anyone know how to fix it? There was little silver pins that came out. Thanks for help in advance.
Sent from my Nexus 7 using Tapatalk

For what it's worth... I had this same problem and was able to fix it fairly easily (if you don't count the PITA of opening the case again). The three cables have to be connected perfectly, which is why they are taped down. The one on the far right (if the device is oriented so the edge with the controls is on top) connects the LCD (it's labeled as such). I have lighted magnifying goggles that I use for many things. I carefully removed the tape (again), opened the locks (again), pulled out the cables, then pushed them gently back in, making sure they were in as far as they could go, all the way across (the goggles make all this very easy to see), and then closed the locks. I did this with all three ribbon cables. I then examined the tape for lint, cleaned off any dirt with 99% isopropyl alcohol and no-lint chamois swabs (just dab it lightly - don't remove all the glue), then pressed the tape down very firmly. When I closed the case again, all was well.
Opening the case isn't nearly as easy as those YouTube videos makes it look. But I'm so glad I did this. It's great to have a working battery again.
Next: Install Android 6!

JohnR0836 said:
Jerry
The new battery still didn't correct the problem with the battery quitting at about 25% left. Do you know if there is any else I should try. I was in contact with Google before I replaced the battery and followed several procedures they suggested. Needless to say none of them worked. When I try to wipe the system cache partition I never get the screen that allows me to select the Recover mode. I get a screen with an arrow on the left that says "Start" and a droid in the center with the words "Downloading" under it. I let that run for over an hour but it didn't appear to do anything. If you have any suggestions I would appreciate them. Thanks.
John R.
Click to expand...
Click to collapse
I have the same problem, replaced the battery tried 2 different recalibrate apps, tried factory reset, cleared cache and battery shuts down at 20% with no warning.

It's the first cable if you have the camera facing upwards. There is the 2 cables that are together, it's the first of those cables that controls touch on the screen. Just make sure it's seated correctly, press down on it some and close the tab and tape it back in place. I know this because I ended up having to take the back off again while the tablet was powered on after I replaced my battery because the screen wasnt working. I checked each cable and that first one was the one that controlled touch. My Nex10 is working as smoothly as it did when I first got it.

Samsung Galaxy S5 autorotate problem found.

So after weeks of trying to figure this out I've found what's causing the problem. Not sure how to fix it. When the phone stays on the charger the rotate will stay on. If your rotating stopped before plugging your phone or the charger then simply plug in ur charger and then restart and once ur charger stays plugged in then it should auto rotate some people my need to restart more than once. So in my view I'm thinking there is some electrical problem or lack of power or some how it's linked to the USB port. Please try it and report if u get the same result. Hopefully this will lead to someone finding a solution. Maybe someone can change their USB port and let us know if that solved the problem.

mickiemas said:
So after weeks of trying to figure this out I've found what's causing the problem. Not sure how to fix it. When the phone stays on the charger the rotate will stay on. If your rotating stopped before plugging your phone or the charger then simply plug in ur charger and then restart and once ur charger stays plugged in then it should auto rotate some people my need to restart more than once. So in my view I'm thinking there is some electrical problem or lack of power or some how it's linked to the USB port. Please try it and report if u get the same result. Hopefully this will lead to someone finding a solution. Maybe someone can change their USB port and let us know if that solved the problem.
Click to expand...
Click to collapse
most of auto rotation become malfunction is because lib file missing. especially if u're in custom rom or stock but doing some debloat.
check in your system/lib folder for file libgnustl_shared.so.
if missing, then auto rotate will not work. but in your case maybe hardware/sensor related problem.

an-_-dro said:
most of auto rotation become malfunction is because lib file missing. especially if u're in custom rom or stock but doing some debloat.
check in your system/lib folder for file libgnustl_shared.so.
if missing, then auto rotate will not work. but in your case maybe hardware/sensor related problem.
Click to expand...
Click to collapse
It would seem like hardware because the file is there.
Sent from my SM-G955F using Tapatalk

Ok. So I can say for sure my rotation issue is related to the usb port. At the begining when I plugged in the usb cable and restarted my phone the rotation would continue working until I removed the usb cable and even for a few minutes after removing it would still work
So what I did was get a very small piece of paper and made it into a little ball and push it under the contact of the usb port right up to the back so that the usb cable could still fit properly. The paper is just to brace the usb connection upwards a little and in doing do so my phone even charging better seeing I had charging issues so I guess it's part of the issue. Now I have normal rotation for weeks.
If rotation stops it's because the usb cable has crushed the paper too small so I just replace the paper but so far it's all good. I just dnt have the interest to do a usb port change but I think that would be a more permanent solve. Hope this helps. Just sharing my experience to those of you who have the same issue and can't find a fix.
Sent from my SM-G955F using Tapatalk

Usb port changed and rotation working flawlessly. I even recorded over 6000 steps and more than 12 minutes walking. Notified by S health, haven't seen that in a long time
Sent from my SM-G955F using Tapatalk

OK guys sad to say I'm bk on this because after awhile my rotation stopped again. I don't know if the replacement USB port is going bad again as it was a Used USB port or its something else but I have found another fix which seems to be working a few days now.
So this fix will require disassembling your phone again.
What I did was disassemble my device and when I reached to the main board I used a little screw driver to pry off the shine piece of covering that covers some of the chips which includes the gyroscope chip. U guys can google to see where the chip that controls the gyroscope is on your s5.
Then I folded a piece of tape and placed it on top of the gyroscope chip just thick enough so the metal covering when place back on it will squeeze the tape down on the chip. After all that is done reassemble ur device and try it out.
On a side not my proximity sensor was not working properly either and I did the same thing. Folded a piece of tape and place it behind the proximity sensor it will be tight again when phone is reassembled. So far its been working for me so I hope this helps.
I know its an old device and most of u might not see the need to fix a device this old but for those of you who like tinkering with ur device like myself u should try and let me know if it works for u.
HAPPY NEW YEAR.
Sent from my SM-G900F using Tapatalk

i have samsung SM-G906S. lately i have been facing the problems with auto rotation, proximity sensor and auto brightness adjustment. All these have stopped working. These problems are not with hardware because they vanish when i factory reset the phone of reinstall OS using samsung smart switch. but these problems occur again after some time (a month or two). seems like some problem with samsung firmware. too bad the official support from samsung has stopped for this phone.

A question for a new LCD Display

Hi
I bought a new screen and installed it but the touch did not work then I installed another screen and the touch did not work
What is the problem with solving it?

I'd say if two different screens have the same issue, it's the hardware problem with the phone itself. Could be the connector for the ribbon cable - if you have a magnifying glass or visor, see if you can find anything wrong with it. Try cleaning it (compressed air is the safest way, but sometimes a wooden toothpick works well, if you are careful). Also, make sure the adhesive "flaps" on both sides of the connector are properly attached to the grounding shield. Other than that, I have no other suggestions for a DIY fix...

mamdooh191 said:
Hi
I bought a new screen and installed it but the touch did not work then I installed another screen and the touch did not work
What is the problem with solving it?
Click to expand...
Click to collapse
Some have lost touch when they messed up flashing or when Essential Sep update had a problem, as I recall, I think they fixed it by side loading an OTA image. Research this first yourself (might be on reddit etc)
---------- Post added at 05:22 AM ---------- Previous post was at 05:10 AM ----------
Seems like it was Oct update, I was thinking of
https://forum.xda-developers.com/essential-phone/help/phone-lose-touch-flash-oct-update-t3849787

IronRoo said:
Some have lost touch when they messed up flashing or when Essential Sep update had a problem, as I recall, I think they fixed it by side loading an OTA image. Research this first yourself (might be on reddit etc)
---------- Post added at 05:22 AM ---------- Previous post was at 05:10 AM ----------
Seems like it was Oct update, I was thinking of
https://forum.xda-developers.com/essential-phone/help/phone-lose-touch-flash-oct-update-t3849787
Click to expand...
Click to collapse
Hi
Thank you brother for your reply
Do I install a new image from the mobile site?

kt-Froggy said:
I'd say if two different screens have the same issue, it's the hardware problem with the phone itself. Could be the connector for the ribbon cable - if you have a magnifying glass or visor, see if you can find anything wrong with it. Try cleaning it (compressed air is the safest way, but sometimes a wooden toothpick works well, if you are careful). Also, make sure the adhesive "flaps" on both sides of the connector are properly attached to the grounding shield. Other than that, I have no other suggestions for a DIY fix...
Click to expand...
Click to collapse
thanks YOU brother
This method did not work

IronRoo said:
Some have lost touch when they messed up flashing or when Essential Sep update had a problem, as I recall, I think they fixed it by side loading an OTA image. Research this first yourself (might be on reddit etc)
---------- Post added at 05:22 AM ---------- Previous post was at 05:10 AM ----------
Seems like it was Oct update, I was thinking of
https://forum.xda-developers.com/essential-phone/help/phone-lose-touch-flash-oct-update-t3849787
Click to expand...
Click to collapse
The method did not work

mamdooh191 said:
The method did not work
Click to expand...
Click to collapse
You haven't told us what happened when it first stopped working. Guess it must be hardware then. As KT said above, I'd look at their ribbon cable first if not a new one supplied, they crack easy & even if still touching over time the joint oxidises and then stops current following. Same sort of thing can happen in connector pins or solder joint on components, but you really need a very strong magnifier/eyepiece tool see it though you might get lucky. Also look for any signs of corrosion or dendritic growth, clean with a little alcohol if anything visible on nearby components on PCB.

IronRoo said:
You haven't told us what happened when it first stopped working. Guess it must be hardware then. As KT said above, I'd look at their ribbon cable first if not a new one supplied, they crack easy & even if still touching over time the joint oxidises and then stops current following. Same sort of thing can happen in connector pins or solder joint on components, but you really need a very strong magnifier/eyepiece tool see it though you might get lucky. Also look for any signs of corrosion or dendritic growth, clean with a little alcohol if anything visible on nearby components on PCB.
Click to expand...
Click to collapse
Hi brother
At first, the screen was broken but the device was still working after a while I passed the wrong picture and the device is not working, I installed a picture with the help of
https://forum.xda-developers.com/essential-phone/help/device-hung-start-t3891580
I installed the screen after editing and I had a problem with the touch
Your style brother did not work
Can AC Touch Crash? Or need a touchdriver on the device?

mamdooh191 said:
Hi brother
At first, the screen was broken but the device was still working after a while I passed the wrong picture and the device is not working, I installed a picture with the help of
https://forum.xda-developers.com/essential-phone/help/device-hung-start-t3891580
I installed the screen after editing and I had a problem with the touch
Your style brother did not work
Can AC Touch Crash? Or need a touchdriver on the device?
Click to expand...
Click to collapse
Am I right in saying,
at first the screen was cracked but touch was working,
then you flashed wrong image & touch lost
(what image? another stock image or something else? Or you flashed it to wrong slot (A or B))
But then you got it working by flash image from link above but then edited some file when you install new screen & then lost touch. What did you edit? Did the new screen ever work?
Don't know what AC Touch is, yes a driver would be needed which for touch screens is normally OEM embedded so should be in the chip of the cable of the new touchscreen, I think (I am not 100% certain on our phone though so possibly driver comes with Essential kernal) either way you should have one.
did you get whole screen assembly lcd+digitizer? Do you know for certain the screen you have is confirmed to work on our phone eg by another xda member? If yes then probably it's the file you have edited, then I think your problem is probably software, but it is not fixed by flashing a new FULL STOCK image (try different ones) then you have a problem only Essential can fix, but I don't think they will do this. maybe a more knowledgeably member can confirm some of this ...

Or you flashed it to wrong slot (A or B))
slot B

mamdooh191 said:
Or you flashed it to wrong slot (A or B))
slot B
Click to expand...
Click to collapse
We can't tell if that is right or wrong… it depends which slot you were on before… as it changes with each update on A/B partition phones. I don't know if flashing to wrong slot can give the problems you have though… I haven't read up on that problem...