Bricked LG L70 (D320) reboots continously if I connect it to Linux

Search This thread

VaultTec96

New member
Sep 2, 2017
3
0
Hello, I was trying to flash stock ROM to my phone but I needed to get into Download Mode but it instead was booting into fastboot mode, so I had to erase and rewrite some partitions manually using fastboot. I ask it here because there's no LG L70 forum and may be it's a general issue which can occur in other super bricked phones.

I remember erasing laf, recovery and aboot partitions but while I was rewriting them, phone rebootet itself unexpectedly (probably a battery error) and now it doesn't boot at all. It doesn't show LG logo when booting (it only vibrates) and if I connect it to Windows or Linux PC, it keeps rebooting continously without anything being shown.

I'm following this guide, trying to manually unbrick it with dd'ing aboot.img to aboot partition but I cant because but it keeps disconnecting while these lines keeps on repeating in dmesg output.

Code:
[  +1.067652] usb 1-2: new high-speed USB device number 22 using xhci_hcd
[  +0.130690] usb 1-2: config 1 has an invalid interface number: 20 but max is 1
[  +0.000005] usb 1-2: config 1 has no interface number 1
[  +0.001269] usb-storage 1-2:1.20: USB Mass Storage device detected
[  +0.000721] scsi host4: usb-storage 1-2:1.20
[  +1.519495] usb 1-2: USB disconnect, device number 22

Also after disconnecting and reconnecting it, some purple screen with DBI Error pops up on screen and screen closes (it starts showing this screen with one second interval) and this lines starts to keep repeating in dmesg output:

Code:
[  +0.405246] usb 1-2: new high-speed USB device number 29 using xhci_hcd
[  +0.137032] usb 1-2: config 1 has an invalid interface number: 20 but max is 1
[  +0.000002] usb 1-2: config 1 has no interface number 1
[  +0.001309] usb-storage 1-2:1.20: USB Mass Storage device detected
[  +0.000107] scsi host4: usb-storage 1-2:1.20
[  +1.022123] scsi 4:0:0:0: Direct-Access     Qualcomm MMC Storage      1.00 PQ: 0 ANSI: 2
[  +0.000762] sd 4:0:0:0: Attached scsi generic sg2 type 0
[  +0.000208] sd 4:0:0:0: [sdb] 7634944 512-byte logical blocks: (3.91 GB/3.64 GiB)
[  +0.000187] sd 4:0:0:0: [sdb] Write Protect is off
[  +0.000005] sd 4:0:0:0: [sdb] Mode Sense: 0f 0e 00 00
[  +0.000176] sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[  +0.007774]  sdb: sdb1 sdb2 sdb3 sdb4 sdb5 sdb6 sdb7 sdb8 sdb9 sdb10 sdb11 sdb12 sdb13 sdb14 sdb15 sdb16 sdb17 sdb18 sdb19 sdb20 sdb21 sdb22 sdb23 sdb24 sdb25 sdb26 sdb27 sdb28 sdb29 sdb30 sdb31 sdb32 sdb33 sdb34 sdb35
[  +0.002044] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[  +0.761824] usb 1-2: USB disconnect, device number 29
[  +0.013062] sd 4:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00
[  +0.000005] sd 4:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 00 00 00 80 00 00 90 00
[  +0.000002] blk_update_request: I/O error, dev sdb, sector 128
[  +0.009148] sd 4:0:0:0: [sdb] Synchronizing SCSI cache
[  +0.000053] sd 4:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00

It recognizes all the partitions in the device for a split second and it goes off and reboots again. I can get partition table and lsusb outputs Bus 001 Device 084: ID 1004:61a1 LG Electronics, Inc. also with gdisk if I time it correctly, it's like this:

