yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
Yeah, not the first time I'm doing this either. I've had many other Android phones in the past. This is just strange.
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
Thanks for responding.

I've tried everything you suggested. I have in no way indicated that I don't know how to use adb/fastboot. I was able to flash the google image and re-lock the bootloader, but the problem persists.
[Nexus 4 Q&A, Help & Troubleshooting] ntt1409:
i flash new roms and kernels on my n7 thousand time but nothing goes wrong. I am only able to access bootloader for 2s but thats enough for me to relock bootloader and send it back to GG :D
[Nexus 4 Q&A, Help & Troubleshooting] enserio:
In all fairness, I don't think I've felt the need to OC since the sensation. The GNex was perfectly fine as is, and this thing is certainly quick and smooth out of the box - so to push it to its limits sounds a little playing with fire.

I wanna say I had an issue on the Sensation or the Vision very similar to this, where the phone was only recognized in adb for a couple of seconds, but once I got it into fastboot, it stayed connected.

Either way, lesson learned.
[Nexus 4 Q&A, Help & Troubleshooting] AIovanna:
To put it simple...both of you have literally fried your phone...this is a hardware problem....not smart...goodluck though...hopefully those who buy/bought the phone get theirs before your replacements...
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
Is there a way to clear the battery stats or delete batterystats.bin from fastboot?
[Nexus 4 Q&A, Help & Troubleshooting] v-haker:
But why do you need this? This file is the stats only, so it doesn't affect the battery
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
Because the phone was fully charged before all this nonsense began and now it's indicating that it isn't charged. So it might be helpful to delete the battery stats. Just an idea. I doubt it might work since I flashed the google stock image, that should've deleted it.
[Nexus 4 Q&A, Help & Troubleshooting] v-haker:
This file doesn't contain battery percentage. Maybe you need to disassemble your nexus and plug out/in the battery
[Nexus 4 Q&A, Help & Troubleshooting] pyroemaniac:
It would appear that you are the one being an "internet tough guy" callong people dorks and what not :rolleyes:

As for flashing a stated test kernel and bricking your phone, well you've only got yourself to blame. They have those test kernels for testing. They arent there for you to get "super" high benchmark scores to brag about online.

All in all if you dont know how to kernel trouble shoot then dont install a test kernel and then talk down to people who think its funny ;)
[Nexus 4 Q&A, Help & Troubleshooting] zelendel:
OK guys calm down. There is no reason for all this school yard behavior.

Now as for why a kernel would be released that could do this. Welcome to a development site. You accept all risks of what you do and know fully that using anything here could brick your device.

Sent from Arkham
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
Of course. I don't blame the kernel at all. This comes with the territory of wanting to test/experiment with beta kernels. Anyways, I've exhausted all my efforts. I don't see what else can be done that would have more of a restorative effect than going back completely to stock and re-locking the bootloader. That said, Google will be sending me a new device in a few days.

Thank you to everyone who tried to help.
[Nexus 4 Q&A, Help & Troubleshooting] Alex240188:
OffTopic:

WOW, this thread just like most of the others in the N4 sections is full of SH!T

If you dont have the phone yet and want to bash the OP or do not wish to post something constructive and relevent to the OP's statement. Just keep it to yourself, this is not the place for mindless bashing

OnTopic

I would most likely say you have done some Hardware damage here

Overclocking

just raising the clock speeds will not cause any of the damage you are describing (contrary to what others are saying), but there are many things that are related to it that probably have

If the Thermal Throttle Values have not been tampered with, then raising the clock speeds just means its going to get to the thermal throttle point quicker as "Higher Clock Speed = Higher Heat Production"

I'm not sure where the themal config file is (either rom / kernel) but if that has been altered to a higher value then your phone has possibly overheated and caused damage.

If it has not been touched then your phone is not going to have gotten any hotter than it normally would have

OverVolting

what i would say the most likely cause is, is the voltage. you may want to check this with faux

as any Overlclocker will know. in order to be stable at high OC's you usually have to tinker the voltages to the CPU

