Neets: The update.zip I've left on my Internal SD is the one from Doc. So I'll just apply that first before I factory rest, wipe cache and dalvik. Then I'll apply his JPX rom. Thanks for letting me know there wasn't any problems from switching one to the other.

Wont help I think. The CWM we want (for doc) is built into the kernel of docs rom. I think. They are not very explicit - info is scattered all over the place in the i9000 forum.

And yes, anytime you flash back to stock rom (and you could go JPU) will reset everything. You wouldn't even need to do any wiping of the cache if all you're doing is that. If you go JPU you'll have to use Odin to flash CF-root to get 2e. If you flash say JM9 (Eclair) then you can apply the update.zip file and then flash Doc's ROM.

I flashed jm8, as it was pre-rooted, with odin. Then I flashed darky's latest. I think it's a bit faster and a bit more stable. Also, it did not do a wipe so all the old apps were still there, crashing and playing up.

jm8 did not fix the MMS issue either, but it got further along than jpu and jpx. The point of difference was the includion of a csc file; not the right one mind you, but somewhat close I think as it actually sent the attachment. But it was not received by the receiver. No need for mobile data to be on first either.

So, the MMS issue is rooted in the csc. Pathetic - the way samsung has added this complication. The HTC Desire does not have this problem. (But I like the sgs more for other reasons).

Oops, almost forgot. Have you rebooted the phone since moving to Doc's rom. I recall once it appeared I didn't have all the CWM options. When I shut the phone down and went back to recovery it was all there.

I flashed jm8, as it was pre-rooted, with odin. Then I flashed darky's latest. I think it's a bit faster and a bit more stable. Also, it did not do a wipe so all the old apps were still there, crashing and playing up.

jm8 did not fix the MMS issue either, but it got further along than jpu and jpx. The point of difference was the includion of a csc file; not the right one mind you, but somewhat close I think as it actually sent the attachment. But it was not received by the receiver. No need for mobile data to be on first either.

Gah! I just flashed yesterday, ah well - off to flashing again.I managed to actually do a full brick of my phone yesterday which wasn't too good, took me about 6hrs to recover it.

Yikes. 6 hours! Still, it's obviously resolved and hasn't done you any harm ;-) Did you have your phone in debugging mode? Would be interested in the method your used. Not a blow by blow account, just the highlights ;-) Maybe you made a jig rather than tussle with adb or whatever.

Gah! I just flashed yesterday, ah well - off to flashing again.I managed to actually do a full brick of my phone yesterday which wasn't too good, took me about 6hrs to recover it.

Yikes. 6 hours! Still, it's obviously resolved and hasn't done you any harm ;-) Did you have your phone in debugging mode? Would be interested in the method your used. Not a blow by blow account, just the highlights ;-) Maybe you made a jig rather than tussle with adb or whatever.

It was not booting up / wouldn't get into Android (Reboot Loop) or wouldn't flash anything from Recovery.

Since I can't use Oden (Linux user here) I had to compile Heimdall, get it into Download Mode (adb reboot download - the 3 button shortcut wasn't working) and install Android 2.1 from there (it wouldn't boot with Android 2.2)

Once it booted I was able to install a custom kernal to get the full blown Recovery Image installed, from here I had to flash Samsung's Android 2.2.1 (Doc's didn't work, wouldn't boot at all) to get the initial partition table.

Once this was done, I flashed Doc's 5.1 image, and things went all good after that.

I suspect that I messed up the internal partition table somehow, took me ages to figure out what rom to start off with (and boy-oh-boy I got sick of Megaupload by that stage) - Going straight to Android 2.2 / 2.2.1 didn't work for me.

But now, I can successfully use Heimdall straight from the terminal, that's a good start. And now my phone is flashing Doc's 6.0.

Install Jdownloader then select the monitor clipboard option. then you just right click on any megaupload/rapidshare/etc/etc links and click copy link, then it automatically gets added to jdownloader, jdownloader takes care of the wait 60 seconds and all the other crap for you. I use filestube.com a lot and you can just right click + copy the links from filestube and jdownloader takes care of the rest for you.

Gah! I just flashed yesterday, ah well - off to flashing again.I managed to actually do a full brick of my phone yesterday which wasn't too good, took me about 6hrs to recover it.

