yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] osm0sis:
Please don't post builds unless you also plan to start posting a changelog. There was 1 change since 6.0.4.0 and it was to the sideload command; there were two other version bumps with no changes so realistically there's no point other than placebo "bigger numbers"-itis. :p

Edit: I'll post one anyway since it's an official, but still... ;)

Once notified of a version bump, the most I've ever taken to post a build is a day because I was on the road. In this case, I was working on the update when you posted. In fact I could have had builds up as soon as I noticed it hit 6.0.4.3 yesterday, but I saw that there were 20 builds queued on Jenkins and suspected koush would be making it official so I waited. :good:
[Samsung Galaxy Nexus] :
OK..we'll wait for You next time :P
[Samsung Galaxy Nexus] osm0sis:
CWM Unofficial "Nightlies" Changelog - maguro:

https://github.com/CyanogenMod/android_bootable_recovery/commits/cm-10.2

Oct 1, 2013 - 6.0.4.0 is the most recent on ROM Manager, format external storage to custom fstype, fix refresh USB devices with key repeat, fix tgz multi-volume extraction, reintroduce Easter Egg, fix f2fs formatting from EDIFY.

Oct 5, 2013 - 6.0.4.1 allow sideload to be used with other commands.

Oct 6, 2013 - 6.0.4.2 revision bump for new device support. No other changes.

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

Known Bugs / Notes:

- Key test does not have a confirmation, so if triggered by mistake a hard reset is required if no USB connection is available to make it exit.

- SELinux in JB4.3 changes the permissions of su on every boot, so after any boot back to Android you will get a su warning in CWM; it can be ignored.

- If you're using the SuperSU daemonsu then you may want to create /system/etc/.installed_su_daemon to suppress the CWM dialog to disable reflashing stock recovery (the install-recovery.sh it checks for is required to run the root daemon on ROMs without a native service).

[ Attachments removed as there is a newer nightly. ]
[Samsung Galaxy Nexus] osm0sis:
BUNP :silly:

Freshly brewed 6.0.4.4 nightly.

CWM development is kinda crazy lately. cyanogen himself got involved again and PhilZ is submitting fixes to the gerrit so there's lots of action. :)
[Samsung Galaxy Nexus] D3VI0US:
Ok guys since i have a Nexus 4 now i won't have time to follow the thread here so i would like to move the OP to [MENTION=4544860]osm0sis[/MENTION] if possible
[Samsung Galaxy Nexus] GamaX320:
how to fix every tim reboot system always asking fix root????
[Samsung Galaxy Nexus] osm0sis:
On it! :) Thanks so much for everything.

OP updated, new second post with past changelog list coming soon.

Known issue listed in my changelog posts. I'll try and find a place in the op for the issues (and headline features) as well.

