A big problem - XPERIA X10 General

Hi
Unfortunatly I am having to send my phone back to my carrier for repairs. My phone is currently rooted on world generic 2.0.2a.0.24( thanks to the team on here )
I have used the method of editing default prop and build prop to change to the most recent software to fool seus and every time its worked a charm.
Tonight however when I connected to seus after changing the codes back to my carrier the repair button was not available. I reinstalled seus just incase but same thing. I tried PC companion but each time it failed to offer me a repair option also.
After checking every stage I noticed that the default prop file was reverting back to the world generic code instead of my carrier after each boot. The build prop file remained as changed.
I am at a loss as to why this is happening and no search on here has provided the answer. I have also rerooted etc but every time the problem remains.
Is this a new security feature not yet picked up? I fear for my warranty now as cant send phone back in its current software state!
Any help would be greatly appreciated x

Hi, I might be wrong but i'm sure you have to use the binary flash tool to go back to .504 from .24 firmware:-/ Thats what I had to use anyway
Sent from my X10i using XDA App

Thanks for the info. I did not know that was the case for this firmware. Is that info available anywhere regarding having to downgrade 1st before repairing via seus using the above method?
I would like to read up on it before using tools I havent before

If you look on rabetionline's thread about the new .24 firmware there is a link on first page that has all info plus a tutorial vid;-) It can be found in the X10 general section
Sent from my X10i using XDA App

Hi - you might not have to do that.. you may have inadvertently used the wrong codes.. I tried using the codes printed on the sticker under the battery and had the same problem - no repair option. but it was because the codes I'd used were for the handset and not the software build!.. use the first of the codes shown here...http://forum.xda-developers.com/showthread.php?t=826875 for your specific region/ handset

That's what I done a few days ago:-/ I changed my codes from UK generic to World generic so I could get update, after updating was having problems with some apps so decided to change back. I changed codes back to UK generic then tried repair via pc companion & SEUS but to no avail! Pc companion said that it was not possible to update at this time! & SEUS said no updates available! In the end using binary flash tool seemed only option! Worked straight away, just had to change World generic .504 to UK generic then repair via SEUS! Voila problem solved & took about 30 mins ;-)
Sent from my X10i using XDA App

Thanks for the info iceman but dbl checked and Im using correct codes.
I just went for the binary flashing method and downgraded to nordic .504 software. I then rooted,changed codes again in root explorer for o2...connected to seus...allowed me to repair and would you believe it Im on nordic 0.24!!!
Argghhhh! Any further help would be much appreciated guys and thanks for your thoughts so far...

Did you remember to delete the SEUS db foldet before trying to repair? Just a suggestion as it worked fine for me
Sent from my X10i using XDA App

yes made sure that was done. Im at a loss but the same thing is happening every time I change the default prop file, it reverts back to current software code.....very strange indeed......

BackOrLay said:
yes made sure that was done. Im at a loss but the same thing is happening every time I change the default prop file, it reverts back to current software code.....very strange indeed......
Click to expand...
Click to collapse
If you are working with .504, .24 you should be changing build.prop. Default.prop is for 1.6.
If using Root Explorer method, make sure to change r/o to r/w. UNIX is a little strange in that it looks like the write was good, but not changed, no error message.

Related

SEUS Update Problem

