yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Q&A, Help & Troubleshooting] kerman19:
Just a note to add to this one.

My phone was on charge and it reported 100%, I went out and around an hour after taking it off charge it was on 94% and just turned off. Wouldn't do **** all.

Once I got home it took about 3 hours on the charger before it'd decide to boot up.

It would appear even though I'm using the stock charger the phone at some point thought it was fully charged and wasn't, why? No idea myself, but it freaked me out a little bit and highlights that the battery monitoring on this phone is somewhat inaccurate.

I've never managed to drain the last 15% of my phone, it always hits 15% and then a few minutes later hits 2% and says piss off.

Also, my phone is completely stock, minus an unlocked bootloader so I don't have to wipe when I do decide to start tweaking.

Phil
[Nexus 4 Q&A, Help & Troubleshooting] ntt1409:
Have you received the tracking # for your replacement abnormalreply?
[Nexus 4 Q&A, Help & Troubleshooting] djkinetic:
I dont think you phone was bricked, do this hold down volume down and power till you see the bootloader then volume up till it says restart recovery, boot into recovery, wipe cache then dalvik cache, redownload faux kernel from his site, then reboot into bootloader, flash new kernel with fastboot, reboot and you should get into Android, I had the same issue with the red light after flashing his new kernel, this fixed it.
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
Not yet. I placed the order on Saturday, so technically, today is the first business day in the 5 day window.

As I mentioned before, I can only get into the bootloader and nothing else. Anything else causes a bootloop. It is more evident that the battery is defective on the devices that are having this problem.
[Nexus 4 Q&A, Help & Troubleshooting] djkinetic:
did you try to reflash CWM or TWRP? then booting into recovery again...something might have gotten corrupted.
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
Please read the OP. This isn't a software problem.
[Nexus 4 Q&A, Help & Troubleshooting] djkinetic:
I find it hard to believe, that its a hardware issue, that cropped up just after you flashed a kernel...You would think if it was a hardware issue that your phone would exhibit some kind of symptom while it was still on stock before you flashed the kernel, i.e. you turn it on and it turns right back off, or bootloops on the charger, this should have happened to you long before you flashed the kernel, one would logically deduce, but I guess stranger things have happened. Either way good luck on your replacement.
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
What other explanation could there be that explains why the phone doesn't even turn on without the charger and when it does and I pull the charger out, it shuts off? The only reasonable assumption is that the battery isn't functioning, because I know it's charged. There are other people in this thread who reported the same exact thing--people who didn't flash any software; only unlock + root. I was using the kernel for a day before it happened. I think it's just a coincidence that it happened when I tried to OC + antutu.

I don't see how there could've been any initial symptoms. Either electricity flows or it does not.
[Nexus 4 Q&A, Help & Troubleshooting] djkinetic:
Guess you were just unlucky =/
[Nexus 4 Q&A, Help & Troubleshooting] spadie:
me too :S

http://xdaforums.com/showthread.php?t=2008222&page=28
[Nexus 4 Q&A, Help & Troubleshooting] Prod1702:
Goodluck with the exchange man. Hopefully this doesn't become a known problem and most of the people with N4's start to have this happen to them.
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
Sorry to hear that, man. People don't seem to want to accept that this is an unusual amount of failures so early after a device's release. I hope the newer batch for the limbo 3 folks are better built.
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
We'll definitely know more in about two-three weeks or so after the backordered people get theirs.
[Nexus 4 Q&A, Help & Troubleshooting] wera750:
Got me too. I had just flashed faux kernel and ran quadrant. Happened 3 days ago...
[Nexus 4 Q&A, Help & Troubleshooting] bhazard451:
I was able to fix mine.

I also crashed during the new Antutu today, while OC'ed. I had thought I had 20% battery while doing this. It turns out, it was actually at 0. The battery stats are off and not accurate. Huge bug.

The phone would not turn on at all. Plugging it into the wall would bring up the red led, but would not bring up the charging icon. I still could not boot or get into recovery.