Edit: Done! :D
[Samsung Galaxy Nexus] Lancez:
accidently formated factory folder, now i have generic IMEI instead of my own, now i have no signal at all :( i do have a backup rom on my computer and restore it will work, but i don't think i still have that EFS folder on my backup anymore. tried Ktool and EFS professional tool, but none of them worked. dose anyone have any idea how i can get back my EFS/IMEI? thanks in advance
[Samsung Galaxy Nexus] osm0sis:
Yikes! :(

Try here:

http://xdaforums.com/showthread.php?t=1264021

Might be your only hope.

Then remember to backup your efs if you get it working again:

http://xdaforums.com/showthread.php?t=1352371

Pretty much a necessity on Samsung devices.
[Samsung Galaxy Nexus] Lancez:
thanks, 1 more favor to ask, can you show me your /factory folder?
[Samsung Galaxy Nexus] osm0sis:
/factory/

bluetooth/bt_addr
imei/mps_code.dat
lost+found/
wifi/.mac.info
.nv_core.bak
.nv_core.bak.md5
.nv_data.bak
.nv_data.bak.md5
.nv_state
hdcp.keys
nv.log
nv_data.bin
nv_data.bin.md5
wv.keys

You may be out of luck since you actually formatted it... That link assumes the directory still exists even though your IMEI is screwed.
[Samsung Galaxy Nexus] Lancez:
after i restored my early nandroid backup, there's only lost+found folder in factory folder. i guess i'm screwed :crying:

P.S. i think the imei/mps-code.dat is where the imei stored
[Samsung Galaxy Nexus] savantist:
flashed 6.0.4.4

btw, how to get or see the rainbow mode easter egg? :D
[Samsung Galaxy Nexus] mrgnex:
Few posts back it was told.
[Samsung Galaxy Nexus] Lancez:
sorry to quote my own post, but i have fixed my generic imei problem after wiped factory folder from recovery yesterday. so be extremely careful when you go into mounts and storage on 6.0.4.4, coz there's a wipe factory option and if you accidently wiped it, you'll lose your original imei and it'll be replaced with generic imei starting with "0049xxxxx" and in my case, no signals at all.
[Samsung Galaxy Nexus] osm0sis:
And how did you fix it in the end? Don't bury the lead!
[Samsung Galaxy Nexus] Lancez:
i've come across this thread first, but it didn't work for me since i don't have backup of original factory folder. i've been thinking, if you can copy .nv_data.bin from /factory to /data/radio to fix imei problem, why can't i just do the backwards?

coz flashing my previous nandroid backup is the only way to get my phone working again, so /data/radio should contain the correct .nv_data.bin file, since nandroid backup only backs up data and system. so i just copied .nv_datda.bin and .nv_data.bin.md5 from /radio/data to /factory then clean install a ROM. now i have my imei back and phone is running like it's supposed to be.
[Samsung Galaxy Nexus] abalam:
[MENTION=4544860]osm0sis[/MENTION]

Which version of cwm had again fix permission
[Samsung Galaxy Nexus] dirtygoldfish:
Dunno why you want it back when it apparently doesn't do much, but it was taken out in the 6.0.3.5 build I believe. So 6.0.3.4 or earlier would be what you would want.
[Samsung Galaxy Nexus] abalam:
I unpack the zip so to see what script it use to make a .zip for it. Btw found it in osm0sis treat. Tnx
[Samsung Galaxy Nexus] osm0sis:
2nd OP now contains a features added/removed list with versions. Check it out! :)

Also search the thread, cyanogen wrote fix_permissions, and said himself that it causes more trouble than it's worth in the latest versions of Android.
[Samsung Galaxy Nexus] :
Just stumbled upon this to my utter surprise. Nighties for a recovery omg
[Samsung Galaxy Nexus] dmarmstr:
Lancez

Did you have do any permission changes to get those to be read from the /factory partition? I can restore my old nandroid and my phone is working, but I copied those files to the /factory partition but when I flashed a new rom the IMEI is back to the generic one. Are you still just running the nandroid backup? This really sucks that option is in there. Why would it even be there? It even shows up on the release of v6.0.4.3!
[Samsung Galaxy Nexus] Lancez:
I'm running latest AOKP 4.3.1 nightly and I have flashed a bunch of ROMs after the "incident". everything seems to be fine. I've attached couple of screenshots, hopefully it'll help you out.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Lancez:
Oh, don't forget to reboot your phone. But a clean install is what I did. Try the easy step first tho.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] dmarmstr:
By easy first step you mean the copying? Also would you mind checking the /factory in adb shell with

ls -l /factory

I want to see what the owner is listed as.

Oh yeah and how did you copy? Were you in recovery and did the copy via adb shell?
[Samsung Galaxy Nexus] Lancez:
By easy step first I meant "reboot" you phone after changed permission. Don't have computer handy.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] dmarmstr:
When you get a chance I would greatly appreciate it
[Samsung Galaxy Nexus] Lancez:
Have you tried my method? Still not working?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] dmarmstr:
When I tried earlier it didn't seem to work. In root explorer can you check the ownership of the files too?

Also if you can check permissions and ownership of the factory folder.
[Samsung Galaxy Nexus] Lancez:
They both are 1001-radio

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] gaich:
If anyone of Gnex owners is interested -

