yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] devil snake:
Is it OK if I take EVERYTHING in my "Data/Media/0" and move it to "Data/Media" ??

Will that get things how they used to be?
[Samsung Galaxy Nexus] NCguy:
If you are on 4.2 or above the new official location is data/media/0. There is a possible workaround back to /data/media but its not as simple as moving your files. I would probably avoid it unless you're the adventurous type.

Here's a link to the workaround if you're still interested:

http://xdaforums.com/showthread.php?p=34292849
[Samsung Galaxy Nexus] darko.baruh:
OK thanks
[Samsung Galaxy Nexus] devil snake:
Began copying everything before I had seen your answer.. then during the process I saw it and feared the worst xD

But it's all good.

Moved everything and deleted 0\ thingy.. that simple..
[Samsung Galaxy Nexus] NCguy:
I don't think it is. According to the thread for it to be set you still need to flash. I'll bet your symbolic links are hosed. Honestly I don't know enough to say for sure. Good luck and I hope it works. If you have problems down the road you can always flash a stock rom.
[Samsung Galaxy Nexus] Khizar:
yeah and thats exactly why i told him to flash twrp.. i clean flash all roms so i wipe data every time i am about to flash a rom and havent had any issues on twrp
[Samsung Galaxy Nexus] airswoosh1:
In my experience, if you are on CWM 6.0.1.9, there isn't a need to move all your files, but if you need access to your earlier backups, move your clockworkmod folder from data/media/0/ to data/media/......that's all
[Samsung Galaxy Nexus] devil snake:
On day 2.

Apparently not everything was ok. I'm having problems side-loading, and about 300 Camera-shot pictures were corrupted (out of about 450) and pictures in the 'Download' files were ALL corrupted..

Good thing I don't really care about those minor losses. But now I'll backup my SD and wipe the entire phone clean (SD and System storage).. Hope this fixes things.

Android 4.2 gave me more more headache than features.. If I had known i wouldn't have updated until I had enough time to waste -__-

Just thought I'd follow up my earlier claims for people who might have wanted to just copy stuff as i did.
[Samsung Galaxy Nexus] NCguy:
That should take care of it
[Samsung Galaxy Nexus] jeremysherriff:
Best thing to do is flash the entire factory image of 4.2 (or 4.2.1 if there is one??) including all data parts, push in CWM, then apply Bigxie's stock/OTA edition over the top to get root etc. Fixes everything 100% but of course you lose all the sdcard contents.
[Samsung Galaxy Nexus] sk8oldschool74:
Has v6.0.1.9 become an official update or is it still a test version??? Forgive me for my lazy question... ;):)
[Samsung Galaxy Nexus] aR_ChRiS:
Latest official version is always on the rom manager website.

=>Most of the attached builds here are unofficial.
[Samsung Galaxy Nexus] sk8oldschool74:
6.0.1.5 works fine Thanx.. :rolleyes:
[Samsung Galaxy Nexus] Kalavere:
Where is 6.0.1.9 backing up my Nandroids? I've got a '/0' a '/0/0' a 'legacy', 'obb'. I've got Nandroids I can't access via CWM because it says they aren't on the SD card. Where can I move them so CWM can access them?
[Samsung Galaxy Nexus] 3rdstring:
look in /data/media
[Samsung Galaxy Nexus] NCguy:
I'm going to try and help you since nobody else is jumping in but I warn you I am no expert. This is just what I've picked up mostly from reading.

First, your backups, since the new CWM, should be in /data/media/clockworkmod. That's the new permanent home. Move the older Nandroids there using a root file manager.

Second, you should move all of your data from the last /0 to the first and then delete all the subsequent /0 folders.

Third, if you still are messed up after all that then you may want to start over from scratch by flashing a new stock 4.2.1 rom. Make sure you are fully backed up first including internal sd.

