Database Info

[Q] twrp manager to downgrade??

I've been reading and researching for weeks and have finally decided to unlock and install twrp recovery. I have successfully unlocked, but that is as far as I can get. For some reason, my win7 pc thinks my tf700 is a Samsung android phone. In the pc device manager, under Samsung android phone is where my asus adb interface device shows up. Clicking on properties of the Samsung phone does not produce any drivers to uninstall and uninstallation of the phone works, but reinstalls when I connect my tf700. So, I'm stuck. I'm wondering if I can use twrp manager from the playstore to install 10.6.1.14.8.zip to downgrade and then root, install twrp from goo manager ? Fastboot method of installing twrp has not worked for me either, I'm thinking because of the drivers issue. Any one have any thoughts of where I can go from here ? I'd really like to get a custom rom on my tablet.

fwuser said:
I've been reading and researching for weeks and have finally decided to unlock and install twrp recovery. I have successfully unlocked, but that is as far as I can get. For some reason, my win7 pc thinks my tf700 is a Samsung android phone. In the pc device manager, under Samsung android phone is where my asus adb interface device shows up. Clicking on properties of the Samsung phone does not produce any drivers to uninstall and uninstallation of the phone works, but reinstalls when I connect my tf700. So, I'm stuck. I'm wondering if I can use twrp manager from the playstore to install 10.6.1.14.8.zip to downgrade and then root, install twrp from goo manager ? Fastboot method of installing twrp has not worked for me either, I'm thinking because of the drivers issue. Any one have any thoughts of where I can go from here ? I'd really like to get a custom rom on my tablet.
Click to expand...
Click to collapse
Strange problem. Did you have the drivers for a Samsung phone installed prior?
It would be good if you could solve the driver issue - just so that you have fastboot access to your tab in the future.
Sure, you could downgrade to .8 and use Motochopper to root, then GooMangager to install TWRP (though I have never heard of TWRP manager to install stock firmware???), a quick search on the forums will give you the steps.
But to solve the driver issue, you may want to try to install the Universal Naked Drivers from Google, or install the Android SDK tool and through it the Platform Tools and drivers. I would prefer the latter.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4

berndblb said:
Strange problem. Did you have the drivers for a Samsung phone installed prior?
It would be good if you could solve the driver issue - just so that you have fastboot access to your tab in the future.
Sure, you could downgrade to .8 and use Motochopper to root, then GooMangager to install TWRP (though I have never heard of TWRP manager to install stock firmware???), a quick search on the forums will give you the steps.
But to solve the driver issue, you may want to try to install the Universal Naked Drivers from Google, or install the Android SDK tool and through it the Platform Tools and drivers. I would prefer the latter.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
yes, I rooted, twrp'd and installed bone stock on my vzw gs3.
I have used guides to install platform tools, put them in my PATH so I could use a cmd prompt from anywhere, plus I've tried to install the naked drivers and everytime I connect the tablet it goes through the installing drivers through windows update and and says my 700 is a Samsung phone. I uninstall the drivers, don't let it use windows update for drivers, and point it toward naked drivers folder (unzipped) and it doesn't install. says I still have a Samsung phone. click on Samsung phone in device manager and have asus adb interface under it. I must be missing something. maybe I'll redo my platform tools and see if maybe I missed an important step or typed something wrong. when I connect my 700 to the pc in fastboot, it isn't recognized. what should be happening ? what should I be seeing ?

