yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] alex1419:
i've installed rootexplorer but i can't find any .nv_data.bak and .nv_data.bak.md5 files. The efs folder is empty..what can i do? i can't use my phone.

i have to do this cause i installed the jpc firmware.
[Galaxy S I9000 Android Development] javahaxxor:
is it possible to use this firmware / CSC combo on the vibrant ?

Is it possible to use the XEE (nordic) CSC with other (stock or not) Vibrant firmwares ?

I have a Vibrant and trying to modify it so it has nordic locales (UI)
[Galaxy S I9000 Android Development] wacas:
good answer so maybe it is more then a mth away :confused:

just installed it quadrant score 905
[Galaxy S I9000 Android Development] Idan73:
it is also very plausible that some operators will choose to stay on eclair indefinitely
[Galaxy S I9000 Android Development] Kolemar:
Sweet! Thnx m8!

Finally some Danish swype for the peeps :D

Better try this one and see if it´s better than JM5.
[Galaxy S I9000 Android Development] Ferdimage:
any one thats flashed from M5 or older, please report on this M7 if its any good...

thanks
[Galaxy S I9000 Android Development] irenic:
guys,

i'm about to give this rom a try, eventhough i am quite satisfy with JPC on my device (except my product code has changed to KOR).

but i'm still not clear about this:

Requirements: Rooted phone, "Root Explorer" (or similar), .nv_data.bak and .nv_data.bak.md5 files (PRIOR the date of I9000XXJPC release)

i updated my SGS to JPC using KIES (test mode, regedit hack) and i never do any kind of backup for the nv_data file.. So where can I get those files now?

and right after flashing to JPC, i went into recovery mode.. there i wipe data, wipe cache and also format the internal sd card. will these delete the backup for nv_data that might be stored in the phone?

someone please help enlighten me!

thanks~
[Galaxy S I9000 Android Development] wacas:
so far i cant say it is better than jm6 but it has only been a cpl of hrs
[Galaxy S I9000 Android Development] plemen:
Installed this on a Bell GT-I9000m and it seems to have changed the model number to GT-I9000... the Bell root update.zip doesn't work but I can use the regular i9000 update.zip...

I've tried the *#272*????# and that just returns "rejected" - can't get to the list to pick the bell CSC... is there some other way of getting to it?

Overall it seems zippy - haven't had too much time to play with it yet... thanks.
[Galaxy S I9000 Android Development] cheetah2k:
I agree, however surely Samsung know how to fix the problems (especially lag) already.

1. Apply same method to fix lag as used in the Epic

2. Apply same method to fix GPS as used in the Epic

3. Enable JIT (FFS!)

:D
[Galaxy S I9000 Android Development] BakaSenpai:
So I did exactly what you said to do here...but the product code is still on KOR. My phone is flashed to JM7.

After rebooting, i saw that the new nv_data.bin and nv_data.bin.md5 files have been made...but it seems like the product code is still stuck as KOR..

Anything else I should do?

Edit: I have a feeling that there was no .nv_data.bak and .nv_data.bak.md5...hence why it's still stuck on KOR...
[Galaxy S I9000 Android Development] Henrik313:
My brandnew amazon I9000 have also from the beginning KOR instead of DBT...

ist not bad.
[Galaxy S I9000 Android Development] pharaohdk:
I´ve got a question, why do we need to tick the re-partition thing?

I´ve never done it any of my prior flashes, so whats the reason for doing it.
[Galaxy S I9000 Android Development] adz86:
same question for me
[Galaxy S I9000 Android Development] Ferdimage:
whats the deal with all the extra steps?? isnt this just a basic flash similar to older firmwares? use odin and load all three files for flash??
[Galaxy S I9000 Android Development] dagrim1:
How do I figure out what my product code is?
[Galaxy S I9000 Android Development] EarlZ:
+1 same question... is there any possibility for us end users to revert back to what our phones were ?
[Galaxy S I9000 Android Development] vnuh:
Yup, same question. :D
[Galaxy S I9000 Android Development] grelbar:
What do you mean no official word? Well unless the samsung uk twitter feed has been deemed unreliable, the official 2.2 update is coming at the end of September.