Either by sheer coincidence, or the fact that I had previously charged a bit through the wall, I plugged my charger into my PC, and the charging icon came up. It also was visible to the PC. I was happy I didn't have a complete brick. Both recovery and normal booting worked while plugged in. I let it charge a bit, and all is well.

If you are not able to charge, try to use as many different cables as you can, regardless if they work on other phones or not. Give it about 5 minutes, and try using a PC (not a wall jack) to provide power.
[Nexus 4 Q&A, Help & Troubleshooting] wera750:
mine was at 80% when it went down with the red led of death, left it on the wall charger for 8 hours and still nothing
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
Were you in the exact same situation as I described in this thread? i.e. not getting a voltage output with "fastboot getvar battery-voltage"? Because this is the reason why I'm not booting up beyond the Google logo when plugged in the wall or PC.
[Nexus 4 Q&A, Help & Troubleshooting] kerman19:
Talk about shoddy battery stats.

Plugged my phone in this morning, but I had to rush out so it was only on charge for about 10 minutes... it was on 14% when I put it on charge, 100% when I took it off, by the time I got to work (20 minutes) it was dead, completely dead.

It's now been on charge for about just over 4 hours and has finally booted up, with 4%, and gradually charging.

Second time this has happened now.

Phil
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
This is identical to some of the initial issues I had before complete shutdown :/
[Nexus 4 Q&A, Help & Troubleshooting] USSENTERNCC1701E:
Uh, oh. No, my battery cannot have fully charged that fast. Le sigh

By the way, this is completely stock, not rooted, not unlocked. I have adb debugging enabled so I could take the screen shot. I restocked and locked after my touchscreen developed a non-responsive section, while I wait to be able to get it replaced.
[Nexus 4 Q&A, Help & Troubleshooting] MusicMan374:
I don't see why you guys feel the need to overclock a 1.5 GHz quad-core processor. Of course you run the risk of frying circuitry doing that. I think the only people that have had the batteries completely go out on them have been the ones overclocking. It's possible that it is a defect, but this phone is already more powerful than half of the budget computers being sold on the market today, why push it further if you're running the risk of literally frying the motherboard? :confused:
[Nexus 4 Q&A, Help & Troubleshooting] tweaked:
Because they can..
[Nexus 4 Q&A, Help & Troubleshooting] heat361:
One does not just brick a nexus :silly:
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
I'll go ahead and assume you didn't actually read the thread or even the OP, which leaves me to question: why are you posting here?
[Nexus 4 Q&A, Help & Troubleshooting] joshyy_rey:
Butt hurt much? He asked a question. Answer it if you like. But going off about your thesis of an OP is ridiculous. Because in your OP you stated you OC'd... Battery issue aside. He asked why you felt the need to OC...
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
Why do devs add OC capability to kernels?
[Nexus 4 Q&A, Help & Troubleshooting] joshyy_rey:
Because people beg and whine if it's not there....It's only truly useful when a device gets old as balls. I OC my vibrant but thats because it's single core and 2 1/2 years old....
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
Devs choose to add OC because they simple CAN. They're not obligated to add jack *** despite anyone's "whining." Whether a user chooses to use that OC because THEY can, it's just a personal choice/preference which may be for the sake of testing, or out just out curiosity. Whatever reason someone has to do it, that's their choice. I didn't make this thread complaining in regret of what I did or blaming the kernel or ROM I used. I made it, more or less, to report a finding and to find out whether or not it was truly screwed up and why exactly--which, if you took the time to carefully review, resulted in many people reporting the same issue even without OC. and this might very well lead to a more cautious outlook by other users or even garner more attention to something that might be a severe defect in the device. Or it may just be a few bad ones. who knows
[Nexus 4 Q&A, Help & Troubleshooting] Luxferro:
From what's been posted about this battery issue so far, it seems like a software/firmware type of issue. Not that the physical battery died, but that the phone thinks it's dead or at 0% or whatever is the threshold for preventing it from booting. I'm sure messing around with kernel's and OCing is one cause of making it glitch out.

