yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] builtboosted:
I can confirm the latest cwm work fine. No issues with multiple folders and I can restore from 4.1.2-4.2 and back with no issues
[Samsung Galaxy Nexus] jeremysherriff:
Sorry guys, I thought I had a really good handle on this but seems I've been fooling myself.

I've installed cwm 6.0.1.5 and done a backup, to confirm where I should move my previous backups to (not that they would be useful, but I like a tidy house).

Data was created on /data/media/clockworkmod (as expected, right) but I now have a warning that my storage space is low.

Investigating, I have 4G free on /sdcard but my system ("data" ?) partition has filled up. Checking, /data/media is *not* a symlink to /storage/emulated/0 - should it be??

Coz if it's not supposed to be, then I have some serious storage space problems.

TIA

Edit: NVM, I flashed the stock rom image from developer.google.com and then started over, it's too hard to fix all the symlinks if they get messed up.
[Samsung Galaxy Nexus] AbhishekS:
6.0.19 is made for 4.2 but can I use it on 4.1.2 too?
[Samsung Galaxy Nexus] jeremysherriff:
Yes

Sent using xda app
[Samsung Galaxy Nexus] AbhishekS:
Just flashed it. Visually obviously I see no differences even though previously I was using a very old version of CWM but still it gives me the psychological satisfaction of being on the latest version. :D

BTW what is this new feature - flash from sideload?
[Samsung Galaxy Nexus] Khizar:
from what i understand it flashes a file that is on your pc using the usb cable
[Samsung Galaxy Nexus] jeremysherriff:
Don't run it unless you really have something to flash - there's no way out !!

It gives people some on-screen instructions about pushing files via adb - useful for people unfamiliar with adb, or who want to copy to device & flash in one step.
[Samsung Galaxy Nexus] AbhishekS:
I didn't get what you meant by 'no way out'!

And this thing seems to be of my use as I don't have any knowledge about adb commands and want to learn about it.
[Samsung Galaxy Nexus] jeremysherriff:
If you chose this option but cannot supply a file, you must pull the battery out to escape.
[Samsung Galaxy Nexus] phegard:
There is no "go back" menu when you come "flash sideload" screen.

So if you mistouch it and get in to this screen, you have to pull out the battery to exit this situation.
[Samsung Galaxy Nexus] EddyOS:
Anyone tried 'adb reboot-recovery' if you get stuck in adb sideload and see if that reloads? Not flashed it yet as I'm in work but thought I'd suggest it :)
[Samsung Galaxy Nexus] pa.pn2:
just to clarify for now

i am on 4.12 and flashed 6.0.1.9 cwm recovery today

if i backup now my 4.1.2 rom and flash a 4.2 rom, i will have no problems to return to 4.12 afterwards if i like to?

i did that with 6.0.1.4, and i had this weird sd card structure with the 0 folder, and had no chance to nandroid restore, cause my backup was in the 0 folder, and not anymore in the main structure of the sd card...
[Samsung Galaxy Nexus] Khizar:
use this guide to keep the old sdcard format..

xdaforums.com/showthread.php?t=1999214
[Samsung Galaxy Nexus] pa.pn2:
had a look at it

do i really have to do the whole procedure of flashing stock,unlock, root....flash 4.2 rom?

otherwise i always will have this 0 folder on sd card?
[Samsung Galaxy Nexus] Khizar:
yes you have to do everything exactly as it says..
[Samsung Galaxy Nexus] pa.pn2:
hmm ok. so the new multiuser feature wont be there anymore, right?

if i follow these steps, i can afterwards copy my 4.12 backup back to internal storage and i could restore,right?

what shall i do with this obb folder?
[Samsung Galaxy Nexus] Khizar:
there is no multi-user feature in the gnex.. its for tabs only.

as for the obb folder if its empty just delete and if it has stuff in it check to make sure that you its all there in the "0" before deleting it

and if all you want to do is restore a backup you can transfer that your cwm to sdcard and restore, no need to follow this guide
[Samsung Galaxy Nexus] pa.pn2:
i will follow your guide of course when miui hits the 4.2 update:)
[Samsung Galaxy Nexus] m.is.for.michael:
Paranoid Android will have multi user feature.... :D
[Samsung Galaxy Nexus] Khizar:
yeah.. i read about that, but didnt flash the preview build will have to see if it effects sdcard format after they release it officially
[Samsung Galaxy Nexus] cloney:
My backup file is missing from the CWM Recovery backup folder that I can access to via USB. I flashed to 4.2 via Bigxie Odexed odexed flash file and encountered the sdcard/0/ problem. After flashing a couple of times I updated CWM so it wont create /0/ folder after every flash. But now when I do a nandroid backup it creates the file in the CWM recovery folder above the sdcard/0/ folder where my original SD card files are. I cannot see it via USB nor ES File manager even with all root access. I can only see it in the recovery mode under restore backups.