would post link, but.. look at google and samsungmobileuk's twitter feed.
[Galaxy S I9000 Android Development] m4ssnet:
Changelog from M6 ?

Any important different/improvements ? :confused:
[Galaxy S I9000 Android Development] irenic:
i guess.. the .nv_data is the automated backup file created by our phone..i just checked mine and the date is 18/8/2010.. while the nv_data is dated today..

so i guess if we delete the current nv_data, it will automatically create nv_data from the backup file that is prior to JPC..

others, please correct me if i'm wrong..
[Galaxy S I9000 Android Development] dakine:
Im in the Netherlands with an unlocked phone, what advantage is there to flashing a different CSC rather than just the CSC found in the 7zip package?

And I really wish that someone could just answer why repartition is preferable. In the past I've been told its a common way to brick a phone in odin.

And Richthofen, thanks for releasing this stuff! We're pretty lucky to have someone that goes through the trouble.
[Galaxy S I9000 Android Development] efimov oleg:
What changes in comparison with JM6?
[Galaxy S I9000 Android Development] mittu1:
Mobile AP not working

Can anyone help with the mobile AP which doesn't seem to be working when flashed with

GT-I9000_I9000XWJM7_I9000XXJM3_CODE-MODEM.rar

+

CSC_I9000OXAJM1.rar

The wireless network is seen by both my laptop and ipad, and you can connect to it, but it seems like there is no internet connection. Both the ipad and laptop get 169.X.X.X ip addresses. Not sure what's going on!!

Very important for me this works!
[Galaxy S I9000 Android Development] hacksome:
Quadrant: 917.

seems faster than JM6.

Temporary 'stalling' during application installation seems to have gone.

Protected apps still don't list in market
[Galaxy S I9000 Android Development] Roy Ngan:
Hi Richthofen,

I'm from Malaysia, hence OLB is my choice,

but after the command *#272*????# , there are few options availabe, like SIN, MM1 and etc (my default is SER), none of them i'm familiar with, may I know how do I know which CSC value shall I pick?

Thanks.

2nd question: I wasn't able to root XFJM6 with OLB combination, any other combination I can try?
[Galaxy S I9000 Android Development] whepper:
I did the .nv_data.bak and .nv_data.bak.md5 files rename trick by hand (that you mentioned in another thread when you just found out the productcode issue), so following your theory they are not signed now. I do not have any issues with my phone (old productcode shows up correct in Kies and IMEI showing up ok).

Do I need to follow any other step to get back to the original state? So renaming my nv_data files to bak and see if the phone corrects them after a reboot or leave them untouched? I'm on JM6.

Your advise would be very valuable!
[Galaxy S I9000 Android Development] hacksome:
Quadrant 1697 after Supercurio's Voodoo Lagfix. Zippy!

Everything (especially Market ) loads so fast after the EXT4 fix. Thank you Supercurio.
[Galaxy S I9000 Android Development] Phk:
917?

Man... I get 2300 in Quadrant and 9 in Linpack using only JM5+OneClickLagFix+HackEclair.

Believe me: It's fast, and non-laggy. The only bug is Bluetooth new stack not working with some devices..
[Galaxy S I9000 Android Development] hacksome:
JM7 + supercurio's EXT4 LagFix yields the best performance for me yet.

Quadrant is perhaps unreal. It is just a nerd fix ;) Ryanza is working on a real 'benchmark'.
[Galaxy S I9000 Android Development] Phk:
Yeah i'm really trustful on Ryanza's work, i think the guy rocks this Galaxy S s**t. Let's wait and see.

How about Linpack?

_____________________________

Facts:

My Galaxy S with HackEclair-JM5+1ClickLagFix:

Quadrant: 2300

Linpack 9

Some guy's Galaxy S with Doc's RomMod Froyo JPC:

Quadrant: 1800 (i think)

Linpack 14

This JM7:

Quadrant: 1800 (after Supercurious LagFix)

