NFC? - Mate 8 Q&A, Help & Troubleshooting

Has anyone got NFC to work?
You have an option of choosing NFC secuity chip by choosing kne of the sim slots
But it does not read any nfc tags
M

I'll admit I had a time trying to get nfc to work. Just sending a picture to my wife (who also has the Mate 8), was a task. I finally got it to work when we took our cases off.

dpagoh said:
I'll admit I had a time trying to get nfc to work. Just sending a picture to my wife (who also has the Mate 8), was a task. I finally got it to work when we took our cases off.
Click to expand...
Click to collapse
First i read "clothes" then "cases" ... :laugh:

lol, it just needed a little LUV baby!

have you found the solution? mine also not working and been trying to reset as well... this is a nightmare!

I had my NFC work as mobile payment. It works smoothly.

AL10 reflashed to L29
NFC doesnt work, i try to read card, on oher phone works
kangvip b170

On my AL10 NFC works. I transferred a video I had taken to a friends Samsung phone through NFC and it worked fine. I was running KangVIP B168 at the time but NFC should work on stock as well.

jbmc83 said:
it just needed a little LUV baby!
Click to expand...
Click to collapse
what you mean ? or just laughing ?
i dont try took case off yet (it is not metal) and very hard do it

Its a very strange but after i took of case ... it works. I put phone back in case and ... work again... In other apps works too... In same app that dont work earlier... Nothing other changes - only on off NFC button, try to send photo via NFC ... May be first launch was hard ? I start thinking thats needed to receive next level in Hogwarts
AL10 KangVIP 170 4/64

dpagoh said:
I'll admit I had a time trying to get nfc to work. Just sending a picture to my wife (who also has the Mate 8), was a task. I finally got it to work when we took our cases off.
Click to expand...
Click to collapse
I tried this with another Mate 8, made the 2 Mate 8 "kiss" close to where the camera is. The other phone recognized a tag which it could not read (My Mate 8). That was L29C185B560. I just updated mine to L29C636B563... I tried to NFC with a Windows Phone. No luck.
Pretty pissed now!

I also have a problem with NFC on my Mate 8.
Current firmware L29C636B563, previous firmware tested on L29C636B321 (and maybe L29C636B330)
First off, I was testing this with an LG Washer / Dryer with the "Tag On" logo. The LG Application could not detect the NFC so I will assume the problem is with the phone? Where exactly is this NFC strip they are talking about? No, even after updating to L29C636B563 Nougat OTA Push Update, my Mate 8 will still not work with LG Tag On.
So, I got curious as to whether or not NFC was working to begin with. I live in Canada. It is a very *backwards* country and NFC applications are few and not mainstream. Apple Pay just got introduced... and Android Pay is not even available for download... so... I never really had any use of NFC at all.
Anyway, I have another Mate 8 (not mine). It recently got an OTA push, L29C185B560. At that time, my Mate 8 was still at L29C636B321.
We tried Android Beam... I guess the instruction was to bring the phone close together (in this case - back to back) and both phones will detect each other... then you can tap content to the other phone...
Well... the L29C185B560 (let's call this C185 for short) made a sound and it picked up a tag, but that tag was empty... ?? My phone, the L29C636B321 (let's call this C636 for short) did not do anything at all... it just stared and stared in outerspace....
I also tried to "Share" and then pick "Huawei Beam" and of course, nothing happened between the 2 phones....
I was suddenly discouraged... eeeks! No NFC? I thought this phone was the *super* phone... time to shop for another phone.
Just last week, my C636 got its first OTA update... uhm... only after downloading Firmware Finder... maybe it did something to the settings to correct it...
So, it got updated to C636B330 first, then 2 days later, C636B563 arrived. Yay... Nougat! What bugs are there?
Just 2 days ago, I tried to Beam with a Samsung Galaxy S4. No luck there...
So just this weekend, I tried Beam again... first, just putting the phone together... no luck.
Then, I thought... uhm... so this time, I put the phones together, back to back and then picked a photo on my phone, "Share" and "Huawei Beam".... surprise, surprise... I heard a tone.... I angled my head and saw that my phone recognized a device and I tapped and I guess the other phone, the C185 didn't need to accept the beam, it was already downloading the photo...
So I tried the LG Tag On again... no luck...
Then. I got home and downloaded apps to read my chip enabled Canadian passport (inside and outside the covers) and my Paypass enabled credit card... No... none of the apps detected anything.
To my understanding NFC will "communicate" once detected. No further action. In the experience with Huawei Beam... it seems that an "action" has to be triggered for NFC to activate? Maybe I am wrong and have been wrong all this time?
So, does "reading" an NFC tag also require an action?
What else is broken?
I found some documentation on Huawei Mate 8 NFC. Maybe someone with more experience will be able to explain this occurrence way better? Give us more insight and get it working?
I just bought 10 NFC Tag stickers on eBay, let's see late on if the phone actually reads it....

