Related
I've currently got an issue with my Dash that is making it nearly unusable. On a regular basis the phone will turn off and then right back on and reconnect to the T-mobile network. The device doesn't turn off, just the phone as though I put it in flight mode. Also, the device does sometimes reboot in my pocket. I also get Call Failed errors and sometimes SIM errors when making calls and sending SMS. I had this issue once before a couple months ago and replaced the SIM which did not fix the issue, but installing the new WM6.1 corrected it until just a couple days ago. Tried reinstalling the OS again, but this time the issue persists.
Here's the odd part.... I'm sure it's just a coincindence, but both times this has happened now has been right after taking a flight. The device was powered off both times, but that is when the issue came up last time and again this time. Any advice or possible ways to correct the issue would be HUGELY appreciated. Thanks in advance.
Jory
Ummm do you still have warranty on the phone cause if you do just ask for a replacement
jdoggraz said:
Ummm do you still have warranty on the phone cause if you do just ask for a replacement
Click to expand...
Click to collapse
Unfortunately I believe the phone is out of warranty. If I'm not mistaken the phone only has 1 year and I purchased it back in December of 2006. Am I to assume this phone is just gone and needs replacing?
I am faced with the exact same issues & my phone is from Dec 2006 as well. I ordererd a new battery to see if anything changes but I am lost as to what to do next. I flashed my phone to Ricky's (Old was TMO) and even then the issue still persists.
That would definitely be a manufacture issue.
Hey guys,
I have a 5X that recently had a bootloop. The motherboard was swapped out using a donor phone. The phone is happy now with the exception of constant signal drops. I'm currently running 7.1.2 Pure Nexus rom however this issue was happening on stock 7.1.1 and after a 8.0 update (I reverted back to 7.1.2). The phone will behave normally then out of the blue the single strength indicator triangle is displays empty with an outlined triangle vs the traditional filled. I have no data and no cellular service. The only way I can get service back is after a reboot. Sometimes service will last 10 min, other times 4 hours. When I do have service its significantly weaker than typical, ~ -110. Is there some sort of hardware handshake that needs fixing? Would flashing a different radio be worthwhile? Wifi works fine and never cuts out. Any help would be most appreciated as this is very frustrating! Thanks in advance.
-Jesse
you can flash any roms with your repaired phone?
how did you that??
does your bootloader the "no RPMB" message?
jstein84 said:
Hey guys,
I have a 5X that recently had a bootloop. The motherboard was swapped out using a donor phone. The phone is happy now with the exception of constant signal drops. I'm currently running 7.1.2 Pure Nexus rom however this issue was happening on stock 7.1.1 and after a 8.0 update (I reverted back to 7.1.2). The phone will behave normally then out of the blue the single strength indicator triangle is displays empty with an outlined triangle vs the traditional filled. I have no data and no cellular service. The only way I can get service back is after a reboot. Sometimes service will last 10 min, other times 4 hours. When I do have service its significantly weaker than typical, ~ -110. Is there some sort of hardware handshake that needs fixing? Would flashing a different radio be worthwhile? Wifi works fine and never cuts out. Any help would be most appreciated as this is very frustrating! Thanks in advance.
-Jesse
Click to expand...
Click to collapse
openyourmind said:
you can flash any roms with your repaired phone?
how did you that??
does your bootloader the "no RPMB" message?
Click to expand...
Click to collapse
I'm not sure I understand the question. After swapping, the device behaves like a new phone. I was able to install TWRP, unlock bootloader, root etc. I do not receive any error about "no RPMB".
weird... I'm a little confused.
I read in many different forums that the repaired Nexus5x can no longer be rooted.
I have tried it with mine several times already unsuccessfully.
When you start the bootloader you see the message (no RPMB)
Maybe somebody has a solution for this?
openyourmind said:
I read in many different forums that the repaired Nexus5x can no longer be rooted.
Click to expand...
Click to collapse
Depends on who does it. LG UK replaced my motherboard last month. After repair, I was able to root it as easily as I did when I first got the phone.
my phone was at lg german
for over 2 weeks I am looking for a solution
Mine was not sent to a repair facility, I was fortunate to have a donor. Thread has slightly gotten off topic. Any thoughts to flashing another radio? Are some OS better suited for specific radios? Is there a way to verify which radio is most compatible with my OS / rom?
When I got my 5x repaired (motherboard replacement with brand new manufactured at 7/8/17) I can root my phone, unlocking bootloader etc.
Hi jstein84, I've the same identical problem (motherboard replacement after bootloop, and now intermittent signal and very poor reception, often -110dB)... Did you find any solution?
sebastian90 said:
Hi jstein84, I've the same identical problem (motherboard replacement after bootloop, and now intermittent signal and very poor reception, often -110dB)... Did you find any solution?
Click to expand...
Click to collapse
Could it be that something wasn't reattached correctly by the repairer?
In my case, the phone was perfect for 2-3 months after the replacement (never dropped, never got water in this period). Now, since one week, it started issuing this new problem, which seems to be very common after screen or mb replacement in the 5X. Very poor signal, with every SIM card I tried (it happened after I used the wifi hotspot, but no sure it matters). I've tried resetting network settings and hard resetting the phone, nothing changed. I've also tried to check the speaker component inside the rear case (where there are the antennas). It seems ok, I just noticed that if I cover the bottom left right corner of the phone, the signal totally disappears immediately. I'm getting crazy with this problem...
sebastian90 said:
In my case, the phone was perfect for 2-3 months after the replacement (never dropped, never got water in this period). Now, since one week, it started issuing this new problem, which seems to be very common after screen or mb replacement in the 5X. Very poor signal, with every SIM card I tried (it happened after I used the wifi hotspot, but no sure it matters). I've tried resetting network settings and hard resetting the phone, nothing changed. I've also tried to check the speaker component inside the rear case (where there are the antennas). It seems ok, I just noticed that if I cover the bottom left corner of the phone, the signal totally disappear instantly. I'm getting crazy with this problem...
Click to expand...
Click to collapse
You might try flashing the stock firmware with fastboot. I had a similar issue with bluetooth randomly cutting out. After flashing the stock firmware bluetooth now works without issue. I can't tell you why it fixed it because it shouldn't have made a difference, but maybe something got corrupted. Worth a try.
Sent from my [device_name] using XDA-Developers Legacy app
Thank you for your suggestion! I'll try and then I'll let you know if it works!
jd1639 said:
You might try flashing the stock firmware with fastboot. I had a similar issue with bluetooth randomly cutting out. After flashing the stock firmware bluetooth now works without issue. I can't tell you why it fixed it because it shouldn't have made a difference, but maybe something got corrupted. Worth a try.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I've flashed the stock firmware with fastboot, but nothing changed. It seems to be an hardware problem: when covering the right side of the phone, in particular the bottom right corner (and not the left one, as I wrongly said before), the signal immediately drops...
sebastian90 said:
I've flashed the stock firmware with fastboot, but nothing changed. It seems to be an hardware problem: when covering the right side of the phone, in particular the bottom right corner (and not the left one, as I wrongly said before), the signal immediately drops...
Click to expand...
Click to collapse
I'm glad to see this post is getting some new activity. To answer Sebastian's question, my phone seems better but still not great. I seem to have better coverage but I noticed that if I enter a complete dead zone, I get the hollow triangle, and the phone is not able to get service again until a reboot. This is after returning to a known service area. I have received numerous ota updates since my original post so I'm not sure if that's the cause. I had also tried flashing new radios a few months ago but to no avail. I personally believe that its a hardware issue but I have no way to verify that. I'm glad Im not the only one and I hope this helps out somebody. If nothing else its validation that you're not alone.
I am running the security patch dated January 5, 2018 and Android 8.1.0. Probably two weeks ago, I started having problems making and receiving phone calls and went back to the Verizon Store. At first Google and Verizon thought it may be a hardware issue, but had to do a factory reset to rule that possibility out or in. Today I started having similar issues and brought it back to the store. Since I rely on the phone for my business, factory resetting, even once per month is unacceptable. I called Google from the store and all they could offer was that this is a known issue and I will need to do another factory reset. I am in the process of completing this right now. Has anyone else had similar issues? I bought the phone since I want as close a pure android experience as possible, but I can't run my business with an unreliable phone. Are there any ROMs out there that are stable and don't have this issue?
if they wont RMA for that issue, then id call and just say you have burn in or the screen is very blue. should get an immediate RMA. They never questioned me when i got mine swapped
redman1982 said:
I am running the security patch dated January 5, 2018 and Android 8.1.0. Probably two weeks ago, I started having problems making and receiving phone calls and went back to the Verizon Store. At first Google and Verizon thought it may be a hardware issue, but had to do a factory reset to rule that possibility out or in. Today I started having similar issues and brought it back to the store. Since I rely on the phone for my business, factory resetting, even once per month is unacceptable. I called Google from the store and all they could offer was that this is a known issue and I will need to do another factory reset. I am in the process of completing this right now. Has anyone else had similar issues? I bought the phone since I want as close a pure android experience as possible, but I can't run my business with an unreliable phone. Are there any ROMs out there that are stable and don't have this issue?
Click to expand...
Click to collapse
I too am on big red, using an unlocked phone from google, not the Verizon variant. If you've done 3 factory resets, and still having the problem, then I'd say it's either a hardware, or sim card issue. Since you can't unlock the bootloader to try a different radio, or flash a factory image, I'd definitely lobby hard for a replacement. That's just not right. Certainly hope you get it figured out though.
redman1982 said:
I am running the security patch dated January 5, 2018 and Android 8.1.0. Probably two weeks ago, I started having problems making and receiving phone calls and went back to the Verizon Store. At first Google and Verizon thought it may be a hardware issue, but had to do a factory reset to rule that possibility out or in. Today I started having similar issues and brought it back to the store. Since I rely on the phone for my business, factory resetting, even once per month is unacceptable. I called Google from the store and all they could offer was that this is a known issue and I will need to do another factory reset. I am in the process of completing this right now. Has anyone else had similar issues? I bought the phone since I want as close a pure android experience as possible, but I can't run my business with an unreliable phone. Are there any ROMs out there that are stable and don't have this issue?
Click to expand...
Click to collapse
Redman1982 .. I had the exact same issue after installing the January Security Patch .. after calls to both Google and Verizon, took back to Verizon store and they switched it out for a brand new sealed one.
Like others have said, after multiple factory resets on a locked device, you should demand Google replace your $900 flagship device that is not working properly after 3 factory resets, and nothing you can do to it (it's locked) could make it not work, so it's obviously a faulty device issue.
I would certainly try to get Google to send you a replacement, as several folks who had VZW locked devices have said when getting Google replacement devices, they were sent unlockable Google variants instead of locked Verizon variants.
It might be a long shot, but if you go into a VZW store, you have a 100% chance of getting another locked device
Either way, don't stop bugging them until they replace your device!
Good luck!
Az Biker said:
Like others have said, after multiple factory resets on a locked device, you should demand Google replace your $900 flagship device that is not working properly after 3 factory resets, and nothing you can do to it (it's locked) could make it not work, so it's obviously a faulty device issue.
I would certainly try to get Google to send you a replacement, as several folks who had VZW locked devices have said when getting Google replacement devices, they were sent unlockable Google variants instead of locked Verizon variants.
It might be a long shot, but if you go into a VZW store, you have a 100% chance of getting another locked device
Either way, don't stop bugging them until they replace your device!
Good luck!
Click to expand...
Click to collapse
Yeah .. I tried doing that .. problem was, I walked into a Verizon store that had stock of the Pixel 2 XL Black 128GB version .. I was like .. ****tttt .. LOL
LordGeek said:
Yeah .. I tried doing that .. problem was, I walked into a Verizon store that had stock of the Pixel 2 XL Black 128GB version .. I was like .. ****tttt .. LOL
Click to expand...
Click to collapse
Update. I continued to have issues which began to include a loud screech when the other party answered. I went back to the store about two weeks ago and they gave me a new sim card. This worked about a week and began having problems again. I called Verizon Saturday night as I was unable to work. After about two hours of troubleshooting, the rep conceded that I should get a new phone which arrived yesterday. I hope this one works out.
Sent from my Pixel C using Tapatalk
redman1982 said:
Update. I continued to have issues which began to include a loud screech when the other party answered. I went back to the store about two weeks ago and they gave me a new sim card. This worked about a week and began having problems again. I called Verizon Saturday night as I was unable to work. After about two hours of troubleshooting, the rep conceded that I should get a new phone which arrived yesterday. I hope this one works out.
Click to expand...
Click to collapse
Keep us posted on your progress.
I wonder if it is a common problem
I've been having this same issue since the March update. I make calls and I don't get the ringing tone and when the other person answers the call there's no audio. I've already done a factory reset and this is already my second Pixel 2 XL. This sucks.
brazcub said:
I've been having this same issue since the March update. I make calls and I don't get the ringing tone and when the other person answers the call there's no audio. I've already done a factory reset and this is already my second Pixel 2 XL. This sucks.
Click to expand...
Click to collapse
Did you have any Bluetooth connected? I have Gear S2 smarwatch connected and I had to switch off call forwarding to get rid of that issue
I have enabled jump to camera with double power button click. Ever since the may update the camera launches randomly when I try and shut my phone off.
Anyone else seeing this? Fix?
I've been noticing the same behavior. Happens intermittently with no real reason. No noticeable physical difference with the power button either. Still clicks just fine. Definitely seems like a software bug of sorts.
Itachisasuke said:
I've been noticing the same behavior. Happens intermittently with no real reason. No noticeable physical difference with the power button either. Still clicks just fine. Definitely seems like a software bug of sorts.
Click to expand...
Click to collapse
Google RMAed my phone for it (new one comes tomorrow) so I'll let you know if it persists across a hardware swap.
madscribblerz said:
Google RMAed my phone for it (new one comes tomorrow) so I'll let you know if it persists across a hardware swap.
Click to expand...
Click to collapse
Thanks for the reply. Good to know.
Two friends that also have this issue after the May update so I'm hoping that it's software but it's good to know we can get a replacement if it's not.
Any updates on the new device are appreciated.
Itachisasuke said:
Thanks for the reply. Good to know.
Two friends that also have this issue after the May update so I'm hoping that it's software but it's good to know we can get a replacement if it's not.
Any updates on the new device are appreciated.
Click to expand...
Click to collapse
So far no issues on new hardware, but was intermittent and unpredictable so not entirely certain issue has resolved. Given multiple reports its unlikely hardware.
I did do something slightly differently on this phone though. On my old I went from OPM2 to OPM4 with the June release. This time I stayed with OPM2. Only manually wrote June update, rest was OTA.
Will provide updates as time passes or if I see it again.
Itachisasuke said:
Thanks for the reply. Good to know.
Two friends that also have this issue after the May update so I'm hoping that it's software but it's good to know we can get a replacement if it's not.
Any updates on the new device are appreciated.
Click to expand...
Click to collapse
Promised update - since switching to the rma unit I've not seen this issue in any form. It could have been moving over to a clean userdata but otherwise the software and firmware were identical between my old and new phone.
Edit (1 Aug 2018): After one day of the factory reset, the problem started happening again but a lot less frequently than it was before the factory reset. After two days, the problem is back just as bad as it was before I did the reset. I'm certain this is a software problem because of this but it makes no sense to me.
----------------------
I had the same problem with my Pixel 2 XL and had an experience I wanted to share.
I did a factory reset on my phone and restored all of my apps and data from backup except for my device settings. The problem remained for just a few minutes after my phone booted after factory resetting it, but after that, I've never had the problem since.
I'm not too sure if this is a permanent fix yet, but it seems a factory reset solved the issue for me. Fingers crossed it lasts.
exactly the same issue. But i think this is definitely a hardware problem, due to a design defect or quality control. so replace with new machine would not fix this entirely.
hope this could be fixed on pixel 3
The same issue have been happening with my phone , was hoping someone had a solution. It had never been an issue until recently
I had this issue, Google just did an RMA without much question. Just had to check in Safe Mode. I suspect a slight quality issue with the button mechanism registering double clicks despite it only feeling like one click.
pemz82 said:
I had this issue, Google just did an RMA without much question. Just had to check in Safe Mode. I suspect a slight quality issue with the button mechanism registering double clicks despite it only feeling like one click.
Click to expand...
Click to collapse
Started a chat today with them, I got it through the Google Store and they are going to RMA my device as well. This is my second Google phone that had issues after a year. As much as I like the google phone . I can't say I trust it's QC . Nexus 6p was a useless brick after the power issue and bootloop and now this with the Pixel 2
I've also just started having this problem. I'm going to try a full wipe when Android 10 gets released on the 3rd. If that doesn't work, guess I'll be RMAing my 3rd phone.
2 days ago my display start to flickering (constant small horizontal line flickering) all over the screen.
What i have done is
1. wipe cache partition
2. restart
3. safe mode
but no luck.
during startup boot, recovery mode or optimising app no flickering seen.
Never had this before (Android 11). after 3 week updated to Android 12. this issue happen.
is it probably Firmware issue? currently im on G988BXXSCEUL9 XME (Malaysia)
Try using different fixed frequency display rates and brightness levels.
blackhawk said:
Try using different fixed frequency display rates and brightness levels.
Click to expand...
Click to collapse
Tried turn off adaptive brightness
Change from 60hz to 120hz and back to 60hz
Turn off/on night light
Eyeshield off
Screen mode to natural
Resolution to 1080 and 720
No luck.
Guess try reflashing it. If you can downgrade do so. Maybe a mobo failure, if a downgrade solves the issue... leave it there.
If under warranty, send it in.
blackhawk said:
Guess try reflashing it. If you can downgrade do so. Maybe a mobo failure, if a downgrade solves the issue... leave it there.
If under warranty, send it in.
Click to expand...
Click to collapse
its not underwarranty anymore. tried factory reset also no luck.
does reflashing remove my esim carrirer data?
apecx92 said:
its not underwarranty anymore. tried factory reset also no luck.
does reflashing remove my esim carrirer data?
Click to expand...
Click to collapse
Not sure as I haven't had to do it. I rarely mess with the firmware if it's running good even to do updates. This N10+ is still running on Pie, the current load will be 2yo in June.
Alright thanks for the reply. I will just wait for next update hopefully it will fix. Otherwise i'll just buy new phone
apecx92 said:
Alright thanks for the reply. I will just wait for next update hopefully it will fix. Otherwise i'll just buy new phone
Click to expand...
Click to collapse
Not written in stone. Maybe a loose connector or it got corrupted doing the upgrade. A Samsung Experience center at a Best Buy might be able to find the issue and if firmware, reflash it.
blackhawk said:
Not written in stone. Maybe a loose connector or it got corrupted doing the upgrade. A Samsung Experience center at a Best Buy might be able to find the issue and if firmware, reflash it.
Click to expand...
Click to collapse
I downgraded back to Android 11 Nov 2021 build using Odin (my esim data doesnt get erase).
no more flickering screen after 2 hour of usage, i will keep monitor the display and update here again.
Hopefully its the Android 12 Firmware issue not my hardware.
apecx92 said:
I downgraded back to Android 11 Nov 2021 build using Odin (my esim data doesnt get erase).
no more flickering screen after 2 hour of usage, i will keep monitor the display and update here again.
Hopefully its the Android 12 Firmware issue not my hardware.
Click to expand...
Click to collapse
Could be either or a combination of both. Best shot is to not update/upgrade it again. It can run for many years like that.
Android isn't PC and anything from Pie up is reasonably secure as is.
With 11 you have more than enough security in place unless you do something stupid... which is how malware usually gets loaded.
Hi
I'm having the same issue in my s20ultra exynos G988b/DS and it's nearly 2 years old and in clean condition. got this problem last week and it wasn't under the warranty anymore service center said it was hardware and need to changethe display which cost ~$290 which i refused since the device is not even scratched and pretty sure must be a software thing.
Came across your post today, can you verify that problem has gone after the downgrade?
Thanks in advance.