Samsung Diagnostic Codes - Windows Phone 7 Development and Hacking

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.

Related

Zte bluebelt (zte n61) rom dump + factory images !

Hi !
Well i hope someone can cook up one wince 6.1 english rom or better. If possible i even know way to write it.
ROM DUMP
----------
http://www.hack3r2k.com/BELT/Part00.img
http://www.hack3r2k.com/BELT/Part01.img
http://www.hack3r2k.com/BELT/Part02.img
http://www.hack3r2k.com/BELT/Part03.img
FACT FILES
-----------
http://www.hack3r2k.com/BELT/partition.mbn
http://www.hack3r2k.com/BELT/amsshd.mbn
http://www.hack3r2k.com/BELT/amss.mbn
http://www.hack3r2k.com/BELT/appsboothd.mbn
http://www.hack3r2k.com/BELT/appsboot.mbn
http://www.hack3r2k.com/BELT/FLASH.bin
MEMORY INFO
-------------
Name : Share Memory - smem.bin
------------------------------
Base : 07F00000 - Length : 00100000 - Info : 0
Name : Amss Memory - amss.bin
------------------------------
Base : 05E00000 - Length : 02200000 - Info : 0
Name : Pmem - pmem.bin
------------------------------
Base : 05300000 - Length : 00B00000 - Info : 0
Name : Msg Output - MsgOutput.bin
------------------------------
Base : 052E0000 - Length : 00020000 - Info : 0
Name : Eboot Memory - eboot.bin
------------------------------
Base : 00000000 - Length : 00100000 - Info : 0
Name : EBI Memory - ebi.bin
------------------------------
Base : 00000000 - Length : 07FFFFFC - Info : 1
Name : MDSP RAM A region - mdsp_rama.bin
------------------------------
Base : B1000000 - Length : 00008000 - Info : 1
Name : MDSP RAM B region - mdsp_ramb.bin
------------------------------
Base : B1200000 - Length : 00008000 - Info : 1
Name : MDSP RAM C region - mdsp_ramc.bin
------------------------------
Base : B1400000 - Length : 0000C000 - Info : 1
Name : MDSP Register region - mdsp_regs.bin
------------------------------
Base : B1C00000 - Length : 00000028 - Info : 1
Name : ADSP RAM A region - adsp_rama.bin
------------------------------
Base : AC000000 - Length : 00080000 - Info : 1
Name : ADSP RAM B region - adsp_ramb.bin
------------------------------
Base : AC200000 - Length : 00080000 - Info : 1
Name : ADSP RAM C region - adsp_ramc.bin
------------------------------
Base : AC400000 - Length : 00080000 - Info : 1
Name : ADSP RAM I region - adsp_rami.bin
------------------------------
Base : AC800000 - Length : 00080000 - Info : 1
Name : CMM Script - load.cmm
------------------------------
Base : 05E9B9E0 - Length : 00000468 - Info : 2
PARTIONS DUMP FROM MEMORY
-------------------------------
http://www.hack3r2k.com/BELT/MEM_REG.rar (INCLUDES ALL LISTED PARTITIONS ABOVE + NV AREA DUMP
USEFULL COMBOS
-----------------
1. BOOTLOADER MODE (UP VOLUME KEY + DOWN VOLUME KEY + POWER)
2. FTM MODE - PROGRAMMING (DOWN VOLUME KEY + POWER)
WELL I HOPE ANYONE WILL GET INTERESTED REALLY WANT TO SEE ENGLISH ON MY BLUE CRAP
Br
Upgrade
Do you know about de upgrade to B13? It can be downloaded foorm pocketpt.net
/roms/BLUEBELT/Bluebelt_upgrade_B13.zip
ZTE BlueBelt Englsih ROM Needed Urgently, Please can anyone share it with me?
thanx in advance
how to flash N61(write rom to N61)?thanks
Announcement
Soon I'll be doing a firmware for Bluebelt/Bluebelt2 in English. Now I am collecting money to buy this phone. When the handset will be purchased and test firmware will be ready, I'll let you know here: http://forum.xda-developers.com/showthread.php?t=744571

New Debug Rom EXT List