Code:
Number  Start (sector)    End (sector)  Size       Code  Name
   1            8192          139263   64.0 MiB    0700  modem
   2          139264          141311   1024.0 KiB  FFFF  sbl1
   3          141312          142335   512.0 KiB   FFFF  rpm
   4          142336          143359   512.0 KiB   FFFF  tz
   5          143360          144383   512.0 KiB   FFFF  sdi
   6          144384          148479   2.0 MiB     FFFF  aboot
   7          148480          149503   512.0 KiB   FFFF  rpmb
   8          149504          150527   512.0 KiB   FFFF  tzb
   9          150528          154623   2.0 MiB     FFFF  abootb
  10          154624          158719   2.0 MiB     0700  pad
  11          158720          164863   3.0 MiB     FFFF  modemst1
  12          164864          171007   3.0 MiB     FFFF  modemst2
  13          171008          203775   16.0 MiB    FFFF  misc
  14          204800          270335   32.0 MiB    0700  persist
  15          270336          315391   22.0 MiB    FFFF  laf
  16          319488          364543   22.0 MiB    FFFF  boot
  17          364544          409599   22.0 MiB    FFFF  recovery
  18          409600          415743   3.0 MiB     FFFF  fsg
  19          417792          418815   512.0 KiB   FFFF  fsc
  20          418816          419839   512.0 KiB   FFFF  ssd
  21          425984          427007   512.0 KiB   FFFF  DDR
  22          434176          435199   512.0 KiB   FFFF  encrypt
  23          435200          436223   512.0 KiB   FFFF  rct
  24          442368          458751   8.0 MiB     0700  drm
  25          458752          475135   8.0 MiB     0700  sns
  26          475136          516095   20.0 MiB    FFFF  factory
  27          516096          581631   32.0 MiB    FFFF  fota
  28          581632          583679   1024.0 KiB  FFFF  sbl1b
  29          583680          649215   32.0 MiB    0700  mpt
  30          655360          757759   50.0 MiB    8300  cust
  31          761856          762879   512.0 KiB   FFFF  eksst
  32          770048         3841023   1.5 GiB     0700  system
  33         3841024         4353023   250.0 MiB   0700  cache
  34         4353024         7564287   1.5 GiB     0700  userdata
  35         7569408         7634910   32.0 MiB    0700  grow

So I think there's still hope, by the way if I plug in and out a few times, Linux starts recognizing it as a Qualcomm modem device and phone stops rebooting. If I reboot system to Windows, it shows as a Qualcomm 9008 device and there are 2 folders in it called image and verinfo. But sometimes Windows recognizes it LGE AndroidNet Device.

I don't know what to do after this point. I tried forcing dd after it sees /dev/sda6 file but it can't write all the image file (only 700~kb of it)(file is 1mb).

Is there any going back from this?
Kind regards.
 
Last edited:

Droidriven

Senior Member
Jan 27, 2014
16,239
13
5,625
NC
Verizon Samsung Galaxy S III
HTC Thunderbolt
Hello, I was trying to flash stock ROM to my phone but I needed to get into Download Mode but it instead was booting into fastboot mode, so I had to erase and rewrite some partitions manually using fastboot. I ask it here because there's no LG L70 forum and may be it's a general issue which can occur in other super bricked phones.

I remember erasing laf, recovery and aboot partitions but while I was rewriting them, phone rebootet itself unexpectedly (probably a battery error) and now it doesn't boot at all. It doesn't show LG logo when booting (it only vibrates) and if I connect it to Windows or Linux PC, it keeps rebooting continously without anything being shown.

I'm following this guide, trying to manually unbrick it with dd'ing aboot.img to aboot partition but I cant because but it keeps disconnecting while these lines keeps on repeating in dmesg output.

Code:
[  +1.067652] usb 1-2: new high-speed USB device number 22 using xhci_hcd
[  +0.130690] usb 1-2: config 1 has an invalid interface number: 20 but max is 1
[  +0.000005] usb 1-2: config 1 has no interface number 1
[  +0.001269] usb-storage 1-2:1.20: USB Mass Storage device detected
[  +0.000721] scsi host4: usb-storage 1-2:1.20
[  +1.519495] usb 1-2: USB disconnect, device number 22

