So, I rebooted my phone this morning (old habits die hard) and it made it loaded...then froze on the lockscreen. There was a slight graphic glitch on the screen too. So, I pulled the battery and rebooted again. And the same thing happened. So, I tried again. And it just hung on the boot animation. Not "boot looping", per say, since it never started over, just going on and on and on. Tried clearing the cache and rebooting. Nope. Finally, I tried wiping the caches and system, reflashed my ROM, and watched as nothing changed.
So, I accepted my fate, made a nandroid, wiped everything, and started fresh. This isn't a big deal, EXCEPT I lost all the info from my expense manager app (I like to know how much I spend on beer each month). Now, I've tried pulling the data from the nandroid (with Nandroid Manager, Rom Toolbox Pro, and Titanium Backup) to no avail. I was able to pull the data out for a couple other apps, but not the one I really want.
So, is there anything I can do?
Related
Last night, out of the blue, my Dinc started going to a black screen requiring battery pull to get to anything interactive, then soon after would go back to black screen again. All that would show up is botoom hard buttons and top notification bar but all buttons, including power button were useless. Required battery pull. I am on root running SkyRaider but this happened when I tried to flash Froyo ROM also. I do use Titanium Backup. When you get this far into rooting and trying new ROMs its really hard to tell where the problem actually is. I want to use Titanium, thats why I have it, it would suck to not be able to get my apps back.
Hope someone has some insight to this, or at least how to troubleshoot it.
Wipe
I would use titanium to back up apps no data though. hopefully you have a nandroid you can flash back to, but first do titanium then clockwork and wipe/ factory/ wipe cache/ then advanced and wipe dalvik, basically wipe everything except your sd card. then reflash your nandroid or any rom that you know works. make sure the rom is already on your sd card though.
This really sucked. Tried everything, even nandroid was blacking out on early interactions. I had to wipe everything, including onboard and sd card then start completely from scratch. Good thing I had some screenshots to remember some apps, but it took hours to reload eerything. Best thing I can figure was it was a corrupt file somewhere and unable to weed it out I had to start from scratch.
Prior to that I did all the wipes and did attempt nandroid, none of that worked. Now I'm making backups of my SD card and onboard mem to avoid having to wipe that all over again. PIA!!!!
It almost sounds like your screen is going out. Do you see image tearing before it blacks out? What kernel are you using? DO you have it OC'd?
this is exactly what my phone started doing yesterday! so u wiped ur sd card and it all worked again?
This evening I was playing around with my Evo and got thinking, "I really like how everything is running right now! I've been running SteelH I.2 ROM stable for a few weeks, launcherpro, all my homescreens setup... perfect! I should take a backup."
I reboot into recovery, take a nandroid backup, then go to reboot the phone. Backup completed without any errors, but the phone would not restart. It sat at the white HTC and would not budge. I removed the battery several times and rebooted, but nothing. I could still get into recovery, so I wiped data, cache, dalvik and attempted to reboot. Again, nothing... just sat at the HTC screen. At this point I was thinking, "great... gonna have a long night ahead of me troubleshooting this one." I restored the backup I had just taken about 30 minutes earlier, but wasn't very confident that it would help at all... reboot, and after a few seconds, my boot screen starts loading!
So, here is what I am wondering.... I had not done any "hacking" since the last reboot... just installed/uninstalled a few apps from the market. What could have caused my phone to react like this? Also, if it wouldn't reboot in the first place, why did restoring the backup work? I had just taken the backup a few minutes earlier....
thanks!
Well, that certainly is unique. I've had problems doing nandroid back-ups (recovering from and creating them) before but it always booted just fine no matter what happened. Maybe there was a small software error that was fixed when you recovered.
Either way, I wouldn't worry about it. Recovering a nandroid back-up = problem got deleted.
That's why I tell everyone to nandroid before doing anything
Before I went to sleep last night I decided to backup my phone via recovery. After it backed up I rebooted and I had no service and a service called com.phone or something like that would force close every 5 seconds. I went back into recovery and reflashed CM7 and it bootlooped. I went back into recovery and restored a backup from the day before and it worked flawlessly. I hadn't changed any type of settings, I had just installed the new Swiftkey Beta and Robot Unicorn Attack between the 2 backups. Through trial and error and many reboots into recovery I found out that it is the data portion of the backup that was causing the problems. Does anyone know why this happened? I am a little nervous about doing another backup for fear of not being able to use my phone.
CM7 Stable
Incredikernal (latest)
hboot .92
3.0.0.8 recovery
I suspect the backup had nothing to do with it. I'd bet you would have had the same problems after a simple reboot.
As far as I know, a nandroid backup simply reads from the phone and writes to the SD. I don't see how it could have changed anything on the phone itself.
That's what I thought. I can't remember if I had recently rebooted at that point but after getting the phone working through a restore of the previous backup I tried one last time and restored the backup that had caused the problem and the problem persisted.
How much free space do you have on data/data?
Sent from my ADR6300 using XDA App
I'm on an EVO 4G running Fresh 3.5.0.1 with Netarchy Toastmod 4.3.4 cfs havs-less no sbc. I'm currently using ClockworkMod recovery 2.6.0.1.
Last weekend, I wanted to try Synergy with GodMode. I don't know if it wasn't in the thread when I read it (I see the thread's been updated since my attempt), or if I just missed it, but either way, I was unaware that I couldn't install the GodMode ROM with ClockworkMod.
So I did a Nandroid backup and attempted install (I'll admit, I initially forgot to wipe data/davlik/cache). It seemed to install fine, but then couldn't make it past the boot splash. So I figured I'd cut my losses and just restore my backup. After restoring, it once again got stuck at the bootsplash (never had this issue in the past). And when I say stuck, I mean I let it sit at the boot splash screen for 5-10 minutes, pulled the battery, repeated (including wiping everything), and it could never get past it. To get the phone working again, I had to restore to a much earlier Gingerbread Deck backup that I had made while fooling around with that ROM, then I was able to restore the most recent backup without issue.
Fast forward to this evening. I figured I'd try again, but now I know I need Amon_RA's recovery. So my plan was to do another Nandroid backup, install Amon_RA, and try Synergy with GodMode. I never made it past the first step... after creating the backup (no changes were made, just the backup created), the phone wouldn't progress past the boot splash. I had to go to an earlier restore point (last weekend's) to get the phone to work. Tried restoring today's backup after getting it to work on the old backup, no luck.
Thinking perhaps the attempted GodMode install messed something up, I did a fresh install of Fresh 3.5.0.1 (pun semi-intended), fresh install of my kernel, and then tried restoring the most recent backup. Once again, couldn't get past the boot splash.
I feel like something is seriously wrong, and I don't feel comfortable going into recovery to make any changes until I have some insight into what the issue is.
To make matters worse, I rely on 4G tethering for internet, and have no landline, so if the phone is bricked while trying to resolve this issue, I'll have no resources to get help.
Any help is GREATLY appreciated. I've searched, but it seems that the problems everyone has that are like this occur immediately after changes are made and are remedied by wiping data/davlik/cache. I made no changes this evening, and wiped everything multiple times in my many attempts.
Edit: Almost forgot, some things did stand out as I was trying to get it to work.
While whiping Davlik, I was given the line:
E:Can't mount /dev/block/mmcblk0p2
(File exists)
While restoring today's backup:
sd-ext.img not found. Skipping restore of /sd-ext/.
There was a nandroid restore issue using a previous version of twrp that was remedied by restoring nandroid and then flashing the rom over top of the nandroid. Maybe try that
Sent From My Pocket
Ok I had the same problem. I wiped everything three times also wiped dilvak (might have spelled wrong) cache, and wiped battery stats. Then flashed it. It took forever also close to 15 mins. This is what I did I hope it helps.
Just a followup: I decided I could do without restoring to that specific backup (tried restoring it after wiping data a few more times, but oh well). I only installed a couple apps and changed a couple other things since the last backup that worked, so I installed Amon_Ra since it seems to be the consensus that it's a better recovery and made a backup with that... rebooted just fine afterwards.
I've been curious about a few things. For one, is there a "proper" way to restore a backup from TWRP? Should you do a wipe first before you restore, or does that not matter? Let me give an example of an issue I ran into. I have a (Verizon) Galaxy Nexus, and I've mostly stuck to AOKP, but a while back, I wanted to try out a different ROM. This was back when TWRP was on version 2.4.x.x, so maybe it was just an issue with that. But anyway, I made a backup in TWRP, did my wipe, then flashed the new ROM to play around with. I played with the new ROM a little, but ultimately decided I didn't like it. So I went back into TWRP, wiped again, then used the restore function to go back to the backup I made. When my phone rebooted, though, I was dismayed to find that lots of stuff did not restore properly, and I had to waste a bunch of time fixing things that didn't restore. I was under the impression that when you restore, it just returns exactly the way you left everything before you wiped it out?
Also, I'm doing something similar now, on 2.6.0.0 of TWRP. I wanted to try a new ROM, so I made a backup, wiped, flashed the new ROM, played around with it, and decided to restore my previous backup. The backup file was about 7GB. My phone seems to be "stuck", though, in the recovery process. The bar is all the way at the end (the little slanted lines are still moving), and it's been stuck at "Restoring data..." for about 10-15 minutes, now. Is this normal? I don't remember it taking this long before, although I've only ever restored a backup a handful of times. Should I just leave it alone, or should I pull the battery, or what? I don't want to screw anything up, but I kinda need to have my phone working within the next five or so hours...