Database Develop

Replacement N1 defective?

My original N1 had a display problem, so I sent it in and HTC replaced it. I got the replacement back today.. and it's rebooting at random. I updated to Froyo FRF91 (it was running some 2.1 version), and I wasn't paying close attention. I think it might have rebooted mid flash, and is now sitting at the boot logo, and was there for ~10 minutes.
Eventually I pulled the battery, and now I can't even get into recovery to try to re-flash. It just hangs on the Nexus logo.
What should I do?
Edit: On the phone with Google support, forwarding me to HTC for another replacement.
Edit 2: It seems my phone can boot, but only when it has no SIM. It still seems to randomly reboot. Is it possible my radio is messed up? It seems to reboot when I try to do anything that involves the cell radio. Any hope for repairing this myself?

Bump for edit 2. Still looking for help.

I had the same exact thing happen to me. Since the replacement phone didn't work (hard reset, stock) either HTC told me it might be the battery, and it would take two weeks to get one. I ordered one next day and the same exact thing happens. I'm sending back the replacement phone now, in order to get another "replacement". Crazy.

G4 Boot Loop

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.

Won't turn on or charge after flash fail

So I've had a sprint variant of the LG G4 for a couple of weeks now, but a couple of days ago I started working on it because of all the problems it's given me. First off, I live in the Dominican Republic so I contacted Sprint to unlock the phone internationally because it belonged to my sister and she used it on sprint (but then switched to t-mobile after she sent me the phone). They helped me out but I was unable to receive calls and when I made calls I couldn't hang up even though the end call button could be pressed. I investigated a bit and found a thread that was supposed to fix that problem. But in order to do any of the steps I had to root the phone first. I tried to root it but the phone gave me an autentication error #11. I investigated about that and read that I should stock flash the phone. I tried that using TOT zv5 (and had previously read to not do that if I was zv6 or above, and with the LG Mobile Support Tool saw that my phone was zv4). The LG Flash Tool said that the flash failed. Since the screen on the phone was off after it failed I tried to turn it on and nothing happened. I pulled the battery a couple of times and nothing. I connected the phone to the wall with and without the battery and nothing. Can I assume that the phone is fried or something?

josetj34 said:
So I've had a sprint variant of the LG G4 for a couple of weeks now, but a couple of days ago I started working on it because of all the problems it's given me. First off, I live in the Dominican Republic so I contacted Sprint to unlock the phone internationally because it belonged to my sister and she used it on sprint (but then switched to t-mobile after she sent me the phone). They helped me out but I was unable to receive calls and when I made calls I couldn't hang up even though the end call button could be pressed. I investigated a bit and found a thread that was supposed to fix that problem. But in order to do any of the steps I had to root the phone first. I tried to root it but the phone gave me an autentication error #11. I investigated about that and read that I should stock flash the phone. I tried that using TOT zv5 (and had previously read to not do that if I was zv6 or above, and with the LG Mobile Support Tool saw that my phone was zv4). The LG Flash Tool said that the flash failed. Since the screen on the phone was off after it failed I tried to turn it on and nothing happened. I pulled the battery a couple of times and nothing. I connected the phone to the wall with and without the battery and nothing. Can I assume that the phone is fried or something?
Click to expand...
Click to collapse
same here man, after try like 10 times to restore my g4 using ZV6 tot I had no luck, I get frustrated and install ZV5:silly: after that my phone did not turn on anymore either in download mode, I still have not found anythig

manuelperro said:
same here man, after try like 10 times to restore my g4 using ZV6 tot I had no luck, I get frustrated and install ZV5:silly: after that my phone did not turn on anymore either in download mode, I still have not found anythig
Click to expand...
Click to collapse
Same exact thing just happened to me

Nexus 6 (rooted, stock rom) won't turn on anymore. Please help

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!

3T freezes/reboots on setup

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.