Related
The phone is unlocked, with clockworkmod recovery 6.0.1.0 and stock rooted 4.1.1 ROM.
I'm using Windows 7 x64 SP1.
When the phone is ON and the debug mode is activated, it shows correctly under "device manager" and adb works right, but when I reboot in bootloader ADB doesn't see any attached device even if it shows correctly under device manager.
I tried to update the USB driver of the Android SDK but dosn't work
I then uninstalled it and tried to install the Universal Naked Driver (almost all of the nexus or samsung types) but doesn't work
I uninstaleld it and tried another USB driver found on the forum but doesn't work.
I tried to install Android SDK on another PC with Windows 7 x86 SP1 and repeat all the steps but it's the same.
How can I unroot and lock the device if it doesn't shows when in bootloader mode?
You don't use adb in bootloader. You use fastboot.
Locking the bootloader does not unroot by the way.
crespo80 said:
The phone is unlocked, with clockworkmod recovery 6.0.1.0 and stock rooted 4.1.1 ROM.
I'm using Windows 7 x64 SP1.
When the phone is ON and the debug mode is activated, it shows correctly under "device manager" and adb works right, but when I reboot in bootloader ADB doesn't see any attached device even if it shows correctly under device manager.
I tried to update the USB driver of the Android SDK but dosn't work
I then uninstalled it and tried to install the Universal Naked Driver (almost all of the nexus or samsung types) but doesn't work
I uninstaleld it and tried another USB driver found on the forum but doesn't work.
I tried to install Android SDK on another PC with Windows 7 x86 SP1 and repeat all the steps but it's the same.
How can I unroot and lock the device if it doesn't shows when in bootloader mode?
Click to expand...
Click to collapse
Have you tried the Nexus Root Toolkit by WugFresh? It is an application that takes you in several easy steps in installing drivers, rooting, and lock/unlock your device. For installing drivers there are several additional steps when installing them seems unsuccessful.
Leauwie said:
Have you tried the Nexus Root Toolkit by WugFresh? It is an application that takes you in several easy steps in installing drivers, rooting, and lock/unlock your device. For installing drivers there are several additional steps when installing them seems unsuccessful.
Click to expand...
Click to collapse
This is true, I've used Wugfresh toolkit too but I had some problem...
I've Nexus S 9023, with wug toolkit I had no problem to install driver with its very complete guide, this part can solve your problem but make attention on other function, for example with it I've also unlocked my phone but when I tried to root my device freeze.
So maybe that not all toolkit function will work well on all Nexus S.
Please stop with this toolkit nonsense.
Its not a driver issue at this point. Its the user using ADB instead of fastboot.
Remove this and that when he is just using the wrong command. This is the nonsense you see when all people know is some toolkit.
Yeah, I'm an idiot, that was not a driver issue
it's just because I usually root/unroot/unlock/lock my android phones once in a while (when I first buy and when I sell them), so I always forget some basic procedures and searching through the forums is always a mess, I spent three hours doing that, before posting...
I had forgotten ADB and fastboot weren't the same... anyway, I solved with WugFresh (I didn't know it, thanks for the tip) but I could have solved even with plain fastboot commands, I know
Anyway, I'm surprised to realize that the real stock ROM is more stable than the rooted and deodexed stock ROM I was using before, now the 3G/2G/airplanemode swithing is blazing fast and the performance drops on some games are gone... I'll never figure out this Android world
Thanks for all your help :victory:
Hi. Fresh root user here. Maybe the exact problem was solved elsewhere but after 2h of searching I didn't really found anything to solve this.
I installed TWRP on my TF300T, rooted, changed kernel for Clemsyn's Elite Kernel 1.7ghz and didn't change the ROM because of WiFi connection problems.
Anyway, everything went fairly well until I wanted to push tweaks to the android. I then realized that ADB doesn't see my device.
img62.imageshack.us/img62/2922/adbn.jpg
As you can see, fastboot.exe can see my transformer but adb can't. I think that drivers are installed correctly (maybe wrong), USB Debugging is on. There's no error icon under management of installed devices.
I'm on Windows 7 x64.
Agred said:
Hi. Fresh root user here. Maybe the exact problem was solved elsewhere but after 2h of searching I didn't really found anything to solve this.
I installed TWRP on my TF300T, rooted, changed kernel for Clemsyn's Elite Kernel 1.7ghz and didn't change the ROM because of WiFi connection problems.
Anyway, everything went fairly well until I wanted to push tweaks to the android. I then realized that ADB doesn't see my device.
img62.imageshack.us/img62/2922/adbn.jpg
As you can see, fastboot.exe can see my transformer but adb can't. I think that drivers are installed correctly (maybe wrong), USB Debugging is on. There's no error icon under management of installed devices.
I'm on Windows 7 x64.
Click to expand...
Click to collapse
Were are you on your Pad while trying adb?
For me ADB only runs in TWRP recovery or in system
mikaole said:
Were are you on your Pad while trying adb?
For me ADB only runs in TWRP recovery or in system
Click to expand...
Click to collapse
+1
mikaole said:
Were are you on your Pad while trying adb?
For me ADB only runs in TWRP recovery or in system
Click to expand...
Click to collapse
Nah... I didn't even think of connecting in fastboot/recovery/anything with Pad.
uh... I just realised that while connected in TWRP my OS sees TF300T as Transformer and there IS a yellow icon. Even though, I can't install drivers or anything. Windows says that there he couldn't update drivers for this device. Any solutions? Beside using drivers from the SDK I tried downloading drivers from other topics but it didn't help.
Agred said:
Nah... I didn't even think of connecting in fastboot/recovery/anything with Pad.
uh... I just realised that while connected in TWRP my OS sees TF300T as Transformer and there IS a yellow icon. Even though, I can't install drivers or anything. Windows says that there he couldn't update drivers for this device. Any solutions? Beside using drivers from the SDK I tried downloading drivers from other topics but it didn't help.
Click to expand...
Click to collapse
Okay... So I changed the OS and installed drivers again. Now everything works. Dunno why it didn't for the first time, but nevermind now. Thanks for help, anyway
I used to have a rooted EVO 4G through work, but recently they switched me over to an iSheep, and as you can imagine I absolutely hate it. And since it’s for work they’ve installed AirWatch so I can’t jailbreak it. But I also have a TF101 that's currently not rooted.
I got my TF101 about a year ago and rooted it like every good android user should. But after about 6 months, I found a small hair line crack in the touch screen. I unrooted it and sent it in to ASUS for them to repair. I always keep my tablet closed in the docking station when it wasn’t in use. I then found this thread, http://forum.xda-developers.com/showthread.php?t=1498237 that stated this is why the screen cracked. So ASUS and I went back and forth for about a month before they finally covered it under warranty and repaired my tablet.
When I got my tablet back I found they upgraded it to 9.2.1.27. I connected it to a computer so I could reroot it, but my tablet is no longer detected by a computer. I tried two computers and two data cables. I’ve also tried all the methods for installing the drivers. I didn’t want to send it back to ASUS due to the issues I previously had with them. I’ve been following Thing O Doom’s thread, http://forum.xda-developers.com/showthread.php?t=1681155 because he stated he's working on a rooting apk, but he no longer has his TF101 so progress has been slow.
But in my searching I found this thread,http://www.transformerforums.com/fo...rmed-fix-gain-root-after-8-6-5-21-update.html that stated I can get the zip out of an old ASUS update and put that on my sdcard and let the tablet update itself to an older version. ASUS made an instruction sheet for manually updating with a zip, http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101G/e6754_TF101_Update_SOP.pdf. Once downgraded I could use RazerClaw http://forum.xda-developers.com/showthread.php?t=1345049 to root, and then flash a recovery, rom, etc.
Will this method work? I have to believe no, it just seems too easy. I haven’t tried it yet because I worried about bricking my tablet and not being able to fix it since it won’t connect to a computer.
Any response, opinion, recommendation, experience would be greatly appreciated.
I am not sure that will work. It worked when you had 8.6.5.X because it was upgrading to a "newer" version that is 8.6.6.X (for the TF101G).
Now you are on a 9.X, so it most likely will not work.
Have you tried APX mode? I used that to root from the .27 firmware without having to downgrade. Turn off your tablet, hold VOL UP and then press the POWER button for about 3 seconds. The screen will be black, but when you plug it into a computer it should be detected.
If it does work, use EasyFlasher and install a custom recovery (HIGHLY recommend TWRP over CWM).
Here is a guide I wrote on how to root and ROM: LINKY
frederuco said:
I am not sure that will work. It worked when you had 8.6.5.X because it was upgrading to a "newer" version that is 8.6.6.X (for the TF101G).
Now you are on a 9.X, so it most likely will not work.
Have you tried APX mode? I used that to root from the .27 firmware without having to downgrade. Turn off your tablet, hold VOL UP and then press the POWER button for about 3 seconds. The screen will be black, but when you plug it into a computer it should be detected.
If it does work, use EasyFlasher and install a custom recovery (HIGHLY recommend TWRP over CWM).
Here is a guide I wrote on how to root and ROM: LINKY
Click to expand...
Click to collapse
Thanks for the reply. I did try APX mode but I would get a message on both computers I tried stating the device was unrecognizable. I then tried to load the drivers but it still didn't work on either computer.
I guess you could try the other method. Since it is using stock recovery there is very little chance of bricking IMO. It will either install the older firmware, or it will not.
You may be able to use Wolf's tut for this...
benmatlock said:
You may be able to use Wolf's tut for this...
Click to expand...
Click to collapse
Thanks for the response, but I'm unable to successfully connect my tablet to a computer so I can't use ADB. I'm looking for a way to root it without a computer.
air adb, there's at least 1 good free one in the play store.
Lethe6 said:
air adb, there's at least 1 good free one in the play store.
Click to expand...
Click to collapse
Thanks for the response, I looked into that and I thought you had to be rooted for it to work. I'll look at it again.
akt27x said:
Thanks for the reply. I did try APX mode but I would get a message on both computers I tried stating the device was unrecognizable. I then tried to load the drivers but it still didn't work on either computer.
Click to expand...
Click to collapse
Just curious, did you reboot your PC after you installed/uninstalled the drivers?
I had this same problem once. What I did was pulled up Device Mgr and checked for APX drivers. If there was some, I uninstalled and Rebooted the PC. I downloaded these Universal Naked Drivers and saved them where I knew where they would be. I left the Device Mgr open and booted into APX mode. It asked to install drivers. I said yes and it failed. I then pointed it to the Naked Drivers and and it found them pretty easily. Once I saw APX pop up in Device Mgr, I was good to go. I then used EasyFlasher to flash back to .27 with Root. The link in the EasyFlasher OP for stock firmware is off for some reason. I posted the direct link near the last pages. Here it is.
akt27x said:
Thanks for the response, but I'm unable to successfully connect my tablet to a computer so I can't use ADB. I'm looking for a way to root it without a computer.
Click to expand...
Click to collapse
You don't /need/ adb to root it this way, all you need is a terminal interface on your tablet. If you can download and unpack the zip file containing the blob for whatever recovery you wanna use, then link the mmcblk0p4 to tmp, you should be able to be good to go after a dd and reboot.
--edit--
start here: Instructions - Method 2 - UnRooted
then replace step two with "download terminal emulator from the play store"
then replace step three with 'open terminal emulator'
continue with the rest of the tut, using whatever recovery you want (i use Rogue XM)
frederuco said:
I guess you could try the other method. Since it is using stock recovery there is very little chance of bricking IMO. It will either install the older firmware, or it will not.
Click to expand...
Click to collapse
I tried this and you're right it didn't install the older firmware. It looked like it was going to because the status bar was moving at the bottom, but after a few minutes it went to an android laying down with his guts open and a exclamation mark above him.
benmatlock said:
You don't /need/ adb to root it this way, all you need is a terminal interface on your tablet. If you can download and unpack the zip file containing the blob for whatever recovery you wanna use, then link the mmcblk0p4 to tmp, you should be able to be good to go after a dd and reboot.
--edit--
start here: Instructions - Method 2 - UnRooted
then replace step two with "download terminal emulator from the play store"
then replace step three with 'open terminal emulator'
continue with the rest of the tut, using whatever recovery you want (i use Rogue XM)
Click to expand...
Click to collapse
I think I've tried this. I have a terminal emulator installed and I followed some instructions about entering things like this in but I think I got a message stating access denied. But I'll try it again tonight and reply back with the results.
Re: [Q] Possible Downgrade to Root
Using wolf's instructions I tried this with a terminal app on my tablet and got the following.
[email protected]:/ $ mv /data/local/tmp /data/local/tmp.bak
failed on '/data/local/tmp' - Permission denied
I then tried this and got the following.
[email protected]:/ $ dd if=/sdcard/recoveryblob.bin of=/dev/block/mmcblk0p4
/dev/block/mmcblk0p4: cannot open for write: Permission denied
Sent from my Transformer TF101 using XDA Premium HD app
Woody said:
Just curious, did you reboot your PC after you installed/uninstalled the drivers?
I had this same problem once. What I did was pulled up Device Mgr and checked for APX drivers. If there was some, I uninstalled and Rebooted the PC. I downloaded these Universal Naked Drivers and saved them where I knew where they would be. I left the Device Mgr open and booted into APX mode. It asked to install drivers. I said yes and it failed. I then pointed it to the Naked Drivers and and it found them pretty easily. Once I saw APX pop up in Device Mgr, I was good to go. I then used EasyFlasher to flash back to .27 with Root. The link in the EasyFlasher OP for stock firmware is off for some reason. I posted the direct link near the last pages. Here it is.
Click to expand...
Click to collapse
This weekend I tried to install the drivers again. I first went through the control panel and device manager and deleted anything that said android and asus, then rebooted my computer. I then tried to install PDANet because I read that it'll install the drivers needed and if you're having a problem it's an easy way to install them. During the PDANet install it told me to plug my transformer in to load the drivers. When I did it said it was installing new drivers but then it said they didn't install. My transformer came up as an unknown device in device manager.
I then went through and deleted the unknown device and checked in the control panel again, then rebooted my computer. I then put my tablet in APX mode to try and get it to load the drivers. Again it didn't install them and my transformer came up as an unknown device. I deleted the unknown device agian, rebooted, and went to ASUS website and installed ASUS Sync. When it finished I rebooted and then started ASUS Sync. Again when I connected my transformer to my computer it said it was loading the drivers, then it failed, and the computer showed my transformer as an unknown device. ASUS Sync also stated there was no device connected to it.
All the reading I've been doing, it seems like there are some other people experiencing the same issues I am, and I haven't seen where anybody has posted a solution. If anybody has any input please let me know.
I think I'm getting closer. I downloaded WLanAdb from the play store and followed the directions and downloaded the needed files to my computer. In the command prompt I type "WLanAdbTerminal devices" and my tablet will show in the list of devices. But WLanAdb is only setup to except a few commands, the main purpose of the app is for pushing files. It was the only wireless ADB app that I could find that didn't require root.
I then found SSHDroid in the play market and I downloaded putty to my computer. I connect to my computer using that. When I type "adb devices" I get a mesage that states
daemon not running. starting it now on port 5038
daemon started successfully
List of devices attached
I then left putty and went back to the command prompt and typed "adb connect (with my ip address and port from SSHDroid)" and it said it connected to that ip address and port. I then type "adb devices" and there are no devices listed.
Again I think I'm very close to getting my tablet connected wirelessly to adb. I think there is just one simply thing I'm missing. Any help would be greatly appreciated.
I'll continue to update this thread until my tablet is rooted or I reach a dead end, so this will be a reference for anybody experiencing the same issues as me.
Thanks in advance.
akt27x, did you ever come to a solution?
presbypenguin said:
akt27x, did you ever come to a solution?
Click to expand...
Click to collapse
I haven't. I'm now trying to make a Linux boot flash drive to see if I can get my tablet to connect that way, since I've read that Linux doesn't require drivers. I downloaded LinuxLive USB Creator but haven't had the time to try it yet.
Hi All,
It has been a time that I unlocked my TF700t then followed the CM10 documentation to install 10.0 using CWM.
Recently I wanted to upgrade to 10.1 but it didn't work and ended with my tablet rebooting undefinitely.
I reverted then to install back the ASUS stock Rom from their website :
- I downloaded the file
- unzipped it (since it contains another zip)
- put it on a micro SD
- Booted into CWM
- installed the zip
I ended with a working tablet on the stock rom JB 4.1 but know I wanted to try again CM but I cannot access recovery anymore. I can access the bootloader but when I select RCK I get the droid laying on his back with the warning sign.
I thought I would need to flash another recovery (TWRP or other) using fastboot but now when I plug the tablet to my PC it keeps telling me that the device is not recognized. I tried to install the USB driver but it doesn't get detected.
Can anyone please help ? The tablet is working but I am afraid that it has lost some of its capabilities.
Thanks
Nacef
nacef_l said:
Hi All,
It has been a time that I unlocked my TF700t then followed the CM10 documentation to install 10.0 using CWM.
Recently I wanted to upgrade to 10.1 but it didn't work and ended with my tablet rebooting undefinitely.
I reverted then to install back the ASUS stock Rom from their website :
- I downloaded the file
- unzipped it (since it contains another zip)
- put it on a micro SD
- Booted into CWM
- installed the zip
I ended with a working tablet on the stock rom JB 4.1 but know I wanted to try again CM but I cannot access recovery anymore. I can access the bootloader but when I select RCK I get the droid laying on his back with the warning sign.
I thought I would need to flash another recovery (TWRP or other) using fastboot but now when I plug the tablet to my PC it keeps telling me that the device is not recognized. I tried to install the USB driver but it doesn't get detected.
Can anyone please help ? The tablet is working but I am afraid that it has lost some of its capabilities.
Thanks
Nacef
Click to expand...
Click to collapse
Go to your system setting and select storage. Click the 3 dots in the upper right corner and tick the box which is Media device (MTP).. Good luck..
LetMeKnow said:
Go to your system setting and select storage. Click the 3 dots in the upper right corner and tick the box which is Media device (MTP).. Good luck..
Click to expand...
Click to collapse
I just tried that but it did not work, windows is still displaying USB device not recognized.
nacef_l said:
I just tried that but it did not work, windows is still displaying USB device not recognized.
Click to expand...
Click to collapse
What Windows version are you running?
You may have to uninstall the drivers for your MTP device before installing new ones as well as disabling Windows to automatically install drivers for a new device, then manually point it to the Universal Naked Drivers folder.
Or downlaod Android SDK tool ad through it the Platform Tools and USB drivers.
BTW: When you flashed the stock firmware you lost your custom recovery. That's why you see the dead Droid - it's the stock recovery.
If you can't get fastboot to work you can use Motochopper to root your JB 4.1 stock firmware and then GooManager to install the latest TWRP recovery.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
I have tested it on WinXP, Win7, Ubuntu and another box with Win XP. Always same thing the device is not recognized.
When I try to update the driver and point it manually to the naked drivers it cannot detect them.
I guess that even for running Motochopper I will need to get USB working to be able to root my device.
Any help please ? I am stuck with a sluggish stock mod that buries the perfs of my device.
nacef_l said:
I have tested it on WinXP, Win7, Ubuntu and another box with Win XP. Always same thing the device is not recognized.
When I try to update the driver and point it manually to the naked drivers it cannot detect them.
I guess that even for running Motochopper I will need to get USB working to be able to root my device.
Any help please ? I am stuck with a sluggish stock mod that buries the perfs of my device.
Click to expand...
Click to collapse
You do have USB debugging enabled in the Developer settings, do you?
Sent from my DROID4 using Tapatalk 2
berndblb said:
You do have USB debugging enabled in the Developer settings, do you?
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
Yes checked and double checked that
nacef_l said:
Yes checked and double checked that
Click to expand...
Click to collapse
Then it's a driver problem and it's solvable. What do you see in Device Manager under Portable Devices with your tablet connected? Did you uninstall the driver and re-install it?
Did you try to install Asus Sync (which should give you compatible drivers for the TF700)?
So many driver problems lately... there's got to be a pattern to it, but what it may be beats me :what:
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
berndblb said:
Then it's a driver problem and it's solvable. What do you see in Device Manager under Portable Devices with your tablet connected? Did you uninstall the driver and re-install it?
Did you try to install Asus Sync (which should give you compatible drivers for the TF700)?
So many driver problems lately... there's got to be a pattern to it, but what it may be beats me :what:
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
In the Device Manager I have nothing under Portable Devices, but under USB devices it appears an Unrecognized USB Device and a bubble notifying about an unrecognized USB device keeps popping in the task bar. Even after installing ASUS Sync it is not detected.
nacef_l said:
In the Device Manager I have nothing under Portable Devices, but under USB devices it appears an Unrecognized USB Device and a bubble notifying about an unrecognized USB device keeps popping in the task bar. Even after installing ASUS Sync it is not detected.
Click to expand...
Click to collapse
You don't connect your tablet to the PC through the dock USB port, do you?? Just had that in another thread....
If you connect the tablet directly, I'm stumped. No idea why it's not recognized...
Sent from my DROID4 using Tapatalk 2
berndblb said:
You don't connect your tablet to the PC through the dock USB port, do you?? Just had that in another thread....
If you connect the tablet directly, I'm stumped. No idea why it's not recognized...
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
I don't have a dock and I am connecting directly with the cable. I have just reflashed it to stock rom again hoping it resolves itself but nothing.
It's driving me crazy. The stock rom is really sluggish and I want to flash it to CM
Sounds like a windows driver issue to me. You need to force windows to use the right usb drivers. You normally do this by upgrading thenm in device manager. You may have a borked windows installation to fix as well..
Try the ones I have attached.
sbdags said:
Sounds like a windows driver issue to me. You need to force windows to use the right usb drivers. You normally do this by upgrading thenm in device manager. You may have a borked windows installation to fix as well..
Try the ones I have attached.
Click to expand...
Click to collapse
I have tried different windows installations with the different drivers that you provided me, still nothing. It seems to me that the device is not even sending proper ids to the system. Can it be caused by a damaged cable ?
Sent from my iPhone using Tapatalk - now Free
Had the same problem.I fixed it by uninstalling the faulty usb device. Then disconnected the usb cable. Reconnected. And the drivers installed.
nacef_l said:
I have tried different windows installations with the different drivers that you provided me, still nothing. It seems to me that the device is not even sending proper ids to the system. Can it be caused by a damaged cable ?
Click to expand...
Click to collapse
Im having the same problem and after one day of research I could not find a solution. I bought a use TF700 with a standard andriod on it, no mod, not unlocked, no root. When I connect it to the pc I get the same error, meaning just a USB Device showing up. Tried different PC's with different types of OS, no success.
Did you manage to fix the problem ? I would really appreciate some help because now I can't use that tablet in debug mode to test my android applications and that's all I bought it for. By the way, is there a adb tool that works wireless and doesn't neet root access or can I get root access without connecting my pad to my pc ?
Thanks for the help !
Well did you install adb fastboot drivers on the PCs you tried? Did you try it under Linux? Do you have the original Asus cable you connect it with?
adb over network is an option under Developer Options in Omni and Omni based roms - at least the LP roms. I don't think you can get that with an app you install. Probably needs to be baked into the kernel.
berndblb said:
Well did you install adb fastboot drivers on the PCs you tried? Did you try it under Linux? Do you have the original Asus cable you connect it with?
adb over network is an option under Developer Options in Omni and Omni based roms - at least the LP roms. I don't think you can get that with an app you install. Probably needs to be baked into the kernel.
Click to expand...
Click to collapse
First of all thanks a lot for your response, didn't think anyone would still react on that post because it's quite old. Yes I did install adb fastboot drivers, the device only shows up in the usb section saying usb device not recognized. I tried nearly every driver I found, installed the Andriod SDK, the Asus Sync Tool, the naked drivers... then removed them all (including the hidden ones) and installed just the adb fastboot -> no success. I have not tried it on linux, but on windows 7, 8 and 10. Android version is 4.2.1 and Build is 10.6.1.14.10. I now unlocked it using the apk provided by asus (version 7 , 8 did not work). Still for rooting I need pc connection, so I ordered a new cable today (cable is original Asus though).
I installed the Rom Manager and that tells me the ClockworkMod Recovery and TWRP are already installed. I also tried that recovery (power + vol) and got the same result as nacef meaning " I can access the bootloader but when I select RCK I get the droid laying on his back with the warning sign." Thing is, I don't know what the previews owner did, so it might be the reason he sold the Tablet. Can I get anywhere form that Bootloader ? Maybe boot as a Superuser and then use wireless adb to root the device ?
Thanks a lot for your help, Im feeling that I have wasted the money and the only way to get rid of that feeling is to fix the problem
Grab the Puppy Linux live CD from here: http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
It has adb fastboot already installed. If you don't get a connection with that one the problem would be tablet side, not Windows related.
I booted using that Puppy Linux and followed the Guide but no success. After entering "adb devices" I get the output "list of adb devices attached" and than a blank space. So I tried booting in fastboot like you described in your guide and entered "fastboot devices" but that also gives me nothing. Fastboot works though (as it's already included in that image) so I tried a bunch of other fastboot commands but that just results in "waiting for the device".
I don't know what to do now, it has something to do with the tablet itself. Im waiting for the new cable but don't think thats gonna change anything.
You are not trying to do this through the dock port, right? You are connecting the tablet directly to the PC?
The only answer I have left is either a broken cable or one of the pins in the port is bent or broken. Get a magnifying glass and check them out.
Howdy, folks. I recently bricked my tablet thanks to a bad install of CWM, but following Buster's guide I was able to successfully reflash stock firmware and the device runs fine when booted up now.
However, now ADB is not detecting my device. At all. I have tried running the kill-server and start-server commands to see if that would do the trick to no avail. I'm not even receiving an error saying "device not found." Rather, the device listing is left blank whenever I enter the devices command into the command prompt. I can still send commands via fastboot, but I'm concerned that there's something here that I'm missing, or that I have somehow managed to completely bork the motherboard. I have already tried uninstalling and reinstalling the Asus usb drivers, in addition to the ADB drivers/software to no avail.
Does anyone have any suggestions to getting ADB to work for my tablet again? I have scoured the web, particularly these forums, for days looking for an answer, but haven't turned anything up yet. Any help would be greatly appreciated.
Does usb debugging is on?
Graiden05 said:
Does usb debugging is on?
Click to expand...
Click to collapse
Yes, USB debugging is enabled; yes that was the first thing I checked.
Any other ideas?
If You use asus drivers it worth to try universal naked driver.
Graiden05 said:
If You use asus drivers it worth to try universal naked driver.
Click to expand...
Click to collapse
I'll give that a shot this evening.
Graiden05 said:
If You use asus drivers it worth to try universal naked driver.
Click to expand...
Click to collapse
I just installed the naked drivers and tried again, but that didn't work either. Fastboot still works just fine, but I'm still at a complete loss as to how to get adb working again.
Thanks for your help thus far.
Hmm... How windows show tablet when You connect it to PC?
Graiden05 said:
Hmm... How windows show tablet when You connect it to PC?
Click to expand...
Click to collapse
Yeah everything *looks* normal, and appears to be acting normally whenever I have the tablet plugged in. When my tablet is booted up and connected to my pc, I can transfer files to and from with no issue. Also when it's plugged in, there are two different entries under the device manager (one for adb and the other for the tablet itself). It's only when I have my tablet running in bootloader mode that things don't seem to want to work correctly.
I even ran netstat last night to see if there were any programs/services using the same port as adb, and even that turned up nothing. Is it possible that I somehow inadvertently altered the settings on my tablet's motherboard when I installed a bad version of CWM, per my original post?
It shouldn't be posible to brick anything on motherboard with just flash wrong recovery. It might be just "too smart" windows, that reject to use adb driver on same device that alredy used by mtp one. It wasn't a problem before?
Graiden05 said:
It shouldn't be posible to brick anything on motherboard with just flash wrong recovery. It might be just "too smart" windows, that reject to use adb driver on same device that alredy used by mtp one. It wasn't a problem before?
Click to expand...
Click to collapse
It wasn't a problem until I flashed the wrong version of CWM, got stuck in a boot-loop and fixed the problem using fastboot to completely wipe my tablet and start over from scratch.
Edit: I suppose I could try a fresh install of Windows.
Try first remove all drivers and software for tablet. Then install universal naked driver.
Graiden05 said:
Try first remove all drivers and software for tablet. Then install universal naked driver.
Click to expand...
Click to collapse
Update: finally got adb to detect my device. Ended up removing everything Android-related from my desktop and re-downloaded/installed everything, including usb drivers. That did the trick.
Thanks again for the help.