Yikes. 6 hours! Still, it's obviously resolved and hasn't done you any harm ;-) Did you have your phone in debugging mode? Would be interested in the method your used. Not a blow by blow account, just the highlights ;-) Maybe you made a jig rather than tussle with adb or whatever.

It was not booting up / wouldn't get into Android (Reboot Loop) or wouldn't flash anything from Recovery.

Since I can't use Oden (Linux user here) I had to compile Heimdall, get it into Download Mode (adb reboot download - the 3 button shortcut wasn't working) and install Android 2.1 from there (it wouldn't boot with Android 2.2)

Once it booted I was able to install a custom kernal to get the full blown Recovery Image installed, from here I had to flash Samsung's Android 2.2.1 (Doc's didn't work, wouldn't boot at all) to get the initial partition table.

Once this was done, I flashed Doc's 5.1 image, and things went all good after that.

I suspect that I messed up the internal partition table somehow, took me ages to figure out what rom to start off with (and boy-oh-boy I got sick of Megaupload by that stage) - Going straight to Android 2.2 / 2.2.1 didn't work for me.

But now, I can successfully use Heimdall straight from the terminal, that's a good start. And now my phone is flashing Doc's 6.0.

I think I would have cried long before all of that. Well done! Yes, megaupload is annoying (to put it mildly). Will revisit Kiwijunglist's suggestion above.

Wipeout may ask a few questions about your use/experience of Heimdall. He's looking at it as an alternative to Odin to get the 3BR working.

You could also delete everything except nv_data.bin in /efs so that the checksum was recreated on boot.

Not to knock your logic, but if it was only that, why not have those instructions on the XDA forum. It makes me wonder if there's some other *magic* that happens to perhaps make the files compatible or whatever.

I've copied the OPS folder (provided by Bloodrider) into the /system/csc folder, but I don't know whether Bloodrider had made any changes to any of the other files inside the OPS folder. I guess I wouldn't be confident to put hand on heart and swear the files you have existing in the VFNZ folder can be copied verbatim and be completely compatible.

Why not ask if that's all that's required. If he says yes you can go ahead and do just that :-D

Doc's roms don't come with a modem/pda file though. I guess it's all wound up in the zip file somewhere.

You could also delete everything except nv_data.bin in /efs so that the checksum was recreated on boot.

Not to knock your logic, but if it was only that, why not have those instructions on the XDA forum. It makes me wonder if there's some other *magic* that happens to perhaps make the files compatible or whatever.

I've copied the OPS folder (provided by Bloodrider) into the /system/csc folder, but I don't know whether Bloodrider had made any changes to any of the other files inside the OPS folder. I guess I wouldn't be confident to put hand on heart and swear the files you have existing in the VFNZ folder can be copied verbatim and be completely compatible.

Why not ask if that's all that's required. If he says yes you can go ahead and do just that :-D

Doc's roms don't come with a modem/pda file though. I guess it's all wound up in the zip file somewhere.

Oh I completely agree - I'm sure if it was that simple, it would be on XDA. . . .But I tend to think (probably naively) that the CSC isn't actually that complex - it's just a bunch of .xml files in a specific location with specific names that are referenced by the O/S for certain details. The catch may be that they're tied up with /efs somehow, which means you may need to delete everything in /efs except nv_data.bin, and do a hard reset so that any checksums are rebuilt?

nofam:You could also delete everything except nv_data.bin in /efs so that the checksum was recreated on boot.

The only way I have found for me to get SGS Tools to identify my csc as VNZ instead of KOR is to delete nv_data.bin. Having nv_data.bk in the efs folder ensures that nv_data.bin is rebuilt with the correct csc. I'm not sure how deleting everything but nv_data.bin would help?

As far as I can tell, nv_data.bin holds your phones unique information. Its CSC, its IMEI and it MAC address. When you flash to another rom, it gets rebuilt and in most cases the IMEI and Mac address remain untouched, but the CSC gets hijacked (probably based on the new system/csc folder). This is also why nv_data.bk is a critical file to keep safe.

So unless the appropriate system/csc folder is created at time of flashing, then I think not only does that folder need to be amended, but nv_data.bin probably has to be rebuilt too.

