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
Related
Hi All, I've down a fair bit of web searching but haven't found a reason as to why this would be happening. So here goes:
Basically, I bought the Asus P525 when it was about 9 months old, and after about 4 months it decided to flash this up on my screen - Invalid or Missing Sim Card. It seemed to fix itself, however, and I had another week of using it. Then, it did it again, and fixed itself again shortly after, but it wasn't long before it was dong it so often that the phone became unusable. It would flash that up, and usually stay that way, it would become a rarer thing for it to fix itself. So, back to my crappy old nokia with half working buttons I went, telling myself I should ring an Asus repair center and talk to them about it. Anyway, a couple of months later I got around to ringing them, they told me they'd probably have to replace the mainboard, and it could cost me more to do that than to get a replacement phone. Not very impressed as I was, I decided to boot the phone back up, and amazingly it worked again, and gave me another week of usage before packing it in. Now it's stopped working, so I tried different roms and different firmware, to see if that would fix it... nope.
So here I am. Anybody experienced this? Any idea what I can do? I don't have heaps of bucks to throw around on phones, I really like this phone except for this obvious problem, so would like to keep using it. But I don't think the future looks bright for it
Any help is extremely appreciated.
Thanks
Matt
Seems I've asked the impossible...? Anybody have any ideas? I'm going out of my brain trying to work this one out...
Matt
It seems noone in this part of the forum likes to answer questions I'm afraid.
As to your problem, it's likely a hardware fault and theres a loose connection betweeb SIM and phone somewhere.
You could try cleaning the contacts with an electrical contact cleaner solution sprayed on a cotton bud and wipe the pins that sit on the SIM.
Maybe you could also try using a needle underneath the pins and gently pull them up so that they make better contact with the SIM (maybe some are bent).
Bear in mind, I have no experience with this device and the sensible option would be to take it to a repair shop for service.
Hope that helps.
yeah I know what you mean
Thanks for the suggestions. I have tried to bend the pins up but that didn't work. I haven't tried cleaning the contacts... sadly though I think that may not be the issue. I'll definitely give that a go, I'll try just about anything, because obviously if I can't get it to work it will just sit in my girlfriend's car so she can use the maps and camera on it. Seems such a sad waste really...
thanks again for your help
Matt
I just powered it up, and it's working again. God knows for how long though... could it be a battery or cpu issue?
I am having issues with my Captivate's micro-USB port being loose. This is my second Captivate, and although it's still under warranty, the first one was RMA'd with the same issue. I never drop the phone while charging, etc, and I've tried multiple chargers so I really can't see why this would be happening. Both phones were 1008 versions, not sure if the 1008 is known to have this issue, or if I just have horrid luck. If anyone here can solder / fix the phone, I'm hesitant to go to AT&T again, as last time they made me go to the store and have the person working there verify that the USB port was not broken (luckily it still charged if you held it a certain way, and even more luckily I was able to flash stock before returning it!). Anyways, this phone is a refurb, and I did call and almost get it replaced as soon as I got it, as it had this issue slightly upon arrival, but decided it would be a hassle. It's only been about a month since the RMA, so I'm pretty sure that if I try now, they're going to get very mean about it, and possibly try and send me a bill for the phone, not to mention, the guy at the AT&T store will probably think something is up.
Any ideas are welcome, I love my Captivate, and I was just getting into develping on XDA :S
Sent from my Cappy using XDA Premium App
I actually found a fix to my issue. I actually was looking at it one day, and figured that in theory, it should be easy to fix, so I (CAREFULLY!!!) took a small knife I had and gently bent the inner part of the port up just a tad (it looked like it was too far down, and yes, I know it's supposed to be far down, but not that far), and it actually worked perfectly.
Thats weird... It kinda has to be what you're doing with it, since mine doesn't even have an irregular slight wiggle.
Obviously it could be just your luck but i doubt it.
edit: and who cares if the att dude thinks somethings up... its your $500..
Like I said, the second one actually had the issue upon arrival, but it was barely noticeable (the USB port would work, but if you moved the phone a lot, etc, it'd disconnect, then reconnect). I called in and talked to them, but decided not to RMA because it'd be a pain (in hindsight I should have...), and the problem just got worse.
Is the port internally lose? Or just when you plug a cable in it wiggles alot? Ive heard about people stretching the casing inside the port from alot of flashing (plugging in the usb). But if the hole port moves inside the phone thats no good lol. You should try to locate a nearby device service center and show them the problem and make sure you walk out with refurb thats fine. Dont worry about the people at atnt questioning it. Hell I use to walk in and just say "gps dosent work" and they would switch it out no questions.
What you said makes sense, the port looks like it's pretty sturdy, it's just that the cable wiggles a LOT, and it makes it hard to get it to even register.
I had the same issue but a new cable solved it
Sent from my samsung captivation
erraz said:
I had the same issue but a new cable solved it
Sent from my samsung captivation
Click to expand...
Click to collapse
I also had this issue, i opened up the stock Samsung Cable end to find that two of the four wires had insufficient strain relief and broke off at the solder joints
Oddly enough I had issues with the first cable as well, but I replaced it, and have tried others from my current.
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.
I've read a few threads on the screen Flickering and there doesn't seem to be any resolution .
I'm on my 3rd tablet now (thanks best buy accident damage warranty!) And this one is flickering worse lately than ever. I updated to the latest firmware, yesterday only to boot up to horrible bouts of flickering during the setup screens.
The odd thing is, there seem to be no consistency to it. Some days it's so had I can't even use the thing, other days it doesn't happen at all. I use the tablet every day for notes or PDF viewing. I've used it with no magnetic cover (totally naked) and with the cover.. doesn't seem to change the occurrences.
I've turned overlays on/off force gpu render on/off.. nothing seems to fix it. Sometimes changing the overlay will reduce the flickering other times it doesn't affect it at all.
I hate to say it, but if I can't resolve it, I'm going to be forced to move to the surface 3.
I'm an electrical engineer and I've done as much trouble shooting as I can think to do.. but I've come up empty handed.
Anyone else have these problems? Has anyone found a definitive fix?
I sent mine back 3 times. The first was a reset. Thanks for wasting my time. The second was a motherboard and that didn’t do it. The third time they did a motherboard, digitizer, and usb port. It's finally stable and back to normal. After 5 trips back, the BB warranty triggers a new unit. Check if it triggers a refund.
I get it occasionally, so far I'm able to resolve it by booting into custom recovery (TWRP) and clearing dalvic to allow all apps to rebuild. Sometimes this resolves it for a few days, sometimes a couple of weeks. Its a repeatable "fix" that makes me question if the issue is related to memory or trim or something like that. Kind of reminds me of how with the first generation nexus 7s one would see slow downs after a while and filing storage with fake data then deleting it would improve performance for a while.
I'm definitely not a tender user of the device. I go back and forth between multiple ROM's and kernels on a daily basis testing what is testable, and unfortunately also what is not. Anyway, even though mine was bought as refurbished on eBay, I have never had any issues like the ones you describe. More specifically, I have never had any issues what-so-ever, that was not created due to my own ignorance. To me the device seems indestructible.
Besides, I would hate to be in the place of my device, or I would definitely have turned schizophrenic. Should I feel bad about pushing it through all this?
Because we're trying to figure out if it's related to a specific device type, which one do you have? P900, 905, 907A or another?
ShadowLea said:
Because we're trying to figure out if it's related to a specific device type, which one do you have? P900, 905, 907A or another?
Click to expand...
Click to collapse
P900 wifi. Us version bought at best buy.
Today the tablet has been rock solid, I have literally done nothing between when it was flickering like mad and now.
I wonder if it might be related to some kid of data transfer. either over wifi, or when data is written or read from storage or SD card. I've take then SD card out to eliminate that as the problem.
Mine was P900 from BB
Issue lies with the screen.
This happened with me I sent it back to Samsung, 3 times. They seem to have finally got it right. They replaced the battery and then the display screen. Now it appears to be working I will let you know after a month if it is still good. They also told me that they will not replace the device even though I bought it and the issue was right from the start. Not even 6 months old. When working the device is excellent.
Ah, so now we know for sure the battery is replaceable. That's good news. Maybe someday our batteries will no longer hold a charge and we can replace it. Now for a good video on tear down and what tools to use to do that and where to get a replacement battery. I know it's early for most of us but someday......we will have to replace that battery. I'm one of those that keep my toys (computers/laptops/tablets/phones,) for many years.
Mine is running like new since last service. Getting the BB Geek Squad warranty has paid for itself already. I get 2 years on anything over $500.
Mine is a p900. I purchased from samsung website. Mine has been doing it fresh out of box. So bummed.
Ive had my 12.2 since march and it recently started flickering. It seems to tuen of the screen for a millisecond especially when lots of refreshes happen. Like scrolling a pdf. A few days back it was bad. Now it has gotten better and I havent noticed anything.
{Diemex} said:
Ive had my 12.2 since march and it recently started flickering. It seems to tuen of the screen for a millisecond especially when lots of refreshes happen. Like scrolling a pdf. A few days back it was bad. Now it has gotten better and I havent noticed anything.
Click to expand...
Click to collapse
My P900 has just begun flickering exactly as you describe. So I should just be patient and hope it goes away by itself?
I'm flickering again. Turning the screen brighter is what triggers it for me. Returning to stock just to get it back and have it flicker again to hit the magic 5 returns may be what I have to do.
https://youtu.be/CvxbVft69Kg
I just followed this guide. Its been a week now, not had any flickering since I did it.
Manya3084 said:
I just followed this guide. Its been a week now, not had any flickering since I did it.
Click to expand...
Click to collapse
Lifting the motherboard only temporary close the gaps of cracked battery connector. The permanent fix need to do: re solder the battery connector.
Look closely under magnified glass or microscope , you'll see the cracked solders. You can test by pushing the connector slightly, a bad one will move easily or lift off from its solder joints.
This video was removed from the poster after I pointed out his guessing solution. Flickering screen has nothing to do with LCD connector on the motherboard.
Lifting mother board actually you're applying pressure on the battery connector from rear cover.
I have had my P900 sent to Samsung service twice without having the screen flicker fixed. I thought this was a known problem and that Samsung themselves should be aware of it? Maybe I should supply some XDA links next time...
Skickat från min SM-P900 via Tapatalk
bluebirch said:
I have had my P900 sent to Samsung service twice without having the screen flicker fixed. I thought this was a known problem and that Samsung themselves should be aware of it? Maybe I should supply some XDA links next time...
Skickat från min SM-P900 via Tapatalk
Click to expand...
Click to collapse
Depend on where you send for service, they know how to fix it now. Service Centers actually are contractors provide services for Samsung and others, the fact that most people don't know.
http://forum.xda-developers.com/showpost.php?p=59573206&postcount=100
It Works. Battery connector replaced. Smoooooth
After 2 visits to Samsung , my unit finally works fine.
Motherboard and LCD were changed first time. But issue persisted.
Second time, battery connector was replaced. Since then it has worked very very smoothly.
Beut said:
Depend on where you send for service, they know how to fix it now. Service Centers actually are contractors provide services for Samsung and others, the fact that most people don't know.
http://forum.xda-developers.com/showpost.php?p=59573206&postcount=100
It Works. Battery connector replaced. Smoooooth
After 2 visits to Samsung , my unit finally works fine.
Motherboard and LCD were changed first time. But issue persisted.
Second time, battery connector was replaced. Since then it has worked very very smoothly.
Click to expand...
Click to collapse
Thanks, missed that other thread. Next time, I'll send them an en explicit request to replace the battery comnector, and refer to those two threads.
Stefan
Tapatalked on some kind of Samsung tablet
Well I have been a owner of a LG Nexus 5 for the past (almost) 2 years now, in fact I am coming to the end of my contract very soon and will be able to either goto another company or get a new phone.
Anyways, sometime ago I experienced a problem with my microphone and external speakers not working, or at at least some of the time... After a bit of research online I found out my problem was related to a connection inside the phone that connected the bottom assembly to the main board at the top of the phone. It required me to remove the back panel and a few screws to remove the plastic cover, but the poster suggested putting some tape on top of that connection to hold it down more firmly to the socket it connected too. So I did this. I put some black tap (electrical tape cut to fit.) on top and then assembled the phone again. Viola, It worked!
Well, a short time after I decided that I wanted to update my phone from stock kitkat (4.4.4). Always been curious about custom ROMs and gave Cyanogenmod a try. Not only that I got bold and tried the nightly releases of the new marshmellow update. After some time I started experiencing things not working, like the camera, and a lot of freezing, hang ups and random reboots (not so much the reboots as the constant freezing). Often I couldn't get anything on the screen or the phone to respond from a locked state and when I did, often the phone would lag so much, that doing anything would take a long time and proved to be impossible.
I started thinking it was the nightly releases as the source of my problem and just kind of shrugged it off and figured "they will eventually fix the problem". I kept this thinking for quite some time. But it occurred too me one day that something else was causing the issue I was facing for the simple fact that the lag started showing up in the recovery mode (also custom) and a lot of times would continue to show up after I rebooted my phone. Hence, would rule out any 'software' issues I was facing.
I began to think that my problem was hardware. Maybe it was just time for a new phone. But still months away from the end of my contract, this meant I would have to pay off the 'problematic' phone first before getting a new one. I really didn't like that idea. So while looking into this problem, in a last ditch effort, I opened my phone again. Dunno why but I also decided to get rid of the tap on the connection I tried to fix before... I popped off the connection there and had a look at it. It didn't seem damaged in any way nor did the socket. Strange as it was I put that connect back in the socket and put the cover plate back on making sure not to torque the screws and assembled everything back up....
Now the mic and ext speakers work just fine and the phone is working like I just opened the box and took it out for the first time. And I have not once seen any problems... I understand what's happening here... still just wanted to share that for it was definitely weird or what?
https://drive.google.com/open?id=0B0pUNVcVRCJ7MThMc0NHLUNkSEU
Sorry about the link, only way I can upload an image.
Just so there is no confusion... an image of the effected area, inside the phone. The arrow points to the connector and more importantly the area of the connector that seems damaged. If I press lightly where the arrow is pointing on this image, the assemable at the bottom (speaker/mic) will work, indicating a loose connection. Although after visual inspection, I cannot see any damage to connector or the socket. I suppose the only way to really "fix" the issue is to order a new part. As stated previously, already tried tape on the socket to help hold it down, but that seem to cause just as many issues with the phone performance. Any other suggestions?
When ordering a replacement part, you need to be careful because there was another XDA member replaced the same part with a cheap 3rd party solution and the phone would not charge until he replaced it with an oem part.
http://forum.xda-developers.com/google-nexus-5/help/to-buy-usb-charging-port-flex-cable-t3314357
Does anyone else have issues with there ext. speaker and mic not working?
An update on the phone;
back to square one. My ext speaker and mic will not work. And that socket has something to do with the LCD connection on the screen as it will black out if just the right area on the back of the phone is pressed. Only way to revive the phone is to long-press the power button for a reboot. Then will come up fine but speaker and mic still do not work.
audit13 said:
When ordering a replacement part, you need to be careful because there was another XDA member replaced the same part with a cheap 3rd party solution and the phone would not charge until he replaced it with an oem part.
http://forum.xda-developers.com/google-nexus-5/help/to-buy-usb-charging-port-flex-cable-t3314357
Click to expand...
Click to collapse
Wow, that sounds pretty low level tactics of LG... just shameful really, but not hard to believe these days...
Quite honestly, I am just going to replace the phone. Think I got a pretty good run out of it and think its pretty well time for an upgrade. Anyway, for the reason I got the phone, it wont matter the speaker and mic don't work. Just going to use it for development and it will be a good test device.
Oh an this post is related to this thread so I thought I would link it for it may help someone else facing similar problems....
https://forum.cyanogenmod.org/topic/125227-nightly-cm13-releases-make-my-nexus-5-very-slow/
I'm not sure that LG had anything to do with the low-quality replacement parts.
If I were you, look for a n5 with a smashed screen that is suitable for parts.
audit13 said:
I'm not sure that LG had anything to do with the low-quality replacement parts.
If I were you, look for a n5 with a smashed screen that is suitable for parts.
Click to expand...
Click to collapse
Good idea, except the iphone is the most popular phone around here ... find it pretty hard to find one, been looking. But thanks.
I have seen quite a few busted n5 phones in Toronto. I have managed to get working phones with a smashed screen for as little as $30 which is rare for Toronto. Average I pay is $40 to $50. For this price, I either use the phone for parts in several phones or I get third part screen from Aliexpress for around $40 CAD.
I just want to update this as well...
I am fairly certain (now thinking about causes) its not really a design flaw, but more so because I frequently sat on my phone when it was in my back pocket...
audit13 said:
When ordering a replacement part, you need to be careful because there was another XDA member replaced the same part with a cheap 3rd party solution and the phone would not charge until he replaced it with an oem part.
http://forum.xda-developers.com/google-nexus-5/help/to-buy-usb-charging-port-flex-cable-t3314357
Click to expand...
Click to collapse
It was not me but I had that same experience. Replaced with a cheap oem and it didn't charge after that.
I found out why. The charger usb socket was not connected to anything ! Unbelievable! It lacked the black plastic backing for that part of the cable to connect to.