I have a T-Mobile UK Galaxy S and would like to back up the stock firmware before flashing anything new to it. It has:
Baseband: I9000XXJF3
PDA: I9000XXJF4
PHONE: I9000XXJF3
CSC: I9000TMUJE6
Obviously I can download I9000XXJF3 so I can get back to the correct baseband/PHONE. However, I've not seen any JF4 firmware files, and obviously the CSC is custom for T-Mobile's APN settings.
Therefore, if I make a nandroid backup and restore that onto I9000XXJF3, will it restore the PDA and CSC to those versions? I'm not sure how, exactly, what nandroid backs up correlates with those parts of the ROM (although I think it doesn't back up PHONE?).
Thanks!
I have the same versions as you and made a nandroid backup of my rom and then upgraded to other roms (currently SamSet 1.9b) but I can confirm Nandroid backs up CSC and PDA. To get it back to stock (including modem) I just flash back to I9000XXJF3 and restore Nandroid backup and then modem, PDA and CSC are the same as when I received the phone.
On a side note, any chance you could upload your csc folder (or at least the TMU folder) I don't know if mine got messed up before I backed up as customer.xml references files such as "/Customer/TMU/Messagetone/TMO Message tone.mp3" that don't exist?
Hm, where would I find these files? The csc folder doesn't contain them, and I don't see a /Customer/ directory off the root. Indeed, I've never seen a T-Mobile ringtone as an option anywhere, and if I search for "TMU" in Astro I can't find anything. It's also not listed in /system/CSCFiles.txt, which I assume is a list of files contained in the CSC, and only contains:
Code:
/system/csc/customer.xml
/system/csc/others.xml
/system/csc/sales_code.dat
/system/csc/feature.xml
/system/csc/contents.db
/system/app/VoiceSearch.apk
/system/SW_Configuration.xml
/system/CSCFiles.txt
I could pull out those files, and perhaps dropping those onto the device (with root) would give it I9000TMUJE6 CSC? I don't know how to make it into an update.zip.
Anyway, I did a factory reset followed immediately by a nandroid backup, which I've uploaded in case that's useful:
http://www.megaupload.com/?d=G033UEH5
I don't see a /Customer either on mine and the CSCFiles.txt doesn't list it but in CSC/customer.xml it references them... maybe they were going to put them in but never did?
As for creating the update.zip I did manage to make one but it didn't seem to apply (the CSC version changed to TMU but the bookmarks/settings etc didn't get applied) until I followed http://forum.xda-developers.com/showthread.php?p=7338830#post7338830 to change it to TMU.
To be honest though, I have never bothered doing it as no matter what I flash, MMS and 3G internet and everything works without me doing a thing. I just keep it incase I need to send it back for any reason.
Accidentally created new post instead of editing old one, sorry.
So... does nandroid backup everything?
I mean, if I do a backup (let's call it original).
Then I install a ROM with a different baseband/MODEM.
If I restore the backup... Will I have the original baseband/MODEM?
Thanks!
Related
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
Hi Guys , New to the forum but I have learned a lot in the last few weeks, from the excellent guides and information in the forum ,however there is a question that somehow no one seems to answer, I have a samsung galaxy s with the following firmware
PDA : I9000XWJM3
Phone : I9000XXJM2
CSC :I9000OXXJM2
The phone is about 2 months old, anyways I have done a few Custom rom Installs and flashed newer versions of android, and I find that every time I revert to a nandroid backup, of the orignal firmware , the baseband (I9000XXJM2) will never restore back i.e will always keep the baseband of the custom rom or the newer firmware, now the problem is that I cant find this stock firmware anywhere on the net, neither can I backup the orignal baseband. the versions are always either older or newer than my stock firmware... the phone had a dead pixel so sent it back to samsung and it came back flashed with my old original firmware. now to get to the point is there anyway to backup the baseband ? or can anyone point me in the right direction ? samfirmwares definitely doesn't have a copy of this original firmware. I sent the phone back to samsung with the incorrect baseband not even available in my country I may not be so lucky the next time something goes wrong so id like to keep a full stock version of the original firmware. any help will be cool
don't forget to back up the /efs folder. so that if your phone's /efs folder gets corrupt and you can't make calls, you can restore it easily.
by the way, your modem (baseband) can be found on samfirmware and it must be contained in I9000XXJM2 firmware.
the guy who flashed your firmware mixed 2 firmwares, that is the reason why you couldnt find it.
by the way, your modem (baseband) can be found on samfirmware and it must be contained in I9000XXJM2 firmware.
Can you find XXJM2 save the OP looking for the invisible firmware .
Looks like you have odd original, firmware .
Save baseband file downloaded from sam will include the baseband/modem file in the zip/tar file . You can just save that or extract the modem .Its possible to just flash the modem or swap modem in custom roms .
Can you open the Nandroid backup and see if modem is in that .
jje
thanks , I have backed up the EFS folder already , but as I said I cant find that version of firmware, samfirmware does not have a XXJM2 firmware rather a XWJM2 firmware package the has a XXJM1 modem file in it
legend-zn said:
thanks , I have backed up the EFS folder already , but as I said I cant find that version of firmware, samfirmware does not have a XXJM2 firmware rather a XWJM2 firmware package the has a XXJM1 modem file in it
Click to expand...
Click to collapse
hi buddy
can u tell me or post a link on how to backup baseband?
Hi all,
I'm preparing to flash a stock JPY version to my SGS (samfirmware one). In order to get the same version of all partitions (pda, phone and csc) I mean to flash all of them (pit+repartition).
Is this procedure dangerous for my efs folder if the CSC is different from my actual operator (movistar-spain)?
I don't know what information CSC carries on and i'm scared of spoil any essential folder...
Another option is update through KIES to the last fw that my operator has released (2.2) and then just the JPY PDA, leaving untouched PHONE and CSC, but in that case i won't have the same CSC/PHONE version than the PDA one.
What would you advice??
In any case, later on I'll flash a JPY stock voodoo which is my target until a stable Gingerbread is released...
Thanks a lot...
I am not sure if it is dangerous or no, but you should always keep a backup of your /efs folder just in case. You can either copy one manually with a file manager and save it on your external SD card, or use an app to do it...or both. I both manually made a copy and used SGS Toolbox, free on the Market.
When in doubt, back it up!
Welcome,
Since you are new to flashing the SGS with custom Rom (i suppose), i can only recommand you to stick with Kies rom update, until you master and understand every aspect of Kernel/rom (pit-csc-pda/partition).
Custom flashing is not supposed to alter the efs, but some partition error or file corruption could happen.
Anyway if you think you are ready, make a check list, verify the 3 Combo button, AND ALWAYS! ALWAYS! make a backup of your efs folder (all / folder is better in fact). Do also an img of your own phone, it'll give you a chance to reflash it to Stock.
Good luck.
CalabiYau said:
Hi all,
I'm preparing to flash a stock JPY version to my SGS (samfirmware one). In order to get the same version of all partitions (pda, phone and csc) I mean to flash all of them (pit+repartition).
Is this procedure dangerous for my efs folder if the CSC is different from my actual operator (movistar-spain)?
I don't know what information CSC carries on and i'm scared of spoil any essential folder...
Another option is update through KIES to the last fw that my operator has released (2.2) and then just the JPY PDA, leaving untouched PHONE and CSC, but in that case i won't have the same CSC/PHONE version than the PDA one.
What would you advice??
In any case, later on I'll flash a JPY stock voodoo which is my target until a stable Gingerbread is released...
Thanks a lot...
Click to expand...
Click to collapse
@ CalabiYau, the first thing that you must do is a copy of your efs folder (for your Imei some error in the flash might to require the use this backup), then you can put all the PDA and Modem part with CSC Fop.
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
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