Develop Bugs

[Toolkit] Wug's Nexus Root Toolkit v2.1.4 [Updated 01/16/16]: Nexus 10 Thread

Unlocking, rooting, relocking and unrooting simplified! (and much more!)
VERSION 2.1.4 - This program will automatically bring together all the files you need to unlock and root your device in a few clicks, or flash it back to stock and re-lock it. You can also use this program to backup/restore all your important data, flash zips, set file permissions, push and pull files, install apps, generate logcats/bugreports, and much more! With the included file association options, you can perform tasks like flashing zips, installing apps, restoring android backup files, and flashing/booting img files with just a double click! The program includes a full featured interface for automating tasks in TWRP, enhanced restore features, an in-built auto-updater/notification system, ‘any build’ mode, advanced restore features,’NRT- Live Log’ for viewing the adb/fastboot cmds that are run in the background, quick tools utilities, and tools for taking screenshots/screen-recordings. All the latest official Android builds and Nexus devices are supported. The program intelligently and selectively downloads the files it needs for your device and makes sure you are using the latest files available. The program can even auto-detect your device and build. This release brings full Marshmallow root support plus all automated features by utilizing a new system that no longer requires modified boot.imgs. Check out the updated changelog for a more comprehensive breakdown of the feature set and changes in this release.
~ my goal for this project is make the entire process as smooth and simple as possible ~
{
"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"
}
Please read the FAQs before posting questions: http://www.wugfresh.com/nrt/faqs/
Looking for a walk-through? >> Excellent Instructional/How-To Videos: http://www.wugfresh.com/videos/
More information & Download Links: http://www.wugfresh.com/nrt/
Changelog: http://www.wugfresh.com/nrt/changelog/
Enjoy! ^_^
{{ WugFresh }}

Wow, this is brilliant, thank you very much.

WugFresh said:
Unlocking, rooting, relocking and unrooting simplified! (and much more!)
~ my goal for this project is make the entire process as smooth and simple as possible ~
{{ WugFresh }}
Click to expand...
Click to collapse
Thanks so much for this! Your toolkit got me started down the road to crack flashing on my Galaxy Nexus, and seeing this version just reinforces my decision to go ahead and order the Nexus 10 (just returned an ASUS TF700T / Infinity).

jonstrong said:
Thanks so much for this! Your toolkit got me started down the road to crack flashing on my Galaxy Nexus, and seeing this version just reinforces my decision to go ahead and order the Nexus 10 (just returned an ASUS TF700T / Infinity).
Click to expand...
Click to collapse
I can't seem to get the samsung drivers included in the toolkit to play nice with the N10 in fastboot mode (won't recognize the device). Any ideas? Do I need to use the pdanet drivers or try a similar universal naked driver?
EDIT: This may be a problem with the toolkit... I installed the drivers that are bundled with the Nexus 10 Toolkit (which show as Nexus 4 ADB drivers), and they show fastboot as recognizing the device, whereas the wug's toolkit fastboot test still doesn't recognize the device or show it as connected....

YES! ,but.. is this the same Toolkit as the one in the N7 section?.. does it get updated w/N10 support or do i have to re-download this one Seperate?.. do i even have to do the Driver guide if i already did it for my N7?.. am super anxious to get the Flashathon on my N10 sorry man haha -
EDIT: nvm,just downloaded the Update for N10 support.. had to go into options and enable "check for updates on boot" or something like that haha My bad dude.. gonna try this sucker out ina minute,Peace out! -

Grandroidster said:
YES! ,but.. is this the same Toolkit as the one in the N7 section?.. does it get updated w/N10 support or do i have to re-download this one Seperate?.. do i even have to do the Driver guide if i already did it for my N7?.. am super anxious to get the Flashathon on my N10 sorry man haha -
Click to expand...
Click to collapse
Yes. It is the same. You only need the one toolkit, it will get updated for all devices. You don't need to configure your drivers again if the toolkit successfully communicates with the device. I would try step 3 of the driver guide 'Test Drivers', if that works feel free to proceed. If you have problems, I recommend driver solution #3 for multiple devices (however #1 or #2 may work for your setup).
{{ WugFresh }}

DagrXDA said:
I can't seem to get the samsung drivers included in the toolkit to play nice with the N10 in fastboot mode (won't recognize the device). Any ideas? Do I need to use the pdanet drivers or try a similar universal naked driver?
EDIT: This may be a problem with the toolkit... I installed the drivers that are bundled with the Nexus 10 Toolkit (which show as Nexus 4 ADB drivers), and they show fastboot as recognizing the device, whereas the wug's toolkit fastboot test still doesn't recognize the device or show it as connected....
Click to expand...
Click to collapse
I included three driver solutions to provide a full range of potential solutions depending on the users setup. I would suggest trying more than one if the first one you try doesn't work. When in doubt, always try driver solution #3.
{{ WugFresh }}

I too am having issues with the driver seeign Fastboot.
I installed NeXus 10 toolkit and it see fastboot no problem.
I go to command line and can issue fastboot commands no problem.
However 1.6.0 refuses to see NeXus10 in fastboot mode.
Uggg..

Gunthermic said:
I too am having issues with the driver seeign Fastboot.
I installed NeXus 10 toolkit and it see fastboot no problem.
I go to command line and can issue fastboot commands no problem.
However 1.6.0 refuses to see NeXus10 in fastboot mode.
Uggg..
Click to expand...
Click to collapse
Adb/fastboot communicate with the drivers, not the toolkit specifically, so what you are describing doesn't make sense. Are you saying that everything worked fine, then you went ahead and tried installing more/different drivers with this toolkit, and now it doesn't work? If that is the case, then it makes sense.. no need to install drivers when you have ones working. You should start over at step one. Uninstall all the drivers, reboot, and try driver solution #3. Cheers.
{{ WugFresh }}

