Related
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..
Hi
Was running CM10 nightly from 12 Dec. Bluetooth froze while in car. I rebooted phone. It never came back up after booting, just looping Cyanogenmod logo.
Went into recovery, did a Nandroid, restored my previous backup from the 11th. Still looping Cyanogenmod logo.
Got home. Reflashed stock kernel. Went into recovery and flashed CM10 stable after wiping. Comes up with HTC logo, then black.
Tried to go back into recovery. Comes up with HTC logo, then goes black.
Now it lets me into fastboot, and into the bootloader menu, but recovery does not work. Neither does booting normally. Tried reflashing kernel AND recovery (stable TWRP). It just keeps looping the HTC logo.
HBOOT is 1.14.
Help, please. I'm going to destroy this piece of ****.
If all else fails, run a RUU and skip the thread.
yea, just ruu. i ruu'd a few days ago for kicks.
some car chargers and even wall chargers can make ur phone go wonky, my old moto backflip would randomly press buttons if i used a non-motorola charger.
on a side note, i never used the word "wonky" until this forum.
try running "fastboot erase cache"
also try a clean install instead of restoring nandroid, im assuming your also fastbooting the boot.img from all your nandroid backups. if not they probably wont boot.
strange...
I would say ruu and retry as well.. Sometimes accessories can make a phone go haywire.. Besides the phone is not a piece of crap.Roms can never give you complete stability while stock unrooted can.
Yep. Thanks. Had to start from scratch with Sense again. Now on CM10 stable (and stable CM10 kernel). Hopefully it doesn't lose its mind again, I'm going overseas soon. Sigh.
For anyone who has a similar catastrophe - Titanium recovered most (but not all) of my apps from my TWRP backup. I guess my data partition was slightly corrupt. AppExtractor restored my SMS database from the backup too.
I hate phones.
Passa91 said:
Yep. Thanks. Had to start from scratch with Sense again. Now on CM10 stable (and stable CM10 kernel). Hopefully it doesn't lose its mind again, I'm going overseas soon. Sigh.
For anyone who has a similar catastrophe - Titanium recovered most (but not all) of my apps from my TWRP backup. I guess my data partition was slightly corrupt. AppExtractor restored my SMS database from the backup too.
I hate phones.
Click to expand...
Click to collapse
I always export my contact list to /sdcard if a change is made and then backup to google just in case
Passa91 said:
Yep. Thanks. Had to start from scratch with Sense again. Now on CM10 stable (and stable CM10 kernel). Hopefully it doesn't lose its mind again, I'm going overseas soon. Sigh.
For anyone who has a similar catastrophe - Titanium recovered most (but not all) of my apps from my TWRP backup. I guess my data partition was slightly corrupt. AppExtractor restored my SMS database from the backup too.
I hate phones.
Click to expand...
Click to collapse
I'd suggest keeping a boot.IMG and a stock ROM on the SD card along with adb drivers so you can fix it with a computer without downloading anything.
Sent from my Nexus 4 using xda premium
So, the tablets been working fine. It's been running some older version of CM10 unofficial from March of 2013. It would deep sleep every now and then and boot loop, but it's always come out of it. Now, this weekend while out of town, it deep sleeps, so I reboot it and it just boot loops now. I can get to recovery (TWRP) and I've tried re-flashing the zips for the rom and kernel, but I'm not getting any results. It hangs on the circling Cyanogen logo and just keeps spinning in circles. I've tried everything short of factory reset...
This thing was mainly used for games, and I really really don't want to lose the data if at all possible. Is there a way to get this thing to work without a wipe? Flash a different rom over top or something? Any help is appreciated.
Details:
TF101
CM10 Unofficial from March
Tim Kat Kernel 47b
TWRP 2.3.1.1
It is much appreciated! I'll be updating it once I get back into it and am able to back it up. Thank you!!
Hard to say what will fix it. I know a lot of KatKiss users have had data corruption issues during some random reboots and the fix is to turn FSYNC on (zip file in the KatKiss thread). I am not sure if that would fix this issue you had or not, but it has to be flashed before it gets corrupted.
Here is what I would do:
Since a dirty flash is not helping (wipe caches & system and reflash), make a backup of the DATA partition.
Wipe the data, system & caches.
Flash the ROM, kernel and GAPPS.
Boot up, login with your google account.
Go to the Play Store and grab Titanium Backup and the Pro Key.
You can then use TiBu Pro to restore from a Nandroid (it is in the menu under special backup/restore). It works for most all apps and games, but there may be some that do not work. Not much you can do about it.
Well, I'll give that whirl today. I actually have another back up app that I forgot what it's called. My Backup Pro I think? I use it on my DNA and it works well. Will probably just use that for the game data. I plan to get the KatKiss multi window rom after this fiasco is taken care of. Thanks for the tip!
Hi all,
Yesterday I was flashing a theme for the Vemon ROM on the M8. I ended up deciding I didn't like it, so I tried to go back and flash a backup I had made. However, once I flashed the backup, the device wouldn't boot up past the HTC One white screen (it will go past the HTC logo by itself, but then the One appears on the screen and stops there). I have no idea why, as I have made backups before and have had no issues. On the default backup name, it does say KOH Release keys. I don't know if that means anything. I was able to get to recovery and flash the base Venom ROM, but I'd like to know why my backups are not playing nice.
Any and all help regarding this would be appreciated.
Did you try wiping everything before restoring your backup?
Sent from my HTC6525LVW using Tapatalk
I had the same, exact issue. Absolutely no reason why it shouldn't have worked. I made sure the Nandroid copied the necessary partitions/directories and also performed a full wipe before restoring the backup. Same issue. I was on TWRP and I'm pretty sure there is some issue with TWRP.
I haven't attempted to make a backup or restore a Nandroid since, so I don't know whether its still an issue.
ChuckFinley1992 said:
Hi all,
Yesterday I was flashing a theme for the Vemon ROM on the M8. I ended up deciding I didn't like it, so I tried to go back and flash a backup I had made. However, once I flashed the backup, the device wouldn't boot up past the HTC One white screen (it will go past the HTC logo by itself, but then the One appears on the screen and stops there). I have no idea why, as I have made backups before and have had no issues. On the default backup name, it does say KOH Release keys. I don't know if that means anything. I was able to get to recovery and flash the base Venom ROM, but I'd like to know why my backups are not playing nice.
Any and all help regarding this would be appreciated.
Click to expand...
Click to collapse
I tried wiping everything yes. I did a factory reset data wipe first, and then tried installing the backup. I don't know why it did not work. I was eventually able to get out of the boot screen with an volume up and power key combination, but it was more frustrating not knowing why this issue was happening. If anyone knows why this is occurring, I would gladly like to know.