yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 General] damenchoy:
I think this one should be the official one.

http://www.kingmobi.net/bbs/thread-148803-1-1.html
[Galaxy S I9000 General] miketwn:
im on zsjpd that should be for taiwan.........official from kies...
[Galaxy S I9000 General] manager77:
where can l take JPD?! thanks!
[Galaxy S I9000 General] chanw4:
Really don't like the Chinese forum... Poster always hiding the content and require user to reply...

Anyway, can't upgrade cos I'm on JPO now.
[Galaxy S I9000 General] miketwn:
I downloaded directly from kies. Its an official update...now how to root?
[Galaxy S I9000 General] ragin:
Please relocate this THREAD, NOTHING related to ROM DEVELOPMENT.
[Galaxy S I9000 General] RA017:
How I can check the build date of these roms to tell which one is the latest ?
[Galaxy S I9000 General] manager77:
can you tell me your Product Code and HIDSWVER or Software Revision
[Galaxy S I9000 General] saphirrot:
Thank god, we can now download official 2.2 Froyo from Kies :D

News : http://www.inside-handy.de/news/19712.html
[Galaxy S I9000 General] frauhottelmann:
Which version is it?
[Galaxy S I9000 General] dupel:
Better question is "which forum is it?"
[Galaxy S I9000 General] NoOoSi:
I'm currently at:

PDA:JP6 / PHONE:JPM / CSC:JP4 (updatet to JP6 via reghack+kies)

Kies now tells me that firmware can be updated and offers me:

PDA:JPA / PHONE:JPP / CSC:JP4

So is this now the official version??
[Galaxy S I9000 General] dcc22:
JPO / .../ JP3

can't remember the part in the middle :/
[Galaxy S I9000 General] saphirrot:
iam sorry, im in the wrong forum :D