Thank you for this. I had sworn my NFC was dead, then I took the extra step you mentioned of trying to send a picture using Beam, and that appears to have woken the NFC chip up. I can't believe it's working fine now.
Cheers!
childoftheworld said:
I also have a problem with NFC on my Mate 8.
Current firmware L29C636B563, previous firmware tested on L29C636B321 (and maybe L29C636B330)
First off, I was testing this with an LG Washer / Dryer with the "Tag On" logo. The LG Application could not detect the NFC so I will assume the problem is with the phone? Where exactly is this NFC strip they are talking about? No, even after updating to L29C636B563 Nougat OTA Push Update, my Mate 8 will still not work with LG Tag On.
So, I got curious as to whether or not NFC was working to begin with. I live in Canada. It is a very *backwards* country and NFC applications are few and not mainstream. Apple Pay just got introduced... and Android Pay is not even available for download... so... I never really had any use of NFC at all.
Anyway, I have another Mate 8 (not mine). It recently got an OTA push, L29C185B560. At that time, my Mate 8 was still at L29C636B321.
We tried Android Beam... I guess the instruction was to bring the phone close together (in this case - back to back) and both phones will detect each other... then you can tap content to the other phone...
Well... the L29C185B560 (let's call this C185 for short) made a sound and it picked up a tag, but that tag was empty... ?? My phone, the L29C636B321 (let's call this C636 for short) did not do anything at all... it just stared and stared in outerspace....
I also tried to "Share" and then pick "Huawei Beam" and of course, nothing happened between the 2 phones....
I was suddenly discouraged... eeeks! No NFC? I thought this phone was the *super* phone... time to shop for another phone.
Just last week, my C636 got its first OTA update... uhm... only after downloading Firmware Finder... maybe it did something to the settings to correct it...
So, it got updated to C636B330 first, then 2 days later, C636B563 arrived. Yay... Nougat! What bugs are there?
Just 2 days ago, I tried to Beam with a Samsung Galaxy S4. No luck there...
So just this weekend, I tried Beam again... first, just putting the phone together... no luck.
Then, I thought... uhm... so this time, I put the phones together, back to back and then picked a photo on my phone, "Share" and "Huawei Beam".... surprise, surprise... I heard a tone.... I angled my head and saw that my phone recognized a device and I tapped and I guess the other phone, the C185 didn't need to accept the beam, it was already downloading the photo...
So I tried the LG Tag On again... no luck...
Then. I got home and downloaded apps to read my chip enabled Canadian passport (inside and outside the covers) and my Paypass enabled credit card... No... none of the apps detected anything.
To my understanding NFC will "communicate" once detected. No further action. In the experience with Huawei Beam... it seems that an "action" has to be triggered for NFC to activate? Maybe I am wrong and have been wrong all this time?
So, does "reading" an NFC tag also require an action?
What else is broken?
I found some documentation on Huawei Mate 8 NFC. Maybe someone with more experience will be able to explain this occurrence way better? Give us more insight and get it working?
I just bought 10 NFC Tag stickers on eBay, let's see late on if the phone actually reads it....
Click to expand...
Click to collapse

Actually, never mind. It's dead again. I have no idea what I did to make it work for a short while,
but now it won't read my cards anymore. (sigh)
r0bgar said:
Thank you for this. I had sworn my NFC was dead, then I took the extra step you mentioned of trying to send a picture using Beam, and that appears to have woken the NFC chip up. I can't believe it's working fine now.
Cheers!
Click to expand...
Click to collapse