This is all subject to an experts verification.
[Samsung Galaxy Nexus] osm0sis:
I'm not going to make a habit of this but, since koush has updated a separate branch that the public can't build from using builder.clockworkmod.com to 6.0.2.1 (for mako) already, I'll release an interim "6.0.1.9+" unofficial build (to distinguish it from the existing 6.0.1.9 builds) with the few fixes he has merged into the main branch from his mr1-staging testing branch so far.

Things that have changed: tar is now the default format again, the format selection submenu is fixed, wipe battery stats is gone because it's pointless, some other stuff.

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

[Attachment removed since new version posted.]
[Samsung Galaxy Nexus] DJxSpeedy:
so we can use it as stable ?
[Samsung Galaxy Nexus] osm0sis:
Yeah it works just the same, just with some fixes.
[Samsung Galaxy Nexus] DJxSpeedy:
ok man thx then i install it now ;)
[Samsung Galaxy Nexus] NCguy:
Interesting. Do we know why he changed back? Was it just not worth the extra complexity?
[Samsung Galaxy Nexus] NCguy:
BTW, its ok to flash the new recovery using the older cwm recovery isn't it?
[Samsung Galaxy Nexus] 3rdstring:
yes
[Samsung Galaxy Nexus] osm0sis:
dup format is still there, just not default anymore like it's been in 6.x. I think it was just confusing for too many people, and most people want to move the backups off device easily so tar made more sense. If you want to keep multiple backups from different ROMs on your device then dup is still the way to go to save space.
[Samsung Galaxy Nexus] NCguy:
From different roms? I thought that blob folder was applied to different versions of the same rom?
[Samsung Galaxy Nexus] osm0sis:
There'll be fewer differences if it's the same ROM, but the idea of saving space with the overlapping files still applies to multiple ROMs. So yeah, for either of those usage cases, where you want multiple backups on your device, dup is better.
[Samsung Galaxy Nexus] NCguy:
Wow. Didn't realize that. Pretty cool feature. So the blob folder grows whenever it sees virgin code regardless of the rom?
[Samsung Galaxy Nexus] osm0sis:
Yeah, that's right. As I understand it, anyway. I could be wrong but I think it compares each ROM file back to the ones it has already blobbed and if they're different then they get blobbed too.
[Samsung Galaxy Nexus] jeetS:
I flashed cwm 6.0.1.9 over 6.0.1.5... It shows 6.0.1.0 as current recovery in ROM manager... But it is the touch .9 when I reboot to recovery.

