Database Develop

Pre-Update, Research of Chinese Galaxy S

Dear all
I write this post as I hope to get some input and some expert suggestions on the course of action I should take with my phone.
For many years I have been supplied with a phone through my company but it seems to be always the crappy old Nokia. Good for making telephone calls but worthless for anything else.
So recently I bought a Galaxy S on a business trip to China. I love the phone, it works and by now I have almost no Chinese letters and applications left anymore. This is really something else; I'll never go back to the company Nokia. Never!
I think most of the applications are working and I have access to the Android Marked. However, Youtube is not installed or working and I think that the GPS is a little off.
Now I read a lot about Froyo and I bet I would want to get that on my phone, I am also pretty sure that I want to get the phone totally de-Chinese and preferably into something Danish or at least English.
What do I do next?
I have been reading so much on this site that I am getting dizzy. Flashing, rooting, updating, kies(hey, I actually got it working now (again) ) Odin, JM1, JPK etc.
Now my phone has the following;
ProductCode: I9000HKDVD2
PDA: I9000XXXXX
Phone: I9000BUJG1
CSC: I9000GVD2JG1
SalesCode: VD2
Reading through posts on this forum I never saw anyone with the same codes as mine.
Model number: GT-I9000
Firmware version: 2.1-update1
Kernel version: 2.6.29 [email protected] #2
Build number: ECLAIR
As mentioned, I bought the phone in China and I have no idea if it is branded (with Google printed on the back cover) has been unlocked, but I suspect it has. It has been rooted (I have a little black ninja guy giving Superuser Permission) and there is a folder-like icon named "root(and some Chinese letters)"
Well, as I said I have Kies running again. First it was running fine then it stopped connecting to the phone and now after unmounting the external SDcard I can again access the phone from my PC.
Through Kies I can do a firmware update. But should I?
Will it be re-locked?
Will it get all the Chinese stuff back?
Will it somehow be converted into a European phone?
Should I wait for the official Froyo or just go ahead and update?
I can update again when the Froyo finally arrive?
Do I need to make backup of any of my "system" files before doing anything?
Any help suggestions and/or warnings will be appreciated.

If you can do an upgrade through Kies it will aslo tell you what the update is (JG2 for example) since you have what I gues is a chine salescode, you will probably get a chinese update .. What you can do, is goint to the devlopers section and read the topic about spoofing your productcode in the registry so Kies thinks you have phone from another provider / country than that what you have now
I am almost certain that if you can enter an old danish firmware in the registry and a danish productcode you will get offeren a new new danish firmware through kies ..This will not relock your phone ( if it was locked before) as far as I know only the froyo builds will do that.

I have been reading some more on the forum and found that the phone is actually branded.
Model [Country of Origin](Branded Phone Carrier) = Code
I9000 [Germany](Vodafone) = GT-I9000HKDVD2
I have also checked out the 3-button combo which seems to be disabled on my phone. I'll get this fixed before doing anything.
So I want to update to the froyo release and will probably be uding the Kies hack to do this. I'll use the XEE code which I believe will give me the danish language as an option.
Do I need to make backup of some of the system files before doing this?
In some poste there is talk about backing up some system files before upgrading as there is some information which is needed to unlock the phone again.

Well. I am still investigation this issue.
Now I am looking into using odin and firmware from samfirmware . com. Probably to JPA or JPO? Then I have been reading about the DocRambone ROM and will probably try that.
However they suggest to "- Check Simlock and Network lock is OFF *#7465625#". When I do this I am promted with a "Rejected" message.
Can anybody please tell me what this means?
I do not want to start messing with it before I know that the phone will not be locked after flashing to new firmware?
If it will be locked then what is the procedure of unlocking anagin. I have already made backup of the "nv_data.bin.md5" and the "nv_data.bin". Having these files is the same as having backup of the /efs? Reason for asking is that I cannot find /efs on the root of my phone.
Please help!

[Q] Debranding SGS and updating to 2.2