now as you raise your Core speed (MHZ) you will be increasing the Voltage (MV) to the CPU.

If when above 1.5Ghz this voltage is anything above stock then it could be as simple as that. you have a (unique) CPU that was pretty much already at the limit of what it can handle. it got some more voltage pumped through it and fried something.

i believe that it is this that has caused your damage based on the fact that, after the bootup, you will probably not have used any CPU states above 1.5GHz, then when you run Antutu, CPU ramps up to max, and as such the voltage for the higher clock speeds is set and BAM

DOWNLOAD MODE

i would liken this to my current device (HTC ONE X)

on the HTC One X, everything is done through Fastboot or Recovery, just like the Nexus 4

however should you Brick a HTC One X it will instead flash a red light and only boot into APX Mode for use with NVFlash

APX mode been pretty much like ODIN for samsung and Download Mode on N4 (except we dont have any secure keys so we cant do anything in APX yet)

I have commented in the Nexus 7 (2ndary device) in relation to "SPECIAL" people who have ran commands like "fastboot erase bootloader" DO NOT TRY THIS COMMAND and "adb shell rm /dev/block/mmcblk0" DO NOT TRY THIS COMMAND and ended up without a bootloader (fastboot). This also forces them into APX Mode

meaning, if it pushes you to APX mode, you are not capable of loading the bootloader

if you cant get to the bootloader then either something is wrong with your nand memory, or something is broken with the device

i would suggest that been forced into Download Mode means you have severe damage to your device that is preventing from being able to boot the first thing the phone loads when turned on
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
Thank you for the VERY informative post. I can get into the bootloader though (and download mode.) I flashed the stock image using the toolkit while in the bootloader. Also, I'm not sure if I mentioned it before but nothing happens if the charger isn't plugged in--it is completely dead, no button combination for any length of time--nothing. And I'm certain that the battery is fully charged, as it was >90% before all this started. Only when the charger is plugged in I'm able to go into the bootloader or download mode (not recovery.)

EDIT: Also, when I'm in the bootloader and I unplug the charger, it shuts off--as if the battery isn't supplying power to the motherboard at all.
[Nexus 4 Q&A, Help & Troubleshooting] undercover:
Your try is appreciated but has nothing to do with the issue. Battery stats are for the graphs you see when you click on battery in settings, ie what consumed battery for what and for how long (like screen on time). It has nothing to do with reported percentage.

Just to educate other people and make sure that they don't go back to that myth...
[Nexus 4 Q&A, Help & Troubleshooting] Alex240188:
to look at it constructively many will say that it probably has something to do with what you have done to it. (you probably know this aswell)

sinse you have flashed stock now, can you boot into android (while its still plugged in)

if not you could try running a command from fastboot like "fastboot getvar battery-voltage" to see if your device is still able to communicate with the circuitry for the battery. and if it works to give you some idea what actual charge it has in it)

in all odds its looking very much like you have a hardware failure and i hope you get sorted with a replacement soon
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
I cannot boot into android even with stock. I received no output for that command either.
[Nexus 4 Q&A, Help & Troubleshooting] Alex240188:
well it points to where your issue is then. clearly something has either fried or disconnected between the CPU and battery

by comparrison, you should get something like

C:\Users\Alex>fastboot getvar battery-voltage
battery-voltage: 3800mV
finished. total time: 0.218s

