Hello everyone.
I am having this error while trying to flash the latest factory image.
Adb and fastboot seem propoerly configured as I have adb devices and fastboot devices working.
sending 'bootloader' (3911 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time 5.011s
rebooting into bootloader...
FAILED (status read failed ( Too many links))
finished. Total time: 117.384s
Any help would be appreciated, because I am lost on this one.
SDK is fully updated and doing everything as I did to flash 5.0.1
Thanks in advance.
Can't help with ADB or Fastboot but I can suggest dirty flashing this stock, rooted rom by scrosler found here: http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22g-t3004110 . Worked great for me. Good luck!
Mine failed the first couple of times too, but on the third attempt it went through. However, it turns out that I had failed to turn on the ADB bridge on the first one, and I guess it was still coming up on the second.
Adb has nothing to do with this. Fastboot is what's used when you're in the bootloader.
Have you tried a different cable/USB port?
yosmokinman said:
Adb has nothing to do with this. Fastboot is what's used when you're in the bootloader.
Have you tried a different cable/USB port?
Click to expand...
Click to collapse
Very true, except that it uses adb to initially reboot the tablet into fastboot mode.
It would probably skip that step if you were already in fastboot mode, but if the OS is running, the flash-all script will attempt to restart the device by running adb reboot bootloader.
That said, if ADB isn't working, checking the cable and drivers is the next step.
Getting into the bootloader doesn't require adb. Use the hardware buttons.
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...
So through a series of attempts to root the latest MM software ive found myself with nothing but fastboot to boot into, but whenever i try to use a command such as boot for example i get:
C:\android>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.560s]
booting...
And it just hangs at booting forever. It does this every command. If i unplug the phone i get:
FAILED (status read failed (Too many links))
Any idea why it's doing this?
I'm on windows 7 with the drivers for my device along with google drivers installed. I've tried two different computers with the same results.
boho555 said:
So through a series of attempts to root the latest MM software ive found myself with nothing but fastboot to boot into, but whenever i try to use a command such as boot for example i get:
C:\android>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.560s]
booting...
And it just hangs at booting forever. It does this every command. If i unplug the phone i get:
FAILED (status read failed (Too many links))
Any idea why it's doing this?
I'm on windows 7 with the drivers for my device along with google drivers installed. I've tried two different computers with the same results.
Click to expand...
Click to collapse
Do you have access to download mode?if yes, flash back to kit Kat.bit If you are stuck at this Fastboot,you are left with only option of getting to Qualcomm 9008 mode.and flash from that.because this Fastboot fail has no solution.
Jahanzaibawan said:
Do you have access to download mode?if yes, flash back to kit Kat.bit If you are stuck at this Fastboot,you are left with only option of getting to Qualcomm 9008 mode.and flash from that.because this Fastboot fail has no solution.
Click to expand...
Click to collapse
Thanks, I'll try the qualcom fix.
Can anyone offer a little assistance please?
I took delivery of my 3rd replacement G4 this afternoon and I'm trying to unlock the bootloader which hasn't been an issue on any of the past 3 devices.
First up, I managed to get the device id, get the unlock.bin from LG but couldn't get the device to respond to any fastboot commands (it was just stuck at "waiting for any device"). After an hour or so of pissing about with drivers, fastboot can now see the phone using the "fastboot devices" command, but when I attempt to flash the unlock.bin file, I receive the below -
Code:
C:\sdk-tools>fastboot flash unlock unlock.bin
target didn't report max-download-size
sending 'unlock' (1 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.016s
It doesn't appear to respond to other fastboot commands now either. "fastboot oem device-id" returns -
Code:
FAILED (command write failed (Unknown error))
finished. total time: 5.005s
"fastboot reboot" looks to reboot the device and the on screen command prompt claims to have rebooted the phone successfully, but the phone doesn't reboot.
I've tried different cables, different ports to no avail. I could try another PC but it's in my sons room and he's asleep at the moment. Both PC's are running Windows 10.
Any other ideas?
It's an EE Branded device and according to the LG Info app, the serial number begins with 609 if that's important.
Please disregard, after uninstalling LGUP, the associated dll file and using an alternative version of fastboot (specifically the version included in this)., I've just managed to flash the unlock key and my G4 is unlocked.
Same here sir
I am trying to flash recovery in my Asus Zenfone max Pro m1 .this error shows ..plzz help any fix I am using windows 10PC
Chetancm said:
Same here sir
I am trying to flash recovery in my Asus Zenfone max Pro m1 .this error shows ..plzz help any fix I am using windows 10PC
Click to expand...
Click to collapse
Um... This is LG forum.
For your device check this: https://forum.xda-developers.com/asus-zenfone-max-pro-m1
so recently ive tried again to root my motorola g5s (not plus) and after unlocking the bootloader which took like 5 mins, i ran into a problem, i did get the right twrp img for my motorola yet when i try to flash it onto the recovery like ive been told to, it says img unsigned or corrupted, ive asked in the r/AndroidRoot discord and nothing worked. Not too long after i went online on forums to try and find a way to get this fixed, ive seen that appearently even if it says img unsigned or corrupted, to try "fastboot boot twrp.img" while that did get the phone to boot, it booted into normal Android OS, so next i was told to try to flash a vbmeta.img with the verifications removed onto the vbmeta partition but got this error:
(bootloader) is-logical:vbmeta: not found Sending 'vbmeta' (0 KB) OKAY [ 0.165s] Writing 'vbmeta' (bootloader) Invalid partition name vbmeta FAILED (remote: '') fastboot: error: Command failed
ive taken some screenshots of the cmd window in hopes of that helping to find whats wrong ill attach em(theyre named by me smashing my head against the keyboard because it doesnt work)
antipositive said:
so recently ive tried again to root my motorola g5s (not plus) and after unlocking the bootloader which took like 5 mins, i ran into a problem, i did get the right twrp img for my motorola yet when i try to flash it onto the recovery like ive been told to, it says img unsigned or corrupted, ive asked in the r/AndroidRoot discord and nothing worked. Not too long after i went online on forums to try and find a way to get this fixed, ive seen that appearently even if it says img unsigned or corrupted, to try "fastboot boot twrp.img" while that did get the phone to boot, it booted into normal Android OS, so next i was told to try to flash a vbmeta.img with the verifications removed onto the vbmeta partition but got this error:
(bootloader) is-logical:vbmeta: not found Sending 'vbmeta' (0 KB) OKAY [ 0.165s] Writing 'vbmeta' (bootloader) Invalid partition name vbmeta FAILED (remote: '') fastboot: error: Command failed
ive taken some screenshots of the cmd window in hopes of that helping to find whats wrong ill attach em(theyre named by me smashing my head against the keyboard because it doesnt work)
Click to expand...
Click to collapse
What does getvar all say? remove imei before posting
Code:
fastboot getvar all
sd_shadow said:
What does getvar all say? remove imei before posting
Code:
fastboot getvar all
Click to expand...
Click to collapse
Ill check that tomorrow after installing the new battery, what's imei?
So in cmd i just type "fastboot getvar all" in the platform-tools folder?
antipositive said:
Ill check that tomorrow after installing the new battery, what's imei?
So in cmd i just type "fastboot getvar all" in the platform-tools folder?
Click to expand...
Click to collapse
sd_shadow said:
What does getvar all say? remove imei before posting
Code:
fastboot getvar all
Click to expand...
Click to collapse
...bad news, the battery was replaced... Part of the backlight is ****ed but so little it doesnt matter, yet the entire bottum of the screen with the three buttons, its unresponsive altho it worked shortly after the replacement was finished, now it just stopped working. Idk if its even worth at that point to even replace the screen, really depends on the cost ngl but as of now i put the rooting on ice.
Youll hear from me again soon maybe.