Related
Hey guys,
I have kind of a serious issue right now. I used Touch Recovery 5.8.0.2 and made a full backup today of my whole ROM (2.5GB) before trying out some mods which eventually didn't work. So I decided to wipe and restore the backup I made. No matter what I do I cannot get it to restore my data partition properly. I keep getting "Error while restoring /data!" message, however it does the boot image and system fine but doesn't continue to cache and sd-ext because of the failed data. Whenever I boot it up, some of my apps are missing from the home screen and practically all of them are not working when I launch them (force close). I also get boot up error of Google+ force close, among a bunch of other issues. This is happening even when I try to restore an older backup as well. My device is not working state right now and although I can just restore the stock images to get it working again, it is urgent that I restore my data ASAP! I tried wiping several times and even using the non-touch 5.5.0.4 recovery to restore and same thing keeps happening.
Any help would be highly appreciated!
Please don't tell me my backup is corrupt
Update 1: Eventually I gave up and started from scratch but I have confirmed already this happened on a fresh backup as well, at this time we are trying to figure out what is causing this so I can go back to safely backing up and restoring backups.
Update 2: We have test builds of TWRP Recovery that may have resolved this issue! We need testers!
Please see this post: Link Here
Update 3: We have test builds of ClockworkMod Recovery 6 that may have resolved this issue as well! We need testers!
Please see this post: Link Here
***Always see last few posts on the thread for updates on what we discovered just in case I don't update the OP***
Unfortunately I also have the same error today!
Please help us out.
JayantSparda said:
Unfortunately I also have the same error today!
Please help us out.
Click to expand...
Click to collapse
is your phone encrypted?
are you running stock recovery?
are you running a stock Rom?
have you done a factory reset yet?
Hi Spectre85,
My phone did fine yesterday, I was running AOPK Milestone 3 with FAUX123 kernel.
But when I woke up, my phone looked like it's battery was emtpy.
- When I plugged the phone with the charger, I started the phone again.
- Unfortunately my phone keep looping at the Google screen over and over.
So I pulled the battery and put the battery back again in the phone.
- I went to the bootloader and went to CWM recovery.
Deleted Data, Cache and Dalvike cache.
- Tried to retrieve my backup rom, but keep getting this "Error while restoring /data!" message.
I've tried to install other roms as well, but I still keep getting the bootloop at the Google screen.
Have you guys have any advice for me?
spectre85 said:
is your phone encrypted?
are you running stock recovery?
are you running a stock Rom?
have you done a factory reset yet?
Click to expand...
Click to collapse
For me, no, no (CWM Touch 5.8.0.2), yes (stock rooted 4.0.4), no but my goal is to restore my data not erase it.
I had this happen to me before, what I did was flash a factory image through fast boot and it was fine after.
Sent from my Galaxy Nexus using xda premium
Thanks guys..I flashed the factory image through Fastboot mode and the phone works perfectly again! Too bad I lost all my data, but I'm happier that I have my phone fully functional again
You can't access your backup right? There's no way you can copy the file to your desktop?
mohitrocks said:
You can't access your backup right? There's no way you can copy the file to your desktop?
Click to expand...
Click to collapse
I did copy it. I have full access to the file. Also, just fyi my goal here is not just to get to working state (I'm aware of the stock images) but to actually recover my data. My phone is currently on stock images completely blank and working now.
Fast boot flash the nand images just like u did the stock ones.
Sent from my Galaxy Nexus
bwcorvus said:
Fast boot flash the nand images just like u did the stock ones.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Nanadroid files can be flashed in fastboot? Are you sure? First time I'm hearing this. Doesn't fastboot need .img files? These are .tar files.
Open it up and see if its image...sorry all my recoveries use images.
Sent from my Galaxy Nexus
bwcorvus said:
Open it up and see if its image...sorry all my recoveries use images.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I guess it depends on the recovery version you use. I remember older versions actually had .img files. However 5.5.0.4 and Touch 5.8.0.2 both have ext4.tar files.
Which version of recovery do you use?
If you have root, you can restore your data partition using Titanium Backup. Use "Export from Nandroid Backup" within TB, select the nandroid backup and then select all apps that you want to restore
Immix said:
If you have root, you can restore your data partition using Titanium Backup. Use "Export from Nandroid Backup" within TB, select the nandroid backup and then select all apps that you want to restore
Click to expand...
Click to collapse
Interesting...will this include settings as well like my home screen icon/widget layout, wallpaper, etc?
open1your1eyes0 said:
Interesting...will this include settings as well like my home screen icon/widget layout, wallpaper, etc?
Click to expand...
Click to collapse
Yes. Titanium Backup can restore all your system apps as well as downloaded apps from a nandroid backup. Not as clean as a nandroid restore from CWM but essentially the same thing. But try to see if Titanium Backup can extract your nandroid backup. It all depends on what exactly went wrong with your nandroid backup to begin with. I don't think it restores cache. So not sure about wallpaper.
Immix said:
Yes. Titanium Backup can restore all your system apps as well as downloaded apps from a nandroid backup. Not as clean as a nandroid restore from CWM but essentially the same thing. But try to see if Titanium Backup can extract your nandroid backup. It all depends on what exactly went wrong with your nandroid backup to begin with. I don't think it restores cache. So not sure about wallpaper.
Click to expand...
Click to collapse
You're right. This works great for restore data to select apps (got my notes and game saves back). I think the icon layout is held in the launcher settings, I'm about to try and restore the data to the launcher app and see what happens. I'm making a CWM backup of first of my current state (that's assuming this backup will actually work).
EDIT: Yes! That did it! Widgets position weren't saved but it's ok I only had a few so I manually put them back. Thank you! I never knew TB had the ability to work with nandroid backups.
I guess this now just leaves me figuring out what went wrong with the CWM backup. It happened twice (I have two backups from the same day that won't restore). Does anyone else use CWM Touch 5.8.0.2 and have successful backups? I would experiment to see if it works now but I don't want to end up with a corrupt backup and redo everything again.
Yes with me its the same thing my data its corrupt is even worse every time I do a nanobackup and restarted my phone the phone freezes on the boot logo and I have to go back to recovery trying to use my backups but I can't so I have to flash a new from again and start from the beginning again!!!! Anybody here has the same experience with that ???
So AGAIN, I'm having the same issue. This time on a recovery 5.5.0.4 that used to work for me when I originally got my phone. I think either my data partition might be too big or something but this really needs to fixed pronto. Anyone know how to contact Koush directly in regards to this matter?
i made a nandroid backup using twrp...i flashed a different rom didnt like it..when i went to restore my nandroid it restored the previous rom i made a backup of but no apps data or settings restored?? is this a known issue with gs3? i couldnt find anything in the forums??
rbarcenaslp said:
i made a nandroid backup using twrp...i flashed a different rom didnt like it..when i went to restore my nandroid it restored the previous rom i made a backup of but no apps data or settings restored?? is this a known issue with gs3? i couldnt find anything in the forums??
Click to expand...
Click to collapse
I have not seen this problem. TWRP will only restore what was backed up. Are you sure that the data was backed up? Go to the folder where your backup is saved... do you see a file "data.ext4.win" in addition to the "system.ext4.win". If no data file then the data partition was not backed up.
If the data backup is there but you are still not seeing the data restored you may want to look at the recovery log after you restore to see what happened.
m20120 said:
I have not seen this problem. TWRP will only restore what was backed up. Are you sure that the data was backed up? Go to the folder where your backup is saved... do you see a file "data.ext4.win" in addition to the "system.ext4.win". If no data file then the data partition was not backed up.
If the data backup is there but you are still not seeing the data restored you may want to look at the recovery log after you restore to see what happened.
Click to expand...
Click to collapse
yea no data.ext4.win file was found..idk what happened??
rbarcenaslp said:
yea no data.ext4.win file was found..idk what happened??
Click to expand...
Click to collapse
When you run the backup you have to select which partitions are to be backed up. For some reason it did not run in your case.
bumnda was
rbarcenaslp said:
yea no data.ext4.win file was found..idk what happened??
Click to expand...
Click to collapse
In TWRP's Backup menu, there are 5 check boxes giving you the choice of what to backup. System, Data, Boot are checked by default, leaving Recovery & Cache to be selected (if you choose to do so). I just made backups of 2 custom ROMS, and my stock rooted ROM, and only used the default settings during backup. There were 6 files created in each backup: boot.emmc.win; boot.emmc.win.md5; data.ext4.win; data.ext4.win.md5; system.ext4.win; system.ext4.win.md5. After I made these backups, I tested each to see if I could go from one ROM to another without problems, and I could. The data.ext4.win & system.ext4.win should be big files in size as well.
I'm using TWRP 2.3.1.0, and have had zero problems with it (knock wood!)
Hey guys,
After flashing to 4.2.2 and then reverting back to 4.2.1, my file structure is completely screwed up. If I do a wipe, will I be left with a clean file system and my base custom ROM and updated radio?
Sent from my SGH-T999 using Tapatalk 2
llcooljayce said:
Hey guys,
After flashing to 4.2.2 and then reverting back to 4.2.1, my file structure is completely screwed up. If I do a wipe, will I be left with a clean file system and my base custom ROM and updated radio?
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Okay I'm not super familiar with the S3 yet because I just got it last week, but I'll give you a generic answer. First if you have a backup you should be in really good shape. Basically wipe everything in recovery (system, cache, and davlik). I always do it three times because this was the standard since the g1 just to be safe. Then after that you should be able to just revert back to your backup on 4.2.1. As far as the radio goes if you installed a custom (unless things are different with the S3) you have to reflash the original radio you were using. The radio should have nothing to do with it messing up the file system though. Finally after you revert back make sure you do not restore system data with titanium, only apps If you restore any system data you risk conflicts happening. There are a couple of exceptions to this like bluetooth pairings, but I would do these one at a time if you really want to restore them via titanium. If your file structure is still screwy after that, post back here exactly what is screwy.
spursrchamps2007 said:
Okay I'm not super familiar with the S3 yet because I just got it last week, but I'll give you a generic answer. First if you have a backup you should be in really good shape. Basically wipe everything in recovery (system, cache, and davlik). I always do it three times because this was the standard since the g1 just to be safe. Then after that you should be able to just revert back to your backup on 4.2.1. As far as the radio goes if you installed a custom (unless things are different with the S3) you have to reflash the original radio you were using. The radio should have nothing to do with it messing up the file system though. Finally after you revert back make sure you do not restore system data with titanium, only apps If you restore any system data you risk conflicts happening. There are a couple of exceptions to this like bluetooth pairings, but I would do these one at a time if you really want to restore them via titanium. If your file structure is still screwy after that, post back here exactly what is screwy.
Click to expand...
Click to collapse
Be careful wiping since it might wipe the backup data. Done it before and could not restore because it was deleted. Make sure all backups are in the external SD card.
Sent from my SGH-T999 using xda app-developers app
I actually want to erase all my files and file structure. Will the format even erase the content on SD?
I keep running out of file space and it's because of the 0 folder (created because of 4.2.2 and the introduction of separate log ins)
I basically want to start over but don't want to go through getting root or flashing my ROM)
Sent from my SGH-T999 using Tapatalk 2
Make a backup of the contents of your sdcard.
Go into /data/media, and delete the "0", "legacy", and "obb" folders (back them up first). No reason to format anything. You can't see these from your computer. Needs to be done from the phone.
/data/media/0
/data/media/legacy
/data/media/obb (may not exist)
What you are left with is an intact 4.1.x file structure with no redundancy.
So... I flashed AGAT_Recovery tREC_v0.2.2 and was intending to restore a "nandroid" backup from before I wiped my phone. First of course I made a backup (just Stock Rooted ROM I used to flash the recovery partition). I then tried to restore the previous image of my custom ROM and the restore failed. Investigated and found that the filenames in the nandroid backup folder were named differently from previous nandroid backups I had taken:
system.ext4.tar (0 bytes)
system.ext4.tar.a (large)
data.ext4.tar (0 bytes)
data.ext4.tar.a (large)
I'm not sure how the backup format changed as I don't recall updating the recovery partition, I'm wondering if some ROM I installed did this for me (if so thanks a lot). Looks like this:
http://forum.xda-developers.com/showthread.php?t=2194171
So trying to be clever, I deleted the 0 byte files and renamed all of the stupid .a files to the original (I had no .b, .c files etc.) Then I did a restore.
The restore completed successfully but com.android.Phone was crashing on startup repeatedly, the launcher wasn't working properly and basically the image wasn't usable.
I then decided that it wasn't worth all the trouble and I would just restore to the backup I had taken of the Stock Rooted ROM immediately prior to this whole mess starting (using AGAT_Recovery tREC_v0.2.2). The restore completed successfully but the O/S didn't boot at all (it just showed a black screen after POST of the Samsung logo).
For now I've reflashed stock using ODIN.
So basically my question is: why is this so complicated? Am I missing something here? Is AGAT_Recovery 0.2.2 not a good choice for a recovery partition?
Is the recovery you are trying to restore the sane recovery you are currently running.
I've gotten stuck by being in a different version of the same recovery and it just didn't work. I had to be in the same recovery in order to do a restore.
Just a thought
Bt is right. You should always use the same cwm to restore that you used on the backup. And the latest Agat recovery is essentially bugfree, which is 0.3.5. So I would use that. And it's not difficult, at all . Just takes a few "oh craps" to get it down pat!
Sent from my SPH-D710 using xda premium
thanks
jdsingle76 said:
Bt is right. You should always use the same cwm to restore that you used on the backup. And the latest Agat recovery is essentially bugfree, which is 0.3.5. So I would use that. And it's not difficult, at all . Just takes a few "oh craps" to get it down pat!
Click to expand...
Click to collapse
I suspect part of the reason I couldn't restore the one backup image was because I wasn't using the same version, or perhaps even product. Doesn't explain why the older version of Agat couldn't restore its own backup though. I'll try the newer version out. Thanks!
It's too bad the utilities don't write out some metadata about the format used, what product/version did the backup, etc.
philipdl71 said:
I suspect part of the reason I couldn't restore the one backup image was because I wasn't using the same version, or perhaps even product. Doesn't explain why the older version of Agat couldn't restore its own backup though. I'll try the newer version out. Thanks!
It's too bad the utilities don't write out some metadata about the format used, what product/version did the backup, etc.
Click to expand...
Click to collapse
That was an earlier kernel that probably still had bugs. Could have been a bad backup. It happens. The latest kernel will do solid backups/restores and serve as a very dependable dd. Good luck.
Sent from my SPH-D710 using xda premium
First of all I am a novice when it comes to this sort of thing. I was running Paradigm 2.3.5. Created a clockworkmod backup using version 5.0.x.x (can't remember the exact version). I then wiped data, wiped cache, installed Paradigm 3.1, installed gapps, and booted. Well I decided I wasn't ready to re do everything I have done to my phone and I wanted to go back to my previous backup. I restarted into recovery, but when I attempted a recovery I get no files found. The files are still there if I look through a usb connection. I understand this has something to do with the /0 folder and moving from 4.1 to 4.2 android. I'm not sure what to do here I just want to restore my phone to before all of this mess. I also understand there are other topics on this issue, and I have been looking through them for hours now, but I can't seem to get anything to work. Please help.
Edit: I was able to download a file manager and transfer the clockwork backups into the correct clockwork folder and then restore to my previous rom. I still would like to know if it is possible to flash a new rom without losing all of your files and apps.
ddrawer said:
First of all I am a novice when it comes to this sort of thing. I was running Paradigm 2.3.5. Created a clockworkmod backup using version 5.0.x.x (can't remember the exact version). I then wiped data, wiped cache, installed Paradigm 3.1, installed gapps, and booted. Well I decided I wasn't ready to re do everything I have done to my phone and I wanted to go back to my previous backup. I restarted into recovery, but when I attempted a recovery I get no files found. The files are still there if I look through a usb connection. I understand this has something to do with the /0 folder and moving from 4.1 to 4.2 android. I'm not sure what to do here I just want to restore my phone to before all of this mess. I also understand there are other topics on this issue, and I have been looking through them for hours now, but I can't seem to get anything to work. Please help.
Edit: I was able to download a file manager and transfer the clockwork backups into the correct clockwork folder and then restore to my previous rom. I still would like to know if it is possible to flash a new rom without losing all of your files and apps.
Click to expand...
Click to collapse
You shouldn't lose your files if you wipe unless you wipe sdcard (in a custom recovery). You can save data and apps with titaniumbackup.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
You shouldn't lose your files if you wipe unless you wipe sdcard (in a custom recovery). You can save data and apps with titaniumbackup.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Yes I never lost any files they were still on my sdcard, but there was an sdcard\ and an sdcard\0 with duplicate folder except one of the duplicates were empty. So your saying if I do a back up with titaniumbackup then flash a new rom that uses android 4.2.2 or 4.3 I can then restore with titaniumbackup and have all my old data and apps on the new rom?
Do a search on the GNEX Development forum for the current version of CWM. 6.0.4.0 was just posted earlier today.
Sent from my Galaxy Nexus using Tapatalk 2
Sorry to be so annoying with this, and I really appreciate everyones help. To clarify, I just installed CWM 6.0.4.0. If I now make a backup with CWM, clear files/factory reset, clear cache, and flash latest rom, I can then boot and it will be like nothing changed as far as my app configurations and data goes? If not, is there a way to do that? Will titan do that for me?
ddrawer said:
Sorry to be so annoying with this, and I really appreciate everyones help. To clarify, I just installed CWM 6.0.4.0. If I now make a backup with CWM, clear files/factory reset, clear cache, and flash latest rom, I can then boot and it will be like nothing changed as far as my app configurations and data goes? If not, is there a way to do that? Will titan do that for me?
Click to expand...
Click to collapse
Think of CWM as an image bu of your phone. If something messes up when you flash that latest rom, you can restore the bu and all will be back to the way it was pre-flash. TiBU will backup your apps and data, so after you do a clean flash you can restore them. My personal preference for a clean flash is to let the Play Store restore my apps, then use TiBU to restore the data for my user apps. I've found TiBU to be a bit of a crap shoot when it comes to system apps. There's always a bit of work involved with a clean flash, but it's not too much and will usually save some headaches.
Sent from my Nexus 7 using Tapatalk 4
Well this weekend I decided to flash CM 10.2. I backed up to titanium, I backed up to cwm latest version, factory reset, flashed CM 10,2, flashed gapps, booted, play store repopulated my apps. Open titanium backup "no backups found", tell it to detect the backup folder on whole device, no backups found. So I just ran my cwm restore and when I boot I get a whole new error. When I try to browse my files with astro file browser I get "cannot downgrade database from 2 to 1". What is wrong now?
Edit:
I just tried to do another cwm backup because I was going to move around some files through usb, it took forever and then in the end failed because the boot image was messed up. It said something about free space so I deleted all but the most recent cwm backup and then the backup that failed before was able to finish. After doing that I booted again and I was able to browse my files with astro again. So that isn't an issue anymore, but there has got to be something wrong with my file structure that this keeps happening.
I have two 0 folders, is that normal. From root I have storage\sdcard0\0\0 and that contains my data from before I started any of this flashing from 4.1. storage\sdcard0\0 has duplicate folders of storage\sdcard0\0\0 but they are empty. There is also a folder called sdcard in the root folder. So obviously there is a huge mess here. Is there a tool I can run to clean it up, or can someone tell me how the file structure is supposed to be so I can just move things back the the way it should be.
Edit 2:
I ended up copying the files in the deepest 0 folders out to the 0 folder above them then removing the deepest 0 folder. I now have sdcard\0 which only has a clockworkmod folder with a recovery file in it, and storage\sdcard0\0 which when I go into the 0 folder I get routed to sdcard\0. Everything seems to be working fine still. I'm thinking about just combining the sdcard0 with the sdcard and removing the sdcard0 since I'm currently on android 4.1. Then with everything cleaned up I might give it another go.