HI there,
I've been jumping back and forth between beanstalk and carbon 4.4.2 roms, with an occasional validus. No issues, making backups, restoring, etc. Today I installed a validus fresh to try to change the boot animation with ROM toolbox. That worked with no issues. I then backed that up.
I then tried to restore my carbon back I'd made before the test, and no go.
I've tried many times installing new and then trying to restore - no go.
I can wipe and install fresh, any ROM, but cannot restore any ROM. Any ideas?
EDIT 1: I deleted ALL backups, did a fresh carbon 4.4.2 install. Rebooted. Rebooted then into recover. Backup to SD card as usual. Reboot. Then tried to restore the backup I'd just made. NO Go. So had to do a fresh install again.
EDIT 2: After fresh reboot, moved my backup to internal storage. Recovery, then attempt restore, no go. Had to do another fresh install.
EDIT 3: After fresh install, I created a backup directly to internal storage (no copy/paste), then wiped everything as usual. Then restore direct from internal - it worked. Going to do a full tibu restore of all apps. THEN backup/restore again, to see if this works.
So now, I'm wondering if my SD card is nuts up somehow. Maybe I'll format that, then start over.
oh, and I'm on 2.6.3.0
newskate9 said:
HI there,
I've been jumping back and forth between beanstalk and carbon 4.4.2 roms, with an occasional validus. No issues, making backups, restoring, etc. Today I installed a validus fresh to try to change the boot animation with ROM toolbox. That worked with no issues. I then backed that up.
I then tried to restore my carbon back I'd made before the test, and no go.
I've tried many times installing new and then trying to restore - no go.
I can wipe and install fresh, any ROM, but cannot restore any ROM. Any ideas?
EDIT 1: I deleted ALL backups, did a fresh carbon 4.4.2 install. Rebooted. Rebooted then into recover. Backup to SD card as usual. Reboot. Then tried to restore the backup I'd just made. NO Go. So had to do a fresh install again.
EDIT 2: After fresh reboot, moved my backup to internal storage. Recovery, then attempt restore, no go. Had to do another fresh install.
EDIT 3: After fresh install, I created a backup directly to internal storage (no copy/paste), then wiped everything as usual. Then restore direct from internal - it worked. Going to do a full tibu restore of all apps. THEN backup/restore again, to see if this works.
So now, I'm wondering if my SD card is nuts up somehow. Maybe I'll format that, then start over.
oh, and I'm on 2.6.3.0
Click to expand...
Click to collapse
Format data & data media with philz & the restore will go. I take it you are on a twrp w/o usb mount?
aviwdoowks said:
Format data & data media with philz & the restore will go. I take it you are on a twrp w/o usb mount?
Click to expand...
Click to collapse
Ok, so time to demonstrate some noobness.......... format with "philz", what does that mean? I am on twrp, not sure what w/o usb mount means. When restoring, I always "MOUNT SYSTEM". is that what you're asking?
Sorry for the off topic but where do you find kitkat carbon ??
Envoyé depuis mon XT925 avec Tapatalk
spart'84120 said:
Sorry for the off topic but where do you find kitkat carbon ??
Envoyé depuis mon XT925 avec Tapatalk
Click to expand...
Click to collapse
Assuming I'm allowed to post a link............
http://www.droidrzr.com/index.php/topic/34591-romxt926unofficial442carbon-kk-01-10-14/
So, I backed up a full version of Carbon to internal. rebooted, then recover. Wiped the thing silly, and then was able to restore with no issue.
I'll wait to see what the philz / twrp step is before going any further.
EDIT: Sorry, couldn't wait! With everything clean, I backed up to ext. card - and it restored fine. I think I may have done something to whack the backup(s). All seems fine now. Go figure.
Related
So I just switched from Prime to Revolution ICS. I made a nandroid before I flashed, as well as a full system+data backup in TitaniumBackup, but when I went back to try to restore TB in ICS there was nothing there. Oh, of course, I thought. I should transfer it to the external SD card so I can get at it after I flash. So I go back in and nandroid restore the Prime ROM, but it hangs on the boot screen.
Is this because ClockwordMod 3.2.0.1 skips the internal /sdcard? Did it then get wiped when I flashed to ICS? Because if so, that seems like a major flaw of which I was never warned when flashing that recovery. I tried to extract TB from my nandroid using unyaffs, but I can't find anything useful.
Any idea if I can get my old TB back?
TB works fine. Look in the TB folder on your internal or external card wherever you have it and if files are there then it should be okay.
Did you flash prime kernel when you restored nandroid? Recovery doesn't make back up of kernel so you need to flash one after restoring backup that's why it probably hangs on boot screen.
Sent from samsung vibrant
Alex9090 said:
TB works fine. Look in the TB folder on your internal or external card wherever you have it and if files are there then it should be okay.
Did you flash prime kernel when you restored nandroid? Recovery doesn't make back up of kernel so you need to flash one after restoring backup that's why it probably hangs on boot screen.
Sent from samsung vibrant
Click to expand...
Click to collapse
Dangit, I was hoping to get back to edit my post before somebody noticed my stupid mistake. Forgot to flash a new (old) kernel when I nandroid'ed. I'm flashing up to ICS now to copy a HC kernel to my external SD, so I can nandroid restore the old ROM and kernel together.
Thanks, though. I'm sure this will fix it. Booting now.
Well, I got restored okay... but the TB folder is nowhere to be found. I'm thinking the SuperWipe script cleared my sdcard (internal) since it's basically empty. Good to know if I ever wanted to, you know, not erase all that stuff that CWM nandroid skips. I'm a little perturbed about that, but it's partially my fault for assuming it all worked the same as my Evo. Live and learn.
Well super wipe script does erase the internal card, at least that's what it says. Personally I always change TB backup folder location to external card as soon as I install titanium.
Sent from samsung vibrant
Alex9090 said:
Well super wipe script does erase the internal card, at least that's what it says. Personally I always change TB backup folder location to external card as soon as I install titanium.
Sent from samsung vibrant
Click to expand...
Click to collapse
As will I, now.
Hello All,
I am new at this "flashing" scene and have a few questions. Could someone please tell me exactly what steps I need to take in order for me to put a newer "Nightly" CM 10.2 on my Verizon Galaxy S3? I hate the idea of having to re-download all my apps each time I get a new ROM. One of the questions I have is exactly what is "Dalvik Cache"?
Any help would be really appreciated.
Thanks,
Bruce
I'm not sure what recovery you have installed, but i use Cwm & I backup my ROM to external sdcard. Flash the new nightly & use advanced restore option & restore data only. Its always worked for me, I just wouldn't do it going in between touch wiz & AOSP
Sent from my SCH-I535 using xda app-developers app
Upgrading CM 10.2 Nightly
sjpritch25 said:
I'm not sure what recovery you have installed, but i use Cwm & I backup my ROM to external sdcard. Flash the new nightly & use advanced restore option & restore data only. Its always worked for me, I just wouldn't do it going in between touch wiz & AOSP
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Hi & thanks for responding! I am using the latest release of CWM. What I'm still not clear on is what steps do I need to take to flash the new Nightly?
Thanks!
Bruce
0 - make sure you've back up your IMEI.
1 - always do a nandroid backup
2- titanium backup (TiBu) to back up your apps
3- back up all your data (music, etc) onto your external SD card.
4 - going from TW to AOSP (or from one AOSP to a different one) always do a clean wipe: cache, dalvik, and factory reset.
Would not hurt to format your internal SD card either.
5 - after new ROM installation, can restore your apps with TiBu - restore apps and data. NEVER use restore system data option!!
.... Unfortunately there's no way to install a new build of ROM without having to reinstall your apps. TiBu makes it easier, but they still need to be re installed
Upgrading CM 10.2 Nightly
epagib said:
0 - make sure you've back up your IMEI.
1 - always do a nandroid backup
2- titanium backup (TiBu) to back up your apps
3- back up all your data (music, etc) onto your external SD card.
4 - going from TW to AOSP (or from one AOSP to a different one) always do a clean wipe: cache, dalvik, and factory reset.
Would not hurt to format your internal SD card either.
5 - after new ROM installation, can restore your apps with TiBu - restore apps and data. NEVER use restore system data option!!
.... Unfortunately there's no way to install a new build of ROM without having to reinstall your apps. TiBu makes it easier, but they still need to be re installed
Click to expand...
Click to collapse
Thank you for the info! I will give this a try once the next Nightly comes out.
I've always dirty flashed nightlies and have never had an issue.
With all due respect I would ignore everyone who has posted in this thread so far (except jbjarko's comment). Not sure if they misunderstood the question or if they just have a lot of extra time on their hands.
If you already have CM10.2 installed then all you have to do is download the newer nightly via the cmupdater app (System Settings / About Phone / CyanogenMod Updates) then after it is downloaded select it and click "update".
It's not a back idea to make a backup once in a while (i make a backup using Rom Manager about once a week), but 99.9% of the nightlies will flash just fine. AND if you ever do have a problem after flashing a new nightly just reboot into CWM recovery, wipe cache and dalvik cache, then re-flash the last working nightly.
The vast vast majority of the time you should never need to redownload a single app or reconfigure anything when going from one CM10.2 nightly to another CM10.2 nightly.
So in summary:
1. Use the built-in cmupdater to update from one nightly to the next
2. Always keep the last working nightly on your phone in case you need to flash back one version (cmupdater saves it on your internal sd card in a folder conveniently called "cmupdater")
3. Occasionally make a full backup (a nandroid) using CWM in case things really get jacked up
'Dalvik cache' can be cleared by going to "Advanced" when you are in CWM recovery
Restola said:
With all due respect I would ignore everyone who has posted in this thread so far (except jbjarko's comment). Not sure if they misunderstood the question or if they just have a lot of extra time on their hands.
If you already have CM10.2 installed then all you have to do is download the newer nightly via the cmupdater app (System Settings / About Phone / CyanogenMod Updates) then after it is downloaded select it and click "update".
It's not a back idea to make a backup once in a while (i make a backup using Rom Manager about once a week), but 99.9% of the nightlies will flash just fine. AND if you ever do have a problem after flashing a new nightly just reboot into CWM recovery, wipe cache and dalvik cache, then re-flash the last working nightly.
The vast vast majority of the time you should never need to redownload a single app or reconfigure anything when going from one CM10.2 nightly to another CM10.2 nightly.
So in summary:
1. Use the built-in cmupdater to update from one nightly to the next
2. Always keep the last working nightly on your phone in case you need to flash back one version (cmupdater saves it on your internal sd card in a folder conveniently called "cmupdater")
3. Occasionally make a full backup (a nandroid) using CWM in case things really get jacked up
'Dalvik cache' can be cleared by going to "Advanced" when you are in CWM recovery
Click to expand...
Click to collapse
Thanks for the props. :good:
Well laid out post.
Thanks!
Restola said:
With all due respect I would ignore everyone who has posted in this thread so far (except jbjarko's comment). Not sure if they misunderstood the question or if they just have a lot of extra time on their hands.
If you already have CM10.2 installed then all you have to do is download the newer nightly via the cmupdater app (System Settings / About Phone / CyanogenMod Updates) then after it is downloaded select it and click "update".
It's not a back idea to make a backup once in a while (i make a backup using Rom Manager about once a week), but 99.9% of the nightlies will flash just fine. AND if you ever do have a problem after flashing a new nightly just reboot into CWM recovery, wipe cache and dalvik cache, then re-flash the last working nightly.
The vast vast majority of the time you should never need to redownload a single app or reconfigure anything when going from one CM10.2 nightly to another CM10.2 nightly.
So in summary:
1. Use the built-in cmupdater to update from one nightly to the next
2. Always keep the last working nightly on your phone in case you need to flash back one version (cmupdater saves it on your internal sd card in a folder conveniently called "cmupdater")
3. Occasionally make a full backup (a nandroid) using CWM in case things really get jacked up
'Dalvik cache' can be cleared by going to "Advanced" when you are in CWM recovery
Click to expand...
Click to collapse
Thanks Restola! This should be very helpful!
Bruce
Restola nailed it.
Sent from my SCH-I535 using Tapatalk 4
Hi, I'm running Cyanogenmod 10.1.3 with the latest cwm installed (6.0.4.3).
I've made multiple nandroid backups before and restored them perfectly fine, but it seems that recently,
1) When I try to backup using the rom manager app, my S3 boots into recovery, but then cwm says:
*date*
E: unknown volume for path [/external_sd/clockworkmod/backup/*the name of the backup*]
Can't mount backup path.
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.
This has been going on for a while, even after the app updated to its newest version (5.5.2.8).
2) When I try to restore a backup, it restores all the way until half of the data is restored. Then it shows:
Restoring data...
Error while restoring /data!
I've tried advanced restore, and only restoring data, but that doesn't work either.
Are these simply all of the app's errors? Or are they something more complicated? Thanks!
aznsensazn29 said:
Hi, I'm running Cyanogenmod 10.1.3 with the latest cwm installed (6.0.4.3).
I've made multiple nandroid backups before and restored them perfectly fine, but it seems that recently,
1) When I try to backup using the rom manager app, my S3 boots into recovery, but then cwm says:
*date*
E: unknown volume for path [/external_sd/clockworkmod/backup/*the name of the backup*]
Can't mount backup path.
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.
This has been going on for a while, even after the app updated to its newest version (5.5.2.8).
2) When I try to restore a backup, it restores all the way until half of the data is restored. Then it shows:
Restoring data...
Error while restoring /data!
I've tried advanced restore, and only restoring data, but that doesn't work either.
Are these simply all of the app's errors? Or are they something more complicated? Thanks!
Click to expand...
Click to collapse
It has something to do with the folders it's trying to restore. You're on a 4.2 rom, so if you really want to get it to work then moving your backups, formatting your SD card, and moving them back on will probably get them to restore properly.
Also I wouldn't use rom manager to make backups, try doing it manually and see if you can get it to backup to the internal or external SD card.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
It has something to do with the folders it's trying to restore. You're on a 4.2 rom, so if you really want to get it to work then moving your backups, formatting your SD card, and moving them back on will probably get them to restore properly.
Also I wouldn't use rom manager to make backups, try doing it manually and see if you can get it to backup to the internal or external SD card.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks! I definitely will try it, just not enough time right now.
BadUsername said:
It has something to do with the folders it's trying to restore. You're on a 4.2 rom, so if you really want to get it to work then moving your backups, formatting your SD card, and moving them back on will probably get them to restore properly.
Also I wouldn't use rom manager to make backups, try doing it manually and see if you can get it to backup to the internal or external SD card.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
It didn't work...
So I have been doing a lot of flashing and I wanted to clean up my phone so I did a full wipe,factory reset and then rooted,unlocked bootloader and flashed TWRP 2.6.3.Then I backed up my fresh image of Samsung Touchwiz.Then I moved my TWRP backup of my Carbon setup into the backup directory created by my initial backup.then I did a restore of that backup.Now my problem is that my directory structure is out of whack.I plug the phone into the PC and all I see is Rocket Player,Android and clockworkmod folders in that order.I can't access Music or set a custom ringtone,those directories are not found.I can no longer see the original backup either,Trying to figure out what I did wrong.Did I need to flash Carbon and Gapps first and then do a restore?I missed a step somewhere just wondering if anyone can shed any light.
Thanks.
When you cleaned house on your internal storage while on TW, everything was in /sdcard. When you flashed Carbon (AOSP JB) Jellybean moved your internal storage to /0/sdcard and everything from TW is sort of hidden from that directory now. You should be able to see it or unhide that data in /data/media, /legacy, or /emulated if you switch back to TW. Idk if you'll be able to find it while currently on AOSP, someone correct me if I'm mistaken.
SlimSnoopOS said:
When you cleaned house on your internal storage while on TW, everything was in /sdcard. When you flashed Carbon (AOSP JB) Jellybean moved your internal storage to /0/sdcard and everything from TW is sort of hidden from that directory now. You should be able to see it or unhide that data in /data/media, /legacy, or /emulated if you switch back to TW. Idk if you'll be able to find it while currently on AOSP, someone correct me if I'm mistaken.
Click to expand...
Click to collapse
Hey man thanks for the reply-I repeated the whole process,doing a complete TWRP wipe as in no OS at all,flashed back to stock,flashed a "virgin" Carbon and Gapps,THEN did my TWRP restore (After a backup of the virgin Carbon).Now everything seems to be working normally.Evernote had to reformat and Swiftkey needed to download languages again but so far so good.
Hope this helps someone in the future-couldn't find any procedures for a restore AFTER doing a Full wipe,starting over from scratch.Now I know,first flash the ROM you will be restoring.
chiadrum said:
Hey man thanks for the reply-I repeated the whole process,doing a complete TWRP wipe as in no OS at all,flashed back to stock,flashed a "virgin" Carbon and Gapps,THEN did my TWRP restore (After a backup of the virgin Carbon).Now everything seems to be working normally.Evernote had to reformat and Swiftkey needed to download languages again but so far so good.
Hope this helps someone in the future-couldn't find any procedures for a restore AFTER doing a Full wipe,starting over from scratch.Now I know,first flash the ROM you will be restoring.
Click to expand...
Click to collapse
Glad you're all set! :good:
Hey Guys!
I'm kind of a noob, so sorry in advance!
Today I wanted to try out the new Q Beta, so I opted in, but before that I made sure to create a TWRP backup, so that I could roll back easily if needed.
Well, after like 30 minutes I realized, that some of my apps won't work properly when using this Q preview. So I went back to TWRP, did a factory reset, then I tried to restore my backup from there. It worked without a problem, but during the boot process it showed me an error like:"AuthFailed..." or something. After that, rebooting back to TWRP I couldn't see my normal folders and stuff. I managed to sideload the latest Pie OTA, it works, but still can't access my internal storage and I only see the wierd folders with scrambled letters and numbers.
I know, that there are multiple mistakes I've made doing this and I should have removed my password... Is there any way to get my stuff back and/or restore that backup? Every available box was checked when creating the backup, I copied it to my PC beforehand, I assume it doesn't contain my pictures etc.
Any suggestion is welcome! Thanks in advance!
hsoma94 said:
Hey Guys!
I'm kind of a noob, so sorry in advance!
Today I wanted to try out the new Q Beta, so I opted in, but before that I made sure to create a TWRP backup, so that I could roll back easily if needed.
Well, after like 30 minutes I realized, that some of my apps won't work properly when using this Q preview. So I went back to TWRP, did a factory reset, then I tried to restore my backup from there. It worked without a problem, but during the boot process it showed me an error like:"AuthFailed..." or something. After that, rebooting back to TWRP I couldn't see my normal folders and stuff. I managed to sideload the latest Pie OTA, it works, but still can't access my internal storage and I only see the wierd folders with scrambled letters and numbers.
I know, that there are multiple mistakes I've made doing this and I should have removed my password... Is there any way to get my stuff back and/or restore that backup? Every available box was checked when creating the backup, I copied it to my PC beforehand, I assume it doesn't contain my pictures etc.
Any suggestion is welcome! Thanks in advance!
Click to expand...
Click to collapse
The weird folders mean the data is encrypted. As long as the data is safely backed up on your PC you can format the data partition and boot the phone completely once and then go back to TWRP and copy the backup back to your phone and restore it.