| Author |
Message |
roswell108
Posts: 278
Phone Model:
Moto Razr Black (Nokia 6820b, Samsung x426 (x2) / x427M, SE T306, Nokia 3390, Moto v2282)
Service Provider:
Cingular (AT&T Wireless, T-Mobile, Voicestream) |
 
Mon Jan 03, 2005 4:52 am |
Ok everyone. I have a problem I need some help with. Currently Optiflash 3.6 is the only working version for backing up and flashing an x426, x427, and x427M. I am sure you are all aware of the fault that caused the X426 to have a bad sailboat screensaver. This problem is not the firmware, it is in fact Optiflash. Optiflash cannot seem to back-up this part of the phone. The problem is, this part of the phone happens to be the part that displays the text message arrival on an X427M. So when you flash a backup to this phone, it will crash whenever a text message is received. Anyone think of a way around it? I have tried flashing the backup then a separate mod of the text display to overwrite the problem with no success. Thanks for your help.
EDIT
Problem solved. It was, in fact, Optiflash that was the problem. I can now back-up and flash the new X427M firmware without any problems. Thanks guys!
Last edited by roswell108 on Wed Feb 02, 2005 7:36 pm, edited 1 time in total |
 |
Advertisement
|
|
|
|
|
knight_2004
Posts: 9
Phone Model:
samsung x427
Service Provider:
T-Mobile, AT&T |
Thu Jan 06, 2005 4:41 am |
| roswell108 wrote: | | Optiflash cannot seem to back-up this part of the phone. The problem is, this part of the phone happens to be the part that displays the text message arrival on an X427M. So when you flash a backup to this phone, it will crash whenever a text message is received |
roswell108, I was thinking about what you said above. Well, I have two x426 phones. I had updated one of them with X427M Firmware from your site. I sent myself a text message, and yes, it crashes, exactly as you said. I just re-flashed both of them, with X427M Firmware. On one of them I used "OptiFlash 3.6" and on the other I used "OptiFlash Version 4.14 T" Sometimes OptiFlash gives an Error after it reaches 99%. (TOO_MANY_RETRIES, or other errors) I don't understand the errors at the end, but I figure if the error happens after the 99%, I assume it's okay (correct me if I am wrong).
Now, the phone I flashed using "OptiFlash Version 4.14 T" does not crash when a text message is received. I tried both phones. The other one still crashes. I assume, what you said above is right, | Quote: | | This problem is not the firmware, it is in fact Optiflash |
I need your feedback, I am just experementing with with trial and error here. I don't know if this would correct the problem though, but at least it does not crash on text messages.
Here are the settings I used with "OptiFlash Version 4.14 T":
Options Settings:
Flash and Verify:
Flash to Load and Verify: X427M Rev 1.2.sre
Specify Hardware Platform: Customer T:X40x
Read:
I removed all Regions
Save File: Any Filename
Generic:
Specify Hardware Platform: Customer T: X40x. (Since it does not have a Hardware Platform Reference to x426, I tried others, but with errors, I tried this one and it was ok  )
Misc Settings:
Flash Erase Passes: 1
Operation Passes: Default
Check boxes: All Unchecked
COM Port:
COM Port: COM 1
Max. Transfer Speed: 115200
Second COM Port: COM 1
Max. Transfer Speed: 115200
Another question about the X427M. *#9998*9999# does not seem to work. Also, *8888#. If you check the help menu *#9998*4357# the codes "9999" and "8888" are included. Here are my findings:
VER (9999): SW Version (Does not work)
VER (8888): HW Version (Does not work)
VB (842): Vibrator (It works)
BUZ (289): Buzzer (It works)
BAT (228): Battery Start (It works)
RTC (782): RTC Display (It works)
LCD (523): LCD Contrast (It works)
ERR (377): NVM error log (It works )
LOGO (5646): GSM Logo set (It works)
SST (778): SIM Serv. Table (It works)
NET (638): SIM network ID(It works)
SIM (746): SIM info (It works)
PN (76): Production No (It works, but gives 00000000)
BRKN (2576): SIM error(It does not work, with SIM or without SIM)
Note: The above experiment was made on a x426 phone (AT&T), and the firmware "X427M Rev 1.2.sre" downladed from "http://www.personal.psu.edu/users/s/j/sjs342/"
Yet another question from a previous experience with OptiFlash 3.6. Why did OptiFlash 3.6 change the IMEI on the phone at one point and at another time it did not change it? Even though I used two different .sre files???? Could it be that Firmware contains the IMEI? If so, then how come I cannot change the IMEI back using a data cable and OptiFlash can change it using the same cable? Sooo, many questions, I wish I can find an answer. I need to change the IMEI back, as I cannot use the phones with the IMEI's changed like this. One of them has a different IMEI and the other is all zeros.
Well, that's it for now, waiting for your feedback.
|
|
steven7165
Posts: 3
Phone Model:
SGH-D410C & SGH-X426
Service Provider:
Rogers AT&T |
Thu Jan 06, 2005 5:33 pm |
| knight_2004 wrote: |
...
Another question about the X427M. *#9998*9999# does not seem to work. Also, *8888#. If you check the help menu *#9998*4357# the codes "9999" and "8888" are included. Here are my findings:
VER (9999): SW Version (Does not work)
VER (8888): HW Version (Does not work)
...
|
Try this
VER (1111): SW Version
VER (2222): HW Version
Where did you get OptiFlash Version 4.14 T ?
When backing firmware using optiflash, why do you need to specify memory region AND how do one know which region to backup ? Is all Samsung phone have the same memory region ?
Is there any tools to convert .s3 / .sre to .bin ?
|
|
roswell108
Posts: 278
Phone Model:
Moto Razr Black (Nokia 6820b, Samsung x426 (x2) / x427M, SE T306, Nokia 3390, Moto v2282)
Service Provider:
Cingular (AT&T Wireless, T-Mobile, Voicestream) |
Fri Jan 07, 2005 3:01 am |
Samsung DIY include mot to bin which converts them (or you could get it stand-alone but it is harder to use that way). Thanks for the idea. I guess I will have to get that Optiflash and try it out. The IMEI IS included in the firmware and can be reverted using the Cerebros from my site. Thanks for your brave testing. I have had to take advantage of that "replacement plan" twice now from testing without having a second phone. I think I have one now, it just has no sound.  Either way... give me about three hours to test this new Optiflash and I will have it hosted on my site as a replacement for the version 4 I have now that isn't working
|
|
knight_2004
Posts: 9
Phone Model:
samsung x427
Service Provider:
T-Mobile, AT&T |
Fri Jan 07, 2005 3:56 am |
| steven7165 wrote: | ...
Try this
VER (1111): SW Version
VER (2222): HW Version
Where did you get OptiFlash Version 4.14 T ?
When backing firmware using optiflash, why do you need to specify memory region AND how do one know which region to backup ? Is all Samsung phone have the same memory region ?
Is there any tools to convert .s3 / .sre to .bin ? |
You are right, the (1111) and the (2222) work and give the Software and Hardware versions. But, the (9999) and the (8888) are in the help menu of the phone. Isn't that wiered? Maybe the firmware was modified!!!??
I don't remember where I got "OptiFlash 4.14 T", I have downloaded a lot of stuff in the past two weeks. If you need a copy, let me know and I will send it to you. It's about 3MB in size. I don't know if I can upload it here.
| steven7165 wrote: | ...
When backing firmware using optiflash, why do you need to specify memory region AND how do one know which region to backup ? Is all Samsung phone have the same memory region ?
Is there any tools to convert .s3 / .sre to .bin ? |
You specify memory regions in order to keep your personal settings (ring tones, pictures, etc. ) I think that part of memory hold the ring tones pictures, etc. Specifically in the "0x00B64290 - 0x00CF2FA7" where the original ring tunes that came with the phone are stored.
I don't have access to a full memory map of the x426,, but I keep searching.
I don't know if all Samsung phones have the same memory mapping. The flash files seem to be the same size. I tried to flash a x426 phone with a x460 firmware in order to update it with Arabic language. But, the x460 is not compatible with x426, the phone did not turn on, I had to re-flash it with x426 firmware again. It was a mistake, I was trying to compare the model numbers in the US with some Samsung model numbers in Europe and the Middle East. I think that x450 is compatible with x426, they look the same to me, although they are different in GSM frequencies. I did not find any firmware for that one (x450) yet.
| steven7165 wrote: | ...
Is there any tools to convert .s3 / .sre to .bin ? |
Yes, I am using Samsung Mobile Phone DIY 3.2 Full. I got it from
http://www.personal.psu.edu/users/s/j/sjs342/
It will convert .sre ---> .bin, .bin ---> .sre for you. It also can replace, save the ring tunes that are in the firmware. Yu can save a text file of the list along with the memory offset addresses for each tune in the firmware. But, it has to be in .BIN formats.
|
|
knight_2004
Posts: 9
Phone Model:
samsung x427
Service Provider:
T-Mobile, AT&T |
Fri Jan 07, 2005 4:27 am |
| roswell108 wrote: | | Samsung DIY include mot to bin which converts them (or you could get it stand-alone but it is harder to use that way). Thanks for the idea. I guess I will have to get that Optiflash and try it out. The IMEI IS included in the firmware and can be reverted using the Cerebros from my site. Thanks for your brave testing. I have had to take advantage of that "replacement plan" twice now from testing without having a second phone. I think I have one now, it just has no sound. Either way... give me about three hours to test this new Optiflash and I will have it hosted on my site as a replacement for the version 4 I have now that isn't working |
Well, I think that the version yo have on your site is okay and it is working. I think, as you said before, it is the OptiFlash that was causing the problem to crash the wallpaper on text messages. I used the same 427M v1.2 from your site on two phones. One was freezing when a text message was received (even when a voice message was received), and the other was okay. One was flashed using OptiFlash 3.6 and the later using 4.14 T.
I cannot wait to see your results.
You know, the amazing thing is that when I made a backup copy of the firmware 427M 1.2 from the phone, then flashed it back to the phone, it changed the IMEI number into zero's. I used your original copy from your site and it kept the IMEI number as is. In other words:
1. I flashed a x426 phone with "x426 Firmware V1.6", it changed the IMEI to your IMEI (which was in the firmware)
2. Flashed the same phone with "x427M Firmware V1.2" it did not change the IME number. The IMEI number was kept the same as the result from step 1.
3. Made a backup copy of the "x427M Firmware V1.2" from the phone.
4. Flashed the phone with the backup copy from step 3. The IMEI was changed into zero's.
5. Flashed the phone again with "x426 Firmware V1.6" as in step 1. IMEI back as in step 1.
6. Flashed the phone with "x427M Firmware V1.2" (from your site) and the IMEI was not changed. It was kept the same as in step 5 and 1.
I wonder why though. what does Optiflash add/do to the file when making a backup?
I am doing this to try and map the IMEI offset address in the firmware, although changing the backup from .SRE to .BIN takes forever in each step. I am using two computers and it is still a slow process. Becuase I think all the mapping should be done on a .BIN file where the .sre file is long and unreadable. I use WinHex for comparisions. I only have a generic data cable without the switch on the box. I have no access now to an unlocking cable, so I cannot use any of the unlocking software  . I need to change the IMEI number back to its original as fast as I can. I am placing an order for an unlocking cable, but I am sure it will take forever untilI receive it. I am trying and I will keep you posted.
Thank you for sharing and for keeping up your site.
|
|
roswell108
Posts: 278
Phone Model:
Moto Razr Black (Nokia 6820b, Samsung x426 (x2) / x427M, SE T306, Nokia 3390, Moto v2282)
Service Provider:
Cingular (AT&T Wireless, T-Mobile, Voicestream) |
Fri Jan 07, 2005 4:45 am |
Okay, I am uploading a copy of the Optiflash to my site. I found it and all your results worked for me, too. Seems it was that version of optiflash that was causing the error, but it was isolated to flashing (not backing up). Also, as far as IMEI, that is a weird topic. I have had it change when I have flashed a backup from one of my other phones in one test and not change it in another. Optiflash doesn't add or modify to my knowledge, or at least the file is the same once it is converted to a bin because you modify text that can't be reached through DIY using a hex editor. I could possibly create a mod for that 8888 and 9999 issue to correct the issue, but I will have to make sure it works before I release it. Give me a little more time, lol.
NEW FIND!: If you have time to convert to bin, throw a copy of the x427M bin in a hex editor and do a text search for 9999, you will come across something interesting.... A TON OF *#numbers! Seems you can find the codes through a hex editor! This could be a great find!
|
|
steven7165
Posts: 3
Phone Model:
SGH-D410C & SGH-X426
Service Provider:
Rogers AT&T |
Sat Jan 08, 2005 12:57 am |
I flash using the previous "x427M Firmware V1.2" and it did not change my imei but the latest one change it to zeros. Now I have to learn how to set it back to my own imei (cerebros ?).
Also, I tried using optiflash 3.7 to flash but it returns error saying invalid memory range (even though there's nothing in the region setting) but 4.14T is o.k. BTW, why does 3.7 and 4.14 have quite a substantial different in the GUI ? For example there is no "browse" on the main page but have to load it under "option" unlike 3.7. Also, the phone models are not as complete as in 3.7.
NOTE : I got an error when flashing the latest ""x427M Firmware V1.2" on the last few sector. Here is the log:
I E1885 00:17:20 Sector: 1/127
I E1886 00:17:20 OpenSector: 1/127, 0x00ff0000, 8192, 0x11
I E1887 00:17:20 SendData: 0x00ff0000 - 0x00ff1fff
I E1888 00:17:21 CloseSector: 1/127
I E1889 00:17:21 Cmd CLOS FAILED: Err:502, 127=0x7f, 16711680=0xff0000, 10=0xa, 162=0xa2
I E1890 00:17:21 Sync'ing
I E1891 00:17:21 sync'ed
I E1892 00:17:21 Sector: 1/127
I E1893 00:17:21 OpenSector: 1/127, 0x00ff0000, 8192, 0x11
I E1894 00:17:21 SendData: 0x00ff0000 - 0x00ff1fff
I E1895 00:17:22 CloseSector: 1/127
I E1896 00:17:22 Cmd CLOS FAILED: Err:502, 127=0x7f, 16711680=0xff0000, 10=0xa, 162=0xa2
I E1897 00:17:22 Sync'ing
I E1898 00:17:22 sync'ed
I E1899 00:17:22 Sector: 1/127
I E1900 00:17:22 OpenSector: 1/127, 0x00ff0000, 8192, 0x11
I E1901 00:17:22 SendData: 0x00ff0000 - 0x00ff1fff
I E1902 00:17:23 CloseSector: 1/127
I E1903 00:17:23 Cmd CLOS FAILED: Err:502, 127=0x7f, 16711680=0xff0000, 10=0xa, 162=0xa2
I E1904 00:17:23 Sync'ing
I E1905 00:17:23 sync'ed
I E1906 00:17:23 Sector: 1/127
I E1907 00:17:23 OpenSector: 1/127, 0x00ff0000, 8192, 0x11
I E1908 00:17:23 SendData: 0x00ff0000 - 0x00ff1fff
I E1909 00:17:23 CloseSector: 1/127
I E1910 00:17:23 Cmd CLOS FAILED: Err:502, 127=0x7f, 16711680=0xff0000, 10=0xa, 162=0xa2
I E1911 00:17:23 Sync'ing
I E1912 00:17:23 sync'ed
I E1913 00:17:23 Sector: 1/127
I E1914 00:17:23 OpenSector: 1/127, 0x00ff0000, 8192, 0x11
I E1915 00:17:23 SendData: 0x00ff0000 - 0x00ff1fff
I E1916 00:17:24 CloseSector: 1/127
I E1917 00:17:24 Cmd CLOS FAILED: Err:502, 127=0x7f, 16711680=0xff0000, 10=0xa, 162=0xa2
I E1918 00:17:24 Sync'ing
I E1919 00:17:24 sync'ed
I E1920 00:17:24 Sector: 1/127
I E1921 00:17:24 OpenSector: 1/127, 0x00ff0000, 8192, 0x11
I E1922 00:17:24 SendData: 0x00ff0000 - 0x00ff1fff
I E1923 00:17:25 CloseSector: 1/127
I E1924 00:17:25 Cmd CLOS FAILED: Err:502, 127=0x7f, 16711680=0xff0000, 10=0xa, 162=0xa2
I E1925 00:17:25 SendFile: 20 (ERR_CMD_FAILED)
I E1926 00:17:25 Closed COM1
I E1927 00:17:25 ReLoad: 20 (ERR_CMD_FAILED)
I E1928 00:17:25 Error code: ERR_CMD_FAILED
E E1929 00:17:25 Sorry, an error has occured ! (ERR_CMD_FAILED)
I E1930 00:17:25 ThreadProtocol finished
I E1931 00:17:25 ThreadProtocol: 20
I E1932 00:17:25 ThreadGUI finished
After removing the battery and power on, the phones seems to work. But using cerebros and selecting Q100 as the model, I can not change the imei. It always zeros. Anyone can help ?
|
|
knight_2004
Posts: 9
Phone Model:
samsung x427
Service Provider:
T-Mobile, AT&T |
Mon Jan 10, 2005 1:24 am |
| steven7165 wrote: |
But using cerebros and selecting Q100 as the model, I can not change the imei. It always zeros. Anyone can help ? |
I have the same problem. It is the cable you and I are using. It is a generic data cable without a switch on the box. You need an Unlocking cable. A samsung OEM cable will do it. I forgot the part number for the samsung OEM cable. But, it is available on eBay.
|
|
steven7165
Posts: 3
Phone Model:
SGH-D410C & SGH-X426
Service Provider:
Rogers AT&T |
Mon Jan 10, 2005 2:50 am |
|
I am going back to Optiflash 3.7 which have more models to select ( D410 etc. ) and flashes without error. And yes, I switch the cable to D/L and the unlock is successfull and thanks for the new X427M firmware.
|
| | |
|
|
|
|
