yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] Avataar120:
Many thanks Guy !
[Galaxy S I9000 Android Development] Idan73:
for the stock tried jg8 and jh2 with 512 pit
[Galaxy S I9000 Android Development] Electroz:
and you are clicking on "repartition" in odin right?
[Galaxy S I9000 Android Development] Idan73:
yes and it shows success at the end and everything but....
[Galaxy S I9000 Android Development] Electroz:
Well, I'm out of ideas. Sorry.

Try flashing on another USB port? or another computer maybe?
[Galaxy S I9000 Android Development] cosmic76:
Hi , can I update from jp3 modaco to jpc version? jpc is an update for jp3 or not? Tks
[Galaxy S I9000 Android Development] jimsey:
unfortunately it's bricked if you have a bad flash and no 3 button recovery mode... i'm taking mine back to T-mobile shop today after hours of trying to get it into recovery or download mode after a bad flash last night... button combinations dont do anything and no success with adb!

i think i had left an update.zip on the internal SD, I should have known better, but it might be worth advising against this in the first post?
[Galaxy S I9000 Android Development] psmorgan:
Hi,

I've managed to get the sim unlock code to disappear but it refuses to connect to the network properly.

I'm on Orange, UK.

I've copied the whole efs folder to my sdcard and i've looked at both of the nv_data.bin and nv_data.jpc files I have - they are exactly the same in terms of md5 hashes.

The product code when I view them in a hex editor says 'Not Available'.

Is there any way to restore the nv_data.bin back to original?
[Galaxy S I9000 Android Development] Heroic_Kaizer:
I am just gonna take it to a local phone repair place to see if they can fix it. I tried taking it back to Telephone booth where i got the phone and they wont exchange it for me because when they ask me for a bell # i was like..i dont hv one so they knew i tampered with the phone.

I am gonna leave it charging overnight and see if it will just die itself out and fix itself. its black screen right now with the 2 bottom touch buttons lid up all the time and vibrating once in a while.
[Galaxy S I9000 Android Development] EarlZ:
The Root Package comes with Odin 3 v1.3v and it seems to work better on my PC/Device can this be used to flash any other firmware or just specific to the rooting process for JPC ?

EDIT:

Should I also update busy box and the SU apk ?
[Galaxy S I9000 Android Development] Henrik313:
I have successful rootet my phone.

which speedfix could I use?

thank you:)
[Galaxy S I9000 Android Development] EarlZ:
Isnt it a little to risky to use speedfixes for this firmware I mean its just been relaesed
[Galaxy S I9000 Android Development] Henrik313:
I dont think so. Its also risky to flash this unoffical beta ^^
[Galaxy S I9000 Android Development] whippie:
Excellent flashed with Odin V1.0 from JM6 with s1_odin_20100512.pit flash first methode.... Rooted using odin kernals and lagfix score 1800 ext2..

KIES WAY NO THANKS<<<

