Related
Hello,
Yes, I am a noob, and after searching and looking through a lot of threads, I decided to make this post, knowing full well how annoying it must seem to those of you who actually know even a little about phones.
Someone special to me got the HTC HD2, and it was a bargain. But she hated windows, so I offered to help. She's had it for ages by now.
I believe I did everything correctly, blindly following guides (which I know is a bad idea from reading threads similar to this one).
The thing that makes my problem somewhat special is:
- Everything went smoothly, the android build is amazing
- I was a hero for a few hours
- She's playing some game when it suddenly freezes.
- Buttons not responding, afraid the battery has to go.
- Boots up, android guy stares at us for more than five minutes, battery has to go again.
- Nothing, NOTHING, happens after. Can't boot, screen is black.
So obviously I'm suspecting the battery is completely dead. It won't charge either from the computer or by plugging it to the wall. It was connected when it crashed, and there must have been power left. Now, I have the HTC desire HD, so I can't test my battery with the other phone.
Before I try to buy a new one, I need to know, being completely oblivious with regards to anything more complicated than rocks, if it's possible that I have installed any kind of software that can permanently mess up a battery. Feel free to laugh if this is the dumbest question ever. It's weird how it booted a little before permantently shutting down.
To make matters a lot worse, she's going abroad for five months possibly only equipped with a really old nokia phone until I can get things fixed and sent off to her (which will be quite expensive and perhaps risky.)
Have I messed up good, or is it just chance that the battery should fry hours after getting the android rom? Should I get a new one? Her phone was actually smoother than mine until the crash.
Sorry to make yet another "dumb noob ruins phone" but I really need to redeem myself, and fast.
Edit: Remembered the course of events was a bit different.
well, if I tell you that the phone wont charge when off when magldr is installed, would that change your opinion of whether the battery is at fault?
id suspect the crash broke something preventing rebooting (had this myself once or twice with nand android ) followed by teh battery being flat so wouldnt come back on. (And of course magldr wont let it charge when off....)
get an old usb cable, any type, cut end off, bare red and black wires, plug into wall charger and then hold red to + black to - on the battery for about a minute, this should let the phone start, , put it into bootloader (coloured stripey screen, not magldr) and let it sit there for a hour or three with usb plugged in, should now be charged enough to see if you can get into magldr, from there into cwm, and from there id do a backup, and then perform 'wipe data/factory reset', , if it boots to the clean rom, you can try (again in cwm) selectively restore the data and/or sd-ext partitions, which should bring back teh data and the installed apps. if the restore doesnt work, just do another wipe data/factory reset and start from scratch.
also, check the battery pins very carefully, they bend easily, especially when you pull teh battery whilst panicking!
samsamuel said:
well, if I tell you that the phone wont charge when off when magldr is installed, would that change your opinion of whether the battery is at fault?
id suspect the crash broke something preventing rebooting (had this myself once or twice with nand android ) followed by teh battery being flat so wouldnt come back on. (And of course magldr wont let it charge when off....)
get an old usb cable, any type, cut end off, bare red and black wires, plug into wall charger and then hold red to + black to - on the battery for about a minute, this should let the phone start, , put it into bootloader (coloured stripey screen, not magldr) and let it sit there for a hour or three with usb plugged in, should now be charged enough to see if you can get into magldr, from there into cwm, and from there id do a backup, and then perform 'wipe data/factory reset', , if it boots to the clean rom, you can try (again in cwm) selectively restore the data and/or sd-ext partitions, which should bring back teh data and the installed apps. if the restore doesnt work, just do another wipe data/factory reset and start from scratch.
also, check the battery pins very carefully, they bend easily, especially when you pull teh battery whilst panicking!
Click to expand...
Click to collapse
What ARE you?
It started. Honestly, when I was crossing wires I half suspected someone was pulling my leg. I can't thank you enough. Maybe I will be able to get this thing running again before I leave in the morning. I'll visit the link in your signature at a later point, too, as you may have saved me some money here.
The only real problem is that with no prior experience, I didn't even really get into what the different programs I installed actually do, so I'm not even sure where to go from magldr. I took a backup of what was essential before flashing, so I guess I'll just try to navigate to wiping and resetting. So relieved.
e: Progress, thanks again, fantastic.
Multiplum said:
e: Progress, thanks again, fantastic.
Click to expand...
Click to collapse
youre welcome.
im on green clockwork recovery and no matter what i try to flash it says bad zip. Also i have wipe everything and formattted sd card. Can i just unroot and fastboot usb mode? please need help
I personally never had good luck with CWM for Eris. I have been using Amon Ra recovery with no problems. I would give that one a shot.
There is one application on the Market called 'HTC Eris One Click Root', it installs a custom recovery and at the same time you it gives a zip so you can root the Eris. This might not be relevant to your situation, however, if you delete your current recovery mode and you can try this; this is just a suggestion.
Hope this helped
I second the Amon Ra recovery for the eris.
I can fix cars but I might have jacked my Eris
So i have ClockworkMod, And was using CyogenMod 7, no problems, Even tried a few other Roms, well I was switching Roms one day with the battery low. Stupid me. It died in the middle of it (F..k me). I now have the problem of- assert failed: write_raw_image("/tmp/boot.img", "boot")
E:Errorn /sdcard/update-cm-7.2.0-RC1-desirec-signed.zip
(status7)
installation aborted.
This happens or similar no matter the ROM!!
And my nandroid backup- Well its now missing!!!
What can I do? I can boot into hboot and go to usbbootlogger and into clockworkmod recovery so it aint bricked yet! Might as well be though cause I am using a old NON ANDROID hoopdee till I fix this one. Its like my Cadiliac is broke and Im driving a VW bug till I fix it! Ugh!!!! This was a Verizion Flashed(reprogramed by me with no problems) for months. I guess I know enough to fix it if some one holds my hand through the steps! Or enough to get myself in trouble!!! Anyway, any suggestions! And yes please talk to me like im 5 explaining all the steps in detail or It just might be bricked! If you live in Denver Colorado I will fix some Cars for some phone help! That is a great deal as cars are way more expensive as the tools and schooling are Very expensive! A scanner will buy you 50 new phones!!! But hey, I just want my phone back! And ya might get your car fixed for it!
jayram1408 said:
well I was switching Roms one day with the battery low. Stupid me. It died in the middle of it (F..k me). I now have the problem of- assert failed: write_raw_image("/tmp/boot.img", "boot")
E:Errorn /sdcard/update-cm-7.2.0-RC1-desirec-signed.zip
(status7)
installation aborted.
Click to expand...
Click to collapse
jayram1408 said:
What can I do? I can boot into hboot and go to usbbootlogger and into clockworkmod recovery
Click to expand...
Click to collapse
You should be able to flash ErisMTDNuke_v0.9.zip from within ClockworkMod recovery. Get it here.
Note that this procedure will completely wipe out the "boot", "system", and "data" partitions, so you should also either:
(a) have a ROM on your SD card ready to install OR
(b) figure out what you did to your nandroid backups and restore one of those.
You can do the flashing of the ROM or nandroid restore in the same session of ClockworkMod after flashing the ErisMTDNuke_v0.9.zip repair.
As you've learned, do this stuff with a 100% charged phone.
Let us know how it works.
bftb0
I really messed up now
Now it wont even light up, turn on, charge, NADA. Does this mean its toast? Nothing.
jayram1408 said:
Now it wont even light up, turn on, charge, NADA. Does this mean its toast? Nothing.
Click to expand...
Click to collapse
What exactly was it that you attempted? Did you charge it before you did anything?
You might try pulling the battery, wait a couple seconds, press each of the mechanical buttons (vol-up/down, send, trackball, end) once, and re-insert the battery, and put it on the charger. (This is a very long shot, probably will do nothing.)
Note that if you left the phone sitting in HBOOT, FASTBOOT, RUU mode, or a bootloop the battery can discharge even if you have it plugged into a USB hub. IIRC Li-Ion battery packs have a safety circuit that prevents charging if the battery charge (voltage) level drops too low.
It is possible that you simply have a dead battery that can not be recharged. Not easy to tell if that is the case, though - if you plug an Eris in to a charger without its battery, it won't start up in any mode even though there is (in principle) sufficient voltage/current (I just tried it on a working Eris). About the only way to know for sure is to see whether it's the phone or the battery is if it will go into any mode with a known-good battery.
I just measured the open-terminal voltage on a charged Eris battery - 4.11 V
bftb0
Battery reads 3.89 volts
I don't know what happened? I did'nt get a chance to do anything. I tried to boot into recovery and that was the last time it did anything. No lights, beeps, backlights, even no charge indicator. I cleaned the contacts with alcohol, still nothing. Its like its fried. I am wondering if it has lost all programing and that prevents buttons and charging from working?
jayram1408 said:
I don't know what happened? I did'nt get a chance to do anything. I tried to boot into recovery and that was the last time it did anything. No lights, beeps, backlights, even no charge indicator. I cleaned the contacts with alcohol, still nothing. Its like its fried. I am wondering if it has lost all programing and that prevents buttons and charging from working?
Click to expand...
Click to collapse
That sounds like a hardware problem other than the battery - I think that the discharged voltage for a low Li-Ion battery is close to 3.0v or below, so a discharged battery is probably not your problem.
100% of all "software" - even the bootloader itself - is stored on the single NAND flash chip in the phone. So, it could be that the bootloader code got corrupted, but it could also be any number of other hardware defects that prevents the phone from getting to the point where it loads and runs the bootloader code. It could even be something trivially simple like a problem in the battery charging circuit - it seems hard to imagine that the microprocessor needs to be awake and running (maybe in deep power down mode) for the battery charging to be operational.
Ok cooked eris.
I liked it so much I found a near new one on Craigs List for 30. And im back up and good again. Flashed Amon RA Recovery this time.
My problem is kind of strange.. when I turn off the phone, it thinks it's being charged (no cable plugged in).. and i'm unable to boot the OS as per usual. The only way for me to do it is to load CWM and choose the reboot option, which does work but only with 1 battery (a spare hyperion one). The stock battery and my other hyperion aftermarket battery does not work. Instead, it takes me to the stock recovery system.
I tried remedying this problem by doing wiping battery stats, but it doesn't help any. I also decided to make the jump from unnamed ROM (gingerbread) to an ICS rom (AOKP)
On top of that, the phone no longer makes a beeping sound when i plug the cable in, but it does charge the battery.
Another thing: the boot screen (when turning phone on) shows "samsung i9100" when i'm pretty sure my phone is an i777.. i might have done something to this phone when i got it about 10 months ago, but i don't remember. All i remember was rooting the phone and flashing it to unnamed ROM.
It seems like this might be a hardware issue, but i'm no expert.
mistabeo said:
My problem is kind of strange.. when I turn off the phone, it thinks it's being charged (no cable plugged in).. and i'm unable to boot the OS as per usual. The only way for me to do it is to load CWM and choose the reboot option, which does work but only with 1 battery (a spare hyperion one). The stock battery and my other hyperion aftermarket battery does not work. Instead, it takes me to the stock recovery system.
I tried remedying this problem by doing wiping battery stats, but it doesn't help any. I also decided to make the jump from unnamed ROM (gingerbread) to an ICS rom (AOKP)
On top of that, the phone no longer makes a beeping sound when i plug the cable in, but it does charge the battery.
Another thing: the boot screen (when turning phone on) shows "samsung i9100" when i'm pretty sure my phone is an i777.. i might have done something to this phone when i got it about 10 months ago, but i don't remember. All i remember was rooting the phone and flashing it to unnamed ROM.
It seems like this might be a hardware issue, but i'm no expert.
Click to expand...
Click to collapse
I would try wiping cache and dalvik cache in cwm. Also, fix permissions in cwm. If that does nothing, I would try a different kernel. However, this may be an internal issue of the phone.
Sent from my GT-I9100 using xda premium
mistabeo said:
My problem is kind of strange.. when I turn off the phone, it thinks it's being charged (no cable plugged in).. and i'm unable to boot the OS as per usual. The only way for me to do it is to load CWM and choose the reboot option, which does work but only with 1 battery (a spare hyperion one). The stock battery and my other hyperion aftermarket battery does not work. Instead, it takes me to the stock recovery system.
I tried remedying this problem by doing wiping battery stats, but it doesn't help any. I also decided to make the jump from unnamed ROM (gingerbread) to an ICS rom (AOKP)
On top of that, the phone no longer makes a beeping sound when i plug the cable in, but it does charge the battery.
Another thing: the boot screen (when turning phone on) shows "samsung i9100" when i'm pretty sure my phone is an i777.. i might have done something to this phone when i got it about 10 months ago, but i don't remember. All i remember was rooting the phone and flashing it to unnamed ROM.
It seems like this might be a hardware issue, but i'm no expert.
Click to expand...
Click to collapse
Well you fixed your charging issue by itself It says that because the flash counter has been tripped. Just use any triangle away app from the play store.
jt.61 said:
I would try wiping cache and dalvik cache in cwm. Also, fix permissions in cwm. If that does nothing, I would try a different kernel. However, this may be an internal issue of the phone.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
i just flashed to AOKP ics rom yesterday from unnamed ROM, so i doubt it's a a kernel issue. just tried wiping cache, dalvik cache, and fixed permissions. still the same issue. im afraid of shutting the phone off or changing the batteries now, which is a pain since the new ICS rom burns battery power like crazy.
122ninjas said:
Well you fixed your charging issue by itself It says that because the flash counter has been tripped. Just use any triangle away app from the play store.
Click to expand...
Click to collapse
the flash counter isn't a big issue for me; thought i had circumvented it when i flashed the ROM 10 months ago, but i guess not. the phone still thinks it's being charged when it's turned off though. that's my main problem.
mistabeo said:
i just flashed to AOKP ics rom yesterday from unnamed ROM, so i doubt it's a a kernel issue. just tried wiping cache, dalvik cache, and fixed permissions. still the same issue. im afraid of shutting the phone off or changing the batteries now, which is a pain since the new ICS rom burns battery power like crazy.
the flash counter isn't a big issue for me; thought i had circumvented it when i flashed the ROM 10 months ago, but i guess not. the phone still thinks it's being charged when it's turned off though. that's my main problem.
Click to expand...
Click to collapse
Try to go to stock and see if the problem persists. If it does obviously a hardware issue
ultimately, if i really want to confirm, i'd probably have to do that. but i've already installed 2 different ROMs and the issue is still persistent, so i'm just going to assume it's a hardware issue. it also seems now that the phone no longer turns off. if i choose to turn it off, it'll just reboot the phone. this phone will have to last me another 9-10 months, i just hope it doesn't die out on me.
but yeah, i tried ICS for about a day and didn't like it. bad battery life, seems slower, and less user intuitive UI.. so i'm going back to gingerbread.
mistabeo said:
ultimately, if i really want to confirm, i'd probably have to do that. but i've already installed 2 different ROMs and the issue is still persistent, so i'm just going to assume it's a hardware issue. it also seems now that the phone no longer turns off. if i choose to turn it off, it'll just reboot the phone. this phone will have to last me another 9-10 months, i just hope it doesn't die out on me.
but yeah, i tried ICS for about a day and didn't like it. bad battery life, seems slower, and less user intuitive UI.. so i'm going back to gingerbread.
Click to expand...
Click to collapse
you know samsung has factory warranty for that kind of stuff.
i got my phone refurbished, about 9 or so months ago.. it only came with 3 months for the warranty. i guess getting a returned phone ended up biting me in the ass.
now the phone is overheating when im charging it.. looks like it's going to crap out on me soon.
Download the stock 2.3.4 firmware from the download repository. Do a full wipe including system data cache and dalvik. Boot into download mode hook up Odin and flash the stock firmware. If its a hardware issue your problems will persist in which case u could sell it on eBay for parts. If its a software issue that will fix it.
Sent from my SGH-I777 using xda premium
that's what i'll probably have to do tomorrow. if i remember correct, rooting the phone on 2.3.4 wasn't that straight forward, so i'd have to read up on how to do that again. but im just gonna leave it as is right now.
the phone acts really weird. when i took out the battery and replaced it with another one, it would keep doing the same thing. so then i plugged the phone into the USB charger and tried turning it on - that worked.
if it's a hardware thing, it's got to be something to do with the battery sensor. the phone is simple to remove, so i wonder if i can replace it myself.
i believe my phone is now semi-FUBAR.. it still runs, but seems like the battery sensor issue is a hardware one. i just tried doing a stock flash/odin thingy, and it still has the same issues... also, the phone is now permanently showing as MTP connected. i am also seeing decreased battery life.. only lasts about 1/2 a day now.
i guess i learned my lesson.. don't switch out the batteries too often, or your phone will die.
Another thing: the boot screen (when turning phone on) shows "samsung i9100" when i'm pretty sure my phone is an i777.. i might have done something to this phone when i got it about 10 months ago, but i don't remember. All i remember was rooting the phone and flashing it to unnamed ROM.
Click to expand...
Click to collapse
is this a big deal? i'm also having samsung i9100? im using ucle5 AJ's rom/kernel.
i'm also having issues with charging the phone. it seems to charge forever, i have to unplug and plug the charger again to properly charge it.
When it says i9100 it means you tripped the flash counter. If you want to reset it use a triangle away app.
Sent from my SGH-I777
i see thanks.
i'll try to run this app and see what will happen.
do wiping battery stat needs to be in full charged? i used to do that on my tab so i guess same principle applies.
bubuty said:
i see thanks.
i'll try to run this app and see what will happen.
do wiping battery stat needs to be in full charged? i used to do that on my tab so i guess same principle applies.
Click to expand...
Click to collapse
No the same principle does not apply. Battery state wiping has no effect on this phone.
Sent from team Pirate! Using Tapatalk 2
So, yesterday afternoon i plugged in my phone to charge (about 11 PM) and left it for the whole night. I also have to add that Ive been running a mobile AP on it for the whole time. Today morning, I wake up and its crazy hot. I quickly DC it from charging, remove the back cover and let it be for a sec. I unlock it, it runs for few seconds normally and BAM, background behind icons is black and it froze up. I remove the battery to perform a hard reset of sorts and then the worst thing happens... Phone is stuck on boot Samsung logo. I turn it off again, hoping for a quick fix but it accomplishes NOTHING. I plug it into the charger and battery icon is visible but the circle on it is stuck and nothing seems to be happening.
Now I go into recovery mode that's working - surprise! And delete cache and dalvik cache. Nothing. I go back delete those things again and battery stats too this time. Nothing. I go back and do a factory reset... Nothing. Yeah.
So, imo since recovery is working it can't be a burned CPU/RAM right? Most likely (or hopefully) it's just the software that died? Im in the process of downloading a ROM and I will put it on my ext. SD card along with super-wipe that I will run but I was wondering - are there any good ROMs (or something else that might save my ass) that can be installed using Odin?
Yeah, it seems it was the case. Just installed ROM from my ext. SD and it's booted up which is very nice. Seems that it overheated and somehow killed my everything. Which is weird and anyone cares to help me explain this?
There's no need for n extensive backstory because rooting, flashing, etc I am pretty familiar with, having first rooted the old HTC Thunderbolt.
Now here's what happened:
I have quite a few roms for the S4 but the BoneStock 1.1.4 rom by Andybones always kept bringing me back. I pretty much settled for that one as my dail driver and kept it so for at least 2 months.
Recently in the past week i started getting notifications on my internal sys memory almost out. So i check and realize that my Google Play Music is almost at 6 gb, so I decide to wipe my entire phone just to give it a fresh new flash. Flash goes well, fresh install. I hardly have the time to let my phone die, so I usually just charge it regardless (I have a 5200 mAh extended battery) but this time I decided to let it die. Once it did, i put it to charge immediately and thats when i noticed something was wrong. It was stuck at the battery logo, the animated one that charges while your phone isn't on yet? Well the circle that spins and sort of 'detects' how much battery is left is stuck there. Even if i disconnect my charger it stays there.
So i did what's natural and battery pulled. Did that, reconnected my phone, still the same thing. Now i tried multiple times to get it to turn on and what not but it won't. It gets stuck at the samsung boot logo, no idea why.
So i've decided to call it a night (3 am here, work in the afternoon) and hopefully this thread gets seen by someone who knows how to deal wth this.
TL;DR Clean re-flash of the same daily driver (BoneStock 1.1.4) and let my phone die because I realize I never let it die. Once it does, it get stuck at both the Samsung boot logo, or the animated battery charge circle. I tried accessing recovery, and while I see the little blue message top left hand corner, it just seems to shut itself off, and boot back up only to be stuck again. I have no idea what happeend, I never mess with system functions or any thing of that sort.
The only real solution I see if restoring to stock firmware through Odin? Hopefully that will work, but anyone else experience this before? or something similar and can shed some light on this weird situation?
Thanks in advance!
EDIT: I apologize for the bad grammar, I've been trying to figure this out for the past 2 hours, and it's very late right now.
FriendlyNeighborhoodEnt said:
There's no need for n extensive backstory because rooting, flashing, etc I am pretty familiar with, having first rooted the old HTC Thunderbolt.
Now here's what happened:
I have quite a few roms for the S4 but the BoneStock 1.1.4 rom by Andybones always kept bringing me back. I pretty much settled for that one as my dail driver and kept it so for at least 2 months.
Recently in the past week i started getting notifications on my internal sys memory almost out. So i check and realize that my Google Play Music is almost at 6 gb, so I decide to wipe my entire phone just to give it a fresh new flash. Flash goes well, fresh install. I hardly have the time to let my phone die, so I usually just charge it regardless (I have a 5200 mAh extended battery) but this time I decided to let it die. Once it did, i put it to charge immediately and thats when i noticed something was wrong. It was stuck at the battery logo, the animated one that charges while your phone isn't on yet? Well the circle that spins and sort of 'detects' how much battery is left is stuck there. Even if i disconnect my charger it stays there.
So i did what's natural and battery pulled. Did that, reconnected my phone, still the same thing. Now i tried multiple times to get it to turn on and what not but it won't. It gets stuck at the samsung boot logo, no idea why.
So i've decided to call it a night (3 am here, work in the afternoon) and hopefully this thread gets seen by someone who knows how to deal wth this.
TL;DR Clean re-flash of the same daily driver (BoneStock 1.1.4) and let my phone die because I realize I never let it die. Once it does, it get stuck at both the Samsung boot logo, or the animated battery charge circle. I tried accessing recovery, and while I see the little blue message top left hand corner, it just seems to shut itself off, and boot back up only to be stuck again. I have no idea what happeend, I never mess with system functions or any thing of that sort.
The only real solution I see if restoring to stock firmware through Odin? Hopefully that will work, but anyone else experience this before? or something similar and can shed some light on this weird situation?
Thanks in advance!
EDIT: I apologize for the bad grammar, I've been trying to figure this out for the past 2 hours, and it's very late right now.
Click to expand...
Click to collapse
I would tend to agree odin the full wipe stock image back and start over
FriendlyNeighborhoodEnt said:
There's no need for n extensive backstory because rooting, flashing, etc I am pretty familiar with, having first rooted the old HTC Thunderbolt.
Now here's what happened:
I have quite a few roms for the S4 but the BoneStock 1.1.4 rom by Andybones always kept bringing me back. I pretty much settled for that one as my dail driver and kept it so for at least 2 months.
Recently in the past week i started getting notifications on my internal sys memory almost out. So i check and realize that my Google Play Music is almost at 6 gb, so I decide to wipe my entire phone just to give it a fresh new flash. Flash goes well, fresh install. I hardly have the time to let my phone die, so I usually just charge it regardless (I have a 5200 mAh extended battery) but this time I decided to let it die. Once it did, i put it to charge immediately and thats when i noticed something was wrong. It was stuck at the battery logo, the animated one that charges while your phone isn't on yet? Well the circle that spins and sort of 'detects' how much battery is left is stuck there. Even if i disconnect my charger it stays there.
So i did what's natural and battery pulled. Did that, reconnected my phone, still the same thing. Now i tried multiple times to get it to turn on and what not but it won't. It gets stuck at the samsung boot logo, no idea why.
So i've decided to call it a night (3 am here, work in the afternoon) and hopefully this thread gets seen by someone who knows how to deal wth this.
TL;DR Clean re-flash of the same daily driver (BoneStock 1.1.4) and let my phone die because I realize I never let it die. Once it does, it get stuck at both the Samsung boot logo, or the animated battery charge circle. I tried accessing recovery, and while I see the little blue message top left hand corner, it just seems to shut itself off, and boot back up only to be stuck again. I have no idea what happeend, I never mess with system functions or any thing of that sort.
The only real solution I see if restoring to stock firmware through Odin? Hopefully that will work, but anyone else experience this before? or something similar and can shed some light on this weird situation?
Thanks in advance!
EDIT: I apologize for the bad grammar, I've been trying to figure this out for the past 2 hours, and it's very late right now.
Click to expand...
Click to collapse
When you see the blue text for recovery do you continue to hold the buttons down until you see the recovery screen? If you take your fingers off it will do what your describing. If you can get into recovery reflash your ROM.
Sent from my Nexus 7 using XDA Premium 4 mobile app