Database Users

sbf_flash error:verifying CG31

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?

[Q] Getting a working Android

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.

LG G3 D855 D850 Tools and Documentation

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:

Galaxy s5 SM-G901F

WELCOME
Samsung Galaxy s5 Do not start At the entrance to make bot
[ VOL +] + [ Home] + [ Power]
I can not write it any rom
because no one I can not enter a file in bot ? How to fix it ?
I download rom from sammobile
odin PDA fires
< ID: 0/003 > Added !!
< SSO > Enter CS for MD5 ..
< SSO > Check MD5 .. Do not unplug the cable ..
< SSO > Please wait ..
< SSO > G900FXXU1ANJ1_G900FXEO1ANJ1_G900FXXU1ANJ1_HOME.tar.md5 is valid .
< SSO > Checking MD5 finished sucessfully ..
< SSO > Leave CS ..
< ID: 0/003 > Odin v.3 engine (ID: 3 ) ..
< ID: 0/003 > File analysis ..
< ID: 0/003 > SetupConnection ..
< ID: 0/003 > Initialzation ..
< ID: 0/003 > Get PIT for mapping ..
< ID: 0/003 > Firmware update start ..
< ID: 0/003 > SingleDownload .
< ID: 0/003 > sbl1.mbn
< ID: 0/003 > NAND Write Home !!
< ID: 0/003 > aboot.mbn
< ID: 0/003 > rpm.mbn
< ID: 0/003 > FAIL ! ( Auth )
< ID: 0/003 >
< ID: 0/003 > Complete ( Write) operation failed .
< SSO > All threads completed . ( succeed 0 / failed 1)
the result of such

http://forum.xda-developers.com/showthread.php?p=59876587
think here is your answer

I cannot install any app because I've uninstalled system guard app [rooted device]

By running logcat while attempting to re-install the guard app (com.miui.guardprovider), I see the followin error (FYI I see this error when installing any app):
Code:
[ 01-21 03:49:18.090 1462: 2549 I/ActivityManager ]
START u0 {dat=file:///storage/emulated/0/Root_Uninstaller_Backup/Bezpečnostní prvky MIUI_null.apk cmp=com.google.android.packageinstaller/com.android.packageinstaller.InstallAppProgress (has extras)} from uid 10023 on display 0
[ 01-21 03:49:18.095 1462: 2549 D/ActivityTrigger ]
ActivityTrigger activityPauseTrigger
[ 01-21 03:49:18.098 3467: 3501 I/Finsky ]
[25] com.google.android.finsky.bo.an.run(6): Stats for Executor: NotificationAssistDatabaseManager [email protected][Running, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 6]
[ 01-21 03:49:18.106 1462: 2301 I/Timeline ]
Timeline: App_transition_ready time:1710168
[ 01-21 03:49:18.120 11313:11313 W/ResourceType ]
No package identifier when getting name for resource number 0x00000000
[ 01-21 03:49:18.124 1462: 2507 W/ResourceType ]
No package identifier when getting name for resource number 0x00000000
[ 01-21 03:49:18.125 1462: 2507 W/ ]
Unable to open '/storage/emulated/0/Root_Uninstaller_Backup/Bezpečnostní prvky MIUI_null.apk': Permission denied
[ 01-21 03:49:18.125 1462: 2507 W/zipro ]
Error opening archive /storage/emulated/0/Root_Uninstaller_Backup/Bezpečnostní prvky MIUI_null.apk: I/O Error
[ 01-21 03:49:18.125 1462: 2507 D/asset ]
failed to open Zip archive '/storage/emulated/0/Root_Uninstaller_Backup/Bezpečnostní prvky MIUI_null.apk'
[ 01-21 03:49:18.129 2724: 2724 W/ContextImpl ]
Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:788 android.content.ContextWrapper.sendBroadcast:411 android.content.ContextWrapper.sendBroadcast:411 com.miui.permcenter.install.PackageVerificationRecevier.ar:-1 com.miui.permcenter.install.PackageVerificationRecevier.onReceive:-1
[ 01-21 03:49:18.135 1462: 2332 W/ActivityManager ]
cann't getContentProviderImpl: guard, cpi is null.
[ 01-21 03:49:18.135 2724: 9453 E/ActivityThread ]
Failed to find provider info for guard
[ 01-21 03:49:18.135 2724: 9453 E/PackageVerifyedRecevier ]
parseApk
java.lang.IllegalArgumentException: Unknown URI content://guard
at android.content.ContentResolver.call(ContentResolver.java:1424)
at com.miui.permcenter.install.q.doInBackground(Unknown Source)
at com.miui.permcenter.install.q.doInBackground(Unknown Source)
at android.os.AsyncTask$2.call(AsyncTask.java:295)
at java.util.concurrent.FutureTask.run(FutureTask.java:237)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
at java.lang.Thread.run(Thread.java:818)
[ 01-21 03:49:18.135 2724: 9453 D/PackageVerifyedRecevier ]
verify package /storage/emulated/0/Root_Uninstaller_Backup/Bezpečnostní prvky MIUI_null.apk info: null
[ 01-21 03:49:18.135 2724: 9453 D/PackageVerifyedRecevier ]
verify package /storage/emulated/0/Root_Uninstaller_Backup/Bezpečnostní prvky MIUI_null.apk finish false
[ 01-21 03:49:18.136 1462: 2507 I/com.android.server.pm.PackageManagerServiceInjector ]
MIUILOG- INSTALL_FAILED_VERIFICATION_FAILURE uid: 10023 pkg : com.google.android.packageinstaller
[ 01-21 03:49:18.138 9998: 9998 D/PackageVerificationReceiver ]
PackageVerificationReceiver onReceive:Intent { act=com.miui.global.packageinstaller.action.verifypackage flg=0x10 cmp=com.miui.global.packageinstaller/.PackageVerificationReceiver }
Would it be possible to skip resolving the content://guard link? I've already tried to go to Settings -> System apps settings -> Security -> Security scan and unchecked the "Scan before installing" button, but the error is still the same :/
Any ideas how to fix this?
Btw, I've tried to post this to the development section, but I was rejected due to the fresh account, so that's why I'm writing here.

Dirty flash the ROM means just wipe catches and dalvic catches and flash ROM zip again.