The problem with this is that I cannot backup my backup onto my local desktop harddrive so I can save space on the phone itself. Does anyone know how to get the correct folder with the backup file to show?

Thanks,
[Samsung Galaxy Nexus] osm0sis:
CWM Unofficial "Nightlies" Changelog:

https://github.com/CyanogenMod/android_bootable_recovery/commits/jellybean

Nov 16, 2012 - 6.0.1.5 is the most recent on ROM Manager, fixes nesting /sdcard/0/0/0 issue with ROM flashing on JB 4.2+, and the dup format MD5 issue.

Nov 16, 2012 - 6.0.1.6 version bump for new device support. No other changes.

Nov 17, 2012 - 6.0.1.7 more backup completion logging, support for fallback to single buffering video if dual fails as out of memory, and a potential fix for mako.

Nov 17, 2012 - 6.0.1.8 just another revision bump, no changes.

Nov 18, 2012 - 6.0.1.9 reverts the mako hack fix.

Dec 15, 2012 - 6.0.2.2 larger font for 1080p+, backup format is now tar again by default, format choice menu now displays correctly and shows currently chosen format, wipe battery stats option removed, sdcard partition menu fixes, fixes for dedupe and a crash during backup.

Dec 16, 2012 - 6.0.2.3 revision bump. No other changes.

(For an unofficial list of other changes between recent versions, see my previous changelog.)

Known Bugs:

- Sideload does not have a confirmation, so if triggered by mistake a battery pull is required if no USB connection is available to make it exit.

- Factory reset option may still wipe the /data/.layout_version file, resulting in the /0/0/0 issue; use format data instead. (Need confirmation on this bug).

[ No attachments since a newer official has been released. ]
[Samsung Galaxy Nexus] hshaikh:
yea i am wonding this exact same thing. i dont know where the backup is stored? il like to save that 700 mb to 1GB on the phoen for me
[Samsung Galaxy Nexus] beaubin:
The new backups are stored in root\data\media\clockworkmod\backup folder as well the folder next to it called blobs.
[Samsung Galaxy Nexus] cloney:
That does show where my backups are. Is there anyway i can link to this folder via USB to copy to desktop? I can see it via ES File manager.
[Samsung Galaxy Nexus] AbhishekS:
Is there a method by which I can take a nandroid backup directly to a pendrive and also restore the same by just connecting it?
[Samsung Galaxy Nexus] osm0sis:
No, beaubin is correct, /data/media/clockworkmod/ is where they need to be. You can't access that directory when the regular OS is booted since it mounts them differently due to the mulitiuser sd, but that's where it makes sense for them to be so the CWM backups are outside of any one user's account; it's for every account. The ones you see in file manager are in the /sdcard/0/clockworkmod/ directory (the user 0 sdcard, ie. you), and that's why you don't see them in CWM, because the upgrade to 4.2 moved everything in /sdcard/ to /sdcard/0/.

Is everyone clear now?

To get them back you need to connect to your PC, boot to CWM and adb shell in. Then mount data in CWM. And mv /data/media/0/clockworkmod /data/media/

Done. Please stop repeating the same questions and complaints. Nothing is broken, you just haven't read enough yet.

---------- Post added at 03:51 PM ---------- Previous post was at 03:49 PM ----------

I think CWM has USB OTG support, but I could be wrong. Try it out? :)
[Samsung Galaxy Nexus] m.is.for.michael:
opening adb shell while in recovery and creating a symbolic link between /data/media/0/clockworkmod and /data/media/clockworkmod gives me the best of both worlds as far as backups go. This way the data is visible in android and in recovery.

Sent from my brain using telepathy
[Samsung Galaxy Nexus] jeremysherriff:
Something like this?

adb shell
mv /mnt/shell/emulated/clockworkmod /mnt/shell/emulated/0/
ln -s /mnt/shell/emulated/0/clockworkmod /mnt/shell/emulated/clockworkmod

Prolem is, I get "link failed Function not implemented" or "link failed Function not permitted" if I try this from ADB while Android is running.

And I get nothing if I use ADB while in recovery (ADB devices shows no device). This is using CWM.

A little help?

---------- Post added at 12:32 PM ---------- Previous post was at 12:18 PM ----------

Sorted:

adb shell

# If your clockworkmod directory needs moving into the "visible" part of your sdcard:
mv /data/media/clockworkmod /data/media/0/

