Database Users

[Q] Boots Into "No Command" Screen

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

Need Help! Tablet Stuck and Fastboot Not Working

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.

[Q]Stuck on Google splash

OK, first, I have searched the internet and XDA for help.
Currently, I'm stuck on The black screen with Google. It shows the unlocked Bootloader icon as well. Earlier today I was stuck in a boot with CM boot animation, but that's apparently gone now. I can fastboot, so I'm pretty sure it's recoverable. In TWRP, it says unable to mount /system, /data/ cache/ storage, basically everything. Using NRT i've flashed stock everything, which didn't work, so I tried flashing the kernel, which also didn't work, so I tried the bootloader and system, but they all result in the google splash screen. I am completely out of ideas.
Question: How do i fix it?
Edit: It stayed on the splash screen for at least 4 hours and it wasn't caused by anything I did. No ROM flashes, nothing. It was working then it wasn't.

a.child said:
OK, first, I have searched the internet and XDA for help.
Currently, I'm stuck on The black screen with Google. It shows the unlocked Bootloader icon as well. Earlier today I was stuck in a boot with CM boot animation, but that's apparently gone now. I can fastboot, so I'm pretty sure it's recoverable. In TWRP, it says unable to mount /system, /data/ cache/ storage, basically everything. Using NRT i've flashed stock everything, which didn't work, so I tried flashing the kernel, which also didn't work, so I tried the bootloader and system, but they all result in the google splash screen. I am completely out of ideas.
Question: How do i fix it?
Edit: It stayed on the splash screen for at least 4 hours and it wasn't caused by anything I did. No ROM flashes, nothing. It was working then it wasn't.
Click to expand...
Click to collapse
If you are using NRT, try to flash stock with soft-bricked/Bootloop option.
{
"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"
}
After restore, perform a wipe data/factory reset in stock recovery before booting to android.
Best of luck

joegestes said:
If you are using NRT, try to flash stock with soft-bricked/Bootloop option.
After restore, perform a wipe data/factory reset in stock recovery before booting to android.
Best of luck
Click to expand...
Click to collapse
Thanks for the help, you even edited a screenshot :') haha unfortunately, no luck. But some interesting stuff happens when I do the stock flash.
First time I tried (yesterday), I went through the instructions just how they're listed, I erased all user data and rebooted, still stuck. This time, though, I couldn't get it to boot the stock recovery. Tried pwr+Vol Up like the directions say, but it gets stuck on splash. Tried Pwr+Vol down and I could boot into TWRP which informed me that it was still unable to mount any partitions and that there was no OS installed.
Edit: Looked closer at the command prompt log from the flash and noticed it failed to write any of the images. Sending is OKAY but writing FAILED.

a.child said:
Thanks for the help, you even edited a screenshot :') haha unfortunately, no luck. But some interesting stuff happens when I do the stock flash.
First time I tried (yesterday), I went through the instructions just how they're listed, I erased all user data and rebooted, still stuck. This time, though, I couldn't get it to boot the stock recovery. Tried pwr+Vol Up like the directions say, but it gets stuck on splash. Tried Pwr+Vol down and I could boot into TWRP which informed me that it was still unable to mount any partitions and that there was no OS installed.
Edit: Looked closer at the command prompt log from the flash and noticed it failed to write any of the images. Sending is OKAY but writing FAILED.
Click to expand...
Click to collapse
Hmmm.
Its possible your cable is no good, but it could be something else like a driver issue or charging port failure.
Try using a known good, high quality data cable. Also try connecting to a different USB port on PC.
Just so I understand better.
What version of android did you attempt to flash?
Were you using NRT to flash when the flashing's failed?
Was Force Flash enabled in NRT? .......Try that.
Did you try flashing a different version of STOCK android?
Do you have Android ADB/fastboot installed on PC aside from the one in NRT?
If so, does fastboot detect your phone when running the command "fastboot devices" while in the bootloader?
Is ADB able to detect your phone when running the command "ADB devices" while in TWRP?