atm kies shows me : PDA:JPA / PHONE:JPP / CSC:JP4
[Galaxy S I9000 General] miketwn:
I got official update today in asia.... FROYO.ZSJPD....
[Galaxy S I9000 General] DarKprince87:
what's your product code?? because I've a DTM product code (which means germany t-mobile) and a JG3 PDA firmware but still no update availables from kies :-(
[Galaxy S I9000 General] NoOoSi:
this firmware update is for unbranded phones only
[Galaxy S I9000 General] gonsa:
i've got a DBT product code phone, and right now i'm using Doc_Kalpik V7 JPO.

How can I update via Kies?

and what version is for DBT, JPA or JPO?
[Galaxy S I9000 General] DarKprince87:
unbranded = GT-I9000HKDXEG product code for germany??

and when will it be released for branded ones??
[Galaxy S I9000 General] gonsa:
mine is unbranded and is DBT.
[Galaxy S I9000 General] bendikou:
I have JPM with reg hack but now i have a problem
[Galaxy S I9000 General] DarKprince87:
DBT = 2.2 available with kies? am I right?

following a list on xda

DBT is branded (debitel) and XEG is unbranded for germany.... I'm a bit confused :S
[Galaxy S I9000 General] Philbert123:
this seems to be wrong.

In my opinion near all unbranded sold SGS in germany are DBT!

edit:
[Galaxy S I9000 General] pfannenwender:
does anybody have an idea what we do have to enter into the registry entries to get this german firmware?
[Galaxy S I9000 General] DarKprince87:
you cannot change anything by registry hack anymore. I've personally changed my product code with the exadecimal method but still can't receive the update... it seems that kies matches product code + firmware version
[Galaxy S I9000 General] pfannenwender:
doesnt even work with an old kies version?
[Galaxy S I9000 General] DarKprince87:
it "should" work with an older version of Kies btw if you don't have the last kies release the update to froyo is not possible. so it's useless.... ant I'm getting mad about this!

Here my specs:

product code: I9000HKDDBT

pda: JG3

phone: JF1

csc: JH2

AND STILL CANNOT UPDATE WITH KIES!! what the hell are they doing??
[Galaxy S I9000 General] pfannenwender:
im at

I9000XXJM1/I9000OXAJM1/I9000XXJM4/I9000XXJM1

product code: I9000HKDDBT

any idea what i can flash to to get this update?
[Galaxy S I9000 General] Phandroid:
I thought JPO was official for Germany?..
[Galaxy S I9000 General] Philbert123:
If you want to flash, why not flashing directly to the final froyo version?
[Galaxy S I9000 General] pfannenwender:
could do just that, but im not really sure what i have to flash to land on an unbranded froyo that will be updatable via kies.
[Galaxy S I9000 General] logih:
Einfach lesen:

http://xdaforums.com/show...2&postcount=19
[Galaxy S I9000 General] majava:
Just upgraded to JPA via Kies. Available in Finland as of today I guess. Seems pretty much the same as the earlier version from Kies, but doesn't lose your market app or any of that jazz.
[Galaxy S I9000 General] pfannenwender:
thanks logih!

going to try that in a bit.
[Galaxy S I9000 General] snack23:
Here we go...

Die neue Firmware trägt die kryptische Bezeichnung PDA:JPO / PHONE:JPP / CSC:JP3

xxx.areamobile.de/news/17005-android-2-2-froyo-fuer-galaxy-s-in-deutschland-angekommen
[Galaxy S I9000 General] DarKprince87:
which product code do you have? DTM or DBT??

anw I'm gonna try the logih method ^^
[Galaxy S I9000 General] brack11:
I9000HKDDBT

I9000XXJM9/I9000OXAJM1/I9000XXJMD

Original was unbranded jm1 dbt from Germany no update here.
[Galaxy S I9000 General] DarKprince87:
I'm having a lot of troubles :-(

1st I've used the reg-hack and update with kies.... results? my phone freeze at startup on the S, then the screen goes black and the phone vibrate several time...

2nd I've flashed with odin to jf3, and then updated with kies . This time the phone was able to launch but.... the MODEM part was NOT INSTALLED !!!

3rd: I've flashed with odin 1.3 directly to JPO but with no good results.... same of 1st time.... lightin' S and black vibration....

I'm very sad of this :(
[Galaxy S I9000 General] Philbert123:
Have you made a factory reset?
[Galaxy S I9000 General] DarKprince87:
yes.... I think there might be a problem with the lagfix I did previously..
[Galaxy S I9000 General] brack11:
If you used odin, set tick on repartition, and after doing first reset after flashing, format your sd cars as well. The last point helped me to solve the same issue with jpm.
[Galaxy S I9000 General] DarKprince87:
it seems that the upgrade via kies old (with reghack changes) doesn't work fine... I've tried it 3 times, and each time kies doesn't install the phone part!
[Galaxy S I9000 General] brack11:
Maybe experts will kill me, but having the same problem with kies a well as with odin I inserted sim card in the phone and flashed while it was in the phone, after flash I had phone part. But I'm not sure how dangerous is it for sim or for phone.
[Galaxy S I9000 General] DarKprince87:
can you exlpain it better please? :D
[Galaxy S I9000 General] darren2190:
Flashing way I9000XWJPO:

First I9000XWJM8 with RE-Partition and 512.pit.

Then I9000XWJPO without RE-Partion use 803.pit.

You should not have any problems.
[Galaxy S I9000 General] snack23:
---> i9000hkddbt
[Galaxy S I9000 General] brack11:
It's just that people recommend to take sim off while flashing, but I decided to disobey them and kept sim inside, and think this helped me.
[Galaxy S I9000 General] DarKprince87:
I've always flashed with flash inside the phone.... but the weird thing is that if I flash a previous FW all works fine. When i flash JPO the phone part is not installed, and when i press *#1234# the phone part tells: UNKNOWN
[Galaxy S I9000 General] fear619:
@ ligih: thanks dude, that quote u gave worked fine i Croatia.
[Galaxy S I9000 General] Xer007:
Hey people, my phone also from Germany, with code :I9000HKDDBTGT; I9000HKDXEU and firmware nto availiable in KIES, also my firmware now is JG1, can you give me advice?
[Galaxy S I9000 General] brack11:
When I say SIM I mean not FLASh memory card, but sim card issued to you by provider.
[Galaxy S I9000 General] eurocat63:
Check this tread and wait a litle:

http://www.youmobile.org/blogs/entry...rldwide-Dates-

:D
[Galaxy S I9000 General] ayn:
Hi,

has anyone a Problem with the Navigon MobileNavigator 3.5.1 D-A-CH since the FroYo Up?

I'm currently not able to get the Software running, short after the Spalshscreen it hangs and has to be forced close.

Oh - and the App disapper from the Market for me so i cannot flame into the Comments... :/

Mail to android@navigon.com is out but... NULL. Damn, the App costs about 60€ and the Support is like a bad Joke...

Bye
[Galaxy S I9000 General] MCOGW:
Don't understand what you exactly want to do.

Both 2.2 firmwares (XEU and DBT) are already available...
[Galaxy S I9000 General] brack11:
navigon select wad not designed with galaxy s in mind because it looks for it's files in sd folder of sdcard as eclair has, but froyo has renamed sd to external_sd and navigon cannot find it's files. However, after googling a bit I found recommendation to go to /data/data/com.navigon.../files/NaviKernelConf_SG.ini and change all references to from sd to external_sd this hack should work if your phone is rooted, but I didn't try it myself though. Backup your file before editing.
[Galaxy S I9000 General] bendikou:
i got the PDA:JPO / PHONE:JPP / CSC:JPo !?!

where is the difference and why !?
[Galaxy S I9000 General] Xer007:
for me not availiable /:, KIES last version
[Galaxy S I9000 General] Midnight_Rambler:
Hello campers! I have a problem updating my SGS. I'm in Germany, I've installed the latest version of Kies and the update is available. When I try to update Kies gives me a message "die Datei ist vorhanden" and nothing happens. Have someone confronted with this issue? Thanks
[Galaxy S I9000 General] Chronos12:
( official Froyo - Germany ) After SuperOneClick, then I installed Lag Fix OCLF.

I installed EXT2 then Lag Fix 1+. After this I uninstalled Lag Fix. After this I removed the EXT2 from Lag Fix and then the warning came.
[Galaxy S I9000 General] sean2476:
The server is probably busy, keep trying.
[Galaxy S I9000 General] brack11:
Of those with DBT phone with JPO flashed with Kies, can you tell me if there is Russian locale in Swype? I need Russian keyboard, but if it's not in JPO Swype, there is no inteest for me to upgrade.

Thank you in advance.
[Galaxy S I9000 General] brack11:
Answering my own question - no, there is no russian locale in jpo swype. The thing is also not acceptably lagging, so, I'm back to jm9.
[Galaxy S I9000 General] Nafiganado:
I tried to do this, but when I call Update firware dialog - the modified data in registry are replaced again with the ones from the phone :(

So I can't update...
[G2 and Desire Z General] Veggies:
So the signature is encoded over the update.zip right so all we need to do is steal the difference between signed and unsigned update files they have to be the same file but uziping and reziping does so. All that needs to be done from there in my thought is calculate each offsets difference and bam signature. Now create a new update.zip with all rooted files. Clockwork and s-off being all we need. Make the update the same size exactly and add the difference we obtained to it and bam rooted it is
[G2 and Desire Z General] John5788:
public key cryptography 101 says it wont work.
[G2 and Desire Z General] Veggies:
Why won't it work if I may ask.
[G2 and Desire Z General] Markley02:
What you are proposing sounds acurate in my head, but everything says it doesn't work that way. I guess some things I will never understand..... Women is another one.
[G2 and Desire Z General] Veggies:
Ill do it on my own and test it when I get home again. MORE COFFEEE!!!
[G2 and Desire Z General] Dom18:
Chances are the security will relise something is wrong when doing the update even if everything is set perfectly and thus you may end up with a bricked phone.
[G2 and Desire Z General] Veggies:
Yayy for phone insurance claims then
[G2 and Desire Z General] Dom18:
More power to you then my friend, go nuts, maybe youll get something out of it that helps with the perm root.
[G2 and Desire Z General] Markley02:
I highly doubt that will happen. Look at all the failed updates due to the whole goggles thing.
[G2 and Desire Z General] Veggies:
Quick question though how does one set s-off in the image so I can try this. And to clarify I'm using a hex editor to re-add the diff from the signed and unsigned updates so the calculating will be a headache :/
[G2 and Desire Z General] funkadesi:
Didn't they say decrypting the signature from or the key would take a lot of time, i mean were talking years?
[G2 and Desire Z General] rmk40:
Just incorrect in every way imaginable. That's not how signature verification works. If cryptography could be circumvented that easily no one would use it. I am not going to explain asymmetric encryption in this thread, there are plenty of resources for that. Let's just say what you're proposing here has no chance of working whatsoever.
[G2 and Desire Z General] StanSimmons:
Start here: http://en.wikipedia.org/wiki/Public-key_cryptography

and here: http://en.wikipedia.org/wiki/Digital_signature

Unless HTC put an idiot in charge of their crypto, what you are proposing won't work.
[G2 and Desire Z General] enderblue:
Yeah, if you are lucky, they will have put jdkoreclipse in charge of that. I think that is the only way the encryption could be done as poorly as you are suggesting.
[G2 and Desire Z General] Hosermage:
I forget where I suggested this... but I was thinking someone could write one of the SETI@home or bovine (for those who remember) type application, where the client can run on anyone's machine that tries to crack the key by connecting with a central server in a coordinated effort. All of us G2 owners could run the client on 1 or multiple machines 24/7 and we may get lucky and find the real key.

I'm willing to install it on every machine at work if someone will write that client program ;-)

reference: http://www.distributed.net/RC5/en
[G2 and Desire Z General] ibemad1:
To the best of my knowledge unzipping and rezipping it wouldn't break the signature...
[G2 and Desire Z General] JanetPanic:
I don't want to be insulting but if you do not understand PPK cryptography and how cryptographic signatures work please do not try and "break" something that has been evaluated and probed by numerous security experts in an attempt to find vulnerabilities.

It might be possible to crack ppk based signatures but it is not a simple matter of a diff between pre and post signature files. Again, I don't want to hurt anyones feelings but people A LOT brighter than you who actually understand the mathematics involved are not able to do it.

Put simply I will give you 2 documents, a signature for one of the documents, and a public key to verify the signature. If you can derive the key from which the signature is made or a way to create a valid signature for the second without the key you will be famous overnight since you will have found a vulnerability in one of the cornerstones of modern cryptography. Again it is possible but the chance of success without knowledge of the mathematics involved is monumentally small. Even with knowledge of the mathematics such a crack has not been found by people dedicated to researching such vulnerabilities.

Sorry for the rant but voodoo mechanics is a sore subject for me.
[G2 and Desire Z General] flarbear:
The simplest way I can explain it is the following.

Let's say they put a tag in the file that said "Google signed this". All someone would have to do is move that tag to a new file and it would look like Google signed that new file. So, that process doesn't work.

OK, let's say they put a tag in the file and said "Google signed a document that contained these bytes - blah blah blah", well same problem, someone could move the tag and edit the "blah blah blah" part to match their new file, so that doesn't work either.

So, instead Google puts their signature into the file, then they encode that file in a way that only they know how to do, but using an algorithm that they can make public the way to decode it. So, everyone can still get access to the contents, but nobody knows how the magic "encode" process works so nobody can pretend to be Google and produce a file that has their particular encoding. Since their signature is inside the part that was encoded, it is clear that they put their stamp on it prior to running the encode algorithm so you know for a fact that it was "signed at the Google factory".

Someone can try to put Google's signature in another file and then try to figure out how to do that encoding, but they wouldn't be able to mimic the exact way that Google does it so everyone would know that the encoded file came from someone else. Thus they are foiled.

A few details:

- The encode/decode process is actually a backwards encryption algorithm. Google encodes a file by "decrypting" it (i.e. pretending the real data was encrypted and running a decrypt on it and getting some garbage). The public then decodes this file by "encrypting" it (i.e. using the public keys to encrypt a file for Google and running it on the results of their decryption ends up getting back to the original file). Magic

- They don't really encode the entire file as that would be computationally intensive. Instead they generate a "checksum" of the original file that is both fast to compute and unique (i.e. the chances of a different file generating the same checksum is 1 in a HUGE number). They then encode that checksum (which is much, much smaller than the original file) using their special encode mechanism and not only can nobody produce a file that happens to have the same checksum (it is not known how to produce a different data stream that results in the same checksum), but they also cannot reencode the signed checksum due to the properties that make encryption so safe. (Note that the "checksum" algorithm here is quite a bit more complicated than adding up all of the bytes in the data stream - which would be easy to falsify - but it is still easier to compute than an encryption algorithm).
[G2 and Desire Z General] damien667:
I wanna add that most of that process is known because of AOSP and how we sign with the test keys. The only piece missing is google's/t-mobile's/htc's private key (because...who knows who really made the one for the G2?).

my 2 cents
[G2 and Desire Z General] khaosxiii:
Awaiting OPs response :D
[EVO 4G General] CheesyNutz:
Google just launched an enormous volley in the war of the data kings. Facebook and Google have been gearing up for war for a long time now, and Facebook’s alliance with Microsoft and Bing was practically an act of war. Now, Google is fighting back, albeit subtly. They changed their terms of service ever so slightly, but in a way that hurts Facebook in a big way.

According to TechCrunch, the ToS now requires reciprocity for anyone using the Google Contacts API to grab contact information from Google users. This means that whenever Facebook uses a Google API call to get contact data from a Google account, which is exactly what happens when new users are asked if they want to import their contact data from Google, Facebook will be required to give the user’s Facebook contact information back to Google. Facebook has never given their contact information out, and it’s highly unlikely that they will all of a sudden change this practice. It also affects the entire Google portion of their vaunted Open Graph, restricting a lot of information from Facebook’s data mining operation.

The only other option for Facebook at this point is to take away the Google importing functionality and hope for the best. Somehow, though, the idea of the biggest social network in the world backing off so easily doesn’t seem likely. It will be interesting to see what happens if they lawyer up and argue the legality of the new reciprocity clause.

In a statement, a Google spokesperson highlighted that this isn’t a greedy push for data.

It’s important that when we automate the transfer of contacts to another service, users have some certainty that the new service meets a baseline standard of data portability. We hope that reciprocity will be an important step towards creating a world of true data liberation–and that this move will encourage other websites to allow users to automate the export of their contacts as well.

It sounds less like a greedy grab for data, and more like an attempt to enforce an open data portability standard on the web, but neither one will sit well with many companies using the Contacts API. Facebook would rather have control over potentially sensitive information, and release it to select contractual partners, than start adopting Google’s open data portability standard. Google is sacrificing a level of openness to enforce open standards on other companies, but this is first and foremost a move on Facebook, and you can bet Facebook won’t take it lightly.

http://techcrunch.com/2010/11/04/facebook-google-contacts/

what will this mean for us people who import contact info from facebook
[EVO 4G General] Rydah:
I want to know what the fu(k this actually means. Since we can link Facebook contacts with our Google contacts. I hope this doesn't lead to Facebook leaving android.

Sent From My HTC Evo 4G Using Tapa Talk Pro!
[EVO 4G General] glennpettit:
google and facebook contact sync'ing

How does facebook allow you to collect contacts and save them off to say your PC.. sure you can sync your phone with limits but you are not able to say export them to Outlook.

If you I have been looking for the last few months.
[TG01 General] aliaslYn:
hey, on my tg01 i run the newest ROM original from Thosiba. i like to use twitter, like in the way its implementet in the Sense interface but just without sense :P

is there anything ?

merci
[Epic 4G General] 1deviant:
is the gtalk application in most roms here? Did NOT see it runnning stock. I need to have it and the Experience does which I am curently running with the Xtreme kernel. I would like to try the new Syndicate rom but do not know if gtalk will be there or not...
[G2 and Desire Z Q&A, Help & Troubleshooting] infinitron:
I just got off the phone with what seemed like a pretty knowledgeable rep and she said that tmobile will charge foreign data fees if you use wifi calling from another country. I asked how this was possible given that I would be connected to my hotel's wifi. She claims they look to see where the ip address is coming from. That sounds petty involved if you ask me, but not impossible. Does anyone know if this is true?
[G2 and Desire Z Q&A, Help & Troubleshooting] KShatzkes:
Thats odd, because I talked to a T-Mobile rep yesterday, and he said the exact opposite!

They really need to get this straight...
[G2 and Desire Z Q&A, Help & Troubleshooting] shinkinrui:
This stems from a misunderstanding a lot of reps(and even some supervisors) had from an internal communication earlier this year. Some customers had been able to make free international calls(dialing out TO a country besides the US) using UMA while roaming internationally. T-Mobile fixed the bug and sent out a communication that people could no longer make free INTERNATIONAL calls while connected to UMA while roaming internationally. Reps misread this as meaning that we would now be charging roaming even while on UMA/wifi calling and T-Mobile had devised some means for doing so. Not true- all it means is that while connected to UMA/wifi calling it's the same as if you're connected to the regular GSM network in the US. Regular calls to the US will be regular minutes and calls to any other country(even the one you're roaming in) results in international long distance charges. If baffles me that some reps still have this misunderstanding, because there's even a chart dealing with this issue on the internal website.

TL;DR: The rep you spoke to was confused. Don't worry, you can't be charged roaming while connected to UMA/wifi calling. Just remember it will be charged just like making a call from the US.