Develop Bugs

[Q] How are YOU dealing with 4.2 /0 folders?

Koush has released an updated CWM that mitigates the sdcard/0 folder migration, but for the users that have the /0 folders already, how are YOU fixing these extra folders?

Move every file in front of the /0 folder
Sent from my Galaxy Nexus using xda premium

using it how theyre supposed to be used, all the files are in the 0 folder. why fight it? its not a bug of any kind, that how android is set up now. everything works properly, as it should. unless you mess with it.

simms22 said:
using it how theyre supposed to be used, all the files are in the 0 folder. why fight it? its not a bug of any kind, that how android is set up now. everything works properly, as it should. unless you mess with it.
Click to expand...
Click to collapse
doesnt it affect your restoration of local backups?
eg. titaniumbackup, whatsapp messages, nova launcher settings

dornestic said:
dowork fine,ffect your restoration of local backups?
eg. titaniumbackup, whatsapp messages, nova launcher settings
Click to expand...
Click to collapse
nope. twrp recovery backups work fine, and i sync my titanium backups to the cloud(google drive) and restore from there. i dont use whatsapp nor nova.

Flash the 4.2 stock images: profit :good: (fresh and clean sdcard with no /0 folder. (Only in recovery its visible )
Sent from my Galaxy Nexus

I did a clean flash of stock 4.2 takju factory image an I have data/media/0 directory as well as the usual /sdcard directory with exact same folders in both, I used a titanium backup that I moved to PC then back to my phone after flashing 4.2 image an then restored, nova layout an settings restored fine for me as I used the updated beta nova that was already updated to work with 4.2 before I did my titanium backup that I restored from.
Sent from my Galaxy Nexus using xda premium

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.

Can't get any backups to work

Hello,
I having been having some major problems the last 2 weeks with any and all backups i create of my phone. I have tried to make backups of various Roms using both Rom Manager and also directly by flashing into recovery (CWM touch). Each time the backup is successfully made, but then when i try to flash the backup i get errors saying "file not found". I lost my stock rooted backup, a backup of CM10, a backup of Liquid Smooth, and a backup of JellyBam. Does anyone have any idea why my backups don't seem to work? This is incredibly frustrating as I lose all of data and have no security blanket should something go wrong. Every time i flash a new Rom i wipe Dalvik, Cache, and factory reset/wipe.
Anyone have any idea what's going on with the backups?

what versions of android have you been flashing and are you sure your on the latest recovery?

psycho2k9 said:
what versions of android have you been flashing and are you sure your on the latest recovery?
Click to expand...
Click to collapse
Thanks for the reply. believe liquid smooth was version 4.2 and the jellbam was 4.1.2. My stock was either 4.1.1 or 4.1.2, whichever the last update went to. As far as CWM, I am on 6.0.2.3.

westmenu Marquette
Not sure if this is relevant in all this, but my Titanium Backup wasn't working on it's own either when I flashed any new Rom. It would not see any backups and I would have to go into the Preferences and scan for the folder that had backups in it as it did not automatically detect backups in whatever folder it defaults to. This is also a recent development.

Something Creative said:
Hello,
I having been having some major problems the last 2 weeks with any and all backups i create of my phone. I have tried to make backups of various Roms using both Rom Manager and also directly by flashing into recovery (CWM touch). Each time the backup is successfully made, but then when i try to flash the backup i get errors saying "file not found". I lost my stock rooted backup, a backup of CM10, a backup of Liquid Smooth, and a backup of JellyBam. Does anyone have any idea why my backups don't seem to work? This is incredibly frustrating as I lose all of data and have no security blanket should something go wrong. Every time i flash a new Rom i wipe Dalvik, Cache, and factory reset/wipe.
Anyone have any idea what's going on with the backups?
Click to expand...
Click to collapse
I started several threads on this very issue....my backups also are not working - "file not found" You aren't alone, once more people start experiencing this I'm sure we will see an answer

jackryan57 said:
I started several threads on this very issue....my backups also are not working - "file not found" You aren't alone, once more people start experiencing this I'm sure we will see an answer
Click to expand...
Click to collapse
I've tried searching and nothing relevant came up. Do you also have several folders that appear the same when you reboot into recovery? For example, I have a folder titled "0" that popped up around when the issue started. I have a CWM folder as a subfolder under "0" that appears to be identical to the CWM folder that is not in a subfolder. That's why i brought up the issue i am having with titanium backup, wondering if that has anything to do with anything.
I've tried flashing the backups from both the subfolder and the non-subfolder, and nothing seems to work. The only thing i can successfully do is do a complete wipe and reset and flash a new Rom from scratch off the zip.

If your flashing anything 4.2 related its highly recommended that you use twrp as your recovery because of how the files get condensed into that "0" folder.. Your probably going to have to hunt down your backups I'm sure they are somewhere in that 0 folder
Sent from my SAMSUNG-SGH-I747 using xda premium

psycho2k9 said:
If your flashing anything 4.2 related its highly recommended that you use twrp as your recovery because of how the files get condensed into that "0" folder.. Your probably going to have to hunt down your backups I'm sure they are somewhere in that 0 folder
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I thought it might have to do with the folder issue, but i have tried flashing from the CWM, backup, and various other folders in both the "0" subfolder and the main folder. In both cases i get an error that say's file not found. That said, do you really think twrp would make a difference? I'm pretty new to android, so i'm not really familiar with it beyond knowing it's a recovery like cwm. I'd be willing to try it out if it wont jack up the little amount of cwm i do actually know and am familiar with. At least now i can flash a new Rom and start over with a titanium backup of files if shizz hits the fan.

The only thing I can think of is to copy and paste the clockworkmod folder from the 0 folder to the root folder and try the restore process from the root folder instead of the 0 sub folder. If that doesn't work I dunno bro
Sent from my SAMSUNG-SGH-I747 using xda premium

psycho2k9 said:
The only thing I can think of is to copy and paste the clockworkmod folder from the 0 folder to the root folder and try the restore process from the root folder instead of the 0 sub folder. If that doesn't work I dunno bro
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I'll give it a shot even though I've tried loading from the folder directly already.
How would i move it? I've actually tried using file manager and it doesnt let me. It says it can't move the file, or any file actually, from the "0" subfolder.

so i made some serious progress. I used ES file explorer instead of file explorer and it let me move the file for CWM from the "0" subfolder to the main folder. It said that it was going to overwrite everything in the main folder with the subfolder stuff. I accepted and then i dirty flashed a backup of the same Rom (in case the file would not be found again) that had previously not worked.
It actually ended up working. I am afraid to try to flash a backup after completely wiping b/c i dont want to go through the crap of setting everything up again tonight, but i will give it a go tomorrow and report back. So for some reason, backups can't be flashed from CWM from the "0" subfolder, and they can't be flashed from the main folder, unless you move the files from the "0" subfolder to the main folder.
Hope that makes sense to anyone that may have this problem.

If you have the time and are by a computer you can also just move everything out of the 0 folder into the root folder and just get rid of the 0 folder altogether and start from scratch. I think it has something to do with cwm and how they recognize the file system. Like I said you should give twrp a try its very good.
Sent from my SAMSUNG-SGH-I747 using xda premium

Where are my CWM backups now? (4.2)

ever since I updated to 4.2.1 I cannot locate my nandroid backups in the folder where it's supposed to be.. I heard that 4.2 puts the old nandroids to a folder named 0, but theres nothing in there. I have old backups made to internal storage and i want to delete these to clear space. only backing up on my sd card will work. However, when in recovery mode, I can see the old file if i press restore. can anyone help me find those folders to delete?

x10user2011 said:
ever since I updated to 4.2.1 I cannot locate my nandroid backups in the folder where it's supposed to be.. I heard that 4.2 puts the old nandroids to a folder named 0, but theres nothing in there. I have old backups made to internal storage and i want to delete these to clear space. only backing up on my sd card will work. However, when in recovery mode, I can see the old file if i press restore. can anyone help me find those folders to delete?
Click to expand...
Click to collapse
When looking at your nandroid, does it give you the path?

BWolf56 said:
When looking at your nandroid, does it give you the path?
Click to expand...
Click to collapse
Noo, but do you know where those files may be? what folder directory? cause isn't it supposed to be the cwm folder

x10user2011 said:
Noo, but do you know where those files may be? what folder directory? cause isn't it supposed to be the cwm folder
Click to expand...
Click to collapse
depends on your recovery version. I'd suggest to go make sure you have the latest one.

BWolf56 said:
depends on your recovery version. I'd suggest to go make sure you have the latest one.
Click to expand...
Click to collapse
I just realized that I deleted all the stuff within my 0 folder before realizing that my backups were there... This was a long time ago but what can I do now that I dont have those files in the 0 folder? I really need to delete the backups because they are taking up my space on the internal storage

x10user2011 said:
I just realized that I deleted all the stuff within my 0 folder before realizing that my backups were there... This was a long time ago but what can I do now that I dont have those files in the 0 folder? I really need to delete the backups because they are taking up my space on the internal storage
Click to expand...
Click to collapse
Update your cwm recovery (on clockwordmod website).
PS.: Can't you delete old nandroids in recovery?

BWolf56 said:
Update your cwm recovery (on clockwordmod website).
PS.: Can't you delete old nandroids in recovery?
Click to expand...
Click to collapse
can you please link it? I dont know where to find it on the site sorry :\

x10user2011 said:
can you please link it? I dont know where to find it on the site sorry :\
Click to expand...
Click to collapse
Or use ROM Manager to update to the latest CWR. That's the easiest way instead of flashing the .img file.

Or if you've even bothered to use the search you'd know that rom manager just causes issues and download goo manger from play store and use twrp recovery. Problem solved
Sent from the scary door....

need help with flashing a 4.2.2 rom from tw..

basically whats happening is im currently on fre3 rom and i want to try out liquid, but when i flash liquid my internal sd is wiped? everything from downloaded items, backups from titanium, to my twrp backups and anything in the internal sd is gone
now i suspect it has something to do with the way 4.2.2 roms deal with the users and that whole 0 folder thing, but my question is, is there any way to keep the contents of my sd card so liquid will see it?
because when i pop it into my pc, theyre gone gone, its not like they were overlooked (happened when i tried another rom)
any ideas?

therenegadenail said:
basically whats happening is im currently on fre3 rom and i want to try out liquid, but when i flash liquid my internal sd is wiped? everything from downloaded items, backups from titanium, to my twrp backups and anything in the internal sd is gone
now i suspect it has something to do with the way 4.2.2 roms deal with the users and that whole 0 folder thing, but my question is, is there any way to keep the contents of my sd card so liquid will see it?
because when i pop it into my pc, theyre gone gone, its not like they were overlooked (happened when i tried another rom)
any ideas?
Click to expand...
Click to collapse
No matter what, when you wipe your phone, it wipes internal memory....... At least I'm pretty sure..

Joe0113 said:
No matter what, when you wipe your phone, it wipes internal memory....... At least I'm pretty sure..
Click to expand...
Click to collapse
yea but to an extent no? i mean i always am able to restore things from titanium with no issue, also it erases twrp backups? thats never happened before
also i cannot delete that 0 folder at all, in phone or plug to computer, theres a folder in it, anbech? and in that theres a backup file? an sh file? it wont let me delete it at all

therenegadenail said:
yea but to an extent no? i mean i always am able to restore things from titanium with no issue, also it erases twrp backups? thats never happened before
also i cannot delete that 0 folder at all, in phone or plug to computer, theres a folder in it, anbech? and in that theres a backup file? an sh file? it wont let me delete it at all
Click to expand...
Click to collapse
Download ES File Explorer and you can delete it. Just make sure you don't delete important folders/files.

Joe0113 said:
Download ES File Explorer and you can delete it. Just make sure you don't delete important folders/files.
Click to expand...
Click to collapse
i have es file explorer, and it still wont let me
if i restore back to my tw rom which is 4.1.2 the 0 folder is there, and its the only folder in there, and every time i try, it says i cant

Joe0113 said:
No matter what, when you wipe your phone, it wipes internal memory....... At least I'm pretty sure..
Click to expand...
Click to collapse
This is not true. I've been installing custom ROMs for a long time and I've never had this. If you're restoring a 4.1.2 ROM (like FRE) and all your files are gone then you may have accidentally wiped your internal memory somehow. You are correct in saying that when you flash a 4.2.2 ROM, a new directory gets created called "0" but when flashing back to a 4.1.1 your old files should reappear, only with a new directory called "0.". The best way to avoid this problem all together is, whenever flashing from a 4.1.2 to a 4.2.2 ROM, before doing so copy all the contents of your internal SD card to your desktop (or external storage if you have the space), then when doing your wipes (just b4 flashing your new ROM), wipe your internal memory. Once you're all booted into your new ROM, go back to where ever you copied your internal SD card and copy them back to your internal SD directory. Again you only need to do this when going from a 4.1.x ROM to a 4.2.x ROM (or vice versa).
Good luck!
Hello my name is George and I'm a flashoholic.
EDIT: BTW, for future reference you should put your twrp backups on external.

External sd card doesnt get wiped when the upgrade from 4.1.1 to 4.2.2 as i have my backups stored on internal but should move them to external sd .
Sent from my SPH-L710 using xda app-developers app