Database Users

[Q] sbf_flash (linux) to download FROM phone -r -d --cgname :: nandroid alternative

these new commands seem promising
http://blog.opticaldelusion.org/2011/02/sbfflash-updates.html
will this function like the nandroid I should have setup?
but I am clearly misunderstanding something
Code:
[email protected]:~/vzw/grab$ sudo ./sbf_flash -r -d --userdata userdata.img
SBF FLASH 1.23 (mbm)
http://opticaldelusion.org
>> waiting for phone: Connected.
CG64 0xB0000000-0xB001FFFF mbr
CG63 0xB0020000-0xB003FFFF mbmloader
CG30 0xB0080000-0xB00FFFFF mbm
CG55 0xB0100000-0xB017FFFF mbmbackup
CG65 0xB0180000-0xB01FFFFF ebr
CG56 0xB0200000-0xB027FFFF bploader
CG31 0xB0280000-0xB02FFFFF cdt.bin
CG38 0xB0300000-0xB06FFFFF pds
CG34 0xB0700000-0xB077FFFF lbl
CG57 0xB0780000-0xB07FFFFF lbl_backup
CG42 0xB0800000-0xB08FFFFF logo.bin
CG41 0xB0900000-0xB0AFFFFF sp
CG61 0xB0B00000-0xB0B7FFFF devtree
CG62 0xB0B80000-0xB0BFFFFF devtree_backup
CG45 0xB0C00000-0xB0FFFFFF bpsw
CG35 0xB1000000-0xB13FFFFF boot
CG47 0xB1400000-0xB18FFFFF recovery
CG33 0xB1900000-0xB24FFFFF cdrom
CG44 0xB2500000-0xB257FFFF misc
CG43 0xB2580000-0xB25FFFFF cid
CG53 0xB2600000-0xB29FFFFF kpanic
CG39 0xB2A00000-0xC41FFFFF system
CG40 0xC4200000-0xCFFFFFFF cache
CG66 0xD0000000-0xDFFFFFFF preinstall
CG37 0xE0000000-0xEFFFFFFF userdata
>> waiting for phone: Connected.
>> downloading userdata: 0.0%
RX(7): [02]ERR[1e][8a][03]
>> downloading userdata: failed at e0000000/f0000000
Usage: /tmp/sbf_flash_1802_1801/Linux <filename>
downloading userdata: 0.0%
this did create a 256 meg file:userdata.img
buuuut I have no facility for verifying contents.. or do I?
is this new sbf_flash capable of SBF only /data/system

[Q] Officially Bricked?

Current Status: Brick
Hi,
I tried flashing stock SBF CEE 3.4.2-179-2 (retail central Europe) from here http://sbf.droid-developers.org/umts_jordan/list.php
I get IO and checksum errors resulting in FAIL. Now the phone does not boot.
Boot Loader
Code:
Bootloader
09.10
[B]Code Corrupt[/B]
Battery OK
OK to Program
Connect USB Data Cable
With RSD Lite 5.7 on Windows XP and MotoHelper drivers MotoHelper_2.0.40_Driver_4.9.0.exe
RSD Lite log::
2012/12/20 02:05:45 | -- | ERROR: AP Die ID: 1b10000791b963010000dcff0200
2012/12/20 02:05:45 | -- | ERROR: BP Die ID: 0000000000000000000000000000
2012/12/20 02:05:45 | -- | ERROR: AP Public ID: 35bc21063d231f528e8ce8e9b9942dcd161967c5
2012/12/20 02:05:45 | -- | ERROR: BP Public ID: 0000000000000000000000000000000000000000
2012/12/20 02:09:03 | 0 | ERROR: Phone[0000]: Error verifying Code Group 31 checksums. File: 0x9A68, Phone: 0x9C68 ->(1557)FlashOp
2012/12/20 02:09:03 | 0 | ERROR: Phone[0000]: Error verifying Code Group 32 checksums. File: 0x4805, Phone: 0x4A05 ->(1557)FlashOp
2012/12/20 02:13:03 | 0 | ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE003003F Command: RQRCS ->(1511)FlashOp
2012/12/20 02:26:03 | 0 | ERROR: Phone[0000]: Error verifying Code Group 65 checksums. File: 0x2409, Phone: 0x4A05 ->(1557)FlashOp
2012/12/20 02:26:03 | 0 | ERROR: Phone[0000]: Flash failed. ->(1195)PST_FP_FlashThread
2012/12/20 02:26:03 | 0 | ERROR: Flash failure: Phone[0000]: Error verifying Code Group 31 checksums. File: 0x9A68, Phone: 0x9C68 (Error Code: 31),
Detailed Error Details: Direction of the Error=No Direction, Command Value=4000000, Code Group Number=31 ->(625)FlashHdlr
Click to expand...
Click to collapse
Based on advice from skeevy420, I tried flashing with sbf_flash on linux.
sbf_flash:
Code:
Index[1]: Unexpected chip 32
>> Verifying CG32
Chechsum error (Expected 0x4805, Got 0x4a05)
!! failed
>> Verifying CG53
usb_bulk_write -110
!! failed
>> Verifying CG65
usb_bulk_write -19
!! failed
It looks like writing (or reading) fails, resulting in checksum errors.
More Info:
Verified MD5 of all my downloads
Tried a couple of other SBF from the same version (3.4.2)
Phone is from T-Mobile USA
Can I do something to change brick status?
Do I need a different SBF version?
Does read/write error really means hardware problem, cannot be fixed by software?
Do those IO errors mean driver version problem?
New sbf not compatible with old (old was stock T-Mobile Froyo)?
Accept the fact that the phone is hopeless?
Any help appreciated!

