Database Develop

Problem with return

I'm having to return my Galaxy S for a replacement, however before i realised there was a hardware issue, i flashed it.
Since i'm in Australia, on Optus, there isn't a leaked DTJF3 image. So i can't just flash back to the original.
Is there a way using busybox, or an update.zip (I create and sign update.zips, Have done a little) to update the model numbers to at least look like i haven't been messing with it. Best to be safe rather than have them not honor the warranty because of a flashed update.
I ask in here as this is where the people with an intimate knowledge of the underlying code hang out.
Regards,
aRTie

Australian Stock Rom (Dump) : ............
PLEASE NOTE: IF YOU ARE NOT A DEVELOPER, PLEASE DO NOT DOWNLOAD THIS FILE.
http://rapidshare.com/files/406741229/dump.tar !!!!
not my work but taken from this forum, so mayb try a search before posting

So I guess the first silly question would be.....
how to separate out the CSC, Phone & PDA tar files from the Dump?
Or is there a way to use Odin to flash the dump.tar?
(just thought I'd ask the question before the OP does )
****************
Ok, so i was just looking at Odin, and there is a place where you can upload the dump.tar file. Is it really that simple - select the dump.tar downloaded from this thread, keep all other PDA/CSC/Modem spots empty, maybe select re-partition then flash??

cheetah2k said:
So I guess the first silly question would be.....
how to separate out the CSC, Phone & PDA tar files from the Dump?
Click to expand...
Click to collapse
Hey mate, caught in a similar situation here. The dump is not available now, do you mind uploading to another location? I know many other users waiting for this as well.
All the best with your flashing.

In the end until there is a leaked copy of the rom,we won't be able to flash it.we can customize with update.zip however we can't turn the dump into a rom.
The dump will contain the optus parts of the rom.but not the rom itself. I just figured someone may be able to help me fool the about screen into showing the wrong rom version.
At some point nandroid might get running, then we can do some interesting stuff until then, we just wait.
That's how I understand it
Sent from my GT-I9000 using XDA App

artie11 said:
In the end until there is a leaked copy of the rom,we won't be able to flash it.we can customize with update.zip however we can't turn the dump into a rom.
The dump will contain the optus parts of the rom.but not the rom itself. I just figured someone may be able to help me fool the about screen into showing the wrong rom version.
At some point nandroid might get running, then we can do some interesting stuff until then, we just wait.
That's how I understand it
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
During inspection of your handset, the firmware check is done by the supplied tools to Optus, this will have no effect even if you change the About section on the Android OS, voiding your warranty further. I would rather advise you to wait for a month or so until 2.2 update comes up on Optus, then you can update the firmware via recovery.

cheetah2k said:
So I guess the first silly question would be.....
how to separate out the CSC, Phone & PDA tar files from the Dump?
Or is there a way to use Odin to flash the dump.tar?
(just thought I'd ask the question before the OP does )
****************
Ok, so i was just looking at Odin, and there is a place where you can upload the dump.tar file. Is it really that simple - select the dump.tar downloaded from this thread, keep all other PDA/CSC/Modem spots empty, maybe select re-partition then flash??
Click to expand...
Click to collapse
the dump has a different format, it doesnt have a radio and csc file ( though you dont need it ) but you still need samsung.pit file i.e the bootloader file .. but be careful while doing that.

[Q] Restoring product Code

Does anyone know a proven method to restore my product code through the nv_data file in the efs folder? Like many who flashed to Froyo on here, My code is showing as HKKOR and should be back to stock HKOPS (Australia). Or any other way if possible.
If not, will I be able to update to the official Froyo through Kies when it's released?

If you are with Froyo, Flash multi CSC JP3 through ODIN and select your area will set your Product Code. It worked for me.

use root explorer and delete both your nv_data.bin and nv_data.bin.md5 files and reboot.
correct product codes will be recreated from your .bak files.
kies checks your product code before upgrading, but there are patcher programs to take care of that, if you want.
both topics have been discussed to death previously, I kindly suggest you do some search before posting next time.

That sounds like it might work. Do you have a link for that JP3 Rom? and does it have to be JP3.
I had just flashed back to a clean JG4 just need to restore that product code.

Sorry, I just see that you're from Australia requiring OPS csc file.
JP3 csc file will not include Australia.
You have to find a multi csc file that include your area code.
Multi csc file ask to choose area amongst several, then when choosing correct area it set this area into the product code.

Hey guys, please, i have one btw question:
I have unbranded and unlocked product code I9000HKDDBT (Debitel,Germany), but i want put firmware XFJP7 with Multi CSC XXJP7 wich have Croatian APN settings...Can I make this without any dangerous ? At this moment im on firmware in my signature wich is not for my prod.code too, but fw work like a charm, and with staying my original product code in nv_data.bin without restoring (original from stock firmware).
Or: Can I put only Multi CSC XXJP7 with Odin (without PDA and MODEM files) on my presents (XWJP6) firmware?
P.S. What i must care, i will not to stay without Download and Recovery Mods (3-comb buttons) ?
Forwarding thanks on answer
Regards

MPM86 said:
That sounds like it might work. Do you have a link for that JP3 Rom? and does it have to be JP3.
I had just flashed back to a clean JG4 just need to restore that product code.
Click to expand...
Click to collapse
See this post : http://forum.xda-developers.com/showthread.php?t=787163

also found this :
http://forum.xda-developers.com/showthread.php?p=9352031#post9352031

MPM86 said:
That sounds like it might work. Do you have a link for that JP3 Rom? and does it have to be JP3.
I had just flashed back to a clean JG4 just need to restore that product code.
Click to expand...
Click to collapse
JP3 is seriously old rom.

dupel said:
JP3 is seriously old rom.
Click to expand...
Click to collapse
I know, badly. I'm just trying to prepare for the official froyo when it hits. I have a feeling it will be a disappointment, then I'll be back to a rooted JPO or something. I was still on JPK
Sent from my GT-I9000 using XDA App

[Q] Do we need PIT files while flashing ROMs?

Hi people,
Have you seen samfirmware site lately?? They now recommend NO PIT FILES FOR EVERY ROM from Eclier to latest JPX. I think it makes sense. Our phones already come with a pit suited best for them, we actually dont need to do it again.
Imagine re-partitioning your hard-drive every time you want to install linux or windows. We actually don't do that, The max we do is format 1 drive.
This topic doesn't belong in Dev, & can be moved to an appropriate location once this issue has been sorted out.
Thanks.
Update :
1. SEA (South East Asia) is one region where you require to re-partition with a 512 pit if you want to flash other region ROMs.
PS : All the partitions of our SGS are formatted anyway when we flash a FW through Odin.
EDIT : I have had to use a 512 PIT twice when I downgraded from froyo to eclier. Without that I was getting error. Some developer may shed some light on that.
EDIT 2 : I remember that happened because I followed wrong steps & had flashed 803 PIT. I had to reflash 512 to come out of it.

I don't know ragin.
The table with the firmware on samfirmware is still containing PIT-files.
Exeptions are the first 13 firmwares.
Even JPU and JPX need a PIT file.
But thats only how i read the table!

LaurensJ said:
I don't know ragin.
The table with the firmware on samfirmware is still containing PIT-files.
Exeptions are the first 13 firmwares.
Even JPU and JPX need a PIT file.
But thats only how i read the table!
Click to expand...
Click to collapse
I mean this page where they have published their ROMs for downloading.
http://www.samfirmware.com/WEBPROTECT-i9000.htm

76 ROMs published, all with the same note '1 file select NO .PIT'
That includes JPU & JPX.

If your phone is already formatted with 512.pit you can flash any ROM which works on 512.pit without selecting a PIT file and without selecting repartition.

ragin said:
I mean this page where they have published their ROMs for downloading.
http://www.samfirmware.com/WEBPROTECT-i9000.htm
Click to expand...
Click to collapse
Yes i mean that page as well (with the table).
Its also say's:
Please when you have only one file SKIP RE-PARTITION!
Use only .PIT files if you have 3 files!
So the last column of that table i interpret as using no PIT file ONLY when you have one file. But if the you update 3 files you need a PIT-file.

izibi said:
If your phone is already formatted with 512.pit you can flash any ROM which works on 512.pit without selecting a PIT file and without selecting repartition.
Click to expand...
Click to collapse
Exactly my thought, should we all update our guides & tell everyone, NO PIT to be used?
A lot of people get confused over pit, & a lot of guys have faced problems too.
PS : I have International SGS, & I think they all come pre-partitioned with 512.

PIT files are only ever used when you wish to repartition, which is rarely necessary. There has been a lot of confusion in regards to this as in the past samfirmware was telling users to select a PIT file without repartitioning, which does nothing. Odin doesn't really make this clear either. I have tried to make this clear with Heimdall Frontend by only allowing the selection of a PIT file when repartitioning.

LaurensJ said:
Yes i mean that page as well (with the table).
Its also say's:
Please when you have only one file SKIP RE-PARTITION!
Use only .PIT files if you have 3 files!
So the last column of that table i interpret as using no PIT file ONLY when you have one file. But if the you update 3 files you need a PIT-file.
Click to expand...
Click to collapse
One file means a high level package, 3 files means a middle level package, both contain the same information. No difference at all. Richthofen has helped us a lot by converting a lot of high level packages to middle level ones & made it safer to flash because they dont contain boot loaders.
PS : No boot loaders, safer to flash.

ragin said:
One file means a high level package, 3 files means a middle level package, both contain the same information. No difference at all. Richthofen has helped us a lot by converting a lot of high level packages to middle level ones & made it safer to flash because they dont contain boot loaders.
Click to expand...
Click to collapse
OK.... Learned something new today. Thanks.

First- thanks for the clarification. For a newbie all this flashing process is unclear. Now I know I don't have to select a PIT file.
Second- Is it important to have CSC file? In Nokia you had to change your product code to be able to flash different firmwares. Is this the same in SGS?
Thanks!

bomba6 said:
First- thanks for the clarification. For a newbie all this flashing process is unclear. Now I know I don't have to select a PIT file.
Second- Is it important to have CSC file? In Nokia you had to change your product code to be able to flash different firmwares. Is this the same in SGS?
Thanks!
Click to expand...
Click to collapse
I am just an observer. I hope some real developers will really look into the matter & clarify things.
For SGS, you can flash any official firmware with a reg-hack, dont need to change the CSC for it

@ragin,
Not true, if you come from SEA region, pit513 is needed if your rom is from the Europe or US region, else there will be an error.
This apply as well, vice-versa.
Sent from my GT-I9000 using XDA App

I think repartition is necessary when lagfix problem happens, for example.
Sometimes we forgot the unlagfix before running new Roms on Oddin. In this cases repartition and pit flie, may fix the broken partition. Am i right?

criscan said:
I think repartition is necessary when lagfix problem happens, for example.
Sometimes we forgot the unlagfix before running new Roms on Oddin. In this cases repartition and pit flie, may fix the broken partition. Am i right?
Click to expand...
Click to collapse
Lagfixes dont alter partitions. Or am I wrong? They only change the file systems.

g00ndu said:
@ragin,
Not true, if you come from SEA region, pit513 is needed if your rom is from the Europe or US region, else there will be an error.
This apply as well, vice-versa.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Do you have to do it everytime? Since you already have a phone thats partitoned with 513.
India is SEA? I haven't used 513 ever.

ragin said:
Do you have to do it everytime? Since you already have a phone thats partitoned with 513.
Click to expand...
Click to collapse
Well, whenever I switched firmwares between the regions, yes, I need to. From DXJG4 to JP3, and from JP3 back to DXJPA.
No, SEA refers to Singapore, Malaysia, Thailand, Vietnam, Philippines, and it is also not the same as Hong Kong, Taiwan and China, that region has the prefix of ZS.
Sent from my GT-I9000 using XDA App

g00ndu said:
Well, whenever I switched firmwares between the regions, yes, I need to. From DXJG4 to JP3, and from JP3 back to DXJPA.
No, SEA refers to Singapore, Malaysia, Thailand, Vietnam, Philippines, and it is also not the same as Hong Kong, Taiwan and China, that region has the prefix of ZS.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
SO, SEA (South East Asia) is one region where you require a 512 if you want to flash other region ROMs.
Thats a start.

Is there a way to know how my device is partitioned right now (512,513,803)? any app to show this?
I have a phone from Thailand (so, 513?) and would like to flash firmware of another region (probably 512).

I think this is how re-partition and pit files work:
1. Pit files are only needed if you tick the re-partition box.
2. Re-partitioning reformats partitions back to rfs. (Not so sure about this.)
3. When you flash without ticking re-partition, odin overwrites the files without reformatting. This is where not disabling lagfixes can be problematic.
There are a few instances wherein you will need to re-partition:
1. As mentioned earlier, when you flash roms that use different pits, ie, 512 ->513 or 513 -> 512.
2. When you don't want to bother disabling lagfixes, you can do a re-partition to format everything. I've done this before and it's much faster than waiting for the robo-girl voice to finish her job.

[solved] Is this Odin setup correct to flash JVO?

Hello,
1) if I wanted to flash to JVO with Odin, is the setup in the attached pic correct (especially the files on PDA, PHONE, CSC and repartition ticked)?
2) Wasn't there a bootloader I needed to flash? I think I read somewhere the bootloader changed with GB.