There`s a petition to Google:

Google: Update the Galaxy Nexus with Android 4.4 "Kitkat"
[Samsung Galaxy Nexus] dmarmstr:
Lancez,

Thanks a bunch. After changing the owner back to 1001:radio it appears to be working now. I wonder what all the other files/folders were for in that /factory partition and whether it will ever come back to bite us later. But for now I'm happy that I don't have to live with the old nandroid again.
[Samsung Galaxy Nexus] Lancez:
I only have a two files into one folder in the factory folder, as you can see from the previous screen shot. Hit thanks if I helped you out

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Utkarsh-ezzo:
Same happend with me,

I dont have the nandroid backup not even of /data,

what I am thinking is getting the nv_data.bin and nv_data.bin.md5 from my friends galaxy nexus's /data/radio and pating it to my /data/radio and then to /factory,

while doing this do I need to do anything more , permissions should be rwe correct???
[Samsung Galaxy Nexus] osm0sis:
You shouldn't take it from anyone else's, since your IMEI needs to be unique to your device, like a serial number. In this case, if I understand Lancez' method correctly, you don't need an old nandroid, you just need to go to your radio partition (which shouldn't have been wiped) and grab the needed files there instead.

Edit: I didn't understand it correctly. ;)
[Samsung Galaxy Nexus] dmarmstr:
Chances are he already wiped data which will wipe the data/radio location
[Samsung Galaxy Nexus] Utkarsh-ezzo:
actually all that **** happnd when I was doing a clear format , for that I did data wipe , dalvik wipe and format system and also by mistake format factory,

one ques , by doing wipe data which data do the cwm wipe? the one inide sdcard or the one on root with all folder such as radio and all??

as per my research when i formated factory and booted up, the os loaded generic imei as it was unable to find the needed files on /factory,

and os loads the vn_data.bin files from /factory to /data/radio..

so whatever files I have on /data/ radio are the one with generic imei..

m I right???
[Samsung Galaxy Nexus] dmarmstr:
Correct. You would need an old nandroid of any kind from your device to get the files out of /data/radio/
[Samsung Galaxy Nexus] osm0sis:
minor update on the su "perms fix" issue: https://github.com/CyanogenMod/andr...c0e201bf058a19eeea7db99#commitcomment-4528741
[Samsung Galaxy Nexus] Lancez:
Not if you can edits nv.data.bin file to your own imei. Or else, you'll be in trouble, it is illegal to duplicate imei in some countries.

Sent from my Nexus 5
[Samsung Galaxy Nexus] andriodee:
Okay, I am currently running SlimKat 4.4. My most recent nandroid was a 4.3 backup. I can extract the backup data somehow (I'm assuming), but then how would I get it onto my current ROM?
[Samsung Galaxy Nexus] osm0sis:
You need to learn to read a thread before posting.

1) Restore the nandroid.

2) Fix your factory partition.

3) Upgrade again as normal.
[Samsung Galaxy Nexus] andriodee:
[MENTION=4544860]osm0sis[/MENTION] I read back to where the person said they resolved the issue by copying a file and pasting it elsewhere, but I don't understand how to do that. It's clear that I've never done anything like this before, so why is it so hard for you to just help me out without chewing me out? You're telling me to just "fix [my] factory partition" like I know how to do that! The "perms_fix" link you shared just takes me to some sort of coding page for developers (apparently).

This is where I am:

1) restored nandroid.

I need to know how to fix the factory partition so I can reflash my KitKat ROM and never look back! Please just help me get this done.
[Samsung Galaxy Nexus] dmarmstr:
Restore the nandroid. Then boot into it and verify the imei is correct. Then using root explorer or similar to copy the 2 files from /data/radio to /factory. Make sure the permissions and owner match to what they are in the/data/radio folder in root explorer. Reboot and make sure it still works. Then flash your new ROM again without formatting /factory and you should be good to go.
[Samsung Galaxy Nexus] osm0sis:
I was going to link you back here: http://xdaforums.com/showthread.php?p=46376962#post46376962 ;)

It tells you which two files to move. Do that with any root explorer app.

Then here: http://xdaforums.com/showthread.php?p=47008167#post47008167

It tells you what the owner apparently needs to be on the files, you can change that from Terminal Emulator if you can't from your root explorer app,

chown -R <owner:group> <path>
[Samsung Galaxy Nexus] andriodee:
Oh, you're totally awesome, dude. Thank you so much for that! I guess I need to learn more about Android. Maybe learn how to develop. ?
[Samsung Galaxy Nexus] goorek:
So just to know for the future, is there a separate 'format /factory' option or it just gets formatted when you format /system? Don't want to do this by mistake :)

Wysłane z mojego Galaxy Nexus przy użyciu Tapatalka
[Samsung Galaxy Nexus] osm0sis:
Nah the issue is it's directly below /system in the list of partitions you can format, so some people are wiping /factory by mistake when they meant to wipe /system. You should be okay if you're careful and don't have enormous sausage fingers. :p:)

You could also just be sure to use only the volume up+down for selection on critical menus like that. :good:
[Samsung Galaxy Nexus] dmarmstr:
Just curious by why is it even an option ever? Can it be removed from cwm?
[Samsung Galaxy Nexus] osm0sis:
Yeah, I agree it likely shouldn't be. Maybe mountable but not formattable. I already put in a request but was redirected to follow up with device specific guys:

http://xdaforums.com/showthread.php?p=47186391#post47186391

Haven't gotten to that yet. Feel free to take the initiative since I'm pretty busy right now.

Edit: Left a message with djMesias today. Hopefully he's okay with fixing it for us.

[MENTION=5214480]dadenet[/MENTION] below, you don't "convert" an image to a zip, you package it with a script that flashes the image. Download one of my zips and look inside, and read the updater-script. :)
[Samsung Galaxy Nexus] dadenet:
Dear [MENTION=4544860]osm0sis[/MENTION] and friends ,

Please be so kind to link me a guide how to convert img file in to zip file to flash by recovery ?
[Samsung Galaxy Nexus] osm0sis:
CWM Unofficial "Nightlies" Changelog - maguro:

https://github.com/CyanogenMod/android_bootable_recovery/commits/cm-10.2

Oct 6, 2013 - 6.0.4.3 is the most recent on ROM Manager, another version bump for new builds. No other changes.

Oct 7, 2013 - 6.0.4.4 fix touch events on some devices, updates to loki support.

Nov 11, 2013 - 6.0.4.5 remove all extra "no" options (create .many_confirm to restore), optional swipe-based touch controls on some devices, reboot more cleanly, vold fixes, new "last path" option under install zip and menu fixes, make/clean build fixes.

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

Known Bugs / Notes:

- Key test does not have a confirmation, so if triggered by mistake a hard reset is required if no USB connection is available to make it exit.

- SELinux in JB4.3 changes the permissions of su on every boot, so after any boot back to Android you will get a su warning in CWM; it can be ignored.

[ Attachments removed since there is a newer nightly. ]
[Samsung Galaxy Nexus] Utkarsh-ezzo:
Just to inform you,

After trying many solutions available there on internet, I am here with generic IMEI, actually the challenge is the md5 of nv_data.bin i.e. nv_data.md5, it is calculated every single time, so if we change the IMEI in nv_data.bin, we will still be on generic IMEI as the md5 newly calculated and the one stored in nv_data.bin wont match, clearly logged in nv_log, this is a good security measure though by samsung.

the solutions I found are:

1) downgrade to 4.0.2, use those software+hardware boxes and UART cable to flash IMEI ,(this box's software also change the md5 in nv_data.md5 to the new one)

2) get .nv_data.bak & .nv_md5.bak form /factory from some friends gnex who knows what he is sharing, and put it in your phone and flash a new rom cleanly.

This is for those guys like me who have totally lost their nv files, i.e. no nandroid backup and nothing..

BTW now I am using my gnex as a tab with 3g connection...

and a nokia for all calling and stuff..urgh
[Samsung Galaxy Nexus] skraam:
Is there a "tar" file available? I wanted to flash 4.4 and forgot to update recovery, so i'm stuck without OS and can't move any files to my phone. only way possible for my pc is to odin flash this new cwm, but i can't find tar file.
[Samsung Galaxy Nexus] Utkarsh-ezzo:
or the other way,

get the .img file , boot into fastboot(bootloader), flash .img using fastboot

the comand will be

fastboot flash recovery name-of-image-file.img

thats it...
[Samsung Galaxy Nexus] skraam:
I don't have Android SDK and haven't used fastboot, but I guess I can't get tar file, so thats the only way.
[Samsung Galaxy Nexus] Utkarsh-ezzo:
no need of full SDK , only platform tools which has fastboot in it is available in zip format google it , also get the fastboot drivers,

or best way is you can use the galaxy nexus toolkit, it will do all these things for you...
[Samsung Galaxy Nexus] skraam:
Something is wrong and can't get fastboot to work. Just flashed stock rom via odin, but recovery is missing and now i can't find any recovery tar file. links are broken or something, maybe someone could help? after i can install recovery via odin I will be able to update it and all, but can't get there. :(
[Samsung Galaxy Nexus] Braakie:
I have made a recovery cwm 6.0.4.3 for odin converted with toolkit, but not tested.
[Samsung Galaxy Nexus] skraam:
Thank you very much.
[Samsung Galaxy Nexus] Mevordel:
Maybe the information in http://xdaforums.com/showthread.php?t=1606982 would be useful.
[Samsung Galaxy Nexus] miguelbaines:
I am guilty of accidentally wiping factory too. I don't have fat fingers, but I'm using TWRP from now on. My question is, so do I either downgrade OR get the nv.data... from a friend OR do both?

Thanks.
[Samsung Galaxy Nexus] Utkarsh-ezzo:
not just downgrade u will need those harware box ,

and about getting files from frnd is whole dffrnt thng, it dont need downgrading but your phone will be having same IMEI as of your friend, and duplicate IMEI is banned in some countries so be sure about it first
[Samsung Galaxy Nexus] miguelbaines:
Well, good thing the new sim card for my Nexus 5 arrived... Still would like to revive the Galaxy Nexus.
[Samsung Galaxy Nexus] osm0sis:
Definitely try to restore it from the radio folder as previously discussed. That is your legit IMEI and entirely legal.
[Samsung Galaxy Nexus] Utkarsh-ezzo:
Finally repaired my gnex, took it to local mobile repair shop, he did it with spt box, and he flashed some dffrnt firmware first (was able to see boot animation only and it was android in blue color) and then the 4.0.1 ,

now I have all other files loke bluetooth etc with nv data files in /factory..

thank you all for the support.

P.S. they charged INR 800 for the same.
[Samsung Galaxy Nexus] osm0sis:
Try 6.0.4.5?
[Samsung Galaxy Nexus] ScardracS:
No, i haven't tried it yet
[Samsung Galaxy Nexus] qf19910623:
I cant flash CM10.2 stable with CWM 6.0.4.5 nightly:(
[Samsung Galaxy Nexus] osm0sis:
Explain.
[Samsung Galaxy Nexus] qf19910623:
For the command "assert(getprop("ro.product.device") == "maguro" || getprop("ro.build.product") == "maguro");"

When I use CWM 6.0.4.3 stable it works normally.
[Samsung Galaxy Nexus] osm0sis:
Weird. I don't have that problem on my device. Some people were reporting sporadic problems with getprop on other devices lately though. Interesting..
[Samsung Galaxy Nexus] Ashtrix:
There's been a new rel of PhilZ Advanced recovery !!
[Samsung Galaxy Nexus] erghetto:
is there a flashable zip of CWM 6.0.4.3? not touch version

edit: oh and do i lose something upgrading recovery? i mean all i have on sdcard
[Samsung Galaxy Nexus] qu4nd:
Why don't you take latest version 6.0.4.5?

And no, you'll not lose anything at all by updating your recovery...
[Samsung Galaxy Nexus] erghetto:
that is a nighlty.. i prefer the stable version
[Samsung Galaxy Nexus] osm0sis:
There's absolutely no difference in those that get posted to ROM Manager and those that don't. It's all just a matter of laziness to update the site. 6.0.4.5 is the current release for the N5, for example. ;)
[Samsung Galaxy Nexus] drive2droad:
There's a new version out 6.0.4.6 !!
[Samsung Galaxy Nexus] joesalve:
where?
[Samsung Galaxy Nexus] osm0sis:
CWM Unofficial "Nightlies" Changelog - maguro:

https://github.com/CyanogenMod/android_bootable_recovery/commits/cm-10.2

Oct 6, 2013 - 6.0.4.3 is the most recent on ROM Manager, another version bump for new builds. No other changes.

Oct 7, 2013 - 6.0.4.4 fix touch events on some devices, updates to loki support.

Nov 11, 2013 - 6.0.4.5 remove all extra "no" options (create .many_confirm to restore), optional swipe-based touch controls on some devices, reboot more cleanly, vold fixes, new "last path" option under install zip and menu fixes, make/clean build fixes.

Jan 1, 2014 - 6.0.4.6 memory usage improvements, fix vold formatting, menu fixes, move all recovery settings to one file in /data/media/0/clockworkmod/, code cleanups, update loki support to v2.1, revert to old Andy with earwiggle (I worked around this change in the ramdisk because it was hideous).

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

Known Bugs / Notes:

- Key test does not have a confirmation, so if triggered by mistake a hard reset is required if no USB connection is available to make it exit.

- SELinux in JB4.3+ changes the permissions of su on every boot, so after any boot back to Android you will get a su warning in CWM; it can be ignored.

- Default format menu doesn't update.

[ Attachments removed since a newer nightly is available. ]
[Samsung Galaxy Nexus] rahimali:
I seem to have messed up real real bad here. accidentally formatted factory and now stuck with generic IMEI without a prior nandroid :(

why in the hell did those people have to enable that option anyways? :(

somebody please help...
[Samsung Galaxy Nexus] qu4nd:
Did you do a backup of efs in the past? Imho rule number one: backup efs first!

But you're right, the spot for format rectory option is quite bad...
[Samsung Galaxy Nexus] rahimali:
no nandroid backup unfortunately :(

it's really highly irresponsible of the people involved to make formatting factory (even accidentally) so easy, especially when recovering from the loss is so tough... :(
[Samsung Galaxy Nexus] m.is.for.michael:
Only a partial solution, but see here:

http://xdaforums.com/showthread.php?p=48101537

sent from my brain using telepathy