I've personally OCed all of my phones at one time or another, except my N4. I usually go back to stock clocks after playing around for a bit. But I don't feel the need to on my N4. Maybe I'm just getting old, or I appreciate the piece of mind of leaving well enough alone now a days. I haven't even put a custom ROM on it yet because I want to have a nice baseline for knowing how my phone is on stock :o
[Nexus 4 Q&A, Help & Troubleshooting] emuneee:
As I posted in two other threads, I am having the same issue. My Nexus 4 is stocked besides the unlocked bootloader. My Nexus 4 did exhibit the behavior described hear though before I even unlocked it. I already ordered an RMA. Just have to get this thing charged up enough to relock for the RMA. Sucks. First experience with a sealed battery... :-/
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
If it doesn't get charged up (like mine), you can still get into the bootloader while it's plugged in the computer. You just have to time it right. Once you're in the bootloader, you can easily flash back to stock / re-lock.
[Nexus 4 Q&A, Help & Troubleshooting] emuneee:
My Nexus 4 sat in the box all night because I thought it was toast.. It turned on by itself. I randomly opened the box and saw it was on. It has been perfect all day! This is amazing. I still have an RMA that was shipped. But at least I have something to play with for the weekend.

I'm still shocked how it goes from a brick to a fully functional device by itself.

---------- Post added at 08:43 PM ---------- Previous post was at 08:13 PM ----------

Spoke to soon. Lol back to my GNex until the RMA arrives.
[Nexus 4 Q&A, Help & Troubleshooting] Bwlian:
You get to keep the defect N4? How did you prove to them it was broken?
[Nexus 4 Q&A, Help & Troubleshooting] THE_KINGDOM:
Keep until replacement arrives, then send out.
[Nexus 4 Q&A, Help & Troubleshooting] sassafras_:
to OP-

Have you even confirmed that the fastboot getvar command actually outputs a value on a normal phone? I checked on mine and I get no value either, though my phone works fine and is untampered with running a locked bootloader.

I don't want to jump to conclusions about how this came to happen to your phone, but I'm not yet convinced you didn't bring this upon yourself.

sassafras
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
Normal phones returned a voltage with the command. People with the same bricks after only unlocking the bootloader were not able to return a voltage. Ever since my incident, I've seen reports of at least 5 other people reporting similar symptoms, most of whom have not done anything to the phone.
[Nexus 4 Q&A, Help & Troubleshooting] USSENTERNCC1701E:
Mine does not return a voltage. And once I've had the phone immediately report a full charge from like 70% to 100% in seconds. Other than that I've no had battery issues.
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
I experienced similar things shortly before it crashed completely. It was going from >90% down to 2% within seconds and charging from 15% to 90% in a few seconds--as if the battery's contacts were loose or something and resulting in the phone not 'knowing' what the present capacity was. I can't be too optimistic about your situation, but I hope it doesn't become a major problem like mine did.
[Nexus 4 Q&A, Help & Troubleshooting] sassafras_:
So my phone is not normal? It does not return a voltage. Who else with normal phones has reported their phone returning a value?

sassafras
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
Look, I'm just telling you what I've found out from others, and relaying on their experiences so maybe you can get a better handle on your own device on whether it will fail or not. I have no obligation to try to help you, nor are you obligated to place any consideration on anything I say. No need to be an a** about it.
[Nexus 4 Q&A, Help & Troubleshooting] sassafras_:
Fair enough. No need to be defensive. Maybe it's not clear, but I'm trying to tell you that I don't think that command ever returns a value, even on non-defective units. Doesn't that help you? If it were me, I would want to be sure that this fastboot command actually works before I start assuming this must be the root cause of your device failure.

What if you get a new device, try the command, get no value and assume your replacement is faulty too?

