Develop Bugs

[Q] Help, stuck in Bootloop/CMR

Situation
My SGH-T989 boots to the cyanogenmod circular animation screen, and stays there. If I hold volume up + volume down, I am able to boot to clockworkmod recovery 6.0.3.1. Some functions in CMR (format /cache, Go Back) lock up CMR and I have to reboot.
My PC doesn't seem to find the USB device using adb devices nor Odin. After searching xda, I bought this USB jig, which allows me to boot to download mode. Still no dice on USB though, doesn't even show up in Device Manager. I have tried both ports and three different cables, at least one of which worked on my Motorola Atrix2.
Background
I was running great using cyanogenmod 9 and clockworkmod recovery 5.0.2.7, which I originally set up using Odin on Windows 7 within VMWare Fusion on my Mac.
Through ROM Manager notifications, I downloaded clockworkmod recovery 6.0.3.1 and cyanogenmod 10.0.0 and later, cyanogenmod 10.1RC1. I upgraded to CMR6 and CM10.0 (not sure which order) successfully, after making a backup using CMR5. I decided to try out CM10.1, and downloaded it using ROM Manager. I made another backup and installed CM10.1. For some reason I decided to go back, and restored that backup.
I have Samsung drivers v1.5.14.0 installed. Here's what Odin looks like. Since I am new, please copy and paste the link below to see it.
{
"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"
}
My Goal
Get back to a working phone, with any ROM and any recovery.
Get cyanogenmod 10.0 working with any recovery and make sure I have a good backup.
Try Jedi Mind Trick with TWRP
I really appreciate any help or xda pointers. I honestly searched my butt off before posting, and watched the noob video.

rhoegg said:
Situation
My SGH-T989 boots to the cyanogenmod circular animation screen, and stays there. If I hold volume up + volume down, I am able to boot to clockworkmod recovery 6.0.3.1. Some functions in CMR (format /cache, Go Back) lock up CMR and I have to reboot.
My PC doesn't seem to find the USB device using adb devices nor Odin. After searching xda, I bought this USB jig, which allows me to boot to download mode. Still no dice on USB though, doesn't even show up in Device Manager. I have tried both ports and three different cables, at least one of which worked on my Motorola Atrix2.
Background
I was running great using cyanogenmod 9 and clockworkmod recovery 5.0.2.7, which I originally set up using Odin on Windows 7 within VMWare Fusion on my Mac.
Through ROM Manager notifications, I downloaded clockworkmod recovery 6.0.3.1 and cyanogenmod 10.0.0 and later, cyanogenmod 10.1RC1. I upgraded to CMR6 and CM10.0 (not sure which order) successfully, after making a backup using CMR5. I decided to try out CM10.1, and downloaded it using ROM Manager. I made another backup and installed CM10.1. For some reason I decided to go back, and restored that backup.
I have the Samsung drivers installed. Here's what Odin looks like. Since I am new, please copy and paste the link below to see it.
My Goal
Get back to a working phone, with any ROM and any recovery.
Get cyanogenmod 10.0 working with any recovery and make sure I have a good backup.
Try Jedi Mind Trick with TWRP
I really appreciate any help or xda pointers. I honestly searched my butt off before posting, and watched the noob video.
Click to expand...
Click to collapse
Try downloading a new recovery to your sd card using a sd card reader on your computer or monitor if you have one. If not try one click unbrick. kies ( emergency firmware) , or reinstalling drivers. As long as you have a boot screen usually your phone can be fixed so there is hope.

You've over done this a bit I think, no purchases should be necessary, just boot into recovery, mount your SD card or internal storage, copy over a ROM of your choice (check t989 development section), copy it to your phone, and another recommendation would be to use the infamous wipe scripts, but always make sure to flash a new ROM after using any wipe function (except for cache) otherwise phone won't have anything to boot from. Basically, just format and reflash
Sent from my SGH-T989 using Tapatalk 2

