My OnePlus 3T gave up the ghost 2 weeks ago. I was running stock everything, unrooted.
One night I had just finished up a Pokemon GO trading session and went to plug in my phone (it was below 10%). I then noticed that the screen was frozen so I rebooted the phone, and then I got stuck in a boot loop.
(In hindsight, I was having connectivity issues with my network carrier (ATT) earlier in the day where I would randomly lose the signal, exclusive to this device)
I did the first sensible thing, I did a factory reset of the phone. During the setup process I can make it through several pages of the setup before the device freezes and shuts down. I then went through the fiasco that is OnePlus customer support. I did a live session this morning where the current ROM was flashed and I still get nothing. Their response is send it in for repair, which I'm guessing will cost more than the phone is worth.
I should note that the Fastboot and Recovery menus function fine. I have not rooted the device.
If anyone has thoughts on whether this is truly a hardware problem, I would appreciate them.
Related
I am having a boot loop issue. I have T-Mobile G4 that is NOT rooted. I bought it on release day. I too would get random reboots, particularly after the recent security update. I also noticed that the operating temperature was really high, a lot lately. I thought it was a rogue app (clean master). Anyway, I updated a few apps and installed a few watch faces. Suddenly, my phone was drained prematurely. Plugged it into a quick charge charger when all the fun begins. Early on it would boot to the home screen but would reboot a minute or two later. Then it stopped booting to home. On two occasions that I caught, it was starting up like a firmware update just installed with the "Android is starting 1 of 143 apps" type of line. After seeing that and still not getting to home, I figured I might as well factory reset it. Well I was amazed to discover that a factory reset yields the same boot loop. All I get is the LG logo.
Defeated. I go to my local TMo retailer where I bought the phone only to find out that I have to wait for delivery of a replacement( I smell refurb). I'm in Jump btw. I did notice that when the phone will boot to home screen for whatever length of time, the LED would work. The LED does not work during a boot loop. My research on this issue uncovered an alarming trend on the Internet. No solutions other than replacement. No cause has been identified either. Without proof, these are my top suspicions: Quick charge, 128G SD, apps moved to SD. My hunch is quick charge. All of my chargers are Qualcomm certified quick chargers. and I use them 95% of the time. I would hate to add LG to my list of boycotted Android vendors under Samsung.
Things I tried:
Recovery mode
Download mode
No SIM, Battery and/or SD
Swapping batteries
Safe mode (once)
This happened to me yesterday. I was listening to music through the bluetooth at the gym and it stopped playing. When I walked over to the phone it was already in a boot loop.
Reflashing does nothing nor does a factory reset. They are sending me a new one as well.
Funny thing is once it did make itself passed the boot screen to: "updating apps" This smells like an update is bricking phones. I went to the store and the agent said he couldn't find any data on a recent update but I think he wasn't looking at the right place. If there's an update bricking phones I will be livid. I'm 40 days away from a Jump upgrade and they said I can't exchange it early anyway because it "has to be in working condition." Well no ****, YOU can do the warranty replacement...give me a new phone! I too abandoned Samsung after the Lollipop Note Edge upgrade made the phone discharge in 3 hours or less and run as smooth as gravel. LG has suddenly made me sour too.
Same exact issue as you described.
Also tried everything you did. I went with TMO's replacement, and to my surprise, it was a new phone rather than a refurb.
Hi,
I've owned my VERIZON Samsung Galaxy Note 5 since early December and have not rooted the device. Today while taking notes in lecture, the device began displaying notices for crashed background apps (Gmail has crashed, Nova launcher has crashed, etc.) The problem persisted for another hour, even after booting into safe mode. I wiped the cache and factory reset the device, however during setup, Samsung keyboard would crash along with other apps running in the background during setup (One time I got "Samsung Galaxy has stopped working"). The phone started increasingly randomly rebooting since the phone first began to malfunction.
Since the factory reset didn't seem to actually reflash the firmware, I downloaded OJ3 stock ROM and flashed successfully using Odin, however the phone began acting even more erratically and failed to boot 4 out of every 5 boot loops. I tried flashing OGJ, which failed to boot worse than OJ3. I just flashed OJ2, which seems to be more stable than the other flashes I tried, however I'm still getting sluggish performance, random reboots and crashes of background apps immediately after booting.
At this point I believe it is defective hardware and I should call in the warranty for a new phone.
Has anyone experienced similar issues? Any speculation on the source of the issue? What should I know going into attempting to exchange for a new phone?
Note 5 crash
Yep, have the same problem, but I have not attempted to Flash the Phone yet...
Did multiple factory resets, clear caches... but to no avail. There is no structure or pattern in crash rate. Although it is getting more often day by day...
Found no working sollution, but it feels like there is a bad memory segment or something. Everytime it randomly uses that segment... crash!
Really don't know. Will try to get warrenty fix.
Let me know if you found a sollution on your side?
Cheers,
Wim
kbiscu1t said:
Hi,
I've owned my VERIZON Samsung Galaxy Note 5 since early December and have not rooted the device. Today while taking notes in lecture, the device began displaying notices for crashed background apps (Gmail has crashed, Nova launcher has crashed, etc.) The problem persisted for another hour, even after booting into safe mode. I wiped the cache and factory reset the device, however during setup, Samsung keyboard would crash along with other apps running in the background during setup (One time I got "Samsung Galaxy has stopped working"). The phone started increasingly randomly rebooting since the phone first began to malfunction.
Since the factory reset didn't seem to actually reflash the firmware, I downloaded OJ3 stock ROM and flashed successfully using Odin, however the phone began acting even more erratically and failed to boot 4 out of every 5 boot loops. I tried flashing OGJ, which failed to boot worse than OJ3. I just flashed OJ2, which seems to be more stable than the other flashes I tried, however I'm still getting sluggish performance, random reboots and crashes of background apps immediately after booting.
At this point I believe it is defective hardware and I should call in the warranty for a new phone.
Has anyone experienced similar issues? Any speculation on the source of the issue? What should I know going into attempting to exchange for a new phone?
Click to expand...
Click to collapse
OP here. Made a warranty claim, they seem to have replaced the motherboard as the solution. Complete repair experience from warranty claim to package back at my doorstep was less than two weeks, which is impressive for what I've heard about Samsung's support. Good luck!
Hello everyone,
I'm experiencing a pretty tough issue mith my beloved (and, so far, flawless) Nexus 6. It had root and a stock rom on it, 6.0.1 (MMB29V). I had unlocked the bootloader and rooted the phone right after buying it more than a year ago and I've been flashing new factory images a couple times (specifically when 6.0.0 and 6.0.1 were released). I usually do everything via Wugfresh's NRT, not because I can't use adb and fastboot, just because it works fine and I'm lazy.
Yesterday, while I was working, I used "Tiny Scanner Pro" to scan a document (legit copy bought on the store, as any other premium app in my phone) and it got stuck for a while, then a popup about Google Play Services came up. I dismissed it and another appeared, and it kept going like that. I was at a client's and I was in a hurry, so I took the pic with my tablet and forced the phone off. Later I turned it on, it seemed to boot regularly, but when the SIM unlock screen appeared and I entered the (right!) PIN, it said that no SIM was found, then the home screen appeared but after a while the screen went black and it started rebooting. Recovery (TWRP) and fastboot were working, so I decided to take it home and re-flash the stock rom: it had been a while since the last time anyway, a new version was out and the OTA update notification was getting annoying. I connected to my PC in recovery mode and transfered my pics and data via adb while I downloaded the latest stock rom (6.0.1 MOB30D). Then I user NRT to flash it (selecting "Soft-bricked/Bootloop" as current status). It appeared to work fine as it went through the usual copying and unpacking. Then, when the phone was supposed to reboot, it just blacked out. I waited a long time, in fact I went out and came back a few hours later, and it was still that way. Now it doesn't power up, no matter how long or hard I press any combination of the three buttons, adb and fastboot do not detect it in any way, of course, and it doesn't seem to charge either (i.e. I left it plugged to its original charger overnight and it still feels dead cold). By the way, the phone warranty shouldn't have expired, but I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
I've taken a look at similar threads but none of them describes the very same situation. Is there something, anything I can try to do before giving up? I hope somebody can help me. I thank you all very much in advance.
lupus
lupusyon said:
.... I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
Click to expand...
Click to collapse
Bricked!. When the phone is still under warranty send it for repair. Do not use arguments.
Just: phone will not switch on and does not charge.
Because this is a Nexus device, the custom recovery shouldn't affect your warranty. It is however, a moot point. The device is totally dead, and a call to Motorola is in order.
lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...
dahawthorne said:
lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...
Click to expand...
Click to collapse
I bought it on Amazon Italy Marketplace, I'm not sure if they're supposed to handle the thing or if I should contact Motorola. I'll just check with them first. Thank you everybody for the kind advice, I'll let you know how this turns out. :good:
I confirm what dahawthorne wrote above: it took them about a month but Motorola repaired my Nexus under warranty, no questions asked. It seems they replaced the Mainboard PCB.
Thanks everybody!
The title speaks for it self.
At the time of the original problem I was using...
OS: Android N Preview 5 (stock, rooted)
kernel: Elementalx 4.07 (default settings)
My N6 is about a year and a half old. It all started when I was punching an address in to google maps, and the screen goes dark out of the blue. No back light, nothing. Through process of elimination I am able to tell that the phone works, but the screen doesn't. Later on I'm in a phone conversation (was able to call using moto 360) and once the call is disconnected, the screen powers back up. Now everything is fine and dandy for about another week. The other day I am browsing and again out of no where the screen goes dark.
Failed troubleshooting attempts include:
Blindly rebooting into recovery and wiping cache/dalvik
Blindly rebooting into bootloader and re-flashing boot.img
Blindly doing a hard factory reset
Blindly re-flashing 6.0.1 (mob30w) and Elementalx 4.07
Disassembling phone and verifying connections on display assembly
I'm 90% sure I was able to correctly execute all the failed attempts above with a non-working screen - albeit it was not easy.
Any how, I'm still stuck. Someone help me
I have Project Fi so I almost NEED a nexus device. I ordered a 5x, but I'd hopefully like to return my N6 to it's working condition so I can return the 5x to the factory. I really wanted to use that money for one of the new nexuses (nexi?) when they come out in a month or so.
The one thing I stupidly didn't do was call motorola (whom I purchased the phone through) before dis-assembling the phone and I imagine voiding any sort of warranty claim I could take.
nioletmc said:
The title speaks for it self.
At the time of the original problem I was using...
OS: Android N Preview 5 (stock, rooted)
kernel: Elementalx 4.07 (default settings)
My N6 is about a year and a half old. It all started when I was punching an address in to google maps, and the screen goes dark out of the blue. No back light, nothing. Through process of elimination I am able to tell that the phone works, but the screen doesn't. Later on I'm in a phone conversation (was able to call using moto 360) and once the call is disconnected, the screen powers back up. Now everything is fine and dandy for about another week. The other day I am browsing and again out of no where the screen goes dark.
Failed troubleshooting attempts include:
Blindly rebooting into recovery and wiping cache/dalvik
Blindly rebooting into bootloader and re-flashing boot.img
Blindly doing a hard factory reset
Blindly re-flashing 6.0.1 (mob30w) and Elementalx 4.07
Disassembling phone and verifying connections on display assembly
I'm 90% sure I was able to correctly execute all the failed attempts above with a non-working screen - albeit it was not easy.
Any how, I'm still stuck. Someone help me
I have Project Fi so I almost NEED a nexus device. I ordered a 5x, but I'd hopefully like to return my N6 to it's working condition so I can return the 5x to the factory. I really wanted to use that money for one of the new nexuses (nexi?) when they come out in a month or so.
The one thing I stupidly didn't do was call motorola (whom I purchased the phone through) before dis-assembling the phone and I imagine voiding any sort of warranty claim I could take.
Click to expand...
Click to collapse
I have had the same problem quite a few times. I thought it was the layers that i had installed. I eventually had to reboot to recovery, clear cache and dalvik. Then the phone booted in to Android with screen active. I have now disabled my lock screen pattern. Hopefully that stops it.
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Before restarting, I'm confident the "ear sensor" that turns the screen off when I'm on a call as functioning. I'm also confident the auto-rotate functionality of the phone was working perfectly.
After I tried to factory reset the phone from the power-volume reset options, I actually ran into a TON of trouble trying to get the phone to properly reset. It tooks me countless tries to eventually get the phone to start after resetting it over and over again. I was stuck trying to get the phone to actually move through the setup steps. SUPER frustrating. I actually went to sleep while the phone was somewhere in the middle of setting up and when I woke up the phone somehow eventually made it through some setup steps.
I'm now using the phone as I normally would, but it's very odd. The phone is a LOT more unstable. At least 3 of the sensors I had working have just completely stopped working.
The phone is in otherwise perfect condition. I'm genuinely confused about how I should go about trying to resetting this thing to a pure stock configuration and slowly installing apps again to make the experience what I'd want.
And no, I'm not a super power user. I am a strong engineer happy to do crazy things like flashing bootloaders and whatnot, but I'm honestly confused about where to start. I understand other versions of this device may have had corrupted persist partitions during updates -- those problems seem like my problems -- but I don't know how I should go about simply flashing my phone at the lowest level into something stock that I can try to build back from.
And obviously when talking to google support their suggsetion is that I mail them the device and wait 10 days without a phone. I'm confused about how that could EVER be a reasonable way to get a phone repaired, sigh -- phones are not toys, they're pretty critical to the day-to-day work of so many people including myself. I'm pretty disappointing with that approach from Google and I had always considered them much better than that before this experience.
Anyway, I'm really lost and I'd love to understand how to repair the software on my phone.
(You all kick ass!)
aliljet said:
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Before restarting, I'm confident the "ear sensor" that turns the screen off when I'm on a call as functioning. I'm also confident the auto-rotate functionality of the phone was working perfectly.
After I tried to factory reset the phone from the power-volume reset options, I actually ran into a TON of trouble trying to get the phone to properly reset. It tooks me countless tries to eventually get the phone to start after resetting it over and over again. I was stuck trying to get the phone to actually move through the setup steps. SUPER frustrating. I actually went to sleep while the phone was somewhere in the middle of setting up and when I woke up the phone somehow eventually made it through some setup steps.
I'm now using the phone as I normally would, but it's very odd. The phone is a LOT more unstable. At least 3 of the sensors I had working have just completely stopped working.
The phone is in otherwise perfect condition. I'm genuinely confused about how I should go about trying to resetting this thing to a pure stock configuration and slowly installing apps again to make the experience what I'd want.
And no, I'm not a super power user. I am a strong engineer happy to do crazy things like flashing bootloaders and whatnot, but I'm honestly confused about where to start. I understand other versions of this device may have had corrupted persist partitions during updates -- those problems seem like my problems -- but I don't know how I should go about simply flashing my phone at the lowest level into something stock that I can try to build back from.
And obviously when talking to google support their suggsetion is that I mail them the device and wait 10 days without a phone. I'm confused about how that could EVER be a reasonable way to get a phone repaired, sigh -- phones are not toys, they're pretty critical to the day-to-day work of so many people including myself. I'm pretty disappointing with that approach from Google and I had always considered them much better than that before this experience.
Anyway, I'm really lost and I'd love to understand how to repair the software on my phone.
(You all kick ass!)
Click to expand...
Click to collapse
I would try flashing the latest factory image via fastboot.
[Guide] Root Pixel 4 XL with Magisk Android 13
[Guide] Root Pixel 4 XL With Magisk Android 13 Android Security Bulletin—Feburary 2023 Pixel Update Bulletin—Feburary 2023 Introduction This Guide is for Pixel 4 XL owners that want to Root their phone, and enjoy the benefits of rooting it. The...
forum.xda-developers.com
https://forum.xda-developers.com/t/guide-unlock-flash-root-for-the-pixel-2-xl-taimen.3702418/ (This is for a Pixel 2 XL but the process is the same. It's basically a condensed version of the one above.)
aliljet said:
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Click to expand...
Click to collapse
You did not provide the most important information we need- whether your phone is bootloader unlocked. Probably not, otherwise you would have already flashed it with a full Google image, which returns the phone to "out of the box" condition. You need to determine whether you can unlock your bootloader. If you cannot unlock (allow oem unlock is off and or greyed out in Dev options) then you will not be able to fastboot flash ANYTHING. If that is your case, the next best thing is flashing a full OTA image (sometimes called a rescue OTA) from recovery mode using the OTA via ADB option. This means you need fastboot/adb installed and working on your PC. Instructions on how are on the same Google dev page for OTA's.
So, my phone's bootloader is not unlocked. But I have an update for the crowd that may one day find this. I know your frustration and I can report that my phone is once again fixed.
A day (or two) after I sent this, a set of updates came down to my phone. And WebView was updated. That restored all of my sensors and also restored most of my crashing applications. It was an incredibly odd experience.
My phone once again functions. And the nightmare of owning a Google phone and talking to Google support has ended.