Related
[Q] "Retroactive Bricking" or "spontaneous" hardware fault? [Xpost One X/X+ Help]
*PSA: This will be crossposted in xda GenerAL Q&A and HTC One X+ forums, I hope cross posting is allowed, haven't seen it mentioned in rules.*
Hi all,
Quick disclaimer: I've been lurking parts of xda now and again for a couple years now, have flashed a couple of phones and tablets now and again for mainly practical reasons, recently getting more interested in it as a ""fun" interest or "hobby".
SO: I am very aware that this is my first post, the rules, search function, etc. ..
BUT: After extensively searching both google and specifically xda to help me resolve this issue *myself*, I decided to create an account and post. I'm sorry if this Q should have been put in the newbie thread, my assessment was that it probably has no place there.
ALSO PLZ NOTE: What was meant to be a succinct summary and question somehow turned into a condensed but complete rundown of events, so here is a...
TL;DR:
- Replaced HTC One X+ display/digitizer unit myself, ran fine for 5 weeks.
- Then: flashed twrp 2.7x or 2.8, not sure anymore, before installing Android HD Revolution 33.1 by mike1986, and following the official instructions, which ran great for about week until my phone spontaneously BRICKED THE F*CK OUT COMPLETELY.
(yes, true brick, paperweight, robot-corpse, whatever)
=> Question: IS "RETROACTIVE/RETROGRADE BRICKING POSSIBLE/A "THING"??
If so, what could I have done wrong? (POSSIBLY something to do with a bootimage of firmware that I was sure I had the up to date version of... dunno though).
=========================================================================
About 6 weeks ago:
- Cracked the display of my HTC One X+ badly by dropping it onto concrete-type floor at a rave/party
=> Decided to try and replace it myself, researched for a good while (talking several days here, 90s/00s kids),
=> Decided to replace the display/digitizer unit myself to save money and gain knowledge.
Repair process was challenging and nearly as nerve wracking as playing the WSOP (not kidding, have played it three times), had an issue immediately after putting it back together where it suddenly wouldn't charge AT ALL anymore (NO LED), and overheated, and had unusually fast battery drain of its remaining charge (which never ran out completely before resolving that issue, since I kept turning it off whenever possible).
=> Took it apart and put it together again XX times until realizing the power switch flex cable kept slipping out of its two (jawbone?) connectors during putting it back together (I was doing something wrong with the flex positioning).
=> This resolved the issue.
=> Felt like a hero and that I win at life (since this phone has a rep as being hard to meddle with, and this was my first time even opening, let alone taking apart a smartphone).
=> Continued joyful phone shenanigans for over one month.
=> THEN: Decided to root it, mainly because there was a particular app I wanted that required root ("Quick reply for Whatsapp/Pushbullet", for the curious).
My previous, very limited rooting/flashing experiences =
- Google Nexus One (CWM/Cyanogen) a few times, years ago
- Galaxy Tab 10.1 (CWM/Cyanogen 10.1 ages ago, TWRP/Omnirom Kitkat 4.4.4 recently) a couple times.
So, did my research (or so I thought..?) for this particular custom ROM, decided to go for Android Revolution HD for HTC One X/+ 33.1 by mike 1986 (because it looked fckin awesome, and it was, while it ran) and loved the sh*t out of my "new" phone for about a week. Especially the vastly improved battery life seemed almost surreal, a big deal for a fixed-battery phone.
Then, ONE FATFUL EVENING in a bar, I remember looking at my phone and seeing 35% left, (days before it would've been an amazing 70-80% on an avg. day), which may not be relevant as it was my birthday, so had been using it a lot that day => may be a moot point
- Next time I looked at the phone ( < 1 hour without active use for sure) it was dead.
"Hmmmm," thought slightly drunk me. Whatever, charge it later, weird sh*t happens.
- Got home later, charged it over night after booting it with usb cord attached (mains).
Seemed normal, I even set an alarm.
=> Alarm never rang because it was in a powered-off state again come morning, despite all-night charging.
=> It booted to HTC logo. Seconds later, it turned off again. Held down power again, all I saw was the soft touch buttons flashing red a few times. After this it unexpectedly became (or was secretly crowned):
!! COMPLETE AND UTTER FCKNG KING BRICK OF BRICK COUNTRY AND ATTACHED TERRITORIES !!
No power on with or without volume up/down held for whatever amount of time;
No charging, no heating up when "charging";
No LED in any colour or flashing frequency, ever;
No response after hours and days of charging on different USB cables on PC/wall socket;
PCs and laptops don't register a sign of anything when it penetrates their port parts, etc etc...
...
.Even that semi-mystical bright-light-exposure-while-charging "light sensor manipulation" thing (which apparently worked for a lo of people with similar issues) did nothing for the cause.
Promotion: *Paperweight status successfully acquired.* Yay.
=====================================================
Now, obviously my first thought was that the power flex that gave me trouble during display replacement probably slipped again., somehow (I had taped it down solidly I thought).
=> SO I opened it once again, flex position seemed ok, but I wasn't sure of its functionality as it did look kind of battered from the somewhat unprofessional repair I had conducted on it (which I openly admit to, though I really did try my absolute best).
- Spontaneously took mainboard/battery combo to a local independent phone/accessory shop after being told they'd take a look for free
(I was in there was in there buying a microsim adapter so I could use my ancient Nexus One, since my GF has my old S2 now, which she kindly offered back, but its hers now, so nah. Great phone though.)
=>Shop's advice echoed my thoughts: Flex cable may be screwed, I may have damaged it by bending in the wrong direction/too often, and that damage somehow didn't manifest until much later. I didn't mention the recent rooting + flashing as I deemed it irrelevant at the time.
Their secondary thoughts: Battery or mini-usb port fukt, (which would require soldering, which they don't even offer).
=> SO, feeling confirmed in my layman's assessment, I cheaply got a pristine new replacement flex on ebay, double checked all videos/tutorials, implemented the damn thing with considerably more skill/experience and even higher anticipation. What happened next was shocking:
Absolutely nothing, obv.
=> Did an additional epic f*ckton of internet/forum research, found similar problems and some resolutions, but no real answers, probably because my main problem translates to a kind of hybrid question.
So here I am now am with my core question:
Is it possible to FULLY brick an HTC/any smartphone but not become aware of this until one week later, when the device dies OVER ONE WEEK of reliable and amazing performance?
(and if yes, what aspect/stage of the flashing process is this likely related to?)
If the answer is NO, it must be a hardware fault with probability rank (I think)
:
1.) Battery dead for whatever reason
2.) Mini USB OR mainboard/integral component (equal rank as not sure), possibly caused by incompetent repair, but why or how would this express itself over a month later??
3.) Other, which I'm not aware of.
While researching new ROMS for the N1, I realized that I may have messed up on the "bootimg part" of the flashing process of the Revolution ROM, a part I found v. confusing in the instructions, even after rereading them many, many times. It was about the most recent firmware, which I was pretty sure I had anyway, since it was unrooted before and I do remember installing some firmware updates over the air.
I still did my best to follow the instructions though.
=> Maybe this has something to do with it, i.e. the hardware can't accept a charge because the software allowed it to become too uncharged (a fairly paradox concept to me, but apparently it can happen. Guess it's like a BIOS-type thing).
Thank you for anyone who read this far!
As it stands, I refuse to give up hope so soon after experiencing that rush of having fixed it myself.
Any specific or general help, tips, hints, pointers, replacement phones (One M8 or S5 plz., Iphones will go straight on ebay) would and will be greatly appreciated!!
The obvious choice is to get a new battery and see what happens, but I'm not sure if I wanna sink any more money into this phone, only to later find out the mainboard is at fault (not worth the money replacing), AKA "get a new phone without a contract", which would more than suck for me financially atm (Im ignoring my N1 here, which I love, but don't wanna be stuck with, esp. as it has the standard-issue broken power button (which I actually had repaired once under warranty, back in the ol' days of yore some prefer to refer to as 2009.
So guys: What's my move, if there is one, besides going to a local/online service centre (I live in Germany btw.) and probably paying unproportionate cash money to even have it looked at?
Cheers, thanks, merci, danke
PS: Just saw the polling function, so I attached one just for the hell of it, to see what happens (never used one before).
If you feel both qualified AND so inclined as to pass judgement on this here serious business, please indicate what you think may be the cause of my issue.
Poll is in "General QA" Forum original post: http://forum.xda-developers.com/general/help/retroactive-bricking-spontaneous-t2948954
*BUMP 1*
Come on guys, I know it's a wall of text, but can't someone at least answer the TL;DR?
=> Is is possible to flash a custom rom which then (possibly because of improper installation) causes the phone to brick about a week later?
Simple question surely!
I am in need of help! My phone is dead. Here's the rundown
AT&T Samsung Galaxy Note II (i317)
Used on the Straight Talk Network
Running the latest Unofficial CM12, Lollipop 5.01 for the last week and loved every bit of it. No problems.
I cracked my screen in July and never got it fixed. The cracks spread and I was planning on getting it fixed, but haven't yet. I dropped it two days ago and then the screen wouldn't come back on. The buttons lit up and it would even ring when called. So I thought my screen was finally gone and started looking for a replacement. I took the battery out because I didn't want it ringing without the ability to answer it. Yesterday I put the fully charged battery in and attempted to turn the phone back on. It will not come back on and I think it's more than just the screen now.
Red LED blinks. Half of the screen seems like it is turning on, but then it all goes dark again. Will not enter Download or Recovery. I've been reading and thinking this is more of a hardware issue than software. I've flashed dozens of Roms with only minor issues here and there. I haven't had any issue with Lollipop and can't see it being related, although I could really be wrong.
My question is, is my phone dead? Do I need a new motherboard, along with the screen I was already gonna replace? If that's the case, I will just replace the phone and start over, unless anyone has free parts they want to donate, LOL! Seriously, just looking for input and suggestions.
Thanks
dirtyalphaman said:
I am in need of help! My phone is dead. Here's the rundown
AT&T Samsung Galaxy Note II (i317)
Used on the Straight Talk Network
Running the latest Unofficial CM12, Lollipop 5.01 for the last week and loved every bit of it. No problems.
I cracked my screen in July and never got it fixed. The cracks spread and I was planning on getting it fixed, but haven't yet. I dropped it two days ago and then the screen wouldn't come back on. The buttons lit up and it would even ring when called. So I thought my screen was finally gone and started looking for a replacement. I took the battery out because I didn't want it ringing without the ability to answer it. Yesterday I put the fully charged battery in and attempted to turn the phone back on. It will not come back on and I think it's more than just the screen now.
Red LED blinks. Half of the screen seems like it is turning on, but then it all goes dark again. Will not enter Download or Recovery. I've been reading and thinking this is more of a hardware issue than software. I've flashed dozens of Roms with only minor issues here and there. I haven't had any issue with Lollipop and can't see it being related, although I could really be wrong.
My question is, is my phone dead? Do I need a new motherboard, along with the screen I was already gonna replace? If that's the case, I will just replace the phone and start over, unless anyone has free parts they want to donate, LOL! Seriously, just looking for input and suggestions.
Thanks
Click to expand...
Click to collapse
I see a bunch of views................but not replies. Please Help............Bump!
dirtyalphaman said:
I see a bunch of views................but not replies. Please Help............Bump!
Click to expand...
Click to collapse
There's pretty much nothing to say, but I guess I will.
You can't get to download mode, can't get to recovery mode, you can't see the screen......
If you're looking for a second opinion to say you're f*cked, then consider this it.
If you could get to download mode or recovery mode, it has a chance. But you still have hardware issues like the screen to replace. Which is not fun.
Possible yes. But unless you really know what you're doing and careful as hell, you take the chance of hosing something else up. Like ripping a ribbon cable or yanking a soldered wire out....
I tried replacing a Motorola Atrix screen. The result of that was me buying an Atrix 2.
Unless you are emotionally attached to this phone, bury it.
If not,
https://www.ifixit.com/Device/Samsung_Galaxy_Note_II#guideList
http://www.sw-box.com/Samsung-Galaxy-Note-2-Replacement-Parts.html?p=1
I did some quick searches and doesn't appear to be any kind souls out there with spare parts. You may want to try CraigList or something like that.
Good luck to you
dicksteele said:
There's pretty much nothing to say, but I guess I will.
You can't get to download mode, can't get to recovery mode, you can't see the screen......
If you're looking for a second opinion to say you're f*cked, then consider this it.
If you could get to download mode or recovery mode, it has a chance. But you still have hardware issues like the screen to replace. Which is not fun.
Possible yes. But unless you really know what you're doing and careful as hell, you take the chance of hosing something else up. Like ripping a ribbon cable or yanking a soldered wire out....
I tried replacing a Motorola Atrix screen. The result of that was me buying an Atrix 2.
Unless you are emotionally attached to this phone, bury it.
If not,
https://www.ifixit.com/Device/Samsung_Galaxy_Note_II#guideList
http://www.sw-box.com/Samsung-Galaxy-Note-2-Replacement-Parts.html?p=1
I did some quick searches and doesn't appear to be any kind souls out there with spare parts. You may want to try CraigList or something like that.
Good luck to you
Click to expand...
Click to collapse
Hey, Thanks man! That's what I needed to hear. I have been flashing Roms since I had a Sprint PPC 6700 and I have enough experience to now I was f#@$ed, but I really needed to hear it from someone else. Someone with developer experience. A screen assembly and motherboard cost more than another phone on ebay or Swappa. Welp, back to the drawing board. Anyone got a note 2 they wanna sell cheap?
dirtyalphaman said:
Hey, Thanks man! That's what I needed to hear. I have been flashing Roms since I had a Sprint PPC 6700 and I have enough experience to now I was f#@$ed, but I really needed to hear it from someone else. Someone with developer experience. A screen assembly and motherboard cost more than another phone on ebay or Swappa. Welp, back to the drawing board. Anyone got a note 2 they wanna sell cheap?
Click to expand...
Click to collapse
No worries.
Feb 3 I'll be on 2 years with my Note 2. Longest I've kept one. Only have one smallish crack on the lower left corner.
With everything I've done to it I'm amazed it's still working.
My phone just shut off at 19% as I was plugging in the charger. No orange light while plugged in. I've tried multiple cords/charging blocks. Holding the power button does nothing. Guess it's time to move on from HTC and Verizon.
buddahj said:
My phone just shut off at 19% as I was plugging in the charger. No orange light while plugged in. I've tried multiple cords/charging blocks. Holding the power button does nothing. Guess it's time to move on from HTC and Verizon.
Click to expand...
Click to collapse
Just plug it in and leave it plugged in. Something similar happened to me about two weeks ago while streaming over BT at work in freezing temperatures. I just left the phone plugged in for an hour or two and it booted up again just fine.
P.S. : I got myself a Pixel 2XL last week. I'm still using the 10 more as a daily driver for work (I'm in construction and the 10 is solid), but the 2XL is my phone for nights and weekends and I love it! Plus Google will keep their update promises. HTC has not been able to over the last few years even though it was part of what they promoted.
I still have love for HTC though, and I hope they get their act together
xunholyx said:
Just plug it in and leave it plugged in. Something similar happened to me about two weeks ago while streaming over BT at work in freezing temperatures. I just left the phone plugged in for an hour or two and it booted up again just fine.
P.S. : I got myself a Pixel 2XL last week. I'm still using the 10 more as a daily driver for work (I'm in construction and the 10 is solid), but the 2XL is my phone for nights and weekends and I love it! Plus Google will keep their update promises. HTC has not been able to over the last few years even though it was part of what they promoted.
I still have love for HTC though, and I hope they get their act together
Click to expand...
Click to collapse
Looks like it's back from the dead. I was able to finally boot up into download mode. Once there, I booted into the bootloader mode and rebooted into recovery. Then rebooted system and bam...back into my phone. Hopefully it'll last 2 more month lol.
have you identified what was the issue with your phone? What cause it?
I hear ya....just sold my HTC 10, only to have 3 days later to be contacted by the buyer that the charge port is garbage all of the sudden. I contact support, they swear they will contact me in 24-48hrs to work and resolve the issue. 5 days later now...nothing.
I already bought and moved to a OnePlus 5T. Way better phone than any HTC I've owned, or they make now. Seems like for 5ys I've been constantly buying a phone with very marginal design and feature improvements. The 7, 8, 9, One, A9 and 10 also can't forget, the Google Nexus One...the original and why I moved from iPhone like 10yrs ago to Android. Not even going to make an effort with the U11 and saying goodbye. Nothing like HTC Dev Support here on the XDA forum for years.
Guess I have to call them and demand to get my phone fixed so I can resell it again and recoup some money and get on with my life.
Just look at all the HTC phones, as others have been saying, nothing hardly changes every year with each model..until you see it on a web page with photos...now I get it.
https://www.gsmarena.com/htc-phones-45.php
Good luck TS.
RossTeagan said:
have you identified what was the issue with your phone? What cause it?
Click to expand...
Click to collapse
No idea what caused it. I do know that the battery is starting to fail.
Keeping this concise. Background:
I've been using Windows Phone devices for 8 years. My original 8yr old Samsung Focus is still kicking.
I figured it was about time to jump to Android and picked up a "used for 3 months" Pixel XL. Originally purchased from the Google Store. (purchaser forwarded his receipt).
Bought first week of November, didn't use for a month as I didn't have a case, then used on WiFi but didn't have a sim in it until December 20th or so.
It had been running great. Now that I think of it, it had shut off twice from ~30% battery but in extreme cold. Thought it was cold related.
Two nights ago I set it down to go to sleep. I woke up, it did not.
At first I thought the screen died. I would get the odd vibration when long-pressing power for example, but never anything on the screen. The power + vol brought up the quickboot/recovery but:
"start" results in a blank screen
""restart bootloader" goes to blank screen
"Recovery mode" flashes a white screen with the Google logo for half a second then blank screen
"Barcodes" displays barcodes
I recently picked up a USB C > USB 3 cable and plugged it into my Win10 PC. It showed "Android Device Ready" but I expected to see some removable drive show up (dunno, had never hooked it up to my PC before to know what the usual behaviour should be).
Today, when trying to start it again it flashed the battery/charge icon for half a second, then blank screen.
I had a chat with a Google support agent who got me to try a remote erase which, I'm guessing, hasn't been received by my phone.
So my Android experience thus far has been: spending more than I've ever spent on a phone for a device that I accessed wifi on for a few weeks, then started to set up as my daily driver for a few weeks, just in time for it to seemingly die. Oh yeah, and of course, it's out of warranty. This world is new to me. Google's suggestion was to send it in to a partner for repairs (who knows how much that will cost). I'm hoping there's something else I can try before resorting to that.
Originally I was hoping to get some data off it. I'm not familiar with what Google backs up within Android (I had those settings checked, but no third party backup apps). I guess my photos should be backed up which would have been the biggest thing. Now I'd just like to recover the device without having to spend more money!
Oh, previous owner had Oreo 8.1 on it.
Any guidance would be most appreciated. Back to my trusty 5+ yr old Lumia 1020 in the interim!
tyyan said:
Keeping this concise. Background:
I've been using Windows Phone devices for 8 years. My original 8yr old Samsung Focus is still kicking.
I figured it was about time to jump to Android and picked up a "used for 3 months" Pixel XL. Originally purchased from the Google Store. (purchaser forwarded his receipt).
Bought first week of November, didn't use for a month as I didn't have a case, then used on WiFi but didn't have a sim in it until December 20th or so.
It had been running great. Now that I think of it, it had shut off twice from ~30% battery but in extreme cold. Thought it was cold related.
Two nights ago I set it down to go to sleep. I woke up, it did not.
At first I thought the screen died. I would get the odd vibration when long-pressing power for example, but never anything on the screen. The power + vol brought up the quickboot/recovery but:
"start" results in a blank screen
""restart bootloader" goes to blank screen
"Recovery mode" flashes a white screen with the Google logo for half a second then blank screen
"Barcodes" displays barcodes
I recently picked up a USB C > USB 3 cable and plugged it into my Win10 PC. It showed "Android Device Ready" but I expected to see some removable drive show up (dunno, had never hooked it up to my PC before to know what the usual behaviour should be).
Today, when trying to start it again it flashed the battery/charge icon for half a second, then blank screen.
I had a chat with a Google support agent who got me to try a remote erase which, I'm guessing, hasn't been received by my phone.
So my Android experience thus far has been: spending more than I've ever spent on a phone for a device that I accessed wifi on for a few weeks, then started to set up as my daily driver for a few weeks, just in time for it to seemingly die. Oh yeah, and of course, it's out of warranty. This world is new to me. Google's suggestion was to send it in to a partner for repairs (who knows how much that will cost). I'm hoping there's something else I can try before resorting to that.
Originally I was hoping to get some data off it. I'm not familiar with what Google backs up within Android (I had those settings checked, but no third party backup apps). I guess my photos should be backed up which would have been the biggest thing. Now I'd just like to recover the device without having to spend more money!
Oh, previous owner had Oreo 8.1 on it.
Any guidance would be most appreciated. Back to my trusty 5+ yr old Lumia 1020 in the interim!
Click to expand...
Click to collapse
Factory reset.
Sounds like a hardware problem. Most likely a motherboard issue. Try flashing the official 8.0 factory image first though.
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.