Hi, after some time searching for tools and info i have gathered a few working tools and service manuals for our belloved G3.
Here is the Service Manual Link
Here is the Smart Boot Diagnostic Tool Link
Here is the QDLoader HS-USB driver for 64bit windows pc Link
Here is the QDLoader HS-USB driver for 32bit windows pc Link
Here is the AP-CHIP dll and ATT achive for Flash Tool for use without LG B2B connection Link
Here is the LG FlashTool 1.5.10.1120 Link
Here is the Megalock .dll file to overwrite in flash tool folder for B2B nologin Link
Here is the How To Calibrate document Link
Here is a document that shows how to Flash a "dead boot" LG phone Link
Hope this will help someone or teaching others. Excuse my english and if i posted in a wrong section. Thanks !
scamex said:
Hi, after some time searching for tools and info i have gathered a few working tools and service manuals for our belloved G3.
Here is the Service Manual Link
Here is the Smart Boot Diagnostic Tool Link
Here is the QDLoader HS-USB driver for 64bit windows pc Link
Here is the QDLoader HS-USB driver for 32bit windows pc Link
Here is the AP-CHIP dll and ATT achive for Flash Tool for use without LG B2B connection Link
Here is the LG FlashTool 1.5.10.1120 Link
Here is the Megalock .dll file to overwrite in flash tool folder for B2B nologin Link
Here is the How To Calibrate document Link
Here is a document that shows how to Flash a "dead boot" LG phone Link
Hope this will help someone or teaching others. Excuse my english and if i posted in a wrong section. Thanks !
Click to expand...
Click to collapse
Thank you for posting these links, it's sometime impossible to figure out "what to google" if you know what I mean.
Was wondering if you had found any MTP drivers that work, as the ones LG provides does not work for windows 8 64bit.
tidaboy9 said:
Thank you for posting these links, it's sometime impossible to figure out "what to google" if you know what I mean.
Was wondering if you had found any MTP drivers that work, as the ones LG provides does not work for windows 8 64bit.
Click to expand...
Click to collapse
Just install Media Sync Manager i belive from microsoft and you`ll be fine.
problem with my lg g3 help!!
i have a problem with my lg g3 d855, not write in emmc
elite124 said:
i have a problem with my lg g3 d855, not write in emmc
Click to expand...
Click to collapse
Once it happened me too. I just factory resetted the device and after that flashing was ok.
scamex said:
Once it happened me too. I just factory resetted the device and after that flashing was ok.
Click to expand...
Click to collapse
and I do, so now I'm losing esperansas that attempt everything and get errors
elite124 said:
and I do, so now I'm losing esperansas that attempt everything and get errors
Click to expand...
Click to collapse
Please use google translate.
How fixed
elite124 said:
and I do, so now I'm losing esperansas that attempt everything and get errors
Click to expand...
Click to collapse
Dis you fix this issue????? i have the same error
same error
error flashing or erasing
if you solve this problem, please email me [email protected]
where to place AP-CHIP dll and ATT archive to choose in smart boot diagnostic tool ?
nickamania said:
where to place AP-CHIP dll and ATT archive to choose in smart boot diagnostic tool ?
Click to expand...
Click to collapse
I want to know too.
--------------------------------------------------------
I take this opportunity to present my case, I have the green screen (Appz Whatchdog bark) screen when I try to enter download mode with the usual method (Volume Up and push USB cable) tries to enter but ends up turning off the display and is recognized immediately in admisnistrador device as "Qualcomm HS-USB QDLoader 9008" all with the battery connected. My question now is this, do I still should remove the battery and make the bridge between the 2nd. and ground contact on the motherboard of the device? And thenceforth to follow the repair with SmartBootDiag v1.3.1
Lg g3 d 850 att smart boot bin missing in recovery folder .if any one have plz upload
hello, i have bought g4 with same problem, i have lg flash tool and qualcomm drivers but i dont have required files for it, its h818n dual sim, any idea ?
thanks
At & t lg g3 d850
cdmababa said:
Lg g3 d 850 att smart boot bin missing in recovery folder .if any one have plz upload
Click to expand...
Click to collapse
Please send mesage from me [email protected]. Using LG smart boot Diag Tool to unbrick LG G3 models that stuck in qualcomm 9008 mode.I got the link:good:
ertas71 said:
Please send mesage from me [email protected]. Using LG smart boot Diag Tool to unbrick LG G3 models that stuck in qualcomm 9008 mode.I got the link:good:
Click to expand...
Click to collapse
Plz explain ,
Sent from my HTC_One_max using Tapatalk
G3
Hi.D850 D851 Ap_chip https://mega.nz/#!h0JExLwb!rDBMrSbj5nuUhyVN5EzoeHO6d3apl1EPjU4ugLcgYFI
http://www.gsmkolik.com/lg-g3/21619-lg-smart-boot-diag-tool-unbrick-lg-g3.html
Ap-Chip for D850,D851,All EU Global,LGLS990_ASPR_Sprint,LGVS985_AVRZ_VRZ
LG G3 D858HK hard Bricked Need Help
After Boot diagnostic still my phone is on same bricked state only qualcomm 9008 no emmc detected the log file of boot diagnostic is as
>> ---------------------------- Start Logging ----------------------------
>> USB Status : Qualcomm HS-USB QDLoader 9008 (COM41)
>> Ready to access the target board...
>> BootLoader File : LGD858HK_AHKG_HKG.mbn
>> 1. Model : LGD858HK , 2. Suffix : AHKG , 3. Operator : HKG
>> Bootloader : LGD858HK_AHKG_HKG.mbn
>> AP Chip : MSM8974_G3 , BootLoader : LGD858HK_AHKG_HKG.mbn
>> Trying Connection To Device with sahara protocol for AP Chip.
>> Successfully Connection To Device with sahara protocol for AP Chip.
>> connected with Sahara Protocol successfully.
>> Loading flash to SYS_IMEM.
>> Loading 0 Kbytes to SYS_IMEM.
>> Loading 4 Kbytes to SYS_IMEM.
>> Loading 8 Kbytes to SYS_IMEM.
>> Loading 12 Kbytes to SYS_IMEM.
>> Loading 16 Kbytes to SYS_IMEM.
>> Loading 20 Kbytes to SYS_IMEM.
>> Loading 24 Kbytes to SYS_IMEM.
>> Loading 28 Kbytes to SYS_IMEM.
>> Loading 32 Kbytes to SYS_IMEM.
>> Loading 36 Kbytes to SYS_IMEM.
>> Loading 40 Kbytes to SYS_IMEM.
>> Loading 44 Kbytes to SYS_IMEM.
>> Loading 45 Kbytes to SYS_IMEM.
>> Successfully Loaded to SYS_IMEM.(Total 45 Kbytes)
>> Flash Image was normally loaded to SYS_IMEM.
>> Checking for device status.
>> [Verifying Hello Protocol]
>> Sending Hello request 0 time(s).
>> SendSync EHOST_HELLO_RSP OK.
>> Hello Response OK.
>> Got Hello response for Hello request.
>> [Verifying Security Protocol]
>> Security Response OK.
>> Connected to flash bootloader.
1> ----------------------------------------------------------------------
>> PBL SOFTWARE HISTORY
1> ----------------------------------------------------------------------
>> 1.Smart Boot Diagnosis Tool v1.3.1 <analysis tool="" for="" booting="" failure="">
>> 2.PBL_VERSION_NUMBER [fc021834] = 1c6c6162
1> ----------------------------------------------------------------------
1> ----------------------------------------------------------------------
>> SECURE_BOOT_INFORMATION
1> ----------------------------------------------------------------------
>> [QFPROM - AP Anti-rollback Region of OEM Region ]
>> QFPROM_AP_ANTIROLLBACK_1 [0xFC4B80B8] = 0x00000000
>> QFPROM_AP_ANTIROLLBACK_2 [0xFC4B80BC] = 0x00000000
>> QFPROM_AP_ANTIROLLBACK_3 [0xFC4B80C0] = 0x00000000
>> QFPROM_AP_ANTIROLLBACK_4 [0xFC4B80C4] = 0x00000000
1> ----------------------------------------------------------------------
>> QFPROM_DEVICE_SN_1 [0xFC4B81F0] = 0x1256AFAE
>> QFPROM_DEVICE_SN_2 [0xFC4B81F4] = 0x8800000B
1> ----------------------------------------------------------------------
>> QFPROM_MSA_ANTIROLLBACK_1 [0xFC4B80C8] = 0x00000000
>> QFPROM_MSA_ANTIROLLBACK_2 [0xFC4B80CC] = 0x00000000
1> ----------------------------------------------------------------------
>> [QFPROM QFuse INFO]
>> QFPROM_OEM_ID_LSB [0xFC4B80F0] = 0x00310000
>> QFPROM_OEM_ID_MSB [0xFC4B80F4] = 0x00000000
>> QFPROM_SECURE_BOOT_ENABLE_LSB [0xFC4B83F8] = 0x00202020
>> QFPROM_SECURE_BOOT_ENABLE_MSB [0xFC4B83FC] = 0x00000000
>> QFPROM_JTAG_DISABLE_LSB [0xFC4B80E8] = 0x3FC000C0
>> QFPROM_JTAG_DISABLE_MSB [0xFC4B80EC] = 0x040001FE
1> ----------------------------------------------------------------------
>> JTAG_ID [0xFC4BE0E0] = 0x107B40E1
>> OEM_ID [0xFC4BE0E4] = 0x00310000
>> SERIAL_NUM_MSB [0xFC4B81F4] = 0x8800000B
>> SERIAL_NUM_LSB [0xFC4B81F0] = 0x1256AFAE
>> [SECURITY INFO]
>> OEM_CONFIG_ROW0_LSB_ADDR [0xFC4B80E8] = 0x3FC000C0
>> OEM_CONFIG_ROW0_MSB_ADDR [0xFC4B80EC] = 0x040001FE
>> OEM_CONFIG_ROW1_LSB_ADDR [0xFC4B80F0] = 0x00310000
>> OEM_CONFIG_ROW1_MSB_ADDR [0xFC4B80F4] = 0x00000000
>> FEAT_CONFIG_ROW0_LSB_ADDR [0xFC4B80F8] = 0x00B08010
>> FEAT_CONFIG_ROW0_MSB_ADDR [0xFC4B80FC] = 0x00000000
>> FEAT_CONFIG_ROW1_LSB_ADDR [0xFC4B8100] = 0x00000001
>> FEAT_CONFIG_ROW1_MSB_ADDR [0xFC4B8104] = 0x0004785F
1> ----------------------------------------------------------------------
>> Start Address : 0xfc102140
>> End Address : 0xfc102c80
1> ----------------------------------------------------------------------
>> PBL_APPS LOG
1> ----------------------------------------------------------------------
>> PBL_LOG_COUNT=15
>> LOG_CODE :: 0xef010800 [ DECODED : 0x00010800 ]
>> TIMESTAMP :: 0x0002f50c
>> LOG_CODE :: 0xef0f0203 [ DECODED : 0x000f0203 ]
>> TIMESTAMP :: 0x0002fb8e
>> LOG_CODE :: 0xef010802 [ DECODED : 0x00010802 ]
>> TIMESTAMP :: 0x000330c9
>> LOG_CODE :: 0xef010804 [ DECODED : 0x00010804 ]
>> TIMESTAMP :: 0x0003471e
>> LOG_CODE :: 0xef010806 [ DECODED : 0x00010806 ]
>> TIMESTAMP :: 0x00034a84
>> LOG_CODE :: 0xef010808 [ DECODED : 0x00010808 ]
>> TIMESTAMP :: 0x00034b25
>> LOG_CODE :: 0xef01080a [ DECODED : 0x0001080a ]
>> TIMESTAMP :: 0x00034bae
>> LOG_CODE :: 0xef0f0300 [ DECODED : 0x000f0300 ]
>> TIMESTAMP :: 0x00034c11
>> LOG_CODE :: 0xef01080c [ DECODED : 0x0001080c ]
>> TIMESTAMP :: 0x00034c48
>> LOG_CODE :: 0xef5d0200 [ DECODED : 0x005d0200 ]
>> TIMESTAMP :: 0x00034d17
>> LOG_CODE :: 0xef5d0400 [ DECODED : 0x005d0400 ]
>> TIMESTAMP :: 0x0006f367
>> LOG_CODE :: 0xef5d0201 [ DECODED : 0x005d0201 ]
>> TIMESTAMP :: 0x0006f3bc
>> LOG_CODE :: 0xef0f0600 [ DECODED : 0x000f0600 ]
>> TIMESTAMP :: 0x0009bad1
>> LOG_CODE :: 0xef0f0500 [ DECODED : 0x000f0500 ]
>> TIMESTAMP :: 0x0714aad1
>> LOG_CODE :: 0xefa00502 [ DECODED : 0x00a00502 ]
>> TIMESTAMP :: 0x071766a9
1> ----------------------------------------------------------------------
>> < PBL DUMP LOG >
1> ----------------------------------------------------------------------
>> 1> PBL_GENERAL_LOG_FUNC_EXEC
1> PBL_FUSE_LOG_DEFAULT
1> PBL_GENERAL_LOG_DEFAULT
1> PBL_GENERAL_LOG_DEFAULT
1> PBL_GENERAL_LOG_DEFAULT
1> PBL_GENERAL_LOG_DEFAULT
1> PBL_GENERAL_LOG_DEFAULT
1> PBL_FUSE_FAST_BOOT
1> PBL_GENERAL_LOG_DEFAULT
1> PBL_SDCC_LOG_DETECT_PORT_ACCESS_ERR
1> PBL_SDCC_LOG_CARD_TYPE_ERR
1> PBL_SDC_LOG_DEFAULT
1> PBL_FUSE_USB_ENUM_TIMEOUT
1> PBL_FUSE_AP_SW_REV
1> PBL_AUTHENTICATION_LOG_DEFAULT
>> Logged Time : 2016-09-02 15:47:33...successfully Completed.
>> Saved Log File(LOG_LGD858HK_AHKG_HKG_20160902_154733.txt) successfully.
scamex said:
Hi, after some time searching for tools and info i have gathered a few working tools and service manuals for our belloved G3.
Here is the Service Manual Link
Here is the Smart Boot Diagnostic Tool Link
Here is the QDLoader HS-USB driver for 64bit windows pc Link
Here is the QDLoader HS-USB driver for 32bit windows pc Link
Here is the AP-CHIP dll and ATT achive for Flash Tool for use without LG B2B connection Link
Here is the LG FlashTool 1.5.10.1120 Link
Here is the Megalock .dll file to overwrite in flash tool folder for B2B nologin Link
Here is the How To Calibrate document Link
Here is a document that shows how to Flash a "dead boot" LG phone Link
Hope this will help someone or teaching others. Excuse my english and if i posted in a wrong section. Thanks !
Click to expand...
Click to collapse
Thanks. Was very usefull
this post save me multiple times;
everityme i use autoreck on a stock LG i got bulk error ecc and smartboot is the only tool that instantaneously unbrick the phone
:good:
Related
hi, when I tried to flash my motorola defy with sbf_flash I get error:verifying CG31 Checksum error (Expected 0x9a68, Got 0xc5a4)
===JRDNEM_U3_3.4.2_179-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTCEE_P016_A016_HWp3_Service1FF.sbf ===
Index[1]: Unexpected chip 32
Index[2]: Unexpected chip 32
Index[3]: Unexpected chip 32
Index[4]: Unexpected chip 32
Index[5]: Unexpected chip 32
Index[6]: Unexpected chip 32
Index[7]: Unexpected chip 32
Index[8]: Unexpected chip 32
Index[9]: Unexpected chip 32
Index[10]: Unexpected chip 32
Index[11]: Unexpected chip 32
Index[12]: Unexpected chip 32
Index[13]: Unexpected chip 32
00: RDL03 0x82000000-0x8204CFFF 4035 AP
01: CG31 0xB0280000-0xB02847FF 9A68 AP
02: CG32 0xC7A00000-0xC7A207FF 4805 AP
03: CG33 0xB2000000-0xB2DC07FF 8BAC AP
04: CG34 0xB0700000-0xB07047FF AB80 AP
05: CG35 0xB1000000-0xB17FFFFF 100C AP
06: CG39 0xB3300000-0xC79C07FF C7E6 AP
07: CG42 0xB0800000-0xB0842FFF 4BB7 AP
08: CG45 0xB0C00000-0xB0F007FF 738D AP
09: CG47 0xB1800000-0xB1FFFFFF 45F0 AP
10: CG53 0xB2F00000-0xB2F007FF FDFF AP
11: CG61 0xB0B00000-0xB0B7FFFF 4A7C AP
12: CG64 0xB0000000-0xB00047FF 85D0 AP
13: CG65 0xB0180000-0xB01847FF 2409 AP
>> waiting for phone: Connected.
>> uploading RDL03: 100.0%
-- OK
>> verifying ramloader
-- OK
>> executing ramloader
-- OK
>> waiting for phone: Connected.
>> sending erase
-- OK
>> uploading CG31: 100.0%
-- OK
>> uploading CG32: 100.0%
-- OK
>> uploading CG33: 100.0%
-- OK
>> uploading CG34: 100.0%
-- OK
>> uploading CG35: 100.0%
-- OK
>> uploading CG39: 100.0%
-- OK
>> uploading CG42: 100.0%
-- OK
>> uploading CG45: 100.0%
-- OK
>> uploading CG47: 100.0%
-- OK
>> uploading CG53: 100.0%
-- OK
>> uploading CG61: 100.0%
-- OK
>> uploading CG64: 100.0%
-- OK
>> uploading CG65: 100.0%
-- OK
>> verifying CG31
Checksum error (Expected 0x9a68, Got 0xc5a4)
!! failed
>> verifying CG32
Checksum error (Expected 0x4805, Got 0x4a05)
!! failed
>> verifying CG33
usb_bulk_read -110
!! failed
>> verifying CG34
usb_bulk_read -110
!! failed
>> verifying CG35
usb_bulk_write -110
!! failed
>> verifying CG39
usb_bulk_write -110
!! failed
>> verifying CG42
usb_bulk_write -110
!! failed
>> verifying CG45
usb_bulk_write -110
!! failed
>> verifying CG47
usb_bulk_write -110
!! failed
>> verifying CG53
usb_bulk_write -110
!! failed
>> verifying CG61
usb_bulk_write -110
!! failed
>> verifying CG64
usb_bulk_write -110
!! failed
>> verifying CG65
usb_bulk_write -110
!! failed
>> rebooting
usb_bulk_write -110
Click to expand...
Click to collapse
Now, it does not boot, going straight to bootloader and no futher, regardless of the buttons I'm pressing.
What I can doing to unbrick my defy?
Thank's!
Were you trying to downgrade? What rom were you on earlier?
Sent from my MB525 using Tapatalk
ryan8r said:
Were you trying to downgrade? What rom were you on earlier?
Click to expand...
Click to collapse
I don't know what rom version was before, maybe I can somehow check it?
Were you on Eclair, Froyo or Gingerbread?
Sent from my MB525 using Tapatalk
I am having the same issues here, my defy wont load, been stuck in the bootloader for a couple of hours. Any help will be greatly aprecciated
I'm having the same error's. Somebody solved the problem or know, what is the problem?
Hi All,
I was updating my LG 540GT toswift droid 2.3 from 2.1.While using kdz_fw_upd.exe ,some error occured in between and the process was some what like stuck and not responding.So i exit the program,(meanwhile phone was showing downloading mode).So i unplugged the usb cable and removed the battery to restart it.But after that it is not even switching ON.i tried to go to recovery mode by pressing volume down+camera+power keys,button nothing happened.i tried home+volume up key,the same result.
i tried using Kdz_fw_upd.exe again,its showing "PHONE WAS NOT FOUND" error.I tried all the ways i could.Please help me if i can do anything with it?
Its bricked.
Sent from my GT540 using xda premium
So i cant do anything???
anoopmohamed said:
So i cant do anything???
Click to expand...
Click to collapse
if the phone doesnt turn on at all then u can't
do anything about it..
can the service center rectify it??my warranty expired lst month.i am ready to pay charge. they wiil not replace as the warranty expired.or the phone is unusable permenantly?
anoopmohamed said:
can the service center rectify it??my warranty expired lst month.i am ready to pay charge. they wiil not replace as the warranty expired.or the phone is unusable permenantly?
Click to expand...
Click to collapse
actually u do have little hope!
Follow this, this might unbrick ur phone if u
are lucky!
[HOW-TO] Repair your device if it feels like dead | When you click power button nothing happens (Note that this may or may not work)
Make sure you use USB ports that are in back of youre PC, dont use front ones.
Disable LGE Virtual Modem. In your Windows operating system, go to Control Panel > System > Hardware > Device Manager > Modems > Right click on LGE Virtual Modem and click Disable.
Try to boot your phone into Emergency/Download mode (VOL DOWN + POWER).
If the phone booted into Emergency/Download mode, launch KDZ Updater.
In TYPE dropdown menu, choose EMERGENCY.
Load KDZ(ROM) and flash your phone.
If the phone failed to boot into Emergency/Download mode (VOL DOWN + POWER), launch KDZ Updater.
In TYPE dropdown menu, choose CS_EMERGENCY.
Load KDZ(ROM) and flash your phone.
Thanks to fishears!
Thanks,
i had tried it all earlier :'( bt in vain...
cursing the moment where i thought of upgrading
anoopmohamed said:
Thanks,
i had tried it all earlier :'( bt in vain...
cursing the moment where i thought of upgrading
Click to expand...
Click to collapse
trust me i know how it feels...
the first week i got my phone i stuffed it up by trying
fastboot... then i managed to fix it myself. from then on
i stuffed my phone nearly every single time i tried something...
But i always managed to fix it!
But i guess bad luck 4 u..
Thanks dude..
i think my bootloader is gone if it is switching ON i had hope.bt
I heared something about Riff box jtag which can repair from brick..but i am not sure.
Can the service center fix this issue???
anoopmohamed said:
Thanks dude..
i think my bootloader is gone if it is switching ON i had hope.bt
I heared something about Riff box jtag which can repair from brick..but i am not sure.
Can the service center fix this issue???
Click to expand...
Click to collapse
yeah they can be changing the motherboard!
But i think that will cost more than the phone itself..
If u have warranty just say ur phone doesn't turn on and
they will give u a new one!
Actually the 1 warranty expired by last month(oct). When i purchased it,it came with 1.6,later i upgraded to 2.1 successfully.With this confidence only i planned to upgraded to swift droid 2.3.Do u know what had went wrong??
anoopmohamed said:
Actually the 1 warranty expired by last month(oct). When i purchased it,it came with 1.6,later i upgraded to 2.1 successfully.With this confidence only i planned to upgraded to swift droid 2.3.Do u know what had went wrong??
Click to expand...
Click to collapse
Yeah u took out the USB cable while flashing!
Sent from my GT540 using xda premium
but the program was non responsive and return with some error
[00:15:55:880] : TYPE_WPARAM_UPGRADE_ERROR
[00:15:55:880] : ¸Þ½ÃÁö º¸³¿ - TYPE_WPARAM_UPGRADE_ERROR Error Code = 1002...
so i had exit the program,then only i removed the cable unfortunate..
anoopmohamed said:
but the program was non responsive and return with some error
[00:15:55:880] : TYPE_WPARAM_UPGRADE_ERROR
[00:15:55:880] : ¸Þ½ÃÁö º¸³¿ - TYPE_WPARAM_UPGRADE_ERROR Error Code = 1002...
so i had exit the program,then only i removed the cable unfortunate..
Click to expand...
Click to collapse
I dont know about that ....
Sent from my GT540 using xda premium
the program showed up a windows-message that it does not work anymore ?
or was it just doing nothing ?
1st the program showed windows error(im using vista) asking the close down the program.So i closed and restarted the program and loaded the kdz file and it again started to do the work.but after few seconds it displayed some upgrade error like "WPARAM_UPGRADE_ERROR Error Code = 1002"
the log file is shown below
[00:15:21:945] : =============================================
[00:15:21:945] : Log is started on 26.11.2011, at 00:15:21:945,
executable: C:\Users\anoopmohamed\Desktop\swift droid\KDZ_FW_UPD.exe (ProcID: 0x00001120),
compile time : Sep 8 2010 17:19:53
[00:15:21:945] : Version :
[00:15:21:947] : strFilename1 = eur
[00:15:21:948] : m_DlMode = 4, m_strBinaryPath = C:\ProgramData\LGMOBILEAX\Phone\europen+fastboot.dz, m_nSelectedImages= 70787108
[00:15:46:357] : Start Web Downloading
[00:15:46:357] : Get Usb Port
[00:15:46:436] : rsi.strFriendlyName=Standard Serial over Bluetooth link (COM6)
[00:15:46:436] : Remove Standard Serial over Bluetooth link (COM6)
[00:15:46:436] : rsi.strFriendlyName=Standard Serial over Bluetooth link (COM8)
[00:15:46:436] : Remove Standard Serial over Bluetooth link (COM8)
[00:15:46:436] : rsi.strFriendlyName=Standard Serial over Bluetooth link (COM5)
[00:15:46:436] : Remove Standard Serial over Bluetooth link (COM5)
[00:15:46:436] : rsi.strFriendlyName=Standard Serial over Bluetooth link (COM7)
[00:15:46:436] : Remove Standard Serial over Bluetooth link (COM7)
[00:15:46:436] : rsi.strFriendlyName=Standard Modem over Bluetooth link #2
[00:15:46:436] : Remove Standard Modem over Bluetooth link #2
[00:15:46:436] : rsi.strFriendlyName=Nokia 6300 Bluetooth Modem
[00:15:46:436] : Remove Nokia 6300 Bluetooth Modem
[00:15:46:436] : rsi.strFriendlyName=Agere Systems HDA Modem
[00:15:46:436] : Remove Agere Systems HDA Modem
[00:15:46:436] : rsi.strFriendlyName=RIM Virtual Serial Port v2 (COM29)
[00:15:46:436] : Remove RIM Virtual Serial Port v2 (COM29)
[00:15:46:436] : rsi.strFriendlyName=RIM Virtual Serial Port v2 (COM30)
[00:15:46:436] : Remove RIM Virtual Serial Port v2 (COM30)
[00:15:46:436] : rsi.strFriendlyName=LGE Android Platform USB Serial Port (COM13)
[00:15:46:436] : FriendlyNameList[iii].szFriendlyName=LGE Android Platform USB Serial Port
[00:15:46:436] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 1 - COM13
[00:15:46:436] : Port = COM13
[00:15:46:436] : Clear
[00:15:46:437] : Clear
[00:15:46:438] : UNKNOWN : Req(12) -> Rsp(13)
[00:15:46:438] : Clear
[00:15:46:439] : UNKNOWN : Req(12) -> Rsp(13)
[00:15:46:439] : Clear
[00:15:46:440] : UNKNOWN : Req(12) -> Rsp(13)
[00:15:46:440] : >> DIAG_STATUS_F FAILED
[00:15:46:445] : >>Get Model Name [DIAG_VERNO_F]
[00:15:46:445] : Clear
[00:15:46:446] : BAD CONN MODE : Req(0) -> Rsp(3)
[00:15:46:446] : Clear
[00:15:46:447] : BAD CONN MODE : Req(0) -> Rsp(3)
[00:15:46:447] : Clear
[00:15:46:448] : BAD CONN MODE : Req(0) -> Rsp(3)
[00:15:46:448] : Clear
[00:15:46:449] : BAD CONN MODE : Req(0) -> Rsp(3)
[00:15:46:449] : Clear
[00:15:46:450] : BAD CONN MODE : Req(0) -> Rsp(3)
[00:15:46:450] : Clear
[00:15:46:451] : BAD CONN MODE : Req(0) -> Rsp(3)
[00:15:46:451] : FAIL (No Phone)
[00:15:46:451] : GetModelName() Operation Failed Check Diag CMD
[00:15:46:451] : EMERGENCY Booting Mode
[00:15:46:451] : >>Get Model Name in Emergency Mode [DLOAD_VERREQ_F]
[00:15:46:451] : Clear
[00:15:46:451] : Clear
[00:15:46:452] : BS/GT540/7D
[00:15:46:452] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 0 - GT540
[00:15:46:452] : >>Get Mobile SW [DIAG_EXT_BUILD_ID_F]
[00:15:46:452] : Clear
[00:15:46:452] : Clear
[00:15:46:453] : DLOAD_NAK_F reason_msb = 6, reason_lsb = 6
[00:15:46:453] : [ DLOAD ERROR ] : NAK_INVALID_CMD
[00:15:46:453] : Clear
[00:15:46:454] : DLOAD_NAK_F reason_msb = 6, reason_lsb = 6
[00:15:46:454] : [ DLOAD ERROR ] : NAK_INVALID_CMD
[00:15:46:454] : Clear
[00:15:46:455] : DLOAD_NAK_F reason_msb = 6, reason_lsb = 6
[00:15:46:455] : [ DLOAD ERROR ] : NAK_INVALID_CMD
[00:15:46:455] : FAIL
[00:15:46:455] : Phone_Diag_Status = FALSE
[00:15:46:455] : Clear
[00:15:46:455] : Clear
[00:15:46:456] : DLOAD_NAK_F reason_msb = 3, reason_lsb = 3
[00:15:46:456] : [ DLOAD ERROR ] : NAK_INVALID_LEN
[00:15:46:456] : Clear
[00:15:46:457] : DLOAD_NAK_F reason_msb = 3, reason_lsb = 3
[00:15:46:457] : [ DLOAD ERROR ] : NAK_INVALID_LEN
[00:15:46:457] : Clear
[00:15:46:458] : DLOAD_NAK_F reason_msb = 3, reason_lsb = 3
[00:15:46:458] : [ DLOAD ERROR ] : NAK_INVALID_LEN
[00:15:46:458] : NV Write Fail : NV ITEM 9028(9028)
[00:15:46:558] : m_pPhoneCtrl->m_pDload->Dl_GetCommMode(&m_pPhoneCtrl->m_pDload->m_nCommMode)
[00:15:46:558] : >> GET DLOAD COMM MODE
[00:15:46:558] : Clear
[00:15:46:558] : Clear
[00:15:46:559] : [GetCommMode] Communication mode : 2
[00:15:46:559] : Pre Nand Download
[00:15:46:559] : >>Set Trusted Mode [DLOAD_NAND_SEC_MODE] sec_mode = 1 (1=trusted 0=NonTrusted)
[00:15:46:559] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - TRUSTED MODE
[00:15:46:559] : Clear
[00:15:46:559] : Clear
[00:15:46:560] : [COM13] >>NandFlashInitWithFile(PARTITION TBL), BinType =8
[00:15:46:560] : NandFlashInitWithFile :: LG3GBinaryList[BinType].szBinaryTypeName = PARTITION TBL, BinType = 8
[00:15:46:560] : NandFlashInitWithFile ::
[00:15:46:560] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - INIT PARTITION TBL
[00:15:46:560] : Clear
[00:15:46:560] : Clear
[00:15:49:672] : DLOAD_NAK_F reason_msb = 55, reason_lsb = 55
[00:15:49:672] : [ JNAND ERROR ] : ERR_RESERVED_x37
[00:15:49:672] : Clear
[00:15:52:777] : DLOAD_NAK_F reason_msb = 55, reason_lsb = 55
[00:15:52:777] : [ JNAND ERROR ] : ERR_RESERVED_x37
[00:15:52:777] : Clear
[00:15:55:880] : DLOAD_NAK_F reason_msb = 55, reason_lsb = 55
[00:15:55:880] : [ JNAND ERROR ] : ERR_RESERVED_x37
[00:15:55:880] : [COM13] FAIL
[00:15:55:880] : Clear
[00:15:55:880] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - Close Port
[00:15:55:880] : Close Port<<
[00:15:55:880] : TYPE_WPARAM_UPGRADE_ERROR
[00:15:55:880] : ¸Þ½ÃÁö º¸³¿ - TYPE_WPARAM_UPGRADE_ERROR Error Code = 1002
[00:15:55:904] : Log finished
So no process was showing later.I tried a couple of times,same.So i thought of doing it later.Exit the program.But the phone was still in DOWNLOAD MODE,then i pulled out the battery and the usb cable from it.
Hey Guys,
I have a german Vodafone branding Defy, which only boots in Bootloader. I tried flashing some sbf's with RSD-Lite 4.9 and 6.1.5 but everytime I'm getting the error verifying Code Group 32.
Trying to flash with sbf_flash on linux giving me this:
[email protected]:~/Downloads$ sudo ./sbf_flash -f eclair2.sbf
[sudo] password for daniel:
SBF FLASH 1.24 (mbm)
http://opticaldelusion.org
=== eclair2.sbf ===
Index[1]: Unexpected chip 32
Index[2]: Unexpected chip 32
Index[3]: Unexpected chip 32
Index[4]: Unexpected chip 32
Index[5]: Unexpected chip 32
Index[6]: Unexpected chip 32
Index[7]: Unexpected chip 32
Index[8]: Unexpected chip 32
Index[9]: Unexpected chip 32
Index[10]: Unexpected chip 32
Index[11]: Unexpected chip 32
Index[12]: Unexpected chip 32
Index[13]: Unexpected chip 32
Index[14]: Unexpected chip 32
00: RDL03 0x82000000-0x8204CFFF C943 AP
01: CG31 0xB0280000-0xB02847FF 4972 AP
02: CG32 0xC7A00000-0xC7A207FF 4805 AP
03: CG33 0xB2000000-0xB2DC07FF 1ABC AP
04: CG34 0xB0700000-0xB07047FF D9D1 AP
05: CG35 0xB1000000-0xB17FFFFF 3E04 AP
06: CG39 0xB3300000-0xC79C07FF F954 AP
07: CG40 0xC7B00000-0xC7D59FFF D196 AP
08: CG42 0xB0800000-0xB0842FFF C4B4 AP
09: CG45 0xB0C00000-0xB0F007FF 3664 AP
10: CG47 0xB1800000-0xB1FFFFFF 695F AP
11: CG53 0xB2F00000-0xB2F007FF FDFF AP
12: CG61 0xB0B00000-0xB0B7FFFF 538B AP
13: CG64 0xB0000000-0xB00047FF 85D0 AP
14: CG65 0xB0180000-0xB01847FF 2409 AP
>> waiting for phone: Connected.
>> uploading RDL03: 100.0%
-- OK
>> verifying ramloader
-- OK
>> executing ramloader
-- OK
>> waiting for phone: Connected.
>> sending erase
-- OK
>> uploading CG31: 100.0%
-- OK
>> uploading CG32: 100.0%
-- OK
>> uploading CG33: 100.0%
-- OK
>> uploading CG34: 100.0%
-- OK
>> uploading CG35: 100.0%
-- OK
>> uploading CG39: 100.0%
-- OK
>> uploading CG40: 100.0%
-- OK
>> uploading CG42: 100.0%
-- OK
>> uploading CG45: 100.0%
-- OK
>> uploading CG47: 100.0%
-- OK
>> uploading CG53: 100.0%
-- OK
>> uploading CG61: 100.0%
-- OK
>> uploading CG64: 100.0%
-- OK
>> uploading CG65: 100.0%
-- OK
>> verifying CG31
Checksum error (Expected 0x4972, Got 0xc461)
!! failed
>> verifying CG32
usb_bulk_read -110
!! failed
>> verifying CG33
usb_bulk_read -110
!! failed
>> verifying CG34
usb_bulk_write -110
!! failed
>> verifying CG35
usb_bulk_write -110
!! failed
>> verifying CG39
usb_bulk_write -110
!! failed
>> verifying CG40
usb_bulk_write -110
!! failed
>> verifying CG42
usb_bulk_write -110
!! failed
>> verifying CG45
usb_bulk_write -110
!! failed
>> verifying CG47
usb_bulk_write -110
!! failed
>> verifying CG53
usb_bulk_write -19
!! failed
>> verifying CG61
usb_bulk_write -19
!! failed
>> verifying CG64
usb_bulk_write -19
!! failed
>> verifying CG65
usb_bulk_write -19
!! failed
>> rebooting
usb_bulk_write -19
Click to expand...
Click to collapse
Idon't have acces to recovery, can anyone help me pls?
DanielKrause said:
Hey Guys,
I have a german Vodafone branding Defy, which only boots in Bootloader. I tried flashing some sbf's with RSD-Lite 4.9 and 6.1.5 but everytime I'm getting the error verifying Code Group 32.
Trying to flash with sbf_flash on linux giving me this:
Idon't have acces to recovery, can anyone help me pls?
Click to expand...
Click to collapse
Some people managed to fix it using the original USB cable/different USB port/different PC, most went to the service center after frustration got to them.
I'll see what I can dig up.
EDIT- Might be a RAM/Flash memory problem.
hotdog125 said:
Some people managed to fix it the original USB cable/different USB port/different PC, most went to the service center after frustration got to them.
I'll see what i can dig up.
Click to expand...
Click to collapse
tried different cables and ports on win 7 and different cables on linux. next try is another usb port thanks for trying to help me
DanielKrause said:
tried different cables and ports on win 7 and different cables on linux. next try is another usb port thanks for trying to help me
Click to expand...
Click to collapse
Was your Win7 64bit? It might give problems. Also, people in droidforums reported fixing the issue by using a more powerful PC. Or, try downloading the sbf from some other site/other PC.
EDIT - Some people also reported their Defys to randomly revive after a few days in the dust.
hotdog125 said:
Was your Win7 64bit? It might give problems. Also, people in droidforums reported fixing the issue by using a more powerful PC. Or, try downloading the sbf from some other site/other PC.
Click to expand...
Click to collapse
Nope, my Win7 is 32bit version. But tried it with a Win 7 64bit pc but getting same error. I'm getting the sbf's from this site: http://sbf.droid-developers.org/umts_jordan/list.php
Do u have another site u would recommend?
trying now with this sbf: JORDN_U3_97.21.51
DanielKrause said:
Nope, my Win7 is 32bit version. But tried it with a Win 7 64bit pc but getting same error. I'm getting the sbf's from this site: http://sbf.droid-developers.org/umts_jordan/list.php
Do u have another site u would recommend?
trying now with this sbf: JORDN_U3_97.21.51
Click to expand...
Click to collapse
I believe that is the best site available for Defy SBFs.
EDIT - See this - http://forum.xda-developers.com/showthread.php?t=966537
hotdog125 said:
I believe that is the best site available for Defy SBFs.
EDIT - See this - http://forum.xda-developers.com/showthread.php?t=966537
Click to expand...
Click to collapse
But i can't do anything with it. The latest sbf I've tried to flash was the JRDNEM_U3_3.4.2_179-4.4.
I didn't flashed a gingerbread rom or a dafy + rom. Is there a way to get from bootloader to recovery per adb?
DanielKrause said:
But i can't do anything with it. The latest sbf I've tried to flash was the JRDNEM_U3_3.4.2_179-4.4.
I didn't flashed a gingerbread rom or a dafy + rom. Is there a way to get from bootloader to recovery per adb?
Click to expand...
Click to collapse
I don't think so.
Hi folks,
So my MI 9T was hardbricked when I stopped a flashing mid-process. I'm using a UMT dongle with authorization credits to flash a fastboot rom via EDL mode. According to the flashing software (QCfire v5.1) the process is successful, but the phone won't turn on. Can someone help me out and tell me what I'm doing wrong? Am I flashing the wrong ROM?
Model: M1903F10G
Purchased in Germany
ROM: davinci_eea_global_images_V10.3.15.0.PFJEUXM_20190921.0000.00_9.0_eea
QCfire log:
Operation : Flash
Checking for existing devices...Found
Port : Qualcomm HS-USB QDLoader 9008 (COM10)
Driver Info : Qualcomm Incorporated, qcusbser.sys, 2.1.0.5
Opening Port...OK
Init Handshake Sequence...OK
Hardware ID : E1600E00 [E1600E00] 00007200
OPK_DATA : 4B60244704D721E5B96DD5BB7233886E38F2198FBDE6433FCE1D25A7B0472DD7
Initializing Protocol...OK
Sending Loader [prog_ufs_firehose_sdm855_ddr.elf]...Done
Executing Loader...OK
Auth Enabled Device! You need Mi Auth Account to service!
Reading Auth Blob...OK
Blob : NDE1MTQxNDE0MTQ3MzA0MjQxNDE0Mjc2MzU0RTRGNTE0NDUzNEY0QTRCNTM0QzQ0NjM2ODZBNjE1NzQ3MzAzNTU4NDczNjM5Mzg0MT==
Requesting UMT Server for Auth Data...OK
Credits Left: 0
Authenticating...OK
Detecting Chip Type...OK
Using Alternate Method...
Hardware : E1600E00, UFS, 64 GB
LU Count : 6 [0x00E98800] [0x00000800] [0x00000800] [0x00002000] [0x00040000] [0x0000A000]
WARNING! High Speed Driver is not installed.
Please install driver from QcFire\Drivers folder using Device Manager.
Payload Info : In: 65536 [65536], Out: 1048576, Sector Size: 4096
Writing [dummy.img] -> [switch] ...Done
Writing [misc.img] -> [misc] ...Done
Writing [logfs_ufs_8mb.bin] -> [logfs] ...Done
Writing [vendor.img ] -> [vendor]...Done
Writing [system.img ] -> [system]...Done
Writing [imagefv.elf] -> [imagefv] ...Done
Writing [recovery.img] -> [recovery] ...Done
Writing [cache.img ] -> [cache]...Done
Writing [cust.img ] -> [cust]...Done
Writing [userdata.img ] -> [userdata]...Done
Writing [gpt_main0.bin] -> [PrimaryGPT] ...Done
Writing [gpt_backup0.bin] -> [BackupGPT] ...Done
Applying Patches................Done
Resetting device...Done
Operation Finished.
QcFire Ver. 5.1
Hello !
I'm in the exact same situation as you (hardbricked) but with the global image "davinci_global_images_V10.3.11.0.PFJMIXM_20190802.0000.00_9.0_global".
Could you indicate me how were you able to flash the image through EDL ? Was it using Xiaomi Flash tool ? I tried that and it says that i'm not authorized to do that operation
Thanks in advance !
u can't if u don't have a EDL authorized Account and u won't get one. Unless you pay around $50 for a EDL Flash.
As long as I can fix this expensive paperweight I think that even paying is fine... Do you have the details on how to do it ?
Hello Xda Experts,
I own LG D855. on fulmics MM rom. it started freezing and hanging so in TWRP i cleard cache and dalvik cache. after boot it freeze on boot logo.
so i decided to flash rom again by twrp. but i unable to do so. because its giving error failed to mout internal storage system etc...
download mode was showing but after 10 secs blank screen.
After that i decided to do hard brick method by board diag. after 9008 mode. i got AP: passed Emmc: failed
Failed to open partition from EMMC.
now i cant boot in twrp nothing. totally dead. no logo.
here is lg smart boot log:
>> ---------------------------- Start Logging ----------------------------
>> USB Status : Qualcomm HS-USB QDLoader 9008 (COM14)
>> Ready to access the target board...
>> BootLoader File : All EU Global_XXXX_XXXX.mbn
>> 1. Model : All EU Global , 2. Suffix : XXXX , 3. Operator : XXXX
>> Bootloader : All EU Global_XXXX_XXXX.mbn
>> AP Chip : MSM8974_G3 , BootLoader : All EU Global_XXXX_XXXX.mbn
>> Trying Connection To Device with sahara protocol for AP Chip.
>> Successfully Connection To Device with sahara protocol for AP Chip.
>> connected with Sahara Protocol successfully.
>> Loading flash to SYS_IMEM.
>> Loading 0 Kbytes to SYS_IMEM.
>> Loading 4 Kbytes to SYS_IMEM.
>> Loading 8 Kbytes to SYS_IMEM.
>> Loading 12 Kbytes to SYS_IMEM.
>> Loading 16 Kbytes to SYS_IMEM.
>> Loading 20 Kbytes to SYS_IMEM.
>> Loading 24 Kbytes to SYS_IMEM.
>> Loading 28 Kbytes to SYS_IMEM.
>> Loading 32 Kbytes to SYS_IMEM.
>> Loading 36 Kbytes to SYS_IMEM.
>> Loading 40 Kbytes to SYS_IMEM.
>> Loading 44 Kbytes to SYS_IMEM.
>> Loading 45 Kbytes to SYS_IMEM.
>> Successfully Loaded to SYS_IMEM.(Total 45 Kbytes)
>> Flash Image was normally loaded to SYS_IMEM.
>> Checking for device status.
>> [Verifying Hello Protocol]
>> Sending Hello request 0 time(s).
>> SendSync EHOST_HELLO_RSP OK.
>> Hello Response OK.
>> Got Hello response for Hello request.
>> [Verifying Security Protocol]
>> Security Response OK.
>> Connected to flash bootloader.
1> ----------------------------------------------------------------------
>> PBL SOFTWARE HISTORY
1> ----------------------------------------------------------------------
>> 1.Smart Boot Diagnosis Tool v1.3.1 <Analysis Tool for Booting failure>
>> 2.PBL_VERSION_NUMBER [fc021834] = 1c6c6162
1> ----------------------------------------------------------------------
1> ----------------------------------------------------------------------
>> SECURE_BOOT_INFORMATION
1> ----------------------------------------------------------------------
>> [QFPROM - AP Anti-rollback Region of OEM Region ]
>> QFPROM_AP_ANTIROLLBACK_1 [0xFC4B80B8] = 0x00000000
>> QFPROM_AP_ANTIROLLBACK_2 [0xFC4B80BC] = 0x00000000
>> QFPROM_AP_ANTIROLLBACK_3 [0xFC4B80C0] = 0x00000000
>> QFPROM_AP_ANTIROLLBACK_4 [0xFC4B80C4] = 0x00000000
1> ----------------------------------------------------------------------
>> QFPROM_DEVICE_SN_1 [0xFC4B81F0] = 0x0FF90131
>> QFPROM_DEVICE_SN_2 [0xFC4B81F4] = 0x8800000B
1> ----------------------------------------------------------------------
>> QFPROM_MSA_ANTIROLLBACK_1 [0xFC4B80C8] = 0x00000000
>> QFPROM_MSA_ANTIROLLBACK_2 [0xFC4B80CC] = 0x00000000
1> ----------------------------------------------------------------------
>> [QFPROM QFuse INFO]
>> QFPROM_OEM_ID_LSB [0xFC4B80F0] = 0x00310000
>> QFPROM_OEM_ID_MSB [0xFC4B80F4] = 0x00000000
>> QFPROM_SECURE_BOOT_ENABLE_LSB [0xFC4B83F8] = 0x00202020
>> QFPROM_SECURE_BOOT_ENABLE_MSB [0xFC4B83FC] = 0x00000000
>> QFPROM_JTAG_DISABLE_LSB [0xFC4B80E8] = 0x3FC000C0
>> QFPROM_JTAG_DISABLE_MSB [0xFC4B80EC] = 0x040001FE
1> ----------------------------------------------------------------------
>> JTAG_ID [0xFC4BE0E0] = 0x107B40E1
>> OEM_ID [0xFC4BE0E4] = 0x00310000
>> SERIAL_NUM_MSB [0xFC4B81F4] = 0x8800000B
>> SERIAL_NUM_LSB [0xFC4B81F0] = 0x0FF90131
>> [SECURITY INFO]
>> OEM_CONFIG_ROW0_LSB_ADDR [0xFC4B80E8] = 0x3FC000C0
>> OEM_CONFIG_ROW0_MSB_ADDR [0xFC4B80EC] = 0x040001FE
>> OEM_CONFIG_ROW1_LSB_ADDR [0xFC4B80F0] = 0x00310000
>> OEM_CONFIG_ROW1_MSB_ADDR [0xFC4B80F4] = 0x00000000
>> FEAT_CONFIG_ROW0_LSB_ADDR [0xFC4B80F8] = 0x00B08010
>> FEAT_CONFIG_ROW0_MSB_ADDR [0xFC4B80FC] = 0x00000000
>> FEAT_CONFIG_ROW1_LSB_ADDR [0xFC4B8100] = 0x00000001
>> FEAT_CONFIG_ROW1_MSB_ADDR [0xFC4B8104] = 0x0004785F
1> ----------------------------------------------------------------------
>> Start Address : 0xfc102140
>> End Address : 0xfc102c80
1> ----------------------------------------------------------------------
>> PBL_APPS LOG
1> ----------------------------------------------------------------------
>> PBL_LOG_COUNT=11
>> LOG_CODE :: 0xef010800 [ DECODED : 0x00010800 ]
>> TIMESTAMP :: 0x0002bea8
>> LOG_CODE :: 0xef0f0203 [ DECODED : 0x000f0203 ]
>> TIMESTAMP :: 0x0002c53e
>> LOG_CODE :: 0xef010802 [ DECODED : 0x00010802 ]
>> TIMESTAMP :: 0x0002fa67
>> LOG_CODE :: 0xef010804 [ DECODED : 0x00010804 ]
>> TIMESTAMP :: 0x000310b6
>> LOG_CODE :: 0xef010806 [ DECODED : 0x00010806 ]
>> TIMESTAMP :: 0x000313ff
>> LOG_CODE :: 0xef010808 [ DECODED : 0x00010808 ]
>> TIMESTAMP :: 0x000314a0
>> LOG_CODE :: 0xef01080a [ DECODED : 0x0001080a ]
>> TIMESTAMP :: 0x00031515
>> LOG_CODE :: 0xef01080c [ DECODED : 0x0001080c ]
>> TIMESTAMP :: 0x0003155c
>> LOG_CODE :: 0xef0f0600 [ DECODED : 0x000f0600 ]
>> TIMESTAMP :: 0x00044c53
>> LOG_CODE :: 0xef0f0500 [ DECODED : 0x000f0500 ]
>> TIMESTAMP :: 0x08084edd
>> LOG_CODE :: 0xefa00502 [ DECODED : 0x00a00502 ]
>> TIMESTAMP :: 0x080b0add
1> ----------------------------------------------------------------------
>> < PBL DUMP LOG >
1> ----------------------------------------------------------------------
>> 1> PBL_GENERAL_LOG_FUNC_EXEC
1> PBL_FUSE_LOG_DEFAULT
1> PBL_GENERAL_LOG_DEFAULT
1> PBL_GENERAL_LOG_DEFAULT
1> PBL_GENERAL_LOG_DEFAULT
1> PBL_GENERAL_LOG_DEFAULT
1> PBL_GENERAL_LOG_DEFAULT
1> PBL_GENERAL_LOG_DEFAULT
1> PBL_FUSE_USB_ENUM_TIMEOUT
1> PBL_FUSE_AP_SW_REV
1> PBL_AUTHENTICATION_LOG_DEFAULT
>> Logged Time : 2020-08-03 01:47:06...successfully Completed.
>> Saved Log File(LOG_All EU Global_XXXX_XXXX_20200803_014706.txt) successfully.
Please HELP ME Properly in this. what i do now?