I went for a run yesterday with my phone and it got a little damp. Really only a little. I'm really surprised I'm having issues as it has gotten more wet than this in the past.
When I got back I need to charge the phone but when I plugged it in it wouldn't start charging. I've had that issue before so I pulled the battery, put it back in plugged in the charger to charge while powered off. Needed it to charge fast. Anyway, Tried to boot it again, (running CM9, 0522 nightly) and it was hanging on the boot animation indefinitely.. Tried clearing cache, davlik, battery stats, everything and it wouldn't work. I tried a nandroid backup and it took forever and gave an error while backing up data. I tried again and it threw an error instantly while backing up the bootloader.
I gave up and did a full wipe and tried to reinstall CM9. No luck.
I wiped it again and luckily had a copy of HDRevolution still on the phone so I installed that after running the "super wipe" app for it. It booted to that just fine.
Tried CM9 again and it didn't boot. Freakin frustrating.
Any ideas on what to do here?
If you booted to a useable state, then you don't need to worry about water damage. Download cm9 again and reinstall
Related
Hey all, first time poster. I wrote a real nice explanation of my problem, but i lost it so anyways, i'll keep it short(ish).
The EVO is less than 3 weeks old, running the latest OTA, recently rooted using UnrEVOked 3, nothing fancy. I ran the battery down completely last night (first time since i got the phone) and once i got to a power source, it wouldn't boot correctly. It hangs at the white splash screen, and then finally boots up but won't respond to any touch input.
Also the phone seems to be running exceedingly slow, the boot process takes substantially long than normal once it gets past the splash screen and my live background is freezing and seems to be stuttering.
I launched into the bootloader and i get a "Touch Panel - Fail". LAME!
I'm not sure what to do at this point, whether i should wipe it or go back to stock or what. Any advice would be much appreciated.
UPDATE:
I managed to get the phone into the recovery console, make a back up (i was planning on going back to the stock image) and wipe the dalvik cache and fix permissions. I rebooted and voila! fixed. Hopes this helps any one else who has this problem.
Moral of this story: Travel with a charger.
Another update. It froze up again in the middle of sending a text. I rebooted by battery removal, and it did the same thing again. Super long splash screen and sluggish boot up, no touch response when it finally came up. I booted into recovery and cleared the dalvik cache again. Seems to be working again now. We'll see if it does it again.....
Well, the screen locked up again. I tried going through the whole process again. I wiped the caches and battery stats, nothing. I wiped all the storage and data, booted into a clean stock interface, nothing. Restored the backup image, and then at some point, through all the rebooting and whatnot, it just shut down completely. I can't even get it to the bootloader. I'm really feeling like it's a hardware problem, and i've made peace with sending it back for TEP, but i have no way to unroot it.
Any suggestions? Please......
Theres unroot processes out there. I cant remember where but ive seen them. Mine gets sluggish too, but after a reboot its ok. You cant even get into the bootloader tho. I'm not even close to an expert but.......uh I'd 'lose' it and call the insurance co....
Hi all. I'll try and make this quick.
I went to make a Nandroid backup of my phone after having flashed the newest CM7 nightly build a day or so ago. It was being pretty unstable (lots of force closes), so I decided to switch back to the ROM I had been using before, Myn's Warm TwoPointTwo. Rather than doing it the way I normally by booting into recovery and running the backup there (I know, that's my first mistake), I ran the backup from ROM Manager. The phone rebooted into recovery, began the backup, but then rebooted again, went into recovery and started the backup again (I'm not 100% sure if it had restarted the backup or continued it from a previous point), and then did this one more time. Then it turned off and wouldn't turn on again. When I plug the phone in, no lights come on. I haven't taken the battery out (the last shutdown was about 15 minutes ago). I had about 50% battery life, and the backups never took up more than 5 or 10%, so I'm fairly sure it didn't die in the process.
So, the question is: Am I bricked?
Did u try getting back to recovery to restore?
Sent from my ADR6300 using XDA App
The phone won't turn on at all. Nothing happens when I hit the power button or plug the phone in.
Nevermind! I pulled the battery and put it back in and it booted. Sorry!
xP
Hey guys, so I have this big problem I have never seen before.
My Verizon Galaxy Nexus keeps turning itself off after about 1-2 minutes of turning on. The only way to turn it back on is to do a battery pull. This started when I upgraded the Franco Kernel to the latest version which I think is #350 I believe. I thought it was the kernel at first so I booted into recovery and flashed Tinys Kernel. Needless to say it turned off again. It would make a weird flash transition as the screen would shut off. I then wiped data, wiped cache, wiped dalvik, flashed Muzzys latest ROM, and booted. Then it said the process for Setup was unable to process. I booted into recovery, flashed the zip for SuperWipe, flashed Muzzy's again and it worked. But after 3 minutes right when it was logging into my Google Account through setup, it turned off again.
Does anybody know how to fix this? What a horrible way to start Christmas...ugh
Thanks everyone.
Nevermind. I found the problem. Apparently it seems that the OEM Samsung Extended 2100 mAh battery is shot. It came with my phone at Verizon when I bought it from them the day this phone launched. I put my girlfriend's GNex battery in my phone and it is running no problem. I put the OEM Extended into hers and her phone shut off after 1 minute of being powered on. The battery has about 3/4 full charge. Not sure what happened but it seems the battery is done and I got to get a new one.
Hope this helps out people who have the same issue!
Hi, I have been running JellyTime 4.2 R11 for few weeks now on my S-OFF Desire HD.
Today, I noticed that the light was blinking and battery was low 6%, so I decided to put it into charger, and somehow when I connected it soon I accidently disconnected the charger, and when I put it back, the phone probably crashed or something, since it went black and the white screen with HTC logo appeared and it started to boot again. Now, JellyTime tries to boot, the bootanimation goes fine for sometime but then it gets stuck after "playing" the bootanimation for a while, nothing happens, even if I wait 5 minutes, it's stuck, bootanimation is frozen, no matter do I have the charger connected or not.
So, is there anything I could do, or is reflashing the only solution? I did full wipe when I flashed the ROM.
If you need more information, sure, just ask.
You could try dirty flashing, but if that doesn't work you'll have to reflash.
bananagranola said:
You could try dirty flashing, but if that doesn't work you'll have to reflash.
Click to expand...
Click to collapse
Thanks for the tip, but it didn't help, gets stuck still on bootanimation.
Time to full wipe and flash it again then. Wipe&FlashTime
Happened to me a few times. I suggest a battery pull before anything else. Seems stupid. But it can work in some cases
- Sent from Guy's Super Duper S3
GuyInTheCorner said:
Happened to me a few times. I suggest a battery pull before anything else. Seems stupid. But it can work in some cases
- Sent from Guy's Super Duper S3
Click to expand...
Click to collapse
I did battery pull several times considering that the phone refused to shutdown even when holding the power button for 10 secs, so battery pull was needed every time.
Anyway, it's now running fine when I reflashed.
910263 said:
Hi, I have been running JellyTime 4.2 R11 for few weeks now on my S-OFF Desire HD.
Today, I noticed that the light was blinking and battery was low 6%, so I decided to put it into charger, and somehow when I connected it soon I accidently disconnected the charger, and when I put it back, the phone probably crashed or something, since it went black and the white screen with HTC logo appeared and it started to boot again. Now, JellyTime tries to boot, the bootanimation goes fine for sometime but then it gets stuck after "playing" the bootanimation for a while, nothing happens, even if I wait 5 minutes, it's stuck, bootanimation is frozen, no matter do I have the charger connected or not.
So, is there anything I could do, or is reflashing the only solution? I did full wipe when I flashed the ROM.
If you need more information, sure, just ask.
Click to expand...
Click to collapse
I have the same problem since a crash on opening the outlook-email App (JellyTime 4.2 R9).
I found, that the "data" partition causes the trouble when booting. Formating the "data" partition with "4ext recovery" fixes boot-freezing. But this is not an option for me as my last (working) backup is a couple of months ago (yes, I know - should backup more frequently...).
I was able to backup the up-to-date "data" partition (with 4ext recovery) but when restoring it (even on an fully wiped and updated system) boot sequence freezes again.
Any ideas???
Many thanks!
Solved the problem with the data-backup. Instead of restoring complete partition the APP "AppExtractor" works fine for restoring data of the partition backuped.
For now, system runs perfectly.
Conclusion:
If system hangs in Boot-Animation use Recovery for backup of up-to-date system. Full wipe system and install ROM of your choise. After that restore SMS, contacts, etc. with "AppExtractor". Apps should be installed from PlayStore as far as possible. "AppExtractor" allows restoring of app, data+app, data.
A few months ago, the display broke on my Moto Z Play. It took me awhile, but I finally got a replacement display.
During the time I was not using it (starting immediately after it broke) it would make the sounds for my calendar notifications as they would come up, and continued to do so until the battery died.
While the battery was dead, I carefully took off the remnants of the old broken LCD.
About two weeks before I got the new display, I plugged it into my computer to see if I could pull any of my information off of it. Unfortunately, I was unable to get it to show up as a drive on my computer so I couldn't pull anything off of it.
Since it had power, it once again made sounds for my calendar notifications until the battery died.
I got my new display in the mail a couple days ago. I set about installing it and after I was done, I charged the battery to 96%. The charging screen appeared perfectly normal. I had no indication that there was going to be any problem when I went to use it until I powered it on at 96%. It looked like it was going to boot up just fine and made it three screens (not counting the triangle screen) into the boot up process and restarted the process.
The last time the phone was fully functional (as well as while it was on with a broken LCD) it was running OmniROM and it has TWRP 3.2.1-0 recovery on it.
First I tried clearing the cache and dalvik cache. That didn't help. Then, as I keep a copy of the zip for that ROM on my SD card, I decided to reflash OmniROM and 8.1 gapps. That didn't help. So, I decided to do a nandroid backup. It got part of the way through the back up and failed at system image. So, I decided to try to backup my data so that I can at least hopefully restore some of it at a later date on my computer or something. Thankfully, I was able to successfully backup my data partition.
After the backup finished, I decided to attempt to dirty flash CosmicOS.
However, I experienced the same boot loop.
I then did a full wipe and did a clean flash of OmniROM.
Still: the triangle screen, 3 seconds of the boot process and then it starts over again.
I am lost as to what to do now.
Help!
Hello?...