Greets All,
Just wanted to post the new EXT packages from the: RUU_Huashan_Dopod_CHS_0.90.706.0_0.97.332.6_Debug. (NOT a TP2 ROM!)
Mods if this is in the wrong place please move to proper location. Link provided by mobileunderground "cnzqy1".
RUU_Huashan_Dopod_CHS_0.90.706.0_0.97.332.6_Debug EXT Packages Build
=====================================
: AdobePDF_2_5_1_0_404840_06
: AdvancedNetwork_1_0_13_0
: aGPS_Confirmation_1_0_20163226_00
: Album_3_2_20171628_00
: AppointmentEditor_1_0_20163010_0
: App_Service_1_87_0_0
: Arphic_CHS_Font_1_1_20090924_00
: Audio_Booster_2_5_20164011_00
: BacklightRedirect_1_0_0_0
: BluetoothSetting_2_11_0_0
: Boot_Launcher_1_0_20143626_2
: BrowserSnapshot_1_0_20163010_0
: Calculator_1_1_20162033_0
: CalenderLauncher_1_0_0_0
: Camera_6_45_20171631_00
: ChineseSlidingBlock_1_0_10060401_Dopod_CHS_R03
: CHS_FontSetting_1_1_20091203_00
: ClearStorage_2_3_2_2
: CMBandSwitching_2_2_2_0
: CMBluetooth_1_2_2_0
: CMCallBarring_1_3_5_0
: CMCallerID_1_5_3_0
: CMCallForwarding_1_4_15_0
: CMCallWaiting_1_3_2_0
: CMCC_DM_1_0_20100602_Dopod_CHS_RC0
: CMInternetSharing_1_2_B_0
: CMMB_1_5_20163926_00
: CMPhone_1_6_I_0
: CMPhoneVMSetting_1_9_0_0
: CMPin_1_5_5_0
: CMRead_1_08_100407_Dopod_CHS_R05
: CMWifiAdvanced_1_0_5_0
: CommManager_2_10_3_0
: Concurrence_Mgr_1_5_19221227_00
: Contact_Picker_1_0_20163220_00
: Contact_Utility_Engine_1_2_20152422_00
: CreateCMCCMailAccount_1_0_20163220_02
: Customer_Service_1_0_10062501_Dopod_CHS_R03
: CyberonVoiceSpeedDial_1_2_b100303_HuaShan_01
: DataDisconnect_1_14_0_1
: DCD_1_0_10060401_Dopod_CHS_R06
: DeviceInfo_2_14_0_0
: Dopod_Base_1_0_10052501_Dopod_CHS_R02
: Dopod_MyFavorite_1_0_10060201_Dopod_CHS_R02
: DRM_Middleware_1_5_19221328_00
: Dshow_2_0_20161331_00
: Email_Setup_Wizard_2_3_20163221_20
: EngMode_Tool_1_13_0_0
: EventNotify_1_0_10060401_Dopod_CHS_R03
: Fetion_3_1_0_100702_Dopod_CHS_R06
: FM_Radio_2_5_20171525_00
: FormatSD_2_10_0_0
: Full_Screen_Player_1_8_20171624_00
: GoogleLocationService_1_0_1_22
: GroupEditor_1_0_20163833_00
: G_Sensor_Calibrator_1_1_20153824_0
: HTCAnimation_2_0_0_0
: HTCApplication_1_17_3_0
: HTCBirthday_1_2_0_0
: HTCBookmark_1_0_20163010_0
: HTCFDN_1_15_2_1
: HTCFont_Link_1_0_19213429_00
: HTCFramework_1_7_20163525_00
: HTCGeoService_1_0_20162730_00
: HTCLockScreen_2_0_20171132_00
: HTCMessage_1_11_281_0
: HTCMessaging_Client_1_8_20171628_00
: HTCScroll_2_0_20161825_00
: HTCSettings_1_4_4_0
: HTCStartUp_1_7_0_0
: HTCUtil_4_19_0_0
: IE6Enhancement_1_0_20163010_0
: IME_CHS_2_2_20171228_00
: In_Call_Recorder_1_1_20162725_01
: IPDial_1_0_10053101_Dopod_CHS_R03
: LockstreamDRM_1_2_091113_O9_01
: Long_Press_End_Key_1_5_20142530_00
: Manila_Calendar_2_6_20171823_0
: Manila_Core_2_6_20164010_0
: Manila_Home_2_6_20171727_0
: Manila_Internet_2_6_20162821_0
: Manila_Mail_2_6_20163325_0
: Manila_Message_2_6_20163810_0
: Manila_People_2_6_20162110_0
: Manila_Photo_2_6_20163130_0
: Manila_Settings_2_6_20171524_0
: Manila_Weather_2_6_20171726_0
: Media_Tool_kit_1_2_20171629_00
: Menu_Enhancement_1_1_20171128_00
: Message_Enhancement_1_2_20163924_00
: mHub_VO_1_8_100513_0
: MobileNavigation_6_0_7_2010060401Dopod_CHS_R2
: MP3_Trimmer_1_2_20162510_0
: MusicWalkman_3_0_20100612_Dopod_CHS_R001
: Mute_1_1_2_0
: MyCPL_3_13_0_6
: M_Market_1_1_0_000_2507_Dopod_CHS_R04
: New_Contact_Card_1_1_20163010_0
: Notification_Enhancement_3_5_20163228_00
: NTF_Alarm_Module_1_0_20161822_00
: OMADM_LIB_1_0_20152129_1
: OmniBizCard_1_4_9_20100622_Dopod_CHS_R02
: OOBE_1_0_20163128_01
: Opera_Browser_9_70_36009_0
: PhoneSetting_1_72_0_0
: Phone_Canvas_Enhancement_5_0_61220163232_0
: PKG_1_1_0_0
Manila and many Pkgs updated, SYS Build 23121
Time to Play Anyone that needs the pvr files in the packages ripped let me know. Very easy to rip the icons out into individual files.