Cheers for a brilliant guide :)
[Galaxy S I9000 Android Development] cheetah2k:
Mate, I got the same thing. No JPC, only JM1 :mad:
[Galaxy S I9000 Android Development] adirtymonkey:
Did you change the registry settings when connected to Kies ?
[Galaxy S I9000 Android Development] Aery:
For Root and Lagfix see first Post. There are all Infos you need!
[Galaxy S I9000 Android Development] hacksome:
Too tempted to flash JPC using Odin because I don't use Kies. I have a backup of my IMEI. Will it be safer to flash using Odin now?
[Galaxy S I9000 Android Development] speedofheat:
Thanks for the awesome OP. Followed your instructions and now I have a functional, rooted SGS running FROYO :D
[Galaxy S I9000 Android Development] moosamm:
Same here :(
[Galaxy S I9000 Android Development] tetz79:
same here

tried reinstalling kies, cleaning registry..

only JM1 versione prompted.

:(
[Galaxy S I9000 Android Development] yuliusaje:
is there any way to use ad hoc in jpc??
[Galaxy S I9000 Android Development] GregerW:
I got the same thing, i have changed registry .
[Galaxy S I9000 Android Development] Alberto96:
no jpc , only jm1

i have do a factory reset and a cache wipe before trying kies and...... it shows only jm1 . i have uninstalled all my programs !!!!!!!!!!!!!!!!!!!!!!! :eek: :eek: :eek: :eek:

what can i do?
[Galaxy S I9000 Android Development] Aery:
Did you press CTRL+ALT+U+P at Firmware Update Window in Kies to activate Test Mode???
[Galaxy S I9000 Android Development] cheetah2k:
YES!

My phone is currently on JM6

I did the tutorial exactly as stated - and can only flash JM1.....

Do we need to have an authentic legit FW on the phone to flash to JPC??
[Galaxy S I9000 Android Development] tetz79:
tried exactly many times

TEST MODE

REGISTRY EDITOR

nothing changed, showing only JM1

info : I'm on JM5, Italian Samsung Galaxy S
[Galaxy S I9000 Android Development] miker33:
Same here, tried test mode enabled, test mode disabled.

Registry changed as per instruction, still says JM1 only as option to upgrade to.

Phone is currently on JM1 firmware via kies test mode.

Kies latest updated version.
[Galaxy S I9000 Android Development] lucasjohny:
no luck now kies only offer me jm1 after the reg edit, i think samsung had block it. Hope someone can dump it.
[Galaxy S I9000 Android Development] moosamm:
I guess its gone for now :eek::eek:

Is flashing via Odin a safe option?
[Galaxy S I9000 Android Development] newtonthecat:
Same question for me - after seeing MrArkhanist's video I am compelled to upgrade to JPC now.

Where is the JPC ROM? It's not on Samsung Firmwares.

Mark.
[Galaxy S I9000 Android Development] moosamm:
Its in the OP: http://www.multiupload.com/LVY75LHMNT

But there are potential downsides described in the first post.
[Galaxy S I9000 Android Development] adi_g_s:
Hi, I upgraded to JPC by Kies registry mod, but now the phone asks for Network Unlock Code.

Phone rooted, followed instruction on FAQ for restoring the product code, (B case, .nv_data.bin), reboot, phone still asks for Code.

When viewing the nv_data.bin by Hex editor it shows now the correct Product code MP 0.800 ÿKOR GT-I9000HKDORO, but still phone asks for Code.

Generated Unlock Code is 00000000 but it doesn't work

What else to do?

Maybe flash by Odin to previous JM6?

Funny is that i can receive calls but cannot initiate.
[Galaxy S I9000 Android Development] He4dShOt:
Potential?
[Galaxy S I9000 Android Development] newtonthecat:
Thanks. I will have to think about it some more!
[Galaxy S I9000 Android Development] SS2006:
The way I see it, sure itll change your product code, not let you update thru keis enymore and so on

but think to the future when the official froyo is out, dont you think itll be alll over this forum for download, and in a ODIN format so you can just flash it. ALso by then there'll probably be CyanogenMod, I mean if your flashing and doing this stuff now, it means you can do it again when the official is out.

I didn't think twice about flashing this personally, and I'm very happy with it, it seems final to me.
[Galaxy S I9000 Android Development] Quiksilver78:
Is there a "more elegant" way of rooting the JPC firmware?

I know I took a huge risk by upgrading to JPC but the whole thing about flashing and reflashing using Odin and the update.zip seems overkill.

:)
[Galaxy S I9000 Android Development] SS2006:
Does anyone know if the JIT compiler is working in this, if it is, with the lagfix the quadrant score should reach an unseen figure..
[Galaxy S I9000 Android Development] SS2006:
LOL I agree,

would the RyanZA Lagfix app work, it has a root funciton in it
[Galaxy S I9000 Android Development] _dsk_:
Linpack seems to hit around 13 to 14 for people and quadrant without the lag fix is in the 900 to 1000 region.
[Galaxy S I9000 Android Development] EarlZ:
Since my unit is now asking for an UNLOCK code, I tried the steps posted on the first page after rebooting it still asks for an unlock code.. since it is moving the back-ups to a new location am I screwed till I get the same copy from a unit that came from the same operator ? Coz i can recieve SMS but cant send any and i get the simcard error icon =(

I redid the moving of the files and Im now its not asking for any lock codes what so ever, i hope 3G internet works on this also..
[Galaxy S I9000 Android Development] aatjitra:
This morning I was still able to get JPC...

What I did is:

1. Detect the available version: JM1

2. Click Upgrade until the second steps (phone info)

3. Press the CTRL+ALT+U+P

4. Back a few times until the Firmware Upgrade windows closed.

5. Click the Firmware Upgrade and press the CTRL+ALT+U+P

and now KIES detected the available firmware as JPC...

Not really sure about the correct sequence of the steps but it works...

Anyone knows how to dump the firmware using Odin ?
[Galaxy S I9000 Android Development] n1ck2010:
Thought id share what things dont seem to be working for me.

Messaging (SMS) - Forces Quit when trying to read any msgs. Have tried clearing cache and data but app stills forces quit. Had to install Handcent which works fine.

Email (Exchange) - No longer works, will not connect to any Exchange servers and mailbox just stays empty. Have tried K9 mail but this still will not connect to exchange.

If any one has any solutions that would be great.

Thanks for all your hard work in getting this release working guys, its def the most stable of the pre-release firmwares since JG5.
[Galaxy S I9000 Android Development] funk0014:
Exchange is working for me! I think you have to do a factory reset!
[Galaxy S I9000 Android Development] Fatherboard:
Since it's no longer possible to update to JPC through KIES, it would be nice to have the subject changed.
[Galaxy S I9000 Android Development] rdy2go:
You have to enable TEST MODE
[Galaxy S I9000 Android Development] He4dShOt:
Are you messing with us? :confused:
[Galaxy S I9000 Android Development] xarxiusxiii:
I second this, I'm now updating to JM1 via Kies, it's the only available update...

I don't think I'm going to risk JPC again, I'll just wait a few weeks for the actual official Froyo update... From what I did test out (which wasn't a lot I admit), JPC does look like a good ROM. However, I'm against rooting just to be able to use my phone...
[Galaxy S I9000 Android Development] rdy2go:
I used to have "No connection to server" for couple of hours but... suddenly in the morning it worked - servers are too busy to handle all the traffic...
[Galaxy S I9000 Android Development] xarxiusxiii:
The update just isn't there for me, and yes, I do have test mode enabled...
[Galaxy S I9000 Android Development] kgk888:
Which were then refuted by that same poster just a few minutes later after confirming you can self edit that data.

The OP just never updated it to reflect that. Search the thread.
[Galaxy S I9000 Android Development] newtonthecat:
CONSPIRACY THEORY No.1: They were about to release Froyo RC1 into Kies (JPD) and accidentally released JPC instead. They ran around the office shouting and pointing fingers then some bright spark took it offline. In doing so he messed up the server. So now they are rebuilding the server ready to release JPD, or JPE or whatever! ;)
[Galaxy S I9000 Android Development] n1ck2010:
Is that the reboot into recovery way or the through the android menu options in the os?
[Galaxy S I9000 Android Development] rdy2go:
It seems I was one of the last few to upgrade using KIES... (2010-08-31 07:30 CET)