maybe CMR is broken?
nashy10 said:
You've over done this a bit I think, no purchases should be necessary, just boot into recovery, mount your SD card or internal storage, copy over a ROM of your choice (check t989 development section), copy it to your phone, and another recommendation would be to use the infamous wipe scripts, but always make sure to flash a new ROM after using any wipe function (except for cache) otherwise phone won't have anything to boot from. Basically, just format and reflash
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for your quick answer... I guess my problem is with clockworkmod recovery. Your reply reminded me that I can just put the SD into my other phone to put ROMs on it, which I did. I copied both INFAMOUS scripts to the SD and tried to install them using CMR6.0.3.1, but the phone seems to freeze when I try to install each of them, then the phone reboots after a short while (around 2-3 minutes).
Is it possible to install a different recovery without being able to see the phone in Odin?

rhoegg said:
Thanks for your quick answer... I guess my problem is with clockworkmod recovery. Your reply reminded me that I can just put the SD into my other phone to put ROMs on it, which I did. I copied both INFAMOUS scripts to the SD and tried to install them using CMR6.0.3.1, but the phone seems to freeze when I try to install each of them, then the phone reboots after a short while (around 2-3 minutes).
Is it possible to install a different recovery without being able to see the phone in Odin?
Click to expand...
Click to collapse
If your phone can be recognized on the computer for at least 3 minutes than you can use different programs to install it straight to your phone.
Sent from my SGH-T989 using Tapatalk 2

Trying these suggestions...
richardlibeau said:
Try downloading a new recovery to your sd card using a sd card reader on your computer or monitor if you have one. If not try one click unbrick. kies ( emergency firmware) , or reinstalling drivers. As long as you have a boot screen usually your phone can be fixed so there is hope.
Click to expand...
Click to collapse
Thanks I am working my way through these suggestions; so far, clockworkmod recovery 6.0.3.1 doesn't seem to be able to flash anything without freezing and rebooting after 2-3 minutes. I will update once I try all the options you listed. I am on a fresh install of the drivers (I think) and the phone doesn't appear under USB in Device Manager, so I think that option is out
Will update once I get through a recovery update, one click, and kies. Thanks again.

My problem might be USB...
richardlibeau said:
Try downloading a new recovery to your sd card using a sd card reader on your computer or monitor if you have one. If not try one click unbrick. kies ( emergency firmware) , or reinstalling drivers. As long as you have a boot screen usually your phone can be fixed so there is hope.
Click to expand...
Click to collapse
I tried all of these except one click unbrick, because what I read tells me Odin has to be able to see the device in order for one-click-unbrick to work.
First I tried booting to CMR 6.0.3.1 and installing recovery-clockwork-touch-5.8.1.3-hercules.zip. One line printed saying it was flashing, the phone sat there a short while then rebooted.
Neither Kies, nor Odin can see my device when I connect it either booted to CMR, or in download mode via the USB Jig. I noticed that when in Download Mode, I see "Factory Mode" at the top in red, not "Odin Mode".
I uninstalled the USB drivers from my PC (I was on 1.5.20.0) and installed the ones I got from the Samsung site (1.5.14.0). Same response, nothing under ID:COM in Odin.
I suspected a bad USB cable or port, so I tested my Motorola Atrix2 with the exact same cable and port. It works.
Maybe I have a bad USB connection on my phone? I think it still charges the battery as of this morning.... how could I test this idea? Or, how else can I install a new recovery?

rhoegg said:
I tried all of these except one click unbrick, because what I read tells me Odin has to be able to see the device in order for one-click-unbrick to work.
First I tried booting to CMR 6.0.3.1 and installing recovery-clockwork-touch-5.8.1.3-hercules.zip. One line printed saying it was flashing, the phone sat there a short while then rebooted.
Neither Kies, nor Odin can see my device when I connect it either booted to CMR, or in download mode via the USB Jig. I noticed that when in Download Mode, I see "Factory Mode" at the top in red, not "Odin Mode".
I uninstalled the USB drivers from my PC (I was on 1.5.20.0) and installed the ones I got from the Samsung site (1.5.14.0). Same response, nothing under ID:COM in Odin.
I suspected a bad USB cable or port, so I tested my Motorola Atrix2 with the exact same cable and port. It works.
Maybe I have a bad USB connection on my phone? I think it still charges the battery as of this morning.... how could I test this idea? Or, how else can I install a new recovery?
Click to expand...
Click to collapse
what exactly does your computer say when your phone is connected? USB, MT
P DEVICE, ADB, QHS_USB_DOWNLOAD MODE, UNRECOGNIZED DEVICE, ETC?

