I have Iced 1.1.4, by accident I wiped all my apps and data when upgrading to it so I wanna go back to my backup of nandroid before to get all my stuff back.
I wiped cache and data and tried to restore the backup, but when I reboot it stays stuck on the MyTouch 4G splash screen. I've searched the forums and haven't found much of a solution for this. Any help would be great, thanks.
BTW battery is at 100%
try giving it a few minutes to load up
yes, I would recommend giving it a few minutes before loading up. Typcially on first boot it can take a few minutes. Only issue I have ever ran into with nandroid is when I renamed it and left a space, had to rename it again and was fine.
Related
Alright, so here's the issue. I searched and could not find anything close to this...
I have stock JH7 installed. Installed Clockwork (via Rom Manager,) backed up my ROM, Metamorphed a theme, didn't like the theme, tried to use Clockwork to restore from my backup. Clockwork would go through all of the files, but when it gets to "ReceivedFiles," it just hangs. I let it run through the night, approximately 5 hours, and in the morning it was still in the restore process at this same step. I knew something was wrong, so I unplugged, removed battery, and booted it up. My phone just sat at the Galaxy 'S' screen and would not start up.
After several more attempts with 2 different backups (always hanging at the same place) I finally wiped data, cache, & dalvik cach, then booted it up. All was well and working stock. Then I shut down, booted into recovery, opened Clockwork, and attempted to restore again. My phone is currently sitting at the same step as before.
Any clues? I've attached a picture of its screen.
Did you pull the battery out? Mine is stuck as well....was updating to Serendipity 5.1.
Finding update package...
Opening update package...
installing update....
And it's been there for over half hour
I pulled it and can get back in the phone just fine. It seems to still get stuck there though.
Hi
I installed Thiaz ROM and the ICS theme which there is a link to on his V2.4 page. All was running fine and dandy for a day. I installed all of my programs, apps, etc, and used App2SD to move some of them to the SD. Each time I did this, it said 'failed' the first time and then allowed them to be moved on the next. I rebooted the phone a couple of times and never had any problems. After I had got things set up as I wanted them, I rebooted into CWM and did a new backup. I then rebooted and went into bootloop.
Cleared data, dalvik and even battery stats. Tried fixing permissions. Nothing worked at all, still boot loop. Did a factory reset and restored the backup and still bootloops.
If I restore to the original backup from when I first put on the ROM (no ICS theme), it works OK. Then after a few hours and after I have turned on and off successfully a few times, I get the old bootloop again. I have not messed around with any system files, etc. One time it was after I moved a file with File Expert but I uninstalled that programme and haven't used since.
Any help or suggestions would be very gratefully received as I don't really want to go back to the stock V21a but I can't be doing with setting up everything on my phone from scratch every day either!
I hope someone can help me.
Any ideas what might be causing this, or how to fix it?
If I have to power off my phone, when I turn it back on, it is perpetually stuck on the boot screen animation. The only way to move past that is to go into recovery and wipe data, davlik, and cache. Then I have to reinstall everything. But inevitably, it will do it again when I restart my phone.
I'm running the current ota version and rooted.
It shouldn't just happen randomly unless there's a hardware problem. Since you have root access, you might have done something that caused it. I suggest re-flashing factory images and then see if it still happens.
I did flash the factory image on Tuesday night after it happened the first time. I'll try it again when I get home this evening. Mayb there is something corrupt in my titanium backup file I restored a few programs from.
udrunner said:
I did flash the factory image on Tuesday night after it happened the first time. I'll try it again when I get home this evening. Mayb there is something corrupt in my titanium backup file I restored a few programs from.
Click to expand...
Click to collapse
Make sure you don't restore system apps.
udrunner said:
I did flash the factory image on Tuesday night after it happened the first time. I'll try it again when I get home this evening. Mayb there is something corrupt in my titanium backup file I restored a few programs from.
Click to expand...
Click to collapse
That might be it. But a fresh clean install is the way to go.
Sent from my Nexus 5 using Tapatalk
Somehow my phone is bricked, although I still am not sure if it's because I actually did something wrong or it just decided to brick itself out of spite. Here's the rundown of events:
This past August I rooted my phone and installed cm-10.2. I made a backup of the stock rom beforehand (which for some reason is dated from 1970). Since then there have been a bunch of bugs, but nothing super major.
Today I decided to upgrade to cm-11, so I backed up everything important to my PC and used the auto-updater. I got a Status 7 error and the installation didn't complete, and I got stuck in a reboot loop that kept returning me only to the bootloader. I read on another forum that the problem was probably my CWM version (6.0.1.2 instead of 6.0.1.3). Anyway, I tried restoring one of my backups, but the bootloader said the folder was empty and no backups were found. I ended up reinstalling cm-10.2 and gapps from the same zip files I used months ago. This let me properly boot up my phone, but for some reason the google play store still wasn't working. I did a simple reboot and it started working again, so I downloaded rom manager and updated cwm. Rebooted into bootloader, made another rom backup, and tried again to install cm-11. Same error, install aborted. This time, however, my backups magically reappeared (along with an extra mystery backup that had today's timestamp but was ~10 hours in the future), so I restored the original (1970, stock rom). Things boot up fine.
I decide to try installing cm-11 one more time because at this point I assume that if it fails again I can safely restore a backup or at the very least reinstall cm-10.2. It fails again, but this time, when I try restoring any of my cm-10.2 backups I get a DM5 mismatch error and it immediately stops. Restoring 1970 is different, it starts recovering but then halfway through says "error restoring /system" or something like that. So now I'm left with no choice but to reinstall cm-10.2 from the same zip file again. Only this time, booting up only shows the cyanogenmod logo forever. I go back into bootloader and my backups are once again suddenly not recognized. I make a new backup of my broken phone to see if it will make the folder show up. I reboot, and now that new backup is the only one that does show up. Trying to restore gives me a DM5 error. I've now tried reinstalling cm-10.2 several times, but my phone will never get past the cyanogenmod logo. I'm out of ideas for how to get my phone to work.
My questions:
1. Any idea how to unbrick my phone? I have not done any factory resetting because I was worried it would erase my backups and also I don't really see how it would help.
2. Does anyone have a backup image I could use? I don't have mine stored anywhere but on my phone's internal SD, but I could maybe try loading one from my external SD if I had one.
3. What did I do wrong here? From my viewpoint it seems I basically tried the same thing twice and got different results. Is there something I'm missing?
4. If I get a new photon q, how the hell should I go about installing cm-11? I know people have gotten it to work before. Which version are you using?
Thanks for any and all help
I'm guessing you don't have a backup of stock?
Have you tried restoring stock everything using RSD Lite?
Also, how long have you let the phone sit? If the phone requires a 'fsck' (file system check) on you /data partition, you could be waiting for an hour or more at the boot animation.
I do not have any backups stored externally. I'm not familiar with RSD lite, could you explain and/or link? I have only left my phone for about half an hour at the most before hard rebooting it. I'll let it sit for a couple hours and see if it does anything different.
DRH48 said:
I do not have any backups stored externally. I'm not familiar with RSD lite, could you explain and/or link? I have only left my phone for about half an hour at the most before hard rebooting it. I'll let it sit for a couple hours and see if it does anything different.
Click to expand...
Click to collapse
See this thread for information on how to restore stock... always a good idea to know how to reset the phone back to a complete stock configuration
I just tried to do a nandroid restore. It's hanging at the restore system step for about 40 minutes. Is this normal? I don't remember other restores I have done taking this long.
I don't think that it should take this long for the recovery process.
Yeah I agree. I guess I'm not sure what to do now. Pull the battery and see if I can get into recover and flash one of the other backups. Hopefully I can still get back into TWRP.
As scary as it is. I had to pull the battery and it hung at the logo screen. But was able to boot into TWRP and the second restore worked. It's first time in 7 years that I have nandroid restore just hang on me.
Sent from my SAMSUNG-SM-N900A using Tapatalk