I'm at work now, but I'll try new cables and ports when I get home as well as the adb commands.
I was trying to flash 5.0.1 , and was running some CM12 nightly when it failed. To be clear, the ROM was working fine until it wasn't.
I was using NRT and I had force flash selected (recommended settings I think), but I'm not 100% sure post flash factory reset was checked but in the CMD log I did see it wipe and attempt to write userdata.
I have not tried a different version of stock.
I believe ADB is installed outside of NRT abd i have to manually set my path variable to C:/ADB (which screws up normal command prompt, but idk how to fix that) for NRT to work. I have a 2013 nexus 7 and used the same setup to flash PA a while back without any issues.
NRT doesn't detect my phone when displaying the splash screen, but idk about TWRP.

joegestes said:
Hmmm.
Its possible your cable is no good, but it could be something else like a driver issue or charging port failure.
Try using a known good, high quality data cable. Also try connecting to a different USB port on PC.
Just so I understand better.
What version of android did you attempt to flash?
Were you using NRT to flash when the flashing's failed?
Was Force Flash enabled in NRT? .......Try that.
Did you try flashing a different version of STOCK android?
Do you have Android ADB/fastboot installed on PC aside from the one in NRT?
If so, does fastboot detect your phone when running the command "fastboot devices" while in the bootloader?
Is ADB able to detect your phone when running the command "ADB devices" while in TWRP?
Click to expand...
Click to collapse
So the computer does not recognize a fastboot device while in TWRP, but does in the BL.
I attempted to flash 5.0 with the settings mentioned, no luck

a.child said:
So the computer does not recognize a fastboot device while in TWRP, but does in the BL.
I attempted to flash 5.0 with the settings mentioned, no luck
Click to expand...
Click to collapse
If you are absolutely certain your cable is a good one, it is possible you have a driver issue, but I doubt it.
You could try deleting/uninstalling you current ADB driver set and then install the following ADB clockworkmod universal drivers . It might help.
64bit
32bit
If you decide to install the drivers. make sure you select "Android Composite ADB Interface"
after installing the driver set
If that does not help, I am sorry to say, you are likely looking at a hardware failure of the charging port(Dock Connector &Flex Cable)
It looks easy and economical to replace. I found the part here, but you could Google around. I have no experience with the following site.
http://www.repairsuniverse.com/lg-nexus-4-e960-dock-connector-flex-cable-replacement.html
If it were my N4(still great phone), I'd replace the part and attempt to re-flash.
Best of luck.

joegestes said:
If you are absolutely certain your cable is a good one, it is possible you have a driver issue, but I doubt it.
You could try deleting/uninstalling you current ADB driver set and then install the following ADB clockworkmod universal drivers . It might help.
64bit
32bit
If you decide to install the drivers. make sure you select "Android Composite ADB Interface"
after installing the driver set
If that does not help, I am sorry to say, you are likely looking at a hardware failure of the charging port(Dock Connector &Flex Cable)
It looks easy and economical to replace. I found the part here, but you could Google around. I have no experience with the following site.
http://www.repairsuniverse.com/lg-nexus-4-e960-dock-connector-flex-cable-replacement.html
If it were my N4(still great phone), I'd replace the part and attempt to re-flash.
Best of luck.
Click to expand...
Click to collapse
Thanks for the links, I might give it a go.
I bought an original Moto x last night for $100 and I was going to root the potatoes out of it, but who knew non-nexus phones were so difficult to unlock? Damn AT&T....
I sort of suspected it was a hardware issue when I was getting nowhere with NRT, but I wanted confirmation from someone more knowledgeable than me. Any idea on the likelyhood it is something other than the port? The bit that concerns me is that TWRP was unable to mount any partitions, but then again, if i couldn't connect while in TWRP, sort of sounds like a port issue.
oh well...

