Related
what a bad luck in 2008.
when i was flashing a cooked Excalibur rom to my phone my cat touched my usb cable with his tail...only touch. The cable did not disconect from the phone physically...but maybe the static or whatever effected...the RUU gave me a communication error and let me unplug the cable and battery for recovery.
but the result is bad, the phone stop boot in the first screen, and my uspl has been flashed to 1.33(it was uspl 1.11 before )
now the situation is...i can enter the bootloader(tri-color). but i can not flash other roms, I tried wm5 from dopod singapore and htc wm6 both give me an invalid ID error
my phone was from dopod taiwan....
please help, any advice suggestion will be appreciated...thank u
if anyone can offer a proper ROM file from DOPOD taiwan, that will be very useful...thanks in advance.
if there is someone who are using a dopod c720w from taiwan, please help to dump two files from your phone.
just run simlock.bat from attachment...thanks
please remove .zip extension for those bin file....thanks jockyw2001
same problem with my jasjar i was upgrading and my light wentout and when i tried again it gave me invalid country ID and still no solution!!!!!!
thank you anyway....anyone have a working solution?
i am trying to use RUU_signed-with-uspl.zip
still downloading...and waiting for more help...
update
bad bad....i try to flash the RUU_signed-with-uspl.zip
it gives me
"the image file is corrupted"....how about now?
any help?
did u try a hard reset? i have no idea if it will help, but u might get lucky
-jd
Try flashing the original rom from SD card
If you haven't got it fixed yet, you could try flashing from your SD card. I have done this with my T-Mobile Dash several times and it works. Search the forum and you will find the instructions I posted some time back. Hope this will help. From my understanding this is also the method used by manufacturers, but they have a special SD card they use for different utilities.
P.S. You must use a matching ROM (Vendor ID and CID) for your device with SD flash. T-Mobile Dash should be flashed with T-Mobile ROM, HTC S620 should be flashed with HTC ROM, Rogers... etc.
mar11974 said:
If you haven't got it fixed yet, you could try flashing from your SD card. I have done this with my T-Mobile Dash several times and it works. Search the forum and you will find the instructions I posted some time back. Hope this will help. From my understanding this is also the method used by manufacturers, but they have a special SD card they use for different utilities.
P.S. You must use a matching ROM (Vendor ID and CID) for your device with SD flash. T-Mobile Dash should be flashed with T-Mobile ROM, HTC S620 should be flashed with HTC ROM, Rogers... etc.
Click to expand...
Click to collapse
thank you, but the problem is that i can not find a proper ROM for my device, there is rom from "dopod singapore" "HTC" "TMO" "ROGER"....but none of those are from DOPOD taiwan....I tried the ROM from "DOPOD singapore" with no luck...
jdhelstrom said:
did u try a hard reset? i have no idea if it will help, but u might get lucky
-jd
Click to expand...
Click to collapse
thank u anyway....hard reset won't work....the flash process stopped at 24%...I think the OS part has not fully flashed into the device...
falleny said:
thank you, but the problem is that i can not find a proper ROM for my device, there is rom from "dopod singapore" "HTC" "TMO" "ROGER"....but none of those are from DOPOD taiwan....I tried the ROM from "DOPOD singapore" with no luck...
Click to expand...
Click to collapse
Normal flash via USB or flash via SD card?
mar11974 said:
Normal flash via USB or flash via SD card?
Click to expand...
Click to collapse
via USB use RUU...any problem? haven't tried card flash yet...ok, one more try now.....its 5 A.M now...another sleepless night...
falleny said:
via USB use RUU...any problem? haven't tried card flash yet...ok, one more try now.....its 5 A.M now...another sleepless night...
Click to expand...
Click to collapse
no luck....sd flash gets invalid certification...
thanks jockyw2001
I don't know which keyword should I grep...but i do found some CID error and EXCA100 EXCA10000 there...
I believe the vendor ID is HTCS
48544353
also I can find
H...T...C...I...
M...A...G...E...
EXCA10000
falleny said:
I don't know which keyword should I grep...but i do found some CID error and EXCA100 EXCA10000 there...
I believe the vendor ID is HTCS
48544353
also I can find
H...T...C...I...
M...A...G...E...
EXCA10000
Click to expand...
Click to collapse
The modelID is EXCA10000
The CID is not yet clear from your dumps.
I will check how you can easily find it.
i tried to dump the raw data with diffrent ROM update
something interesting...
I found EXCA20000 both in dopod singapore ROM and HTC WWE ROM
and found EXCA10000 when I tried to update USPL only
so I think EXCA10000 or EXCA20000 is something in the nbh file?
I found the diffrence between Dopod and HTC...
DOPOD001 in the dopod dump
HTC__001 in the HTC dump
11111111 in the USPL dump
in the same position of the raw date....I think this is vendor ID in the ROM and Model ID is the same EXCA20000 in both dopod and HTC rom.
bad news is that I still can not find my CID and Model ID....still struggling with those huge raw date...
i found the flash procedure already broken at 2%...but something still copying until 4%
I found it at row 655634
Code:
DO 48 54 43 45 HTCE
DI 4d 53 5f 43 45 52 54 5f 52 41 57 0d 0a MS_CERT_RAW..
DI 62 72 65 61 6b 0d 0a break..
DI 48 54 43 53 01 00 01 00 00 00 00 00 48 54 43 45 HTCS........HTCE
DO 70 72 6f 67 72 65 73 73 20 32 0d 00 00 00 00 00 progress 2....
mean less character stopped at row 131192
Code:
DO 48 54 43 45 HTCE
DI 4d 53 5f 43 45 52 54 5f 52 41 57 0d 0a MS_CERT_RAW..
DI 62 72 65 61 6b 0d 0a break..
DI 43 68 65 63 6b 49 6d 67 48 65 61 64 65 72 20 0d CheckImgHeader .
0a .
DI 44 65 76 69 63 65 20 4d 6f 64 65 6c 20 49 44 20 Device Model ID
3d 20 45 20 58 20 43 20 41 20 32 20 30 20 30 20 = E X C A 2 0 0
30 20 30 20 00 20 00 20 00 20 00 20 00 20 00 20 0 0 . . . . . .
00 20 00 20 00 20 00 20 00 20 00 20 00 20 . . . . . . .
DI 00 20 .
DI 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 . . . . . . . .
00 20 0d 0d 0a . ...
DI 48 54 43 53 02 80 02 00 00 00 00 00 48 54 43 45 HTCS........HTCE
DO 70 72 6f 67 72 65 73 73 20 34 0d 00 00 00 00 00 progress 4......
hope it helps
No, all you see are the IDs of the image you try to flash and not the ones of your device
I have to play with my Vox bootloader and see if there is a command. Vox and Excal are very similar.
You could look up a thread I did in the Vox forum ("Vox bootloader" or so)
bump...and thanks jockyw2001 for all his help these days
falleny said:
bump...and thanks jockyw2001 for all his help these days
Click to expand...
Click to collapse
My pleasure. The IDs of the excalibur you posted above are:
CID = DOPOD601
ModelID = EXCA20000
So your challenge is to find an official ROM which has these characteristics.
The description of such a ROM is very likely "traditional chinese (TCH) for Excalibur".
Any officially signed RUU_signed.nbh file which has the string DOPOD601 at offset 0x1E0 and the string EXCA20000 at offset 0x40 will do.
It seems Kies use OBEX...
AT+SYNCML=MOBEXSTART
First time I saw OBEX was in Brew Mobile Commander in 2006.
Also there was an Plugin for Total Commander...
But this seems not work with S8500.
Other used Protocol is TFS... Samsungs Test Commands. For instance in TkFileExplorer_2.2.exe used.
Hmmm. I need more info/practice about OBEX...
Best Regards
TFS - I saw references to that on the boot loader stuff that was decrypted elsewhere on this forum... Tiny File System, Transparent File System.....?????
New year... old questions.
In Kies you can find several OBEX Commands... like:
m-obex/system/memory
m-obex/application/count
apps_c...
m-obex/fs/info
m-obex/fs/mem_size
In bada 2.0 it seems removed obex... replaced by other stuff...
Anyway. For learning I wish I could use obex Commands successfully.
At the moment no idea how.
Maybe someone could help me.
Best Regards
Edit 1.
Found something via Google...
http://wammu.eu/docs/manual/protocol/m-obex.html
But I sent on XXJL2 AT Command, but can't see any results...
AT+SYNCML=MOBEXSTART
For instance I use WinComm...
AT Commands work on my Port 5...
But if I send this:
AT+SYNCML=MOBEXSTART
AT Commands not more work on COM 5...
Also I get no answer for obex Commands like this:
m-obex/application/count
Is obex open new port?
Or if I sent on 5 I should receive on COM 5 ?
Again many Questions.
Thanx for reading.
Best Regards
todo: implement it in bterm
Code:
Request: AT
41 54 0D 0A
Answer: AT OK
41 54 0D 0D 0A 4F 4B 0D 0A
Request: ATZ
41 54 5A 0D 0A
Answer: ATZ OK
41 54 5A 0D 0D 0A 4F 4B 0D 0A
Request: AT+SYNCML=MOBEXSTART
41 54 2B 53 59 4E 43 4D 4C 3D 4D 4F 42 45 58 53 54 41 52 54 0D 0A
Answer: AT+SYNCML=MOBEXSTART OK
41 54 2B 53 59 4E 43 4D 4C 3D 4D 4F 42 45 58 53 54 41 52 54 0D 4F 4B 0D 0A
Request:
80 00 0F 11 00 20 00 46 00 08 4D 4F 42 45 58
Answer:
A0 00 14 10 00 20 00 CB 00 00 00 01 4A 00 08 4D 4F 42 45 58
#########################################
# Additional command goes here...
#########################################
Request:
81 00 03
Answer:
A0 00 03
Request: ATZ
41 54 5A 0D 0A
Answer: ATZ OK
41 54 5A 0D 0D 0A 4F 4B 0D 0A
commands examples
Code:
Request: m-obex/connection_packet
82 00 23 CB 00 00 00 01 42 00 1B 6D 2D 6F 62 65 78 2F 63 6F 6E 6E 65 63 74 69 6F 6E 5F 70 61 63 6B 65 74
Answer:
A0 00 03
Request: m-obex/security/privacylock
83 00 27 CB 00 00 00 00 42 00 1F 6D 2D 6F 62 65 78 2F 73 65 63 75 72 69 74 79 2F 70 72 69 76 61 63 79 6C 6F 63 6B 00
Answer:
A0 00 12 C3 00 00 00 02 4C 00 05 00 00 49 00 05 00 00
Request: m-obex/fs/privacy_lock
83 00 22 CB 00 00 00 00 42 00 1A 6D 2D 6F 62 65 78 2F 66 73 2F 70 72 69 76 61 63 79 5F 6C 6F 63 6B 00
Answer:
A0 00 0D C3 00 00 00 02 49 00 05 4E 4F *
Request: m-obex/application/count
83 00 27 CB 00 00 00 00 42 00 1C 6D 2D 6F 62 65 78 2F 61 70 70 6C 69 63 61 74 69 6F 6E 2F 63 6F 75 6E 74 00 4C 00 03
Answer:
A0 00 14 C3 00 00 00 04 4C 00 05 00 00 49 00 07 2C 00 00 00
Request: m-obex/system/imsi
83 00 21 CB 00 00 00 00 42 00 16 6D 2D 6F 62 65 78 2F 73 79 73 74 65 6D 2F 69 6D 73 69 00 4C 00 03
Answer: IMSI ;)
A0 00 1F C3 00 00 00 0F 4C 00 05 00 00 49 00 12 .......
Request: ƒm-obex/system/mnc
83 00 20 CB 00 00 00 00 42 00 15 6D 2D 6F 62 65 78 2F 73 79 73 74 65 6D 2F 6D 6E 63 00 4C 00 03
Answer: 02
A0 00 12 C3 00 00 00 02 4C 00 05 00 00 49 00 05 30 32
Request: ƒm-obex/system/csc
83 00 20 CB 00 00 00 00 42 00 15 6D 2D 6F 62 65 78 2F 73 79 73 74 65 6D 2F 63 73 63 00 4C 00 03
Answer: S8500OXAJID
A0 00 1B C3 00 00 00 0B 4C 00 05 00 00 49 00 0E 53 38 35 30 30 4F 58 41 4A 49 44
Request: m-obex/system/openapiversion
83 00 2B CB 00 00 00 00 42 00 20 6D 2D 6F 62 65 78 2F 73 79 73 74 65 6D 2F 6F 70 65 6E 61 70 69 76 65 72 73 69 6F 6E 00 4C 00 03
Answer: 1.2.0_1009152352_LIS_S8500XXJID_XEO
A0 00 33 C3 00 00 00 23 4C 00 05 00 00 49 00 26 31 2E 32 2E 30 5F 31 30 30 39 31 35 32 33 35 32 5F 4C 49 53 5F 53 38 35 30 30 58 58 4A 49 44 5F 58 45 4F
Request: m-obex/application/getinstallsetting
83 00 33 CB 00 00 00 00 42 00 28 6D 2D 6F 62 65 78 2F 61 70 70 6C 69 63 61 74 69 6F 6E 2F 67 65 74 69 6E 73 74 61 6C 6C 73 65 74 74 69 6E 67 00 4C 00 03
Answer:
A0 00 14 C3 00 00 00 04 4C 00 05 00 00 49 00 07 01 00 00 00
---------- Post added at 06:31 PM ---------- Previous post was at 06:29 PM ----------
PS. tested on bada 2.0
Thank you very much.
I got it now.
Tested on bada 1.x
Older then XXJL2 seems to have other syntax...
But I can confirm work also on XXKL6.
Wow. Every little mistake have lead to no further connection...
Best Regards
Oh "surprise"...
Again obelix power...
m-obex/system/restore/start
.
.
See here:
http://forum.xda-developers.com/showpost.php?p=21541765&postcount=4
Best Regards
My problem ; no adb connection in booted OS nor in recovery .
everything else works fine; sdcard, bluetooth , mounting sd on PC all ok.
my handset : pvt4, oxygen Hboot, S-off
I allready tried "fastboot oem eraseconfig"
but stil no adb connection possible..
before I do anything stupid I want to make sure if I have the usb-brick
cause it seems I haven't apart from the not working adb.
I can adb with my other pvt3 desire so my pc setup is ok.
Is it possible to have usb brick whilst everything else apart from adb is working fine?
Is there something that can be checked? I have uploaded my misc.img
for the specialists amongst us to see if its ok or not
Hope anyone can shed some light on this.
ps similar post of me in usb brick thread in developer section but I thought
I had more chance on an answer here.
grtz lanbase
well you dont have USB brick
what happens when you do adb devices ?
also make sure your ADB is installed properly (try reinstalling?) and maybe try with diffrent ROM ?
hi,
just edit your misc img =>
00000000:48 54 43 5f 5f 33 30 34 00 ff ff ff ff ff ff ff HTC__304.ÿÿÿÿÿÿÿ
00000010:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000020:44 65 76 69 63 65 57 61 72 6d 42 6f 6f 74 00 ff DeviceWarmBoot.ÿ
00000030:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
00000040:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
00000050:43 45 20 53 65 72 69 61 6c 20 49 6e 55 73 65 00 CE Serial InUse.
00000060:44 65 62 75 67 20 43 61 62 6c 65 20 45 6e 61 00 Debug Cable Ena.
00000070:43 45 20 20 20 55 53 42 20 20 49 6e 55 73 65 00 CE USB InUse.
00000080:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000090:43 6c 65 61 72 41 75 74 6f 49 6d 61 67 65 20 00 ClearAutoImage .
000000a0:32 2e 32 39 2e 34 30 35 2e 32 00 00 00 00 00 2.29.405.2.....
so to my point of veiw your file is right (see first line)
compare to mine it s all right (mine is HTC_204)
i won't say it s usb brick, when plug did you look at device manager??
know that your comp is fine but maybe the also right just sof issue.
just to be sure
hoe tis help
dzumagos said:
what happens when you do adb devices?
Click to expand...
Click to collapse
You should a serial number followed by "device" - this confirms your PC is recognizing your device.
thanx dzumagos for confirming my misc.img is ok, that's what I thought; no usb brick, then why the hell is adb not working on this device and working fine on my other one???
adb devices command doesn't
give me anything.
I have 2 desires, one of them is ok and gives me the serial as it should.
the one with non working adb just returns with command promt.
Sent from my HTC Desire using Tapatalk
hi,
i won't say it s usb brick, when plug did you look at device manager??
know that your comp is fine but maybe the also right just sof issue.
just to be sure
Click to expand...
Click to collapse
Thanx mate, for making me look at device manager when I plug in the phone. I noticed "adb with an exclamation mark" when plugging in my pvt4 and "android adb interface" when plugging in my pvt3
in device manager.
I reinstalled the adb driver with the pvt4 plugged in and now both devices have working adb!!! who would have thought that adb driver was corrupted somehow and able to recognize one phone and not the other....
Anyhow problem solved! thanx guys!
Sent from my HTC Desire using Tapatalk
Any idea how Kies identify model? It seems not via AT Commands...
Or I am dumb...
AT+DEVCONINFO
I have used portmon to sniff communication...
Maybe it is the name, what Explorer shows?...
So the mass thingie USB driver...
How for instance S8600 answers in Explorer?
Best Regards
May be it?
http://forum.xda-developers.com/showpost.php?p=11286021&postcount=78
amss.bin I have checked... maybe not.
I have tried MANY combinations... maybe I have something not seen.
Maybe much easier.
Little example how bada Version is checked... Attention, high protection...
extreme hardcoded to prevent change...
2 parts needed...
Part 1:
SystemFS\User\OspSys\registry\buildnumber.ini
Part 2:
SystemFS/User/OspSys/registry/systeminfo.ini
Compare with latest Firmware and you know how to prepare your bada 1.x device for bada 3.0 Apps.
Anyway, I'm blind to manage Kies to work as S8600...
Best Regards
Okay, I've found Original Screenshot of S8600...
But I know where this Text String is stored...
But I can remember, I've tried this... and was not enough...
Maybe I'll try again.
Best Regards
It can be usb device description string in USB driver on phone or PC side (if it's PC side, description is paired with certain PID and VID), try to connect phone to linux in kies mode and use lsusb -a (aint sure if it's -a, anyway the thing is to get verbose info about device)
Hi, I think stune reads the same data that the kies when connected to the terminal.
I mean:
STUNE when you start telling us the firmware version terminal model of our product code, even our imei
Not fully correct
There is something in the PC driver that needs to be changed
You can see this in the driver details
Best Regards
Maybe Kies via Wi-Fi easier...
Not tested yet.
Best Regards
Bus reported device description is sent from device during USB enumeration. So model id is stored in Bada USB module. I'm nearly sure it's unicode string.
Maybe my fault...
AT+PROF="Device
Leads to file device.xml...
Will compare Wave 1, 2, 3 device.xml ...
Best Regards
Edit 1...
Code:
<ModelName value="GT-S8500"/>
<BaseModelName value="GT-S8500"/>
<ProjectName value="Lismore"/>
<FriendlyName value="Lismore"/>
<ProductLineup value="HHP"/>
Code:
<ModelName value="Wave 3"/>
<BaseModelName value="GT-S7250"/>
<ProjectName value="Wave3"/>
<FriendlyName value="Wave3"/>
<ProductLineup value="HHP"/>
Kies now shows other Error
Please, maybe someone can post from S8600 under Explorer...
Remember to remove IMEI...
I think this is MTP device... USB blabla portable Device Driver under Device Manager in Windows...
PS...
Text Samsung... in white Background is editable...
Edit 1.
Hmmm... Wave 2 can't edit ... grey colored...
Screenshot from S8600 would be nice.
Thanx in advance.
why do you think AT+DEVCONINFO is wrong? whole infos including imei in one packet
http://forum.xda-developers.com/showpost.php?p=20497198&postcount=15
Because I've found all files and positions to make 1:1 clone... including IMEI...
But this is not working for Kies.
Kies shows Error, that unsupported device is attached.
Best Regards
error it is kind of progress
what about these ones
Code:
Request: m-obex/connection_packet
82 00 23 CB 00 00 00 01 42 00 1B 6D 2D 6F 62 65 78 2F 63 6F 6E 6E 65 63 74 69 6F 6E 5F 70 61 63 6B 65 74
Answer:
A0 00 03
Request: m-obex/security/privacylock
83 00 27 CB 00 00 00 00 42 00 1F 6D 2D 6F 62 65 78 2F 73 65 63 75 72 69 74 79 2F 70 72 69 76 61 63 79 6C 6F 63 6B 00
Answer:
A0 00 12 C3 00 00 00 02 4C 00 05 00 00 49 00 05 00 00
Request: m-obex/fs/privacy_lock
83 00 22 CB 00 00 00 00 42 00 1A 6D 2D 6F 62 65 78 2F 66 73 2F 70 72 69 76 61 63 79 5F 6C 6F 63 6B 00
Answer:
A0 00 0D C3 00 00 00 02 49 00 05 4E 4F *
Request: m-obex/application/count
83 00 27 CB 00 00 00 00 42 00 1C 6D 2D 6F 62 65 78 2F 61 70 70 6C 69 63 61 74 69 6F 6E 2F 63 6F 75 6E 74 00 4C 00 03
Answer:
A0 00 14 C3 00 00 00 04 4C 00 05 00 00 49 00 07 2C 00 00 00
Request: m-obex/system/imsi
83 00 21 CB 00 00 00 00 42 00 16 6D 2D 6F 62 65 78 2F 73 79 73 74 65 6D 2F 69 6D 73 69 00 4C 00 03
Answer: IMSI ;)
A0 00 1F .....
Request: ƒm-obex/system/mnc
83 00 20 CB 00 00 00 00 42 00 15 6D 2D 6F 62 65 78 2F 73 79 73 74 65 6D 2F 6D 6E 63 00 4C 00 03
Answer: 02
A0 00 12 C3 00 00 00 02 4C 00 05 00 00 49 00 05 30 32
Request: ƒm-obex/system/csc
83 00 20 CB 00 00 00 00 42 00 15 6D 2D 6F 62 65 78 2F 73 79 73 74 65 6D 2F 63 73 63 00 4C 00 03
Answer: S8500OXAJID
A0 00 1B C3 00 00 00 0B 4C 00 05 00 00 49 00 0E 53 38 35 30 30 4F 58 41 4A 49 44
Request: m-obex/system/openapiversion
83 00 2B CB 00 00 00 00 42 00 20 6D 2D 6F 62 65 78 2F 73 79 73 74 65 6D 2F 6F 70 65 6E 61 70 69 76 65 72 73 69 6F 6E 00 4C 00 03
Answer: 1.2.0_1009152352_LIS_S8500XXJID_XEO
A0 00 33 C3 00 00 00 23 4C 00 05 00 00 49 00 26 31 2E 32 2E 30 5F 31 30 30 39 31 35 32 33 35 32 5F 4C 49 53 5F 53 38 35 30 30 58 58 4A 49 44 5F 58 45 4F
Request: m-obex/application/getinstallsetting
83 00 33 CB 00 00 00 00 42 00 28 6D 2D 6F 62 65 78 2F 61 70 70 6C 69 63 61 74 69 6F 6E 2F 67 65 74 69 6E 73 74 61 6C 6C 73 65 74 74 69 6E 67 00 4C 00 03
Answer:
A0 00 14 C3 00 00 00 04 4C 00 05 00 00 49 00 07 01 00 00 00
m-obex/system/csc and
m-obex/system/openapiversion ?
Thank you.
m-obex I have no success because also not enough knowledge.
See here:
http://forum.xda-developers.com/showpost.php?p=20954943&postcount=3
Best Regards
I've somewhere correct sequence to start obex on wave. I will post later
Good afternoon if it will not for anything in this case but I found this on apps_compressed:
x40BF86FF 'kDHd:! eNULL: @ STRENGTH'
0x40BF8765 'eNULL:! ANULL: @ STRENGTH'
0x40BF8784:'/../ cx / source / Xsupplicant / src / auth_methods / eapfast / eapfast.c '
0x40BF889C:'/../ cx / source / Xsupplicant / src / auth_methods / eapfast / eapfast_key.c '
0x40BFAE8C '/ www.openssl.org / support / faq.html'
0x40BFB506: '23456789ABCDEF '
0x40BFC610 '] VOHyrkd'
0x40BFD099: '56789.: AbcdefABCDEF '
ferrloz said:
Good afternoon if it will not for anything in this case but I found this on apps_compressed:
x40BF86FF 'kDHd:! eNULL: @ STRENGTH'
0x40BF8765 'eNULL:! ANULL: @ STRENGTH'
0x40BF8784:'/../ cx / source / Xsupplicant / src / auth_methods / eapfast / eapfast.c '
0x40BF889C:'/../ cx / source / Xsupplicant / src / auth_methods / eapfast / eapfast_key.c '
0x40BFAE8C '/ www.openssl.org / support / faq.html'
0x40BFB506: '23456789ABCDEF '
0x40BFC610 '] VOHyrkd'
0x40BFD099: '56789.: AbcdefABCDEF '
Click to expand...
Click to collapse
Umm, sorry, it's not helping anything in that case. FYI there are literally tenths of thousands such char strings in apps_compressed. Good you're looking tho. ;P
Maybe my goal is not clear enough...
Most of us have NO S8600...
But S8600 has few nice NEW Apps.
You can download without attached handset EVERY App you can find via Kies.
BUT not install if attached handset is not valid...
My goal is to make S8500 valid to install S8600 Apps via Kies.
Solution 1 is wait...
Maybe Samsung will offer these Apps like Tintin before Christmas 2012...
Really realistic...
I think minimum 2-3 months not available for S8500/S8530 to be exclusive for S8600...
Solution...
Move your bu ehm brain.
This mission is NOT impossible.
Best Regards
Sorry for them to lose the time, now I will focus more on the subject.
ferrloz thanks.
This topic came up yesterday and I was dumb enough to indicate that I knew how to change the MAC address..
So, to stop further questions in my Inbox, here's a quick and dirty HowTo
Warning:
Modifying system files can cause irreversible damage to your device and unless you know exactly what you're doing, don't do it!
The tiwlan driver reads the MAC address (and more) from /rom/WiFiBackupCalibration, so any changes to the MAC can be done there.
I'll explain the location and order of the MAC by giving an example:
MAC Address: 58:67:1A:78:54:AC
Code:
$ hexdump -C WiFiBackupCalibration
00000000 01 6d 54 ac 54 78 1a 01 71 54 67 58 00 00 00 00
...
Got it?, no?
Here's the address broken down and positions marked:
Code:
Position: 1 2 3 4 5 6
MAC Address: 58 67 1A 78 54 AC
Position 6 5 4 3 2 1
00000000 01 6d 54 ac 54 78 1a 01 71 54 67 58 00 00 00 00
...
That's it, now you know where the MAC address hides on the NST