Landorin said:
Hello,
1) if I wanted to flash to JVO with Odin, is the setup in the attached pic correct (especially the files on PDA, PHONE, CSC and repartition ticked)?
2) Wasn't there a bootloader I needed to flash? I think I read somewhere the bootloader changed with GB.
Click to expand...
Click to collapse
1)Yup
2)The bootloaders are included in the file you have ( See where it says sbl in the file name of the PDA )

Yeah saw that SBL and that made me suspicious whether that file really should go into the PDA slot and leave the bootloader slot blank.

Landorin said:
Yeah saw that SBL and that made me suspicious whether that file really should go into the PDA slot and leave the bootloader slot blank.
Click to expand...
Click to collapse
Nope leave it EXACTLY as you have it there mate and you are good to go.

and repartition has to be ticked as well, right?

Landorin said:
and repartition has to be ticked as well, right?
Click to expand...
Click to collapse
Yes.
You are using a pit file so you need repartition ticked.

Thanks a lot for the quick help!

Landorin said:
and repartition has to be ticked as well, right?
Click to expand...
Click to collapse
no don't repartition unless you want to in which case you need ONE EXTRA FILE: 512.pit!! You sound like a newbie so depending where you are coming from -stock firmware-wise, by all means repartition but you must obtain the 512.pit that you add to odin and flash with the rest of the rom. WARNING: this will wipe all your data and apps and repartition your phone including the sd card. make sure that you remove any external SD cards if you have one and the SIM card too...for peace of mind
UPDATE: oops! England has beaten Algeria...in cyberworldcup

