Develop Bugs

Interesting Experience with CWM Recover 6.0.2.3

I was wondering whether anyone has experienced the following:
I was on Team Sonic-Free GS3 v.3.0.0. Everything was setup the way i wanted it. I booted into Recovery and created a Restore point.
Right after, I did the following:
- Wipe Data/Factory Reset
- Wipe Cache partition
- Wipe Dalvik Cache
- Format /System
- Format /Data
- Format /Cache
I installed the latest Nightly from Cyanogenmod 10 (12.26). Initially I used an older version of gapps-jb but immediately flashed the correct one. Everything went fine. The system loaded and nothing seemed wrong. After some messing around I noticed it was a big sluggish on my phone. So I decided to restore the phone back to its original setting.
When I went to backup/restore and hit the Restore option, it told me that I had no recovery points! :crying::crying: At this point I started freaking out.
I tried to see if I could flash from the SDCard and I noticed one thing. This was in order to get to the main folder of the SDCard i needed to enter a folder named "0". All the files were there including my CMW recover file. Although it was on the card the recovery option was unable to see it.
After this I decided to do the following. I clean swiped again and installed the Free GS3 version i had on the SDCard already. I booted into the system and saw that the folder "0" was there but also in the main directory there were still folders. In the main portion of the card i loaded my copy of the recovery.
I went back into recovery and and tried again. The restore file was there! :good::good: I was able to recovery my original setup. Unfortunately, all of my pictures and music were still located within the newly created "0" folder. I just copied those back.
Can anyone explain why this happened? I'm very curious!
I do apologize if this has been answered before. I have done a search and have only found scenarios for the SDcard is not seen as mounted. (also dont know if the icons mean anything for the post)
*Update - Folder "0" cannot be deleted. Root explorer says "failed" and Windows Explorer says "Cannot delete 0: THe storage is write-protected". Any ideas on this also?

solidhound said:
I was wondering whether anyone has experienced the following:
I was on Team Sonic-Free GS3 v.3.0.0. Everything was setup the way i wanted it. I booted into Recovery and created a Restore point.
Right after, I did the following:
- Wipe Data/Factory Reset
- Wipe Cache partition
- Wipe Dalvik Cache
- Format /System
- Format /Data
- Format /Cache
I installed the latest Nightly from Cyanogenmod 10 (12.26). Initially I used an older version of gapps-jb but immediately flashed the correct one. Everything went fine. The system loaded and nothing seemed wrong. After some messing around I noticed it was a big sluggish on my phone. So I decided to restore the phone back to its original setting.
When I went to backup/restore and hit the Restore option, it told me that I had no recovery points! :crying::crying: At this point I started freaking out.
I tried to see if I could flash from the SDCard and I noticed one thing. This was in order to get to the main folder of the SDCard i needed to enter a folder named "0". All the files were there including my CMW recover file. Although it was on the card the recovery option was unable to see it.
After this I decided to do the following. I clean swiped again and installed the Free GS3 version i had on the SDCard already. I booted into the system and saw that the folder "0" was there but also in the main directory there were still folders. In the main portion of the card i loaded my copy of the recovery.
I went back into recovery and and tried again. The restore file was there! :good::good: I was able to recovery my original setup. Unfortunately, all of my pictures and music were still located within the newly created "0" folder. I just copied those back.
Can anyone explain why this happened? I'm very curious!
I do apologize if this has been answered before. I have done a search and have only found scenarios for the SDcard is not seen as mounted. (also dont know if the icons mean anything for the post)
*Update - Folder "0" cannot be deleted. Root explorer says "failed" and Windows Explorer says "Cannot delete 0: THe storage is write-protected". Any ideas on this also?
Click to expand...
Click to collapse
Was it registering a different recovery version when you flashed CM10 from the FreeGS? If so that would be why it didn't register the backup that you made. (I had this issue or similar to on my Touch) flashed a different rom that used CVM 5.something.. and original was a newer version. Caused me some issues. As for the folder being write protected. Try using root explorer, mount as R/W and then try to delete from there. Just ensure you have everything out of it you want tho.

milky1112 said:
Was it registering a different recovery version when you flashed CM10 from the FreeGS? If so that would be why it didn't register the backup that you made. (I had this issue or similar to on my Touch) flashed a different rom that used CVM 5.something.. and original was a newer version. Caused me some issues. As for the folder being write protected. Try using root explorer, mount as R/W and then try to delete from there. Just ensure you have everything out of it you want tho.
Click to expand...
Click to collapse
hey milky1112.
Thanks for reading and providing your input!
I actually used the sames recovery when creating and trying to restore. That's the odd part. I did recently flash the newer version within the old recovery. Do you think that may have been it? Although the new one was used to create a nandroid and restore it.
I just tried deleting using Root Explorer and the same result. It's not a big deal since its only 69mb but it's quite annoying knowing I can't.
thanks again!