Yesterday, all the attempts were refused "No connection to server" etc.
[Galaxy S I9000 Android Development] xarxiusxiii:
Well I'm just happy to be on JM1 with a fully functioning phone, and very thankful that Aery found a fix for the SIM lock problem :)
[Galaxy S I9000 Android Development] SS2006:
I cant anymore either, I did it using ODIN

Its WAY easier, and faster, and I think has a less chance of screwing up, since KIES is a USB connection disaster IMO

Just flash it, first page, amazing ROM
[Galaxy S I9000 Android Development] whippie:
I flashed with Odin working fine brilliant update worth the effort...
[Galaxy S I9000 Android Development] newtonthecat:
When you flash using Kies it keeps all your apps and settings. Is that possible using Odin?

Sorry, I'm a bit of a newbie and I've only flashed a couple of times using Odin following the basic tutorial and when I did that I had a factory resetted phone and had to re-install and re-configure all my stuff.

oh, what's this abot the /efs folder? Should I root, install root explorer and backup that folder before flashing? Why do I need to do this?

Mark.
[Galaxy S I9000 Android Development] kgk888:
Going to quote these for emphasis. Kies is an abortion. Just flash with ODIN and avoid the headache and crapware installation on your computer. The only people that should touch Kies with a ten foot pole are people who have locked phones.