Linpack: __?__ (please someone give us this value hehe)

_____________________________

Cheers,

Phk
[Galaxy S I9000 Android Development] hacksome:
Just did a 'realworld' test of GPS by tracking with 'my tracks'. It showed my walking path more accurately than any other firmwares yet.
[Galaxy S I9000 Android Development] hacksome:
Linpack: 8.2
[Galaxy S I9000 Android Development] Phk:
Which ones have u tried?
[Galaxy S I9000 Android Development] bartek46op:
Faster than JM1 rev 3? (with lagfix)

GPS?
[Galaxy S I9000 Android Development] ebbhead:
Does that mean that it is good, or just better than crap? ;)
[Galaxy S I9000 Android Development] Richthofen:
If there is no problems (product code unchanged, IMEI ok, phone unblocked etc), the is no need to play around with nv_data files.

I´ll explain what will happen when you update to I9000XXJPC firmware:

Let´s say we have a brand new phone.

The phone was sold in Germany and it has I9000XXJF3/I9000DBTJF3/I9000XXJF3 firmware inside it. The product code stored inside the phones nv_data.bin file is GT-I9000HKDDBT, which indicates German market. The phone does not have .nv_data.bak & .nv_data.bak.md5 files (only "current" nv_data.bin & nv_data.bin.md5), yet.

We will update the phone with newest official Eclair 2.1 release, lets say I9000XWJM2 firmware. Once we check the EFS folder on the phone, we can see two new files .nv_data.bak & .nv_data.bak.md5. They have last modification date of ... (old, the date the phone was made). The current nv_data.bin and nv_data.bin.md5 files will have a current last modification date (the date when the firmware was changed = today).

Now we will open (the current) nv_data.bin file with a hex editor and see the product code section: it is in the original state: GT-I9000HKDDBT.

Every time the phone firmware is being changed, the nv_data.bin and nv_data.bin.md5 files are being rewritten / resigned, no matter which firmware version you will use (even Eclair). Pre I9000XXJPC builds just don´t touch your product code, etc.

The original nv_data.bin and nv_data.bin.md5 files are renamed to .nv_data.bak & .nv_data.bak.md5 and new data will be created based on them.

So:

Our example phone in a "virgin" condition:

Original firmware (I9000XXJF3 -> I9000XWJM2) update:

nv_data.bin & nv_data.bin.md5 renamed to nv_data.bak & nv_data.bak.md5

Once the phone boots after the update, the missing nv_data.bin & nv_data.bin.md5 files will be calculated automatically based on nv_data.bak & nv_data.bak.md5 files.

New firmware (I9000XWJM2 -> I9000XXJPC) update:

nv_data.bin & nv_data.bin.md5 renamed to nv_data.bak & nv_data.bak.md5 (any excisting nv_data.bak & nv_data.bak.md5 will be overwritten).

Once the phone boots after the update, the missing nv_data.bin & nv_data.bin.md5 files will be calculated automatically based on nv_data.bak & nv_data.bak.md5 files and the product code will be changed to KOR

This is the last chance to save the original product code.

Because if you update or downgrade to any firmware version the nv_data.bin and nv_data.bin.md5 files (which now contains the modified product code of KOR, by I9000XXJPC) will be rename to nv_data.bak and nv_data.bak.md5 and your original one (with original product code) will be overwritten.

So if your nv_data.bak and nv_data.bak.md5 files have earlier last modification date than 08/30/2010 (the date when I9000XXJPC was available) they will contain your original product code. So they are good.

If they are 08/30/2010 or later, they already have the new modified KOR product code (by I9000XXJPC).
[Galaxy S I9000 Android Development] xarxiusxiii:
I upgraded to JPC, then down to JM1 and again to JF3 (the latter two via Odin), and then replaced the nv_data.bin with the .bak ones, and my product code has changed back from KOR to ORA, and everything looks to be fine... Or maybe I've just misunderstood what you've said :P
[Galaxy S I9000 Android Development] hacksome:
@Richthofen Is JM7 newer than HVJH1?
[Galaxy S I9000 Android Development] Trollitito:
Galaxy S JM7:

