*****DISCLAIMER*****DISCLAIMER*****DISCLAIMER*****
If you brick your device it's a whole lot of NOT MY PROBLEM
*****DISCLAIMER*****DISCLAIMER*****DISCLAIMER*****
With that out of the way enjoy
1) Download this
https://www.androidfilehost.com/?fid=95747613655047389
2) unzip: V510_4.4.4+tools.zip
3) Install the LG drivers
4) Install LGFlashTools v1.8 (but don't run it)
5) Copy MegaLock.dll to C:\LG\LGFlashTool, This is a hidden folder so enable "hidden folders". Replace the old MegaLock.dll file if you have already installed LG Flash Tool on your computer
6) Launch LG Flash Tool
You might see a window with Korean language, just click on OK
Check the Select Manual Mode on the top
7) MAKE SURE UNDER, DEVICE MANAGER, YOUR PORT IS SET TO COM 41 FOR YOUR DEVICE.
8) Click the DLL box and choose LHV510_SVC_LGFLASHv160.dll
9) Click the S/W box and select the firmware file with .tot extension
10) Now click the Yellow arrow button on the top left of the main window
11) Boot your V510 into Download Mode. To do this power V510 completely off. Then hold Volume Up + Volume Down + plug in USB to PC (in that order)
The firmware installation will be triggered
Ignore if you see any temporary error and just wait patiently till it is finished.
I took these instructions from another post. That post ended by giving "Credit [email protected] for making a cleaner guide for the TOT Method"
It's a shame the v500 can't be converted
n0credit said:
It's a shame the v500 can't be converted
Click to expand...
Click to collapse
This might help: http://goo.gl/rPx8KK
+1 worked perfectly for me.
The only part that I had a little trouble with was changing the COM port to 41.
Windows users: you must be booted into Download Mode for the tablet to show up in Device Manager, where you change the COM port. I was trying to change the port while the tablet was booted up (normally) and it was driving me crazy.
Need some help:
tl;dr: Pretty sure I still need to flash the stock recovery, but having problems.
Coming from a rooted LG GPad GPE with TWRP installed. I followed the instructions on this thread and everything seems to have worked. I'm now unrooted, but I'm still getting "your system is up to date" when I check for an update in settings.
I think I do not have the right recovery installed, and that is why I am not getting the update. When I try to boot into recovery mode, I get the android guy on his back with a red triangle. No signs of TWRP being installed anymore.
I've tried several times to flash the stock recovery as listed in this thread: http://forum.xda-developers.com/showthread.php?t=2574639. It seems to work, but I don't think it is working properly. I also can't sideload the 5.0 file through ADB, since I need to put the device into recovery mode to do it.
---------- Post added at 02:24 PM ---------- Previous post was at 01:46 PM ----------
Nevermind. Turns out that is the stock recovery. Now my problem is I can't push the file over ADB. The ADB connection doesn't persist into recovery mode. I've followed the steps here: http://forum.xda-developers.com/showthread.php?t=2575783.
When the device is on normally, the ADB connection is fine. It shows up in the list of connected devices. When I reboot into recovery and choose "apply update from ADB" and then enter "adb devices" I get no devices connected.
In device manager, I see "LG-V510" under "other devices" but when I try to manually update the drivers to the google drivers as indicated in the post above, the computer says "Windows could not find driver software for your device."
Still need help...
mcaurilio said:
Need some help:
tl;dr: Pretty sure I still need to flash the stock recovery, but having problems.
Coming from a rooted LG GPad GPE with TWRP installed. I followed the instructions on this thread and everything seems to have worked. I'm now unrooted, but I'm still getting "your system is up to date" when I check for an update in settings.
I think I do not have the right recovery installed, and that is why I am not getting the update. When I try to boot into recovery mode, I get the android guy on his back with a red triangle. No signs of TWRP being installed anymore.
I've tried several times to flash the stock recovery as listed in this thread: http://forum.xda-developers.com/showthread.php?t=2574639. It seems to work, but I don't think it is working properly. I also can't sideload the 5.0 file through ADB, since I need to put the device into recovery mode to do it.
---------- Post added at 02:24 PM ---------- Previous post was at 01:46 PM ----------
Nevermind. Turns out that is the stock recovery. Now my problem is I can't push the file over ADB. The ADB connection doesn't persist into recovery mode. I've followed the steps here: http://forum.xda-developers.com/showthread.php?t=2575783.
When the device is on normally, the ADB connection is fine. It shows up in the list of connected devices. When I reboot into recovery and choose "apply update from ADB" and then enter "adb devices" I get no devices connected.
In device manager, I see "LG-V510" under "other devices" but when I try to manually update the drivers to the google drivers as indicated in the post above, the computer says "Windows could not find driver software for your device."
Still need help...
Click to expand...
Click to collapse
I guess I'm not quite sure what you were trying to accomplish. If it is to install TWRP. You need to use fastboot from download mode and flash your recovery there, rather than trying to use adb from the recovery itself. "Fastboot flash recovery palman.img". , where palman.img is the name of whatever recovery you want to flash.
Fairly certain I did everything correctly according to the directions. When I press the yellow arrow about how long does it take to complete the install? When i started it, little box came up said some things that I don't remember and after about 30 seconds, the little box went away and the COM41 box says Ready!! Does that mean its finished? Just dont want to unplug tablet before the process is finished and brick it. Thanks
Nevermind, figured it out. Had to unplug device and plug usb back in and that triggered it to start.
sleekmason said:
I guess I'm not quite sure what you were trying to accomplish. If it is to install TWRP. You need to use fastboot from download mode and flash your recovery there, rather than trying to use adb from the recovery itself. "Fastboot flash recovery palman.img". , where palman.img is the name of whatever recovery you want to flash.
Click to expand...
Click to collapse
No, I was trying to sideload the 5.0 upgrade. Couldn't get my adb connection to persist through to recovery mode. Finally figured it out and was able to get the tablet upgraded this morning - but I had to use the TWRP backup method. Everything seems to be good to go now though!
Correct drivers
I'm having problems getting the port changed to 41 and I think it because the drivers aren't installing correctly. Could someone confirm from the screenshot below that I'm on the right track, or maybe post a shot of what the correct driver set-up should look like? Thanks.
**Edit: Got it, I did have the wrong drivers.
I don't think you have the right drivers installed. There should be two of them and mine were both banged-out yellow, but only when in download mode and with the software running. You don't even have a ports tab to change it (or you have the wrong device).
I gave up and restored the Lollipop backup someone posted, which worked great except then I had to re-root and flash TWRP again.
-MX- said:
I'm having problems getting the port changed to 41 and I think it because the drivers aren't installing correctly. Could someone confirm from the screenshot below that I'm on the right track, or maybe post a shot of what the correct driver set-up should look like? Thanks.
{
"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"
}
Click to expand...
Click to collapse
If drivers are installed correctly, you should find it under Ports(COM & LPT) expand that and LG should be there. Right click and properties and find the COM41
shawn13165 said:
If drivers are installed correctly, you should find it under Ports(COM & LPT) expand that and LG should be there. Right click and properties and find the COM41
Click to expand...
Click to collapse
Yeah, definitely wrong drivers, had to do some uninstalling/reinstalling and finally got it to work.
Colchiro said:
I don't think you have the right drivers installed. There should be two of them and mine were both banged-out yellow, but only when in download mode and with the software running. You don't even have a ports tab to change it (or you have the wrong device).
I gave up and restored the Lollipop backup someone posted, which worked great except then I had to re-root and flash TWRP again.
Click to expand...
Click to collapse
I had given up for the 4.4.4 update when it initially came out and upgraded through TWRP, but now I'm running into issues with not being able to use the external SD card from the TWRP backup of LP that was posted, so I figured I needed to give this method a shot and do it right.
Any chance we will get the 5.0 TOT file for the v510? I tried following this guide: http://forum.xda-developers.com/showthread.php?t=2220801 and also tried using wireshark to capture the path in the LG Support tool but haven't had any luck with either method.
Thanks man. This helped me restore my G Pad when I thought all hope was lost.
Thank you very much, this worked perfect!
Related
Tried my best to search the forums for anyone else having this issue, couldn't find much.
My N7 isn't rooted at all. It worked fine until last night, the screen wouldn't turn on so I held the power button down to turn it off, booted it back up and it goes into a screen with a red triangle and says "No Command". It sits on this screen for a while and then reboots, and does the same over and over. I can get into fastboot (it also throws the "No Command" when trying to get into recovery), but I'm not sure what my options are. I'm hoping I don't have to resort to wiping the device, so any suggestions would be appreciated, thanks!
AW: [Q] Boots Into "No Command" Screen
When you boot in recovery and the red triangle appears, have you tried to press volume down and power again? It should boot in recovery
Sent from my SK17i running Android 4.1.2
Use fastboot to flash a custom recovery, and then do a nandroid backup. From there, you can mess around without fear of losing your data. Perhaps you will need to re-flash the boot or system image, but I can't imagine what could have happened to it in the first place.
AW: [Q] Boots Into "No Command" Screen
korockinout13 said:
Use fastboot to flash a custom recovery, and then do a nandroid backup. From there, you can mess around without fear of losing your data. Perhaps you will need to re-flash the boot or system image, but I can't imagine what could have happened to it in the first place.
Click to expand...
Click to collapse
He said he has no root and so I guess the bl is locked so he would loose his data while unlocking, right?
Sent from my SK17i running Android 4.1.2
I contacted support and they pretty much immediately started to process an RMA. She said someone had called in earlier today with the same problem and they couldn't figure anything out. I have a feeling they don't send new ones for these types of things, so I'm still going to try to fix mine. Thanks for the suggestions.
Here's a pic, I'm still confused on how little I've found about this "No Command" screen:
{
"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"
}
mihahn said:
When you boot in recovery and the red triangle appears, have you tried to press volume down and power again? It should boot in recovery
Sent from my SK17i running Android 4.1.2
Click to expand...
Click to collapse
Woah, did you mean power and volume UP? Because that works... it brings up the recovery menu.....
Am I missing something? Is it normal to have to press power + volume up to see the recovery menu?
Okay, so I guess the real problem is that I'm stuck booting into recovery. Was there an OTA update?
I ended up fixing this. Once I realized what I was seeing was recovery mode, I tried clearing data + cache, but that didn't work. Still booted into recovery mode every time. I went through the mess of installing the right drivers (no idea if it's just me but I always have issues with my computer recognizing my devices), and I used the android SDK to unlock the bootloader and then flashed the factory image. Lost all my data but oh well, better than going through the RMA process.
Thanks again for the help. I seriously would have never realized that silly screen was recovery. Why can't it just show the menu by default...
edit: one other thing, the biggest hurdle I ran into was that I didn't have the drivers installed at all. but since I couldn't boot up I couldn't install the adb driver. I was able to install the fastboot one just fine, but the fastboot commands didn't work until I installed the adb driver. only way I was able to install the adb driver was to go into the 'sideload using adb' option in recovery, at that point windows prompted for the drivers. not sure if there's a manual way of installing the driver but yeah. hopefully that made some sense.
Leadsuit said:
Woah, did you mean power and volume UP? Because that works... it brings up the recovery menu.....
Click to expand...
Click to collapse
Just for future reference, when at the red triangle, you can get into recovery by holding vol up and power?
Sent from my SGH-I777 using xda premium
From efrants android 101 sticky:*I just flashed CWM, but every time I try to boot into CWM, I keep seeing the stock recovery. Why?If you updated your Android build using an OTA update file (either manually or over-the-air), the update placed two files on your device that re-flash the stock recovery every time you reboot your device. These two files are:/system/etc/install-recovery.sh <== this is the script that installs the patch file/system/recovery-from-boot.p <== this is the patchYou have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick.
Sent from my GT-I9300 using xda premium
---------- Post added at 06:17 AM ---------- Previous post was at 06:10 AM ----------
That is the cause of the No Comnand screen.
Sent from my GT-I9300 using xda premium
please explain the steps to fix the NO COMMAND on your tablet
Leadsuit said:
I ended up fixing this. Once I realized what I was seeing was recovery mode, I tried clearing data + cache, but that didn't work. Still booted into recovery mode every time. I went through the mess of installing the right drivers (no idea if it's just me but I always have issues with my computer recognizing my devices), and I used the android SDK to unlock the bootloader and then flashed the factory image. Lost all my data but oh well, better than going through the RMA process.
Thanks again for the help. I seriously would have never realized that silly screen was recovery. Why can't it just show the menu by default...
edit: one other thing, the biggest hurdle I ran into was that I didn't have the drivers installed at all. but since I couldn't boot up I couldn't install the adb driver. I was able to install the fastboot one just fine, but the fastboot commands didn't work until I installed the adb driver. only way I was able to install the adb driver was to go into the 'sideload using adb' option in recovery, at that point windows prompted for the drivers. not sure if there's a manual way of installing the driver but yeah. hopefully that made some sense.
Click to expand...
Click to collapse
please explain the steps to fix the NO COMMAND on your tablet?
tHanks
help please
Leadsuit said:
I ended up fixing this. Once I realized what I was seeing was recovery mode, I tried clearing data + cache, but that didn't work. Still booted into recovery mode every time. I went through the mess of installing the right drivers (no idea if it's just me but I always have issues with my computer recognizing my devices), and I used the android SDK to unlock the bootloader and then flashed the factory image. Lost all my data but oh well, better than going through the RMA process.
Thanks again for the help. I seriously would have never realized that silly screen was recovery. Why can't it just show the menu by default...
edit: one other thing, the biggest hurdle I ran into was that I didn't have the drivers installed at all. but since I couldn't boot up I couldn't install the adb driver. I was able to install the fastboot one just fine, but the fastboot commands didn't work until I installed the adb driver. only way I was able to install the adb driver was to go into the 'sideload using adb' option in recovery, at that point windows prompted for the drivers. not sure if there's a manual way of installing the driver but yeah. hopefully that made some sense.
Click to expand...
Click to collapse
hi Sir! I'm having the same problem, please help me. i dont know anything about adb drivers..
please tell me steps to use adb side load my android spice dream uno mi498
Leadsuit said:
I ended up fixing this. Once I realized what I was seeing was recovery mode, I tried clearing data + cache, but that didn't work. Still booted into recovery mode every time. I went through the mess of installing the right drivers (no idea if it's just me but I always have issues with my computer recognizing my devices), and I used the android SDK to unlock the bootloader and then flashed the factory image. Lost all my data but oh well, better than going through the RMA process.
Thanks again for the help. I seriously would have never realized that silly screen was recovery. Why can't it just show the menu by default...
edit: one other thing, the biggest hurdle I ran into was that I didn't have the drivers installed at all. but since I couldn't boot up I couldn't install the adb driver. I was able to install the fastboot one just fine, but the fastboot commands didn't work until I installed the adb driver. only way I was able to install the adb driver was to go into the 'sideload using adb' option in recovery, at that point windows prompted for the drivers. not sure if there's a manual way of installing the driver but yeah. hopefully that made some sense.
Click to expand...
Click to collapse
I have spice dream uno 498 6.0.1 my phone showing no command Pls tell me steps of using adb +command to give via pc
* I don't know enough to be messing with this, but here I am.
** My device is rooted, but I got into this mess by updating (device was working fine, did not use 3rd party software) and when it restarted after install it went to boot loader.
*** Device only turns on when its plug into wall outlit for 20 seconds. I can not get it to turn on with power button or when its plugged into laptop. Not sure if this is normal or not.
**** Something similar happened to this before but I just used twrp and fixed it. I can not flash a recovery unless my nexus is working normally.
***** Yes, I read other threads, on this forums and others, havnt found anything that has helped. I figured i could post specific details that other threads were lacking.
My nexus 10 is currently stuck in boot loader. If I select recovery mode, it does not switch to the smaller green android, that you can press down power, volume down/up and get into TWRP. Nothing I have done has gotten me anywhere except boot loader. I have tried to use Nexus Root Tool Kit and use the Flash Stock + Unroot and Flash Image to various partitions. No success. Today, downloaded Odin 3.07, but it crashed when file analysis in message box.
Im downloading SDK tools right now, but Im not quite sure what those are, will have to experiment.
See attached files 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"
}
Image of recovery that I can not get to.
Current state of device. can not get anywhere else.
Close up of date.
Picture of odin failing. I tried to flash using the option called PDA by the way.
Picture of options Im trying to use on NRT. I also tired flash stock +unroot but no change to device.
solved - cant find where to set this thread to solved thought.
Any help is greatly appreciated.
Nyreb said:
* I don't know enough to be messing with this, but here I am.
** My device is rooted, but I got into this mess by updating (device was working fine, did not use 3rd party software) and when it restarted after install it went to boot loader.
*** Device only turns on when its plug into wall outlit for 20 seconds. I can not get it to turn on with power button or when its plugged into laptop. Not sure if this is normal or not.
**** Something similar happened to this before but I just used twrp and fixed it. I can not flash a recovery unless my nexus is working normally.
***** Yes, I read other threads, on this forums and others, havnt found anything that has helped. I figured i could post specific details that other threads were lacking.
My nexus 10 is currently stuck in boot loader. If I select recovery mode, it does not switch to the smaller green android, that you can press down power, volume down/up and get into TWRP. Nothing I have done has gotten me anywhere except boot loader. I have tried to use Nexus Root Tool Kit and use the Flash Stock + Unroot and Flash Image to various partitions. No success. Today, downloaded Odin 3.07, but it crashed when file analysis in message box.
Im downloading SDK tools right now, but Im not quite sure what those are, will have to experiment.
See attached files please.
View attachment 2637629
Image of recovery that I can not get to.
View attachment 2637596
Current state of device. can not get anywhere else.
View attachment 2637598
Close up of date.
View attachment 2637611
Picture of odin failing. I tried to flash using the option called PDA by the way.
View attachment 2637622
Picture of options Im trying to use on NRT. I also tired flash stock +unroot but no change to device.
Any help is greatly appreciated.
Click to expand...
Click to collapse
Shoot me a email at [email protected]... We can talk more about your issues there..... Thx lj
Solution
Thanks to lj50036, my nexus now actually works.
Here's what he told me to do:
----------
1.) start here http://forum.xda-developers.com/showthread.php?t=2588979
This will install abd fastboot and the drivers for your tablet just follow instructions.
2.) Now open cmd as admin and type
fastboot
should see commands and options listed
3.) now type
cd /
this will move root to c drive.
4.) plug in tablet, boot into bootloader (holding down power, volume up and down I think) and type
fastboot devices
this output serial number of device and then type of device (Fastboot)
5.) go to https://developers.google.com/android/nexus/images#mantaray or google factory images and find Nexus 10. use what ever version you want. download, unzip and you should see something along the lines of this (the kot49h will be what ever version of the image you used.)
6,) move everything but the 2 .sh files to root of c drive (c:/)
and then in cmd prompt type
dir
this will print out file names, data, and other information of c:/. make sure you see the 3 files you moved from the factory image you unzipped.
7.) if so, make sure tablet is in bootloader still, and type
flash-all.bat in cmd prompt.
--About halfway through it reboots your nexus and because my nexus wont reboot its self, and will only come on when its plugged into wall outlet for a bit, I just did that and plugged in and it worked fine.
-- once the whole process runs, my nexus rebooted into recovery mode, and after a minute rebooted correctly and I was able to start setting up.
----------------
Thank you again to lj50036
@Nyreb
Change the forum name to include (SOLVED)
@lj50036
So I had mostly the same problem happen, except I tried to get into recovery to flash a CM11, but I was completely stock. It would get stuck on the screen below. I did what you said to do above and it still sticks at the same screen it did before, except sometimes it shows the Google logo before getting stuck. It used to just show the android on it's back right off the bat. Not sure what to do anymore.
spudsmac said:
@lj50036
So I had mostly the same problem happen, except I tried to get into recovery to flash a CM11, but I was completely stock. It would get stuck on the screen below. I did what you said to do above and it still sticks at the same screen it did before, except sometimes it shows the Google logo before getting stuck. It used to just show the android on it's back right off the bat. Not sure what to do anymore.
Click to expand...
Click to collapse
Shoot me a email.... Sounds like you need some help....
So I ended up emailing @lj50036 and we went back and forth and had to reflash everything, including custom recovery, TWRP. I think the recovery was messed up.
Finally works again!
spudsmac said:
So I ended up emailing @lj50036 and we went back and forth and had to reflash everything, including custom recovery, TWRP. I think the recovery was messed up.
Finally works again!
Click to expand...
Click to collapse
What happen in android some time, and I may be way off in left field here but, it has happened this way on the tf700, tf300, tf201, and the nexus 10... Just what I have help people with is that....
The storage no matter what command you issue in fastboot e.g
Code:
fastboot erase boot
fastboot erase system
fastboot -w
It just will not erase everything, and by doing these commands your really only telling the tab and or phone that you are going to be putting other
data in those partitions, so if you just flash exactly what was already on the tablet it does not like it...
@spudsmac had upgraded to 4.4.2 and was trying to install cm11 when things went wrong
So by us trying to reset the tablet to factory 4.4.2 firmware it would not take it... Just froze at android guy with x
So when, we went one version older on the firmware... Magic happened and he was golden....
Thx Josh
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.
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!
So I downloaded a 16mb OTA update and let the tablet do its thing without touching it. I waited for the tablet to boot up, but it was stuck in a black screen for about 12 minutes until I decided to turn it off and on. It didn't work, so I went to the recovery to do a factory reset and clear the cache, but it still didn't work. I later went to this Russian forum here from this thread. I downloaded a lollipop rom and proceeded to flash it using Phone Flash Tool Ver. 5.2. It went well until 16% in where it failed. Unfortunately, I don't have a screenshot of 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"
}
(image of the files in the rom I downloaded)
After all this happened, I tried to start it up but I got the message "Boot Failed. EFI Hard Drive. Boot Successful - Enter Setup"
And now it won't go into recovery mode, but it does go into fastboot and bios setup.
Since it does go into fastboot, I tried to use a tool from this thread (Temp recovery) to use a temporary cwm recovery to hopefully be able to at least boot into that, but that didn't end up working.
I got another rom from the same Russian site that had differently packaged files but still the same stock lollipop rom.
I tried to just use the recovery from there to manually flash it using fastboot, but it still failed.
I later found this thread with these instructions for this problem.
1. download and extract this file someplace on your pc
2. uninstall your existing Phone Flash Tool and from the drivers folder install both files (Intel Phone Flash Tool and Android Driver accepting defaults) reboot pc when finished
3. place your tab in DNX mode (from power off press and hold both volume keys then press pwr to start, in a few you screen will show "Fastboot starting..." message and hang on that. you must get that message on your tab screen, restart from power off until you have it)
4. start the installed Phone Flash Tool and load flash.xml from the extracted YT2-830L... folder then Start Flashing, it will reboot when done
Click to expand...
Click to collapse
The file he linked in his post (ionioni ) was gone but I still tried to do this with the roms I had. And guess what? It still didn't work. The instructions said to place the tablet in DNX mode (meaning fastboot), which I did do...only when I put it into fastboot, it was set to DNX_OS which came to say "Wrong device state" in Phone Flash Tool.
I've tried what I could, but failed. Anyone have any suggestions?
AgentXGhost said:
So I downloaded a 16mb OTA update and let the tablet do its thing without touching it. I waited for the tablet to boot up, but it was stuck in a black screen for about 12 minutes until I decided to turn it off and on. It didn't work, so I went to the recovery to do a factory reset and clear the cache, but it still didn't work. I later went to this Russian forum here from this thread. I downloaded a lollipop rom and proceeded to flash it using Phone Flash Tool Ver. 5.2. It went well until 16% in where it failed. Unfortunately, I don't have a screenshot of this.
(image of the files in the rom I downloaded)
After all this happened, I tried to start it up but I got the message "Boot Failed. EFI Hard Drive. Boot Successful - Enter Setup"
And now it won't go into recovery mode, but it does go into fastboot and bios setup.
Since it does go into fastboot, I tried to use a tool from this thread (Temp recovery) to use a temporary cwm recovery to hopefully be able to at least boot into that, but that didn't end up working.
I got another rom from the same Russian site that had differently packaged files but still the same stock lollipop rom.
I tried to just use the recovery from there to manually flash it using fastboot, but it still failed.
I later found this thread with these instructions for this problem.
The file he linked in his post (ionioni ) was gone but I still tried to do this with the roms I had. And guess what? It still didn't work. The instructions said to place the tablet in DNX mode (meaning fastboot), which I did do...only when I put it into fastboot, it was set to DNX_OS which came to say "Wrong device state" in Phone Flash Tool.
I've tried what I could, but failed. Anyone have any suggestions?
Click to expand...
Click to collapse
This is the file you need https://drive.google.com/file/d/0B1LaMEhefCBgYzNTOUxJZmtWQ0E/view
And this https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
Ignore the oops error warning, it's something to do with what G drive can scan.
Holy Sh!t. this just absolutely worked!! I didn't think I could bring this thing back to life, but the files you linked just did it! Really, I don't know how to thank you enough for this.
corasman said:
This is the file you need https://drive.google.com/file/d/0B1LaMEhefCBgYzNTOUxJZmtWQ0E/view
And this https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
Ignore the oops error warning, it's something to do with what G drive can scan.
Click to expand...
Click to collapse
Hi folks,
had the exact same issue and indeed the 1st link offered (https://drive.google.com/file/d/0B1LaMEhefCBgYzNTOUxJZmtWQ0E/view) worked like a charm.
The second link is to download the "Intel platform flash tool lite", but I used my existing version of the Intel Phone Flash Tool (5.2.1-0) which worked fine with the image.
In other words, Corasman, it appears you have saved 2 people's life (or at least tablets) with your solution, so Thanks ! :good:
Regards.
Make that 3 people! Thank you so much corasman - your post has finally fixed my yoga 2 tablet, which I was sure would be going in the bin. Can't overstate how grateful I am - Cheers!
update 830f with 1050f rom?
updating 830f with 1050 rom? does it work?
hello. I have the same problem. I update OTA to lolipop. Since the table is slow, i tried flashing some ROM (which i cannot recall) and the tablet stopped working. Now, I am trying to flash the link you provided and it succeed. However after that i get blank Screen. what Could be wrong. My table is YT2 830LC. Please help
I am typing this all over again after my full report vanished. Do not have the patience of typing all that again. Suffice to say I had a similar situation with the boot failed EFI Hard Drive. Boot Successful - Enter Setup" message on my 830LC.
I had even found the bios restore tool for moving back from lollipop to kitkat but it too would hang. And attempts to flash lollipop would fail immediately with the same message as the OP, wrong device state.
So, in spite of it seeming completely counter-intuitive, I flashed the 1050F rom in the link shared by Corasman. Strange as it may seem, my tablet is now alive and working. No calling function, but it is working and calling itself a 1050F.
Now my research has to shift to whether the 830 LC rom can be flashed now.
i have a same problem with yoga 2 pro 1380f mr corasmancan help me
prabuddhadg said:
I am typing this all over again after my full report vanished. Do not have the patience of typing all that again. Suffice to say I had a similar situation with the boot failed EFI Hard Drive. Boot Successful - Enter Setup" message on my 830LC.
I had even found the bios restore tool for moving back from lollipop to kitkat but it too would hang. And attempts to flash lollipop would fail immediately with the same message as the OP, wrong device state.
So, in spite of it seeming completely counter-intuitive, I flashed the 1050F rom in the link shared by Corasman. Strange as it may seem, my tablet is now alive and working. No calling function, but it is working and calling itself a 1050F.
Now my research has to shift to whether the 830 LC rom can be flashed now.
Click to expand...
Click to collapse
i have same problem with my yoga 830lc this rom not work help me to run my tab agian
---------- Post added at 10:55 AM ---------- Previous post was at 10:47 AM ----------
corasman said:
This is the file you need
And this
Ignore the oops error warning, it's something to do with what G drive can scan.
Click to expand...
Click to collapse
hy sir downlod the rom from google drive but unable to download 2nd link (link not working)
i use latest intel flas tool light but the rom no flash to my device its show errors. plese sir help me to run my tab again