Hi everyone, first post here. Looked around and haven't found an answer to this yet. Phone is EVO 4G
Have flashed this rom multiple times and the rom itself functions well with little to no lag. The problems arise if I do anything in recovery. Tried flashing a kernel (goldenmonkey) and wound up with endless force closes. Did a nandroid restore to a state just before I had flashed the kernel and the force closes continued. Shouldn't the restore have returned everything to the previous state with the stock kernel as that was what I had installed with the rom? That's what always happens with the other rom I have saved on my SD card.
Just a few minutes ago, I reflashed the kingedshooter rom, installed apps, etc. Was planning on trying another kernel, but forgot to put the zip on my SD card. Anyway, I did a nandroid backup (with everything working fine) and as soon as I rebooted the phone, I could not access the settings and the power control widget I had loaded on one of my home screens was gone. I couldn't make phone calls, and would get a force close if I tried to access any settings. Tried to restore to my most recent backup where once again everything was working perfectly and am still having the issues I just described. Anyone know what's going on? Thanks.
Anyone that reads this, please disregard the above. Made a nandroid after installing a theme and kept trying to go back to that. Thanks.
Hi Folks,
I am running Infinity 1204. I love it, stable as can be. Think I am gonna stay with this version after reading all the problems people are having with the 1211 version.
I am on CWM v5.0.2.7 and when I go to do a nandroid backup, it halts with an error sayin 'unable to create image of' on time it was system and the other was of data.
Has anyone else encountered this? Is it possible due to the ext4 formatting? any pointers?
Also: I have successfully done a backup with rom manager. It seems as though cwm sees this as a valid backup for restoring. Does anyone know if you can use a rom manager backup to restore in CWM?
I'm not much help, but I have successfully restored to CWM backups on 4.0.1.4 on Gummycharged FE 2.0 with IMO 13.6 kernel and I believe Humblecharged 5.0 RC2 with IMO 4.0 kernel.
Check the Infinity ROM thread from known issues with CWM 4.0.1.4. You may be able to use that version to create and restore backups. To my knowledge, people have successfully used the new version of CWM with Infinity to create and restore backups.
I don't know this for certain, but I haven't heard of a single successful instance of ROM manager working on this phone regarding backup and restore. I suspect it will not work, although it would be interesting to see.
Even if you soft-brick your device, you could easily get back to working order via Odin. I've soft-bricked a few times- as long as you can get into download mode, you should be fine.
You could try P3Droid's Odinmaker from the market. I haven't really used it much because I have been able to restore from CWM.
Yeah ... I'm pretty comfortable with Odin and CWM for flashing and installing zip files and such. I've had this phone since the weekend it hit the market and I have recovered from numerous brick jobs in learning my way around the phone.
But I've never played with nandroid until now and the phone hasn't completed a nandroid backup the couple of times I've tried it. Was just wondering if it was an issue maybe with this combination of ROM and CWM.
Edit: Now that I'm home I decided to try it with the cable plugged into desktop to ensure max power source. It goes through the whold backup process and at what I would assume is the end of the process it pukes up;
"Error while making a backup image of /datadata!"
But!! If I go back into the restore section of cwm, it does show a copy with today's date that I just performed. I just don't know if it is a valid full backup with the error I got.
I have a Verizon Galaxy Nexus (rooted stock 4.0.4). I decided I would test out Clockworkmod touch recovery before doing anything too serious with it. So, I made a backup, rebooted, deleted an app, went back to recovery, and restored my backup. But, while it was restoring my data, it suddenly stopped and said "Error while restoring /data!" I rebooted and, after waiting through a really long boot, it booted into a semi-reset version of my phone. All of the apps claim to be installed but will not start.
So, thinking it could be a touch recovery issue, I flashed an older version of clockworkmod recovery and tried restoring after clearing my data, cache, factory reset, and Dalvik cache. Still, the exact same thing happened. I also tried restoring older backups, but the exact same thing happened.
What is going on, and what should I do? Thank you for your time.
Eric_Eric_Eric said:
I have a Verizon Galaxy Nexus (rooted stock 4.0.4). I decided I would test out Clockworkmod touch recovery before doing anything too serious with it. So, I made a backup, rebooted, deleted an app, went back to recovery, and restored my backup. But, while it was restoring my data, it suddenly stopped and said "Error while restoring /data!" I rebooted and, after waiting through a really long boot, it booted into a semi-reset version of my phone. All of the apps claim to be installed but will not start.
So, thinking it could be a touch recovery issue, I flashed an older version of clockworkmod recovery and tried restoring after clearing my data, cache, factory reset, and Dalvik cache. Still, the exact same thing happened. I also tried restoring older backups, but the exact same thing happened.
What is going on, and what should I do? Thank you for your time.
Click to expand...
Click to collapse
There may have been a corruption in your data backup. Just delete that backup and make a new one.
Nope, I tried all three of my backups and had the same problem with all three. Plus, I can't simply make a new backup. I tried restoring to the backup and lost my stuff because it didn't finish restoring my data.
I'm having some issues with cwm too. Sometimes when I'm trying toi recover, it says "md5 mismatch", maybe its a linked problem?
Sent from my GT-S5830 using XDA
rommanager
Install rommanager.apk premium and, to me is to solve the problem
So, I think I figured it out. Apparently, I only get this error when my backup contains more than a certain number of apps (or possibly the /data is over a certain size). Granted, I do have over 350 apps, but why is CWM Recovery messing up while trying to restore a big backup? It really should not affect it, but it seems to. So, I will be backing up with Titanium for my apps, and making nandroid backups only when I have under about 350 apps installed. If anybody else has any insight, please share it with me. Thanks.
The Answer (I am pretty sure...)
Okay, I think I finally figured it out. The reason it was not restoring properly was because I had about 350 user apps installed. My guess is that, while restoring, the recovery (CWM recovery in my case) puts the /data onto the RAM, and the RAM is not large enough to hold that much at once. I deleted a lot of apps, backed up in CWM recovery, and restored back to the backup, and everything worked flawlessly. I am surprised that no one has ever had this problem. So, in the future, I am making Titanium backups of all my apps, batch uninstalling a bunch of them from within Titanium (so that I have under 300 at the most), and then making a backup. Then, I can flash a new ROM, recover, or whatever and finally use Titanium to put all my apps and data back. I just thought I would post this in case anyone else ever finds this problem. It was really frustrating for me, but the insufficient RAM theory seems to explain it. Post your thoughts on the matter.
Eric_Eric_Eric said:
I have a Verizon Galaxy Nexus (rooted stock 4.0.4). I decided I would test out Clockworkmod touch recovery before doing anything too serious with it. So, I made a backup, rebooted, deleted an app, went back to recovery, and restored my backup. But, while it was restoring my data, it suddenly stopped and said "Error while restoring /data!" I rebooted and, after waiting through a really long boot, it booted into a semi-reset version of my phone. All of the apps claim to be installed but will not start.
So, thinking it could be a touch recovery issue, I flashed an older version of clockworkmod recovery and tried restoring after clearing my data, cache, factory reset, and Dalvik cache. Still, the exact same thing happened. I also tried restoring older backups, but the exact same thing happened.
What is going on, and what should I do? Thank you for your time.
Click to expand...
Click to collapse
its better to use titanium backup application for you.user friendly and worthy..
The past few times I have restored a backup, the phone acts like it's the first time I've used it. Whats weird is all my apps are there less the data and I have to sign into my account again. Luckily I use Titanium Backup, so I don't lose data. But my screen setup is gone, my ringtones are different. This has all happened once I went to 4.2.2 with Carbon. I am constantly getting mismatched md5's upon restore (I fixed that). I have used CWM since Droid 1 days and never a problem!
Any suggestions?
Something else I just thought of, last week I couldn't get a gps fix so I flashed back one recovery and it worked perfectly. (gps, too) Today I tried to restore same recovery and same result apps but no data and screens back to stock.
Is the back up your trying to restore on on 4.1.2?
Surge1223
No all backups I have are 4.2.2
Hi guys, has anyone else encountered that WiFi AP will refuse to work after restoring from a TWRP Backup? (it worked fine when the backup was made). Has happened multiple times to me, at least while running PA (can't remember if it occurred on other ROMs as well).
It simply says "Error" under the setting menu. WiFi also won't work after trying this until a restart.
I've tried the following, none seem to work:
Wipe /System and reflash rom
Reflash Kernel
Try different kernels (including PA stock)
Apart from clean flashing, does anyone have other possible solutions?
I have noticed the same issue multiple times after a restore.
Only way I've found to get it working again is a factory reset then clean install, which a pain in the ass.
five40 said:
I have noticed the same issue multiple times after a restore.
Only way I've found to get it working again is a factory reset then clean install, which a pain in the ass.
Click to expand...
Click to collapse
Yea, clean installing almost ruins the whole point of that backup though (unless you want to restore so you can run Titanium or another app/data specific backup app).
Have you noticed it across roms? Or only on PA?
Thanks for your reply.
Never ran PA.
I ran Stock or Cataclysm for the most part.
But I tried Vanir, Slim, Carbon & Liquid Smooth.
Whenever I would discover a bug in any of those ROM's I would revert back to my Stock Nandroid and the WIFI AP would give me an error message.
I then would have to factory reset and start from scratch to get WIFI AP working again. Deleting the data/wifi folder did not help like some people suggested.