fwuser said:
yes, I rooted, twrp'd and installed bone stock on my vzw gs3.
I have used guides to install platform tools, put them in my PATH so I could use a cmd prompt from anywhere, plus I've tried to install the naked drivers and everytime I connect the tablet it goes through the installing drivers through windows update and and says my 700 is a Samsung phone. I uninstall the drivers, don't let it use windows update for drivers, and point it toward naked drivers folder (unzipped) and it doesn't install. says I still have a Samsung phone. click on Samsung phone in device manager and have asus adb interface under it. I must be missing something. maybe I'll redo my platform tools and see if maybe I missed an important step or typed something wrong. when I connect my 700 to the pc in fastboot, it isn't recognized. what should be happening ? what should I be seeing ?
Click to expand...
Click to collapse
Once connected in fastboot, if you type 'fastboot devices' (without the '), you should see the serial number of your tablet. Otherwise you see: No devices found or something to the effect.

USB not recognized + no Recovery

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.

Device not being detected in recovery mode?

I'm trying to install the 4.4.1 update but my device isn't being detected in recovery mode and thus adb sideload is not working. Would really appreciate some help. I've tried almost every solution that I've googled and nothing seems to be working.

I had a similar issue. Found the naked drivers and they seemed to work after uninstalling the other drivers and rebooting my PC.
Sent from my Nexus 5 using xda app-developers app

jkimbro said:
I had a similar issue. Found the naked drivers and they seemed to work after uninstalling the other drivers and rebooting my PC.
Click to expand...
Click to collapse
Any chance you could post those drivers? Mine works fine, but it would certainly help others if you could post them, or at least post a link to where you found them.

You just need the Google drivers from their website:
http://developer.android.com/sdk/win-usb.html

I had to force the installation of the drivers for the "AOSP on Hammerhead" device in the device manager.
I couldn't even get the device to show until I pressed VolUp in recovery and selected the ADB option in the recovery.
I used USB ADB Composite Interface or something like that by pointing the device manager's Update Driver dialog to the USB drivers from the SDK that EddyOS pointed at.
Windows 7 x64

Yep, had issues with my work PC (Win 7 Pro x64) - had to manually point Device Manager to the android_winusb.inf so it would find the drivers. Bit of a ballache but all working after that!

greenkabbage said:
I couldn't even get the device to show until I pressed VolUp in recovery and selected the ADB option in the recovery.
Click to expand...
Click to collapse
ADB isn't enabled on stock recovery, and sideload is not the same thing. From Google's POV, ADB access on recovery would be a heavy security risk, since you can still access recovery even with your bootloader locked. That's why they created sideloading.
a hammerhead wrote this.

beekay201 said:
ADB isn't enabled on stock recovery, and sideload is not the same thing. From Google's POV, ADB access on recovery would be a heavy security risk, since you can still access recovery even with your bootloader locked. That's why they created sideloading.
Click to expand...
Click to collapse
ADB Server may not be enabled, but ADB obviously is, otherwise you wouldn't be able to connect in order to Sideload, which you can certainly do with stock recovery (even with a locked bootloader). Also, if ADB wasn't available on the device, it wouldn't show up with the "ADB Devices" command.
Now, maybe you mean it's not available once you boot into recovery until you select "apply update from ADB." That may be true (not sure), but that's not what I got from your statement.

jt3 said:
Any chance you could post those drivers? Mine works fine, but it would certainly help others if you could post them, or at least post a link to where you found them.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2513339

jt3 said:
ADB Server may not be enabled, but ADB obviously is, otherwise you wouldn't be able to connect in order to Sideload, which you can certainly do with stock recovery (even with a locked bootloader). Also, if ADB wasn't available on the device, it wouldn't show up with the "ADB Devices" command.
Now, maybe you mean it's not available once you boot into recovery until you select "apply update from ADB." That may be true (not sure), but that's not what I got from your statement.
Click to expand...
Click to collapse
Try it. Select "apply update from ADB", and then try to get a ADB prompt like you would normally, you know, ls /sdcard/, something.

[Q] fastboot, win7/64 drivers?

Hey all,
I've got a new-to-me TF700. Got CROMBi-KK installed, which took some backflips as I could not get fastboot connectivity.
I'd like to be setup for NvFlash (but then never need it), so even though I don't need fastboot right now, I'm feeling the lack.
Data transfer works fine.
ADB (not fastboot) works fine (adb shell gets me a shell, etc, etc)
When I put the phone in fastboot/bootloader "fastboot devices" gets an empty response "fastboot reboot" gets no response.
In Win7 device manager, the TF700, which appears in the "portable devices" section normally when I plug it in, does not appear.
So... probably device drivers.
Have you had this problem on your w7/64 box? How did you fix it? Sorry, but "install linux" isn't all that helpful.
Thanks!

From a semi-related question I'd asked, berndblb mentioned
berndblb said:
Windows is infamous for driver problems.....
Connect the tab in fastboot and open device manager. Near the top you should have an entry for Android device, bootloader mode or something similar, and probably a yellow ! next to it.
Right click it and choose "update driver", let Windows search for it.
If you're lucky it'll install the driver by itself.
If not: What Windows version are you running?
Click to expand...
Click to collapse
Yep, I get an "unknown device" in the USB section when I connect a TF700 in fastboot. Win can't find an appropriate driver. I've tried (manually) ASUS_Android_USB_Drivers and Universal_Naked_Driver_0.72 (both, AFAIR, from the xda tf700 forums). Neither worked.
So... if you got this going, what driver did you use? Thx!

I have a Win7 32 bit laptop and this cool little tool installed the drivers for me:
http://forum.xda-developers.com/showthread.php?t=2588979

berndblb said:
http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
I'd installed that previously (easiest way to setup fastboot). Re-downloaded, re-installed. Went fine. Still no fastboot.
Unzipped the exe, looked at the drivers being installed - labeled "google". No google driver in the driver cache (so no device ever associated with it.)
Looked at the driver error again. Code 43. That means hardware or driver. I'd been taking it to mean driver, but... switched the USB cable to a port in the rear of the PC - and it worked.
Thanks!
So, for anybody with a similar issue, install the package above. If that doesn't work, maybe try a different USB port.

[Help] Google Nexus 5 might be bricked

Heya. First things first:
My Google Nexus 5 is quite... Well bricked.
I've updated CarbonROM a couple of hours ago and since then the phone's been stuck on the Google Logo, as well as starting automatically after shutting it down.
Here's some specifications:
Recovery: ClockworkMod Recovery v6.0.4.5
ROM: Carbon. The version I updated to was CARBON-KK-NIGHTLY-20140706-0428-hammerhead (Edit: For a strange reason, it didn't update to the latest version available.)
I've tried performing:
Reinstall of the same Rom
Factory reset
Following the many unbricking tutorials that require the computer to actually recognize the phone yet no "Nexus 5" appears... Actually nothing appears in devices other than my regular devices.
Phone has been already rooted (obviously) using tutorials here on XDA.
Please help :3

Almogpas said:
Heya. First things first:
My Google Nexus 5 is quite... Well bricked.
I've updated CarbonROM a couple of hours ago and since then the phone's been stuck on the Google Logo, as well as starting automatically after shutting it down.
Here's some specifications:
Recovery: ClockworkMod Recovery v6.0.4.5
ROM: Carbon. The version I updated to was CARBON-KK-NIGHTLY-20140706-0428-hammerhead
I've tried performing:
Reinstall of the same Rom
Factory reset
Following the many unbricking tutorials that require the computer to actually recognize the phone yet no "Nexus 5" appears... Actually nothing appears in devices other than my regular devices.
Phone has been already rooted (obviously) using tutorials here on XDA.
Please help :3
Click to expand...
Click to collapse
if no new devices appear in your device manager we cant yet do much for you. Get the phone recognised in fastboot or in recovery on any pc then restore stock rom or sideload new rom

bitdomo said:
if no new devices appear in your device manager we cant yet do much for you. Get the phone recognised in fastboot or in recovery on any pc then restore stock rom or sideload new rom
Click to expand...
Click to collapse
Do you think I should get a new phone or maybe take it to a professional? I just can't get the pc to recognize it even though I have the drivers installed. (Although even if the drivers weren't installed it would still recognize it...)

Almogpas said:
Do you think I should get a new phone or maybe take it to a professional? I just can't get the pc to recognize it even though I have the drivers installed. (Although even if the drivers weren't installed it would still recognize it...)
Click to expand...
Click to collapse
hmmm... try lg flashtool. Link in my signature.