If you're flashing this ROM onto a Vibrant/Captivate/etc, i.e. the carrier specific versions of the i9000, just stop. This is meant for the Galaxy S, so if you brick it because you're in the wrong forum you have only yourself to blame. If you have a Galaxy S that is net-locked because you bought a contract phone, don't act surprised if issues pop up.

Normal, unlocked Galaxy S phones can flash this via ODIN 1.3 just fine. Follow the rooting instructions that come with the ODIN 1.3 download. Then apply lag fix. Voila.
[Galaxy S I9000 Android Development] irkkso:
for PHONE DOESNT SUPPORT 3-BUTTON RECOVERY/DOWNLOAD-MODE
[Galaxy S I9000 Android Development] newtonthecat:
I just read this on http://twitter.com/SamFirmware

"Do not flash your phone to xxjpc problems with bootloader! Just WAIT." (2 hours ago)

and

"We don't release I9000XXJPC because flash trouble with Odin Just wait for couple more days. :)" (19 hours ago)

I think I'll wait a couple more days!
[Galaxy S I9000 Android Development] newtonthecat:
erm, I've looked on samsung firmwares and in the stickies but where is Odin 1.3 I can only find links to V3 1.0

Feel free to shoot me down in flames if it's really obvious and I am just being dumb!
[Galaxy S I9000 Android Development] Thread Astaire:
Ooops. too late.
[Galaxy S I9000 Android Development] cheetah2k:
No **** sherlock
[Galaxy S I9000 Android Development] Aery:
While this is for most Users a Upgrade from 2.1 to 2.2, please do a factory reset. There are so much problems if you do not!

2.1 Data is not fully compatible with 2.2.

Dont use Titanium Backup or similar Apps to restore your Data!
[Galaxy S I9000 Android Development] dereknas:
JPC FIRMWARE FOR FLASHING WITH ODIN:

http://www.multiupload.com/LVY75LHMNT

Thanks to Richthofen!

Howto from the sticky BIG FAQ Thread:

- Make sure your Phone is fully charged!

- Open ODIN. (And close Kies, if you have it open. It is important to have ODIN open BEFORE connection the phone via USB!)

- Select the PDA/Modem/CSC/.PIT files in Odin. (.PIT and PDA are required. CSC and Modem are HIGHLY recommended. They may be necessary depending on the PDA! Try flashing all three BEFORE reporting bugs, if you only used one initially!)

- Remove the SD card and SIM card from the phone.

- Turn the phone into the download mode by pressing and holding VolumeDown+Home+Power.

- Connect your phone with your computer and wait until the drivers are installed.

- If the drivers are installed, click Start.

- The phone will be flashed and once it’s finished, it will boot up. (Do NOT disconnect the usb-cable, remove the battery or otherwise interrupt this process!)

- You have successfully flashed your phone.

- Do a Data/Factory Reset

For the step above flashing through ODIN, do we need to select re-partition?
[Galaxy S I9000 Android Development] bucklino:
Idem here......Anyone???

i wanna flash JPC with Odin.....but i only have Odin V3 1.0........where do I find Odin 1.3 for download?

Which pit should i use?? Regular 512.pit??

Thanks.
[Galaxy S I9000 Android Development] veescript:
I flashed with Online 1.0 with 512 PIT. All gone well.
[Galaxy S I9000 Android Development] rpritch:
How did you flash this file...I dont see a PDA, CSC, PHONE file. Did you use ODIN?
[Galaxy S I9000 Android Development] Mr2311:
Hi,

