Hey guys !
So since i messed up with the recovery mode, i'm stucked in the fastboot with no Download mode (recovery doesnt work neither).
So after searching 3 days in the internet i found the acces to fast through adb by puting a new laf.img in order to restore the download mode and flash a stock firmware !
My problem is that when i try to enter the command on the cmd, i get severals errors, take a look :
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
error: device not found
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase laf
erasing 'laf'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.034s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash laf laf.img
target reported max download size of 2147483648 bytes
sending 'laf' (18432 KB)...
OKAY [ 0.581s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.615s
Also command : "fastboot boot laf.img" result to "Failed(remote: dtb not found) instead of flash write failure..
Of course i have my G3 855 32GB in download mode (but it goes into fastmode), so when i try a command, lines are added in the screen etc..
Does that mean that my laf.img don't work? I assumed that so i try several, but does it have to be the exact same one as the one who was in my phone before( v20a if i record correctly ) or could it be from any 855 32GB version ?
I also thought it could be a recognition problem as when i type "adb devices" or "adb shell" nothing is found..
If someone has any clue or a link to some guide i'll be more than joyful, thanks in advance !
Try adb fastboot when writing command hope it helps
Anik49 said:
Try adb fastboot when writing command hope it helps
Click to expand...
Click to collapse
Hey thank you so much for answering !
What do you mean by that, i already download the adb/fastboot driver and launch a cmd in the directory they are at, writing "adb fastboot" has no result neither, can you be more specific please ?
cm13 recently messed up my phone in exactly the same way, no recovery and download mode would jump straght to fastboot. I followed this guide to the letter and am now back running again: http://open-freax.fr/guide-unbrick-your-lg-g3/
BigsyBiggins said:
cm13 recently messed up my phone in exactly the same way, no recovery and download mode would jump straght to fastboot. I followed this guide to the letter and am now back running again:
Click to expand...
Click to collapse
Well i hope my problem can be solved in a safer way, i dont like much to go on the hardware part, so I'll use it as my last hope, but thanks
Altought i think my device is recognized by fastboot in someway because it responds when i type commands in fastboot, and also when i reboot it.
But i'm getting this error :
Code:
error : command never completed
error : auto CMD12 error
error : command completed with errors
error : command timeout error
failed to send stop command
failed writing block @ 1
in the screen of my phone. Does that stand for Cyanogen mode which i was trying to put on my phone ?
I mean when you enter command in cmd use adb before any command also use cmd which one available on android sdk folder....also you can use this method if adb not workinhg properly http://forum.xda-developers.com/lg-g...-9008-t3072091
BigsyBiggins said:
cm13 recently messed up my phone in exactly the same way, no recovery and download mode would jump straght to fastboot. I followed this guide to the letter and am now back running again: http://open-freax.fr/guide-unbrick-your-lg-g3/
Click to expand...
Click to collapse
Like @BigsyBiggins said, this is the guide which could fix your phone. HW Part is not too hard!
Anik49 said:
I mean when you enter command in cmd use adb before any command also use cmd which one available on android sdk folder....also you can use this method if adb not workinhg properly
Click to expand...
Click to collapse
Oh ok ! Also your link is not working :s
I understand that the method can work but I think that the method i'm trying to use is really close to succeed, over my search on the internet, i saw lots of people who manage to succeed with it.
But i guess i must do something wrong. I downloaded the kdz file according to my IMEI.
Then I extracted the .dz file with LG Firmware Extract. Then I extracted the file named laf_393216.bin from the dz file. Changed his name into laf.img , put it into the fastboot directory.
Then i typed
Code:
fastboot format cache
fastboot erase laf
fastboot flash laf laf.img
in a cmd from the directory.
It all seemed to work, but then when i remove the battery and restart into download mode, it goes into fastboot after the download mode charging animation..
Also when i try to boot with fastboot boot laf.img i get the error (remote: dtb not found) on the cmd.
And ERROR: Unable to find suitable device tree for device(194/0x0001001/112/0) ERROR: getting device tree adress failed DTB offset is incorrect, kernel image does not have appended DTB)
Am I doing something wrong, should I changed more file than just laf ?
SisGG said:
Oh ok ! Also your link is not working :s
I understand that the method can work but I think that the method i'm trying to use is really close to succeed, over my search on the internet, i saw lots of people who manage to succeed with it.
But i guess i must do something wrong. I downloaded the kdz file according to my IMEI.
Then I extracted the .dz file with LG Firmware Extract. Then I extracted the file named laf_393216.bin from the dz file. Changed his name into laf.img , put it into the fastboot directory.
Then i typed
Code:
fastboot format cache
fastboot erase laf
fastboot flash laf laf.img
in a cmd from the directory.
It all seemed to work, but then when i remove the battery and restart into download mode, it goes into fastboot after the download mode charging animation..
Also when i try to boot with fastboot boot laf.img i get the error (remote: dtb not found) on the cmd.
And ERROR: Unable to find suitable device tree for device(194/0x0001001/112/0) ERROR: getting device tree adress failed DTB offset is incorrect, kernel image does not have appended DTB)
Am I doing something wrong, should I changed more file than just laf ?
Click to expand...
Click to collapse
I don´t know what exactly is the problem, maybe something with your win-driver, some crashed or drifted partitions or some broken files...
I just can repeat my advice: I was in the same situation with my phone after a failed cm13 update and i was trying and reading about 2 days how to solve it - after the above mentioned method, your phone would get out of this "coma".
Maybe somebody else here in this forum could help you with your mentioned method, sorry.
Ernesto0023 said:
I don´t know what exactly is the problem, maybe something with your win-driver, some crashed or drifted partitions or some broken files...
I just can repeat my advice: I was in the same situation with my phone after a failed cm13 update and i was trying and reading about 2 days how to solve it - after the above mentioned method, your phone would get out of this "coma".
Maybe somebody else here in this forum could help you with your mentioned method, sorry.
Click to expand...
Click to collapse
Well I think i'm still under warranty, so i dont wanna touch to much on the hardware.
So do you think, if i send it back without touching anything, saying i put it on charge one night and the next morning it was like this, the warranty could work?
If they found it's rooted or they understand you did something with your software your warrenty is void ?
SisGG said:
Well i hope my problem can be solved in a safer way, i dont like much to go on the hardware part, so I'll use it as my last hope, but thanks
Altought i think my device is recognized by fastboot in someway because it responds when i type commands in fastboot, and also when i reboot it.
But i'm getting this error :
Code:
error : command never completed
error : auto CMD12 error
error : command completed with errors
error : command timeout error
failed to send stop command
failed writing block @ 1
in the screen of my phone. Does that stand for Cyanogen mode which i was trying to put on my phone ?
Click to expand...
Click to collapse
Remove the battery, put it, press the volume + and connect to PC USB, if like entering download, what happens to us not to go, will leave the ****ing LoGo, Well, hold down the volume + and not let go, I think it is less for 2 minutes more. After a while, the computer tells us that something was connected, the phone will tell you who is in fastboot as I said before, if not let me fastboot flash boot files and the LAF, recovery ect, nothing happens, there is still a magic command.
fastboot boot laf.img
Keep it in the ****ing heart
miguexneox said:
Remove the battery, put it, press the volume + and connect to PC USB, if like entering download, what happens to us not to go, will leave the ****ing LoGo, Well, hold down the volume + and not let go, I think it is less for 2 minutes more. After a while, the computer tells us that something was connected, the phone will tell you who is in fastboot as I said before, if not let me fastboot flash boot files and the LAF, recovery ect, nothing happens, there is still a magic command.
fastboot boot laf.img
Keep it in the ****ing heart
Click to expand...
Click to collapse
I dont quite understand what u meant there :s
I already have acces on the fastboot, actually now, my phone goes instantly on fastboot whatever i do.. Though i cannot boot a laf.img downloaded and flashed .. :'(
SisGG said:
I dont quite understand what u meant there :s
I already have acces on the fastboot, actually now, my phone goes instantly on fastboot whatever i do.. Though i cannot boot a laf.img downloaded and flashed .. :'(
Click to expand...
Click to collapse
were u able to resolve this issue. I am in your shoes at the moment.
I have tried the qualcomm. The drivers doesnt seem to work for my phone .
I can't flash or the laf.img . the fastboot commands doesnt seem to work.
and I'm stuck in fastboot .
What can be done
datrmon said:
were u able to resolve this issue. I am in your shoes at the moment.
I have tried the qualcomm. The drivers doesnt seem to work for my phone .
I can't flash or the laf.img . the fastboot commands doesnt seem to work.
and I'm stuck in fastboot .
What can be done
Click to expand...
Click to collapse
You have several options:
- find your phone firmware, extract recovery.img and flash it back through fastboot(do exactly the same for the LAF partition to restore download mode)
- flash a custom recovery for your phone model, if it doesn't work try an older version of TWRP, also it can be that your phone is not d855 but d850 model, so try to flash a d850 custom recovery and see if it works(that was exactly my problem and why i got stuck in fastboot mode, because my phone is d850 model and in settings it says d855, so I flashed wrong TWRP)
Ghikya said:
You have several options:
- find your phone firmware, extract recovery.img and flash it back through fastboot(do exactly the same for the LAF partition to restore download mode)
- flash a custom recovery for your phone model, if it doesn't work try an older version of TWRP, also it can be that your phone is not d855 but d850 model, so try to flash a d850 custom recovery and see if it works(that was exactly my problem and why i got stuck in fastboot mode, because my phone is d850 model and in settings it says d855, so I flashed wrong TWRP)
Click to expand...
Click to collapse
Thanks for the response .
I am unable to flash files at all.
This is the error
D:\mfastboot-v2>fastboot flash laf laf.img
target max-download-size: 2048MB
sending 'laf' (18432 KB)...
OKAY [ 0.646s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.726s
D:\mfastboot-v2>
datrmon said:
Thanks for the response .
I am unable to flash files at all.
This is the error
D:\mfastboot-v2>fastboot flash laf laf.img
target max-download-size: 2048MB
sending 'laf' (18432 KB)...
OKAY [ 0.646s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.726s
D:\mfastboot-v2>
Click to expand...
Click to collapse
It seems that your phone's bootloader is locked, you can try to execute this command: "fastboot oem unlock", and then check state with "fastboot oem device-info". But some people says that it does nothing, so you can try and check for yourself.
You can also try to boot directly an image from fastboot for eaxmple:
Code:
fastboot boot laf.img
or
Code:
fastboot boot twrp.img
So if you could successfully boot a laf image you would be able to access download mode, and if you could boot a custom recowery then you could access ADB and to try to flash other partitions, or even flash a custom rom...
I have D855 32GB, installed Lollipop D85520A on it. (official polland rom as i learned) it has rooted but no recovery. so i tried to install TWRP but my phone is stucked in Fastboot mode. Can't enter download mode , when i try fastboot screen appearing again. i can use fastboot commands and tried to remove and reflash aboot, boot ang laf.img files. there is no error all is ok but no change... When i try to list my fastboot devices it says
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
? fastboot
but in device manager page i can see recognised as Android Bootloader Interface.
Also i cannot find 32GB 20A official kdz or img files so i tried 20H istead .
So how can i fix this problem???
draqkin said:
I have D855 32GB, installed Lollipop D85520A on it. (official polland rom as i learned) it has rooted but no recovery. so i tried to install TWRP but my phone is stucked in Fastboot mode. Can't enter download mode , when i try fastboot screen appearing again. i can use fastboot commands and tried to remove and reflash aboot, boot ang laf.img files. there is no error all is ok but no change... When i try to list my fastboot devices it says
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
? fastboot
but in device manager page i can see recognised as Android Bootloader Interface.
Also i cannot find 32GB 20A official kdz or img files so i tried 20H istead .
So how can i fix this problem???
Click to expand...
Click to collapse
Now, can you use fastboot command ? Like fastboot flash recovery "withyourrecovery.img"
Now, can you use fastboot command ? Like fastboot flash recovery "withyourrecovery.img"
Click to expand...
Click to collapse
Yes i can use fastboot commands also tried to write recover, laf, aboot img files. I dont have original img files of 20A but tried with 20H recovery and custom recovery img (TWRP) but no change. There was no problem or error while writing images with fastboot commands...
i have the same problem
it also says
? fastboot
still couldn't find a solution
please let me know if u find a solution
ghadeer.m96 said:
i have the same problem
it also says
? fastboot
still couldn't find a solution
please let me know if u find a solution
Click to expand...
Click to collapse
Can you erase recovery ? or not ? ( with command : fastboot erase recovery )
I can't erase recovery because i have this error ( remote failed to erase partition )
th0was said:
Can you erase recovery ? or not ? ( with command : fastboot erase recovery )
I can't erase recovery because i have this error ( remote failed to erase partition )
Click to expand...
Click to collapse
i can't do any command successfully
like when i do a flash command
it finishes sending successfully but then it gets stuck at writing ...
and it never finishes writing
---------- Post added at 07:11 PM ---------- Previous post was at 06:51 PM ----------
draqkin said:
I have D855 32GB, installed Lollipop D85520A on it. (official polland rom as i learned) it has rooted but no recovery. so i tried to install TWRP but my phone is stucked in Fastboot mode. Can't enter download mode , when i try fastboot screen appearing again. i can use fastboot commands and tried to remove and reflash aboot, boot ang laf.img files. there is no error all is ok but no change... When i try to list my fastboot devices it says
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
? fastboot
but in device manager page i can see recognised as Android Bootloader Interface.
Also i cannot find 32GB 20A official kdz or img files so i tried 20H istead .
So how can i fix this problem???
Click to expand...
Click to collapse
btw do u have an unlocked bootloader ?
mine is locked
i think this is why we're facing this problem .. cuz of locked bootloader
Can you erase recovery ? or not ? ( with command : fastboot erase recovery )
Click to expand...
Click to collapse
Yes i can erase and rewrite recovery and others with no error.
btw do u have an unlocked bootloader ?
mine is locked
i think this is why we're facing this problem .. cuz of locked bootloader
Click to expand...
Click to collapse
I don't know about my bootloader because i have bought my phone from someone else. It was rooted, used 3 days and tried to install twrp than *kaboom*. Stuck fastboot....
Hi,
I tried to flash european version of firmware to my LG G7+ by LGUP. It got stuck at 91%. After that i am not able to go in to download mode, becouse phone automaticly goes to fastboot mode.
I tried to flash laf.img extracted from firmware but fastboot is showing error:
Code:
C:\platform-tools>fastboot boot laf.img
Sending 'boot.img' (36736 KB) FAILED (Write to device failed (Too many links))
fastboot: error: Command failed
And then I can see that phone is unplugging from computer and fastboot cant see it. (fastboot menu on phone is vanishing in that moment too, there left only charging icon)
Any solutions? If you have any contact to someone who could help, please advice me.
pozdrowiony said:
Hi,
I tried to flash european version of firmware to my LG G7+ by LGUP. It got stuck at 91%. After that i am not able to go in to download mode, becouse phone automaticly goes to fastboot mode.
I tried to flash laf.img extracted from firmware but fastboot is showing error:
And then I can see that phone is unplugging from computer and fastboot cant see it. (fastboot menu on phone is vanishing in that moment too, there left only charging icon)
Any solutions? If you have any contact to someone who could help, please advice me.
Click to expand...
Click to collapse
Try using qfil to flash the required partitions.