Also after disconnecting and reconnecting it, some purple screen with DBI Error pops up on screen and screen closes (it starts showing this screen with one second interval) and this lines starts to keep repeating in dmesg output:

Code:
[  +0.405246] usb 1-2: new high-speed USB device number 29 using xhci_hcd
[  +0.137032] usb 1-2: config 1 has an invalid interface number: 20 but max is 1
[  +0.000002] usb 1-2: config 1 has no interface number 1
[  +0.001309] usb-storage 1-2:1.20: USB Mass Storage device detected
[  +0.000107] scsi host4: usb-storage 1-2:1.20
[  +1.022123] scsi 4:0:0:0: Direct-Access     Qualcomm MMC Storage      1.00 PQ: 0 ANSI: 2
[  +0.000762] sd 4:0:0:0: Attached scsi generic sg2 type 0
[  +0.000208] sd 4:0:0:0: [sdb] 7634944 512-byte logical blocks: (3.91 GB/3.64 GiB)
[  +0.000187] sd 4:0:0:0: [sdb] Write Protect is off
[  +0.000005] sd 4:0:0:0: [sdb] Mode Sense: 0f 0e 00 00
[  +0.000176] sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[  +0.007774]  sdb: sdb1 sdb2 sdb3 sdb4 sdb5 sdb6 sdb7 sdb8 sdb9 sdb10 sdb11 sdb12 sdb13 sdb14 sdb15 sdb16 sdb17 sdb18 sdb19 sdb20 sdb21 sdb22 sdb23 sdb24 sdb25 sdb26 sdb27 sdb28 sdb29 sdb30 sdb31 sdb32 sdb33 sdb34 sdb35
[  +0.002044] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[  +0.761824] usb 1-2: USB disconnect, device number 29
[  +0.013062] sd 4:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00
[  +0.000005] sd 4:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 00 00 00 80 00 00 90 00
[  +0.000002] blk_update_request: I/O error, dev sdb, sector 128
[  +0.009148] sd 4:0:0:0: [sdb] Synchronizing SCSI cache
[  +0.000053] sd 4:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00

It recognizes all the partitions in the device for a split second and it goes off and reboots again. I can get partition table and lsusb outputs Bus 001 Device 084: ID 1004:61a1 LG Electronics, Inc. also with gdisk if I time it correctly, it's like this:

Code:
Number  Start (sector)    End (sector)  Size       Code  Name
   1            8192          139263   64.0 MiB    0700  modem
   2          139264          141311   1024.0 KiB  FFFF  sbl1
   3          141312          142335   512.0 KiB   FFFF  rpm
   4          142336          143359   512.0 KiB   FFFF  tz
   5          143360          144383   512.0 KiB   FFFF  sdi
   6          144384          148479   2.0 MiB     FFFF  aboot
   7          148480          149503   512.0 KiB   FFFF  rpmb
   8          149504          150527   512.0 KiB   FFFF  tzb
   9          150528          154623   2.0 MiB     FFFF  abootb
  10          154624          158719   2.0 MiB     0700  pad
  11          158720          164863   3.0 MiB     FFFF  modemst1
  12          164864          171007   3.0 MiB     FFFF  modemst2
  13          171008          203775   16.0 MiB    FFFF  misc
  14          204800          270335   32.0 MiB    0700  persist
  15          270336          315391   22.0 MiB    FFFF  laf
  16          319488          364543   22.0 MiB    FFFF  boot
  17          364544          409599   22.0 MiB    FFFF  recovery
  18          409600          415743   3.0 MiB     FFFF  fsg
  19          417792          418815   512.0 KiB   FFFF  fsc
  20          418816          419839   512.0 KiB   FFFF  ssd
  21          425984          427007   512.0 KiB   FFFF  DDR
  22          434176          435199   512.0 KiB   FFFF  encrypt
  23          435200          436223   512.0 KiB   FFFF  rct
  24          442368          458751   8.0 MiB     0700  drm
  25          458752          475135   8.0 MiB     0700  sns
  26          475136          516095   20.0 MiB    FFFF  factory
  27          516096          581631   32.0 MiB    FFFF  fota
  28          581632          583679   1024.0 KiB  FFFF  sbl1b
  29          583680          649215   32.0 MiB    0700  mpt
  30          655360          757759   50.0 MiB    8300  cust
  31          761856          762879   512.0 KiB   FFFF  eksst
  32          770048         3841023   1.5 GiB     0700  system
  33         3841024         4353023   250.0 MiB   0700  cache
  34         4353024         7564287   1.5 GiB     0700  userdata
  35         7569408         7634910   32.0 MiB    0700  grow

