Database Users

My Device is done. please help.

i have to have the worst luck in the world..
got my nexus one today. condition is MINT. seller also included the receipt from HTC proving that it got replaced.
popped in my sim, everything worked fine. turned it off to swap batteries and thats when the hell started.
im not able to get past the nexus logo. NOTHING. it would turn on, than go to the screen, vibrate, than repeat multiple times. phone has never been rooted.
i did EVERYTHING. i did the volume down plus power and than i cleared wiped the memory, same result.
than i tried downloading 2.2.1, renaming it to update.zip, put it on my zip, but that doesnt work. the phone can't tell theres a update.
like **** man. i than went here
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_&_Tutorials
read that i needed FRG33 and rename it to PASSIMG.ZIP. when the phone turns on, it gives me the message if i want to update, i get excited. i click yes, everything says ok, than i reboot and bam, still endless reboot. tried to do the passimg again but this time i get a fail on radio V2 or something like that.
WTF is going on. i didnt do anything. ANYBODY HELP?

maybe the battery you swapped in is bad?

same result with both batteries :/
i hate my effing luck.

Make sure your batteries are fully charged, seriously.

great, now when i click recovery, it doesnt even go to the android guy with the exclamation mark, it just gets stuck at the logo. all im able to do is get to hboot. WTF.
i mean the battery has half a charge. just checked with my desire. i even tried with it plugged in in the wall. nothing.

my aim is screwupboy444. your welcome to help me there or even laugh at me for being a bone head and getting in this situation.

Do you have a different SD card you can use?
Sent from my Nexus One using XDA App

yeah, i was using both the desire 8gb and the nexus one 4gb. both were reading fine in the desire. i read that if it gets to the nexus one logo then my phone isn't bricked, but im starting to think otherwise. nothing works.
ive been searching for the past hour half. everyone seemed to have fixed there by doing the passimg method or wiping data. but unfortunately none of that is working. i tried placing the froyo "update.zip" and running it but when i clicked recovery, it went into the boot cycle again.

http://forum.xda-developers.com/showthread.php?t=614850
thinking about doing that but i have a feeling it doesnt apply to me. that and i don't understand any of the process. i dont think my phone will even be read by my comp.

did the passimg for the third time. went past the logo and actually to the set up screen. than it rebooted again. and now its stuck on the nexus one logo again.

could it actually be that? i left the battery charging in the desire for about 40 minutes, than took it out and put it in the nexus one and actually got to the set up screen for the first time.
but my question is, if thats the solution, does that mean my phone is gonna trip out everytime its less than 60 percent battery power?

this is what i get when i put the 2.2.1 update on my sd card and go into recovery mode
Uploaded with ImageShack.us
most of the threads where people got this fixed required them unlocking the bootloader and doing something. im the second owner of the phone but would like to avoid rooting but if its required in this situation, i will. i just need a dummies guide to do it..

No, there's threads for recalibrating the battery, if needed.
Keep it fully charged, and see if it will run for a reasonable period... That way, we can see if it really is the battery...
Sent from my Nexus One using XDA App

Don't worry about the exclamation and Android for now, and see if the phone will boot and run with a fully charged battery...
Sent from my Nexus One using XDA App

frick, i know thats what i should do. it just blows that i got this today and theres already a chance that its trashed...

danger-rat said:
Don't worry about the exclamation and Android for now, and see if the phone will boot and run with a fully charged battery...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
thanks for all the help man. you dont think i need to unlock the bootloader right...? im just more curious on why the desire can work with either party no matter the charge. damn.

Wait until your battery is about 75% or more would be better, then try the passimg again...
Sent from my Nexus One using XDA App

not sure if its good news or not but (i apologize for my lack of patient before hand haha), i took out the battery the desire was charging again and put it in the nexus one. it got to the set up screen all three times before it resets again. i tried plugging it in the wall charger but it still resets at that area.
edit:
the battery level was at 74% when i tried it.

75% is not a hard number, and I'd let it charge as much as possible. I'd also quit switching batteries, and just stick with one until you isolate the problem...
Sent from my Nexus One using XDA App

danger-rat said:
75% is not a hard number, and I'd let it charge as much as possible. I'd also quit switching batteries, and just stick with one until you isolate the problem...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
oh iam. im charging the nexus one battery in the desire because once i turn on the nexus one, it gets frozen there, and than i cant turn it off.