Repair
Same case but i have found the reason.
The nfc antenna is embedded in to top side of back cover.
It's connected not with flex cable, but with spring contacts
2 screws on bottom
open carefully (fingerprint scanner on cover is connected with flexible cable)
adjust spring contacts
clean contacts and contact pads on cover with alcohol or ...
that's all
now it works

Related

Wallet - Won't actually pay.

I've got Google Wallet installed, and cards activated, but I can't seem to make it actually pay...
A couple of trips to the local McDonalds - waking up my phone and waving it over the red sensor part of their card reader does nothing... unlocking or having wallet open at the time doesn't help either.
What am I doing wrong?
Sent from my SCH-I535 using xda app-developers app
Does your phone beep to let you know the nfc receiver has picked up an rfid signal?
Sent from my SCH-I535 using xda app-developers app
Did you have the NFC box check under settings more settings. It allows information to be sent between NFC device which is necessary.
Sent from my SPH-L710 using Tapatalk 2
No response at all from my phone or the terminal. Might as well have been waving my hand over it.
Does the phone need a physical "bump" instead of a wave to do its thing? I would expect this to work much the same as my proximity company ID badge.
NFC is turned on. SBeam is off (does that matter?)
Sent from my SCH-I535 using xda app-developers app
I always touch my phone back to the spot on the card reader. Do you have a case on your phone? There is only like a half inch of play before the phone is too far away. Try it again by tapping the phone.
Sent from my SCH-I535 using xda app-developers app
yeah. i get embarrass too if wallet doesnt work. how embarrassing!
but they have nfc soda vending machines in Atlantis hotel casino in reno! i tried it there with wallet on my nexus without the embarrassment and it works!
https://www.youtube.com/watch?v=OEwHMk4qFTs
"waving it over the red sensor part"
You dont know what your doing if you "waved" it. You must hold it up to the scanner for it to recognize. Also, if you have a case, it takes longer to pick up because the case adds thickness which reduces the bandwidth NFC can utilize due to a weaker signal.
Experiences: 8 successful payments. 1 failed (Walgreens isnt there yet)
There is no red sensor where I used it. 7-11 and cumbys. It's the grey part above the debit/credit card scanner that has the nfc symbol....Walgreen's failed for me also the manager said they just recently installed.
Sent from my SCH-I535 using xda premium
I've had the same exact problem as the OP. I tried mine at a local gas station where a friend works so I didn't look like a complete dunderhead and I tried it on 6 separate occasions and tried installing it several different times/ways and could never get it to work. They have the EZ Pay NFC reader above the credit card machine and every time I tried it it would not work no matter if I tapped it, took it out of the TPU case, got the cashier to hit credit, opened and unlocked the app. Nothing. It just simply refused to work. Maybe I'm just an idiot though, I just assume the EZ Pay NFC card reader would read my NFC chip in my phone. Maybe it won't. I am just at a loss. I just reset the app and went to my backup nandroid and left it along after all the attempts because I was so embarrassed.
i've only used it once thus far, i was worried it wouldn't work right since i never used NFC payments before so i had no idea how to do it......it took about 15 secs for GW to open up from a locked status on my phone then about another 20 secs for it to recognize the nfc scanner and to process a payment to mcdonalds, not bad, i had my card out in preparation though lol
Try without a case.I had no comm using NFC due to my case blocking the signal somehow. took it off and now it works every time.
Sent from my galaxy nexus using xda app-developers app
digitalsynner85 said:
i've only used it once thus far, i was worried it wouldn't work right since i never used NFC payments before so i had no idea how to do it......it took about 15 secs for GW to open up from a locked status on my phone then about another 20 secs for it to recognize the nfc scanner and to process a payment to mcdonalds, not bad, i had my card out in preparation though lol
Click to expand...
Click to collapse
I had thought that maybe it would take a bit for GW to notice the NFC reader but i left it there for a full 5 minutes at one point, I was running my mouth, and it never pulled up GW nor recognized the NFC reader. Also this was with the phone off. Another thing I found funny about it was that it the app would not pull up as Ready to Use until I had let it set up my Play Store credit card they have on file. I dont know if the OP is having the same exact problem as I am but it sounds exactly the same. I have also tested my NFC with my girlfriends GS3 to see if maybe I recieved a bad battery or maybe my phone was somehow faulty but it pulled the fileshare using S-Beam off without a hitch so.....
shangrila500 said:
I had thought that maybe it would take a bit for GW to notice the NFC reader but i left it there for a full 5 minutes at one point, I was running my mouth, and it never pulled up GW nor recognized the NFC reader. Also this was with the phone off. Another thing I found funny about it was that it the app would not pull up as Ready to Use until I had let it set up my Play Store credit card they have on file. I dont know if the OP is having the same exact problem as I am but it sounds exactly the same. I have also tested my NFC with my girlfriends GS3 to see if maybe I recieved a bad battery or maybe my phone was somehow faulty but it pulled the fileshare using S-Beam off without a hitch so.....
Click to expand...
Click to collapse
My phone wasn't off, just locked. If the phone's off then the nfc reader is supposed to be off too. I found that just quickly opening GW right before touching it to the reader makes it happen almost instantly. At least for me already.
Beamed via NFC through the local store to the internet from my SGS3.
digitalsynner85 said:
My phone wasn't off, just locked. If the phone's off then the nfc reader is supposed to be off too. I found that just quickly opening GW right before touching it to the reader makes it happen almost instantly. At least for me already.
Beamed via NFC through the local store to the internet from my SGS3.
Click to expand...
Click to collapse
Sorry about the misunderstanding. When I said off o meant my screen was locked. My phone just edited that part out. I have tried it like you did also, by opening the app right before touching it to the reader. Still doesn't work. It may just be an issue with my phone. No matter how I try to use it to pay it won't work...
i've had no issues having my nfc chip being scanned but i have yet to complete a purchase successfully. i'm going to chalk it up to the terminals not being configured correctly... my other nfc functions work fine.
Some dont work for some odd reasons because the storemanager/higher ups dont know what it is so they might have disabled it for what ever reason.
I know Walgreens has scanners but does not work JUST yet, they are partners of the whole NFC movement thing.
Stores that have worked for me are.
Chevron, 7-11 ( had to tilt there scanner up), McDonalds, BJ's (like walmart), Vending Machines.
Doesnt work: Walgreens, Some Random gas station out of town
I find that if you see a LED blinking or on thats connected to the scanner, the scanner works, but if it doesnt scan right away its the case's fault or not placing it.
Source: I like to consider myself a Wallet expert haha, my thread is over in Developer Section to get wallet as well. Also all my purchases have been used using a Otterbox Defender, and take about 3-5 seconds to complete the transaction.
mine failed as well at a jack in the box drive thru. looked like a fool. haha
i took my case off, opened the app, clicked the lock in the corner, entered my pin, and held it up against the reader for a good few seconds but nothing happened. nfc was on. their reader had like 4 spots for lights and the first one was on with a solid green light so not sure, hopefully it was their reader. will try again at a 7-11 if I can get over the embarassment
LOL at you guys thinking your case is giving you a problem, most likely you are not putting the battery (where the NFC is) up to the correct part of the terminal (your phone should chime or make a noise when its recognized, just like when Android Beam comes up),
or just plain out the terminal doesn't work (not your phone), a mcdonalds and wendys in my area they have them but nothing happens and one mcd across town works perfectly fine. Just depends on the vendor.
I have the Otterbox Defender on both my S3 and Galaxy Nexus, and haven't had a problem or delay yet as long as their terminal is working correctly, and they are pretty thick cases. As long as you line it up right and they work shouldn't be a problem
NeoMagus said:
LOL at you guys thinking your case is giving you a problem, most likely you are not putting the battery (where the NFC is) up to the correct part of the terminal (your phone should chime or make a noise when its recognized, just like when Android Beam comes up),
or just plain out the terminal doesn't work (not your phone), a mcdonalds and wendys in my area they have them but nothing happens and one mcd across town works perfectly fine. Just depends on the vendor.
I have the Otterbox Defender on both my S3 and Galaxy Nexus, and haven't had a problem or delay yet as long as their terminal is working correctly, and they are pretty thick cases. As long as you line it up right and they work shouldn't be a problem
Click to expand...
Click to collapse
Well said and 100% accurate. I bet the problems people are facing are user error or the terminal just doesnt work.
I've used mine on about three different occasions and it worked perfectly. But what's funny, I was in a local vzw store buying something. They have what looks like the press pass set up, tried to use it and it wouldn't go through. The girl checking me out was surprised and had no idea that you could even do that. Anyway, my point is that even though the card reader looks like it will work, if they don't have it set up it won't. Vzw's looks just like the ones at McDonald's.

