in the morning yesterday i used the xperia cwm install app to auto magically do a nandroid backup. so i clicked it and left the phone alone for a while. i came back some time later and i was on the lock screen so i thought it must've not done the backup. so i went into recovery and clicked on restore. there were two backups and i chose the one that looked more recent. on checking md5 sums i thought it froze. the stupid habit i have when something freezes is to pull the battery out. so i did it and i thought aww...i must have ****ed up the phone. it went to the android logo and it wouldn't boot. the weird thing is that i could raise the ringer volume, lock the screen, and the white notification light would light up when i opened the battery cover, but hte only thing on the screen was the android logo. i made a nandroid backup after that thinking i could restore it from that. it stayed on the android logo again but the thing that happened was that a screen that popped was the screen it shows when u forgot your lock pattern and it asked for the security question answer. i put it in and the screen went black. i used an old nandroid backup to revive my phone but it's a month old and i was wondering if i can use the one i made during the problem.
Related
Sorry, I'm sure this must have been covered before but a search did not find an answer and I cannot now use my phone at all!
I installed a new ROM last night but had problems with it this morning. Restored a nandroid backup of my previous ROM and it says the install was complete but I cannot get past the first HTC boot screen. Left it on that screen for 10 minutes in case. I also tried an earlier backip I had. Nothing works.
Please help!!
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
So while i was making a backup on twrp, and let it finish and rebooted back to the phone and nothing lit up but my buttons i felt the lockscreen circle and what , and was left stump on what to do so i dusted the old odin out and unrooted blindfolded into download mode and did the proper stuff into stock ICS for T989, and it showed for the stock bootanimation at first, so i was like cool, i'll let it sit and settle before i do anything and it stayed on the samsung sign for about 15 mins, so i did a battery pull and then back to square one on the same problem but now under stock, any ideas on how to bring the light back up, kinda bummed that ive had this phone since it came out and still survived me and i just got it new gear so any ideas could help thank you
the samething happened to me buddy. go to stock recovery and wipe data and cache. and you will be fine.
just fully unrooted and sent it back since i had insurance
I had a similar issue last night.. turned out to be CWM screwing up.. reflashed to the newest cwm and everything worked again
I had Android 4.1.1 installed on a rooted Sprint Galaxy S3 with ClockworkMod. Someone recommended TWRP, so I installed it and used the backup feature, thinking I was completely covered if my foray into ROM flashing on the SGS3 went awry.
So I booted to TWRP, did a "Wipe Data/Factory Reset", and installed the "Blazer" ROM; didn't like it. So I TWRP'ed again, wiped it and flashed CyanogenMod 10.1. Didn't like it either. So I went back into TWRP, did the "Wipe Data/Factory Reset" again, and restored my backup.
When it finished rebooting, it was good for like 20 seconds. I left it on the "lock" screen, and the date reverted back to Dec 24th at some ungodly hour (4 am?). It wouldn't unlock. After less than a minute, it reboots. It kept doing this.
I had a hard time getting back *into* TWRP. I kept getting this weird picture of the battery (?) and the phone kept buzzing every 10 seconds or so. The battery had at least 30% charge. Eventually, by taking the battery out, I was able to get back into TWRP.
Tried it again 2 or 3 more times with the same result. This last time, I immediately got off the lock screen and let it "sit". It has been stable for 10 hours now.
Any idea what's going on?
(If I'm leaving out important information, I apologize. Please let me know and I'll add it.)
Something wrong happened in the restore process. Just make sure that you have at least 80% battery next time.
Sent from my SPH-L710
Thanks.
If I keep restoring it over and over again, is there a chance it will "take" one of these times?
Ok so, check the size of your backups and make sure that they are consistent (for the same ROM types)
I've seen an issue where someones recovery got corrupted, and all restores made with the corrupted recovery were unnaturally small and would bootloop once done restoring
Reflashing your recovery (i recommend through ODIN from a PC) should fix it if this is the issue
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?...