i can't find this 2 files on my galaxy s?
[Galaxy S I9000 Android Development] LuffarJoh:
I checked the register and found out that my ProductCode had changed to GT-I9000HKDKOR. I did as mentioned:

After doing this Kies cannot connect to my phone. I reverted the procedure and now it connects without any problems, but now I have GT-I9000HKDKOR as ProductCode again.

Have anybody else had this issue?

Is it even necessary to do this? I still can get JM1 update if I do the reg hack.
[Galaxy S I9000 Android Development] stepping:
Ever tried to delete the complete Samsung-Entry in regedit and restart Kies again, that the Produktcode is listed under Nr.1?
[Galaxy S I9000 Android Development] kgk888:
Not being dumb at all. It's included with the JPC Kernal Root 7zip file but no one has posted updates to the stickies for it I guess. So it's kind of hidden until you open up the JPC Kernel Root folder. I used it to flash the phone to JPC before the root just to be safe since the JPC root is bundled with it.

Lemme grab a link, just a sec.

http://www.multiupload.com/GJEZ1OT9NN

That is for the JPC Kernel Root fix. Within that folder when you unzip it, in addition to the rooting files/readme is Odin v1.3 It's from the HK firmware release that was posted a few days ago.

I used that ODIN when flashing the files in this:

http://www.multiupload.com/LVY75LHMNT

Just use the regular 512.pit that you use for all the other firmwares. Doesn't need to be any special version or anything.

I'm assuming you have an unlocked (non-carrier locked) i9000. I cannot recommend flashing this firmware for people who have netlocked phones or the bizarro Canada version. People with the bipolar US market phones (Captivate, Vibrant, Epic, etc) shouldn't touch this unless you're a dev and know what you're doing.

The process I followed (I had Samset 1.9 with lag fix prior to this) was the following:

1.) Flash the phone back to a stock ROM (I went to JM1rev3)

2.) Clear cache/factory reset from recovery.

3.) Flash to JPC using ODINv1.3

4.) Root using instructions provided by Readme in the JPC Kernel Root folder

5.) Apply RyanZA's OneClick LagFix 2-3 as normal

Runs perfectly fine for me. Aside from the minor common bugs (Swype auto-capitalizing the second word in an initial sentence in a text field within the browser) I have no major issues to report.

Follow the Bug/Issue thread for JPC that was started if you have other questions.
[Galaxy S I9000 Android Development] richardbroder:
Same thing over here. Update went perfect. Then the phone wouldn´t boot, did the data wipe and it booted, and ALL programs crash, the phone is trhased. Gonna have to try it through Odin...
[Galaxy S I9000 Android Development] LuffarJoh:
I deleted all devices, maye I should delete the whole samsung Kies entry?
[Galaxy S I9000 Android Development] Electroz:
Just load the included TAR file in the PDA section of odin, click repartition, set the 512 pit and flash away.
[Galaxy S I9000 Android Development] bajica:
Everyone should stay away from JPC build, it has bootloader problems that can brick your phone, besides we are getting NEW FROYO build THIS WEEK, why take the risk, just wait for couple more days. :)
[Galaxy S I9000 Android Development] He4dShOt:
This week??
[Galaxy S I9000 Android Development] mickeko:
Didn't that particular feature also modify IMEI for some people? Seems risky if that's the case.

Sent from my personal Dis-organizer GT-I9000
[Galaxy S I9000 Android Development] chocoboyo:
First of all thanks for the tutorial.

I'm with this problem,th device ask me for a network code.

How must be the telephone connected to the computer for do this step? (Download mode, restore mode...)

Thanks!
[Galaxy S I9000 Android Development] stepping:
Never read that somebody used this method before and his IMEI has changed. Can you give me a link?
[Galaxy S I9000 Android Development] Greg82uk:
re: rooting JPC...

Just installed JPC and have now rooted... recently I noticed that you don't need to rip out the battery... personally I've always thought that seemed a bit barbaric... if you push and hold the power button for about 10 seconds then the phone will turn off... no need to yank the batt!
[Galaxy S I9000 Android Development] grim201:
I tried this method. it doesn't work.