sassafras
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
I haven't implied in any way that I didn't confirm that this wasn't the case with unaffected devices. Here's a post in this very thread from the user who led me to confirm the defect. I don't see why you would think this command shouldn't return a value. It is a fastboot command, and where else could you run it but in the bootloader? If I'm completely missing something here, I'm very open to other explanations (though I don't have the device anymore.)
[Nexus 4 Q&A, Help & Troubleshooting] ragiut1:
@OP

I managed to recover from the same situation, check my thread

http://xdaforums.com/showthread.php?t=2021919

It's too simple but it might work for you
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
This is interesting. I did try download mode while plugged into the PC, but it didn't occur to me to leave it there all night. I no longer have the device to try this though. Thanks for the helpful post!
[Nexus 4 Q&A, Help & Troubleshooting] marty331:
OP,

I hate to be a total ****, but I'm going to be.

If you are using a toolkit to flash things on a Nexus, you don't know what the hell you are doing and should stay stock until you understand.

If you are using a windows machine, that's problem number one. You should only work on Android devices using Linux. Start there.

Your phone is not bricked, it's just pissed at you for mistreating it.
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
Way to make the post ignorant post in the entire thread.
[Nexus 4 Q&A, Help & Troubleshooting] CMNein:
I wouldn't go that far. ADB and fastboot have never given me issues on a Windows machine.

That said, the only reason I'm not running Linux is because no one else in my family would appreciate it, and I won't install it on my work cpu until I get a new one :crying:
[Nexus 4 Q&A, Help & Troubleshooting] marty331:
Prove my comments wrong.
[Nexus 4 Q&A, Help & Troubleshooting] USSENTERNCC1701E:
No. Nearly anything you need to do to the device itself can be accomplished from a Windows PC. The one major advantage I've seen to working the device itself through Linux is that it recognizes and can interface with the device quicker (difference is on the order of seconds), and if you need that you are already in sketchy territory. There are also some proprietary tools I've seen that have no Windows counterpart. But if you look through XDA there are more Windows only tools released by devs than Linux only.

If you are building for Android a case could be made that you're better off using Linux, and if you are compiling Android itself you are definitely better off in Linux.
[Nexus 4 Q&A, Help & Troubleshooting] Roxy:
LOL seriously?

I don't use a toolkit ( ever ), but " You should only work on Android devices using Linux " = roll eye. :rolleyes:
[Nexus 4 Q&A, Help & Troubleshooting] Impulse33:
So the flashing red light happened to me. My phone was rooted with busybox and twrp, but no custom rom since none of them have appealed to me so far. Before i return the phone for rma is flahing the rom stock necessary? Also, before unrooting it and locking the bootloader how do i get rid of twrp/busybox?
[Nexus 4 Q&A, Help & Troubleshooting] zephiK:
your bootloader has to be LOCKED. if it is UNLOCKED, your warranty is voided. so yes you have to RELOCK the phone before sending it back in.

although I feel that you sending your phone back in as a "RMA" is a fraud because it was you who messed it up, not because of LG or Google meaning you're going to cost them money.

PLEASE PLEASE dont use a toolkit.... it just brings way too many problems and taking shortcuts when you dont know what is going on is just bad
[Nexus 4 Q&A, Help & Troubleshooting] Impulse33:
I dont see how simply rooting would cause this issue (the battery disconnect). The phone overheated while playing nfs most wanted and shut off, then the issue started. This makes me believe it is a manufacturing defect.
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
Flash the stock image back onto the phone then re-lock then bootloader. Use the toolkit if you need to.

Did you even read the OP of this thread? Or even skimmed it to see how many people are reporting the same issue? I'm gonna go ahead a assume not. It's ignorance like this, that, when propagated, we can get nothing resolved properly. It's not a fraud at all. I had the exact same issue and I'm doing the same things with my replacement now that I did with the first N4 and this one is working like a champ. Some people are legitimately getting defective hardware, and people like you, spewing nonsense without being properly informed about the issue aren't helping at all.

Do you have any sources / reports of the toolkit actually causing "too many problems?" It's there and it's stickied for a reason: it's simple and it works.

That said, even if someone does use the toolkit, it would be wise to know what it is actually doing even if you're not actually typing out the commands.
[Nexus 4 Q&A, Help & Troubleshooting] zephiK:
Uh.. Sources of toolkits causing problems? Tons. People are getting into things they don't understand the basic idea of adb or fast boot. So when their phones are screwed, they don't know how to fix it.

http://xdaforums.com/showthread.php?t=1469909

49 page thread. So yes tool kits do cause problems. It's easy but the basic fundamentals of flashing a basic custom recovery won't be learned because a toolkit does it for them.

Oh phone won't boot? What do I do? Post on xda for someone to help me. When I started android I had to root via adb and terminal emulator on my G1. You had to work for root access.

It is imperative that people understand adb and fast boot before getting into flashing roms and then wondering why their phone won't start and then say that their phone bricked or whatever it may be.

Toolkits do More harm than good.

Next time you should really look into what you're saying before quoting me since I've been around xda for quite some time with helping the community in various ways.

It is very easy to blame it on LG or Google for a users mess up. Regardless of what it may be, they were warned on unlocking the bootloader. This is why people (mainly amaeteurs) to use the phone as stock for 2-3 days to make sure that their phone has no defects or whatever then proceed to tinker with their phone. But at least unlock the device beforehand to keep the data.

There has been many people who claim insurance fraud with their phone insurance. Not saying that there aren't legitimate problems but if a problem started occur, it's very easy to lie about it and blame it as a defect and act like you don't know what happened.
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
You completely missed the point of my post. The toolkit itself does not cause problems. It's the user's lack of understanding of how it works that can cause problems. That, we're in agreement on. I'm sure hundreds, if not thousands of people use toolkits all the time without a hitch, because they actually understand how it works. So, don't encourage folks to not use the toolkit, encourage them to learn what it does.

And being on XDA for "quite some time" doesn't mean you can say whatever you want and it will magically be factual. Nor is time spent on XDA some kind of universal qualification of being knowledgeable. There are a few other forums on the internet, last I checked.
[Nexus 4 Q&A, Help & Troubleshooting] vipero07:
Clarification

So I've been flashing custom roms since the G1. I would like to clarify this red light issue. I am currently experiencing it (hoping that my phone suddenly starts working later tonight / tomorrow). If not I

will

RMA it. And for those of you who are butt hurt you do not have an N4 and keep posting in here saying the people who this has happened to are morons, I assure you that is not the case. If it is a software thing, it should be recoverable (it doesn't seem to be minus waiting it out). I have done everything in my power to attempt to recover from this issue.

fastboot erase boot

fastboot erase cache

fastboot erase recovery

fastboot erase system

fastboot erase userdata

and then fastboot installing the factory image from developer.google.com to no avail. I have attempted flashing and/or booting to the two most common recovery images through fastboot (TWRP and CWM) as well as the stock recovery, again to no avail. I only have access to bootloader and that odd LG Download Mode, which is any ones guess what it is actually doing. Additionally to give an idea of what caused this issue for me, I was in the middle of a nandroid

backup

. I had no custom firmware on the device, no custom kernel, the only things I did to the device were fastboot oem unlock and the usual root method. Followed by nandroid backup. All I was attempting to do was get a backup of my device should anything occur to it.

Again not going to over clock or under clock or anything "sinister" the device ran perfectly until the moment it stopped booting normally gave me the red light boot loop and who knows what it means. The lack of any help from anyone including Google or LG the lack of useful comments in regards to this issue, and the continuous "you are an idiot" posts from people who clearly have no clue what they are talking about are extremely unhelpful. If anyone has found any actual useful information besides wait it out (which I am going to attempt to do because I don't think its fair to RMA unless absolutely necessary). I will post any further information or attempts. But I've been looking into this issue for a few hours, and still have no absolute solution.

As of this moment, although this device is a Nexus and is INTENDED for developers, I will be extremely hesitant to even root it again should I RMA. Which is extremely upsetting to say the least, as part of the reason I purchased a Nexus was to have the ability to work on development on it. Too bad the stock kernel could use so much tweaking to improve battery life its ridiculous, and too bad this type of issue I'm sure has turned many developers away from it.