Quadrant: 895

Linpack: 8.2

Galaxy S JM7+1ClickLagFix:

Quadrant: 2034

Linpack: 8.1

Well, by this scores, i think it's not much better, with JM5 i had better ones. After JM5, i have JPC but as i have some lags even after lagfix (of course, with a data/factory reset), i decided to put JM7 to see how would it be. Besides the results of benchmarks, i think it's pretty smooth so far.
[Galaxy S I9000 Android Development] He4dShOt:
Linpack ~8 and quadrant 897 here...
[Galaxy S I9000 Android Development] dutchcow:
I downgraded from JPC using the steps provided and it went flawlessly. I had problems with my SIM card not getting on any network, or only getting on for a few seconds. This was caused by me renaming files instead or deleting them and let the phone restore the backups itself.

Great advice, this ROM seems good, only had a 2-3% battery drain overnight, with wifi enabled. Compared to JM1 (new) and JM5/JM6 I dont see/feel much difference though.

The product code is located in /efs/imei some text file had KOR inside, which I changed to my letter code, rebooted the phone, did the CSC selection thing, phone rebooted (and seemingly factory reset itself) and all is good now.
[Galaxy S I9000 Android Development] °Dexter°:
I didn't lose any of my apps using first post method for flash,is that right?
[Galaxy S I9000 Android Development] Aweb:
You really should not rely on quadrant scores especially with lagfix installed (supercurio said it was a sync problem), they are quite wrong.

For instance I had 2200 with RyanZA's One click lag fix, I have now 1733 with supercurio's fix and it is frakly a much more smooth experience, no more lag when installing apps on market etc..
[Galaxy S I9000 Android Development] Trollitito:
But besides the scores, which difference are between RyanZA's lag fix and supercurio's fix? Is one of them much better than other or are both quite the same?
[Galaxy S I9000 Android Development] vnuh:
AP app

Hi guys, I couldn't find AP app with JM7, I'm using CSC OLB for Asia. Does this matter?

I really need to have AP app, is there anyway that I can install it ?

Thanks a bunch.
[Galaxy S I9000 Android Development] no.one.writeme:
Can you please point me to the link o supercurio's EXT4 LagFix, I've been searching like mad but i am unable to find it. Thanks!
[Galaxy S I9000 Android Development] trenje:
It's not public, yet.
[Galaxy S I9000 Android Development] ebbhead:
If you are referring to the phone acting as a WiFi access point, it's under settings -> Mobile AP -> and a checkbox at the top.

Just tried it and it works flawlessly.
[Galaxy S I9000 Android Development] OrionBG:
One Question!

When I go to the Multi CSC menu, there are many three letter options! which one is for which operator??? Specifically which one is for Bulgaria?
[Galaxy S I9000 Android Development] cheetah2k:
I'm actually pretty happy with JM7. I installed mine with the Optus CSC and its smooth for the time being with out any lag fixes.

One thing I have noticed is that Market is quick. All other FW's have been slow at loading the artwork for each app. This one loads them real quick.
[Galaxy S I9000 Android Development] yc1437:
The official csc for maxis is XME, which not appears in OLB unless you are digi DGI or celcom CCM. But you can always extract XME files fr JF4 installed phone the use root explorer to inject the XME folder extracted fr system...csc....xme and copy to your phone install with JM rom, then use the chg sales code *#*#273*hhmm# to install xme csc
[Galaxy S I9000 Android Development] vnuh:
Thanks dude, can't believe I missed its location.
[Galaxy S I9000 Android Development] Ferdimage:
did you guys flash the M7 via odin normal way, load three files and pit & re-partition then flash?
[Galaxy S I9000 Android Development] yc1437:
Hi off topic a bit the number above referring to mflops?
[Galaxy S I9000 Android Development] hacksome:
GPS on this is more accurate than HVJH1.
[Galaxy S I9000 Android Development] vgpbms77:
@ Richthofen,