Timeline - Firmwarehistory bada 1.x and bada 2.x devices

The last 3 Chars of Firmwarename are timecode...
Example JL2:
J for 2010
L for ...
ehm A is january, B is feb...
The oldest Firmware I found is XXJB6 from February 2010.
The latest from 2011...
Btw. these timecodes are Compile dates for apps_compressed.bin...
One way is to enter Internal menu. See Screenshot.
Here are little overview...
Code:
[B]S8500XXJB6[/B]
Type : Unofficial Version
Number : 1907
Builder : scm27
Host : SCMSERVANT03
Date : 2010/02/24
Time : 04:49:31
Size : 66323804 bytes
CheckSum : 0x7a1fe855
[B]S8500XXJL2[/B]
Type : Unofficial Version
Number : 362
Builder : Administrator
Host : S1-AGENT05
Date : 2010/12/23
Time : 14:24:54
Size : 82576764 bytes
CheckSum : 0x32cdbee8
[B]S8500XEKA1[/B]
Type : Unofficial Version
Number : 12
Builder : Administrator
Host : HP28076212482
Date : 2011/01/04
Time : 11:54:38
Size : 72615292 bytes
CheckSum : 0x9620d783
[B]S8500XIKA1[/B]
Type : Unofficial Version
Number : 118
Builder : dell22
Host : SCM_DELL_23
Date : 2011/01/31
Time : 20:39:15
Size : 82576764 bytes
CheckSum : 0x31f17a34
[B]S8500JPJKB1[/B]
Type : Unofficial Version
Number : 1
Builder : user
Host : SEL-E4285A63E81
Date : 2011/02/08
Time : 17:14:38
Size : 73663868 bytes
CheckSum : 0x984141f3
Best Regards
may i ask how you get build info from menu??
http://forum.xda-developers.com/showthread.php?t=906966
further infos for RC2 file is here:
http://forum.xda-developers.com/showthread.php?t=915469
It look like another way to find date for Build... under Phone info. Look under:
Softw.-Version
bada 1.x
123456blablaLISS8500blabla
The first 6 Digits seems Compile Date too. Need to be check twice...
Best Regards
hmmm....i do not have this internal menu. i saw in phone info first six digits are indeed date. maybe next 4 are time?? but my digits are 1341 wheras u have given time as 1424 for xxjl2. btw i am on xxjl2 modified for social hub premium. perhaps you have taken stock not full firmware from samfirmware.com??
hmmm....i do not have this internal menu.
Click to expand...
Click to collapse
This is correct, if you flash Rsrc2_S8500_Open_Euro_Common(Low).rc2
Menu is disabled.
If you flash Rsrc2_S8500_Open_Euro_Common(Mid).rc2
Best Regards
Very good description.
http://samsung-stuff.de/board/thread.php?threadid=24148
Big Thanx.
year
J: 2010
K: 2011
month
A: JAN
B: FEB
C: MAR
D: APR
E: MAY
F: JUN
G: JUL
H: AUG
I: SEP
J: OCT
K: NOV
L: DEC
revsision
1-9
A-
XXJL2 is from 2010, December, revision 2
Best Regards
To be precise, the bootloader decodes that and supports dates from the letter F (2006) to P (2016), Revision 1-9, A-W (case unsesitive) meaning 1-32. There's still one more letter that is parsed case unsesitive A-Z with meaning 1-26 and space, tabulation or null meaning 100, but I haven't looked close enough to know what that is.
@adfree from where did u get the mid file? why does samfirmware says never to flash with mid always low. any extra settings we need to check in multiloader? and finally are there any changes other than this internal menu? thank u for your patience
Code:
Type : Unofficial Version
Number : 194
Builder : scmdpi06
Host : DPI06
Date : 2011/04/04
Time : 15:52:32
Size : 72353148 bytes
CheckSum : 0x95f5bb78
Nice to see that in April also S8500 Firmware is compiled.
Taken from DDKD1 India.
Best Regards
no updates for s8530 since february
Code:
Type : Unofficial Version
Number : 7
Builder : Venugopal
Host : M_VENUGOPAL-LAP
Date : 2011/05/16
Time : 23:59:05
Size : 73139580 bytes
CheckSum : 0x97909654
S8500JPKE1
So also from May Firmware available...
Best Regards
It seems that a new firmware for the Wave II is available (Bada 1.2)
The Firmware is the S8530XXKC1/S8530OXAKC1 (Open Europe) it is a March 2011 build. i will flash it later the at day, bootloader and so on is in, but it is only a update firmware.
//Edit:
Better is the scrolling in dolfin (much better) and the scrolling in voluntas (a little bit better, already not smooth)
XPKG5, both S8500 and S8530...
bada 2.0 (alpha/beta)
S8530
Code:
Type : Unofficial Version
Number : 952
Builder : Administrator
Host : S1-AGENT06
Date : 2011/07/[B]19[/B]
Time : 17:22:18
Size : 39323008 bytes
CheckSum : 0xe0d0beba
S8500
Code:
Type : Unofficial Version
Number : 806
Builder : Administrator
Host : S1-AGENT08
Date : 2011/07/[B]19[/B]
Time : 17:23:23
Size : 39323004 bytes
CheckSum : 0xe09410e7
We will see when first official release will arrive.
In September or much later...
Best Regards
@ Adfree are you sure? Is the worklload so much or are they Lazy?
One way we can compare: Bada 1.2 XX versions:
1.XXJID: September
2.XXJJ9: October
3.XXJK1: November
4.XXJL2: December
(source: Samfirmware)
Four months fom beta to a stable Version....
So Bada 2.0 Stable:October?
S8500 XPKG6
Code:
Type : Unofficial Version
Number : 817
Builder : Administrator
Host : S1-AGENT08
Date : 2011/07/22
Time : 16:35:52
Size : 39323004 bytes
CheckSum : 0xe0cef3c4
S8500 XPKG7
Code:
Type : Unofficial Version
Number : 824
Builder : Administrator
Host : S1-AGENT08
Date : 2011/07/26
Time : 15:26:07
Size : 39323004 bytes
CheckSum : 0xe11b43b5
S8530 XPKH1
Code:
Type : Unofficial Version
Number : 981
Builder : Administrator
Host : S1-AGENT06
Date : 2011/08/02
Time : 16:25:54
Size : 42206592 bytes
CheckSum : 0xede5e259
So between KG6 and 7 only 4 days... from KG5 to KG6 3 days...
So theory, all 4 or 3 days new build... but this also means, that only minor changes can be... minor bugfixes...
Maybe more changes/bugfixes possible with 14 days time... between builds...
Theory... only 1 month left for September start... but it seems bugy, ehm unfinished...
So minimum 2 months... for stable Firmware...
Btw...
These leaked Firmware are very fresh... so I think direct from Testserver...
Thanx to friendly Mr. Nice Guy from Samsung for sharing.
Best Regards
Sure they are fresh FWs
Maybe if we left bada team work silently for 2 weeks we will see a good FW
As you can see from KG6 to KG7 the change made it so much stable and they have only 4 days between them
What will happen if the 4 days were 2 weeks??
Best Regards
apps.bin from official bada 2.0 SDK
Code:
Type : Unofficial Version
Number : 255
Builder : darren.ha
Host : BA-XP4
Date : 2011/08/23
Time : 21:22:09
Size : 36177276 bytes
CheckSum : 0xc8c9e8b1
S8500 XPKH3
Code:
Type : Unofficial Version
Number : 863
Builder : Administrator
Host : S1-AGENT08
Date : 2011/08/16
Time : 20:56:16
Size : 42468732 bytes
CheckSum : 0xee43ccad
S8530 XPKH3
Code:
Type : Unofficial Version
Number : 1008
Builder : superuser
Host : S1-AGENT06
Date : 2011/08/16
Time : 20:19:21
Size : 42468736 bytes
CheckSum : 0xee79fb68
Wave 3 S8600 is seen with XPKHB... maybe on IFA in Germany.
Maybe we can test this Version also an Wave 1+2...
SDK Apps are latest compiled I found yet... 2011/08/23
Best Regards
S8500MBUKI1
Code:
Type : Unofficial Version
Number : 262
Builder : Dell02
Host : SCMDELL16
Date : 2011/09/16
Time : 19:35:07
Size : 42468732 bytes
CheckSum : 0xef3c5853
S8600XXKI9
Code:
Type : Unofficial Version
Number : 952
Builder : superuser
Host : S1-AGENT05
Date : 2011/09/27
Time : 02:53:48
Size : 55050240 bytes
CheckSum : 0x0cbbad48
Latest known/downloadable Firmware yet:
S8600BOKJ1_TPLKJ1
Code:
Type : Unofficial Version
Number : 981
Builder : dpi
Host : DELL42
Date : [COLOR="Red"][B]2011/10/03[/B][/COLOR]
Time : 15:48:05
Size : 55050240 bytes
CheckSum : 0x0c9a8ca5
This means we have no idea, what is now actual status of bada 2.0... because tested Version is older then 4 weeks...
This is SDK 2.0.2 ... 2 days between latest known S8600 Firmware.
Code:
Type : Unofficial Version
Number : 338
Builder : darren.ha
Host : BA-XP4
Date : [B]2011/10/01[/B]
Time : 07:51:28
Size : 35128700 bytes
CheckSum : 0xc2e51d24
Best Regards
S8600XXKJC
Code:
Type : Unofficial Version
Number : 1096
Builder : superuser
Host : S1-AGENT05
Date : [B]2011/10/26[/B]
Time : 17:26:52
Size : 55050240 bytes
CheckSum : 0x0d3edb3f
No idea if date is same from Kies Version...
Between 2011/10/26 and today are 2 weeks...
Also no idea, if this means, if available from Kies. It is now final bada 2.0 Version...
Maybe soon, if Wave III is real available. We can see Firmware Version on device... maybe it is higher or lower XXKJC.
Best Regards
S8500XPKJ1
Code:
Type : Unofficial Version
Number : 984
Builder : Administrator
Host : S1-AGENT08
Date : [B]2011/10/05[/B]
Time : 22:44:23
Size : 42730876 bytes
CheckSum : 0xf57d5099
S8530XPKJ1
Code:
Type : Unofficial Version
Number : 1141
Builder : superuser
Host : S1-AGENT06
Date : [B]2011/10/06[/B]
Time : 00:37:37
Size : 42730880 bytes
CheckSum : 0xf580ab96
This means older then 1 month...
So again, we have no idea if Final are close, closer or in the closet... this month.
Best Regards

