I have one LeEco X720 Bricked.
I can run the TWRP and Fastboot , but USB Device not recognized and OTG not work.
I no have options to connect with PC and transfer IMG to device for update TWRP ou rom.
I try use flashone to qfil but not connect.
I'm see videos and tutorial but no solution.
:chorando:
Rios-BR said:
I have one LeEco X720 Bricked.
I can run the TWRP and Fastboot , but USB Device not recognized and OTG not work.
I no have options to connect with PC and transfer IMG to device for update TWRP ou rom.
I try use flashone to qfil but not connect.
I'm see videos and tutorial but no solution.
:chorando:
Click to expand...
Click to collapse
Do you have drivers on ur pc installed? What system?
Quavosh said:
Do you have drivers on ur pc installed? What system?
Click to expand...
Click to collapse
I use this driver (Qualcomm Diag Qd Loader 2016 Qfil Driver) and try use FlashOne2.0 , I have one X722 and work fine but this X720 don't work.
I try deep flash cable but no sucess.
try that all in one tool to flash a system on the phone from pc
motanel_pufos said:
try that all in one tool to flash a system on the phone from pc
Click to expand...
Click to collapse
I try that too.
But If system pc no recognize I cant use any tool.
I try
Tool All in One
ADB Fastboot
FlashOne2.0
All with good usb cable and with deep flash cable .
All in my X722 work fine but at X720 no detect.
Rios-BR said:
I try that too.
But If system pc no recognize I cant use any tool.
I try
Tool All in One
ADB Fastboot
FlashOne2.0
All with good usb cable and with deep flash cable .
All in my X722 work fine but at X720 no detect.
Click to expand...
Click to collapse
Does your X720 charge?
Sony make.belive said:
Does your X720 charge?
Click to expand...
Click to collapse
Yes
I thinking maybe the problem are Conector of phone, maybe - + are OK but communication pins no.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have this problem and I have not found a solution ...
This issue sounds like one of two things:
First, its possible that your usb card is damaged.
Second, Its much more likely that the issue is with PC that you are connecting to or the USB cord.
The PC obstructions can be resolved by following steps outlined in several extensive posts that I made on these types of issues in this forum: https://forum.xda-developers.com/le-pro3/how-to/guide-unbrick-le-pro3-tested-t3622340 I did alot of research to help a couple of friends successfully unbrick their phone, and created several sets of unbricking steps, in addition to the OP. Everything that I know on how to resolve a bricked phone is covered.
Does the phone charge? If so its mostly likely not the card. if its charging you will see a blinking red light. If you do not see the red blinking light leave it on the charger for 24 hours and recheck.
Quite a few people have unbricked their phones using these steps. Go to search box within the forum and search my name I posted updated links for every file and provided an abundance of steps to try to resolve your issue. Read through the forum many people provided alot of great information. Its long, but worth fixing your phone.
tsongming said:
This issue sounds like one of two things:
First, its possible that your usb card is damaged.
Second, Its much more likely that the issue is with PC that you are connecting to or the USB cord.
The PC obstructions can be resolved by following steps outlined in several extensive posts that I made on these types of issues in this forum: https://forum.xda-developers.com/le-pro3/how-to/guide-unbrick-le-pro3-tested-t3622340 I did alot of research to help a couple of friends successfully unbrick their phone, and created several sets of unbricking steps, in addition to the OP. Everything that I know on how to resolve a bricked phone is covered.
Does the phone charge? If so its mostly likely not the card. if its charging you will see a blinking red light. If you do not see the red blinking light leave it on the charger for 24 hours and recheck.
Quite a few people have unbricked their phones using these steps. Go to search box within the forum and search my name I posted updated links for every file and provided an abundance of steps to try to resolve your issue. Read through the forum many people provided alot of great information. Its long, but worth fixing your phone.
Click to expand...
Click to collapse
HI tsongming thanks for your reply. And sorry my English.
I try this method before this post a try 3 days various methods.
But I can't find nothing for recognize this Fone.
I have other LE PRO 3 and use it for test all connections mode.
I use generic drivers of windows and the drivers of qualcomm. I try select and install by the list on windows. But all options not working.
One time trying I select and install the qualcomm driver manually the device show in the device list on windows and I configure the port to show in flash one in QFIL mode and try flash some times. But when disconnect the phone it show in the list permanently connected or not. When I try open it in flash one I need change the COM to show again in flash one but not really connect.
I turn on the Fone in all mode recovery, fastboot and system.
TWRP work fine but is a old version and not work OTG all other functions work fine.
FASTBOOT I can enter normally but I can connect to pc.
System only stop in the leEco logo.
QFIL mode I can entre by +-power and I have a deep flash cable.
I'm newbie and this is a fist bricked phone in my hands is my learning experience.
If you have any ideas for helping me.
Thanks for the attention.
Rios-BR said:
HI tsongming thanks for your reply. And sorry my English.
I try this method before this post a try 3 days various methods.
But I can't find nothing for recognize this Fone.
I have other LE PRO 3 and use it for test all connections mode.
I use generic drivers of windows and the drivers of qualcomm. I try select and install by the list on windows. But all options not working.
One time trying I select and install the qualcomm driver manually the device show in the device list on windows and I configure the port to show in flash one in QFIL mode and try flash some times. But when disconnect the phone it show in the list permanently connected or not. When I try open it in flash one I need change the COM to show again in flash one but not really connect.
I turn on the Fone in all mode recovery, fastboot and system.
TWRP work fine but is a old version and not work OTG all other functions work fine.
FASTBOOT I can enter normally but I can connect to pc.
System only stop in the leEco logo.
QFIL mode I can entre by +-power and I have a deep flash cable.
I'm newbie and this is a fist bricked phone in my hands is my learning experience.
If you have any ideas for helping me.
Thanks for the attention.
Click to expand...
Click to collapse
Your phone is not bricked. ( It it was you would not be able to access Fast boot or recovery)
When you connect the OTG drive, Don't forget to click install and then select the drive.
If it does not see it reformat the flash drive on your desktop computer to Fat 32 add your Rom, Gapps and magisk.
If it still does not see it try another flash drive or use the All in One tool.
TOOL ALL IN ONE
If your device not recognized is a usb driver issue, and You will need to reinstall the Google USB driver, and while you are at it check to make sure adb is up to date.
Easy Way to do this with one tool
@mauronofrio built an excellent tool for keeping your drivers and adb up to date. Plus it will give ADB system wide privileges.
Mauronofrio's tool is called: "TOOL ALL IN ONE"" and it's great,
After you install it, make sure to check for updates.
Get it here:*https://toolaio.tk**
XDA Main Page:*https://forum.xda-developers.com/le-pro3/development/tool-tool-one-mauronofrio-t3580611
* The all is one tool is excellent and you can use it to install everything you want.
* You can use it to unlock the bootloader.
* Install TWRP,
* Fast your Rom, Gapps and Magisk etc.
* The tool will also update your existing installation of ADB, Android Drivers, and provide system wide ADB privileges.
Since you are having issues I would recommend that you flash lineage 15.1 - It is highly stable and is Caf based.
Make sure that you are using a current version of TWRP and you are rooted. be in the habit of alway rebooting to recovery before rebooting to system. Make sure TWRP stay installed overtime you flash a Rom by checking boxes to check for TWRP install. Otherwise you will be bricked.
This issue sound like you are just boot-looping or you have a soft brick .
You should first try to do a factory reset from the Wipe menu. Then if you can get the OTG drive working, use the all in one tool, or just send the files to the phones storage using Windows explorer.
If you end up with a encrypted storage issue
To format the storage*
Go to Wipe, choose Format Data and follow the instructions.*
This will erase all of photos , music, etc
If you wiped your data partition, you'll need to push the zip file to the newly formatted storage. -*This is one BIG reason why using OTG is better.*You can use Mauronofrio's "TOOL ALL IN ONE"" for pushing the ROM, Gapps, and Magisk to storage.
Root: You absolutely should root!
You will need to wipe storage>Advanced wipe select everything except for your usb drive ( Note this will erase your storage and any files you have on storage)
Reboot to recovery > Install> RoM, Gapps, Magisk > reboot to recovery> reboot to system
If you still have issues, let me know. I am certain that you do not have a brick, it is possible that you USB card in the phone is going bad. but I doubt it.
Finally, get rid of the factory usb cable and replace it with a high quality cable. The stock cable has been known to fry the usb card. and some people go ahead and replace the cable and charger altogether.
I would recommend Anker or this one by google: https://www.amazon.com/Google-Origi...8064&sr=1-22&keywords=USB+Type+C+Wall+Charger
Related
Hello,
I have the following type device: CYXTECH_RK3188 909 V1_1 (CX919 II)
Android stick was working great with XMBC until the screen crashed and since then the stick is not able to boot anymore. CX-919 II is recognized correctly by ROCKusb drivers and i could flash different ROMS (standard and custom) succesfully. However when i connect the tv stick to my television only Google TV logo is shown and after a minute device is rebooting again. So now i am looking for the correct ROM which should work on my stick and advise how to get it up and running again. Anyone who can help me with this?
Thanks a lot!
Dataking said:
Hello,
I have the following type device: CYXTECH_RK3188 909 V1_1 (CX919 II)
Android stick was working great with XMBC until the screen crashed and since then the stick is not able to boot anymore. CX-919 II is recognized correctly by ROCKusb drivers and i could flash different ROMS (standard and custom) succesfully. However when i connect the tv stick to my television only Google TV logo is shown and after a minute device is rebooting again. So now i am looking for the correct ROM which should work on my stick and advise how to get it up and running again. Anyone who can help me with this?
Thanks a lot!
Click to expand...
Click to collapse
Nobody who can advise or help me?
I bricked my device too
I don't think you bricked your device; first, try using a different hdmi cable or different display/monitor
if that doesn't work, it might be a software thing, after some research on your device, you'll find some flashing tools which you can use to flash different roms, if that is the problem, go to this thread http://forum.xda-developers.com/showthread.php?t=2677979 , it is on rooting your device but i'm sure somewhere in the thread, you'll find the flash tool, if you don't, then download Finless ROM 1.6b (I've installed it on my cx919 ii 8gb rom, it is rooted and works perfectly [but there seems to be a bt problem]) http://www.freaktab.com/showthread.php?7553-UPDATED-CX919-4-2-2-Finless-ROM-1-6b
when you connect your device(windows only), you must manually install the provided driver in the file, don't let stu stu windows to install it, if you don't do it correctly, restart
here's how:
P.S. Yea... just hope you had the settings: usb debugging: off, connect to pc: yes/check mark, and connect as mass storage (not camera or mtp or something)
1. Open the flash tool (it should say something like: 'rk device not found' depending on the one u have)
2. Unplug your device from any power source
3. Connect a micro usb to usb cable to the otg port (i used a blackberry cable that was laying around, i believe the provided cable will work)
4. Then connect the usb to a port and imedeately press the 'fn' button (aka the one on the side)
5. Then in the device manager, manually update the driver for it with the one provided in the finless rom, be sure to update the device itself and not the drive/nand flash/ "memory"
6.Then in the flash tool, it should've found the device
7. erase nand memory/ idb
8. finally flash all the preselected items (that's how i bricked my device, when installing ubuntu, the files didn't have a recovery image so i couldn't conect it to my pc and reflash it)
Moment of truth, turn on ur device! u might wanna change some time settings cause some little problems with the rom like the time can bug u a bit
Hope it worked!
If i were u, i would do some more research, that's how i got this, u might stumble upon something and it might be a better guide then mine so just research it!
Now I'm gonna go find out how to fix mine!
Good luck flashing!
---------- Post added at 02:11 AM ---------- Previous post was at 02:07 AM ----------
mindstorms8888 said:
I don't think you bricked your device; first, try using a different hdmi cable or different display/monitor
if that doesn't work, it might be a software thing, after some research on your device, you'll find some flashing tools which you can use to flash different roms, if that is the problem, go to this thread http://forum.xda-developers.com/showthread.php?t=2677979 , it is on rooting your device but i'm sure somewhere in the thread, you'll find the flash tool, if you don't, then download Finless ROM 1.6b (I've installed it on my cx919 ii 8gb rom, it is rooted and works perfectly [but there seems to be a bt problem]) http://www.freaktab.com/showthread.php?7553-UPDATED-CX919-4-2-2-Finless-ROM-1-6b
when you connect your device(windows only), you must manually install the provided driver in the file, don't let stu stu windows to install it, if you don't do it correctly, restart
here's how:
P.S. Yea... just hope you had the settings: usb debugging: off, connect to pc: yes/check mark, and connect as mass storage (not camera or mtp or something)
1. Open the flash tool (it should say something like: 'rk device not found' depending on the one u have)
2. Unplug your device from any power source
3. Connect a micro usb to usb cable to the otg port (i used a blackberry cable that was laying around, i believe the provided cable will work)
4. Then connect the usb to a port and imedeately press the 'fn' button (aka the one on the side)
5. Then in the device manager, manually update the driver for it with the one provided in the finless rom, be sure to update the device itself and not the drive/nand flash/ "memory"
6.Then in the flash tool, it should've found the device
7. erase nand memory/ idb
8. finally flash all the preselected items (that's how i bricked my device, when installing ubuntu, the files didn't have a recovery image so i couldn't conect it to my pc and reflash it)
Moment of truth, turn on ur device! u might wanna change some time settings cause some little problems with the rom like the time can bug u a bit
Hope it worked!
If i were u, i would do some more research, that's how i got this, u might stumble upon something and it might be a better guide then mine so just research it!
Now I'm gonna go find out how to fix mine!
Good luck flashing!
Click to expand...
Click to collapse
Sorry i didn't respond that quick, i just found this thread now, i didn't notice that this was submitted in 2013, i guess it's kinda late...
CX-919 II android TV stick bricked
Hi! I just purchased CX-919 II android TV stick. I was having wifi connection issues, so I decided to change the firmware with 4.4 kitkat. The problem was that when I was going to downgrade to 4.2 I had the usb debugging checked on. so now It seems my device is brick. the blue power light comes on, but the tv screen continues black with no sign og the system booting.
I´m RKbatch tool 1.7 and CX-919 4.2.2 Finless 1.6b with cx919-rk3188-4.2-6210-20131209 firmware
Can anyone help me unbrick my device, please?
Robotechvfx said:
Hi! I just purchased CX-919 II android TV stick. I was having wifi connection issues, so I decided to change the firmware with 4.4 kitkat. The problem was that when I was going to downgrade to 4.2 I had the usb debugging checked on. so now It seems my device is brick. the blue power light comes on, but the tv screen continues black with no sign og the system booting.
I´m RKbatch tool 1.7 and CX-919 4.2.2 Finless 1.6b with cx919-rk3188-4.2-6210-20131209 firmware
Can anyone help me unbrick my device, please?
Click to expand...
Click to collapse
Been there, done that.
When connected to the RKbatch tool, what message do you get?
Do you connect to a WINXP, 7, 8?
I messed my CX919II up when I flashed it using a WIN8 laptop. I tried everything to reconnect to my WIN8 laptop but with no luck.
I then tried on my old WINXP laptop and after installing the USB driver I managed to connect and flash my CX919II.
Now it's up'n,running again
Hope it works for you.
Cheers
Stefan
Unbricking only with the short circuit mehod
I flashed it with win7. I already figured out what went wrong. it´s up and running again. I had to open the case of the CX-919 II / J22 / EKD03 Quad Core Rk3188 Android Smart TV Stick. Although it still connected to the RKbatchtool 1.7 it was always hanging up on the IDB preparing. - IDB fail. So I had no other choice but to short circuit the 7-8 pins of the nan chip in order to flash it again.
I´ll try to leave a detailed guide in this thread:
http://forum.xda-developers.com/hardware-hacking/android-sticks/cx919-ii-completely-bricked-tv-signal-t2859564
It might be useful to anyone who buys the CX 919 from ebay chinese sellers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Short pins 8 and 9
I experimented with mine and unbricked it, Thnx everyone, but I figured it out already, just put a metal thing like a knife or a paper clip on pins 8 and 9,it worked for me, ur tool will see it as maskrom mode, this isn't very specific so unless u no exactly what I mean, don't Try it pls, (I'm really busy these days with homework) ?good luck
EKD03 / J22 / CX 919 lastest firmware
If anyone needs here´s the latest firmware from:
Enybox.com
https://www.dropbox.com/s/m2r18kq6v8e1ld9/cyxtech_rk31_809III_8089_140331.img?dl=0
Ebay Chinese seller
https://www.dropbox.com/s/bhb606vxkc0zh8w/cyxtech_rk31_dongle_ap6210_140606_8G2G.rar?dl=0
Just out of curiosity
Chinese firmware update manual in English
https://www.dropbox.com/s/owus612axk1qelo/EKD03%20-CX919%20firmware%20update%20manual.pdf?dl=0
For drivers please use: Release_DriverAssitant from Rockchip. I´m not posting the link for this one because it´s all over the net.
Robotechvfx said:
If anyone needs here´s the latest firmware from:
Enybox.com
https://www.dropbox.com/s/m2r18kq6v8e1ld9/cyxtech_rk31_809III_8089_140331.img?dl=0
Ebay Chinese seller
https://www.dropbox.com/s/bhb606vxkc0zh8w/cyxtech_rk31_dongle_ap6210_140606_8G2G.rar?dl=0
Just out of curiosity
Chinese firmware update manual in English
https://www.dropbox.com/s/owus612axk1qelo/EKD03%20-CX919%20firmware%20update%20manual.pdf?dl=0
For drivers please use: Release_DriverAssitant from Rockchip. I´m not posting the link for this one because it´s all over the net.
Click to expand...
Click to collapse
Can enyone suggest a working 4.4 ROM for my version of CX919 II? Board details shown in attached picture.
Thanks
Andrea
hi
i flashing the rom but it's no wifi
cant turn it on,
can someone know what can i do?
CX-919 RC-3188 clean stock rom with 4 gb ram
Hi All,
I have CX-919 RC-3188 clean stock rom with 4 gb ram if you interested in
thanx
I am sitting dead in the water with an EVGA Tegra Note 7 that can't turn on Wireless and won't let me install drivers to move further or even do a restore.
First off I am using Tomsgt Super Tool: http://forum.xda-developers.com/showthread.php?t=2627654
So my device was continuing to fail an OTA update so I was going to use this device to reinstall the basic 4.4.2. However during the process Fastboot.exe gave a failed message in Windows, but it showed fastboot after the device name. I continued to let it Restore Tegra Note 7 to Android 4.4.2 and first of all it did it way too fast and once it was finished I couldn't get the Wireless to enable. I read another person with the same problem that had to redo the process. Well I can't get past reinstalling ADB and Fastboot, now not even ADB..
I tried uninstalling the device from Windows letting it reinstall and then checking it again. No matter what I do the USB Driver Scan fails over and over. I got this issue the first time, but somehow I got it to catch the device once and install ADB.
1) Yes USB Debugging in Enabled
2) Yes Anti-Virus is Off
3) Bootloader unlocked
4) Tried Different USB Ports
So what the hell is going on here?? All I wanted to do was run a damn OTA update.. Now I have a tablet with no wireless and I obviously can't do an OTA update now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I was thinking about not using the tool and doing it all manually like I used to do, but all the tool does is auto execute files/folders in specific orders, basically an elaborate .bat file. So if it is failing at ADB, it is going to fail for me manually too.
Please give me some idea of what to do. I don't see how relocking the bootloader would do anything, but aside from that it was a non-rooted stock 4.4.2 OS running.
Is there something I need to do in order to get Impactor to work?
So then I plug the device into a 9 year old laptop with Windows XP and Impactor sees the device on the first try and installs the driver (it takes 2-3 minutes). Then it finishes and I close impactor, but I get an error next saying device not found. I restart the machine and now it is exactly like my desktop, Impactor can't see the device at all.
What in the hell is going on here? If I had known all this was going to happen I would have skipped their damn OTA update that continued to fail.
BTW with XP I can prevent Windows from installing any type of driver, so I did. Should I let XP search for a driver and see what happens?
Someone throw me some ideas, you can see a full explanation of what is happening if you scroll up to my screenshot. I basically have a dead device because I wanted to use this tool to do a recovery...
Wireless refuses to turn on, it just sits there for hours if I let it.
Someone please give me guidance, I was out of the Android scene for a while and I've forgotten a lot of the tricks I used to know.
If your computer is recognizing the fastboot mode that is all you need. Forget the supertool for now.
Can you use the tablet to get into the Fastboot Protocol? It so that will put it in fastboot mode even if it doesn't look like it.
If that works, you can run TWRP or a custom recovery by using ADB and the fastboot command "fastboot boot TWRP_recover.img"
Notice the fastboot "boot", that will only run TWRP once so if you want to on your tablet for good you replace boot with "flash". fastboot flash TWRP_recover.img
You have to make sure the filename is correct with the custom recovery you downloaded.
At this point, put the update you want on your SD card, put that card in the tablet, and go to TWRP or your custom recover and upload the new software.
It sounds complicated but it isn't.
share_needles said:
If your computer is recognizing the fastboot mode that is all you need. Forget the supertool for now.
Can you use the tablet to get into the Fastboot Protocol? It so that will put it in fastboot mode even if it doesn't look like it.
If that works, you can run TWRP or a custom recovery by using ADB and the fastboot command "fastboot boot TWRP_recover.img"
Notice the fastboot "boot", that will only run TWRP once so if you want to on your tablet for good you replace boot with "flash". fastboot flash TWRP_recover.img
You have to make sure the filename is correct with the custom recovery you downloaded.
At this point, put the update you want on your SD card, put that card in the tablet, and go to TWRP or your custom recover and upload the new software.
It sounds complicated but it isn't.
Click to expand...
Click to collapse
Thanks for the suggestions, but I don't think Fastboot has completely installed on my tablet. When I hit Fastboot kernel all I get is a black flash and back to the bootloader again. I believe there is a quick message that flashes the first time I try to select Fastboot, however it's way too fast to read. When I do it again after that is when I will see a black flash, but apparently from what I have heard that is all Fastboot kernel is supposed to do??
How do I verify Fastboot is working before I flash the damn thing?
NCSUZoSo said:
Thanks for the suggestions, but I don't think Fastboot has completely installed on my tablet. When I hit Fastboot kernel all I get is a black flash and back to the bootloader again.
How do I verify Fastboot is working before I flash the damn thing?
Click to expand...
Click to collapse
That is what I was saying when I said you wouldn't even know you're in fastboot. The black-screen with message flashes for a milisecond and goes back to the same screen so it looks like nothing happened when it is actually in fastboot mode.
You can verify this by running your super tool and it will say "fastboot device"
Do you know how to use the ADB command prompt?
Using that, I flashed a custom recovery and then put the below 4.3 zip file on my SD card and going through the tablet I used the TWRP custom recovery to upload 4.3 on the tablet.
I used this old backup of 4.3:
Forum post and links: forum.xda-developers.com/showthread.php?t=2580287
Backupfile name: productionbl_signed_tn7_114gp_2923379__4.3.zip
FYI,
I was in your same situation and that worked for me. I could not get my computer to recognize my device in anything other than fastboot mode.
share_needles said:
That is what I was saying when I said you wouldn't even know you're in fastboot. The black-screen with message flashes for a milisecond and goes back to the same screen so it looks like nothing happened when it is actually in fastboot mode.
You can verify this by running your super tool and it will say "fastboot device"
Do you know how to use the ADB command prompt?
Using that, I flashed a custom recovery and then put the below 4.3 zip file on my SD card and going through the tablet I used the TWRP custom recovery to upload 4.3 on the tablet.
I used this old backup of 4.3:
Forum post and links: forum.xda-developers.com/showthread.php?t=2580287
Backupfile name: productionbl_signed_tn7_114gp_2923379__4.3.zip
FYI,
I was in your same situation and that worked for me. I could not get my computer to recognize my device in anything other than fastboot mode.
Click to expand...
Click to collapse
Can I get some official links for the newest/compatible versions of TWRP and the latest stock ROM I can install that is the most up to date (with Google Apps)?
Sorry to ask, but I am short on time most of the time and I might have an hour or so to work on it tomorrow.
Sorry I don't have official links but it would take you 10mins to find them through google. Good luck.
I have two files which I believe are correct except the TWRP file has an odd extension..
"Shaky156-TWRP-recovery.img.exe"
the other that is supposed to have GApps is: Stock-4.4.2-2.5-TegraNote7.zip
If that zip is only like 440 MB is that even possible? Can someone point me in a better direction if this sounds wrong.
Sources, TWRP: http://forum.xda-developers.com/showthread.php?t=2586432
Actually thinking about it and I bet with having things specific to img files like IMGBurn and other software it may create a .exe so it's easier to emulate it as a disk.
Do we have any good custom ROMs these days you'd suggest over stock? Are any that stable yet? If not can anyone find me a complete download if a 440MB zip is too small to have GApps in it.
I used Fastboot commands to get TWRP installed and Android is "upgrading.." now, so hopefully this will fix it.
I have the tablet up and running going into Google Play now.
I used this thread's link for the latest TWRP (2.7.1.0): http://forum.xda-developers.com/showthread.php?t=2586432
I got a completely stock version of 4.4.2 and OTA shows this as the most up to date version. I got my copy of the 4.4.2 ROM out of the Super Tool's folder that you can find here: http://forum.xda-developers.com/showthread.php?t=2627654
The tricky part to this my first time was I forgot you can open a command window inside the folder that contains TWRP/Fastboot/etc. (hold Shift and Right Click in the folder where all the data is and hit open command window)
Obviously everything came off a SD Card installed into the TN7.
answer for dummies
Hi
Is anyone able to explain how to rectify wifi being turned off constantly in basic non technical talk?
I am not a tech pro and am unsure what to do
All of the above answers are like a different language to me .
Thansks
aimeymarie said:
Hi
Is anyone able to explain how to rectify wifi being turned off constantly in basic non technical talk?
I am not a tech pro and am unsure what to do
All of the above answers are like a different language to me .
Thansks
Click to expand...
Click to collapse
Your best bet is to find someone you know who the above is not a foreign language to. I mean it could be broken down step by step as basic as possible and you may still not understand parts.
So my G2 D800 is currently stuck on Fastboot mode but whenever I run the command "Fastboot devices" it only shows the device as "?", which I thought meant that it had issues recognizing it because of corrupted drivers.
After doing some searching, I decided to download Google USB drivers and LG device drivers, but sadly the computer installs the device as "ADB Google Interface" or "Fastboot Google Interface" and not as an LG device, and this makes the device to show as "?" when the "Fastboot devices" command is run.
I also tried the "ADB devices" command and it came back with a empty line where the G2 should appear.
Just for the record, the G2 cannot enter into Download mode nor Recovery Mode.
Is there a way of making my device show up properly?
potemkinbuster said:
So my G2 D800 is currently stuck on Fastboot mode but whenever I run the command "Fastboot devices" it only shows the device as "?", which I thought meant that it had issues recognizing it because of corrupted drivers.
After doing some searching, I decided to download Google USB drivers and LG device drivers, but sadly the computer installs the device as "ADB Google Interface" or "Fastboot Google Interface" and not as an LG device, and this makes the device to show as "?" when the "Fastboot devices" command is run.
I also tried the "ADB devices" command and it came back with a empty line where the G2 should appear.
Just for the record, the G2 cannot enter into Download mode nor Recovery Mode.
Is there a way of making my device show up properly?
Click to expand...
Click to collapse
ADB devices doesn' t work as it' s in fastboot mode. The ? doesn' t matter fastboot should work.
There are also plenty of guides here in general how you can fix your problem. you need to use the fastboot flash command to flash the proper files to get everything working again. I suggest to erase download mode partition first and get your phone booting/working recovery again. Cause if you did something wrong you could always still enter Fastboot mode by entering download mode because the download mode will be missing so it will go to fastboot.
So fastboot is detected else there wouldn' t be a ?
the only solution for your case is to use testpoint solution to get the download mode (fastboot dont work) i have the same problem before.
wulsic said:
ADB devices doesn' t work as it' s in fastboot mode. The ? doesn' t matter fastboot should work.
There are also plenty of guides here in general how you can fix your problem. you need to use the fastboot flash command to flash the proper files to get everything working again. I suggest to erase download mode partition first and get your phone booting/working recovery again. Cause if you did something wrong you could always still enter Fastboot mode by entering download mode because the download mode will be missing so it will go to fastboot.
So fastboot is detected else there wouldn' t be a ?
Click to expand...
Click to collapse
I've tried this, but it takes forever and when it comes back with a response it only says (ERROR TOO MANY LINKS), which makes the use of fastboot commands useless
albatron34 said:
the only solution for your case is to use testpoint solution to get the download mode (fastboot dont work) i have the same problem before.
Click to expand...
Click to collapse
I wishi I could make it get into download mode xP
Ok, I will keep updating this and hopefully if I find the solution, I might be able to help others with the same case as me.
So far I've tried:
*Flashing all *.img files of my model (D800).
-If you are able to finally enter Download mode, but when you try to flash the ROM you can't because of a wrong model, please check here for a solution.
*Since the method above did not work for me, I had to "destroy" download mode to get back into Fastboot mode so I could Flash TWRP recovery image file.
This has caused my phone to stop being recognized by the PC, which means that when the fastboot commands are run, I cannot get it to work as the computer doesn't know the exact location of the phone (USB, Vendor ID, Details about phone).
To try to make it appear again, I redownloaded the drivers, fastboot files and even went as far as installing manually the drivers through Linux, but none of this seem to work.
As of now, the phone cannot be recognized, but I won't give up until I find a solution!!!
potemkinbuster said:
Ok, I will keep updating this and hopefully if I find the solution, I might be able to help others with the same case as me.
So far I've tried:
*Flashing all *.img files of my model (D800).
-If you are able to finally enter Download mode, but when you try to flash the ROM you can't because of a wrong model, please check here for a solution.
*Since the method above did not work for me, I had to "destroy" download mode to get back into Fastboot mode so I could Flash TWRP recovery image file.
This has caused my phone to stop being recognized by the PC, which means that when the fastboot commands are run, I cannot get it to work as the computer doesn't know the exact location of the phone (USB, Vendor ID, Details about phone).
To try to make it appear again, I redownloaded the drivers, fastboot files and even went as far as installing manually the drivers through Linux, but none of this seem to work.
As of now, the phone cannot be recognized, but I won't give up until I find a solution!!!
Click to expand...
Click to collapse
Did you also tried linux to run the fastboot command as root? Or did you saw the device in device manager in windows?
If all the things don't work then you might need to do the hard brick fix method.
It also may sounds odd but check oe the device is maybe recognized in adb
I ve had same problem as op does. What I did is next:
1. Opened phone and shortened those two capacitors to force phone in QHUSB_BULK mode. (there is tutorial on XDA how to do it)
2. After I connected it to PC it showed many partitions (as it supposed to do)
3. Followed this video https://www.youtube.com/watch?v=_d5b_osUTug
4. Flashed .kdz of choice using flashtool
Im in u hurry now but ask if you need anything else and Ill anwer you when I get home.
wulsic said:
Did you also tried linux to run the fastboot command as root? Or did you saw the device in device manager in windows?
If all the things don't work then you might need to do the hard brick fix method.
It also may sounds odd but check oe the device is maybe recognized in adb
Click to expand...
Click to collapse
I tried with Linux and it wasn't identified.
When I used the "lsusb" command I would get back a google device connected as the vendor ID.
ADB doesn't recognize it either
Godra said:
I ve had same problem as op does. What I did is next:
1. Opened phone and shortened those two capacitors to force phone in QHUSB_BULK mode. (there is tutorial on XDA how to do it)
2. After I connected it to PC it showed many partitions (as it supposed to do)
3. Followed this video https://www.youtube.com/watch?v=_d5b_osUTug
4. Flashed .kdz of choice using flashtool
Im in u hurry now but ask if you need anything else and Ill anwer you when I get home.
Click to expand...
Click to collapse
I'd try this, but I don't have a guide good enough to show me which capacitor I should deal with...
potemkinbuster said:
I tried with Linux and it wasn't identified.
When I used the "lsusb" command I would get back a google device connected as the vendor ID.
ADB doesn't recognize it either
Click to expand...
Click to collapse
so it partly like works, perhaps you can still get it to work but else you must do the hardbrick fix method from general. I can't say much other things how you could fix it if fastboot mode doesn't work recovery not then you must use that.
potemkinbuster said:
I'd try this, but I don't have a guide good enough to show me which capacitor I should deal with...
Click to expand...
Click to collapse
Yeah, its a bit tricky when doing it first time but its not that hard. I used this tutorial to open phone and short those capacitors. You just have to remove almost all conectors (but camera one) and remove everything to get to SoC.
I did try to shorten capacitors and removes all connectors but i suppose to shorten them when i put back connectors exept the battery , the probleme whene i reattach them i can no longer see the capacitors @@
There is that small metal piece that is glued to one of those conectors I have removed to be able to access capacitors.
Godra said:
There is that small metal piece that is glued to one of those conectors I have removed to be able to access capacitors.
Click to expand...
Click to collapse
that small metal piece is the volume boutton , and it seemd that they are not removable
No, there is one bellow it but it might be different in your phone. What version of G2 do you have?
Godra said:
No, there is one bellow it but it might be different in your phone. What version of G2 do you have?
Click to expand...
Click to collapse
I have a g2 d802 32g , and I faild trying to shorten the capacities , there is no clear tut to do it
note : in fastboot devices , my lg is recognized as an "?"
kakashi_senpai said:
I have a g2 d802 32g , and I faild trying to shorten the capacities , there is no clear tut to do it
note : in fastboot devices , my lg is recognized as an "?"
Click to expand...
Click to collapse
So exactly same device as mine. And mine device was recognized as "?" as well. I have tried all drivers and yet it didnt work.
Is your phone still opened?
There is one small hole on each side of back of device from which you can see LCD. When you successfuly shorten capacitors youll see purple-like color which means display got power although if you flip your phone your screen will look like its not on. After that you connect battery conector and unplug USB and your device should (well, mine at least did) be in bulk mode.
Godra said:
So exactly same device as mine. And mine device was recognized as "?" as well. I have tried all drivers and yet it didnt work.
Is your phone still opened?
There is one small hole on each side of back of device from which you can see LCD. When you successfuly shorten capacitors youll see purple-like color which means display got power although if you flip your phone your screen will look like its not on. After that you connect battery conector and unplug USB and your device should (well, mine at least did) be in bulk mode.
Click to expand...
Click to collapse
this is a pic from my phone can u please show where to put the wire please
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
kakashi_senpai said:
this is a pic from my phone can u please show where to put the wire please
Click to expand...
Click to collapse
Well first you need to remove the buttons plate as it's located underneath that. See the images if you don't know what I mean:
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
The only video perhaps available I searched through the thread was this:
https://www.youtube.com/watch?v=15krGmydqgQ&feature=youtu.be
It isn't very clear with the unbricking situation but I unbricked my phone using the images too, Just try to read and see the images and you should be able to unbrick it only you need a thin wire kinda not too large. I couldn't find a smaller wire so it took me like 15 minutes to get it unbricked as I also had some fail attempts.
Yes sir thats my probleme , I tryd to remove the buttons plates but they are stuck with both side , in the video u gave , they are separated
---------- Post added at 10:59 PM ---------- Previous post was at 10:04 PM ----------
well i succeeded to remove button plate , and my device was read as bulk mode. and now i reattached battery and unplug usb connector, now i put back buttons ? and plug it again or what i do exactly ?
ok this was my sister's phone & i screwed it up. i rooted it with towel root while i was backing it up with auto rec & then it asked me to go into recovery mode & when i tapped on it, booom not working since. the device is showing grey lines & computer is not picking it up & yes i have the drivers installed, LG Flash tools & tried powerbutton+volume button trick with no avail. please help me, she'll gonna kill me(literally)
it is like this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Device; LG G2 D802 32GB
Some one please?
DroidsRugly said:
ok this was my sister's phone & i screwed it up. i rooted it with towel root while i was backing it up with auto rec & then it asked me to go into recovery mode & when i tapped on it, booom not working since. the device is showing grey lines & computer is not picking it up & yes i have the drivers installed, LG Flash tools & tried powerbutton+volume button trick with no avail. please help me, she'll gonna kill me(literally)
it is like this.
Device; LG G2 D802 32GB
Click to expand...
Click to collapse
Hi,
I have reported this thread to be moved to the right Q & A section where you might be able to get help quickly.
Good luck.
This is why I worry messing around with my G2
Have you tried long holding the power button?
Sent from my Nexus 6 using Tapatalk
Same thing here. Any answers? I can hold the power button and it turns off for a second then turns itself on and these lines show up again. Same setup after using AutoRec on 4.4.2 rom.
This is a known problem. Have LG send you a new one
blastagator said:
This is a known problem. Have LG send you a new one
Click to expand...
Click to collapse
Sadly way outside the warranty. So it's pretty much toast?
did you try to TOT back to stock?
btw, why were you rooting and messing with your sister's phone in the first place?
stan54 said:
did you try to TOT back to stock?
btw, why were you rooting and messing with your sister's phone in the first place?
Click to expand...
Click to collapse
Computer won't recognize the device at all, and it won't enter download mode. So I am not sure I can TOT back without that functionality.
walkingagh said:
Computer won't recognize the device at all, and it won't enter download mode. So I am not sure I can TOT back without that functionality.
Click to expand...
Click to collapse
Make sure you're phone is fully charged. I had a problem entering download mode with low battery. I also had to try different usb ports on my laptop for whatever reason.
Take the battery out, recharge it through an external charger.
Also enter download mode via inserting USB Cable (Make sure u have LG United driver installed) and keeping Volume Up button pressed for the whole time until Downlaod mode appears on screen, or atleast the screen is on with those lines.
In case of success (i-e. phone shows signs of life), go to Device Manager in ur PC and see if Android Device is connected. Use LG Flash tool 2014 to flash kdz back to normal or try the tot method just in-case your phone is D802/LS/VS variant which doesn't need download mode tbh, just healthy battery.
walkingagh said:
Computer won't recognize the device at all, and it won't enter download mode. So I am not sure I can TOT back without that functionality.
Click to expand...
Click to collapse
And sadly this was my phone. I switched for a while and was coming back and wanted an upgrade to the software. I hadn't updated from 4.4.2 as it had sat in a drawer, then did AutoRec (which I thought I had done before) and boom phone is completely unusable.
---------- Post added 27th December 2015 at 12:07 AM ---------- Previous post was 26th December 2015 at 11:55 PM ----------
dark_prince said:
Take the battery out, recharge it through an external charger.
Also enter download mode via inserting USB Cable (Make sure u have LG United driver installed) and keeping Volume Up button pressed for the whole time until Downlaod mode appears on screen, or atleast the screen is on with those lines.
In case of success (i-e. phone shows signs of life), go to Device Manager in ur PC and see if Android Device is connected. Use LG Flash tool 2014 to flash kdz back to normal or try the tot method just in-case your phone is D802/LS/VS variant which doesn't need download mode tbh, just healthy battery.
Click to expand...
Click to collapse
I can get signs of life (the bars), and windows makes the "you plugged something in and it worked" sound, but there is nothing in device manager despite having the LG drivers installed. Battery is healthy, I used the phone for a day or so to watch videos and stuff. I was working on it there. I think I need to try a different computer.
walkingagh said:
I can get signs of life (the bars), and windows makes the "you plugged something in and it worked" sound, but there is nothing in device manager despite having the LG drivers installed. Battery is healthy, I used the phone for a day or so to watch videos and stuff. I was working on it there. I think I need to try a different computer.
Click to expand...
Click to collapse
Expand under "Ports Com Ports & LPT"
And you will see LGE Com Port Device.
Just flash the kdz away if u see so. otherwise go through the tot method if u see the com port devices to change the com port address to com41 and then flash tot.
I tried this on Windows 10, Windows 8.1, Windows 8 and Windows 7 (all 64-bit versions) and it worked on all of those. Even with USB 3.0 supported laptop.
Your device is at fastboot mode at background, so use fastboot to erase and flashing img files.For example:
fastboot erase laf.img
fastboot flash laf laf.img
you just need your stock img files
wzedlare said:
Your device is at fastboot mode at background, so use fastboot to erase and flashing img files.For example:
fastboot erase laf.img
fastboot flash laf laf.img
you just need your stock img files
Click to expand...
Click to collapse
Any good tutorials on fastboot? And those files come from a bootstack correct?
stan54 said:
did you try to TOT back to stock?
btw, why were you rooting and messing with your sister's phone in the first place?
Click to expand...
Click to collapse
Same problem with me tried Kdz Method. But no luck any idea? It's been 3 months em using it like this. Any help?
Sent from my LG-D800 using Tapatalk
So pretty stuck at this point as well. KDZ method stalls at 60%.
UPDATE FASTBOOT WORKING! Took forever to figure out the drivers, but it's working. I have no clue what to do now.
Fastboot won't recognize the device though I have the fastboot driver installed and running. Any ideas?
TOT is just kinda giving up on me. Still chasing down any leads, but the phone feels pretty borked at this point.
Update: Now in download mode! Man this has been crazy. TOT working! Okay so here is how I did it.
First, I downloaded google's ADB drivers and installed the LG drivers as well. I am not sure which one did it. Then I plugged my phone in and went to device manager. For me, it had an unrecognized device and fastboot wasn't working. So I had to manually assign the driver.
Right click on the device and update driver > Let me choose > all devices > Google > LGE mobile ADB interface.
Now fastboot should be working.
Then I used the srktool_2.1. Option 4 then option 4 again, select model number. It reboots to black screen. From there I was able to completely power off (10 second hold on power button). And when it booted back up all the drivers installed. I was able to TOT back to stock using this guide. http://forum.xda-developers.com/showthread.php?t=2432476. KDZ might work as well.
Unfortunately the screen damage looks to be permanent. But I think this is worth more now than it was 30 minutes ago!
Hello everyone, first let me give major props to my man @bender_007 for creating the amazing LG G Series Autorec Apps which make installing TWRP on LG G Devices a simple process and for also helping me and others who ignorantly misused his app, thanks B!
Anyway recently I bought a LG G3 on Verizon that was on 35b 5.1.1 Lollipop and I rooted. Boy was I eager to get some TWRP poppin on this beast, however flashing TWRP thru Flashify and TWRP Manager left me unsuccessful giving me Secure Booting Error. So desperate I seen Autorec on the Play Store, installed immediately. From there I went through the app's proccesses and from there attempted to boot into recovery hoping for some success.... I did not realize this was went for 24b 5.0.1 until it was late, I mean hey he says it in the description. The phone was dead it wouldn't show anything on the display when I held the power button and it only vibrated, I was f***ed.... At least that is what I thought. I used the method below that me and @bender_007 were collaborating upon as he tried to help me. So please give him credit. I cannot guarantee this will work for you but it worked for me and you don't have to worry about opening up your phone and shorting pins, that nonsense if this works for you.
MATERIALS
A FUNCTIONAL COMPUTER (PREFERABLY WINDOWS, I USED WINDOWS 7)
LG FLASH TOOL 2014: http://www.mediafire.com/?fwrcd3pdj0svjtb
LG DRIVERS-
UNIVERSAL: http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
VERIZON:
http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00520120427
THE LATEST KDZ FOR YOUR PHONE MODEL (GOOGLE IT)
Your Dead but Still Amazing LG G3 and a USB Cable
Note: IF DONE PROPERLY YOU WILL STILL HAVE ALL YOUR EXSISTING DATA PRE-BRICK
PROCEDURE
1. Gather all materials, and know the locations of all your downloaded files.
2. Install the drivers for your phone.
3. Unzip LGFlashTool_2014.zip
4. Move the .KDZ you should've downloaded to the LGFLASHTOOL_2014 folder.
5. Open Device Manager (press start, type in Device Manager into search bar, hit enter)
6. Click View, "Show Hidden Devices"
7. PLUG in USB CABLE TO COMPUTER ONLY!
8. THIS STEP IS VERY VERY VERY IMPORTANT! TAKE THE BATTERY OUT OF YOUR LG G3. PUT IT BACK IN. CLOSE THE BACK. HOLD VOLUME UP ONLY, WHILE HOLDING POWER UP DO NOT LET GO PLUG IN OTHER HALF OF USB CABLE INTO PHONE. KEEP HOLDING VOLUME UP FOR 20 SECONDS. YOURE PHONES SCREEN WILL STILL BE BLACK AND IT SHOULDVE VIBRATED ABOUT 2 SECONDS AFTER YOU PLUGGED IN WIRE (You'll know when you do it right when COMPUTER says installing drivers in bottom right corner.)
9. In Device Manager under Modems there should be something like LGandroidNET I DONT REMEMBER EXACTLY THIS IS ALL OFF THE TOP OF MY HEAD. Anyway, if it says that then you are good, believe it or not your in download mode. (IF YOU DO NOT SEE THIS REPEAT STEP 8)
10. Go to LGFlashTool_2014 folder and run the LGFlashTool2014.exe application.
11. Change PhoneMode to Emergency
12. For "SELECT KDZ FILE" open the folder of the the FlashTool, it should be on it by default and pick the KDZ file.
13. Click "Normal Flash"
14. On the next SCREEN click "START" at the bottom
15. Now there should be a pop-up that says "Select Country & Language" Do not mess with this, just click "OK"
16. There should be a SCREEN now that has a % or whatever... From HERE TO THE END OF IT DO NOT UNPLUG YOUR PHONE!!!
17. When you hit like 85% your phone will boot up do not UNPLUG still and once it hits 100% your done! Safe to UNPLUG and YOU FIXED YOUR PHONE!!!!!!
If you have any questions please ask I have pure empathy for anyone who goes through this hell.
The first time I attempted to connect the phone I successfully had the phone under the modem tab. After being unable to find a .KDZ file (after a minute of searching) I stupidly tried another approach. Now after that not cooperating, I came back to attempt this again after finding a .KDZ file and am unable to set up the device properly to show under the modem tab. I'm following your instructions exactly and gave no luck. Any idea why this would be happening?
wombatthing said:
The first time I attempted to connect the phone I successfully had the phone under the modem tab. After being unable to find a .KDZ file (after a minute of searching) I stupidly tried another approach. Now after that not cooperating, I came back to attempt this again after finding a .KDZ file and am unable to set up the device properly to show under the modem tab. I'm following your instructions exactly and gave no luck. Any idea why this would be happening?
Click to expand...
Click to collapse
Okay I'm here to provide my best assistance and for that you'll have to answer a few questions?
1. What is your device model? ex. VS985 Verizon
2. What KDZ did you attempt to flash? ex. VS98547a_01.kdz
Looking forward to your reply.
Sent from my VS985 4G using Tapatalk
@wombatthing I would go to device manager go to view "Show Hidden devices" then disconnect your phone take out battery put it back in close back then hold volume up for 20 SECONDS while doing that connect to computer. It probably won't say installing drivers because you said it worked the First time, from there see if it's under Modems. Good luck my friend in here for any questions
Sent from my VS985 4G using Tapatalk
Will this method keep all my files that were stored in the internal memory? I'm not worried about the device, i just want my files! Camera pictures etc.
Edit. I tried it but in DIAG mode because i'm afraid emergency can delete my files? I can see the "LGandroidNET " but no vibration and seems like the driivers never install properly. My phone is completely dead.
@bender_007 @OneShotGoGetter
Thanks
Ray1000 said:
Will this method keep all my files that were stored in the internal memory? I'm not worried about the device, i just want my files! Camera pictures etc.
Edit. I tried it but in DIAG mode because i'm afraid emergency can delete my files? I can see the "LGandroidNET " but no vibration and seems like the driivers never install properly. My phone is completely dead.
@bender_007 @OneShotGoGetter
Thanks
Click to expand...
Click to collapse
My friend all is good. First of all as long as it says LGandroidnet you are good you should be in download mode, in lg flash took for mode click emergency and not diag then click normal flash THIS WILL KEEP YOURE DATA IF YOU SEE CRS FLASH OR SOMETHING LIKE THAT THEN ITLL RESET YOURE PHONE just do Emergency and Normal Flash and it should work. Hope I help if you have questions please ask.
@Ray1000 "Emergency" Mode is just Download Mode flashing. Diag is not that's why you were unsuccessful.
Thanks for this! I'm getting stuck at the end (step 16) when the flash tool says:
"Problem with communication between cell phone and PC.
Please disconnect the cable from your cell phone in order and remove and connect the battery. Power on your cell phone and press the Restart button to resume update. If LG Support Tool is stopped abnormally, try with [Options]-[Upgrade Recovery] in tool menu."
I've tried just clicking the retry button, and also unplugging the phone and putting it in recovery mode again before clicking retry. Neither has worked so far. Any thoughts?
Phone is D855, kdz version is D855V20b_00
For all people with Windows 10 an problems with drivers (device is detected by Windows but app is not connecting). Decompress de correct cab for your Windows version, and update the driver "Qualcomm HS-USB QDloader 9008" with the path you used to extract. Now this driver isn't advertising that isn't signed anymore, and all apps will connect with your LG G3
Qualcomm HS-USB QDLoader 9008 2.1.0.5 x86
Qualcomm HS-USB QDLoader 9008 2.1.0.5 x64
mackleroar said:
Thanks for this! I'm getting stuck at the end (step 16) when the flash tool says:
"Problem with communication between cell phone and PC.
Please disconnect the cable from your cell phone in order and remove and connect the battery. Power on your cell phone and press the Restart button to resume update. If LG Support Tool is stopped abnormally, try with [Options]-[Upgrade Recovery] in tool menu."
I've tried just clicking the retry button, and also unplugging the phone and putting it in recovery mode again before clicking retry. Neither has worked so far. Any thoughts?
Phone is D855, kdz version is D855V20b_00
Click to expand...
Click to collapse
Sorry for the late response. First of all you are welcome. I don't know if you fixed the problem yet but I'll help anyway. First remove youre battery for at least 10 seconds then put battery in, hold up and connect charger for 20 seconds. Of you are unsuccessful try reinstalling drivers. Best of luck my friend.
Sent from my VS985 4G using Tapatalk
Hi, I have tried your method but get stuck on "Problem with communication..." Is this a problem specific to windows 10?
I have attempted to update the Qualcomm HS-USB QDloader 9008 but cannot see it in device manager.
Any help would be greatly appreciated!
Perezvon said:
Hi, I have tried your method but get stuck on "Problem with communication..." Is this a problem specific to windows 10?
I have attempted to update the Qualcomm HS-USB QDloader 9008 but cannot see it in device manager.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
Im having the same problem!!!!!! I've tried everything. I will let you know if I fix it and please let me know if you get your's running?
Does anyone know if this method will work for the Sprint LS990 variant? I too had my phone broke by autorec and I lost download bit have access to TWRP and can flash roms but can't do a factory reset with the LG Flash Tool.
Sent from my LG-ls990 using Tapatalk
Failed to flash
Hi,
Thank you for this post. But unfortunately I can not get back my device. What happened was I bricked my phone while flashing TWRP. It's a G3 D855 and does not power on at all. Screen is blank, no LED or vibrate. I tried volume up/down combinations with power button but nothing happens. However when I connect it to PC, device manager shows it under Modem and COM ports.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried to flash a stock ROM using your method. But I got following error during process.
The only problem was phone did not vibrate when I connect it as you mentioned.
Do you think my phone is gone forever? Is there any other way? Appreciate a reply.
Thanks!
i also cannot find the Qualcomm's driver on windows 10 & phone looses communication with flash tool..
vajee555 said:
Hi,
Thank you for this post. But unfortunately I can not get back my device. What happened was I bricked my phone while flashing TWRP. It's a G3 D855 and does not power on at all. Screen is blank, no LED or vibrate. I tried volume up/down combinations with power button but nothing happens. However when I connect it to PC, device manager shows it under Modem and COM ports.
I tried to flash a stock ROM using your method. But I got following error during process.
The only problem was phone did not vibrate when I connect it as you mentioned.
Do you think my phone is gone forever? Is there any other way? Appreciate a reply.
Thanks!
Click to expand...
Click to collapse
the same thing happened to me, just dont close the error notification and move it to the side, so you can see the cellphone is upgrading, dont close the error message until your cellphone boots, this worked for me
ayarihime said:
the same thing happened to me, just dont close the error notification and move it to the side, so you can see the cellphone is upgrading, dont close the error message until your cellphone boots, this worked for me
Click to expand...
Click to collapse
Hello. I managed to get my device to work. Flashed a stock MM rom and now stucked with damn Mcfee kill switch. Can not go to download mode either . Any idea how to fix this? Thanks!
Hi how did you manage to fix it @vagee555? I am receiving the same error message: Problem with communication between cell phone and PC
mjmaxint said:
Hi how did you manage to fix it @vagee555? I am receiving the same error message: Problem with communication between cell phone and PC
Click to expand...
Click to collapse
Hello, I had to short some other two pins to get it identified by my PC. The pins mentioned it this post did not work for me. Follow the link given below and it will work for you. Thank me later.
http://forum.gsmhosting.com/vbb/f494/how-hard-unbricked-lg-g3-all-variants-fix-qhsusb-bulk-_-qualcomm-9008-a-2029025/
He guys thank you very much. My LG3 was already down for months after many failed attempts and I was about to bin it. Decided to give it one last try, found your instructions and it works, I now have Marshmallow!! (However I downloaded the KDZ file from "downloadmirror.de" and I am not sure if that was a good idea.