Neets: You sound all tongue twisted ;-) Ok, I've disabled that option. Waiting for my hubby's txt message to arrive. Must be doing a round the world tour first though.

I'm not sure if you're having a lend of me or it's a serious question, for which I'm now doubting the answer. But the front facing "little hole thingo, top right of the screen" is the video camera for video calling. Maybe I should be asking what Blink LED is then. I thought it was like the backlight led that would have the menu and return buttons flash.

Actually, in my mind that was what passes for a little self-deprecating humour, but apparently my mind is misinformed since it just served to confuse the heck out of you. :)

I'll leave the 'humour' to Billy Connelly in future. [Shuffles feet uncomfortably and reddens with embarrassment before slinking off into cyberspace again...]

After a very long time waiting for my hubby's test text message to arrive, and asking him to try again, I've flashed the JPP modem. I've just sent a text and immediately received a reply text. So that seems better if nothing else.

I noticed today when I went to 3G mobile data that the signal was a bit weak and my tweet wouldn't update (yeah I know, poor me). I'm not sure if the modem change will also impact 3G or not (I'm no techno geek). Now to test making/receiving a call.

Neets: After a very long time waiting for my hubby's test text message to arrive, and asking him to try again, I've flashed the JPP modem. I've just sent a text and immediately received a reply text. So that seems better if nothing else.

I noticed today when I went to 3G mobile data that the signal was a bit weak and my tweet wouldn't update (yeah I know, poor me). I'm not sure if the modem change will also impact 3G or not (I'm no techno geek). Now to test making/receiving a call.

JPP is an improvement. Text messages are sent/received immediately. Phone calls sent/received with perfect clarity and no additional noise (not that I had the problem anyway). And I can use 3G without any glitches either.

@nofam, I've been trying to do a bit of research about your mucked up IMEI number. I don't have any miracle cure, but one of the posts I had kept and saved in my early days related to the product code changing.

Mine had changed and I followed these instructions from here. I wondered if you wanted to have a look at see if your product code was correct for your phone. Mine was OPS but it's an Optus phone. If your phone came from Vodafone NZ I think it's VF something. Someone had made mention of it on this forum some weeks ago.

If you felt like having a look at your nv_data.bin file (open in Notepad - takes yonks to open, and the stuff you're searching for is way way hidden, so you'll need to use the search function.). I think the guys on the Doc forum are saying O2(something).

I wonder if it might have something to do with you not receiving calls.

And I might be barking up the wrong tree completely. Might be worth a shot if you've not yet found an answer elsewhere and not yet lost hope.

And I'm signing off for a bit. Time to spend time away from the computer (but not the phone )

Thanks so much for persevering with me Neets; I'm afraid I've not making much progress. On a tip from something I read from another forum, I replaced nv_data.bin with the one from my /efs backup, and now I have no phone functionality at all. . . . . . . Under Settings==>About Phone==Status I have:

Phone NumberUnknown

NetworkUnknown

Signal Strength0 dBm 0 asu

Mobile Network TypeUnknown

Service StateUnknown

RoamingNot Roaming

Mobile Network StateDisconnected

IMEIUnknown

IMEI SV

And back in in About phone I have

Baseband versionUnknown

When I try to go into Setting==>Wireless and networks==>Mobile networks I get:

Insert SIM card to access network services.

So yeah, not so good I fear.

Am wondering if I should send it back to Samsung, or return it to Noel Leeming? Not really sure where to from here. . . . .

Life is mostly froth and bubble, two things stand like stone - kindness in another's trouble, courage in your own.

And I'm signing off for a bit. Time to spend time away from the computer (but not the phone )

Thanks so much for persevering with me Neets; I'm afraid I've not making much progress. On a tip from something I read from another forum, I replaced nv_data.bin with the one from my /efs backup, and now I have no phone functionality at all. . . . . . . Under Settings==>About Phone==Status I have:

When I try to go into Setting==>Wireless and networks==>Mobile networks I get:

Insert SIM card to access network services.

So yeah, not so good I fear.

Am wondering if I should send it back to Samsung, or return it to Noel Leeming? Not really sure where to from here. . . . .

When I try to go into Setting==>Wireless and networks==>Mobile networks I get:

Insert SIM card to access network services.

So yeah, not so good I fear.

Am wondering if I should send it back to Samsung, or return it to Noel Leeming? Not really sure where to from here. . . . .

I think it might be time to either post a new message on XDA, or post on the Doc thread since it was flashing one of his ROM things went haywire.

Also I saw SuperCurio tweet about potential problems with the /efs after comments from 2 people. He asked others to report back and apparently it's fine. It makes me wonder though if an earlier release of Voodoo might have had problems. Might also be worth sending him a message. I know he provided some feedback on a different forum where another user had problems with the IMEI being lost.

Another thing, the other night when I suggested to copy back the /efs, you did but reported back it made no difference.

Now if I understand correctly you've copied only the nv_data.bin file and things have gotten worse. It makes me wonder if the /efs didn't actually overwrite. You'd also mentioned at one stage about not having access to r/w so perhaps it didn't work. In which case I wonder if it's worth trying to copy the /efs again now (assuming) you've got r/w access.

I think the *.md5 file is a checksum file and it's meant to be recreated (if you'd deleted it as an example) when you use your phone. And that makes me wonder now with the extra details whether the *.md5 file matches the nv_data.bin file you've copied in. Perhaps there's a mismatch.

Ok, over to you. Sorry it's not much help other than my thoughts on what I understand (and the order) in which you've attempted to fix the problem.

Oh, and I wonder if you can find the original firmware for Vodafone NZ on the samfirmware website. Maybe restoring back to the original (Eclair) build might kick things back into life, or at least make it easier to point the finger at Kies messing things up should you return the phone.

I know that the pdf suggests going back to another ROM and restarting. That might also be worth a try.

More reading:http://forum.xda-developers.com/showthread.php?t=835930http://forum.xda-developers.com/showthread.php?t=845785http://forums.whirlpool.net.au/archive/1561196 - maybe some one will answer this personhttp://www.galaxyroot.com/q-baseband-unknown-after-flashing-to-froyo/ Same person as above and I think in one of the XDA forums.

Yeah there's definitely something amiss with the /efs folder - after posting last night I had a closer look at it with root explorer, and the nv_data.bin in there is 0 bytes. . . . . .the original in my backup is around 2Mb.

I've double-checked that the phone has root access, and made sure I set Root Explorer's permissions to R/W, but if I delete /efs and then go to my external sdcard to copy the backup into root directory, efs seems to have reappeared?

I think this is a promising lead, as having a blank nv_data file would explain why all those settings showed as unknown.

Just wondering if I should try doing it from a command line or ADB?

Life is mostly froth and bubble, two things stand like stone - kindness in another's trouble, courage in your own.

nofam: Yeah there's definitely something amiss with the /efs folder - after posting last night I had a closer look at it with root explorer, and the nv_data.bin in there is 0 bytes. . . . . .the original in my backup is around 2Mb.

I've double-checked that the phone has root access, and made sure I set Root Explorer's permissions to R/W, but if I delete /efs and then go to my external sdcard to copy the backup into root directory, efs seems to have reappeared?

I think this is a promising lead, as having a blank nv_data file would explain why all those settings showed as unknown.

Just wondering if I should try doing it from a command line or ADB?

I guess the question is "what have you got to lose"? Awful question. Since you have the /efs I'd say there's a good reason to try to get the file across through Terminal or ADB.

Just make sure you've still got the download mode (volume down) so that if something goes more belly up, you'll be able to flash via Odin.

Oh, I had read somewhere where someone else reported the nv_data.bin file had a size of 0. Not sure if that had something to do with making sure there was adequate space on the internal SD before using clockworkmod to take a backup.

I've got a 16gb phone so it's never been a problem for me.

I've just done another search and Doc answered a person about whether to copy over their entire /efs and he said only the nv_data.bin file. But you've tried that, haven't you?

Thanks Neets - yes, my hunch is that when I did restore the nv_data.bin, the phone has baulked because it didn't match the md5 file; I probably need to delete/restore both, as they obviously go hand-in-hand?

From Doc's post, it sounds like you shouldn't normally need to replace the .md5, but if they get 'out of whack' like mine, it causes issues. I've read elsewhere that so long as your nv_data.bin is fine, the .md5 should regenerate on reboot?

Will take a look tonight :-)

Life is mostly froth and bubble, two things stand like stone - kindness in another's trouble, courage in your own.

nofam: Thanks Neets - yes, my hunch is that when I did restore the nv_data.bin, the phone has baulked because it didn't match the md5 file; I probably need to delete/restore both, as they obviously go hand-in-hand?

From Doc's post, it sounds like you shouldn't normally need to replace the .md5, but if they get 'out of whack' like mine, it causes issues. I've read elsewhere that so long as your nv_data.bin is fine, the .md5 should regenerate on reboot?

Will take a look tonight :-)

You have a very apt signature line for where you're at with your relationship with the phone