Related
I feel silly and ashamed asking for help, but i f***ed up big time.
For some stupid reason I wiped my kindle and was left with only twrp. So no worries I thought Ill just push a rom back onto the sdcard via adb and all everything is fine...
So I though... win xp wont recognise the kindle any more. Well it does as amazon kindle 2 but not as adb device.
So I tried all this again:
http://forum.xda-developers.com/showthread.php?t=2283230
http://forum.xda-developers.com/showpost.php?p=37733595&postcount=361
and a little bit of this:
http://forum.xda-developers.com/showthread.php?t=2069117&highlight=root
and several other crazy things I read on XDA. Nothing realy helped.
So I thought. Hey! Why not try fastboot.... So I did. What a noobish thing to do...
Looking around I found this:
http://forum.xda-developers.com/showthread.php?t=2117224
screw adb in twrp, we'll use twrp's terminal emulator to go to fastboot with the command idme bootmode 4
In twrp, go to advanced. then go to terminal command. then press the select folder button.
type idme bootmode 4
reboot and you're in fastboot.
That is what I did.
Funny enough. Now ADB Drivers work perfectly and recognise Kindle as ADB device in the device manager.
Sadly though, when I try to connect through ADB or Fastboot in CMD no device is being detected.
I know you guys have better things to do than help noobsters to clean their mess up they have caused. However I would be dead gratefull if one of you mighty tech gurus could help me out on this one.
What can I do to get this fixed?
Thank you ever so much in advance!
androidschima said:
I feel silly and ashamed asking for help, but i f***ed up big time.
For some stupid reason I wiped my kindle and was left with only twrp. So no worries I thought Ill just push a rom back onto the sdcard via adb and all everything is fine...
So I though... win xp wont recognise the kindle any more. Well it does as amazon kindle 2 but not as adb device.
So I tried all this again:
http://forum.xda-developers.com/showthread.php?t=2283230
http://forum.xda-developers.com/showpost.php?p=37733595&postcount=361
and a little bit of this:
http://forum.xda-developers.com/showthread.php?t=2069117&highlight=root
and several other crazy things I read on XDA. Nothing realy helped.
So I thought. Hey! Why not try fastboot.... So I did. What a noobish thing to do...
Looking around I found this:
http://forum.xda-developers.com/showthread.php?t=2117224
screw adb in twrp, we'll use twrp's terminal emulator to go to fastboot with the command idme bootmode 4
In twrp, go to advanced. then go to terminal command. then press the select folder button.
type idme bootmode 4
reboot and you're in fastboot.
That is what I did.
Funny enough. Now ADB Drivers work perfectly and recognise Kindle as ADB device in the device manager.
Sadly though, when I try to connect through ADB or Fastboot in CMD no device is being detected.
I know you guys have better things to do than help noobsters to clean their mess up they have caused. However I would be dead gratefull if one of you mighty tech gurus could help me out on this one.
What can I do to get this fixed?
Thank you ever so much in advance!
Click to expand...
Click to collapse
I'm in a similar situation. TWRP will not mount anything, If i try to wipe cashe, ect it says failed. If i try adb push it does not work. At this point I would be fine with just going back to stock. Hopefully someone can find a solution to our problem.
androidschima said:
I feel silly and ashamed asking for help, but i f***ed up big time.
For some stupid reason I wiped my kindle and was left with only twrp. So no worries I thought Ill just push a rom back onto the sdcard via adb and all everything is fine...
So I though... win xp wont recognise the kindle any more. Well it does as amazon kindle 2 but not as adb device.
So I tried all this again:
http://forum.xda-developers.com/showthread.php?t=2283230
http://forum.xda-developers.com/showpost.php?p=37733595&postcount=361
and a little bit of this:
http://forum.xda-developers.com/showthread.php?t=2069117&highlight=root
and several other crazy things I read on XDA. Nothing realy helped.
So I thought. Hey! Why not try fastboot.... So I did. What a noobish thing to do...
Looking around I found this:
http://forum.xda-developers.com/showthread.php?t=2117224
screw adb in twrp, we'll use twrp's terminal emulator to go to fastboot with the command idme bootmode 4
In twrp, go to advanced. then go to terminal command. then press the select folder button.
type idme bootmode 4
reboot and you're in fastboot.
That is what I did.
Funny enough. Now ADB Drivers work perfectly and recognise Kindle as ADB device in the device manager.
Sadly though, when I try to connect through ADB or Fastboot in CMD no device is being detected.
I know you guys have better things to do than help noobsters to clean their mess up they have caused. However I would be dead gratefull if one of you mighty tech gurus could help me out on this one.
What can I do to get this fixed?
Thank you ever so much in advance!
Click to expand...
Click to collapse
What is the exact command you are running? Also uninstall any kindle drivers that are installed and let it reinstall the device, I always have to do that when I switch from adb recovery to fastboot, sometimes it will be part of a component device you have to uninstall, but in that case you have to check the components vid so you don't uninstall something else by accident. All fastboot commands should be prefixed with ”-I 0x1949” so for ex: fastboot -i 0x1949 getvar product
Hope this helps.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
What is the exact command you are running? Also uninstall any kindle drivers that are installed and let it reinstall the device, I always have to do that when I switch from adb recovery to fastboot, sometimes it will be part of a component device you have to uninstall, but in that case you have to check the components vid so you don't uninstall something else by accident. All fastboot commands should be prefixed with ”-I 0x1949” so for ex: fastboot -i 0x1949 getvar product
Hope this helps.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
hi there. thank you. when i type the command you said i get the following:
product otter2-prod-04
finished. total time: 0.016s
does this mean, that fastboot is actually working and i get a connection to the device?
androidschima said:
hi there. thank you. when i type the command you said i get the following:
product otter2-prod-04
finished. total time: 0.016s
does this mean, that fastboot is actually working and i get a connection to the device?
Click to expand...
Click to collapse
ok i get in and out of fastboot fine. i looked through the commands here for fastboot.
http://forum.xda-developers.com/showpost.php?p=23747804
so far so good.
However whenever i flash something onto the kindle in cannot find it. also when i am in twrp it tell me unable to mount data.
fastboot wont let me format the userdata. did i break the filesystem? this must have been done by twrp when accidently formatting it... right?
androidschima said:
ok i get in and out of fastboot fine. i looked through the commands here for fastboot.
http://forum.xda-developers.com/showpost.php?p=23747804
so far so good.
However whenever i flash something onto the kindle in cannot find it. also when i am in twrp it tell me unable to mount data.
fastboot wont let me format the userdata. did i break the filesystem? this must have been done by twrp when accidently formatting it... right?
Click to expand...
Click to collapse
im stuck....
i flashed new recovery through fastboot because this was supposed to get the twrp 2.3.3.0 bug out of the system formatting the data partition in a way i could flash a rom onto it. so new twrp 2.7 flashed through fastboot. according to the cmd it worked all fine...
now i come into white blue boot loade choose recovery and kindle wont boot from there.
this is just f***d up. Next time i jsut keep my hands of jailbreaking hardware.
anychance anyone out there could give me a hand and get this fixed? I am
I thought 2.7 hadn't been release for kf2. You sure you flashed the right version for your device? If it is a kf2 then flash this one: http://forum.xda-developers.com/showthread.php?t=2218868
Once you flash it from fastboot, recovery should work again.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
I thought 2.7 hadn't been release for kf2. You sure you flashed the right version for your device? If it is a kf2 then flash this one: http://forum.xda-developers.com/showthread.php?t=2218868
Once you flash it from fastboot, recovery should work again.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
ok got a factory cable and flashed the recovery as you said like that:
fastboot i- 0x1949 flash recovery d:\.android\recovery\twrpnew.img
target reportet max downlaod size of 486539264 bytes
sending 'recovery* (6768 KB)...
OKAY [ 0.438s}
writing 'recovery'...
OKAY [0.719s]
finished. total time 1.156s
so i reboot and select recovery but I get stuck on the blue white logo... what do I do wrong?
androidschima said:
ok got a factory cable and flashed the recovery as you said like that:
fastboot i- 0x1949 flash recovery d:\.android\recovery\twrpnew.img
target reportet max downlaod size of 486539264 bytes
sending 'recovery* (6768 KB)...
OKAY [ 0.438s}
writing 'recovery'...
OKAY [0.719s]
finished. total time 1.156s
so i reboot and select recovery but I get stuck on the blue white logo... what do I do wrong?
Click to expand...
Click to collapse
ok i am just making things worse here. i tried to erase the chach but accidently worte boot... (i know - stuidity needs to be punished)
soo now i get into fastboot. thats to the cable but i need all the files to flash to the right partitions.
could anyone tell me were to get the right
boot.img
system.img
Recovery.img
bootloader.bin
so i can just flash them back onto my device and get i over with....
PLEASE PLEASE PLEASE PLEASE!!!!
androidschima said:
ok i am just making things worse here. i tried to erase the chach but accidently worte boot... (i know - stuidity needs to be punished)
soo now i get into fastboot. thats to the cable but i need all the files to flash to the right partitions.
could anyone tell me were to get the right
boot.img
system.img
Recovery.img
bootloader.bin
so i can just flash them back onto my device and get i over with....
PLEASE PLEASE PLEASE PLEASE!!!!
Click to expand...
Click to collapse
kindle fire first aid has them. But it downloads them off the net last i heard so you wont find the images directly in there unless i am mistaken.
androidschima said:
ok i am just making things worse here. i tried to erase the chach but accidently worte boot... (i know - stuidity needs to be punished)
soo now i get into fastboot. thats to the cable but i need all the files to flash to the right partitions.
could anyone tell me were to get the right
boot.img
system.img
Recovery.img
bootloader.bin
so i can just flash them back onto my device and get i over with....
PLEASE PLEASE PLEASE PLEASE!!!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=43569633
This should be all u need
-》Sent from my mind to your screen.
Thank you! I will look into it!
Hi Everyone
Sorry for my not so good English.
I have problem with my G3 and maybe someone can help? I instal root without problem, than I try to install Twrp recovery and after that I have that message ( [780] fast boot mode started) all the time, I try to do hard reset, click yes twice, but getting the same message, Is there any chance to unbrick that device when I can't go even to download mode?
Thank You very much for any suggestions
help!
help my G3 died the same thing happened!
same to me...
What model(s)? Youll need a pc, adb/fastboot, stock laf.img and boot.img for your device. Youll use adb commands to erase these img files and restore them with the new ones. Once you have adb running and recognizing your device with both files in same folder as adb you'll type adb erase laf [Enter] then adb flash laf laf.img [Enter] do the same steps for the boot.img. Next type adb reboot [Enter] you'll still be in fastboot but just pull the battery. Then replace battery and you should be able to enter download mode by inserting the usb and pressing vol +(i believe, it's been a while) and then kdz flash..
lg g3. maybe you have link ? how to do this..
Thanks.
nerija.nest said:
lg g3. maybe you have link ? how to do this..
Thanks.
Click to expand...
Click to collapse
I know its an lg g3 but what model. I dont have a link to these files and don't feel like searching youll have to search the forum.. Also I just told you how to do this..
D855 16gb , This is what needs to be missed for several days in search of forum. Will be a beautiful day..
nerija.nest said:
D855 16gb , This is what needs to be missed for several days in search of forum. Will be a beautiful day..
Click to expand...
Click to collapse
Ok well I'll meet you in the middle. Heres the link to the d855 partion files http://forum.xda-developers.com/showthread.php?t=2766437. I believe you'll need the second link in the ops first post. As far as adb.. If you dont know how to use it or get the files, Google should be able to help you.
Swizzle82 said:
Ok well Ill meet you in the middle. Heres the link to the d855 partion files http://forum.xda-developers.com/showthread.php?t=2766437. I believe youll need the second link in the ops first post. As far as adb.. If you dont know how to use it or get the files, Google should
be able to help you.
Click to expand...
Click to collapse
Did he drag the .img to the command prompt in order for it work. So its flash laf (the file that is dragged) next do the same thing with boot.img ( flash boot (drag boot file)) and the recovery.img
---------- Post added at 07:47 PM ---------- Previous post was at 07:46 PM ----------
Its suppose to boot up the phone with no problem
i have one problem, not can write files FAILED (remote: flash write failure fastboot unlock , bet I not can write and erase... failure...
download mode problem
I couldn't fix this problem.
[520] Fastboot mode started
[610]--reset--
[610]--portchange--
[730] fastboot: processing commads
can't go to download.I tried adb erase laf adb erase boot I guess I couldn't do.help
if not done contact fb tungkick777 i can help all every body free
fastboot mode started
plz
tungkick said:
if not done contact fb tungkick777 i can help all every body free
Click to expand...
Click to collapse
I have the same problem.. i have d852.. please help!!
i have the same problems after the new upgrade to lollipo 20E vodafone Italy..
Same here
Edit: Solved
1) Took battery and USB Cable off
2) Pressed Volume Up
3) Took battery back while pressing volume up
4) Inserted USB Cable while pressing volume up
5) Phone started Download Mode
6) installed kdz through LG Flash Tools
Right now typing from my LG G3
Great!!!
Thank you very mucho Fusquinha77!!!
I cant get it, I use every way(erase boot,system,recovery, use advence power menu ext..)
But i cant go to download mode
Sent from my Smartfren Andromax AD6B1H using XDA Free mobile app
Fusquinha77 said:
Same here
Edit: Solved
1) Took battery and USB Cable off
2) Pressed Volume Up
3) Took battery back while pressing volume up
4) Inserted USB Cable while pressing volume up
5) Phone started Download Mode
6) installed kdz through LG Flash Tools
Right now typing from my LG G3
Click to expand...
Click to collapse
I can see a different screen for a split of a second but it's going back to Fastboot mode...
@SaharLevi
Here's the fix Quick and easy
need to have fastboot, I used ubuntu can install with sudo apt-get install android-tools-fastboot
info on fastboot
[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer
also need recovery.img, I used the lastest twrp
In terminal
fastboot boot recovery.img
this will boot your phone with the img on your computer.
in recovery restore or install a good boot or kernel.
your phone should be good to go after that.
I had my phone fixed in about 5 min, I really should not play around with boot partition.
Also should be able to flash boot if you have a good one,
fastboot flash boot boot.img
I was trying to install TWRP on my phone (LS990, ZV8) using flashify app. This didn't work and after I did so, every time I would try to "reboot into recovery" the phone would get stuck and I would need to pull the battery out. I then read somewhere that the fix was to delete the aboot.img and install the kitkat aboot.img . I tried to do that, and afterwards my phone won't boot at all. It gets stuck and screen turns black and the LED flashes. It sometimes gives me an error message about the bootloader I think. If I try to boot into Download mode, it (sometimes) takes me straight into fastboot instead. When I try to run fastboot and type "devices" I either get back nothing or now I get back a "?". Maybe I don't have the proper driver. Please Please help!!!
Upsdate: Ok so I played with the drivers and although I still can't get a response to "fastboot devices" I tried to flash a recovery and I can get response on the phone to some degree. It says "fastboot: getwarartition-type:recovery" but the cmd prompt on the computer says "cannot load recovery.img".
Maybe I just need to try and flash a bootloader or a download mode. Anyone know where I can get an laf for download mode. Or Have any directions?
Please help me!!!
UPDATE: FIXED IT!!!! What I did was use fastboot to load up an laf.img that I was able to download from someone on here (took a lot of searching to find an laf.img). Even though I was unable to flash the laf (tried a bunch of times and it always gave me that "failure to write" error right at the end), I was able to use fastboot to boot up the laf.img that was on my computer and that got the phone into download mode. Bear in mind that I still wouldn't get the serial number back from "fastboot devices" so if you're having this problem and it doesn't give you the serial number back it's ok. Just try to run some fastboot commands and see if you get a response on the phone, that way you'll know if fastboot is working. Anyway, I was then able to restore it via LGFlashtool. So yup, its fixable!
MWGiants said:
I was trying to install TWRP on my phone (LS990, ZV8) using flashify app. This didn't work and after I did so, every time I would try to "reboot into recovery" the phone would get stuck and I would need to pull the battery out. I then read somewhere that the fix was to delete the aboot.img and install the kitkat aboot.img . I tried to do that, and afterwards my phone won't boot at all. It gets stuck and screen turns black and the LED flashes. It sometimes gives me an error message about the bootloader I think. If I try to boot into Download mode, it (sometimes) takes me straight into fastboot instead. When I try to run fastboot and type "devices" I either get back nothing or now I get back a "?". Maybe I don't have the proper driver. Please Please help!!!
Upsdate: Ok so I played with the drivers and although I still can't get a response to "fastboot devices" I tried to flash a recovery and I can get response on the phone to some degree. It says "fastboot: getwarartition-type:recovery" but the cmd prompt on the computer says "cannot load recovery.img".
Maybe I just need to try and flash a bootloader or a download mode. Anyone know where I can get an laf for download mode. Or Have any directions?
Please help me!!!
Click to expand...
Click to collapse
Unfortunately its hard bricked and the repair center will know that you tampered with it. The nature of the LG bootloader makes it so that you cant write or boot any images using fastboot.
What was wrong with your method is, when you downgrade to KitKat android bootloader you have to also downgrade the bootloader, laf and recovery partition or other wise it bricks. You should have downgraded your phone using LG Flash Tool to KitKat and then root and install whatever you wanted
In your case the version mismatch between your aboot, bootloader and laf partition is the reason why it doesnt work
MWGiants said:
I was trying to install TWRP on my phone (LS990, ZV8) using flashify app. This didn't work and after I did so, every time I would try to "reboot into recovery" the phone would get stuck and I would need to pull the battery out. I then read somewhere that the fix was to delete the aboot.img and install the kitkat aboot.img . I tried to do that, and afterwards my phone won't boot at all. It gets stuck and screen turns black and the LED flashes. It sometimes gives me an error message about the bootloader I think. If I try to boot into Download mode, it (sometimes) takes me straight into fastboot instead. When I try to run fastboot and type "devices" I either get back nothing or now I get back a "?". Maybe I don't have the proper driver. Please Please help!!!
Upsdate: Ok so I played with the drivers and although I still can't get a response to "fastboot devices" I tried to flash a recovery and I can get response on the phone to some degree. It says "fastboot: getwarartition-type:recovery" but the cmd prompt on the computer says "cannot load recovery.img".
Maybe I just need to try and flash a bootloader or a download mode. Anyone know where I can get an laf for download mode. Or Have any directions?
Please help me!!!
Click to expand...
Click to collapse
If, as you say, you can enter Download Mode, you could try this Method by @hyelton :- http://forum.xda-developers.com/showthread.php?t=2785089. Any problems ask in that Thread, they will try and Help. GOOD LUCK.......:good:
itsbighead said:
Unfortunately its hard bricked and the repair center will know that you tampered with it. The nature of the LG bootloader makes it so that you cant write or boot any images using fastboot.
What was wrong with your method is, when you downgrade to KitKat android bootloader you have to also downgrade the bootloader, laf and recovery partition or other wise it bricks. You should have downgraded your phone using LG Flash Tool to KitKat and then root and install whatever you wanted
In your case the version mismatch between your aboot, bootloader and laf partition is the reason why it doesnt work
Click to expand...
Click to collapse
OK sir, I fixed it so clearly it was not hard bricked (don't say that if you aren't sure, it would have cost me plenty of money to replace that had I not known better). What I did was use fastboot to load up an laf.img that I was able to download from someone on here. Even though I was unable to flash the laf, I was able to use fastboot to boot up the laf.img that was on my computer and that got the phone into download mode. I was then able to restore it via LGFlashtool. So yup, its fixable!
573v3 said:
If, as you say, you can enter Download Mode, you could try this Method by @hyelton :- http://forum.xda-developers.com/showthread.php?t=2785089. Any problems ask in that Thread, they will try and Help. GOOD LUCK.......:good:
Click to expand...
Click to collapse
Yeah, once I got it into download mode (that was the whole problem, I was stuck in fastboot) I was able to fix it.
MWGiants said:
OK sir, I fixed it so clearly it was not hard bricked (don't say that if you aren't sure, it would have cost me plenty of money to replace that had I not known better). What I did was use fastboot to load up an laf.img that I was able to download from someone on here. Even though I was unable to flash the laf, I was able to use fastboot to boot up the laf.img that was on my computer and that got the phone into download mode. I was then able to restore it via LGFlashtool. So yup, its fixable!
Yeah, once I got it into download mode (that was the whole problem, I was stuck in fastboot) I was able to fix it.
Click to expand...
Click to collapse
congrats. it is good to know it is fixable
That's awesome to hear. It seems that booting the laf partition does not actually work under fastboot mode for D855 variants which is why I thought it wouldn't work for you
Sent from my iPad using Tapatalk
That's great. And what fastboot commands did you use to execute the laf from your computer ?
Verstuurd vanaf mijn HTC One_M8 met Tapatalk
Hakem said:
That's great. And what fastboot commands did you use to execute the laf from your computer ?
Verstuurd vanaf mijn HTC One_M8 met Tapatalk
Click to expand...
Click to collapse
Fastboot boot laf.img
But beware this doesnt work for D855. His LS980 has a unlocked bootloader
Ok thanks
Verstuurd vanaf mijn HTC One_M8 met Tapatalk
MWGiants said:
I was trying to install TWRP on my phone (LS990, ZV8) using flashify app. This didn't work and after I did so, every time I would try to "reboot into recovery" the phone would get stuck and I would need to pull the battery out. I then read somewhere that the fix was to delete the aboot.img and install the kitkat aboot.img . I tried to do that, and afterwards my phone won't boot at all. It gets stuck and screen turns black and the LED flashes. It sometimes gives me an error message about the bootloader I think. If I try to boot into Download mode, it (sometimes) takes me straight into fastboot instead. When I try to run fastboot and type "devices" I either get back nothing or now I get back a "?". Maybe I don't have the proper driver. Please Please help!!!
Upsdate: Ok so I played with the drivers and although I still can't get a response to "fastboot devices" I tried to flash a recovery and I can get response on the phone to some degree. It says "fastboot: getwarartition-type:recovery" but the cmd prompt on the computer says "cannot load recovery.img".
Maybe I just need to try and flash a bootloader or a download mode. Anyone know where I can get an laf for download mode. Or Have any directions?
Please help me!!!
UPDATE: FIXED IT!!!! What I did was use fastboot to load up an laf.img that I was able to download from someone on here (took a lot of searching to find an laf.img). Even though I was unable to flash the laf (tried a bunch of times and it always gave me that "failure to write" error right at the end), I was able to use fastboot to boot up the laf.img that was on my computer and that got the phone into download mode. Bear in mind that I still wouldn't get the serial number back from "fastboot devices" so if you're having this problem and it doesn't give you the serial number back it's ok. Just try to run some fastboot commands and see if you get a response on the phone, that way you'll know if fastboot is working. Anyway, I was then able to restore it via LGFlashtool. So yup, its fixable!
Click to expand...
Click to collapse
Hey bro i m having same issue ! Can you please explain laf.img , i tried twrp.img !
What does 'laf' means
bikrame said:
Hey bro i m having same issue ! Can you please explain laf.img , i tried twrp.img !
What does 'laf' means
Click to expand...
Click to collapse
Hi, sorry for the late reply. I hope you've already fixed it, but if you're still having this problem then let me explain. "laf.img" is the "download mode" partition. The reason you can't use twrp.img (which is a recovery partition image) is because you're "too far gone" so to speak and not even at the point to try and get into recovery. You need to restore download mode first. If you have fastboot properly working (not going to explain that, look it up, there is plenty of info about that on here and other sites), then you can do what I did. (Although from what other people are saying if you have a D855 it will have a locked bootloader and this won't work, I cant tell you about that because I don't have one and haven't played around with one). Anyway, if you have fastboot working properly (read my first post about how it can be working as long as the phone is responsive, even if you don't get back the "devices comman", you may need to play around with the drivers to get this to work) then you need to obtain an laf.img from somwhere. I found a complete set of .img's for my model somewhere (don't remember if it was on this site or somewhere else). It took a lot of searching, but I'm sure you can find one. Once you have that and the working fastboot then run the command "fastboot boot [location of your laf.img]laf.img"
GOOD LUCK!!!
itsbighead said:
That's awesome to hear. It seems that booting the laf partition does not actually work under fastboot mode for D855 variants which is why I thought it wouldn't work for you
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
That's interesting...do you have any idea why that would be? Is it a locked bootloader like someone else mentioned? (I don't know much about the D855 model, never got to play with one). Maybe there is a workaround we can come up with...
itsbighead said:
Unfortunately its hard bricked and the repair center will know that you tampered with it. The nature of the LG bootloader makes it so that you cant write or boot any images using fastboot.
What was wrong with your method is, when you downgrade to KitKat android bootloader you have to also downgrade the bootloader, laf and recovery partition or other wise it bricks. You should have downgraded your phone using LG Flash Tool to KitKat and then root and install whatever you wanted
In your case the version mismatch between your aboot, bootloader and laf partition is the reason why it doesnt work
Click to expand...
Click to collapse
I realized the problem with the mismatched aboot after the fact... ironically it all worked out because after all of this I am now back to the original kitkat and can just root and flash as you said lol.
Complete Fix Guide
http://forum.xda-developers.com/spr...y-download-t3053985/post60106965#post60106965
Can you please post where you got your laf file? I have the same problem :crying:
MWGiants said:
I was trying to install TWRP on my phone (LS990, ZV8) using flashify app. This didn't work and after I did so, every time I would try to "reboot into recovery" the phone would get stuck and I would need to pull the battery out. I then read somewhere that the fix was to delete the aboot.img and install the kitkat aboot.img . I tried to do that, and afterwards my phone won't boot at all. It gets stuck and screen turns black and the LED flashes. It sometimes gives me an error message about the bootloader I think. If I try to boot into Download mode, it (sometimes) takes me straight into fastboot instead. When I try to run fastboot and type "devices" I either get back nothing or now I get back a "?". Maybe I don't have the proper driver. Please Please help!!!
Upsdate: Ok so I played with the drivers and although I still can't get a response to "fastboot devices" I tried to flash a recovery and I can get response on the phone to some degree. It says "fastboot: getwarartition-type:recovery" but the cmd prompt on the computer says "cannot load recovery.img".
Maybe I just need to try and flash a bootloader or a download mode. Anyone know where I can get an laf for download mode. Or Have any directions?
Please help me!!!
UPDATE: FIXED IT!!!! What I did was use fastboot to load up an laf.img that I was able to download from someone on here (took a lot of searching to find an laf.img). Even though I was unable to flash the laf (tried a bunch of times and it always gave me that "failure to write" error right at the end), I was able to use fastboot to boot up the laf.img that was on my computer and that got the phone into download mode. Bear in mind that I still wouldn't get the serial number back from "fastboot devices" so if you're having this problem and it doesn't give you the serial number back it's ok. Just try to run some fastboot commands and see if you get a response on the phone, that way you'll know if fastboot is working. Anyway, I was then able to restore it via LGFlashtool. So yup, its fixable!
Click to expand...
Click to collapse
can you please help. adb shows my device and fastboot wont. when i type in fastboot devices it doesnt show anything. tried to run commands but it always gets stuck on waiting for device..
MWGiants said:
(Although from what other people are saying if you have a D855 it will have a locked bootloader and this won't work,
Click to expand...
Click to collapse
What to do with D855 than, my friend have D855 and it's stcked in fastboot mode, doesn't allow to flash anything?
lg g3 f410 stuck at fastboot
i tried the solution it didnot work. phone accepts the cmds but remain stuck at fastboot any other method?
Alright here's the story. I was trying to put CM on this rooted LP 5.0.1 tmobile d851 (20e i think). I backed up and removed the LAF in order to access fastboot so i could flash the custom recovery. fastboot would send the recovery, but the phone would never actually flash the img to the device and report done. Even "fastboot reboot" did nothing. "fastboot devices" reported the serial as "?" and no driver or Arch/CentOS/other windows installs would get fastboot working. fastboot showed up as Marshal london bootloader in device manager.
So then i tried using flash_image from inside of rooted LP to flash the recovery however i ran into PIE errors that could be fixed by replacing /usr/bin/linker. So I found a patched version, rm -rf the old one and tried to cp in the new one. This seemed like a totally valid idea from my linux experience. Buuuut crap. Nothing works. No commands are accepted because I deleted linker. I rebooted cause I had no better alternative and i get a dead android "no command".... Looks like I found the single best way to kill an android installation.
Now im really stuck because i cant use download mode (LAF) to restore because it has been deleted to access fastboot and fastboot wont actually do anything so I can't restore the laf. There is no custom recovery. The stock recovery adb sideload will only let me install OTAs and far as i know there isn't a FULL OTA that will restore the entire system. I even tried the qualcomm 9008 hard brick method with boardDiag, but that doesnt work on tmobile.
I see a few options:
Somehow get fastboot and then download mode working
Wait for a 6.0 OTA and hope it updates the linker bin
advise?
also, the LG logo appears on screen and the LG serial port (the one used for the LG flasher tool) is present in my device manager for a good 15secs before the no command android shows up. I tried lg flasher tool with this time window but it always cut out before the tool could get anywhere.
Edit: This is what the fastboot process would look like:
Screen right after fastboot boot:
[500] Fastboot mode started
[600] -- reset --
[610] -- portchange --
[710] fastboot: processing commands
fastboot erase aboot brings:
erasing 'aboot' ... on command prompt
and
[346290] fastboot: getvarartition-type:aboot
[346350] fastboot: erase:aboot
after those appear it just hangs like that
unplugging it after that command gives me:
FAILED (status read failed (Too many links))
finished. total time: 164.350s
on cmd
and
[514820] -- reset --
[514820] EP1/out FAIL nfo=40 p0=f90bao0
[514830] -- portchange --
[514840] usb_read(0) transaction failed
[514890] fastboot: oops!
[514940] fastboot: processing commands
Click to expand...
Click to collapse
Did you ever find a fix for this?
No, its either professional jtag, or maybe the MM stock ota update zip will fix it if it includes the linker. i havent found this ota on the Internets yet though.
i just had the same problem. any fixes?
flash laf via fastboot
sirbow2 said:
Alright here's the story. I was trying to put CM on this rooted LP 5.0.1 tmobile d851 (20e i think). I backed up and removed the LAF in order to access fastboot so i could flash the custom recovery. fastboot would send the recovery, but the phone would never actually flash the img to the device and report done. Even "fastboot reboot" did nothing. "fastboot devices" reported the serial as "?" and no driver or Arch/CentOS/other windows installs would get fastboot working. fastboot showed up as Marshal london bootloader in device manager.
So then i tried using flash_image from inside of rooted LP to flash the recovery however i ran into PIE errors that could be fixed by replacing /usr/bin/linker. So I found a patched version, rm -rf the old one and tried to cp in the new one. This seemed like a totally valid idea from my linux experience. Buuuut crap. Nothing works. No commands are accepted because I deleted linker. I rebooted cause I had no better alternative and i get a dead android "no command".... Looks like I found the single best way to kill an android installation.
Now im really stuck because i cant use download mode (LAF) to restore because it has been deleted to access fastboot and fastboot wont actually do anything so I can't restore the laf. There is no custom recovery. The stock recovery adb sideload will only let me install OTAs and far as i know there isn't a FULL OTA that will restore the entire system. I even tried the qualcomm 9008 hard brick method with boardDiag, but that doesnt work on tmobile.
I see a few options:
Somehow get fastboot and then download mode working
Wait for a 6.0 OTA and hope it updates the linker bin
advise?
also, the LG logo appears on screen and the LG serial port (the one used for the LG flasher tool) is present in my device manager for a good 15secs before the no command android shows up. I tried lg flasher tool with this time window but it always cut out before the tool could get anywhere.
Edit: This is what the fastboot process would look like:
Click to expand...
Click to collapse
download laf file for your model and flash it....
"fastboot erase laf" then
"fastboot flash laf laf.img"
"fastboot reboot"
Then try to put your phone into download mode.
nibedankaran said:
download laf file for your model and flash it....
"fastboot erase laf" then
"fastboot flash laf laf.img"
"fastboot reboot"
Then try to put your phone into download mode.
Click to expand...
Click to collapse
thanks for the reply, but as i mentioned in my post, fastboot commands don't work. i wish it was that easy.
nibedankaran said:
download laf file for your model and flash it....
"fastboot erase laf" then
"fastboot flash laf laf.img"
"fastboot reboot"
Then try to put your phone into download mode.
Click to expand...
Click to collapse
I think you have a serious problem
You have to see google fix lg g3 on Qualcomm mode...I mean hard brick fix....
Download as instructed
I think it will be fixed
Recently I fixed lg g3 from only led blink no signal to pc and only vibrate and others
That doesn't work on tmobile G3s, thanks though. I did try it anyways btw.
Getting the update.zip from a friend. its in the SD card but its not showing up in MTP so were trying to figure that out. once i have the zip ill try flashing it. if it doesnt work, itll get a octoplus jtag flash.
Well the update did not like the fact that this phone was missing the linker bin or the previous root because it fails when checking the current system. Looks like octoplus is the only way cause i'm an idiot.
Anyone know where i can send this to get it done? i thought some people on ebay did it but i cant find them.
I have same problem, no download mode, system corrupted and recovery is useless.
mysteryjeans said:
I have same problem, no download mode, system corrupted and recovery is useless.
Click to expand...
Click to collapse
If it's a tmobile G3 (d851) you have no choice but send it to someone for an octoplus jtag service because the DIY jtag method doesn't work. Got mine done for $42 after shipping from an ebay service.
sirbow2 said:
If it's a tmobile G3 (d851) you have no choice but send it to someone for an octoplus jtag service because the DIY jtag method doesn't work. Got mine done for $42 after shipping from an ebay service.
Click to expand...
Click to collapse
Finally I recovered it, I have to short testpoint then connect cable to PC, my device is dual sim therefore different logic board, see this http://forum.xda-developers.com/lg-g3/help/lg-d858-qualcomm-test-location-t3293440 for D856/7/8 testpoint to get device into Qualcomm 9008 mode, then I had flash F400K (yes korean rom) tot from thread http://forum.xda-developers.com/showthread.php?t=2785089 using BoardDiagv2.99 http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 to get it live and get into download mode.
Now finally flashed stock KDZ using this post http://forum.xda-developers.com/showpost.php?p=64624353&postcount=3
If I knew there is new tool to flash MM stock, I wouldn't brick my device. :silly:
Thats exactly what i tried but didn't work because D851
Hi everybody, i've an issue with my LG G3 D855(Hong Kong). I bought it with the D85510M version (kitkat). I flashed it with the D85510B with "flashtool 1.8, tot file and a dll file" but it stopped at 94%. Since then, i can't access download mode and recovery. The phone stucks in the Logo and after few minutes goes to fastboot mode. I khow that i have to flash the partitions to restore download mode but the problem is that i can execute the command "Fastboot reboot" but not the other commands. fastboot erase "partition" returns: "failde to erase partition". Fastboot flash "partition" file.img returns: "flash write failure". The latest Android ADB drivers are installed (android adb interface in device manager).
adb devices return nothing. fastboot devices : "? Fastboot."
What is the problem ? Help me please... I'm in windows 10 but i have the same probleme when using Ubuntu. please help me...
SamKat said:
Hi everybody, i've an issue with my LG G3 D855(Hong Kong). I bought it with the D85510M version (kitkat). I flashed it with the D85510B with "flashtool 1.8, tot file and a dll file" but it stopped at 94%. Since then, i can't access download mode and recovery. The phone stucks in the Logo and after few minutes goes to fastboot mode. I khow that i have to flash the partitions to restore download mode but the problem is that i can execute the command "Fastboot reboot" but not the other commands. fastboot erase "partition" returns: "failde to erase partition". Fastboot flash "partition" file.img returns: "flash write failure". The latest Android ADB drivers are installed (android adb interface in device manager).
adb devices return nothing. fastboot devices : "? Fastboot."
What is the problem ? Help me please... I'm in windows 10 but i have the same probleme when using Ubuntu. please help me...
Click to expand...
Click to collapse
Helpe please....
SamKat said:
Helpe please....
Click to expand...
Click to collapse
follow this. it worked for me.
http://forum.xda-developers.com/spr...very-guide-t3132359/post61280085#post61280085
Jahanzaibawan said:
follow this. it worked for me.
http://forum.xda-developers.com/spr...very-guide-t3132359/post61280085#post61280085
Click to expand...
Click to collapse
Thank's for the reply. I've seen this tuto yet but as it's a little bit risky to do this, i decided to look for other solutions. I'm desesperate so i think i'll try this. But, tell me, you did this with wich kind of wire ?
SamKat said:
Thank's for the reply. I've seen this tuto yet but as it's a little bit risky to do this, i decided to look for other solutions. I'm desesperate so i think i'll try this. But, tell me, you did this with wich kind of wire ?
Click to expand...
Click to collapse
I did this on two different mobiles and worked like a charm. It's really useful.
Just use any jumper wire.But be cautious to use thin wire which touch only single pin.
Jahanzaibawan said:
I did this on two different mobiles and worked like a charm. It's really useful.
Just use any jumper wire.But be cautious to use thin wire which touch only single pin.
Click to expand...
Click to collapse
Ok, Thank's a lot.