Sirf interface log

Help to fix this error:
ERROR: (LSM_Start) LSMInitPattern != LSM_INIT_PATTERN
Here ma log file:
<17:17:59> ========== NEW Session ==========
<17:17:59> Session State Machine : MOSession
<17:17:59> GPS ONOFF Report : 1
<17:17:59> INFO: GPS_WAKE_LOCK_ENABLE
<17:17:59> [SIF Disabled.]
<17:17:59> [START_MODE : 1]
<17:17:59> [SSL : ENABLED]
<17:17:59> [SUPL : supl.google.com:7276]
<17:17:59> [AGPS MODE : USER PLANE]
<17:17:59> [TRACKING MODE]
<17:17:59> [HORIZONTAL ACCURACY = 50]
<17:17:59> LSM_setCapabilities
<17:17:59> Position Mode : GPS_POSITION_MODE_MS_BASED
<17:17:59> Local time is not available - wait for time udate from NTP or GPS
<17:17:59> QoP Configuration : Horizontal Accuracy : 50, Vertical Accuracy : 250, TTFF Response Time : 240
<17:17:59> session resumed : ANDROID_MO_SESSION
<17:17:59> INFO: LSM_Start is called
<17:17:59> ERROR: (LSM_Start) LSMInitPattern != LSM_INIT_PATTERN
<17:17:59> sirf_gps_start : LSM_Start Failed!!!!
<17:17:59> android_mo_session_start fail!!!!
<17:17:59> IdleState:updating session check
<17:17:59> GPS ONOFF Report : 0
<17:17:59> INFO: GPS_WAKE_LOCK_DISABLE
<17:18:59> sirf_gps_stop called
<17:18:59> no session to suspend !!!
<17:18:59> android_session_handler_suspend fail!!!
<17:57:08> sirf_gps_cleanup: called
<17:57:13> sirf_agps_ril_update_network_state: called - connected : 1, type : 0 extra : free
<17:57:13> sirf_agps_update_network_availability : available = 1, apn = free
<17:59:19> sirf_agps_ril_update_network_state: called - connected : 1, type : 0 extra : free
<17:59:19> sirf_agps_update_network_availability : available = 1, apn = free
<18:27:04> sirf_agps_ril_update_network_state: called - connected : 1, type : 0 extra : free
<18:27:04> sirf_agps_update_network_availability : available = 1, apn = free
<18:32:07> sirf_agps_ril_update_network_state: called - connected : 1, type : 0 extra : free
<18:32:07> sirf_agps_update_network_availability : available = 1, apn = free
<19:26:47> sirf_agps_ril_update_network_state: called - connected : 1, type : 0 extra : free
<19:26:47> sirf_agps_update_network_availability : available = 1, apn = free
<19:31:15> sirf_agps_ril_update_network_state: called - connected : 1, type : 0 extra : free
<19:31:15> sirf_agps_update_network_availability : available = 1, apn = free
<19:33:28> sirf_agps_ril_update_network_state: called - connected : 1, type : 1 extra : NULL
<19:33:28> sirf_agps_update_network_availability : available = 0, apn = free
<19:33:31> sirf_agps_ril_update_network_state: called - connected : 1, type : 1 extra : NULL
<19:33:31> sirf_agps_update_network_availability : available = 0, apn = free
<19:33:31> sirf_agps_ril_update_network_state: called - connected : 1, type : 1 extra : NULL
<19:33:31> sirf_agps_update_network_availability : available = 0, apn = free
LikeM8 said:
Help to fix this error:
ERROR: (LSM_Start) LSMInitPattern != LSM_INIT_PATTERN
Here ma log file:
<17:17:59> ========== NEW Session ==========
<17:17:59> Session State Machine : MOSession
<17:17:59> GPS ONOFF Report : 1
<17:17:59> INFO: GPS_WAKE_LOCK_ENABLE
<17:17:59> [SIF Disabled.]
<17:17:59> [START_MODE : 1]
<17:17:59> [SSL : ENABLED]
<17:17:59> [SUPL : supl.google.com:7276]
<17:17:59> [AGPS MODE : USER PLANE]
<17:17:59> [TRACKING MODE]
<17:17:59> [HORIZONTAL ACCURACY = 50]
<17:17:59> LSM_setCapabilities
<17:17:59> Position Mode : GPS_POSITION_MODE_MS_BASED
<17:17:59> Local time is not available - wait for time udate from NTP or GPS
<17:17:59> QoP Configuration : Horizontal Accuracy : 50, Vertical Accuracy : 250, TTFF Response Time : 240
<17:17:59> session resumed : ANDROID_MO_SESSION
<17:17:59> INFO: LSM_Start is called
<17:17:59> ERROR: (LSM_Start) LSMInitPattern != LSM_INIT_PATTERN
<17:17:59> sirf_gps_start : LSM_Start Failed!!!!
<17:17:59> android_mo_session_start fail!!!!
<17:17:59> IdleState:updating session check
<17:17:59> GPS ONOFF Report : 0
<17:17:59> INFO: GPS_WAKE_LOCK_DISABLE
<17:18:59> sirf_gps_stop called
<17:18:59> no session to suspend !!!
<17:18:59> android_session_handler_suspend fail!!!
<17:57:08> sirf_gps_cleanup: called
<17:57:13> sirf_agps_ril_update_network_state: called - connected : 1, type : 0 extra : free
<17:57:13> sirf_agps_update_network_availability : available = 1, apn = free
<17:59:19> sirf_agps_ril_update_network_state: called - connected : 1, type : 0 extra : free
<17:59:19> sirf_agps_update_network_availability : available = 1, apn = free
<18:27:04> sirf_agps_ril_update_network_state: called - connected : 1, type : 0 extra : free
<18:27:04> sirf_agps_update_network_availability : available = 1, apn = free
<18:32:07> sirf_agps_ril_update_network_state: called - connected : 1, type : 0 extra : free
<18:32:07> sirf_agps_update_network_availability : available = 1, apn = free
<19:26:47> sirf_agps_ril_update_network_state: called - connected : 1, type : 0 extra : free
<19:26:47> sirf_agps_update_network_availability : available = 1, apn = free
<19:31:15> sirf_agps_ril_update_network_state: called - connected : 1, type : 0 extra : free
<19:31:15> sirf_agps_update_network_availability : available = 1, apn = free
<19:33:28> sirf_agps_ril_update_network_state: called - connected : 1, type : 1 extra : NULL
<19:33:28> sirf_agps_update_network_availability : available = 0, apn = free
<19:33:31> sirf_agps_ril_update_network_state: called - connected : 1, type : 1 extra : NULL
<19:33:31> sirf_agps_update_network_availability : available = 0, apn = free
<19:33:31> sirf_agps_ril_update_network_state: called - connected : 1, type : 1 extra : NULL
<19:33:31> sirf_agps_update_network_availability : available = 0, apn = free
Click to expand...
Click to collapse
Read the rules
Thanks Menelkir for your repply. But I do not udestand what your mean
LikeM8 said:
Thanks Menelkir for your repply. But I do not udestand what your mean
Click to expand...
Click to collapse
from the forum rules at the top of each forum
15. Keep posts/threads on-topic
Whilst a minor amount of off-topic posting may be overlooked, the general rule is your posts / threads must be relevant to the Forum / thread in which you are posting.
General Forums - For news and announcements relating to your device.
Q&A Forums - For all question threads / posts. If there is no Q&A forum use the device General Forum
Accessories subforum - For posts related to accessories relevant to the phone model
Development Forums (ones with the word development in the title) - For developers to post release threads e.g. ROMs and Kernels including modifications to Kernels, Bootloaders, ROMs, etc.
Themes and Apps Forums - For themers to post Themes and App. announcements & discussions including modifications made to Apps and Themes.
Click to expand...
Click to collapse
LikeM8 said:
Thanks Menelkir for your repply. But I do not udestand what your mean
Click to expand...
Click to collapse
You are in wrong section bro...i think this is for developer..if you want to ask..please move to Q&A
Sent from my Galaxy Nexus using xda premium
arief347 said:
You are in wrong section bro...i think this is for developer..if you want to ask..please move to Q&A
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
OK...sorry!

