• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root bricked lg-f320k

Any help please, "fastboot: processing commands"..Can these phone be recovered?

  • YES

    Votes: 1 100.0%

  • NO

    Votes: 0 0.0%
  • Total voters
    1
D

dfre

Newbie
Hi everyone, i bricked my lg-g2 f320k by flashing a wrong laf.img
now am stuck on
[1100] fastboot mode started
when i pluck in my phone it shows
Android device> Android Bootloader Interface which seems the drivers are ok in device manager
but i cant see the device using Adb or fastboot devices. When i flash am image it takes forever, i even leave my PC the whole night and find it still writing.

Any help please! i already downloaded everyhing concerning flashtool, .kdz/.tot files for f320k, support tool in vain.

see the problem below

C:\Users\SDK\Desktop\LG_Root_LP_20150313>fastboot flash laf laf.img
target reported max download size of 1862270976 bytes
sending 'laf' (15360 KB)...
OKAY [ 0.548s]
writing 'laf'...
 
bingo! you nailed it.
I was able to shot the capacitors...though for lg-f320k, i did alot of guess work to get to the capacitors.
i used SRK Tool 2.0 fix qshusb_bulk but now am stuck on the logo...
wen i try download mode (volup+usb) it displays download mode then "error: Boot certification verify" then phone goes back to QSHUSB_BULK mode ....i have tried fixing it using all the 3 variants in vain (K/S/L)
 
dfre said:
bingo! you nailed it.
I was able to shot the capacitors...though for lg-f320k, i did alot of guess work to get to the capacitors.
i used SRK Tool 2.0 fix qshusb_bulk but now am stuck on the logo...
wen i try download mode (volup+usb) it displays download mode then "error: Boot certification verify" then phone goes back to QSHUSB_BULK mode ....i have tried fixing it using all the 3 variants in vain (K/S/L)
Click to expand...

Hmm, I wonder if the SRK tool isn't flashing enough partitions with some of the newer firmwares in play. So you may want to try flashing them yourself in either Linux (if you happen to have it) or a Linux Virtual Machine. So here's the basic instructions on how to do that:
http://forum.xda-developers.com/showthread.php?t=2582142

However, it is very important that you do NOT flash the partitions that they list in that thread. I'm only linking that to give you the basics on how to flash each partition. So instead of the ones they suggest there, you instead flash aboot, boot, dbi, laf, rpm, sbl1 and tz for the f320k (In retrospecr, I uploaded the entire bootstack for you, see post below). This can be from any firmware package. If that does not do it, also add stock recovery to the list on a 2nd effort.

Unless somebody has the partitions uploaded for the f320k, you may have to extract them yourself from a tot or kdz. There are instructions out there (mostly at xda) on how to do that.
 
Last edited:
On 2nd thought, extracting the partitions is tricky if you've never done that before. I found an f320k kitkat kdz...I'll extract the partitions and upload them for you. I'll share a link shortly.

edit: link shared via private message. please check your "conversations" as they're called on this site.
 
Last edited:
think am already lost...i was already seaching the tot file for f320k and replacing with d802...but for hex editing am raw...for sure
 
http://imgur.com/X5Gebpl

See this example. This was an f400k which was edited to D855 for a similar situation to your own. Note how there's now an extra period in the right most viewer pane directly after the D855 and that is represented on the main viewing area (where all the bytes are represented) as a 00, or "blank" if you will. This is necessary because you are starting with a 5 character (f320k) and editing to a 4 character (d802). You cannot mess with the total number of bytes so you must add a blank to retain the 5 character standard you began with. Make sense?

So in another way of explanation..
f320k
d802.

^^both are 5 characters due to the period (represented in the byte layout as 00)
 
I followed the instructions and below is the results
upload_2016-1-1_9-33-33-png.98880

upload_2016-1-1_9-36-37-png.98881
 
i have tried these three in vain

LGUP_8974.dll
LGD802_20130912_LGFLASHv160.dll
LGF320K_20130704_LGFLASHv160.dll
 
Another thiing i have noticed is that LG D802 is 16GB yet F320k is 32GB so i have lost some 16GB as i get 10GB as storage
 
I think am getting am getting somewhere..NO i have a solution..it worked...this is what i did
1. I got this zip back and after extracted it
2. I then flashed system.img from this zip using linux as illustrated here http://forum.xda-developers.com/show....php?t=2582142
3. Then i now used flashtool to flash stock Rom..and it worked

P/S: I thought i was going to loose my IMEI but lucky am i ...the phone is back to stock ROM

Vote of thanks

  1. f320k partitions
    With: iowabowtech, dfre
Man! i just don't know how to thank you....i wish gratitute could be counted, mine are countless...you've got my phone from nothing to samething.
 
Moved to the LG G2 root forum (best guesstimate on my part as the F320k is a variant).
My actions are more for organizational purposes, but with a permanent redirect from where the thread was.
(if better served elsewhere, please let me know:) )

Good to hear you are up and running @dfre with the AWESOME help from @iowabowtech!!!
 
You must log in or register to reply here.
Back
Top Bottom