solidhound said:
hey milky1112.
Thanks for reading and providing your input!
I actually used the sames recovery when creating and trying to restore. That's the odd part. I did recently flash the newer version within the old recovery. Do you think that may have been it? Although the new one was used to create a nandroid and restore it.
I just tried deleting using Root Explorer and the same result. It's not a big deal since its only 69mb but it's quite annoying knowing I can't.
thanks again!
Click to expand...
Click to collapse
That is very possible, still odd that it will not let you delete even with R/W permissions set. But as long as everything is working.. Then i wouldn't fuss too much

The new rom you installed is on 4.2 not 4.1 which is probably what you had originally. The new 4.2 releases by Google move everything into the O folder its part of the new Android set up to dual boot devices. If the recovery is not set up to correct for this your phone will not recognize where the files have been moved to. In my understanding only TWRP is corrected to do this, we'll at least in the Gnex it is. Anyone on Cwm has had issues with this. The fix is to copy and paste your files back into its original location. You can not delete O folder it is an essential part now of your system and it's where it will reference everything from and originals must remain.
Transmitted with a portable device using Xparent Blue Tapatalk 2

edfunkycold said:
The new rom you installed is on 4.2 not 4.1 which is probably what you had originally. The new 4.2 releases by Google move everything into the O folder its part of the new Android set up to dual boot devices. If the recovery is not set up to correct for this your phone will not recognize where the files have been moved to. In my understanding only TWRP is corrected to do this, we'll at least in the Gnex it is. Anyone on Cwm has had issues with this. The fix is to copy and paste your files back into its original location. You can not delete O folder it is an essential part now of your system and it's where it will reference everything from and originals must remain.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Thanks for clarification Ed. I've been on TPR for a while so haven't flashed any 4.2 roms.

edfunkycold said:
The new rom you installed is on 4.2 not 4.1 which is probably what you had originally. The new 4.2 releases by Google move everything into the O folder its part of the new Android set up to dual boot devices. If the recovery is not set up to correct for this your phone will not recognize where the files have been moved to. In my understanding only TWRP is corrected to do this, we'll at least in the Gnex it is. Anyone on Cwm has had issues with this. The fix is to copy and paste your files back into its original location. You can not delete O folder it is an essential part now of your system and it's where it will reference everything from and originals must remain.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
hey edfunkycold,
thanks a ton for the response and clarification! i was thinking about swapping recoveries but i already reverted back to the original nandroid image i had at that point.
and you are correct. i was on 4.1 and not 4.2. i didn't know such changes were made but its great to see dual boot is coming up.
i will make sure to THANK both responses once i reach 10 posts. i'm trying hard to participate in these forums but haven't had time until recently.

[Q] ANY method to clean up the "0" directories?