NFC not working with Android 5.0

Hey guys, I recently flashed the factory Lollipop image from my Nexus 5 (LRX210) and everything was running great.
Not soon after I set up my Tap & Pay, I realized that I couldn't complete my purchases. I thought maybe it was my Wallet app, or something was wrong with the priority of the wallet app, but that wasn't that case.
I tried beaming content via NFC to many other androids, but it was like my NFC card was dead. I didn't get any feedback from other devices, and even when I scanned a NFC tag it didn't react.
My NFC card was working fine before I went to 5.0, does anyone else have this problem? Really hoping I can get some info about it.
Thanks.
Bump :/
Sent from my Nexus 5 using XDA Premium 4 mobile app
me 2
Same here . my sony qx 10 wont conect . my g2 also . nfc is dead
So I guess very few have this issue then?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Try pressing down on the back cover where the qi and NFC connectors are. If that doesn't work then you'll have to open it up or RMA.
Lethargy said:
Try pressing down on the back cover where the qi and NFC connectors are. If that doesn't work then you'll have to open it up or RMA.
Click to expand...
Click to collapse
I was just reading up on it. Before I upgraded I opened up the back cover to show my friend the internals, then I snapped the cover back on (without pushing the back cover). A week past, then I updated to Lollipop. Another week has past since I upgraded and I just now realized the NFC wasn't working. I got my friend to let me use his wireless charger, and it worked fine. I also tried pushing the back in to hear that extra snap, but nothing has seemed to work.
Edit: I also flashed the factory image for KitKat, and NFC still does not work.
Perhaps I should be more detailed when I say "not working." The NFC does indeed recognize NFC tags and other enabled devices, however it does not vibrate like it should, or work like it should. I have many NFC tags that I bought and were working just fine. I tried them out 1 by 1 with my Nexus, and every time I scanned 1, a white screen would flash for a very brief moment, as if it was a windows opening and then closing before the animation finished. I used the NFC Tools app, and it recognizes the tags, but it can't read, write, lock, or do anything to them. I downloaded an app called NFCSniffer, and I get feedback from tags as well. But it seems as though my NFC chip is not working correctly ever since I opened the back. I'm really confused about this whole situation and wish I hadn't even opened the thing.
ToolB0x said:
I was just reading up on it. Before I upgraded I opened up the back cover to show my friend the internals, then I snapped the cover back on (without pushing the back cover). A week past, then I updated to Lollipop. Another week has past since I upgraded and I just now realized the NFC wasn't working. I got my friend to let me use his wireless charger, and it worked fine. I also tried pushing the back in to hear that extra snap, but nothing has seemed to work.
Edit: I also flashed the factory image for KitKat, and NFC still does not work.
Perhaps I should be more detailed when I say "not working." The NFC does indeed recognize NFC tags and other enabled devices, however it does not vibrate like it should, or work like it should. I have many NFC tags that I bought and were working just fine. I tried them out 1 by 1 with my Nexus, and every time I scanned 1, a white screen would flash for a very brief moment, as if it was a windows opening and then closing before the animation finished. I used the NFC Tools app, and it recognizes the tags, but it can't read, write, lock, or do anything to them. I downloaded an app called NFCSniffer, and I get feedback from tags as well. But it seems as though my NFC chip is not working correctly ever since I opened the back. I'm really confused about this whole situation and wish I hadn't even opened the thing.
Click to expand...
Click to collapse
Weird. In all the cases I know of, the NFC chip is either completely dead or just not connected properly. Try opening it up and putting it together again. If that doesn't help then I guess you'll have to replace the chip.
Lethargy said:
Weird. In all the cases I know of, the NFC chip is either completely dead or just not connected properly. Try opening it up and putting it together again. If that doesn't help then I guess you'll have to replace the chip.
Click to expand...
Click to collapse
Alrighty, I'll let you know how it goes.
Thanks for the responses.
Alright well I guess that didn't work... Can you recommend a good place to buy a chip?
ToolB0x said:
Alright well I guess that didn't work... Can you recommend a good place to buy a chip?
Click to expand...
Click to collapse
Not sure where exactly one would find them. Just have to search for one, or if they don't exist then I guess you'll have to send it to LG for repair.
Alright, thanks for the info.