a.child said:
Thanks for the links, I might give it a go.
I bought an original Moto x last night for $100 and I was going to root the potatoes out of it, but who knew non-nexus phones were so difficult to unlock? Damn AT&T....
Click to expand...
Click to collapse
LOL....That's why I mostly stick with Nexus devices. No carrier garbage, global bands, unlockable and plenty of potatoes:laugh:
a.child said:
Any idea on the likelyhood it is something other than the port?.
Click to expand...
Click to collapse
Could be a bad eMMC but I doubt that. Port failure is more likely to be the issue based on your inability to ADB devices in TWRP.
a.child said:
The bit that concerns me is that TWRP was unable to mount any partitions, but then again, if i couldn't connect while in TWRP, sort of sounds like a port issue
Click to expand...
Click to collapse
Its harder know exactly when using NRT.
That is one reason why, IMO, it is far better to use Fastboot commands to flash instead of relying on toolkit automation.(I do think NRT is the best toolkit)
My guess is NRT sends erase commands to a partition before flash attempts which then failed or sometimes, when a port goes bad,
it is intermittent, a partial flash occurs which would also explain why TWRP can,t mount a particular partition.
For ten bucks delivered on eBay its a no brainier to change out the port. It will probably fix it and if not, you'll have learned something.

joegestes said:
LOL....That's why I mostly stick with Nexus devices. No carrier garbage, global bands, unlockable and plenty of potatoes:laugh:
Could be a bad eMMC but I doubt that. Port failure is more likely to be the issue based on your inability to ADB devices in TWRP.
Its harder know exactly when using NRT.
That is one reason why, IMO, it is far better to use Fastboot commands to flash instead of relying on toolkit automation.(I do think NRT is the best toolkit)
My guess is NRT sends erase commands to a partition before flash attempts which then failed or sometimes, when a port goes bad,
it is intermittent, a partial flash occurs which would also explain why TWRP can,t mount a particular partition.
For ten bucks delivered on eBay its a no brainier to change out the port. It will probably fix it and if not, you'll have learned something.
Click to expand...
Click to collapse
Well i replaced the port and the battery and i'm having the same problem. And I did check to make sure I didn't reinstall the old port.
Guess she's dead :'(

Hmmm... You can connect in fastboot mode, right?
How about re-locking and unlocking the bootloader? It helped me several times...
You'll have to search about how to use fastboot. Connect your phone to your pc while in fastboot mode, and type this into terminal window :
fastboot oem lock
(Press enter)
(bootloader will be locked)
fastboot oem unlock
(Press enter)
(Phone's screen will display sth, use volume keys and power keys to unlock the bootloader)
(It will erase itself)

ddaggebi said:
Hmmm... You can connect in fastboot mode, right?
How about re-locking and unlocking the bootloader? It helped me several times...
You'll have to search about how to use fastboot. Connect your phone to your pc while in fastboot mode, and type this into terminal window :
fastboot oem lock
(Press enter)
(bootloader will be locked)
fastboot oem unlock
(Press enter)
(Phone's screen will display sth, use volume keys and power keys to unlock the bootloader)
(It will erase itself)
Click to expand...
Click to collapse
Thanks for the suggestion, but it didn't work. I was able to lock and unlock the bootloaded again, but it didn't have any effect.

Have you tried flashing Jellybean or kitkat stock rom by fastboot?
If that doesn't work, then the problem is within EMMC. You'll have to let her go...

ddaggebi said:
Have you tried flashing Jellybean or kitkat stock rom by fastboot?
If that doesn't work, then the problem is within EMMC. You'll have to let her go...
Click to expand...
Click to collapse
Looking at other forums, pretty sure the emmc is dead, but I'll try flashing an older version.

Fastboot mode not detected by PC

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 ?

US996 Unlock Problem

I have had my US996 almost a month. Infant mortality period should be past so I tried to unlock bootloader today. I had all the necessary settings enabled and got into Fastboot mode. I entered "fastboot oem device-id' and " waiting for device" stayed on PC screen for 5 minutes until I aborted. I'm sure this isn't normal. I really want to unlock this beauty because I paid $117 more than Verizon charges just so I could. Any suggestions?

If it says waiting for device you phone is not being recognized in fastboot. Verify the fastboot DRIVERS are installed in device manager.

I am obviously missing something here I have verified that the phone has the latest usb driver. I open an administrative command prompt and go to the directory where the 3 downloaded files are. I use the oem cable to connect the phone to my PC. I select either photo or file transfer (tried both several times) and enter "adb bootloader reboot" which reboots the phone into adb mode. I then enter "fastboot oem device-id" and the dos screen says "waiting for any device". IMy previous phone was the LG G3 which was rooted, bootloader unlocked, and running SkyDragon ROM and with heavy modding via Xposed. I'm no developer but I'm not exactly a noobie either. I'm about ready to throw in the towel. Very frustrating! Thanks for your help anyway me2131

The reboot command is "adb reboot bootloader" not "adb bootloader reboot". You can confirm you're in fastboot mode as your phone screen will show the following,
{
"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"
}
If you're sure you're in fastboot, you can check if your computer I registering it by running "fastboot devices"
Code:
C:\Users\XXX\AppData\Local\Android\sdk\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
LGUS996XXX device
C:\Users\XXX\AppData\Local\Android\sdk\platform-tools>adb reboot bootloader
C:\Users\XXX\AppData\Local\Android\sdk\platform-tools>fastboot devices
LGUS996XXX fastboot
If it does not register in "fastboot devices" you're either not in fastboot mode or the drivers aren't installed.

redshorty4 said:
The reboot command is "adb reboot bootloader" not "adb bootloader reboot". You can confirm you're in fastboot mode as your phone screen will show the following,
If you're sure you're in fastboot, you can check if your computer I registering it by running "fastboot devices"
Code:
C:\Users\XXX\AppData\Local\Android\sdk\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
LGUS996XXX device
C:\Users\XXX\AppData\Local\Android\sdk\platform-tools>adb reboot bootloader
C:\Users\XXX\AppData\Local\Android\sdk\platform-tools>fastboot devices
LGUS996XXX fastboot
If it does not register in "fastboot devices" you're either not in fastboot mode or the drivers aren't installed.
Click to expand...
Click to collapse
No devices were seen. when I run "fastboot devices". Also, the PC device manager displays this information in "Events":: Device USB\VID_1004&PID_633E&MI_00\6&7f41b3b&6&0000 requires further installation.
What further installation? I have never run across this cryptic message before. No idea what to do now.

Go over the process again and do a search on XDA for the latest fastboot drivers and install those. I was having problems with the old fastboot and it worked for me after I updated it.

LBJM said:
Go over the process again and do a search on XDA for the latest fastboot drivers and install those. I was having problems with the old fastboot and it worked for me after I updated it.
Click to expand...
Click to collapse
There has been progress but I still cannot get fastboot to work. I am using fastboot.exe dated 11-12-2016 and is the latest I could find. The progress is that, after loading and installing the file "Universal USB Driver" on the PC can now see the device when I enter "adb devices" at the C:\Tools> prompt. It shows LGUS996b******* device. I then enter "adb reboot bootloader" and the phone shows the "Welcome to Fastboot mode for bootloader unlock". But when I enter "fastboot oem device-id" I still get the "Waiting for any device" message and nothing further happens. Sorry, I'm STILL missing something. Thanks for the help so fay to the three responders.

PhoneBull said:
There has been progress but I still cannot get fastboot to work. I am using fastboot.exe dated 11-12-2016 and is the latest I could find. The progress is that, after loading and installing the file "Universal USB Driver" on the PC can now see the device when I enter "adb devices" at the C:\Tools> prompt. It shows LGUS996b******* device. I then enter "adb reboot bootloader" and the phone shows the "Welcome to Fastboot mode for bootloader unlock". But when I enter "fastboot oem device-id" I still get the "Waiting for any device" message and nothing further happens. Sorry, I'm STILL missing something. Thanks for the help so fay to the three responders.
Click to expand...
Click to collapse
I used "fastboot oem unlock" as I only had the V20 attached to the PC and not any android devices.

Has anyone successfully unlocked the US996 using a Windows 10 Pro 64 bit PC?

PhoneBill said:
Has anyone successfully unlocked the US996 using a Windows 10 Pro 64 bit PC?
Click to expand...
Click to collapse
I did it with windows 8.1 x64, just make sure you have adb that supports win 10 and find fastboot drivers for win 10.

I hate to admit it but I am ready to give up. I have tried all the suggestions made here plus many others and cannot get past the "Waiting for any device" message when I try to fastboot. I have used both 3.0 and 2.0 USB ports, have disabled driver signature enforcement in windows, disabled Automatic Download of Drivers from Windows Update and virtually everything else I could find about this problem. I am SO SICK of "Waiting for any device" that I am considering selling the US996 and getting another G3 because last night US99610f was installed on my phone and apparently root has been lost with this ROM version. I thought I had auto updates disabled but all the playing around with settings I have had to do in the past week must have turned it back on. I thank all in this thread who have tried to help me.

PhoneBill said:
I have had my US996 almost a month. Infant mortality period should be past so I tried to unlock bootloader today. I had all the necessary settings enabled and got into Fastboot mode. I entered "fastboot oem device-id' and " waiting for device" stayed on PC screen for 5 minutes until I aborted. I'm sure this isn't normal. I really want to unlock this beauty because I paid $117 more than Verizon charges just so I could. Any suggestions?
Click to expand...
Click to collapse
I'm the OP and am finally unlocked and rooted! It took a lot of searching, deleting stuff from Windows 10 and loading new stuff, and time but I finally succeeded and am happy to report have experienced no problems. The OTA was pushed to my phone 2 days before I succeeded in unlocking so I was on US99610f. So maybe those of you holding off on the OTA for fear of losing root are going to be OK. TWRP and Titanium Backup both fully functional although I don't understand why the SuperSu version I have is 2.79 when I downloaded 3.0.2-1. I am anxiously awaiting Xposed for Nougat and hopefully success someday with mods for enabling the FM radio and Verizon Advanced Calling. Even if none of that happens it's still a beast of a phone.
Edit: OOPS! I DO have TWRP ver. 3.0.2-1 and SuperSu ver. 2.79. I wasn't thinking when I typed the above!

That's good to know. I took the update last week. I'm waiting to root. I'm not confident about being able to go back to stock. Still pretty confused by the methods... and waiting for Xposed.
EDIT
Oh, I wasn't aware Advanced calling is lost once phone is rooted...

advanced calling was lost for me when I upgraded to the F firmware. I had to clear cache and reboot a million times but I also had my friend at Verizon toggle advanced calling on and off to trigger something...and something worked and it wasn't grayed out anymore and was on again. so I don't think it's rooting that does it, but it was the new OTA.
Sent from my LG-US996 using Tapatalk

I had the same problem with fastboot saying "waiting for any device" even though adb was able to list the devices. I finally got "fastboot oem device-id" working with my LG V20 model US966 on Windows 10.
Go into Windows Device manager and find the phone. Right click the phone and choose "Update Driver".
Then "Browse my computer for drivers".
Then "Let me pick from a list of available drivers on my computer"
You may see a single item "Android Device". If so, select that and you will get the option to choose which device driver to load.
Choose "LGE Mobile ADB Interface" and click Next.
You will get a warning that the driver is not recommended. Click "Yes" to use it anyway.
Note that if you do not get an option to install the driver then make sure you have installed the Android Driver (via Google's Android SDK) and the LG Driver.