[Q] Wierd

So im starting to notice that basically on every rom i run after about a week or 2 its starts to get all crazy and laggy and i start getting fcs ill reflash then same thing a week or 2 and it goes crazy again is it just me ?

ever tried starting from a fresh, clean slate? Meaning, ODIN to stock ec05 then root and flash roms? This should take care of any problems

Lots of roms have disabled journaling. When you disable journaling, you gain a tiny bit of performance, but every time you shut down incorrectly or drop the phone and the battery pops out, you are corrupting the hell out of some data. I can only assume that that is what is happening to you.

1. i have odin bout 1000000 times lol so doubt its that.
2.i usually HAVE to pull the battery after the 2 weeks cause its starts being an ass but i never drop my phone hard enough to make it drop the battery

Download reEnable journaling from here: http://forum.xda-developers.com/showthread.php?t=1071723
Flash your rom.. Let it boot up... then boot back into clockwork and flash this.. no wipes necessary.. should help.

CrfEpic4g said:
1. i have odin bout 1000000 times lol so doubt its that.
2.i usually HAVE to pull the battery after the 2 weeks cause its starts being an ass but i never drop my phone hard enough to make it drop the battery
Click to expand...
Click to collapse
You ever turn the phone off and pull the battery for any reason? Has the battery left the phone for any reason at all? I have noticed that some newer roms vibrate when they are turned off, but they are really not off for like 30 seconds after the vibration. You can see this by opening up the phone and looking at the keyboard lights or looking really closely at the screen and seeing its not completely off. Pulling the battery for any reason before the phone is completely 100% turned off can lead to corruption.

muyoso said:
You ever turn the phone off and pull the battery for any reason? Has the battery left the phone for any reason at all? I have noticed that some newer roms vibrate when they are turned off, but they are really not off for like 30 seconds after the vibration. You can see this by opening up the phone and looking at the keyboard lights or looking really closely at the screen and seeing its not completely off. Pulling the battery for any reason before the phone is completely 100% turned off can lead to corruption.
Click to expand...
Click to collapse
nah only time i turn my phone off honestly is to go into recovery or like i said when it starts acting up ..
but im gunna odin and reflash and crap and see what happens

CrfEpic4g said:
nah only time i turn my phone off honestly is to go into recovery or like i said when it starts acting up ..
but im gunna odin and reflash and crap and see what happens
Click to expand...
Click to collapse
When I used to run no journal, I would start getting force closes after day 4 or 5 like clockwork. I always shut my phone down properly and waited a bit. I re-enabled journal and haven't had data corruption or force closes in over 2 months...unless I am beta testing something for a dev and its not quite right
Sent from my SPH-D700 using XDA Premium App

guys where can i get the stock odin EC05 tar i only found a prerooted one and its not compatible with ext4

CrfEpic4g said:
guys where can i get the stock odin EC05 tar i only found a prerooted one and its not compatible with ext4
Click to expand...
Click to collapse
Click on link in my signature and click on my odin video... its in the description of it.
Sent from my SPH-D700 using XDA App

qbking77 said:
Click on link in my signature and click on my odin video... its in the description of it.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Thanks awarded and nice video very informational

>>>>>>ignore this post<<<<<<<<<<

I didn't bother to read previous post but, that happens when u had a bad fresh install to begin with. *aka odin*
Sent from my Epix 4G using XDA

yup, like I said, fresh ODIN of ec05 should do the trick. Then as others have said, enable journaling with whatever custom rom you slap on.
If you still have problems with f/c and lagging/freezing then you may have larger issues to attend to. I have been running custom roms with journaling disabled for the past 6 months and rarely have f/c problems.
Oh, and once you do get a fresh install of the rom you want, do a NAND backup immediately so you can restore to it if problems arise again.

If you don't use journaling, NEVER use the reset feature from the power button menu. Resetting and using utilities like Root Booter will cause data corruption and software rot.
Sent from my SPH-D700 using XDA App

And never pull the battery without waiting for the vibration. Also back up often in case of a freeze and battery pull.

kynetx said:
If you don't use journaling, NEVER use the reset feature from the power button menu. Resetting and using utilities like Root Booter will cause data corruption and software rot.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Huh mayb that was my problem ahahah I started fresh from odin today well see how it goes
Sent from my SPH-D700 using XDA App