debug
Gunthermic said:
I too am having issues with the driver seeign Fastboot.
I installed NeXus 10 toolkit and it see fastboot no problem.
I go to command line and can issue fastboot commands no problem.
However 1.6.0 refuses to see NeXus10 in fastboot mode.
Uggg..
Click to expand...
Click to collapse
I am having the same problem. I think it's because debug is checked but not functioning. In the ROM I'm running after you check the debug option nothing will happen unless you also select what app to debug. Because I don't know what app to debug, the Toolkit does not recognize it as being debuged and hangs at that point.
For me it's not a driver issue. It fails the full driver test because of my debug problem. What specific app should we apply the debug to?

jmtend said:
I am having the same problem. I think it's because debug is checked but not functioning. In the ROM I'm running after you check the debug option nothing will happen unless you also select what app to debug. Because I don't know what app to debug, the Toolkit does not recognize it as being debuged and hangs at that point.
For me it's not a driver issue. It fails the full driver test because of my debug problem. What specific app should we apply the debug to?
Click to expand...
Click to collapse
Are you referring to the "Android debugging"? That should be under Settings / Developer Options. Scroll down to the "Debugging" section, and simply check "Android debugging" (the subtitle is "Allow Android debug mode, the adb interface on USB (or on network)". You're not actively debugging anything in particular -- simply allowing the activation of debug mode.

WugFresh said:
Adb/fastboot communicate with the drivers, not the toolkit specifically, so what you are describing doesn't make sense. Are you saying that everything worked fine, then you went ahead and tried installing more/different drivers with this toolkit, and now it doesn't work? If that is the case, then it makes sense.. no need to install drivers when you have ones working. You should start over at step one. Uninstall all the drivers, reboot, and try driver solution #3. Cheers.
{{ WugFresh }}
Click to expand...
Click to collapse
I kinda follow. However.
I went to use your toolkit, and it says no fastboot device seen.
I use the other toolkit and it boots to fastboot and functions.
After 1.6.0 said that it see no fastboot device, then i tried your drivers, and it fails.
After tryign to install your drivers, i can still go to other toolkit and/or cmd line and fastboot still works and can issue commands.

Gunthermic said:
I kinda follow. However.
I went to use your toolkit, and it says no fastboot device seen.
I use the other toolkit and it boots to fastboot and functions.
After 1.6.0 said that it see no fastboot device, then i tried your drivers, and it fails.
After tryign to install your drivers, i can still go to other toolkit and/or cmd line and fastboot still works and can issue commands.
Click to expand...
Click to collapse
This is exactly my experience as well. In fact, I was able to fully use the previously posted toolkit to unlock my device, while this one still fails during the fastboot check. If you bring up a command line and look at the fastboot devices, it shows my device... yet it is still failing in the fastboot check in the toolkit. /shrug
In a slightly related note.. since the 4.2.1 update is pushing out OTA... will JUST an unlocked bootloader on this device prevent OTA's? (I usually would expect to still get OTA's, especially if still running the stock bootloader (which I am... I have not flashed TWRP / CWM yet, and have not yet rooted).

answer
jonstrong said:
Are you referring to the "Android debugging"? That should be under Settings / Developer Options. Scroll down to the "Debugging" section, and simply check "Android debugging" (the subtitle is "Allow Android debug mode, the adb interface on USB (or on network)". You're not actively debugging anything in particular -- simply allowing the activation of debug mode.
Click to expand...
Click to collapse
Yes I have debuging checked however, I don't think anything is debuged until you go further down the menu and it ask's what app to debug. I think in the factory ROM once you check debug everything is debuged. In my custom ROM you must also select what you want debug to apply to. If you do not select the correct one the Toolkit assumes you are not debuged.

jmtend said:
Yes I have debuging checked however, I don't think anything is debuged until you go further down the menu and it ask's what app to debug. I think in the factory ROM once you check debug everything is debuged. In my custom ROM you must also select what you want debug to apply to. If you do not select the correct one the Toolkit assumes you are not debuged.
Click to expand...
Click to collapse
I've got the same option as well ("Select debug app") - also shows "No debug application set". Never been an issue...

answer
jonstrong said:
I've got the same option as well ("Select debug app") - also shows "No debug application set". Never been an issue...
Click to expand...
Click to collapse
Debug then must not be the cause of my problem it then must be a driver issue. I have tried all three driver options and all three seamed to install correctly. I don't know what else to try. If it's of interest my ROM is ParanoidAndroid v 2.99.3 and the build number is pa_manta-userdebug 4.2 JOP40C eng.block.20121125.113032 test-keys

Gunthermic said:
I kinda follow. However.
I went to use your toolkit, and it says no fastboot device seen.
I use the other toolkit and it boots to fastboot and functions.
After 1.6.0 said that it see no fastboot device, then i tried your drivers, and it fails.
After tryign to install your drivers, i can still go to other toolkit and/or cmd line and fastboot still works and can issue commands.
Click to expand...
Click to collapse
Please try what I suggested. Fully uninstalling ALL adb/fastboot drivers (step 1 of driver guide).. Rebooting your computer like it says (essential step), then reinstalling the drivers (solution #3), then trying the driver test. Also, please try rebooting your computer before using this toolkit if you were using a different one before, or try force closing any background instances of adb.exe/fastboot.exe. Like I said, drivers are associated with those processes, not the toolkit. If the you had drivers working correctly with adb.exe or fastboot.exe then they will work. Chances are something else is causing your problem.
That said, I noticed that 1wayjonny released newer universal drivers then the ones in this release, I will push an update out with those. But the signed google drivers which are included in driver solution #3 are all you need.
If you are still experiencing problems hit me up on gchat and we will see if we can get it resolved.
{{ WugFresh }}

I have the same problem.
Fastboot device is not recognized in the GUI but if I run fastboot.exe from your installation it recognizes the device i.e. the correct driver is installed.

Johan1976 said:
I have the same problem.
Fastboot device is not recognized in the GUI but if I run fastboot.exe from your installation it recognizes the device i.e. the correct driver is installed.
Click to expand...
Click to collapse
To clarify, when your device is in bootloader mode, connected via usb - and you use the toolkits list devices (fastboot) in quick tools, what happens?
{{ WugFresh }}

I think it says something about failed fastboot connection. I'll check tomorrow. Anyway i'm unlocked now which was essential from start since that wipes the tablet. Now i'm prepared for root later on.
Skickat från min Nexus 10 via Tapatalk 2

[Q] I Did the impossible! - Galaxy Nexus fully bricked

Hello everyone!
I have fully bricked my phone (at least, I am unable to repair it). So I hope there is someone who could help me restore my Galaxy Nexus to a working state again.
Story:
I wanted to flash a new custom ROM and a whole new clean phone. So I decided to wipe everything. I wiped all /sdcard, /system, /cache and /data with ClockWorkMod (recovery mode). Now it looks like I do not have any OS on the device at all and the device would not boot past the 'Google' logo and the 'unlocked' padlock symbol. Connecting the device to the computer is also not working (cannot recognize the device, even with the drivers installed manually). So my conclusion, I bricked my Galaxy Nexus.
Facts:
1) Wiped all /sdcard, /system, /cache and /data. So the phone is emptier than there is dirt in a hole that is 6 feet by 6 feet by 4 feet.
2) Cannot boot past the 'Google' logo and the 'unlocked' padlock, it gets stuck there
3) Rooted
4) Can get in Download (Odin) mode
5) Can get in Recovery (CWM) mode
6) Can get in Fastboot mode
7) None of the computers of laptops would recognize the device
8) Can not access the device or sdcard with a computer
Tried:
1) Universal Naked Driver
2) ADB push the files
3) Odin to restore to factory settings (Odin cannot see the device)
4) Send for repairs to Samsung (denied because of water damage , the device was working just fine before the wipe..)
5) Kies for the drivers
6) Galaxy Nexus ToolKit
None of the things I tried has worked.
I hope there is someone who could help me. I would buy that person a cup of coffee
Thanks in advance!