Hi guys.
I just got a SGS yesterday as my HTC Desire was stolen last week.
The one I got is a German T-Mobile branded phone (has customised boot and shutdown logo) and I really wan't to get rid of the branding and all those useless apps on it. I live in Denmark so i have no use for T-Mobiles apps that don't work here.
Now i have been reading a lot yesterday on these forums and reading lots of guides but I'm still unsure what route to go. Currently the phone is running 2.1 and I wan't to upgrade to 2.2 or 2.2.1 but unbranded, and then root the phone a bit later and probably move to Darky's Gingerbread edition ROM.
From what i can gather there are 2 methods to do this, but I can't really find out witch one would be right for debranding.
1. Using KIES registry pattcher and change my product code to XEE (Nordics) and try that to flash it to official 2.2 and root that.
2. Using this [HOWTO] manually flash Samsung Galaxy S with JPY firmware ** WORKS **
If anyone can point me in the right direction that would be awesome.
[EDIT] Forgot to mention that i can boot the phone in both download mode and recovery mode holding the 3 buttons, so no need to fix that first.
Information on my phone:
Product code from KIES registry:GT-I9000HKDDTM
*#1234#
PDA: I9000BOJG3
PHONE: I9000BOJF1
CSC: I9000GDTMJH2
Build number:​ECLAIR.BOJG3
Firmware revision:​2.1-update1
Baseband:​I9000BOJF1
Kernel version:​[email protected] #2

1. Using KIES registry pattcher and change my product code to XEE (Nordics) and try that to flash it to official 2.2 and root that.
Thats the way to go but you would be best to safe a copy of the current ROM for warranty purposes as you would need to flash it back to make a claim .
Flashing via Odin only if you cannot use method 1 .
jje

Ok, thanks.
But how do I make a backup of the current rom? There is no download for it at far as i can tell.

Get Backup from Samfirmware.com
Go to Samfirmware.com click on Firmware then go to Firmware Section. Select then Android and then Galaxy S GT-I9000. Then download the I9000XWJG3 firmware.
Done

blockbusta said:
Go to Samfirmware.com click on Firmware then go to Firmware Section. Select then Android and then Galaxy S GT-I9000. Then download the I9000XWJG3 firmware.
Done
Click to expand...
Click to collapse
But XWJG3 is not a T-Mobile branded firmware is it? If it is nothing on these guides makes any sense.
Btw I did find a I9000BOJG3.rar file on some download page, downloaded and it does contain the following files that match my current versions. I have no idea if it's a working flash but if it is I would be able to flash thsi from odin to return to stock right?
I9000BOJG3.rar file contains:
CODE_I9000BOJG3.tar.md5
CSC_I9000GDTMJH2.tar.md5
MODEM_I9000BOJF1.tar.md5