meaning either your battery has come loose and is not been detected at all, or the circuitry that talks to the battery is dead
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
Seems so. I wouldn't think this ought to be a problem with phones these days--that software can cause such serious hardware damages. Surely there ought to be safety measures implemented to prevent dangerous increases in voltages.I don't think I was doing anything very unreasonable when it comes to XDA standards. The kernel actually maxes out at 1.8+. I only went to 1.6. You'd think 100Mhz OC wouldn't have such devastating effects. What's even more interesting is that I'm not the only person who's had this very problem with the N4. I certainly hope it's not a problem with the N4 design itself, but it's difficult for me to think otherwise. Anyways, thank you for your help. I'll hit the thanks button once my daily limit is refreshed.
[Nexus 4 Q&A, Help & Troubleshooting] shadymouse:
Not to be an asshole or anything... But why would you even "overclock" to 1.6 GHz from 1.5??!! I can't fathom the benefit one will get from such a measly overclock. To each is own. Hopefully, you get this sorted, in fact, Hopefully WE (XDA) can get this issue sorted for our precious devices.
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
Because it's foolish and reckless to jump to the maximum OC in any kernel. Obviously you're new to this. Just because a kernel supports overclocking to a certain speed, doesn't necessarily mean the ROM will be completely stable at any speed. The proper way to do it is increment up until you start seeing minor issues like frequent force closes, or random reboots, then clock down to the last stable speed.
[Nexus 4 Q&A, Help & Troubleshooting] Alex240188:
No i agree with you 100% here, i would think that a kernel dev is not really going to drasticly mess with voltages.

And that you would find instability, in the form of crashes and reboots rather than damaged hardware.

Could be something simple as a bit of bad wiring inside. not enough to cause any problems but with OC & benchmark its pulling more current and caused heat buildup at weak point and its burnt a cable
[Nexus 4 Q&A, Help & Troubleshooting] decepticon:
There are safeguards in place to prevent that from happening and by flashing another kernel, you removed such safeguards.
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
Of course, but is it unreasonable on XDA to OC 100Mhz? I am by no means omitting my own responsibility for my actions, but I do think there is something to be said about the design of the phone itself. The manufacturer stated clock speed for most phones is almost always well below the potential of the processor itself. This is why it is relatively safe (for the most part) to overclock our phones, and why we do it here. and for a phone that's supposed to be Google's "flagship" device should, in my opinion, be a little more resilient to stress. Is the sub-par build quality of the N4 really that much of a secret? Considering the known inclination of the device to overheat and have insane thermal throttle, I think it's safe to concede that it's not a device that's meant to be stressed. But honestly, how many people on XDA would object to a 100Mhz overclock? I'll have to go a few days without a phone till my replacement gets here and that doesn't really bother me. I'm not lashing out at the N4, I'm just saying we should all be a little bit more cautious than usual when it comes to using custom kernels with this phone in particular. Personally, I don't see myself ever trying to OC this phone again.
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
This would be one of those situations where, if you have no idea what you're talking about or you're emotionally distraught because Santa Clause didn't bring your toy early this year, crying about it doesn't make it come faster, and you really shouldn't add your useless dribble to the thread. XDA is a community which explores the limits of our software and hardware which helps us use them to their full potential. So instead of whining about not having your phones, maybe you should be interested in learning about something that may affect your device when you get it.

I wouldn't say it's the combo that did it. Just overclocking hardware that was fairly weak to begin with. But if you must know: I was running AOKP + the Faux kernel (overclocked to 1.6MHz and tried running Antutu.) If you use the same kernel and not overclock, you should be alright.
[Nexus 4 Q&A, Help & Troubleshooting] shadymouse:
New to overclocking??!! Slow down there buddy LOL. I've been in the game for a very long time. What I meant, there was no point in even trying out an overclock. This is the best phone on the market right now, specs wise. What exactly were you trying to accomplish by running a higher clock when no app in the play store can even scratch the surface of a 1.5 GHz x4?? You already had the custom ROM, did you need to bump up the clock? Was the phone lagging prior? Was the phone taking long to load and/or multitask apps? Those should be the MAIN questions one should ask him/herself before they start tinkering. Seriously, how much faster do you want your phone to go...
[Nexus 4 Q&A, Help & Troubleshooting] Slappy00:
New-schoolers really just want to put a pic in their sig showing : "Nexus 4 @ 1.7ghz (stable)"

But really there's no need to OC other than e-peen in my opinion. This isn't a celeron 350 to 550 where you almost double the performance or a shader unlock for a Radeon card. The difference from 1.5 to 1.7 is (drumroll) ~12%, and that's assuming you even get that far. And what will that performance give you? A faster phone call or text message? The phone is butter smooth so I'm not sure what folks want to accomplish unless they are compiling binaries on their phone.

I would

never