my imei is the same after the operation.
[Galaxy S I9000 Android Development] Heroic_Kaizer:
I just took my bricked phone into a local cellphone repair shop. Hopefully they have the tools we dont have to start up my phone again.
[Galaxy S I9000 Android Development] stepping:
Your IMEI should be the same. Did your ProduktCode changed? This is important.
[Galaxy S I9000 Android Development] bajica:
So i hear, besides there is like a 10 things to do after u flash JPC to FIX everything, and its not worth the trouble and risk. I will stay with JM6 for now.
[Galaxy S I9000 Android Development] streakpt:
Check my guide on how to get the codes on JPC. Hope it works for you.
[Galaxy S I9000 Android Development] grim201:
in the registry the productcode entry now is GT-I9000HKDORO. but my phone still askes for network sim unlock code.
[Galaxy S I9000 Android Development] stepping:
This is an other problem that you can solve with a different hack. The User "streakpt" posted it one post before you. ;)

http://xdaforums.com/showpost.php?p=7935630&postcount=270
[Galaxy S I9000 Android Development] grim201:
cp /efs/nv_data.bak /sdcard

cp: not found

# cp /efs/.nv_data.bak /sdcard

cp /efs/.nv_data.bak /sdcard

cp: not found

when i type ls -al in /efs folder i can't fine any *.bak file

i tried this commands too:

cat /efs/nv_data.bak >> /sdcard/nv_data.bak

/efs/nv_data.bak: No such file or directory

# cat /efs/.nv_data.bak >> /sdcard/nv_data.bak

cat /efs/.nv_data.bak >> /sdcard/nv_data.bak

/efs/.nv_data.bak: No such file or directory
[Galaxy S I9000 Android Development] matty___:
Well cp the copy command was not found
[Galaxy S I9000 Android Development] stepping:
Ever tried this? :
[Galaxy S I9000 Android Development] grim201:
i tried this too. i tried unloking using the app, using hex editor too, but with no success
[Galaxy S I9000 Android Development] streakpt:
Are you in windows? because ## cp: not found ## means that the CP command wasn't found...
[Galaxy S I9000 Android Development] grim201:
i run in windows command prompt the following:

adb shell

su

cp (and the rest of what i posted earlier)
[Galaxy S I9000 Android Development] streakpt:
after you tyoe adb shell does this appear:

* daemon not running. starting it now *

* daemon started successfully *

??
[Galaxy S I9000 Android Development] grim201:
yes, it appears
[Galaxy S I9000 Android Development] BakaSenpai:
I don't want to sound like a noob...but I've been at this for about an hour and I'm still not able to flash to JPC.

I've done the regedit hack and the update box is in test mode..and i even unmounted my internal sd and formatted...but I'm getting JM1 as my latest firmware upgrade...and I'm on JM3 with JH2 CSC...

any ideas what could be wrong?
[Galaxy S I9000 Android Development] EarlZ:
I managed to remove the requirement for unlock code by using the guide on the first page does this mean it restored my original product code?

EDIT:

Connecting the phone back to Kies shows my product code is now XXXXXXXXXX

I have a copy of my original nv files should I restore them or it will lock the phone again , my hand set is carrier locked btw.
[Galaxy S I9000 Android Development] Henrik313:
rededit hack: change the DBdevice numbers from 1 to 2, 3, 4, ...

and import rededit again, during the phone is connected with kies
[Galaxy S I9000 Android Development] BakaSenpai:
Still nothing...originally the device numbers were 9,10,11 where the info was in 9. I changed it to 2,3,4 with the info in 2 and I'm still not getting it. I'm running the latest Kies as well. :confused:

And yes, while i was doing the regedit, kies was still running and my phone was connected
[Galaxy S I9000 Android Development] Henrik313:
Update:

JPC is not available over kies because of the bootproblems.
[Galaxy S I9000 Android Development] BakaSenpai:
man, looks like i might flash with odin then. -_-