NFC issue on my Mate 8 (L29C432B560)

Hello,
I have an issue with NFC on my Mate 8. Indeed, I tried to read the informations of a NFC credit card and it's very very very hard to detect the card (I have to push the card on the NFC antenna with my fingers and trying multiple positions before success). I have no issue with the same card and my old Nexus 5.
So NFC is working but it's like the NFC antenna power is too low.
I'm on L29C432B560 (EMUI 5, Nougat), never unlocked booterloader, never tried NFC on EMUI 4 and 4.1.
Any way to fix this?
My 2 years warranty will expire in one month so if it's an hardware issue I can always use it.
Surian said:
Hello,
I have an issue with NFC on my Mate 8. Indeed, I tried to read the informations of a NFC credit card and it's very very very hard to detect the card (I have to push the card on the NFC antenna with my fingers and trying multiple positions before success). I have no issue with the same card and my old Nexus 5.
So NFC is working but it's like the NFC antenna power is too low.
I'm on L29C432B560 (EMUI 5, Nougat), never unlocked booterloader, never tried NFC on EMUI 4 and 4.1.
Any way to fix this?
My 2 years warranty will expire in one month so if it's an hardware issue I can always use it.
Click to expand...
Click to collapse
Is is possible to draw a simple photo of the angle & location? What did you mean by "push the card on the NFC antenna with my fingers?"
--
Here's my sad experience:
kibrito said:
NFC antenna is placed on upper side of the back - above the camera. Use that area to touch when using NFC for file transfer, not the whole back of the phone.
Click to expand...
Click to collapse
OK...
I tried back-to-back, 'top to top'... Is there a specific angle? Maybe someone who has had success can draw a simple picture?
I have an L29C636B321 (recently updgraded to L29C636B330) ~ when 'back-to-backed' with another Mate 8 L29C185B560 (after many trials) - the L29C185560 seems to activate it's NFC as seeing a 'Tag' without information. My phone, the L29C636B330 did not do anything... nada... really, nothing.
It is becoming annoying now. I've had this phone for close to a year but never thought of using NFC until I bought an LG Washer with "Tag On". Of course, my Mate 8 was not able to read the Tag?? So I had to test.
Today, my L29C636B330 was officially upgraded to L29C636B561 Nougat. NFC and Huawei Beam turned on off course...
NFC back-to-back with my Lumia 1520 Windows Phone... not working.
NFC many positions with a Samsung Galaxy S4 (SBeam/NFC On) - nothing. Sharing a photo...
So is this phone broken from the get go?
It the firmware responsible for this?
Is there a hardware malfunction?
How do I get NFC to work???
When I used an App to detect NFC. It says, NFC is enabled but "no tag detected"?
HELP!!!!
See images here "Where is this NFC Antenna?"
https://forum.xda-developers.com/mate-8/help/nfc-t3286848/page2#post71873419
Hi,
I recently bought Mate 8 and I got the NFC issue as you describe.
I came to my mind when reading your post that you said "push the card on...".
Here is my solution:
1. Disassemble the phone, two screw off and open the rear cover.
2. You can see metal spring contacts on the top of the phone to connect the main board to the rear cover.
3. Raise the metal contacts to easily touch the rea cover.
4. Assemble back the rear cover.
Thanks

Question Sim recognition issue

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

Note 20 ultra black screen of death

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

Categories

Resources