is it possible to upload the XXJM4 modem file? I know that it hasn't major changes except some names, but it would be nice if we had its latest version!

Thank you in advance! And also many many thanks for the good work!:)
[Galaxy S I9000 Android Development] nickporwal:
Any changes from JM6? is it worth to upgrade from JM6?
[Galaxy S I9000 Android Development] bucklino:
What about root? Someone did get it? I noticed that some people didn't get root on JM6......

Guys, are you flashing as the first post or the old way, by Odin?

Thanks ...and thanks a lot to Richthofen.
[Galaxy S I9000 Android Development] dutchcow:
I got root easily. Just use the update.zip method.
[Galaxy S I9000 Android Development] Phk:
@Richthofen Many many thanks for your time.. Explanations like this avoid having to explain it all over and over again. I think you just need to leave one last line saying "so if you have these files backed up at your PC, you will always be able to restore your product code, following these steps:"

That would be just it :)

@Trollitito Thanks :)

@He4dShOt Thanks too :)

Phk
[Galaxy S I9000 Android Development] Aweb:
Frankly the difference is really impressive. RyanZA's lagfix was still using part of RFS (which forbids reading files while writing to the internal sd card from what I understood) while supercurio's is using ext4.

For instance there are no more hangs while downloading/installing from the market of Samsung apps.
[Galaxy S I9000 Android Development] bucklino:
Thanks!.

And it may be the update.zip (file) from thread on xda forum ?

What are you thinking of JM7 rom so far?
[Galaxy S I9000 Android Development] Roy Ngan:
GPS Test on XWJM7,

now, who wanna tell me SGS got GPS issue??

My Test,

On to of that, I can get 10 in view, 10 in use constantly

and 11 in view, 10 in use most of the time.
[Galaxy S I9000 Android Development] DavidX_07:
Any chanse to update first post with changelog and some screeny ?
[Galaxy S I9000 Android Development] nonreviad:
I'm not sure that's the case, since I managed to restore my product code after reflashing TWICE after JPC. The .nv_data.bin and .nv_data.md5 files still contained the original product code. I have not yet tried upgrading again using Odin.

Maybe just Kies is the one that does the whole changing nv_data* files to nv_data*.bak files, while Odin just leaves the /efs folder alone?
[Galaxy S I9000 Android Development] nlpz:
Can this be done on rooted JPC?
[Galaxy S I9000 Android Development] whepper:
Thanks, Richthofen.

Because I renamed the files after flashing to JM6, I decided to rename them back to the .bak versions (after backing up), deleted the originals and rebooted. And you're right! Their are regenerated from the .bak versions. Thanks for your explanation. Very helpful! :D
[Galaxy S I9000 Android Development] kalpik:
So.. JM7 better than HVJH1?
[Galaxy S I9000 Android Development] Fornowagain:
Flashed JPC twice now and mine is still on the original O2U code. I've backup the nv_data files. The .nv_data are still dated 8/20/2010, the new nv_data ones are todays 9/1/2010, Looking at the nv_data.bin line of code its still "MP 0.800 XEU GT-I9000HKDO2U"
[Galaxy S I9000 Android Development] BronzedDroid:
This has been possible for a while. What matters is how it works during driving or walking.

In response to Roy Ngan with his screen shot of 12 satellites in view, 11 in use.
[Galaxy S I9000 Android Development] pharaohdk:
someone please answer.

why must we check re-partition when flashing this?

I´ve never checked re-partition befor, so whats the reason for doing it now
[Galaxy S I9000 Android Development] yc1437:
Still cannot conclude yet, are the satellite signal bars stand still or up down like the audio equalizer? The most important thing is the satellites locking must be persistent & consistent. U can compare the signal bar of bluetooth external gps using bluetooth gps fr market vs the JM7. If the JM7 give a very stable satellite lock signal, no jumping here & there then can conclude that samsung solve the gps issue
[Galaxy S I9000 Android Development] Roy Ngan:
Notice the big number 45? That's my speed, I was travelling in 45mph in my car while capture this.

