Hi,
A few hours ago I randomly got into a some kind of bootloop. It's not the "normal" bootloop where simply the boot animation is played forever. Instead my boot continues afterwards like normal until there's this short black screen before entering your SIM's pin card. This never appears and it begins again with the "Your bootloader is unlocked. Please lock it...."-message.
I already flashed the Factory Image twice via the ADB console on my PC and Wugfresh's Toolkit.
Additionally I can't seem to acess the stock recovery, the "red android guy" never appears and it only reboot itself after choosing the recovery in Fastboot Mode.
Any help is appreciated!
Vulkaistos
Try to flash TWRP, in TWRP wipe every partition and then try to flash the stock image again
Sent from my Nexus 5X using Tapatalk
dc239 said:
Try to flash TWRP, in TWRP wipe every partition and then try to flash the stock image again
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I already tried that, same problem as Stock Recovery.
Vulkaistos said:
I already tried that, same problem as Stock Recovery.
Click to expand...
Click to collapse
It seems like your partitions are messed up, did you tried to flash it via the flash-all script that is included in the stock image zip file?
dc239 said:
It seems like your partitions are messed up, did you tried to flash it via the flash-all script that is included in the stock image zip file?
Click to expand...
Click to collapse
Nope, I flashed them one by one. I may try the flash-all script now. Thanks!
Vulkaistos said:
Nope, I flashed them one by one. I may try the flash-all script now. Thanks!
Click to expand...
Click to collapse
OK, I now tried the flash-all script with the newest factory image drectly from Google but still the same issue.
I'll now contact Lg to at least try to get a RMA because I think I tried the most solutions.
If there's anyone that has another Idea, feel free to post it here
Vulkaistos said:
OK, I now tried the flash-all script with the newest factory image drectly from Google but still the same issue.
I'll now contact Lg to at least try to get a RMA because I think I tried the most solutions.
If there's anyone that has another Idea, feel free to post it here
Click to expand...
Click to collapse
Yea, that would be the best idea. Maybe it's slowly getting into that "classic" bootloop, which everyone talks about
Sent from my Nexus 5X using Tapatalk
dc239 said:
Yea, that would be the best idea. Maybe it's slowly getting into that "classic" bootloop, which everyone talks about
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I got a very interesting update on my issue.
My phone worked for a few minutes now, it booted normally and I could even set it up completely. But now it's the same problem again so I more and more think it could be faulty hardware.
Anyways I contacted LG for a RMA and we'll what happens.
Thanks for your help
Vulkaistos said:
I got a very interesting update on my issue.
My phone worked for a few minutes now, it booted normally and I could even set it up completely. But now it's the same problem again so I more and more think it could be faulty hardware.
Anyways I contacted LG for a RMA and we'll what happens.
Thanks for your help
Click to expand...
Click to collapse
You'll get the RMA, that is a hardware failure.
Last Update:
LG accepted my RMA request and I'll send them it ASAP.
Thank you everyone for helping me!
I'll mark this thread as solved.
Vulkaistos said:
Last Update:
LG accepted my RMA request and I'll send them it ASAP.
Thank you everyone for helping me!
I'll mark this thread as solved.
Click to expand...
Click to collapse
Little OT, but how long have you had your 5X? It looks like all the 5x's are just time bombs in case of that hardware bootloop. I'm thinking about selling my 5x and buying something that will not die on me some day.
Sent from my Nexus 7 using Tapatalk
dc239 said:
Little OT, but how long have you had your 5X? It looks like all the 5x's are just time bombs in case of that hardware bootloop. I'm thinking about selling my 5x and buying something that will not die on me some day.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I bought my Nexus in December 2015 so around 2 1/2 years ago. It's a nice phone never had any serious problems with it except now.
Related
I've been using my Galaxy Nexus for a month or so, with the official JB ROM (JR30C or whatever, deodexed and rooted) and today I opened Gmail.
That's it. I opened GMail, switched accounts, and my phone has been bootlooping ever since.
I wiped everything in CWM multiple times and reflashed it, and I can't get the phone to do anything else.
Any clues?
Do you have a working nandroid? Have you tried flashing a different ROM?
Allons-y
Xfanatic said:
Do you have a working nandroid? Have you tried flashing a different ROM?
Allons-y
Click to expand...
Click to collapse
I do not have a working NANDROID. I wasn't sure about the Internet policies at work, but it looks like I can at least make it on here, I'm not sure I'll be able to download another ROM.
I'm confused though, I mean I know it would help to try as many options as possible (to fix it) - but this ROM has been working for weeks. And the phone died randomly, not due to a recent file change or a botched program. The only boot loops I've experienced before were on the Nexus One, and it was always due to a buggy/bad flash or a corrupted ROM download - this one just developed epilepsy on its own...
Here's my plan, since these are the only things I can manage to download due to restrictions on Internet usage at work.
Factory 4.1.1 takju image from here : https://developers.google.com/android/nexus/images#takju
Modified ODIN software here: http://forum.xda-developers.com/showthread.php?t=1586807
ODIN won't rewrite my bootloader, recovery, or userdata, since I already OEM unlocked, but will reflash a stock image.
EDIT: ODIN won't do anything with my device. Trying this ROM instead:
http://forum.xda-developers.com/showthread.php?t=1801664 was using bigxie OTA before.
is your (sd)storage recognized? thus is a similar symptom to when the stirage goes bad.
Hook the phone up to adb, boot it, and let logcat run. Maybe that will turn something up.
Sent from my Galaxy Nexus using Tapatalk 2
simms22 said:
is your (sd)storage recognized? thus is a similar symptom to when the stirage goes bad.
Click to expand...
Click to collapse
Hmm, you know, I'm not able to find the option to mount to USB in CWM...and just in case I forgot where that is, when I plug it in, I get the "hardware failed" noise from Windows and not the usual friendly "plug in" sound.
infazzdar said:
Hook the phone up to adb, boot it, and let logcat run. Maybe that will turn something up.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'm at work, and I only have my work computer. Group/secpolicy won't allow me to install anything, no admin rights, etc.
Would it even do anything? The phone barely makes it through one second of the boot animation before it loops.
sheik124 said:
Hmm, you know, I'm not able to find the option to mount to USB in CWM...and just in case I forgot where that is, when I plug it in, I get the "hardware failed" noise from Windows and not the usual friendly "plug in" sound.
Click to expand...
Click to collapse
you cant mount the sd card. there is no USB mass storage period. not in recovery or booted normally.
Zepius said:
you cant mount the sd card. there is no USB mass storage period. not in recovery or booted normally.
Click to expand...
Click to collapse
Oy. Then how do I get another ROM on here? fastboot/adb?
sheik124 said:
Oy. Then how do I get another ROM on here? fastboot/adb?
Click to expand...
Click to collapse
Adb push.
Sent from my Galaxy Nexus using Tapatalk 2
Zepius said:
you cant mount the sd card. there is no USB mass storage period. not in recovery or booted normally.
Click to expand...
Click to collapse
sheik124 said:
Oy. Then how do I get another ROM on here? fastboot/adb?
Click to expand...
Click to collapse
Got more than one additional ROM on there via adb/recovery - my clue that CWM hasn't actually been able to do anything since the phone start looping is I'm still getting my custom boot animation.
I'm using the toolkit to reflash a stock image now. What a mess.
Even reflashing a stock image via fastboot did nothing. WTF happened to my phone? Won't stay on long enough to get a logcat
I'm having the same problem as this guy:
http://forum.xda-developers.com/showthread.php?t=1827685&page=2
I just got finished trying to flash 4.1.1 using ODIN. It still shows me the custom animation from bigxie's ROM (which has supposedly since been overwritten 2-4x times).
Screw you Samsung...this phone is a month old, I flashed -once- to rooted Jelly Bean, and the phone dies when I open the GMail app.
EDIT: WTF - I write screw you Samsung, it boots to the Welcome screen! Just long enough for me to see that my files aren't on it anymore, then it bootloops again. And again. Now it's re-stuck in a bootloop.
And now I'm at the homescreen. I can't rely on this thing like this...is my flash dying or something?
Nobody?
It worked long enough for me to re-enter all of my different Google account information and now it's dead again. Now it only flashes the boot animation for a split second for bootlooping.
I'm thinking of a hardware defect.
Beamed from my Grouper
Mach3.2 said:
I'm thinking of a hardware defect.
Beamed from my Grouper
Click to expand...
Click to collapse
Mee too. As you can see from my signature, I gave up and bought a One S yesterday night from Craigslist. Feels like a true successor to the Desire / N1. It's nice to finally have an AMOLED screen that actually seems color calibrated after the ugly mess that was my RAZR and my less than perfect GNex. It's a damn shame how much more painless flashing a recovery was on this thing.
Sent from my HTC VLE_U using xda app-developers app
Hey there, this is my first post here so go easy on me.
I was fortunate enough to unlock my HTC One through the HTCDev site and didn't do anything really exciting with the phone for a few days. However, last night I flashed newtoroot's GPE rom and have been unable to send or receive phone calls or messages on my device.
According to newtoroot, when the phone begins setup and tries to activate on the network you should try to avoid that step by pressing back. However, pressing back or home buttons wouldn't let me escape that process and it just continued all the way through. I suspect this is where the issues started. Anyway, after it finally finished searching for the network, it said it failed to activate.
I tried wiping my data/cache/dalvik and flashing the stock rom, and newt's other Sense based rom, but neither have helped. I thought I had made a backup, but apparently I didn't.
Any ideas? Thanks for taking the time to read through my problem!
Try taking the sim card out and putting it back in and reset the phone. That worked for me one time with my DNA.
Sent from my 4G LTE HTC One
Storkie said:
Hey there, this is my first post here so go easy on me.
I was fortunate enough to unlock my HTC One through the HTCDev site and didn't do anything really exciting with the phone for a few days. However, last night I flashed newtoroot's GPE rom and have been unable to send or receive phone calls or messages on my device.
According to newtoroot, when the phone begins setup and tries to activate on the network you should try to avoid that step by pressing back. However, pressing back or home buttons wouldn't let me escape that process and it just continued all the way through. I suspect this is where the issues started. Anyway, after it finally finished searching for the network, it said it failed to activate.
I tried wiping my data/cache/dalvik and flashing the stock rom, and newt's other Sense based rom, but neither have helped. I thought I had made a backup, but apparently I didn't.
Any ideas? Thanks for taking the time to read through my problem!
Click to expand...
Click to collapse
Follow the stuff they did in the CM10.2 thread to get calls/data working on that. It involved flashing the stock recovery and some other stuff, idk but it worked so it can't hurt to try.
Sent from my Nexus 7 using Tapatalk 2
Something similar happened to me. I had to go into Settings -> Mobile Data, and change Preferred Network from Global to LTE / CDMA mode. I'm not sure why it picked Global as the default.
antp121 said:
Follow the stuff they did in the CM10.2 thread to get calls/data working on that. It involved flashing the stock recovery and some other stuff, idk but it worked so it can't hurt to try.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Thanks so much for referring me to that thread. Followed the steps and flashed the stock recovery and did a factory reset within HBOOT. It did the trick! Thanks everyone for helping me get this solved.
antp121 said:
Follow the stuff they did in the CM10.2 thread to get calls/data working on that. It involved flashing the stock recovery and some other stuff, idk but it worked so it can't hurt to try.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Storkie said:
Thanks so much for referring me to that thread. Followed the steps and flashed the stock recovery and did a factory reset within HBOOT. It did the trick! Thanks everyone for helping me get this solved.
Click to expand...
Click to collapse
I wish we saw more interactions like this on XDA. I gave both you guys a thumbs up for restoring my faith in humanity.
Sent from my HTC6500LVW using Tapatalk 4
Storkie said:
Thanks so much for referring me to that thread. Followed the steps and flashed the stock recovery and did a factory reset within HBOOT. It did the trick! Thanks everyone for helping me get this solved.
Click to expand...
Click to collapse
No problem
Sent from my Nexus 7 using Tapatalk 2
antp121 said:
No problem
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I'm looking through that thread and can't find the HBOOT method to fix this problem, I believe I am going through the same thing. If someone could help or post their method I would be eternally greatful. Also the link for the vzw stock recovery is giving me a 500 error internal server error so if someone could post that I'd be very appreciative.
I hit a boot loop snag on my Galaxy Nexus GSM after installing the recent 4.3 OTA security update. I had no issues with the initial Android 4.3 release, but the security update did something that made my device hit a boot loop. I could restore from a Nandroid backup, but about once a day I would hit the boot loop snag again. After dealing with daily restores for a couple days I dug into it a bit and found that when the phone gets mired in a boot loop I can fix it by deleting two files.
The trick is you have to be using TWRP on the recovery partition because that will let you use a file manager to delete the two files. There may well be other solutions but that's been the easiest for me. The two files which need to be deleted are:
/data/system/locksettings.db
/data/system/locksettings.db-shm
If you use Google Wallet you'll see a similarly named file there "locksettings.db-wal" -- DO NOT DELETE THIS ONE, just the two above.
If this helps anyone please post so if it doesn't people won't waste their time -- THANKS!
Told my cousin she said that it worked like a charm! What do those two files actually do?
Sent from my Galaxy Nexus using Tapatalk 4
Vekhez said:
Told my cousin she said that it worked like a charm! What do those two files actually do?
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
To be honest -- I have no idea. I found this by pure trial and error after a totally non-related post pointed to the /data/system folder.
The files appear to get recreated when the phone reboots so it's probably generated from the system partition ultimately.
From what I know now, it appears as though SuperSU is causing this somehow. Is your cousin using SuperSU do you know?
There was a recent update to version 1.60 of SuperSU which was supposed to address this and I think it did for some users, perhaps Nexus 4 users only, but I definitely have this issue still even with the newest 1.65 version.
I've ended up created a Tasker script to delete the files on reboot because I was tired of having to repetitively reboot into TWRP and manually delete them. It works well but I'd much rather fix the underlying cause.
sansnil said:
To be honest -- I have no idea. I found this by pure trial and error after a totally non-related post pointed to the /data/system folder.
The files appear to get recreated when the phone reboots so it's probably generated from the system partition ultimately.
From what I know now, it appears as though SuperSU is causing this somehow. Is your cousin using SuperSU do you know?
There was a recent update to version 1.60 of SuperSU which was supposed to address this and I think it did for some users, perhaps Nexus 4 users only, but I definitely have this issue still even with the newest 1.65 version.
I've ended up created a Tasker script to delete the files on reboot because I was tired of having to repetitively reboot into TWRP and manually delete them. It works well but I'd much rather fix the underlying cause.
Click to expand...
Click to collapse
Yeah, they are using SuperSU...they are still on 1.5, I'll tell them to update.
Sent from my Galaxy Nexus using Tapatalk 4
Vekhez said:
Yeah, they are using SuperSU...they are still on 1.5, I'll tell them to update.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Thanks, Vekhez. Let me know if that hopefully fixes the problem for them. If it does it means I'm "special" not in a good way!
sansnil said:
Thanks, Vekhez. Let me know if that hopefully fixes the problem for them. If it does it means I'm "special" not in a good way!
Click to expand...
Click to collapse
Nope it didn't.. Same problem.
Sent from my Galaxy Nexus using Tapatalk 4
Vekhez said:
Nope it didn't.. Same problem.
Click to expand...
Click to collapse
Thanks for this. I'm sorry for your cousin but happy for me because that means it's not something unique or specific to my device.
This is helpful -- I'm going to post this over in the SuperSU thread and see if Chainfire will pick it up and look into it.
Stay tuned...
sansnil said:
Thanks for this. I'm sorry for your cousin but happy for me because that means it's not something unique or specific to my device.
This is helpful -- I'm going to post this over in the SuperSU thread and see if Chainfire will pick it up and look into it.
Stay tuned...
Click to expand...
Click to collapse
Ok, so it turns out this is actually being caused by the app "Delayed Lock" if you use a pattern lock. If you use a PIN/password lock it won't happen, but if you use a pattern lock with the current version of Delayed Lock on a Galaxy Nexus this boot loop issue will occur.
I've opened a bug with the Delayed Lock Dev so hopefully he'll find a way to fix it. In the meantime, choices are to either disabled/uninstall Delayed Lock (hate!) or switch to a PIN or password lock setting.
Hey guys,
I had the same problem and found out that it could be solved, without losing any data, by directly flashing the update.
Here's what I did: http://forum.xda-developers.com/showthread.php?t=2427613
Best of luck.
please help me, thanks a lot. The following is the detailed picture.
byyangatchina said:
please help me, thanks a lot. The following is the detailed picture.
Click to expand...
Click to collapse
btw, My current stock rom version on nexus 7 is 4,4,2, and this wifi problem had bother me many times. I had to have the device restore factory settings once, and the problem disappears. But one day it come up again. I DO not know how to deal with it. Please help me. Thank you.
byyangatchina said:
btw, My current stock rom version on nexus 7 is 4,4,2, and this wifi problem had bother me many times. I had to have the device restore factory settings once, and the problem disappears. But one day it come up again. I DO not know how to deal with it. Please help me. Thank you.
Click to expand...
Click to collapse
I don't know why it does that, I'm sure someone else does. But I would suggest rooting and install a ROM. That should take care of it.
Sent from my Nexus 7 using Tapatalk
barondebxl said:
I don't know why it does that, I'm sure someone else does. But I would suggest rooting and install a ROM. That should take care of it.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thank you for your advice. i have considered flashing ROM but i do not want to errase all my data. If i can get a solution for this problem, that will be great. can this be something related to software confliction?
byyangatchina said:
Thank you for your advice. i have considered flashing ROM but i do not want to errase all my data. If i can get a solution for this problem, that will be great. can this be something related to software confliction?
Click to expand...
Click to collapse
I have no idea honestly, this is weird.
Sent from my Nexus 7 using Tapatalk
Try factory reset and it may work?
byyangatchina said:
Thank you for your advice. i have considered flashing ROM but i do not want to errase all my data. If i can get a solution for this problem, that will be great. can this be something related to software confliction?
Click to expand...
Click to collapse
So, backup your data first. If you have a PC, you can use Helium to backup your apps and data to your PC, you don't need root either. And you can just use MTP to transfer your /sdcard to a folder on your PC.
Bobbi lim said:
Try factory reset and it may work?
Click to expand...
Click to collapse
i did and after a few days use, the problem occurs again. now i have flashed the stock ROM, and the wifi goes well. but i dont know whether the same problem will appear again.
As others have said-install a custom ROM, I'd suggest something close to stock. If the device keeps acting strangely, and the problem occurs again, relock the boot loader, restore to stock(all can be done with Wug's toolkit)and send it for repair, as the problem might be faulty hardware.
How long have you been facing this issue? Once it's grayed out, can you turn it on/off, or is it stuck until you reboot? Are you using a custom kernel? Is the device rooted?
Sent from my Nexus 7 using XDA Premium 4 mobile app
This happened to me once, on an unstable rom, but on stock is kinda weird.
I know this can be a bad Idea. But I am on a time crunch to return this RMA and I have been gone on a business trip. Which now leaves me with only a few days (including shipping) to get my RMA all running and my old phone sent back to Google without having to pay for the phone in full. My problem is I have no way to pull my data off my old phone because anytime I do it say is Analog Audio Accessory Detected. (The Attached Deviced is not compatible with this phone).... So I had to get a RMA. I can't even charge my phone with my original charger. Also my old 6P charger... Only my watch charger which is only .5A...
Is there a way to restore a old backup I have on my computer from my old phone to my RMA without any problems? Also I have done this once but ran into the fingerprint problems and Ti backup with its Android ID issue. Other than that NO problems. Here is something somewhat similar to the problem for the fingerprint sensor. But I notice that the some of the stuff is missing on the Pixel. https://forum.xda-developers.com/nexus-6p/help/fingerprint-issue-restoring-twrp-backup-t3307734
stalls said:
I know this can be a bad Idea. But I am on a time crunch to return this RMA and I have been gone on a business trip. Which now leaves me with only a few days (including shipping) to get my RMA all running and my old phone sent back to Google without having to pay for the phone in full. My problem is I have no way to pull my data off my old phone because anytime I do it say is Analog Audio Accessory Detected. (The Attached Deviced is not compatible with this phone).... So I had to get a RMA. I can't even charge my phone with my original charger. Also my old 6P charger... Only my watch charger which is only .5A...
Is there a way to restore a old backup I have on my computer from my old phone to my RMA without any problems? Also I have done this once but ran into the fingerprint problems and Ti backup with its Android ID issue. Other than that NO problems. Here is something somewhat similar to the problem for the fingerprint sensor. But I notice that the some of the stuff is missing on the Pixel. https://forum.xda-developers.com/nexus-6p/help/fingerprint-issue-restoring-twrp-backup-t3307734
Click to expand...
Click to collapse
I assumed you did a twrp backup of your broken phone, and saved it to your pc. If so, when you get the new phone, unlock it, install twrp, you could, in theory, restore your data partition from the backup you made. Google restore also works pretty good, which should be saved on your google drive. I would also recommend you keep your screen lock set to none or swipe before you begin. Best of luck to ya
Badger50 said:
I assumed you did a twrp backup of your broken phone, and saved it to your pc. If so, when you get the new phone, unlock it, install twrp, you could, in theory, restore your data partition from the backup you made. Google restore also works pretty good, which should be saved on your google drive. I would also recommend you keep your screen lock set to none or swipe before you begin. Best of luck to ya
Click to expand...
Click to collapse
Got it up and ruinning Badger! So how do I go about updating to the latest July Patch on DU ROM? I am on June? Thanks again!
stalls said:
Got it up and ruinning Badger! So how do I go about updating to the latest July Patch on DU ROM? I am on June? Thanks again!
Click to expand...
Click to collapse
I'm not even sure if DU has been updated yet. If it has, then pull the vendor.img from the factory image and put it on your phone. Go into twrp, wipe ART/dalvik cache only! Then flash the vendor.img to the vendor partition, then flash the rom, then the twrp installer zip, boot up, and hopefully everything is ok. Then go back to twrp and flash your kernel(optional) and then magisk. Then you should be good :good:
Badger50 said:
I'm not even sure if DU has been updated yet. If it has, then pull the vendor.img from the factory image and put it on your phone. Go into twrp, wipe ART/dalvik cache only! Then flash the vendor.img to the vendor partition, then flash the rom, then the twrp installer zip, boot up, and hopefully everything is ok. Then go back to twrp and flash your kernel(optional) and then magisk. Then you should be good :good:
Click to expand...
Click to collapse
Do I have to flash the previous Factory image if I might have tried to flash the latest update lol and start all over ?
stalls said:
Do I have to flash the previous Factory image if I might have tried to flash the latest update lol and start all over ?
Click to expand...
Click to collapse
Either that, or just stay on stock July and wait for DU to be updated
Badger50 said:
Either that, or just stay on stock July and wait for DU to be updated
Click to expand...
Click to collapse
But Man I love to screw things up and have to fix them
stalls said:
But Man I love to screw things up and have to fix them
Click to expand...
Click to collapse
Then have at it Big Dog! ???
I'm curious if anyone has restored a TWRP nandroid from their original phone to the RMA. My understanding is that it should be fine as long as you make sure you're on the right base factory image first.
Reechings said:
I'm curious if anyone has restored a TWRP nandroid from their original phone to the RMA. My understanding is that it should be fine as long as you make sure you're on the right base factory image first.
Click to expand...
Click to collapse
I've seen it done on the 6P without issue. Should be ok on the P2XL so long as it's just the data partition your restoring :good:
Badger50 said:
I've seen it done on the 6P without issue. Should be ok on the P2XL so long as it's just the data partition your restoring :good:
Click to expand...
Click to collapse
Yeah that makes the most sense, I'll restore my data then "dirty flash" the rom I'm using over top.
Reechings said:
Yeah that makes the most sense, I'll restore my data then "dirty flash" the rom I'm using over top.
Click to expand...
Click to collapse
That's what I did and it works perfect
Sent from my Pixel 2 XL using XDA-Developers Legacy app
stalls said:
That's what I did and it works perfect
Click to expand...
Click to collapse
How did your RMA turn out?
Reechings said:
How did your RMA turn out?
Click to expand...
Click to collapse
Pretty good so far
Sent from my Pixel 2 XL using XDA-Developers Legacy app
stalls said:
Pretty good so far
Click to expand...
Click to collapse
How's the screen? What's the manufacturing date of replacement unit?
Reechings said:
How's the screen? What's the manufacturing date of replacement unit?
Click to expand...
Click to collapse
Normal blue tint thing still but not bad.. it was in October
Sent from my Pixel 2 XL using XDA-Developers Legacy app
stalls said:
Normal blue tint thing still but not bad.. it was in October
Click to expand...
Click to collapse
Ok. My last RMA was from October too. We'll see what this one is.