richardlibeau said:
what exactly does your computer say when your phone is connected? USB, MT
P DEVICE, ADB, QHS_USB_DOWNLOAD MODE, UNRECOGNIZED DEVICE, ETC?
Click to expand...
Click to collapse
Nothing, it behaves like there is nothing connected. I have reinstalled the drivers twice, and Kies reinstalled them again I think. This is the same whether the phone is booted with the USB Jig to "Factory Mode" or ClockworkMod Recovery.

Dumb question... but did you restart your pc when you installed the drivers?
Sent from Evils Cradle of Filth T999

alloycowboy said:
Dumb question... but did you restart your pc when you installed the drivers?
Sent from Evils Cradle of Filth T999
Click to expand...
Click to collapse
No I didn't
I just did, though, and I got the same results. It's like nothing is plugged in at all.

rhoegg said:
No I didn't
I just did, though, and I got the same results. It's like nothing is plugged in at all.
Click to expand...
Click to collapse
Can you try installing over the system within the CWM you currently have now, or will it just freeze on you? If you have a SD card, you could put the CM9 ROM back on there, and try reflashing to see if you can at least get into your phone...

smokinjoe2122 said:
Can you try installing over the system within the CWM you currently have now, or will it just freeze on you? If you have a SD card, you could put the CM9 ROM back on there, and try reflashing to see if you can at least get into your phone...
Click to expand...
Click to collapse
I have tried several versions of CM that I already had on my external SD (9.0.0, 9.1.0, 10.0.0) and now it boots to a black screen rather than the infinite CM10 boot animation. I think that's due to a successful format /system and format /data I did yesterday.
When I try to install any of these zips, it prints a single line "Installing <whatever>..." then sits there for several minutes, then reboots.

rhoegg said:
I have tried several versions of CM that I already had on my external SD (9.0.0, 9.1.0, 10.0.0) and now it boots to a black screen rather than the infinite CM10 boot animation. I think that's due to a successful format /system and format /data I did yesterday.
When I try to install any of these zips, it prints a single line "Installing <whatever>..." then sits there for several minutes, then reboots.
Click to expand...
Click to collapse
Hmmm. I do think ODIN may be the only way to go. I know you said you can't get your PC to see your phone, have you tried a different computer? Just to make sure it's not a comm problem with your particular computer or driver corruption?

