This won't help much. Eclair used 512. Then Froyo started with 803 fome some versions. But those who had previosly flashed using 512 were to stick wirh 512. And with some roms you don't need a pit file at all. Told you it wouldn't help :)

Correct me if I'm wrong anyone, but as I understand it, the only time a .pit file isn't specifically required is when the update file contains all of the components needed for flashing in a single .tar, and in Odin, that single 'omnibus' update file is loaded as a PDA.

Otherwise, the .pit file is a necessary configuration for validating the separate elements that are each loaded separately in Odin - PDA, modem and CSC. The downloaded 2.2.1 update I used contained the .pit file for that update.

While we're on the subject though, I noticed that in SGS Toolbox>Firmware info, my CSC shows up as 'Unknown". So it seems I still have a problem. Not certain how serious that is, or how to resolve it since I've read nothing about such issues before.

Google to the rescue maybe? Or if anybody reading this has experienced similar, your experience would be received with much interest.

Cheers,R2D2

Galaxy S has gone to its new owner. HTC Sensation has gone to its new owner. Galaxy S3 has gone to its new owner. Now using Galaxy Note 3. Skipping Note 4 I think...

ArtooDetoo: Correct me if I'm wrong anyone, but as I understand it, the only time a .pit file isn't specifically required is when the update file contains all of the components needed for flashing in a single .tar, and in Odin, that single 'omnibus' update file is loaded as a PDA.

Otherwise, the .pit file is a necessary configuration for validating the separate elements that are each loaded separately in Odin - PDA, modem and CSC. The downloaded 2.2.1 update I used contained the .pit file for that update.

While we're on the subject though, I noticed that in SGS Toolbox>Firmware info, my CSC shows up as 'Unknown". So it seems I still have a problem. Not certain how serious that is, or how to resolve it since I've read nothing about such issues before.

Google to the rescue maybe? Or if anybody reading this has experienced similar, your experience would be received with much interest.

Cheers,R2D2

Let me see if I can find the XDA thread that had a list of CSC's. Though from memory it didn't state NZ. But it had the Optus one which is what I used instead of the multi csc that comes with most of Docs Roms.

And yes you're correct. Some files for Odin contain the 3 parts. So one file incorporates 3 files. Most of the stuff I've read (and followed for Odin flashing) have the PDA first and then tackle the rest in a second round of Odin flashing.

ArtooDetoo: Correct me if I'm wrong anyone, but as I understand it, the only time a .pit file isn't specifically required is when the update file contains all of the components needed for flashing in a single .tar, and in Odin, that single 'omnibus' update file is loaded as a PDA.

Otherwise, the .pit file is a necessary configuration for validating the separate elements that are each loaded separately in Odin - PDA, modem and CSC. The downloaded 2.2.1 update I used contained the .pit file for that update.

While we're on the subject though, I noticed that in SGS Toolbox>Firmware info, my CSC shows up as 'Unknown". So it seems I still have a problem. Not certain how serious that is, or how to resolve it since I've read nothing about such issues before.

Google to the rescue maybe? Or if anybody reading this has experienced similar, your experience would be received with much interest.

Cheers,R2D2

Have a gander through this post. Damn, good job I keep notes everytime I flash my phone about where I get my info from and the steps I've used to get from A to B. (yes, pat me on the head, I'm a good girl :P)

I've applied the voodoo lagfix and tbh I've noticed that the phone still isn't really that snappy lately (particularly with browsing my 3g ipod touch is lightning fast in comparison). Is it worth trying out one of the custom roms?

If I am to start from scratch, whats the best way to do that? I've done a factory reset, but my understanding is that I'll need to reflash...what's the best way to do that?

Hi, have you decided what ROM you want? It will most likely depend on that as to what is the best way to flash.

Neets: Have a gander through this post. Damn, good job I keep notes everytime I flash my phone about where I get my info from and the steps I've used to get from A to B. (yes, pat me on the head, I'm a good girl :P)

Thanks Neets. Just had a swift dekko at the thread and it's a major mission. Basically, the procedure seems to be designed around IMEI recovery, and entails total app removal and such, with a dose of CLI commands. Not to be churlish, but the whole thing seems rather daunting. My IMEI is still valid and phone makes and received calls fine so I'm not certain that it warrants a 'start again' approach.

If I was to find it necessary to start from scratch, I think I'd factory reset and flash with an 'omnibus' updater file so it's all done in one hit, complete with re-partition and stuff. So it'd mean re-rooting, and doing a new lagfix, then installing all my apps and data. Not an insignificant undertaking.

