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.
Related
Guys
I don't get this at all, can anyone please help out?
I have a Nexus One. Have been running Cyanogen since purchase, upgraded to 5.0.6-N1 few weeks ago. Obviously, root access and all that. Just a few days ago, I backed up the device with nandroid and flashed it with a Enoc theme. That also went well, but I suddenly noticed apparent lack of root access. Apps that require it wouldn't work (like QuickBoot, MarketEnabler). So I wiped the device and flashed with a clean 5.0.6-N1 and restored the backup prior to theme update, but now I cant get the root access back no matter which backup I restore (even older ones).
Any clues on what might have caused it? I cant think of any indications that the theme update might have anything to do with it, but that is pretty much only update I've done to the phone.
Thanks
what recovery image do you have?
Hey, thanks for the reply. I don't have any recovery image.
I just tried booting in recovery mode, wiping the phone and then flashing with the Cyanogen 5.0.6. That should get me a fresh install on which I then apply a nandroid restore of the OS prior to the theme update I mentioned above.
Besides, I see that applying the recovery image via terminal starts with 'su' command. That one gives me 'permission denied' after my problem occured. Its almost as if my phone wasn't rooted at all, which it definetly is.
So right now I'm using CWM to do my nandroid backups. I make one after I make any major updates or changes - call me a worry wort. I also use Titanium Backup.
With doing this, obviously it takes up a bit of room so I offload them to my computer. The issue here is if I do something detrimental and need to restore, I don't know of a way to get the backup files back onto the internal memory since you can't access them via CWM, if that makes sense.
I guess I can simply keep just the latest backup saved on the phone itself but I'm wondering if there's another method that I'm not aware of. Is there a way to get files copied to the internal memory if you can't fully boot into the OS?
Oh and one other question: Does a nandroid backup include every single item? Basically is it a 100% clone of the device or are some thing left out? Basically if I tried a completely different rom and then decided to go back to an entirely different rom, would I simply be able to restore it and be up and running? The last restore I did seems to indicate it does but that was going from different versions of the same rom.
nandroid is a clone of ur system.
diablo009 said:
nandroid is a clone of ur system.
Click to expand...
Click to collapse
Ok that's what I figured; read something a bit ago which seemed to say something else.
So if I want to test a few completely different rom setups and make a nandroid backup of each one, I could essentially swap between them whenever I want by simply restoring them and I'll get back to the exact state as I was at the time they were made? Menus and all?
So apparently a kernel change will not get reverted via nandroid. Anything else? Just tried Entropy's daily driver and apparently it's a no go for me. Restored via nandroid and still freezes during 'X' boot animation.
I was running Infusion 1.1 and made sure to reset the VC O/C back to stock and reboot before updating...
First off, I am unfamiliar with any ADB terms used on these forums.
What I did:
I rooted my Tab 2 (GT-P5113) using Odin and everythng worked out fine. Then I wanted to install a custom rom so I used Titanium Backup to back up my information. The directory com.titaniumbackup was on my SD card, but contained no files. I would think it may have cancelled the backup without me knowing.
I then did a NANDroid backup but I have no idea what happened to it. I then downloaded and succesfully installed CleanRom, but now I realized rooting isn't really what I thought, and is much more complicated, so I removed the cleanrom.zip from my SD. The CleanRom however is still on my system.
Is there ANY type of factory reset that will give me how my tablet was before? Unrooted?
atmon said:
I then did a NANDroid backup but I have no idea what happened to it. I then downloaded and succesfully installed CleanRom, but now I realized rooting isn't really what I thought, and is much more complicated, so I removed the cleanrom.zip from my SD. The CleanRom however is still on my system.
Is there ANY type of factory reset that will give me how my tablet was before? Unrooted?
Click to expand...
Click to collapse
If you go back to the backup/restore section where you made the backup and click on restore you should be able to restore your device with the backup it made. Unzipping the clean ROM should not have deleted the backup. The backup file will have the date you created it. From that point you should have the stock ROM. Then from there you can use Odin to unroot device by following the post in the development area of this forum.
Hope that helps - Let me know
I've had quite an ordeal with my G2X the past few days, and nothing is making sense. I was running CM 7.2 on the 2011 baseband but was getting frustrated with the excrutiatingly slow GPS lock. I read that the 2012 baseband has much faster locking, so I read up on and upgraded my baseband.
So then I had the stock V21y ROM and I rooted and installed ROM Manager, and then flashed CWM. After many, many attempts at getting back to my original config:
Holding down power and vol down just performs a factory reset, it does not start CWM. The only way I can get into CWM is via ROM Manager > Reboot into Recovery. Doesn't matter how many times I flash CWM recovery. This is CWM 5.0.2.0 installed from the Play store.
I cannot restore backups I made with my previous version of CWM. Always results in an error, "Can't mount /system".
I often can't even restore backups made with *this* version of CWM, also resulting in the above error.
I *can* restore some backups I made of the stock ROM, which *isn't* supposed to be possible. From what I read, trying this should result in the above error, "Can't mount /system", but I've never received that error backing up a stock rom.
Attempting to install CM 7.2 from scratch via CWM makes the device unbootable. Boot stops at the second LG boot screen (the wavy LG logo). And since I can't start CWM via power + vol down, I need to flash V21e over USB, root, install CWM, then restore my last saved V21y CWM backup, which is a huge pain.
So, can anyone explain what's going on here? I seem to be able to do things I shouldn't be able to do, and not do things I should be able to do, and CWM doesn't work like it used to or like it should.
Before anything,nvflash cwm on to your phone. If you were able to search and upgrade your base Band. This will be trivial.
ROM manager is fatal for this phone. It almost every time screws the flashing of a ROM or a restore.
Sent from my LG-P999
cricketAC said:
Before anything,nvflash cwm on to your phone. If you were able to search and upgrade your base Band. This will be trivial.
ROM manager is fatal for this phone. It almost every time screws the flashing of a ROM or a restore.
Sent from my LG-P999
Click to expand...
Click to collapse
NVFlash CWM 5.0.2.0
Sent from my LG-P999 using Tapatalk 2
cricketAC said:
Before anything,nvflash cwm on to your phone. If you were able to search and upgrade your base Band. This will be trivial.
Click to expand...
Click to collapse
You are absolutely correct. I totally forgot that this is how I went about it last time. I was able to restore my previous CM7.2 backups after I nvflashed CWM. Thank you both!
Well I can't say that I'm all that impressed with the new baseband. GPS doesn't seem to lock any faster. If anything it seems worse.
CM 7.2 didn't work out of the box either for calls. I had to install a manual update, and receiving calls are still more finicky than they used to be. Sometimes I don't receive calls, or pick up and the audio is garbled.
I also still have a phone freezing issue where messages received at night while the phone is charging almost always lock up the phone's screen. I had read somewhere here that this issue was resolve with the update, or at least less severe, but that isn't the case at all.
Whether these are new baseband issues, or just issues which wouldn't exist if I were just on a stock ROM isn't clear. I may just try stock for awhlie and see.
Just curious if anyone else has experienced any of the following:
I was running CM10.0.0, but had that issue where my NFC was unchecked. So i wanted to restore to a TW ROM so i can check on NFC, restore back to CM10, etc.
I did a backup. Tried to restore my old TW (synergy r73), but got an error in CWM 6.0.1.2:
Error while Restoring /System!
Then i got the same message for ALL of my nandroid backups, including the newest one i made of CM10. I did some searching and found tons of folks with the same issues, but no solutions beyond.. format your SDCard properly (which mine is).
That's fail #1.
After being unable to restore, i just flashed CM10 zip again and started over. I did however use that new Titanium feature where it makes a flashable zip of all of your apps a few days back.
But every time i try to flash the zip, the phone resets in the middle of the install. I've never seem CMW crash and reboot.
That's fail #2.
I ended up restoring apps the old fashioned way, but regardless... any ideas?
Thanks,
Mangler