me=power phone off, wait for vibration, then count to ten.

darksideauto said:
me=power phone off, wait for vibration, then count to ten.
Click to expand...
Click to collapse
me=enable journaling, then enjoy phone.

People are so hung up on benchmark scores they lose sight of things like data loss on non-journaled roms. If I'm not mistaken if you make a backup with clockwork recovery and restore itit remounts with default mount options.
Sent from my Nexus S 4G using XDA App

[FIXED] having issues.. EDIT! ram issue! Edit 2: fixed! sd card issue

im not sure when this started but it seems like every rom, every kernal i use now my phone will close apps to a black screen and freeze up for different lengths of time. was doing it in stock, and now a custom rom. tried different kernals... seems to be worse when the phone first boots up. its almost like a force close but slower and i don't get the force close message. help
Edit: ok i brought up the ram manager and my ram would start around 250 and climb up before my eyes until the screen blacks out.... how do i figure out what is eating up the ram.. and why does it stop?

murso74 said:
im not sure when this started but it seems like every rom, every kernal i use now my phone will close apps to a black screen and freeze up for different lengths of time. was doing it in stock, and now a custom rom. tried different kernals... seems to be worse when the phone first boots up. its almost like a force close but slower and i don't get the force close message. help
Click to expand...
Click to collapse
I assume you already tried Odin to clear out any crap left right?
Sent from my SPH-D700 using XDA Premium App

JohnCorleone said:
I assume you already tried Odin to clear out any crap left right?
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
yeah odined to stock ec05 and it was just as bad. rebooting the phone actually made it worse... seemed like it took forever for everythign to stabilize. phone also seems to get hot but i could be wrong about that. not the battery but above the battery near the camera

Quite often this is caused by restoring old data over a new rom using a program like titanium backup. Sometimes you can get away with it between similar roms but restoring Froyo data on to a gingerbread rom will almost always cause lots of FCs.

poit said:
Quite often this is caused by restoring old data over a new rom using a program like titanium backup. Sometimes you can get away with it between similar roms but restoring Froyo data on to a gingerbread rom will almost always cause lots of FCs.
Click to expand...
Click to collapse
i never restore data from nandroid backups and i reinstall all my apps from the market...
maybe my phone is tired
modem seems to be resetting alot too

murso74 said:
yeah odined to stock ec05 and it was just as bad. rebooting the phone actually made it worse... seemed like it took forever for everythign to stabilize. phone also seems to get hot but i could be wrong about that. not the battery but above the battery near the camera
Click to expand...
Click to collapse
Isn't the spot right above the battery where the chip is located? Have you been overclocking your phone like I have at 1400 everyday? I was wondering if I have been flashing too much. I saw some of these issues myself. Odin started freezing as well but it seems to have smoothed out. I thought I may have wiped out my phone
Sent from my SPH-D700 using XDA Premium App

JohnCorleone said:
Isn't the spot right above the battery where the chip is located? Have you been overclocking your phone like I have at 1400 everyday? I was wondering if I have been flashing too much. I saw some of these issues myself. Odin started freezing as well but it seems to have smoothed out. I thought I may have wiped out my phone
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
no.... set at concervitive 200 - 1000. but i was using drockstars kernal before this without using a governer and it was still doing it. now i'm using TZ 1.1.1
it is that spot.. but its not hot there all the time either. very annoying issue

murso74 said:
no.... set at concervitive 200 - 1000. but i was using drockstars kernal before this without using a governer and it was still doing it. now i'm using TZ 1.1.1
it is that spot.. but its not hot there all the time either. very annoying issue
Click to expand...
Click to collapse
Ummm, I am kind of at a loss here. You don't have any physical damage to your phone? No serious drops? You didn't go swimming with it in your pocket? But seriously, I run at 1400/100 on demand all of the time and that spot gets hot on Gingerbread ROMs but not on Froyo unless I run a lot of video at 1400 max.
Sent from my SPH-D700 using Tapatalk

JohnCorleone said:
Ummm, I am kind of at a loss here. You don't have any physical damage to your phone? No serious drops? You didn't go swimming with it in your pocket? But seriously, I run at 1400/100 on demand all of the time and that spot gets hot on Gingerbread ROMs but not on Froyo unless I run a lot of video at 1400 max.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
yeah i don't know what to think either. i guess when official gb finally drops i'll try one last clean install and if it keeps doing it i'm going to have to go through insurance

