Any help is appreciated! First some background:
Flashed device to stock using KK 4.4 version d80020c following steps found here http://forum.xda-developers.com/showthread.php?t=2432476. Successfully rooted using directions (and ioroot25) found here https://www.youtube.com/watch?v=HKuedInhdjU&noredirect=1.
Here's where I got into trouble...Downloaded TWRP 2.7 recovery img and flashed via Flashify. Since this step, my D800 has the exact same symptoms found on this thread http://forum.xda-developers.com/showthread.php?t=2582142.
- No download mode (tried many times)
- No recovery (tried many times also)
- Secure booting error
- LG detected as qhsusb_bulk in device manager
- Device is recognized as 15 different drives, one of which contains a folder named image with 79 different files being .B0X files and Microsoft Access Add-in Data files
- Upon restarting, LG logo with secure booting error, then the screen goes black while your phone is still on
I've followed the steps in the thread that matches my G2's symptoms, run ubuntu 13.1 in VM, apply usb filters for my device which is then recognized as either LG Electonics Inc. QHUSB_BULK or Unknown Device 05C6:9006 when running in VM.
Upon running command ls /dev/sd* in VM Ubuntu Terminal, all that is returned is /dev/sda /dev/sda1 /dev/sda2 /dev/sda5 which are the partitions for Ubuntu, no LG.
I've tried to download and update the Qualcomm drivers, device manager tells me that the drivers were recognized, but cannot be installed and do not pass the hash check (Note: PC is running Windows 8.1).
I've spent over 12 hours on this trying to fix this problem, researched and searched everywhere. If I could get ubuntu to recognize the device, I would be able to continue on with the instructions on this thread http://forum.xda-developers.com/showthread.php?t=2582142.
Links for windows 8 qualcomm drivers, suggestions on how to get the device recognized in ubuntu vm, experiences from others in similar situation, or any with experience working with LG to get a repair done if I'm SOL (as in eMMC is fried) would be so helpful right now.
Thank you all!
After flashing recovery did you flash a patched kernel to boot stock kk?
Sent from my LG-D800 using Tapatalk
I had the same, also with a lot of drives etc.
Screen is black but low backlighted?
Then try with pluged USB Cabel in Phone, hold Power button until screen is realy off, then hold the Power Up Button and plug Cabel into PC.
So I got download mode after I tryed many times
I had problems a few weeks ago getting mine to go into Download mode... turned out that the cable I was using was great for charging, but sucked for everything else. Once I switched to a different cable things worked fine and I was able to load D80010c on the device.
I was running D80020c this morning (with the D80010c boot.img to have a custom recovery) and decided to do an update. Since you can't load D80020k if you have the older bootloader I went all the way back to D80010c, updated to D80010o, D80010q, D80020c and finally D80020k. I was able to root that using IOroot and have restored everything back onto my phone.
-Daryel
Thanks so much for the responses! I've tried endlessly to get the device into download mode, and tried a new cable to no avail. Any other suggestions?
The URL you've linked to will help you solve your problem.
So once you power off your device, hold volume down and power till the lg logo shows, then release shortly and hold them again together till the white window with "factory reset appears", you should notice a text behind the white screen it's fine. So right now when you think it's gonna enter recovery mode the screen is gray(not black), now you connect your device to your ubuntu or whichever linux. You will notice the screen repeatelly blinking when linux is trying to automount the partitions. Figure out which device it is according to the messages it throws. (sdc, sdb, sdX)
This way you should proceed according to the instructions on the thread you linked.
d800 partitions are here
Still no luck
bender_007 said:
The URL you've linked to will help you solve your problem.
So once you power off your device, hold volume down and power till the lg logo shows, then release shortly and hold them again together till the white window with "factory reset appears", you should notice a text behind the white screen it's fine. So right now when you think it's gonna enter recovery mode the screen is gray(not black), now you connect your device to your ubuntu or whichever linux. You will notice the screen repeatelly blinking when linux is trying to automount the partitions. Figure out which device it is according to the messages it throws. (sdc, sdb, sdX)
This way you should proceed according to the instructions on the thread you linked.
Click to expand...
Click to collapse
Thanks for your advice.
I got the white screen asking whether or not I want to perform a factory reset. If I choose No, the phone sends me right to the LG Logo with the error screen. If I choose Yes, it does the same thing. If I plug my phone into my computer while on the white screen asking if I want to perform a factory reset, the device isn't recognized and the PC doesn't see it as plugged in or mounted. I'm not sure what you mean by the timing of when I should try to plug in my device. Thanks again for all your help.
Sneaky Elephant said:
Thanks for your advice.
I got the white screen asking whether or not I want to perform a factory reset. If I choose No, the phone sends me right to the LG Logo with the error screen. If I choose Yes, it does the same thing. If I plug my phone into my computer while on the white screen asking if I want to perform a factory reset, the device isn't recognized and the PC doesn't see it as plugged in or mounted. I'm not sure what you mean by the timing of when I should try to plug in my device. Thanks again for all your help.
Click to expand...
Click to collapse
As soon as in the background of the white menu (factory reset) the secure boot appear plug it in. I'm not sure how much usb filter helps you(maybe it does) but try installing ubuntu over WUBI installer so your win remains. Or at least try ubuntu from usb stick. So you can know for sure if it's working.
Hi Sneaky E. I have the same issue you have. I'll be following your thread. If I figure anything out I'll let you know. I am also having an issue getting mine to charge now. Have you tried downgrading your TWRP?
VirtualBox Error
VirtualBox recognizes the device is plugged in, but won't allow me to push the device for use in linux. I keep getting this error message:
Failed to attach the USB device LG Electronics Inc. QHSUSB__BULK to the virtual machine Ubuntu.
USB device 'LG Electronics Inc. QHSUSB__BULK' with UUID {d8db3712-b86c-4257-a87b-275cef04e5a3} is busy with a previous request. Please try again later.
Result Code: E_INVALIDARG (0x80070057)
Component: HostUSBDevice
Interface: IHostUSBDevice {173b4b44-d268-4334-a00d-b6521c9a740a}
Callee: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}
Click to expand...
Click to collapse
I've tried all USB ports, 2.0 and 3.0. I feel like if I can get past this there should be no reason linux can't see the partitions in the phone. Please Help!!!
Ok so thank you for your help so far. I was able to install Linux on a USB drive and ran the commands and pushed appropriate files from there. I pushed all files including recover.img but the phone will not boot into recovery. Please help!
Thank you!
Sneaky Elephant said:
Ok so thank you for your help so far. I was able to install Linux on a USB drive and ran the commands and pushed appropriate files from there. I pushed all files including recover.img but the phone will not boot into recovery. Please help!
Thank you!
Click to expand...
Click to collapse
you are not alone dude. i had the same issue since sunday and i have spent almost 46 hours already trying to restore my LG G2 F320S korean model.
i followed that instruction in linux, everything went well but then I ended up with a phone not going past the LG logo. the screen no longer dims like how it used to with the secure boot fail error. again, it stucked at the LG logo and thats it.
pressing the 3 buttons though for 5 seconds shows a white screen with 3 options and a bar code under.
but all of these options will just take me back to the LG logo.
I went to a phone technician today, and they said the doing a JTAG fix is the only way to resolve the problem because after trying to fix it with linux, it is no longer identified by my PC.
what are your solutions so far?
anyways before this issue came up, i tried to flash TWRP using flashify, it failed. then went back up. tried to update the OS via OTA then thats it.
i home someone could help us out.
ambetdelarosa said:
you are not alone dude. i had the same issue since sunday and i have spent almost 46 hours already trying to restore my LG G2 F320S korean model.
i followed that instruction in linux, everything went well but then I ended up with a phone not going past the LG logo. the screen no longer dims like how it used to with the secure boot fail error. again, it stucked at the LG logo and thats it.
pressing the 3 buttons though for 5 seconds shows a white screen with 3 options and a bar code under.
but all of these options will just take me back to the LG logo.
I went to a phone technician today, and they said the doing a JTAG fix is the only way to resolve the problem because after trying to fix it with linux, it is no longer identified by my PC.
what are your solutions so far?
anyways before this issue came up, i tried to flash TWRP using flashify, it failed. then went back up. tried to update the OS via OTA then thats it.
i home someone could help us out.
Click to expand...
Click to collapse
What are the negatives to doing a JTAG fix?
Sneaky Elephant said:
What are the negatives to doing a JTAG fix?
Click to expand...
Click to collapse
Here is your fix.
follow exactly. LINK
ingoljosh said:
Here is your fix.
follow exactly. LINK
Click to expand...
Click to collapse
Followed steps already, still can't boot into recovery.
Sneaky Elephant said:
Followed steps already, still can't boot into recovery.
Click to expand...
Click to collapse
if your device is insured maybe report it lost and pay deductible and get a new one AND NEVER ROOT AGAIN
linux cant recognizy my lg g2 f320L
Sneaky Elephant said:
Ok so thank you for your help so far. I was able to install Linux on a USB drive and ran the commands and pushed appropriate files from there. I pushed all files including recover.img but the phone will not boot into recovery. Please help!
Thank you!
Click to expand...
Click to collapse
HI Sneaky elephant........bro I am having the same problem with my lg g2(hard bricked) that its not recognised by Ubuntu...it just shows hssusb-hulk.....no partitions to mount.............
in ur next reply u said that issue solve.....
kindly tell me too that how ur issue resolved...........thanks......
dr jam said:
HI Sneaky elephant........bro I am having the same problem with my lg g2(hard bricked) that its not recognised by Ubuntu...it just shows hssusb-hulk.....no partitions to mount.............
in ur next reply u said that issue solve.....
kindly tell me too that how ur issue resolved...........thanks......
Click to expand...
Click to collapse
The same with me - UP
install ur Ubuntu sing VMware....then partitions will appear.........
---------- Post added at 06:48 PM ---------- Previous post was at 06:46 PM ----------
install ur Ubuntu using VMware......then ur mobile will be recognised and partitions will appear.....
Hello everyone! A guy from the forum told me to ask here for better advice. A few days ago i found my old lg e400 on a drawer and i was curious about its condition. I boot it up and everything is fine, exept for the fact that as soon as i entered my pin, the phone shut down due to low battery. Then, when i reboot, it somehow stuck on the lg logo (it does not even go to the flashing one) and thats it. It is not rooted, nor has cwm recovery installed or usb-debugging enabled. All i can do is see the lg logo, or boot into emergency mode. I tried recovery via lg support tool, but i get errors when it comes to writing data to device. kdz updater brings extract file error too. Please, help me. I want to fix it because it was a gift from my late girlfriend. Thank you in advance.
Never mind guys! After a lot of canibalizing with guides i found online, the phone finally works! If anyone from the moderators can delete this thread, beacause now its kind of non-functional. Thank you!
Hello.
First, sorry for my bad english..
I got the F800L model and I rooted the device following the guide of Dirty Santa.
One day I read in forum that someone was able to flash H918 rom to the F800L device.
So I tried to do same.. but with the mistake of not backing up my original rom.
When I tried to flash the H918 rom through TWRP, it installed well, but when it booted, it just remained hanged in LG logo.
I just left it over a day waiting if it pass the LG logo. But it didn't.
Then I searched for the fix and read the guide about restoring the bricked device through LGUP and kdz file.
So I entered in download mode and connected to PC.
Executed LGUP software and my device appeared in H91810i model instead of F800L. I downloaded the F800L kdz file and tried to restore with LGUP but it appeared error saying kdz invalid.
So I managed to download the H918 10i kdz file and tried again to restore.. and WOW! it completed the process.
But.. Now my device is in worse condition. It doesn't even turn on.
Tried to enter again in download mode but nothing happens.. neither enters in fastboot mode...
Pulled out the battery and reinserted, and tried to turn on but nothing happens..
Can anybody help me please???
I think you destroyed your phone
You should get it to repair service
lol, u just facing the same problem with me, i did exactly the same what u do, was looking around for solution, but nothing really helpful out there, the only way i found is the method with sd card, u get the debrick img file, burn it to a 32gb sd card with the right tool, put sd card to your phone and hope it will get to downloadmode or fastboot or whatever idknow cause i'm don't have the debrick.img file for F800L, looking for it right now, people say u can get that file from the phone (has same model) that still working, that all i know for now, if u found anyway to fix your phone please told me :highfive:
It has been repeated over and over and over "DO NOT FLASH ANYTHING THAT IS NOT MEANT FOR YOUR DEVICE" and also "FLASH AT YOUR OWN RISK". Both of them together makes it pretty clear that you shouldn't have flashed something that was meant only for the h918 into an f800l variant. Developers dont write this down as fancy words or for fun. They do it in order to let everybody know that if flashed, it could easily alter your system in such a way that it might never be fixed except by the company itself. By flashing something that wasnt meant for your device, you are trying to override the system with an image. And if the developer never made the source compatible with yours, then software and hardware will be contradicting each other. The motherboards of the phones comes for its specific variants and only developers can alter an image of a system to make it somewhat compatible with the variant.
Now, lets hope you get an answer to how to fix it because LG wont be fixing it for you since you voided your warranty by a) the simple fact of unlocking the bootloader (which is pretty easy to identify since it shows the warning sign when you turn the phone on), and b) you rooted the device. And LG wont work with neither of those. Unless.... and this is a maybe because i dont know if they would agree too (if you pay the sum they request to fix it, which i assure you it will be more that $100+ maybe even significantly more). Then they fix it for you.
I personally made a backup in a separated MIcro SD card i have outside the phone. So that if i have problems with my system, then i just insert that micro sd card and restore the backup.
Good luck!
If the phones screen is blank when you try to turn it on you bricked. Only fix is a replacement. There is NO debrick.img
oh my god, if u stop at the step KDZ tool found your device that H918, I can help you. Just boot to fastboot mode and fastboot the file name bootbackup.img and KDZ tool will found your device is F800L then KDZ normally. Sorry for my bad English.
gamza88 said:
Hello.
First, sorry for my bad english..
I got the F800L model and I rooted the device following the guide of Dirty Santa.
One day I read in forum that someone was able to flash H918 rom to the F800L device.
So I tried to do same.. but with the mistake of not backing up my original rom.
When I tried to flash the H918 rom through TWRP, it installed well, but when it booted, it just remained hanged in LG logo.
I just left it over a day waiting if it pass the LG logo. But it didn't.
Then I searched for the fix and read the guide about restoring the bricked device through LGUP and kdz file.
So I entered in download mode and connected to PC.
Executed LGUP software and my device appeared in H91810i model instead of F800L. I downloaded the F800L kdz file and tried to restore with LGUP but it appeared error saying kdz invalid.
So I managed to download the H918 10i kdz file and tried again to restore.. and WOW! it completed the process.
But.. Now my device is in worse condition. It doesn't even turn on.
Tried to enter again in download mode but nothing happens.. neither enters in fastboot mode...
Pulled out the battery and reinserted, and tried to turn on but nothing happens..
Can anybody help me please???
Click to expand...
Click to collapse
hi did you find any way to help ? i m in similar position
me2151 said:
If the phones screen is blank when you try to turn it on you bricked. Only fix is a replacement. There is NO debrick.img
Click to expand...
Click to collapse
Hello My Friend,
I have F800s and I rooted by your methos and did exactly the same thing as OP installed H918 rom through twrp. Now I can only go in download mode and LGUP reads my phone as H918 what should I do please help .
hey guys today I am here to help you with your hard bricked beloved yu .when I got my device bricked(you yureka plus) I searched almost every corner on web to rectify the problem but every where I found words like"yu yureka hard bricked but can be detected by windows as Qualcomm hsb bulk ,fake guides on you tube some other guides which do not match peoples consequences
ANALYISING THE PROBLEM
this guide will work if you found following characteristics in your dead yu
1)its not detected in windows weather you put the PC on test or install the Qualcomm drivers
2)only a red led near the recover glow when you connect it to a power source
RECTIFYING YOUR PROBLEM
okay let's start first make a backup emmc image for yu which will send it to fastboot mode
fetch a memory card of 16gb format it in fat32 now using a IMG writing tool (I used win32 disk manager)write the emmc image on it(will take around 20mins)
I know some people has resource deficiency(like me) but get your yu's battery charged at least 40% now unscrew your you on the main board you will see six golden points now insert battery connect data cable to PC and phone(I had assumed here you have installed yu latest drivers in PC) you will see the red led glows again now press the vol up button and short the 2and 6 points on the main board (by a copper wire)pressing the power button
you will several colored lines come on screen and your device will connect as a verified USB device this is the fastboot mode in yu
Now the real works starts as some people still has locked bootloader I here use the official cyanogen as only stock ROM will automatically boot the device now download the requested files I had given the link viz official firmware for yu
The firmware zip contains ygdp tool open it(password 369) fill the CPB file click on start and done on the first boot several lines will appear they will vanish after you warm up your yu by playing games:laugh:
All credits for ygdp assembly tools goes to the coolpad corporation ,Android mtk for firmware files again coolpad for general coolpad drivers
sorry if you found a little tedious here its my first post by my revived you
Mind a little financial help
paytm no 7404034359(Rs 50 or 20 whatever you like)
Help.....
I have done the above steps and and the flashing of stock firmware is done successfully, but when i turn on the phone it always shows low battery. Is there a problem with my battery or Motherboard?
i had a friend's yureka with bootloop on YU logo,i flashed it using adb fastboot,the phone started vibrating and dint even turned on,only goes to fastboot mode after long pressing volume up and shows red light on connection.I also tried emmc image burning on sd card method but still in same condition.Please help
ygdp tool reference
iamtj said:
i had a friend's yureka with bootloop on YU logo,i flashed it using adb fastboot,the phone started vibrating and dint even turned on,only goes to fastboot mode after long pressing volume up and shows red light on connection.I also tried emmc image burning on sd card method but still in same condition.Please help
Click to expand...
Click to collapse
Bro try flashing stock ROM go to android mtk download from there drivers as well as rom
may be bad battery
davidchellappah said:
I have done the above steps and and the flashing of stock firmware is done successfully, but when i turn on the phone it always shows low battery. Is there a problem with my battery or Motherboard?
Click to expand...
Click to collapse
Bro after flashing stock ROM do it rebooted it self?
It worked dude...million thanks to you!!! Since i burned those emmc image to my brand new sandisk 16gb sd card...it is not formatting nor showing the correct size.. Nothing.... so can you tell me how to use the sd card normally again with detailed and 100%working steps. Thanks in advance!!!!
Harish Topgi said:
It worked dude...million thanks to you!!! Since i burned those emmc image to my brand new sandisk 16gb sd card...it is not formatting nor showing the correct size.. Nothing.... so can you tell me how to use the sd card normally again with detailed and 100%working steps. Thanks in advance!!!!
Click to expand...
Click to collapse
well you see the memory card used by me belonged to
one of my friend and i returned him as it is with image file
written on it. when i asked him how he got it normal he said that he put it in a net setter dongle and formatted by going in disk management but i think a simple card reader will do the job for you
Mosam panghal said:
well you see the memory card used by me belonged to
one of my friend and i returned him as it is with image file
written on it. when i asked him how he got it normal he said that he put it in a net setter dongle and formatted by going in disk management but i think a simple card reader will do the job for you
Click to expand...
Click to collapse
Yeah.. Formatting didn't seem to work so spending some time on internet I repartitioned the memory card using a software and I'm good to go now!!