Hi,
I know that for some ROMs that when you flash them, you will get a "0" directory (I forgot the exact reason, but something to do with multiuser?)
I have been playing around with various ROMs lately, and they have been creating "0" directories inside my currently existing "0" directories (eg. sdcard0/0/0)
This was not a big issue for me back when I had just one 0 directory, but now that I have a couple inside each other, titanium backup restores app data to directories that is not visible to some of my apps like S Note. (Plus it is eating up my internal sd card memory) Temporarily, I currently just cut and pasted my .snb files for my S Note to the working directory so I can view them on my phone for now.
Does anyone know of ANY method (I mean ANY method. I don't mind having to do factory reset/wipe, flashing the ROM again, etc) to clean up my internal sd card?
I've already tried flashing stock ROM and unrooting, then rooting and flashing a new ROM again, but that did not work.
Thanks!

A full reflash with odin will do it otherwise I think theres a cleanup zip somewhere in one of the cm 10.1 threads

mrevankyle said:
A full reflash with odin will do it otherwise I think theres a cleanup zip somewhere in one of the cm 10.1 threads
Click to expand...
Click to collapse
I tried flashing the stock ROM with Odin, and rooting it again with Odin, but it still left the 0 files there.
Can you tell me a little bit more about the cleanup zip for CM10.1?

Wipe Data with TWRP. Backup everything you need and remove your external SD card first.

jmapark91 said:
Hi,
I know that for some ROMs that when you flash them, you will get a "0" directory (I forgot the exact reason, but something to do with multiuser?)
I have been playing around with various ROMs lately, and they have been creating "0" directories inside my currently existing "0" directories (eg. sdcard0/0/0)
This was not a big issue for me back when I had just one 0 directory, but now that I have a couple inside each other, titanium backup restores app data to directories that is not visible to some of my apps like S Note. (Plus it is eating up my internal sd card memory) Temporarily, I currently just cut and pasted my .snb files for my S Note to the working directory so I can view them on my phone for now.
Does anyone know of ANY method (I mean ANY method. I don't mind having to do factory reset/wipe, flashing the ROM again, etc) to clean up my internal sd card?
I've already tried flashing stock ROM and unrooting, then rooting and flashing a new ROM again, but that did not work.
Thanks!
Click to expand...
Click to collapse
First of all take a nandroid backup. Save it on sdcard and on your pc/laptop. Than copy all in folder 0 to root of int sdcard amd then delere folder 0. Restart your phone and all is now ok. Tips++ instal Omega rom 43.1 the mostly stabile rom ever.
Not forget to allways read OP before flash something.. have a nice evening..
Sent from my GT-I9300 using xda premium

I had luck changing the permissions of the 0 folder in TWRP to 755, rebooting, and deleting the 0 folder in Root Explorer. Everything defaulted back to /sdcard after that. Make sure to copy anything you don't want to lose out of the 0 folder before deleting it.

[Q] Titanium Backup can't find the files to restore after installing new ROM.

After several tries, I finally successfully installed Cyanogenmod 10.2 on my Rogers Samsung Galaxy S3 for the first time. Unfortunately, Titanium Backup can't find the files to restore app+data. I've gone to Preferences > Backup folder location to detect where the backup is...and it says it's empty.
The weird thing is, when I'm in Clockwork Recovery mode and browse through the folders, the folder structure is identical to before I installed the ROM. Like I see the folder I stored the .zip files in, my photo folders, and a lot of other folders. But when I browse through the File Manager on the phone or when it's plugged into the computer, that stuff doesn't exist.
I'm not really too knowledgeable in this sorta thing, but I've rooted/installed new ROMs on my old Galaxy S before and successfully restored apps+data using Titanium Backup. I'm not too sure what's happening here
Did wiping data during the installation delete the backup too? My photos are gone as well (this didn't happen on the Galaxy S...), I don't mind though since I already backed it all up on my computer, but it's still surprising.
Any help to restore my apps and data is much appreciated!!
[PS: During the setup, Google can also restore apps that it backed up for me...but I've tried this and it only restores the apps and not the data...so I'm really hoping Titanium Backup will do that for me]

If I recall, CM changes the sdcard locations. So say before CM you had sdcard (internal) then extsdcard (external). I believe CM creates an sdcard 0 and 1. Try looking in both places. Good luck.

pre4speed said:
If I recall, CM changes the sdcard locations. So say before CM you had sdcard (internal) then extsdcard (external). I believe CM creates an sdcard 0 and 1. Try looking in both places. Good luck.
Click to expand...
Click to collapse
Ya I couldn't find the backup in sdcard0. I should also mention that I made the mistake of storing it in internal, rather than external (sdcard1). The folders within sdcard0 is what it would look like on a new phone...
Anyways, I'm determined to find out how to recover it because it's in the phone SOMEWHERE because the folder structure still exists when I'm in Clockwork Recovery.

poutineroutine said:
Ya I couldn't find the backup in sdcard0. I should also mention that I made the mistake of storing it in internal, rather than external (sdcard1). The folders within sdcard0 is what it would look like on a new phone...
Anyways, I determined to find out how to recover it because it's in the phone SOMEWHERE because the folder structure still exists when I'm in Clockwork Recovery.
Click to expand...
Click to collapse
Menu, preferences, backup folder location, search whole device it will find then use current folder it will then restart and you're set

louvass said:
Menu, preferences, backup folder location, search whole device it will find then use current folder it will then restart and you're set
Click to expand...
Click to collapse
I did that many times already. It says 'No backup location was found'...

poutineroutine said:
I did that many times already. It says 'No backup location was found'...
Click to expand...
Click to collapse
I'm having the exact same problem. Has this problem been solved?
Some help desperately needed here! Thanks!

This could all depend on if you backed everything up on your device or SD card? If internal then I want to say the AOSP rom will not recognize anything from stock. However if you stored all those files on the external SD card and all lose your data, then there is an issue.
Suggestion: flash stock and see if it all comes back. If so then move all data to external SD card. Flash AOSP rom then it will all be there. Let me know how it works out

[Q] Strange file directory structure

I’m rooted and using CW for my recovery. I’m using a pre-owned phone that I (thought) I wiped before rooting. I am running stock 4.2.2, baseband MDL.
Initially all I wanted to do was nandroid to my SD card in preparation for flashing a custom ROM. I have a 32GB card that my phone recognizes just fine, so I thought it would make sense to put the backup there. So I enabled Use External Storage in ROM Manager settings and tried to begin the backup process.
First I tried it using the ROM Manager itself. Got this error message:
Unknown volume for path [/external_sd/clockworkmod/backup/name of the backupfile here]
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log
Please open ROM Manager to report the issue​
Then I tried doing it by going straight into Recovery and initiating it myself. That was in the Backup and Restore menu. The Backup location options were
/sdcard
/storage/sdcard1
Neither of those is the external card. Then I looked at the Advanced menu but there was no option that mentioned the external card. So it seems that the Recovery doesn’t see my external card. And the subdirectory options that Recovery wants to use do not exist on my phone.
At first I thought it was my SD card. I removed it, re-formatted it (non-Quick) on my computer, etc. I was still not able to save my recovery to my SD card. Again I see that CW want to put the recovery in a subdirectory that does not exist.
I was able to nandroid to the internal memory, so at least there’s that. But the file directories on my card are a mess that make no sense and don’t seem to match what I’ve seen on multiple forums.
Using ES File Explorer I see this from the root directory -
/storage/emulated/0
/storage/emulated/legacy
/storage/extSdCard
/storage/sdcard0 – this one has a little arrow at the start of the pathname. Does that make it a shortcut?
/storage/container – this one has a little arrow at the start of the pathname. Does that make it a shortcut?
Also from the root directory I see this –
/sdcard/ – this one has a little arrow at the start of the pathname
Then there are these –
/mnt which seems to have copies of sdcard and extSdCard
/mnt_1 which just has extSdCard, sdcard_1, sdcard_2, and sdcard_3
I’m running 4.2.2, baseband MDL. What I would like to do is get the directory structure back to stock and remove all the multiples of data and folders that I am seeing.
1. If I totally wipe the phone, will the stock file structure be restored?
2. If the answer to #1 is “yes”, what happens if I do an Advanced Restore, restoring Data from a nandroid created with the screwy structure? Does the screwy structure return?
Thanks,
Veronica

re: nandroid backup/restore
verngator said:
I’m rooted and using CW for my recovery. I’m using a pre-owned phone that I (thought) I wiped before rooting. I am running stock 4.2.2, baseband MDL.
Initially all I wanted to do was nandroid to my SD card in preparation for flashing a custom ROM. I have a 32GB card that my phone recognizes just fine, so I thought it would make sense to put the backup there. So I enabled Use External Storage in ROM Manager settings and tried to begin the backup process.
First I tried it using the ROM Manager itself. Got this error message:Unknown volume for path [/external_sd/clockworkmod/backup/name of the backupfile here]
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log
Please open ROM Manager to report the issue​Then I tried doing it by going straight into Recovery and initiating it myself. That was in the Backup and Restore menu. The Backup location options were
/sdcard
/storage/sdcard1
Neither of those is the external card. Then I looked at the Advanced menu but there was no option that mentioned the external card. So it seems that the Recovery doesn’t see my external card. And the subdirectory options that Recovery wants to use do not exist on my phone.
At first I thought it was my SD card. I removed it, re-formatted it (non-Quick) on my computer, etc. I was still not able to save my recovery to my SD card. Again I see that CW want to put the recovery in a subdirectory that does not exist.
I was able to nandroid to the internal memory, so at least there’s that. But the file directories on my card are a mess that make no sense and don’t seem to match what I’ve seen on multiple forums.
Using ES File Explorer I see this from the root directory -
/storage/emulated/0
/storage/emulated/legacy
/storage/extSdCard
/storage/sdcard0 – this one has a little arrow at the start of the pathname. Does that make it a shortcut?
/storage/container – this one has a little arrow at the start of the pathname. Does that make it a shortcut?
Also from the root directory I see this –
/sdcard/ – this one has a little arrow at the start of the pathname
Then there are these –
/mnt which seems to have copies of sdcard and extSdCard
/mnt_1 which just has extSdCard, sdcard_1, sdcard_2, and sdcard_3
I’m running 4.2.2, baseband MDL. What I would like to do is get the directory structure back to stock and remove all the multiples of data and folders that I am seeing.
1. If I totally wipe the phone, will the stock file structure be restored?
2. If the answer to #1 is “yes”, what happens if I do an Advanced Restore, restoring Data from a nandroid created with the screwy structure? Does the screwy structure return?
Thanks,
Veronica
Click to expand...
Click to collapse
If you wipe the phone using it's internal "factory data reset"
(settings>accounts>backup and reset>factory data reset)
It will restore the stock phone's internal sdcard's structures, directories and folders.
But what I would suggest is to download and odin flash the TWRP custom recovery,
that way you will not loose any data or user files and you will not have any problems
making or restoring nandroid backups.
TWRP is really easy to use and basically self-explanatory.
Here is the direct download link for TWRP: http://techerrata.com/get/twrp2/jfltetmo/openrecovery-twrp-2.6.3.1-jfltetmo.tar
Good luck!

Misterjunky said:
If you wipe the phone using it's internal "factory data reset"
(settings>accounts>backup and reset>factory data reset)
It will restore the stock phone's internal sdcard's structures, directories and folders.
But what I would suggest is to download and odin flash the TWRP custom recovery,
that way you will not loose any data or user files and you will not have any problems
making or restoring nandroid backups.
TWRP is really easy to use and basically self-explanatory.
Here is the direct download link for TWRP: http://techerrata.com/get/twrp2/jfltetmo/openrecovery-twrp-2.6.3.1-jfltetmo.tar
Good luck!
Click to expand...
Click to collapse
Thanks!
Are you saying that using TWRP will preserve the file structures and that CW has some kind of effect on them...or that CW is the reason I can't put my backup on my SD card?

verngator said:
Thanks!
Are you saying that using TWRP will preserve the file structures and that CW has some kind of effect on them...or that CW is the reason I can't put my backup on my SD card?
Click to expand...
Click to collapse
CWM or TWRP do not effect the file structures.
All I am saying is create a nandroid backup using TWRP and then restore
the backup. Then if it works properly for you then keep using twrp.
You will be pleasantly surprised how well twrp works and how easy it is to use.
Good luck!

Full backup via adb?

I tried
adb backup -all
but the resulting file is 60MB, but should be 100GB.
Edit: Some more information:
I'm running HavocOS, but the apps on this Rom are unstable. They are stable for almost 24h every time I flash most recent GApps, but by now I don't really think it's GApps anymore.
Aside from EVERY app being unstable copying files is not stable either. I just copied 150GB of images and videos from internal as well as "external" SD-card to my computer without any interrupt and that worked without any issues. If I try to copy a file from internal to external SD card within the phone, then this works in one out of three tries for every single file.
So next thing is try another ROM, then maybe an older ROM and then search for Hardware defects, before I want to try next ROM I want to create a backup.
There is A LOT of config files here and alot of them are linked to images all over the place, so I will likely have to switch to the backup a few times because if I just save the parts part by part now I will 100% forget a few important things.
This seems like a job for TWRP backup. Oh and btw, I did a TWRP-backup just when I migrated to this ROM, but it is defect! I tried to create a full backup withing TWRP >10 times today and yesterday and it all failed. Oh yes, moving files withing this device is buggy right now. But I can do it via adb, can't I? How?

andy01q said:
I tried
adb backup -all
but the resulting file is 60MB, but should be 100GB.
Edit: Some more information:
I'm running HavocOS, but the apps on this Rom are unstable. They are stable for almost 24h every time I flash most recent GApps, but by now I don't really think it's GApps anymore.
Aside from EVERY app being unstable copying files is not stable either. I just copied 150GB of images and videos from internal as well as "external" SD-card to my computer without any interrupt and that worked without any issues. If I try to copy a file from internal to external SD card within the phone, then this works in one out of three tries for every single file.
So next thing is try another ROM, then maybe an older ROM and then search for Hardware defects, before I want to try next ROM I want to create a backup.
There is A LOT of config files here and alot of them are linked to images all over the place, so I will likely have to switch to the backup a few times because if I just save the parts part by part now I will 100% forget a few important things.
This seems like a job for TWRP backup. Oh and btw, I did a TWRP-backup just when I migrated to this ROM, but it is defect! I tried to create a full backup withing TWRP >10 times today and yesterday and it all failed. Oh yes, moving files withing this device is buggy right now. But I can do it via adb, can't I? How?
Click to expand...
Click to collapse
try using the migrate app

Which migrate app?

andy01q said:
Which migrate app?
Click to expand...
Click to collapse
The app's name is migrate..search on playstore or xda thread

Got it, thank you.
It's not working though for three reasons:
1st: It's not a full backup. I got what I need for migrating, I want a full backup to return to the current state including filesystem, tree and random files. Ideally A full copy of all filesystems which wouldn't fit onto any of the filesystems even if this was what the app did.
2nd: It's not via ADB. Backing up from inside the phone doesn't work as I already wrote.
3rd: Doesn't recognize my SD card (yes it's mounted as R/W) I don't know why I even checked that as the app is useless for my case anyway.