Related
So my earpiece has gone.
Not crackly, not distorted, just nothing - silence.
It was fine a couple of days ago and now it's completely dead.
The phone hasn't been dropped (well, tossed on a mattress/duvet when I'm heading to bed but not onto anything hard and from no great height), I haven't tempted fate by submerging it, I've properly nursed this phone and it's still died on me.
The one thing that I did do between it working and today was flash a different ROM.
I'm just wondering whether there's any chance that might've had something to do with it?
I went from '3.4.2 131-003' to '3.4.2-155-2'.
I know it's a long shot but that couldn't possibly be the cause, could it?
Many people have already complained about that problem (just google it!), return the phone (if your warranty isn't void because of the flashing, but i think it only affects software warranty), and they'll get you a new one. As far as I know, the newly produced defys don't have that defect anymore, mine - which I bought a couple of weeks ago - works just fine (fingers crossed!).
I'm aware that it's a known issue, I was asking because it seems that normally the earpiece gets crackly then dies whereas mine has gone from absolutely fine to completely dead in a couple of days with no usage in-between and the fact it happened after I flashed a new ROM seems coincidental to say the least.
As for the warranty, I have flashed ROMs, so fingers crossed.
same problem
I've the same problem.. no crackling, total silence. yesterday it worked perfectly fine, but since today no sound at all.
didn't do anything weird with it; flashed another froyo rom one week ago, but I can hardly imagine it has something to do with it...
I red there were more persons with a earpiece problem, but I couldn't find anyone who's got total silence from one moment to another..
is there info about this issue?
greetz
mine has gone from working to total silent the way mine was crackly was if i blew into it, it would work sometimes but now nothing at all i need to get a replaceable but dnt ave time
The problem is due to a bad connection, so I suppose it is possible it would break cleanly, going from working to silence with no interference/crackling.
I was just hoping I could fix it myself without having to rely on the Motorola warranty lottery
The fix-it-yourself thread is here. It's easily done if you are even mildly practical. I have sourced 2 SE K850i earpieces as a hedge against the future, once I'm out of warranty.
However, I am currently in warranty, so I sent an email regarding my Defy to Motorola as soon as my earpiece started acting-up. I tried to demand a replacement on the grounds that they were offering for sale devices that they knew were defective. Unfortunately, they were adamant that a repair was my only option so I sent my phone to their centre. I followed their advice, backing up, removing SIM and SD card, performing factory wipe from within Settings/Location & Security, and only sending the phone.
My phone had a custom ROM with the "android" text boot-loader so it was obviously not stock but there have been no complaints from them and I'm able to track my phone through their system. It's been repaired and is in "final testing". I'm expecting it back early next week.
Given the perceived "openness" of android, it would be a PR disaster for Motorola to void the hardware warranty on the grounds of software modification.
Step666 said:
So my earpiece has gone.
Not crackly, not distorted, just nothing - silence.
...
The one thing that I did do between it working and today was flash a different ROM.
I'm just wondering whether there's any chance that might've had something to do with it?
Click to expand...
Click to collapse
mmm, i have something to say ... i flashed lots of different roms, two weeks ago i went back to China 0.26, still one of the best in terms of performance BUT, i had some trouble with the earpiece.
The first time it happened i thought "ok my earpiece has gone", it was just silent, people could hear me and i could hear nothing. Surprisingly after a reboot the earpiece was working, then silence again the day after... so on for 3 - 4 times.
Then i flashed the 3.4.2-155 and the problem disapperead. No failure, no silence, after 10 days it still works.
So, could it be the problem was related to that specific rom or software i used?
Btw, did you try to flash back to your previous rom?
I got same issue last week, and my mobile operator change my phone by a new one.
It's a know pb with first MB525 products.
After flashing did-you remove back door and battery to power off/power on you phone ?
I think when we do that, we push on the back of phone and so increase earpiece failure risk.
Thanks, I'd seen that thread before but I'm still well inside my warranty and have no urge to risk voiding it any more than I potentially already have.
I have no qualms about having to send the phone back to Motorola, I just want to be sure it'll be fixed when I do is all.
It's a shame that Motorola don't allow third-parties to fix the handsets - I know an engineer that works for one of the UK high street mobile phone retailers and he says that any earpiece issues, they have to send the phones back to Motorola themselves, they can't even source the necessary parts.
If they could fix it, I wouldn't think twice about the ROM as I know he couldn't care less, he'd get it sorted for me.
technome said:
Given the perceived "openness" of android, it would be a PR disaster for Motorola to void the hardware warranty on the grounds of software modification.
Click to expand...
Click to collapse
Also, since the issue is known to be purely hardware and there are plenty of cases of it afflicting handsets that are entirely stock, they would leave themselves in a very shaky legal situation.
Personally, I think I'd prefer to have my current handset repaired instead of replaced as it seems to be a little gem in terms of battery life.
As for the warranty, I doubt I'll have this phone for more than a year or so.
Part of the reason I chose it was the excellent deal on the T-Mobile contract I'm on meaning that if I get the urge to 'upgrade' early, I won't feel bad about buying a second phone out of my own pocket.
xdaid said:
Btw, did you try to flash back to your previous rom?
Click to expand...
Click to collapse
No I haven't.
I only discovered the problem at work this afternoon and started this thread as soon as I got home.
I might give it a go over the weekend but part of me can't really be bothered, I might just send it away.
edit:
MisterWB said:
I got same issue last week, and my mobile operator change my phone by a new one.
Click to expand...
Click to collapse
UK law only gives a customer a limited period after purchasing during which they can demand a replacement, after that a retailer is entitled to try and repair a faulty item if it is reasonable to do so.
Only if repairing the phone is in some way unsuccessful would the customer then be entitled to a replacement.
Sorry to hear that.
Let us know if Moto honor the warranty. It's very unreasonable to void hardware warranty just because of software modification.
My defy earpiece failed after 4 weeks. I had the orange 2.2 on the phone. Sent it to solidvision (they do warranty repair for motorola phones in belgium and netherlands). 3 weeks later they sent me a new phone, under warranty. On other sites I read that motorola doenst make a problem about earpiece issue even when you flashed other firmware.
So I handed my handset in to be sent away for repair on the 21st of March.
On the 18th of April I contacted CPW's repairs department to query where my handset was at 28 days had elapsed. The guy I spoke to raised a £10 voucher on their systems and put some sort of trace on it for me.
And on the 21st I was contacted by the store I'd handed my phone into to say it was back.
When I say 'it was back', it's not the same handset I sent away - it's a 'clearance' replacement handset. Thankfully my mate who works for CPW checked the handset's history on their systems and it's not a refurb, it was sat in a store for a month without being sold, then recalled to the warehouse so they had one to send to me.
I just hope this 'new' handset has as good a battery life as the one they kept...
I was just trying to root my friend's mom's kindle fire and install a new rom and now there is a purple line on the screen. Honestly I didn't check beforehand if there was anything wrong with the screen and his mom is asleep so we don't know if it might've already been there or not.
Couldn't some part of rooting,installing twrp, installing jb, gapps etc have messed up the screen? If so, is there a fix? I tried restoring to stock but the line is still there.
Did I screw up her kindle?! :crying:
I hope you checked with her before modifying her device as its not cool to modify someone's device if they don't wish it to be done. If I was her I would be much more perturbed at that than a purple line, its called respect for other people's property... so I hope you guys had permission.
That being said, I don't see how flashing dev apps or custom Rom to it could possibly cause something like this. Have you tried holding down the power button for 20 seconds to do a hard reboot? You could also try doing a factory reset through the stock os to ensure that it is indeed not a software issue. If all else fails return it to stock as it may still be under warranty to ship it back.
Also you did check to make sure it was a first gen before flashing right?
This post should be in q&a section as well...
Sent from my Amazon Kindle Fire using xda app-developers app
Never heard of such problem. Maybe hardware problems.
Sent from my Amazon Kindle Fire using Tapatalk 2
Let me preface by saying I'm not a 12 year old who stole my friend's mom's kindle.
I have rooted 2 other kindles and never had an issue and I of course was asked to do this.
I did a hard reboot didn't help anything.
I restored the stock os and it is still there.
I did a search and someone posted about this problem once in the Kindle Fire Utility thread but it doesn't look like anyone ever responded to it.
http://forum.xda-developers.com/showthread.php?t=1399889&page=105
My friend says his mom has bad vision so it's possible she never noticed it but I dunno, I honestly didn't even turn look at the screen I just went right to rooting it.
Any more help would be greatly appreciated.
If I can't fix it I will just try and get amazon to replace it. Question: I own a kindle fire as well. If I tell them this one is mine and send it back to them will they replace it or notice it's not the one I bought? I could ask my friend's mom to do it but I'd rather do it to save her the trouble.
Did you just restore the stock os or did you flash stock? Where is the purple line located?
Thepooch said:
Did you just restore the stock os or did you flash stock? Where is the purple line located?
Click to expand...
Click to collapse
I restored to stock following the instructions in the restore stock thread using the file from amazon. The line is about 25% down from the top of the screen.
So no more fff and twrp? Sounds more hardware related than software. Is it still in warranty? Rather than a dead pixel it seems more like a string of bad pixels. Pretty good chance it was already there. Do a factory reset if it is to be returned.
Thepooch said:
So no more fff and twrp? Sounds more hardware related than software. Is it still in warranty? Rather than a dead pixel it seems more like a string of bad pixels. Pretty good chance it was already there. Do a factory reset if it is to be returned.
Click to expand...
Click to collapse
Thanks that makes me feel better. There might have been something wrong with how I rooted it but I don't see why that would mess up the screen.
I am going to find out tomorrow if I can return it.
Do you think that if I've bought a kindle but I try and return a different one that amazon will notice?
Amazon is only selling 2nd gen. devices from now on. I think they would notice. If you send back a 1st gen. device they will try to replace it with a 1st gen. till they run out.
Thepooch said:
Amazon is only selling 2nd gen. devices from now on. I think they would notice. If you send back a 1st gen. device they will try to replace it with a 1st gen. till they run out.
Click to expand...
Click to collapse
Well that would be fine. I bought and have a first gen that works fine. Got it back in march. Although I bought it refurbed from amazon.
If I could return this one and tell them it was mine that would be perfect. Not sure what the return policy on a refurb is though.
I think you still have the issue of a serial number.
So they know the serial number of the kindle they sold me and they will check it? Damn, I was hoping I could get away with it.
I'll check with my friend's mom to see if she can try getting it replaced.
I believe they do and they will 200$ is 200$.
The serial number in the device is listed on your account at Amazon.com, no chance of slipping it past them
Sent from my Amazon Kindle Fire using xda app-developers app
I finally ran into the bootloop problem that is common with early G4's (if you have a serial number that starts with 505, you're basically gonna be screwed at some point). Since it's a hardware issue that LG acknowledges, I sent it back to the factory under warranty, waited for two weeks using my old backup phone, and finally received it back today.
Ready for the fun part? They had repaired something that wasn't broken (kind of like surgery on the wrong body part) and had not touched the bootloop issue! They fixed "No power with cable" by replacing the flash memory. This was never an issue. The frustrating thing is that they didn't even restart the phone to find out if it had been fixed, because if they had it would have gone right back into the bootloop. Arg!
The G4 is now back on route to LG. I said they should give me a new phone, but customer service said they only do that if it cannot be repaired. I'll keep my fingers crossed that they go to the trouble to turn on the phone after "repair" this time.
Thanks for letting me rant!
I have currently my 2nd G4 that has run into this issue. This one has serial number starting with 506, so I guess it might stem a little further into production also. This is driving me nuts, I could not send my phone to LG because of how long it takes so had Verizon send me one and of course I run into the same exact issue with the bootloops. Last time I was able to still flash kdz's, this time won't even go past the LG boot screen. Really wish I could wipe my data at least.
I can attest to LG's incompetence. On March 2nd I sent in my G4 because it was bootlooping. Sent it in no problem, and after about a week I received my G4 back with the problem "fixed" by flashing the memory. Well guess what, it wasn't fixed. As soon as I turned it on, it started to bootloop again. I called LG and they arranged another RMA. Sent it back again, and about a week and a half later, I had my G4 back. This time they "fixed" it by replacing a capacitor. Guess what! Still not fixed. It still continued to bootloop. Called LG extremely angry and filed a complaint. LG arranged another RMA. At this point I had been without my phone for over 20 days. Finally, LG fixed it properly by replacing the motherboard. Now its fixed and it only took them over a month to figure it out.
While I applaud their easy RMA process, whoever the idiots are actually doing the repair are just that.. idiots. Its as if they don't even turn the phone on and ensure it fully boots up before they claim its fixed and ship it back. Whats worse for me is my phone was rooted on VS986B. Got the phone back on Marshmallow 24C and it took the update to 25a overnight. Now I'm stuck with no way of rooting.....
When you get your phone back from LG, chances are it will be on 24C. If you plan on rooting, do so quickly and downgrade.
dcorrea said:
I can attest to LG's incompetence. On March 2nd I sent in my G4 because it was bootlooping. Sent it in no problem, and after about a week I received my G4 back with the problem "fixed" by flashing the memory. Well guess what, it wasn't fixed. As soon as I turned it on, it started to bootloop again. I called LG and they arranged another RMA. Sent it back again, and about a week and a half later, I had my G4 back. This time they "fixed" it by replacing a capacitor. Guess what! Still not fixed. It still continued to bootloop. Called LG extremely angry and filed a complaint. LG arranged another RMA. At this point I had been without my phone for over 20 days. Finally, LG fixed it properly by replacing the motherboard. Now its fixed and it only took them over a month to figure it out.
While I applaud their easy RMA process, whoever the idiots are actually doing the repair are just that.. idiots. Its as if they don't even turn the phone on and ensure it fully boots up before they claim its fixed and ship it back. Whats worse for me is my phone was rooted on VS986B. Got the phone back on Marshmallow 24C and it took the update to 25a overnight. Now I'm stuck with no way of rooting.....
When you get your phone back from LG, chances are it will be on 24C. If you plan on rooting, do so quickly and downgrade.
Click to expand...
Click to collapse
When they finally replaced the motherboard, did the physical serial number on the phone change?
enduser23 said:
When they finally replaced the motherboard, did the physical serial number on the phone change?
Click to expand...
Click to collapse
No, that's the same. The board was replaced, but the plastic piece that holds that battery, which is on top of the board, was not replaced.
Happy to report that all is well after the second repair. Came back with 6.0, but I downgraded to 5.1, rooted, and have just about everything working again (can't get Exposed to work, but I'm sure I'll figure it out eventually). Nothing like spending 3+ weeks on a 2011 Droid Bionic to make me appreciate my G4!
Would one of you care to explain how you contacted LG to set up the repair. I have filled out the online form twice and have never heard a word. Thanks.
illek46 said:
Would one of you care to explain how you contacted LG to set up the repair. I have filled out the online form twice and have never heard a word. Thanks.
Click to expand...
Click to collapse
Im not sure if you are in the U.S., but here's their support phone number 800 243-0000. They are usually pretty easy to deal with over the phone.
I am still kicking myself that I didn't downgrade as soon as I got my phone back. I hate not having root anymore.
---------- Post added at 01:02 PM ---------- Previous post was at 12:59 PM ----------
harpdoc said:
No, that's the same. The board was replaced, but the plastic piece that holds that battery, which is on top of the board, was not replaced.
Happy to report that all is well after the second repair. Came back with 6.0, but I downgraded to 5.1, rooted, and have just about everything working again (can't get Exposed to work, but I'm sure I'll figure it out eventually). Nothing like spending 3+ weeks on a 2011 Droid Bionic to make me appreciate my G4!
Click to expand...
Click to collapse
Droid bionic.. I wish! I originally dug up my old Galaxy Nexus, but the battery life was so bad that I swapped it out for my son's old Droid Razr. Of course, I had to safestrap it and put a custom ROM on there because I have a LG G Watch R and android wear was not compatible with the factory software on the Razr. It was a pretty horrible experience overall. I'm glad I have my G4 back, but I really miss root.
You can still downgrade to 5.1 and root. Mine was on the latest version when it came from the factory and I didn't have any problems with the process.
Same thing happened to me. It took 3 RMA's in a row and about 60 days until they finally fixed it. They scratched it, too. OP, I highly recommend you start documenting everything. LG CS will also tell you escalating will get you nowhere; but with persistence you can get a hold of someone. You can only go up to a supervisor, and that's it. LG has specifically designed their CS (including their facebook and twitter) to contain and ignore you.
In less than 1 calendar year i am on my 3rd phone.. Figuring the 1st phone was a flop... serial numbers since my 1st phone are 511 and 505. So yeah.. im debating at what a ticking timebomb i havenow. The 3rd one came w/ MM installed but I downgraded to LL to keep root. Im sure it goes w/o saying that I'll not buy an LG phone ever again.. and this was my 1st one. They could offer to upgrade me to a G5, but honestly there are NO guarantees this sort of thing will happen again. You break trust you pay the price, look at Samsung w/ the no MicroSD card fiasco.
LG just accepted my 15 month old G4 for warranty repair
Even though my phone is 15 months old, LG has accepted it under warranty repair. When requesting repair I wrote that it was the bootloop issue but their repair confirmation states the issue is "No Power with Cable". I hope they fix the correct issue! BTW, my serial number began with 511
The US warranty is 18 months, so LG didn't do you any favors. I have three of these POS phones to get warranty repaired and hope they fix them correctly the first time.
keithfur said:
Even though my phone is 15 months old, LG has accepted it under warranty repair. When requesting repair I wrote that it was the bootloop issue but their repair confirmation states the issue is "No Power with Cable". I hope they fix the correct issue! BTW, my serial number began with 511
Click to expand...
Click to collapse
I just got mine back today june 1st 2017, Sent G4 for bootloops 1st time a week ago. No power / Mainboard was replaced. it was purchased november 2015 and Serial number is 511 which is right after the supposed bad batch. I got the phone back in the same great condition it left. The repair guy reported phone condition has minor scratches when it doesn't, Not sure why he would report that. So far its working great, like a new phone. I can only hope this board has been redesigned to not fail under a year and a half, but thats just wishful thinking. Everything was completely free even though phone was like 5months+ after its warranty. Even though costumer service on phone sounded like she was doped out on crack and ignoring all my questions, it was still ez to do and I got it back fast. The IEMI number or whatever was also changed and they put a new sticker over top the old one under the battery. I tried checking the number on that website and it doesn't even have it registered so i can only hope its brand new.
Got a couple of VS986s back from bootloop warranty repair. Mainboards supposedly repaired, but IMEI stayed the same and nothing on label under battery changed . I recall other people mentioned changes to label information.
Last week a representative told me the current warranty on the G4 for this issue is 27 months from date of manufacture or 24 months from date of purchase.
Mine has S/N 508. It started bootlooping while I was pooping (browsing Facebook on Chrome browser) on June 5.
I attempted the hot-air rework station fix 5 times (for processor on mainboard), and that worked on the 2nd, 3rd, and 4th tries. Each time the phone worked for up to ~4 hours. On the 5th try the phone no longer booted or even showed the LG logo.
It's en-route to LG right now. I opted to ship it without battery or back cover (my back cover has a wireless charging tag).
Using my old Samsung Galaxy S3 running an AOSP-variant on 4.4.2. Actually isn't a bad phone.
My old LG G2's touchscreen no longer responds to touches on roughly 50% of the screen... can't even unlock it via pattern lock any more.
Thinking LG won't be the next new phone I buy...
Well, my G4 is on its way back to me after LG's warranty repair. Turn-around time at the LG service facility was ONE (1) DAY!! So that was super fast. Should get it tomorrow or the day after. Contemplating putting it back up for sale or trade-in though... it's basically gonna be a virgin device that will require root, xposed, restoring apps/messages/call log/etc., then adjusting everything else to my liking. Would be a shame to do all that work and then the bootlooping problem happens again.
My Shield running stock 6.2 with stock recovery started bootlooping. I was literally watching Netflix the night before and in the morning it was looping. It shows the Nvidia logo and then there is a video glitch and it loops. I can only boot into safe mode. I tried wiping and flashing the official recovery ROM via fastboot. I tried rolling back to 6.1 and then the 6.3 preview build. No dice. I'm guessing some kind of video driver issue. I have not been able to find anyone having the same issue. Any ideas?
I think I have the same issue.
I have the Nvidia Shield TV 16GB (2017), latest update installed (not roorted).
Plugged it in it worked the whole evening, turned it off, turned on in the morning and it started bootlooping. It is showing the Nvidia Shield logo, stays on it then reboots. Once in a while it actually goes trough and boots till the end, and the strange thing is that, if it manages to boot in to the OS, it works like charm, basically I need to keep that thing forever On, if I power it off, it is bootlooping again.
I got this thing brand new, sealed in the package from eBAY and can not return it to Nvidia, for replacement, so I at least need to understand if this is a software issue or hardware.
If anyone have any idea pleas respond.
Thank you and Happy New Year
Haik0 said:
I got this thing brand new, sealed in the package from eBAY and can not return it to Nvidia, for replacement, so I at least need to understand if this is a software issue or hardware.
Click to expand...
Click to collapse
Don't screw around, just return it to the eBay seller instead and get a replacement.
SimonTS said:
Don't screw around, just return it to the eBay seller instead and get a replacement.
Click to expand...
Click to collapse
I concur, return it, what you are experiencing is definitely not normal, also just my two cents if you got it brand new sealed on ebay aren't you on nvidias warranty?
I don't honestly, I don't have an invoice or any purchase papers or information, to provide to Nvidia for return. You think I should still contact Nvidia?
Btw, I can't return this anymore. Now just need to figure out what to do with it. If it's a software issue maybe i can re-flash the bootloader, recovery or everything. Or if it's a known hardware issue then, that's it.
Your contract isn't with Nvidia, it's with the seller on eBay.
Why can't you just return it to them, or is there something else you're not telling us?
Haik0 said:
I don't honestly, I don't have an invoice or any purchase papers or information, to provide to Nvidia for return. You think I should still contact Nvidia?
Btw, I can't return this anymore. Now just need to figure out what to do with it. If it's a software issue maybe i can re-flash the bootloader, recovery or everything. Or if it's a known hardware issue then, that's it.
Click to expand...
Click to collapse
if its brand new all the info you need is on the box as far as your invoice why cant you go to your ebay account and print out a invoice? Return to ebay seller or rma with nvidia if its brand new, their rma policy is excellent as well as their customer service
i have a Pixel 2 XL and the speaker grill seems to be loose and i read that the speaker grill has everything to do with thew phones water resistance, so i want to take no chances... My phone was purchased directly from the playstore and i have never done an rma before, and i know that they send refurbs back to anyone requesting an rma for whatever issue,.... I have read about the faulty RMA devices sent back with screen issues speaker issues etv... and i was wondering if anyone has RMA'd recently to tell me the condition of their new device.... i have a 64 gb panda version and the screen is flawless speakers are good camera is perfect... im scared to get a dud back....thanks for reading... looking forward to your feed back
i42o said:
i have a Pixel 2 XL and the speaker grill seems to be loose and i read that the speaker grill has everything to do with thew phones water resistance, so i want to take no chances... My phone was purchased directly from the playstore and i have never done an rma before, and i know that they send refurbs back to anyone requesting an rma for whatever issue,.... I have read about the faulty RMA devices sent back with screen issues speaker issues etv... and i was wondering if anyone has RMA'd recently to tell me the condition of their new device.... i have a 64 gb panda version and the screen is flawless speakers are good camera is perfect... im scared to get a dud back....thanks for reading... looking forward to your feed back
Click to expand...
Click to collapse
I've legitimately had 7 or so rma's and just got one this week for a speaker issue. It was just buzzing, try the YouTube technique of pressing in with a guitar pick and it did not help at all.
Sent from my [device_name] using XDA-Developers Legacy app
kickenwing13 said:
I've legitimately had 7 or so rma's and just got one this week for a speaker issue. It was just buzzing, try the YouTube technique of pressing in with a guitar pick and it did not help at all.
Click to expand...
Click to collapse
now if I may ask you, what were the main issues with the devices you got in return again the device that I have right now is spotless but the girl on the speaker seems to be loose and I can actually move it around and wiggle it inside of the hole... The only reason I want to return it is because of the waterproofing being faulty now I don't want to damage my device
that and I have an abnormal battery drain on my phone as well so I am hoping that I get a newer phone with a better screen and newer battery if it is possible and a fixed speaker Grill lol..
The guilty for this device was in December did you notice anything about the build dates for your devices how are the screen or what was your experience like
i42o said:
now if I may ask you, what were the main issues with the devices you got in return again the device that I have right now is spotless but the girl on the speaker seems to be loose and I can actually move it around and wiggle it inside of the hole... The only reason I want to return it is because of the waterproofing being faulty now I don't want to damage my device
that and I have an abnormal battery drain on my phone as well so I am hoping that I get a newer phone with a better screen and newer battery if it is possible and a fixed speaker Grill lol..
The guilty for this device was in December did you notice anything about the build dates for your devices how are the screen or what was your experience like
Click to expand...
Click to collapse
I honestly am ignorant to the build date thing. 1st one screen burn in w/in first month or so. rejected RMA because screen would flash white every time i turned screen off. 3rd one, gps kept saying i was in CLE, no one from google knew why, so they sent replacement. they sent RMA, rma speakers were garbage. rattled and muted with ANY pressure to the screen, they repkaced and lower speaker was buzzing.. this one seems great
RMA'd mine in August for a problem with the USB port. The refurbished device I received was like new. The only difference, it came in a different, thinner box, without the charger.
Don't worry, you'll get a perfect phone. In fact the replacement device I got has a better display, with less blue shift
Phazonclash said:
RMA'd mine in August for a problem with the USB port. The refurbished device I received was like new. The only difference, it came in a different, thinner box, without the charger.
Don't worry, you'll get a perfect phone. In fact the replacement device I got has a better display, with less blue shift
Click to expand...
Click to collapse
I did the same at the beginning of October for the same problem. The one i received is in mint condition.
I just RMAed mine because it would no longer hold USB C cables. Like they wouldn't click in they just fall out. Also i had an enormous amount of screen burn-in (happened just weeks after i got the phone)
My RMA phone looks brand new i would never guessed its a refurb. Screen is perfect and USB cables click in and stay there.
Plus if you got the phone from Google the RMA process is super easy (had to RMA my Nexus 5 too) They dont make you jump through hoops doing stupid troubleshooting crap.
RMA'd mine a few days ago, replacement should arrive today
Had screen burn-in around the navbar area
Speakers rattled too much for my liking
Battery life was becoming pretty bad regardless of being stock/on a custom ROM/kernel
USB port, although was holding cables in place, would come out very easily
The Google rep basically stopped me at burn-in and asked for proof of purchase (order ID) and proof of burn-in (taking a pic of the screen with another phone)
After I did both, he set the RMA up and now I'm just hoping the replacement is issue-free, since I have read some users sending replacement after replacement back because the replacements had issues of their own. Fingers crossed!
Update 1:
Due to Canada Post labour disruptions, my replacement is delayed ?. I'll update this post with the quality of the replacement as soon as it arrives.
Update 2:
Finally received the replacement and I got lucky with a brand new device! I called to ask if I need to send back accessories that came with my device and I do not. Basically have two of every accessory, on top of a brand new phone (and not refurbished).
It is manufactured in October 2017 but I see no blue shift or other screen issues. If anything it looks better! I just need to test the battery, hopefully it hasn't depreciated just sitting in the box for a year.
I RMAed a pixel 2 and a pixel 2xl and got 2 brand new phones (with old manufacture date tho) living in germany fyi
I RMA my Verizon pixel 2 xl about 2 months ago because the phone would lag, freeze, and become unusable Everytime I had Google maps navigation open and Spotify running in the background. No questions asked, phone was still under warranty, and I received my new device(was not refurbished) 2 days later.
I just RMA'd to Google here in Canada. Had freezing and lagging issues. That sent me what appears to be a brand new device, box, charger and all. My screen even had a small crack but they still sent me a new one.
acheney1990 said:
I just RMA'd to Google here in Canada. Had freezing and lagging issues. That sent me what appears to be a brand new device, box, charger and all. My screen even had a small crack but they still sent me a new one.
Click to expand...
Click to collapse
I wonder if they actually use the same facilities for Canada and the United States
Did you ship locally in Canada or did you ship to the United States @acheney1990
I'm in this same boat. I have RMA'd three times now, always having random freezes, frame drop outs and lagging on stock ROM, no root. My RMA is scheduled to be delivered today. I have received refurbs each time, but they have been good phones for the most part.
I had to RMA the replacement device I got in August because of camera problems.
It went smoothly and it was fast the first time, but that time it seems Google it trying to make the RMA process hell for me.
I contacted them last Monday (October 22nd). After the usual resolution steps (Was the phone dropped? Is the camera app up-to-date? Can you reproduce the problem in Safe Mode? Have you factory resetted it? blah blah blah), they accept my RMA request and tell me I would receive my shipping label soon.
At 9 PM the same day I receive this email instead:
Thanks for contacting Google Support.
This email is in regards to our conversation we had over chat. Due to some tool issue at our end we're not able to generate RMA for the standard replacement. Once the issue will resolve, we'll create the RMA and send you an confirmation email.
Alternatively, if you wish we can process the Advance exchange in this case.
If you've any query, please let us know. I'd happy to help you.
Thanks!
The Google Support Team
Click to expand...
Click to collapse
Fair enough, problems can happen and they must be very busy with the Pixel 3 launch. I'm not a jerk, I can understand there are delays.
But still no email, follow-up or update from them after a week. On October 29th (last Monday), I contact them again and talk to someone else. I explain the situation, and they tell me they'll retry to generate my RMA request/shipping label. After almost an hour of trying to re-create my RMA , the employee I'm talking to asks me if it's OK to continue the discussion by mail instead. I accept. Mistake
Later that day, same sh*t again. No shipping label, I receive this email instead:
Thanks for contacting Google.
This email is in regards to the chat conversation we had earlier today, I'm sorry we weren't able to complete it. Hence I wanted to follow up via email to ensure all your queries have been answered. Please help me with the below mentioned details to help me assist you further.
Kindly provide the following details please.
Point of Purchase:
Type of Replacement:
Full name:
Shipping address:
Email address:
Phone number:
Order ID
Please reply to the same email, it will come directly to me and we will not lose our point of contact, I will be right here to help you with the same.
Thanks!
Click to expand...
Click to collapse
I provide them with the requested informations immediately.
Two days later, still no follow up. I write an email asking what's going on and asking if they need something else. Many hours later, they send me this:
Thank you for contacting Google support team.
My apology for the delay. I am in direct touch with the next level. I would request you to help me with the proof of purchase of the device with visible order ID on it.
Click to expand...
Click to collapse
I sent them a screenshot of my phone order with the order ID. I'm awaiting for a response, but at this point I feel they're somehow trying to buy some time.
I'm a very polite customer, but that's so frustrating... the RMA was accepted 10 days ago, just send me my shipping label for the love of God... You're telling me it's been a week and a half, and your system still can't generate RMA shipping labels? You're Google ffs, not a small, unknown company...
I'm stuck with a device I paid $1400 CAD and it doesn't work. Can I get a device that works please Google?
Google Is sending me a Band New Pixel 2 XL. I received a refurbished device with a dead speaker and the guy I called was like( I have good news) your getting a Brand New Phone. I still had to put a hold for $919 on my card for the device and now I'm hopping I don't receive another crappy device.