Is this a .9 issue?
[Samsung Galaxy Nexus] NCguy:
I also flashed 6.0.1.9 over 6.0.1.5. In recovery it shows 6.0.1.9 but in rom manager mine shows 6.0.1.5. You are right, rom manager isn't picking up the correct version.
[Samsung Galaxy Nexus] ACHILLES R32:
ROM manager has the latest official release, version 6.0.1.9 is unofficial built.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] NCguy:
Makes sense for mine. But not for jeetS (post 1017) who flashed the unofficial and his rom manager says version 6.0.1.0?
[Samsung Galaxy Nexus] ACHILLES R32:
Did you flash the update via recovery? it could be that the text file in the cwm zip was not updated. Open in with notepad change the version number, save it and reflash.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] NCguy:
The text file changes what the recovery shows or what rom manager shows?
[Samsung Galaxy Nexus] ACHILLES R32:
Changes what the recovery shows, sorry I just realized that I misread your original post , lol. Must be a ROM Manager glitch, I always used romtoolbox pro to manage Roms and backups.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] m.is.for.michael:
ROM manager has _never_ shown the correct version for me since I first started flashing recoveries through recovery rather than ROM manager. And I have the premium version. X(

Sent from my brain using telepathy
[Samsung Galaxy Nexus] Braska90:
Hello!

Just a question... Why if I look with RomManager it says that I've no recovery installed? XD If I reboot into recovery I see the normal CW recovery...

It is safe to flash over mine version the new 6 version of CWM?

Details:

- Rom : Slim 3.1.0 (JB 4.1.2)

- Kernel : 3.0.48 LEan Kernel

- CWM : 5.8

-Tapatalked with GNexus-
[Samsung Galaxy Nexus] 2stardiver:
help panic?!

I did have good working slimbean, but I did like to test 4.2 xenon rom.

well I did get backup with cwm 6.0.1.5 and after one guy helpful tip it I manage to get one backup with tar, not just incremental version.

I didn like xenon so I did try restore and now it tells me

"couldnt open directory no files found"

I did allready upgrade cwm to 6.0.1.9 version but same message.

it has to do somehow folder naming, under sdcard there is 0 directory.

so how can I get restore back ?
[Samsung Galaxy Nexus] NCguy:
Look for cwm folder in /data/media with a root file manager?
[Samsung Galaxy Nexus] 2stardiver:
How do I do that in cwm ?

mounting data wont help, mount sdcard wont even succeed.
[Samsung Galaxy Nexus] NCguy:
The new version of cwm will look for it there. If not, its over my head. You need to copy any old backups from /0 over to the new folder in /data/media.
[Samsung Galaxy Nexus] 2stardiver:
thanks,

/data/media/clockworkmod is empty and there is 0 directory which points to sdcard.

I will test copying restore files to /data/media/clockworkmod/backup

I use 4.2.1 xenonhd rc3 rom.
[Samsung Galaxy Nexus] m.is.for.michael:
Don't forget to copy the blobs folder also or it won't work.

Sent from my brain using telepathy
[Samsung Galaxy Nexus] 2stardiver:
one more question.

before I noticed that backups are only ~20mb. I deleted those from /sdcard/clockworkmod/backup like before older cwm version big backups, I didnt delete any blobs.

is this problem ?

and is it safe to remove all 20mb backups+blobs and take new backup only tar mode?
[Samsung Galaxy Nexus] m.is.for.michael:
No, because the first thing clockwork mod does in the backup routine is free up space used by blobs that are no longer required.

Sent from my brain using telepathy
[Samsung Galaxy Nexus] EddyOS:
I just backup using .tar - makes life a lot easier! :D
[Samsung Galaxy Nexus] sk8oldschool74:
I can't seem to find the 6.0.1.5 touch flash able zip... Help Thanx...
[Samsung Galaxy Nexus] osm0sis:
Use my .1.9+ zip a few pages back?
[Samsung Galaxy Nexus] kizakiyuria:
cwm 6.0.2.2 :D

http://jenkins.cyanogenmod.org/job/recovery/12916/artifact/archive/recovery.img
[Samsung Galaxy Nexus] savantist:
CWM 6.0.2.2 NON TOUCH:

http://jenkins.cyanogenmod.org/job/recovery/12984/artifact/archive/recovery.img

fastboot

CWM flashable non-touch:

http://share-space.undip.ac.id/download.php?file=801cwm-recovery-clockwork-6.0.2.2-maguro.zip

CWM 6.0.2.2 TOUCH:

http://jenkins.cyanogenmod.org/job/recovery/12990/artifact/archive/recovery.img

fastboot

CWM flashable touch:

http://share-space.undip.ac.id/download.php?file=147cwm-recovery-clockwork-touch-6.0.2.2-maguro.zip

build from:

http://builder.clockworkmod.com/

visible changes:

- added option to format /sdcard (also known as /data/media)
[Samsung Galaxy Nexus] osm0sis:
I'll check it out and see about a changelog sometime tomorrow. Thanks guys! :good:
[Samsung Galaxy Nexus] D3VI0US:
v 6.0.2.2 added to the OP
[Samsung Galaxy Nexus] Reviz:
Where can I read the features of this version?
[Samsung Galaxy Nexus] DJxSpeedy:
CWM flashable touch dosnt work ;)
[Samsung Galaxy Nexus] Godra:
File from first post works :D
[Samsung Galaxy Nexus] fredryk:
Can someone explain to me the need to continue building non-touch recoveries? You can still use the volume and power buttons to navigate the touch recovery, can't you?
[Samsung Galaxy Nexus] savantist:
LOL... it's funny since there isn't any differences between my upload and the OP's... :)

