Related
For some reason my Touch Pro (Sprint) shows that the headphones are always plugged in. I get no sound because the headphones icon is showing up, even though they are not attached to my device. If I attach the headphones I get sound. I can hear calls with the headphones but I cannot talk to people. For some reason they cannot hear me. I am running Juggalo's rom, I believe his original version. I have done a hard reset which didn't fix the problem. I would flash back to stock OS and get it serviced but my soft reset button doesn't work now for some reason.
Is there anyway to completely disable headphones so that I might be able to hook it up to my computer with active sync (because of the headphones showing as being activated I cannot use active sync)?
If not, is there any way I can flash my phone without using the Power + Vol Down + Soft Reset, or active sync?
Thanks,
Lord of the Midgets
I've got the same problem nobody knows what it is ?
i did not have it on my TPro - but I've seen this on a lots of phones, in 99% the reason was that the connector got some moisture / water > got oxidated > phone believes headset is plugged in. clean it with contact-cleaner fluid.
I ended up trading my phone in at Best Buy which is where I purchased it. Just bring your manufacturer warranty, which is in the booklet you should have received with the phone, and the phone to whatever retailer you bought it from. They have to honor the manufacturer warranty. If they say no talk to a manger and if he says no tell him you will go to corporate and he will almost instantly agree.
I can say that the performance on my new touch pro is so much better than the US launch version. I don't know what they did but it seems to perform better.
I'm sure there is a registry tweak to take this off. Since I know I saw someone post up that there was a tweak to keep it on so there was no need for headphones.
Hello all. I have HTC Surround from AT&T with updated 8107 firmware. I have spoted some strage bug (i don't know how else i could call it) and wanted to ask if thisone is possible and if i do think right. So i have this phone for about half a year and i'm pleased with it, nothing happened to it until now. Last week i was typing an SMS message and suddenly it just froze. I tried to restart it but the phone got stuck in the white HTC screen. My firmware then was 7720. I have done the hard reset and everything seemed to be ok but today the same thing happened with updated version too. I thought a bit and remembered that both times my phone was lying on top or near by wireless microphone receiver which was in working state. So can it be possible that some sord of electromagnetic waves is causing my phone to do this? Or it's just a coincidence?
as i'm a developer i didn't this it's a bug ithink it's accidentaly and you were at that place again like other time
But that's quite too big to be jusn an accident. I had this phone for half a year and nothing. Well i'll try this Friday not to put it on top of the receiver and will post what happened. This thing scared my quite big, i thought that mmc is broken but i have checked the bootloader (i don't know how the screen with 4 colors is called, i think it's bootloader) and it showed my mmc working perfectly. If it was not because of microphones what could then be the problem?
OK tried that this Friday too. Same think - phone near the receiver - phone dies and i must hard reset it to work again. How is this possible? Which part of the phone messes?
Very possible that a strong magnet could do this. Internally the surround uses a microsd (there are guides here for upgrading it but taking the phone apart). I imagine a strong enough field could corrupt a microsd pretty easily. When u say wireless mic do you mean bluetooth?
No no no, i mean microphones which are used on stages, i work as a sound engineer and my phone always is close to receivers, close to controlers and other stuf i use. So to avoid further coruptions i should put my phone further from all equipment right?
OK after this other few tries i have found out that it does indeed mess my phone, i have tried holding it near wireless microphone receiver and my phone have frozen and when i placed my phone further from receiver nothing happened. So look out for that
r0mka said:
Hello all. I have HTC Surround from AT&T with updated 8107 firmware. I have spoted some strage bug (i don't know how else i could call it) and wanted to ask if thisone is possible and if i do think right. So i have this phone for about half a year and i'm pleased with it, nothing happened to it until now. Last week i was typing an SMS message and suddenly it just froze. I tried to restart it but the phone got stuck in the white HTC screen. My firmware then was 7720. I have done the hard reset and everything seemed to be ok but today the same thing happened with updated version too. I thought a bit and remembered that both times my phone was lying on top or near by wireless microphone receiver which was in working state. So can it be possible that some sord of electromagnetic waves is causing my phone to do this? Or it's just a coincidence?
Click to expand...
Click to collapse
Is frozen screen? Still completely can't use? I feel a little bit like WM6 era's problems. After a certain amount to you. May is hardware have dark disease.
Hi,
I've had two Moto G's. both have been returned/replaced due to the ear piece/speaker buzzing like a kazoo when someone speaks/audio is heard through it.
I can now only assume it's dust that's caused this to happen, as I use my phone in a reasonably dusty environment occasionally through work.
Has anyone noticed similar problems? Anyone know ways to prevent/cure this should it happen again?
I came here to post this same thing. Mine was fine until shortly after the latest ota. I plan on calling Motorola soon, just haven't gotten around to it.
Sent from my XT1034 using Tapatalk
Aerogriff said:
I came here to post this same thing. Mine was fine until shortly after the latest ota. I plan on calling Motorola soon, just haven't gotten around to it.
Sent from my XT1034 using Tapatalk
Click to expand...
Click to collapse
It could have changed after an update for me too. The only physical change could be the dust, but this seems unlikely because it excluded to a fairly modest amount very briefly!
iamtherealmungo said:
Hi,
I've had two Moto G's. both have been returned/replaced due to the ear piece/speaker buzzing like a kazoo when someone speaks/audio is heard through it.
I can now only assume it's dust that's caused this to happen, as I use my phone in a reasonably dusty environment occasionally through work.
Has anyone noticed similar problems? Anyone know ways to prevent/cure this should it happen again?
Click to expand...
Click to collapse
Have the same problem! I got a new moto g because the 1st one was doing this cracking sound during calls both on 4.3 and 4.4!
The one has the same problem AGAIN!! i am very angry with this because i feel like the phone is fake and very cheap with this extreme bad sound i will try contact motorola
Στάλθηκε από το XT1032 μου χρησιμοποιώντας Tapatalk
I'm also having this problem. In fact, I'm on hold right now with motorola as I call to swap my second phone for the same reason. I started having the problem on my first phone a few weeks ago. The second phone had the buzzing problem as soon as it arrived. In both cases the phones have buzzed intermittently and tapping them face down hard against my palm seems to stop the noise for a bit. That isn't a good option because you have to tell the person on the other end to hold the phone away from their ear while you do it. It suggests to me that there is something like sand in the speaker.
We have three phones. One other has had almost no use, while the third has had a huge amount of use as phone and audio player using the headphone. Yesterday the speaker on that last one stopped working altogether. It only works with headphones. I assume it doesn't recognize the headphones have been removed. I don't believe it had the buzzing problem.
I love the phones otherwise.
I have sucessfully solved the problem in two moto g's
Hello to everyone.
First of all, I'd like to thank to everybody that have been developing the threads that as made this possible.
I have read many pages trying to understand the problem.
But I'm going to explain the whole process. I HAVE DONE THIS WITH SINGLE CHIP MOTO G 16GB AND MOTO G 8GB BOTH GSM!!!!
You can find the problem starting the call in a quiet place and you'll see that the sound is good, then in the same call you put some music playing around you and you'll start to have the issue. Try it and you'll find that is what happens.
I've seen mostly on Ebay, that this earpieces are selling like cakes, but definetly you don't have a broken earpiece, and you can test it activating SETTINGS-» DEVELOPER OPTIONS-» USB DEBUGGING, then you go to the dialer an dial this code *#*#2486#*#* or you may see in app drawer an app called CQAtest, it's the same thing, but this is only possible with USB DEBUGGING ENABLED.
Now that you have entered in the test menu you see two bars, select the first one, then select AUDIO, after that you see EARPIECE, click on it and make the BUZZ TEST, when it starts you should put your phone next to your ear. You'll be listening an harmonic sound that starts on a lower frequency and goes to an higher frequency, and it wil be repeating itself.
In this step you can for sure know if you earpiece has problems, if you don't listen any distortion in the loop that it's played, THEN YOU HAVE A FULL OPERATING EARPIECE. Otherwise, it's faulty and you should replace it ( I REALLY DOUBT THAT YOU HAVE A FAULTY EARPIECE).
OK. Now that we have tested the earpiece and we found that has nothing wrong with it, we have to take another steps.
THIS INVOLVE FLASHING THE WHOLE FIRMWARE TO JB 4.3 BUT IT WILL WORK REALLY BEATIFULL
I've taken the Android 4.3-Blur_Version.14.91.11.falcon_umts.Retail.en.DE that is the one that really solve the problem, from sbf.droid-developers.org.
Both Moto G's were UK retail one with 4.3 first version (never updated, that so it couldn't install apk's unless they were downloaded from Playstore or GDrive) and the other one with 4.4.2, this can tell us that it is not a problem caused from updating firmware.
I really think even Motorola isn't aware of this problem caused by a little piece of software on the phone.
BEFORE YOU FLASH THIS FIRMWARE, YOU CAN TRY IF IT SOLVES THE PROBLEM GOING RIGHT TO THE SPOT.
Go to SETTINGS--» SOUND--» AUDIO EFFECTS.
Now you'll see a switch that can be turned to OFF, you can try this at first, go back all the way until the app drawer, search your dialer and make a call, could be to your voicemail or another service from your operator that you're sure you aren't paying. Iniciating the call in a quiet environment you can listen well but if you put some music to play from a radio or something that it is near from you, that will increase the surrounding sound and makes the problem reapears, if the switching OFF AUDIO EFFECTS doesn't solved the problem. Try this several times to make sure that the problem it is still there.
If the problem persists go to SETTINGS--» SOUND--» AUDIO EFFECTS and you'll see WIRED STEREO and SPEAKER. In the Speaker badge set Equalizer to OFF and repeat the process of the call in quiet and during the call add surround sound with a level that can match the volume of the call. Then again, if the problem resides in there it will reveal himself right in that point. Try this several times to make sure that the problem it is still there.
If the problem it is there after this whole process and tests, then to get rid of it FOR SURE, reflash or downgrade to the firmware I've mentioned before. After reflash, Go to SETTINGS--» SOUND--» AUDIO EFFECTS, select the SPEAKER badge and turn the equalizer to OFF.
Make the tests I've mentioned before in call quiet, and with surrounding music and you'll be pleased that THE PROBLEM HAS GONE FOREVER.
Hope I've helped.
Cheers
I'm on my 2nd Moto G due to the buzzing earpiece problem. My Moto G is running stock non-rooted 4.4.3.
I used the sequence you mentioned to run the BUZZ TEST and I didn't hear any distortion at all! Amazing!
I'm having some trouble following your instructions though. I did turn off Audio Effects completely. However, the problem still persists. Can you explain why this would produce a buzzy sound in the earpiece?
Possible Solution
Hi everyone!
I found a peculiar solution. Maybe don't work for everyone, but worked with my Moto G and it's very easy to perform.
First, some comments about my case:
I've followed every step described by @jomedeiros ...I performed the CQAtest and the buzzing noise is clearly heard in the BUZZ TEST, especially in the low frequency sound at the begin of the harmonic sound. I should clarify that the buzzing sound was almost unbearable, like a broken speaker.
My Moto G is running stock non-rooted 4.4.4 (latest ota).
I set all the audio effects OFF, equalizer to OFF, etc... etc... But the buzz was still there.
My solution?
Vacuum cleaner!!!
Yes, too easy right? But works!!
I removed the back cover of the Moto G and with the crevice tool accessory, aspirate all the sides of the phone, then for several seconds on the rubber piece where the cancelation mic was, and specially all over the earpiece metal grid, then tapping the phone face down hard against my palm and aspire the earpiece again, from one side to another (gently taking care not to scratch the glass with the vacuum accessory).
In the first round with the vacuum, the buzzing sound drops significantly, and with one second attempt, the earpiece returned to the original sound, clear and undistorted.
Well... In my case should be only dust, but worth the test because here in Argentina the technical service it can take up to 90 days :/
Perhaps it's worth noting I'm designer and don't spent too much time in dusty spaces. Maybe the little dust in the pockets is enough!. Who knows!
jomedeiros said:
Hello to everyone.
First of all, I'd like to thank to everybody that have been developing the threads that as made this possible.
I have read many pages trying to understand the problem.
But I'm going to explain the whole process. I HAVE DONE THIS WITH SINGLE CHIP MOTO G 16GB AND MOTO G 8GB BOTH GSM!!!!
You can find the problem starting the call in a quiet place and you'll see that the sound is good, then in the same call you put some music playing around you and you'll start to have the issue. Try it and you'll find that is what happens.
I've seen mostly on Ebay, that this earpieces are selling like cakes, but definetly you don't have a broken earpiece, and you can test it activating SETTINGS-» DEVELOPER OPTIONS-» USB DEBUGGING, then you go to the dialer an dial this code *#*#2486#*#* or you may see in app drawer an app called CQAtest, it's the same thing, but this is only possible with USB DEBUGGING ENABLED.
Now that you have entered in the test menu you see two bars, select the first one, then select AUDIO, after that you see EARPIECE, click on it and make the BUZZ TEST, when it starts you should put your phone next to your ear. You'll be listening an harmonic sound that starts on a lower frequency and goes to an higher frequency, and it wil be repeating itself.
In this step you can for sure know if you earpiece has problems, if you don't listen any distortion in the loop that it's played, THEN YOU HAVE A FULL OPERATING EARPIECE. Otherwise, it's faulty and you should replace it ( I REALLY DOUBT THAT YOU HAVE A FAULTY EARPIECE).
OK. Now that we have tested the earpiece and we found that has nothing wrong with it, we have to take another steps.
THIS INVOLVE FLASHING THE WHOLE FIRMWARE TO JB 4.3 BUT IT WILL WORK REALLY BEATIFULL
I've taken the Android 4.3-Blur_Version.14.91.11.falcon_umts.Retail.en.DE that is the one that really solve the problem, from sbf.droid-developers.org.
Both Moto G's were UK retail one with 4.3 first version (never updated, that so it couldn't install apk's unless they were downloaded from Playstore or GDrive) and the other one with 4.4.2, this can tell us that it is not a problem caused from updating firmware.
I really think even Motorola isn't aware of this problem caused by a little piece of software on the phone.
BEFORE YOU FLASH THIS FIRMWARE, YOU CAN TRY IF IT SOLVES THE PROBLEM GOING RIGHT TO THE SPOT.
Go to SETTINGS--» SOUND--» AUDIO EFFECTS.
Now you'll see a switch that can be turned to OFF, you can try this at first, go back all the way until the app drawer, search your dialer and make a call, could be to your voicemail or another service from your operator that you're sure you aren't paying. Iniciating the call in a quiet environment you can listen well but if you put some music to play from a radio or something that it is near from you, that will increase the surrounding sound and makes the problem reapears, if the switching OFF AUDIO EFFECTS doesn't solved the problem. Try this several times to make sure that the problem it is still there.
If the problem persists go to SETTINGS--» SOUND--» AUDIO EFFECTS and you'll see WIRED STEREO and SPEAKER. In the Speaker badge set Equalizer to OFF and repeat the process of the call in quiet and during the call add surround sound with a level that can match the volume of the call. Then again, if the problem resides in there it will reveal himself right in that point. Try this several times to make sure that the problem it is still there.
If the problem it is there after this whole process and tests, then to get rid of it FOR SURE, reflash or downgrade to the firmware I've mentioned before. After reflash, Go to SETTINGS--» SOUND--» AUDIO EFFECTS, select the SPEAKER badge and turn the equalizer to OFF.
Make the tests I've mentioned before in call quiet, and with surrounding music and you'll be pleased that THE PROBLEM HAS GONE FOREVER.
Hope I've helped.
Cheers
Click to expand...
Click to collapse
Can you send me another link for the Android 4.3-Blur_Version.14.91.11.falcon_umts.Retail.en.DE ? this site is off sbf.droid-developers.org.
thanks
ruibvb said:
Can you send me another link for the Android 4.3-Blur_Version.14.91.11.falcon_umts.Retail.en.DE ? this site is off sbf.droid-developers.org.
thanks
Click to expand...
Click to collapse
Hello everyone.
In the case of the moto G that had the 4.4.2 version, I've downgraded to this one, 4.3.
What is the cause of this problem?
I really don't know, but before reflashing with the mentioned firmware, I have tried all kind of things, also the vaccum cleaner (BUT BE CAREFUL WHEN YOU USE THE VACCUM CLEANER, IT CAN DAMAGE FOREVER THE EARPIECE) including reflashing with the original firmware (UK) among others and the only solution untill today remais the same. Reflash with the firmware 4.3 bold mentioned in the first post that I' ve wrote.
I can tell that both phones still working very nice until today, and the problem of the earpice has never happened. But both are in the version 4.3. and so far I can tell, everyone that has upgraded their phones have tons of problems with them, so mi wife and my mother prefer to stay with the 4.3 version (so do I because I don't like of what they have done to Android from the 4.3 to the day of today, I have a Note 2 and I'm still with the 4.1.2, because they've messed the Android system in the upper versions and I refuse to upgrade. So this are preferences of each user).
XDA doesn't let me post the direct link here to download the firmware.
So maybe throug pm?
Hope I've helped. Cheers
Another solution
ANOTHER SOLUTION TO SOLVE THE BUZZING BUZZ EARPIECE MOTO G
I have the same issue that many of us had, the buzzing earpiece.
SOLUTION:
- I bought 2 earpiece from ebay 3€ both.
- Then I dissasembly the phone, like is this youtube tutorial: https://www.youtube.com/watch?v=ycER7MH61l8
Its simple you only have to care about the conector, but slowly Ive done it.
- To desatach the battery I use a cut credit card to lift it up and to unglued the black conector from the screen. (i didnt use the hairdrier)
- Then I put the 2 earpiece BUT still making the buzzing noise!!!!
. Then I move the metal spring conector on the earpiece to make it stronger and turn it the other way to use the other 2 conectors that are in the motherboard.
- And voilá, the noise is gone!
The original earpeice probably was working, but I broke it when taking out.
(I know theres some mistakes, but you undestand)
jomedeiros can't put links so here the link for the rom
https://meocloud.pt/link/ba12605f-3e...ail_DE.tar.gz/
thanks to him
Is upgrading moto g to marshmello will solve the buzzing sound problem
Does upgrading to marshmello helps
Earspeaker always bRRRzzing
I post in this old thread because is the only I found googling which try to give some (and different) solutions to the earspeaker making "GRRRR".
My XT1032 has the problem. My first attempt was to wipe, than to reset, then to change TWO earspecker (one from England as OEM and one sold as compatible from Italy), then to try the simcard into another phone (and it works very well inside an Y300, I can't believe that into MotoG 2013 VS Y300 match the first loses ) then to unlock and install a Cyanogen, then rotating the speaker during assembly (in the printed circuit there are 4 fields to give connection and only a pair is used at time), then moving the 2 spring connectors to try to give better stronger connections. From one try to the other the problem persists also using the service menu. So at the last point I revert and changed again the speaker with the original piece. Vivavoice is good and the ear phones too, no distortion.
My conclusions? The original speaker is bad (and I can see that the transparent sheet of nylon is not well plain), the second was worse but very similar in results, the last was really bad and if with the original I obtain a distortion in a window in the low harmonic with the compatible I obtain a distortion in all the low harmonic, from start to the middle.
So, now, the question to anybody who has similar problems: maybe the two earspeakers I bought were not good, or maybe the circuit (I think the ampli) is broken?
Changing the phone because it works very well but not well as a phone is a bit..... frustrating, the battery (original) is good for my needs and the screen too, but trying to change other 1, 2, ... 10 earspeakers without a reply is a dead end....
Solved
moxmose said:
I post in this old thread because is the only I found googling which try to give some (and different) solutions to the earspeaker making "GRRRR".
My XT1032 has the problem. My first attempt was to wipe, than to reset, then to change TWO earspecker (one from England as OEM and one sold as compatible from Italy), then to try the simcard into another phone (and it works very well inside an Y300, I can't believe that into MotoG 2013 VS Y300 match the first loses ) then to unlock and install a Cyanogen, then rotating the speaker during assembly (in the printed circuit there are 4 fields to give connection and only a pair is used at time), then moving the 2 spring connectors to try to give better stronger connections. From one try to the other the problem persists also using the service menu. So at the last point I revert and changed again the speaker with the original piece. Vivavoice is good and the ear phones too, no distortion.
My conclusions? The original speaker is bad (and I can see that the transparent sheet of nylon is not well plain), the second was worse but very similar in results, the last was really bad and if with the original I obtain a distortion in a window in the low harmonic with the compatible I obtain a distortion in all the low harmonic, from start to the middle.
So, now, the question to anybody who has similar problems: maybe the two earspeakers I bought were not good, or maybe the circuit (I think the ampli) is broken?
Changing the phone because it works very well but not well as a phone is a bit..... frustrating, the battery (original) is good for my needs and the screen too, but trying to change other 1, 2, ... 10 earspeakers without a reply is a dead end....
Click to expand...
Click to collapse
Ok, problem solved: this time the eraspecker from eBay was good! It come, again, from england. The first two were simple broken new guarenteed not working special price original best than sh**t Pentium inside tax free etc etc. Maybe some rule should prevent to sell broken new spares damn!
Owned the phone for about a month now. Phone was working perfectly fine for the majority of this time. I use 2 different sims and they were both working smoothly until recently.
A few days ago, I woke up and the phone wouldn't recognize the Sim cards anymore. I took out the Sim tray, cleaned the Sim cards and the tray as thoroughly as I could and they both started working again. A few days later, I restarted my phone and both of the Sims stopped working again.
This time nothing I would do would solve the matter, so for the next few days the phone wouldn't recognize either Sim. I have unlocked the bootloader and rooted, factory reset it and updated it none of which seems to solve the issue.
I use this phone for gaming so last night to my surprise one of the Sims started working (sim was in for a couple of days) and all connectivity was perfectly fine - I tried putting in my other Sim as well but again the phone wouldn't recognize them anymore. Tried putting in only one card on the Sim 1 slot but it made no difference. I don't understand what the issue could be.
Do you have a converted CN version or did you buy a global version? (just curious, as far as I know only CN -> WW versions faced this issue and I would like to know if this is a coincidence or an issue with these versions. But I could be wrong as well)
Nevertheless I would make use of warranty and send it back to Asus to get it repaired.
Yeah it's CN version > WW ROM. It's absurd how randomly it was hit with this issue. Again, the phone was reading a sim card perfectly fine out of the blue last night, then when I took out the Sim tray to insert another card, went back to square one and wouldn't recognize either.
I know.. If you had searched this forum or the rog reddit you would have noticed there are multiple topics like yours and all people explained the very same. Seems totally random.. sometimes it works, sometimes not. Unfortunately no one was ever able to post an accurate answer of why this is the case or how to fix it. At least there is none here, on reddit or the zentalk forums.
Since all device so far were CN -> WW version I don't know any successful case. Asus mostly rejects the support and redirects people to their sellers but those mostly refuse to do something. (they probably know that issue and it's cheaper to do nothing)
I wish you best of luck. Maybe you could try to contact Asus and report the outcome so we finally have a documented successful repair.
Edit: as said, that's only my knowledge, maybe there is a fix and someone found a way but they either didn't publish it or they posted it in a not so well known forum.
I wonder if the connections that touch the SIM are poorly designed. If it is such a widespread issue that randomly seems to come and go, it could be similar to the issue I had with the Kunai 3.
The pins on the side are designed to give a little when sliding the controller off and on the mount or charger. After moving them between the mount and charger twice, some pins fell off and others never popped back into place so they could make a connection. It turns out they never secured the pins well enough to handle it.
Hello, I had a similar issue.
My sim-cards wouldnt be recognized, sometimes only one of them, sometimes both. Additionally, my fingerprint-sensor wasnt working too. By checking pictures of a disassembled phone I could locate the problem inside. It has a connector on the lower end of the phone, which is for sim and FP-sensor. I can definitely and easily come loose.
Quick and dirty fix for me, was pressing with controlled but quite some force on the lower end of the LED-Rog logo while the phone laying flat on the table. I used my thumb, pushed and restarted the phone to check. Didnt work, pushed a bit harder and restarted again until it worked. The back glass has some flex to it, to make it possible to push the connector back in. Still, be careful to not break it, if you try it yourself.
When I found that solution, I've sent it in on warranty for proper fixing with this Information to ASUS. They replaced allegedly the mainboard. But I actually think, they just fixed the connector in place, because bending the phone to a certain degree "unfixed" it in my case again. I dont know, if its the same issue you have, but if it is, hope it helps everyone.
r0me5 said:
Hello, I had a similar issue.
My sim-cards wouldnt be recognized, sometimes only one of them, sometimes both. Additionally, my fingerprint-sensor wasnt working too. By checking pictures of a disassembled phone I could locate the problem inside. It has a connector on the lower end of the phone, which is for sim and FP-sensor. I can definitely and easily come loose.
Quick and dirty fix for me, was pressing with controlled but quite some force on the lower end of the LED-Rog logo while the phone laying flat on the table. I used my thumb, pushed and restarted the phone to check. Didnt work, pushed a bit harder and restarted again until it worked. The back glass has some flex to it, to make it possible to push the connector back in. Still, be careful to not break it, if you try it yourself.
When I found that solution, I've sent it in on warranty for proper fixing with this Information to ASUS. They replaced allegedly the mainboard. But I actually think, they just fixed the connector in place, because bending the phone to a certain degree "unfixed" it in my case again. I dont know, if its the same issue you have, but if it is, hope it helps everyone.
Click to expand...
Click to collapse
Good tip and glad it worked - this could help a few out there. Perhaps ASUS should have included some instructions explaining how to press/bend the device back in order when it happens ...
I had the same issue and quickly found a fix. I bought a OnePlus 9 Pro and relegated this glitchy piece of junk to my desk drawer. Good riddance.
nickdagriff said:
I had the same issue and quickly found a fix. I bought a OnePlus 9 Pro and relegated this glitchy piece of junk to my desk drawer. Good riddance.
Click to expand...
Click to collapse
Paying over $2,000 for a OnePlus 9 Pro seems like an expensive solution, but I am glad it worked out for you. Best of luck over there.
r0me5 said:
Hello, I had a similar issue.
My sim-cards wouldnt be recognized, sometimes only one of them, sometimes both. Additionally, my fingerprint-sensor wasnt working too. By checking pictures of a disassembled phone I could locate the problem inside. It has a connector on the lower end of the phone, which is for sim and FP-sensor. I can definitely and easily come loose.
Quick and dirty fix for me, was pressing with controlled but quite some force on the lower end of the LED-Rog logo while the phone laying flat on the table. I used my thumb, pushed and restarted the phone to check. Didnt work, pushed a bit harder and restarted again until it worked. The back glass has some flex to it, to make it possible to push the connector back in. Still, be careful to not break it, if you try it yourself.
When I found that solution, I've sent it in on warranty for proper fixing with this Information to ASUS. They replaced allegedly the mainboard. But I actually think, they just fixed the connector in place, because bending the phone to a certain degree "unfixed" it in my case again. I dont know, if its the same issue you have, but if it is, hope it helps everyone.
Click to expand...
Click to collapse
Works like a charm here! Congratz!
Omg worked here too, now I have a Poco F3 AND a revived ROG Phone 5...
.
You are the mvp. I love this phone and using it for almost a year. Suddenly sim no longer detected. I tried everything, unlocked bootloader, update firmware. Hour and hours of trying to revive it. I even called Asus and they said to call the Chinese warranty support. Then finally came across this thread. Pressed down hard on the lower end of the logo of the phone on its back. Restarted and now it's detecting the sim again. Thank you so much
Hello all,
My 1 year old note 20 ultra bougth on wondamobile because it was cheaper that in my country and had the snapdragon version.
Just got this HUGE problem, i was watching a youtube video and the screen just got black all of a sudden, and for 2 days never lit up again.
I live in Europe and Samsung says they wont cover the warranty of it as it wasnt purchased in Europe.
This is completely ridiculous, the phone costed 1300 euros, top of the line.
And now all of the sudden just dies.
I have tried all the methods online and none of them works, conecting a hdmi usb c cable to the screen, the iphone conects but i can only see the hours and a lock, cant unlock the phone, even tried with a mouse and keyboard using a usb c hub and nothing works.
Anyone knows a real fix for this?
as a new screen is 400 € and i dont want to pay this value.
This never happened specialy with a high end phone.
The N20U has had some display issues... Sorry.
Likely the display, could be a connector, battery or mobo failure.
See if you have legal recourse, otherwise lean all over Samsung like a cheap suit.
In the end you may need to do it out of pocket.
Last drama free rollout from Samsung was the N10+Snapdragon (new ones still available for $800). I got a second one because of Samsung's and Android 11/12's lack luster performance.
Some don't think it's that bad...
I sure do, which why I stepped back and rejected 5G, variable rate displays, no flagships SD card slots and one of the most dysfunctional Android OS's ever released.
I'm in a holding pattern running on P and Q until the fallout settles. Minimum 1-2 years perhaps longer.
This problem also happens in the note 10, s20 and others.
The biggest issue is that its a phone from South Korea and im In Europe so the warranty isnt valid.
Was so happy with it until now. Its not the 5g, neither the Android version.
According to what i read this issue is caused due to the one ui 3.1 update.
Because if it was a screen problem the touch wouldnt even respond to touches and it does respond.
Battery was at 81 percent went this happened, and the mobo for sure is good as i can conect the phone to screen and see it like Dex problem is the phone is locked so i cant unlock it even using this option.
And once again as the screen is locked it isnt recognized by usb so no program will work to get the data out of it or try any solution using dex.
As its a version bougth in Sk when i called the assistence they say they cant even do nothing because they only get parts for European phones and that parts are diferent, but the screens must be the same in both versions what differs is the mobo.
This is giving me headaches
Are you saying the update is causing hardware failures or that the black screen is not hardware damage but a just firmware issue?
The phone was working fine.
Until with the last updates the wi fi got inconsistent and i have the best and fastrst internet in my country.
Also as in this image shows the phone does work , problem is i cant unlock it. If i could probably could reset the software.
As the screen only had a minor scratch, so it was never damaged.
Now a 1300 euros phone is just a paper weigth
If it's a firmware you may be able to pull up the boot menu... and go from there.
This is beyond my skillset but it's not a paperweight yet.
I tried it all.
Would be easy if it worked via usb or via dex.
But its stuck in it.
This is a Samsung problem on the latest phones.
Raid3n__pt said:
I tried it all.
Would be easy if it worked via usb or via dex.
But its stuck in it.
This is a Samsung problem on the latest phones.
Click to expand...
Click to collapse
Try letting it fully discharge until auto shutdown if possible.
Physically disconnect the battery, hard reset.
Try some Google searches to find more options.
You might need to pay a repair shop or Samsung to fix it.
It wont shut down. Its like this for 2 days
Removing the battery will be dificult also.
Yeah its going to cost 400 euros for a phone npw worth near 900 or less altough its unlocked.
Will never buy a flagship again.
You don't need to remove the battery, just disconnect it. Watch a tear down vid.
You need a heat gun or pad, anhydrous isopropyl alcohol to help break the rear cover adhesive, plastic picks and perhaps some drivers maybe not. A new OEM rear cover seal.
A good phone repair shop can easily do this for you. Start there and see what you got.
The QC was solid on the N10+ Snapdragon but less so after especially on the S21U.
If the display needs to be replaced that should be the end of your problems with it.
Not perfect but what are you gonna do?
With Samsung, all phones it's best to wait 6 months and see what crops up. Otherwise it's more of a gamble.
I was indeed going to buy the note 10 plus back then but then i saw the n20 and all the advertisement and let myself into the hype.
Even bougth first a oneplus 8 pro but it got stolen in spain and i was refunded
Well going to try for one more day and see if it comes back to life,wich seems like a dream rigth now.
In last case will try a techician but its going to be expensive as this is a korean phone in europe.
Raid3n__pt said:
I was indeed going to buy the note 10 plus back then but then i saw the n20 and all the advertisement and let myself into the hype.
Even bougth first a oneplus 8 pro but it got stolen in spain and i was refunded
Well going to try for one more day and see if it comes back to life,wich seems like a dream rigth now.
In last case will try a techician but its going to be expensive as this is a korean phone in europe.
Click to expand...
Click to collapse
May not be as bad as you think.
Shop around. Getting the right replacement parts is critical. I know on the 10+ the C port pcb, cam module, and obviously the mobo are different and not interchangeable, not sure about the display!
Lol, found out the hard way with the C port pcb, there are 2 variants for the Snapdragon! My C port wasn't bad but was replacing the battery so decided to do the C port for $20 more. No cell service, no internet... put the original one in, back in service. Rather irritating
Ricky tricky Sammy...
This seems to be a design fault so Wonda should honour a repair or replacement. I would pursue it with them.
I also have a N20U SD HK version bought from them but it's only 6 months old.
I take it their warranty is just one year then?
Yes its only one year. And i bougth last october
And the problem is that i live in europe, wonda mobile is from china.
I dont know if its a design flaw or update problem as the phone magicaly started to work witouth the screen theme i had but i puted it down and the screen once again went off.
The phone was working back again for 10 minutes and black out again.
So the screwn migth be good.
I got a message saying the one ui stoped working when i used dex.
Dex mode with a usb c hub now works, but i cant put the phone back to stock while in dex.
Its in portuguese language but what it says in the message is that a one ui error happened.
This after the screen black out again.
In dex i cant put firmware back to stock but can update the firmware.
This is just stupid a 1300 phone with a faulty screen or software problem.
Cant figure it out. As the touch isnt working while is conected to dex, only worked using a mouse and keyboard.
But the touch worked when the screen went back on even for 10 minutes.
So if it works on dex it cant be mobo or battery.
If its the screen i will be 400 euros in pain.
Who would guess this n20 purchsee on wonda mobile would be a nigthmare
Likely a hardware issue...
blackhawk said:
Likely a hardware issue...
Click to expand...
Click to collapse
But how if it works in dex mode, everything works in dex mode, internet, cameras as well, games open, so the mobo cant be bad.
Guess the crap screen is gone for once, as it was only on for 10 minutes. Or maybe something disconected as i droped like 2 or 3 weeks ago but that cant be checked witouth opening.
Raid3n__pt said:
But how if it works in dex mode, everything works in dex mode, internet, cameras as well, games open, so the mobo cant be bad.
Guess the crap screen is gone for once, as it was only on for 10 minutes. Or maybe something disconected as i droped like 2 or 3 weeks ago but that cant be checked witouth opening.
Click to expand...
Click to collapse
When I said hardware I was implying the display.
It still could be a loose/bad connector as well.
The mobo's not entirely ruled out yet but a less likely candidate.
This seems to have happened to a lot of other people too, and some of them have said the display has come back on.
Samsung need to get a grip and offer some advice to affected cusomers.
For sure it seems the display is gone.
Samsung would replace the screen if it was bougth in Europe amd the screen had no damage.
Mine has a minor scratch and a very small mark due to a drop.
Anyway seems there wont be any fix, as the crap screen only worked for 10 minutes so no hope for it to be back on again
Samsung never again