OC my primary work computer or my primary phone, that's just silly.
[Nexus 4 Q&A, Help & Troubleshooting] BravoMotorola:
Bro, listen. Do you ever consider that it wasn't even the kernel at all but just a simply faulty device? I have been running Faux's OC kernel. All the way to 1.8ghz. I've ran benchmarks too. There is STILL a thermal threshold in Faux's kernel and guess what? It's the same as stock. What does this mean? Past 60C it downclocks just the same as the stock did. No thermal damage possible any more then stock. Don't think its all devices or the kernel, its just your device. That it, its that simple. Don't wonder why only 100mhz damaged it because it didn't. I'm not saying it helped, but it's not that 100mhz fault that your jumping to conclusion here. You got unlucky, sorry.. hope you get a new device and it works well.
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
I'm not saying 100Mhz damaged my device at all. In fact, you're stating my point. The device was in fact, faulty. And no, they're not all made the same, but there's a good chance mine wasn't the only faulty one. I know for a fact that at least two people have reported the exact same problem as me and have had to get replacements. And that's the only point I'm trying to get across. Along with trying to get some of the nitwits here, typing without thinking, to understand that 100Mhz is not enough to completely kill a perfectly good device--there must have been an inherent flaw. Obviously, I'm not glad I got a faulty device, but I'm glad I found the problem with it and can get a replacement within the 15-day window. I'm not sure where I wrote it before today, but I mentioned that these phones SHOULD be able to OC without causing hardware damage. The manufacturer stated clockspeed is hardly the highest a device can use while still operating normally.
[Nexus 4 Q&A, Help & Troubleshooting] TwinkyOfHope:
Did you try this? Straight from the man himself.
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
Yes. If you read just a few posts down, you will see my response as well as someone else who had the same problem.
[Nexus 4 Q&A, Help & Troubleshooting] BravoMotorola:
Alrighty. Just saying, I know many have tried that OC kernel and only 3 reported "bricked" although with Fauxs institution I think by the looks of it at least on would have been able to unbrick. I'd say the chance of you bricking due to fauxs kernel is the same as the chance that you own a faulty piece of hardware.
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
I explained here how exactly I think it is bricked. It really does not seem to be an issue with the kernel, but rather the kernel acting as a catalyst on a already compromised device.
[Nexus 4 Q&A, Help & Troubleshooting] h00py:
Any chance of you posting a partial serial number so others with devices from the same batch can be careful?
[Nexus 4 Q&A, Help & Troubleshooting] Bwlian:
I'm having the same problem and all I did was root/un-lock with the toolkit (I know I know..) 2 days ago.

