Sony Ericsson / Sony : Symbian phones : Unbranding a M600/W950/P990/P1/W960 for free with xs++ & seus!
>
New Topic
>
Reply<
Esato Forum Index
>
Sony Ericsson / Sony >
Symbian phones
> Unbranding a M600/W950/P990/P1/W960 for free with xs++ & seus!
Bookmark topic
I did it yesterday on my P1i and it worked. I just ran the script to change my CDA to GW1, ran SEUS, and that was it.
--
Posted: 2008-03-09 22:36:49
Edit :
Quote
Hmm, I tried it a few more times and I could never get it to work. In the end, I resorted to the old blob_fs trick and that did the trick.
I'm not sure what the reason for the XS++ method not working for me was.
One possible thing I could guess to try in the future would be to perform a forced update prior to using XS++ to change the CDA. Perhaps SEUS is happier if there is already some downloaded content in the blob_fs directory? Wild guess, with no evidence behind it...
Other thing could be that some of the GDFS scripts aren't working properly? But it did seem to change the CDA the same way the blob_fs trick does. (At least, the system information screen looks the same when using both methods).
--
Posted: 2008-03-10 03:45:02
Edit :
Quote
On 2007-10-01 11:06:37, cadcad wrote:
The process requires replacing two specific files in a folder named blob_fs which is located in SEUS installation folder.
System Requirements
* XVI32 Hex Editor (http://www.chmaas.handshake.de/delphi/freeware/xvi32/xvi32.htm)
* Sony Ericsson Update Service software
* DCU-60 USB Cable
The Steps
* 1. Install SEUS, back-up phone data and fully-charge phone
* 2. Update (or force update) P1i firmware to its latest (1st update)
* 3. Download and extract P1i.rar from here
http://rapidshare.com/files/48693772/P1i.zip.html
* 4. Determine the files to be replaced in blob_fs folder
* 5. Rename two files from downloaded archive (step #3)
* 6. Replace two files in blob_fs folder with files contained in the extracted archive (step #3)
* 7. Force update P1i firmware (2nd update)
* 8. Finally, force update P1i firmware again (3rd update, now for the new firmware)
How To Determine The Files To Be Replaced (the tricky part):
Two files are needed to be replaced in the blob_fs folder. But the names and size of these files differ from one firmware to the other.
In my old blob_fs folder, I sorted the files by size and I had like 11 1k files...
Now you'll have to compare them to the P1i WG1 downloaded files which are also of a 1k but of a number of 8.
I had 6 identical files by name and 2 that I couldn't find in the blob_fs folder...
To identify these 2 files, I had to use the XVI32 Hex Editor.
Now you should forget about the 6 identical files to be able to determine the exact files to be replaced in the blob_fs folder and in my case there were 5 files left. (11-6=5)
First go to the P1i WG1 folder and open the first file (of the 2 left) with the editor and write down the first 12 bytes of the file, they should look like this:
E3 4C 88 75 FB 5E CC C0 FD 57 E4 70 (not exactly like this line just an example)
Do the same for the second file...
Now go to the blob_fs folder and begin checking the 5 left files one by one with the hex editor program... 2 out of 5 will have the same line respectively like the 2 left files in P1i extracted folder. (Note that in some CDAs it has been found the the last 2 bytes are being different but consecutive. Ex: E5 instead of E4 in the 11th byte)
Once determined, rename them in the P1i folder just like they are in the blob_fs folder respectively then select all 8 files copy, paste and replace them in the blob_fs folder...
This is it, you'll have to update ur P1i twice after that...
after the first update you'll have 2 CDA lines. (Just an update, it doesn't download anything).
Now run SEUS again, it'll go through the whole download and update progress, this way you'll have the WG1 CDA...
P.S: U can back up your blob_fs folder before messing with it just in case you want to go back to ur old CDA.
In case you need anything, just let me know...
Good luck.
[ This Message was edited by: cadcad on 2007-10-14 22:03 ]
Hi, i am a new here. I dont understand, i downlouded files wich writed in 3 step, then i go to blob_fs folder, but just 4 of 8 files are in same name, not 6.. what to do? My phone is P1i branded 02 UK. Thanks for help, best regards
[ This Message was edited by: Robis on 2008-03-10 11:12 ]
--
Posted: 2008-03-10 12:10:42
Edit :
Quote
There's no a much easier way, Robis.
Download XS++
here.
Run XS++, tick "smartphone connect", make sure your P1 is off, hold down C, and connect it. XS++ should recognise the phone.
Click the GDFS radio button and backup the GDFS. This is important.
Once that's done, you'll need to reconnect your phone to XS++ again. Then, go to the Flash radio button and at the top, select the P1i script for GW2.
Now, just run SEUS and your phone will be updated with the latest generic firmware.
--
Posted: 2008-03-10 12:15:58
Edit :
Quote
On 2008-03-10 12:15:58, Sebby wrote:
There's no a much easier way, Robis.
Download XS++
here.
Run XS++, tick "smartphone connect", make sure your P1 is off, hold down C, and connect it. XS++ should recognise the phone.
Click the GDFS radio button and backup the GDFS. This is important.
Once that's done, you'll need to reconnect your phone to XS++ again. Then, go to the Flash radio button and at the top, select the P1i script for GW2.
Now, just run SEUS and your phone will be updated with the latest generic firmware.
I was try and with XS++ before that, but some problem:
11:55:54| Executing SEMC Smartphone Operations!
11:55:54| Please hold boot key ('@' or 'C') and connect device...
11:55:58| Master Port detected: COM9
11:55:58| Slave Port detected: COM10
11:55:58| Opening Port!
11:59:28| Init Master Failed!
11:59:28| Error: Cannot open phone communication port
11:59:30| Disconnected... Unplug the phone
XS++ version is 3.1, maybe the problem is that cable isn't DCU-60, but DCU-65?
[ This Message was edited by: Robis on 2008-03-10 11:44 ]
--
Posted: 2008-03-10 12:42:03
Edit :
Quote
I know some people have cured that in the past by taking the battery out of the phone and putting it back in before connecting it to XS++.
--
Posted: 2008-03-10 13:25:14
Edit :
Quote
On 2008-03-10 13:25:14, Sebby wrote:
I know some people have cured that in the past by taking the battery out of the phone and putting it back in before connecting it to XS++.
i was try ant that, but still same problem... :/
--
Posted: 2008-03-10 13:41:51
Edit :
Quote
I can't help then.
You might be better off posting on SE-NSE forums as there are some XS++ gurus there.
--
Posted: 2008-03-10 14:19:34
Edit :
Quote
remove and reinsert the battery. then when XS++ is detecting the phone, hold down the '7' key (the one with letter C) instead of the back key. i had this same problem before.
--
Posted: 2008-03-10 14:28:50
Edit :
Quote
Have you installed the Symbian drivers?
--
Posted: 2008-03-10 15:08:54
Edit :
Quote
New Topic
Reply