#now link to the clockworkmod dir on the visible portion of the sdcard:
cd /data/media
ln -s 0/clockworkmod clockworkmod
[Samsung Galaxy Nexus] NCguy:
I get it! I think, lol. Thanks for your patience, you've really helped a lot and this can be confusing stuff. I hope the ultimate benefits make it worth the added complexities it brings to this community of people.

while adb is the most elegant and efficient way to transfer those files to the PC, can't you go around the horn and use a root-level android file manager to copy the files from /data/media to /data/media/0 (assuming space available) and then mtp them back to your pc?

I know that's a very inefficient and lengthy process and you would never suggest it but in theory shouldn't it work? There are kit centric people out there that may be rooted and rommed and don't want to learn the tools at the most fundamental level?
[Samsung Galaxy Nexus] jeremysherriff:
See my post (one above yours) for a way to permanently link into both locations, allowing for MTP access.
[Samsung Galaxy Nexus] osm0sis:
Good solution, I don't think there's a need to move them back to /data/media/0 though if you're just going to symlink. Should work both ways for the File Managers/MTP, no? I'd think you could just as well leave them in /data/media/ and put the symlink in 0/.

Edit: Thought about it some more and I guess MTP would depend on how the MediaStore handles symlinks. I'll do some experimenting and report back. :good:
[Samsung Galaxy Nexus] NCguy:
I agree symlinks are the better solution. I'm a bit hesitant only because I've never created one and I don't know the potential side effects. Are they only session active or do they become permanent?
[Samsung Galaxy Nexus] osm0sis:
Should be permanent since it's the same idea as a shortcut file in Windows (just no metadata), but they're fairly simple to remove again in the shell too.

From the dir with the symlink in it:

unlink <filename>

or

rm <filename with no slash>

The no slash is important, if you put the slash it might try to remove the directory/contents you linked to. I haven't done it before either, so I'd try unlink first. ;)
[Samsung Galaxy Nexus] jeremysherriff:
Agreed, should be fine either way.
[Samsung Galaxy Nexus] osm0sis:
Cool. :)

And on devices that actually use the multi-user framework it'll make more sense since the clockworkmod folder will still be central, but each user could have a symlink in their personal sd. koush should build making those symlinks into CWM. Add it to the list I guess! ;)
[Samsung Galaxy Nexus] osm0sis:
Yeah, so I tested it out my way and MediaScanner/MediaStore DB doesn't recognize symlinks; so your method is the only way to get them visible with MTP. :good: Unfortunately it's not a very good solution for multi-user tablets unless you want it so that only 1 user is allowed to move the backups off. Could work I suppose. Meh. Oh well. :p
[Samsung Galaxy Nexus] NCguy:
Regarding tablet users, wouldn't user 0 actually have control of the entire CWM store using this method? Not that it would be an issue for me personally.

Also,

CWM itself would have to use the symlink to access the store using this link wouldn't it? Do the links work in recovery mode?
[Samsung Galaxy Nexus] right7left:
Can I just use ES file copy those cwm backup to /sdcard/0/ and copy it to my desktop via USB?

And if I flash a 4.2 ROM and want to restore a old backup created by 5.0.x.x cwm), can I just flash back the old cwm and restore it?

thanks
[Samsung Galaxy Nexus] Khizar:
yeah just move everything back to data/media from the "0" folder to restore a 4.1.2 backup and next time use this guide when updating to 4.2, you will keep the same sdcard format no more "0" folders

xdaforums.com/showthread.php?t=1999214
[Samsung Galaxy Nexus] osm0sis:
Possible news about what's coming:

From: https://plus.google.com/u/0/103583939320326217147/posts/b6cSma5GiSQ.
[Samsung Galaxy Nexus] jeremysherriff:
CWM does follow the symlink for reading, I'll test writing in a minute and post back, but I can't see why it wouldn't work.

I can imagine that a second user (/sdcard/1) would be created and then the original user removed, so that needs to be considered. Anyone got a tablet with 4.2 and can test behavior of deleting the first user?

Edit: CWM follows the symlinks fine in recovery mode (as expected)

Sent using xda app
[Samsung Galaxy Nexus] osm0sis:
I was looking at this the other day on my N7. The first user is considered the "Owner" and so far I don't think there is a way to transfer ownership or remove the owner without a factory reset.
[Samsung Galaxy Nexus] right7left:
Thank you;)
[Samsung Galaxy Nexus] Godra:
So I can flash ZIP recovery file using recovery?

Sorry for stupid questions, Im new to GN (used to have Xperia X8)