So I think there's still hope, by the way if I plug in and out a few times, Linux starts recognizing it as a Qualcomm modem device and phone stops rebooting. If I reboot system to Windows, it shows as a Qualcomm 9008 device and there are 2 folders in it called image and verinfo. But sometimes Windows recognizes it LGE AndroidNet Device.

I don't know what to do after this point. I tried forcing dd after it sees /dev/sda6 file but it can't write all the image file (only 700~kb of it)(file is 1mb).

Is there any going back from this?
Kind regards.
Try this

https://xdaforums.com/showthread.php?t=2426426

It's a general guide, ignore the device specific stuff, do not flash any of the files there, start at the section labelled "using adb by samantha".

DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
 

VaultTec96

New member
Sep 2, 2017
3
0

Droidriven

Senior Member
Jan 27, 2014
16,239
13
5,625
NC
Verizon Samsung Galaxy S III
HTC Thunderbolt
Hi, tried it. adb wait-for-device doesn't work because adb never sees the device. But lsusb sees it LG Electronics and lsblk sees all the partitions in it for a split second until it disappears.
Did you happen to read the part about using the ondemand.exe script for Windows or the ondemand.sh for Linux.

The purpose of the script is to freeze the device when adb connection becomes available, it should stop the loop and connect-disconnect so that you can issue other adb commands.

Or, if you can get the Qualcomm qhsusb 9008 again, try this

https://xdaforums.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830



DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
 
Last edited:

-Hope-

Senior Member
Oct 29, 2016
448
111
Did you happen to read the part about using the ondemand.exe script for Windows or the ondemand.sh for Linux.

The purpose of the script is to freeze the device when adb connection becomes available, it should stop the loop and connect-disconnect so that you can issue other adb commands.

Or, if you can get the Qualcomm qhsusb 9008 again, try this

https://xdaforums.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830


DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

In addtion to what Droiddriven said i would like to say if you couldn't find qfil files you can extract them from the tot file if you found one but the bad news is that i couldn't find a trusted website that offers them
 
Last edited:

VaultTec96

New member
Sep 2, 2017
3
0
In addtion to what Droiddriven said i would like to say if you couldn't find qfil files you can extract them from the tot file if you found one but the bad news is that i couldn't find a trusted website that offers them

I have the .kdz file, not .tot and I extracted its content's. I tried the QFIL method but didn't understand it, seems like I need patch0.xml and some other prog_emmc_firehose_8x10.mbn (which I could find online) but I can't find the other file.

Did you happen to read the part about using the ondemand.exe script for Windows or the ondemand.sh for Linux.

The purpose of the script is to freeze the device when adb connection becomes available, it should stop the loop and connect-disconnect so that you can issue other adb commands.

Or, if you can get the Qualcomm qhsusb 9008 again, try this

https://xdaforums.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830

As for BoardDiag method, Windows recognizes the device as Qualcomm HS-USB QDLoader 9008 (COM4) in device manager but BoardDiag gives the error Device was not found in dload trying flash programmer. I've even created partition.txt manually, following this guide (look it up on wayback machine, it's deleted) but, still the same error.

As for the ondemand.sh method, yes I tried running it, it never executes the line after adb wait-for-device (I checked with echo) so device always keeps rebooting itself without adb noticing anything.
 
Last edited: