Thanks bitdomo. Just uninstalled everything and started again and this time no error
. I will definitely check those links out. Thanks again.
[Tutorial] How to flash factory images with LG Flashtool
- Thread starter bitdomo
- Start date
Thanks bitdomo. Just uninstalled everything and started again and this time no error
. I will definitely check those links out. Thanks again.
Hope I can get some help here. Been tracking you here from numerous other "bricked" threads.
THE CULPRIT: While running stock, rooted on multirom with elemental kernel, I used the app Flashify to flash the stock kernel.
BRICK: No boot. No recovery. No Bootloader. No Display.
Biggest problem is I don't know what mode my device is in. But it does appear in device manager. Usually it's the USB section as "USB composite device" that is unable to start. At one point, with various button presses I did see it under ports as "Qualcomm HS-USB QDLoader 9008 (COM5).
So what state is my device in when I see USB composite?
What state is my device in when I see the QDLoader?
Do I have a chance of getting my Nexus back to life? Just got it back from LG with new screen!!!
THE CULPRIT: While running stock, rooted on multirom with elemental kernel, I used the app Flashify to flash the stock kernel.
BRICK: No boot. No recovery. No Bootloader. No Display.
Biggest problem is I don't know what mode my device is in. But it does appear in device manager. Usually it's the USB section as "USB composite device" that is unable to start. At one point, with various button presses I did see it under ports as "Qualcomm HS-USB QDLoader 9008 (COM5).
So what state is my device in when I see USB composite?
What state is my device in when I see the QDLoader?
Do I have a chance of getting my Nexus back to life? Just got it back from LG with new screen!!!
Remove any usb cable
Press and hold power key for 30 secs
Release power key
Press and hold volume up, volume down and power keys at once. If you dont see any sight of life your phone is bricked and no chance to revive it. If you end up im fastboot then reflash stock rom from google.
You were in a secondary rom when you flashed the stock kernel with flashify?
Using your key combo....nothing shows on display. I haven't seen anything on display.
I was in primary ROM when I used flashify to flash stock 4.4.4 kernel.
Looks pretty good per your guide, but nothing happens with the LG Flash screen. (Also had to do some weird adjusting of PC clock and enter registration key).
The driver shows as LGE Mobile USB serial only after manually updating from Qualcom QDL Loader...
So how much does LG get this time?
I was in primary ROM when I used flashify to flash stock 4.4.4 kernel.
Looks pretty good per your guide, but nothing happens with the LG Flash screen. (Also had to do some weird adjusting of PC clock and enter registration key).
The driver shows as LGE Mobile USB serial only after manually updating from Qualcom QDL Loader...
So how much does LG get this time?
I guess the motherboard cost. Which cost around $200-250 here in India. International pricing should not be much different.
When LG flashtool says "READY!!" you have to reconnect your phone.Using your key combo....nothing shows on display. I haven't seen anything on display.
I was in primary ROM when I used flashify to flash stock 4.4.4 kernel.
Looks pretty good per your guide, but nothing happens with the LG Flash screen. (Also had to do some weird adjusting of PC clock and enter registration key).
The driver shows as LGE Mobile USB serial only after manually updating from Qualcom QDL Loader...
So how much does LG get this time?
Have you edited your build.prop file or anything?
Because of those brick things like what happend to you I avoid to use any app or toolkit to flash anything to my nexus. I always use fastboot or flashable zips to flash kernel or anything.
from your screen shot it looks like it's in download mode there (com41).. have you tried running the tool?
No edits to build.prop. It was rooted stock with custom kernel on primary of multiROM.
I've tried reconnecting device with "READY" displayed. Tried holding all three buttons down until it disappears in device manager, then just holding down volume up.
Problem is, I doubt it is truly in download mode. The LG drivers did not automatically install per the guide. I right clicked on my QDLoader device and forced it to the LG driver, and set it to port 41.
if you look at he g2 general forum you should find a big thread on how to restore partitions when download revovery are corrupted... might be able to grab the laf.bin/img from the n5 tot file and flash it using the same method.. this will give you download mode back
Last edited:
This one?
http://xdaforums.com/showthread.php?t=2582142
Do you guys think it could work? Would be a lot of work. Need to install VM for ubuntu, and even then I don't know linux at all.
So it seems that "brick" is a very vague term. Some get stuck in boot loop and they're bricked! How bricked am I? Is there a chance that my hardware is all good? Like I said, I never see anything on my screen. But, I am able to get device recognized as QDL Loader. What exactly is that?
Also, above, you would try just laf.bin/img and then go back to procedure in this thread instead of restoring all the partitions mentioned in the G2 thread?
With a chance, I might give it a try. Thanks.
It only works when your phone is in qualcomm 9006 mode. Sadly your phone is in qualcomm 9008 mode.
Jtag is not a solution since jtag port on the motherboard is disabled in the Qfuse table. You cant change and efuse value. It is like the warranty counter in samsung devices.
3 soultion remained:
-Buy new phone
-Buy new motherboard
-Find connections to the emmc chip on the motherboard. Solder wires to the connection points. Modify an sdcard reader and solder the other end of the wires to the modified sdcard reader. Then you can reflash your bootloader.
The last option is really really hard. The resistors where you can find connection points are so small and also they are covered with some kind material which first have to be removed without tearing off the resistors or damaging tne board.
Thanks! You saved me countless hours fiddling with VM Ware, Ubuntu, and cursing. Would have been neat to resurrect though.
Now I just have to go to PO and send back to Dallas.
Now I just have to go to PO and send back to Dallas.
https://docs.google.com/file/d/0B4JF8SB-3jiqUHdZcFdVNGlJLVE/edit?usp=docslist_api
Regarding my brick:
I had copied this log file from Flashify to send to Dev. The first instance is from a different device I had used. It shows up here because I had used Titanium to restore the app and data to my Nexus.
The log shows activity when Flashify failed to backup kernel on Nexus 5. I asked Dev if this failure was related to multi Rom? I was just wondering if there was any evidence here (logged partition information) that might reveal the reason for it later wiping out my boot loaders and download mode?
Regarding my brick:
I had copied this log file from Flashify to send to Dev. The first instance is from a different device I had used. It shows up here because I had used Titanium to restore the app and data to my Nexus.
The log shows activity when Flashify failed to backup kernel on Nexus 5. I asked Dev if this failure was related to multi Rom? I was just wondering if there was any evidence here (logged partition information) that might reveal the reason for it later wiping out my boot loaders and download mode?
Last edited:
Hello all,
My Nexus 5 is in a bootloop where we cannot enter Download Mode, Fastboot Mode, Bootloader Mode, and surely not Recovery Mode.
It loads to the "Google" screen (1st screen) and then restarts. When Vol Up + Down Buttons are pressed with Power Button, it temporarily loads to Bootloader Screen, then restarts.
Was hoping that Flashtool would solve my issue, but without being able to enter Download Mode, I'm stuck.
Can someone please help me?
My Nexus 5 is in a bootloop where we cannot enter Download Mode, Fastboot Mode, Bootloader Mode, and surely not Recovery Mode.
It loads to the "Google" screen (1st screen) and then restarts. When Vol Up + Down Buttons are pressed with Power Button, it temporarily loads to Bootloader Screen, then restarts.
Was hoping that Flashtool would solve my issue, but without being able to enter Download Mode, I'm stuck.
Can someone please help me?
hi, power off, just vol up and insert USB let your pc install driver's only if your useing lg-flashtool and start again with flash, maybe someone could verify this, hope this help's regard's joe.
Hi Joe,
Not able to do that either. It continues to bootloop once it's connected. When not connected to a power supply (laptop or charger), it is dead to the world, but as soon as juice is given to it, it goes into an eternal bootloop.
Sent from my C6903 using Tapatalk
maybe you could try "nexus root toolkit" hope tis help's. it has maybe a fix for soft brick and bootloop,
Last edited:
Think I tried that as well. Seems that the circuit board shorted or something. Will carry it to a hardware repair shop.
Thanks though.
Sent from my C6903 using Tapatalk
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
48Only you are the responsible if you brick your device. I tried the whole method a few times and no problems so far, but random things could happen.
What is LG Flashtool?
- LG Flashtool is used by LG to flash firmwares to phones.
What are the advantages of using LG Flashtool?
- The flashing process is faster than the fastboot flashing process.
[*]You don't need unlocked bootloader to flash.
[*]It locks bootloader and resets tamper flag.
What are the disadvantages of using LG Flashtool?
- Your battery level must be over 10%.
[*]It changes the device factory version. If your phone had KFS78N version of android initially and you flash a KRT16M firmware, then the device factory version is going to change from KFS78N to KRT16M.
[*]LGD821AT-00-V10a-NXS-XX-OCT-01-2013-KFS78N-USER-16G+0 ==> LGD821AT-00-V10b-NXS-XX-OCT-31-2013-KRT16M-USER-16G+0
[*]This info stored on the misc partition at the 0x00008800 offset. You can change it back to the original one if it bothers you.
[*]To get your original device factory version then just open the log file in the LOG folder which is created at the location of the DLL and TOT file and search for "device factory version" text.
[*]I made a flashable zip (mirror) which bacups the device factory version to /sdcard/version.txt. After the backup just copy the txt to your PC. Then here is the restore zip (mirror). Just place the version.txt to /sdcard and flash the zip to restore.
Preparation (you have to do it only for the first time)
Flashing the firmware
Restore device factory version (optional)
- Create a new txt file called "version.txt" and open it.
- Paste your device factory version from the log file located in the LOG folder where the DLL and TOT file are. Search for "device factory version" text in the log file
- Copy version.txt to the root of the sdcard (/sdcard).
- Download the restore_device_factory_version.zip (mirror).
- Flash restore_device_factory_version.zip in recovery.
Videos
Credits
All the guys from [REF] [TOT] Stock Firmware Collection for Nexus 5 (D820 & D821) thread.
Code:In PDF ([URL="https://mega.co.nz/#!584SzYbC!hSiymZnhn1SVBqwjOY7qsXB4PvgPnYDwYRnMIid9pfE"].docx for translate[/URL]): [URL="https://mega.co.nz/#!koRHkIYa!L6esc81aRvQ3PdbklRgdrQZTIu-vbhhbfC6mam4gIzo"]English-English_LGFlashtool.pdf[/URL] [URL="https://mega.co.nz/#!lwZxhDLa!9L9HE0qjGZ3iIxi01m6nm1EYt23zllri8K9s__5Nmcw"]Magyar-Hungarian_LGFlashtool.pdf[/URL]2
Fastboot: Phone restarts twice. Send the images to the phone memory, after the whole image has been sent, then the phone write it to the emmc from the memory.
LG flashtool: writes the images directly to the emmc.2Great work @bitdomo on putting this together!
I think one of the main advantages that bitdomo may have forgot to mention is that this will work even if fastboot won't (in most cases). For example, say you had a bad bootloader flash, and now you cannot access the bootloader. Consequently, you are not able to flash images using fastboot. However, using LG Flash Tool (or LGNPST) should still allow you to flash your device and get back to a stock state.
Now, the one thing that remains is to figure out how to flash the device using QPST...2Great work @bitdomo on putting this together!
I think one of the main advantages that bitdomo may have forgot to mention is that this will work even if fastboot won't (in most cases). For example, say you had a bad bootloader flash, and now you cannot access the bootloader. Consequently, you are not able to flash images using fastboot. However, using LG Flash Tool (or LGNPST) should still allow you to flash your device and get back to a stock state.
Now, the one thing that remains is to figure out how to flash the device using QPST...
Yes I forgot to say that.
People who killed their bootloaders get Qualcomm HS-USB QDloader 9008 device (without drivers it is QHSUSB_BULK) when they connect their devices to the PC. If they try to enter Download mode they get a black screen as well, but on the pc LGE androidnet serial usb port device comes up. Atleast two out of two people's phone do these symptoms. I don't know what's with the others. LGE androidnet serial usb port device is used to setup CDMA networks on nexus 5, there is a thread about it somewhere. So in short LGE androidnet serial usb port is useless for LG flashtool.
I started an investigation on LGE androidnet serial usb port device to figure out why this comes up for that two people. I found out when you try to enter to Download mode then the phone boots up the LAF image, which is a kernel image like recovery.img or boot.img. I extracted the ramdisk of the LAF (it is on the laf partition) and I found this file init.laf.usb.rc.
Code:# init.laf.usb.rc # it can run as user cable on property:ro.boot.laf=USER wait /sys/class/android_usb/android0/enable write /sys/class/android_usb/android0/enable 0 write /sys/class/android_usb/android0/idVendor 1004 write /sys/class/android_usb/android0/idProduct 6000 write /sys/class/android_usb/android0/bDeviceClass 2 write /sys/class/android_usb/android0/bDeviceSubClass 0 write /sys/class/android_usb/android0/bDeviceProtocol 0 write /sys/class/android_usb/android0/f_acm/acm_transports tty write /sys/class/android_usb/android0/f_diag/clients diag write /sys/class/android_usb/android0/functions acm,laf write /sys/class/android_usb/android0/enable 1 # it can run as user cable for PID of verizon on property:ro.boot.laf=VUSER wait /sys/class/android_usb/android0/enable write /sys/class/android_usb/android0/enable 0 write /sys/class/android_usb/android0/idVendor 1004 write /sys/class/android_usb/android0/idProduct 6246 write /sys/class/android_usb/android0/bDeviceClass 239 write /sys/class/android_usb/android0/bDeviceSubClass 2 write /sys/class/android_usb/android0/bDeviceProtocol 1 write /sys/class/android_usb/android0/f_acm/acm_transports tty write /sys/class/android_usb/android0/f_diag/clients diag write /sys/class/android_usb/android0/functions acm,laf,ecm write /sys/class/android_usb/android0/enable 1 # it can run as factory cable(910K USB cable) on property:ro.boot.laf=910K wait /sys/class/android_usb/android0/enable write /sys/class/android_usb/android0/enable 0 write /sys/class/android_usb/android0/idVendor 1004 write /sys/class/android_usb/android0/idProduct 6000 write /sys/class/android_usb/android0/bDeviceClass 2 write /sys/class/android_usb/android0/bDeviceSubClass 0 write /sys/class/android_usb/android0/bDeviceProtocol 0 write /sys/class/android_usb/android0/f_acm/acm_transports tty write /sys/class/android_usb/android0/f_diag/clients diag write /sys/class/android_usb/android0/functions acm,laf write /sys/class/android_usb/android0/enable 1 # it can run as factory cable(56K USB cable) on property:ro.boot.laf=56K wait /sys/class/android_usb/android0/enable write /sys/class/android_usb/android0/enable 0 write /sys/class/android_usb/android0/idVendor 1004 write /sys/class/android_usb/android0/idProduct 6000 write /sys/class/android_usb/android0/bDeviceClass 2 write /sys/class/android_usb/android0/bDeviceSubClass 0 write /sys/class/android_usb/android0/bDeviceProtocol 0 write /sys/class/android_usb/android0/f_acm/acm_transports tty write /sys/class/android_usb/android0/f_diag/clients diag write /sys/class/android_usb/android0/functions acm,laf write /sys/class/android_usb/android0/enable 1 # it can run as factory cable(130K USB cable) on property:ro.boot.laf=130K wait /sys/class/android_usb/android0/enable write /sys/class/android_usb/android0/enable 0 write /sys/class/android_usb/android0/idVendor 1004 write /sys/class/android_usb/android0/idProduct 6000 write /sys/class/android_usb/android0/bDeviceClass 2 write /sys/class/android_usb/android0/bDeviceSubClass 0 write /sys/class/android_usb/android0/bDeviceProtocol 0 write /sys/class/android_usb/android0/f_acm/acm_transports tty write /sys/class/android_usb/android0/f_diag/clients diag write /sys/class/android_usb/android0/functions acm,laf write /sys/class/android_usb/android0/enable 1 # it can run as user cable for QCT PID on property:ro.boot.laf=QCOM wait /sys/class/android_usb/android0/enable write /sys/class/android_usb/android0/enable 0 write /sys/class/android_usb/android0/idVendor 05C6 write /sys/class/android_usb/android0/idProduct 903A write /sys/class/android_usb/android0/f_acm/acm_transports tty write /sys/class/android_usb/android0/f_diag/clients diag write /sys/class/android_usb/android0/functions mtp,laf write /sys/class/android_usb/android0/enable 1
So, for some reasone for those two guys the laf runs the "on property:ro.boot.laf=QCOM" lines and not the "on property:ro.boot.laf=USER" lines. In the comments you can see both of this mode triggered by "user" cable. I think "user" cable means the normal usb cable. There are 3 more "modes" for 56k, 130k, 910k cables all of these three are identical with "on property:ro.boot.laf=USER" settings. Maybe if that two people get or make one of those cable then they can avoid to get the "on property:ro.boot.laf=QCOM" lines run.
I attached the ramdisk to this post.2Hi as I was on the image link on mega the one that is named as the same as the one installed on my phone...you have the folder marked "Converted"
How is the image Converted/modified?
Thanks in advance
P.S. Could you also Please post the md5 chksums for all of the files, save a brick!
Converted means it is from the other nexus 5 variant. I just changed a text from D820 to D821 and vice-versa, since all nexus 5 the same, using tot images from the other variant cant cause problem. To test out my theory i flashed the d820 kfs78n rom to my d821 and no problem. Here read this: http://xdaforums.com/showpost.php?p=51651325&postcount=82
Tot files has crc check, but if you feel it safer i can make the md5 sums.
Tapatalk-kal küldve az én Nexus 5-el