iKaosTony said:
Hello everyone!
I have fully bricked my phone (at least, I am unable to repair it). So I hope there is someone who could help me restore my Galaxy Nexus to a working state again.
Story:
I wanted to flash a new custom ROM and a whole new clean phone. So I decided to wipe everything. I wiped all /sdcard, /system, /cache and /data with ClockWorkMod (recovery mode). Now it looks like I do not have any OS on the device at all and the device would not boot past the 'Google' logo and the 'unlocked' padlock symbol. Connecting the device to the computer is also not working (cannot recognize the device, even with the drivers installed manually). So my conclusion, I bricked my Galaxy Nexus.
Facts:
1) Wiped all /sdcard, /system, /cache and /data. So the phone is emptier than there is dirt in a hole that is 6 feet by 6 feet by 4 feet.
2) Cannot boot past the 'Google' logo and the 'unlocked' padlock, it gets stuck there
3) Rooted
4) Can get in Download (Odin) mode
5) Can get in Recovery (CWM) mode
6) Can get in Fastboot mode
7) None of the computers of laptops would recognize the device
8) Can not access the device or sdcard with a computer
Tried:
1) Universal Naked Driver
2) ADB push the files
3) Odin to restore to factory settings (Odin cannot see the device)
4) Send for repairs to Samsung (denied because of water damage , the device was working just fine before the wipe..)
5) Kies for the drivers
6) Galaxy Nexus ToolKit
None of the things I tried has worked.
I hope there is someone who could help me. I would buy that person a cup of coffee
Thanks in advance!
Click to expand...
Click to collapse
From what I can see in your explanation, it won't boot up because you wiped your old rom (system) and did not flash a new one before you tried to boot up. If you can boot into recovery you are not bricked. Perhaps you still have a downloaded rom on there. Full wipe (at least with TWRP) Doesn't usually wipe that partition nor your Nandroids. So you should be able to flash a rom or a restore from recovery. If that fails, get Wugs Tool kit and carefully follow the instructions, especially about driver installation. After that, Wugs should see your Nex in adb and fastboot and you can put rom on from there.
Odin useless on Gnex & Kies is dicey at best.
Sent from my Hyperdriven Vzw Dev Edition Galaxy S4 with Tapatalk 4

supposing that there is no issue with driver
hmmmm water damage?
did you try to clean micro usb port from rust or dust, or see if there is a pin needs bending?