Here's a basic tutorial to flash sbf's with Linux -- RSDLite quit recognizing my Bravo and the Linux sbf_flash tool was the only way to fix it. You may have to install the Linux adb drivers, not sure, but those instructions are on Kayant's Compile CM10 thread (first post).
After flashing, you might have to go to factory recovery and wipe data and cache in order for the phone to boot -- maybe even have to flash a 2nd or 3rd time. I once had to flash the sbf AND wipe data\cache 5 times in a row in order to get my Bravo to boot up after accidentally flashing a Defy boot.img (usually only 1 flash is needed, I do stupid things with my phones)

Thanks, I will give this a try.
Do you install linux on the drive (like dual boot) or boot from a CD? If you boot from a CD, how do you install motorola drivers?
Just did MD5 checksum of all my downloaded files and they are all good.

Tried it with linux, getting similar errors:
Code:
>> Verifying CG32
Chechsum error (Expected 0x4805, Got 0x4a05)
!! failed
>> Verifying CG53
usb_bulk_write -110
!! failed
>> Verifying CG65
usb_bulk_write -19
!! failed

Unfortunately this error has no solution that I'm aware of, it seems like a hardware issue. Though you can try selecting the ti omap blank flash checkbox while flashing from rsd
Sent from my MB526 using xda premium

Just a silly idea: is your USB cable/PC USB port OK? Try it on another PC and with another cable. Use a cable as short as possible and make sure that the phone is the only device connected to the PC via USB including the mouse.
Sent from my MB526 using xda app-developers app

thekguy said:
Unfortunately this error has no solution that I'm aware of, it seems like a hardware issue. Though you can try selecting the ti omap blank flash checkbox while flashing from rsd
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Thanks, I think you are right.
I tried the omap option, did not help. Any other tweaks I can do to RSD light?
As far as USB, its the stock motorola cable. I disconnected everything from the computer, basically a laptop with nothing around it. I dont think its the problem, I tried over 10 sbfs and they all consistently show the same errors.

I am gonna hijack this thread...
So I believe I bricked the Defy I was supposed to be fixing.
It was acting up, the battery was sometimes showing a ? mark, and the rom it was flashed with was super buggy.
I decided to flash it with this sbf
Code:
T-Mobile_MB525_6.19.0_1FF
from here (Because I had read that it was the stock 2.1 Eclair from T-Mobile, the one the one was running originally.)
Now it won't boot.
Edit: The battery was dead. The cable was faulty so it cause a problem while flashing. Managed to get back at bootloader. Re-trying again but with:
Code:
JORDN_U3_6.36.0_SIGNED_USAJRDNTMOB1B4B5DE1028.0R_JORDANTMO_P022_HWp3_Service1FF.sbf
EDIT 2: The keyboard is not working so I can't logging into motoblur ._." Frustration... Going to keep flashing to see if its the screen of my phone or the actual program.
Edit 3: It appears it was the screen sensors being dirty. All solved.
-Defy MB525 GREEN LENS-

Any solution for this??

ChavitoArg said:
Any solution for this??
Click to expand...
Click to collapse
Try This
http://forum.xda-developers.com/showthread.php?t=1486731

I am having same problems flashing my defy. Tried different kinds of sbf using rsd lite but keep getting error verifying group code checksums from code 33 onwards...then flashing fails.
Any solutions??

[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:

FULLY BRick D855

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?