murso74 said:
yeah i don't know what to think either. i guess when official gb finally drops i'll try one last clean install and if it keeps doing it i'm going to have to go through insurance
Click to expand...
Click to collapse
When did you purchase your phone? did this start to happen after you started loading custom ROMs or since the start?
What is your current setup right now? Do you use RFS or EXT4?
What hacks have you loaded to your phone, and after what even that you performed on the phone did you start experiencing this issues?

megabiteg said:
When did you purchase your phone? did this start to happen after you started loading custom ROMs or since the start?
What is your current setup right now? Do you use RFS or EXT4?
What hacks have you loaded to your phone, and after what even that you performed on the phone did you start experiencing this issues?
Click to expand...
Click to collapse
i've had the phone for a year. i've been doign roms for at least 6 months.. this only started in the last month on both rfs and ext4. i don't know what i did that could have done this.. honestly i started noticing it when i odined back to EC05 a few weeks ago. then i did an rfs rom, then drockstars kernal, now srf 1.2 and tz kernal. just seems to be getting worse and worse. to be honest it may have started after i flashed back from eh22

Are you on TW4 Launcher? That can cause phone to freeze.

Overstew said:
Are you on TW4 Launcher? That can cause phone to freeze.
Click to expand...
Click to collapse
i am actually.... although this started before the tw4 launcher. i guess i'll remove it for a while and see what happens. dammit i liked the tw4 launcher too

Don't use any CPU programs like setcpu, etc.. if not try wiping your sd card. Could just be your phone too.
Sent from my SPH-D700 using Tapatalk

I had this issue for a while and it caused me to leave to the iPhone, but now after months of waiting I am trying to bring my epic back
I will post my results I am going to try flashing back to stock and see it if can stay on for a day with out crashing....I'll be back with results in a day or 2

Mine does the same thing and it shuts off sometimes at 35% battery left. Just in the past month. Im stock not rooted. One more thing somedays i get 13 hrs of life and others like 6, same usage everyday and same area so service isnt the issue.
Sent from my SPH-D700 using XDA App

I had this same issue. I was to a point of chamging phones.
I decided to watch 5 different tutorials/youtibe videos on how to odin back to stock.
In that process, 3 of the videos had different options checked. Yes, I decided to try each way, restoring apps/data from Titanium, each time.
After the first 2 attempts, and still seeing the freezes, I started to get some kind of com.google.apps process force close errors.
I was really ready to beat my phone up at this point.
So, after deciding, I've had enough, I said I would do it ONE more time. (There was still one more checkbox that another video was showing...)
Sent from my SPH-D700 using XDA Premium App

Sry, my fat fingers pressed submit.
Anyhow, Ive 0 programming experience so, all of this might kust be a lucky fluke. When I odin'd, I checked all three options. Re-Partition, Autoreboot, And F. Reset Time.
Only 1 video of the 4 I watched said to do this.
I then restored my apps and data back w/ Titanium.
I did make sure that any data from OEM apps, was not broight back, as a precaitonary on my part. It was really driving me nuts. Hope this helps....
Sent from my SPH-D700 using XDA Premium App

crap well it wasn't TW4... uninstalled it last night. today rebooted and same thing.... its so strange it only happens the most after i reboot the phone. black screen with the status bar up top. if i touch the screen the button lights will come on ... if i swipe down the status bar it will eventually come down.. but with a ton of lag
i guess i'll nandroid backup and start from scratch with odin again. bone stock no root see what happens.
EDIT: just noticed that the modem seems to reset every time it does this. didn't see that before cause it doesn't always make the no signal sound. but the bars on the status screen go dark and the little x pops up above them before the home screen redraws. so basically whatever i'm doing goes to black screen.. times out for 10 min with just the bar on top, modem resets and goes back to the home screen

ok i brought up the ram manager and my ram would start around 250 and climb up before my eyes until the screen blacks out.... how do i figure out what is eating up the ram.. and why does it stop?
man this is nuts... i've got android system info running and i'm watching the processes tab... all the programs start usign memory, then android starts killing them off until they are almost all gone then i go to black screen... i dont' know what the hell is going on
edit: tasks is showing android.process.acore twice, package com.fede.launcher. both are using 34.89 MB and have cpu at 100... however total CPU usage is only showing 7%