wtherrell said:
From what I can see in your explanation, it won't boot up because you wiped your old rom (system) and did not flash a new one before you tried to boot up. If you can boot into recovery you are not bricked. Perhaps you still have a downloaded rom on there. Full wipe (at least with TWRP) Doesn't usually wipe that partition nor your Nandroids. So you should be able to flash a rom or a restore from recovery. If that fails, get Wugs Tool kit and carefully follow the instructions, especially about driver installation. After that, Wugs should see your Nex in adb and fastboot and you can put rom on from there.
Odin useless on Gnex & Kies is dicey at best.
Sent from my Hyperdriven Vzw Dev Edition Galaxy S4 with Tapatalk 4
Click to expand...
Click to collapse
no... just no.
dont ever recommend a toolkit.
OP,
your problem is the phone isnt bricked. you just do not have a system for the phone to boot into. if it was bricked it would not turn on and you could not get into fastboot.
you need to fix your drivers.
follow this: http://forum.xda-developers.com/showthread.php?t=1626895
it has steps for drivers, etc.

wtherrell said:
From what I can see in your explanation, it won't boot up because you wiped your old rom (system) and did not flash a new one before you tried to boot up. If you can boot into recovery you are not bricked. Perhaps you still have a downloaded rom on there. Full wipe (at least with TWRP) Doesn't usually wipe that partition nor your Nandroids. So you should be able to flash a rom or a restore from recovery. If that fails, get Wugs Tool kit and carefully follow the instructions, especially about driver installation. After that, Wugs should see your Nex in adb and fastboot and you can put rom on from there.
Odin useless on Gnex & Kies is dicey at best.
Sent from my Hyperdriven Vzw Dev Edition Galaxy S4 with Tapatalk 4
Click to expand...
Click to collapse
Thank you for your fast reply.
That is about right. When I go in CWM and try 'install zip' -> 'choose zip from sdcard', I get 2 folders. The first one is called '0/' and the other is called 'clockworkmod/' both of them are empty. So I guess there are no files on my device anymore.
I will try Wugs Toolkit. I will keep you updated.