also that zip is working flawlessly with me... tested before uploaded... :)
[Samsung Galaxy Nexus] gpfnzl:
Good about touch = quick and easy,

Bad about touch = quick and easy, some tend to touch without reading, causing a few issues. Non-touch gives you time to read what your doing as you have to look at the screen and read more.

A matter of choice.
[Samsung Galaxy Nexus] sk8oldschool74:
So which one osmosis do you recommend??? 1.9+ or 6.0.2.2??? I don't understand i am getting 0/0/0/0 again on 1.0.1.5??? Any ways i trust your judgment osmosis my friend so i will wait your response...;):) Also waiting for an osmosis kernel... :D:D:D
[Samsung Galaxy Nexus] 15israellai:
I'm not catching up, are the newer ones for 4.2 only?

Transmitted from my Nexus Prime
[Samsung Galaxy Nexus] DJxSpeedy:
i think no...but they support 4.2.x ;)
[Samsung Galaxy Nexus] sk8oldschool74:
Well this is true but it would be nice if the text was the size of the touch and i use my touch like non touch a lot.... So touch can be used either way which is a plus... ;):)
[Samsung Galaxy Nexus] Godra:
No "Wipe Battery Stats" option in 6.0.2.2 :(
[Samsung Galaxy Nexus] sk8oldschool74:
That was already stated...;):)
[Samsung Galaxy Nexus] osm0sis:
CWM Official 6.0.2.3 Changelog:

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

Dec 16, 2012 - 6.0.2.3 is the most recent on ROM Manager, 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.

(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).

Fastboot Images Download: http://clockworkmod.com/rommanager

[Attachment removed due to newer nightly.]
[Samsung Galaxy Nexus] savantist:
CWM 6.0.2.3 NON-TOUCH

http://jenkins.cyanogenmod.org/job/recovery/13119/artifact/archive/recovery.img

b13119

:)
[Samsung Galaxy Nexus] osm0sis:
Build number is only really useful as a timestamp for when it was built; Since going back to that build on Jenkins we can compare the build date against the github commits to know where exactly it lies. That's why I include it anyway, otherwise it's meaningless. ;)
[Samsung Galaxy Nexus] EddyOS:
6.0.2.3 now on the ClockworkMod site
[Samsung Galaxy Nexus] osm0sis:
oh snap.

Edit: Checksummed the official img against mine and they're identical. Post updated with the renamed zip now. ;)
[Samsung Galaxy Nexus] sk8oldschool74:
Were are we going to find this??? So the previous 6.0.2.3 is not the one I should have flashed.... :confused::confused:
[Samsung Galaxy Nexus] osm0sis:
Identical means identical. So the one you flashed was exactly the same as the official build. All I did was rename the zip to reflect that it's official now.
[Samsung Galaxy Nexus] Juno-First:
I previously had 6019 installed & everything was fine, then installed 6022 from the front page but after doing a backup the internal memory has been wiped inc the backup... sick or what.
[Samsung Galaxy Nexus] osm0sis:
Try official 6.0.2.3 from one page back.
[Samsung Galaxy Nexus] sk8oldschool74:
Wasn't sure... If you look back a few pages I asked you about 6.0.1.9+ wasn't sure if that might have been what you were referring to... I do know what identical means...;):)
[Samsung Galaxy Nexus] gaich:
Did I miss anything? I flashed 6.0.2.3 and made a backup. No blobs in data/media/clockworckmod, there`s backup folder only. Although the old backups are sdcard/clockworckmod and there are blobs and backup folder. And the recovery proposes me to restore sdcard/clockworckmod/backup (as it is written above in the recovery section), but shows the backups in data/media/clockworkmod folder!!! Now I`ve made another backup and it is again in data/media/clockworkmod and there are nj blobs again. What`s wrong?:confused:
[Samsung Galaxy Nexus] builtboosted:
Can anyone confirm these versions working? I don't want to flash anything till i know they work as they should.
[Samsung Galaxy Nexus] D3VI0US:
v 6.0.2.3 added to the OP
[Samsung Galaxy Nexus] gaich:
Still searching the thread and trying to get the answer - with this old tar. format -I do not need these blobs anymore??? Should I leave it only when I choose dup. format?
[Samsung Galaxy Nexus] osm0sis:
Is this your first time using CWM since upgrading to JB4.2? You just have to move your backups from /data/media/0/clockworkmod/ back to /data/media/clockworkmod/ as has been explained many times. And as I wrote in my changelog post a page ago, tars are the default again (like it was pre-6.x). So if you want blobs you should go into backup/restore and change the default format to dup (dedupe) to make sure you're using the dedupe/blob format. :good:

dup was conceived to save space for those who like to keep multiple backups on their device at a time. tar makes more sense for those who like to move their backups off-device. Not sure but I don't think you can use both at the same time.. so if you've got tar as your format I don't think you can use your old dup/blob backups. If you don't need them then I'd delete the blob folder and corresponding backups; but it all depends on how you intend to store/use your backups.

Yes of course it works. It's 6.0.1.5 with more fixes (hence newer version?). ;) Check the github link in my post a page ago if you'd like to see exactly what has changed and make an educated decision for yourself. However if you're already on 6.x then there is no reason not to upgrade.
[Samsung Galaxy Nexus] gaich:
I did not move from 5.8.0.2 for a long time because of these blobs, they spoiled something when I moved from ICS to JB, but finally I gave up and flashed 6.0.1.9 and backuped my 4.1.2 image. Now I flashed the latest CWM and, thanks to God and your explanation, I don`t need these huge blobs anymore!!!!!!

