I know that this theme has been beaten mercilessly, but let's try it again. Maybe someone can help.
I'm looking to breath some life back into my old TF101 with an update to KatKiss.
My serial number starts 037. I'm running 4.0.3 ICS. I have USB debugging enabled. I have MTP enabled. On the computer side, I'm running Win 8.1 on a Haswell i7 16GB with USB 3.0.
I have the original USB cord, and a new 3.0 USB cord from a third-party manufacturer. I've tried both cables. The TF101 itself is well-aged and somewhat beat up, but not beyond use. The cords work for charging.
When I plug the USB cable into the PC, the computer makes a sound, but no device is shown. The TF101 doesn't show that it's connected to the computer. I've looked everywhere: Devices and Printers, Device Manager (there's no "Other Device Listed"), under safely remove devices, and even under Computer Management > Storage > Disk Management. The TF101 is nowhere to be found. The computer does not recognize it.
When I power off the tablet, and try going to APX (or whatever) mode with VOL UP and POWER, nothing happens there either. (The computer shows nothing whether connected through the USB cable while Android OS is running, or while I'm trying to go into APX mode.) I can, however, go into recovery mode (or whatever it would be called) by holding VOL DOWN and POWER. I tried a factory reboot, but that didn't work either. The computer still doesn't see it.
Basically, I've concluded that there's no hope. Given this state of affairs, I cannot root my TF101, and, because I cannot root the tablet, I cannot install custom ROMs on it.
Does that about sum it up? Anybody else have any other great ideas?
I'd very much appreciate any insight anyone could give me.
Install the drivers on this thread and download Easyflasher
http://forum.xda-developers.com/showthread.php?t=1688012
Power off the TF while it is connected to the PC
Hold Power & Vol Up to enter APX mode
Device should be recognised by windows and hear the USB connect sound
Nothing will appear on TF screen
Run the Easyflasher and install TWRP
When done, boot to recovery to check you have TWRP recovery installed
If yes, copy KatKiss ROM to Micro SDCard in TF and flash from TWRP along with Gapps
*Detection* said:
Install the drivers on this thread and download Easyflasher
http://forum.xda-developers.com/showthread.php?t=1688012
Power off the TF while it is connected to the PC
Hold Power & Vol Up to enter APX mode
Device should be recognised by windows and hear the USB connect sound
Click to expand...
Click to collapse
Detection, I appreciate your response! The thing is, when I try to enter APX mode, nothing is recognized by the computer. I don't hear any sound. I don't see any new devices appear anywhere.
Should I conclude that I have the "TF101-is-not-recognized-by-PC Problem"? And, if I do, is there anything else I can do to about rooting and installing a custom ROM?
RJM
In device manager, try enabling "View hidden devices" and see if you can see the TF101 ghost entry, if yes, remove it and then plug the TF back in and see if it's recognised then
If you don't see anything that way, try viewing hidden devices with it plugged in too
There is no reason it shouldn't be detected in APX mode unless you have been unlucky and have 2 dodgy cables, or there is actually hardware damage to the TF
Try installing windows to a virtual machine too, see whether you can get it recognised that way
If you have access to another machine, see if you can get it seen on there to rule out hardware as the issue
Thanks for the reply. I appreciate your interaction very much.
I've tried it on both machines. There is no sign of TF101 anywhere, on either machine, as a ghost or anything else. I've looked under the Android section, as well as under Portable devices and every other list. There's definitely no sign of a TF101. No sign of anything that my TF101 might be posing under.
The only time I get any kind of response by the computer is when I plug the TF101 into the computer when the TF101 has Camera (PTP) mode activated. When I do that, I hear a little jingle. If I have the Device Manager open, it flashes. But, even then, I don't see any sign of it anywhere.
I'm totally stumped. Would there be some clear indication on the hardware that would cause the problem?
By the way, both USB cables charge just fine when I'm using the USB power box. But when using the computer, there is no charge or any other sign of the thing.
If you have any other advice, I'd love to try it!
The power and data connections on the USB lead are separate, so if you have a faulty lead, it could still charge, but not be seen by the PC
Something like this:
1: Power
2. Data
3. Data
4. Power
You won't see the TF charge from PC, it is only a trickle charge via PC, and the TF has to be powered off iirc, or at least the screen has to be off, so you only see the result, not the actual charge
Not sure what having the camera on is doing, I would still lean towards faulty USB cables being the issue even though you have 2 of them
Im guessing that the 2nd cable is a 3rd party cable, not a genuine ASUS TF101 cable ?
Hi everyone. I post this topic in here, because I don't know where else I could do it, because my device is of a not much known brand. I own a Krono Net 1032, chinese tablet, is rooted via magisk, and everything was going ok with it, until several days ago, when I tried to connect from pc, to adb via wifi, but it didn't connect (adb debugging was enabled and adb returned me 10061 error); action that was performed right without any issue till that day. Uneasied, I tried to connect it via usb, but not only won't connect to adb, but it won't be detected as mass storage... even is not detected as anything. Now, really worried, I tried to connect it by changing usb cable... the same; tried connecting on another usb ports...the same; tried connecting tablet on another pc... the same; tried connecting any peripheral via otg... peripherals won't work; I disabled and reenabled adb debugging... the same. It barely charges, but if I move the tablet, stops charging.
The alarming behavior is that, for I could get root access, it should be connected on preloader mode, for can flash it; so if I told you that this tablet is already rooted, is because in the past I could connect it on that mode and my pc did recognize it with such mode. But now, not even pc recognize such connection.
I suspect that is a hardware issue, but I don't know if that could be happening because of usb port solderings or an usb controller ic issue; and I don't want to open it and try to repair, without before read your opinions.
So please ¿What can be happening there?
Thanks in advance for your answers.
Do a Factory Reset.
xXx yYy said:
Do a Factory Reset.
Click to expand...
Click to collapse
I would do, if my device would be detected on fastboot mode or preloader mode, but none of those usb connection modes are detected by pc. So I don't guess it's an operating system issue; or better said, i'm afraid of doing that, and find that it remains the same. But I'll consider it as my last resort (because i've made many customizations that I don't want to lose -root, gravity box, lsposed, etc-). Anyway I think the reason of what could be happening, would be maybe worst than that (I think is a tablet's usb port issue). Thanks for your opinion.
PS: I forgot to say something that confuses me too much but at the same time, gives me hope that this isn't a hardware issue: Wifi adb isn't working too,and something weird, remote control from pc (eg. via teamviewer or anydesk) doesn't work also.
Don't think device's USB-port is defective, that of all things the lanes are broken, but not the power related connections.
I rather think that USB is not configured correctly in Android's build.prop file, expected USB- setting in build.prop always should be
Code:
persist.sys.usb.config=mtp,adb
xXx yYy said:
Don't think device's USB-port is defective, that of all things the lanes are broken, but not the power related connections.
I rather think that USB is not configured correctly in Android's build.prop file, expected USB- setting in build.prop always should be
Code:
persist.sys.usb.config=mtp,adb
Click to expand...
Click to collapse
I tried adding that line, and rebooted the device, but nothing happened, is still without usb support... But wait a moment, about it ¿is there any specific place to paste that line, or can be pasted wherever inside this file
Did you verify that buld.prop got changed?
Not already existing key-value pairs typically are added to end of build.prop file.
Ckeck for existence of these 2 key-value pairs too:
persist.service.adb.enable=1
persist.service.debuggable=1
Does the USB work properly in fastboot?
Renate said:
Does the USB work properly in fastboot?
Click to expand...
Click to collapse
No, is not recognized in fastboot or preloader. That's why I suspect of tablet's usb port, which would be probably the worst scenary to me. The weird thing is, if the suspected problem is related to hardware ¿Why adb via wifi is not working too? ¿Isn't that a routine separated from usb adb? or definitely ¿if usb adb is not working, wifi adb also stops working?
xXx yYy said:
Ckeck for existence of these 2 key-value pairs too:
persist.service.adb.enable=1
persist.service.debuggable=1
Click to expand...
Click to collapse
Yes, they are already written there, but none of the expected happened (which comes alive again its usb port).
If my problem would be hardware related, I mean, if the problem is at the usb port (i think it is, because, despite it charges when cable is plugged, if I move a little the tablet, it loses charge connection. I tried several cables and happens the same), if sadly i'm right, I think that, being positivist, it would be just solderings retouch on the usb port. But investigating, I can see that micro USB type C (female) connector, is not so easy (even is complicated to not say hard) to resolder, so ¿is there any technique?¿Do i need a hot air gun or something like that?¿or is that only solvable by swapping its main board?
Anyway, If my problem is of hardware, none of the options could be nice.
Often the USB connector is on its own little board connected by a flex printed circuit to the main board.
I Googled "Krono Net 1032 USB connector board" and got https://www.aliexpress.com/i/2255799845922187.html
Yeah, it would be great if they were related, but at least you can see what I mean and how cheap it would be if you could find the right one.
Renate said:
Often the USB connector is on its own little board connected by a flex printed circuit to the main board.
I Googled "Krono Net 1032 USB connector board" and got https://www.aliexpress.com/i/2255799845922187.html
Yeah, it would be great if they were related, but at least you can see what I mean and how cheap it would be if you could find the right one.
Click to expand...
Click to collapse
That board seems to be a spare part of a nokia device. It would be very good if only was disconnecting the suspected bad component, and connecting the new one. But I opened this tablet and what I saw, is that seems, that usb port is integrated with the mainboard.
If it were micro USB 2.0 I'd do it myself.
USB Type C on a motherboard I'm sure that I'd destroy somwthing.
Renate said:
If it were micro USB 2.0 I'd do it myself.
USB Type C on a motherboard I'm sure that I'd destroy somwthing.
Click to expand...
Click to collapse
That's my worry, because it's USB type C.
There are two types of Type C connector:
Real, USB 3.0 24 pin
Lite, USB 2.0 12 pin
I'm not sure that I'd even want to tangle with the 12 pin.
I have an update about this topic. Well, I took courage and disassembled as much carefully I could, I tried to get as much tools I could (besides solder iron, magnifying glass, focal illumination, soldering paste, etc.). I could saw that usb socket pins were tiny but accessible, so, also as much carefully I could, I resoldered them, I cleaned them, and reassembled the tablet.
To be brief, after that treatment, the battery charging was more consistent, more stable (now I can move the tablet without losing charging connection) but it still, doesn't want to be recognized by the pc, wheter if it's on fastboot mode, or normal mode (with tablet on). I must clear that my pc, recognizes other android devices that are plugged into it, but this one doesn't. So, that's very wird to me. My only explanation for that, is that its usb controller IC is working bad or could be broken, but if it would be broken, how could be possible, that tablet still can charges its battery? What do you think about it?
PS: I didn't see too much pins, so I think it has 12 pins.
Renate said:
There are two types of Type C connector:
Real, USB 3.0 24 pin
Lite, USB 2.0 12 pin
I'm not sure that I'd even want to tangle with the 12 pin.
Click to expand...
Click to collapse
I was seized by a big doubt since this problem happened. ¿Is wifi ADB bound to usb adb? I mean, if USB ADB isn't working, ¿Does wifi adb stop working too?
Another question is: Before this, I remember remote control worked on this tablet (control tablet remotely), but now there's no way to make it work ¿Can be this related to the original issue?
Even worst ¿Can the initial issue, be related to a ROM corruption issue? I say "worst" because if it is, I don't know how to reflash it without usb support.
No, WiFi ADB should work even if USB is broken.
You should be able to switch to WiFi ADB using a non-rooted terminal app.
You should be able to do this without root.
Code:
$ setprop service.adb.tcp.port 5555
But adbd has to be stopped and restarted. I'm not sure that this works without rooting.
Code:
$ stop adbd
$ start adbd
But you should be able to go to Settings > Developer options > Enable USB debugging and turn it off then on.
Then:
Code:
C:\>adb connect 192.168.1.12345:5555
Of course 192.168.1.12345 must be the actual IP of the Android on your router.
Renate said:
No, WiFi ADB should work even if USB is broken.
You should be able to switch to WiFi ADB using a non-rooted terminal app.
You should be able to do this without root.
Code:
$ setprop service.adb.tcp.port 5555
But adbd has to be stopped and restarted. I'm not sure that this works without rooting.
Code:
$ stop adbd
$ start adbd
But you should be able to go to Settings > Developer options > Enable USB debugging and turn it off then on.
Then:
Code:
C:\>adb connect 192.168.1.12345:5555
Of course 192.168.1.12345 must be the actual IP of the Android on your router.
Click to expand...
Click to collapse
Ok, I did all that, with a terminal emulator. Without root permission, those commands do nothing. So I invocated root access by typing "su" command; then root request appeared, I gave it to the app root access, and then all those commands worked ok. After corroborate the right wifi adb connection (after enable on developer options "usb debbugging" and all those stuff). I tried a remote control program called "scrcpy", and it worked as expected in a normal condition, I mean, I can see on my pc, the tablet's screen and also i can control the tablet from it, but after that , I'm still wondering, why all other remote control programs, like team viewer and anydesk, don't want to control this tablet, hmmm... ¡anyway!
That news in general to me, is an advance, and is good, but i'm still wondering why usb connection isn't responding (mtp, adb, fastboot nor preloader mode) , not even its OTG support and I'm pretty sure this tablet has it, because with it, came additional an OTG adapter, so why would do they add an otg adapter if tablet wouldn't support it?
I took several pictures on my new P7P and am having trouble getting them off of the phone and into my desktop computer. Here's what I have done:
From the P7P Home screen, I tapped "Settings". A "Settings" menu appeared.
I tapped "Connected devices". A "Connected devices" menu appeared.
I tapped "Connected devices".
Under "Other devices", I tapped "USB /file Transfer". Then I tapped "USB File transfer". A "USB Preferences" menu appeared.
Under USB controlled by I tapped "This device", and under "Use USB for" I tapped "File transfer / Android Auto.
And I sat there waiting for something to happen. I expected to see something like "P7P" appear on my computer when I opened the file manager but the only things that showed up were my disk drives. No P7P. What did I miss?
Use Nearby Share for Windows. It works beautifully
Do you have pixel USB drivers installed?
I had a similar issue where I could no longer get USB tethering to work on a Mac where it had previously worked. Solved it by buying a new cable. The original cable still works for charging just doesn't allow me to connect to the Mac for tether or file transfer
Skuddle said:
I took several pictures on my new P7P and am having trouble getting them off of the phone and into my desktop computer. Here's what I have done:
From the P7P Home screen, I tapped "Settings". A "Settings" menu appeared.
I tapped "Connected devices". A "Connected devices" menu appeared.
I tapped "Connected devices".
Under "Other devices", I tapped "USB /file Transfer". Then I tapped "USB File transfer". A "USB Preferences" menu appeared.
Under USB controlled by I tapped "This device", and under "Use USB for" I tapped "File transfer / Android Auto.
And I sat there waiting for something to happen. I expected to see something like "P7P" appear on my computer when I opened the file manager but the only things that showed up were my disk drives. No P7P. What did I miss?
Click to expand...
Click to collapse
Hi,
Since no one here has a crystal ball, What OS is installed on your computer?
Assuming you have a Windows OS, open device manager and see if something pops up plugging your USB cord..?
Good luck,
Sébastien.
I took a look at the C connector to verify that it has 24 pins. It only had 14 pins (or maybe 12 pins? My eyes aren't that good anymore). So I used another cable after verifying that it has the full 24 pins.
@Sébastien! My phone runs Android 13 and my computer runs Windows 10 Home. When I look at the devices on my computer I see a Pixel 7 Pro icon. After clicking that icon I was able to upload my photos from the P7P to my computer!
@K1nsey6: I'll have a look at your link - thank you for providing it.
So: is there a way that I can mark this thread as resolved?
Skuddle said:
I took a look at the C connector to verify that it has 24 pins. It only had 14 pins (or maybe 12 pins? My eyes aren't that good anymore). So I used another cable after verifying that it has the full 24 pins.
@Sébastien! My phone runs Android 13 and my computer runs Windows 10 Home. When I look at the devices on my computer I see a Pixel 7 Pro icon. After clicking that icon I was able to upload my photos from the P7P to my computer!
@K1nsey6: I'll have a look at your link - thank you for providing it.
So: is there a way that I can mark this thread as resolved?
Click to expand...
Click to collapse
I think you have to click on report and report it to a mod, or at least that is what I remember.
Skuddle said:
I took a look at the C connector to verify that it has 24 pins. It only had 14 pins (or maybe 12 pins? My eyes aren't that good anymore). So I used another cable after verifying that it has the full 24 pins.
@Sébastien! My phone runs Android 13 and my computer runs Windows 10 Home. When I look at the devices on my computer I see a Pixel 7 Pro icon. After clicking that icon I was able to upload my photos from the P7P to my computer!
@K1nsey6: I'll have a look at your link - thank you for providing it.
So: is there a way that I can mark this thread as resolved?
Click to expand...
Click to collapse
If you click on the 3 dots at the top of the thread, you can edit the title yourself -- for future reference.
But I took care of it for you! Glad you got it figured out!