Tnx
[Samsung Galaxy Nexus] bartolinio:
yes, You can ;)
[Samsung Galaxy Nexus] Godra:
Tnx.Its really cool to have a Nexus device :eek: :D
[Samsung Galaxy Nexus] dratif:
I flashed the latest recovery and then flashed bigxie deodexed rom..now i have 4 Local Storages and my titanium backup is vanished.under each local storage i have 0/0 directories like hell...wtf?
[Samsung Galaxy Nexus] v12xke:
Running JB 4.2 with CWM 6.0.1.9. Using adb shell, I moved all my old backups to the data/media cwm folder. While connected to the PC via USB in Android, I see what I consider to be a "normal" file structure with no Sdcard/0 folders. In the root, /clockworkmod/backups folder is there, but backups are not stored there anymore, obviously. When I boot into CWM, and choose restore, I can see (and use) my old backups.

It used to be real handy before being able to check file sizes, rename and transfer backups to and from the PC using USB in Android. Now the backup files are not available, and it looks like adb will be needed to manipulate/ transfer backups to and from the PC? Is the intent going forward for the backups to not be visible from within Android or is this still a work in progress? Thanks.
[Samsung Galaxy Nexus] jeremysherriff:
Work in progress. For now I am using symbolic links.

Sent using xda app
[Samsung Galaxy Nexus] gautam_nexus:
Guys i i was on 4.1.2 PA rom with cwm 6.0.1.8 and I flashed to 4.2 using Factory Image using gnex toolkit...now how do I check if i have the 0 folder issue?
[Samsung Galaxy Nexus] osm0sis:
You don't. It was fixed with CWM 6.0.1.5 (official), so as long as you were on it before moving to 4.2 you should be fine.
[Samsung Galaxy Nexus] gautam_nexus:
from the screen shot:

when i click on internal storage its takes me to the contents of my sdcard and when i click on legacy it also takes me to the contents of my sdcard
[Samsung Galaxy Nexus] osm0sis:
Correct. All symlinks 4.2 creates to maintain backwards compatibility with most apps that might look for /sdcard/ or /storage/sdcard0/
[Samsung Galaxy Nexus] Langduscher:
Will this syslink thingy also work with other recoveries?
[Samsung Galaxy Nexus] gautam_nexus:
so is that a bug?
[Samsung Galaxy Nexus] osm0sis:
No. That's expected compatibility behavior from JB 4.2 like I just explained. Everything is fine. :) :good:
[Samsung Galaxy Nexus] DLM2583:
please help

Hi guys

I'm having g some weird issues I have a gs3 from bell. I rooted it and been flashing all kinds of Roms and never having any issues going back to restoring stable Roms until I decided to try twrp recovery but I noticed that I couldn't restore anything backed up by cwm so I flashed cwm though Rom manager and since then whenever I try to backup a Rom it finishes then when I try to restore them they say md5 mismatch. So after a lot of research I managed to notice that cwm isn't making any nandroid md5 files.

So my question is have I flashed a bad version of cwm through Rom manager or may I have just screwed my phones files somehow I was thinking of uprooting my phone and rerooting it but I don't know if that will fix this. Please help
[Samsung Galaxy Nexus] sk8oldschool74:
I don't think so.... I have 0/0/0/0 how can that not be a bug? My phone gets weirder every time i flash a ROM now... not too worried though my friend knows how to fix it... but I do believe it is a bug as some are not getting these zeros???

Sent from my BUGGY Nexus...
[Samsung Galaxy Nexus] jeremysherriff:
If you are getting extra 0's then you do not have a new enough recovery.
[Samsung Galaxy Nexus] AbhishekS:
I have the latest CWM recovery but I'm afraid to flash a 4.2 ROM due to extra 0s. Some people report multiple 0 folders even when on the latest CWM. Can someone confirm whether CWM tackles the 0 folders in a COMPLETELY PERFECT MANNER?
[Samsung Galaxy Nexus] osm0sis:
CWM as of version 6.0.1.5 official keeps the nested /0/0/0 issue from occurring. So yes, it's completely perfectly working now.

Of course it does not fix it if you already have them from using previous builds. You have to fix that yourself.
[Samsung Galaxy Nexus] jeremysherriff:
Yeah it works fine. But keep in mind you will get one 0 which is part of the new multi user framework. This happens on first boot. It's not a bug.

After that, you *may* have to move your cwm backups to /data/media to be able to access them inside the recovery mode. Or symlink them like I did.