Checked phone (wasn't connected) and it was in the Google screen. (the battery was low at the time)

Can't get it further than that.

Yesterday I could get to the bootloader but recovery-mode did nothing.

Can get to download mode but pc fails to install drivers.

I've tried what faux said but nothings working atm.

Edit: just had the red-led so that should be somewhat of a save..

By holding power and vol + & - with red led permanently on I got into bootloader but won't get further than the google screen again.
[Nexus 4 Q&A, Help & Troubleshooting] USSENTERNCC1701E:
Faulty is a little strong, the chip ran fine at stock speeds, so it met minimum design specs, many chips just happen to be a little over-engineered, and yours was not. But definitely due to hardware capabilities exceeded. I had mine running at 1.8 and faux. Crashed when I tried undervolting at that rate, but ran stable at 1.8.
[Nexus 4 Q&A, Help & Troubleshooting] decepticon:
If you can get to the bootloader, flash the factory image and go from there.
[Nexus 4 Q&A, Help & Troubleshooting] nyijedi:
Are you stuck on the X logo? If so, just go into recovery and wipe data. That fixed it for me.
[Nexus 4 Q&A, Help & Troubleshooting] Bwlian:
Thanks for your answers. I however already tried a reflash but it didn't help :S This was with the toolkit though.

I'm now trying it as explained here fwiw: http://xdaforums.com/showthread.php?t=2010312
[Nexus 4 Q&A, Help & Troubleshooting] nyijedi:
Did you try wiping the data and cache?

1. Reboot into Fast Boot

2. Select Recovery using volume rocker. Hit power to select. You'll get the android mascot with the red exclamation point.

4. Press Power and Volume Up at the same time.

5. Choose to wipe all data. Confirm the selection.

6. Reboot.
[Nexus 4 Q&A, Help & Troubleshooting] Bwlian:
Recovery however hasn't yet responded or done anything.

When flashing it also gets stuck at the google screen so that hasn't helped.

So what should I do next :/

It's the same like this guy though I don't know how to check the battery with commands. Or none are being recognized as command so I might be doing it wrong.

http://xdaforums.com/showpost.php?p=34586637&postcount=84
[Nexus 4 Q&A, Help & Troubleshooting] nyijedi:
Okay. Try going into recovery a few times if it hangs at first.

Also, ignore the part of my post about the location of the volume rocker. That was in reference to the N10. Everything else is the same on the N4 though.
[Nexus 4 Q&A, Help & Troubleshooting] Bwlian:
What I mean't was that recovery just brought me back to the google screen.

No matter what recovery flashing I do it brings me back there and stops.

Hardware failure? :/
[Nexus 4 Q&A, Help & Troubleshooting] nyijedi:
Gotchya. What about using fastboot to boot to a custom recovery, like clockwork, and then using that to wipe data and cache?

EDIT: Here's instructions on using fastboot to boot to a recovery file (as opposed to flashing the recovery file). The instructions are for flashing JB on a Galaxy Nexus, but you can ignore those and just use the instructions re: using fastboot to boot into clockworkmod recovery.

http://www.androidcentral.com/how-manually-flash-jelly-bean-update-your-galaxy-nexus
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
Go into the bootloader while connected to the PC. Do "fastboot getvar battery-voltage" without quotes. This should tell you the voltage the battery is supplying the phone. If you don't get an output, then you have the exact same problem as me, which is somehow the battery is no longer communicating properly to the motherboard.

Edit: if the phone powers on at all by itself without the USB/charger plugged in, then you can just try flashing a custom recovery or something.
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
I'll post all the info I have on it. Since I'm getting a replacement, Google will be disabling this from operating anyways. See pic.
[Nexus 4 Q&A, Help & Troubleshooting] Bwlian:
Tried everything, won't get passed google screen so can't restore to anything either. I really don't get it how nothing has helped.
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
Go into the bootloader and run the fastboot command I mentioned above.
[Nexus 4 Q&A, Help & Troubleshooting] Bwlian:
Ah yes, no output. We're in this together :(
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
I initially thought mine was caused by overclocking, but it's becoming apparent that these phones were shipped with a defective battery that just randomly stopped working. You probably should get on the phone with Google for a replacement and prepare for a 30min wait time.
[Nexus 4 Q&A, Help & Troubleshooting] Bwlian:
Myea, problem for me is that it's bought from a German and I don't live there. Warranty will have to be sent via him as where I live you can't register N4's and they probably don't have parts for it anway.

My IMEI etc is largely the same as the one you posted btw so yeah...
[Nexus 4 Q&A, Help & Troubleshooting] djkinetic:
I'm willing to bet something either shorted/fried when you overclocked, or mayb you got a corrupted partition, which won't let you boot...either way overclocking this phone seems pretty pointless to me but to each their own.
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
You probably shouldn't be willing to bet on anything unless you've read the thread in its entirety and have gotten all the facts and reports from other users as well :P
[Nexus 4 Q&A, Help & Troubleshooting] Bwlian:
Yea, mine was only unlocked/rooted...:angel:
[Nexus 4 Q&A, Help & Troubleshooting] Clarkster:
Just pointing out another thread. His phone bricked after installing the Faux kernel. http://xdaforums.com/showthread.php?t=2013977

It seems to be the common theme here. Most people are okay with the Faux kernel, but the only bricks all have Faux in common.

So there is a problem with some devices and that kernel. I'd recommend avoiding it for now.
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
I'm not sure it's just the kernel. One person was bricked just after unlocking and rooting; nothing else.