Upside is I'm constantly learning what not to do, thanks to my seemingly endless parade of missteps.

Cheers,R2D2

Edit: And you were right about NZ being absent from the list of regions.

Galaxy S has gone to its new owner. HTC Sensation has gone to its new owner. Galaxy S3 has gone to its new owner. Now using Galaxy Note 3. Skipping Note 4 I think...

While we're on the subject though, I noticed that in SGS Toolbox>Firmware info, my CSC shows up as 'Unknown". So it seems I still have a problem. Not certain how serious that is, or how to resolve it since I've read nothing about such issues before.

Google to the rescue maybe? Or if anybody reading this has experienced similar, your experience would be received with much interest.

Cheers,R2D2

Does SGS Toolbox also list you as .nv_data.bk with the correct product code? If you don't have .nv_data.bk in your efs folder then this won't help you, but If so, you can delete nv_data.bin from your efs folder and then reboot the phone. A new nv_data.bin file will be generated from the nv_data.bk file which will then have your correct CSC/imei etc.

I agonised over this for a day after I flashed my first custom rom and found my CSC was KOR. There are countless different posts on xda forums with methods for CSC restoration and all of them left me with doubts. Deleting nv_data.bin using root explorer was nerve-racking but it simply couldn't have been easier and acheived precisely what I wanted with minimal fuss.

Before doing this, I'd advise you to have a backup of .nv_data.bin aswell as your imei somewhere safe.

Ha ha, I think your PC's clock is dodgy. I posted that at 2am. And I seem to remember a couple of your posts appearing in the dark hours pre-dawn.

Pot, meet kettle...

Cheers,R2D2

Nah, not my PC. It's saying 10:21 right this minute. The quote here is 11:10am. In the future! Geekzone seems to do strange things to the timestamp of posts. I've checked in the past to make sure I had the right settings, and I didn't. But I do now. I wonder if they get buggered up somewhere. Need to go back and check again (not that I can remember where!)

Neets: Have a gander through this post. Damn, good job I keep notes everytime I flash my phone about where I get my info from and the steps I've used to get from A to B. (yes, pat me on the head, I'm a good girl :P)

Thanks Neets. Just had a swift dekko at the thread and it's a major mission. Basically, the procedure seems to be designed around IMEI recovery, and entails total app removal and such, with a dose of CLI commands. Not to be churlish, but the whole thing seems rather daunting. My IMEI is still valid and phone makes and received calls fine so I'm not certain that it warrants a 'start again' approach.

If I was to find it necessary to start from scratch, I think I'd factory reset and flash with an 'omnibus' updater file so it's all done in one hit, complete with re-partition and stuff. So it'd mean re-rooting, and doing a new lagfix, then installing all my apps and data. Not an insignificant undertaking.

Upside is I'm constantly learning what not to do, thanks to my seemingly endless parade of missteps.

Cheers,R2D2

Edit: And you were right about NZ being absent from the list of regions.

I just added my OPS CSC folder using Root Explorer to /system/csc, then followed the last 2 steps listed under the "Automatic" method:

2. After, check your IMEI with this code on the dialer, *#06#, and save it as you'll need.

3. Then, type on the dialer, *#272*???????????????# (??????????????? it's your IMEI, it must have 15 digits), after you can chose your CSC, then it'll reboot (it may take some time, you'll see bootloader applying the changes), you'll have to do the initial configuration and it's done!

I realise that. Has anyone provided the file the OP asks for in the forum so that he can create the NZ CSC?

Unfortunately not. Its a cache file apparently but by the time I read it, I had already flashed to the custom rom and cleared the cache out.

Calling all Vodafone peeps. Has anyone NOT flashed their phone to a non-Vodafone rom? If you have not, can you assist with providing the CSC folder (it's in /system/csc and likely to be a subfolder VNZ).

These are the destructions from the XDA forum where the CSC folder can be provided so that the OP can create a downloadable CSC file to be used *after* people have flashed to a non-Vodafone firmware.

If you've got Root Explorer it will make it really easy to search and copy the folder to then provide on the thread to the OP.

For your country you'll need a specific folder. If you don't find it , give me an CSC file for your country (any firmware version, I just need the file "cache.rfs" or the "CSC_I9000------.tar.md5") and I will make the folder for your country available.

[not sure why I'm asking, I don't have a Vodafone phone but for the good of the community here, it would be good if we could get our hands on the VNZ CSC details]