[Android General] pr3dicament:
Yeah I'm wondering this same thing, but first I need to know if it's just me or if the device is might be defective? I cannot get it through to ADB and I've used a straight male A to male A USB cable, four different kinds, along with microusb cables, both at once, separately, with the power on, etc... it never, ever, ever even does anything aside from say that it's "not recognized" with a microusb cable. I cannot get ADB to even talk to it... I've enabled USB Debugging, I've made sure it has as much access as it can i.e. Developer Options.. I tried switching from MTP to PTP and then back to others listed and then going back to MTP and it still doesn't acknowledge it at all. It's as if a device does not exist. in Linux, lsusb shows zip. In Windows, there's nothing with any sort of indication in device manager i.e. 'unknown device' .. nothing, zip. I'm sorry for such a long post, but.. Is this normal for this particular device? It was from walmart, really cheap.. I've dealt with another one before but a different model and it came with lollipop and it talked with ADB, MTP would work, etc.. this one, however, wouldn't work with any driver so far--and I've tried just about any driver known to man, and it's as if it doesn't exist.. in Linux (tried redhat, then ubuntu) and Windows 7 x64.. so i thought, at first, that it might just be the device..

Then I booted it into fastboot (I did this by using the volume key + power key combo to enter stock recovery. I tried ADB there.. STILL NOTHING. Then I still had it plugged in (USB, Male to Male) .. and I used the volume key to highlight "Reboot to bootloader" i.e. fastboot. Now, I just did this for the hell of it. Then suddenly it recognizes the device, I remember comically typing fastboot devices -l -- and suddenly I saw it.. it seemed like a miracle or something--this was in linux. It shows the exact serial number, as opposed to adb showing "error, device not found" --- I did this in Linux (redhat, ubuntu and I figured it'd work more natively in it, but same thing... ONLY fastboot works.) -- I also tried windows 7 of course.. multiple machines, multiple cords... etc.. reset to factory defaults as well hoping it was a glitch. I tried "fastboot oem unlock" and well.. volume keys aren't programmed in... even though in Developer Options, it has "Allow unlocking of OEM bootloader" or whichever.. same place where you pick USB debugging and usually, on a box trying to access it via adb, it would ask for a hash fingerprint. It did not do anything at all to recognize it while booted into recovery or in android. In bootloader mode? It installed the precise driver in windows.. "ADB Bootloader Interface" -- it detected it with no problem.

I literally have to use bluetooth or.. wifi direct, or my google drive.. etc, just to send a file over... and ADB will not remotely work via tcpip; tried that. I even tried opening adb on the tablet with terminal emulator.. and note that all of my other devices do work with this, from Nougat down to marshmallow, lollipop, and one with kitkat. I'm usually considered an "expert".. but I might as well just ask someone who knows something about it, having it.. I couldn't find anything else about this thing. Jesus. I'm able to launch adb on my other devices.. that was another point i was making. I had to type this all out or I don't think this would get any attention. I did everything I could and there's no scatter file for this, and that is the only way I can even try. And all one click root tools do not work including the latest Kingroot etc... I doubted it. I just wanna know if I need to take this back before it's too late, basically. I'll wait regarding root/custom roms.. etc. Anyway.. Sorry for the whole book here, I just had to make sure I explained it and that I exhausted the options typically measured. It looks like I'm replying out of the blue and in the wrong place but it's close enough I'd hope.