Am running: CWM-based Recovery v6.0.1.5
Rooted with SU method.
Rom: Resurrection Remix JB 3.1.2 with CM10 kernel
Having problems restoring a recent backup with CWM recovery 6 as this stops half way through saying:
com.android.renderscript.cache
com.ratebeer.android
files
DATA_Preferences
DATA_Tiles
DATA_Tiles_1
Segmentation fault
com.ratebe
Error while restoring /data!
Md5 checksums are all ok and there are no errors on the SD card.
The full logs are here on pastebin and being a noob I cant link to them. However if you google the topic title you should come across the thread with links on Cyanogenmod forum. I'm not sure how active that forum is so I thought I'd post here see if anyone could throw some suggestions my way as pretty desperate to recover this backup and not have to factory default. Thanks in advance!
Ok so I found out from a helpful chap on CM forum that the data.ext4.dup file has some erroneous lines in it where they get truncated from being too long. Apparently editing these lines so they're no longer truncated works but now I'm having SD card problems :/
He also mentioned in the latest CWM recovery 6.0.1.9 this problem is fixed. Currently looking for this but cant find it anywhere for SGS2.
Related
hi all, hoping someone can help point me in the right direction, new to samsung devices
had my i9300 a couple of months now - rooted using SGS3 toolkit
I finally plucked up the courage to flash a custom rom and went a bit crazy!!!
Flashed the following roms:
Android Revolution
Revolution Resurrection
3 minit
and finally
Hellybean
Before flashing each new rom I did the following:
Backed up my apps and data with TB pro
a full nandroid back up of my existing rom
followed by a factory data reset and wipes of cache and dalvik
I thought I had covered my butt pretty well but apparently not!!
i really liked hellybean and decided to restore my apps with TB but I got an error "unable to access external sd card" I tried changing the backup location folder which seemed to work, but once back in the main program I get the unable to access error....
So I thought ok i'll restore my nandroid backup!!! but that gives me an error "error restoring /data"
then I tried flashing the 3 minit rom again and then back into cwm and trying to restore that backup and I got an error restoring system this time!!!!
I'm not sure what to do now....have I lost my data for ever???
Is there a way to try and restore using odin??
and any hints for backing up and restoring in the future??
many thanks if anyone who can help
rgds
dibb
sdcard/0/0/0/0/0
Update 1.
Well on further reading it seems 4.2 has a 'unique' feature!!!
I'm using my own words here to help me comprehend whats going on, so forgive me if i'm not using "android-speak"
When upgrading to 4.2 it creates a new "partition" on your /sdcard called /emulated and all your new 4.2 data etc goes in here....all your pre 4.2 stuff goes into /sdcard/0...
I believe this happens also whenever you flash a new rom
so if you get a flash happy as I did then all of a sudden you get /sdcard/0/0/0/0/0/0...???? can this be correct????
The issue is I have different files in each of these "0" folders. My titanium Backup folder is in /sdcard/0/0/0/0 - which TB cannot access...I checked the /data/media folder which I believe is where my files are actually residing and sure enough in /data/media/0/0/0/0 theres my TB b/u folder
what i'd like to know now is if I can copy that folder to say, data/media without causing havoc?
Of course my next question is can I also move my cwm backup folder from sdcard/0/0/0/0/0/0 to data/media even tho I already have a cwm folder in there but which does not have the same files in it???
The other question is how to figure out which of the sdcard "0" folders hold which rom???
Anyone out there thats been thru the same thing???
Update 2
ok I just booted to cwm and did a backup just to see where it gets stored to...
Took ext sdcard out to force to int storage
backup saved by cwm to /sdcard
boot to android and fire up Total Commander
the only file in my cwm folder on /sdcard is an older one which cwm will not restore from
navigate to /data/media and sure enought theres my backup
boot back to cwm to restore my backup and cwm says No file found....wtf...
cwm cannot restore the backup it just made??
so back to android and check all my '0' folders and zip nothing?
my backup is in internal storage but NOT /sdcard??
So it would seem, that once you install a 4.2 rom - no apps can find their backups cos theyre
stored in a different location which they are unable to access??
thoughts people??
sdcard0/0/0/0/0/0
Hi dibb_nz,
As a new participant to installing custom ROMs I can confirm I'm having exactly the same issue that you're experiencing, my file system adding an extra /0 every time I flash an update to my Carbon ROM. It's causing major issues restoring backups from various apps and I'd also love to know if it's possible to fix this issue.
Any help from the more experienced would be very much appreciated.
Kind regards.
rpm-speed
rpm-speed said:
Hi dibb_nz,
As a new participant to installing custom ROMs I can confirm I'm having exactly the same issue that you're experiencing, my file system adding an extra /0 every time I flash an update to my Carbon ROM. It's causing major issues restoring backups from various apps and I'd also love to know if it's possible to fix this issue.
Any help from the more experienced would be very much appreciated.
Kind regards.
rpm-speed
Click to expand...
Click to collapse
Just make sure you use the latest version of clockworkmod or twrp recovery...that should fix your issue
Verstuurd van mijn Galaxy Nexus met Tapatalk
odin13 said:
Just make sure you use the latest version of clockworkmod or twrp recovery...that should fix your issue
Verstuurd van mijn Galaxy Nexus met Tapatalk
Click to expand...
Click to collapse
Hi odin13,
Flashed the latest CWM and will flash my ROM once again, thank you for your swift reply, I'll post the results shortly.
Kind regards
rpm-speed
---------- Post added at 08:33 PM ---------- Previous post was at 07:55 PM ----------
rpm-speed said:
Hi odin13,
Flashed the latest CWM and will flash my ROM once again, thank you for your swift reply, I'll post the results shortly.
Kind regards
rpm-speed
Click to expand...
Click to collapse
Well sadly that didn't work...
Re-flashed the ROM and now have /storage/sdcard0/0/0/0/0/0/0
Any suggestions would be greatly appreciated...
Kind regards.
rpm-speed
rpm-speed said:
Hi dibb_nz,
As a new participant to installing. ustom ROMs I can confirm I'm having exactly the same issue that you're experiencing, my file system adding an extra /0 every time I flash an update to my Carbon ROM. It's causing major issues restoring backups from various apps and I'd also love to know if it's possible to fix this issue.
Any help from the more experienced would be very much appreciated.
Kind regards.
rpm-speed
Click to expand...
Click to collapse
odin13 said:
Just make sure you use the latest version of clockworkmod or twrp recovery...that should fix your issue
Verstuurd van mijn Galaxy Nexus met Tapatalk
Click to expand...
Click to collapse
EDIT: sorry for the format of my post its difficult to read...not sure why it ended up like that
Using latest recovery only allows cwm to find yr backups, it will not
'fix' the 0 folder issue IF you already have more than one.
I found it best to totally reformat the internal storage and starting fresh.
I manually deleted the 0 folders with a file explorer. Then formatted the
internal SD in cwm.
I also made sure my backups saved to .tar rather than the .DUP format,
as I had also ended up with 1000's of .blob files which totally
confused the situation even more....they would not restore after taking
hours and hours to copy....
As previous poster said....using the latest cwm will prevent the creation
of multiple 0 folders.
Save what data you need to your external SD or PC. I had a couple
older SD cards laying around so I used those.
After that, delete all 0 folders, remember to enable read/write access
to the data partition so they stay deleted!!!
Using the latest cwm or twrp - format data/media,...
If u don't want to use the new .dup/blob incremental backup, change
the option "default backup format" to .tar...this could already be enabled
in the latest cwm, I'm not sure on that!
If you're 'experimenting' with 4.2 ROMs - you will always have a
0 folder, its just how things are done so don't go deleting that one
in future! And you might wanna look at dual booting if you're a wee bit
'flash-happy' like me, lol....I'm using siyahmod app and have 3 ROMs
installed, although I really only use 2. If your apps have a save to
external SD option, use it!!! Likewise with your nandroid backups
And titanium backups, I've had lottsa trouble with TB not being able
to find or access backups even after it finds the backup folder??
Also remember, 4.2 apps are different to 4.1apps, its not good practice
to restore 4.1 apps to a 4.2 ROM or vice versa....things get screwy!!!
If you want to go dual boot, 4.2 ROMs MUST Only be installed as
the secondary rom, it cannot be installed as your primary ROM.
If you only want to run 2 ROMs then use siyah kernel and the stweaks app.
If you want to have 3 ROMs then use siyah kernel and siyahmod multi boot app.
There can be issues with the sjiyahmod app...i find it best to use either whether?
but not both.
That's been my experience anyway....hope it helps and good luck
rgds dibb
PS I've had no issues at all running the siyah kernel with any other ROM,
even works we'll with my stock ROM...
Hey guys,
I have a little problem I can't find a solution to by searching.
I have a GS3 i9300 rooted with CF-Root-SGS3-v6.4.
When rooting, a version of CWM was installed (5.something).
Later, when installing af custom rom, I followed instructions and updated to a newer CWM (6.0.1.2):
http://forum.xda-developers.com/showthread.php?t=1719744
Later, I was thinking about restoring my original system backup, which I had made with the older CWM version right after rooting.
The new CWM can't restore my older backup. It can't recognize the file, not even when I copy it manually to the new CWM folder.
How can I solve this problem?
Do I need to install an older CWM again?
If yes, then one more question: As I said, my original CWM was installed when rooting. Can someone give me a download just for the CWM tar file included in the mentioned CF-Root?
Thanks a lot in advanced,
Agoston
Replace with older CWM root .
From Original Development section .
jje
still not recognizing + weird directory tree
After trying out three custom ROMs and after updating CWM, my system directory is rather weird. Besides the usual system folders, there is a "0" folder, that contains another set of system folders, and another "0" folder, containing the same. Also, my free internal storage as good as disappeared, from 8 GB to 1 GB. So, it looks like I have several systems on each other?!
How can I reduce this weird directory tree to just one? Do I need to wipe the SD-card?!
And by the way, I rooted the device again through Odin, and the old CWM is now installed again. Still though, it can't recognize the old backup.
As you probably imagine, I am hesitating to format SD-card, especially if CWM can't restore my factory ROM.
Can anyone help?
Thanks!
szaboagoston said:
Still though, it can't recognize the old backup.
Click to expand...
Click to collapse
I copied the backup directory manually to the "most superficial" CWM folder, and now trying system restore. I'ts not easy with four (!) different CWM directories.
Unfortunately I got an "error restoring data" message, and the phone is stuck in Samsung logo when booting.
Also, when trying to do a factory reset, I get the message: "error mounting /sd-card/.android_secure!"
Could this be because there is not enough space or something?!
If someone could help me with how to proceed, I would appreciate it!
Thanks.
Okay, the issue is solved. I admit, I might have been a little inpatient. Despite the "error restoring data" message, the stock factory system booted after a few tries - I might not have waited long enough. It seems that these "Folder 0"s were all just security copies of the old systems, and of course consumed a lot of hard disc space, so I just deleted them. Haven't met any negative consequences so far. I just got scared because of the error message and the too long boot time. Also this phenomenon with "Folder 0"s is not something I met before on other devices.
This error is still not answered on the forums so im starting a new thread.
i get the error as the title.
sd card space is not the problem.
i tried formatting the sd card.
i have less than 50 apps installed.
wiped dalvik cache, and all other sorts people say on other posts.
(my phone is LG P936 so "fix permission" screws up the phone. all text disappears)
have latest cwm recovery.
and still get the error.
any answers please?
and please dont reply if you are going to write an opinion.
only answers please.
sorry for my rude behaviour but I'm sick and tired of reading posts full of opinions and "maybe"s.
Not sure if you ever got this fixed but I 'm suffering from the same error. I tried pretty much everything you tried (even fix permissions) and I have about 20GB free on my SD card so space shouldn't be an issue. I have not yet tried formatting the SD card since it has always worked and CWM is able to write to it because the following files are created:
- boot.img
- data.ext3.tar
- recovery.img
- system.ext3.tar
The files that are missing are (based on older backups):
- .android_secure.vfat.tar
- cache.ext3.tar (probably because I wiped it first?)
- nandroid.md5
I have attached the log from CWM in the hopes that someone can tell me what is wrong. The error occurs at the end of the progress bar of 'backing up /data'.
hey just use TWRP Recovery. It's way better than CWM. normal backup on cwm took me like an hour but twrp was never longer than 10minutes.
Today I have formatted the SD card and tried again, but as expected it did not change anything.
ceoleaders said:
hey just use TWRP Recovery. It's way better than CWM. normal backup on cwm took me like an hour but twrp was never longer than 10minutes.
Click to expand...
Click to collapse
I guess I will give this a try. Can I just install it over CWM or can they run side by side?
different reciveries cannot be run side by side as they are installed on a different partition. so it will always be installed over your current one.
ceoleaders said:
different reciveries cannot be run side by side as they are installed on a different partition. so it will always be installed over your current one.
Click to expand...
Click to collapse
Well, I tried TWRP and it also fails at backing up my data partition. The log is a bit more clear though and it seems to get stuck on "/data/data/com.android.vending/cache/images" which is the last line before it gives an error. I checked the "images" folder and it seems empty but I cannot delete it. Tried ES File Explorer and Terminal Emulator but no way to get rid of it. The folder appears to be related to Google Play, so I cleared all data and cache from Google Play, even uninstalled the updates but there 's simply no way to get rid of it. I 'm not sure if this is the reason why the backup fails, but I CAN copy the folder and even rename it.
Pff looks like I 'm going to have to do a clean install after all .
Hello, I too have this problem and unfortunately TWRP is not available for my phone.
I used to be able to do CWM backups fine on my old phone, and they work great on my tablet. But they consistently fail at "/data" on my Galaxy Ace II x. Might it be because I'm using Link2SD? I don't see why that would cause a problem, but maybe it's having trouble with the symlinks?
Hmm. Seems the issue was that, despite having only 1.28 GB total available storage space on stock, the backups wanted more than 4 GB. Cleared some room on my microSD card and suddenly backups worked fine! Of course, shortly after I installed CyanogenMod, which has much smaller backups...
Sent from my GT-S7560M using Tapatalk 4
I forgot to report back here but the only way I found to fix the problem was by doing a clean install. After that, I was able to backup my data partition again. I then restored my apps ' data with TB and was unable to backup the data partition again. I 'm guessing one of my apps had corrupt data, but never got to find out which one it was.
maybe your partition not match with recovery, like something wrong vold.fstab
Just in case anyone still wants to know how to fix this, I managed to solve it by running these commands:
1. run adb shell in recovery.
2. unmount data partition (umount /dev/block/mmcblk0p26). -> this one failed so I skipped it
3. run e2fsck /dev/block/mmcblk0p26
See http://forum.xda-developers.com/showpost.php?p=48659092&postcount=868 for original post.
I got a few HTREE errors and a bunch of duplicate names which I renamed when prompted. Booted the phone and rebooted into TWRP and now I am able to backup my data partition again. :good:
EDIT: Problem reappeared so I tried the above commands again but it said that the filesystem was clean. Ran 'e2fsck -f /dev/block/mmcblk0p26' instead and had to fix a bunch of HTREE errors from Facebook again and duplicate names from Xprivacy but now I 'm able to backup my data partition again.
Dude just selest the backup format as both zip and tar filea
Hi, my device is running a CM10.1 nightly. After encrypting it, TWRP 2.4.2.0 is not able to decrypt the /data partition when I enter the password. So I updated to 2.5.0.0 using the Goo Manager thinking it will fix this issue. 2.5.0.0 seems to accept the password but burps a" 'unable to mount /data' message when I try to access data storage. TWRP seems to see /data as the entire size of the internal storage too. Then I flashed 2.5.0.0 with ODIN, to exclude any problems related to local installation, and still the same issue is there. From what i read TWRP should support encryption, these bugs show that there are serious issues, how would I go about reporting that to them? Also is there a way I can resolve this without tearing down this setup?
Another issue is that my file manager cannot access my /data partiton any longer. Everytime it comes up it hangs and crashes without showing any directories. Maybe this issue would go away with a firmware update but I can't get that going because of the issue above.
you can also try CWM touch recovery if that doesn't work. just flash it from odin and install another custom rom. good luck.
-------------------------------------
please let me know if i'm wrong and CLICK thanks if i help
SRIRAM
sent from my GT-I9300 running CM10.1 RC4.4 by Temasek
Do you have a similar setup to mine I want to confirm that this is a general bug rather than an issue with mine specifically. If you are anyone else let me know I'd appreciate it. From what I have researched CWM does not support encryption so it would be a non-starter.
I have a question about TWRP that is not directly related to the Samsung Galaxy S III. Testing CM 10.2 this evening and I carefully made a nandroid backup first. After installing CM 10.2 I had some troubles -- nothing major -- and thought I'd just revert. However, I couldn't see the backup in the TWRP restore list. Turned out that CM 10.2 has created sdcard1 and sdcard0 and the backup directory was pointing to a different place. In a momentary lapse I pressed the "Restore Defaults" button in TWRP. Now when TWRP starts there is a log message which says "E: Storage partition '//TWRP/BACKUPS/6a0a9ba9' which is not a valid location.
Any ideas how to correct this? Reinstalling TWRP does not seem to correct this.
Thanks!
Check TWRP post in your phones forum for link to their web site .
This is I9300 forum