Hey guys,
I updated to 2.2 froyo yesterday using the registry hack and all went smooth.
My question is this.
When i used to plug my phone into kies it said "Latest version already installed"
Now it says "This device's version cannot be updated"
Does this mean i will no longer get future updates?
Or will i just have to do another registry hack at the time...
PDA: JP6/ PHONE JPM/ CSC/ JP4.
Thanks for any help
Just an update i have figured it out...
I have just gone back to the registry and changed my product code from XEU to XEE as i did with the registry hack and it came back up saying latest version already installed.
So its just a matter of changing my registry code to XEE on the next update and all will be good.
For anybody that was wondering if this would block future updates... NO it doesnt look like it will just change the product code on each update to what it should be and you will be able to get them.
Related
I have a Samsung Galaxy S original model number GT-I9000HKAOPS. Like many others I jumped the gun and used Kies Registry Patcher 1.6.0.0 to upgrade to Froyo. The firmware version I upgraded to was XEU which I understand is the UK unbranded ROM. Also like many others doing so has changed my Product Code to KOR. With the recent release of the official Optus 2.2 Froyo version I decided to flash this firmware, again using the Kies Registry Patcher. On completion I noticed my product code is still KOR. This has a number of side effects such as Kies continuously prompting that a firmware upgraded is available, plus indicating the wrong market area.
My objective is to restore my Galaxy S back to how it was when it was supplied or how it should be if I had only flashed the official Optus Froyo ROM. I have a rough idea how to do this though I have a few questions:
1. What is the best way to restore my product code? I have seen references to deleting your nv_data.bin as well as entering in a code via your dialler.
2. If rooting your phone to delete nv_data.bin is the best way, this installs an updated kernel as well as other files. If I restore my product code then upgrade to the official Optus Froyo firmware will this replace the updated kernel and remove the other files added through rooting?
3. What other things may have changed upgrading to the XEU ROM that may reside after flashing to the official Optus Froyo ROM?
4. What else may I need to do to achieve my objectives?
Please note I have searched for many hours trying to find solutions and answers to achieve what I want to achive without much luck, any advice would be appreciated.
How to Restore my Galaxy S
Hi - I'm also looking for the same solution but didn't get any. Did u get a chance to get any results ?
I found a solution in regards to the repeated prompt to update firmware through Kies. The fix is, if you have used Kies Registry Patcher 1.6.0.0, to run this again and set enable spoof to false, then click ‘Write Registry’. Next time you run Kies the prompt to upgrade firmware is gone. A residing problem is that if you try to manually do a firmware update through Kies, it comes up with a message stating ‘This device’s version cannot be update’. I imagine this is due to the mismatch between the currently installed firmware, (PDA: I9000DTJP5, PHONE: I9000DTJP3, CSC: I9000OPSJP4) and the current device product code(GT-I9000HKAKOR).
Another interesting question, if anyone has upgraded direct to the official Optus Froyo ROM using Kies without any hacking, have they got the same PDA, PHONE, and CSC details as I have.
http://forum.xda-developers.com/showthread.php?t=787163 go to this page i used the automatic method takes like 2 mins.
Thanks a lot for the post. It was really helpful
Thanks again
--Durai
I have had great success, all without rooting or any other complicated steps, though it wasn’t all smooth sailing.
The steps I took were to use the Kies Registry patcher ver 1.6 to cross grade my phone to the XSA Froyo ROM which is the Australian Telstra, Virgin and etc ROM. Given I’m on Telstra this is ideal ROM for me. The problem I ran into though is the ROM would ‘fail to convert to upgrade mode’. Kies would then report a failed upgrade and would prompt to attempt recovery. I ignored this message a number of times then decided to run with it. Doing so gave me step by step instructions to put the phone into download mode, from there the installation of the ROM began. Once the ROM was fully installed I formatted the internal SD memory, did a factory restore and all is sweet. Product code is XSA, sales code is XSA as well. This is a better outcome to what I was hoping to achieve.
sorry but looked through quite a few pages about the 2.2.1 upgrade and is it avaiable on UK 02 or do I have to do something special ??
I am new to the Glaxaxy S and have tried the search so appoligies if the answer is lurking somewhere.
I have plugged my phone in to Kies checked for a firmware upgrade and get the following Current version: PDA:JP6/Phone JP3/CSC: JP3
The latest version is already installed on connected device.
Thanks for looking
Currently it is only rolled out to Product code XEU and CPW if your product is either of those then kies will inform you have an upgrade. The Upgrade is JPY, if your product is not either of those then you will need to use Nodial Registry patcher for Kies to spoof XEU.
hey,
sorry for the slightly noob question but here goes lol
i've looked around the net a bit and i've seen that the 2.2.1 update is out and ready to be downloaded from Kies! however, when i connect my phone to Kies all it seems to say is "latest firmware already installed". but i only have the original 2.2 froyo.
i thought it might have been because it's not officially out yet but i looked around and found that 18th january was the release date.
ive heard good things about the update and am eager to get it, so any help please!!
it's not out for every product codes only for a few ones. i you still want to update via kies you can try registry patcher to fake your product code located here: http://forum.xda-developers.com/showthread.php?t=835628
scorpeeon said:
it's not out for every product codes only for a few ones. i you still want to update via kies you can try registry patcher to fake your product code located here: http://forum.xda-developers.com/showthread.php?t=835628
Click to expand...
Click to collapse
does this mean they will soon release an update on all product codes, or some will never get it and some will?? thanks
Hi there,
I successfully upgraded my SGS to 2.2.1 (JPY) via the Kies Registry Patcher in January. All seems well however I just tried doing exactly the same trick with my sister-in-laws SGS and no luck. Successfully got her rooted and unlocked, but for some reason I cannot get the registry spoof working.
I know I have not done things in exactly the same order for her phone, but it is bugging me. I tried with Kies 1.5(?) but when the phone was plugged into Kies it flashed up the "You can update your firmware" but when the actual process kicked off no firmware was available. She's on JF3.
Her SGS is from the same company, locked to the same network. The only thing I can think of is that the original spoof I did is still in my system registry and that her values do not match up in the same way? I have no idea...
I have now updated to Kies 2.0 to see if I can just get a normal 2.2 update for the T-Mobile firmware, but if her experience is like mine, that firmware has to go! So 2.2.1 XEU is the goal.
Any ideas?
As a side issue, now that OTA is enabled for 2.2.1, does that mean I will never have to fight Kies for an update?
http://forum.xda-developers.com/showthread.php?t=959806, as well you could also use Odin/Heimdall (? spelling) to flash a 2.2.1 ROM. OTA is not currently activated.
OTA at Samsung end? As the option is there on my phone and when i run it is says "no updates available".
Anyway - yeh. I saw that link. Will check it out when I next get my mitts on her phone.
What I don't know is what has changed? Has ?Samsung wised up to the previous spoof in some way?
skinfreak said:
OTA at Samsung end? As the option is there on my phone and when i run it is says "no updates available".
Anyway - yeh. I saw that link. Will check it out when I next get my mitts on her phone.
What I don't know is what has changed? Has ?Samsung wised up to the previous spoof in some way?
Click to expand...
Click to collapse
You can spoof by patching a file to make Kies2.0 believe that another firmware is connected, but when the update starts, another check is made directly to the phone, which is new as of Kies2.0. This is where we get stuck in patching Kies2.0. The module that checks this is encrypted which makes is impossible to patch it.
This is why I went for another approach and spoofed the firmware that the device is reporting, to fool Kies2.0 in every moment
I upgraded my SGS, via KIES, this saturday using a spoofed NEE (Scandinavian) product code, but now it seams like the Gingerbread update is no longer available via KIES:
When I spoof my product code today i get: This is the latest firmware (check ExcibitA attachment) instead of it telling me that there is an update.
ExcibitB attachment is my current version without spoofing.
Can anyone else confirm this?
I'm in the UK and i updated this morning not using any spoof or anything, completely stock. I can confirm my kies is saying the same as yours.
Im in norway and yesterday Kies offered me to upgrade my phone to: PDA:JVB PHONE:JVK CSC:JV3 (XEE)
But today it is telling me i currently have the latest firmware: PDA:JS7 PHONE:JPY CSC:JS1 (XEE)
So it seems to me they pulled out the scandinavian update
Possible its a server overload with millions who cannot wait all spoofing product code .
jje
Well I just phoned Samsung uk, and the guy said it has been removed due to a problem with the server. So, wanting a second opinion, I phoned straight back and spoke to someone else, who just said it's been removed as it was just a test!!? I don't think half of them know what they're talking about in that place!