[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.

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.

MTP Not Working Windows 10

I am unable to get Windows to mount my Pixel XL in MTP mode. I have the Pixel's screen turned on and unlocked, and the connection option on the phone's pull down menu is set to transfer files. Windows is able to mount the phone when it is in picture transfer mode, but not in MTP mode.. When I look in Window's device manager I can see that the MTP device is connected but I'm getting a yellow triangle exclamation, as in the driver is no good. I uninstalled the driver and tried letting Windows reinstall to no avail. I have searched the web for MTP drivers for Windows, but I can't really find anything. The specific version of Windows that I am using is Windows 10 Education 64.
The main reason for my concern is that I am about to attempt to apply the new root method that is available, and I wasn't sure if I needed to be connected successfully via MTP before I get the ball rolling with ADB. I do have the ADB drivers installed, along with ADB and fastboot and that seems to be working fine. When I run the command 'adb devices' the console shows that my Pixel XL is connected. I am assuming that I should be good to go on that front, but I still want to know why MTP is not working on Windows, and how I can fix it. Any suggestions would be greatly appreciated.
Here's a screen shot of what Window's device manager is showing me.
{
"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"
}

norcal61 said:
I am unable to get Windows to mount my Pixel XL in MTP mode.
Click to expand...
Click to collapse
Maybe this will help: http://www.technobuzz.net/download-google-pixel-xl-usb-drivers-adb-fastboot/
Personally I installed the latest SDK which comes with the latest drivers.

Scott said:
Maybe this will help: http://www.technobuzz.net/download-google-pixel-xl-usb-drivers-adb-fastboot/
Personally I installed the latest SDK which comes with the latest drivers.
Click to expand...
Click to collapse
I tried that already. I stumbled across it while searching for a solution. The adb and fastboot parts worked well but not the regular mtp drivers. I think maybe the problem has to do with Windows itself.

I had a similar issue with my Pixel C tablet. I don't remember which driver that I had to use but I eventually got it to work. I believe that I ended up needing PDANet to resolve. I am using the same computer for my Google Pixel phone. I have successfully been able to use MTP on my Google Pixel phone and have access to all the files via file explorer.

I noticed the same thing. When I first attached my phone to the laptop I could see the phone in device manager. Couldn't get into internal storage. Changed the phone from mtp to picture mode then back to mtp and was able to get in. I have to use this method whenever I attach my phone to the laptop using Windows 10. I didn't get any yellow exclamation signs at any time.

plug your phone to your computer then check the notifications,tap on the USB charging this device for other options...just tick the usb to transfer files ....

Check out this Youtube video, fixed it for me.
https://www.youtube.com/watch?v=fUHQzqxxsZI

defens23 said:
I noticed the same thing. When I first attached my phone to the laptop I could see the phone in device manager. Couldn't get into internal storage. Changed the phone from mtp to picture mode then back to mtp and was able to get in. I have to use this method whenever I attach my phone to the laptop using Windows 10. I didn't get any yellow exclamation signs at any time.
Click to expand...
Click to collapse
Believe it or not have seen / owned many devices that exhibited this behavior.
Switching back and forth always fixed.

awesome thanks for that video!!
peejayw said:
Check out this Youtube video, fixed it for me.
https://www.youtube.com/watch?v=fUHQzqxxsZI
Click to expand...
Click to collapse

This was from Microsoft's site, is a little quicker. It would be nice if this got fixed.
(1) Go to C:\Windows\INF
(2) Type "wpdmtp.inf" in search bar provided to the right of the address bar in Windows 10.
(3) Once you found it, just right click on it and select install. It will take a very few seconds.
(4) Connect your device to the pc.

I've found that switching from a USB 3.0 port to a USB 2.0 port fixes all file transfer issues with the Pixel XL. Anyone else seeing that? Any ideas why?

triumvirant said:
I've found that switching from a USB 3.0 port to a USB 2.0 port fixes all file transfer issues with the Pixel XL. Anyone else seeing that? Any ideas why?
Click to expand...
Click to collapse
Nope. Coincidence.
Sent from my Pixel using XDA-Developers Legacy app

triumvirant said:
I've found that switching from a USB 3.0 port to a USB 2.0 port fixes all file transfer issues with the Pixel XL. Anyone else seeing that? Any ideas why?
Click to expand...
Click to collapse
bobby janow said:
Nope. Coincidence.
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
I don't know if it's a coincidence because USB 3.0 is still not fully supported or functional on all new motherboards. Even the brands that claim to and brag about having it still have a half ace implementation of it. I'm looking at you Asus and Gigabyte!!! :crying: I have had to stop using their boards because I've gotten too many complaints from customers.
I can never get any 3.0 device to run off my 3.0 ports, wtf?! I can get flash drives to work all day for sure though!!!:silly:

i'm running an ASUS MB too...perhaps there are more variables to this equation than we want to believe.

Jammol said:
I don't know if it's a coincidence because USB 3.0 is still not fully supported or functional on all new motherboards. Even the brands that claim to and brag about having it still have a half ace implementation of it. I'm looking at you Asus and Gigabyte!!! :crying: I have had to stop using their boards because I've gotten too many complaints from customers.
I can never get any 3.0 device to run off my 3.0 ports, wtf?! I can get flash drives to work all day for sure though!!!:silly:
Click to expand...
Click to collapse
I'll grant you that, some of those things happen to me too. But as for a driver not recognizing the device this thread fixes that. That doesn't have anything to do (afaik) with USB 3.0. This was just a silly driver that lost its way. As soon as I tried the method here everything was back to normal.

bobby janow said:
I'll grant you that, some of those things happen to me too. But as for a driver not recognizing the device this thread fixes that. That doesn't have anything to do (afaik) with USB 3.0. This was just a silly driver that lost its way. As soon as I tried the method here everything was back to normal.
Click to expand...
Click to collapse
Windows! Lol.

FireTV 4K sees keyboard but not flash drive

Firmware 6.2.7.6, not rooted
My FireTV 4K sees a keyboard but not a flash drive
Long story... so I decided to add external storage to my FTV and ordered a flash drive (Sandisk Ultra Flair USB 3.0 32GB) While waiting to get it I decided to see if my WD SSD USB drive ( Western Digital "My passport" 500GB) would be recognized. I plugged it into my OTG cable and I was notified that it needed to be formatted. I didn't want that so I just exited out and unplugged it. At least now I know FTV recognizes drives.
A few days later I got my flash drive but when I plugged it in it didn't see it, I thought perhaps that flash drive doesn't work with the firestick. So, I retried some other flash drives to no avail. I decided to retry my WD SSD USB drive and now it doesn't get recognized. The only answer I can find on the web is I need to turn off USB DEBUGGING but there is no option for that in developer options just ADB debugging and Unknown sources. Besides that my keyboard does work so I know my OTG cable is good.
I have reset my FTV to factory settings but still have the same issues. I also have rebooted many times.
My questions would be:
1. Where is my USB Debugging gone?
2. Why did it see my WD drive one day and not three days later?

carpenter940 said:
The only answer I can find on the web is I need to turn off USB DEBUGGING but there is no option for that in developer options just ADB debugging and Unknown sources. Besides that my keyboard does work so I know my OTG cable is good.
I have reset my FTV to factory settings but still have the same issues. I also have rebooted many times.
My questions would be:
1. Where is my USB Debugging gone?
2. Why did it see my WD drive one day and not three days later?
Click to expand...
Click to collapse
There isn't an USB debugging option for the sticks, only for the fireTV boxes... so forget about that point
About the WD drive, that could be a power issue, maybe try a stronger power supply...
If you get a new usb storage stick, you can try a format to fat32 on a PC, in case exfat doesn't work.

I had the flash drive formatted as Fat 32 and tried formatting to exfat but still nothing. I also am using a powered USB hub. I also replaced the amazon power module which was 850ma with a 1Amp but still nothing. My next attempt will be to get a flash drive that I read will work with the firestick (Sandisk ultra 32GB 3.0,
Model : SDCZ48-032G-A46).

Idk whats your goal, but here is a thread that is maybe useful for you (in case you've the 4k stick and you decide to root it):
[Magisk][Module] Amazon FireTV4k NTFS/F2FS/EXT4/exFAT OTG support
Warning !!! Use this module on your own risk !!! I can't be held responsible for any kind of damage or data loss !!! Version 1.3 and higher requires my custom kernel 6.2.7.1_v3 or higher + Selinux magisk module from the kernel thread Magisk 20.3...
forum.xda-developers.com

Sus_i said:
Idk whats your goal, but here is a thread that is maybe useful for you (in case you've the 4k stick and you decide to root it):
[Magisk][Module] Amazon FireTV4k NTFS/F2FS/EXT4/exFAT OTG support
Warning !!! Use this module on your own risk !!! I can't be held responsible for any kind of damage or data loss !!! Version 1.3 and higher requires my custom kernel 6.2.7.1_v3 or higher + Selinux magisk module from the kernel thread Magisk 20.3...
forum.xda-developers.com
Click to expand...
Click to collapse
I will try this if the new flash drive doesn't work.

Update: Turns out my firestick may have been seeing the flashdrive all the time but never gave me any indication that I plugged it in. On a hunch, I opened remote abdshell and ran the show me drives command and it popped up. I was always checking the STORAGE section of the settings but only saw internal storage.
Thank you for all your help.