my xoom appears to be dead (?)

Hello, android developer here.
The other day my xoom drained all the way to 0% (this happened overnight while I was asleep). I noticed right away because I use the xoom as my alarm clock. I ended up sleeping in that day (doh!)
Anyways, now the darn thing simply wont turn on. I try to soft reset (vol up + power) but nothing happens. I tried plugging it in via usb thinking I could reboot it with adb, but my computer fails to see the device. So its turned off and simply will not turn on. I've even let it charge for 2 days straight (green charge light on device).
Nothing.
What the heck man?

Dumb question.... How long have you held the power button? My Xoom (maybe others?) won't turn on unless I hold the button for 2-3 seconds.

Ive gone up to 60 seconds of button pressing...when it doesnt work one tends to go to extremes lol
I can't believe this, first time I've ever had a device die like this :-/

Did you charge it before you tried to turn it back on? My Milestone tends not to turn on after it drained below zero for like ten minutes until the battery has at least some basic charge again.

Try turning on right 3~4 minutes later putting on a yiur charger
Sent from my MZ605 using XDA App

Zhenech said:
Did you charge it before you tried to turn it back on? My Milestone tends not to turn on after it drained below zero for like ten minutes until the battery has at least some basic charge again.
Click to expand...
Click to collapse
Yeah its been charged for 48 hours now, green light on power indicator as well.
It still wont boot. I tell ya its the strangest thing I've seen in a while...

did you try booting in recovery? vol down ±power

zylith said:
did you try booting in recovery? vol down ±power
Click to expand...
Click to collapse
Of course. I've tried every combo imaginable.
F this, I'm getting an ipad.

techs1200 said:
Of course. I've tried every combo imaginable.
F this, I'm getting an ipad.
Click to expand...
Click to collapse
If you really want the iPad, here's the perfect excuse.
However, if you want to save your Xoom, you might want to check out the Motorola Factory cable from Team Black Hat (Google it). If there was ever a use for this cable, your situation seems to define it. Your Xoom seems to think it's not charged (drained) or can't take a charge, but it sounds more like the former situation. The Factory/Programming cable obviously makes a different electrical connection and makes the Xoom think it's charged...something like that. Check it out.
Also, at least one person made one out of a usb cable and it saved his bacon. You'll have to do a search for his thread...it was a while back.
Good luck, what ever you do.

You need to make or buy the motorola factory cable. That will get you booting.
Sent from my Xoom using xda premium

Well I did buy an iPad2 a few days ago, but I will definitely be making one of those cables.
Wow, thanks so much! XDA never disappoints

Remove your SD card then restart... Happens to me all the time..
Sent from my GT-N7000 using XDA App

davidblaine021 said:
Remove your SD card then restart... Happens to me all the time..
Sent from my GT-N7000 using XDA App
Click to expand...
Click to collapse
Yes, I have seen this also. Pull out the SD card and the unit comes back to life.

My Nexus 7 is doomed...

A few weeks ago, i flashed a stock rom on my wifi nexus. I was happy with it until last week. Charging became incredibly slow - 30% over 8 hours. I threw it in my bag and wheb i got home 8 hours later, the battery was depleted completely. I couldn't turn it on. I plugged it in over night and it stayed at zero percent. I booted into recovery and reflashed my stock rom abd wiped my data. Still didn't charge. I tried going into my bootloader and hitting power off and then plugging in, but it still wouldn't charge. I can't flash my backup because it's on my card that i lost, and even if i had it, i wouldn't be able to keep it on long enough to flash it. ADB won't run on my pc and i don't know how to use the program anyway. What can i do to save my device? Please help.....
Sent from my YP-G1 using xda app-developers app

Replace battery?

veeman said:
Replace battery?
Click to expand...
Click to collapse
Not the average flasher knows how to tear apart a device - including myself. Anyways, this thing won't power up at all? You tried leaving it plugged in and booted into bootloader? If so, sounds like a hardware issue or the battery is defective.

I would be willing to bet that your battery connection came loose. Start at your USB port with a thin piece of plastic, such as a guitar pic. Work your way around the device and remove the back.
Sent from my Nexus 7 using xda app-developers app

