I recently purchased two used A100's for a steal. One of them is recognized by my computer and I was able to root it just fine, but the other isn't recognized by my computer. It doesn't even show up in device manager. I thought the usb port on the tablet may have come unsoldered, but after taking the device apart and inspecting the port nothing seems to be physically wrong with it (at least from what I can see).
I have tried several different usb cables, different computer ports, I tried flashing the stock ICS zip posted by Romman0, factory reset a few times, toggled usb debugging on and off, changing usb mode from mtp to ptp and back, I even tried to get an adb boot logcat but it just sat there waiting for device.
My question is, does this sound like a hardware fault?
Is there something else I can try to obtain root? Everything else seems to work great, but I really want to root this thing.
Any help is appreciated.
monkeybuttons said:
I recently purchased two used A100's for a steal. One of them is recognized by my computer and I was able to root it just fine, but the other isn't recognized by my computer. It doesn't even show up in device manager. I thought the usb port on the tablet may have come unsoldered, but after taking the device apart and inspecting the port nothing seems to be physically wrong with it (at least from what I can see).
I have tried several different usb cables, different computer ports, I tried flashing the stock ICS zip posted by Romman0, factory reset a few times, toggled usb debugging on and off, changing usb mode from mtp to ptp and back, I even tried to get an adb boot logcat but it just sat there waiting for device.
My question is, does this sound like a hardware fault?
Is there something else I can try to obtain root? Everything else seems to work great, but I really want to root this thing.
Any help is appreciated.
Click to expand...
Click to collapse
Its been awhile since I've seen the method used but it probably requires adb at some point so it would need a working USB connection. Aside from some sort of physical damage (pins are a good bet) there's not usually any reason it stops working, of the faults this device has the USB port isn't one.
If the process just uses adb for commands and pushing files you may be able to root it from android itself.
pio_masaki said:
Its been awhile since I've seen the method used but it probably requires adb at some point so it would need a working USB connection. Aside from some sort of physical damage (pins are a good bet) there's not usually any reason it stops working, of the faults this device has the USB port isn't one.
If the process just uses adb for commands and pushing files you may be able to root it from android itself.
Click to expand...
Click to collapse
That's one of the things i am really struggling with about this. I can't see why the USB port would go bad. I am at my wits end. I can't see anything physically wrong with it. I even tried cleaning the pins with isopropyl alcohol using q-tips and a male micro-usb connector i have laying around.
How would i root from android itself? Can i run adb commands from a terminal without root access? I can't see how this would be possible.
If you can illuminate on how to root without the usb port i am all ears.
Also, thanks for the reply.
monkeybuttons said:
That's one of the things i am really struggling with about this. I can't see why the USB port would go bad. I am at my wits end. I can't see anything physically wrong with it. I even tried cleaning the pins with isopropyl alcohol using q-tips and a male micro-usb connector i have laying around.
How would i root from android itself? Can i run adb commands from a terminal without root access? I can't see how this would be possible.
If you can illuminate on how to root without the usb port i am all ears.
Also, thanks for the reply.
Click to expand...
Click to collapse
You don't need root to use adb, some commands yes but you can do quite a bit without it, things that gain you root access. Some commands done via adb can also be done on the device itself via terminal.
That aside like I said its been awhile I'd need to look at it and see if it can be done, I wouldn't get my hopes up, though, if it hasn't been done yet there's probably a reason.
Ok. I appreciate your insight and time. I'll see what I can do with it.
Related
I have been searching for about a week now and still can't figure this problem out. I bought this phone used about a month ago and I haven't tried to connect it to my pc until just recently. I am wanting to root and unlock my phone but I can't connect to pc using usb cord although it will charge it.
I am on GB 2.3.6 vuvkj6, stock.
I have tried 4 different usb cords, 4 different pc/laptops and all usb ports. I have also installed and uninstalled several usb drivers with no luck.
My phone can only get into download mode using a jig. Even in download mode, I can't connect to pc. I have tried using Heimdall, Odin, and kies but it just does not connect.
If I can use a jig to get it into dl mode, does that mean the phones usb port is fine?
I just want to be able to connect with pc. Is it possible to flash using my sdcard? I am thinking maybe the phone is missing something to pick up the usb signal or something.
I am lost, any help would be appreciated.
Maybe, I think it's a phone issue.
Do you still have a warranty?
I bought this phone used, so no warranty. If the jig works, does that mean the usb port is ok?
Does the phone charge when plugged in? Have you tried to go ahead and flash even though it says not recognized?
ligitalipeople
Yes the phone does charge when plugged in. I can't flash using Heimdall or Odin. Any other way of flashing?
I have also put the phone into debug mode with no luck.
Have you done a factory reset?
Yes, I have done a factory reset.
FINALLY! I got it to work.
Can you post back here and tell us what you did to get it working in case someone else has the issue?
Thanks and glad you got it going!
I am not sure what made it work for me. But what I did was "clear memory" on ram. I don't remember how I got onto that screen but I clicked on ram and clear memory.
I then pushed the usb into the pc a few times really fast until pc showed somethnig other than "usb device not recognized". Pc then started to show device connected.
if you are using windows i have found that sometimes the usb ports u used for the phone get stuck to the driver that was there in the first place. So what I do to fix this is go into device manager from the control panel and then uninstall the drivers for the specific port that I am trying to use. While keeping my phone unplugged from the computer I then reinstall the samsung drivers, restart my computer and then try to plug my phone in. 90% of the time that has been what works for me.
Ok, I figured out the problem. It has nothing to do with the drivers or clearing ram memory. My problem is the actual micro usb connection. If is a little loose from side to side and when I push it to one side, it connects no problem.
That is the exact same thing that happened to my wife's phone... luckily it was still under warranty...
Sent from my SGH-T959V using Tapatalk
My phone is out of warranty. At least now I know the problem. It was extremely frustrating trying to figure it out.
Here is my case, I am now on stock 4.1.1
When I connect my nexus to my PC, it only charges. I can neither mount USB storage nor attaching to debug mode. What even worse is that, I can't even run fastboot command in bootloader, so basically I can't flash a custom recovery.
As a result, I am now stuck on stock ROM.
Can anyone please give me an idea to get my USB driver work, or at least to flash a recovery?
EDIT: I have used fast charge before, so will it screwed up or disable the USB driver? Any way to restore it in my case?
EDIT: Solved. The two USB line charges only
Can anyone help me?
I have tried two USB lines with two PCs, so I do think there is a problem of my phone.
barrielui said:
EDIT: I have used fast charge before, so will it screwed up or disable the USB driver? Any way to restore it in my case?
EDIT: Solved. The two USB line charges only
Click to expand...
Click to collapse
Hello barrielui,
would you describe more information how you solved that issue? What do you exactly mean by last line? It's working only for "charging" or for data transfer (mass_storage) too? You've found new type of USB cabel or what?
Unfortunately have the exactly same issue few days after upgrade to JLB 4.1.1 stock Rom. It works properly few days and than from some reason something happen, but don't know what&why and how to fix it.
Think maybe it's a hardware problem, but how it happened is mystery
I had issues with my usb for a while myself, it just kept getting worse until I would not get a charge at all. Your issue may be different than mine, but I had my nexus s the first week it came out. I had already planned to have my phone sent in for repair on my usb, so I figured I could tinker with it. It turns out that the little tab in my charge port was pushed down (away from the screen when holding in hand) just enough that it would barely make contact with my micro usb cables. I used a tac and slipped it in between and carefully pried up a little.
Caution, this may not be your problem, look at other options, or compare your usb port to another phone to determine if it is it. My tab was just barely gaped from the bottom.
Solution
Try cleaning the Nexus port pins with something pointy...deposits on pins inside cellphone port prevents the usb contact..clean it one by one with a pin and tell me if it worked
teekex said:
Think maybe it's a hardware problem, but how it happened is mystery
Click to expand...
Click to collapse
It was a hardware issue with USB connector on motherboard on my case, but strange is that it was occurred when flashing to newer system.
1. phone working 100%. USB and all.
2. previously had USB debugging on, plugged into PC & needed ADB drivers so installed the Motorola ones.
3. Windows then tells me unrecognized device, swapped cable, tried different PC, no go. all the same.
4. Whilst in fastboot, same issue.
Things were fine prior to this, which is why I'm finding it odd. I did have USB debugging on & the device plugged in when I installed the drivers but I'm not sure if this was the cause or not. Any help?
Would the usb connector on the phone happen to be stuffed?
Do you have any Linux machines around?
It sounds like typical Windows driver issues, unfortunately.
Sent from my SPH-D700 using xda app-developers app
Windows can't identify the device to even install a driver, this is why I'm finding it a little bizarre. I do have Linux live cds I guess ill give that a try
Rzeractor said:
Windows can't identify the device to even install a driver, this is why I'm finding it a little bizarre. I do have Linux live cds I guess ill give that a try
Click to expand...
Click to collapse
Would be interesting at least to see what lsusb says.
My device kinda works still, although the screen is broken... Should say something like 22b8:0228 for your Motorola.
Edit - and I guess what I meant to say, is if Windows installs the wrong drivers it may be getting something hosed up.
Nope, no go. Lsusb doesn't even seem to recognise it.
However, when I did factory reset the phone, and plugged it into a mac, the phone responded by telling me that it was in 'charge only' mode; and that usb debugging was enabled [which I did]. Which techincally meant it was working!
but, as soon as I tried to plug it into a PC, same unknown device issue. Back into the Mac, and didn't even register. I'm stumped
Very bizarre.
Any other ideas?
What do you mean lsusb doesn't recognize it...? What's the output?
Sent from my SPH-D700 using xda app-developers app
arrrghhh said:
What do you mean lsusb doesn't recognize it...? What's the output?
Sent from my SPH-D700 using xda app-developers app
Click to expand...
Click to collapse
The output doesn't even list the device connected. I tested this with random flash drives and such, libusb sees them, but when the phone itself is plugged into the machine, it lists the same items [I assume the usb bus] as when it isn't plugged in.
As I said, very bizarre. This seemed to have happened when I had the phone connected to the PC whilst installing the motorola drivers. Weird. & that the phone only charges via a mains plug now, and not thru usb directly.
You said you tried a different cable & PC... did you?
It does sound like USB is broken, water damage perhaps? Seems popular nowadays
(kidding, my Q was water damaged...)
If USB doesn't work in fastboot mode, on multiple USB cables (I'm assuming you have the OEM cable and have tried it first), multiple USB ports, and multiple computers... It does sound like the port is somehow fried. Never heard of such a thing, to be honest. Even my water damaged Q eventually started working on USB again and I was able to RSD it back to stock.
So, my phone won't quick charge, nor will it connect to pc. Keep getting the divice not recognized and has malfunctioned. Stock everything, cause I can't unlock the bootloader to flash it. 7.0 android. Things I've tried, brand new cables, the charging block is the one that came with the phone. 3 different pcs, windows 7 to 10. USB Debugging, the secret enter code in dialer to the menu to enable hisense or whatever USB setting, enabling it USB to hisense in advanced (its not hisense its something, can't remember its the oem exe) various drivers and Android drivers.. I've tried it all almost. It's not beyond me to take the phone down and replace the port but I'd rather not if it's a common correctable issue. I reset this phone twice to see if a reset would fix it.. Nothing. Anyone else with the issue or something like it? Just wanna root this thing.. This is a "new to me" phone so probably why they sold it if it's the actual port jacked up, it's not a big big deal as my g3 was overheating and dying and I got this for $80.. Figure I came out on top cause the USB c boards are cheap enough. But I hate the glued together stuff cause you never get it exact when throwing it together or at least I don't. Big hands. So... Here is to hoping it's software. Phone works 100% other than that I like it.
Yeah, I know this. Quick charge won't work on the block. I'm not concerned with quick charge on my pc.. I'm concerned with connecting to my pc period. I can't connect at all. The bootloader is locked because I can't connect to pc to unlock it. So to recap. Quick charge will not work on the block at all so I lack being able to quick charge, and I cannot connect to a pc via USB. I have tried all the fixes I can think of in my original post with no success unless I missed something?
I'm thinking I'm gunna have to tear this phone apart and replace the dang port... Lol. Too easy.
Hello everyone!
I found my old Galaxy S6 lying around in my home and I decided to use it as a development phone. The battery was bad and the usb wouldn't connect with my pc anymore. When I connected it it on Windows it gave bad descriptor errors for some time, and then it wouldn't get recognized anymore. I thought it was the USB connector board and since it was hard to replace I gave up and bought a new phone.
I recently decided to risk replacing it since I have no use for it anyway so I got a battery and a USB connector board replacement. I managed to do it and the phone looks good, except the USB still doesn't work. On windows it doesn't even get listed in the device manager and on linux the dmesg command gives this output:
Code:
[4249.142864] usb 1-1-port3: attempt power cycle
[4250.314394] usb 1-1-port3: Cannot enable. Maybe the USB cable is bad?
[4251.170460] usb 1-1-port3: Cannot enable. Maybe the USB cable is bad?
[4251.171100] usb 1-1-port3: unable to enumerate USB device
I don't know what to think. I also thought the stock firmware got corrupted last time I flashed it but I can't try a different one since the USB is broken and there's no root on it. At this point I think the issue is either the software or the motherboard, but the phone is good except for the usb so I don't really know what to do.
Do you have any suggestions? Is there a way to flash a custom firmware without the USB?
Carefully check the ribbon connector pins for damage.
Was the replacement port PCB the correct one?
blackhawk said:
Carefully check the ribbon connector pins for damage.
Was the replacement port PCB the correct one?
Click to expand...
Click to collapse
Yes the PCB is the right one, it's a very specific board with the audio jack, capacitive sensors for the back and task-manager buttons and the usb connector. There's no ribbon cable, it's just a connector that snaps into the motherboard.
And everything is fine on the board except for the device enumeration. It's like either the firmware can't get the USB up or there's some other kind of issue in the main board.
The problem is I can't try flashing another firmware since I can't get root on it. I also tried apk based roots but it seems they've been patched on my android version (7.0)
EDIT: there actually is a ribbon cable connecting the usb board to the motherboard through the snap connector, but being on the replaced board I guess it is fine. I also checked the connector on the MB side and it looks okay.
Was the old port PCB known bad?
If not, probably a blown mobo.
blackhawk said:
Was the old port PCB known bad?
If not, probably a blown mobo.
Click to expand...
Click to collapse
Not confirmed, but I assumed it was since the USB was broken... the charging was slow but that was probably due to the dirty connector. At this point if it's a hardware issue then it's the motherboard...
Isn't there anything I can do to root the phone without the USB? At least I would be able to use adb wifi debugging and make use of it as a dev phone...
I have an update. I tried using an old pc with USB 1.1 ports and a linux live distro and it somehow recognized the phone. It was working fine so I got into download mode and I tried flashing TWRP using heimdall. I had some issues so I had to compile the latest version, but the flashing process stops when reading the PIT data.
I installed windows and tried with Odin, same result, it works until "Get PIT for mapping" and never goes further...
I also tried different USB cables, ports with the same result. Could there be an issue with this "PIT"?
Samsung PIT Files | Explained | iHax
What is a Samsung PIT file? What does it do? Which PIT file to use if there is more than one? We answer this and a lot more in this explainer article!
ihax.io
It's possible you suffered a SEU, they are rare but can happen at any time. The data effected is completely random, it can be any data on the flash memory including the PIT. Restoring the corrupted data is the only fix.
The hardware will be intact if this is the cause.
blackhawk said:
Samsung PIT Files | Explained | iHax
What is a Samsung PIT file? What does it do? Which PIT file to use if there is more than one? We answer this and a lot more in this explainer article!
ihax.io
It's possible you suffered a SEU, they are rare but can happen at any time. The data effected is completely random, it can be any data on the flash memory including the PIT. Restoring the corrupted data is the only fix.
The hardware will be intact if this is the cause.
Click to expand...
Click to collapse
Well, that would explain why the USB suddenly stopped working, but it's like a one in a billion chance. In the meantime, with no other idea coming to my mind, I officially give up and use the phone with stock firmware and no root.
I will install userland and use it as a raspberry with touch screen lol.
Thank you for your patience and your help