Well, I managed to update the firmware of my X10 but I've a little problem.
When I start the device, it shows an exclamation point in a yellow triangle. Then I tried to update it one more time and SEUS says that I have the most actual firmware, even changing the files to make the unbranding. I would like to know if there is a method to force SEUS to update from those files and skip all the checks. Any suggestions?
I recommend you to just go to the sony ericsson service center to get your phone unbricked. Or maybe you can use the davinciteam debranding service to unbrick your phone but it costs 10 euros.
Just flash the davinciteam's firmware and it would work I guess.
Anyway I went to the service center and told then that my phone could not start after I did an update.
-------------------------------------
Sent via the XDA Tapatalk App
Aztriltus said:
I recommend you to just go to the sony ericsson service center to get your phone unbricked. Or maybe you can use the davinciteam debranding service to unbrick your phone but it costs 10 euros.
Just flash the davinciteam's firmware and it would work I guess.
Anyway I went to the service center and told then that my phone could not start after I did an update.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Well, I suppose that there is another way to solve this problem. Something like forcing the program like what Davinci does but made by us.
I did it once yesterday and paid 10euro to davinci to bring my x10lives.
But i heard from other chinese post that people debranded their phone to x10a and can't flash it back to original version and they now got a solution to flash it back to original version by replacing the edited jar file in plugins folder to force update button appear in SEUS.
I have no idea will it works the same way on your case or not i can upload the file to let u give it a try but before that can you try a few things for me. Try press different combination key(eg. cameria button+ volume up... ect) when your screen showing is yellow ! to see will there be any words showing up.
tlky said:
I did it once yesterday and paid 10euro to davinci to bring my x10lives.
But i heard from other chinese post that people debranded their phone to x10a and can't flash it back to original version and they now got a solution to flash it back to original version by replacing the edited jar file in plugins folder to force update button appear in SEUS.
I have no idea will it works the same way on your case or not i can upload the file to let u give it a try but before that can you try a few things for me. Try press different combination key(eg. cameria button+ volume up... ect) when your screen showing is yellow ! to see will there be any words showing up.
Click to expand...
Click to collapse
First of all, tnx for the info.
No words apearing at screen, at least on my x10, and I tried several times but no result. No words too, pressing different combination of keys during boot(before vibration).
Finally I send my device to SAT they will make the durty job I expect! (I'll have to pay 25 euros just for updating... but they will bring it back to life)
Cheers and thanks a lot one more time for your time spend!
PD: I realise that jar files could work perfectly in order to force SEUS, that's what people is doing, isn't it?
Anyone find out how to force SEUS to update??
Try flashing the stock 2.1 rom posted by bin4ry that will fix your problem for sure
Sent from my X10i using XDA Premium App
With PC Companion, even if it tells you that the phone has the latest firmware, you can choose to update anyway so it reflashes the phone with the latest firmware
You can use Binary's tools for update and downgrade. This post is quite old...
yemgi said:
With PC Companion, even if it tells you that the phone has the latest firmware, you can choose to update anyway so it reflashes the phone with the latest firmware
Click to expand...
Click to collapse
It doesn't show that always, incase if that happens you can reboot your computer and try it with SEUS/PC Companion one after one.
If you have problem with the update via SEUS because it says that you have the latest update and wont lets you reinstall the OS, you should try the following
1. Go Here and download the .504 version and flash it via flash tool.
2. Boot your phone and finish the settings wizard.
3.Shut it down
4. Run SEUS and update to .435
I hope that helps for any upcoming problems.
AN7 OverClocker said:
If you have problem with the update via SEUS because it says that you have the latest update and wont lets you reinstall the OS, you should try the following
1. Go Here and download the .504 version and flash it via flash tool.
2. Boot your phone and finish the settings wizard.
3.Shut it down
4. Run SEUS and update to .435
I hope that helps for any upcoming problems.
Click to expand...
Click to collapse
He should be able to just download .435 and flash it with Flashtool.
update your seus or try flashing back to fw .435
To update with SEUS whatever firmware you are running:
Do not attach phone to PC.
Open PC companion on desktop, click support zone, then software update. Will pop up a window with a message saying could not find phone, with an underscored repair phone option. Click this and follow steps including selecting phone model (x10 obviously!). Then attach phone while powered off and holding back key when prompted. SEUS will then wipe your phone and install stock firmware. Done this 3 times as fiddle with my system files far too much and have bootlooped my x10 many times!!!!!
Hope this helps
Sent from my X10i using XDA App

[OBSOLETE] Flash ANY official firmware on your phone using Kies.

When mucking about with firmwares and such, it's always nice to know that you can revert back to the original line of firmwares should there be a problem. It's now possible (100% restoration is only possible for regions that has had an official update already).
Special thanks to Zangieff, whose finding made this hack possible.
You can actually use this hack to get any official firmware update available on Kies installed on your phone regardless of your phones region (assuming you have the correct data available).
Check the replies for an appropriate region with code. If you can't find one, it's likely not discovered yet (or has not had any kind of upgrade by Kies).
1) Start Kies. Start the upgrade software and make sure the upgrade software detects your phone properly.
2) If your preferred region requires you to have test mode ON, press CTRL-ALT-U-P. You should get a popup window stating that Test mode is ON. (Test mode is disabled in the most recent Kies versions, as far as I know it's also unused, so there's no real benefit in downgrading to get it)
3) Now close down the update program (Do not close Kies).
4) Run regedit, and browse to the key HKEY_CURRENT_USER/Software/Samsung/Kies/DeviceDB/. Under it you have a bunch of numbered keys, find the one that contains the relevant keys (HIDSWVER and ProductCode). If you find more than one HIDSWVER and ProductCode modify the number that also have a key with the IMEI of the phone you wish to upgrade.
5. Replace HIDSWVER and ProductCode with the apropriate values.
6. Launch the upgrade software, and update your firmware.
Enjoy your new firmware.
About the hack:
There seems to be confusion about what this hack REALLY does, so I'll take this space to explain it a bit further.
Every region has a RegionCode (some operators have their own RegionCode too), to ensure people get appropriately localized firmwareupdates. This hack allows the user to trick Kies into thinking the phone is a phone from another region (or with another firmware version). It means you can get a firmwareupdate from a different region on your phone. It does NOT mean you can magically enter a code to have a localized firmware supplied where none has been released. However, should you have a branded phone there is a CHANCE (not all regions have officially released updates) that an update has been released for unbranded phones in your region. If that's the case, all you should need to do is figure out appropriate settings for the registry keys, and Kies will allow you to "upgrade" to an unbranded localized firmware. There is no way for Kies to automatically make hebrew (or any other language not available in chinese firwmares) available in a chinese firmware. Which means that you will NOT retain your localized settings should you upgrade to that chinese firmware.
Here's a list of currently known codes. Please post any codes not listed here that you find, I'll add to this list as they are discovered.
Sweden: (Currently upgrades to I9000XWJM2/I9000XEEJM1/I9000XWJM1)
ProductCode: XEE
HIDSWVER: I9000XXJF3/I9000SWC/I9000XXJF3/I9000XXJF3
Test Mode: OFF
TMN Region (portugal? spain? Something ): (Currently upgrades to XWJM8)
ProductCode: GT-I9000HKDTMN
HIDSWVER: I9000XWJM2/I9000TMNJM1/I9000XXJM1/I9000XWJM2
Test Mode: OFF
Unknown region: (currently unverified, will test when I have an opportunity)
ProductCode=GT-I9000HKDXSG
HIDSWVER=I9000JPJG8/I9000OJPJG9/I9000JXJG2/I9000JPJG8
Test Mode: Probably not necessary
United Kingdom
ProductCode: XEU
HIDSWVER: I9000XXJF3/I9000OXAJF3/I9000XXJF3/I9000XXJF3
Test Mode: ON
Upgrades to Official XXJM1. With mickeko`s settings i get the XWJM2 official ROM.
Going to try some more combinations, I need the one for Orange Romania
Multi CSC Europe
ProductCode: VDI
HIDSWVER: I9000XWJFB/I9000OXX/I9000XXJF5/I9000XWJFB
Test Mode: ON
Upgrades to official XWJM2 with OXX *Multi CSC* (for Austria, Baltic, Bulgaria, Croatia, Czech Republic, Greece, Hungary, Ireland, Macedonia, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, South Africa, Switzerland)
mickeko said:
When mucking about with firmwares and such, it's always nice to know that you can revert back to the original line of firmwares should there be a problem. It's now possible (100% restoration is only possible for regions that has had an official update already).
Special thanks to Zangieff, whose finding made this hack possible.
You can actually use this hack to get any official firmware update available on Kies installed on your phone regardless of your phones region (assuming you have the correct data available).
Check the replies for an appropriate region with code. If you can't find one, it's likely not discovered yet (or has not had any kind of upgrade by Kies).
1) Start Kies. Start the upgrade software and make sure the upgrade software detects your phone properly.
2) If your preferred region requires you to have test mode ON, press CTRL-ALT-U-P. You should get a popup window stating that Test mode is ON.
3) Now close down the update program (Do not close Kies).
4) Run regedit, and browse to the key HKEY_CURRENT_USER/Software/Samsung/Kies/DeviceDB/. Under it you have a bunch of numbered keys, find the one that contains the relevant keys. (HIDSWVER and ProductCode)
5. Replace HIDSWVER and ProductCode with the apropriate values.
6. Launch the upgrade software, and update your firmware.
Enjoy your new firmware.
Click to expand...
Click to collapse
i have just checked my registry and there are 2 number with, HIDSWVER & ProductCode, these are numbers 2 & 8, so which do i edit.
Great job. Well done
this imo needs to be stickied but with a better title and slighty better description.
there was a post somewhere on here with .reg files that can just be run.
does this allow you to upgrade to any firmware from any firmware? my current flashed firmware says it cannot be upgraded. not that its upto date, but that it actually cannot be upgraded.
EDIT:
1. To the guy above asking about the 2 sets of keys with HIDSWVER in, im guessing that you've connected to Kies. Thats the case with mine, where i can clearly see my device, on JM1 and my girlfriends i connected today and was going to update, which is JF3 still. Hope this helps.
2. So if i replace my value 'I9000XWJM1/I9000OXXJG7/I9000XXJG6/I9000XWJM1' with my girlriends 'I9000XXJF3/I9000OXAJF3/I9000XXJF3/I9000XXJF3' then ill be shown i can update to the official JM1? Does this have any complications either during installation, or because my device is already on JM1. Kies does a full flash anyway doesnt it ?
current question: (solved thanks to OP) Does this (upgrading to JM1) have any complications during installation because my device is already on JM1?
sensi_ said:
this imo needs to be stickied but with a better title and slighty better description.
Click to expand...
Click to collapse
Yes, the title is bad... I should have considered it better before posting, as I can't change it now.
EDIT: Ah, I needed to go to advanced mode to change the title.. Hope it's better now.
If you feel there's something that's unclear/flawed please do tell and I'll change it appropriately.
there was a post somewhere on here with .reg files that can just be run.
Click to expand...
Click to collapse
.reg files is not really viable as the number of the registry key is not always the same.
does this allow you to upgrade to any firmware from any firmware? my current flashed firmware says it cannot be upgraded. not that its upto date, but that it actually cannot be upgraded.
Click to expand...
Click to collapse
Yes. You can flash any firmware available on Kies over firmware from any region and any version. You do need to have the data from an upgradable phone though.
2. So if i replace my value 'I9000XWJM1/I9000OXXJG7/I9000XXJG6/I9000XWJM1' with my girlriends 'I9000XXJF3/I9000OXAJF3/I9000XXJF3/I9000XXJF3' then ill be shown i can update to the official JM1? Does this have any complications either during installation, or because my device is already on JM1. Kies does a full flash anyway doesnt it ?
Click to expand...
Click to collapse
Just make sure ProductCode also matches and it should be possible. In test mode it seems to be possible to reflash even if the firmware version is already available on the phone.
current question: Does this (upgrading to JM1) have any complications during installation because my device is already on JM1?
Click to expand...
Click to collapse
None that I know of.
And also: If you have multiple keys with HIDSWVER and ProductCode, I'm guessing you have connected more than one SGS on your computer. If that's the case, modify the keys where you find the IMEI of the phone you want to upgrade. (I'll add this to the original post too)
mickeko said:
Yes, the title is bad... I should have considered it better before posting, as I can't change it now.
EDIT: Ah, I needed to go to advanced mode to change the title.. Hope it's better now.
If you feel there's something that's unclear/flawed please do tell and I'll change it appropriately.
.reg files is not really viable as the number of the registry key is not always the same.
Yes. You can flash any firmware available on Kies over firmware from any region and any version. You do need to have the data from an upgradable phone though.
Just make sure ProductCode also matches and it should be possible. In test mode it seems to be possible to reflash even if the firmware version is already available on the phone.
None that I know of.
And also: If you have multiple keys with HIDSWVER and ProductCode, I'm guessing you have connected more than one SGS on your computer. If that's the case, modify the keys where you find the IMEI of the phone you want to upgrade. (I'll add this to the original post too)
Click to expand...
Click to collapse
nope mate im the only one with an SGS in the house, and im the only one with access to my laptop, so dont know how i have multiple keys, either way i try it im getting a mtp connecting lopp atm, so im guessing i need to format the phone internal sd card, just have to find a decent free tool to back everything up now.
ghosty_uk said:
nope mate im the only one with an SGS in the house, and im the only one with access to my laptop, so dont know how i have multiple keys, either way i try it im getting a mtp connecting lopp atm, so im guessing i need to format the phone internal sd card, just have to find a decent free tool to back everything up now.
Click to expand...
Click to collapse
if you check the keys mate, if they have the same device name but different build numbers, then thats just when youve connected your device on different firmwares. If i was you id delete one of the 'folders' say 8, then connect your device and see if it creates another one, then use that, if not use the other one you had. (dont forget to refresh in regedit!)
sorry if that wasnt clear
btw to backup a free tial MyBackup in market, or Titanium if you have root.
¬ to the OP, the title is great now! the .reg files i was talking about were for each individual firmware! mad i know, but some members probably wont get this, and installing a key is probably easier for them. thanks for clearing things up!
Just delete the entire Samsung entry
it will be recreated upon starting kies
and your device will be in number 1
sensi_ said:
if you check the keys mate, if they have the same device name but different build numbers, then thats just when youve connected your device on different firmwares. If i was you id delete one of the 'folders' say 8, then connect your device and see if it creates another one, then use that, if not use the other one you had. (dont forget to refresh in regedit!)
sorry if that wasnt clear
btw to backup a free tial MyBackup in market, or Titanium if you have root.
¬ to the OP, the title is great now! the .reg files i was talking about were for each individual firmware! mad i know, but some members probably wont get this, and installing a key is probably easier for them. thanks for clearing things up!
Click to expand...
Click to collapse
nope i have not flashed it or routed it yet for that matter, and i did a yahoo search for a backup program, using the trial of MyBackup which it if works how i expect it to ill purchase it as it will be good to keep things backed up, was fed up having to re-do all my phone entries when i got the replacement SGS.
omrij said:
Just delete the entire Samsung entry
it will be recreated upon starting kies
and your device will be in number 1
Click to expand...
Click to collapse
yeah i was thinking the same but wasnt sure if it needed it to run in the first place.
edit: i have now just restored my phone back to factory settings, using the factory reset option in privacy in the settings menu.
SERIOUSLY HELP!
just done this, going from JM1 with a different modem and csc, to the official JM1, phone was restarting after completed update.... IT WONT TURN ON!
EDIT: with battery pulled it booted again, only to go to a black screen after Galaxy S logo, man i asked before doing this!
Official updats from kies don't update your bootloader (no boot/sbl bin files)
try to remove your battery, replace it and then try again
if it still doesn't boot, try entering download mode
omrij said:
Official updats from kies don't update your bootloader (no boot/sbl bin files)
try to remove your battery, replace it and then try again
Click to expand...
Click to collapse
yea just did this and same happened, understandably fuming at the moment.... has anyone got an official JF3 firmware? i dont see any way back now?
Enter download mode (hold power+home+vol down)
and flash again with odin
omrij said:
Enter download mode (hold power+home+vol down)
and flash again with odin
Click to expand...
Click to collapse
yea defeats the whole point of this thread though doesnt it, it cant have been tested or it would have worked... i need a link to
I9000XXJF3/I9000OXAJF3/I9000XXJF3/I9000XXJF3
exactly this nothing else, ive contributed a fair bit on here so would appreciate if someone could sort me out, thanks
before re-flashing is it worth factory reset from recovery, or wiping cache partition? thinking back im sure ive seen this same problem with failed flashes, and this being recommended
at last finally got this to work!
ive tried every method posted and none have worked this finally has worked.
brilliant stuff many many thanks.
sensi_ said:
SERIOUSLY HELP!
just done this, going from JM1 with a different modem and csc, to the official JM1, phone was restarting after completed update.... IT WONT TURN ON!
EDIT: with battery pulled it booted again, only to go to a black screen after Galaxy S logo, man i asked before doing this!
Click to expand...
Click to collapse
Wipe the data from volup+home+startbutton.
rkantos said:
Wipe the data from volup+home+startbutton.
Click to expand...
Click to collapse
Yes im the impatient type and couldnt wait for a reply, just done this and im back! thank F***!
scrap that its totally screwed, force closes everywhere after entering unlock pattern.
TwLauncher process blah blah has stopped working,
JF3 Uk someone please?
5. Replace HIDSWVER and ProductCode with the apropriate values.
Click to expand...
Click to collapse
Ok...I found it but which values should I put?
6. Launch the upgrade software, and update your firmware.
Click to expand...
Click to collapse
Should I update with test mode on or off ?

That was easy!

Ok so, ive been trying to debrand my phone for a few weeks now and all attempts have failed...
But i just got it!!!
I was on 020 but now on global generic 026 fw
All i did was download the flashtool with the 026 fw and flashed my phone...
Done.
Question i have though is this.
If it was that damn easy to debrand why has no one else suggested i do it that why when i have and others asked??
Seansmit17 said:
Ok so, ive been trying to debrand my phone for a few weeks now and all attempts have failed...
But i just got it!!!
I was on 020 but now on global generic 026 fw
All i did was download the flashtool with the 026 fw and flashed my phone...
Done.
Question i have though is this.
If it was that damn easy to debrand why has no one else suggested i do it that why when i have and others asked??
Click to expand...
Click to collapse
Everyone here suggest to rest of us to debrand, but luckily you did it without anyone telling you.
Anyways, I hope this update works on one of this generic one and I wish that I knew which one.
Seansmit17 said:
Ok so, ive been trying to debrand my phone for a few weeks now and all attempts have failed...
But i just got it!!!
I was on 020 but now on global generic 026 fw
All i did was download the flashtool with the 026 fw and flashed my phone...
Done.
Question i have though is this.
If it was that damn easy to debrand why has no one else suggested i do it that why when i have and others asked??
Click to expand...
Click to collapse
Thats how I did mine, I didn't ask anybody, was fairly obvious to me that it would be the easiest way to do it.
Could you state which flash tool you used and which firmware file please?
I was trying to debrand a few weeks ago and just couldn't get it with the swap file technique thats all over the place so I gave up.
I used the xploid long root method, it includes a generic firmware.
I used this here:
http://forum.xda-developers.com/showthread.php?t=683793
I used the (for flashtool) Generic_R2BA026
Make sure you use the right file for your phone, X10i or X10a
Follow this as well for the device ID:
Code:
Hi,
Loader.sin must be there. All other sin files are optional.
1.) Open regedit and search the String :
"USB\Vid_0fce&Pid_adde\"
You will find the "DeviceInstance" should look like this :
"USB\Vid_0fce&Pid_adde\1&23cfa456&7&8"
copy the last part "1&23cfa456&7&8" into the DeviceID.txt file. Don't paste any free lines/blocks before or after!
2.) Start X10flash.bat
3.) Connect X10 in flash Mode:
a) Power down
b) Hold "back" Key
c) conncet USB cradle on PC
If the LED is green everythin is good!
4.) Press ENTER :)
Thanks heaps.
I'm at work at the moment, but I'll give it a go tomorrow.
my scenario is different, i never thought of debranding it but after i installed lcd density changer on my 020, i got yellow exclamation mark and i used the flashtool and viola lol.

[TUT] T-Mobile UK Upgrading/root/lag fix and De-branding.

I take no credit for any of this work. I have added it all to one post to help make life a little easier for those who are wanting help in getting rid of any need of waiting for T-Mobile to release any firmware again. Credits will be added to all post at the bottom of the respective page. This TUT will also work with other networks.
If you have 3 Button Download mode you can jump to page 2.
Post 1: 3 Button Download Mode.
Post 2: Upgrade to Froyo.
Post 3: Rooting and lag fix.
Post 4: De-Branding.
3 Button Download.
I have run out of time to add this today i will finish off tomorrow. For now follow this http://forum.xda-developers.com/showthread.php?t=821698
Upgrade to Froyo.
PRELIMINARY NOTE:
[WARNING!] Do Not flash Any ROM (firmware) until you can get the 3 buttons DOWNLOAD MODE working, even with this Kies trick.
If you want to test the 3 buttons download mode then notice that you can switch back to normal mode by pulling the battery out and then back in. At the next boot the phone will be back in normal mode.
LAGFIX USERS:
[WARNING!] Remember to disable lagfix before to update.
This will avoid filesystem errors that may occurs at the boot of the new flashed firmware.
INSTRUCTIONS:
1) Download latest Kies Registry Patcher, tool is attachment. Note: It require Microsoft .NET Framework 3.5 or later version.
2) Update Kies to 1.5.3.10103.102.
3) Launch Kies Registry Patcher; If you patched the dll in the past with an older version of the patcher then be sure to launch new release as administrator since it have to revert the dll to the original version as the patch isn't needed anymore (Right click on application > Run as Administrator).
4) Launch Kies and connect your phone; Wait for Kies to recognize it properly.
5) You have 2 possibilities now:
5a) Drop down the combo-box "Spoof Product Code as" and select the wanted one. It should automatically fill the "Spoof Software Revision as" textbox with the needed data necessary to find your update.
This feature was added in order to give all the opportunity to use the needed product code. (Special thanks to MCOGW that shared with me his database of product codes/sw revisions).
The label above will be completed with the country related to the chosen product code.
5b) From patcher select:
File > Load Backup
Open the backup that you want to use (e.g. kies-backup-XEU.xml if you want to spoof your phone as XEU, or if your phone is XEU yet and you want to flash it again).
6) From patcher answer "YES" in order to apply the registry update.
7) From Kies you can now update as normal.
Remeber that this patch will remain ACTIVE until you set "Enable Spoof" field to False!
It's not a problem but ater you update the phone it's suggested to put that value to false so the patch become inactive.
Full Post: http://forum.xda-developers.com/showthread.php?t=835628
Credits:
Nodial
Root/Lag fix.
Download the attached files, place them on your memory card and install them on your handset by navigating to them in My Files app and click on them to install.
Once installed run z4root first, then run OCLF.2.3.0 and except Superuser permissions.
Inside OCLF2.0 application click on the following:
1st: Install EXT2 Tools (follow instructions)
2nd OneClickLagFix V2.2+ (follow instructions)
Congrats you now are rooted and have applied a lag fix.
Full Post z4root: http://forum.xda-developers.com/showthread.php?t=833953&highlight=Z4root
Full Post OCLF: http://forum.xda-developers.com/showthread.php?t=833953&highlight=oclf
Credits:
RyanZA
z4ziggy
Sebastian Krahmer's rageagainstthecage
De-branding.
To truly de-brand you need to get rid of the branded product code and have the correct CSC. Follow the steps below.
[WARNING] Make a full backup of your \efs folder just in case you go wrong or any errors occur.
You will need to be rooted and have the root explorer app installed from the market.
Copy your \efs folder to your pc and open nv_data.bin with note pad, Search for TMU and replace with XEU. If you can not find TMU try KOR. Save the file and and copy it back to your \efs folder on your handset. Delete the nv-data.md5 file off the handset and reboot. repeat steps with the nv_data.bak file.
Once completed change your CSC to XEU by typing *#272*(yourimei)# and click on XEU.
Now when Samsung release a new update you will get it straight away.
Sorry if I have missed any people in the credits. Please post with name and post number if poeple need to be added.
Hey I want to get Froyo, tired of waiting for T-mobile but i dont have the 3 button combo on my phone so is there any safe way of doing this or fixing 3 button....?
hey n1kon nice idear b4 barry shuts down the forum on T,M
have you used the root/lag fix ??
Great post, tired of waiting for t-mobile to release 2.2
Thanks.
n1kon said:
Upgrade to Froyo.
5a) Drop down the combo-box "Spoof Product Code as" and select the wanted one. It should automatically fill the "Spoof Software Revision as" textbox with the needed data necessary to find your update.
This feature was added in order to give all the opportunity to use the needed product code. (Special thanks to MCOGW that shared with me his database of product codes/sw revisions).
The label above will be completed with the country related to the chosen product code.
6) From patcher answer "YES" in order to apply the registry update.
7) From Kies you can now update as normal.
Credits:
Nodial
Click to expand...
Click to collapse
I'm rather new to all this and before I attempt to update my T-Mobile Galaxy S using the described 5(a) option, I would appreciate some advice, please.
I understand the instructions right up to the end of para 5(a) but at this point there is no "yes" button to click. However, there is a "Read Registry" button. Presumably I click this and will then be asked the click a "Yes" button to proceed with the update.
What then happens? What should I expect to see on the PC and on my phone?
Some step-by-step instructions would be much appreciated to boost my confidence!
P.S. I've already checked that I have the three-button system restore active on my phone.
Ain't done no root because I wil be ****ed if it bricks and I don't know no way of rooting without restore mode.
Sent from my GT-I9000 using XDA App
I've been running 2.2 on my T-Mobile UK Galaxy S for some time, but have never used or even installed Kies. I just installed the relevant USB drivers, then flashed a ROM I've downloaded from mirrors linked here with Odin3 (I've always had download mode working properly). Currently I'm using JPO with SpeedMod Kernel K10H, which provides root.
Hi i upgraded via the kies registry way all works well apart from i cant find where to switch between 2g and 3g. It was in mobile networks on 2.1 but its not there now also having issues using myplayer and beebplayer once again they worked in 2.1 but not on froyo atm. other then that alss good
I used this guide to fix the 3 button combo issues - http://forum.xda-developers.com/showthread.php?t=785201
It still is in there 2g is gsm
Sent from my GT-I9000 using Tapatalk
blazevxi said:
I used this guide to fix the 3 button combo issues - http://forum.xda-developers.com/showthread.php?t=785201
Click to expand...
Click to collapse
Im looking into the safest one to use but am at work right now
Sent from my GT-I9000 using Tapatalk
I use both root and lag fix
Sent from my GT-I9000 using Tapatalk
Surely the easiest way to debrand is to just flash a new ROM via ODIN?
Is that way safe, dont want to brick my phone?
-Elvin- said:
Is that way safe, dont want to brick my phone?
Click to expand...
Click to collapse
I've done a branded Orange and Vodafone by flashing XXJPO via ODIN.
It's very hard to totally brick your phone with ODIN, but there can be complications.
Before you do anything, make sure you have working 3br and download mode. If you don't have it, I don't recommened using Kies or ODIN.
Rawat said:
Surely the easiest way to debrand is to just flash a new ROM via ODIN?
Click to expand...
Click to collapse
Flashing with odin will not allow u to update with kies when the next release is issued as your product will stay the same and your software versions will be wrong so you will need to use odin again. Plus if odin is used wrong it can brick you phone
Sent from my GT-I9000 using Tapatalk
n1kon said:
Flashing with odin will not allow u to update with kies when the next release is issued as your product will stay the same and your software versions will be wrong so you will need to use odin again. Plus if odin is used wrong it can brick you phone
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Nope, if you flash a full ROM via ODIN, including the CSC, it'll work fine. It'll even work on kies (although i don't know why anyone would want to do that )
Kies can also brick your phone >_>;

[Q] Couple of questions...

Hi! I just got my xplay a month or two ago, and my last phone was a iphone. As such, stepping from the relatively easier to handle ios to android system's not exactly a piece of cake...
And I still have a couple questions despite lurking in this forums for a while...
1) im running 2.3.2 , rooted with gingerbreak. I heard there's an improvement in battery life.. so im quite tempted to update, but the thought of bloatware coming back kind of scares me.. ._.
So should I update?
2) is unlocked or locked bootloader better?
3) finally, will there be a final or complete version of cm7?
Also, would be great if anyone could explain what is an OTA and kernel...
Thanks!
1) its up to you, it is possible to upgrade with root as long as you have any model except a r800 x
2) I dont think either is better just depends on what you want to do to your phone
3) It depends what you mean by complete. There will probably be a stable version that is better than the stock rom eventually, but im not a dev
Ota means "over the air" and a kernel if im not mistaken is the part of the phone responsible for managing sysyem resources and the like. Not that I know much about anything and I could be wrong lol
Sent from my R800i using XDA App
LemonPlusTea said:
Hi! I just got my xplay a month or two ago, and my last phone was a iphone. As such, stepping from the relatively easier to handle ios to android system's not exactly a piece of cake...
And I still have a couple questions despite lurking in this forums for a while...
1) im running 2.3.2 , rooted with gingerbreak. I heard there's an improvement in battery life.. so im quite tempted to update, but the thought of bloatware coming back kind of scares me.. ._.
So should I update?
2) is unlocked or locked bootloader better?
3) finally, will there be a final or complete version of cm7?
Also, would be great if anyone could explain what is an OTA and kernel...
Thanks!
Click to expand...
Click to collapse
This will be my second numbered answer today. Anyway:
1) What model do you have? I assume it's an r800i or r800a. If it is, I would head over to the development section and check out how to get the UK generic firmware on your phone without unlocking the boot loader. I did that, rooted it, then updated to 2.3.3 and removed a lot of bloat and it's good to go now.
2) I have unlocked the boot loader on every Android I've owned, but I haven't on this phone. I wouldn't until development takes off a little bit more. It will soon, but I probably won't even do it then, personally.
3) Yes, we have great people working on it. It's progressing majorly with each update.
Just next time search before posting...nah, I'm just kidding. Welcome to Android.
adb shove iPad2post.apk to /forum/thread
OTA means you are updating the firmware on your phone through your phone over wifi.
If you didn't remove the boats you can still do it by pressing the software update button on your phone. Just make sure that your bootloader is is still LOCKED.
Sent from my XPlay using XDA App.
Thanks guys! I'll try to flash the firmware on my phone after I get home from school. my xplay is a r800i. Also, if I use the UK firmware and update to 2.3.3, will it affect my ability to update to 2.3.4 as I live in Singapore?
No, when 2.3.4 comes out it would probably be available to generic uk before any other versions. As long as you freeze and not remove boats, you would be able to ota update to 2.3.4
Sent from my XPlay using XDA App.
Hey guys Im back from school.
Is it this thread to follow ?
http://forum.xda-developers.com/showthread.php?t=1119074
Because I saw another one ..
http://forum.xda-developers.com/showthread.php?t=1097591
^ which requires an unlocked BL. :O
Oh my god.. I didnt enable debugging and the process stopped halfway.. now the phone displays an exclaimation mark next to a phone.. did i just brick my phone? ...
EDIT : googled around and now im trying to restore my phone via SEUS...
Ok.. my phone started up fine after running SEUS.. but I clicked restore to factory instead of update..
I want to try updating to 2.3.3 with root again.. So can anyone point out anything I did wrong the previous time?
1. I downloaded the generic UK version (http://forum.xda-developers.com/showthread.php?t=1119074) and flashtool 0.2.8 (http://forum.xda-developers.com/showthread.php?t=920746)
2. I used flashtool and flashed the .tft file and followed the onscreen instructions...
3. the flashing stops halfway cause i didnt enable usb debugging (?) and it causes my phone to be unable to boot up and trauma for me for panicking for 30 minutes. ._.
I tried flashing again with USB debugging on..?
My version is now 2.3.3 after I restored with SEUS, however.
07/046/2011 18:46:02 - INFO - Flashing adsp.sin
07/046/2011 18:46:05 - INFO - Flashing kernel.sin
07/046/2011 18:46:07 - INFO - Flashing amss_fs.sin
07/046/2011 18:46:07 - INFO - Flashing fota1.sin
07/046/2011 18:46:08 - INFO - Flashing fota0.sin
07/046/2011 18:46:09 - INFO - Flashing apps_log.sin
07/046/2011 18:46:09 - INFO - Flashing amss.sin
07/046/2011 18:46:19 - INFO - Flashing cache.sin
07/046/2011 18:46:20 - INFO - Flashing system.sin
07/046/2011 18:46:44 - ERROR - Error flashing. Aborted
07/046/2011 18:46:44 - INFO - Now unplug the device and power it on
07/046/2011 18:46:44 - INFO - Then go to application settings
07/046/2011 18:46:44 - INFO - turn on Unknown Sources and Debugging
( after that resulted in the same problem as before but luckily I knew how to fix it again.. ._. )
It might be that you're not using the latest version of flashtool, it's 0.2.9.1 and it's the beta one and afaik it's the only one to support the play.
Regards Dousan...
Dousan said:
It might be that you're not using the latest version of flashtool, it's 0.2.9.1 and it's the beta one and afaik it's the only one to support the play.
Regards Dousan...
Click to expand...
Click to collapse
I see.. Cause I thought beta might not be stable!
Thanks alot! Time to go try again ^_^
EDIT : Same error with the newest flashtool.. ._.
Crapp...
I unpacked the 0.2.9.1 and ran the X10 Flash Tool... and it still doesnt like me..
It seems it hates me more and more..
now instead of even starting flashing after i send my phone into flash mode it gives me this error..
ERROR - USB\VID_0FCE&PID_ADDE\5&1F015A4B&0&5
Triple edit : Now Im back to square one of flashing till system.sin and getting an error.. ._.
LemonPlusTea said:
I see.. Cause I thought beta might not be stable!
Thanks alot! Time to go try again ^_^
EDIT : Same error with the newest flashtool.. ._.
Crapp...
I unpacked the 0.2.9.1 and ran the X10 Flash Tool... and it still doesnt like me..
It seems it hates me more and more..
now instead of even starting flashing after i send my phone into flash mode it gives me this error..
ERROR - USB\VID_0FCE&PID_ADDE\5&1F015A4B&0&5
Triple edit : Now Im back to square one of flashing till system.sin and getting an error.. ._.
Click to expand...
Click to collapse
Maybe it's a corrupt download or the unpacking of the .zip/.rar file went bad. Could try a reunpacking or/and redownload?
Regards Dousan...
Redownloaded the flashtool 2 times and the generic UK ftf 3 times already.. could it be my computer's problem?
LemonPlusTea said:
Redownloaded the flashtool 2 times and the generic UK ftf 3 times already.. could it be my computer's problem?
Click to expand...
Click to collapse
I know back in my Galaxy S days the firmware tool Samsung used worked on one of my computers but didn't work on the other. I would try another computer if you had access to one.
adb shove iPad2post.apk to /forum/thread
TheBassman369 said:
I know back in my Galaxy S days the firmware tool Samsung used worked on one of my computers but didn't work on the other. I would try another computer if you had access to one.
adb shove iPad2post.apk to /forum/thread
Click to expand...
Click to collapse
Alright, I'll try it with my sister's laptop ^^..
Entire day has been miserable without my apps... :l
Nope.. still doesnt work.. ._.
LemonPlusTea said:
Nope.. still doesnt work.. ._.
Click to expand...
Click to collapse
Man. That's crazy. I have no idea what to do. Hopefully you can get it.
When flashing, have you ticked the 'erase data' (I'm not sure it's the exact name) or are you flashing without erasing? Cus it looks like that's where the error occurs when it's supposed to flash the data?
Regards Dousan...
Did you install the Sony software from your phone first?
Mine needed it to get the drivers. It said it had errors but I let it go for a while and it finished no problem.
Dousan said:
When flashing, have you ticked the 'erase data' (I'm not sure it's the exact name) or are you flashing without erasing? Cus it looks like that's where the error occurs when it's supposed to flash the data?
Regards Dousan...
Click to expand...
Click to collapse
Yeah I checked the erase data box all the time...
@ncaissie, im not entirely sure what you mean... Would you mind explaining?

Categories

Resources