samersh72 said:
supposing that there is no issue with driver
hmmmm water damage?
did you try to clean micro usb port from rust or dust, or see if there is a pin needs bending?
Click to expand...
Click to collapse
Yeah, really strange. I have never dropped it in water or let it get in contact with water.
But because of that reason they will not accept it for repairs and I have to deal with it myself.
I have checked the port for dust and pins for bending, nothing wrong with them.
Zepius said:
no... just no.
dont ever recommend a toolkit.
OP,
your problem is the phone isnt bricked. you just do not have a system for the phone to boot into. if it was bricked it would not turn on and you could not get into fastboot.
you need to fix your drivers.
follow this: http://forum.xda-developers.com/showthread.php?t=1626895
it has steps for drivers, etc.
Click to expand...
Click to collapse
I just tried Wugs Toolkit without success.
{
"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 just tried the Universal Naked Driver guide from bourne-nolonger here http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
But I cannot get the window that says 'Windows can't verify the publisher of this driver software' with the button 'Install this driver software anyway'. That is step 3E and 3F. It just skips that and say Unknown Device.
Could it be my USB port being broken? That the reason no computer would recognize it because of that?

iKaosTony said:
Yeah, really strange. I have never dropped it in water or let it get in contact with water.
But because of that reason they will not accept it for repairs and I have to deal with it myself.
I have checked the port for dust and pins for bending, nothing wrong with them.
I just tried Wugs Toolkit without success.
I just tried the Universal Naked Driver guide from bourne-nolonger here http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
But I cannot get the window that says 'Windows can't verify the publisher of this driver software' with the button 'Install this driver software anyway'. That is step 3E and 3F. It just skips that and say Unknown Device.
Could it be my USB port being broken? That the reason no computer would recognize it because of that?
Click to expand...
Click to collapse
You would have been in a very bad luck if your usb port died spontaneously at the same time you fully wiped your device....
Did you check another cable, often is the easiest solution which is overseen...

19Max87 said:
You would have been in a very bad luck if your usb port died spontaneously at the same time you fully wiped your device....
Did you check another cable, often is the easiest solution which is overseen...
Click to expand...
Click to collapse
I did tried using other cables, 2 from other Samsung devices, 1 cheap one and a cable from another Galaxy Nexus.
So I tried it on a computer with all the drivers working from another Galaxy Nexus.
Maybe bring it to a repairstore?

iKaosTony said:
I did tried using other cables, 2 from other Samsung devices, 1 cheap one and a cable from another Galaxy Nexus.
So I tried it on a computer with all the drivers working from another Galaxy Nexus.
Maybe bring it to a repairstore?
Click to expand...
Click to collapse
OK, you installed all the drivers, but did you delete every driver before you installed the new one.
I would try to delete every nexus driver from your computer and start from the very beginning. As the others said, your phone is not bricked and sometimes the drivers just want to fùck brains....
I'm sure you will find the solution, wish you the best of luck... :thumbup:

19Max87 said:
OK, you installed all the drivers, but did you delete every driver before you installed the new one.
I would try to delete every nexus driver from your computer and start from the very beginning. As the others said, your phone is not bricked and sometimes the drivers just want to fùck brains....
I'm sure you will find the solution, wish you the best of luck... :thumbup:
Click to expand...
Click to collapse
Yes, I have tried deleting and uninstalling every driver or software related to my device or any mobile device. Also I used this to make sure I have got rid of everything

iKaosTony said:
Yes, I have tried deleting and uninstalling every driver or software related to my device or any mobile device. Also I used this to make sure I have got rid of everything
Click to expand...
Click to collapse
Sorry bro, I'm out of ideas... :banghead:

Boot into an Ubuntu live USB. It doesn't require drivers. Just install the adb and fastboot tools from apt-get. There are about 50,000 tutorials on how.
Sent from my Galaxy Nexus

Try an other cable or computer or USB port.. Go to a friend if you must.. Then flash the Factory image via fastboot..
Sent from my Galaxy Nexus using XDA Premium HD app

I have tried using Ubuntu to access my device, but no luck either. When I come to the step where I have to use the command 'lsusb' does not show up. I have tried putting my device in Download mode, Fastboot mode and Recovery mode to see if 'lsusb' will show my device.
The tutorials I followed:
http://rootzwiki.com/topic/20770-gu...-adb-and-fastboot-in-linux-ubuntu-and-mint12/
http://www.youtube.com/watch?v=3heTSqjWcaY
http://bernaerts.dyndns.org/linux/245-ubuntu-precise-install-android-sdk
Tried 4 different cables, 3 different computers and a friends computer where all the drivers are working with his Galaxy Nexus.
I do not know what I am doing wrong. :crying:

in recovery mode execute "adb push rom.zip /sdcard/", better from Ubuntu so you don't need any driver
Then flash the rom from the recovery
Inviato dal mio Galaxy Nexus con Tapatalk 2

If neither lsusb shows the device connected nor there's any event under kernel logs that point to the device.. Is the USB port really working?
Sent from my maguro

do you have cwm or twrp? try mounting your device as usb while connected to pc
Sent from my Galaxy Nexus using xda app-developers app

beekay201 said:
If neither lsusb shows the device connected nor there's any event under kernel logs that point to the device.. Is the USB port really working?
Sent from my maguro
Click to expand...
Click to collapse
I am also thinking my USB port is broken...
unmystic said:
do you have cwm or twrp? try mounting your device as usb while connected to pc
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I have CWM. How do I do that?

In Device Manager can you right-click Unknown Device to view its properties?
You should be able to update the device driver there.

stevemw said:
In Device Manager can you right-click Unknown Device to view its properties?
You should be able to update the device driver there.
Click to expand...
Click to collapse
I tried that too, but no luck.

M8 Not recognized by my pc fastboot mode

hello everyone: D
*
I would like to install the rom lollipop but I have to first install a recovery ...
*
For this I have to go and do a fastboot command but this is where it stops: s
*
It makes me that
*
{
"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"
}
*
Yet I installed the drivers 2 times (and reboot the pc), I use the usb cable I originally tried several USB ports and when it is on, it is recognized ..
*
What to do?
*
thank you​

Let's try the obvious...
USB 3.0 vs USB 2.0 ports and, not saying you're stupid or anything but your device is actually in bootloader mode yes? adb reboot bootloader <<< I assume you manually booted into bootloader mode on the phone hence why you didn't use that command in the screenshot? The command won't work from within the running OS it needs to be in bootloader mode.
Of course it should say in fastboot mode that the USB is connected.
Another solution for the drivers that seem to work is to uninstall all the HTC drivers and HTC Sync. Connect the device to the computer, cancel/close the prompt to install drivers. Got to Device Manager, find the device and select the option to manually select drivers thenpick the Generic MTP Android device drivers. @redpoint73 usually recommends this for device driver issues, seems to work out most of the time.

Thank you for your reply! I uninstalled the drivers etc as you say
For cons, I do not really understand the beginning of your paragraph
To get in fastboot mode, I switch off the mobile, then I turned still pressing volume down and power at the same time and press fastboot
My bootloader is unlocked if that's what you want to know
I confess I'm a bit noob with Roma with HTC and I have a little trouble with English (I use an internet translator)

nobody?

BerndM14 said:
Another solution for the drivers that seem to work is to uninstall all the HTC drivers and HTC Sync. Connect the device to the computer, cancel/close the prompt to install drivers. Got to Device Manager, find the device and select the option to manually select drivers thenpick the Generic MTP Android device drivers. @redpoint73 usually recommends this for device driver issues, seems to work out most of the time.
Click to expand...
Click to collapse
I'm not sure about "most of the time" but it worked for me, and some other folks I've given this step to.
OP hasn't stated whether he tried this or not.
Other possible solutions are to try different USB ports or even another PC (he stated that other USB cables were already attempted); re-install HTC Sync; and verify whether the ports are USB 3.0 (which often does not play well with this device).

I had the same problem and couldn't find a solution Its a combination issue of Windows 8.x and USB 3.0 drivers. I tore my hair out trying to fix it and gave up, I just do my Android tinkering on a Windows 7 PC now.
fabidesca said:
hello everyone: D
*
I would like to install the rom lollipop but I have to first install a recovery ...
*
For this I have to go and do a fastboot command but this is where it stops: s
*
It makes me that
*
*
Yet I installed the drivers 2 times (and reboot the pc), I use the usb cable I originally tried several USB ports and when it is on, it is recognized ..
*
What to do?
*
thank you​
Click to expand...
Click to collapse

redpoint73 said:
I'm not sure about "most of the time" but it worked for me, and some other folks I've given this step to.
OP hasn't stated whether he tried this or not.
Other possible solutions are to try different USB ports or even another PC (he stated that other USB cables were already attempted); re-install HTC Sync; and verify whether the ports are USB 3.0 (which often does not play well with this device).
Click to expand...
Click to collapse
Yeah I also saw it working for some of the members you advised to do this...If 10 guys followed it and it succeeded for 6 of them then it's surely "most of them" Won't know about those that don't report back...

I am having the same problem. It all worked fine with my Turbo. Odd it is not working for me now. I am on Windows 10.

Everything works for me on win10 and M8. Strange issue imo

xunholyx said:
Everything works for me on win10 and M8. Strange issue imo
Click to expand...
Click to collapse
I can confirm that
No issues on win 10
Sent from my HTC M8 using XDA Labs

xunholyx said:
Everything works for me on win10 and M8. Strange issue imo
Click to expand...
Click to collapse
ahmed.ismael said:
I can confirm that
No issues on win 10
Click to expand...
Click to collapse
It was before, I fixed it with a reg file (still have it dated Oct 28, 2014 )
... now with updated HTC USB drivers and also microsoft updated drivers, no more problem, no need any fix.

xunholyx said:
Everything works for me on win10 and M8. Strange issue imo
Click to expand...
Click to collapse
ckpv5 explained it. But I don't find it so strange (for it to work for one person, and not another). Consider the endless combinations of possible PC hardware, plus differences in software, such as the mentioned updated Windows drivers which may or may not be installed. USB 3.0 (versus 2.0) alone has cause a lot of folks trouble with getting fastboot/RUU to work on the M8.
Point in case, fastboot and adb have always worked fine with this phone on my work laptop. But on my home desktop PC, I often have to manually select generic MTP drivers to get adb to work. Both run Win7.

I will try my wife's HTC cable.i used the Motorola cable.

hello,
i use htc desire 820 dual sim , my phone is not recognized in the fastboot usb mode. can you please help me out?
A51_DTUL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-01.01.010_U10305041_08.01.51015
OS-
eMMC-boot2048MB

hanubhargava said:
hello,
i use htc desire 820 dual sim , my phone is not recognized in the fastboot usb mode. can you please help me out?
A51_DTUL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-01.01.010_U10305041_08.01.51015
OS-
eMMC-boot2048MB
Click to expand...
Click to collapse
Re-install HTC Sync, try a different USB port, a different cable.
Also, on the PC (assuming Windows) one thing that works for me, is that I have to go into Device Manager, find the phone, and pick the option to manually select a driver, then select the generic "Android MTP device" (or some name like that - can't remember exactly). This method may or may not work. I have to sometimes do it on my home PC to see my phone on fastboot/adb, but don't need to do this on my work laptop PC. Its not consistent.
Other than that (general fastboot tips for HTC devices), I can't offer much more advice. This is the M8 device forum, and I have no experience with your specific device.

No OS, OTG not recognized. Am I bricked?

Accidental full wipe of my Nexus 7 has left me with a no OS paper weight.
Fastboot indicates it's locked but I can boot into TWRP, but can't get it to be recognized by any PC and it won't recognize my OTG-USB (which has been recognized by others).
Any ideas as to how to get her up and running would be greatly appreciated.
{
"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"
}

Did you mount the OTG usb in TWRP or just looked for it to auto detect?
Btw, this belongs in the Q & A section, so ask a mod to move it

I am unable to select/check mount the OTG while in TWRP. The OTG is formatted correctly as the OTG is readable on other devices, but it seems like it just isn't being found by the N7. I'm baffled.

Check this thread: http://forum.xda-developers.com/showthread.php?t=3064562

Tried it on a full battery, still no luck.

tried to get it to work, any suggestions fellow XDAers? I'm in a real jam here

Check this thread: http://forum.xda-developers.com/show....php?t=3064562
Click to expand...
Click to collapse
Thanks, but I can't get the tablet to be recognized. I've tried it in multiple windows computers with both USB 2 and 3.

Have you tried adb/fastboot?

Have you tried adb/fastboot?
Click to expand...
Click to collapse
I am able to fastboot, but still can't get the pc to recognize that it's connected. The tablet takes a charge, but the pc never acknowledges that a device is connected, device manager never indicates a device is connected.

-If you don't have any Roms on internal storage, that's no good since you have TWRP.
-Try A different USB cable.
-Definitly make sure you have installed Google USB drivers.
-Have you tried ADB Sideload in twrp? Maybe TWRPs' adb will work better.
It looks like you need to update your bootloader as well, go with the latest factory images.
If you need to know where to find the above things I can point you to them. You must eventually get the PC to recognise it in fastboot though.

CrazyJ36 said:
-If you don't have any Roms on internal storage, that's no good since you have TWRP.
-Try A different USB cable.
-Definitly make sure you have installed Google USB drivers.
-Have you tried ADB Sideload in twrp? Maybe TWRPs' adb will work better.
It looks like you need to update your bootloader as well, go with the latest factory images.
If you need to know where to find the above things I can point you to them. You must eventually get the PC to recognise it in fastboot though.
Click to expand...
Click to collapse
Thanks. Everything hinges on the PC being able to recognize that I'm attempting to connect the tablet (or for the tablet to recognize that I've attached the OTG).
I have tried multiple USB cables and ensured that the drivers are installed on the multiple PCs I've attached to.
I have tried to ADB sideload in TWRP, but since none of the PCs recognize that the tablet is connected to the PC, ADB won't work.
Again, it's not that the drivers are not installed, but rather the PC not recognizing that I have attached a device through the USB (no sound, no pop-up, nothing in the device manager). It is extremely frustrating, especially since the device charges via the USB from the PC.

DorianX said:
Check this thread: http://forum.xda-developers.com/showthread.php?t=3064562
Click to expand...
Click to collapse
CrazyJ36 said:
Have you tried adb/fastboot?
Click to expand...
Click to collapse
Still no luck, any other recommendations?

Device Manager doesn't even show something like "qualcomm_qloader"? That's seems worse than any other hard brick I've seen.
-OTG should be FAT32 formated (probably is).
-We're you using Lollipop with that 4.02 bootloader? I believe that was A prerequisite for installing Lollipop which may have cause the tablet to not show on the PC.
- Nexus Root Toolkit has different methods for installing drivers http://www.wugfresh.com/faqs/
-Found this thread http://forum.xda-developers.com/showthread.php?t=2404297&page=1
Shows holding power for A minute got theres' to start doing stuff. It' A different recovery issue though.
Hate to be A downer, I hard bricked A galaxy s4 I had for only 5 days last month. That never turned on again. It's not fun.

I had the same issue. The only way I could fix was a full adb restore. I tried several other ways and none worked.
sent from my Hyperdrive powered G Note 10.1

CrazyJ36 said:
Device Manager doesn't even show something like "qualcomm_qloader"? That's seems worse than any other hard brick I've seen.
-OTG should be FAT32 formated (probably is).
-We're you using Lollipop with that 4.02 bootloader? I believe that was A prerequisite for installing Lollipop which may have cause the tablet to not show on the PC.
- Nexus Root Toolkit has different methods for installing drivers http://www.wugfresh.com/faqs/
-Found this thread http://forum.xda-developers.com/showthread.php?t=2404297&page=1
Shows holding power for A minute got theres' to start doing stuff. It' A different recovery issue though.
Hate to be A downer, I hard bricked A galaxy s4 I had for only 5 days last month. That never turned on again. It's not fun.
Click to expand...
Click to collapse
Nothing shows in the device manager. I was using KitKat on the tablet.
Turns on without an issue, opens TWRP with no issue.
when connected to the PC nothing occurs, not when it's on the Google screen, not when it's in TWRP, not in Fastboot, not when it's restarting. Nothing.
if it was the driver being missing, I'd at least see the device attached, just not communicating properly
sorry to hear about your GS4

The Apostle said:
I had the same issue. The only way I could fix was a full adb restore. I tried several other ways and none worked.
sent from my Hyperdrive powered G Note 10.1
Click to expand...
Click to collapse
if you truly had the same exact problem, how were you able to use ADB if your device wasn't recognized on a PC or OTG?

Welp, that would be my fault for not completely reading. My apologies.
sent from my Hyperdrive powered G Note 10.1

The Apostle said:
Welp, that would be my fault for not completely reading. My apologies.
sent from my Hyperdrive powered G Note 10.1
Click to expand...
Click to collapse
it's alright, thanks for the thought.
I'm just hoping since I can get into TWRP someone has an idea of how I can get it to recognize the OTG or the PC to see it and I can get into ADB.

Corrupted usb port on the tablet? Maybe broken pin. Try to examine it. It can happen that it is being charged but not identified by the pc because of a faulty port. Try live install of ubuntu to chech if it sees the device.

zandgreen said:
Corrupted usb port on the tablet? Maybe broken pin. Try to examine it. It can happen that it is being charged but not identified by the pc because of a faulty port. Try live install of ubuntu to chech if it sees the device.
Click to expand...
Click to collapse
the port looks perfectly fine, I was thinking the same thing, but there doesn't seem to be any damage. I almost wish it was damaged so I could at least assume that's the problem and just trash the thing.

Moto G5 does not connect to the PC in any way!

So, after upgrading to Android 8.1 OPP28-85-13 . somehow I could not upgrade to version OPP28-85-16 (OFFICIAL VERSION) and so I tried to update the computer, but the same did not recognizes the cell phone.
I already installed the drivers of the motorola 5x, I changed PC, cable, I activated USB debugging, I already changed that MTP option and nothing! The cell phone does not live on the PC, the only thing that happens is that it carries, nothing else! Does anyone have a solution to this? I'm stuck in a version that still has bugs and I can not update anymore ... I've tried everything!
Excuse my English, I'm from Brazil and I can not find anyone here to solve this.

Assuming you did find the correct OTA to go from OPP28-85-13 to OPP28-85-16, you'd have to go to fastboot, and I doubt those options matter then. Also if you didn't sign up for soak test you wouldn't be able to go from a soak to official version through OTA. Check if your PC recognizes your phone in fastboot.

Hyoretsu said:
Assuming you did find the correct OTA to go from OPP28-85-13 to OPP28-85-16, you'd have to go to fastboot, and I doubt those options matter then. Also if you didn't sign up for soak test you wouldn't be able to go from a soak to official version through OTA. Check if your PC recognizes your phone in fastboot.
Click to expand...
Click to collapse
it does not work in fastboot mode, in fact it is as if the cell phone was dead, it stopped working on the computer, it only loads, I already installed drivers, everything ... but no use, I already tried to use rsd lite but it does not recognize!

Kinda dumb but you're using fastboot command right? Last time that happened to me I was using adb devices and it never showed up

Hyoretsu said:
Kinda dumb but you're using fastboot command right? Last time that happened to me I was using adb devices and it never showed up
Click to expand...
Click to collapse
to recognize in fastboot mode, the cell phone does not need to be recognized on the pc first? I connect the USB cable and it's the same as nothing, besides that, debugging usb also does not work to proceed in fastboot

Nope. If it's in fastboot, it won't get recognized as an actual device, you'll just hear the plugging sound and be able to interact with it via commands

Hyoretsu said:
Nope. If it's in fastboot, it won't get recognized as an actual device, you'll just hear the plugging sound and be able to interact with it via commands
Click to expand...
Click to collapse
{
"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"
}
Does not recognize, neither in fastboot nor in normal mode

@kolple
Hey I know you said you installed drivers and all.. But maybe you should uninstall them and try again. This really sounds like a driver problem honestly.
You could try looking up for UsbDeview on google. It's a pc app which lets you see installed devices.. You could uninstall everything related to your Moto g5.. Then reinstall official Motorola drivers.

Chekm8Qc said:
@kolple
Hey I know you said you installed drivers and all.. But maybe you should uninstall them and try again. This really sounds like a driver problem honestly.
You could try looking up for UsbDeview on google. It's a pc app which lets you see installed devices.. You could uninstall everything related to your Moto g5.. Then reinstall official Motorola drivers.
Click to expand...
Click to collapse
I already tested it on other computers, and the same thing happens, does not install anything, nor does the device manager appear. It is as if the cell phone was no longer receiving data through the cable ... I do not know, it could be an android bug or the faulty usb port, some solution to that?

kolple said:
I already tested it on other computers, and the same thing happens, does not install anything, nor does the device manager appear. It is as if the cell phone was no longer receiving data through the cable ... I do not know, it could be an android bug or the faulty usb port, some solution to that?
Click to expand...
Click to collapse
This is odd for sure. I wish I could help more honestly. Trying USB 2.0 or 3.0 ports doesn't change anything right? Probably not.

kolple said:
Does not recognize, neither in fastboot nor in normal mode
Click to expand...
Click to collapse
I would say update your adb/fastboot
I never use minimal adb/fastboot but always the package that comes with the full android sdk
Also try a different USB cable
And you can try cmd as admin instead of the windows power shell not that it should make a difference

kolple said:
So, after upgrading to Android 8.1 OPP28-85-13 . somehow I could not upgrade to version OPP28-85-16 (OFFICIAL VERSION) and so I tried to update the computer, but the same did not recognizes the cell phone.
I already installed the drivers of the motorola 5x, I changed PC, cable, I activated USB debugging, I already changed that MTP option and nothing! The cell phone does not live on the PC, the only thing that happens is that it carries, nothing else! Does anyone have a solution to this? I'm stuck in a version that still has bugs and I can not update anymore ... I've tried everything!
Excuse my English, I'm from Brazil and I can not find anyone here to solve this.
Click to expand...
Click to collapse
Try using Moto lenovo smart assistant it will flash the latest firmware.

riyan65 said:
Try using Moto lenovo smart assistant it will flash the latest firmware.
Click to expand...
Click to collapse
Really? I didn't even know that.

riyan65 said:
Try using Moto lenovo smart assistant it will flash the latest firmware.
Click to expand...
Click to collapse
No application that will connect USB will not work, nor with debugging, no use! My salvation would be if there was an application that does these methods over wifi.

kolple said:
No application that will connect USB will not work, nor with debugging, no use! My salvation would be if there was an application that does these methods over wifi.
Click to expand...
Click to collapse
Man this is so weird.. In your screenshot the bootloader screen actually detects the phone being connected to usb.

Chekm8Qc said:
Man this is so weird.. In your screenshot the bootloader screen actually detects the phone being connected to usb.
Click to expand...
Click to collapse
Exactly! But it does not recognize on the system, on any computer. In fastboot it appears that it recognized, but without signal ... With the cellphone turned on normal, also nothing appears in the computer, even with usb debugging

kolple said:
Exactly! But it does not recognize on the system, on any computer. In fastboot it appears that it recognized, but without signal ... With the cellphone turned on normal, also nothing appears in the computer, even with usb debugging
Click to expand...
Click to collapse
Have you tried in device manager to scan for hardware changes when the phone is connected? And of course you selected mtp right? Have you selected mtp in developer options? You should try to revoke USB debugging authorizations ( right under USB debugging) this will reset the adb permission you first allowed. You should get prompt for permission again when you type adb devices under cmd ( if phone is seen by pc)
When you check your installed programs on pc do you have other USB drivers installed at the same time as the Motorola ones? If so that might cause some issues.

Chekm8Qc said:
Have you tried in device manager to scan for hardware changes when the phone is connected? And of course you selected mtp right? Have you selected mtp in developer options? You should try to revoke USB debugging authorizations ( right under USB debugging) this will reset the adb permission you first allowed. You should get prompt for permission again when you type adb devices under cmd ( if phone is seen by pc)
When you check your installed programs on pc do you have other USB drivers installed at the same time as the Motorola ones? If so that might cause some issues.
Click to expand...
Click to collapse
I've already changed all these options, I already installed and reinstalled the motorola drivers and nothing works for me

kolple said:
I've already changed all these options, I already installed and reinstalled the motorola drivers and nothing works for me
Click to expand...
Click to collapse
There seems to be quite a few cases like yours if you Google the problem.
Mind looking at this to start with?
https://www.google.ca/amp/s/forum.x...p-problems-8-1-official-windows-t3715171/amp/

Chekm8Qc said:
There seems to be quite a few cases like yours if you Google the problem.
Mind looking at this to start with?
https://www.google.ca/amp/s/forum.x...p-problems-8-1-official-windows-t3715171/amp/
Click to expand...
Click to collapse
did not work, even changing the options MPT, PTP, loading, the device manager did not appear anything either!
@edit
USB HOST DIAGNOSTIC