Too my surprise, while I'm station, I can only get 10 in view, 10 in use most of the time, nothing more than that.
[Galaxy S I9000 Android Development] whepper:
CSC for the Netherlands (XEN)

Does anybody have an unbranded CSC for the Netherlands (XEN)? Or know how to find one?
[Galaxy S I9000 Android Development] Roy Ngan:
You are right, it's jumping. Does other phone don't have this issue? I hope N1 or Motorola Droid user can share with us their experience.
[Galaxy S I9000 Android Development] jcdusse1981:
I've got the Freeze bug on first boot : what can i do ? I've tried to reflash JM7 but always Freeze bug. Is there a solution or must i flash an older firmware ?
[Galaxy S I9000 Android Development] laggedHero:
:/

About the JM7.

It's worth updating from JM5? I think the greater gain here is supercurio's lagfix, isn't?
[Galaxy S I9000 Android Development] Roy Ngan:
But in the earlier complain is that the number of satellite locked never go beyond 6.

I need to capture a video then. Or is there any software allure video capture on Android phone?
[Galaxy S I9000 Android Development] funk0014:
Netherlands CSC

I need one too!
[Galaxy S I9000 Android Development] windy31:
My efs folder is empty when I check in with Estrong file manager.

Now I'm still in JPC firmware. What should i do to get my product code back?
[Galaxy S I9000 Android Development] tomdot:
update.zip Root method doesn't work for me in JM7.

I downgraded from JPC
[Galaxy S I9000 Android Development] LeDiable:
What version to use for a phone purchased in India?
[Galaxy S I9000 Android Development] carlocb:
THANKS A LOT MAN!! :D

I followed the procedure you told in first post to downgrade from jpc.

Now it seems EVERYTHING IS WORKING FINE!! :D

I got italian product code and all...THANKS! :D
[Galaxy S I9000 Android Development] Roy Ngan:
Linpack results
[Galaxy S I9000 Android Development] Roy Ngan:
Linpack result
[Galaxy S I9000 Android Development] Roy Ngan:
Quadrant result after OCLF v1
[Galaxy S I9000 Android Development] plemen:
Anybody else try this with Bell i9000m? It's working well except I can't get into the menu to change the CSC using *#272*????# - I keep getting the "Rejected" message...

Is there another way to do this? Also, the update.zip for root isn't working for me...

Thanks.

Edit: the *#272*????# worked after the 23rd attempt :) !!

Edit 2: Root works as well.
[Galaxy S I9000 Android Development] likingandroid:
Will this work with the T-Mobile's Samsung Vibrant? If so what files should I select?

Any assistance is appreciated.
[Galaxy S I9000 Android Development] pramods:
Can you please post the ODD CSC to be used with India, this was there in DDJG4 the latest firmware available on kies.

-Pramod
[Galaxy S I9000 Android Development] ebbhead:
Just did a real life test. Phone lying with clear sky visibility on the dashboard while driving and the result is crappy. According to myTracks I've been driving through buildings and on the opposite side of the freeway...

I've done the same test with my HTC Hero, and the result was perfect, you could even see where I had changed lanes.

Here's todays test if anyone is interested:

My track at googlemaps
[Galaxy S I9000 Android Development] kalpik:
No verdict yet on HVJH1 vs XWJM7? :(
[Galaxy S I9000 Android Development] Koenig77:
Where can I find this Ext4-fix?
[Galaxy S I9000 Android Development] Ferdimage:
isnt it just the same as Minco EXT4 Lag Fix?
[Galaxy S I9000 Android Development] Bynar010:
Which means jack all if it still can't track you properly! Proof of NOTHING. I can get a lock on more than eight satellites but its still inaccurate.
[Galaxy S I9000 Android Development] Koenig77:
I have no idea, the only time I've heard about it is in this thread, and I would like some more info on this since it uses Ext4.
[Galaxy S I9000 Android Development] grim201:
can somebody help me to find CSC I9000OXXJF5 ?

i posted here because i did't want to open o new thread.
[Galaxy S I9000 Android Development] LeDiable:
delete*

10 chars.