DroidOnRoids said:
Not the average flasher knows how to tear apart a device - including myself. Anyways, this thing won't power up at all? You tried leaving it plugged in and booted into bootloader? If so, sounds like a hardware issue or the battery is defective.
Click to expand...
Click to collapse
It's not too difficult. iFixit has a good tutorial on it. http://www.ifixit.com/Guide/Installing+Nexus+7+Battery/9895/1

happyjack96 said:
A few weeks ago, i flashed a stock rom on my wifi nexus. I was happy with it until last week. Charging became incredibly slow - 30% over 8 hours. I threw it in my bag and wheb i got home 8 hours later, the battery was depleted completely. I couldn't turn it on. I plugged it in over night and it stayed at zero percent. I booted into recovery and reflashed my stock rom abd wiped my data. Still didn't charge. I tried going into my bootloader and hitting power off and then plugging in, but it still wouldn't charge. I can't flash my backup because it's on my card that i lost, and even if i had it, i wouldn't be able to keep it on long enough to flash it. ADB won't run on my pc and i don't know how to use the program anyway. What can i do to save my device? Please help.....
Sent from my YP-G1 using xda app-developers app
Click to expand...
Click to collapse
Sounds like my device... only I even can't get into the bootloader nothing... Someone suggested that the battery got so far depleted that it will nor recharge.
However seems you at least can run the bootloader... for me it just stays black ..... nothing nopes nadda

dkd2625 said:
Sounds like my device... only I even can't get into the bootloader nothing... Someone suggested that the battery got so far depleted that it will nor recharge.
However seems you at least can run the bootloader... for me it just stays black ..... nothing nopes nadda
Click to expand...
Click to collapse
Actually, there's a sticky for these issues haha
N7 Turns Off/Won't Turn Back On/Battery Status Issues - The Fixes **UPDATE**...
---------- Post added at 11:28 AM ---------- Previous post was at 11:27 AM ----------
veeman said:
It's not too difficult. iFixit has a good tutorial on it. http://www.ifixit.com/Guide/Installing+Nexus+7+Battery/9895/1
Click to expand...
Click to collapse
I heard that was a good site. I'm more scared of screwing up any hardware than doing the actually tearing apart.

I can boot for like 30 seconds and then it shuts off. I've tried the solutions in the thread link above; however, i still think it is a software issue. I've used other roms that had really slow charging, but i was able to switch to another one before the battery got depleted. So i think my best bet is to somehow get a new rom on my device somehow. ADB won't run on my computer. It just flashes a command prompt on the screen for like half a second and closes.
Sent from my YP-G1 using xda app-developers app

happyjack96 said:
I can boot for like 30 seconds and then it shuts off. I've tried the solutions in the thread link above; however, i still think it is a software issue. I've used other roms that had really slow charging, but i was able to switch to another one before the battery got depleted. So i think my best bet is to somehow get a new rom on my device somehow. ADB won't run on my computer. It just flashes a command prompt on the screen for like half a second and closes.
Sent from my YP-G1 using xda app-developers app
Click to expand...
Click to collapse
What kernel are you on? The kernel is what does the charging operations.

happyjack96 said:
I can boot for like 30 seconds and then it shuts off. I've tried the solutions in the thread link above; however, i still think it is a software issue. I've used other roms that had really slow charging, but i was able to switch to another one before the battery got depleted. So i think my best bet is to somehow get a new rom on my device somehow. ADB won't run on my computer. It just flashes a command prompt on the screen for like half a second and closes.
Click to expand...
Click to collapse
I had a similar situation in that after the battery died, I got it to the point where I could boot up, but after a screen timeout, it would be dead again. Finally, I got it booted again (while plugged into power) and immediately went to developer options and checked the Stay Awake, never sleep while charging. Keeping the screen awake kept the N7 on and it charged up.

Funny my Galaxy Nexus started doing this crap on me too after I updated the rom and kernel. The phone and battery are only 2 months old replaced in April.
Occasionally it won't take a charge. I have to **** with the battery, removing it several times. Then all of a sudden it starts charging again after 10-15 resets.
Haven't had a problem in a while. Typically hits me like every 2 weeks.
No problem on N7 though but it happens. First thing is to change your kernel and rom to something else. If still draining, flash stock and relock, unlock, relock, wipe. Boot, upgrade to 4.2.2 and test.
Sent from my Nexus 7 using XDA Premium HD app