Oh my Fault. I tought that only the ending is important (Like if the ending is JP7 than it's a Vodafone Firmware and if the ending is JG3 it's a T-Mobile

But XWJG3 is not a T-Mobile branded firmware is it? If it is nothing on these guides makes any sense
You get branded firmware from the network operator .
All firmware on these pages is non branded .
Again my suggestion is to use Kies registry patcher and spoof the update to whatever you want .
jje

I'm also trying to debrand my SGS and get Froyo, but I'd also like to make a backup of my original ROM. However, my ROM isn't available in samfirmware.com. It's I9000BVJJI1 and I want to update to I9000BVJJPD, which one of my friends has and probably is the same hardware.
Is there any way to backup my original ROM?

Your rom and every network rom comes from the network Sam is generic base roms .
Back up = Clockwork Mod Recovery to save the rom .
May i repeat if you dont know what you are doing then dont this forum is littered with broken phones belong to newbies who have not bothered to read and understand and now need to take the phone back to Samsung for repair with non valid firmware that has invalidated the warranty .
jje

Just did the update via KIES using the patcher and everything went smooth.
Saved the new firmware during flashing and a factory reset after the flash as i had basically nothing on the phone yet.
Right now I'm on 2.2
PDA: I9000XWJPA
PHONE: I9000XXJPP
CSC: I9000XEEJP4
Not rooted yet, but I'm gonna do that tomorrow probably.

[Q] Back to Stock using Kies

Hi I need some help, and I am sure this has been answered a number of times before but I am having trouble understanding the answers.
In the past I have installed the following Firmware using Odin 1.7.
PDA - I9000XXJPU
Phone - I9000XXJPU
CSC - I9000OXAJPU
Build 2010 12
PIT - from 12/08/2010
And this work just fine on the phone.
I would like to install an older version of the ROM so Kies will update it to the latest that Kies has to offer.
I know this is not the done thing, but this is what i would like to do.
So today I installed a couple of different ROMS but every time Kies tells me I can not upgrade the version I have installed.
I am sure it is me doing something wrong, but I am getting a little confused.
So any help would be great.

Kies path to upgrade is simple .
Checks Product Code Firmware details etc if Product Code Firmware details etc match up to original phone providers details it upgrades if not it fails .
So on your phone Kies cannot match the firmware you installed with the details as its not the firmware supplied by the provider .
Your path to official upgrade is either reinstall your original saved rom .
Or flash back to stock Eclair and use the Kies Registry Patcher from Themes section to spoof an official upgrade .
jje

JJ,
Thanks for your reply, I must be using the wrong rom's, my Galaxy is a none branded one.
Do you know which ROM I would need to install, I don't have my original backed up.
Is it still possible to spoof Kies, I understand this route has been broken.
All the best.Peter

Branding is not the same as product code .
The original supplier of the phone has a product code for their individual firmware branded or not . Thats the product code for upgrade path .
If you want the latest 2.2 Froyo Kies will only offer that when it gets the correct product code
Example of O2 UK product code
oftwareRevision
was
I9000ADJM1/I9000O2UJM1/I9000ADJM1/I9000ADJM1
ProductCode
Was
GT-I9000HKDO2U
HIDSWVER
Was
"I9000ADJM1/I9000O2UJM1/I9000ADJM1/I9000ADJM1"
That tells Kies to upgrade as numbers match .
I would suggest you use rom kitchin and build your own rom to flash if you are unable to use the Kies registry patcher to spoof the product codes .
http://forum.xda-developers.com/showthread.php?t=817703
Or use Odin to flash latest base rom .
jje

JJ,
Thanks for this information, it is all starting to make more sense now, my phone is supplied by Carphone Warehouse, so I just need to figure out what the original product code is. Then get all of the relevant components together.
Other than the relevant PIT, Modem, Code and CSC files, do I need anything else.
I have reverted by phone back to XXJPU as this works very well for me.
Peter

Rom kitchin has the CPW csc files i would build a rom .
Use JPY and if that works you can try a later one .
jje

[Q] Need some clarification on KIES is looking for

Lots of us are trying to get our phones back to Stock Firmware so KIES can update to 2.2.1 & at some point 2.3. In my case i9000T Latin America (TTT) model which seems to be very popular on the various US sites selling unlocked i9000 phones (New Egg & Expansys-us)
Many of us have used Euro 2.2 or 2.2.1 Firmware without issue using ODIN 1.3.
What happened in the process of applying the Euro firmware that keeps KIES from updating once you've rolled back to a stock firmware. In my case i9000TUBJH1 which is android 2.1 (ECLAIR.UBJI1) .
I've tried everything from changing the Product Code from KOR, TTT, PCW and any other one that might trigger KIES (1.5 or 2.0) in allowing the update.
I have 2 of these phones. One is untouched stock firmware. It was i9000TUBJG7 and after KIES update it's now (i9000TUBJP9 with a TTT Product Code). again, just trying to get my other phone back to stock and then update to 2.2.1 so both phones are the same.
Which file is KIES looking at to allow the update? CSC?
I'm not sure why the i9000T firmware is not readily available on samfirmware.
Thanks - many of us are just trying to learn the basics and spent hours reading these forums.

Try reading the last few pages of this thread. http://forum.xda-developers.com/showthread.php?t=959806

why bother with kies anyway i have a 19000t.. just use odin and flash the stock rom form samsungfimrwares.com or a custom one like docs etc..
i am currently on jpy with jl2 modem.
also once you have clockwork on you can also flash one of docs roms via that.
or is it that you are trying to get a stock rom via kies. that is not on samsungfirmwares.com ?
if that is the case i think the reason may be that these stock firmwares were never release via kies?

I bricked my initial handset using KIES as it crashed during the update. Won't be using it again to flash my phone.
Sent from my GT-I9000 using XDA App

Samfirmware & i9000T
No sign of any i9000T (TTT) Latin America firmware on Samfirmware.com. The latest update via KIES for this phone was about 10 days ago. Version i9000TUBJP9 which installs 2.2.1.
Again, just trying to get back to stock. I'll be passing this phone to another user at some point and they'll need KIES to keep it simple.
Any help in understanding what keeps KIES from updating after you've installed stock 2.1 firmware would be great.
I'll keep reading ...
thanks

Kies reads the codes from the phone .
Firmware 2.2 Product Code Vodaphone Hardware ID Vodaphone .
Looks for update for the product code if all matches downloads .
Product Code stock Hardware ID stock matches nothing on its Database = no update .
Route back i have used is flash Eclair spoof product code via Kies registry patcher . Upgrade and save rom at the same time to enable reflash to product codes firmware .
jje

Did you manage to get the update from Kies? You would do a great service if you can share the firmware.

Kies looks at the product code. I replied to your other post.

[Q] Present, past and still a future (with no product code)?

Hello,
I am new to mess around with mobile phones and Android and (therefore) also managed to bring my girlfriend's GT-I8190 phone to a non-working state. Although there are lots of information in this forum I am more confused than sure what to do. I hope to get here some help / information / explanation.
Past
The phone was bought in Germany and had probably a German firmware. But I do not know, since no connections to Kies or whatsoever and no backups where done earlier. After a error of Android (e:\ failed to mount or something similar) which blocked the phone on the startup logo of the non-modyfied S3 mini, my guess for a quick solution was to flash the firmware with Odin to a new(er) German version. I downloaded (from a German forum) and flashed successfully several versions (supposedly OXA). But with all version the network connection hasn't practically worked. Only very weak and only at a few locations. Once I used in desperation also a so called stock-recovery from somewhere.
Present
I visited a shop where the uber-friendly Samsung service overwrote the firmware first with the general and later with the LaFleur version (PDA: XXAMG4, CSC: QXXA MH1). Kies tells me the CSC is somehow a VE1 version (what country is that code for - moon?). But the problem hasn't changed.
I still have the original IMEI, but I'm missing the baseband and, what worries me more: no product code. I managed to read it out only with "CheckFus" which says only: Not Active1
Future ?
Since I probably haven't used the right firmware at least once, I am hesitating to do more. My ideas are as following: modem, firmware, baseband.
What is the best way to proceed? Is there still a easy solution? I don't mind to change to another version - no stock firmware is required. Am I close to have a 4" tablet?
Any answer is appreciated - thanks!

bohlero said:
Hello,
I am new to mess around with mobile phones and Android and (therefore) also managed to bring my girlfriend's GT-I8190 phone to a non-working state. Although there are lots of information in this forum I am more confused than sure what to do. I hope to get here some help / information / explanation.
Past
The phone was bought in Germany and had probably a German firmware. But I do not know, since no connections to Kies or whatsoever and no backups where done earlier. After a error of Android (e:\ failed to mount or something similar) which blocked the phone on the startup logo of the non-modyfied S3 mini, my guess for a quick solution was to flash the firmware with Odin to a new(er) German version. I downloaded (from a German forum) and flashed successfully several versions (supposedly OXA). But with all version the network connection hasn't practically worked. Only very weak and only at a few locations. Once I used in desperation also a so called stock-recovery from somewhere.
Present
I visited a shop where the uber-friendly Samsung service overwrote the firmware first with the general and later with the LaFleur version (PDA: XXAMG4, CSC: QXXA MH1). Kies tells me the CSC is somehow a VE1 version (what country is that code for - moon?). But the problem hasn't changed.
I still have the original IMEI, but I'm missing the baseband and, what worries me more: no product code. I managed to read it out only with "CheckFus" which says only: Not Active1
Future ?
Since I probably haven't used the right firmware at least once, I am hesitating to do more. My ideas are as following: modem, firmware, baseband.
What is the best way to proceed? Is there still a easy solution? I don't mind to change to another version - no stock firmware is required. Am I close to have a 4" tablet?
Any answer is appreciated - thanks!
Click to expand...
Click to collapse
Try to flash this firmware : http://www.sammobile.com/firmwares/3/?download=18114 via odin3 it's a i8190XXAMG4 (DBT) firmware it also include modemfs (modem) then try to upgrade your baseband to XXAMG4.

bohlero said:
Hello,
I am new to mess around with mobile phones and Android and (therefore) also managed to bring my girlfriend's GT-I8190 phone to a non-working state. Although there are lots of information in this forum I am more confused than sure what to do. I hope to get here some help / information / explanation.
Past
The phone was bought in Germany and had probably a German firmware. But I do not know, since no connections to Kies or whatsoever and no backups where done earlier. After a error of Android (e:\ failed to mount or something similar) which blocked the phone on the startup logo of the non-modyfied S3 mini, my guess for a quick solution was to flash the firmware with Odin to a new(er) German version. I downloaded (from a German forum) and flashed successfully several versions (supposedly OXA). But with all version the network connection hasn't practically worked. Only very weak and only at a few locations. Once I used in desperation also a so called stock-recovery from somewhere.
Present
I visited a shop where the uber-friendly Samsung service overwrote the firmware first with the general and later with the LaFleur version (PDA: XXAMG4, CSC: QXXA MH1). Kies tells me the CSC is somehow a VE1 version (what country is that code for - moon?). But the problem hasn't changed.
I still have the original IMEI, but I'm missing the baseband and, what worries me more: no product code. I managed to read it out only with "CheckFus" which says only: Not Active1
Future ?
Since I probably haven't used the right firmware at least once, I am hesitating to do more. My ideas are as following: modem, firmware, baseband.
What is the best way to proceed? Is there still a easy solution? I don't mind to change to another version - no stock firmware is required. Am I close to have a 4" tablet?
Any answer is appreciated - thanks!
Click to expand...
Click to collapse
I8190XXAMG4 / QXXAMH1 is a German La Fleur firmware. I have no idea why your CSC seems to be messed up. It should probably be DBT.
What does it say if you dial *#1234# in dialer?

Thanks for the infos so far.
I did not intend to link to the LaFleur version in the first post.
Do I need the root recovery for the baseband update?
With the 1234 code I get:
AP: I8190 XXAMG4
CP: XXXX
CSC: I8190 QXXAMH1
I think this is the same as mentioned before. I checked the origin of the files I used before on this mobile and it is possible that I used this a recovery file which may be for a 8190N (I cannot post the outside link yet). I did not read careful enough the thread linking to this file.
Can this be the origin for the messed CSC version and the missing product code?

Looks like you're without baseband.
Take a look at this thread and flash a modem for i8190.
http://forum.xda-developers.com/showthread.php?t=2526831
Sent through time and space from my s3mini/CM11

Happy end
Hello again,
firstly: Problem is solved - phone works properly. Thanks for the replies and to tys0n for the work with the files and the support - acutally doing the job of Samsung and google.
For the sake of completeness, I will tell what I did, if any unexperienced user (as I still am) will ever come across this thread:
I tried first just the standard firmware AMG4 from Sammobile (which is linked above) and afterwards the baseband files - but both did not help as expected.
I installed CWM and used the file from here and miraculously it was working (The phone is used only in 2G). Later I wiped the data and flashed again with the AMG4 firmware to have a clean version now.
AP, CP, CSC say all XXAMG4 now, Kies recognizes it as DBT (as supposed to). But the product code, which came back and was read out with CheckFus, says I8490 RWA XSE. This should be Indonesia, correct? Is there still an inconsistency somewhere?
Thanks again for the help
Robert