Please help!!!!!!!!!!! My bootloader is version 2.01. When I try to flash the radio nbf, it stops a 0%. When I reboot the screen say "No GSM and 1.30.76 WWE.
Everything else works on the jasjar.
Any assistance would be appreciated.
THANKS!!!!!!!!!!
cboy
cboy77 said:
Please help!!!!!!!!!!! My bootloader is version 2.01. When I try to flash the radio nbf, it stops a 0%. When I reboot the screen say "No GSM and 1.30.76 WWE.
Everything else works on the jasjar.
Any assistance would be appreciated.
THANKS!!!!!!!!!!
cboy
Click to expand...
Click to collapse
There are quite a few threads on this already. You may get a solution on any one of them. Try this for starters http://forum.xda-developers.com/showthread.php?t=296393
Hi there..can u let know how did u get No Gsm..accordingly the solution is there..in fact if uhv got no gsm after a radio upgrade then soln exists else u need to change the RF chip
Initially, I noticed that I was not having service when I should have. I would reboot (soft) and get service. Then suddenly one day there was no service at all. I rebooted and noticed it now said "No GSM". That is the situation I am in now.
Don't know what else to do. I have read all the threads. Wasn't sure if it was the bootloader version I have or If it is the device. As I said, everything else works perfectly on the Jasjar.
Any suggestions would be appreciated!!!
cboy77
Sounds to me simply like a corrupted radio installation.
Things to note are...
1. What version of bootloader? If pre 1.1, then upgrade, just saves complications with a lot of installs.
2. NO USB HUB. Very important and seems people are missing this.
3. Use original cable. This appears to be especially important when flashing Radio.
4. AS version should be 4.5 final release. If using Device Centre in Vista, make sure you have the updates installed from Microsoft Update and check the thread on upgrading in Vista.
5. Don't panic!!! It really takes quite a lot to brick your unit and there are usually simple fixes. Don't get too put off by hiccups, they'll be solved by a thread 9 times out of 10
6. (As a last resort!!!) If it does come to having to claim on your insurance... please please please reflash to your original providers rom and extROM before you send it back!!!!!!!
hdubli said:
Hi there..can u let know how did u get No Gsm..accordingly the solution is there..in fact if uhv got no gsm after a radio upgrade then soln exists else u need to change the RF chip
Click to expand...
Click to collapse
hi hdubli,
i'm having the same problem like of cboy77; the NO GSM thing. Like you said that there is solution of this if one had a bad radio flash. that i did...
i felt like i am getting poor signals and dropping call... so i tried to upgrade my radio from 1.13.00 to 1.14.10 and while it was being upgraded... it stopped at 66% with an error and happend to get NO GSM status in the begining and IMEI Lost. since then whenever i try to upgrade my radio rom; it freezes at 0%. However the Ext Rom and Win CE rom gets flashed with no problems at all... just the RADIO ROM that is creating fuss around here... could you help somehow!
Farehmani.
Help No GSM ERROR
I have tried everything in the wiki. Below is the information in my RUU log:
09:52:23:051 [msg] : Version : [2.11].
09:52:23:051 [msg] : Config Info : [857873],[1],[0],[0],[1],[0],[0],[1].
09:52:23:160 [msg] : MSystemFile Not Exist !
09:52:23:160 [msg] : CEFile Not Exist !
09:52:26:238 [msg] : Current Not in CE Mode or in CE Mode but ActiveSync Not Connected.
09:52:30:551 [msg] : Disconnect ActiveSync .... [2]
09:52:30:551 [msg] : Start Get Connect Port.
09:52:30:691 [msg] : Current in BL Mode. Open Port : [\\.\WCEUSBSH001] OK.
09:52:30:816 [msg] : Get Device Backup ID.
09:52:30:816 [msg] : Device BL VER : [2.01 ] [].
09:52:30:816 [msg] : Device ID Is Incompatible.
09:52:30:816 [msg] : Update Image. CE : [0], MSystem : [0], Radio : [1]
09:52:32:488 [msg] : Check Ac in BL mode. AC : [1]
09:52:33:988 [msg] : IsBL. BL : [1]
09:52:34:019 [msg] : =============================================
09:52:34:019 [msg] : START UpdateRadio !
09:52:41:348 [msg] : Check Radio Level 0 [704].
09:52:42:441 [msg] : RUpgrade 0 : 0 Start.
09:55:55:973 [err] : RWipe Data Error.
09:55:56:332 [err] : BL UpdateRadio Error.
09:55:56:332 [msg] : START UnInitialization !
09:55:56:332 [msg] : END UnInitialization !
09:55:56:348 [msg] : IsBL. BL : [1]
Any help in helping me to get pass ther RWipe error would be appreciated.
cboy
Universal Radio Rom Upgrade
I have tried for a few weeks to upgrade the radio rom. I have read all the threads and tried the fixes. None seem to work. I have copyied below the RUU Log:
15:39:35:894 [msg] : Current Not in CE Mode or in CE Mode but ActiveSync Not Connected.
15:39:39:932 [msg] : Disconnect ActiveSync .... [2]
15:39:39:932 [msg] : Start Get Connect Port.
15:39:40:089 [msg] : Current in BL Mode. Open Port : [\\.\WCEUSBSH001] OK.
15:40:05:728 [msg] : Device BL VER : [2.01 ] [].
15:40:05:728 [err] : Device CID Error.
15:40:05:728 [msg] : Update Image. CE : [0], MSystem : [0], Radio : [1]
15:40:42:450 [msg] : Check Ac in BL mode. AC : [1]
15:40:43:953 [msg] : IsBL. BL : [1]
15:40:43:984 [msg] : =============================================
15:40:43:984 [msg] : START UpdateRadio !
15:40:52:906 [msg] : Check Radio Level 0 [704].
15:40:54:487 [msg] : RUpgrade 0 : 0 Start.
15:45:36:433 [err] : RWipe Data Error.
15:45:36:903 [err] : BL UpdateRadio Error.
15:45:36:903 [msg] : START UnInitialization !
15:45:36:919 [msg] : END UnInitialization !
15:45:36:919 [msg] : IsBL. BL : [1]
It seems that I am getting an errow a the Wipe Data command and thereby the Update Radio Command.
If anyone can inform me how to overcome this error I would appreciate it.
Thanks in advance!!!!!
Cboy
Imate jasjar
BL. 201
1.30.76
cboy77 said:
15:40:05:728 [err] : Device CID Error.
Click to expand...
Click to collapse
Is your unit CID-unlocked? Check http://wiki.xda-developers.com/index.php?pagename=Uni_Simlock_by_Buzz_and_team
Sorry, man, I'm just throwing things out here, don't really know what the answer is. Maybe it is the RF chip needs replacing
Help, Can't flash radio rom
Thanks for the suggestion. I think you may be right. It must be the hardware instead of software. Do you think I will be able to replace the RF chip without having to replace the complete board?
Thanks
Can any one provide a solution to this?
I cant upgrade the radio stack on my spvm5000 to 1.18. Always getting the error 114.
Tried everything on Uni Wiki. Still no resolution.
Rest of the ROM flashes work just fine. Problem only with radio upgrade.
Please help.
amitkarir said:
Can any one provide a solution to this?
I cant upgrade the radio stack on my spvm5000 to 1.18. Always getting the error 114.
Tried everything on Uni Wiki. Still no resolution.
Rest of the ROM flashes work just fine. Problem only with radio upgrade.
Please help.
Click to expand...
Click to collapse
If you already read here: http://wiki.xda-developers.com/index.php?pagename=UNI_Radio
Try to reflash with another ROM
Hope it helps
Good luck and don´t forget to vote!
Hi and thanks for your time and prompt reply.
I have tried everything in the thread you mentioned, but to no avail.
Can you please direct me to another suitable ROM for spvm5000 G3 64M, incase you have any such link in mind?
1 more question. Do I need to run the unlock all utility b4 I run the radio rom upgrade?
Thanks
Amit
amitkarir said:
Hi and thanks for your time and prompt reply.
I have tried everything in the thread you mentioned, but to no avail.
Can you please direct me to another suitable ROM for spvm5000 G3 64M, incase you have any such link in mind?
1 more question. Do I need to run the unlock all utility b4 I run the radio rom upgrade?
Thanks
Amit
Click to expand...
Click to collapse
Try Tomal 8.5 here: http://forum.xda-developers.com/showthread.php?t=454906
Works perfect with 64Mb
Well I never run that unlock utility as I buy my Uni unlocked, if you havent unlocked never before or flashed any ROM yes, use it, if not all should be ok
Good luck,
Sorry have not been keeping touch lately..
Iv tried tomal 8.5, 8.7 and currently running on 8.8, all 3 are ecellent ROMs
But the radio flash gives me error 114 with all 3 ROMS.
Here is the exact output log for the update utility....hope it helps!!!
22:40:52:379 [msg] : Version : [2.11].
22:40:52:395 [msg] : Config Info : [857873],[1],[0],[0],[1],[0],[0],[1].
22:40:52:676 [msg] : MSystemFile Not Exist !
22:40:52:692 [msg] : CEFile Not Exist !
22:40:53:004 [msg] : Current in CE Mode.
22:40:59:333 [msg] : Device ID is Special .
22:40:59:333 [msg] : Device BL VER : [] [].
22:40:59:333 [msg] : Update Image. CE : [0], MSystem : [0], Radio : [1]
22:41:08:973 [msg] : Check Ac in CE mode. AC : [1]
22:41:08:973 [msg] : IsBL. BL : [0]
22:41:13:848 [msg] : Enter BL OK.
22:41:18:598 [msg] : Disconnect ActiveSync .... [2]
22:41:18:598 [msg] : Start Get Connect Port.
22:41:18:911 [msg] : Current in BL Mode. Open Port : [\\.\WCEUSBSH001] OK.
22:41:24:458 [msg] : Device ID is Special .
22:41:24:458 [msg] : Device BL VER : [1.01 ] [].
22:41:26:473 [msg] : =============================================
22:41:26:473 [msg] : START UpdateRadio !
22:42:01:239 [msg] : Check Radio Level 0 [704].
22:47:40:129 [msg] : RUpgrade 0 : 0 Start.
22:57:07:192 [err] : RWipe Data Error.
22:57:24:504 [err] : BL UpdateRadio Error.
22:57:24:520 [msg] : START UnInitialization !
22:57:24:567 [msg] : END UnInitialization !
22:57:35:348 [msg] : START UnInitialization !
22:57:35:348 [msg] : END UnInitialization !
Any ideas any one???
Anyone found a fix for this eventualy?
I've been having the same error and it's driving me crazy!!
Hi all,
I happen to have a Qtek 9000 or a HTC Universal
and a few weeks ago I was trying to install a new rom for my phone... (i've done ir before and it all went well) but this rom almost kill my phone, i only can enter the bootloader...
i download all tomal's roms and other ones but when it starts to install... i installs til 60%
the screen is like full of colors, i have pictures but because i'm a new user i don't know...i can't put links here :S
please help! thanks in advance
PD: sorry for my English, i'm from Uruguay
-
the error that appears when the rom is installing is:
error 113 extended rom update error
i've fix it!!! with mtty comand: task 28 55aa
i'm so happy!
Yes, that or Doc format help in most of the cases.
Very documented on the Wiki.
Glad to know you have it back
i'm sorry if i am writting in the wrong place, but.. after i make it work... it shows NO GSM....it has no radio version, or protocol, or IMEI... do you know how to fix this? Thanks
i've tried this: UNI_Radio (which is in the wiki) and didn't work.... then i tried this: Uni_Simlock_by_Buzz_and_team ... and i can't complete step 5... when i run MaUpgradeUt_noID.exe it never ends.... it always gets stuck at 0%
Thanks for any help
Reading and searching is the key:
http://forum.xda-developers.com/showthread.php?t=567017
Thanks!!! i've been searching and found this: http://forum.xda-developers.com/showpost.php?p=4944998&postcount=1 but i don't know how to do it ... can you help me understand? or give me a link which shows the steps.... thanks again
Read here:
http://forum.xda-developers.com/showthread.php?t=301662
sorry to ask you some mucho about this things... but i'm freaking out... i really don't know how to use the UniversalRUU.... i have to put the .nbf radio file in the same folder?.... and run it? if so... it doesn't work for me... i'm so confussed...
please help me
and after i do the way i tell you... it got stuck in bootloader.... fortunately i could fix it
please help me with the other issue
THANKSSS
this is my RUU.log file:
Code:
01:08:57:750 [msg] : Version : [2.11].
01:08:57:750 [msg] : Config Info : [857873],[1],[0],[0],[1],[0],[0],[1].
01:08:57:812 [msg] : MSystemFile Not Exist !
01:08:57:812 [msg] : CEFile Not Exist !
01:08:57:859 [msg] : Current in CE Mode.
01:09:02:203 [msg] : Device BL VER : [] [].
01:09:02:203 [err] : Device CID Error.
01:09:02:203 [msg] : Update Image. CE : [0], MSystem : [0], Radio : [1]
01:09:05:390 [msg] : Check Ac in CE mode. AC : [1]
01:09:05:390 [msg] : IsBL. BL : [0]
01:09:09:937 [msg] : Enter BL OK.
01:09:13:968 [msg] : Disconnect ActiveSync .... [2]
01:09:13:968 [msg] : Start Get Connect Port.
01:09:14:140 [msg] : Current in BL Mode. Open Port : [\\.\WCEUSBSH001] OK.
01:09:35:937 [msg] : Get Device Backup ID.
01:09:35:937 [msg] : Device BL VER : [1.01 ] [].
01:09:35:937 [msg] : Device ID Is Incompatible.
01:09:37:937 [msg] : =============================================
01:09:37:937 [msg] : START UpdateRadio !
01:09:45:437 [msg] : Check Radio Level 0 [704].
01:09:46:515 [msg] : RUpgrade 0 : 0 Start.
01:13:00:078 [err] : RWipe Data Error.
01:13:00:421 [err] : BL UpdateRadio Error.
01:13:00:421 [msg] : START UnInitialization !
01:13:00:421 [msg] : END UnInitialization !
01:16:44:812 [msg] : START UnInitialization !
01:16:44:812 [msg] : END UnInitialization !
i'm borroving this thread for my similar problem, i tried to upgrade rom, and now it's stuck at boot and it seems like there are no windows in there, and RUU wont do a thing, becouse it wont detect my Uni's versions and it puts some error and goes to the recovery, but there it endlessy does nothing =( i've already tried most of rom files and always the same thing. any ideas please?
problem
i don' t know what is happened to my universal... it doesent boot anymore... and i cant go to the bootloader mode... when i connect it to the computer in comes only two textes: USB ant v1.01... can someone help me?
sorry for my english i'm from italy
EDIT: when i try for example to install tomal' s rom v8.7 i have error 112 CE error update.. wat is it??
Welcome to forums
Have a read on my signature link, you may try Doc format or MTTY tool.
Hope it helps
Since i can't post directly to development Forums, i post it here. So please move the post!
I reflected the Samsung Diagnostic App and wrote a programm that creates on a bruteforce basis almost all of the diagnostic codes available.
The source code contains 175 codes, my program was able to create 150.
I can't really create the missing 25 codes, because the input you enter into the diagnostig app, is hashed and then compared, so there is no way (for me) to reverse this hashing.
Please notice: I know some of these codes aren't working but i post them anyway for completeness.
g_FTAMain : 15, 71671835, 56#805353, 716717#15
g_QUALCOMM_TEST : *09#
g_SIMPLE_FUNCTION_TEST : *#05#
g_TouchDelta_80 : *#80#
g_IMEI_NUMBER : *#06#, 57*69*4#0
g_BATT_TEST : *#2*#, 57*69*580
g_TMOServiceMenu : *74*#
g_SMDINFO : *#03#
g_LCDTEST : *#0*#, 57*69*380
g_VIEWHISTORYNW : *#07#
g_QWERTYTEST : *#1*#, 57*69*480
g_BRIGHTNESS_TEST : *#3*#, 57*69*680
g_VPHONE772 : *#772#, 521*86376
g_VPHONE779 : *#779#, 63679*149, 87*809841
g_VPHONE770 : *#770#, 521*86356
g_VPHONE777 : *#777#, 63679*129, 87*809821
g_RILNETLOG : *#638#, 517794#67, 87*808431
g_VPHONE775 : *#775#, 63679*109, 87*809801
g_SR_TEST : *#780#, 521*86456
g_LIGHTTEST : *#12*#, 5*239715#
g_VPHONE773 : *#773#, 405505##8, 521*86386
g_VT_DUMP : *#938#, 517797#67
g_BTLOGDUMP : *#232#, 517790#07
g_RILDUMP : *#745#, 87*809501
g_VPHONE774 : *#774#, 521*86396
g_WIFI_FACTORY_TEST : *#526#, 43985#490, 84#*42#65, 87*807311
g_VPHONE771 : *#771#, 521*86366, 820#611#7
g_VPHONE778 : *#778#, 63679*139, 820#611*7, 87*809831
g_VPHONE776 : *#776#, 63679*119, 87*809811
g_Enable_Testbed : *12358#, 177523034, 7#6850676, 910594*46
g_DEBUGMODE1 : *#0011#, 1#8877754, 472667011
g_LIGHTSENSORTEST : *#0589#, 75#573125, 7#6*32986
g_AUDIOTEST : *#0673#, 6*9495#11, 7#6*33826
g_ILLUMINATIONTEST : *#0843#, 7#6*35526
g_MultiTouch : *#0987#, 75#577105, 7#6*36966
g_TouchFirmare_2663 : *#2663#, 7#6*53726
g_GPSTEST : *#1575#, 7#6*42846
g_AUDIOTEST2 : *#0289#, 472669791, 75#570125
g_FMRADIORX : *#0368#, 18#10#77#, 7#6*30776, 82854#120
g_RRCVERSION : *#0599#, 75#573225
g_DebugOption : *#7450#
g_SOUNDTEST : *#0675#, 6*9495#31, 7#6*33846
g_MOUSETEST : *#121*#, 4726790*1, 75#580*#5
g_MOUSECAL : *#123*#, 4726792*1
g_PHONEDUMP : *#2454#, 7#6*51636
g_HWversionFTA : *#2222#, 1#8899864, 472689121, 4#71746#5
g_BANDSELECTION : *#2263#, 472689531
g_TouchDelta_2665 : *#2665#, 7#6*53746
g_NAVIKEY_TEST : *#2486#, 7#6*51956
g_RTC : *#0782#, 7#6*34916
g_DEBUGDUMP : *#9900#, #9803999
g_ERRORREPCAB_INSTALL : *#9907#, 4316#9456, 8421*4606
g_BATTERYINFO : *#0228#, 472669181
g_DEVICETEST : *#0842#, 7#6*35516
g_CAMERAUPDATE : *#2470#
g_TouchDelta_2664 : *#2664#, 7#6*53736
g_SWversionEx : *#1234#, 1#8889984, 39473*#9*, 472679241
g_MOUSECAL06 : *#126*#, 4726795*1
g_MICROUSB_TEST : *#1793#, 614921**9
g_PHONELOOPBACKTEST : *#0283#, 472669731
g_USBPATHCHANGE : *#7284#
g_CAMERADISABLE : *#2480#
g_RILNETLOG_OFF : *#6380#
g_ERROR_REPORT_VERIFY : *#7452#
g_VPHONE_DISABLED : *#77*0#, 954312475
g_SWversionFTA : *#1111#, 1#8888754, 472678011
g_NETLOCK_NETWORK : *#6955#, 4248*#4#3, 7#6*96646
g_UARTCHANGER : *#9090#
g_SUWON3G_CAB_INSTALL : *#9909#, 4316#9476, 8421*4626
g_INTEGRITY : *#2580#
g_ERROR_REPORT_ON : *#7451#
g_NETLOG_LOG_START : *#9905#, 4316#9436
g_UARTPATH : *#9910#
g_YSSHINTEST : *#9999#, 9*190*03*
g_RILNETLOG_ON : *#6381#, 18#16#90#, 7#6*90906
g_POWERONATTACH : *#7298#, 3604494*2
g_SELF_DIAGNOSTIC_MODE : *#7353#, 18#17#62#
g_PILEDUMP : *#9901#, 8421*46*6
g_GUMITEST3G_CAB_INSTALL : *#9908#, 4316#9466, 8421*4616
g_NETLOCK_SERVICE : *#7755#, 8832#9601
g_VPHONE_ENABLED : *#77*1#, 954312485
g_DEBUG_RIL_DUMP : *#9906#, 166026#0, 4316#9446
g_BATTERYMONITOR : *#9911#, 8421*47*6
g_CONNECTION_SETTING : *#9920#
g_VERIFYCOMPARE : *#9990#, 9*190*0**
g_Disable_Testbed : #12358#, 170523034
g_VersionScript : 19104#2*, *#99732#
g_BLUETOOTH_LOG_ENABLE : 20652619, 61709134
g_BT_SSPDEbugModeDisable : 20652639, 61709154, 1#2066816, 92#351307
g_CELOG_LOG_DISABLE : 20654609, 6*670#817
g_OMADMCLIENT_LOG_DISABLE : 20653609, 9448**0*8
g_OMADMCLIENT_LOG_ENABLE : 20653619
g_BLUETOOTH_LOG_DISABLE : 20652609, 61709124
g_BT_SSPDEbugModeEnable : 20652629, 61709144, 1#2066806
g_CELOG_LOG_ENABLE : 20654619, 6*670#827
g_TOTALCALLTIME : 2934331*
g_ERASE_IMEIITEM : 35190728, 76247243, 81689*06#, 908*#7725
g_IMEI_ADJUST : 35190738, 76247253, 81689*07#, 908*#7735
g_RESET_CUSTOM : 35180948, 76237463, 81688*28#
g_RESET_FACTORY : 35190718, 76247233, 81689*05#, 908*#7715
g_BLUETOOTH_RF_TEST : 3##65*88
g_BLUETOOTH_AUDIO_TEST : 3##65*98
g_AutoSimSetting : 40*047#3, *#94765#
g_PVKKey : 40*549#3, 6#137011, *#99785#, 2069393#3, 505214014, 974495169
g_RESET_FACTORY_WITHDEFAULTLANGUAGE : 76264513
g_NONSLEEPCALL_ON : *#069*1#, 4372903*4, 45*973*82
g_LEDTEST : *#14789#, 318379752
g_NONSLEEPCALL_OFF : *#069*0#, 45*973*72
g_DMSessionInit : *#15428#, 318386142, 9*#85#581
g_NETLOCK_SUBSET : *#78255#, 2067240#3
g_CAMERAUPDATESVC : *#32589#, 318557752
g_LAUNCH_UAEDIT : *#92782#, 974425139
g_CIPHERING : *#32489#, 24#59#547, 318556752
g_LOGDUMPMGR : *#33284#, 318564702
g_PdaBuildTime : *#99820#, 777551390
g_SR_DISABLED : *#780*0#, 4926#99*5, 81*255280
g_SR_ENABLED : *#780*1#, 81*255290
g_VersionTime : *#99821#, 62421*4*6
g_DIS_LOCK_SUB_NW : 17#991#3*
g_PVKFileName : 18*357#25, 6#13702##
g_EN_LOCK_SUB_NW : 193582504
g_EN_LOCK_CORP : 1*0273411
g_EN_LOCK_SVC : 1*0278411, 61491#442
g_GPSTESTTOOL : 1#8865#55
g_DIS_LOCK_NW : 20789802*, 863164*71
g_SellOutSMS : 2615#0922, 5530*6100
g_TFlashUnPairing : 30334*733, 3*87*9122
g_FILE_SYSTEM_TEST : 36*4601*9, 982676614
g_DIS_LOCK_SVC : 38025*93#, 44*7#2049
g_GPSTESTXTRA : 400#40*18
g_GPSTESTTOOL2 : 400#40*08
g_SerialNumber : 5317*0648
g_EN_LOCK_NW : 5494477*3, 71204*91#
g_EN_LOCK_SIM : 5494585*3, 587*9*7#*
g_SERVERURL : 553378683
g_SLIDECOUNT : 584644021
g_SellOutSMSTestMode : 597#*224#
g_APPSLAUNCHER : 5**6244*3, 9372799#5
g_SLOGSERIAL_M2 : 66#6757#1
g_TESTMODE : 718071#49
g_AutoReceive_Enable : 7160*5088
g_RESET_SERVICE : 72673#00#
g_ReactivateSellOutSMS : 74201#086
g_AUDIOGAINCONTROL : 7#16#1#47
g_AUDIOCODEC : 7#16#1#37
g_ADMIN_GENERIC : 838*5448*
g_SLOGSERIAL_ALL_ON : 8644*3081
g_VT_MANUALSETTING : 8802*7*5#, 972#6#115
g_WIFI_TEST : 9304554#5
g_DISLOCK_SIM : 98217*243
g_DMTESTMENU : 9#7357764
regards,
Flow
Hey Flow, thanks for this.
Does this apply to all samsung WP7 devices or is it specific to just one?
Just asking so I can move this to the most appropriate location.
Sorry for taking a while to get round to this as well.
Cheers
I don't have a focus to test this, but my guess is yes, this should apply for the focus too.
And maybe non WP7 Samsung Devices.
Flow WP7 said:
I reflected the Samsung Diagnostic App and wrote a programm that creates on a bruteforce basis almost all of the diagnostic codes available.
Click to expand...
Click to collapse
If you would have searched the forums, you would see that you didn't have to do that, because I already did that for you. I believe there are 174 codes and I found all of them.
Ciao,
Heathcliff74
Yeah tell me how the search works, did you look at the title of that thread?
Anyway if your needs are already satisfied, fine just ignore it. I invested some time to do that (not just copy paste) and my solution provides more then one code for some of the items.
Flow WP7 said:
Yeah tell me how the search works, did you look at the title of that thread?
Anyway if your needs are already satisfied, fine just ignore it. I invested some time to do that (not just copy paste) and my solution provides more then one code for some of the items.
Click to expand...
Click to collapse
Wow. No flame intended! It was just meant as a heads-up for the remaining codes you missed. I always appreciate hacking-efforts
1) Inject your own launch code (with your own passwords )
2) PROFIT!
Now, since i dont know about coding or how to understand to read this codes. I have to ask if, through this tool you could visualize the 3g/2g switch that some Omnia 7 have, and some dont in there setting?
thanks for this.Great,,,
ı have a questıon, whar r the numbers for after the (,) sign?
Alternative code for the same action.