Almogpas said:
Do you think I should get a new phone or maybe take it to a professional? I just can't get the pc to recognize it even though I have the drivers installed. (Although even if the drivers weren't installed it would still recognize it...)
Click to expand...
Click to collapse
Adb drivers are different when compared to mtp drivers (windows reconizes it as mtp when swtiched on) ... U need adb drivers for pc to recognize it in fastboot mode...will fetch u the link wait
http://developer.android.com/sdk/win-usb.html

doctor_droid said:
Adb drivers are different when compared to mtp drivers (windows reconizes it as mtp when swtiched on) ... U need adb drivers for pc to recognize it in fastboot mode...will fetch u the link wait
Click to expand...
Click to collapse
The main problem in all these solutions is that the phone isn't even recognized by the computer. I'm pretty sure it's the computer's problem but you may never know. Tomorrow I'm retrieving my main rig and I'll post if that rig discovers my phone. If it does, it will make me happier than Columbus discovering America. It not, it will make my wallet really sad as I will be obliged to buy a new one.

Almogpas said:
The main problem in all these solutions is that the phone isn't even recognized by the computer. I'm pretty sure it's the computer's problem but you may never know. Tomorrow I'm retrieving my main rig and I'll post if that rig discovers my phone. If it does, it will make me happier than Columbus discovering America. It not, it will make my wallet really sad as I will be obliged to buy a new one.
Click to expand...
Click to collapse
Yup if the pc is not detecting the phone best is to try wid another usb cable and a different pc... let us knw tomorrow

Did you install those libraries properly?
Freshly baked from my Nexus 5

This universal ADB driver + this ADB and Fastboot pack always does the trick for me.
When you get either ADB or Fastboot working we can help you recover the device.