I'd consider myself as noob, yep.
I thought I have to repartition when upgrading from JPY (2.2.1) to JVO? I don't know when this has to be done. Just saw the PIT file recommended for JVO on samfirmware and somehow assumed I have to repartition.
So what should I do, what's the difference if I do or not do it?
I backed up all data and wiped the phone before so there's not much on it right now (and no lagfix or so used, just stock rom with CF kernel).

Landorin said:
I'd consider myself as noob, yep.
I thought I have to repartition when upgrading from JPY (2.2.1) to JVO? I don't know when this has to be done. Just saw the PIT file recommended for JVO on samfirmware and somehow assumed I have to repartition.
So what should I do, what's the difference if I do or not do it?
I backed up all data and wiped the phone before so there's not much on it right now.
Click to expand...
Click to collapse
if you're sure that you used the same pit file as before i.e; 512.pit then you don't have to repartition at all.....if in doubt then repartition. BTW which pit file did you see on samfirmware.com? Should I assume that this is your first rom flashing from stock JPY? Also, make sure that you use the JVO rom that includes GB bootloaders.

Before? I never flashed a full ROM via Odin, only kernel (CF), thus I never re-partitioned myself.
Until now I used KIES always to flash ROMs.
If re-partitioning works like on a HDD I guess then this can be skipped unless something changed partition wise from Froyo to GB?
So do I need to re-partition at all?