Sent using xda app
[Samsung Galaxy Nexus] osm0sis:
Having one 0 is expected along with the symlinks I was explaining to him which 4.2 uses for multi-user and compatibility, respectively. Having 0s continually added with each ROM flash is the buggy behavior that 6.0.1.5 official was released to address. Make sure you're using a newer version (6.0.1.9 perhaps). As for fixing the /0/0/0 once you've previously triggered it... I'm not sure I haven't looked into that. Moving stuff back at least, but there could be a change to that user layout file (that the removal of was causing all the trouble in the first place) which needs to be made to let it know you've moved things back as well. :confused:
[Samsung Galaxy Nexus] m.is.for.michael:
Nope. Just move them. You may want to clear data from the media storage app and then gallery app to force a media scan so all your photos show up correctly.

When you think about it, android is moving everything from data/media to data/media/0 (including the existing 0 directory which then becomes /data/media/0/0) so all the system files are pointing to the highest level of zeroes, not following the user files down to the lowest level (and if it did then most people wouldn't have a problem reporting their pictures etc were missing).

I moved my files around with zero problems (see what i did there?).

Sent from my brain using telepathy
[Samsung Galaxy Nexus] osm0sis:
Haha nicely done there. ;)

That's great that it's not overly complicated. Thanks for figuring that out for everyone. :) You're definitely getting one of my next batch of Thanks. :good:

Edit: Done. :D
[Samsung Galaxy Nexus] sk8oldschool74:
My apologies osmosis... I do have the latest clockwork recovery... and you are correct it did happen before the newer version was released... I haven't flashed on new recovery so not sure and as far as restoring my file system I have never had one 0/ let alone 4 so as far as restoring my file system I'm not even going to mess w/ it at this point. I will wait for my friend who is far more advanced at all this so I make sure its done right as I learned from messing w/ my file system is bad for me until I learn more on managing it cause last time we had a problem w/ cwm putting media files in the wrong spot I tryed to figure it out and ended up deleting my radio system and was w/ out a phone for a bit till they got reinstalled by my buddy and it even took him some time to fix... So after he repairs my system I will get back to you thanx and again sorry for the misunderstanding...:)

Sent from my BUGGY Nexus...
[Samsung Galaxy Nexus] NCguy:
Osm0sis,

Can you comment on this guys approach to permanently eliminating the 0's through all forward and reverse flashes? Basically he's saying they aren't needed on the phone and all apps must maintain compatibility without them due to all the prior os versions that don't use multiuser structure and must and will continue to be supported.

http://xdaforums.com/showthread.php?p=34292849
[Samsung Galaxy Nexus] osm0sis:
Hey no worries man, no need to apologize. Hopefully your friend can fix whatever's wrong. :)

Not sure what's going on there, I guess somehow by moving it after the initial 4.2 flash they trick the layout file to use the /sdcard/ root instead of the 0 folder, which is presumably fine since the GN only has the owner user. Can't comment on how it will be if someone flashes back to stock in the future for an OTA or anything though. We'll have to wait and see.
[Samsung Galaxy Nexus] jmcdonald58:
I am unclear on this I am running 4.2 rooted havent flashed custom rom yet if I look into data/media I have 0 legacy and obb before I flash recovery what should I do? Sorry if this has been covered already for some reason I just cannot wrap my head around this
[Samsung Galaxy Nexus] osm0sis:
Read my post (#900) at the end of the last page. Also #893. ;)
[Samsung Galaxy Nexus] sk8oldschool74:
Yes this is the thread that has lead me to believe it can be done but I can understand the concept of needing a new file system as I believe it may have to do w/ new security purposes (just a thought... but I also think the reason my nexus is so buggy is do to my file system not working properly do to mixed file systems... which is causing my phone confusion so to speak... thanx for your help... like I said once back in order I will get back to you I will try twrp first to test the 0 situation out if none exists... I will let you know hopfuly the twrp devs could shead some light on what they did to fix or by pass the 0 file... but never the less I'm a cwr guy so if I end up having one zero file that I can deal w/ but 4 is beyond frustrating and not normal...

Sent from my BUGGY Nexus...
[Samsung Galaxy Nexus] osm0sis:
Yeah I honestly think you just need to move them back to the first 0 as per m.is.for.michael's instructions above and that should fix your issues, and cwm won't create any more 0's with ROM flashes if you're using one of the latest versions since that bug's been fixed. But I totally get if you don't feel comfortable messing around in adb shell. Linux is a scary place if you haven't spent a little time mucking around with it, although really, what better way to get acquainted than this? ;)

That's how I learned. I made a nandroid, pulled it to my PC along with a backup of my sdcard (adb pull /data/media/) and then felt safe knowing if I messed anything up I had it all backed up and could easily push and restore it back. :) :good: