Database Develop

I've got 2.2 XXJPK (KOR), but not root. How do I fix CSC and update it via Kies?

Current firmware version: PDA:JPK / PHONE:JPK / CSC:JPK (KOR)
I uninstalled Kies 2.0.0.11014_49_2 and am now running 1.5.3.10093.82 (no reghacks yet). Obviously neither version of Kies would upgrade the firmware.
I see this thread:
http://forum.xda-developers.com/showthread.php?t=787163
Except the phone is not rooted. The phone is an international I9000 from Europe (not sure where as I'm in Asia and I bought it used outside of Europe). I'm assuming it's originally XEU but I don't know (also I see reports that official Kies flash for XEU has changed the CSC to KOR before for other people and as my phone is not rooted, I assume it had to have been an official Kies update that did this).
I've already installed a bunch of apps and stuff on it, in case that complicates anything.
On the phone there is an "nv_data.bin.orig" in the main phone directory (the phone is not rooted, I installed Titanium Backup which confirmed it wasn't).
What can I do? Can I see what CSC is in that nv_data.bin.org? And revert the phone to that, and then run Kies to get 2.2.1?
Thanks for any help!
EDIT: Damn. I opened that file in Notepad and searched for the string "HKD" and found it still said HKDKOR, so I guess this is a backup of the current version which won't help me

I ran the Registry Patcher 1.7 with the previous version of Kies and it still won't let me update the phone. =\

First ROOT THAT THING!!! And backup your efs folder.
Then change your CSC to something properly.
The old 1.5 Kies was reported not working (somehow blocked via Sammy so you have to use the new one). So your only way is spoofing the new one (which I heard didnt work, just showed the new FW didnt allow to install) or to change the CSC.
Couple of things.
First what rom you have?
Kernel?
3 button recovery/download?
Did you apply any lagfix?
Dont do any of this till you reply to my questions!
1. Rooting with super one click root. This should be relatively safe even if you did something stupid before.
2. Backup efs folder so you dont loose your imei , this is kinda crucial as it happens from to time(on what you are about to do) and since you bought in europe you would be literaly f.cked . (after root use sgs tools or toolbox, whatever is in market) and send the backup to your PC, USB, mail wherever is safe, not just your phone.
3. If you dont wanna go custom and keep the stock. Well choose the best CSC you would like what would fit you. and check if it also has already froyo 2.2.1 good page is http://www.samfirmware.com/ (I changed mine which was IRD and changed it to XEU as that having updates sooner) . since I have no idea which rom you have, it might even work with that old code which is in SGS toolbox /tools or you use the automatic one from the thread you posted in the first post, the method wiht the IMEI and code.
Anyway dont forget to answer the questions before you do anything. So you dont end up with a useless brick

I rooted it before I saw your post using the CF-Root then used My Backup Root to backup all the Apps + Data.
I haven't done anything else yet. I just got SGS Toolbox, it says:
code in nv_data.bin
HKDKOR
code in nv_data.bak
HKDO2U

Okay, I backed up the efs folder.
Should I change the CSC with SGSToolbox and will that lose all my apps/data? And then I can use new 2.0 Kies to update to 2.2.1?
Or should I flash with 2.2.1 from http://forum.xda-developers.com/showpost.php?p=12159821&postcount=145

Blackbeard_ said:
Should I change the CSC with SGSToolbox and will that lose all my apps/data? And then I can use new 2.0 Kies to update to 2.2.1?
Or should I flash with 2.2.1 from http://forum.xda-developers.com/showpost.php?p=12159821&postcount=145
Click to expand...
Click to collapse
To the loosing, you wrote you did the mybackup thing, so you can use that backup (not on system apps and settings, that might go wrong, but apps, your custom launcher etc)
The changing of CSC (or flashing via Odin I think) or even a rom upgrade is mostly connected with the loosing of everything, even if you dont , a factory reset is recommended so there is no leftover garbage.
So if I was you. I would change my CSC to something nice. Like XEU (or NEE) and then upgrade via Kies. (Not sure NEE might be possible, but you can always try).
But its up to you if you do the ODIN or Kies. Not sure if kies will work and never used odin

Do you know if NEE lets you use English (US) for language?
EDIT: Nevermind!

Post number 17 in that NEE thread where you asked . http://forum.xda-developers.com/showpost.php?p=12135204&postcount=17

Bell Galaxy tab stock firmware

can someone please point me to a guide on how to flash the galaxy tab from bell back to stock firmware (for warranty reasons) and where i can get the bell firmware from, my build number is FROYO.UGJJ7 BASE BAND VERSION IS P1000MUGJJ7.
post here or pm me this site helped me with my telus milestone (how to flash it back to stock) hope i find the same help for my bell galaxy tab thanks

wow 26 views and still no suggestions i actually learn't how to flash the firmware but now i just need the files for stock bell firmware.
i guess the tab is still too new and the firmware im looking for is not being shared yet
just to give a general idea of how easy it was for me to flash my milestone to whatever fw i like go here to see the guide http://forum.xda-developers.com/showthread.php?t=696845 and here to see the roms needed for flashing the milestone http://and-developers.com/sbf:milestone

Bell Stock FW
I've made a copy of my Bell Galaxy Tab FW using the Roto Backup technique which you're welcome to try. I haven't try restoring it to my device yet as I *just* got it and am still a little hesitant - so use at your own risk - I will assume no liability for what it does to your device. The image is version JJ7, rooted using z4root (you should just be able to use the same to unroot it), and unlocked using the hex edit technique (http://forum.xda-developers.com/showthread.php?t=843323 - or specifically, I changed byte 0x181469 from 01 to 00 using a hex editor - so you can just reverse this to lock it again)
I would also consider the alternative of restoring to the JJ3 "Provider Samsung P1000 Firmwares" available on samfirmware.com. After that, upgrade to the most current via Kies. I have not tried this and assume no liability for what this does to your device either.
Let me know if you'd like my Bell image and I'll send you a link to it.

Hi smd2008,
Would you please provide a download link for the 'Bell stock rom'? I need to revert back to stock. Much appreciated!

Hi do you mind if you please send me that bell firmware please thanks

Hi, I'd love to get my hands on a copy of the Bell stock firmware...
warranty issues.... please help!

Roto Backup of Bell Stock ROM
Hi smd2008 or any one,
Could you share your experience with the Roto backup of your Bell stock Rom. I have just tried to do a Roto backup for my Bell SGT ( UGJJ7 ) . When it came to adb pull commands, system returned an error saying the file was not exist.
I have tried both Z4Root and SuperOneClick 1.9.5 to root but both cases showing the same error. I had set the SGT USB to Debugging mode and mounted as R/W with Root Explorer. I used the Command mode in PC then followed the Roto backup scripts. I used the ADB files attached with SuperOneClick download. Occasionally, the connection of the SGT to PC might lost when I entered the -dd command for dbdata.rfs. But I managed to completed all the -dd and tar commands after re-starting the PC. It looks like the files were created but just couldn't find them.
Could any one advise how to correct the problem? Thanks.

Found the cause of problem. It was due to SDcard not mounted.
Could someone please inform how to get the SDcard mounted when using the command mode in PC to do Roto backup.

bell stock firmware
hi
i was wondering if i could get a copy of the firmware as well, for warranty purposes i need to flash my tab back to stock.
thank you

Any hopes to get the stock rom for Bell Froyo?

[Q] CSC file for Gingerbread DXJPC fw,Please.Something wrong with DXJPC fw:

Does anybody have a CWM flashable CSC for stock DXJPC firmware?

DXJPC CSC

Thanks,Noxxious.
I can't stand the suspense,went ahead and flashed the DX fw
over the Italian fw and guess what--- no pda and csc from *#1234#.
Applied your csc file from CWM. now I have PDA XJPC and CSC OLBJPC,,,,
Under Kies it is still showing ITV though.....I tried from *#272*IME# to change to XTC the tab rebooted and I saw some RED TEXT stating that the "E:rfs cannot be formatted" or something like that.
What is this E drive? and how to apply CSC to enable the correct one to show up in Kies?

try reflashing the dxjpc firmware again. that did the trick when i encountered that before.

This is exciting!
should I reflash thru Odin without repartition or repartition with pit and pda?

you could also try doing a factory reset first...
i think it would be better to flash with .pit file

No luck,kabayan.
2 problems: 1. no pda and csc:
Tried everything-flash with pit, flash with no pit, factory reset using recovery mode,factory reset from settings/privacy,using samfirmware fw, using your dbdata file,etc- everything resulted in BLANK PDA AND CSC from *#1234#.
Went back to Italian using chainfire files and there it is complete info.
I researched the problem and found that on the galaxy s thread this CSC problem is extensively discussed. It has something to do with nv_data file not matching the csc. When during boot the fw finds the nv_dat file to be missing it creates a blank one thereby resulting in a blank csc when the 1234 is called. I don't do programming so I don't have a clue on how to resolve this problem.
Also present on the tab is the "E: efs unable to format data" error when changing csc from the *#272*.....
Problem 2. when rooting the dx firmware using CF-root the bootsplash becomes corrupted. The sound disappears from the samsung galaxy tab logo animation, followed by a BLANK screen and the sound comes just before the home screen appears and it is broken. I tried to apply the available bootsplash animation restore from this forum but it has no effect.
--I have now got back to the Italian stock. These 2 problems don't happen at all in this now unofficial fw(since it was pulled out by samsung). I think there definitely is something wrong with the dx fw.....

the DX 2.3.3 firmware is stable enough, the problem seems to be in how the filesystem gets updated/corrupted during the update process..
the only problem i got with the gingerbread firmwares (JQ1 and JPC) was this:
"verifing intermal MMC block...
checksum confirmation - check(1)
E:MBR checksum Error
Internal MMC checksum verify failed"
though i was able to fix that.

noxxious said:
the DX 2.3.3 firmware is stable enough, the problem seems to be in how the filesystem gets updated/corrupted during the update process..
Click to expand...
Click to collapse
not unstable but minor bugs are there (to discover)...felt okay to me but no different from the Italian fw.
noxxious said:
have you tried looking into the /efs in root?
mine contains 2 folders 1. (.android) and 2. (imei) and 6 files .nv_data.bak, .nv_data.bak.md5, .nv_state, nv_data.bin, nv_data.bin.md5, and updated_filesystem.
access dates for the files are as follows:
.nv_data.bak, .nv_data.bak.md5 was the date i made a backup of my efs folder (i was tinkering with the said files because samsung service forgot to reinput my tabs serial number)
Click to expand...
Click to collapse
Yes 2 folders-.android and IME. 7 files same as yours plus nv.log.
the hidden (.nv prefix) files were dated 25 jan 11 while the 2 others (nv) dated 11 jun while the updated_filesystem dated 4 jun
I wonder if there is a check on the md5 hash? or the dates?

seems you still have a safe copy of your EFS. i recommend you back it up somewhere. i myself have it on my pc and the tab's external sd.

I am now on the Italian gb....is this a safe copy? I'll put it on the external sd then....What will I do with it? should I put it in when flashing the dx?

keep it as backup as sometimes flashing firmwares might corrupt it, you ending up with a phone with bogus imei.
do you remember what the dates for .nv_data.bak and .nv_data.bak.md5 mean to you by any chance? say first time you held your tab, the date your tab left the factory even (lol)?

wait I'll check my receipt....I hope the missus did not throw away the box.....

Wait, I am learning something here:
You mean when flashing a new firmware the tab is not completely erased? I was assuming it is reformatted clean....

noxxious said:
keep it as backup as sometimes flashing firmwares might corrupt it, you ending up with a phone with bogus imei.
do you remember what the dates for .nv_data.bak and .nv_data.bak.md5 mean to you by any chance? say first time you held your tab, the date your tab left the factory even (lol)?
Click to expand...
Click to collapse
I got my tab in march so must be manufacture date
Sent from my GT-P1000 using Tapatalk

I think I can confirm now that there is something in the samfirmware file that causes the partition E errors I get. I have flash to DXKJ2 then updated thru Kies. No more errors!

I have been reading your post guys , and I also had the same problem in partition E: when I flashed gingerbread to p1000n, how did you solve the partition e: issue? Have tried everything and still with the same problem! (Obs.: the firmware also was form samfirmware.com)

vettorodrigo said:
I have been reading your post guys , and I also had the same problem in partition E: when I flashed gingerbread to p1000n, how did you solve the partition e: issue? Have tried everything and still with the same problem! (Obs.: the firmware also was form samfirmware.com)
Click to expand...
Click to collapse
I did not really "solve" it...I used Kies to get gingerbread.

I also have missing CSC and PDA, how to I flash using CWM. I root with CF-root and it comes with CWM manager, can it be used? Is it under option flashed an update.zip for csc?
Thanks!

yes you can use cwm.but select zip file not update zip
Sent from my GT-P1000 using Tapatalk

Rogers Captivate (SGH-I896) CSC File For Odin3

Hey guys I'm just wondering if someone could send me their version of Rogers Captivate CSC file, because I just flash my phone back to Eclair and now when I plug it, Kies says "This Version of device cannot be updated". And the CSC Version is JI2(KOR). Please can someone help me out.

http://forum.xda-developers.com/showthread.php?t=979133

Doesn't work
studacris said:
http://forum.xda-developers.com/showthread.php?t=979133
Click to expand...
Click to collapse
I flashed it with this one also and this one csc verison is unknown. The firmware does even shows up on Kies.

Fix my own problem. I also had to modify the nv_data.bin to fix my product code and now it works perfectly, kies recognize my phone.
Sent from my SAMSUNG-SGH-I896 using XDA App

Nick0703 said:
Fix my own problem. I just had to modify the nv_data.bin and now it works perfectly, kies recognize my phone.
Sent from my SAMSUNG-SGH-I896 using XDA App
Click to expand...
Click to collapse
Did you follow a guide to do this? Im having the same issue

The CSC UNKNOW FILE FIX
erbsmokah said:
Did you follow a guide to do this? Im having the same issue
Click to expand...
Click to collapse
Ok here is what you need to do.
1. Flash your captivate with this stock 2.2 Rom. This one will remove the AT&T boot logo. And when flashing do make sure to check the repartition box and use the pit file
Files:
Rogers 2.2 ATT Free
Pit File
2. When you finished flashing, go to the phone dialer and dial *#1234#, if your CSC Version is unknow then put the phone back into download mode. And flash this 2.2 Rom, this one contains the missing CSC file version and make sure to only check the PDA on Odin3 and don't use the pit file and uncheck the Re-Partition box!!!!!!
When finish flashing go the dialer and dial *#1234#, to see the csc version: I896RWCJL1. And connect to kies to see if your phone is recognize. If your having problem PM me.
Files:
Rogers 2.2 Missing CSC

Thanks, I'll give it a shot..

worked like a charm thanks!
I tried to modify the NV_Data.bin myself but the guide is for i897 models, which are the same but not so it wasn't working.
Now im ready to take the official update if rogers ever pushes it.

erbsmokah said:
worked like a charm thanks!
I tried to modify the NV_Data.bin myself but the guide is for i897 models, which are the same but not so it wasn't working.
Now im ready to take the official update if rogers ever pushes it.
Click to expand...
Click to collapse
So everything is working, Kies regconize your firmware now?
Sent from my SAMSUNG-SGH-I897 using XDA App

Make sure you properly modify the NV_Data.bin, or else when you connect to kies it's going to say for the CSC version: JL1 (ATT). If you need help modifying the NV_Data.bin, I'll help you with it.
Sent from my SAMSUNG-SGH-I897 using XDA App

I had already modified it but was still getting CSC : Unknown, after flashing the new rom it began to work as it should.

erbsmokah said:
I had already modified it but was still getting CSC : Unknown, after flashing the new rom it began to work as it should.
Click to expand...
Click to collapse
Glad I could help.

IMEI broke (i have unbrickable mod installed)

Hi I am having IMEI repair issues. I have read multiple threads. However many of the files are missing (i do not have in efs file):
here is a list of files i have
.android
imei
.imei
.nv_state
.nv2_bak
.nv2_bak.md5
cryptprop_applied_reult
cryptprop_onetimeboot
cryptprop_securewipedata
edk_d
edk_p
nv
nv_data.bin
properrordump
rfs
I also have my IMEI (got from AT&T) so i would like to restore it if possible so i can get my phone working again. Currently my IMEI said null/null i deleted the efs file with root explorer and the IMEI is now 004999010640000. I tried to follow the mobiletech video. However in the HEX edit portion of the video when i go into my nv_data.bin file it says "File has only 704512 bytes" when i search for 0188008 to preform the editing. The originial nv_data.bin file (saved prior to wipe and OS creating new bin) shows "File has only 647148 bytes" when i search for 0188008. (this is following this link http://forum.xda-developers.com/showthread.php?t=881162)
i also do not have the following files :
nv_data.bin.md5
nv_data.bak
nv_data.bin.md5.bak
When attempting to correct this issue following
http://forum.xda-developers.com/showthread.php?t=880223
I run into the issue of not finding the SGH file in my nv_data.bin while searching from Hexedit.
I have noticed when i flash 2.2 i get IMEI unknown and when i flash 2.1 i get IMEI:004999010640000.
I have tried both methods with both 2.1 and 2.2 with no luck. Id like to mention i also have unbrickable mod installed.

WANTED: Someones functioning generic efs folder and nv_data.bin. Please help

wtf why would we give you our IMEI #?

I need a Generic functioning IMEI

OKAY IM SAVED AND FIXED.... id just like to write a little bit as to assist others. First my phones history:
refurbished from at&t:
stock: froyo
started off flashing Gingerbread
followed by: Continuum
followed by: Miui
followed by: ICS
ICS issues i went back to 2.1
Flashed 2.2 and hard bricked.
Did Unbrickable mod (thanks to the genious of Adam)
Did Resurrector to bring phone to life. Used Heindall to flash rom.
**Issue began with IMEI not working.
Flashed multiple roms with multiple thread advice. All failed except one for me.
Step 1: I flashed 2.1 JF6 first One-Click
Step 2: I flashed 2.3 using a One-Click
Step 3: I flashed the latest rom that was working ICS build 9
walllla phone is alive

None of those items touch your EFS though...
Sent from my SGH-I897 using xda premium

Im not sure what is causing my phones resurrection. But i have tested a few things since. Currently i cannot go back to 2.1 or 2.2 or 2.3 and have sim work. It only works on ICS roms (potentially only cyanogenmod). I have not had a chance to test CM7, continuum, or MIUI. From my reading, i agree that the efs folder should not be tampered with during these flashes. But im not sure how the IMEI is broken/altered (on most roms) and why it works for ICS roms. I also noticed the ICS IMEI is a generic. But curious how come the 2.1 IMEI generic fails to connect sim.