Hey guys, gonna steal the end of this thread.
Currently I am on 2.2:
PDA: JPA / PHONE: JPP / CSC:JP7 (MET)
I want to use ODIN to upgrade to STOCK 2.2.1 and for it to change the CSC to XEU so that 2.3.3 (and future updates) will be done through kies automatically.
Can somebody confirm how I do this? Which file do i need to d/l - all three? And do I (and why) need to repartition?
Thanks in advance

Unregistered. said:
Hey guys, gonna steal the end of this thread.
Currently I am on 2.2:
PDA: JPA / PHONE: JPP / CSC:JP7 (MET)
I want to use ODIN to upgrade to STOCK 2.2.1 and for it to change the CSC to XEU so that 2.3.3 (and future updates) will be done through kies automatically.
Can somebody confirm how I do this? Which file do i need to d/l - all three? And do I (and why) need to repartition?
Thanks in advance
Click to expand...
Click to collapse
If you used Kies anyway, why not use it now to update to 2.2.1? Afaik you can change the CSC with market apps (think I read that somewhere but someone may want to confirm this). Anyways, you could just stick with your normal CSC as GB will be released to the rest of Europe anyway.
Currently, it's uncertain whether there will be more updates after GB afaik.
But yes, our question remains: do we have to re-partition at all if we only used Kies so far to update ROMs?

Landorin said:
If you used Kies anyway, why not use it now to update to 2.2.1? Afaik you can change the CSC with market apps (think I read that somewhere but someone may want to confirm this). Anyways, you could just stick with your normal CSC as GB will be released to the rest of Europe anyway.
Click to expand...
Click to collapse
Tried changing the CSC but it's didn't work. I'm with meteor and they are useless. So what i want is the stock 2.2.1 for UK and ireland as if it was d/l form kies and be on my way