But if I want to restore my 4.1.2, can I:

1) move this backup and blobs to current CWM folder;

2) switch to dup. format;

3) restore?

Will it work?:confused:

P.S.:tried your color settings -never knew my device could look so awfull!!!!
[Samsung Galaxy Nexus] osm0sis:
From what I know it should work. I haven't tried having concurrent backups in both formats though so I can't confirm it personally.
[Samsung Galaxy Nexus] sk8oldschool74:
V6.0.2.3 works awesome... I love it...:D:D:D i finally have a good recovery again praise the Lord...;):)
[Samsung Galaxy Nexus] TheShoura:
Not sure if this is intentful, but with the latest touch recovery currently linked in OP, I cannot use the Galaxy Nexus Toolkit to ADB Push files while in that recovery - it gives error about insecure boot image - where as an older recovery that was with the toolkit flashed fine and had no problems using ADB Push

Is this intentional?
[Samsung Galaxy Nexus] savantist:
just flash the flashable zip in your CWM... :)
[Samsung Galaxy Nexus] TheShoura:
You know its not often (actually, almost never) that I am this blunt with anyone...but did you even understand what I wrote?

I don't intent any malice but your reply quoting me just doesn't make sense to me :(

To clarify... The issue I have is when using the specified recovery image

Will fail to use the push file to SD card function in the toolkit, it cites an error related to NOT having an insecure boot image...

From my reasonable knowledge on how recoveries work, best practice (for what exact reason I do not know) is to flash via FASTBOOT. However, if they both do the same thing (update recovery to version 6.0.2.3), how would using the the flashable zip work differently in this situation?

I flashed an older version that came with the G-nex toolkit and that version seems to have worked as needed, allowing me to ADB Push files to my phone while in recovery... I'm curious as to what went wrong or what was different here so I can learn why that didn't work..

Can anyone share some information with me on this subject?
[Samsung Galaxy Nexus] osm0sis:
Not sure what's going on for you. ADB and fastboot both work perfectly well here, though I am just using the stripped down package from efrant's How To Flash thread (just the exe's for adb and fastboot + required dlls). So I'd suggest maybe just try that and actually try the adb push commands manually without the toolkit.
[Samsung Galaxy Nexus] flunk86:
Wipe battery stats when missing on latest ver.
[Samsung Galaxy Nexus] osm0sis:
That was done intentionally because it's a garbage option. Literally useless. Wiping hurts more than it helps.
[Samsung Galaxy Nexus] TheShoura:
I later found that ADB commands using ADB from my toolkit did in fact work fine, it seems the issue may have been related to the toolkit somehow... but at the same time, the same toolkit install works with a different recovery?? This is really bizarre to me.. am I alone on this?

There's no real troubleshooting that needs to be done for me as the problem has been overcome already, but I'm genuinely curious as to what prevented me from using that touch recovery as it was much prettier than the one I'm using now. If someone wants to poke at it, I don't mind flashing recoveries and trying to reproduce it if it would help someone
[Samsung Galaxy Nexus] osm0sis:
Probably best brought up in the toolkit thread since it's clearly their derp. ;)
[Samsung Galaxy Nexus] TheShoura:
Heheh sounds good, thanks for your input so far, much appreciated osm0sis!
[Samsung Galaxy Nexus] gpfnzl:
it's a beautiful thing.

Prefer the .tar backup method, saving complete backups off device.

adb commands ok, everything working well.
[Samsung Galaxy Nexus] osm0sis:
You're welcome, smart ass. Every panel is different. It looks amazing on mine. The whole point of my posting my color script is that init.d gives you a better result, not to have people use my color settings.
[Samsung Galaxy Nexus] osm0sis:
Just a quick note. The CWM links in my sig now go directly to my changelog post for that build, so that should make it easier for everyone to find the latest builds and info.
[Samsung Galaxy Nexus] guest_2011:
I tried flashing 6.0.2.3 over 6.0.1.9 (nexus 4 jb4.2.1). Shows flash was ok but still ver 6.0.1.9. Any other way to flash the zip file or is there a bug or something?
[Samsung Galaxy Nexus] builtboosted:
It will show the same build number until you reboot recovery
[Samsung Galaxy Nexus] guest_2011:
reflashed rebooted many times
[Samsung Galaxy Nexus] builtboosted:
Well I cannot speak for everyone but it worked fine for me.
[Samsung Galaxy Nexus] osm0sis:
Worked for me too. In weird cases like this I'd suggest fastboot flash recovery.
[Samsung Galaxy Nexus] 3rdstring:
This is the gNex thread did you DL an image for an N4?
[Samsung Galaxy Nexus] osm0sis:
Hahah good eye. I skimmed right over that! :laugh:
[Samsung Galaxy Nexus] guest_2011:
I thought it's generic. That could be the reason.
[Samsung Galaxy Nexus] playabigfoot:
Can somebody upload 6.0.2.2 flashable zip please

Sent from my smartphone
[Samsung Galaxy Nexus] osm0sis:
No. 6.0.2.3 is official and you can get flashable by following the link in my sig.
[Samsung Galaxy Nexus] sk8oldschool74:
I'm getting the 0 file problem again using 6.0.2.3 ???
[Samsung Galaxy Nexus] osm0sis:
You probably did a factory reset?
[Samsung Galaxy Nexus] gparmar76:
If your just flashing from one 4.2.1 ROM to the next, you won't have the issue...but if you go to a 4.1.2 ROM and then to a 4.2.1, you will have this issue.
[Samsung Galaxy Nexus] sk8oldschool74:
No. But i did come from 4.1.2 althoughy boot loader and factory image were 4.2 and every ROM i have flashed since my first flash of 4.1.2 has been 4.2.or 4.2.1 and still getting the 0s???
[Samsung Galaxy Nexus] gembrit:
Currently I'm on 4.2.1 ROM, can I just flash this from CWM?:confused:
[Samsung Galaxy Nexus] kizakiyuria:
yeah dude,...:D
[Samsung Galaxy Nexus] savantist:
CWM Touch 6.0.2.5

http://jenkins.cyanogenmod.org/job/recovery/13743/artifact/archive/recovery.img

tested by me

flashable zip

http://goo.gl/EUlGQ
[Samsung Galaxy Nexus] kizakiyuria:
thanks ya,...:D
[Samsung Galaxy Nexus] samersh72:
the backup is situated in /mnt/shell/emulated use root option in file manager to see it

move clockworkmod (backup file) from sd card to it