nofam:You could also delete everything except nv_data.bin in /efs so that the checksum was recreated on boot.

The only way I have found for me to get SGS Tools to identify my csc as VNZ instead of KOR is to delete nv_data.bin. Having nv_data.bk in the efs folder ensures that nv_data.bin is rebuilt with the correct csc. I'm not sure how deleting everything but nv_data.bin would help?

As far as I can tell, nv_data.bin holds your phones unique information. Its CSC, its IMEI and it MAC address. When you flash to another rom, it gets rebuilt and in most cases the IMEI and Mac address remain untouched, but the CSC gets hijacked (probably based on the new system/csc folder). This is also why nv_data.bk is a critical file to keep safe.

So unless the appropriate system/csc folder is created at time of flashing, then I think not only does that folder need to be amended, but nv_data.bin probably has to be rebuilt too.

Sorry, I should've been more specific - that's what I meant (restoring your nv_data from a known working backup).

nofam:You could also delete everything except nv_data.bin in /efs so that the checksum was recreated on boot.

The only way I have found for me to get SGS Tools to identify my csc as VNZ instead of KOR is to delete nv_data.bin. Having nv_data.bk in the efs folder ensures that nv_data.bin is rebuilt with the correct csc. I'm not sure how deleting everything but nv_data.bin would help?

As far as I can tell, nv_data.bin holds your phones unique information. Its CSC, its IMEI and it MAC address. When you flash to another rom, it gets rebuilt and in most cases the IMEI and Mac address remain untouched, but the CSC gets hijacked (probably based on the new system/csc folder). This is also why nv_data.bk is a critical file to keep safe.

So unless the appropriate system/csc folder is created at time of flashing, then I think not only does that folder need to be amended, but nv_data.bin probably has to be rebuilt too.

Sorry, I should've been more specific - that's what I meant (restoring your nv_data from a known working backup).

I would have expected nothing less from you nofam. Are you wearing your t-shirt?

This is my theory (based on little/no knowledge of wtf I'm talking about).

I think that system/csc offers nothing useful after a rom has been flashed. It seems to exist to help create the information that gets populated in efs (namely nv_data.bin).

If that is true, then we don't really have to worry about system/csc if we have a working nv_data.bk from back when the phone was stock.

However, if someone was wanting their phone to appear stock for warranty purposes, then that would be a different story...

One way I could test my theory would be to change system/csc and see whether or not it results in nv_data.bin being recreated. If it doesn't, then its a safe bet that post-flash, system/csc doesn't really matter.

I've got V4 but didn't know it was called "final". I looked to see if there were maybe two versions but no. So I guess I'll stick my hand up :)

The battery drain is really bad. I turned wifi off last night and had 3% battery drain in 8 hours. But if you leave wifi on, expect your battery to practically drain over an 8 hour period.

I'm not sure if it relates to Docs rom or JPU in general. ROM Manager doesn't work well - can't take a backup of your ROM, however CWM has a backup function so that's the work around.

I can't quite put my finger on it, but I preferred V9 of the ROM, which was pre JPU.

Lots of things are new in JPU (or since), Market has changed, Google Maps v5 (which is way cool!) but these aren't specific to the ROM version.

What version of Docs ROM are you on, if you're on a customised ROM at all?

Hey Neets,

Im on the Doc V7.6.2 - JPO based rom but im just downloading the new Docs XXJPX V5.1..

One quick question, what lag fix are you running on these roms ? i tried the NO-RFS STANDARD but was thinking about trying the voodoo fix .. need more speed.

Hey Snowsteve. I wasn't using any lag fix at all. I found them to be responsive without needing to amp it up. The Darky rom I've got on at the moment has Voodoo and I think it's a little too fast. When scrolling through the app drawer it really does get away on you and you over shoot what you're looking for. I'm sure you'd get used to it, but I think it's a bit too much.

As Kiwijunglist says, you'll need to do the fix on the kernel before flashing the latest Doc Rom, or flash back a stock ROM and then get 2e, update.zip and then flash Doc's rom via CWM.

Hmmm Crud, i missed that step.. Does it matter (the rom seems to be working fine) ? or do i have to flash again ?

Also now, after updating, kies will not detect the phone, which is a real pain - never had an issue with kies before.