Unregistered. said:
Hey guys, gonna steal the end of this thread.
Currently I am on 2.2:
PDA: JPA / PHONE: JPP / CSC:JP7 (MET)
I want to use ODIN to upgrade to STOCK 2.2.1 and for it to change the CSC to XEU so that 2.3.3 (and future updates) will be done through kies automatically.
Can somebody confirm how I do this? Which file do i need to d/l - all three? And do I (and why) need to repartition?
Thanks in advance
Click to expand...
Click to collapse
Official Samsung GB for UK has already rolled out, it's called XXJVO and believe me once you've done your first ODIN rom flashing you will never stop flashing other..(custom roms and kernels) if there're any geeky tendencies inside you and just waiting to be released... see this thread and all your fears will be assuaged!
http://forum.xda-developers.com/showthread.php?t=1011901

Widget21 said:
see this thread and all your fears will be assuaged!
http://forum.xda-developers.com/showthread.php?t=1011901
Click to expand...
Click to collapse
Thanks! There it says:
"Note: Re-partition is not a must, use it only if you need to change partition sizes on the device, but in most cases you will not need to repartition at all." question answered.
@Unregistered: you could use I9000XXJPY from samfirmware, JPY was the one that was offered to me by Kies back then (German unbranded SGS). But someone may want to confirm this to you first, as I see lots of others 2.2.1 ROMs there and not sure what the difference is. Samfirmware offers a single file and once extracted you should have 3 files.
I just wonder why the 2.2.1 ROM files do not show on that website which CSC is used, maybe it's universal or something?
Well, I guess Widget21 has a point here. If you are willing to flash now with Odin, you might be willing to do it with GB too, then the CSC won't matter (it doesn't matter much anyway as I learned).
Just be sure your 3 button combo is working and that you connect with direct USB.

Landorin said:
Thanks! There it says:
"Note: Re-partition is not a must, use it only if you need to change partition sizes on the device, but in most cases you will not need to repartition at all." question answered.
@Unregistered: you could use I9000XXJPY from samfirmware, JPY was the one that was offered to me by Kies back then (German unbranded SGS). But someone may want to confirm this to you first, as I see lots of others 2.2.1 ROMs there and not sure what the difference is. Samfirmware offers a single file and once extracted you should have 3 files.
I just wonder why the 2.2.1 ROM files do not show on that website which CSC is used, maybe it's universal or something?
Well, I guess Widget21 has a point here. If you are willing to flash now with Odin, you might be willing to do it with GB too, then the CSC won't matter (it doesn't matter much anyway as I learned).
Just be sure your 3 button combo is working and that you connect with direct USB.
Click to expand...
Click to collapse
Is it JPY or JPX for UK (XEU)?
I dont want to flash gingerbread. Not yet anyway.

Landorin said:
Thanks! There it says:
"Note: Re-partition is not a must, use it only if you need to change partition sizes on the device, but in most cases you will not need to repartition at all." question answered.
@Unregistered: you could use I9000XXJPY from samfirmware, JPY was the one that was offered to me by Kies back then (German unbranded SGS). But someone may want to confirm this to you first, as I see lots of others 2.2.1 ROMs there and not sure what the difference is. Samfirmware offers a single file and once extracted you should have 3 files.
I just wonder why the 2.2.1 ROM files do not show on that website which CSC is used, maybe it's universal or something?
Well, I guess Widget21 has a point here. If you are willing to flash now with Odin, you might be willing to do it with GB too, then the CSC won't matter (it doesn't matter much anyway as I learned).
Just be sure your 3 button combo is working and that you connect with direct USB.
Click to expand...
Click to collapse
JVO has multiCSC and UK's xeu is included in it so no need to worry about changing CSCs...remember the 'Thanks' button is there for a reason

@Unregistered: yeah, sorry, that's what I meant. If you wanna flash GB in the future you might want to do it with Odin and then the CSC shouldn't matter anymore.
For some reason, I'm unable to find out the CSC on the file and it's not listed. The JPY I downloaded from samfirmware recently has DBT as CSC (Germany). If you download the JPX file and extract it the CSC file might tell which region it is (as in my case).
@Widget21: I used my thanks feature up for today (5 max). I'll try tomorrow again.

I just downloaded this:
http://hotfile.com/dl/100618077/49a97b4/I9000XXJPY.rar.html
JPY_JPY_JPY.tar. I thought i was getting the three files. Where do i go from here

[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