not sure if bricked

so i finally got the phone the turn on 3 months later and 12 guides, let it be for a week and it turned on... i went to root the phone using super one click, seemed to all go fine right untill it wanted to reboot, now ive worked on allot of phones, generally, the screen dosent just light up without an issue, ive run diagnostics and everything this is the same screen i get when im trying to run a new KDZ via a guide or try to run into recovery mode, im not sure what i can do to fix the phone, if anyone is able to help that would be greatly apreciated
Were you able to successfully complete any of the unbricking guides? Does the LG Software Update tool recognize the phone?
audit13 said:
Were you able to successfully complete any of the unbricking guides? Does the LG Software Update tool recognize the phone?
Click to expand...
Click to collapse
its been hit and miss, im not sure if there working cuz i will get to the the logo screen and than it just goes black but still uses power and is able to transfer files, i fonally got it turned on this morning, its a p930 but the model number when i look in about phone is a sul640 i beleive some something crazy like that, i know its a simmilar model phone, but is this why im having so many issues with the device is because its not allowing me to flash the right software?
In order to unbrick and install a custom recovery, you need to install the Korean ROM. Did complete the guide? If not, how far did you get?
audit13 said:
In order to unbrick and install a custom recovery, you need to install the Korean ROM. Did complete the guide? If not, how far did you get?
Click to expand...
Click to collapse
It improve apparently according to what the guide tells me but I'm still having the same issue of the phone screen going blank immidietyly after the Lte boot logo
It was working than I tried rooting using super one click and now I'm on the black screen again but this time I do have the stock recovery menu which is odd as I didn't know it had one until the others when .I finally got to it I'm not sure were I arsed this all up I've followed all the guides letter by letter and it's done this since day one
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
I recommend following the guide rather than using one click. Following the guide will alow you to unlock the bootloader, load a custom recovery, and root.
Could you link that please? I'll give it a try and see if it helps
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
kagalous said:
Could you link that please? I'll give it a try and see if it helps
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/showthread.php?t=1597488
audit13 said:
Try this: http://forum.xda-developers.com/showthread.php?t=1597488
Click to expand...
Click to collapse
09:28:59 : [C:\LGMobileUpgrade] Try to delete folder
09:28:59 : RemoveDirectory1 Error(2):C:\LGMobileUpgrade
09:28:59 : Start Date : 2013-08-27 09:28:59
09:28:59 : ---------- QM CSE Testmode ---------
09:28:59 : ---------- CSE mode ---------
09:28:59 : ***** Check Tool Version *****
09:28:59 : Tool version : 1.5.4.8
09:28:59 : UpgradeDLL version : 1.2.6.7
09:28:59 : Current Dir : C:\ProgramData\LGMOBILEAX\B2C_Client
09:28:59 : LGE USB Driver Version :
09:28:59 : Android PDLV Version :
09:28:59 : Android NDLV Version :
09:28:59 : ******************************************
09:28:59 : [C:\ProgramData\LGMOBILEAX\Phone] Try to delete folder
09:28:59 : RemoveDirectory1 Error(2):C:\ProgramData\LGMOBILEAX\Phone
09:28:59 : SetEmerModeAT()
09:28:59 : *****CheckOS Start********
09:28:59 : Microsoft_Windows7_Professional_
09:28:59 : *****CheckPCSyncPrograms Start*****
09:29:00 : PCSyncPrograms Not Found - OK and ready to upgrade
09:29:00 : Checking the connection with the cell phone...
09:29:00 : dwWaitResetTime(40000 ms)
09:29:01 : _IsConnectedPhone Call
09:29:09 : _IsConnectedPhone(2)
09:29:09 : 0 - NotConnected.
09:29:09 : 1 - Normal connect success
09:29:09 : 2 - Emergency connect success
09:29:09 : Phone Mode(2)
09:29:09 : *****CheckPCSyncPrograms Start*****
09:29:10 : PCSyncPrograms Not Found - OK and ready to upgrade
09:29:11 : ****************CheckAndDownload********************
09:29:11 : ******Extract Start C:\Users\Jeanette\Downloads\LG-SU640-V10F_00.kdz*****
09:29:11 : Model Dll Dir(C:\ProgramData\LGMOBILEAX\Phone\)
09:29:11 : File Size = 474536279
09:29:58 : Extract kdz file Success.
09:30:07 : Extracted C:\ProgramData\LGMOBILEAX\Phone\\V10f_00.wdb\n
09:30:07 : WDB(or DZ) FullPath(C:\ProgramData\LGMOBILEAX\Phone\\V10f_00.wdb)
09:30:17 : Extracted C:\ProgramData\LGMOBILEAX\Phone\\SU640_WD_1_1_3_0.dll\n
09:30:17 : Model dll FullPath(C:\ProgramData\LGMOBILEAX\Phone\\SU640_WD_1_1_3_0.dll)
09:30:17 : Extracted C:\ProgramData\LGMOBILEAX\Phone\\V10f_00.wdh\n
09:30:18 : NNNNN WDB FullPath(C:\ProgramData\LGMOBILEAX\Phone\V10f_00.wdb)
09:30:18 : NNNNN Model dll FullPath(C:\ProgramData\LGMOBILEAX\Phone\SU640_WD_1_1_3_0.dll)
09:30:18 : Extract End C:\Users\Jeanette\Downloads\LG-SU640-V10F_00.cab
09:30:19 : ------------------Model.dll Information-------------------
09:30:19 : Filename : SU640_WD_1_1_3_0.dll
09:30:19 : Version : 1.1.3.0
09:30:19 : File size : 348160
09:30:19 : File date : 2011/10/27-17:09:48
09:30:19 : PC Created date: 2013/08/27-09:30:07
09:30:19 : ----------------------------------------------------------
09:30:19 : *****Check LGCM Programs Start*****
09:30:19 : LGCM Programs Not Found - OK and ready to upgrade
09:30:19 : *****WorkModelDLL Start*****
09:30:25 : strPhoneBinaryPath(C:\ProgramData\LGMOBILEAX\Phone\V10f_00.wdb)
09:30:25 : strModuleDir(C:\ProgramData\LGMOBILEAX\Phone\)
09:30:25 : strModelDLLPath(C:\ProgramData\LGMOBILEAX\Phone\SU640_WD_1_1_3_0.dll)
09:30:25 : _DetachDLL Call
09:30:25 : _DetachDLL Call End
09:30:25 : Call fn_StartUpgrade
09:30:25 : Phone mode change -> CSE
09:30:25 : ********* CDMA Model.dll input Parameter *************
09:30:26 : MODEL_EVENT : 32769
09:30:26 : PhoneBinaryPath : C:\ProgramData\LGMOBILEAX\Phone\V10f_00.wdb
09:30:26 : ModuleDir : C:\ProgramData\LGMOBILEAX\Phone\
09:30:26 : BootWaitTime : 49500
09:30:26 : UsbHighSpeed : FALSE
09:30:26 : PhoneMode : 4
09:30:26 : NewPhoneBinVersion : LG-SU640-V10F_00
09:30:26 : ClearSI : FALSE
09:30:26 : AuthMark : 0
09:30:26 : ********* CDMA Model.dll input Parameter End*************
09:30:46 : wParam : 2004, lParam = 90
09:30:46 : MODEL DLL Event : (2004, 90)
09:30:46 : Step : TYPE_WPARAM_IFX_DN_POS
09:31:11 : wParam : 2004, lParam = 91
09:31:36 : wParam : 2004, lParam = 92
09:32:01 : wParam : 2004, lParam = 93
09:33:01 : wParam : 2004, lParam = 94
09:33:26 : wParam : 2004, lParam = 95
09:33:51 : wParam : 2004, lParam = 96
09:34:59 : wParam : 2004, lParam = 97
09:35:09 : wParam : 2004, lParam = 98
09:35:19 : wParam : 2004, lParam = 99
09:35:29 : wParam : 2004, lParam = 100
09:35:39 : wParam : 2001, lParam = 0
09:35:39 : MODEL DLL Event : (2001, 0)
09:35:40 : CLGMobileHttp Class ¼Ò¸ê½ÃÀÛ.
09:35:40 : CLGMobileHttp Class ¼Ò¸ê...
09:35:40 : CleanModelDll() : Free Model.dll
09:35:40 : _DetachDLL Call
09:35:40 : _DetachDLL Call End
09:35:40 : Step : S/W Upgrade Complete!
09:35:41 : ==========================================================
09:35:41 : Upgrade total : 402
09:35:41 : Model.dll upgrade sec : 316
09:35:41 : Model.dll name : SU640_WD_1_1_3_0.dll
09:35:41 : Model.dll version : 1.1.3.0
09:35:41 : Model.dll size : 348160
09:35:41 : Model.dll Date : 20111027170948
09:35:41 : =========================================================
got to there, now phone wont turn on again..... goes to lg screen than goes black or the colors run horridly
any suggestions man?
http://forum.xda-developers.com/showthread.php?t=1784709
Try this guide. This worked for me.
still having the same results, ive tried all 3 guides on this forum man, would it work if i tried an actual kdz for my phone not the su640 that all the guides give me? i have the p930
got it working... heres what i did, might wanna keep this post around for people having my unique issue
undid everything i tried on my pc, so remove drivers, the " 127.0.0.1 csmg.lgmobile.com " in the hosts file and uninstalled everything.
downloaded LG SU-640 firmware V10F_00.kdz: http://www.megaupload.com/?d=31XABWWJ
got KDZ_FW_UPD and windows enabler in XP SP3 Compatability mode with Administrator mode (seriously do this or no results)
Ran the Uptest EX (might need the B2CAppSetup)
Let it do its thing, Boots fine now, gonna try a root and let you know how it goes
learn it, Be careful the best
Root is working great still can't figure out the bootloader unlock without starting back where I started lol
Sent from my LG-P930 using xda app-developers app
kagalous said:
Root is working great still can't figure out the bootloader unlock without starting back where I started lol
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
I think you need to downgrade to GB to unlock.
Lol I don't know why but it won't turn on again
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Try this: remove the battery for a few minutes, re-install, and try to boot.
Left it out all night same thing
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Is it possible there is a hardware problem with the phone?

Categories

Resources